CN116056173B - Method for solving influence of SCTP multi-destination address on N2 port signaling synthesis - Google Patents
Method for solving influence of SCTP multi-destination address on N2 port signaling synthesis Download PDFInfo
- Publication number
- CN116056173B CN116056173B CN202310343392.0A CN202310343392A CN116056173B CN 116056173 B CN116056173 B CN 116056173B CN 202310343392 A CN202310343392 A CN 202310343392A CN 116056173 B CN116056173 B CN 116056173B
- Authority
- CN
- China
- Prior art keywords
- key value
- ngap
- amf
- ran
- association key
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0055—Transmission or use of information for re-establishing the radio link
- H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/25—Maintenance of established connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a method for solving the influence of SCTP multi-destination address on N2 port signaling synthesis, comprising the following steps: identifying a message direction according to the signaling flow characteristics of the NGAP protocol; creating a mapping relation between the RAN side association key value and the NGAP context; creating a mapping relation between the AMF side association key value and the RAN side association key value; the method is characterized in that the AMF side can have SCTP coupling multi-destination addresses, and the method always uses the source IP address of the message from the AMF side to the RAN side as the AMF IP address for constructing the association key value by specially processing Xn switching, N2 switching and UE context release flow, so that the association key value of the AMF side is consistent, the influence of the SCTP coupling multi-destination addresses on N2 interface signaling synthesis can be solved, and the DPI signaling acquisition system can be ensured to normally operate when the network element of an operator changes without losing data.
Description
Technical Field
The invention belongs to the technical field of communication, in particular to a method for solving the influence of SCTP multi-destination addresses on N2 port signaling synthesis.
Background
With the development of the mobile communication network, the user has higher perceived experience requirements on the service of the mobile network, so that an operator is required to build a mobile network signaling acquisition system (DPI signaling acquisition system) and a signaling analysis platform, collect and analyze mobile signaling, finely analyze and evaluate network quality and measure perceived experience of the user on the network; thereby guiding the efficient network construction and optimization and improving the service level of the network to the user. Meanwhile, the signaling collection and analysis are the foundation stones for communicating big data, and particularly play a role in epidemic prevention and other fields.
The DPI signaling acquisition system carries out bypass light splitting on related network interface links, carries out real-time analysis on data in the links and generates signaling details, and mainly acquires interfaces of 2G A ports, 3G Iu-CS, iu-PS,4G S1-MME, S6a, gx,5G N2 and the like, wherein the interface transmission layers all adopt SCTP protocols. SCTP is a protocol that transports multiple data streams simultaneously between the two ends of a network connection, provides services similar to UDP and TCP, provides coupling (association) between clients and servers, and provides reliability, sequencing, flow control, and full duplex data transport to applications like TCP, unlike TCP connections which involve only communication between two IP addresses, SCTP supports multihoming, a single SCTP endpoint can support multiple IP addresses, an endpoint may have multiple redundant connections, and each network may have a connection to access the internet infrastructure individually.
When the DPI signaling acquisition system is deployed on line, the mobile signaling network is formally on line and bears the service, so that the data message established by SCTP coupling is difficult to capture, and a flow table like a TCP five-tuple cannot be established, because the conditions of NGAP Xn switching, N2 switching and the like are considered, when the signaling is synthesized, a network element IP address and a unique identifier in the network element are used as associated key values, and because the SCTP coupling multihoming address exists on N2 interface signaling, the associated key values in one direction cannot be associated in the other direction, and the association failure or error can be caused under the condition that the SCTP coupling multihoming address exists on N2 interface signaling, particularly under the condition that NGAP Xn switching and N2 switching are performed.
The method for solving the association failure or error in the presence of SCTP coupling multi-destination address to N2 interface signaling generally comprises the following steps: (1) Learning the coupled multi-destination address of SCTP, namely identifying and correlating SCTP coupled multi-destination address to N2 interface signaling by the inconsistency of the destination IP address of the uplink message and the source IP address of the downlink message in the signaling flow; the method has the defects that the association learning flow is increased, so that the complexity of signaling association is increased, and when the network element of an operator is transited, if the processing cannot be carried out in real time, the signaling association error is inevitably caused; 2) The network element address information is provided by an operator to identify the N2 interface signaling by the SCTP coupling multihoming address to solve the influence of the SCTP coupling multihoming address to the N2 interface signaling on the signaling synthesis, but the method requires that the DPI signaling acquisition system and the operator are synchronous in real time, when the network element changes, the operator provides related information and synchronously configures the related information in the DPI signaling acquisition system, which increases the system inevitably in maintenance and also can lose data inevitably.
Therefore, how to solve the influence of the SCTP coupling multihoming address on N2 interface signaling synthesis becomes the key problem of current research under the condition that the network element SCTP coupling multihoming address is not learned and the network element address information is not acquired from an operator.
Disclosure of Invention
In view of the above problems, the present invention provides a method for solving at least some of the above technical problems, where the method solves the influence of SCTP multi-destination address on N2 signaling synthesis, and by which the influence of SCTP multi-destination address on N2 interface signaling on signaling synthesis can be solved without learning network element SCTP coupled multi-destination address and acquiring network element address information from an operator, so as to ensure that a DPI signaling acquisition system operates normally when an operator network element changes, and data is not lost.
The embodiment of the invention provides a method for solving the influence of SCTP multi-destination addresses on N2 port signaling synthesis, which comprises the following steps: according to NGAP signaling flow characteristics, marking a message direction, taking RAN to AMF as an uplink direction, taking AMF to RAN as a downlink direction, constructing an associated key value of a RAN side when an InitialUEMessage message of the uplink direction is received in an initial UE signaling flow, and creating a mapping relation between the associated key value of the RAN side and NGAP context; when a first downlink message is received, an AMF side association key value is constructed, and a mapping relation between the AMF side association key value and the RAN side association key value is created;
in the Xn switching flow, when receiving a PathSwitchRequest message in the uplink direction, a RAN side association key value is constructed, and a mapping relation between the RAN side association key value and the NGAP context is created, so that a source NGAP context is associated in the PathSwitchRequest message in the uplink direction; when a PathSwitchAcknowledges message in the downlink direction is received, a source AMF side association key value is constructed, a context before switching is acquired through the source AMF side association key value, an AMF side association key value is constructed again, and a mapping relation between the AMF side association key value and the RAN side association key value is created, so that the association of the source NGAP context in the PathSwitchAcknowledges message in the downlink direction is realized; based on which an Xn switching process is completed;
In the NGAP context release flow, when receiving a UEContextRELEASE command message in the downlink direction, constructing an AMF side association key value, and deleting the mapping relation between the AMF side association key value and the RAN side association key value; when receiving a UEContextREACeCompelette message in an uplink direction, constructing a RAN side association key value, and deleting the mapping relation between the RAN side association key value and the NGAP context; based on this, the NGAP context release process is completed;
in the N2 handover procedure, N2 handover signaling on the hand-in side and the hand-out side are associated with each other:
when the cut-in side receives a HandoverRequest message in the downlink direction, an AMF side association key value is constructed, and a mapping relation between the AMF side association key value and the NGAP context is created; when a HandoverAcknowledgemessage in an uplink direction is received, a RAN side association key value is constructed, and a mapping relation between the RAN side association key value and an NGAP context is created; when a first downlink message is received, an AMF side association key value is constructed, a mapping relation between the AMF side association key value and the RAN side association key value is created, and an NGAP context of a HandoverRequest message is obtained; based on this, the N2 handover cut-in side processing is completed;
when the cut-out side receives a HandoverCommand message in the downlink direction, an AMF side association key value is constructed, and the mapping relation between the AMF side association key value and the RAN side association key value is deleted; when an uplink RANStatusTransfer message in the uplink direction is received, a RAN side association key value is constructed, and the mapping relation between the RAN side association key value and the NGAP context is deleted; based on this, the N2 handover cut-out side processing is completed.
Further, the identifying a message direction according to the NGAP signaling flow characteristics, taking RAN to AMF as an uplink direction and taking AMF to RAN as a downlink direction specifically includes:
the uplink direction includes InitialUEMessag, initialContextSetupReponse, UEContextReleaseCompelete, UEContextReleaseRequest, UERadioCapabilityInfoIndication, uplinkNASTransport, pathSwitchRequest, PDUSessionResourceSetupReponse, PDUSessionResourceReleaseReponse, PDUSessionResourceModifyResponse, handoverRequired, handoverAcknowledge, handoverNotification;
the downstream direction includes DownlinkNASTranspor, initialContextSetupRequest, UEContextReleaseCommand, pathSwitchAcknowledg, PDUSessionResourceSetupReques, PDUSessionResourceReleaseCommand, PDUSessionResourceModifyRequest, handoverCommand, handoverRequest.
Further, the creating a mapping relationship between the RAN-side association key value and the NGAP context specifically includes: taking the RAN side association key value as a key value and the NGAP context as a value, and inserting the key value into a RAN_NGAP_CORR table;
the creating the mapping relation between the AMF side association key value and the RAN side association key value specifically comprises the following steps: and taking the AMF side association key value as a key value, taking the RAN side association key value as a value, and inserting the key value into an AMF_NGAP_CORR table.
Further, the building the RAN side association key value and the building the AMF side association key value specifically include:
constructing an RAN side association key value by using the RAN-UE-NGAP-ID and the source IP address;
and constructing an AMF side association key value by using the AMF-UE-NGAP-ID and the source IP address.
Further, associating the source NGAP context in the PathSwitchRequest message in the upstream direction includes:
under the condition that no multi-destination IP address exists, taking the destination IP address as an AMF IP address in an AMF side association key value;
constructing a RAN side association key value by using the RAN-UE-NGAP-ID and the source IP address, and inquiring a RAN_NGAP_CORR table based on the RAN side association key value to obtain the current NGAP context;
acquiring Source-AMF-UE-NGAP-ID value from current NGAP context, constructing association key value with destination IP address, inquiring AMF_NGAP_CORR table based on the association key value to acquire Source RAN association key value, and inquiring RAN_NGAP_CORR table based on the Source RAN association key value to acquire Source NGAP context;
the source NGAP context is populated into the current NGAP context and marked to indicate that the source NGAP context has been associated in the PathSwitchRequest message in the upstream direction.
Further, the implementation associates the source NGAP context in the PathSwitchAcknowledge message in the downstream direction, including:
Under the condition that the multi-destination IP address exists, taking the source IP address of the PathSwitchRequestAcknowledges message in the downlink direction as an AMF IP address in the AMF side association key value;
when receiving a PathSwitchRequestAcknowledges message in a downlink direction, constructing a RAN side association key value by using the RAN-UE-NGAP-ID and the RAN IP address, and inquiring a RAN_NGAP_CORR table based on the RAN side association key value to obtain a new NGAP context;
checking whether the source NGAP context is obtained when processing the PathSwitchRequest message in the upstream direction by the flag in the new NGAP context; if the source NGAP context is not obtained, then:
acquiring Source-AMF-UE-NGAP-ID value from new NGAP context, constructing association key value with Source IP address, inquiring AMF_NGAP_CORR table based on the association key value to acquire Source RAN association key value, and inquiring RAN_NGAP_CORR table based on the Source RAN association key value to acquire Source NGAP context;
the source NGAP context is populated into the new NGAP context.
Further, the method is characterized in that the mapping relation between the AMF side association key value and the RAN side association key value is deleted, and the mapping relation between the RAN side association key value and the NGAP context is deleted, so that NGAP context release is completed; the method specifically comprises the following steps:
When receiving a UEContextRELEASeCommand message in a downlink direction, establishing a RAN side association key value by using a destination IP address and a RAN-UE-NGAP-ID, and inquiring the RAN side association key value to obtain an NGAP context; constructing an AMF side association key value by using a source IP address and an AMF-UE-NGAP-ID, and deleting the mapping relation between the AMF side association key value and the RAN side association key value from an AMF_NGAP_CORR table based on the AMF side association key value;
when receiving the UEContextREaseCompelette message in the uplink direction, a RAN side association key value is constructed by using the source IP address and the RAN-UE-NGAP-ID, and the mapping relation between the RAN side association key value and the NGAP context is deleted from the RAN_NGAP_CORR table by using the RAN side association key value.
Further, the N2 handover includes: when the hand-in side receives the HandoverRequest message in the downlink direction, an associated key value is constructed by using the IP address of the AMF side and the AMF-UE-NGAP-ID, and a mapping relation table of the associated key value and the NGAP context is created, namely, the associated key value of the AMF side is used as the key value, the content of the NGAP context is used as the value, and the associated key value is inserted into the N2_HO_CORR table.
Further, the N2 handover further includes:
when the hand-in side receives the HandoverRequestAcknowledges message in the uplink direction:
if the AMF side does not have the SCTP coupling multihoming address, constructing an AMF side association key value by using the destination IP address and the AMF-UE-NGAP-ID, and inquiring a N2_HO_CORR table to obtain the NGAP context of the HandoverRequest message;
If the SCTP coupling multihoming address exists on the AMF side, constructing an AMF side association key value by the source IP address and the AMF-UE-NGAP-ID according to the signaling flow characteristics of the NGAP protocol, inquiring an N2_HO_CORR table, associating the NGAP context of the Handover request message, and completing the hand-in side signaling context association.
Further, the N2 handover further includes:
when the cut-out side receives a HandoverCommand message in the downlink direction:
and constructing an AMF side association key value by using the source IP address and the AMF-UE-NGAP-ID, and deleting the mapping relation between the AMF side association key value and the RAN side association key value from the AMF_NGAP_CORR table.
When the cut-out side receives an uplink RANStatusTransfer message in the uplink direction:
and deleting the mapping relation between the RAN side association key value and the NGAP context from the RAN_NGAP_CORR table by using the association key value constructed by the source IP address and the RAN-UE-NGAP-ID.
Compared with the prior art, the method for solving the influence of the SCTP multi-destination address on the N2 port signaling synthesis has the following beneficial effects:
1. the invention fully utilizes the characteristics of different signaling flows of the NGAP protocol, accurately analyzes the direction of each signaling message, and exquisitely utilizes the relation among the signaling flows, and in the processes of Xn switching, text release on the NGAP and N2 switching, under the condition that SCTP coupling multihoming addresses exist, AMF side association is simultaneously triggered and processed by messages in the uplink and downlink directions, thereby avoiding association failure caused by the existence of the SCTP coupling multihoming addresses or the association relation of the SCTP coupling multihoming addresses needing to be known in advance when processing in only one direction.
2. The invention realizes that N2 interface signaling data configured with SCTP coupling multi-sink address can be processed correctly without providing network element SCTP multi-sink address information by an operator, and the N2 interface signaling data can be processed intelligently without manual intervention once the program is on line, so that the configuration is not required to be modified when the operator service is cut or expanded, and the problems of data loss, influence on service analysis and the like caused by the cutting and the expansion of the operator service are avoided.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the structure particularly pointed out in the written description and claims thereof as well as the appended drawings.
The technical scheme of the invention is further described in detail through the drawings and the embodiments.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate the invention and together with the embodiments of the invention, serve to explain the invention. In the drawings:
fig. 1 is a schematic diagram of an Xn handover signaling flow in the case that SCTP association multi-homed addresses exist on the AMF side in the related art.
Fig. 2 is a schematic diagram of an Xn switching association flow in the case where SCTP association multi-homed addresses exist on the AMF side in the related art.
Fig. 3 is a schematic diagram of a context release signaling flow of NGAP in the case that SCTP association multi-destination addresses exist on the AMF side in the related art.
Fig. 4 is a schematic diagram of a related art flow for context release association of NGAP in the case that SCTP association multi-destination addresses exist on the AMF side.
Fig. 5 is a schematic diagram of an N2 handover signaling flow in the case that an SCTP association multi-destination address exists on the AMF side in the related art.
Fig. 6 is a schematic diagram of a related art N2 handover association procedure in the case where an SCTP association multi-destination address exists on the AMF side.
Fig. 7 is a schematic diagram of an Xn switching association flow when SCTP coupled multi-destination addresses exist on the AMF side according to an embodiment of the present invention.
Fig. 8 is a schematic diagram of N2 handover association procedure in the case where SCTP association multi-homed addresses exist on the AMF side according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
1. The prior related technology comprises the following steps:
the influence of SCTP coupling multihoming address on N2 interface signaling synthesis in the prior art is specifically explained; at present, the influence of SCTP coupling multi-destination address on N2 interface signaling synthesis is mainly expressed in Xn switching, NGAP context release and N2 switching processes, and the specific contents are as follows:
1.1, the related technology of the existing Xn switching signaling flow:
referring to fig. 1, fig. 1 is a schematic diagram of an Xn switching signaling flow when SCTP coupled multi-destination addresses exist on the AMF side; the RAN initiates a registration request to an AMF IP address 1.1.1.2 by an IP address 1.1.1.1, the AMF side is an SCTP multi-destination address, and the AMF initiates an authentication flow to the RAN by an IP address 1.1.1.3. The mapping relation table of the RAN side association key value and the NGAP context is called as a RAN_NGAP_CORR table, and the mapping relation table of the AMF side association key value and the RAN side association key value is called as an AMF_NGAP_CORR table.
Referring to fig. 2, fig. 2 is a schematic diagram of an Xn switching association flow when SCTP coupled multi-homed addresses exist on the AMF side, and the specific association flow is as follows:
(1) When the uplink direction receives the first signaling message as an InitialUEMessage, a RAN-UE-NGAP-ID and a source IP address, namely a RAN address, are used for constructing a RAN-side association key value, and a mapping relation between the RAN-side association key value and an NGAP context is created, namely, the RAN-side association key value is used as a key value, and the NGAP context content is used as a value and is inserted into a RAN_NGAP_CORR table.
(2) When the downlink direction receives the first signaling message, a RAN side association key value is constructed by using a target IP address, namely a RAN IP address and a RAN-UE-NGAP-ID, and the RAN side association key value is used for inquiring a RAN_NGAP_CORR table to obtain an NGAP context. And constructing an AMF side association key value by using a source IP address, namely an AMF address and an AMF-UE-NGAP-ID, and creating a mapping relation between the AMF side association key value and the RAN side association key value, namely inserting the AMF side association key value as a key value into an AMF_NGAP_CORR table by taking the RAN side association key value as a value, so that the association key value of the RAN side can be obtained by inquiring the AMF_NGAP_CORR table, and then obtaining the NGAP context by inquiring the RAN_NGAP_CORR table by the association key value of the RAN side.
(3) When the uplink direction receives the non-PathSwitchRequest and the UEContextREaseCompelette message, a source IP address, namely a RAN IP address, and a RAN-UE-NGAP-ID are used for constructing a RAN side association key value, and the RAN side association key value is used for inquiring a RAN_NGAP_CORR table to obtain the NGAP context.
(4) When the uplink direction receives the PathSwitchRequest message, a source IP address, namely a RAN address, is used for constructing a RAN side association key value with the RAN-UE-NGAP-ID, and a mapping relation between the RAN side association key value and the NGAP context is created, namely, the RAN side association key value is used as the key value, and the NGAP context content is used as the value to be inserted into a RAN_NGAP_CORR table. And constructing an association key value by using the destination IP, namely the AMF SCTP coupling multihoming IP address and the Source-AMF-UE-NGAP-ID, inquiring an AMF_NGAP_CORR table by using the association key value, and if the SCTP coupling multihoming address exists on the AMF side, because the association key value in the mapping relation between the AMF side association key value and the NGAP context, which is created in the first downlink message before switching, is constructed by the Source IP address and the AMF-UE-NGAP-ID, at the moment, the NGAP context before switching cannot be inquired by constructing the association key value by using the destination IP, namely the AMF SCTP coupling multihoming IP address and the Source-AMF-UE-NGAP-ID.
The AMF_NGAP_CORR table before the switch shown in FIG. 1 uses the IP2 address of the AMF, and the destination IP address of the PathSwitchRequest message is IP1, so that the query fails when the AMF_NGAP_CORR table is queried. Therefore, under the condition that multi-destination addresses exist in the SCTP coupling, the SCTP coupling multi-destination addresses of the AMF network elements can be identified, and the prior art mainly uses network element address information provided by operators to identify that different IP addresses are the multi-destination addresses of the SCTP coupling or uses signaling flow association to learn the association relation of the SCTP coupling multi-destination addresses of the same network element and different IP addresses. Under the condition that the association relation of network element SCTP coupling multihoming addresses is obtained, under the condition that the SCTP coupling multihoming addresses exist, one IP address is associated to the other IP address, an AMF side association key value is constructed through the associated IP address and Source-AMF-UE-NGAP-ID to inquire an AMF_NGAP_CORR table, and then the inquired RAN_NGAP_CORR table is inquired through the inquired RAN side association key value before switching, so that the NGAP context before switching can be inquired.
1.2, the related technology of the existing NGAP context release signaling flow:
referring to fig. 3 and fig. 4, fig. 3 is a schematic diagram of a context release signaling flow of NGAP in the case that SCTP association multi-destination addresses exist on the AMF side; fig. 4 is a schematic diagram of a context release association procedure of NGAP in the case that SCTP association multi-destination addresses exist on the AMF side; when receiving the UEContextREACeCompelette message, a RAN side association key value is constructed by using a source IP address, namely a RAN address, and a RAN-UE-NGAP-ID, and the mapping relation between the RAN side association key value and the NGAP context is deleted from a RAN_NGAP_CORR table by using the RAN side association key value. Because of the existence of the SCTP-coupled multihoming address on the AMF side, at this time, the destination IP address is not an IP address used by the mapping relationship between the AMF-side association key value and the RAN-side association key value created in the first piece of downlink information, at this time, the association relationship between the SCTP-coupled multihoming address obtained in the above step needs to be used, the IP address used in the downlink direction is associated by the destination IP address of the uecontextreeasecomplete message, the AMF-side association key value is constructed by the associated IP address and the AMF-UE-NGAP-ID, and the mapping relationship between the AMF-side association key value and the RAN-side association key value is deleted from the amf_ngap_corr table by using the AMF-side association key value.
1.3, the related technology of the existing N2 switching signaling flow:
referring to fig. 5 and fig. 6, fig. 5 is a schematic diagram of an N2 handover signaling flow in the case that an SCTP association multi-destination address exists on the AMF side; FIG. 6 is a schematic diagram of a N2 handover association procedure in the case where there is an SCTP coupling multi-destination address on the AMF side; the specific association flow is as follows:
(1) When the hand-in side downlink direction receives the Handoverrequest message, an AMF side association key value is constructed by using a source IP address, namely an AMF IP address and an AMF-UE-NGAP-ID, and a mapping relation between the AMF side association key value and the NGAP context is created, namely the AMF side association key value is used as a key value, the NGAP context content is used as a value, and the mapping relation is inserted into a N2_HO_CORR table.
(2) When the hand-in side uplink receives the HandoverRequestAcknowledges message, a RAN-UE-NGAP-ID and a source IP address, namely a RAN address, are used for constructing a RAN-side association key value, and a mapping relation between the RAN-side association key value and an NGAP context is created, namely, the RAN-side association key value is used as a key value, and the NGAP context content is used as a value to be inserted into a RAN_NGAP_CORR table. Because the SCTP coupling multihoming address of the AMF side exists, when the source destination address is not the IP address used by the mapping relation between the AMF side association key value and the NGAP context created when the handlerequest message is processed, the SCTP coupling multihoming address of the AMF network element can be identified under the condition that the multihoming address exists in the SCTP coupling, and the prior art mainly identifies the multihoming address of the SCTP coupling with different IP addresses through network element address information provided by an operator or learns the association relation of the SCTP coupling multihoming address with different IP addresses of the same network element through signaling flow association. Through the obtained association relation of SCTP coupling multi-destination addresses, the IP address used in the downlink direction is associated through the destination IP address of the HandoverRequestAcknowledges message, through the associated IP address and AMF-UE-NGAP-ID, an AMF side association key value is constructed, and the NGAP context of the HandoverRequest message can be obtained by using the AMF side association key value to query the N2_HO_CORR table.
(3) When the hand-in side downlink direction receives the signaling message, an AMF side association key value is constructed by using a source IP address, namely an AMF IP address and an AMF-UE-NGAP-ID, and a mapping relation between the AMF side association key value and the RAN side association key value is created, namely the AMF side association key value is used as a key value and the RAN side association key value is used as a value, and the mapping relation is inserted into an AMF_NGAP_CORR table. And constructing a RAN side association key value by using the target IP address, namely the RAN IP address and the RAN-UE-NGAP-ID, and inquiring the RAN_NGAP_CORR table through the RAN side association key value to obtain the NGAP context.
(4) When the uplink direction of the cut-out side receives the uplink RANStatusTransfer message, a RAN side association key value is constructed by using a source IP address, namely a RAN address and a RAN-UE-NGAP-ID, and the mapping relation between the RAN side association key value and the NGAP context is deleted from a RAN_NGAP_CORR table by using the RAN side association key value. Because of the existence of the SCTP-coupled multihoming address on the AMF side, at this time, the destination IP address is not an IP address used by the mapping relationship between the AMF-side association key value and the RAN-side association key value created in the first piece of downlink information, at this time, the association relationship between the SCTP-coupled multihoming address obtained in the above step needs to be used, the IP address used in the downlink direction is associated by the destination IP address of the uecontextreeasecomplete message, the AMF-side association key value is constructed by the associated IP address and the AMF-UE-NGAP-ID, and the mapping relationship between the AMF-side association key value and the RAN-side association key value is deleted from the amf_ngap_corr table by using the AMF-side association key value.
2. The embodiment of the invention provides a method for solving the influence of SCTP multi-destination addresses on N2 port signaling synthesis, which comprises the following steps:
2.1, in the Xn switching process, when the PathSwitchRequest message is received in the uplink direction, constructing an RAN side association key value, creating a mapping relation between the RAN side association key value and the NGAP context, and realizing association source NGAP context in the PathSwitchRequest message based on the mapping relation; constructing an AMF side association key value, and creating a mapping relation between the AMF side association key value and the RAN side association key value to finish Xn switching; referring to fig. 7, the specific contents are as follows:
when the PathSwitchRequest message is received in the uplink direction, under the condition of no multi-destination address, the destination address in the message is the AMF address in the associated key value of the AMF side, and the RAN associated key value is used for inquiring the RAN_NGAP_CORR table to obtain the NGAP context; and constructing an association key value through the Source-AMF-UE-NGAP-ID and an AMF address, obtaining a Source RAN association key value through an AMF-NGAP-CORR table, obtaining a Source NGAP context through the searched old association key value, and filling the related information of the Source NGAP context into the current NGAP context. The source amf_ngap_corr table is deleted, while the source ran_ngap_corr table is deleted.
In the presence of the multi-destination address, the PathSwitchRequest message destination address is not necessarily the AMF address in the AMF side association key, and if the PathSwitchRequest message destination address is not the AMF address in the AMF side association key, the source address of the PathSwitchRequest acknowledge message is the AMF address in the AMF side association key, after the PathSwitchRequest acknowledge is received, whether the source NGAP context is already associated or not can be known through the queried NGAP context, and if so, it is indicated that the PathSwitchRequest message destination address is the AMF address in the AMF side association key, and no processing is required. If the association is not carried out, the destination address of the PathSwitchRequestAcknowledges message is an AMF address in the association key value of the AMF side, the association key value is constructed through the Source-AMF-UE-NGAP-ID and the Source address, the Source RAN association key value is obtained through an AMF_NGAP_CORR table, the Source NGAP context is obtained through the searched old association key value, and the Source NGAP context related message is filled into the current NGAP context. The source amf_ngap_corr table is deleted, while the source ran_ngap_corr table is deleted.
The complete association flow is as follows:
(1) When the uplink direction receives the PathSwitchRequest message, a RAN-UE-NGAP-ID and a source address, namely a base station address, are used for constructing a RAN side association key value, and a mapping relation between the RAN side association key value and the NGAP context is created, namely, the RAN side association key value is used as the key value, and the NGAP context is used as the value to be inserted into a RAN_NGAP_CORR table. And constructing an association key value through the Source-AMF-UE-NGAP-ID and a destination address, inquiring the AMF-NGAP-CORR table, if a result can be inquired, the value is the association key value of the RAN-NGAP-CORR table before switching, the Source NGAP context can be obtained through the association key value of the RAN-NGAP-CORR table before switching, the related information of the Source NGAP context is filled into the current NGAP context, and a mark is marked to mark the NGAP context before switching in the PathSwitchrequest message.
(2) When receiving the PathSwitchRequestAcknowledges message, constructing a RAN side association key value consisting of a base station address and a RAN-UE-NGAP-ID, and obtaining the NGAP context through the query of the RAN side association key value. The flag in the NGAP context is checked to see if the old NGAP context has been acquired when the PathSwitchRequest message was processed. If the old NGAP context is not acquired, the Source-AMF-UE-NGAP-ID value is acquired from the NGAP context and an association key value is constructed with the Source IP address, the AMF-NGAP-CORR table is queried, the RAN-NGAP-CORR table is queried according to the queried result, namely, the RAN-NGAP-CORR table is queried according to the association key value of the RAN-NGAP-to acquire the NGAP context before the switching, and the NGAP context before the switching is filled into the current NGAP context. And constructing an AMF side association key value by using a source IP address, namely an AMF IP address and an AMF-UE-NGAP-ID, and creating a mapping relation between the AMF side association key value and the RAN side association key value, namely inserting the AMF side association key value serving as a key value and the RAN side association key value serving as a value into an AMF_NGAP_CORR table to finish Xn switching processing.
2.2, in the NGAP context release process, when the cut-out side receives the UEContextREACeCompelette message, deleting the mapping relation between the AMF side association key value and the RAN side association key value, and deleting the mapping relation between the RAN side association key value and the NGAP context to finish NGAP context release; the specific contents are as follows:
when the uplink direction of the cut-out side receives the uecontextreetseseCompelette message, the terminal finishes switching from the source RAN to the target RAN, UEContextReleaseCompelete message from the RAN to the AMF, if the AMF side does not have an SCTP coupling multihoming address, the destination address is the source address of the uecontextreetseseCompelette message, an AMF side association key value is constructed by using the destination IP address, namely the AMF IP address and the AMF-UE-NGAP-ID, the mapping relation between the AMF side association key value and the RAN side association key value is deleted from the AMF-NGAP-CORR table, if the AMF side has an SCTP coupling multihoming address, the destination IP address is not necessarily the IP address used by the AMF side association key value in the AMF-NGAP-CORR table, and the mapping relation between the AMF side association key value and the RAN side association key value cannot be deleted from the AMF-NGAP-CORR table. Therefore, the mapping relationship between the AMF side association key value and the RAN side association key value needs to be deleted from the amf_ngap_corr table by using the association key value constructed by the source IP address, i.e., the AMF IP address, in the downlink message, i.e., the uecontextreessessemcommand, before the uecontextreec message is received in the uplink direction.
The NGAP context release association procedure is as follows:
(1) When the downlink direction of the cut-out side receives the UEContextRELEASE command message, a RAN side association key value is built by using a target IP address, namely a RAN address structure and the RAN-UE-NGAP-ID, and the NGAP context is obtained through the query of the RAN side association key value. And constructing an AMF side association key value by using the source IP address, namely the AMF IP address and the AMF-UE-NGAP-ID, and deleting the mapping relation between the AMF side association key value and the RAN side association key value from the AMF_NGAP_CORR table.
(2) When the uplink direction of the cut-out side receives the UEContextREACeCompelette message, a RAN side association key value is constructed by using a source IP address, namely a RAN address and a RAN-UE-NGAP-ID, and the mapping relation between the RAN side association key value and the NGAP context is deleted from a RAN_NGAP_CORR table by using the RAN side association key value, so that the processing of NGAP context release is completed.
2.3, in the N2 switching process, respectively correlating N2 switching signals of the switching-in side and the switching-out side to finish N2 switching; referring to fig. 8, the N2 handover is divided into two parts of processing of the hand-in side and the hand-out side, and the relation of the hand-in side and the hand-out side N2 handover signaling flows is described as follows:
the hand-in side receives a Handover request message from an AMF to a RAN side, the Handover request message has no RAN side RAN-UE-NGAP-ID in the Handover request, in the association flow of the NGAP protocol, the RAN IP address and the RAN-UE-NGAP-ID are used as key values associated with the NGAP context, for processing N2 handover, the AMF side IP address and the AMF-UE-NGAP-ID are used for constructing an association key value, a mapping relation table of the key values and the NGAP context is created, namely, the AMF side association key value is used as the key value, the NGAP context content is used as the value, and the mapping relation table is inserted into the N2_HO_CORR table.
When the hand-in side receives the Handover RequestAcknowledges message, the Handover RequestAcknowledges message is from RAN to AMF, if the AMF side does not have SCTP coupling multi-destination address, the destination address is the source address of the Handover Request message, the AMF side association key value is constructed by using the destination IP address, namely the AMF IP address and the AMF-UE-NGAP-ID, the NGAP context of the Handover Request message can be obtained by inquiring the N2_HO_CORR table, if the AMF side has SCTP coupling multi-destination address, the destination address is not the source IP address of the Handover Request message, the NGAP context of the Handover Request message can not be obtained by inquiring the NGAP context of the N2-HO_CORR table through the association key value constructed by the destination IP address and the AMF-UE-NGAP-ID, and the NGAP context of the handover Request message can be temporarily not associated by using the signaling characteristics of the NGAP protocol at the moment, and the subsequent handover request message can be received after the NGAP context.
The cut-in side association flow is as follows:
(1) When the hand-in side downlink direction receives the Handoverrequest message, an AMF side association key value is constructed by using a source IP address, namely an AMF IP address and an AMF-UE-NGAP-ID, and a mapping relation between the AMF side association key value and the NGAP context is created, namely the AMF side association key value is used as a key value, the NGAP context content is used as a value, and the mapping relation is inserted into a N2_HO_CORR table.
(2) When the hand-in side uplink receives the HandoverRequestAcknowledges message, a source IP address, namely a RAN address, is used for constructing a RAN side association key value with the RAN-UE-NGAP-ID, and the mapping relation between the RAN side association key value and the NGAP context is created, namely the RAN side association key value is used as the key value, and the NGAP context content is used as the value to be inserted into the RAN_NGAP_CORR table. And constructing an AMF side association key value by using a source IP address, namely an AMF IP address and an AMF-UE-NGAP-ID, inquiring a N2_HO_CORR table, if data is inquired, indicating that the AMF side does not have an SCTP coupling multihoming address, namely a source address of a Handover request message, namely a destination address of the Handover request message, filling an NGAP context related field of the Handover request message into a current NGAP context, marking the NGAP context with a mark for identifying the associated Handover request message in the Handover request Acknowledged message, and deleting the mapping relation between the NGAP context and the NGAP context from the N2_HO_CORR table. If the data is not queried, the existence of the SCTP coupling multi-destination address at the AMF side is indicated, and no processing is performed.
(3) When the downlink direction of the cut-in side receives the downlink RANStatusTransfer message, a source IP address, namely a RAN address structure, is used for establishing a RAN side association key value with the RAN-UE-NGAP-ID, and the NGAP context is obtained through the query of the RAN side association key value. Looking at the flags in the NGAP context, see if the NGAP context of the handlerequest message has been acquired while the handlerequest actknowledgemessage was processed. If the NGAP context of the handlerequest message is not acquired,
And constructing an AMF side association key value by using a source IP address, namely an AMF IP address and an AMF-UE-NGAP-ID, inquiring a N2_HO_CORR table, filling an NGAP context related field of the inquired HandoverRequest message into the current NGAP context, and deleting the mapping relation between the AMF side association key value and the NGAP context from the N2_HO_CORR table. And constructing an AMF side association key value by using a source IP address, namely an AMF IP address and an AMF-UE-NGAP-ID, and creating a mapping relation between the AMF side association key value and the RAN side association key value, namely inserting the AMF side association key value serving as a key value and the RAN side association key value serving as a value into an AMF_NGAP_CORR table to finish N2 switching cut-in side processing.
When the uplink direction of the cut-out side receives the uplink RANStatusTransfer message, the terminal finishes switching from the source RAN to the target RAN, uplinkRANStatusTransfer message from the RAN to the AMF, if the AMF side does not have an SCTP coupling multihoming address, the destination address is the source address of the HandoverRequest message, the AMF side association key value is constructed by using the destination IP address, that is, the AMF IP address and the AMF-UE-NGAP-ID, the mapping relation between the AMF side association key value and the RAN side association key value is deleted from the AMF_NGAP_CORR table, if the AMF side has the SCTP coupling multihoming address, the destination IP address is not necessarily the IP address used by the AMF side association key value in the AMF_NGAP_CORR table, and the mapping relation between the AMF side association key value and the RAN side association key value cannot be deleted from the AMF_NGAP_CORR table. Therefore, the mapping relationship between the AMF side association key value and the RAN side association key value needs to be deleted from the amf_ngap_corr table by using the association key value constructed by the source IP address, i.e., the AMF IP address, in the downlink message before the uplink ranstatustransfer message is received in the uplink direction.
The cut-out side association flow is as follows:
(1) When the downlink direction of the cut-out side receives the handover command message, a RAN side association key value is established by using a target IP address, namely a RAN address structure and the RAN-UE-NGAP-ID, and the NGAP context is obtained through the query of the RAN side association key value. And constructing an AMF side association key value by using the source IP address, namely the AMF IP address and the AMF-UE-NGAP-ID, and deleting the mapping relation between the AMF side association key value and the RAN side association key value from the AMF_NGAP_CORR table.
(2) When the uplink direction of the cut-out side receives the uplink RANStatusTransfer message, a RAN side association key value is constructed by using a source IP address, namely a RAN address and a RAN-UE-NGAP-ID, and the mapping relation between the RAN side association key value and the NGAP context is deleted from a RAN_NGAP_CORR table by using the RAN side association key value, so that N2 handover cut-out side processing is completed.
In the above, the uplink direction includes InitialUEMessag, initialContextSetupReponse, UEContextReleaseCompelete, UEContextReleaseRequest, UERadioCapabilityInfoIndication, uplinkNASTransport, pathSwitchRequest, PDUSessionResourceSetupReponse, PDUSessionResourceReleaseReponse, PDUSessionResourceModifyResponse, handoverRequired, handoverAcknowledge, handoverNotification;
The downstream direction includes DownlinkNASTranspor, initialContextSetupRequest, UEContextReleaseCommand, pathSwitchAcknowledg, PDUSessionResourceSetupReques, PDUSessionResourceReleaseCommand, PDUSessionResourceModifyRequest, handoverCommand, handoverRequest.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (6)
1. A method for resolving the effect of SCTP multihoming addresses on N2 port signaling synthesis, comprising:
according to NGAP signaling flow characteristics, marking a message direction, taking RAN to AMF as an uplink direction, taking AMF to RAN as a downlink direction, constructing an associated key value of a RAN side when an InitialUEMessage message of the uplink direction is received in an initial UE signaling flow, and creating a mapping relation between the associated key value of the RAN side and NGAP context; when a first downlink message is received, an AMF side association key value is constructed, and a mapping relation between the AMF side association key value and the RAN side association key value is created;
In the Xn switching flow, when receiving a PathSwitchRequest message in the uplink direction, a RAN side association key value is constructed, and a mapping relation between the RAN side association key value and the NGAP context is created, so that a source NGAP context is associated in the PathSwitchRequest message in the uplink direction; when a PathSwitchAcknowledges message in the downlink direction is received, a source AMF side association key value is constructed, a context before switching is acquired through the source AMF side association key value, an AMF side association key value is constructed again, and a mapping relation between the AMF side association key value and the RAN side association key value is created, so that the association of the source NGAP context in the PathSwitchAcknowledges message in the downlink direction is realized; based on which an Xn switching process is completed;
in the NGAP context release flow, when receiving a UEContextRELEASE command message in the downlink direction, constructing an AMF side association key value, and deleting the mapping relation between the AMF side association key value and the RAN side association key value; when receiving a UEContextREACeCompelette message in an uplink direction, constructing a RAN side association key value, and deleting the mapping relation between the RAN side association key value and the NGAP context; based on this, the NGAP context release process is completed;
in the N2 handover procedure, N2 handover signaling on the hand-in side and the hand-out side are associated with each other:
When the cut-in side receives a HandoverRequest message in the downlink direction, an AMF side association key value is constructed, and a mapping relation between the AMF side association key value and the NGAP context is created; when a HandoverAcknowledgemessage in an uplink direction is received, a RAN side association key value is constructed, and a mapping relation between the RAN side association key value and an NGAP context is created; when a first downlink message is received, an AMF side association key value is constructed, a mapping relation between the AMF side association key value and the RAN side association key value is created, and an NGAP context of a HandoverRequest message is obtained; based on this, the N2 handover cut-in side processing is completed;
when the cut-out side receives a HandoverCommand message in the downlink direction, an AMF side association key value is constructed, and the mapping relation between the AMF side association key value and the RAN side association key value is deleted; when an uplink RANStatusTransfer message in the uplink direction is received, a RAN side association key value is constructed, and the mapping relation between the RAN side association key value and the NGAP context is deleted; based on this, the N2 switching cut-out side processing is completed;
the creating the mapping relation between the RAN side association key value and the NGAP context specifically comprises the following steps: taking the RAN side association key value as a key value and the NGAP context as a value, and inserting the key value into a RAN_NGAP_CORR table;
the creating the mapping relation between the AMF side association key value and the RAN side association key value specifically comprises the following steps: the AMF side association key value is used as a key value, and the RAN side association key value is used as a value and is inserted into an AMF_NGAP_CORR table;
The building of the RAN side association key value and the building of the AMF side association key value specifically comprise:
constructing an RAN side association key value by using the RAN-UE-NGAP-ID and the source IP address;
constructing an AMF side association key value by using the AMF-UE-NGAP-ID and the source IP address;
the associating the source NGAP context in the PathSwitchRequest message in the uplink direction includes:
under the condition that no multi-destination IP address exists, taking the destination IP address as an AMF IP address in an AMF side association key value;
constructing a RAN side association key value by using the RAN-UE-NGAP-ID and the source IP address, and inquiring a RAN_NGAP_CORR table based on the RAN side association key value to obtain the current NGAP context;
acquiring Source-AMF-UE-NGAP-ID value from current NGAP context, constructing association key value with destination IP address, inquiring AMF_NGAP_CORR table based on the association key value to acquire Source RAN association key value, and inquiring RAN_NGAP_CORR table based on the Source RAN association key value to acquire Source NGAP context;
filling the source NGAP context into the current NGAP context, and marking the current NGAP context to indicate that the source NGAP context is already associated in the PathSwitchRequest message in the upstream direction;
the implementation associates a source NGAP context in a PathSwitchAcknowledge message in a downstream direction, including:
Under the condition that the multi-destination IP address exists, taking the source IP address of the PathSwitchRequestAcknowledges message in the downlink direction as an AMF IP address in the AMF side association key value;
when receiving a PathSwitchRequestAcknowledges message in a downlink direction, constructing a RAN side association key value by using the RAN-UE-NGAP-ID and the RAN IP address, and inquiring a RAN_NGAP_CORR table based on the RAN side association key value to obtain a new NGAP context;
checking whether the source NGAP context is obtained when processing the PathSwitchRequest message in the upstream direction by the flag in the new NGAP context; if the source NGAP context is not obtained, then:
acquiring Source-AMF-UE-NGAP-ID value from new NGAP context, constructing association key value with Source IP address, inquiring AMF_NGAP_CORR table based on the association key value to acquire Source RAN association key value, and inquiring RAN_NGAP_CORR table based on the Source RAN association key value to acquire Source NGAP context;
the source NGAP context is populated into the new NGAP context.
2. The method for solving the problem of the influence of SCTP multi-destination address on N2 port signaling synthesis according to claim 1, wherein the identifying the message direction based on the NGAP signaling flow characteristics, with RAN to AMF as the uplink direction and AMF to RAN as the downlink direction, specifically comprises:
The upward direction comprises InitialUEMessag, initialContextSetupReponse, UEContextReleaseCompelete, UEContextReleaseRequest,
UERadioCapabilityInfoIndication、UplinkNASTransport、PathSwitchRequest、PDUSessionResourceSetupReponse、PDUSessionResourceReleaseReponse、PDUSessionResourceModifyResponse、HandoverRequired、HandoverAcknowledge、HandoverNotification；
The descending direction comprises DownlinkNASTranspor, initialContextSetupRequest, UEContextReleaseCommand, pathSwitchAcknowledg,
PDUSessionResourceSetupReques、PDUSessionResourceReleaseCommand、PDUSessionResourceModifyRequest、HandoverCommand、HandoverRequest。
3. The method for solving the problem of influence of SCTP multi-destination address on N2 port signaling synthesis as claimed in claim 1, wherein the steps of deleting the mapping relation between the AMF side association key value and the RAN side association key value and deleting the mapping relation between the RAN side association key value and the NGAP context are carried out to finish NGAP context release; the method specifically comprises the following steps:
when receiving a UEContextRELEASeCommand message in a downlink direction, establishing a RAN side association key value by using a destination IP address and a RAN-UE-NGAP-ID, and inquiring the RAN side association key value to obtain an NGAP context; constructing an AMF side association key value by using a source IP address and an AMF-UE-NGAP-ID, and deleting the mapping relation between the AMF side association key value and the RAN side association key value from an AMF_NGAP_CORR table based on the AMF side association key value;
when receiving the UEContextREaseCompelette message in the uplink direction, a RAN side association key value is constructed by using the source IP address and the RAN-UE-NGAP-ID, and the mapping relation between the RAN side association key value and the NGAP context is deleted from the RAN_NGAP_CORR table by using the RAN side association key value.
4. The method for resolving the effect of SCTP multihoming address on N2 port signaling synthesis of claim 1, wherein N2 handover comprises: when the hand-in side receives the HandoverRequest message in the downlink direction, an associated key value is constructed by using the IP address of the AMF side and the AMF-UE-NGAP-ID, and a mapping relation table of the associated key value and the NGAP context is created, namely, the associated key value of the AMF side is used as the key value, the content of the NGAP context is used as the value, and the associated key value is inserted into the N2_HO_CORR table.
5. The method for resolving the effect of SCTP multihoming address on N2 port signaling synthesis of claim 1, wherein N2 handover further comprises:
when the hand-in side receives the HandoverRequestAcknowledges message in the uplink direction:
if the AMF side does not have the SCTP coupling multihoming address, constructing an AMF side association key value by using the destination IP address and the AMF-UE-NGAP-ID, and inquiring a N2_HO_CORR table to obtain the NGAP context of the HandoverRequest message;
if the SCTP coupling multihoming address exists on the AMF side, constructing an AMF side association key value by the source IP address and the AMF-UE-NGAP-ID according to the signaling flow characteristics of the NGAP protocol, inquiring an N2_HO_CORR table, associating the NGAP context of the Handover request message, and completing the hand-in side signaling context association.
6. The method for resolving the effect of SCTP multihoming address on N2 port signaling synthesis of claim 1, wherein N2 handover further comprises:
when the cut-out side receives a HandoverCommand message in the downlink direction:
constructing an AMF side association key value by using the source IP address and the AMF-UE-NGAP-ID, and deleting the mapping relation between the AMF side association key value and the RAN side association key value from an AMF_NGAP_CORR table;
when the cut-out side receives an uplink RANStatusTransfer message in the uplink direction:
and deleting the mapping relation between the RAN side association key value and the NGAP context from the RAN_NGAP_CORR table by using the association key value constructed by the source IP address and the RAN-UE-NGAP-ID.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310343392.0A CN116056173B (en) | 2023-04-03 | 2023-04-03 | Method for solving influence of SCTP multi-destination address on N2 port signaling synthesis |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310343392.0A CN116056173B (en) | 2023-04-03 | 2023-04-03 | Method for solving influence of SCTP multi-destination address on N2 port signaling synthesis |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116056173A CN116056173A (en) | 2023-05-02 |
| CN116056173B true CN116056173B (en) | 2023-06-30 |
Family
ID=86125985
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310343392.0A Active CN116056173B (en) | 2023-04-03 | 2023-04-03 | Method for solving influence of SCTP multi-destination address on N2 port signaling synthesis |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116056173B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102316085A (en) * | 2010-07-06 | 2012-01-11 | 大唐移动通信设备有限公司 | Communication method and system for stream control transmission protocol (SCTP) couple |
| CN110650089A (en) * | 2019-10-24 | 2020-01-03 | 北京大学 | Intermediate device supporting multi-path aggregation communication |
| CN112865936A (en) * | 2019-11-28 | 2021-05-28 | 大唐移动通信设备有限公司 | Signaling forwarding method and system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8307097B2 (en) * | 2009-12-18 | 2012-11-06 | Tektronix, Inc. | System and method for automatic discovery of topology in an LTE/SAE network |
| CN102300210B (en) * | 2011-09-01 | 2017-08-04 | 重庆中天重邮通信技术有限公司 | LTE Non-Access Stratum ciphertext decryption methods and its monitoring signaling device |
| CN104660573A (en) * | 2013-11-25 | 2015-05-27 | 上海益尚信息科技有限公司 | Low information interaction multi-base station device for SCTP (stream control transmission protocol) |
| US10743217B2 (en) * | 2014-03-07 | 2020-08-11 | Parallel Wireless, Inc. | X2 brokering between inter-3GPP release eNodeB's |
| CN106713523B (en) * | 2016-12-16 | 2019-12-13 | 无锡华云数据技术服务有限公司 | Network address conversion method based on SCTP |
-
2023
- 2023-04-03 CN CN202310343392.0A patent/CN116056173B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102316085A (en) * | 2010-07-06 | 2012-01-11 | 大唐移动通信设备有限公司 | Communication method and system for stream control transmission protocol (SCTP) couple |
| CN110650089A (en) * | 2019-10-24 | 2020-01-03 | 北京大学 | Intermediate device supporting multi-path aggregation communication |
| CN112865936A (en) * | 2019-11-28 | 2021-05-28 | 大唐移动通信设备有限公司 | Signaling forwarding method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116056173A (en) | 2023-05-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3095032B1 (en) | Controlling of communication network comprising virtualized network functions | |
| CN108429637B (en) | System and method for dynamically detecting process layer network topology of intelligent substation | |
| CN104883736B (en) | The localization method and device of terminal | |
| CN101178715A (en) | Method for combining GIS system with split joint wall system and device thereof | |
| CN105871521A (en) | Data transmission method and device and video monitoring system | |
| CN104243589A (en) | Operation service platform system and method based on Big Dipper RDSS/RNSS | |
| CN106230667B (en) | VTEP keep-alive detection method and device | |
| CN116056173B (en) | Method for solving influence of SCTP multi-destination address on N2 port signaling synthesis | |
| CN105391612A (en) | Virtual extensible local area network (VXLAN) tunnel end point (VTEP) adjacency learning method and VXLAN VTEP adjacency learning device | |
| CN103117880A (en) | Web technology based network topological generation method | |
| CN103873600B (en) | A kind of network address conversion penetrating method and apparatus | |
| CN110035476B (en) | Wireless network control method, wireless access point, access controller and system | |
| CN105827532B (en) | A kind of router is to the discovery method and conversion method for hanging STA real MAC under repeater | |
| CN110519683B (en) | Group position sharing method based on Wi-Fi P2P technology | |
| CN107566208A (en) | The inspection method of civil aviaton's communication system network state | |
| CN108111350B (en) | Method for implementing hot backup of TCP main/standby switching | |
| US20090116454A1 (en) | Communication device, communication system, and handover method | |
| CN114348049B (en) | Multi-radio redundancy control method and device for CTCS (China train control System) | |
| CN103220373B (en) | A kind of distributed logic address exchanges method, apparatus and equipment with physical address | |
| WO2016184025A1 (en) | Device management method and apparatus | |
| CN113794773A (en) | Edge node scheduling method and device, storage medium and electronic equipment | |
| JP3339514B2 (en) | Mobility management device, packet relay device, and mobile communication system | |
| CN101765051B (en) | Method for switching two-layer mobile subnetwork | |
| TWI818328B (en) | System and method for multi-site network quality of experience measurement | |
| CN110460398A (en) | The reliability test system and test method of wireless extensions device synchronous radio channel |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |