Communication method and communication device

Abstract

Provided are a communication method and a communication device. The method comprises: a terminal device establishes a first connection with a first core network element; the terminal device receives first data by means of the first connection, the first data comprising a first identifier, and the first identifier being used for identifying the first connection.

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) involve user plane data transmission. Terminal devices may transmit data when multiple user plane connections coexist. Therefore, ensuring that the terminal device correctly selects the appropriate user plane connection for data transmission becomes a technical problem that needs to be solved. 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: a terminal device establishing a first connection with a first core network element; the terminal device receiving first data through the first connection, the first data including a first identifier, the first identifier being used to identify the first connection.

[0005] Secondly, a communication method is provided, comprising: a first core network element establishing a first connection with a terminal device; the first core network element sending first data to the terminal device through the first connection, the first data including a first identifier, the first identifier being used to identify the first connection.

[0006] Thirdly, a communication device is provided, which is a terminal device. The communication device includes: a first processing unit for establishing a first connection with a first core network element; and a first receiving unit for receiving first data through the first connection, wherein the first data includes a first identifier, and the first identifier is used to identify the first connection.

[0007] Fourthly, a communication device is provided, the communication device being a first core network element, the communication device comprising: a processing unit for establishing a first connection with a terminal device; and a first sending unit for sending first data to the terminal device through the first connection, the first data including a first identifier, the first identifier being used to identify the first connection.

[0008] Fifthly, a communication device is provided, including a transceiver, a memory, and a processor, wherein the memory is used to store a program, the processor is used to invoke the program in the memory, and to control the transceiver to receive or transmit signals, so that the communication device performs the method as described in the first or second aspect.

[0009] A sixth aspect provides an apparatus including a processor for calling a program from a memory to cause the apparatus to perform the method as described in the first or second aspect.

[0010] A seventh aspect provides a chip including a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in the first or second aspect.

[0011] Eighthly, a computer-readable storage medium is provided having a program stored thereon that causes a computer to perform the method as described in the first or second aspect.

[0012] Ninth aspect, a computer program product is provided, including a program that causes a computer to perform the method as described in the first or second aspect.

[0013] In a tenth aspect, a computer program is provided that causes a computer to perform the method as described in the first or second aspect.

[0014] In this embodiment, after the terminal device establishes a first connection (such as a user plane connection) with a first core network element, it can transmit data through this first connection. The first data (such as user plane data) transmitted on this first connection includes a first identifier used to identify the first connection. Therefore, when the terminal device needs to transmit data on multiple first connections, it can distinguish them based on the identifier of the first connection, which helps improve the service quality. Attached Figure Description

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

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

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

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

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

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

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

[0022] Figure 8 is a schematic flowchart of one possible implementation of the method shown in Figure 7.

[0023] Figure 9 is a schematic flowchart of another possible implementation of the method shown in Figure 7.

[0024] Figure 10 is a schematic flowchart of another possible implementation of the method shown in Figure 7.

[0025] Figure 11 is a schematic flowchart of another possible implementation of the method shown in Figure 7.

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

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

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

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

[0030] Communication system

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] 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.

[0038] 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.

[0039] 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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.

[0048] Network system architecture

[0049] 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.

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

[0051] 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.

[0052] 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.

[0053] 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.

[0054] 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.

[0055] 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.

[0056] 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.

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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.

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

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

[0067] 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;

[0068] 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;

[0069] 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;

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

[0071] 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.

[0072] 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.

[0073] 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.

[0074] 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.

[0075] 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.

[0076] 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.

[0077] 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.

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

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

[0080] 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.

[0081] 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.

[0082] 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.

[0083] 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.

[0084] 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 and 6.

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

[0086] 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.

[0087] 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.

[0088] 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.

[0089] 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.

[0090] 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.

[0091] 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).

[0092] 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 UE to use a TLS-based user plane for location.

[0093] 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).

[0094] 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.

[0095] 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.

[0096] 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.

[0097] 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.

[0098] 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.

[0099] 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.

[0100] 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.

[0101] 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.

[0102] 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.

[0103] 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.

[0104] 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.

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

[0106] 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.

[0107] 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.

[0108] 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.

[0109] 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.

[0110] 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.

[0111] 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.

[0112] 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.

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

[0114] 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.

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

[0116] 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.

[0117] The reference architecture and schematic flow of the sensing and positioning systems have been introduced above with reference to Figures 2 to 6. Under the relevant 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, how to manage the first connection is a problem that urgently needs to be solved. The relevant 5G positioning architecture already supports the establishment and management of the first connection, and can provide a solution reference for the sensing architecture. In other words, for both current positioning services and future sensing services, there will be data transmission services. When multiple user plane protocol (UPP) connections coexist, the terminal device needs to determine the mapping relationship between each service and the first connection. For example, when multiple LCS-UPP connections coexist, the terminal device needs to be able to determine the mapping relationship between each service and the LCS-UPP connection.

[0118] However, the related designs fail to provide sufficient mechanisms to ensure that terminal devices correctly select the appropriate UPP connection for data transmission. As an example, this involves situations where multiple user plane connections are not supported. For instance, in location services, terminal devices typically assume only one LCS-UPP connection, and all user plane services are transmitted over that connection. As another example, terminal devices are unaware of the location / awareness services corresponding to user plane connections; that is, the terminal device does not maintain the mapping between connections and services.

[0119] Therefore, when multiple LCS-UPP connections exist, the terminal device cannot effectively select the correct connection to make a location / sensing request, which may lead to data routing errors and affect the accuracy of the location service.

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

[0121] First, the embodiments of this application involve concepts such as first connection, second connection, first information, and first data. For ease of understanding, the meanings of these concepts will be explained with examples.

[0122] The first 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 can be a user plane connection, or other connections with similar functions introduced in future communication systems.

[0123] The 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 control signaling of the terminal device. The first connection and the second connection can be two different types of connections. The second connection can be a control plane connection, or it can be other connections with similar functions introduced in future communication systems.

[0124] The first data mentioned in the various embodiments of this application can be business data. For example, the first data can be user plane data.

[0125] The first information mentioned in the various embodiments of this application can be information used to establish a first connection. For example, the first information can be called user plane information.

[0126] Based on the above concepts, this application proposes a communication method. In this method, after a terminal device establishes a first connection (such as a user plane connection) with a core network element, it can transmit first data (such as user plane data) over the first connection, and the first data includes a first identifier that identifies the first connection. Therefore, when multiple first connections exist, the terminal device can select a suitable first connection for different services based on the identifier of the first connection, thereby improving the service quality of these services.

[0127] It should be noted that the user plane data transmission problem mentioned above for 5G positioning and sensing services is only an example. The embodiments of this application can be applied to any type of data transmission scenario with multiple user plane connections.

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

[0129] 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.

[0130] The embodiments of this application will now be described in detail with reference to Figure 7. Figure 7 is a flowchart illustrating the communication method provided in the embodiments of this application. The method includes steps S710 and S720. Figure 7 is described from the perspective of the interaction between the terminal device and the first core network element.

[0131] 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 first connection with core network elements, or support establishing a first connection with core network elements.

[0132] The first core network element is any core network element that can establish a first connection with the terminal device. The first core network element can be determined based on the services that the terminal device needs to process. That is, the first core network element can be determined based on the service type. For example, for positioning services, the first core network element can be an LMF (Local Messaging Function) or a network element with similar functions. Similarly, for sensing services, the first core network element can be a sensing function network element or a network element with similar functions. A sensing function network element can be represented by SF (Sensing Function), or other names. Furthermore, for data processing services, the first core network element can be a data collection network element, a data management network element, or other data processing network elements.

[0133] As one implementation approach, the first core network element is either a network element used for positioning and management or a network element used for sensing within the core network.

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

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

[0136] As one implementation approach, for the process prior to establishing the first connection, the interaction objects are the control plane portion of the first core network element and the terminal device. For the process after establishing the first connection, the interaction objects are the user plane portion of the first core network element and the terminal device.

[0137] The first core network element can connect to other core network elements or other network entities. In some implementations, the first core network element can connect to the second core network element. The second core network element is a network element in the core network used for access and mobility management. The second core network element can be determined according to the communication system. For example, for a 5G system, the second core network element can be an AMF (Advanced Feature Function) or a network element with similar functions. Similarly, for a future 6G system, the second core network element can be represented by 6G MM (Multi-Mode Network) or other names.

[0138] As an implementation method, for the positioning service of the 5G system, the first core network element is LMF and the second core network element is AMF.

[0139] As an implementation method, for the sensing services of the 5G system, the first core network element is SF and the second core network element is AMF.

[0140] As an implementation approach, for positioning services in a 6G system, the first core network element is LMF, and the second core network element is 6GMM.

[0141] As an implementation method, for the sensing services of the 6G system, the first core network element is SF and the second core network element is 6GMM.

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

[0143] Referring to Figure 7, in step S710, the terminal device establishes a first connection with the first core network element.

[0144] The first connection established between the terminal device and the first core network element can be used for data transmission. In some implementations, this first connection can be used to transmit location service data or sensing service data. In other implementations, this first connection can be used to transmit data that needs to be collected or data that needs to be managed.

[0145] The first connection established between the terminal device and the first core network element can be used for data transmission between the terminal device and the first core network element. For example, the terminal device can receive data sent by the first core network element through the first connection, and it can also send data to the first core network element through the first connection. Similarly, the first core network element can receive data sent by the terminal device through the first connection, and it can also send data to the terminal device through the first connection.

[0146] In some implementations, the first connection can be established based on a triggering action by the terminal device. That is, the terminal device initiates the establishment process for the first connection. Once the terminal device decides to establish the first connection, it can send a request to the core network to establish the first connection. For example, the terminal device can request to establish the first connection by sending user plane initialization information. Alternatively, before establishing the first connection, the terminal device can send a third message to the core network via a second connection. The third message may include user plane initialization information and other information related to the first connection to request its establishment.

[0147] As one implementation, after the terminal device decides to establish the first connection, it can send user plane initialization (UP) information to the access network device, thereby sending a first connection establishment request to the core network through the access network device. For example, this user plane initialization information may include a first connection establishment request. Alternatively, the user plane initialization information may indicate a request to establish the first connection.

[0148] As one implementation, after the terminal device decides to establish the first connection, the third message sent by the terminal device may also carry the first connection identifier (connection ID) assigned by the terminal device, i.e., the first identifier, which will be explained later in conjunction with step S720. The third message may include user plane initialization information and the first identifier, or the third message may be user plane initialization information including the first identifier.

[0149] In some implementations, after receiving a first connection establishment request from a terminal device, the core network can select a first core network element to establish a first connection with the terminal device. The network element in the core network that receives the first connection establishment request from the terminal device is designated as a second core network element. The second core network element can select other core network elements based on the terminal device's first connection establishment request. For example, the second core network element can select a first core network element to establish a first connection with the terminal device based on the terminal device's service requirements.

[0150] In some implementations, the first connection can be established based on a triggering action by a first core network element. That is, the first core network element triggers the establishment process of the first connection. As one implementation, the first core network element can decide whether to use user plane transmission. User plane transmission can be understood as data transmission through the first connection. Once the first core network element decides to use user plane transmission, it can initiate the establishment process of the first connection. For example, the first core network element can determine whether to transmit data through the first connection based on factors such as the capabilities of the terminal device and the state of the control plane. After determining to establish a first connection with the terminal device, the first core network element can initiate the relevant procedures for establishing the first connection with the terminal device.

[0151] As one implementation, after the first core network element decides to transmit data through the first connection, it can send the first information of the first core network element to the second core network element, so that the second core network element can forward the first information to the terminal device. The first information of the first core network element can be used to establish the first connection between the first core network element and the terminal device. The first information of the first core network element may include the address information, FQDN, and IP address of the first core network element.

[0152] As one implementation, after the first core network element decides to transmit data through the first connection, it can send binding information related to the first connection to the second core network element, so that the second core network element can forward the binding information to the terminal device. The binding information may include temporarily assigned identification information, i.e., a binding ID. This binding ID can correspond to the identifier of the terminal device for binding the first connection. In this embodiment, the binding ID in the binding information is the second identifier.

[0153] As one implementation, when the first core network element decides to transmit data through the first connection, it can send a first identifier allocated by the first core network element to the second core network element, so that the second core network element can forward the first identifier to the terminal device. The first identifier allocated by the first core network element can also be used for first connection binding, replacing binding information. That is, when the first core network element sends its allocated first identifier, it may not need to send binding information related to the first connection.

[0154] In the above implementation, the message sent by the first core network element to the second core network element and the message forwarded by the second core network element to the terminal device can be the same or different. For example, both the message sent by the first core network element to the second core network element and the message sent by the second core network element are second messages. Alternatively, the first core network element sends a seventh message to the second core network element, and the second core network element sends a second message to the terminal device. Both the seventh and second messages can include the first information and binding information of the first core network element. As another example, both the message sent by the first core network element to the second core network element and the message sent by the second core network element are fourth messages. Alternatively, the first core network element can send an eighth message to the second core network element, and the second core network element sends a fourth message to the terminal device. Both the eighth and fourth messages can include the first information of the first core network element and the first identifier assigned by the terminal device. As another example, both the message sent by the first core network element to the second core network element and the message sent by the second core network element are fifth messages. Alternatively, the first core network element can send a ninth message to the second core network element, and the second core network element sends a fifth message to the terminal device. Both the ninth message and the fifth message may include the first information of the first core network element and the first identifier assigned to the first core network element.

[0155] In some implementations, the first core network element can participate in the establishment process of the first connection based on messages from the second core network element. After receiving user plane initialization information or a third message from the terminal device, the second core network element can send a first connection establishment request to the first core network element. For example, the first core network element can receive a first request from the second core network element through the second connection. The first request is used to request the establishment of the first connection. The second core network element can select the first core network element based on the terminal device's request and send the first request. The first request may include the identifier of the terminal device, also known as a user plane configuration request.

[0156] As one implementation, when the third message sent by the terminal device to the core network contains the first identifier, the first request received by the first core network element may also include the first identifier assigned by the terminal device. For example, before establishing the first connection, the first core network element receives a first request sent by the second core network element through the second connection. The first request is used to request the establishment of the first connection, and the first request carries the identifier of the terminal device and the first identifier assigned by the terminal device.

[0157] For a terminal device, before establishing the first connection, it can receive different information from the core network depending on the different ways the first connection is triggered. For example, the terminal device can receive at least two of the first information, binding information, and first identifier from the first core network element through the second connection. The first identifier can be assigned by the first core network element or by the terminal device.

[0158] As one implementation, when a terminal device triggers the establishment of a first connection, it can receive first information, binding information, and / or a first identifier through a second connection. This first identifier serves as the first connection identifier. For example, before establishing the first connection, the terminal device can receive a second message sent by a first core network element through the second connection. The second message contains a second identifier and first information from the first core network element, which is used to establish the first connection. As another example, before establishing the first connection, the terminal device can receive a fourth message sent by a first core network element through the second connection. This fourth message contains a first identifier assigned by the terminal device and first information from the first core network element, which is also used to establish the first connection.

[0159] As one implementation, when the first core network element triggers the establishment of the first connection, the terminal device can receive first information, binding information, and / or the first identifier through the second connection. For example, before establishing the first connection, the terminal device can receive a fifth message sent by the first core network element through the second connection. The fifth message contains the first identifier assigned by the first core network element and the first information of the first core network element, which is used to establish the first connection.

[0160] In some implementations, the terminal device and the first core network element can establish the first connection based on messages transmitted before establishing the first connection. For example, the terminal device can establish a first connection with the first core network element based on received first information.

[0161] As one implementation method, the terminal device can establish a first connection with the first core network element based on the received second message.

[0162] As another implementation, the terminal device can establish a first connection with the first core network element based on the received fourth message.

[0163] As another implementation, the terminal device can establish a first connection with the first core network element based on the received fifth message.

[0164] Referring again to Figure 7, in step S720, the terminal device receives first data through the first connection. The first core network element sends the first data to the terminal device through the first connection.

[0165] The first data includes a first identifier, which is used to identify the first connection. As can be seen from step S710, the first identifier belongs to the first connection identifier. Therefore, the first identifier is the identifier corresponding to the first connection currently established between the terminal device and the first core network element.

[0166] The first connection currently established between the terminal device and the first core network element can be one of multiple first connections. In some implementations, the terminal device can establish multiple first connections with the first core network element. These multiple first connections can correspond one-to-one with multiple identifiers, and the multiple identifiers include the first identifier. In other implementations, the terminal device can establish multiple first connections with multiple core network elements. These multiple first connections can also correspond one-to-one with multiple identifiers, and the multiple identifiers include the first identifier.

[0167] In some implementations, after the first connection is established, it can be used for data transmission. Therefore, the terminal device can also send third data to the first core network element through the first connection, and the third data contains the first identifier.

[0168] In some implementations, the first identifier can be associated with the service of data transmitted through the client plane connection. The first identifier can be used to indicate whether the data transmitted through the first connection currently established between the terminal device and the first core network element is location service data or sensing service data.

[0169] In some implementations, the first identifier can be assigned by the terminal device. As one implementation, the terminal device can assign the first identifier before establishing the first connection. As another implementation, the terminal device can assign the first identifier after establishing the first connection.

[0170] If the terminal device assigns a first identifier before establishing the first connection, the terminal device can send the first identifier to the core network via a third message. For example, before establishing the first connection, the terminal device sends a third message to the core network via a second connection. The third message is used to request the establishment of the first connection, and the third message carries the first identifier.

[0171] As one implementation, when the first identifier is allocated before the first connection is established, it can also be used for first connection binding. When the first identifier is allocated through the terminal device and sent directly to the first core network element through the second connection, the first core network element can directly use the first identifier for binding, saving the allocation and use of binding information. As an example, the first core network element can refer to the relevant binding process and directly send the first identifier as binding information to the terminal device. For example, the first core network element can refer to the first connection establishment process in Figure 5 (e.g., steps S502 to S504) or Figure 6 (steps S603 to S606) to send the first identifier and first information together to the terminal device to establish a secure first connection.

[0172] If the terminal device assigns a first identifier after establishing the first connection, the terminal device can assign a connection identifier based on the first connection established between the terminal device and the first core network element. As one implementation, after establishing the first connection, the terminal device assigns a first identifier to the current first connection established between the terminal device and the first core network element.

[0173] If the terminal device assigns a first identifier after establishing the first connection, the terminal device can send the first identifier to the first core network element through the first connection. The first identifier can be carried in the first message.

[0174] As one implementation, the first message may include binding information and a first identifier related to the first connection. For example, after establishing the first connection, the terminal device sends a first message to the first core network element through the first connection. The first message contains a first identifier and a second identifier, with the second identifier corresponding to the identifier of the terminal device. When the first identifier is allocated through the terminal device and sent to the first core network element along with the binding information through the first connection, the allocation and binding of the first connection identifier can be achieved. When managing multiple first connections, the existing binding information usage mechanism can be reused with minimal modifications.

[0175] In the above implementation, after the first core network element receives the first message through the first connection, the first core network element can determine the first identifier corresponding to the current first connection. The first core network element will maintain the mapping relationship between the first identifier and the current first connection.

[0176] In some implementations, the first identifier can be assigned by the first core network element. When the first core network element decides to transmit data through the first connection, it can assign a first identifier to the first connection before establishing it. Therefore, when the first core network element assigns the first identifier, it can use the assigned connection identifier instead of binding information. This method is suitable for scenarios where the first core network element triggers the establishment of the first connection, saving on the allocation and use of binding information.

[0177] After the first core network element assigns the first identifier, it can send the first identifier to the terminal device through the second connection. As one implementation, before establishing the first connection, the terminal device receives a fifth message sent by the first core network element through the second connection. The fifth message contains the first identifier assigned by the first core network element and the first information of the first core network element.

[0178] If the connection identifier is assigned by the first core network element, it may not meet the needs of the terminal device, or identifier conflicts may occur. For example, different first core network elements may assign the same connection identifier. In this scenario, the terminal device can reassign the connection identifier and send it to the first core network element through the first connection after establishing the first connection.

[0179] As one implementation, after establishing the first connection, the terminal device sends a sixth message to the first core network element through the first connection. The sixth message may contain a first identifier assigned by the first core network element and a third identifier reassigned by the terminal device. Therefore, the third identifier is an update identifier of the first identifier. The third identifier becomes the new connection ID for the current first connection.

[0180] As one implementation, when the first identifier is updated to the third identifier, the data transmitted by the first core network element and the terminal device through the first connection includes the third identifier, so as to facilitate the identification and differentiation of the first connection.

[0181] As one implementation, after the first core network element receives the sixth message, it can send data containing the third identifier via the first connection. For example, a terminal device can receive second data sent by the first core network element via the first connection, where the second data contains the third identifier.

[0182] As one implementation, after the terminal device sends the sixth message, it can send data containing the third identifier through the first connection. For example, the terminal device can send fourth data, which contains the third identifier, to the first core network element through the first connection.

[0183] In the above implementation, when the first core network element receives the sixth message through the first connection, the first core network element can determine that the identifier of the current first connection is updated to the third identifier. The first core network element will maintain the mapping relationship between the third identifier and the first connection.

[0184] The above description, in conjunction with Figure 7, introduces a method for managing multiple first connections. As can be seen from the description of steps S710 and S720 above, in this embodiment, after the terminal device establishes a first connection with the first core network element, the data transmitted through the first connection includes the identifier of the first connection. Specifically, the communication method proposed in this embodiment involves the core network element or the terminal device assigning a first connection identifier and using this identifier for connection binding. This achieves synchronization between the terminal device and the core network element, as well as maintaining the mapping relationship between the first connection identifier and specific first connections. During subsequent data transmission, the terminal device and the core network element can identify the corresponding first connection through the first connection identifier carried with the data transmission. When multiple first connections exist, the first connection identifier can be used to distinguish between different first connections.

[0185] The following describes, with reference to several embodiments, taking the first connection as a user plane connection and the second connection as a control plane connection, various methods for allocating user plane connection identifiers (e.g., the first identifier).

[0186] Example 1

[0187] In Embodiment 1, the first core network element triggers the establishment of a user plane connection. After the user plane connection is established, the terminal device assigns a user plane connection identifier and reports the first identifier through the user plane connection. To establish a user plane connection, the first core network element may first issue a temporary binding identifier to the terminal device. After receiving the user plane connection establishment request, the terminal device assigns the identifier corresponding to the user plane connection and then reports it to the first core network element through the user plane connection.

[0188] The specific implementation process of Embodiment 1 will be described below with reference to Figure 8. In Figure 8, NF2 is the first core network element, and NF1 is the second core network element.

[0189] Referring to Figure 8, in step S802, NF2 decides to use user plane transport. NF2 triggers the user plane connection establishment process.

[0190] In step S804, NF2 sends a seventh message to NF1, which contains NF2's user plane information and binding information. User plane information includes, for example, address information, FQDN, and IP address. Binding information includes, for example, temporarily assigned identification information. The binding identifier in the binding information can correspond to the identifier of the terminal device for use in user plane binding.

[0191] In step S806, NF1 sends a second message to the terminal device, which contains the user plane information and binding information of NF2. As shown in Figure 8, NF1 can send the second message to the terminal device through the access network device (RAN).

[0192] In step S808, the terminal device establishes a user plane connection with NF2 based on the received user plane information.

[0193] In step S810, the terminal device allocates the identification information corresponding to the user plane connection, that is, allocates the first identifier.

[0194] In step S812, the terminal device sends a first message to NF2 via the user plane connection, which includes binding information and a first identifier assigned by the terminal device. After receiving the first message, NF2 maintains the mapping relationship between the terminal device's first identifier and the current user plane connection.

[0195] In step S814, the terminal device transmits data to NF2 via the user plane connection, or NF2 transmits data to the terminal device via the user plane connection. All data packets transmitted via this user plane connection contain a first identifier.

[0196] As shown in Figure 8, in Embodiment 1, a first identifier can be assigned to a user plane connection via a terminal device. This first identifier, along with binding information, can be sent to the first core network element via the user plane connection, thus realizing the allocation and binding of user plane connection identifiers. When the method of Embodiment 1 is used to manage multiple user plane connections, the existing binding information usage mechanism can be reused, requiring minimal modifications to the related design.

[0197] Example 2

[0198] Unlike Embodiment 1, in Embodiment 2, the user plane connection establishment process is triggered by the terminal device. The terminal device can send an establishment request to the core network and establish a user plane connection based on the user plane information received from the first core network element. Similar to Embodiment 1, the first core network element can first issue a temporary binding identifier to the terminal device. After the user plane connection is established, the terminal device allocates a first identifier corresponding to the user plane connection and then reports the first identifier to the first core network element through the user plane connection.

[0199] The specific implementation process of Embodiment 2 will be described below with reference to Figure 9. In Figure 9, NF2 is the first core network element, and NF1 is the second core network element.

[0200] Referring to Figure 9, in step S902, the terminal device decides to establish a user plane connection. The terminal device triggers the user plane connection establishment process.

[0201] In step S904, the terminal device sends a user plane connection trigger request to NF1. The terminal device may send user plane initialization information to NF1 to request the establishment of a user plane connection.

[0202] In step S906, NF1 selects NF2.

[0203] In step S908, NF1 sends a user plane configuration request to NF2, which includes the identification information of the terminal device.

[0204] In step S910, NF2 sends a seventh message to NF1, which contains NF2's user plane information and binding information. The user plane information and binding information are the same as in Embodiment 1, and will not be described again.

[0205] In step S912, NF1 sends a second message to the terminal device, which contains the user plane information and binding information of NF2.

[0206] In step S914, the terminal device establishes a user plane connection with NF2 based on the received user plane information.

[0207] In step S916, the terminal device allocates the identification information corresponding to the user plane connection, that is, allocates the first identifier.

[0208] In step S918, the terminal device sends a first message to NF2 via the user plane connection, which includes binding information and a first identifier assigned by the terminal device. Similar to Embodiment 1, NF2 also maintains the mapping relationship between the terminal device's first identifier and the current user plane connection.

[0209] In step S920, the terminal device transmits data to NF2 via the user plane connection, or NF2 transmits data to the terminal device via the user plane connection. All data packets transmitted via this user plane connection contain a first identifier.

[0210] As shown in Figure 9, in Embodiment 2, a first identifier can be assigned to a user plane connection via a terminal device, and the first identifier, along with binding information, is sent to the first core network element through the user plane connection, thereby realizing the allocation and binding of the user plane connection identifier. Similarly, when the method in Embodiment 2 is used for the management of multiple user plane connections, the existing binding information usage mechanism can be reused, requiring minimal modifications to the related design.

[0211] Example 3

[0212] Similar to Embodiment 2, the user plane connection establishment process in Embodiment 3 is also triggered by the terminal device. However, unlike Embodiment 2, the terminal device directly reports the assigned user plane connection identifier via the control plane connection. Specifically, the terminal device can assign a first identifier corresponding to the user plane connection before the user plane connection is established and report it before the connection is established. The first core network element can use the first identifier reported by the terminal device to bind the user plane connection.

[0213] The specific implementation process of Embodiment 3 will be described below with reference to Figure 10. In Figure 10, NF2 is the first core network element and NF1 is the second core network element.

[0214] Referring to Figure 10, in step S1002, the terminal device decides to establish a user plane connection. The terminal device triggers the user plane connection establishment process.

[0215] In step S1004, the terminal device sends a third message, namely a user plane trigger request, to NF1. The third message sent by the terminal device may include user plane initialization information and a first identifier assigned by the terminal device.

[0216] In step S1006, NF1 selects NF2.

[0217] In step S1008, NF1 sends a first request, namely a user plane configuration request, to NF2. The first request may include the identifier of the terminal device and a first identifier assigned to the terminal device. NF1 can send the first request through the control plane connection.

[0218] In step S1010, NF2 sends an eighth message to NF1, which includes NF2's user plane information and the first identifier assigned by the terminal device. The user plane information is the same as in Embodiment 1 and will not be described again.

[0219] In step S1012, NF1 sends a fourth message to the UE, which contains user plane information of NF2 and a first identifier assigned by the terminal device.

[0220] In step S1014, the terminal device establishes a user plane connection with NF2 based on the received user plane information.

[0221] In step S1016, the terminal device transmits data to NF2 via a user plane connection, or NF2 transmits data to the terminal device via a user plane connection. All data packets transmitted via this user plane connection contain a first identifier. Optionally, NF2 can bind the user plane connection to the first identifier based on the data packets sent by the terminal device via this user plane connection. As an example, NF2 can bind the user plane connection to the first identifier based on the first data packet carrying the first identifier sent by the terminal device.

[0222] As shown in Figure 10, in Embodiment 3, the user plane connection identifier is allocated by the terminal device and directly sent to the first core network element via the control plane connection. Therefore, the first core network element can directly use the connection identifier allocated by the terminal device for binding, saving on the allocation and use of binding information.

[0223] Example 4

[0224] Similar to Embodiment 1, the user plane connection establishment process is triggered by the first core network element. Unlike Embodiment 1, the first core network element assigns a user plane connection identifier and uses this identifier to bind the user plane connection. In certain scenarios, the terminal device can also update the connection identifier assigned by the first core network element and report the updated identifier through the user plane connection.

[0225] The specific implementation process of Embodiment 4 will be described below with reference to Figure 11. In Figure 11, NF2 is the first core network element and NF1 is the second core network element.

[0226] Referring to Figure 11, in step S1102, NF2 decides to use user plane transport. NF2 triggers the user plane connection establishment process.

[0227] In step S1104, NF2 sends a ninth message to NF1, which contains NF2's user plane information and the first identifier assigned by NF2. The user plane information is the same as in Embodiment 1 and will not be described again.

[0228] In step S1106, NF1 sends a fifth message to the terminal device, which includes NF2 user plane information and the first identifier assigned by NF2.

[0229] In step S1108, the terminal device establishes a user plane connection with NF2 based on the received user plane information.

[0230] In step S1110, the terminal device reassigns the identification information of the user plane connection, that is, assigns a third identifier. This step is optional.

[0231] In step S1112, the terminal device sends a sixth message to NF2 via the user plane connection, which includes the first identifier assigned by NF2. Optionally, if the terminal device reassigns the identifier corresponding to the user plane connection, the sixth message may also include the third identifier reassigned by the terminal device. After receiving the sixth message, NF2 maintains the mapping relationship between the third identifier assigned by the terminal device and the current user plane connection.

[0232] In step S1114, if the terminal device does not reassign identification information, the terminal device transmits data to NF2 via the user plane, or NF2 transmits data to the terminal device via the user plane. All data packets transmitted through this user plane connection contain the first identifier.

[0233] In step S1116, if the terminal device reassigns identification information, the terminal device transmits data to NF2 via the user plane, or NF2 transmits data to the terminal device via the user plane. All data packets transmitted through this user plane connection contain the reassigned third identifier.

[0234] As shown in Figure 11, Embodiment 4 uses user plane connection identifiers allocated by the first core network element to replace binding information. This allows terminal devices to reassign connection identifiers based on needs and identifier conflicts (e.g., different first core network elements have allocated the same connection identifier). The terminal device can also update the reassigned connection identifier to the first core network element via the user plane connection. The method in Embodiment 4 is applicable to scenarios where NF2 triggers connection establishment and also saves on the allocation and use of binding information.

[0235] The method embodiments of this application have been described in detail above with reference to Figures 1 to 11. The apparatus embodiments of this application will be described in detail below with reference to Figures 12 to 14. 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.

[0236] Figure 12 is a schematic diagram of a communication device provided in an embodiment of this application. The communication device 1200 shown in Figure 12 is any of the terminal devices described above. As shown in Figure 12, the communication device 1200 includes a first processing unit 1210 and a first receiving unit 1220.

[0237] The first processing unit 1210 can be used to establish a first connection with the first core network element.

[0238] The first receiving unit 1220 can be used to receive first data through the first connection. The first data includes a first identifier, which is used to identify the first connection.

[0239] In some implementations, the first identifier is assigned by the terminal device.

[0240] In some implementations, the communication device 1200 further includes a first sending unit, which can be used to send a first message to the first core network element through the first connection after the first connection is established. The first message includes a first identifier and a second identifier, and the second identifier corresponds to the identifier of the terminal device.

[0241] In some implementations, the communication device 1200 further includes a second receiving unit, which can be used to receive a second message sent by the first core network element through the second connection before establishing the first connection. The second message includes the second identifier and the first information of the first core network element, and the first information is used to establish the first connection.

[0242] In some implementations, the communication device 1200 further includes a second processing unit, which can be used to assign the first identifier to the first connection after the first connection is established.

[0243] In some implementations, the communication device 1200 further includes a second sending unit, which can be used to send a third message to the core network through the second connection before establishing the first connection. The third message is used to request the establishment of the first connection and carries the first identifier.

[0244] In some implementations, the communication device 1200 further includes a third receiving unit, which can be used to receive a fourth message sent by the first core network element through the second connection. The fourth message includes the first identifier and the first information of the first core network element, and the first information is used to establish the first connection.

[0245] In some implementations, the first identifier is assigned by the first core network element.

[0246] In some implementations, the communication device 1200 further includes a fourth receiving unit, which can be used to receive a fifth message sent by the first core network element through a second connection before establishing the first connection. The fifth message contains the first identifier and first information of the first core network element, and the first information is used to establish the first connection.

[0247] In some implementations, the communication device 1200 further includes a third sending unit, which can be used to send a sixth message to the first core network element through the first connection after the first connection is established. The sixth message includes the first identifier and a third identifier, wherein the third identifier is an update identifier of the first identifier.

[0248] In some implementations, the communication device 1200 further includes a fifth receiving unit, which can be used to receive second data sent by the first core network element through the first connection, the second data including the third identifier.

[0249] In some implementations, the first core network element is a network element in the core network used for positioning and management or for sensing.

[0250] In some implementations, the first connection is used to transmit location service data or sensing service data.

[0251] Figure 13 is a schematic diagram of another communication device provided in an embodiment of this application. The communication device 1300 shown in Figure 13 is any of the first core network elements described above. As shown in Figure 13, the communication device 1300 includes a processing unit 1310 and a first transmitting unit 1320.

[0252] The processing unit 1310 can be used to establish a first connection with a terminal device.

[0253] The first sending unit 1320 can be used to send first data to the terminal device through the first connection. The first data includes a first identifier, which is used to identify the first connection.

[0254] In some implementations, the first identifier is assigned by the terminal device.

[0255] In some implementations, the communication device 1300 further includes a first receiving unit, which can be used to receive a first message sent by the terminal device through the first connection after the first connection is established. The first message includes a first identifier and a second identifier, and the second identifier corresponds to the identifier of the terminal device.

[0256] In some implementations, the communication device 1300 further includes a second sending unit, which can be used to send a second message to the terminal device through the second connection before establishing the first connection. The second message includes the second identifier and first information of the first core network element, and the first information is used to establish the first connection.

[0257] In some implementations, the communication device 1300 further includes a second receiving unit, which can be used to receive a first request sent by a second core network element through the second connection before establishing the first connection. The first request is used to request the establishment of the first connection, and the first request carries the identifier of the terminal device and the first identifier.

[0258] In some implementations, the communication device 1300 further includes a third sending unit, which can be used to send a fourth message to the terminal device through the second connection. The fourth message includes the first identifier and the first information of the first core network element, and the first information is used to establish the first connection.

[0259] In some implementations, the first identifier is assigned by the first core network element.

[0260] In some implementations, the communication device 1300 further includes a fourth sending unit, which can be used to send a fifth message to the terminal device through a second connection before establishing the first connection. The fifth message contains the first identifier and first information of the first core network element, and the first information is used to establish the first connection.

[0261] In some implementations, the communication device 1300 further includes a third receiving unit, which can be used to receive a sixth message sent by the terminal device through the first connection after the first connection is established. The sixth message includes the first identifier and a third identifier, wherein the third identifier is an update identifier of the first identifier.

[0262] In some implementations, the communication device 1300 further includes a fifth transmitting unit, which can be used to transmit second data to the terminal device through the first connection, the second data including the third identifier.

[0263] In some implementations, the first core network element is a network element in the core network used for positioning and management or for sensing.

[0264] In some implementations, the first connection is used to transmit location service data or sensing service data.

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

[0266] Apparatus 1400 may include one or more processors 1410. The processor 1410 may support apparatus 1400 in implementing the methods described in the preceding method embodiments. The processor 1410 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.

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

[0268] The device 1400 may also include a transceiver 1430. The processor 1410 can communicate with other devices or chips via the transceiver 1430. For example, the processor 1410 can send and receive data with other devices or chips via the transceiver 1430.

[0269] 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.

[0270] 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.

[0271] 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.

[0272] 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.

[0273] 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.

[0274] 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.

[0275] 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.

[0276] 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.

[0277] 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.

[0278] 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.

[0279] 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.

[0280] 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.

[0281] 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.

[0282] 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.

[0283] 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.

[0284] 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: The terminal device establishes a first connection with the first core network element; The terminal device receives first data through the first connection. The first data includes a first identifier, which is used to identify the first connection.

2. The method according to claim 1, characterized in that, The first identifier is assigned by the terminal device.

3. The method according to claim 2, characterized in that, The method further includes: After establishing the first connection, the terminal device sends a first message to the first core network element through the first connection. The first message includes the first identifier and the second identifier, and the second identifier corresponds to the identifier of the terminal device.

4. The method according to claim 3, characterized in that, The method further includes: Before establishing the first connection, the terminal device receives a second message sent by the first core network element through the second connection. The second message contains the second identifier and the first information of the first core network element. The first information is used to establish the first connection.

5. The method according to any one of claims 2 to 4, characterized in that, The method further includes: After the first connection is established, the terminal device assigns the first identifier to the first connection.

6. The method according to claim 2, characterized in that, The method further includes: Before establishing the first connection, the terminal device sends a third message to the core network through the second connection. The third message is used to request the establishment of the first connection and carries the first identifier.

7. The method according to claim 6, characterized in that, The method further includes: The terminal device receives a fourth message sent by the first core network element through a second connection. The fourth message includes the first identifier and the first information of the first core network element, and the first information is used to establish the first connection.

8. The method according to claim 1, characterized in that, The first identifier is assigned by the first core network element.

9. The method according to claim 8, characterized in that, The method further includes: Before establishing the first connection, the terminal device receives a fifth message sent by the first core network element through the second connection. The fifth message contains the first identifier and the first information of the first core network element, and the first information is used to establish the first connection.

10. The method according to claim 8 or 9, characterized in that, The method further includes: After establishing the first connection, the terminal device sends a sixth message to the first core network element through the first connection. The sixth message includes the first identifier and a third identifier, and the third identifier is an update identifier of the first identifier.

11. The method according to claim 10, characterized in that, The method further includes: The terminal device receives second data sent by the first core network element through the first connection, and the second data includes the third identifier.

12. The method according to any one of claims 1 to 11, characterized in that, The first core network element is a network element in the core network used for positioning and management or for sensing.

13. The method according to any one of claims 1 to 12, characterized in that, The first connection is used to transmit positioning service data or sensing service data.

14. A communication method, characterized in that, include: The first core network element establishes the first connection with the terminal equipment; The first core network element sends first data to the terminal device through the first connection. The first data includes a first identifier, which is used to identify the first connection.

15. The method according to claim 14, characterized in that, The first identifier is assigned by the terminal device.

16. The method according to claim 15, characterized in that, The method further includes: After the first connection is established, the first core network element receives a first message sent by the terminal device through the first connection. The first message includes a first identifier and a second identifier, and the second identifier corresponds to the identifier of the terminal device.

17. The method according to claim 16, characterized in that, The method further includes: Before establishing the first connection, the first core network element sends a second message to the terminal device through the second connection. The second message contains the second identifier and the first information of the first core network element. The first information is used to establish the first connection.

18. The method according to claim 15, characterized in that, The method further includes: Before establishing the first connection, the first core network element receives a first request sent by the second core network element through the second connection. The first request is used to request the establishment of the first connection, and the first request carries the identifier of the terminal device and the first identifier.

19. The method according to claim 18, characterized in that, The method further includes: The first core network element sends a fourth message to the terminal device through a second connection. The fourth message contains the first identifier and the first information of the first core network element. The first information is used to establish the first connection.

20. The method according to claim 14, characterized in that, The first identifier is assigned by the first core network element.

21. The method according to claim 20, characterized in that, The method further includes: Before establishing the first connection, the first core network element sends a fifth message to the terminal device through the second connection. The fifth message contains the first identifier and the first information of the first core network element, and the first information is used to establish the first connection.

22. The method according to claim 20 or 21, characterized in that, The method further includes: After the first connection is established, the first core network element receives a sixth message sent by the terminal device through the first connection. The sixth message includes the first identifier and a third identifier, and the third identifier is an update identifier of the first identifier.

23. The method according to claim 22, characterized in that, The method further includes: The first core network element sends second data to the terminal device through the first connection, and the second data includes the third identifier.

24. The method according to any one of claims 14 to 23, characterized in that, The first core network element is a network element in the core network used for positioning and management or for sensing.

25. The method according to any one of claims 14 to 24, characterized in that, The first connection is used to transmit positioning service data or sensing service data.

26. A communication device, characterized in that, The communication device is a terminal device, and the communication device includes: The first processing unit is used to establish a first connection with the first core network element; A first receiving unit is configured to receive first data through the first connection, the first data including a first identifier, the first identifier being used to identify the first connection.

27. The communication device according to claim 26, characterized in that, The first identifier is assigned by the terminal device.

28. The communication device according to claim 27, characterized in that, The communication device also includes: The first sending unit is configured to send a first message to the first core network element through the first connection after the first connection is established. The first message includes the first identifier and the second identifier, and the second identifier corresponds to the identifier of the terminal device.

29. The communication device according to claim 28, characterized in that, The communication device also includes: The second receiving unit is configured to receive a second message sent by the first core network element through the second connection before establishing the first connection. The second message includes the second identifier and the first information of the first core network element, and the first information is used to establish the first connection.

30. The communication device according to any one of claims 27 to 29, characterized in that, The communication device also includes: The second processing unit is configured to assign the first identifier to the first connection after the first connection is established.

31. The communication device according to claim 27, characterized in that, The communication device also includes: The second sending unit is configured to send a third message to the core network through the second connection before establishing the first connection. The third message is used to request the establishment of the first connection and carries the first identifier.

32. The communication device according to claim 31, characterized in that, The communication device also includes: The third receiving unit is configured to receive a fourth message sent by the first core network element through the second connection. The fourth message includes the first identifier and the first information of the first core network element, and the first information is used to establish the first connection.

33. The communication device according to claim 26, characterized in that, The first identifier is assigned by the first core network element.

34. The communication device according to claim 33, characterized in that, The communication device also includes: The fourth receiving unit is configured to receive a fifth message sent by the first core network element through the second connection before establishing the first connection. The fifth message includes the first identifier and the first information of the first core network element, and the first information is used to establish the first connection.

35. The communication device according to claim 33 or 34, characterized in that, The communication device also includes: The third sending unit is configured to send a sixth message to the first core network element through the first connection after the first connection is established. The sixth message includes the first identifier and a third identifier, wherein the third identifier is an update identifier of the first identifier.

36. The communication device according to claim 35, characterized in that, The communication device also includes: The fifth receiving unit is configured to receive second data sent by the first core network element through the first connection, wherein the second data includes the third identifier.

37. The communication device according to any one of claims 26 to 36, characterized in that, The first core network element is a network element in the core network used for positioning and management or for sensing.

38. The communication device according to any one of claims 26 to 37, characterized in that, The first connection is used to transmit positioning service data or sensing service data.

39. A communication device, characterized in that, The communication device is a first core network element, and the communication device includes: A processing unit, used to establish a first connection with the terminal device; A first sending unit is configured to send first data to the terminal device through the first connection, the first data including a first identifier, the first identifier being used to identify the first connection.

40. The communication device according to claim 39, characterized in that, The first identifier is assigned by the terminal device.

41. The communication device according to claim 40, characterized in that, The communication device also includes: The first receiving unit is configured to receive a first message sent by the terminal device through the first connection after the first connection is established. The first message includes a first identifier and a second identifier, wherein the second identifier corresponds to the identifier of the terminal device.

42. The communication device according to claim 41, characterized in that, The communication device also includes: The second sending unit is configured to send a second message to the terminal device via the second connection before establishing the first connection. The second message includes the second identifier and the first information of the first core network element. The first information is used to establish the first connection.

43. The communication device according to claim 40, characterized in that, The communication device also includes: The second receiving unit is configured to receive a first request sent by a second core network element through the second connection before establishing the first connection. The first request is used to request the establishment of the first connection, and the first request carries the identifier of the terminal device and the first identifier.

44. The communication device according to claim 43, characterized in that, The communication device also includes: The third sending unit is used to send a fourth message to the terminal device through the second connection. The fourth message includes the first identifier and the first information of the first core network element. The first information is used to establish the first connection.

45. The communication device according to claim 39, characterized in that, The first identifier is assigned by the first core network element.

46. ​​The communication device according to claim 45, characterized in that, The communication device also includes: The fourth sending unit is configured to send a fifth message to the terminal device via the second connection before establishing the first connection. The fifth message contains the first identifier and the first information of the first core network element, and the first information is used to establish the first connection.

47. The communication device according to claim 45 or 46, characterized in that, The communication device also includes: The third receiving unit is configured to receive a sixth message sent by the terminal device through the first connection after the first connection is established. The sixth message includes the first identifier and a third identifier, wherein the third identifier is an update identifier of the first identifier.

48. The communication device according to claim 47, characterized in that, The communication device also includes: The fifth sending unit is used to send second data to the terminal device through the first connection, the second data including the third identifier.

49. The communication device according to any one of claims 39 to 48, characterized in that, The first core network element is a network element in the core network used for positioning and management or for sensing.

50. The communication device according to any one of claims 39 to 49, characterized in that, The first connection is used to transmit positioning service data or sensing service data.

51. 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 25.

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

53. 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 25.

54. 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 25.

55. 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 25.

56. 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 25.

Images