osmo-msc/tests/test_neighbor_ident.vty

258 lines
9.4 KiB
Plaintext
Raw Normal View History

large refactoring: support inter-BSC and inter-MSC Handover 3GPP TS 49.008 '4.3 Roles of MSC-A, MSC-I and MSC-T' defines distinct roles: - MSC-A is responsible for managing subscribers, - MSC-I is the gateway to the RAN. - MSC-T is a second transitory gateway to another RAN during Handover. After inter-MSC Handover, the MSC-I is handled by a remote MSC instance, while the original MSC-A retains the responsibility of subscriber management. MSC-T exists in this patch but is not yet used, since Handover is only prepared for, not yet implemented. Facilitate Inter-MSC and inter-BSC Handover by the same internal split of MSC roles. Compared to inter-MSC Handover, mere inter-BSC has the obvious simplifications: - all of MSC-A, MSC-I and MSC-T roles will be served by the same osmo-msc instance, - messages between MSC-A and MSC-{I,T} don't need to be routed via E-interface (GSUP), - no call routing between MSC-A and -I via MNCC necessary. This is the largest code bomb I have submitted, ever. Out of principle, I apologize to everyone trying to read this as a whole. Unfortunately, I see no sense in trying to split this patch into smaller bits. It would be a huge amount of work to introduce these changes in separate chunks, especially if each should in turn be useful and pass all test suites. So, unfortunately, we are stuck with this code bomb. The following are some details and rationale for this rather huge refactoring: * separate MSC subscriber management from ran_conn struct ran_conn is reduced from the pivotal subscriber management entity it has been so far to a mere storage for an SCCP connection ID and an MSC subscriber reference. The new pivotal subscriber management entity is struct msc_a -- struct msub lists the msc_a, msc_i, msc_t roles, the vast majority of code paths however use msc_a, since MSC-A is where all the interesting stuff happens. Before handover, msc_i is an FSM implementation that encodes to the local ran_conn. After inter-MSC Handover, msc_i is a compatible but different FSM implementation that instead forwards via/from GSUP. Same goes for the msc_a struct: if osmo-msc is the MSC-I "RAN proxy" for a remote MSC-A role, the msc_a->fi is an FSM implementation that merely forwards via/from GSUP. * New SCCP implementation for RAN access To be able to forward BSSAP and RANAP messages via the GSUP interface, the individual message layers need to be cleanly separated. The IuCS implementation used until now (iu_client from libosmo-ranap) did not provide this level of separation, and needed a complete rewrite. It was trivial to implement this in such a way that both BSSAP and RANAP can be handled by the same SCCP code, hence the new SCCP-RAN layer also replaces BSSAP handling. sccp_ran.h: struct sccp_ran_inst provides an abstract handler for incoming RAN connections. A set of callback functions provides implementation specific details. * RAN Abstraction (BSSAP vs. RANAP) The common SCCP implementation did set the theme for the remaining refactoring: make all other MSC code paths entirely RAN-implementation-agnostic. ran_infra.c provides data structures that list RAN implementation specifics, from logging to RAN de-/encoding to SCCP callbacks and timers. A ran_infra pointer hence allows complete abstraction of RAN implementations: - managing connected RAN peers (BSC, RNC) in ran_peer.c, - classifying and de-/encoding RAN PDUs, - recording connected LACs and cell IDs and sending out Paging requests to matching RAN peers. * RAN RESET now also for RANAP ran_peer.c absorbs the reset_fsm from a_reset.c; in consequence, RANAP also supports proper RESET semantics now. Hence osmo-hnbgw now also needs to provide proper RESET handling, which it so far duly ignores. (TODO) * RAN de-/encoding abstraction The RAN abstraction mentioned above serves not only to separate RANAP and BSSAP implementations transparently, but also to be able to optionally handle RAN on distinct levels. Before Handover, all RAN messages are handled by the MSC-A role. However, after an inter-MSC Handover, a standalone MSC-I will need to decode RAN PDUs, at least in order to manage Assignment of RTP streams between BSS/RNC and MNCC call forwarding. ran_msg.h provides a common API with abstraction for: - receiving events from RAN, i.e. passing RAN decode from the BSC/RNC and MS/UE: struct ran_dec_msg represents RAN messages decoded from either BSSMAP or RANAP; - sending RAN events: ran_enc_msg is the counterpart to compose RAN messages that should be encoded to either BSSMAP or RANAP and passed down to the BSC/RNC and MS/UE. The RAN-specific implementations are completely contained by ran_msg_a.c and ran_msg_iu.c. In particular, Assignment and Ciphering have so far been distinct code paths for BSSAP and RANAP, with switch(via_ran){...} statements all over the place. Using RAN_DEC_* and RAN_ENC_* abstractions, these are now completely unified. Note that SGs does not qualify for RAN abstraction: the SGs interface always remains with the MSC-A role, and SGs messages follow quite distinct semantics from the fairly similar GERAN and UTRAN. * MGW and RTP stream management So far, managing MGW endpoints via MGCP was tightly glued in-between GSM-04.08-CC on the one and MNCC on the other side. Prepare for switching RTP streams between different RAN peers by moving to object-oriented implementations: implement struct call_leg and struct rtp_stream with distinct FSMs each. For MGW communication, use the osmo_mgcpc_ep API that has originated from osmo-bsc and recently moved to libosmo-mgcp-client for this purpose. Instead of implementing a sequence of events with code duplication for the RAN and CN sides, the idea is to manage each RTP stream separately by firing and receiving events as soon as codecs and RTP ports are negotiated, and letting the individual FSMs take care of the MGW management "asynchronously". The caller provides event IDs and an FSM instance that should be notified of RTP stream setup progress. Hence it becomes possible to reconnect RTP streams from one GSM-04.08-CC to another (inter-BSC Handover) or between CC and MNCC RTP peers (inter-MSC Handover) without duplicating the MGCP code for each transition. The number of FSM implementations used for MGCP handling may seem a bit of an overkill. But in fact, the number of perspectives on RTP forwarding are far from trivial: - an MGW endpoint is an entity with N connections, and MGCP "sessions" for configuring them by talking to the MGW; - an RTP stream is a remote peer connected to one of the endpoint's connections, which is asynchronously notified of codec and RTP port choices; - a call leg is the higher level view on either an MT or MO side of a voice call, a combination of two RTP streams to forward between two remote peers. BSC MGW PBX CI CI [MGW-endpoint] [--rtp_stream--] [--rtp_stream--] [----------------call_leg----------------] * Use counts Introduce using the new osmo_use_count API added to libosmocore for this purpose. Each use token has a distinct name in the logging, which can be a globally constant name or ad-hoc, like the local __func__ string constant. Use in the new struct msc_a, as well as change vlr_subscr to the new osmo_use_count API. * FSM Timeouts Introduce using the new osmo_tdef API, which provides a common VTY implementation for all timer numbers, and FSM state transitions with the correct timeout. Originated in osmo-bsc, recently moved to libosmocore. Depends: Ife31e6798b4e728a23913179e346552a7dd338c0 (libosmocore) Ib9af67b100c4583342a2103669732dab2e577b04 (libosmocore) Id617265337f09dfb6ddfe111ef5e578cd3dc9f63 (libosmocore) Ie9e2add7bbfae651c04e230d62e37cebeb91b0f5 (libosmo-sccp) I26be5c4b06a680f25f19797407ab56a5a4880ddc (osmo-mgw) Ida0e59f9a1f2dd18efea0a51680a67b69f141efa (osmo-mgw) I9a3effd38e72841529df6c135c077116981dea36 (osmo-mgw) Change-Id: I27e4988e0371808b512c757d2b52ada1615067bd
2018-12-07 13:47:34 +00:00
OsmoMSC> enable
OsmoMSC# list
...
show neighbor
show neighbor (a|iu) (ran-pc|msc-ipa-name) RAN_PC_OR_MSC_IPA_NAME
show neighbor (a|iu)
show neighbor (a|iu) lac <0-65535>
show neighbor (a|iu) lac-ci <0-65535> <0-65535>
show neighbor (a|iu) cgi <0-999> <0-999> <0-65535> <0-65535>
show neighbor lac <0-65535>
show neighbor lac-ci <0-65535> <0-65535>
show neighbor cgi <0-999> <0-999> <0-65535> <0-65535>
...
OsmoMSC# configure terminal
OsmoMSC(config)# msc
OsmoMSC(config-msc)# list
...
neighbor (a|iu) lac <0-65535> (ran-pc|msc-ipa-name) RAN_PC_OR_MSC_IPA_NAME
neighbor (a|iu) lac-ci <0-65535> <0-65535> (ran-pc|msc-ipa-name) RAN_PC_OR_MSC_IPA_NAME
neighbor (a|iu) cgi <0-999> <0-999> <0-65535> <0-65535> (ran-pc|msc-ipa-name) RAN_PC_OR_MSC_IPA_NAME
no neighbor (a|iu) (ran-pc|msc-ipa-name) RAN_PC_OR_MSC_IPA_NAME
...
OsmoMSC(config-msc)# neighbor?
neighbor Add Handover target configuration
OsmoMSC(config-msc)# neighbor ?
a Neighbor on GERAN-A
iu Neighbor on UTRAN-Iu
OsmoMSC(config-msc)# neighbor a ?
lac Handover target cell by LAC
lac-ci Handover target cell by LAC and CI
cgi Handover target cell by Cell-Global Identifier (MCC, MNC, LAC, CI)
OsmoMSC(config-msc)# neighbor a lac ?
<0-65535> LAC
OsmoMSC(config-msc)# neighbor a lac 1 ?
ran-pc SCCP point code of RAN peer
msc-ipa-name GSUP IPA name of target MSC
OsmoMSC(config-msc)# neighbor a lac 1 ran-pc ?
RAN_PC_OR_MSC_IPA_NAME Point code or MSC IPA name value
OsmoMSC(config-msc)# neighbor iu lac-ci ?
<0-65535> LAC
OsmoMSC(config-msc)# neighbor iu lac-ci 1 ?
<0-65535> CI
OsmoMSC(config-msc)# neighbor iu lac-ci 1 2 ?
ran-pc SCCP point code of RAN peer
msc-ipa-name GSUP IPA name of target MSC
OsmoMSC(config-msc)# neighbor iu lac-ci 1 2 msc-ipa-name ?
RAN_PC_OR_MSC_IPA_NAME Point code or MSC IPA name value
OsmoMSC(config-msc)# neighbor a cgi ?
<0-999> MCC
OsmoMSC(config-msc)# neighbor a cgi 1 ?
<0-999> MNC
OsmoMSC(config-msc)# neighbor a cgi 1 2 ?
<0-65535> LAC
OsmoMSC(config-msc)# neighbor a cgi 1 2 3 ?
<0-65535> CI
OsmoMSC(config-msc)# neighbor a lac 11 ran-pc 1.2.3
OsmoMSC(config-msc)# neighbor a lac-ci 11 12 ran-pc 1.2.3
OsmoMSC(config-msc)# neighbor a cgi 901 70 11 13 ran-pc 1.2.3
OsmoMSC(config-msc)# neighbor iu lac 11 ran-pc 2.3.4
OsmoMSC(config-msc)# neighbor iu lac-ci 11 22 ran-pc 2.3.4
OsmoMSC(config-msc)# neighbor iu cgi 901 070 11 23 ran-pc 2.3.4
OsmoMSC(config-msc)# neighbor a lac 65535 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# neighbor a lac-ci 65535 65533 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# neighbor a cgi 901 70 65535 65531 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# neighbor iu lac 65529 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# neighbor iu lac-ci 65529 65528 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# neighbor iu cgi 901 070 65529 65527 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# # Add the same entries again, but expect them to exist only once below
OsmoMSC(config-msc)# neighbor a lac 11 ran-pc 1.2.3
OsmoMSC(config-msc)# neighbor a lac-ci 11 12 ran-pc 1.2.3
OsmoMSC(config-msc)# neighbor a cgi 901 70 11 13 ran-pc 1.2.3
OsmoMSC(config-msc)# neighbor iu lac 11 ran-pc 2.3.4
OsmoMSC(config-msc)# neighbor iu lac-ci 11 22 ran-pc 2.3.4
OsmoMSC(config-msc)# neighbor iu cgi 901 070 11 23 ran-pc 2.3.4
OsmoMSC(config-msc)# neighbor a lac 65535 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# neighbor a lac-ci 65535 65533 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# neighbor a cgi 901 70 65535 65531 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# neighbor iu lac 65529 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# neighbor iu lac-ci 65529 65528 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# neighbor iu cgi 901 070 65529 65527 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# do show neighbor
neighbor a lac 11 ran-pc 1.2.3
neighbor a lac-ci 11 12 ran-pc 1.2.3
neighbor a cgi 901 70 11 13 ran-pc 1.2.3
neighbor iu lac 11 ran-pc 2.3.4
neighbor iu lac-ci 11 22 ran-pc 2.3.4
neighbor iu cgi 901 070 11 23 ran-pc 2.3.4
neighbor a lac 65535 msc-ipa-name msc-901-70-2
neighbor a lac-ci 65535 65533 msc-ipa-name msc-901-70-2
neighbor a cgi 901 70 65535 65531 msc-ipa-name msc-901-70-2
neighbor iu lac 65529 msc-ipa-name msc-901-70-2
neighbor iu lac-ci 65529 65528 msc-ipa-name msc-901-70-2
neighbor iu cgi 901 070 65529 65527 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# do show neighbor a
neighbor a lac 11 ran-pc 1.2.3
neighbor a lac-ci 11 12 ran-pc 1.2.3
neighbor a cgi 901 70 11 13 ran-pc 1.2.3
neighbor a lac 65535 msc-ipa-name msc-901-70-2
neighbor a lac-ci 65535 65533 msc-ipa-name msc-901-70-2
neighbor a cgi 901 70 65535 65531 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# do show neighbor iu
neighbor iu lac 11 ran-pc 2.3.4
neighbor iu lac-ci 11 22 ran-pc 2.3.4
neighbor iu cgi 901 070 11 23 ran-pc 2.3.4
neighbor iu lac 65529 msc-ipa-name msc-901-70-2
neighbor iu lac-ci 65529 65528 msc-ipa-name msc-901-70-2
neighbor iu cgi 901 070 65529 65527 msc-ipa-name msc-901-70-2
OsmoMSC(config-msc)# do show neighbor a ran-pc 1.2.3
neighbor a lac 11 ran-pc 1.2.3
neighbor a lac-ci 11 12 ran-pc 1.2.3
neighbor a cgi 901 70 11 13 ran-pc 1.2.3
OsmoMSC(config-msc)# do show neighbor iu ran-pc 2.3.4
neighbor iu lac 11 ran-pc 2.3.4
neighbor iu lac-ci 11 22 ran-pc 2.3.4
neighbor iu cgi 901 070 11 23 ran-pc 2.3.4
OsmoMSC(config-msc)# # A cell id that has no ci matches any entries that feature the LAC.
OsmoMSC(config-msc)# # Ambiguous matches are user config error, permitted here but cause error logging during HO
OsmoMSC(config-msc)# do show neighbor a lac 11
neighbor a lac 11 ran-pc 1.2.3
neighbor a lac-ci 11 12 ran-pc 1.2.3
neighbor a cgi 901 70 11 13 ran-pc 1.2.3
OsmoMSC(config-msc)# # The fuzzy matching goes both ways. Same as above.
OsmoMSC(config-msc)# do show neighbor a lac-ci 11 12
neighbor a lac 11 ran-pc 1.2.3
neighbor a lac-ci 11 12 ran-pc 1.2.3
OsmoMSC(config-msc)# do show neighbor a lac-ci 11 13
neighbor a lac 11 ran-pc 1.2.3
neighbor a cgi 901 70 11 13 ran-pc 1.2.3
OsmoMSC(config-msc)# do show neighbor a cgi 901 70 11 13
neighbor a lac 11 ran-pc 1.2.3
neighbor a cgi 901 70 11 13 ran-pc 1.2.3
OsmoMSC(config-msc)# do show neighbor iu lac 11
neighbor iu lac 11 ran-pc 2.3.4
neighbor iu lac-ci 11 22 ran-pc 2.3.4
neighbor iu cgi 901 070 11 23 ran-pc 2.3.4
OsmoMSC(config-msc)# do show neighbor iu lac-ci 11 22
neighbor iu lac 11 ran-pc 2.3.4
neighbor iu lac-ci 11 22 ran-pc 2.3.4
OsmoMSC(config-msc)# do show neighbor iu lac-ci 11 23
neighbor iu lac 11 ran-pc 2.3.4
neighbor iu cgi 901 070 11 23 ran-pc 2.3.4
OsmoMSC(config-msc)# do show neighbor iu cgi 901 70 11 23
neighbor iu lac 11 ran-pc 2.3.4
OsmoMSC(config-msc)# do show neighbor iu cgi 901 070 11 23
neighbor iu lac 11 ran-pc 2.3.4
neighbor iu cgi 901 070 11 23 ran-pc 2.3.4
OsmoMSC(config-msc)# do show neighbor lac 11
neighbor a lac 11 ran-pc 1.2.3
neighbor a lac-ci 11 12 ran-pc 1.2.3
neighbor a cgi 901 70 11 13 ran-pc 1.2.3
neighbor iu lac 11 ran-pc 2.3.4
neighbor iu lac-ci 11 22 ran-pc 2.3.4
neighbor iu cgi 901 070 11 23 ran-pc 2.3.4
OsmoMSC(config-msc)# do show neighbor lac-ci 11 12
neighbor a lac 11 ran-pc 1.2.3
neighbor a lac-ci 11 12 ran-pc 1.2.3
neighbor iu lac 11 ran-pc 2.3.4
OsmoMSC(config-msc)# do show neighbor lac-ci 11 13
neighbor a lac 11 ran-pc 1.2.3
neighbor a cgi 901 70 11 13 ran-pc 1.2.3
neighbor iu lac 11 ran-pc 2.3.4
OsmoMSC(config-msc)# do show neighbor cgi 901 70 11 13
neighbor a lac 11 ran-pc 1.2.3
neighbor a cgi 901 70 11 13 ran-pc 1.2.3
neighbor iu lac 11 ran-pc 2.3.4
OsmoMSC(config-msc)# do show neighbor lac-ci 11 22
neighbor a lac 11 ran-pc 1.2.3
neighbor iu lac 11 ran-pc 2.3.4
neighbor iu lac-ci 11 22 ran-pc 2.3.4
OsmoMSC(config-msc)# do show neighbor lac-ci 11 23
neighbor a lac 11 ran-pc 1.2.3
neighbor iu lac 11 ran-pc 2.3.4
neighbor iu cgi 901 070 11 23 ran-pc 2.3.4
OsmoMSC(config-msc)# do show neighbor cgi 901 70 11 23
neighbor a lac 11 ran-pc 1.2.3
neighbor iu lac 11 ran-pc 2.3.4
OsmoMSC(config-msc)# do show neighbor cgi 901 070 11 23
neighbor a lac 11 ran-pc 1.2.3
neighbor iu lac 11 ran-pc 2.3.4
neighbor iu cgi 901 070 11 23 ran-pc 2.3.4
OsmoMSC(config-msc)# # Ambiguous neighbor config is permitted
OsmoMSC(config-msc)# # This config maps LAC 65535 to two distinct MSCs as well as a local RAN cell.
OsmoMSC(config-msc)# # It is a user config mistake, will cause error logging during handover.
OsmoMSC(config-msc)# neighbor a lac 65535 ran-pc 6.6.6
OsmoMSC(config-msc)# neighbor a lac-ci 65535 65533 msc-ipa-name different-msc
OsmoMSC(config-msc)# do show neighbor a lac 65535
neighbor a lac 65535 msc-ipa-name msc-901-70-2
neighbor a lac-ci 65535 65533 msc-ipa-name msc-901-70-2
neighbor a cgi 901 70 65535 65531 msc-ipa-name msc-901-70-2
neighbor a lac 65535 ran-pc 6.6.6
neighbor a lac-ci 65535 65533 msc-ipa-name different-msc
OsmoMSC(config-msc)# show running-config
...
msc
...
neighbor a lac 11 ran-pc 1.2.3
neighbor a lac-ci 11 12 ran-pc 1.2.3
neighbor a cgi 901 70 11 13 ran-pc 1.2.3
neighbor iu lac 11 ran-pc 2.3.4
neighbor iu lac-ci 11 22 ran-pc 2.3.4
neighbor iu cgi 901 070 11 23 ran-pc 2.3.4
neighbor a lac 65535 msc-ipa-name msc-901-70-2
neighbor a lac-ci 65535 65533 msc-ipa-name msc-901-70-2
neighbor a cgi 901 70 65535 65531 msc-ipa-name msc-901-70-2
neighbor iu lac 65529 msc-ipa-name msc-901-70-2
neighbor iu lac-ci 65529 65528 msc-ipa-name msc-901-70-2
neighbor iu cgi 901 070 65529 65527 msc-ipa-name msc-901-70-2
neighbor a lac 65535 ran-pc 6.6.6
neighbor a lac-ci 65535 65533 msc-ipa-name different-msc
...