Application layer-insensitive service continuity transmission method and device for 5G terminal mobility

By allocating and encapsulating the identification of IPv6 addresses in 5G terminals, dynamically establishing tunnels, the contradiction between service continuity and low latency in 5G mobile communications is solved, and service continuity transmission supported by upper-level applications is realized, reducing traffic delay and tunnel resource occupation.

CN115714970BActive Publication Date: 2024-11-29Chinese People's Liberation Army Cyberspace Force Information Engineering University
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202211456367.5
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-11-21
Publication Date
2024-11-29
Estimated Expiration
2042-11-21

AI Technical Summary

Technical Problem

In 5G mobile communication, it is difficult for the prior art to maintain low latency and continuity of services during terminal movement, especially in the environment where the user plane and the control plane are separated, the traditional session continuous mode has traffic detours and transmission delays. Major problems cannot meet the needs of low latency and high reliability.

Method used

By allocating two types of IPv6 addresses in 5G terminals, they are used for routing identification and session identification, and encapsulating these identifications in the packet header, dynamically establishing GTP tunnels to ensure that services always access the data network through the most recent route when the terminal moves, and implementing Business continuity transmission supported by upper-level applications.

Benefits of technology

It realizes low latency and continuous transmission of services of 5G terminals during mobile, reduces user plane tunnel resource occupation, avoids IP address changes and dependence on upper-level application support in traditional mode, and improves service reliability and efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115714970B_ABST
    Figure CN115714970B_ABST
Patent Text Reader

Abstract

The present invention belongs to the field of mobile communication technology, and particularly relates to a method and device for transmitting business continuity without application layer perception in the movement of 5G terminals. The method comprises: UE moves to a base station gNB, accesses a core network, establishes a PDU session, and establishes communication with a peer node NT; UE moves and switches to a new base station for access, and then the core network receives a message of the UE location change, and determines whether it is necessary to switch UPF; if it is not necessary to switch UPF, under the control of SMF, a bidirectional tunnel from the new gNB to the old UPF is established, during which the IPv6 addresses of both parties remain unchanged; if it is necessary to switch UPF, SMF selects a new UPF nearby, and both parties maintain business continuity; if the UE session ends, including the core network side initiating a release request and the user side initiating a release request, the core network releases the session resources. In the present invention, without the need for application layer protocol support, during the movement of 5G terminals, the service always accesses the data network with the nearest route, ensuring low latency and continuity of the service.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the field of mobile communication technology, and in particular, relates to a method and device for application layer-insensitive service continuity transmission during the movement of a 5G terminal. Background Art

[0002] In mobile communication systems, user terminals (UEs) are always in a state of constant movement. The core network needs to switch the UE state according to the user's business situation and ensure that the UE location information can be obtained and the continuity of data transmission can be ensured when the UE moves. All of these need to be achieved through the mobility management process. How to ensure business continuity is a long-term concern in mobility management.

[0003] The biggest improvement of 5G network compared to 4G network is the complete separation of user plane and control plane. As the only user plane network element, UPF can be flexibly deployed according to business needs and sunk to edge nodes to meet local business needs in low-latency and high-reliability scenarios.

[0004] Currently, in terms of 5G mobility support, 3GPP has provided three session and service continuity modes (SSC). In SSC mode 1, the network will always maintain the UPF that acts as the PDU session anchor when the PDU session is established. During this period, the IP address assigned to the UE remains unchanged; in SSC mode 2, when the user leaves the original UPF area, the network will trigger the release of the original PDU session and anchor UPF, and instruct the terminal user to select a new UPF to establish a new PDU session with the same DN; in SSC mode 3, the network allows the PDU session between the user and the original PDU session anchor to be maintained before the new PDU session is established. At this time, the user has two PDU sessions and UPF session anchors at the same time, and finally releases the original PDU session.

[0005] It can be seen that as the terminal moves, for SSC mode 2, there is an interruption and reconstruction process for both the PDU session and the service, which is suitable for services such as video transmission that tolerate short service interruptions; for SSC mode 1, the PDU session anchor point and IP address remain unchanged, which can ensure the continuity of the session service, such as Figure 5 As shown in the figure, the traffic is circuitous and the transmission delay is large, which cannot meet the low-latency service requirements; for SSC mode 3, the PDU session is established first and then disconnected, and the service continuity is guaranteed through the collaborative mechanism between the network side and the application, thereby meeting the low-latency and high-reliability service requirements, but this mode depends on the support of the upper-layer application. Therefore, it is of practical significance to design and propose a session low-latency continuity mode that is not perceived by the upper-layer application only through the improvement of the network layer protocol. Summary of the invention

[0006] In view of the problems existing in the prior art, the present invention proposes a service continuity transmission method and device that is application-layer-insensitive during the movement of 5G terminals. Without the need for application layer protocol support, when the 5G terminal is moving, the service always accesses the data network via the nearest route, thereby ensuring low latency and continuity of the service.

[0007] In order to achieve the above object, the present invention adopts the following technical solutions:

[0008] The present invention provides a method for transmitting business continuity without application layer perception in mobile 5G terminals. The 5G terminal is represented by UE, the core network network element SMF represents the session management network element, AMF represents the access and mobility management network element, UPF represents the user plane function network element, the node communicating with the 5G terminal in the network is represented by NT, and the base station is represented by gNB; during the session, the UE needs to be allocated two types of IPv6 addresses by the core network, one is a routing identifier for routing addressing in the network; the other is a session identifier for identifying the communication identity of the node in the network; the method comprises the following steps:

[0009] Step 1: The UE moves to the base station gNB, accesses the core network, establishes a PDU session, and establishes communication with the peer node NT.

[0010] Step 2: The UE moves and switches to a new base station for access. Then the core network receives a message about the UE location change and determines whether the UPF needs to be switched. If not, execute step 3, otherwise execute step 4.

[0011] Step 3: Under the control of SMF, a bidirectional tunnel is established from the new gNB to the old UPF. During this period, the IPv6 addresses of both parties remain unchanged.

[0012] Step 4: SMF selects a new UPF nearby, and both parties maintain business continuity;

[0013] Step 5: If the UE continues to move, execute step 2;

[0014] Step 6: If the UE session ends, including the core network side initiating a release request and the user side initiating a release request, the core network releases the session resources.

[0015] Furthermore, the session identifier has two allocation modes, including fixed allocation of static IPv6 addresses and allocation of dynamic IPv6 addresses during a session; the allocated session identifier should be unique, which is achieved by allocating a unique local address or specifying an IP network segment.

[0016] Furthermore, the implementation process of step 1 is as follows:

[0017] Step 1.1, when the initial session is established, according to the UE session identifier allocation mode stored in the core network, if it is configured as dynamic allocation mode, the SMF allocates a dynamic IPv6 address to the UE, otherwise the UE's static address is directly used as the session identifier;

[0018] Step 1.2: SMF selects the nearest UPF to provide access to the UE, and allocates an IPv6 address to the UE as a routing identifier based on the selected UPF.

[0019] Step 1.3: Establish a GTP tunnel between base station gNB1 and UPF.

[0020] Step 1.4, the UE encapsulates the routing identifier in the source address field of the data packet, and encapsulates the session identifier in the destination option extension header of the data packet, and initiates a communication request to the peer node NT;

[0021] Step 1.5: After receiving the message, the NT swaps the source address and destination option extension headers in the message, thereby providing the UE's session identifier to the upper layer application for identifying the UE's communication identity; at the same time, the NT establishes a mapping cache between the monogram identifier and the routing identifier;

[0022] Step 1.6, NT encapsulates the UE's routing identifier in the destination address field of the data packet, encapsulates the session identifier in the routing extension header of the data packet, and then sends the data to the UE;

[0023] Step 1.7: After receiving the message, the UE swaps the destination address and the routing extension header in the message, thereby providing the UE session identifier to the upper layer application;

[0024] Step 1.8: Both parties establish a TCP connection and start transmitting data.

[0025] Furthermore, in step 4, the SMF selects a new UPF nearby, and both parties maintain service continuity according to the following steps:

[0026] Step 4.1, SMF notifies the old UPF that the UE location has changed, and the old UPF caches the routing identifier of the current UE for a period of time;

[0027] Step 4.2, SMF reselects a new UPF and assigns a new routing identifier to the UE;

[0028] Step 4.3, under the control of SMF, the tunnel between the old UPF and the old base station is dismantled, a GTP tunnel from the new base station to the new UPF is established, and a GTP tunnel from the old UPF to the new UPF to the new base station is temporarily established. If there is no direct interface between the old UPF and the new UPF, an I-UPF needs to be allocated to ensure the use of the tunnel. The tunnel lifetime is set by the system. After the lifetime expires, the SMF organizes the tunnel dismantling;

[0029] Step 4.4, UE sends a binding registration message to NT to inform the new routing identifier;

[0030] Step 4.5, after receiving the binding message, the NT updates the mapping relationship between the stored UE routing identifier and the session identifier;

[0031] Step 4.6: If NT sends data before the binding message reaches NT, execute step 4.7; otherwise, execute step 4.8;

[0032] Step 4.7, NT uses the old routing identifier as the destination address to send a data packet to the UE;

[0033] Step 4.8, NT uses the new routing identifier as the destination address to send a data packet to the UE;

[0034] Step 4.9, the UE encapsulates the new routing identifier in the source address field of the data packet, and encapsulates the session identifier in the destination option extension header of the data packet, and sends the data packet to the peer node NT;

[0035] Step 4.10: After receiving the message, the NT swaps the source address and destination option extension headers in the message and provides the UE session identifier to the upper layer application.

[0036] The present invention also provides a 5G terminal mobile application layer non-sensitive business continuity transmission device, including:

[0037] The node communication establishment module is used for the UE to move to the base station gNB, access the core network, establish a PDU session, and establish communication with the peer node NT;

[0038] The UPF switching judgment module is used for UE movement and switching to a new base station for access. Then the core network receives the message of UE location change and determines whether the UPF needs to be switched;

[0039] The new gNB to old UPF tunnel establishment module is used to establish a bidirectional tunnel from the new gNB to the old UPF under the control of the SMF. During this period, the IPv6 addresses of both parties remain unchanged;

[0040] The business continuity maintenance module is used for SMF to select a new UPF nearby so that both parties can maintain business continuity;

[0041] The session resource release module is used to release the session resources by the core network if the UE session ends, including when the core network side initiates a release request and when the user side initiates a release request.

[0042] Compared with the prior art, the present invention has the following advantages:

[0043] 1. Compared with SSC mode 1, the application layer-insensitive service continuity transmission method of the 5G terminal in the mobile of the present invention is that the core network element SMF always allocates the nearest UPF as the anchor point for the terminal to access the data network, and the service always accesses the data network from the nearest route to ensure low-latency data transmission and reduce the user plane tunnel resource occupancy.

[0044] 2. During the movement of the terminal, the GTP tunnel is dynamically established to ensure that the data channel in the core network is not interrupted.

[0045] 3. By utilizing the massive address characteristics of IPv6, two types of IPv6 addresses are allocated to the terminal as routing identifiers and session identifiers, where the routing identifier is used for routing addressing and the session identifier is used to identify the communication identity of the terminal; the two types of identifiers are encapsulated in the header of the data packet using the extended header provided by IPv6, and the header position of the data packet is exchanged at the communication node, so that during the routing switching process, the node IP perceived by the upper-layer application is always the session identifier. Compared with the existing 5G provided SSC mode 3, the user's IP address does not need to change, and the support of the upper-layer application is not required to ensure business continuity. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0047] Figure 1 This is a schematic diagram of the IPv6 data packet header format;

[0048] Figure 2 It is a flowchart of a method for transmitting application-layer-insensitive business continuity during the movement of a 5G terminal according to the first embodiment of the present invention;

[0049] Figure 3 It is a flow chart of a method for transmitting application-layer-insensitive business continuity during 5G terminal movement before UE position movement according to Embodiment 2 of the present invention;

[0050] Figure 4 It is a flow chart of a method for transmitting application-layer-insensitive business continuity during 5G terminal movement after UE position movement according to Embodiment 2 of the present invention;

[0051] Figure 5 This is a data routing diagram of UE-NT based on SSC mode 1 in a 5G terminal mobile scenario;

[0052] Figure 6Schematic diagram of data routing of UE-NT in the 5G terminal mobile scenario of the second embodiment of the present invention

[0053] Figure 7 This is a data routing diagram of NT-UE in a 5G terminal mobile scenario according to the second embodiment of the present invention. DETAILED DESCRIPTION

[0054] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0055] Embodiment 1

[0056] In a method for application layer-insensitive service continuity transmission during the movement of a 5G terminal in this embodiment, the 5G terminal is represented by UE, the core network element SMF represents a session management network element, the AMF represents an access and mobility management network element, the UPF represents a user plane function network element, the node in the network that communicates with the 5G terminal is represented by NT, and the base station is represented by gNB.

[0057] IPv6 is a new generation network layer protocol used to replace IPV4. It can provide enough IP addresses for terminals. Compared with IPv4, it adds an extended header to facilitate functional expansion. The format of the data packet header is as follows: Figure 1 As shown. In terms of mobility support, through the destination option extension header provided by IPv6, the mobile node communicates with the peer node through the home address and notifies the peer node of its own forwarding address, avoiding the triangular routing problem existing in IPv4. 5G uses an anchor point to access the DN network, and the GTP tunnel method is used to transmit data within the core network, which is naturally adapted to the mobile IPV6 protocol. Based on this, we can learn from the existing mobile IPv6 protocol, use the extended header and massive address characteristics provided by IPv6, assign two types of IP addresses to mobile terminals, encapsulate them in the extended header of the data packet for transmission, and adapt the existing 5G SSC mode, which can effectively solve the contradiction between low latency and business continuity, and make the mobile process imperceptible to the upper-layer applications.

[0058] During the session, the core network needs to allocate two types of IPv6 addresses to the UE: one is the routing identifier, which is used for routing addressing in the network; the other is the session identifier, which is used to identify the communication identity of the node in the network. The session identifier has two allocation modes, including fixed allocation of static IPv6 addresses and allocation of dynamic IPv6 addresses during the session; the allocated session identifier should be globally unique, which can be achieved by allocating a unique local address or specifying an IP network segment.

[0059] The method of this example includes the following steps: Figure 2 As shown:

[0060] Step S1, UE moves to the base station gNB, accesses the core network, establishes a PDU session, and establishes communication with the opposite node NT. The specific implementation process is as follows: Step S101 to Step S108.

[0061] Step S101, when the initial session is established, according to the UE session identifier allocation mode stored in the core network, if it is configured as a dynamic allocation mode, the SMF allocates a dynamic IPv6 address to the UE, otherwise the UE's static address is directly used as the session identifier.

[0062] Step S102, the SMF selects the nearest UPF to provide to the UE for access, and allocates an IPV6 address to the UE as a routing identifier based on the selected UPF.

[0063] Step S103, establish the GTP tunnel of base station gNB1-UPF.

[0064] Step S104: The UE encapsulates the routing identifier in the source address field of the data packet, and encapsulates the session identifier in the destination option extension header of the data packet, and initiates a communication request to the opposite node NT.

[0065] Step S105, after receiving the message, the NT swaps the source address and the destination option extension header in the message, thereby providing the UE's session identifier to the upper layer application for identifying the UE's communication identity; at the same time, the NT establishes a mapping cache of the session identifier and the routing identifier.

[0066] Step S106, the NT encapsulates the UE's routing identifier in the destination address field of the data packet, encapsulates the session identifier in the routing extension header of the data packet, and then sends the data to the UE.

[0067] Step S107: After receiving the message, the UE exchanges the destination address and the routing extension header in the message, thereby providing the UE session identifier to the upper layer application.

[0068] Step S108: Both parties establish a TCP connection and start transmitting data.

[0069] In step S2, the UE moves and switches to a new base station for access. Then the core network receives a message about the UE location change and determines whether it is necessary to switch the UPF. If not, execute step S3, otherwise execute step S4.

[0070] Step S3: Under the control of SMF, a bidirectional tunnel is established from the new gNB to the old UPF. During this period, the IPv6 addresses of both parties remain unchanged.

[0071] In step S4, the SMF selects a new UPF nearby, and both parties maintain business continuity according to steps S401 to S410.

[0072] Step S401, SMF notifies the old UPF that the UE location changes, and the old UPF caches the routing identifier of the current UE for a period of time.

[0073] Step S402: SMF reselects a new UPF and assigns a new routing identifier to the UE.

[0074] Step S403, under the control of SMF, the tunnel between the old UPF and the old base station is dismantled, a GTP tunnel from the new base station to the new UPF is established, and a GTP tunnel from the old UPF to the new UPF to the new base station is temporarily established. If there is no direct interface between the old UPF and the new UPF, I-UPF needs to be allocated to ensure the use of the tunnel. The tunnel lifetime is set by the system. After the lifetime expires, SMF organizes the dismantling of the tunnel.

[0075] Step S404: The UE sends a binding registration message to the NT to inform the NT of the new routing identifier.

[0076] Step S405: After receiving the binding message, the NT updates the stored mapping relationship between the UE routing identifier and the session identifier.

[0077] Step S406: If the NT sends data before the binding message reaches the NT, then execute step S407; otherwise, execute step S408.

[0078] Step S407: The NT uses the old routing identifier as the destination address to send a data packet to the UE.

[0079] Step S408: The NT uses the new routing identifier as the destination address to send a data packet to the UE.

[0080] Step S409: The UE encapsulates the new routing identifier in the source address field of the data packet, and encapsulates the session identifier in the destination option extension header of the data packet, and sends the data packet to the opposite node NT.

[0081] Step S410: After receiving the message, the NT swaps the source address and destination option extension headers in the message and provides the UE session identifier to the upper layer application.

[0082] Step S5: If the UE continues to move, execute step S2.

[0083] Step S6: If the UE session ends, including the core network side initiating a release request and the user side initiating a release request, the core network releases session resources including addresses, tunnels, etc.

[0084] Embodiment 2

[0085] In this example, the application layer-insensitive service continuity transmission method of the 5G terminal in the mobile state, the 5G terminal UE communicates with the opposite node NT, adopts the dynamic allocation session identification mode, and the NT allocates the IPv6 address ip_C. Initially, the UE accesses from the base station gNB1. During the mobile process, it switches from the anchor point UPF1 to the anchor point UPF2, and UPF1 and UPF2 have a direct N9 interface. The method includes the following steps:

[0086] Step A: UE accesses the core network from base station gNB1, establishes a PDU session, and establishes a communication connection with the peer NT. The specific implementation process is as follows: Step A1 to Step A8. Figure 3 shown.

[0087] Step A1, when the initial session is established, the SMF allocates a dynamic session identifier ip_U to the UE. The dynamic session identifier adopts the unique local address specification defined in RFC4193 and is generated in a pseudo-random manner.

[0088] Step A2, SMF selects UPF1 nearby to provide it to UE for access, and allocates UE routing identifier ip_R1.

[0089] Step A3, establish a bidirectional GTP tunnel between gNB1 and UPF1.

[0090] In step A4, the UE encapsulates the routing identifier ip_R1 in the source address field of the data packet, and encapsulates the session identifier ip_U in the destination option extension header of the data packet, and initiates a communication request to the peer NT.

[0091] Step A5, after receiving the message, NT swaps the source address ip_R1 and the destination option extension header ip_U in the message, and provides ip_U to the upper layer application to identify the identity of the UE communication; at the same time, NT establishes a mapping cache of the session identifier and the routing identifier, and the mapping relationship is ip_U-ip_R1.

[0092] Step A6, NT encapsulates ip_R1 in the destination address field of the data packet, encapsulates ip_U in the routing extension header of the data packet, and then sends the data to the UE.

[0093] Step A7: After receiving the message, the UE exchanges the destination address ip_R1 and the routing extension header ip_U in the message, thereby providing the UE session identifier ip_U to the upper layer application.

[0094] Step A8: Both parties establish a TCP connection and transmit data. At this time, the destination IP address perceived by the UE application layer is ip_U and the source address is ip_C. The destination IP address perceived by the NT application layer is ip_C and the source address is ip_U.

[0095] Step B: The UE moves to the base station gNB2 for access. The core network detects that the UE's location has changed and determines that the anchor point needs to be switched.

[0096] Step C: SMF selects a new UPF2 nearby and follows steps C1 to C10 to keep the service going. Figure 4 shown.

[0097] Step C1, SMF notifies UPF1 that the location of the UE has changed. UPF1 caches the mapping between the routing identifier ip_R1 and the UE and sets a cache timer t0. If the timer expires, the mapping relationship is deleted.

[0098] In step C2, SMF selects UPF2 nearby for UE to access the network and allocates a new routing identifier ip_R2 to the UE.

[0099] Step C3, under the control of SMF, the bidirectional GTP tunnel of gNB1-UPF1 is dismantled, a bidirectional GTP tunnel of gNB2-UPF2 is established, and a UPF1-UPF2-gNB2 direction GTP tunnel is temporarily established, and the tunnel lifetime t1 is set. If the lifetime expires, the temporary tunnel is dismantled.

[0100] Step C4, the UE sends a binding registration message to the NT to inform the new routing identifier ip_R2.

[0101] Step C5: After receiving the binding message, the NT updates the stored mapping relationship between the UE routing identifier and the session identifier to ip_U-ip_R2.

[0102] Step C6: If the NT sends data before the binding message reaches the NT, then execute step C7; otherwise, execute step C8.

[0103] Step C7, NT uses the old routing identifier ip_R1 as the destination address to send data to UE, and the data transmission path is NT-UPF1-UPF2-UE. Figure 6 shown.

[0104] Step C8, NT uses the new routing identifier ip_R2 as the destination address to send data to UE, and the data transmission path is UE-UPF2-NT. Figure 7 shown.

[0105] Step C9, the UE encapsulates ip_R2 in the source address field of the data packet, and encapsulates ip_U in the destination option extension header of the data packet, and transmits data to the opposite node NT.

[0106] Step C10, after receiving the message, the peer NT swaps the positions of ip_R2 and ip_U in the message, and provides ip_U to the upper layer application. Then, during the communication between the two parties, the IP addresses of the two parties perceived by the application layer are ip_U and ip_C respectively.

[0107] Step D: If the UE ends the session, the UE initiates a session termination request to the core network. After receiving the request, the core network releases resources such as IPv6 addresses and tunnels.

[0108] Corresponding to the above-mentioned service continuity transmission method for application layer insensitivity during 5G terminal movement, this embodiment further proposes a service continuity transmission device for application layer insensitivity during 5G terminal movement, including:

[0109] The node communication establishment module is used for the UE to move to the base station gNB, access the core network, establish a PDU session, and establish communication with the peer node NT;

[0110] The UPF switching judgment module is used for UE movement and switching to a new base station for access. Then the core network receives the message of UE location change and determines whether the UPF needs to be switched;

[0111] The new gNB to old UPF tunnel establishment module is used to establish a bidirectional tunnel from the new gNB to the old UPF under the control of the SMF. During this period, the IPv6 addresses of both parties remain unchanged;

[0112] The business continuity maintenance module is used for SMF to select a new UPF nearby so that both parties can maintain business continuity;

[0113] The session resource release module is used to release the session resources by the core network if the UE session ends, including when the core network side initiates a release request and when the user side initiates a release request.

[0114] The present invention uses the extended header and massive address characteristics provided by IPv6 to allocate two types of IPv6 addresses to the terminal, and then adapts the existing 5G SSC mode 1 protocol to effectively solve the contradiction between low latency and continuity of services during terminal mobility. Compared with the existing SSC mode 3, the user's IP address does not need to change, and the support of upper-layer applications is not required to ensure service continuity; compared with SSC mode 1, the service always accesses the data network from the nearest route, reducing traffic transmission latency and reducing user plane tunnel resource occupancy.

[0115] It should be noted that, in this article, the terms "comprises", "includes" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or apparatus that includes a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or apparatus.

[0116] Finally, it should be noted that the above is only a preferred embodiment of the present invention, which is only used to illustrate the technical solution of the present invention, and is not used to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A method for transmitting business continuity without application layer perception during the movement of 5G terminals, characterized in that: The 5G terminal is represented by UE, the core network element SMF represents the session management network element, AMF represents the access and mobility management network element, UPF represents the user plane function network element, the node in the network that communicates with the 5G terminal is represented by NT, and the base station is represented by gNB; During the session, the UE needs to be allocated two types of IPv6 addresses by the core network, one is a routing identifier, which is used for routing addressing in the network; the other is a session identifier, which is used to identify the communication identity of the node in the network; the method includes the following steps: Step 1: The UE moves to the base station gNB, accesses the core network, establishes a PDU session, and establishes communication with the peer node NT. The implementation process is as follows: Step 1.1, when the initial session is established, according to the UE session identifier allocation mode stored in the core network, if it is configured as dynamic allocation mode, the SMF allocates a dynamic IPv6 address to the UE, otherwise the UE's static address is directly used as the session identifier; Step 1.2: SMF selects the nearest UPF to provide access to the UE, and allocates an IPv6 address to the UE as a routing identifier based on the selected UPF. Step 1.3: Establish a GTP tunnel between base station gNB1 and UPF. Step 1.4, the UE encapsulates the routing identifier in the source address field of the data packet, and encapsulates the session identifier in the destination option extension header of the data packet, and initiates a communication request to the peer node NT; Step 1.5: After receiving the message, the NT swaps the source address and destination option extension headers in the message, thereby providing the UE session identifier to the upper layer application for identifying the UE communication identity; at the same time, the NT establishes a mapping cache of the monogram identifier and the routing identifier; Step 1.6, NT encapsulates the UE's routing identifier in the destination address field of the data packet, encapsulates the session identifier in the routing extension header of the data packet, and then sends the data to the UE; Step 1.7: After receiving the message, the UE swaps the destination address and the routing extension header in the message, thereby providing the UE session identifier to the upper layer application; Step 1.8, both parties establish a TCP connection and start transmitting data; Step 2: The UE moves and switches to a new base station for access. Then the core network receives a message about the UE location change and determines whether the UPF needs to be switched. If not, execute step 3, otherwise execute step 4. Step 3: Under the control of SMF, a bidirectional tunnel is established from the new gNB to the old UPF. During this period, the IPv6 addresses of both parties remain unchanged. Step 4: SMF selects a new UPF nearby, and both parties maintain business continuity. The implementation process is as follows: Step 4.1, SMF notifies the old UPF that the UE location has changed, and the old UPF caches the routing identifier of the current UE for a period of time; Step 4.2, SMF reselects a new UPF and assigns a new routing identifier to the UE; Step 4.3, under the control of SMF, the tunnel between the old UPF and the old base station is dismantled, a GTP tunnel from the new base station to the new UPF is established, and a GTP tunnel from the old UPF to the new UPF to the new base station is temporarily established. If there is no direct interface between the old UPF and the new UPF, an I-UPF needs to be allocated to ensure the use of the tunnel. The tunnel lifetime is set by the system. After the lifetime expires, the SMF organizes the tunnel dismantling; Step 4.4, UE sends a binding registration message to NT to inform the new routing identifier; Step 4.5, after receiving the binding message, the NT updates the mapping relationship between the stored UE routing identifier and the session identifier; Step 4.6: If NT sends data before the binding message reaches NT, execute step 4.7; otherwise, execute step 4.8; Step 4.7, NT uses the old routing identifier as the destination address to send a data packet to the UE; Step 4.8, NT uses the new routing identifier as the destination address to send a data packet to the UE; Step 4.9, the UE encapsulates the new routing identifier in the source address field of the data packet, and encapsulates the session identifier in the destination option extension header of the data packet, and sends the data packet to the peer node NT; Step 4.10: After receiving the message, the NT swaps the source address and destination option extension headers in the message and provides the UE session identifier to the upper layer application. Step 5: If the UE continues to move, execute step 2; Step 6: If the UE session ends, including the core network side initiating a release request and the user side initiating a release request, the core network releases the session resources.

2. The method for transmitting business continuity without application layer sense in 5G terminal movement according to claim 1 is characterized in that: The session identifier has two allocation modes, including fixed allocation of static IPv6 addresses and allocation of dynamic IPv6 addresses during a session; the allocated session identifier should be unique, which is achieved by allocating a unique local address or specifying an IP network segment.

3. A 5G terminal mobile application layer non-sensitive business continuity transmission device, characterized in that: The system is used to implement the application layer-insensitive business continuity transmission method for the 5G terminal in motion as claimed in claim 1 or 2, and comprises: The node communication establishment module is used for the UE to move to the base station gNB, access the core network, establish a PDU session, and establish communication with the peer node NT; The UPF switching judgment module is used for UE movement and switching to a new base station for access. Then the core network receives the message of UE location change and determines whether the UPF needs to be switched; The new gNB to old UPF tunnel establishment module is used to establish a bidirectional tunnel from the new gNB to the old UPF under the control of the SMF. During this period, the IPv6 addresses of both parties remain unchanged; The business continuity maintenance module is used for SMF to select a new UPF nearby so that both parties can maintain business continuity; The session resource release module is used to release the session resources by the core network if the UE session ends, including when the core network side initiates a release request and when the user side initiates a release request.

Citation Information

Patent Citations

  • Method, device and system for implementing continuous session

    CN107592331A