Communication method and communication device

Abstract

Provided are a communication method and a communication device. The communication method comprises: after switching from a source service processing network element of a core network to a target service processing network element, a terminal device receiving mapping information related to a first connection and a second connection, wherein the first connection is a connection between the terminal device and the source service processing network element, and the second connection is a connection between the terminal device and the target service processing network element.

Description

Communication methods and communication equipment Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0002] Some services (such as location services or sensing services) require data transmission via user plane connections. In certain scenarios, the service processing network element that establishes the user plane connection with the terminal device may change. The switching of the service processing network element may lead to inconsistencies in the terminal device's and core network's understanding of the connection status, thereby affecting the smooth operation of the service. Summary of the Invention

[0003] This application provides a communication method and a communication device. The various aspects covered by this application are described below.

[0004] In a first aspect, a communication method is provided, comprising: after a source service processing network element in the core network is switched to a target service processing network element, a terminal device receives mapping information related to a first connection and a second connection; wherein the first connection is a connection between the terminal device and the source service processing network element, and the second connection is a connection between the terminal device and the target service processing network element.

[0005] In a second aspect, a communication method is provided, comprising: after a source service processing network element in the core network is switched to a target service processing network element, the target service processing network element sends mapping information related to a first connection and a second connection to a terminal device; wherein the first connection is a connection between the terminal device and the source service processing network element, and the second connection is a connection between the terminal device and the target service processing network element.

[0006] Thirdly, a communication method is provided, comprising: after a source service processing network element in the core network switches to a target service processing network element, a first core network element receives mapping information related to a first connection and a second connection sent by the target service processing network element; wherein the first connection is a connection between the terminal device and the source service processing network element, and the second connection is a connection between the terminal device and the target service processing network element.

[0007] Fourthly, a communication device is provided, which is a terminal device. The communication device includes: a receiving unit, configured to receive mapping information related to a first connection and a second connection after the source service processing network element of the core network is switched to a target service processing network element; wherein the first connection is the connection between the terminal device and the source service processing network element, and the second connection is the connection between the terminal device and the target service processing network element.

[0008] Fifthly, a communication device is provided, the communication device being a target service processing network element, the communication device comprising: a sending unit, configured to send mapping information related to a first connection and a second connection to a terminal device after the source service processing network element in the core network is switched to the target service processing network element; wherein, the first connection is a connection between the terminal device and the source service processing network element, and the second connection is a connection between the terminal device and the target service processing network element.

[0009] In a sixth aspect, a communication device is provided, the communication device being a first core network element, the communication device comprising: a first receiving unit, configured to receive mapping information related to a first connection and a second connection sent by the target service processing network element after the source service processing network element of the core network is switched to the target service processing network element; wherein the first connection is a connection between a terminal device and the source service processing network element, and the second connection is a connection between the terminal device and the target service processing network element.

[0010] A seventh aspect provides a communication device including a transceiver, a memory, and a processor, the memory for storing a program, the processor for calling the program in the memory, and controlling the transceiver to receive or transmit signals to cause the communication device to perform the method as described in any one of the first to third aspects.

[0011] Eighth aspect, an apparatus is provided, including a processor for calling a program from a memory to cause the apparatus to perform the method as described in any one of the first to third aspects.

[0012] A ninth aspect provides a chip including a processor for calling a program from memory, causing a device having the chip mounted to perform the method as described in any one of the first to third aspects.

[0013] A tenth aspect provides a computer-readable storage medium having a program stored thereon that causes a computer to perform the method described in any one of the first to third aspects.

[0014] Eleventh aspect: A computer program product is provided, including a program that causes a computer to perform the method as described in any one of the first to third aspects.

[0015] In a twelfth aspect, a computer program is provided that causes a computer to perform the method described in any one of the first to third aspects.

[0016] In this embodiment, after the source service processing network element in the core network is switched to the target service processing network element, the terminal device can receive mapping information related to the first connection (such as a user plane connection) and the second connection (such as a user plane connection). The first connection and the second connection are the connections between the terminal device and the source service processing network element and the target service processing network element, respectively. When a service processing network element switch occurs, the network side and the terminal device side can synchronize the connection migration context based on this mapping information, which helps to improve the service quality. Attached Figure Description

[0017] Figure 1 is an example architecture diagram of a communication system applicable to the embodiments of this application.

[0018] Figure 2 is a system architecture example diagram of the communication system applicable to the embodiments of this application.

[0019] Figure 3 is a system architecture example diagram of the sensing system applicable to the embodiments of this application.

[0020] Figure 4 is a system architecture example diagram of the positioning system applicable to the embodiments of this application.

[0021] Figure 5 is a schematic flowchart of a user plane connection establishment method applicable to an embodiment of this application.

[0022] Figure 6 is a schematic flowchart of another user plane connection establishment applicable to the embodiments of this application.

[0023] Figure 7 is a schematic flowchart of the core network element relocation applicable to the embodiments of this application.

[0024] Figure 8 is a schematic flowchart of a communication method provided in one embodiment of this application.

[0025] Figure 9 is a schematic flowchart of a communication method provided in another embodiment of this application.

[0026] Figure 10 is a schematic flowchart of a communication method provided in another embodiment of this application.

[0027] Figure 11 is a schematic flowchart of one possible implementation.

[0028] Figure 12 is a schematic flowchart of another possible implementation.

[0029] Figure 13 is a schematic flowchart of another possible implementation.

[0030] Figure 14 is a schematic flowchart of another possible implementation.

[0031] Figure 15 is a schematic diagram of the structure of a communication device provided in one embodiment of this application.

[0032] Figure 16 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.

[0033] Figure 17 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.

[0034] Figure 18 is a schematic diagram of the structure of a device applicable to the embodiments of this application. Detailed Implementation

[0035] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0036] Communication system

[0037] Figure 1 is an example architecture diagram of a communication system 100 to which embodiments of this application can be applied. The communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 can provide network coverage for a specific geographical area and can communicate with the terminal device 120 located within that coverage area. The terminal device 120 can access a network (such as a wireless network) through the network device 110. Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity (MME), which are not limited in this embodiment.

[0038] Figure 1 exemplarily illustrates a network device and two terminal devices. In some embodiments of this application, the communication system 100 may also include multiple network devices and each network device may include other numbers of terminal devices within its coverage area. This application does not limit this aspect.

[0039] It should be understood that the embodiments of this application can be applied to various communication systems. For example, the embodiments of this application can be applied to Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A), New Radio (NR), evolution systems of NR, LTE-based access to unlicensed spectrum (LTE-U), NR-based access to unlicensed spectrum (NR-U), Universal Mobile Telecommunications System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), and 5th-generation (5G) communication systems. The embodiments of this application can also be applied to other communication systems, such as future communication systems. The future communication system could be, for example, a beyond 5G (B5G) communication system, a sixth-generation mobile communication system, or a satellite communication system.

[0040] Traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, communication systems can now support not only traditional cellular communication but also one or more other types of communication. For example, a communication system can support one or more of the following communication methods: device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, and vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to communication systems that support the above-mentioned communication methods.

[0041] The communication system in this application embodiment can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0042] The communication system in this application embodiment can be applied to unlicensed spectrum. This unlicensed spectrum can also be considered a shared spectrum. Alternatively, the communication system in this application embodiment can also be applied to licensed spectrum. This licensed spectrum can also be considered a dedicated spectrum.

[0043] The embodiments of this application can be applied to terrestrial networks (TN) systems as well as non-terrestrial networks (NTN) systems. As an example, the NTN system can include an NR-based NTN system and an Internet of Things (IoT)-based NTN system.

[0044] A communication system may include one or more terminal devices. The terminal devices mentioned in the embodiments of this application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

[0045] In some embodiments, the terminal device may be a station (ST) in a WLAN. In some embodiments, the terminal device may also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a next-generation communication system (e.g., NR system), or terminal device in a future evolved public land mobile network (PLMN) network, etc.

[0046] In some embodiments, the terminal device may be a device that provides voice and / or data connectivity to the user. For example, the terminal device may be a handheld device, an in-vehicle device, etc., with wireless connectivity. As some specific examples, the terminal device may be a mobile phone, tablet, laptop, PDA, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc.

[0047] In some embodiments, the terminal device may be deployed on land. For example, the terminal device may be deployed indoors or outdoors. In some embodiments, the terminal device may be deployed on water, such as on a ship. In some embodiments, the terminal device may be deployed in the air, such as on an airplane, balloon, or satellite.

[0048] In addition to terminal devices, the communication system may also include one or more network devices. In this embodiment, the network device may be a device for communicating with the terminal device; this network device may also be referred to as an access network device or a radio access network (RAN) device. For example, the network device may be a base station. In this embodiment, the network device may refer to an access network node (or device) that connects the terminal device to the wireless network. Access network equipment can broadly encompass various names listed below, or be interchangeable with them, such as: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point (AP), transmitting and receiving point (TRP), transmitting point (TP), master station (MeNB), secondary station (SeNB), multi-mode radio (MSR) node, home base station, network controller, access node, radio node, transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. Base stations can be macro base stations, micro base stations, relay nodes, donor nodes, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0049] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0050] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an AAU.

[0051] By way of example and not limitation, in the embodiments of this application, the network device may have mobility characteristics; for example, the network device may be a mobile device. In some embodiments of this application, the network device may be satellite-based or space-based, that is, the network device is installed on a satellite or flying equipment. In some embodiments of this application, the network device may also be a base station installed in locations such as land or water.

[0052] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0053] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Taking the communication system 100 shown in FIG1 as an example, the communication devices may include network devices 110 and terminal devices 120 with communication functions. Network devices 110 and terminal devices 120 can be the specific devices described above, which will not be repeated here. The communication devices may also include other devices in the communication system 100, such as network controllers, mobility management entities, and other network entities, which are not limited in this application embodiment.

[0054] Network system architecture

[0055] Figure 2 illustrates an exemplary system architecture diagram of a communication system applicable to embodiments of this application, using a 5G system as an example. As shown in Figure 2, the system architecture of a 5G network may include: a terminal device (also known as a UE) 201, an access network device 202 (including a radio access network (RAN) or an access network (AN)), an access and mobility management function (AMF) network element 203, a session management function (SMF) network element 204, a user plane function (UPF) network element 205, a policy control function (PCF) network element 206, an application function (AF) network element 209, a data network (DN) 208, a network slice selection function (NSSF) 211, an authentication server function (AUSF) 210, and a unified data management (UDM) network element 207.

[0056] Terminal device 201 can be any of the terminal devices shown in Figure 1, which will not be described in detail here.

[0057] Access network equipment 202 is the access device through which terminal devices wirelessly access the network architecture. It is primarily responsible for air interface-side radio resource management, Quality of Service (QoS) management, data compression, and encryption. Examples include NodeBs, eNodeBs, base stations in 5G or NR mobile communication systems, and base stations in future mobile communication systems.

[0058] UPF element 205, AMF element 203, SMF element 204, and PCF element 206 are network functions (NFs) of the 3rd Generation Partnership Project (3GPP) core network, and can be referred to as core network elements. UPF element 205 can be called a user plane function element, mainly responsible for user data transmission. The other elements can be called control plane function elements, mainly responsible for authentication, authorization, registration management, session management, mobility management, and policy control, to ensure reliable and stable transmission of user data.

[0059] The UPF network element 205 (or simply "UPF") can be used to forward and receive data from terminals. For example, the UPF network element can receive service data from the data network and transmit it to the terminal through the access network equipment; the UPF network element can also receive user data from the terminal through the access network equipment and forward it to the data network. The transmission resources allocated and scheduled by the UPF network element for the terminal are managed and controlled by the SMF network element. The bearer between the terminal and the UPF network element can include: the user plane connection between the UPF network element and the access network equipment, and the establishment of a channel between the access network equipment and the terminal. The user plane connection is a Quality of Service (QoS) flow that can be established between the UPF network element and the access network equipment for transmitting data.

[0060] The AMF network element 203 (or "AMF" for short) can be used to manage terminal access to the core network, such as terminal location updates, network registration, access control, terminal mobility management, and terminal attachment and detachment. The AMF network element can also provide control plane storage resources for a terminal's session, storing the session identifier and the associated SMF network element identifier, etc.

[0061] SMF network element 204 (or "SMF" for short) can be used to select user plane network elements for terminals, redirect user plane network elements for terminals, assign Internet Protocol (IP) addresses to terminals, establish bearers (also known as sessions) between terminals and UPF network elements, modify and release sessions, and control QoS.

[0062] PCF network element 206 (or simply "PCF") is used to provide policies, such as QoS policies and slice selection policies, to AMF network element 203 and SMF network element 204. PCF is responsible for formulating policies related to mobility management, session management, and billing of terminal devices.

[0063] AF element 209 (or simply "AF") is used to interact with 3GPP core network elements to support the routing of application-affected data, access network exposure functions, and interact with PCF elements for policy control, etc.

[0064] UDM Network Element 207 (or simply "UDM") includes functions such as generating and storing user subscription data and managing authentication data, and supports interaction with external third-party servers.

[0065] The DN 208 can provide data services to users for networks such as IP Multimedia Service (IMS) and the Internet. The DN 208 can contain various application servers (AS) that provide different application services, such as carrier services, Internet access, or third-party services. The application servers can implement the functions of AF (Active Network Element) network elements.

[0066] NSSF 211 is used for network slice selection and supports the following functions: selecting the set of network slice instances to serve the UE; determining allowed network slice selection assistance information (NSSAI), and, when necessary, determining the mapping to the subscribed single-network slice selection assistance information (S-NSSAI); determining the configured NSSAI, and, when necessary, determining the mapping to the subscribed S-NSSAI; determining the set of AMFs that may be used to query the UE, or determining a list of candidate AMFs based on configuration.

[0067] AUSF 210 is used to receive the AMF 203's request to authenticate the terminal. It requests a key from UDM 207 and then forwards the issued key to AMF 203 for authentication processing.

[0068] As shown in Figure 2, the terminal device connects to the AN (Access Layer) via the Uu interface to exchange access layer messages and wireless data. The terminal device also connects to the AMF (Anti-Access Stratification) network element via the N1 interface to exchange NAS messages. In addition to mobility management of the terminal device, the AMF network element is responsible for forwarding session management-related messages between the terminal device and the SMF network element. The UPF (Universal Power Grid) network element transmits data with the external data network via the N6 interface and with the AN via the N3 interface.

[0069] Current cellular networks, including 5G networks, are used solely for communication. However, the radio electromagnetic signals used by cellular networks can be used for more than just wireless data transmission and communication; they also possess environmental awareness capabilities. These capabilities include user motion or gesture recognition, respiratory monitoring, terminal movement speed measurement, environmental imaging, and weather monitoring. Therefore, future cellular networks could be considered not only for communication and data transmission but also for acquiring sensory information.

[0070] To support sensing capabilities in B5G networks, sensing functions (SFs) and corresponding procedures can be added to the 3GPP network. Communication devices can send and receive sensing information based on sensing tasks. A sensing task requires identifying the corresponding sensing target. When the sensing target is a terminal device, the corresponding terminal device can be found directly through its identity (ID) or IP address information, and this terminal device can be used as the sender or receiver of the sensing signal. This allows for the selection of other surrounding sensing nodes to complete the sensing task.

[0071] For integrated sensing, the main wireless sensing scenarios include the following:

[0072] Scenario 1 is a base station echo sensing link (single gNB sensing), where the base station can send sensing signals and receive echo signals;

[0073] Scenario 2 is an inter-base station sensing link (gNB-gNB sensing), where base station B can receive sensing signals sent by base station A;

[0074] Scenario 3 is an air interface uplink sensing link (UE-gNB uplink sensing), where the base station can receive sensing signals sent by the terminal device;

[0075] Scenario 4 is an air interface downlink sensing link (UE-gNB downlink sensing), where the terminal device can receive sensing signals sent by the base station;

[0076] Scenario 5 is a terminal echo sensing link (single UE sensing), where the terminal device can send sensing signals and receive echo signals;

[0077] Scenario 6 is a terminal-to-terminal sensing link (UE-UE sensing), where terminal device B can receive sensing signals sent by terminal device A.

[0078] In the initial stage of B5G communication and sensing integration, the focus is on reusing existing air interface signals to perform sensing actions, without introducing excessive air interface enhancements. In certain scenarios, considering the complexity of full-duplex implementation, collaborative sensing between terminal devices and / or network devices is the preferred approach. For sensing methods in scenarios 3 to 6, it may be necessary for terminal devices to report a large amount of sensing data to the sensing elements of the core network or obtain auxiliary data from the core network elements.

[0079] Figure 3 is an example diagram of a reference architecture for a sensing system. This reference architecture illustrates a possible process for controlling access network devices or terminal devices to perform terminal device-level sensing operations. The dashed lines in Figure 3 indicate that the network element or function is optional.

[0080] The sensing system reference architecture in Figure 3 includes: terminal device 301 (UE B), terminal device 302 (UE A), access network device 303, AMF network element 304, UDM network element 305, UPF network element 306, control plane (SF-C) of sensing network element 307, user plane (SF-U) of sensing network element 308, network data analytics function (NWDAF) network element 309, location management function (LMF) network element 310, PCF network element 311, network exposure function (NEF) network element 312, and AF network element 313.

[0081] The SF-C 307 (or simply "SF-C"), also known as the sensing control network element, can interact with the core network's control plane network elements, is responsible for control plane message transmission, and provides the address of the sensing user plane function to access network devices or terminal devices. As shown in Figure 3, the SF-C 307 can connect to AMF 304, UDM 305, NWDAF 309, LMF 310, PCF311, and NEF 312 through different sensing interfaces.

[0082] The SF-U network element 308 (or simply "SF-U") is responsible for collecting and analyzing sensing measurement data or related information generated by terminal devices or access network devices to obtain the final sensing results, and then making them available to terminal devices or applications. As shown in Figure 3, the sensing measurement data can be forwarded via UPF 306 or directly transmitted to the sensing user plane function.

[0083] NWDAF element 309 (or simply "NWDAF") can collect data from various core network elements, applications, operation and maintenance systems, and operation support systems, and then analyze this data to provide suggestions and solutions regarding network performance and health status.

[0084] The LMF network element 310 (or "LMF" for short) can interact with the core network to support the positioning function of terminal equipment.

[0085] The NEF element 312 (or simply "NEF") can be used to open up the capabilities of various NFs and transform internal and external information.

[0086] As shown in Figure 3, when an application sends a sensing request for a target terminal device to the 3GPP core network, the core network can select the correct access network device or auxiliary terminal device through the SF-C network element or AMF, triggering the ability to perform sensing-related radio measurements, initiating the measurement of sensing information, and generating sensing results. Considering the large amount of data exchanged between the terminal device and the sensing network element, the terminal device can complete the necessary interaction for sensing services with the sensing network element through user plane data transmission. The terminal device can send sensing data to the SF-U network element through the UPF network element by establishing a special protocol data unit (PDU) session.

[0087] Figure 4 is an example diagram of a reference architecture for a positioning system. The positioning system reference architecture in Figure 4 includes: terminal device 401, access network device 402, positioning reference unit (PRU) 403, AMF network element 404, LMF network element 405, NEF network element 406, UDM network element 407, location retrieval function (LRF) 408, gateway mobile location center (GMLC) 409, NWDAF network element 410, AF network element 411, and location services (LCS) client 412.

[0088] As shown in Figure 4, multiple core network elements or nodes participating in the positioning of terminal device 401 can be connected through relevant interfaces. PRU 403, LRF 408, GMLC 409, and LCS client 412 can all participate in the positioning / location management of terminal device 401.

[0089] It should be noted that the network elements in Figures 2 to 4 can be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform). The network architectures shown in Figures 2 to 4 do not constitute a limitation on the corresponding network architectures. In specific implementations, the corresponding network architectures may include more or fewer network elements than shown in the figures, or combine certain network elements, etc. In addition, AN or RAN is represented by (R)AN in Figures 2 to 4. The user plane portion of the sensing network element in Figure 3 may also have other names, or may be shared with LMF, which is not limited here.

[0090] Referring to the positioning system architecture shown in Figure 4, it can be seen that positioning services also involve user plane (UP) transmission requirements. In some cases of positioning services, user plane data transmission is required between the terminal device and the core network. The configuration and data transmission process of the user plane in positioning services are illustrated below with reference to Figures 5 to 7.

[0091] Figure 5 is a schematic diagram of a process for LMF to trigger the establishment of a user plane connection.

[0092] Referring to Figure 5, in step S501, the LMF can determine whether to utilize the user plane for positioning. As an example, the LMF can decide whether to use the user plane connection between the terminal device and the LMF for positioning based on the user plane positioning capability of the terminal device, the control plane congestion status (such as the AMF load status), and other implementation factors.

[0093] Optionally, the LMF can invoke the Nnrf_NFDiscovery service operation to retrieve control plane congestion status (such as AMF load information). Alternatively, the LMF can invoke the Nnrf_NFManagement_NFStatusSubscribe service to subscribe to specific AMF load information.

[0094] Optionally, if the AMF load information indicates control plane congestion and an available user plane connection exists between the terminal device and the LMF, the LMF may decide to use user plane positioning.

[0095] Optionally, if the user plane connection context of the target terminal device already exists in the LMF, and the LMF decides to use the user plane connection for positioning, then subsequent steps S502-S508 can be skipped.

[0096] Optionally, LMF can select user plane localization for specific localization methods (such as motion sensor-based methods). Which specific localization methods require user plane transmission depends on the implementation and local configuration.

[0097] Optionally, this procedure can also be triggered when the LMF receives a location request from the AMF via control plane signaling (as defined in Clauses 6.1 and 6.3 of specification TS23.273).

[0098] In step S502, the LMF sends user plane information. This user plane information may include the LMF's user plane location address. If the LMF decides to use the user plane for location, and no secure user plane connection has been established between the terminal device and the LMF, the LMF invokes the Namf_Communication_N1N2MessageTransfer (or Namf_Communication_N1N2Transfer) service operation to send the user plane information to the AMF in the NAS container, instructing the terminal device to use a user plane based on transport layer security (TLS) for location.

[0099] Optionally, the LMF can assign an LCS-UP binding ID to associate the user plane connection to be established with the target terminal device, and include this LCS-UP binding ID in the user plane information. The LMF can associate the identifier of the target terminal device with this LCS-UP binding ID. The identifier of the terminal device may include a subscription permanent identifier (SUPI) and / or a generic public subscription identifier (GPSI).

[0100] Optionally, if the terminal device supports user plane positioning and the AMF does not subscribe to the state of the LCS user plane connection, the AMF can subscribe to the state of the LCS user plane connection from the LMF.

[0101] In step S503, the AMF forwards the user plane information. When the AMF receives the user plane information from the LMF in step S502, the AMF can send the user plane information to the terminal device via a DL NAS TRANSPORT message.

[0102] In step S504, the terminal device establishes a user plane connection. If no established PDU session suitable for user plane positioning exists, the terminal device can use the User Routing Selection Policy (URSP) defined in TS23.503

[0041] to establish a PDU session for user plane positioning. The URSP may include PDU session parameters related to user plane positioning. PDU session parameters may include, for example, the Distributed Network Name (DNN) and S-NSSAI.

[0103] Optionally, the terminal device can establish a secure user plane connection with the LMF. If the LMF sends its fully qualified domain name (FQDN) to the terminal device, a Domain Name System (DNS) server / resolver is used to resolve the LMF's IP address. The DNS server could be, for example, an edge application server discovery function (EASDF) or a local DNS used for local LMF address resolution.

[0104] Optionally, after successfully establishing a secure user plane connection, the terminal device can send the LCS-UP binding ID received in step S503 to the LMF through the secure user plane connection, so that the LMF can perform the association between the terminal device and the secure user plane connection. Once the association between the terminal device and the user plane connection is completed, the LCS-UP binding ID will be released.

[0105] In step S505, the terminal device sends a user plane positioning acknowledgement. The terminal device can send an acknowledgement to the LMF via the AMF to indicate that the user plane connection was successfully established, or to indicate that the user plane connection defined in TS24.572

[0048] cannot be used. Optionally, the terminal device can send the acknowledgement via UL NAS TRANSPORT.

[0106] In step S506, the AMF forwards the acknowledgment. The AMF can send the acknowledgment received in step S505 to the LMF via the Namf_N1messageNotify service.

[0107] In step S507, the LMF notifies the AMF. The LMF can indicate to the AMF in the Nlmf_Location_UPNotify message that a user plane connection between the terminal device and the LMF has been established.

[0108] In step S508, the AMF stores the LCS-UP connection context. Optionally, the AMF may store the LCS-UP connection context as part of the UE context.

[0109] In step S509, the terminal device transmits UE positioning and supplementary service messages via the user plane, such as the LTE positioning protocol (LPP) and supplementary service message transmission. If the LMF or the terminal device decides to use a user plane connection for positioning and a secure user plane connection has been established, LPP messages are transmitted between the terminal device and the LMF for interaction based on the terminal device's positioning, terminal device-assisted positioning, and supplementary data.

[0110] Optionally, supplementary service messages may include event reporting messages, periodically triggered call messages, and MS cancel delay location messages. Supplementary service messages can also be transmitted between the LMF and the terminal device via an established user plane connection.

[0111] Figure 6 is a schematic diagram of a process for a terminal device to trigger the establishment of a user plane connection.

[0112] Referring to Figure 6, in step S601, the terminal device sends a user plane connection establishment request. If a secure user plane connection has not been established between the terminal device and the LMF, and the terminal device decides to request a user plane connection for the upcoming positioning request, the terminal device can send a user plane connection establishment request to the AMF via a NAS message. Optionally, the terminal device can send user plane positioning initiation information via UL NAS TRANSPORT.

[0113] In step S602, the AMF performs LMF selection. If the terminal device is authorized to use user plane positioning based on its subscription, the AMF selects an LMF capable of establishing a user plane session with the terminal device for positioning. The AMF can discover and select a suitable LMF by querying the network repository function (NRF) or based on local configuration.

[0114] In step S603, the AMF sends an Nlmf_Location_UPConfig request to the LMF to request the establishment of an LCS-UP connection. The AMF should include the target terminal device identifier (see TS29.572

[0012] ) (SUPI and / or GPSI) in the request.

[0115] In step S604, the LMF sends user plane information to the AMF. For example, it calls Namf_Communication_N1N2MessageTransfer to send user plane information. Optionally, if the LMF accepts the use of the user plane for positioning, and no secure user plane connection is established between the terminal device and the LMF, the LMF sends user plane information to the AMF, instructing the terminal device to accept and use the user plane for positioning. The user plane information may include the LMF's user plane positioning address. The LMF may assign an LCS-UP binding ID to associate the user plane connection to be established with the target terminal device and include the LCS-UP binding ID in the user plane information. The LMF may associate the target terminal device identifier (SUPI and / or GPSI) with the LCS-UP binding ID.

[0116] In step S605, when the AMF receives the user plane information sent by the LMF in step S604, the AMF forwards it to the terminal device via a DL NAS TRANSPORT message.

[0117] In step S606, the terminal device establishes a user plane connection. If a secure user plane connection has not yet been established, the terminal device establishes a secure user plane connection with the LMF. The terminal device can use the LMF's user plane location address and information in the URSP to determine the PDU session parameters, including DNN+S-NSSAI. The terminal device can use the PDU session parameters to establish a PDU session. When the SMF receives a request, it selects a suitable UPF based on DNN+S-NSSAI and establishes a connection between the UPF and the LMF. After successfully establishing a secure user plane connection, the terminal device sends the LCS-UP binding ID received in step S604 to the LMF through the secure user plane connection, enabling the LMF to perform the association between the terminal device and this secure user plane connection. Once the association is complete, the LCS-UP binding ID will be released.

[0118] In step S607, the terminal device sends an acknowledgment to the LMF via the AMF, indicating that the user plane connection was successfully established, or indicating that the user plane connection defined in TS24.572

[0048] cannot be used.

[0119] In step S608, the AMF sends the acknowledgment received in step S607 to the LMF via the Namf_N1messageNotify service.

[0120] In step S609, the LMF responds to the AMF, indicating that a user plane connection has been established between the terminal device and the LMF.

[0121] In step S610, the AMF stores the LCS-UP connection context as part of the UE context.

[0122] In step S611, after establishing a secure user plane connection, if the LMF decides to use the user plane connection for positioning after receiving the positioning request from the AMF, or if the terminal device decides to use the user plane connection for positioning, then an LPP message is transmitted between the terminal device and the LMF for positioning based on the terminal device, terminal device-assisted positioning, and delivery of auxiliary data.

[0123] Figure 7 illustrates a schematic flowchart of core network element relocation using an LMF as an example. As shown in Figure 7, the LMF connected to the terminal device is changed from the source LMF to the target LMF.

[0124] Referring to Figure 7, in step S701, the source LMF sends information to the AMF indicating connection movement or termination. In some scenarios, the source LMF may discover the need to change the LMF, re-establish the user plane connection between the terminal device and the LMF, or terminate the user plane connection. These scenarios include, for example, receiving an event report from the terminal device via the user plane, or receiving AMF relocation information from the target AMF. For AMF relocation, the target AMF can obtain the terminal device's LCS-UP context from the source AMF, which indicates that the terminal device has maintained an LCS-UP connection with the source LMF; the target AMF can use the Nlmf_Locatoion_UPConfig request to notify the source LMF of the AMF changes.

[0125] As shown in step S701, the source LMF can send an Nlmf_Location_UPNotify message. This message includes a request for connection move (termination and establishment) or a request for termination. If a connection move is requested, the message may include the target LMF identifier. The AMF's address is provided to the LMF as the "notification target address" in the latest Nlmf_Location_UPConfig message or Nlmf_Location_UP Subscribe message. If the LMF is about to terminate the user plane connection, steps S701, 704, S707, and S708 are executed, and other steps are skipped. If the request is to terminate the user plane connection, the AMF releases the LCS-UP context.

[0126] Optionally, the LMF modification process is independent of the session and service continuity (SSC) mode of the PDU session used for location by the dedicated DNN. For SSC modes 2 / 3, the PDU session anchor (PSA) UPF connection to the LMF can be relocated as the end device moves, and the LMF can detect the need to modify the LMF to reduce user plane path latency.

[0127] In step S702, the AMF triggers LMF reselection. The AMF can perform LMF reselection when it receives a target LMF identifier for user plane positioning from the source LMF, or if the terminal device moves to a new location (potentially outside the service area of ​​the source LMF but within the service area of ​​the target LMF). For example, the AMF can select a target LMF for the current terminal device location based on the LMF service area, LMF user plane positioning capability information, and other information listed in the relevant clauses. The LMF needs to be able to establish a user plane session with the terminal device for positioning. After AMF relocation, the target AMF can trigger LMF reselection and LCS-UP connection modification procedures, for example, if the source LMF does not perform LMF reselection.

[0128] In step S703, the connection is moved to the target LMF. This step can be referred to as steps S603 to S610 in Figure 6, and is performed between the AMF (or target AMF), the terminal device, and the target LMF. A process can also be added to terminate the connection between the terminal device and the source LMF.

[0129] In step S704, the AMF sends an Nlmf_Location_UPConfig request to the source LMF. This message may include a request for the source LMF to terminate a specific user plane connection with the terminal device and the target LMF identifier. Alternatively, it may include information about AMF relocation. AMF relocation does not always lead to LMF reselection; AMF relocation information can be provided to the LMF.

[0130] In steps S705 and S706, if a user-plane-based periodic and triggered terminal device location event reporting context exists, the source LMF can call Nlmf_Location_LocationContextTransfer to request a service operation from the target LMF to provide the current location context of the terminal device. The target LMF then notifies the source LMF of the result of the location context transfer operation.

[0131] In step S707, if the user plane connection with the source LMF is still active, the source LMF terminates the connection with the terminal device.

[0132] In step S708, the LMF sends an Nlmf_Location_UPConfig response message to the AMF to acknowledge the connection termination or to confirm AMF changes. If this procedure is used for termination, the AMF will release the LCS-UP context upon receiving the response message.

[0133] As shown in Figure 7, the implementation of location services based on LCS-UP requires the establishment of an LCS session and an LCS-UP connection. The LCS-UP connection can be used to carry the LPP protocol.

[0134] The preceding text, with reference to Figures 2 to 7, illustrates the integrated sensing architecture and user plane positioning architecture applicable to embodiments of this application. For the integrated sensing architecture, due to the large amount of data that needs to be transmitted during sensing, most sensing services require data transmission through user plane connections. Therefore, managing user plane connections is a pressing issue. Related 5G positioning architectures already support the establishment and management of user plane connections, providing a solution reference for the sensing architecture. Thus, it is evident that user plane data transmission will be a necessary component for both related positioning services and future sensing services.

[0135] In certain scenarios, due to the movement of terminal devices or adjustments to network-side services, AMF or LMF handover may be necessary. During AMF or LMF handover, it is crucial to maintain the consistency of the correspondence between LCS sessions and LCS-UP connections (i.e., the binding relationship between the old session identifier, the new connection identifier, and the new session identifier (optional)) across all relevant network elements and terminal devices to ensure the smooth operation of deferred location services. LCS-UP can also be understood as the LCS user plane protocol (LCS-UPP).

[0136] However, during AMF migration or LMF handover, there is a risk of state inconsistency. This inconsistency may cause terminal devices to send incorrect event reports or LCS-UPP messages, resulting in network latency or decreased positioning accuracy.

[0137] For example, during handover, the AMF may store the LCS-UP context of the source LMF. When the target LMF takes over (LMF handover occurs), the relevant mechanism allows LCS-UP context synchronization between LMFs and between AMFs. However, currently there is no mechanism for synchronizing LCS-UP context (the mapping relationship between LCS sessions and LCS-UP connections) on the terminal device side, which may lead to desynchronization between the LCS-UPP layer and the LCS layer of the terminal device.

[0138] For example, when an LMF handover occurs, the old LCS-UP connection is released, and the target LMF may establish a new LCS-UP connection, even if one or more LCS-UP connections already exist between the terminal device and the target LMF. If there are multiple LCS-UP connections between the terminal device and the target LMF, the terminal device needs to select one of these connections for the old session. The terminal device may choose the wrong connection from among these multiple LCS-UP connections, causing a conflict in the understanding of the mapping relationship between the LCS session and the LCS-UP connection between the terminal device and the target LMF, thus affecting the smooth operation of services.

[0139] In summary, in services involving user plane connections, the switching of network elements during service processing may lead to inconsistencies in the understanding of connection status between terminal equipment and the core network, thereby affecting the smooth operation of services. Therefore, ensuring consistent understanding among communication devices is a problem that needs to be solved.

[0140] It should be noted that the issue of inconsistent understanding of connection status between terminal devices and the core network during AMF or LMF handover mentioned above is only an example. The embodiments of this application can be applied to any type of scenario where the understanding between terminal devices and the core network is inconsistent.

[0141] To address the aforementioned issues, embodiments of this application will be described below.

[0142] First, the embodiments of this application involve concepts such as first connection, second connection, and third connection. To facilitate understanding, the meanings of these concepts will be explained with examples.

[0143] The first connection and / or second connection mentioned in the various embodiments of this application can be a connection established between the terminal device and the core network for transmitting service data of the terminal device. This first connection and / or second connection can be a user plane connection, or other connections with similar functions introduced in future communication systems.

[0144] The third connection mentioned in the various embodiments of this application can be a connection established between the terminal device and the core network for transmitting control signaling of the terminal device. The first connection and the second connection can be the same type of connection, while the third connection and the first connection (or the second connection) can be two different types of connections. The third connection can be a control plane connection, or it can be other connections with similar functions introduced in future communication systems.

[0145] Based on the above concepts, this application proposes a communication method. In this method, the connection between the terminal device and the source service processing network element is a first connection, and the connection between the terminal device and the target service processing network element is a second connection. After the source service processing network element switches to the target service processing network element, the terminal device can receive mapping information related to the first and second connections. This mapping information can be used for context synchronization of connection migration between the network side and the terminal device side, thereby ensuring the normal progress of connection migration and improving the quality of service.

[0146] In some implementations, the communication method proposed in this application embodiment can be applied to 5G systems, 6G systems, or other communication systems.

[0147] In some implementations, the communication method proposed in this application can be applied to positioning services, sensing services, or extended to other services that are specifically for data collection or data management, without limitation.

[0148] The embodiments of this application will be described in detail below with reference to FIG8. The method shown in FIG8 is executed by a terminal device, and the method includes step S810. The terminal device can interact with the target service processing network element in FIG9 and / or the first core network element in FIG10.

[0149] The terminal device can be any of the communication terminals described above, such as a UE. In some implementations, the terminal device may have the ability to establish a connection with core network elements, or support establishing a connection with core network elements. In some implementations, the terminal device can be a UE in a positioning service architecture or a sensor-integrated architecture.

[0150] Terminal devices can establish connections with service processing network elements in the core network and transmit data through these connections. A service processing network element is any network element in the core network that can establish a connection with a terminal device. When a service processing network element handover occurs, the target service processing network element can be the network element that establishes a connection with the terminal device after the handover. Conversely, the network element that established a connection with the terminal device before the handover is the source service processing network element. Therefore, both the target and source service processing network elements are service processing network elements.

[0151] In some implementations, the service processing network element is related to the service or service type that the terminal device needs to process. For example, the service processing network element is a network element for collecting / processing sensing / location data. Another example is a dedicated data management / collection network element.

[0152] As one implementation approach, the service processing network element can be a location management network element in the core network, i.e., a location core network element. For example, the service processing network element can be an LMF (Local Management Function) or a network element with similar functionality. The source service processing network element is the source LMF, and the target service processing network element is the target LMF.

[0153] As one implementation approach, the service processing network element can be a sensing network element within the core network, i.e., a sensing core network element. For example, the service processing network element can be a sensing function network element or a network element with similar functionality. The sensing function network element can be represented by SF (Sensing Function), or by other names. The source service processing network element is called the source SF, and the target service processing network element is called the target SF.

[0154] As one implementation approach, the service processing network element can be a network element in the core network used for data processing. For example, the service processing network element can be a data collection network element, a data management network element, or other data processing network elements.

[0155] In some implementations, the service processing network element may separate the control plane and the user plane, such as SF-C and SF-U in Figure 3. The service processing network element can interact with other network elements or terminal devices in the core network through the control plane, or it can interact with terminal devices through the user plane.

[0156] As one implementation, the control plane and user plane of a service processing network element are divided into two parts. For example, when the service processing network element is NF2, the control plane can be represented as NF2-C, and the user plane can be represented as NF2-U. The service processing network element can interact with the terminal device through control plane signaling via NF2-C, and interact with the terminal device through user plane via NF2-U.

[0157] The first core network element can be a control plane signaling forwarding element. Therefore, the first core network element can be called the core network control element. In some implementations, the first core network element can be a core network element used for access and mobility management. The first core network element can be determined according to the communication system. For example, for a 5G system, the first core network element can be an AMF (Advanced Feature Module) or an element with similar functions. Furthermore, for a future 6G system, the first core network element can be represented by 6G MM (6G MM) or other names.

[0158] As an implementation approach, for positioning services in 5G systems, the service processing network element is LMF, and the first core network element is AMF.

[0159] As an implementation approach, for sensing services in a 5G system, the service processing network element is SF, and the first core network element is AMF.

[0160] As an implementation approach, for positioning services in a 6G system, the service processing network element is LMF, and the first core network element is 6G MM.

[0161] As an implementation approach, for sensing services in a 6G system, the service processing network element is SF, and the first core network element is 6G MM.

[0162] As one implementation approach, for data management services in 6G systems, the service processing network element is the data collection network element / data management network element, and the first core network element can be a 6G MM.

[0163] Referring to Figure 8, in step S810, after the source service processing network element of the core network is switched to the target service processing network element, the terminal device receives the mapping information related to the first connection and the second connection.

[0164] The connection established between the terminal device and the service processing network element (such as a user plane connection) can be used for data transmission. In some implementations, this connection can be used to transmit location service data or sensing service data. In other implementations, this connection can be used to transmit data that needs to be collected or managed.

[0165] In some implementations, connection-related information (such as user plane connections) may include connection information used to identify the connection. As an example, connection information may include a connection identifier assigned by the terminal device or service processing network element. As another example, connection information may include user plane address information of the service processing network element (e.g., FQDN, IP address, etc.).

[0166] In some implementations, a connection can be used for sessions between terminal devices and service processing network elements. Connection-related information can include session information associated with the connection. Session information can be used to identify specific sessions or services. As an example, session information may include a session ID, correlation ID, or task ID assigned by the terminal device or service processing network element. The session ID can also be called a service session ID. As an example, session information may also include identification information used by a specific user plane protocol stack for transmission. User plane protocol stacks may include, for example, LPP / Quick UDP Internet Connections (QUIC) / TLS / Secure User Plane Location (SUPL) protocol stacks.

[0167] In scenarios where service processing network elements switch over, the service processing network element through which the terminal device transmits data before the switch is the source service processing network element, and the service processing network element through which it transmits data after the switch is the target service processing network element. In the core network, the service processing network element connected to the terminal device may switch over, leading to connection relocation. As mentioned earlier, when the terminal device moves to a new location, the service processing network element may need to be changed. Alternatively, when the control network element connected to the service processing network element is relocated, changes to the service processing network element may also be involved. When a service processing network element switches over, the connection established between the terminal device and the source service processing network element needs to be migrated to the connection established between the terminal device and the target service processing network element.

[0168] The first connection is the connection between the terminal device and the source service processing network element. Before the source service processing network element switches to the target service processing network element, the connection established between the terminal device and the source service processing network element is the first connection. The terminal device and the source service processing network element can transmit data through the first connection.

[0169] In some implementations, the first connection can be one or more connections between the terminal device and the source service processing network element. For example, when the terminal device establishes a connection with the source service processing network element, the first connection is that connection. Alternatively, when the terminal device establishes multiple connections with the source service processing network element, the first connection can be one of those multiple connections, or it can be at least two or all of those multiple connections.

[0170] The second connection is the connection between the terminal device and the target service processing network element. After the source service processing network element is switched to the target service processing network element, the connection established between the terminal device and the target service processing network element is the second connection. The terminal device and the target service processing network element can transmit data through the second connection.

[0171] In some implementations, the second connection can be one or more connections between the terminal device and the target service processing network element. For example, when the terminal device establishes a connection with the target service processing network element, the second connection is that connection. Alternatively, when the terminal device establishes multiple connections with the target service processing network element, the second connection can be one of those multiple connections, or at least two or all of those connections.

[0172] The mapping information related to the first and second connections can be understood as the mapping relationship between the first and second connections, or as the mapping relationship between relevant information of the first connection and relevant information of the second connection. As an example, this mapping information may include the binding relationship between the old session identifier, the new connection identifier, and / or the new session identifier. Receiving this mapping information by the terminal device facilitates the synchronization of this mapping information between service-related core network elements and the terminal device.

[0173] In some implementations, the information related to the first connection can be referred to as "first information," and the information related to the second connection can be referred to as "second information." As one implementation, the mapping information related to the first and second connections can be used to indicate the mapping relationship between the first and second information.

[0174] In some implementations, the first information may include connection information of the first connection and / or session information associated with the first connection. The connection information of the first connection may include a connection identifier assigned by the terminal device or the source service processing network element, and may also include user plane address information of the source service processing network element. This connection information can be used to identify the first connection. The session information associated with the first connection may include a session identifier / association identifier / task identifier assigned by the terminal device or the source service processing network element, and may also include identification information used by the user plane protocol stack during transmission. This session information can be used to identify the session or service associated with the first connection.

[0175] As one implementation approach, after the source service processing network element switches to the target service processing network element, the connection information of the first connection can be understood as the old connection information. The connection identifier of the first connection is the old connection identifier.

[0176] As one implementation, the session information associated with the first connection may include session information of one or more sessions on the first connection. These one or more sessions may include the first session. The session information associated with the first connection includes the session information of the first session associated with the first connection. After the source service processing network element is switched to the target service processing network element, the first session associated with the first connection can also be understood as the old session. The session information associated with the first connection is old session information.

[0177] In the above implementation, one or more sessions on the first connection refer to all sessions associated with the first connection. The data associated with all sessions on the first connection is the data associated with the first connection itself.

[0178] In some implementations, the second information may include connection information of the second connection and / or session information associated with the second connection. The connection information of the second connection may include a connection identifier assigned by the terminal device or the target service processing network element, and may also include user plane address information of the target service processing network element. This connection information can be used to identify the second connection. The session information associated with the second connection may include a session identifier / association identifier / task identifier assigned by the terminal device or the target service processing network element, and may also include identification information used by the user plane protocol stack during transmission. This session information can be used to identify the session or service associated with the second connection.

[0179] As one implementation, after the source service processing network element switches to the target service processing network element, the connection information of the second connection can be understood as the new connection information. The connection identifier of the second connection is the new connection identifier.

[0180] As one implementation, the session information associated with the second connection may include session information of one or more sessions on the second connection. These one or more sessions may include the second session. The session information associated with the second connection includes the session information of the second session associated with the second connection. When the source service processing network element is switched to the target service processing network element, the second session associated with the second connection can also be understood as a new session. The session information associated with the second connection is new session information.

[0181] In the above implementation, one or more sessions on the second connection refer to all sessions associated with the second connection. The data associated with all sessions on the second connection is the data associated with the second connection itself.

[0182] In some implementations, the mapping relationship between the first information and the second information may include connection information and / or session information of different connections. This mapping relationship may include at least one of the following: the first information is session information of a first session associated with a first connection, and the second information is connection information of a second connection; the first information is session information of a first session associated with a first connection, and the second information includes connection information of the second connection and session information of a second session associated with the second connection; the first information is connection information of the first connection, and the second information is connection information of the second connection; the first information is session information of a first session associated with a first connection, and the second information is session information of a second session associated with the second connection.

[0183] As one implementation, the mapping relationship between the first information and the second information can include: the first information being session information of a first session associated with a first connection, and the second information being connection information of a second connection. Thus, this mapping relationship binds the old session information to the new connection information. The mapping relationship between the session information of the first session and the connection information of the second connection indicates that the terminal device will subsequently send data over the new connection. For example, the terminal device transmits data associated with the first session over the second connection.

[0184] In the above implementation, after a service processing network element switch occurs, the session identifier may be reused and remain unchanged.

[0185] As one implementation, the mapping relationship between the first information and the second information can include: the first information being the session information of the first session associated with the first connection, and the second information including the connection information of the second connection and the session information of the second session associated with the second connection. This mapping relationship binds the old session information with the new connection information and the new session information. The mapping relationship between the session information of the first session, the connection of the second connection, and the session information of the second session can instruct the terminal device to subsequently send the old session on the new connection using the corresponding new session. For example, the terminal device transmits data associated with the first session on the second connection based on the second session. Transmission based on the second session can be understood as transmission based on the session identifier of the second session.

[0186] In the above implementation, after a service processing network element handover occurs, when data is sent on the second connection, the session identifier of the second session will replace the session identifier of the first session. The second session corresponds to the first session.

[0187] As one implementation, the mapping relationship between the first and second information can include: the first information being the connection information of the first connection, and the second information being the connection information of the second connection. This mapping relationship binds the old connection information to the new connection information. This mapping relationship can instruct the terminal device to send all sessions on the old connection over the new connection. For example, the terminal device transmits data associated with the first connection over the second connection.

[0188] As one implementation, the mapping relationship between the first information and the second information can include: the first information being session information of a first session associated with a first connection, and the second information being session information of a second session associated with a second connection. This mapping relationship binds the old session information to the new session information. This mapping relationship can also instruct the terminal device to use a new session identifier instead of the old session identifier for transmission. For example, the terminal device transmits data associated with the first session based on the second session over the second connection.

[0189] In the above implementation, the data associated with the first session can be understood as the data packet corresponding to the session information of the first session. After a service processing network element switch occurs, the data associated with the first session is transmitted on the second connection based on the session identifier of the second session. The data transmitted on the second connection may include all session-associated data in the first session.

[0190] As one implementation, the mapping relationship between the first information and the second information may include at least two of the mapping relationships described above. As an example, the mapping relationship between the first information and the second information may include a mapping between session information of the first session and connection information of the second connection, and a mapping between session information of the first session and session information of the second session. As another example, the mapping relationship between the first information and the second information may include an association between connection information of the first connection and connection information of the second connection, and a mapping between session information of the first session and session information of the second session.

[0191] In the above implementation, when the mapping information related to the first connection and the second connection includes multiple mapping relationships, these multiple mapping relationships can be bound sequentially or simultaneously. For example, for the mapping information related to the first connection and the second connection, the old session identifier can be bound to the new connection identifier first, then the old session identifier can be bound to the new session identifier, or the binding can be performed simultaneously. Similarly, for the mapping information related to the first connection and the second connection, the old connection identifier can be bound to the new connection identifier first, then the binding can be performed between the old session identifier and the new session identifier, or the binding can be performed simultaneously.

[0192] In some implementations, when signaling interaction between a terminal device and a location core network element (e.g., LMF) or a sensing core network element (e.g., SF) is achieved via a connection (e.g., a user plane connection), migration of the location core network element or sensing core network element may occur. Furthermore, if multiple connections exist between the terminal device and the target location core network element or sensing core network element, the terminal device can select the correct connection based on the binding relationship between the old session identifier, the new connection identifier, and / or the new service session identifier.

[0193] In some implementations, the mapping information related to the first and second connections is used for connection migration during service processing network element handover. This mapping information may also include some or all of the context information (context relocate) for connection migration. This context information may include session information associated with the first connection and / or connection information of the first connection.

[0194] As one implementation approach, the target service processing network element can obtain this context information. For example, the target service processing network element can obtain this context information through interaction with the source service processing network element.

[0195] As one implementation, the target service processing network element can send some or all of the context information to the first core network element. For example, after obtaining the migration context information, the target service processing network element can send a first message to the first core network element. The first message contains session information associated with the first connection. The first core network element can then send a second message related to the mapping information to the terminal device. The second message can be the same as or different from the first message.

[0196] As one implementation approach, the first core network element can directly forward information sent by the target service processing network element to the terminal device, or it can perform further mapping before sending it to the terminal device. For example, if the information sent by the target service processing network element includes session information of the first session, the first core network element can map the session information of the first session to the session information of the second session. Similarly, if the information sent by the target service processing network element includes connection information of the first connection, the first core network element can map the connection information of the first connection to the connection information of the second connection.

[0197] In the above implementation, the mapping performed by the first core network element may be for security or other specific considerations, and may also include some specific information of the target service processing network element. This specific information can have a one-to-one correspondence with the information sent by the target service processing network element.

[0198] Terminal devices can receive mapping information related to the first and second connections in various ways. The mapping information received by the terminal device can come from the target service processing network element or from the first core network element.

[0199] In some implementations, the mapping information related to the first and second connections can be transmitted via a third connection between the terminal device and the core network. That is, the terminal device can receive the mapping information related to the first and second connections based on control plane signaling. For example, the target service processing network element can send the mapping information related to the first and second connections to the terminal device via the third connection. This mapping information can then be forwarded by the first core network element.

[0200] As one implementation, the target service processing network element can directly send the mapping information to the first core network element. For example, the target service processing network element sends mapping information related to the first connection and the second connection to the first core network element. Alternatively, the target service processing network element can determine the mapping relationship between the first and second information based on the migration context information and send that mapping relationship.

[0201] As another implementation, the target service processing network element can send relevant information about the mapping information to the first core network element. The first core network element can determine the mapping relationship between the first and second information based on this relevant information and forward the mapping information. The relevant information about the mapping information can be part of the mapping information, or it can be part or all of the information that determines the mapping information. The first core network element can further perform mapping based on the relevant information sent by the target service processing network element to determine the mapping relationship.

[0202] After the terminal device obtains the mapping information related to the first and second connections through the third connection, the terminal device can transmit user plane data according to the received connection information and / or session information.

[0203] As one implementation, when the mapping information received by the terminal device is the connection information of the second connection and the session information associated with the first connection, the terminal device will subsequently send the data packet corresponding to the session information associated with the first connection on the second connection.

[0204] As one implementation, when the terminal device receives mapping information that includes connection information of the second connection, session information associated with the first connection, and the corresponding session information associated with the second connection, the terminal device sends data on the second connection. The terminal device can map the session information associated with the first connection to the session information associated with the second connection for transmission. For example, the terminal device can map the session identifier or association identifier of the first session to the session identifier or association identifier of the second session.

[0205] As one implementation, when the mapping information received by the terminal device is the connection information of the second connection and the connection information of the first connection, the terminal device will send all the data corresponding to the first connection on the second connection.

[0206] As one implementation, when the terminal device receives mapping information that is session information associated with the second connection and session information associated with the first connection, the terminal device maps the session information associated with the first connection to the session information associated with the second connection and sends it.

[0207] In some implementations, the mapping information related to the first and second connections can be transmitted based on the second connection. For example, after the source service processing network element switches to the target service processing network element, the target service processing network element can send the mapping information related to the first and second connections to the terminal device through the second connection. Since the messages of the second connection are themselves sent on the second connection, the information sent by the target service processing network element to the terminal device can be a portion of the mapping information. For example, the information sent by the target service processing network element to the terminal device may not include the connection information of the second connection.

[0208] In the above implementation, the information transmitted through the second connection already includes the connection information of the second connection. The mapping information received by the terminal device may include the information transmitted through the second connection and the information sent by the target service processing network element for user plane migration.

[0209] As an example, the information sent by the target service processing network element for user plane migration may be one or more of the following: session information associated with the first connection; session information associated with the first connection and session information associated with the second connection; connection information of the first connection.

[0210] As one implementation, in scenarios where mapping information is sent through a second connection, when the terminal device receives information that is session information associated with the first connection, the terminal device will subsequently send the data packets corresponding to the session information associated with the first connection on the second connection.

[0211] As one implementation, in scenarios where mapped information is sent via a second connection, when the terminal device receives session information associated with both the first and second connections, the terminal device sends data over the second connection. The terminal device can map the session information associated with the first connection to the session information associated with the second connection before sending.

[0212] As one implementation, in scenarios where mapping information is sent through a second connection, when the terminal device receives connection information from the first connection, the terminal device will send all data corresponding to the first connection on the second connection.

[0213] In some implementations, when mapping information related to the first and second connections is transmitted over the second connection, this mapping information can also indicate a first mapping relationship. The first mapping relationship can be a mapping between the connection information of the first connection and / or the session information associated with the first connection and the connection information of the second connection. As mentioned earlier, data transmission over the second connection carries the connection information of the second connection. Therefore, when only the connection information of the first connection and / or the associated session information is transmitted over the second connection, the first mapping relationship can be implicitly indicated. That is, the first mapping relationship can be indicated by transmitting the connection information of the first connection and / or the session information associated with the first connection over the second connection.

[0214] As one implementation, when the connection information of the first connection is transmitted over the second connection, the first mapping relationship is the mapping relationship between the connection information of the first connection and the connection information of the second connection.

[0215] As one implementation, when session information associated with the first connection is transmitted over the second connection, the first mapping relationship is the mapping relationship between the session information associated with the first connection and the connection information of the second connection.

[0216] As one implementation, when the connection information of the first connection and the session information associated with the first connection are transmitted on the second connection, the first mapping relationship is the mapping relationship between the connection information of the first connection and the session information associated with the first connection and the connection information of the second connection.

[0217] In some implementations, when mapping information related to the first and second connections is transmitted based on the second connection, this mapping information can be transmitted in different ways. As one implementation, the mapping information can be carried on signaling transmitted through the second connection. For example, the terminal device can receive the mapping information through signaling transmitted through the second connection, thereby determining the mapping relationship between the first and second information, or the first mapping relationship. As another implementation, the mapping information can be carried in the header of data packets transmitted through the second connection. For example, the terminal device can determine the mapping information through the header information of any data packet or at least one data packet transmitted through the second connection.

[0218] As one implementation, the connection identifier of the first connection can be determined either by the header information of the data packets transmitted by the second connection or by the signaling transmitted by the second connection.

[0219] In the above implementation, the synchronization of mapping information related to the first and second connections can be achieved either through control plane signaling or through the second connection. If implemented through the second connection, the mapping relationship information can be determined either by the header information of the data packets transmitted over the connection or by signaling transmission.

[0220] The target service processing network element can proactively send mapping information related to the first and second connections, or it can send this mapping information based on certain triggering conditions. Different triggering methods can adapt to connection migration in various scenarios.

[0221] In some implementations, the target service processing network element can proactively send mapping information related to the first and second connections to the terminal device and / or the first core network element, so that the terminal device can transmit data packets according to the mapping relationship. For example, the target service processing network element can send the mapping information to the terminal device and / or the first core network element immediately after establishing the second connection with the terminal device. Alternatively, the target service processing network element can send the mapping information to the terminal device and / or the first core network element after a certain period of time following the establishment of the second connection. The duration of this certain period of time can be fixed or variable.

[0222] As one implementation, the target service processing network element can proactively send the mapping information to the terminal device through one or more sessions via a third or second connection.

[0223] In some implementations, the target service processing network element can send mapping information related to the first connection and the second connection to the terminal device and / or the first core network element based on triggering conditions. These triggering conditions can be related to the terminal device.

[0224] In some implementations, before the terminal device receives the mapping information related to the first and second connections, it may send first data associated with the first connection to the target service processing network element. The target service processing network element may send the mapping information after receiving the first data sent by the terminal device. The first data can be sent through one or more sessions.

[0225] As one implementation, after the first connection is released, if the terminal device does not receive the mapping information related to the first and second connections, the first data sent by the terminal device to the target service processing network element may use the session information associated with the first connection. The release of the first connection can occur after the second connection is established.

[0226] In the above implementation, after the target service processing network element receives the first data using the old session identifier, it can send the mapping information to the terminal device, thereby facilitating the terminal device to determine the mapping relationship between the first and second information, or to determine the first mapping relationship. The method by which the terminal device receives the mapping information through the third or second connection is as described above and will not be repeated here.

[0227] In the above implementation, the first data may include a session identifier associated with the first connection, so as to trigger the target service processing network element to send the mapping information related to the first connection and the second connection to the terminal device.

[0228] As one implementation approach, the target service processing network element can determine the transmission of mapping information based on the received first data. For example, when the first data is transmitted through multiple sessions, the target service processing network element can transmit the mapping information for the specific session it receives the data from. In other words, the target service processing network element replies with the mapping information only for the session for which it receives the data.

[0229] In some implementations, the first data is transmitted via a third connection between the terminal device and the core network, or via a second connection. That is, the terminal device will not simultaneously send the first data via both the third and second connections.

[0230] As one implementation, the first data is transmitted via a third connection between the terminal device and the core network. For example, after the first connection between the terminal device and the source service processing network element is released, if new data is generated, the terminal device can send the first data to the first core network element through the third connection. The first core network element can then transmit the first data to the target service processing network element. Similarly, after the first connection between the terminal device and the source service processing network element is released, if new data is generated, the terminal device can send the first data to the source service processing network element through the third connection. The source service processing network element can then transmit the first data to the target service processing network element.

[0231] As one implementation, the first data is transmitted through a second connection. For example, after the first connection between the terminal device and the source service processing network element is released, if new data is generated, the terminal device can send the first data to the target service processing network element through the second connection with the target service processing network element.

[0232] The communication method has been explained above from the perspective of the terminal device, referring to Figure 8. The following explanations, referring to Figures 9 and 10, describe the communication method from the perspectives of the target service processing network element and the first core network element, respectively. For simplicity, the terminology already explained in Figure 8 will not be repeated.

[0233] Figure 9 describes the interaction between the terminal device and the target service processing network element. The method shown in Figure 9 includes step S910.

[0234] Referring to Figure 9, in step S910, the target service processing network element sends mapping information related to the first connection and the second connection to the terminal device. This step is performed after the source service processing network element in the core network switches to the target service processing network element. As mentioned above, the mapping information indicates the mapping relationship between the first information and the second information.

[0235] In some implementations, when the first information is the session information of the first session associated with the first connection and the second information is the connection information of the second connection, the target service processing network element can receive the data associated with the first session on the second connection.

[0236] In some implementations, when the first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection, the target service processing network element receives the data associated with the first session on the second connection, and the data associated with the first session is transmitted based on the second session.

[0237] In some implementations, when the first information is the connection information of the first connection and the second information is the connection information of the second connection, the target service processing network element receives the data associated with the first connection on the second connection.

[0238] In some implementations, when the first information is the session information of the first session associated with the first connection and the second information is the session information of the second session associated with the second connection, the target service processing network element receives the data associated with the first session on the second connection, and the data associated with the first session is transmitted based on the second session.

[0239] In some implementations, before the terminal device receives the mapping information related to the first and second connections, the target service processing network element can receive the first data associated with the first connection sent by the terminal device. As one implementation, the first data can be transmitted via a third connection between the terminal device and the core network. As another implementation, the first data can be transmitted via a second connection.

[0240] Figure 10 describes the interaction between the terminal device and the first core network element. The method shown in Figure 10 includes step S1010.

[0241] Referring to Figure 10, in step S1010, the first core network element receives mapping information related to the first and second connections sent by the target service processing network element. This step is performed after the source service processing network element of the core network switches to the target service processing network element.

[0242] In some implementations, before the terminal device receives the mapping information, the first core network element can receive the first data associated with the first connection sent by the terminal device and transmit the first data to the target service processing network element.

[0243] The above section, with reference to Figures 8 to 10, introduces a method for sensing connection migration. This method designs schemes for sending different connection mapping relationships to the terminal device via the control plane and user plane, respectively, for connection migration context synchronization between the network side and the terminal device side. Furthermore, the method proposes two triggering conditions: one where the network side actively triggers the notification, and the other where the network side triggers the notification after receiving the data packet reported by the terminal device. These methods solve the problem of how to send location / sensing data packets to the correct connection in different scenarios, ensuring the normal progress of connection migration.

[0244] The following examples illustrate various methods for sending mapping relationships during connection migration. In the examples below, the first connection and the second connection are the first user plane connection and the second user plane connection, respectively, and the third connection is the control plane connection.

[0245] Example 1

[0246] In Embodiment 1, the mapping information related to the first user plane connection and the second user plane connection received by the terminal device is transmitted via control plane signaling. After the source service processing network element switches to the target service processing network element, the target service processing network element can send the relevant mapping information through the control plane connection, so that the terminal device can determine the mapping relationship between the first user plane connection and the second user plane connection. This mapping relationship may include the connection information of the first user plane connection and / or the session information associated with the first user plane connection, and may also include the connection information of the second user plane connection and / or the session information associated with the second user plane connection.

[0247] The specific implementation process of Embodiment 1 will be described below with reference to Figure 11. In Figure 11, NF1 is the first core network element, NF2a is the source service processing network element, and NF2b is the target service processing network element.

[0248] Referring to Figure 11, in step S1102, following the relevant process, NF2a and the terminal device establish a user plane connection, namely the first user plane connection.

[0249] In step S1104, NF2a decides to migrate and sends a migration request to NF1.

[0250] In step S1106, NF1 selects NF2b as the target NF2.

[0251] In step S1108, NF1 sends a configuration request to NF2a, which includes information about NF2b. The information about NF2b may include its identification information or address information, etc.

[0252] In step S1110, NF2a performs a context relocation to NF2b. Specifically, NF2a may send some session information (session info) and connection information (connection info) that needs to be relocated to NF2b. The old session information may be the session information associated with the first user plane connection.

[0253] In step S1112, NF2b establishes a user plane connection with the terminal device, i.e., the second user plane connection is established.

[0254] In step S1114, after obtaining the migration context information, NF2b sends a first message to NF1, which contains one or more of connection information and / or session information. The session information 1 in the first message is the session information of the first session.

[0255] In step S1116, NF1 sends a second message to the terminal device, which includes one or more of connection information and / or session information. Optionally, NF1 may directly forward the information received from NF2b, or it may further map the session information before sending it. For example, the session information 2 in the second message may be the session information of a second session.

[0256] In step S1118, the terminal device transmits user plane data based on the received connection information and / or session information. The terminal device and NF2b can transmit data packets through the second user plane connection. Data transmission performed by the terminal device may include the following scenarios.

[0257] In scenario a, the terminal device receives new connection information (connection information for the second user plane connection) and old session information (session information associated with the first user plane connection). In this scenario, the terminal device will subsequently send the data packets corresponding to the old session information on the new user plane connection (the second user plane connection).

[0258] In scenario b, the terminal device receives new connection information, old session information, and the corresponding new session information (session information associated with the second user plane connection). In this scenario, the terminal device sends data in the new user plane connection and maps the old session information to the new session information before sending. The terminal device can map the old session / associated identifier to the new session / associated identifier.

[0259] In scenario c, the terminal device receives both new and old connection information (connection information for the first user plane connection). In this scenario, the terminal device will transmit all data corresponding to the old user plane connection (the first user plane connection) over the new user plane connection.

[0260] In scenario d, the terminal device receives both new and old session information. In this scenario, the terminal device maps the old session information to the new session information before sending it. The terminal device can refer to scenario b for mapping related identifiers.

[0261] In scenario e, the terminal device first receives the mapping relationship between new and old connection information (scenario c), and then receives the mapping relationship between new and old session information (scenario d). Therefore, the target service processing network element can first inform the terminal device of the mapping relationship between new and old connection information, and then inform it of the mapping relationship between new and old session information. In this scenario, the terminal device sends all data corresponding to the old user plane connection on the new user plane connection and maps the old session information to the new session information.

[0262] In scenario f, the terminal device first receives the mapping relationship between new connection information and old session information (scenario a), and then receives the mapping relationship between new session information and old session information (scenario d). Therefore, the target service processing network element can first inform the terminal device of the mapping relationship between new connection information and old session information, and then inform it of the mapping relationship between the old and new session information. In this scenario, the terminal device sends the data packets corresponding to the old session information on the new user plane connection and maps the old session information to the new session information.

[0263] It should be noted that the above-mentioned scenarios of terminal devices transmitting data based on received mapping information are merely examples and not limitations. For instance, terminal devices can also receive other mapping relationships or combinations of mapping relationships. Furthermore, for mapping information consisting of combinations of mapping relationships, terminal devices can receive different mapping relationships sequentially or simultaneously.

[0264] Example 2

[0265] In Embodiment 2, the mapping information related to the first user plane connection and the second user plane connection received by the terminal device is transmitted through the second user plane connection. After the source service processing network element switches to the target service processing network element, the target service processing network element can send the relevant mapping information through the second user plane connection, so that the terminal device can determine the mapping relationship between the first user plane connection and the second user plane connection. This mapping relationship is the same as in Embodiment 1 and will not be described again.

[0266] The specific implementation process of Embodiment 2 will be described below with reference to Figure 12. In Figure 12, NF1 is the first core network element, NF2a is the source service processing network element, and NF2b is the target service processing network element.

[0267] Referring to Figure 12, steps S1202 to S1212 are the same as steps S1102 to S1112 in Figure 11, and will not be described again.

[0268] In step S1214, after obtaining the migration context information, NF2b sends a first message to the terminal device through the second user plane connection, which contains one or more of connection information and / or session information. The session information 1 in the first message is the session information of the first session.

[0269] In step S1216, the terminal device transmits user plane data based on the received connection information and / or session information. The terminal device and NF2b can transmit data packets through the second user plane connection. Data transmission performed by the terminal device may include the following scenarios.

[0270] In scenario a, the terminal device receives old session information (session information associated with the first user plane connection). The terminal device then sends the data packets corresponding to the old session information on the new user plane connection (the second user plane connection).

[0271] Scenario b: When the terminal device receives both old session information and corresponding new session information (session information associated with the second user plane connection). In this scenario, the terminal device sends data in the new user plane connection. The terminal device can refer to Embodiment 1 to map the old session information into the new session information for transmission.

[0272] In scenario c, the terminal device receives the old connection information (the connection information of the first user plane connection). In this scenario, the terminal device will send all data corresponding to the old user plane connection on the new user plane connection.

[0273] Example 3

[0274] In Embodiment 3, after receiving the first data sent by the terminal device, the target service processing network element sends mapping information related to the first user plane connection and the second user plane connection through the control plane connection. The main difference from Embodiment 1 is that in Embodiment 1, the target service processing network element actively notifies the terminal device of the mapping information (one or more sessions) after obtaining the migration context; while in Embodiment 3, the target service processing network element replies, i.e., sends the mapping information, after receiving the first data sent by the terminal device.

[0275] The specific implementation process of Embodiment 3 will be described below with reference to Figure 13. In Figure 13, NF1 is the first core network element, NF2a is the source service processing network element, and NF2b is the target service processing network element.

[0276] Referring to Figure 13, steps S1302 to S1312 are the same as steps S1102 to S1112 in Figure 11, and will not be described again.

[0277] In step S1314, the user plane connection between the terminal device and NF2a is released, that is, the first user plane connection is released.

[0278] In step S1316, after the terminal device releases the user plane connection with NF2a, if new data is generated, it sends the data, i.e., the first data, through the user plane connection with NF2b (the second user plane connection). The first data may use the old session identifier (or session information).

[0279] In step S1318, after the terminal device releases the user plane connection with NF2a, if new data is generated, it sends the data, i.e., the first data, to NF2a through the control plane connection via NF1. Similarly, the first data may use the old session identifier (or session information).

[0280] In step S1320, NF2a sends the received data to NF2b, which may contain old session identifiers.

[0281] It should be noted that steps S1316 and S1318, S1320 will not be performed simultaneously; that is, only one of them will occur.

[0282] In step S1322, after receiving data using the old session identifier, NF2b sends a first message to NF1. The first message contains one or more of connection information and / or session information. The session information 1 may include new session information and old session information.

[0283] Steps S1324 and S1326 are the same as steps S1116 and S1118 in Figure 11, and will not be described again.

[0284] Example 4

[0285] In Embodiment 4, after receiving the first data sent by the terminal device, the target service processing network element sends mapping information related to the first user plane connection and the second user plane connection through the user plane connection. The main difference from Embodiment 2 is that in Embodiment 2, the target service processing network element actively notifies the terminal device of the mapping information after obtaining the migration context; while in Embodiment 4, the target service processing network element replies, i.e., sends the mapping information, after receiving the first data sent by the terminal device.

[0286] The specific implementation process of Embodiment 4 will be described below with reference to Figure 14. In Figure 14, NF1 is the first core network element, NF2a is the source service processing network element, and NF2b is the target service processing network element.

[0287] Referring to Figure 14, steps S1402 to S1412 are the same as steps S1102 to S1112 in Figure 11, and will not be described again.

[0288] In step S1414, the user plane connection between the terminal device and NF2a is released, that is, the first user plane connection is released.

[0289] In step S1416, after the terminal device releases the user plane connection with NF2a, if new data is generated, it sends the data, i.e., the first data, through the user plane connection with NF2b. The first data may use the old session identifier (or session information).

[0290] In step S1418, after the terminal device releases the user plane connection with NF2a, if new data is generated, it sends the data, i.e., the first data, to NF2a through the control plane connection via NF1. Similarly, the first data may use the old session identifier (or session information).

[0291] In step S1420, NF2a sends the received data to NF2b, which may contain old session identifiers.

[0292] It should be noted that steps S1416 and S1418, S1420 will not be performed simultaneously; that is, only one of them will occur.

[0293] In step S1422, after receiving the data sent by the terminal device, NF2b sends a first message to the terminal device through the user plane connection, which includes one or more of connection information and / or session information. The session information 1 in the first message can be the session information of the first data.

[0294] Step S1424 is the same as step S1216 in Figure 12, and will not be described again.

[0295] The method embodiments of this application have been described in detail above with reference to Figures 1 to 14. The apparatus embodiments of this application will be described in detail below with reference to Figures 15 to 18. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments; therefore, any parts not described in detail can be referred to the preceding method embodiments.

[0296] Figure 15 is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 1500 shown in Figure 15 is any of the terminal devices described above. As shown in Figure 15, the communication device 1500 includes a receiving unit 1510.

[0297] The receiving unit 1510 can be used to receive mapping information related to the first connection and the second connection after the source service processing network element in the core network is switched to the target service processing network element; wherein, the first connection is the connection between the terminal device and the source service processing network element, and the second connection is the connection between the terminal device and the target service processing network element.

[0298] In some implementations, the mapping information is used to indicate the mapping relationship between the first information and the second information, wherein the first information includes the connection information of the first connection and / or the session information associated with the first connection, and the second information includes the connection information of the second connection and / or the session information associated with the second connection.

[0299] In some implementations, the first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; or, the first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; or, the first information is the connection information of the first connection, and the second information is the connection information of the second connection; or, the first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection.

[0300] In some implementations, the first information is session information of a first session associated with the first connection, and the second information is connection information of the second connection; the communication device 1500 further includes a first transmitting unit, which can be used to transmit data associated with the first session on the second connection.

[0301] In some implementations, the first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; the communication device 1500 further includes a second sending unit, which can be used to transmit the data associated with the first session on the second connection based on the second session.

[0302] In some implementations, the first information is the connection information of the first connection, and the second information is the connection information of the second connection; the communication device 1500 further includes a third transmitting unit, which can be used to transmit data associated with the first connection on the second connection.

[0303] In some implementations, the first information is session information of a first session associated with the first connection, and the second information is session information of a second session associated with the second connection; the communication device 1500 further includes a fourth transmitting unit, which can be used to transmit data associated with the first session on the second connection based on the second session.

[0304] In some implementations, the mapping information is transmitted based on a third connection between the terminal device and the core network, wherein the first connection and the second connection are of the same type, and the third connection is of a different type than the first connection.

[0305] In some implementations, the mapping information is transmitted based on the second connection.

[0306] In some implementations, the mapping information indicates a first mapping relationship, which is a mapping relationship between the connection information of the first connection and / or the session information associated with the first connection and the connection information of the second connection, and the first mapping relationship indicates that the connection information of the first connection and / or the session information associated with the first connection is transmitted on the second connection.

[0307] In some implementations, the mapping information is carried in the header of signaling transmitted through the second connection or data packets transmitted through the second connection.

[0308] In some implementations, before the terminal device receives the mapping information related to the first connection and the second connection, the communication device 1500 further includes a fifth sending unit, which can be used to send the first data associated with the first connection to the target service processing network element.

[0309] In some implementations, the first data is transmitted via a third connection between the terminal device and the core network, or via a second connection, wherein the first connection and the second connection are of the same type, and the third connection is of a different type than the first connection.

[0310] Figure 16 is a schematic diagram of another communication device provided in an embodiment of this application. The communication device 1600 shown in Figure 16 is any of the target service processing network elements described above. As shown in Figure 16, the communication device 1600 includes a transmitting unit 1610.

[0311] The sending unit 1610 can be used to send mapping information related to a first connection and a second connection to a terminal device after the source service processing network element in the core network is switched to the target service processing network element; wherein, the first connection is the connection between the terminal device and the source service processing network element, and the second connection is the connection between the terminal device and the target service processing network element.

[0312] In some implementations, the mapping information is used to indicate the mapping relationship between the first information and the second information, wherein the first information includes the connection information of the first connection and / or the session information associated with the first connection, and the second information includes the connection information of the second connection and / or the session information associated with the second connection.

[0313] In some implementations, the first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; or, the first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; or, the first information is the connection information of the first connection, and the second information is the connection information of the second connection; or, the first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection.

[0314] In some implementations, the first information is session information of a first session associated with the first connection, and the second information is connection information of the second connection; the communication device 1600 further includes a first receiving unit, which can be used to receive data associated with the first session on the second connection.

[0315] In some implementations, the first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; the communication device 1600 further includes a second receiving unit, which can be used to receive the data associated with the first session on the second connection, and the data associated with the first session is transmitted based on the second session.

[0316] In some implementations, the first information is the connection information of the first connection, and the second information is the connection information of the second connection; the communication device 1600 further includes a third receiving unit, which can be used to receive data associated with the first connection on the second connection.

[0317] In some implementations, the first information is session information of a first session associated with the first connection, and the second information is session information of a second session associated with the second connection; the communication device 1600 further includes a fourth receiving unit, configured to receive data associated with the first session on the second connection, and the data associated with the first session is transmitted based on the second session.

[0318] In some implementations, the mapping information is transmitted based on a third connection between the terminal device and the core network, wherein the first connection and the second connection are of the same type, and the third connection is of a different type than the first connection.

[0319] In some implementations, the mapping information is transmitted based on the second connection.

[0320] In some implementations, the mapping information indicates a first mapping relationship, which is a mapping relationship between the connection information of the first connection and / or the session information associated with the first connection and the connection information of the second connection, and the first mapping relationship indicates that the connection information of the first connection and / or the session information associated with the first connection is transmitted on the second connection.

[0321] In some implementations, the mapping information is carried in the header of signaling transmitted through the second connection or data packets transmitted through the second connection.

[0322] In some implementations, before the terminal device receives the mapping information related to the first connection and the second connection, the communication device 1600 further includes a fifth receiving unit that can be used to receive first data associated with the first connection sent by the terminal device.

[0323] In some implementations, the first data is transmitted via a third connection between the terminal device and the core network, or via a second connection, wherein the first connection and the second connection are of the same type, and the third connection is of a different type than the first connection.

[0324] Figure 17 is a schematic diagram of another communication device provided in an embodiment of this application. The communication device 1700 shown in Figure 17 is any of the first core network elements described above. As shown in Figure 17, the communication device 1700 includes a first receiving unit 1710.

[0325] The first receiving unit 1710 can be used to receive mapping information related to a first connection and a second connection sent by the target service processing network element after the source service processing network element in the core network is switched to the target service processing network element; wherein, the first connection is the connection between the terminal device and the source service processing network element, and the second connection is the connection between the terminal device and the target service processing network element.

[0326] In some implementations, the mapping information is used to indicate the mapping relationship between the first information and the second information, wherein the first information includes the connection information of the first connection and / or the session information associated with the first connection, and the second information includes the connection information of the second connection and / or the session information associated with the second connection.

[0327] In some implementations, the first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; or, the first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; or, the first information is the connection information of the first connection, and the second information is the connection information of the second connection; or, the first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection.

[0328] In some implementations, the mapping information is transmitted based on a third connection between the terminal device and the core network, wherein the first connection and the second connection are of the same type, and the third connection is of a different type than the first connection.

[0329] In some implementations, the mapping information is transmitted based on the second connection.

[0330] In some implementations, the mapping information indicates a first mapping relationship, which is a mapping relationship between the connection information of the first connection and / or the session information associated with the first connection and the connection information of the second connection, and the first mapping relationship indicates that the connection information of the first connection and / or the session information associated with the first connection is transmitted on the second connection.

[0331] In some implementations, the mapping information is carried in the header of signaling transmitted through the second connection or data packets transmitted through the second connection.

[0332] In some implementations, before the terminal device receives the mapping information related to the first connection and the second connection, the communication device 1700 further includes a second receiving unit that can be used to receive first data associated with the first connection sent by the terminal device; and a sending unit that can be used to transmit the first data to the target service processing network element.

[0333] Figure 18 is a schematic structural diagram of a communication device according to an embodiment of this application. The dashed lines in Figure 18 indicate that the unit or module is optional. This device 1800 can be used to implement the methods described in the above method embodiments. Device 1800 can be a chip, a terminal device, or a core network element.

[0334] Apparatus 1800 may include one or more processors 1810. The processor 1810 may support apparatus 1800 in implementing the methods described in the preceding method embodiments. The processor 1810 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0335] The apparatus 1800 may further include one or more memories 1820. The memories 1820 store a program that can be executed by the processor 1810, causing the processor 1810 to perform the methods described in the preceding method embodiments. The memories 1820 may be independent of the processor 1810 or integrated within the processor 1810.

[0336] The device 1800 may also include a transceiver 1830. The processor 1810 can communicate with other devices or chips via the transceiver 1830. For example, the processor 1810 can send and receive data with other devices or chips via the transceiver 1830.

[0337] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to a terminal device or core network element provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device or core network element in various embodiments of this application.

[0338] This application also provides a computer program product. The computer program product includes a program. This computer program product can be applied to a terminal or network device provided in this application embodiment, and the program causes a computer to execute the methods performed by the terminal device or core network element in various embodiments of this application.

[0339] This application also provides a computer program. This computer program can be applied to the terminal device or core network element provided in this application embodiment, and the computer program causes the computer to execute the methods performed by the terminal device or core network element in the various embodiments of this application.

[0340] It should be understood that the terminology used in this application is only for explaining specific embodiments of this application and is not intended to limit this application. The terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

[0341] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0342] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0343] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0344] In this application embodiment, "predefined" or "preconfigured" can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0345] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems. This application does not limit this.

[0346] In the embodiments of this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0347] In the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0348] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0349] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0350] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0351] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0352] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: After the source service processing network element in the core network is switched to the target service processing network element, the terminal device receives the mapping information related to the first connection and the second connection. Wherein, the first connection is the connection between the terminal device and the source service processing network element, and the second connection is the connection between the terminal device and the target service processing network element.

2. The method according to claim 1, characterized in that, The mapping information is used to indicate the mapping relationship between the first information and the second information. The first information includes the connection information of the first connection and / or the session information associated with the first connection, and the second information includes the connection information of the second connection and / or the session information associated with the second connection.

3. The method according to claim 2, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; or, The first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; or, The first information is the connection information of the first connection, and the second information is the connection information of the second connection; or, The first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection.

4. The method according to claim 3, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; The method further includes: The terminal device transmits the data associated with the first session over the second connection.

5. The method according to claim 3, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; The method further includes: The terminal device transmits data associated with the first session on the second connection based on the second session.

6. The method according to claim 3, characterized in that: The first information is the connection information of the first connection, and the second information is the connection information of the second connection; The method further includes: The terminal device transmits data associated with the first connection over the second connection.

7. The method according to claim 3, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection; The method further includes: The terminal device transmits data associated with the first session on the second connection based on the second session.

8. The method according to any one of claims 1 to 7, characterized in that, The mapping information is transmitted based on a third connection between the terminal device and the core network. The first connection and the second connection are of the same type, while the third connection is of a different type than the first connection.

9. The method according to any one of claims 1 to 7, characterized in that, The mapping information is transmitted based on the second connection.

10. The method according to claim 9, characterized in that, The mapping information indicates a first mapping relationship, which is a mapping relationship between the connection information of the first connection and / or the session information associated with the first connection and the connection information of the second connection, and the first mapping relationship indicates that the connection information of the first connection and / or the session information associated with the first connection is transmitted on the second connection.

11. The method according to claim 9 or 10, characterized in that, The mapping information is carried in the header of signaling transmitted through the second connection or data packets transmitted through the second connection.

12. The method according to any one of claims 1 to 11, characterized in that, Before the terminal device receives the mapping information related to the first connection and the second connection, the method further includes: The terminal device sends the first data associated with the first connection to the target service processing network element.

13. The method according to claim 12, characterized in that, The first data is transmitted through a third connection between the terminal device and the core network, or through a second connection. The first connection and the second connection are of the same type, while the third connection is of a different type than the first connection.

14. A communication method, characterized in that, include: After the source service processing network element in the core network is switched to the target service processing network element, the target service processing network element sends mapping information related to the first connection and the second connection to the terminal device. Wherein, the first connection is the connection between the terminal device and the source service processing network element, and the second connection is the connection between the terminal device and the target service processing network element.

15. The method according to claim 14, characterized in that, The mapping information is used to indicate the mapping relationship between the first information and the second information. The first information includes the connection information of the first connection and / or the session information associated with the first connection, and the second information includes the connection information of the second connection and / or the session information associated with the second connection.

16. The method according to claim 15, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; or, The first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; or, The first information is the connection information of the first connection, and the second information is the connection information of the second connection; or, The first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection.

17. The method according to claim 16, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; The method further includes: The target service processing network element receives the data associated with the first session on the second connection.

18. The method according to claim 16, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; The method further includes: The target service processing network element receives the data associated with the first session on the second connection, and the data associated with the first session is transmitted based on the second session.

19. The method according to claim 16, characterized in that: The first information is the connection information of the first connection, and the second information is the connection information of the second connection; The method further includes: The target service processing network element receives data associated with the first connection on the second connection.

20. The method according to claim 16, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection; The method further includes: The target service processing network element receives the data associated with the first session on the second connection, and the data associated with the first session is transmitted based on the second session.

21. The method according to any one of claims 14 to 20, characterized in that, The mapping information is transmitted based on a third connection between the terminal device and the core network. The first connection and the second connection are of the same type, while the third connection is of a different type than the first connection.

22. The method according to any one of claims 14 to 20, characterized in that, The mapping information is transmitted based on the second connection.

23. The method according to claim 22, characterized in that, The mapping information indicates a first mapping relationship, which is a mapping relationship between the connection information of the first connection and / or the session information associated with the first connection and the connection information of the second connection, and the first mapping relationship indicates that the connection information of the first connection and / or the session information associated with the first connection is transmitted on the second connection.

24. The method according to claim 22 or 23, characterized in that, The mapping information is carried in the header of signaling transmitted through the second connection or data packets transmitted through the second connection.

25. The method according to any one of claims 14 to 24, characterized in that, Before the terminal device receives the mapping information related to the first connection and the second connection, the method further includes: The target service processing network element receives the first data associated with the first connection sent by the terminal device.

26. The method according to claim 25, characterized in that, The first data is transmitted through a third connection between the terminal device and the core network, or through a second connection. The first connection and the second connection are of the same type, while the third connection is of a different type than the first connection.

27. A communication method, characterized in that, include: After the source service processing network element in the core network switches to the target service processing network element, the first core network element receives the mapping information related to the first connection and the second connection sent by the target service processing network element. Wherein, the first connection is the connection between the terminal device and the source service processing network element, and the second connection is the connection between the terminal device and the target service processing network element.

28. The method according to claim 27, characterized in that, The mapping information is used to indicate the mapping relationship between the first information and the second information. The first information includes the connection information of the first connection and / or the session information associated with the first connection, and the second information includes the connection information of the second connection and / or the session information associated with the second connection.

29. The method according to claim 28, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; or, The first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; or, The first information is the connection information of the first connection, and the second information is the connection information of the second connection; or, The first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection.

30. The method according to any one of claims 27 to 29, characterized in that, The mapping information is transmitted based on a third connection between the terminal device and the core network. The first connection and the second connection are of the same type, while the third connection is of a different type than the first connection.

31. The method according to any one of claims 27 to 29, characterized in that, The mapping information is transmitted based on the second connection.

32. The method according to claim 31, characterized in that, The mapping information indicates a first mapping relationship, which is a mapping relationship between the connection information of the first connection and / or the session information associated with the first connection and the connection information of the second connection, and the first mapping relationship indicates that the connection information of the first connection and / or the session information associated with the first connection is transmitted on the second connection.

33. The method according to claim 31 or 32, characterized in that, The mapping information is carried in the header of signaling transmitted through the second connection or data packets transmitted through the second connection.

34. The method according to any one of claims 27 to 33, characterized in that, Before the terminal device receives the mapping information related to the first connection and the second connection, the method further includes: The first core network element receives first data associated with the first connection sent by the terminal device; The first core network element transmits the first data to the target service processing network element.

35. A communication device, characterized in that, The communication device is a terminal device, and the communication device includes: The receiving unit is used to receive mapping information related to the first connection and the second connection after the source service processing network element of the core network is switched to the target service processing network element; Wherein, the first connection is the connection between the terminal device and the source service processing network element, and the second connection is the connection between the terminal device and the target service processing network element.

36. The communication device according to claim 35, characterized in that, The mapping information is used to indicate the mapping relationship between the first information and the second information. The first information includes the connection information of the first connection and / or the session information associated with the first connection, and the second information includes the connection information of the second connection and / or the session information associated with the second connection.

37. The communication device according to claim 36, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; or, The first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; or, The first information is the connection information of the first connection, and the second information is the connection information of the second connection; or, The first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection.

38. The communication device according to claim 37, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; The communication device also includes: The first sending unit is used to transmit data associated with the first session over the second connection.

39. The communication device according to claim 37, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; The communication device also includes: The second sending unit is used to transmit data associated with the first session over the second connection based on the second session.

40. The communication device according to claim 37, characterized in that: The first information is the connection information of the first connection, and the second information is the connection information of the second connection; The communication device also includes: The third sending unit is used to transmit data associated with the first connection on the second connection.

41. The communication device according to claim 37, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection; The communication device also includes: The fourth sending unit is used to transmit data associated with the first session on the second connection based on the second session.

42. The communication device according to any one of claims 35 to 41, characterized in that, The mapping information is transmitted based on a third connection between the terminal device and the core network. The first connection and the second connection are of the same type, while the third connection is of a different type than the first connection.

43. The communication device according to any one of claims 35 to 41, characterized in that, The mapping information is transmitted based on the second connection.

44. The communication device according to claim 43, characterized in that, The mapping information indicates a first mapping relationship, which is a mapping relationship between the connection information of the first connection and / or the session information associated with the first connection and the connection information of the second connection, and the first mapping relationship indicates that the connection information of the first connection and / or the session information associated with the first connection is transmitted on the second connection.

45. The communication device according to claim 43 or 44, characterized in that, The mapping information is carried in the header of signaling transmitted through the second connection or data packets transmitted through the second connection.

46. ​​The communication device according to any one of claims 35 to 45, characterized in that, Before the terminal device receives the mapping information related to the first connection and the second connection, the communication device further includes: The fifth sending unit is used to send the first data associated with the first connection to the target service processing network element.

47. The communication device according to claim 46, characterized in that, The first data is transmitted through a third connection between the terminal device and the core network, or through a second connection. The first connection and the second connection are of the same type, while the third connection is of a different type than the first connection.

48. A communication device, characterized in that, The communication device is a target service processing network element, and the communication device includes: The sending unit is used to send mapping information related to the first connection and the second connection to the terminal device after the source service processing network element of the core network is switched to the target service processing network element; Wherein, the first connection is the connection between the terminal device and the source service processing network element, and the second connection is the connection between the terminal device and the target service processing network element.

49. The communication device according to claim 48, characterized in that, The mapping information is used to indicate the mapping relationship between the first information and the second information. The first information includes the connection information of the first connection and / or the session information associated with the first connection, and the second information includes the connection information of the second connection and / or the session information associated with the second connection.

50. The communication device according to claim 49, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; or, The first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; or, The first information is the connection information of the first connection, and the second information is the connection information of the second connection; or, The first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection.

51. The communication device according to claim 50, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; The communication device also includes: The first receiving unit is configured to receive data associated with the first session on the second connection.

52. The communication device according to claim 50, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; The communication device also includes: The second receiving unit is configured to receive data associated with the first session on the second connection, wherein the data associated with the first session is transmitted based on the second session.

53. The communication device according to claim 50, characterized in that: The first information is the connection information of the first connection, and the second information is the connection information of the second connection; The communication device also includes: The third receiving unit is used to receive data associated with the first connection on the second connection.

54. The communication device according to claim 50, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection; The communication device also includes: The fourth receiving unit is configured to receive data associated with the first session on the second connection, wherein the data associated with the first session is transmitted based on the second session.

55. The communication device according to any one of claims 48 to 54, characterized in that, The mapping information is transmitted based on a third connection between the terminal device and the core network. The first connection and the second connection are of the same type, while the third connection is of a different type than the first connection.

56. The communication device according to any one of claims 48 to 54, characterized in that, The mapping information is transmitted based on the second connection.

57. The communication device according to claim 56, characterized in that, The mapping information indicates a first mapping relationship, which is a mapping relationship between the connection information of the first connection and / or the session information associated with the first connection and the connection information of the second connection, and the first mapping relationship indicates that the connection information of the first connection and / or the session information associated with the first connection is transmitted on the second connection.

58. The communication device according to claim 56 or 57, characterized in that, The mapping information is carried in the header of signaling transmitted through the second connection or data packets transmitted through the second connection.

59. The communication device according to any one of claims 48 to 58, characterized in that, Before the terminal device receives the mapping information related to the first connection and the second connection, the communication device further includes: The fifth receiving unit is used to receive the first data associated with the first connection sent by the terminal device.

60. The communication device according to claim 59, characterized in that, The first data is transmitted through a third connection between the terminal device and the core network, or through a second connection. The first connection and the second connection are of the same type, while the third connection is of a different type than the first connection.

61. A communication device, characterized in that, The communication device is a first core network element, and the communication device includes: The first receiving unit is used to receive mapping information related to the first connection and the second connection sent by the target service processing network element after the source service processing network element of the core network is switched to the target service processing network element. Wherein, the first connection is the connection between the terminal device and the source service processing network element, and the second connection is the connection between the terminal device and the target service processing network element.

62. The communication device according to claim 61, characterized in that, The mapping information is used to indicate the mapping relationship between the first information and the second information. The first information includes the connection information of the first connection and / or the session information associated with the first connection, and the second information includes the connection information of the second connection and / or the session information associated with the second connection.

63. The communication device according to claim 62, characterized in that: The first information is the session information of the first session associated with the first connection, and the second information is the connection information of the second connection; or, The first information is the session information of the first session associated with the first connection, and the second information includes the connection information of the second connection and the session information of the second session associated with the second connection; or, The first information is the connection information of the first connection, and the second information is the connection information of the second connection; or, The first information is the session information of the first session associated with the first connection, and the second information is the session information of the second session associated with the second connection.

64. The communication device according to any one of claims 61 to 63, characterized in that, The mapping information is transmitted based on a third connection between the terminal device and the core network. The first connection and the second connection are of the same type, while the third connection is of a different type than the first connection.

65. The communication device according to any one of claims 61 to 63, characterized in that, The mapping information is transmitted based on the second connection.

66. The communication device according to claim 65, characterized in that, The mapping information indicates a first mapping relationship, which is a mapping relationship between the connection information of the first connection and / or the session information associated with the first connection and the connection information of the second connection, and the first mapping relationship indicates that the connection information of the first connection and / or the session information associated with the first connection is transmitted on the second connection.

67. The communication device according to claim 65 or 66, characterized in that, The mapping information is carried in the header of signaling transmitted through the second connection or data packets transmitted through the second connection.

68. The communication device according to any one of claims 61 to 67, characterized in that, Before the terminal device receives the mapping information related to the first connection and the second connection, the communication device further includes: The second receiving unit is used to receive first data sent by the terminal device and associated with the first connection; The sending unit is used to transmit the first data to the target service processing network element.

69. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the communication device performs the method as described in any one of claims 1 to 34.

70. An apparatus, characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1 to 34.

71. A chip, characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 34.

72. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1 to 34.

73. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1 to 34.

74. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1 to 34.

Images