Positioning negotiation method and apparatus, and terminal device and core network device

Abstract

The present application relates to the field of communications. Provided are a positioning negotiation method and apparatus, and a terminal device and a core network device. The positioning negotiation method comprises: a terminal device sending to a first core network device a first message, which is used for performing network registration or establishing a user-plane positioning connection, the first message comprising one or more of the following: a first capability, a first designated protocol and first acknowledgment information, wherein the first capability is used for indicating a transmission protocol which is supported by the terminal device and is used for transmitting user-plane positioning information, the first designated protocol comprises a transmission protocol which is expected to be used by the terminal device and is used for transmitting the user-plane positioning information, the first acknowledgment information is used for indicating that the terminal device accepts or rejects the use of a second designated protocol to transmit the user-plane positioning information, and the second designated protocol comprises a transmission protocol which is designated by the first core network device or a second core network device and is used for transmitting the user-plane positioning information.

Description

Positioning negotiation method and device, terminal equipment and core network equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202310894606.3 filed in China on July 19, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application relates to the field of communications, and more specifically, to a positioning negotiation method and apparatus, a terminal device, and a core network device. Background Art

[0004] In New Radio (NR) systems, user-plane positioning is introduced alongside control-plane positioning. For example, large amounts of positioning information can be transmitted frequently via the user plane to reduce the control-plane load and improve the positioning experience. However, the specific transport protocol used to transmit user-plane positioning information remains an issue.

[0005] Summary of the Invention

[0006] The present application provides a positioning negotiation method and apparatus, a terminal device, and a core network device, which can solve the technical problem of being unable to determine which transmission protocol to use for transmitting user plane positioning information.

[0007] In a first aspect, a positioning negotiation method is provided, comprising:

[0008] The terminal device sends a first message to the first core network device, where the first message is used to perform network registration or establish a user plane positioning connection;

[0009] The first message includes one or more of the following: a first capability, a first designated protocol, and a first confirmation message;

[0010] Among them, the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting user plane positioning information, the first specified protocol includes the transmission protocol that the terminal device expects to use for transmitting user plane positioning information, the first confirmation information is used to indicate that the terminal device accepts or refuses to use the second specified protocol to transmit user plane positioning information, and the second specified protocol includes the transmission protocol specified by the first core network device or the second core network device for transmitting user plane positioning information.

[0011] In a second aspect, a positioning negotiation method is provided, including:

[0012] The first core network device sends a second message to the terminal device, where the second message is used to perform network registration or establish a user plane positioning connection;

[0013] The second message includes one or more of the following: a second capability, a second designated protocol, and a second cause value;

[0014] Among them, the second capability is used to indicate the transmission protocol supported by the network for transmitting user plane positioning information, the second specified protocol includes the transmission protocol for transmitting user plane positioning information specified by the first core network device or the second core network device, and the second reason value is used to indicate the reason why the network rejects the request initiated by the terminal device to establish a user plane positioning connection.

[0015] A third aspect provides a positioning negotiation method, including:

[0016] The second core network device sends a third message to the first core network device;

[0017] The third message is used to establish a user plane positioning connection, and the third message includes a second specified protocol, and the second specified protocol includes a transmission protocol specified by the second core network device for transmitting user plane positioning information.

[0018] In a fourth aspect, a positioning negotiation apparatus is provided, including:

[0019] A sending unit, configured to send a first message to a first core network device, where the first message is used to perform network registration or establish a user plane positioning connection;

[0020] The first message includes one or more of the following: a first capability, a first designated protocol, and a first confirmation message;

[0021] Among them, the first capability is used to indicate the transmission protocol supported by the positioning negotiation device for transmitting user plane positioning information, the first specified protocol includes the transmission protocol that the positioning negotiation device expects to use for transmitting user plane positioning information, and the first confirmation information is used to indicate that the positioning negotiation device accepts or refuses to use the second specified protocol to transmit user plane positioning information, and the second specified protocol includes the transmission protocol specified by the first core network device or the second core network device for transmitting user plane positioning information.

[0022] In a fifth aspect, a positioning negotiation apparatus is provided, including:

[0023] A sending unit, configured to send a second message to the terminal device, where the second message is used to perform network registration or establish a user plane positioning connection;

[0024] The second message includes one or more of the following: a second capability, a second designated protocol, and a second cause value;

[0025] Among them, the second capability is used to indicate the transmission protocol supported by the network for transmitting user plane positioning information, the second specified protocol includes the transmission protocol for transmitting user plane positioning information specified by the positioning negotiation device or the second core network device, and the second reason value is used to indicate the reason why the network rejects the request initiated by the terminal device to establish a user plane positioning connection.

[0026] In a sixth aspect, a positioning negotiation apparatus is provided, including:

[0027] A sending unit, configured to send a third message to the first core network device;

[0028] The third message is used to establish a user plane positioning connection, the third message includes a second designated protocol, and the positioning negotiation device includes a transmission protocol specified by the second core network device for transmitting user plane positioning information.

[0029] In the seventh aspect, a terminal device is provided, comprising a processor and a memory; wherein the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute the method in the above-mentioned first aspect or its various implementation methods.

[0030] In the eighth aspect, a core network device is provided, which is a first core network device, including a processor and a memory; wherein the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute the methods in the above-mentioned second aspect or its various implementation methods.

[0031] In the ninth aspect, a core network device is provided, which is a second core network device, including a processor and a memory; wherein the memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to execute the methods in the above-mentioned third aspect or its various implementation methods.

[0032] In a tenth aspect, an apparatus is provided for implementing the method described in any one of the first to third aspects or their respective implementations. Specifically, the apparatus includes a processor configured to retrieve and execute a computer program from a memory, causing a device equipped with the apparatus to perform the method described in any one of the first to third aspects or their respective implementations.

[0033] In an eleventh aspect, a chip is provided for implementing the method of any one of the first to third aspects or their respective implementations. Specifically, the chip includes a processor for loading and executing a computer program from a memory, causing a device equipped with the chip to perform the method of any one of the first to third aspects or their respective implementations.

[0034] In the twelfth aspect, a computer-readable storage medium is provided for storing a computer program, which enables a computer to execute the method in any one of the above-mentioned first to third aspects or their respective implementations.

[0035] Through the technical solution of the first aspect mentioned above, the terminal device can provide the network side with relevant information of the transmission protocol for transmitting user plane positioning information through the first message, so that the terminal side and the network side can negotiate to determine the transmission protocol for transmitting user plane positioning information and improve the transmission efficiency of user plane positioning information.

[0036] Through the technical solution of the second aspect mentioned above, the first core network device can provide the terminal device with relevant information of the transmission protocol for transmitting user plane positioning information through the second message, so that the terminal side and the network side can negotiate to determine the transmission protocol for transmitting user plane positioning information and improve the transmission efficiency of user plane positioning information.

[0037] Through the technical solution of the third aspect mentioned above, the second core network device can provide the first core network device and the terminal device with relevant information of the transmission protocol for transmitting user plane positioning information through the third message, so that the terminal side and the network side can negotiate and determine the transmission protocol for transmitting user plane positioning information, and improve the transmission efficiency of user plane positioning information. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0039] FIG1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.

[0040] FIG2 is a schematic diagram of a network-initiated user plane positioning connection establishment provided in the present application.

[0041] FIG3 is a schematic diagram of establishing a user plane positioning connection initiated by a terminal provided in the present application.

[0042] FIG4 is a schematic diagram of a SUPL protocol stack provided by the present application.

[0043] FIG5 is a schematic flowchart of a positioning negotiation method provided according to an embodiment of the present application.

[0044] FIG6 is a schematic flowchart of another positioning negotiation method provided according to an embodiment of the present application.

[0045] FIG7 is a schematic flowchart of another positioning negotiation method provided according to an embodiment of the present application.

[0046] 8 to 11 are schematic flow charts of positioning negotiation according to embodiments of the present application.

[0047] FIG12 is a schematic block diagram of a positioning negotiation apparatus according to an embodiment of the present application.

[0048] FIG13 is a schematic block diagram of another positioning negotiation apparatus provided according to an embodiment of the present application.

[0049] FIG14 is a schematic block diagram of another positioning negotiation apparatus provided according to an embodiment of the present application.

[0050] FIG15 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

[0051] FIG16 is a schematic block diagram of a device provided according to an embodiment of the present application.

[0052] Figure 17 is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0053] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. With respect to the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0054] The terms used in the embodiments of the present application are only used to explain the specific embodiments of the present application and are not intended to limit the present application. The terms "first", "second", "third" and "fourth" in the specification and claims of the present application and the accompanying drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices. In addition, the use of "and / or" in the specification and claims represents at least one of the connected objects, such as A and / or B and / or C, which means including 7 situations including single A, single B, single C, and both A and B exist, both B and C exist, both A and C exist, and both A, B and C exist.

[0055] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain it through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain it through C; it can also mean that there is an association between A and B.

[0056] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0057] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Internet of Things (IoT), Wireless Fidelity (WiFi), Fifth Generation Communication (5G) system, Sixth Generation Communication (6G) system or other evolved communication systems.

[0058] The communication system in the embodiments of the present application can be applied to licensed spectrum and / or unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum, and the licensed spectrum can also be considered as a non-shared spectrum.

[0059] For example, a communication system 100 used in an embodiment of the present application may be as shown in FIG1 . The communication system 100 may include a terminal device 110, an access network device 120, and a core network device 130. The terminal device 110 may be connected to the core network device 130 via the access network device 120. The access network device 120 may provide communication coverage for a specific geographic area and may communicate with terminal devices within the coverage area. Specifically, for example, the terminal device 110 may also be referred to as user equipment (UE), a terminal, or other similar names.

[0060] In some embodiments, the terminal device 110 can be a mobile phone, a tablet personal computer, a laptop computer, a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device, a flight vehicle, a vehicle user equipment (VUE), a shipborne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (PC), an ATM or a self-service machine, and other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, vehicle-mounted equipment can also be called vehicle-mounted terminals, vehicle-mounted controllers, vehicle-mounted modules, vehicle-mounted components, vehicle-mounted chips, or vehicle-mounted units.

[0061] In some embodiments, the access network device 120 may also be referred to as a radio access network (RAN) device, a radio access network function, or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AS), or a wireless fidelity (WiFi) node. Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0062] In some embodiments, the core network device 130 may include but is not limited to at least one of the following: a core network node, a core network function, a mobility management entity (MME), an access mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), a policy and charging rules function unit (PCRF), an edge application server discovery function (EASDF), a unified data management (UDM), a unified data repository (UDR), a home subscriber server (HSS), a centralized network configuration (CNC), a network storage function (NRF), a network exposure function (NEF), a local NEF (L-NEF), a binding support function (BSF), an application function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.But not limited to at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized Network Configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (BSF), Application Function (AF), Sensing Function ( It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0063] To facilitate a better understanding of the embodiments of the present application, the user plane positioning related to the present application is explained.

[0064] The NR system supports two methods of establishing user plane positioning connections: network-initiated LCS-UP initiation and terminal-initiated LCS-UP initiation. The user plane can be used to transmit a large amount of positioning-related data between the terminal equipment (UE) and the location management function (LMF) entity, or the user plane can be used between the UE and the LMF entity to transmit positioning-related data more frequently. It should be noted that which protocol stack is used to encapsulate and transmit user plane positioning messages has not been determined.

[0065] Specifically, the network-initiated LCS-UP initiation can be shown in Figure 2. The network-side LMF entity decides to use user plane positioning and informs the access and mobility management function (AMF) entity of the user plane positioning information. The AMF entity then interacts with the UE through non-access stratum (NAS) signaling. After receiving the UE's positive acknowledgment (ACK) message, the AMF entity replies to the LMF entity. The UE then establishes a user plane positioning connection with the LMF entity.

[0066] As shown in FIG2 , the user plane positioning connection establishment process initiated by the network may include at least one of the following steps:

[0067] Step 1: Based on the UE user plane positioning capability and other implementation factors, the LMF entity decides whether to continue the positioning process via the user plane connection between the UE and the LMF entity; if the user plane connection context of the target UE already exists in the LMF entity and the LMF entity determines to use the user plane connection for positioning, step 1 is skipped; the LMF entity can select user plane positioning for a specific positioning method (e.g., a motion sensor-based method), and determine which positioning method (corresponding positioning data) requires user plane transmission based on implementation and local configuration;

[0068] Step 2 (optional): If the LMF entity decides to use the user plane for positioning and no secure user plane connection is established between the UE and the LMF entity, the LMF entity sends user plane information to the AMF entity to instruct the UE to use the user plane for positioning; the user plane information includes the user plane positioning address and security-related information of the LMF;

[0069] Step 3 (optional): When the AMF entity receives the user plane information from the LMF entity in step 2, the AMF entity sends it to the UE via a downlink NAS transport (DL NAS TRANSPORT) message;

[0070] Step 4 (optional): If no applicable Protocol Data Unit (PDU) session is established for user plane positioning, the UE uses the UE Route Selection Policy (URSP), which includes PDU session parameters related to user plane positioning, such as the dedicated data network name (DNN) and single-network slice assistance information (S-NSSAI), to establish a PDU session for user plane positioning. The UE may send a confirmation to the LMF entity through the AMF entity to indicate the success or failure of the user plane connection for positioning services, such as the failure to establish a suitable PDU session.

[0071] Step 5 (optional): The AMF entity sends the confirmation received in step 4 to the LMF entity via the Namf_N1messageNotify service.

[0072] Step 6 (optional): If the LMF entity knows the UE Internet Protocol (IP) address information, the LMF entity may notify the UE to establish a secure user plane connection through the known UE IP address;

[0073] Step 7 (optional): The UE establishes a secure user plane connection with the LMF entity; if the LMF entity sends its Fully Qualified Domain Name (FQDN) to the UE, a Domain Name System (DNS) server / resolver is used to resolve the IP address of the LMF entity (e.g., an edge application server discovery function (easdf) or a local DNS for local LMF entity address resolution);

[0074] Step 8 (optional): The LMF entity indicates in the Nmmf_Location_UP Notify message that the user plane connection between the AMF UE and the LMF has been established.

[0075] Step 9 (optional): The AMF entity stores the Location Service User Plane (LCS-UP) connection context as part of the UE context.

[0076] Step 10: If the LMF entity or UE determines to use the user plane connection for positioning and establishes a secure user plane connection, the LTE positioning protocol (LPP) message is transmitted between the UE and the LMF entity for UE-based positioning, UE-assisted positioning and delivery of auxiliary data; the supplementary service event report message from the UE can also be transmitted to the LMF entity via the established user plane connection.

[0077] Specifically, the user plane positioning connection establishment initiated by the terminal (UE-initiated LCS-UPP initiation) can be shown in Figure 3. The terminal initiates a user plane positioning establishment request to the AMF entity. According to the request, the AMF entity executes the LMF entity selection process, selects a suitable LMF entity for this user plane positioning task, and establishes a connection from the UE to the LMF entity in subsequent signaling.

[0078] As shown in FIG3 , the user plane positioning connection establishment process initiated by the terminal may include at least one of the following steps:

[0079] Step 1: If the UE decides to prepare a user plane connection for the upcoming positioning request, the UE may send a user plane establishment request to the AMF entity via a NAS message.

[0080] Step 2 (optional): If the UE is authorized to use user plane positioning based on UE subscription, the AMF entity selects an LMF entity that can establish a user plane session for positioning with the UE;

[0081] Step 3 (optional): The AMF entity sends a positioning user plane configuration (Nmmf_Location_UP Config) request to the LMF entity to request the establishment of an LCS-UP connection.

[0082] Step 4 (optional): If the LMF entity accepts positioning using the user plane and no secure user plane connection is established between the UE and the LMF entity, the LMF entity sends user plane information to the AMF entity to instruct the UE to accept and use the user plane for positioning; the user plane information includes the user plane positioning address and security-related information of the LMF entity;

[0083] Step 5 (optional): When the AMF entity receives the user plane information from the LMF entity in step 4, the AMF entity forwards it to the UE via a downlink NAS transport (DL NAS TRANSPORT) message;

[0084] Step 6 (optional): The UE establishes a secure user plane connection with the LMF entity.

[0085] Step 7 (optional): The LMF entity responds to the AMF entity that the user plane connection between the UE and the LMF entity has been established.

[0086] Step 8 (optional): The AMF entity stores the LCS-UP connection context as part of the UE context.

[0087] Step 9 (optional). After establishing a secure user plane connection, if the LMF entity determines to use the user plane connection for positioning after receiving a positioning request from the AMF entity, or the UE determines to use the user plane connection for positioning, LPP messages are transmitted between the UE and the LMF entity for UE-based positioning, UE-assisted positioning, and delivery of auxiliary data; supplementary service event report messages from the UE can also be transmitted to the LMF entity via the established user plane connection.

[0088] To facilitate a better understanding of the embodiments of the present application, the security user plane location (SUPL) related to the present application is explained.

[0089] SUPL encapsulates the control plane positioning protocol, using the data network for positioning services without impacting the control plane, thereby offloading any changes to the service provider's infrastructure. This is a standard protocol developed by the Open Mobile Alliance (OMA). SUPL was introduced into the NR architecture of the 3rd Generation Partnership Project (3GPP). As shown in Figure 4, in the research architecture prior to Rel-18, the UE had a SUPL enabled terminal (SET) module (a functional module specified in OMA SUPL), and the network had a SUPL location center (SLC) and a SUPL positioning center (SPC). These modules were deployed close to the LMF entity (i.e., the SLC and SPC could quickly exchange information with the LMF). These modules supported interaction interfaces with the LMF entity and the Location Service (LCS) client, and implemented the transmission and communication of user plane positioning information through the User Plane Function (UPF).

[0090] Specifically, as shown in Figure 4, the UE is connected to the Next Generation Radio Access Network (NG-RAN) through the Uu interface, the NG-RAN is connected to the user plane function (UPF) through the N3 interface, the NG-RAN is connected to the access and mobility management function (AMF) through the N2 interface, the AMF is connected to the LMF through the NLs interface, the AMF is connected to the Gateway Mobile Location Center (GMLC) through the NLg interface, the AMF is connected to the unified data management (UDM) through the N8 interface, the UDM is connected to the GMLC through the NLh interface, the LMF can be directly connected to the SPC, the SPC is connected to the SLC through the Llp interface, the SLC is connected to the LCS client through the Le interface, and the UPF is connected to the SLC through the N6 interface or the Lup interface.

[0091] It should be noted that in Figure 4, Lup and N6 refer to the same interface channel, but from different perspectives. One is called N6 from the 3GPP architecture perspective; the other is called Lup within the SUPL server.

[0092] In order to facilitate a better understanding of the embodiments of the present application, the problems solved by the present application are explained.

[0093] At present, there may be two user plane positioning transmission protocols: one is SUPL; the other is a standard layer 3 protocol (such as the Location Service User Plane Protocol (LCS-UPP)). If both user plane positioning transmission protocols can be deployed on the terminal side and the network side, how to ultimately negotiate which user plane positioning transmission protocol (also known as the protocol stack) to use is still under discussion. To elaborate: if both user plane positioning transmission protocols are optional on the terminal side and the network side, there will be a negotiation problem; if both user plane positioning transmission protocols are required on side A (terminal side or network side) and optional on side B (network side or terminal side), there will be a problem of how to inform side A which user plane positioning transmission protocol to use.

[0094] Based on the above problems, the present application proposes a positioning negotiation method, where the terminal side and the network side can negotiate to determine the transmission protocol for transmitting user plane positioning information, thereby improving the transmission efficiency of user plane positioning information.

[0095] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0096] FIG5 is a schematic flowchart of a method 200 for positioning negotiation according to an embodiment of the present application. As shown in FIG5 , the method 200 for positioning negotiation may include at least part of the following contents:

[0097] S210, the terminal device sends a first message to the first core network device, where the first message is used to perform network registration or establish a user plane positioning connection;

[0098] The first message includes one or more of the following: a first capability, a first designated protocol, and a first confirmation message;

[0099] Among them, the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting user plane positioning information, the first specified protocol includes the transmission protocol that the terminal device expects to use for transmitting user plane positioning information, the first confirmation information is used to indicate that the terminal device accepts or refuses to use the second specified protocol to transmit user plane positioning information, and the second specified protocol includes the transmission protocol specified by the first core network device or the second core network device for transmitting user plane positioning information.

[0100] It should be understood that FIG5 shows the steps or operations of the positioning negotiation method 200, but these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of the operations in FIG5.

[0101] The transmission protocol for transmitting user plane positioning information described in the embodiment of the present application may also be referred to as a protocol stack for transmitting user plane positioning information or a user plane protocol stack, which is not limited in the embodiment of the present application.

[0102] It should be noted that the embodiment of the present application is illustrated by taking two transmission protocols for transmitting user plane positioning information (i.e., the first transmission protocol and the second transmission protocol) as an example. Of course, the embodiment of the present application is also applicable to more (such as 3, 4, 5, ... etc.) transmission protocols for transmitting user plane positioning information. For details, please refer to the relevant description of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0103] In some embodiments, the first transmission protocol is a user plane positioning transmission protocol not developed by 3GPP, and the second transmission protocol is a user plane positioning transmission protocol developed by 3GPP.

[0104] In some embodiments, the first transmission protocol is Secure User Plane Location (SUPL). Of course, the first transmission protocol may also be other user plane location transmission protocols not formulated by 3GPP.

[0105] In some embodiments, the second transmission protocol is the Location Service-User Plane Protocol (LCS-UPP). Of course, the second transmission protocol may also be other user plane positioning transmission protocols developed by 3GPP.

[0106] In an embodiment of the present application, the user plane positioning process may be initiated or triggered by the terminal device, or may be initiated or triggered by the network side (such as the second core network device).

[0107] In some embodiments, the first core network device may be a core network device, for example, an AMF entity. Of course, the first core network device may also be other core network devices, and the embodiments of the present application are not limited to this.

[0108] In some embodiments, the second core network device is a device that establishes a user plane positioning connection with the terminal device. For example, the second core network device is an LMF entity. Of course, the second core network device can also be other core network devices, and the embodiments of the present application are not limited to this.

[0109] In some embodiments, the second core network device can also be replaced by a third-party device (such as a location service (LCS) client) or a 5G core network (5G Core Network, 5GC) network function (NF) entity (such as a network data analysis function (NWDAF)).

[0110] In some embodiments, when the first message is used for network registration, the first message includes the first capability.

[0111] In one embodiment, the first message may be a registration request message. Specifically, the terminal device sends a registration request message to the first core network device (such as an AMF entity) to provide registration information and perform network registration. The terminal device provides the first capability (i.e., the transmission protocol supported by the terminal device for transmitting user plane positioning information) in the registration request message.

[0112] For example, when the bit information carried by the terminal device in the registration request message indicates that the terminal device supports user plane positioning, the terminal device provides the first capability (i.e., the transmission protocol supported by the terminal device for transmitting user plane positioning information) in the registration request message.

[0113] In some embodiments, when the first message is used to establish a user plane positioning connection, the first message includes but is not limited to one or more of the following: the first capability, the first designated protocol, and the first confirmation information.

[0114] In some embodiments, when the first message is used to establish a user plane location connection, the first message may be a user plane location request message sent by the terminal device. In this case, the first message may include the first capability and / or the first designated protocol. In this case, it can be understood that the terminal device initiates or triggers the user plane location process.

[0115] In some embodiments, when the first message is used to establish a user plane positioning connection, the first message may be a user plane positioning response message or a user plane positioning reply message sent by the terminal device. In this case, the first message may include the first confirmation information. Optionally, the first message may also include the first capability and / or the first designated protocol. In this case, it can be understood that the network side (such as the LMF entity) initiates or triggers the user plane positioning process.

[0116] In some embodiments, the first capability includes but is not limited to one of the following:

[0117] The terminal device supports transmission of user plane positioning information using the first transmission protocol;

[0118] The terminal device supports transmission of user plane positioning information using the second transmission protocol;

[0119] The terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information.

[0120] Exemplarily, the terminal device supports using the first transmission protocol to transmit user plane positioning information, including:

[0121] The terminal device supports the use of the first transmission protocol to transmit user plane positioning information, and the terminal device does not support the use of the second transmission protocol to transmit user plane positioning information; or,

[0122] The terminal device supports the use of the first transmission protocol to transmit user plane positioning information, and the terminal device does not support the use of other transmission protocols to transmit user plane positioning information; or

[0123] The terminal device only supports the use of the first transmission protocol to transmit user plane positioning information.

[0124] Exemplarily, the terminal device supports using the second transmission protocol to transmit user plane positioning information, including:

[0125] The terminal device supports the use of the second transmission protocol to transmit user plane positioning information, and the terminal device does not support the use of the first transmission protocol to transmit user plane positioning information; or

[0126] The terminal device supports the use of the second transmission protocol to transmit user plane positioning information, and the terminal device does not support the use of other transmission protocols to transmit user plane positioning information; or

[0127] The terminal device only supports the use of the second transmission protocol to transmit user plane positioning information.

[0128] In some embodiments, the first capability may be characterized by indicating that the terminal device supports user plane positioning capability, indicating that the terminal device supports the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information. That is, if the terminal device supports the user plane positioning capability, it is assumed that the terminal device supports the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information.

[0129] For example, when the terminal device supports the user plane positioning capability, it is assumed that the terminal device supports the use of the first transmission protocol to transmit the user plane positioning information.

[0130] For another example, when the terminal device supports the user plane positioning capability, it is assumed that the terminal device supports the use of the second transmission protocol to transmit the user plane positioning information.

[0131] For another example, when the terminal device supports the user plane positioning capability, it is assumed that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit the user plane positioning information.

[0132] In some embodiments, the first designated protocol includes but is not limited to one of the following:

[0133] The first transmission protocol, the second transmission protocol, the first transmission protocol or the second transmission protocol, the first transmission protocol and the second transmission protocol.

[0134] Exemplarily, when the first capability is included in the first message but the first designated protocol is not included, if the first capability includes that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information, then it is assumed that the terminal device expects to use the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information.

[0135] Exemplarily, when the first designated protocol includes the first transmission protocol and the second transmission protocol, one implementation method is to use the first transmission protocol to transmit LPP messages and use the second transmission protocol to transmit Location Service Supplementary Service (LCS-SS) messages.

[0136] In some embodiments, the second designated protocol includes but is not limited to one of the following:

[0137] The first transmission protocol, the second transmission protocol, the first transmission protocol or the second transmission protocol, the first transmission protocol and the second transmission protocol.

[0138] Exemplarily, when the second designated protocol includes the first transmission protocol and the second transmission protocol, one implementation method is to use the first transmission protocol to transmit LPP messages and use the second transmission protocol to transmit positioning service supplementary service (LCS-SS) messages.

[0139] In some embodiments, when the first message includes the first confirmation information, and the first confirmation information indicates that the terminal device refuses to use the second specified protocol to transmit user plane positioning information, the first message also includes a first cause value, wherein the first cause value is used to indicate the reason why the terminal device refuses the request initiated by the network to establish a user plane positioning connection.

[0140] In some embodiments, the first cause value includes but is not limited to one of the following: the second designated protocol is not supported, the first transmission protocol is not supported, and the second transmission protocol is not supported.

[0141] In some embodiments, when the first cause value is included in the first message, the first message also includes a transmission protocol supported by the terminal device for transmitting user plane positioning information.

[0142] For example, the first reason value includes that the second specified protocol is not supported. Assuming that the second specified protocol includes the first transmission protocol, in this case, the first message also includes that the terminal device supports the use of the second transmission protocol to transmit user plane positioning information.

[0143] For example, the first reason value includes that the second specified protocol is not supported. Assuming that the second specified protocol includes the second transmission protocol, in this case, the first message also includes that the terminal device supports the use of the first transmission protocol to transmit user plane positioning information.

[0144] For example, the first cause value includes that the first transmission protocol is not supported. In this case, the first message also includes that the terminal device supports the use of the second transmission protocol to transmit user plane positioning information.

[0145] For example, the first cause value includes that the second transmission protocol is not supported. In this case, the first message also includes that the terminal device supports the use of the first transmission protocol to transmit user plane positioning information.

[0146] In an embodiment of the present application, the difference between the first capability (i.e., the transmission protocol supported by the terminal device for transmitting user plane positioning information) and the user plane positioning capability of the terminal device is that the latter refers to whether the capability of user plane positioning is supported, while the former refers to what kind of transmission protocol for transmitting user plane positioning information is supported when the capability of user plane positioning is supported.

[0147] In some embodiments, when the first capability is included in the first message, the terminal device may indicate the first capability in a 5G System Mobility Management (5GMM) capability. For example, assuming that the first transmission protocol is SUPL and the second transmission protocol is LCS-UPP, the 5GMM capability information element identity (IEI) can be as shown in Table 1, and the first capability can occupy bits 3 and 4 in octet 9* in the 5GMM capability IEI; wherein, bit 3 in octet 9* is the LCS-UPP support (LCS-UPP support, LUS) field, and bit 4 in byte 9* is the SUPL support (SUPL support, SUPLS) field; specifically, as shown in Table 2, the LCS-UPP support (LUS) field value 0 indicates that the terminal device does not support the use of LCS-UPP to transmit user plane positioning information, and the LCS-UPP support (LUS) field value 1 indicates that the terminal device supports the use of LCS-UPP to transmit user plane positioning information; the SUPL support (SUPLS) field value 0 indicates that the terminal device does not support the use of SUPL to transmit user plane positioning information, and the SUPL support (SUPLS) field value 1 indicates that the terminal device supports the use of SUPL to transmit user plane positioning information. It should be noted that the LCS-UPP support (LUS) field and the SUPL support (SUPLS) field may also occupy other bits in byte 9*, or the LCS-UPP support (LUS) field and the SUPL support (SUPLS) field may also occupy other bytes. This embodiment of the present application is not limited to this.

[0148] Table 1

[0149] Table 2

[0150] Among them, This bit indicates the capability to support LCS-UPP protocol, indicating that this bit indicates the capability to support LCS-UPP protocol; This bit indicates the capability to support SUPL functionality, indicating that this bit indicates the capability to support SUPL function.

[0151] For example, the specific meanings of the LCS-UPP Support (LUS) field and the SUPL Support (SUPLS) field may not be as described in Table 2. For example, the LCS-UPP Support field value 1 indicates that the terminal device does not support the use of LCS-UPP to transmit user plane positioning information, and the LCS-UPP Support field value 0 indicates that the terminal device supports the use of LCS-UPP to transmit user plane positioning information; the SUPL Support field value 1 indicates that the terminal device does not support the use of SUPL to transmit user plane positioning information, and the SUPL Support field value 0 indicates that the terminal device supports the use of SUPL to transmit user plane positioning information.

[0152] In some embodiments, when the first message includes the first designated protocol, assuming that the first transmission protocol is SUPL and the second transmission protocol is LCS-UPP, the terminal device may indicate the first designated protocol in an IE as shown in Table 3. As shown in Table 3, the first designated protocol may occupy bits 1 and 2 in byte 1; bit 1 is the LCS-UPP usage field, and bit 2 is the SUPL usage field; specifically, as shown in Table 4, a value of 1 in the LCS-UPP usage field indicates that the terminal device expects to use LCS-UPP to transmit user plane positioning information, and a value of 0 in the LCS-UPP usage field indicates that the terminal device does not expect to use LCS-UPP to transmit user plane positioning information; a value of 1 in the SUPL usage field indicates that the terminal device expects to use SUPL to transmit user plane positioning information, and a value of 0 in the SUPL usage field indicates that the terminal device does not expect to use SUPL to transmit user plane positioning information. It should be noted that the LCS-UPP usage field and the SUPL usage field may also occupy other bits in byte 1, or the LCS-UPP usage field and the SUPL usage field may also occupy other bytes, which is not limited in this embodiment of the present application.

[0153] Table 3

[0154] Table 4

[0155] Among them, This bit indicates whether the LCS-UPP protocol is used for LCS-UP positioning, indicating whether this bit indicates whether the LCS-UPP protocol is used for LCS-UP positioning; This bit indicates whether the SUPL protocol is used for LCS-UP positioning.

[0156] In an embodiment of the present application, the terminal device can provide the network side with relevant information of the transmission protocol for transmitting user plane positioning information through a first message, so that the terminal side and the network side can negotiate to determine the transmission protocol for transmitting user plane positioning information and improve the transmission efficiency of user plane positioning information.

[0157] In some embodiments, the positioning negotiation method 200 further includes:

[0158] The terminal device receives a second message from the first core network device, where the second message is used to perform network registration or establish a user plane positioning connection; wherein,

[0159] The second message includes one or more of the following: a second capability, a second specified protocol, and a second cause value;

[0160] Among them, the second capability is used to indicate the transmission protocol supported by the network for transmitting user plane positioning information, the second specified protocol includes the transmission protocol for transmitting user plane positioning information specified by the first core network device or the second core network device, and the second reason value is used to indicate the reason why the network rejects the request initiated by the terminal device to establish a user plane positioning connection.

[0161] In some embodiments, when the second message is used for network registration, the second capability is included in the second message. For example, the first message is a registration request message, and the second message is a registration accept message. Specifically, the terminal device provides the first capability in the registration request message, and the first core network device (such as an AMF entity) saves the first capability as terminal context information (UE context). The first core network device sends a registration accept message to the terminal device to inform the terminal device of the registration result and / or the control plane N1 connection information, and the first core network device carries the second capability (i.e., the transmission protocol supported by the network for transmitting user plane positioning information) in the registration accept message.

[0162] For example, when the bit information carried by the terminal device in the registration request message indicates that the terminal device supports user plane positioning, the first core network device carries the second capability (i.e., the transmission protocol supported by the network for transmitting user plane positioning information) in the registration acceptance message.

[0163] In some embodiments, when the second message is used to establish a user plane positioning connection, the second message includes one or more of the following: the second capability, the second designated protocol, and the second cause value.

[0164] In some embodiments, when the second message is used to establish a user plane positioning connection, the second message may be a downlink non-access stratum (NAS) transmission message. For example, the second message is a user plane positioning request message sent by the first core network device (such as an AMF entity). In this case, the second message may include the second capability and / or the second specified protocol. For example, the second capability and / or the second specified protocol may be carried by a payload container information element (IE) or other IE. In this case, it can be understood that the network (such as an LMF entity) initiates or triggers the user plane positioning process.

[0165] In some embodiments, when the second message is used to establish a user plane positioning connection, the second message may be a downlink NAS transmission message. For example, the second message is a user plane positioning response message or a user plane positioning reply message sent by the first core network device (such as an AMF entity). In this case, the second message may include the second cause value. Optionally, the second message may also include the second capability and / or the second designated protocol. For example, the second cause value, the second capability, the second designated protocol, etc. may be carried by a payload container IE or other IE. In this case, it can be understood that the terminal device initiates or triggers the user plane positioning process.

[0166] In some embodiments, when the first capability is included in the first message, the second message is received by the terminal device after sending the first message, and the second message includes the second capability. For example, the first message is a registration request message, and the second message is a registration accept message. That is, the terminal device and the first core network device (such as the AMF entity) exchange their respective capabilities of the transmission protocol for transmitting user plane location information during the network registration process.

[0167] In some embodiments, when the first message includes the first specified protocol, the second message is received by the terminal device after sending the first message, and the second message is used to indicate acceptance of the request initiated by the terminal device to establish a user plane positioning connection, and the second message carries the second specified protocol. For example, the first message is a user plane positioning request message, and the second message is a user plane positioning response message or a user plane positioning reply message.

[0168] Optionally, the transmission protocol included in the second designated protocol is the same as the transmission protocol included in the first designated protocol, or the transmission protocol included in the second designated protocol is different from the transmission protocol included in the first designated protocol.

[0169] In some embodiments, when the first message includes the first designated protocol, the second message is received by the terminal device after sending the first message, and the second message is used to indicate a rejection of the request initiated by the terminal device to establish a user plane location connection, and the second message carries the second cause value. For example, the first message is a user plane location request message, and the second message is a user plane location response message or a user plane location reply message.

[0170] In some embodiments, when the first message includes the first confirmation information, the second message is received by the terminal device before sending the first message, and the second message carries the second specified protocol. For example, the second message is a user plane location request message, and the first message is a user plane location response message or a user plane location reply message.

[0171] In some embodiments, the second capability includes but is not limited to one of the following:

[0172] The network does not support user plane positioning capabilities;

[0173] The network supports transmission of user plane positioning information using a first transmission protocol;

[0174] The network supports transmission of user plane positioning information using a second transmission protocol;

[0175] The network supports transmission of user plane positioning information using a first transmission protocol and a second transmission protocol.

[0176] Exemplarily, the network supports transmitting user plane positioning information using a first transmission protocol, including:

[0177] The network supports the use of the first transmission protocol to transmit the user plane positioning information, and the network does not support the use of the second transmission protocol to transmit the user plane positioning information; or,

[0178] The network supports the use of the first transmission protocol to transmit the user plane positioning information, and the network does not support the use of other transmission protocols to transmit the user plane positioning information; or,

[0179] The network only supports the use of the first transmission protocol to transmit user plane positioning information.

[0180] Exemplarily, the network supports transmitting user plane positioning information using a second transmission protocol, including:

[0181] The network supports transmission of user plane positioning information using the second transmission protocol, and the network does not support transmission of user plane positioning information using the first transmission protocol; or,

[0182] The network supports the use of the second transmission protocol to transmit the user plane positioning information, and the network does not support the use of other transmission protocols to transmit the user plane positioning information; or,

[0183] The network only supports the use of the second transmission protocol to transmit user plane positioning information.

[0184] In some embodiments, the second capability characterizes that the network supports user plane positioning capability by supporting the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information.

[0185] For example, when the network supports the user plane positioning capability, it is assumed that the network supports the use of the first transmission protocol to transmit the user plane positioning information.

[0186] For another example, when the network supports the user plane positioning capability, it is assumed that the network supports the use of the second transmission protocol to transmit the user plane positioning information.

[0187] For another example, when the network supports the user plane positioning capability, it is assumed that the network supports the use of the first transmission protocol and the second transmission protocol to transmit the user plane positioning information.

[0188] In some embodiments, if there is at least one second core network device (such as LMF entity) in the network that supports the use of the first transmission protocol to transmit user plane positioning information, it means that the network supports the use of the first transmission protocol to transmit user plane positioning information; if there is at least one second core network device (such as LMF entity) in the network that supports the use of the second transmission protocol to transmit user plane positioning information, it means that the network supports the use of the second transmission protocol to transmit user plane positioning information; if there is at least one second core network device (such as LMF entity) in the network that supports both the use of the first transmission protocol to transmit user plane positioning information and the use of the second transmission protocol to transmit user plane positioning information, it means that the network supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information; if the second core network devices (such as LMF entities) in the network do not support the user plane positioning function, it means that the network does not support user plane positioning capabilities.

[0189] In some embodiments, the network may forcibly support the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information; or, when there are multiple second core network devices (such as LMF entities) in the network, some second core network devices support the use of the first transmission protocol to transmit user plane positioning information, and some second core network devices support the use of the second transmission protocol to transmit user plane positioning information, then the network supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information.

[0190] In some embodiments, when the network indicates support for user plane positioning capability and does not indicate the capability of the transmission protocol supported by the network for transmitting user plane positioning information, it can be understood that the network supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information.

[0191] In some embodiments, the first core network device (such as an AMF entity) does not need to consider whether the bit information carried by the terminal device in the registration request message indicates whether the terminal device supports the user plane positioning capability, but directly carries the second capability in the registration acceptance message.

[0192] In some embodiments, the second cause value includes at least one of the following: the first designated protocol is not supported, the first transmission protocol is not supported, the second transmission protocol is not supported, and the second core network device is congested.

[0193] In some embodiments, when the second message carries the second cause value, the second message also includes transmission protocol information supported by the network for transmitting user plane positioning information.

[0194] In some embodiments, the second designated protocol is determined by the first core network device (such as an AMF entity) or the second core network device (such as an LMF entity).

[0195] In some embodiments, when the second capability is included in the second message, the first core network device (such as an AMF entity) may indicate the second capability in a 5G system (5G System, 5GS) network feature support information element (IE). For example, assuming that the first transmission protocol is SUPL and the second transmission protocol is LCS-UPP, the 5GS network feature support IEI is shown in Table 5, and the second capability can occupy 2 bits (ie, bits 1-2) in byte 6* in the 5GS network feature support IEI; wherein, the 2 bits in byte 6* are the LCS-UP protocol field, and the specific meaning of the LCS-UP protocol field can be as shown in Table 6, the LCS-UP protocol field value 00 indicates that the network does not support user plane positioning capability (LCS user plane protocol not supported), the LCS-UP protocol field value 01 indicates that the network supports the use of SUPL to transmit user plane positioning information (SUPL protocol supported), the LCS-UP protocol field value 10 indicates that the network supports the use of LCS-UPP to transmit user plane positioning information (LCS-UPP protocol supported), and the LCS-UP protocol field value 11 indicates that the network supports the use of SUPL and LCS-UPP to transmit user plane positioning information (SUPL and LCS-UPP protocol supported). It should be noted that the LCS-UP protocol field may also occupy other bits in byte 6*, or the LCS-UP protocol field may also occupy other bytes, which is not limited in this embodiment of the present application.

[0196] Table 5

[0197] Table 6

[0198] Among them, LCS user plane protocol represents the LCS user plane protocol, This bit indicates the supported protocol to transfer location messages during LCS user plane positioning,

[0199] For example, the specific meaning of the LCS-UP protocol field may not be as described in Table 6. For example, the LCS-UP protocol field value 00 indicates that the network supports the use of SUPL and LCS-UPP to transmit user plane positioning information (SUPL and LCS-UPP protocol supported), the LCS-UP protocol field value 01 indicates that the network supports the use of SUPL to transmit user plane positioning information (SUPL protocol supported), the LCS-UP protocol field value 10 indicates that the network supports the use of LCS-UPP to transmit user plane positioning information (LCS-UPP protocol supported), and the LCS-UP protocol field value 11 indicates that the network does not support user plane positioning capability (LCS user plane protocol not supported).

[0200] In some embodiments, when the second capability is included in the second message, the second message also includes the user plane positioning capability supported by the network. The user plane positioning capability supported by the network can occupy one bit in byte 6* of the 5GS network feature support IEI (i.e., bit 3 in Table 7), as shown in Table 7; wherein, bit 3 in byte 6* is the LCS-UP support field, and the specific meaning of the LCS-UP support field can be as shown in Table 8. The LCS-UP support field value 0 indicates that the network does not support the user plane positioning capability (LCS user plane protocol not supported), and the LCS-UP support field value 1 indicates that the network supports the user plane positioning capability (LCS user plane protocol supported). It should be noted that the LCS-UP support field can also occupy other bits in byte 6*, or the LCS-UP support field can also occupy other bytes, which is not limited in this embodiment of the present application.

[0201] Table 7

[0202] Table 8

[0203] Among them, This bit indicates the capability to support 5G location service via user plane positioning.

[0204] In some embodiments, when the second message includes the second designated protocol, the second message can be transmitted to the terminal device by transmitting the designated protocol information (i.e., the second designated protocol) in a terminal policy process, such as a terminal policy (UE policy) or a policy dedicated to positioning the user plane. One implementation method may be to occupy a new bit based on existing coding, for example: a value of 1 indicates that the user plane positioning message is transmitted using the SUPL protocol, and a value of 0 indicates that the user plane positioning message is transmitted using the LCS-UPP protocol. The reverse is also possible, and the embodiments of the present application are not limited to this.

[0205] In some embodiments, when the second message includes the second designated protocol, assuming that the first transmission protocol is SUPL and the second transmission protocol is LCS-UPP, the first core network device may indicate the second designated protocol in an IE as shown in Table 9. As shown in Table 9, the second designated protocol may occupy bits 1 and 2 in byte 1; bit 1 is the LCS-UPP usage field, and bit 2 is the SUPL usage field; specifically, as shown in Table 10, a value of 1 in the LCS-UPP usage field indicates that the terminal device desires to use LCS-UPP to transmit user plane positioning information, and a value of 0 in the LCS-UPP usage field indicates that the terminal device does not desire to use LCS-UPP to transmit user plane positioning information; a value of 1 in the SUPL usage field indicates that the terminal device desires to use SUPL to transmit user plane positioning information, and a value of 0 in the SUPL usage field indicates that the terminal device does not desire to use SUPL to transmit user plane positioning information. It should be noted that the LCS-UPP usage field and the SUPL usage field may also occupy other bits in byte 1, or the LCS-UPP usage field and the SUPL usage field may also occupy other bytes, which is not limited in this embodiment of the present application.

[0206] Table 9 Table 10

[0207] Among them, This bit indicates whether the LCS-UPP protocol is used for LCS-UP positioning, indicating whether this bit indicates whether the LCS-UPP protocol is used for LCS-UP positioning; This bit indicates whether the SUPL protocol is used for LCS-UP positioning.

[0208] In an embodiment of the present application, the first core network device can provide the terminal device with relevant information of the transmission protocol for transmitting user plane positioning information through the second message, so that the terminal side and the network side can negotiate to determine the transmission protocol for transmitting user plane positioning information and improve the transmission efficiency of user plane positioning information.

[0209] Therefore, in an embodiment of the present application, the terminal side and the network side interact with each other to exchange relevant information about the transmission protocol for transmitting user plane positioning information, so that the terminal side and the network side can negotiate to determine the transmission protocol for transmitting user plane positioning information and improve the transmission efficiency of user plane positioning information.

[0210] The above, in combination with Figure 5, describes in detail the terminal device side embodiment of the present application. The following, in combination with Figure 6, describes in detail the first core network device side embodiment of the present application. It should be understood that the first core network device side embodiment and the terminal device side embodiment correspond to each other, and similar descriptions can refer to the terminal device side embodiment.

[0211] FIG6 is a schematic flowchart of a method 300 for positioning negotiation according to an embodiment of the present application. As shown in FIG6 , the method 300 for positioning negotiation may include at least part of the following contents:

[0212] S310, the first core network device sends a second message to the terminal device, where the second message is used to perform network registration or establish a user plane positioning connection;

[0213] The second message includes one or more of the following: a second capability, a second designated protocol, and a second cause value;

[0214] Among them, the second capability is used to indicate the transmission protocol supported by the network for transmitting user plane positioning information, the second specified protocol includes the transmission protocol for transmitting user plane positioning information specified by the first core network device or the second core network device, and the second reason value is used to indicate the reason why the network rejects the request initiated by the terminal device to establish a user plane positioning connection.

[0215] It should be understood that FIG6 shows the steps or operations of the positioning negotiation method 300, but these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of the operations in FIG6.

[0216] The transmission protocol for transmitting user plane positioning information described in the embodiment of the present application may also be referred to as a protocol stack for transmitting user plane positioning information or a user plane protocol stack, which is not limited in the embodiment of the present application.

[0217] It should be noted that the embodiment of the present application is illustrated by taking two transmission protocols for transmitting user plane positioning information (i.e., the first transmission protocol and the second transmission protocol) as an example. Of course, the embodiment of the present application is also applicable to more (such as 3, 4, 5, ... etc.) transmission protocols for transmitting user plane positioning information. For details, please refer to the relevant description of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0218] In some embodiments, the first transmission protocol is a user plane positioning transmission protocol not developed by 3GPP, and the second transmission protocol is a user plane positioning transmission protocol developed by 3GPP.

[0219] In some embodiments, the first transmission protocol is Secure User Plane Location (SUPL). Of course, the first transmission protocol may also be other user plane location transmission protocols not formulated by 3GPP.

[0220] In some embodiments, the second transmission protocol is the Location Service-User Plane Protocol (LCS-UPP). Of course, the second transmission protocol may also be other user plane positioning transmission protocols developed by 3GPP.

[0221] In an embodiment of the present application, the user plane positioning process may be initiated or triggered by the terminal device, or may be initiated or triggered by the network side (such as the second core network device).

[0222] In some embodiments, the first core network device may be a core network device, for example, an AMF entity. Of course, the first core network device may also be other core network devices, and the embodiments of the present application are not limited to this.

[0223] In some embodiments, the second core network device is a device that establishes a user plane positioning connection with the terminal device. For example, the second core network device is an LMF entity. Of course, the second core network device can also be other core network devices, and the embodiments of the present application are not limited to this.

[0224] In some embodiments, the second core network device may also be replaced by a third-party device (such as a location service (LCS) client) or a 5GC NF entity (such as an NWDAF).

[0225] In some embodiments, when the second message is used for network registration, the second capability is included in the second message. For example, the second message may be a registration accept message. Specifically, the terminal device provides a first capability in a registration request message, and the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting user plane positioning information. The first core network device (such as an AMF entity) saves the first capability as terminal context information (UE context). The first core network device sends a registration accept message to the terminal device to inform the terminal device of the registration result and / or the control plane N1 connection information. The first core network device carries the second capability (i.e., the transmission protocol supported by the network for transmitting user plane positioning information) in the registration accept message.

[0226] For example, when the bit information carried by the terminal device in the registration request message indicates that the terminal device supports user plane positioning, the first core network device carries the second capability (i.e., the transmission protocol supported by the network for transmitting user plane positioning information) in the registration acceptance message.

[0227] In some embodiments, when the second message is used to establish a user plane positioning connection, the second message includes one or more of the following: the second capability, the second designated protocol, and the second cause value.

[0228] In some embodiments, when the second message is used to establish a user plane positioning connection, the second message may be a user plane positioning request message sent by the first core network device (such as an AMF entity). In this case, the second message may include the second capability and / or the second specified protocol. In this case, it can be understood that the network (such as an LMF entity) initiates or triggers the user plane positioning process.

[0229] In some embodiments, when the second message is used to establish a user plane positioning connection, the second message may be a user plane positioning response message or a user plane positioning reply message sent by the first core network device (such as an AMF entity). In this case, the second message may include the second cause value. Optionally, the second message may also include the second capability and / or the second designated protocol. In this case, it can be understood that the terminal device initiates or triggers the user plane positioning process.

[0230] In some embodiments, the second capability includes but is not limited to one of the following:

[0231] The network does not support user plane positioning capabilities;

[0232] The network supports transmission of user plane positioning information using a first transmission protocol;

[0233] The network supports transmission of user plane positioning information using a second transmission protocol;

[0234] The network supports transmission of user plane positioning information using a first transmission protocol and a second transmission protocol.

[0235] Exemplarily, the network supports transmitting user plane positioning information using a first transmission protocol, including:

[0236] The network supports the use of the first transmission protocol to transmit the user plane positioning information, and the network does not support the use of the second transmission protocol to transmit the user plane positioning information; or,

[0237] The network supports the use of the first transmission protocol to transmit the user plane positioning information, and the network does not support the use of other transmission protocols to transmit the user plane positioning information; or,

[0238] The network only supports the use of the first transmission protocol to transmit user plane positioning information.

[0239] Exemplarily, the network supports transmitting user plane positioning information using a second transmission protocol, including:

[0240] The network supports transmission of user plane positioning information using the second transmission protocol, and the network does not support transmission of user plane positioning information using the first transmission protocol; or,

[0241] The network supports the use of the second transmission protocol to transmit the user plane positioning information, and the network does not support the use of other transmission protocols to transmit the user plane positioning information; or,

[0242] The network only supports the use of the second transmission protocol to transmit user plane positioning information.

[0243] In some embodiments, the second capability characterizes that the network supports user plane positioning capability by supporting the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information.

[0244] For example, when the network supports the user plane positioning capability, it is assumed that the network supports the use of the first transmission protocol to transmit the user plane positioning information.

[0245] For another example, when the network supports the user plane positioning capability, it is assumed that the network supports the use of the second transmission protocol to transmit the user plane positioning information.

[0246] For another example, when the network supports the user plane positioning capability, it is assumed that the network supports the use of the first transmission protocol and the second transmission protocol to transmit the user plane positioning information.

[0247] In some embodiments, if there is at least one second core network device (such as LMF entity) in the network that supports the use of the first transmission protocol to transmit user plane positioning information, it means that the network supports the use of the first transmission protocol to transmit user plane positioning information; if there is at least one second core network device (such as LMF entity) in the network that supports the use of the second transmission protocol to transmit user plane positioning information, it means that the network supports the use of the second transmission protocol to transmit user plane positioning information; if there is at least one second core network device (such as LMF entity) in the network that supports both the use of the first transmission protocol to transmit user plane positioning information and the use of the second transmission protocol to transmit user plane positioning information, it means that the network supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information; if the second core network devices (such as LMF entities) in the network do not support the user plane positioning function, it means that the network does not support user plane positioning capabilities.

[0248] In some embodiments, the network may forcibly support the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information; or, when there are multiple second core network devices (such as LMF entities) in the network, some second core network devices support the use of the first transmission protocol to transmit user plane positioning information, and some second core network devices support the use of the second transmission protocol to transmit user plane positioning information, then the network supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information.

[0249] In some embodiments, when the network indicates support for user plane positioning capability and does not indicate the capability of the transmission protocol supported by the network for transmitting user plane positioning information, it can be understood that the network supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information.

[0250] In some embodiments, the first core network device (such as an AMF entity) does not need to consider whether the bit information carried by the terminal device in the registration request message indicates whether the terminal device supports the user plane positioning capability, but directly carries the second capability in the registration acceptance message.

[0251] In some embodiments, the second cause value includes at least one of the following: the first designated protocol is not supported, the first transmission protocol is not supported, the second transmission protocol is not supported, and the second core network device is congested.

[0252] In some embodiments, when the second cause value is carried in the second message, the second message also includes transmission protocol information supported by the network for transmitting user plane positioning information.

[0253] In some embodiments, the second designated protocol includes but is not limited to one of the following:

[0254] The first transmission protocol, the second transmission protocol, the first transmission protocol or the second transmission protocol, the first transmission protocol and the second transmission protocol.

[0255] Exemplarily, when the second designated protocol includes the first transmission protocol and the second transmission protocol, one implementation method is to use the first transmission protocol to transmit LPP messages and use the second transmission protocol to transmit positioning service supplementary service (LCS-SS) messages.

[0256] In some embodiments, the second designated protocol is determined by the first core network device (such as an AMF entity) or the second core network device (such as an LMF entity).

[0257] In some embodiments, when the second capability is included in the second message, the first core network device (such as an AMF entity) may indicate the second capability in a 5GS network feature support IE. For example, assuming that the first transmission protocol is SUPL and the second transmission protocol is LCS-UPP, the 5GS network feature support IEI is as shown in Table 5 above, and the second capability can occupy 2 bits (ie, bits 1-2) in byte 6* in the 5GS network feature support IEI; wherein, the 2 bits in byte 6* are the LCS-UP protocol field, and the specific meaning of the LCS-UP protocol field can be as shown in Table 6 above, the LCS-UP protocol field value 00 indicates that the network does not support user plane positioning capability (LCS user plane protocol not supported), the LCS-UP protocol field value 01 indicates that the network supports the use of SUPL to transmit user plane positioning information (SUPL protocol supported), the LCS-UP protocol field value 10 indicates that the network supports the use of LCS-UPP to transmit user plane positioning information (LCS-UPP protocol supported), and the LCS-UP protocol field value 11 indicates that the network supports the use of SUPL and LCS-UPP to transmit user plane positioning information (SUPL and LCS-UPP protocol supported). It should be noted that the LCS-UP protocol field may also occupy other bits in byte 6*, or the LCS-UP protocol field may also occupy other bytes, which is not limited in this embodiment of the present application.

[0258] For example, the specific meaning of the LCS-UP protocol field may not be as described in Table 6 above. For example, the LCS-UP protocol field value 00 indicates that the network supports the use of SUPL and LCS-UPP to transmit user plane positioning information (SUPL and LCS-UPP protocol supported), the LCS-UP protocol field value 01 indicates that the network supports the use of SUPL to transmit user plane positioning information (SUPL protocol supported), the LCS-UP protocol field value 10 indicates that the network supports the use of LCS-UPP to transmit user plane positioning information (LCS-UPP protocol supported), and the LCS-UP protocol field value 11 indicates that the network does not support user plane positioning capability (LCS user plane protocol not supported).

[0259] In some embodiments, when the second capability is included in the second message, the second message also includes the user plane positioning capability supported by the network. The user plane positioning capability supported by the network can occupy one bit in byte 6* of the 5GS network feature support IEI (i.e., bit 3 in Table 7 above), as shown in Table 7 above; wherein, bit 3 in byte 6* is the LCS-UP support field, and the specific meaning of the LCS-UP support field can be as shown in Table 8 above. The LCS-UP support field value 0 indicates that the network does not support the user plane positioning capability (LCS user plane protocol not supported), and the LCS-UP support field value 1 indicates that the network supports the user plane positioning capability (LCS user plane protocol supported). It should be noted that the LCS-UP support field can also occupy other bits in byte 6*, or the LCS-UP support field can also occupy other bytes, which is not limited in this embodiment of the present application.

[0260] In some embodiments, when the second message includes the second designated protocol, the second message can be transmitted to the terminal device by transmitting the designated protocol information (i.e., the second designated protocol) in a terminal policy process, such as a terminal policy (UE policy) or a policy dedicated to positioning the user plane. One implementation method may be to occupy a new bit based on existing coding, for example: a value of 1 indicates that the user plane positioning message is transmitted using the SUPL protocol, and a value of 0 indicates that the user plane positioning message is transmitted using the LCS-UPP protocol. The reverse is also possible, and the embodiments of the present application are not limited to this.

[0261] In some embodiments, when the second message includes the second designated protocol, assuming that the first transmission protocol is SUPL and the second transmission protocol is LCS-UPP, the first core network device may indicate the second designated protocol in an IE as shown in Table 9. As shown in Table 9, the second designated protocol may occupy bits 1 and 2 in byte 1; bit 1 is the LCS-UPP usage field, and bit 2 is the SUPL usage field; specifically, as shown in Table 10, a value of 1 in the LCS-UPP usage field indicates that the terminal device desires to use LCS-UPP to transmit user plane positioning information, and a value of 0 in the LCS-UPP usage field indicates that the terminal device does not desire to use LCS-UPP to transmit user plane positioning information; a value of 1 in the SUPL usage field indicates that the terminal device desires to use SUPL to transmit user plane positioning information, and a value of 0 in the SUPL usage field indicates that the terminal device does not desire to use SUPL to transmit user plane positioning information. It should be noted that the LCS-UPP usage field and the SUPL usage field may also occupy other bits in byte 1, or the LCS-UPP usage field and the SUPL usage field may also occupy other bytes, which is not limited in this embodiment of the present application.

[0262] In some embodiments, the positioning negotiation method 300 further includes:

[0263] The first core network device receives a first message from the terminal device, where the first message is used to perform network registration or establish a user plane positioning connection;

[0264] The first message includes one or more of the following: a first capability, a first designated protocol, and a first confirmation message;

[0265] Among them, the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting user plane positioning information, the first specified protocol includes the transmission protocol that the terminal device expects to use for transmitting user plane positioning information, and the first confirmation information is used to indicate that the terminal device accepts or refuses to use the second specified protocol to transmit user plane positioning information.

[0266] In some embodiments, when the first message is used for network registration, the first message includes the first capability. For example, the first message may be a registration request message. Specifically, the terminal device sends a registration request message to the first core network device (such as an AMF entity) to provide registration information and perform network registration. The terminal device provides the first capability (i.e., the transmission protocol supported by the terminal device for transmitting user plane positioning information) in the registration request message.

[0267] For example, when the bit information carried by the terminal device in the registration request message indicates that the terminal device supports user plane positioning, the terminal device provides the first capability (i.e., the transmission protocol supported by the terminal device for transmitting user plane positioning information) in the registration request message.

[0268] In some embodiments, when the first message is used to establish a user plane positioning connection, the first message includes but is not limited to one or more of the following: the first capability, the first designated protocol, and the first confirmation information.

[0269] In some embodiments, when the first message is used to establish a user plane location connection, the first message may be a user plane location request message sent by the terminal device. In this case, the first message may include the first capability and / or the first designated protocol. In this case, it can be understood that the terminal device initiates or triggers the user plane location process.

[0270] In some embodiments, when the first message is used to establish a user plane positioning connection, the first message may be a user plane positioning response message or a user plane positioning reply message sent by the terminal device. In this case, the first message may include the first confirmation information. Optionally, the first message may also include the first capability and / or the first designated protocol. In this case, it can be understood that the network side (such as the LMF entity) initiates or triggers the user plane positioning process.

[0271] In some embodiments, when the first capability is included in the first message, the second message is received by the terminal device after sending the first message, and the second message includes the second capability. For example, the first message is a registration request message, and the second message is a registration accept message. That is, the terminal device and the first core network device (such as the AMF entity) exchange their respective capabilities of the transmission protocol for transmitting user plane location information during the network registration process.

[0272] In some embodiments, when the first message includes the first specified protocol, the second message is received by the terminal device after sending the first message, and the second message is used to indicate acceptance of the request initiated by the terminal device to establish a user plane positioning connection, and the second message carries the second specified protocol. For example, the first message is a user plane positioning request message, and the second message is a user plane positioning response message or a user plane positioning reply message.

[0273] Optionally, the transmission protocol included in the second designated protocol is the same as the transmission protocol included in the first designated protocol, or the transmission protocol included in the second designated protocol is different from the transmission protocol included in the first designated protocol.

[0274] In some embodiments, when the first message includes the first designated protocol, the second message is received by the terminal device after sending the first message, and the second message is used to indicate a rejection of the request initiated by the terminal device to establish a user plane location connection, and the second message carries the second cause value. For example, the first message is a user plane location request message, and the second message is a user plane location response message or a user plane location reply message.

[0275] In some embodiments, when the first message includes the first confirmation information, the second message is received by the terminal device before sending the first message, and the second message carries the second specified protocol. For example, the second message is a user plane location request message, and the first message is a user plane location response message or a user plane location reply message.

[0276] In some embodiments, the first capability includes but is not limited to one of the following:

[0277] The terminal device supports transmitting user plane positioning information using a first transmission protocol;

[0278] The terminal device supports transmitting user plane positioning information using a second transmission protocol;

[0279] The terminal device transmits user plane positioning information using a first transmission protocol and a second transmission protocol.

[0280] Exemplarily, the terminal device supports using the first transmission protocol to transmit user plane positioning information, including:

[0281] The terminal device supports the use of the first transmission protocol to transmit user plane positioning information, and the terminal device does not support the use of the second transmission protocol to transmit user plane positioning information; or,

[0282] The terminal device supports the use of the first transmission protocol to transmit user plane positioning information, and the terminal device does not support the use of other transmission protocols to transmit user plane positioning information; or

[0283] The terminal device only supports the use of the first transmission protocol to transmit user plane positioning information.

[0284] Exemplarily, the terminal device supports using the second transmission protocol to transmit user plane positioning information, including:

[0285] The terminal device supports the use of the second transmission protocol to transmit user plane positioning information, and the terminal device does not support the use of the first transmission protocol to transmit user plane positioning information; or

[0286] The terminal device supports the use of the second transmission protocol to transmit user plane positioning information, and the terminal device does not support the use of other transmission protocols to transmit user plane positioning information; or

[0287] The terminal device only supports the use of the second transmission protocol to transmit user plane positioning information.

[0288] In some embodiments, the first capability may be characterized by indicating that the terminal device supports user plane positioning capability, indicating that the terminal device supports the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information. That is, if the terminal device supports the user plane positioning capability, it is assumed that the terminal device supports the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information.

[0289] For example, when the terminal device supports the user plane positioning capability, it is assumed that the terminal device supports the use of the first transmission protocol to transmit the user plane positioning information.

[0290] For another example, when the terminal device supports the user plane positioning capability, it is assumed that the terminal device supports the use of the second transmission protocol to transmit the user plane positioning information.

[0291] For another example, when the terminal device supports the user plane positioning capability, it is assumed that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit the user plane positioning information.

[0292] In some embodiments, the first designated protocol includes but is not limited to one of the following: a first transmission protocol, a second transmission protocol, the first transmission protocol or the second transmission protocol, the first transmission protocol and the second transmission protocol.

[0293] Exemplarily, when the first capability is included in the first message but the first designated protocol is not included, if the first capability includes that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information, then it is assumed that the terminal device expects to use the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information.

[0294] Exemplarily, when the first designated protocol includes the first transmission protocol and the second transmission protocol, one implementation method is to use the first transmission protocol to transmit LPP messages and use the second transmission protocol to transmit location service supplementary service (LCS-SS) messages.

[0295] In some embodiments, when the first message includes the first confirmation information, and the first confirmation information indicates that the terminal device refuses to use the second specified protocol to transmit user plane positioning information, the first message also includes a first cause value; wherein the first cause value is used to indicate the reason why the terminal device refuses the request initiated by the network to establish a user plane positioning connection.

[0296] In some embodiments, the first cause value includes but is not limited to one of the following: the second specified protocol is not supported, the first transmission protocol is not supported, and the second transmission protocol is not supported.

[0297] In some embodiments, when the first cause value is included in the first message, the first message also includes a transmission protocol supported by the terminal device for transmitting user plane positioning information.

[0298] For example, the first reason value includes that the second specified protocol is not supported. Assuming that the second specified protocol includes the first transmission protocol, in this case, the first message also includes that the terminal device supports the use of the second transmission protocol to transmit user plane positioning information.

[0299] For example, the first reason value includes that the second specified protocol is not supported. Assuming that the second specified protocol includes the second transmission protocol, in this case, the first message also includes that the terminal device supports the use of the first transmission protocol to transmit user plane positioning information.

[0300] For example, the first cause value includes that the first transmission protocol is not supported. In this case, the first message also includes that the terminal device supports the use of the second transmission protocol to transmit user plane positioning information.

[0301] For example, the first cause value includes that the second transmission protocol is not supported. In this case, the first message also includes that the terminal device supports the use of the first transmission protocol to transmit user plane positioning information.

[0302] In some embodiments, when the first capability is included in the first message, the terminal device may indicate the first capability in a 5GMM capability. For example, assuming that the first transmission protocol is SUPL and the second transmission protocol is LCS-UPP, the 5GMM capability IEI may be as shown in Table 1 above, and the first capability may occupy bits 3 and 4 in octet 9* in the 5GMM capability IEI; wherein, bit 3 in octet 9* is the LCS-UPP support (LUS) field, and bit 4 in octet 9* is the SUPL support (SUPLS) field; specifically, as shown in Table 2 above, the LCS-UPP support field value of 0 indicates that the terminal device does not support the use of LCS-UPP to transmit user plane positioning information, and the LCS-UPP support field value of 1 indicates that the terminal device supports the use of LCS-UPP to transmit user plane positioning information; the SUPL support field value of 0 indicates that the terminal device does not support the use of SUPL to transmit user plane positioning information, and the SUPL support field value of 1 indicates that the terminal device supports the use of SUPL to transmit user plane positioning information. It should be noted that the LCS-UPP support (LUS) field and the SUPL support (SUPLS) field may also occupy other bits in byte 9*, or the LCS-UPP support (LUS) field and the SUPL support (SUPLS) field may also occupy other bytes. This embodiment of the present application is not limited to this.

[0303] Exemplarily, the specific meanings of the LCS-UPP support field and the SUPL support field may not be as described in Table 2 above. For example, the LCS-UPP support field value 1 indicates that the terminal device does not support the use of LCS-UPP to transmit user plane positioning information, and the LCS-UPP support field value 0 indicates that the terminal device supports the use of LCS-UPP to transmit user plane positioning information; the SUPL support field value 1 indicates that the terminal device does not support the use of SUPL to transmit user plane positioning information, and the SUPL support field value 0 indicates that the terminal device supports the use of SUPL to transmit user plane positioning information.

[0304] In some embodiments, the terminal device may carry the first capability in the registration request message sent during the initial registration and periodic update processes.

[0305] In some embodiments, when the first message includes the first designated protocol, assuming that the first transmission protocol is SUPL and the second transmission protocol is LCS-UPP, the terminal device may indicate the first designated protocol in an IE as shown in Table 3. As shown in Table 3, the first designated protocol may occupy bits 1 and 2 in byte 1; bit 1 is the LCS-UPP usage field, and bit 2 is the SUPL usage field; specifically, as shown in Table 4, a value of 1 in the LCS-UPP usage field indicates that the terminal device expects to use LCS-UPP to transmit user plane positioning information, and a value of 0 in the LCS-UPP usage field indicates that the terminal device does not expect to use LCS-UPP to transmit user plane positioning information; a value of 1 in the SUPL usage field indicates that the terminal device expects to use SUPL to transmit user plane positioning information, and a value of 0 in the SUPL usage field indicates that the terminal device does not expect to use SUPL to transmit user plane positioning information. It should be noted that the LCS-UPP usage field and the SUPL usage field may also occupy other bits in byte 1, or the LCS-UPP usage field and the SUPL usage field may also occupy other bytes, which is not limited in this embodiment of the present application.

[0306] In some embodiments, the positioning negotiation method 300 further includes:

[0307] The first core network device selects, from the at least one second core network device, a second core network device to establish a user plane positioning connection with the terminal device based on the first capability and / or the first designated protocol and a transmission protocol for transmitting user plane positioning information supported by the at least one second core network device; and / or,

[0308] The first core network device determines the second designated protocol based on the first capability and / or the first designated protocol, and a transmission protocol supported by at least one second core network device for transmitting user plane positioning information.

[0309] In some embodiments, the first core network device can obtain and save the transmission protocol supported by the at least one second core network device for transmitting user plane positioning information through local configuration or network storage function (Network Repository Function, NRF) entity query method, so that the first core network device can provide the second capability to provide network supported protocol information to the terminal device.

[0310] In some embodiments, the transmission protocol supported by the second core network device for transmitting user plane positioning information includes one of the following: the second core network device does not support user plane positioning capability, the second core network device supports the use of a first transmission protocol to transmit user plane positioning information, the second core network device supports the use of a second transmission protocol to transmit user plane positioning information, and the second core network device supports the use of a first transmission protocol and a second transmission protocol to transmit user plane positioning information.

[0311] It should be noted that the transmission protocols supported by different second core network devices for transmitting user plane positioning information may be the same or different.

[0312] For example, the first capability includes that the terminal device supports the use of the first transmission protocol to transmit user plane positioning information. In this case, the first core network device selects a second core network device that supports the use of the first transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection between the device and the terminal device.

[0313] For another example, the first capability includes that the terminal device supports the use of the second transmission protocol to transmit user plane positioning information. In this case, the first core network device selects a second core network device that supports the use of the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection between the device and the terminal device.

[0314] For another example, the first capability includes that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information. In this case, the first core network device selects a second core network device from the at least one second core network device that supports the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information to establish a user plane positioning connection between the terminal device and the second core network device.

[0315] For example, the first designated protocol includes the first transmission protocol. In this case, the first core network device may preferentially select a second core network device that supports the use of the first transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device. Of course, in the case where the first designated protocol includes the first transmission protocol, the first core network device may also select a second core network device that supports the use of the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device, or the first core network device may also select a second core network device that supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device.

[0316] For another example, the first designated protocol includes the second transmission protocol. In this case, the first core network device may preferentially select a second core network device that supports the use of the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device. Of course, in the case where the first designated protocol includes the second transmission protocol, the first core network device may also select a second core network device that supports the use of the first transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device, or the first core network device may also select a second core network device that supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device.

[0317] For another example, the first designated protocol includes the first transmission protocol or the second transmission protocol. In this case, the first core network device can select a second core network device that supports the use of the first transmission protocol or the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device. Of course, in the case where the first designated protocol includes the first transmission protocol or the second transmission protocol, the first core network device can also select a second core network device that supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device.

[0318] For another example, the first designated protocol includes the first transmission protocol and the second transmission protocol. In this case, the first core network device can select a second core network device from the at least one second core network device that supports the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information to establish a user plane positioning connection with the terminal device.

[0319] For example, the first capability includes that the terminal device supports the use of the first transmission protocol to transmit user plane positioning information, and the first designated protocol includes the first transmission protocol. In this case, the first core network device selects a second core network device that supports the use of the first transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection between the terminal device and the second core network device.

[0320] For another example, the first capability includes that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information, and the first designated protocol includes the first transmission protocol. In this case, the first core network device can preferentially select a second core network device that supports the use of the first transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device. Of course, the first core network device can also select a second core network device that supports the use of the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device, or the first core network device can also select a second core network device that supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device.

[0321] For another example, the first capability includes that the terminal device supports the use of the second transmission protocol to transmit user plane positioning information and the first designated protocol includes the second transmission protocol. In this case, the first core network device selects a second core network device that supports the use of the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection between the terminal device and the second core network device.

[0322] For another example, the first capability includes that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information, and the first designated protocol includes the second transmission protocol. In this case, the first core network device can preferentially select a second core network device that supports the use of the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device. Of course, the first core network device can also select a second core network device that supports the use of the first transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device, or the first core network device can also select a second core network device that supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device.

[0323] For another example, the first capability includes that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information, and the first designated protocol includes the first transmission protocol or the second transmission protocol. In this case, the first core network device can select a second core network device that supports the use of the first transmission protocol or the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device. Of course, the first core network device can also select a second core network device that supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information from the at least one second core network device to establish a user plane positioning connection with the terminal device.

[0324] For another example, the first capability includes that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information, and the first designated protocol includes the first transmission protocol and the second transmission protocol. In this case, the first core network device can select a second core network device from the at least one second core network device that supports the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information to establish a user plane positioning connection with the terminal device.

[0325] For example, the first capability includes that the terminal device supports the use of the first transmission protocol to transmit user plane positioning information, and there is a second core network device among the at least one second core network device that supports the use of the first transmission protocol to transmit user plane positioning information, or, there is a second core network device among the at least one second core network device that supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information. In this case, the first core network device determines that the second designated protocol includes the first transmission protocol.

[0326] For another example, the first capability includes that the terminal device supports the use of the first transmission protocol to transmit user plane positioning information, and there is no second core network device among the at least one second core network device that supports the use of the first transmission protocol to transmit user plane positioning information, nor is there a second core network device that supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information. In this case, the first core network device will not determine the second designated protocol, or the first core network device determines that the second designated protocol does not exist. Optionally, in this case, the first core network device can indicate to reject the request initiated by the terminal device or the second core network device to establish a user plane connection.

[0327] For another example, the first capability includes that the terminal device supports the use of the second transmission protocol to transmit user plane positioning information, and there is a second core network device among the at least one second core network device that supports the use of the second transmission protocol to transmit user plane positioning information, or, there is a second core network device among the at least one second core network device that supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information. In this case, the first core network device determines that the second designated protocol includes the second transmission protocol.

[0328] For another example, the first capability includes that the terminal device supports the use of the second transmission protocol to transmit user plane positioning information, and there is no second core network device among the at least one second core network device that supports the use of the second transmission protocol to transmit user plane positioning information, nor is there a second core network device that supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information. In this case, the first core network device will not determine the second designated protocol, or the first core network device determines that the second designated protocol does not exist. Optionally, in this case, the first core network device can indicate to reject the request initiated by the terminal device or the second core network device to establish a user plane connection.

[0329] For another example, the first capability includes that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information, and there is only a second core network device among the at least one second core network device that supports the use of the first transmission protocol to transmit user plane positioning information. In this case, the first core network device determines that the second designated protocol includes the first transmission protocol.

[0330] For another example, the first capability includes that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information, and there is only a second core network device among the at least one second core network device that supports the use of the second transmission protocol to transmit user plane positioning information. In this case, the first core network device determines that the second designated protocol includes the second transmission protocol.

[0331] For another example, the first capability includes that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information, and there is a second core network device among the at least one second core network device that supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information. In this case, the first core network device determines that the second designated protocol includes one of the following: the first transmission protocol, the second transmission protocol, the first transmission protocol or the second transmission protocol, the first transmission protocol and the second transmission protocol.

[0332] For another example, the first capability includes that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit user plane positioning information, and all second core network devices do not have a second core network device that supports user plane positioning capabilities. In this case, the first core network device will not determine the second designated protocol, or the first core network device determines that the second designated protocol does not exist. Optionally, in this case, the first core network device can indicate to reject the request initiated by the terminal device or the second core network device to establish a user plane connection.

[0333] In some embodiments, the positioning negotiation method 300 further includes:

[0334] The first core network device receives a third message from the second core network device; wherein the third message is used to establish a user plane positioning connection, and the third message includes the second designated protocol.

[0335] Specifically, when the second designated protocol is included in the second message, before the first core network device sends the second message, the first core network device receives the third message from the second core network device.

[0336] In some embodiments, the third message may not include the second designated protocol. In this case, it is assumed that the second core network device supports all transmission protocols for transmitting user plane positioning information.

[0337] In some embodiments, the third message may further carry at least one of the following: an identifier of the terminal device (such as a UE ID), security key information, an Internet Protocol (IP) address of the second core network device, etc. Of course, the third message may also carry other information, which is not limited in this embodiment of the present application.

[0338] In some embodiments, after the first core network device receives the third message, the positioning negotiation method 300 further includes:

[0339] The first core network device sends a fourth message to the second core network device;

[0340] The fourth message includes second confirmation information, and the second confirmation information is used to indicate that the terminal device accepts or refuses to use the second specified protocol to transmit user plane positioning information.

[0341] For example, the first core network device may determine the second confirmation information based on the first confirmation information, or the information included in the second confirmation information is the same as that of the first confirmation information.

[0342] In some embodiments, the fourth message may indicate whether the user plane positioning connection is successfully established. For example, if the second confirmation information indicates that the terminal device accepts the use of the second designated protocol to transmit user plane positioning information, the fourth message may indicate that the user plane positioning connection is successfully established. For another example, if the second confirmation information indicates that the terminal device refuses to use the second designated protocol to transmit user plane positioning information, the fourth message may indicate that the user plane positioning connection is not successfully established.

[0343] In some embodiments, when the second confirmation information represents that the terminal device refuses to use the second specified protocol to transmit user plane positioning information, the fourth message also includes a third cause value, and the third cause value is used to indicate the reason why the terminal device refuses to use the second specified protocol to transmit user plane positioning information.

[0344] For example, the first core network device may determine the third cause value based on the first cause value, or the third cause value may contain the same information as the first cause value.

[0345] In some embodiments, the third cause value includes one of the following: the second specified protocol is not supported, the first transmission protocol is not supported, and the second transmission protocol is not supported.

[0346] In some embodiments, when the fourth message includes the third cause value, the fourth message also includes the first capability.

[0347] In some embodiments, before the first core network device receives the third message, the positioning negotiation method 300 further includes:

[0348] The first core network device sends a fifth message to the second core network device; wherein the fifth message is used to obtain location information of the terminal device, and the fifth message includes the first capability.

[0349] In some embodiments, the second core network device that sends the third message is selected from the at least one second core network device by the first core network device based on the first capability and / or the first specified protocol, and the transmission protocol supported by at least one second core network device for transmitting user plane positioning information.

[0350] Therefore, in an embodiment of the present application, the first core network device can exchange relevant information of the transmission protocol for transmitting user plane positioning information with the terminal device and / or the second core network device, so that the terminal side and the network side can negotiate to determine the transmission protocol for transmitting user plane positioning information and improve the transmission efficiency of user plane positioning information.

[0351] The above, in combination with Figure 6, describes in detail the first core network device side embodiment of the present application. The following, in combination with Figure 7, describes in detail the second core network device side embodiment of the present application. It should be understood that the second core network device side embodiment corresponds to the first core network device side embodiment, and similar descriptions can refer to the first core network device side embodiment.

[0352] FIG7 is a schematic flowchart of a method 400 for positioning negotiation according to an embodiment of the present application. As shown in FIG7 , the method 400 for positioning negotiation may include at least part of the following contents:

[0353] S410, the second core network device sends a third message to the first core network device;

[0354] The third message is used to establish a user plane positioning connection, and the third message includes a second specified protocol, and the second specified protocol includes a transmission protocol specified by the second core network device for transmitting user plane positioning information.

[0355] It should be understood that FIG7 shows the steps or operations of the positioning negotiation method 400, but these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of the operations in FIG7.

[0356] The transmission protocol for transmitting user plane positioning information described in the embodiment of the present application may also be referred to as a protocol stack for transmitting user plane positioning information or a user plane protocol stack, which is not limited in the embodiment of the present application.

[0357] It should be noted that the embodiment of the present application is illustrated by taking two transmission protocols for transmitting user plane positioning information (i.e., the first transmission protocol and the second transmission protocol) as an example. Of course, the embodiment of the present application is also applicable to more (such as 3, 4, 5, ... etc.) transmission protocols for transmitting user plane positioning information. For details, please refer to the relevant description of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0358] In some embodiments, the first transmission protocol is a user plane positioning transmission protocol not developed by 3GPP, and the second transmission protocol is a user plane positioning transmission protocol developed by 3GPP.

[0359] In some embodiments, the first transmission protocol is Secure User Plane Location (SUPL). Of course, the first transmission protocol may also be other user plane location transmission protocols not formulated by 3GPP.

[0360] In some embodiments, the second transmission protocol is the Location Service-User Plane Protocol (LCS-UPP). Of course, the second transmission protocol may also be other user plane positioning transmission protocols developed by 3GPP.

[0361] In some embodiments, the first core network device may be an AMF entity. Of course, the first core network device may also be other core network devices, and the embodiments of the present application are not limited to this.

[0362] In some embodiments, the second core network device is a device that establishes a user plane positioning connection with the terminal device. For example, the second core network device is an LMF entity. Of course, the second core network device can also be other core network devices, and the embodiments of the present application are not limited to this.

[0363] In some embodiments, the second core network device may also be replaced by a third-party device (such as a location service (LCS) client) or a 5GC NF entity (such as an NWDAF).

[0364] In some embodiments, the third message is used to request establishment of a user plane location connection. That is, the second core network device (such as the LMF entity) triggers or initiates a user plane location process.

[0365] In some embodiments, the second designated protocol comprises one of the following: the first transmission protocol, the second transmission protocol, the first transmission protocol or the second transmission protocol, the first transmission protocol and the second transmission protocol.

[0366] Exemplarily, when the second designated protocol includes the first transmission protocol and the second transmission protocol, one implementation method is to use the first transmission protocol to transmit LPP messages and use the second transmission protocol to transmit positioning service supplementary service (LCS-SS) messages.

[0367] In some embodiments, the third message may not include the second designated protocol. In this case, it is assumed that the second core network device supports all transmission protocols for transmitting user plane positioning information.

[0368] In some embodiments, the third message may further carry at least one of the following: an identifier of the terminal device (such as a UE ID), security key information, an IP address of the second core network device, etc. Of course, the third message may also carry other information, which is not limited in this embodiment of the present application.

[0369] In some embodiments, the positioning negotiation method 400 further includes:

[0370] The second core network device receives a fourth message from the first core network device;

[0371] The fourth message includes second confirmation information, and the second confirmation information is used to instruct the terminal device to accept or refuse to use the second specified protocol to transmit user plane positioning information.

[0372] In some embodiments, the fourth message may indicate whether the user plane positioning connection is successfully established. For example, if the second confirmation information indicates that the terminal device accepts the use of the second designated protocol to transmit user plane positioning information, the fourth message may indicate that the user plane positioning connection is successfully established. For another example, if the second confirmation information indicates that the terminal device refuses to use the second designated protocol to transmit user plane positioning information, the fourth message may indicate that the user plane positioning connection is not successfully established.

[0373] In some embodiments, when the second confirmation information indicates that the terminal device refuses to use the second specified protocol to transmit user plane positioning information, the fourth message also includes a third cause value, and the third cause value is used to indicate the reason why the terminal device refuses to use the second specified protocol to transmit user plane positioning information.

[0374] In some embodiments, the third cause value includes one of the following: the second specified protocol is not supported, the first transmission protocol is not supported, and the second transmission protocol is not supported.

[0375] In some embodiments, the fourth message also includes a first capability, where the first capability is used to indicate a transmission protocol supported by the terminal device for transmitting user plane positioning information.

[0376] In some embodiments, before the second core network device sends the third message, the positioning negotiation method 400 further includes:

[0377] The second core network device receives a fifth message from the first core network device; wherein the fifth message is used to obtain the location information of the terminal device, and the fifth message includes a first capability, and the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting user plane positioning information.

[0378] In some embodiments, the first capability includes but is not limited to one of the following:

[0379] The terminal device supports transmitting user plane positioning information using a first transmission protocol;

[0380] The terminal device supports transmitting user plane positioning information using a second transmission protocol;

[0381] The terminal device transmits user plane positioning information using a first transmission protocol and a second transmission protocol.

[0382] Exemplarily, the terminal device supports using the first transmission protocol to transmit user plane positioning information, including:

[0383] The terminal device supports the use of the first transmission protocol to transmit user plane positioning information, and the terminal device does not support the use of the second transmission protocol to transmit user plane positioning information; or,

[0384] The terminal device supports the use of the first transmission protocol to transmit user plane positioning information, and the terminal device does not support the use of other transmission protocols to transmit user plane positioning information; or

[0385] The terminal device only supports the use of the first transmission protocol to transmit user plane positioning information.

[0386] Exemplarily, the terminal device supports using the second transmission protocol to transmit user plane positioning information, including:

[0387] The terminal device supports the use of the second transmission protocol to transmit user plane positioning information, and the terminal device does not support the use of the first transmission protocol to transmit user plane positioning information; or

[0388] The terminal device supports the use of the second transmission protocol to transmit user plane positioning information, and the terminal device does not support the use of other transmission protocols to transmit user plane positioning information; or

[0389] The terminal device only supports the use of the second transmission protocol to transmit user plane positioning information.

[0390] In some embodiments, the first capability may be characterized by indicating that the terminal device supports user plane positioning capability, indicating that the terminal device supports the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information. That is, if the terminal device supports the user plane positioning capability, it is assumed that the terminal device supports the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information.

[0391] For example, when the terminal device supports the user plane positioning capability, it is assumed that the terminal device supports the use of the first transmission protocol to transmit the user plane positioning information.

[0392] For another example, when the terminal device supports the user plane positioning capability, it is assumed that the terminal device supports the use of the second transmission protocol to transmit the user plane positioning information.

[0393] For another example, when the terminal device supports the user plane positioning capability, it is assumed that the terminal device supports the use of the first transmission protocol and the second transmission protocol to transmit the user plane positioning information.

[0394] Therefore, in an embodiment of the present application, the second core network device can interact with the terminal device and / or the first core network device for relevant information of the transmission protocol for transmitting user plane positioning information, so that the terminal side and the network side can negotiate to determine the transmission protocol for transmitting user plane positioning information and improve the transmission efficiency of user plane positioning information.

[0395] The technical solution of the present application is described below by taking Examples 1 to 4 as examples: When establishing a user plane positioning connection, one or more transmission protocols (also referred to as protocol stacks) are used to transmit positioning information on user plane resources.

[0396] The following embodiment is described by taking the first core network device as an AMF entity and the second core network device as an LMF entity as an example, and taking the first transmission protocol as SUPL and the second transmission protocol as LCS-UPP as an example. Specifically, the terminal side and the network side can exchange the transmission protocols supported by each other for transmitting user plane positioning information, and the AMF entity or the LMF entity determines the final selected transmission protocol for transmitting user plane positioning information.

[0397] The following embodiments mainly revolve around two processes: one is the user plane positioning process initiated by the terminal side (Example 1); the other is the user plane positioning process initiated by the network side (Examples 2, 3 and 4). Among them, in Example 1 and Example 2, the AMF entity determines the final transmission protocol used to transmit the user plane positioning information, in Example 3, the LMF entity determines the final transmission protocol used to transmit the user plane positioning information, and in Example 4, the LMF entity locally determines the transmission protocol used to transmit the user plane positioning information, and the terminal device replies to confirm whether it is supported.

[0398] Embodiment 1: When the UE initiates a user plane positioning request, the AMF entity determines the transmission protocol ultimately used to transmit the user plane positioning information, which may specifically include part or all of the following steps 1-0 to 1-7, as shown in Figure 8.

[0399] Step 1-0: The AMF entity obtains and saves the transmission protocols for transmitting user plane positioning information supported by one or more LMF entities through local configuration or NRF query methods; wherein the transmission protocols for transmitting user plane positioning information supported by the LMF entity include but are not limited to: not supporting user plane positioning capability, supporting the use of SUPL to transmit user plane positioning information, supporting the use of LCS-UPP to transmit user plane positioning information, and supporting the use of SUPL and LCS-UPP to transmit user plane positioning information. The following embodiments 2 and 3 omit this step, but can still obtain and save the transmission protocols for transmitting user plane positioning information supported by one or more LMF entities through local configuration or NEF query methods.

[0400] Step 1-1. The terminal device (UE) sends a registration request message to the AMF entity to provide registration information and perform network registration. When the bit information carried by the terminal device in the registration request message indicates that the terminal device supports the user plane positioning capability, the terminal device provides a first capability in the registration request message; wherein the first capability includes but is not limited to: the terminal device supports the use of SUPL to transmit user plane positioning information; the terminal device supports the use of LCS-UPP to transmit user plane positioning information; the terminal device supports the use of SUPL and LCS-UPP to transmit user plane positioning information.

[0401] It should be noted that the difference between the first capability and the user plane positioning capability is that the latter refers to whether the user plane positioning capability is supported, while the former refers to what transmission protocol is supported to transmit user plane positioning information when the user plane positioning capability is supported.

[0402] For example, the terminal device may indicate the first capability in a 5GMM capability, or may use a new IE to indicate the first capability. Optionally, the terminal device may send the registration request message carrying the first capability in the initial registration and periodic update processes.

[0403] In step 1-2, the AMF entity saves the first capability as terminal context information (UE context). The AMF entity sends a registration accept message to the terminal device to inform the terminal device of the registration result and the information of the control plane N1 connection. When the bit information carried by the terminal device in the registration request message indicates that the terminal device supports the user plane positioning capability, the AMF entity carries the second capability and / or the network supports the user plane positioning capability in the registration accept message.

[0404] The second capability includes but is not limited to:

[0405] The network does not support user plane positioning capabilities;

[0406] The network supports the use of SUPL to transmit user plane positioning information;

[0407] The network supports the use of LCS-UPP to transmit user plane positioning information;

[0408] The network supports the use of SUPL and LCS-UPP to transmit user plane positioning information;

[0409] The network supports user plane positioning capabilities including but not limited to:

[0410] The network supports user plane positioning;

[0411] The network does not support user plane positioning.

[0412] In one implementation method, the AMF entity carries the network support user plane positioning capability in the registration acceptance message, and does not carry the second capability. After receiving the registration acceptance message, the terminal device understands that the network supports the use of all transmission protocols to transmit user plane positioning information.

[0413] It should be noted that when there is at least one LMF entity in the network that supports the use of SUPL to transmit user plane positioning information, it can be characterized as supporting the use of SUPL to transmit user plane positioning information; when there is at least one LMF entity in the network that supports the use of LCS-UPP to transmit user plane positioning information, it can be characterized as supporting the use of LCS-UPP to transmit user plane positioning information; if there is at least one LMF in the network that supports both the use of SUPL to transmit user plane positioning information and the use of LCS-UPP to transmit user plane positioning information, it can be characterized as supporting the use of SUPL and LCS-UPP to transmit user plane positioning information; if none of the LMFs in the network support the user plane positioning function, it can be characterized as not supporting user plane positioning capability.

[0414] In one implementation, the network may force support for the use of SUPL and LCS-UPP to transmit user plane positioning information; or, when there are multiple LMF entities in the network, some LMF entities support the use of SUPL to transmit user plane positioning information, and some LMF entities support the use of LCS-UPP to transmit user plane positioning information, then the network supports the use of SUPL and LCS-UPP to transmit user plane positioning information.

[0415] Optionally, the AMF entity does not need to consider the bit information carried by the terminal device in the registration request message to indicate whether the terminal device supports the user plane positioning capability, and directly carries the second capability in the registration acceptance message.

[0416] One implementation method is that the AMF entity indicates the above-mentioned second capability in the 5GS network feature support IE.

[0417] Step 1-3: When the terminal device expects to use the user plane positioning function in subsequent use, the terminal device sends a user plane positioning request message to the network side (that is, the terminal device triggers the user plane positioning process), carrying a first specified protocol, and the first specified protocol includes the transmission protocol that the terminal device expects to use for transmitting user plane positioning information.

[0418] The first designated protocol includes one of the following:

[0419] SUPL;

[0420] LCS-UPP;

[0421] SUPL or LCS-UPP (It should be noted that if the UE does not provide the first designated protocol and indicates support for SUPL and LCS-UPP, the network side, after receiving the user plane positioning establishment request message, assumes that the terminal device supports all protocols);

[0422] SUPL and LCS-UPP; (It should be noted that this option is used when both the terminal side and the network side support SUPL and LCS-UPP. SUPL can be used to transmit LPP messages, and LCS-UPP can be used to transmit LCS-SS messages).

[0423] It should be noted that when steps 1-1 and 1-2 occur, if the terminal device learns that the transmission protocol supported by the network side is different from the transmission protocol supported by the terminal device (for example, the terminal device supports SUPL and the network supports LCS-UPP, or the terminal device supports LCS-UPP and the network supports SUPL), the terminal device cannot initiate a user plane positioning establishment request message (ie, step 1-3). When both the network side and the terminal side support SUPL and LCS-UPP, the terminal device may optionally provide the first designated protocol to the network.

[0424] In steps 1-4, the AMF entity performs at least one of the following operations:

[0425] LMF entity selection,considers the capability of the user plane positioning protocol stack of LMF;

[0426] Determine a second specified protocol, where the second specified protocol includes a transmission protocol specified by the AMF entity for transmitting user plane positioning information.

[0427] In one implementation, a policy control function (PCF) entity indicates the second designated protocol in a UE policy related process.

[0428] In steps 1-5 and 1-6, the AMF entity and the LMF entity exchange user plane positioning information.

[0429] Step 1-7: If the network can provide user plane positioning service for the terminal, the AMF entity sends a user plane positioning reply message to the terminal device, carrying the second specified protocol and IP address information.

[0430] The IP address information is used to represent the address of the LMF entity.

[0431] The second designated protocol includes one of the following:

[0432] SUPL;

[0433] LCS-UPP;

[0434] SUPL and LCS-UPP; (It should be noted that this option is used when both parties support two protocol stacks. One implementation method is to use SUPL to transmit LPP messages and use LCS-UPP to transmit LCS-SS messages).

[0435] Specifically, if the network cannot provide user plane positioning services for the terminal, the AMF entity sends a user plane positioning rejection message to the terminal device, carrying a second cause value. The second cause value is used to indicate the reason why the network rejects the request initiated by the terminal device to establish a user plane positioning connection.

[0436] The second cause value includes at least one of the following: not supporting the first specified protocol, not supporting SUPL, not supporting LCS-UPP, and LMF entity congestion.

[0437] Optionally, when the user plane positioning reject message carries the second cause value, the user plane positioning reject message further includes transmission protocol information supported by the network for transmitting user plane positioning information.

[0438] It should be noted that, in this embodiment, the following description is given for the capability interaction between steps 1-1 and 1-2, and the transmission protocol (also referred to as a protocol stack) communication between steps 1-3 and 1-7:

[0439] 1) Either capability interaction or transmission protocol communication must be performed; otherwise, the transmission protocol cannot be determined.

[0440] 2) When the UE or the network indicates support for user plane positioning capability, it indicates support for transmitting user plane positioning information using at least one transmission protocol (one of: supporting SUPL; supporting LCS-UPP; supporting SUPL and LCS-UPP).

[0441] 3) When capability interaction is required: Steps 1-2 are required. The terminal device knows the transmission protocols it supports for transmitting positioning information, and must know the transmission protocols supported by the network for transmitting positioning information. If the terminal supports transmission protocol A and the network supports transmission protocol A in step 1-2, then all subsequent information may not be carried (or subsequent steps may not be executed) because only transmission protocol A can be used; if the terminal device supports transmission protocol A and the network supports transmission protocol B in step 1-2, then the terminal device cannot send the user plane positioning request message in step 1-3; if the terminal device supports transmission protocol A and transmission protocol B, and supports transmission protocol A in step 1-2, then the terminal device can only choose to use transmission protocol A, and subsequent information may not be carried; if the terminal supports transmission protocol A and transmission protocol B, and supports transmission protocol A and transmission protocol B in step 1-2, then the choice of which transmission protocol to use for transmitting positioning information is based on its own implementation or the transmission protocol communication part of steps 1-3 and 1-7.

[0442] 4) When transmission protocol communication is required: In this case, capability interaction does not occur. Before establishing a connection, neither the terminal nor the network knows the transmission protocols supported by the other. The other party may support only one or both. Both parties need to perform steps 1-3 / steps 1-7 to determine the transmission protocol to be used for transmitting positioning information.

[0443] Example 2: When the LMF entity initiates a user plane positioning request, the AMF entity determines the transmission protocol ultimately used to transmit the user plane positioning information, which may specifically include part or all of the following steps 2-1 to 2-8, as shown in Figure 9.

[0444] Step 2-1. The terminal device (UE) sends a registration request message to the AMF entity to provide registration information and perform network registration. When the bit information carried by the terminal device in the registration request message indicates that the terminal device supports user plane positioning capability, the terminal device provides a first capability in the registration request message, wherein the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting user plane positioning information; wherein the first capability includes but is not limited to: the terminal device supports the use of SUPL to transmit user plane positioning information; the terminal device supports the use of LCS-UPP to transmit user plane positioning information; the terminal device supports the use of SUPL and LCS-UPP to transmit user plane positioning information.

[0445] It should be noted that the difference between the first capability and the user plane positioning capability is that the latter refers to whether the user plane positioning capability is supported, while the former refers to what transmission protocol is supported to transmit user plane positioning information when the user plane positioning capability is supported.

[0446] For example, the terminal device may indicate the first capability in a 5GMM capability, or may use a new IE to indicate the first capability. Optionally, the terminal device may send the registration request message carrying the first capability in the initial registration and periodic update processes.

[0447] Step 2-2, the AMF entity saves the first capability as terminal context information (UE context). The AMF entity sends a registration accept message to the terminal device to inform the terminal device of the registration result and the information of the control plane N1 connection. When the bit information carried by the terminal device in the registration request message indicates that the terminal device supports the user plane positioning capability, the AMF entity carries the second capability and / or the network supports the user plane positioning capability in the registration accept message.

[0448] The second capability includes but is not limited to:

[0449] The network does not support user plane positioning capabilities;

[0450] The network supports the use of SUPL to transmit user plane positioning information;

[0451] The network supports the use of LCS-UPP to transmit user plane positioning information;

[0452] The network supports the use of SUPL and LCS-UPP to transmit user plane positioning information;

[0453] The network supports user plane positioning capabilities including but not limited to:

[0454] The network supports user plane positioning;

[0455] The network does not support user plane positioning.

[0456] In one implementation method, the AMF entity carries the network support user plane positioning capability in the registration acceptance message, and does not carry the second capability. After receiving the registration acceptance message, the terminal device understands that the network supports the use of all transmission protocols to transmit user plane positioning information.

[0457] It should be noted that when there is at least one LMF entity in the network that supports the use of SUPL to transmit user plane positioning information, it can be characterized as supporting the use of SUPL to transmit user plane positioning information; when there is at least one LMF entity in the network that supports the use of LCS-UPP to transmit user plane positioning information, it can be characterized as supporting the use of LCS-UPP to transmit user plane positioning information; if there is at least one LMF in the network that supports both the use of SUPL to transmit user plane positioning information and the use of LCS-UPP to transmit user plane positioning information, it can be characterized as supporting the use of SUPL and LCS-UPP to transmit user plane positioning information; if none of the LMFs in the network support the user plane positioning function, it can be characterized as not supporting user plane positioning capability.

[0458] In one implementation, the network may force support for the use of SUPL and LCS-UPP to transmit user plane positioning information; or, when there are multiple LMF entities in the network, some LMF entities support the use of SUPL to transmit user plane positioning information, and some LMF entities support the use of LCS-UPP to transmit user plane positioning information, then the network supports the use of SUPL and LCS-UPP to transmit user plane positioning information.

[0459] Optionally, the AMF entity does not need to consider the bit information carried by the terminal device in the registration request message to indicate whether the terminal device supports the user plane positioning capability, and directly carries the second capability in the registration acceptance message.

[0460] One implementation method is that the AMF entity indicates the above-mentioned second capability in the 5GS network feature support IE.

[0461] Step 2-3: The LMF entity sends a message to the AMF entity, requesting to establish a user plane positioning connection, carrying a second specified protocol, UE ID, security key information, and LMF IP address; wherein the second specified protocol includes the transmission protocol specified by the LMF entity for transmitting user plane positioning information. If the second specified protocol is not optionally carried, the AMF entity understands that the LMF entity supports all transmission protocols.

[0462] Step 2-4, the AMF entity performs transmission protocol selection, considering the first capability in the saved UE context, wherein the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting user plane positioning information.

[0463] In some embodiments, the first capability includes but is not limited to one of the following:

[0464] The terminal device supports transmission of user plane positioning information using SUPL;

[0465] The terminal device supports the use of LCS-UPP to transmit user plane positioning information;

[0466] The terminal device supports using SUPL and LCS-UPP to transmit user plane positioning information.

[0467] Specifically, an example of the operation of transmission protocol selection is as follows: if both the terminal and the network support transmission protocol A, transmission protocol A is selected as the transmission protocol, and steps 2-6 are executed; if one party supports transmission protocol A and the other party supports transmission protocol B, the transmission protocol specified by the LMF entity does not overlap with the transmission protocol supported by the current UE, and steps 2-5 are executed; if one party supports transmission protocol A and transmission protocol B and the other party supports transmission protocol A, transmission protocol A is selected to transmit the user plane positioning information, and steps 2-6 are executed; if both the terminal and the network support multiple protocol stacks, the AMF entity selects the transmission protocol for transmitting the user plane positioning information based on the local policy, and executes steps 2-6 to 2-8.

[0468] Step 2-5: If the transmission protocol specified by the LMF entity for transmitting user plane positioning information does not overlap with the transmission protocol supported by the current UE for transmitting user plane positioning information, the AMF entity sends a notification message to the LMF entity, carrying a third cause value, and the third cause value is used to indicate the reason why the terminal device refuses to use the second specified protocol to transmit user plane positioning information.

[0469] Optionally, the third cause value includes one of the following: not supporting the second designated protocol, not supporting SUPL, and not supporting LCS-UPP.

[0470] Optionally, the notification message in step 2-5 also includes the first capability.

[0471] Step 2-6. If the transmission protocol specified by the LMF entity for transmitting user plane positioning information coincides with the transmission protocol supported by the current UE for transmitting user plane positioning information, the AMF entity sends a user plane positioning request message to the terminal, carrying the second specified protocol.

[0472] The user plane positioning request message can be transmitted in one method by using the payload container IE in the downlink NAS transport (DL NAS TRANSPORT) message, or in another method by using a new IE in the downlink NAS transport (DL NAS TRANSPORT) message.

[0473] Step 2-7: The terminal device sends a user plane positioning reply message to the network side to confirm the user plane positioning request message in step 2-6 and establish user plane resources.

[0474] One method for transmitting the user plane location reply message is to use a new IE in an uplink NAS transport (UL NAS TRANSPORT) message.

[0475] Step 2-8: The AMF entity sends a confirmation message to the LMF entity, indicating whether the user plane positioning connection is successfully established.

[0476] It should be noted that, in this embodiment, the following description is provided for the capability interaction of step 1 / step 2 and the transmission protocol (also referred to as protocol stack) confirmation of steps 2-6:

[0477] 1) Either capability interaction or transmission protocol confirmation must be performed; otherwise, the transmission protocol cannot be determined.

[0478] 2) When the UE indicates support for user plane positioning capability, it indicates support for using at least one transmission protocol to transmit user plane positioning information (one of: supporting SUPL; supporting LCS-UPP; supporting SUPL and LCS-UPP). The final method to be used is determined in steps 2-6 to 2-8.

[0479] 3) When capability interaction is mandatory: Step 2-1 is mandatory. The network knows the transport protocols it supports for transmitting positioning information, but it must also know the transport protocols supported by the terminal for transmitting positioning information. If the network supports transport protocol A and the terminal supports transport protocol A in step 2-1, then all subsequent information may not be carried to the terminal because only transport protocol A can be used; if the network only supports transport protocol A and the terminal supports transport protocol B in step 2-1, then the AMF will reject the user plane positioning service for the terminal in step 2-5, and step 2-6 will not occur; if the network supports transport protocol A and transport protocol B, and the terminal only supports transport protocol A in step 2-1, then the network can only choose to use transport protocol A, and subsequent information may not be carried; if the network supports transport protocol A and transport protocol B, and the terminal supports transport protocol A and transport protocol B in step 2-1, then the choice of which transport protocol to use for transmitting positioning information is based on its own implementation, and the terminal is informed in step 2-6.

[0480] 4) When transmission protocol communication is required: In this case, capability interaction does not occur. Before establishing a connection, neither the terminal nor the network knows the protocol stack supported by the other. Either the terminal or the network may support only one or both. Both parties need to perform steps 2-6 and 2-7 to determine the final transmission protocol used to transmit positioning information.

[0481] Example 3: When the AMF entity requests the location information of the UE, the AMF entity informs the LMF entity of the first capability, and the LMF entity decides the transmission protocol to be used for transmitting the user plane positioning information, wherein the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting the user plane positioning information, which may specifically include part or all of the following steps 3-1 to 3-10, as shown in Figure 10.

[0482] Step 3-1. The terminal device (UE) sends a registration request message to the AMF entity to provide registration information and perform network registration. When the bit information carried by the terminal device in the registration request message indicates that the terminal device supports the user plane positioning capability, the terminal device provides a first capability in the registration request message; wherein the first capability includes but is not limited to: the terminal device supports the use of SUPL to transmit user plane positioning information; the terminal device supports the use of LCS-UPP to transmit user plane positioning information; the terminal device supports the use of SUPL and LCS-UPP to transmit user plane positioning information.

[0483] It should be noted that the difference between the first capability and the user plane positioning capability is that the latter refers to whether the user plane positioning capability is supported, while the former refers to what transmission protocol is supported to transmit user plane positioning information when the user plane positioning capability is supported.

[0484] For example, the terminal device may indicate the first capability in a 5GMM capability, or may use a new IE to indicate the first capability. Optionally, the terminal device may send the registration request message carrying the first capability in the initial registration and periodic update processes.

[0485] Step 3-2, the AMF entity saves the first capability as terminal context information (UE context). The AMF entity sends a registration accept message to the terminal device to inform the terminal device of the registration result and the information of the control plane N1 connection. When the bit information carried by the terminal device in the registration request message indicates that the terminal device supports the user plane positioning capability, the AMF entity carries the second capability and / or the network supports the user plane positioning capability in the registration accept message.

[0486] The second capability includes but is not limited to:

[0487] The network does not support user plane positioning capabilities;

[0488] The network supports the use of SUPL to transmit user plane positioning information;

[0489] The network supports the use of LCS-UPP to transmit user plane positioning information;

[0490] The network supports the use of SUPL and LCS-UPP to transmit user plane positioning information;

[0491] The network supports user plane positioning capabilities including but not limited to:

[0492] The network supports user plane positioning;

[0493] The network does not support user plane positioning.

[0494] In one implementation method, the AMF entity carries the network support user plane positioning capability in the registration acceptance message, and does not carry the second capability. After receiving the registration acceptance message, the terminal device understands that the network supports the use of all transmission protocols to transmit user plane positioning information.

[0495] It should be noted that when there is at least one LMF entity in the network that supports the use of SUPL to transmit user plane positioning information, it can be characterized as supporting the use of SUPL to transmit user plane positioning information; when there is at least one LMF entity in the network that supports the use of LCS-UPP to transmit user plane positioning information, it can be characterized as supporting the use of LCS-UPP to transmit user plane positioning information; if there is at least one LMF in the network that supports both the use of SUPL to transmit user plane positioning information and the use of LCS-UPP to transmit user plane positioning information, it can be characterized as supporting the use of SUPL and LCS-UPP to transmit user plane positioning information; if none of the LMFs in the network support the user plane positioning function, it can be characterized as not supporting user plane positioning capability.

[0496] In one implementation, the network may force support for the use of SUPL and LCS-UPP to transmit user plane positioning information; or, when there are multiple LMF entities in the network, some LMF entities support the use of SUPL to transmit user plane positioning information, and some LMF entities support the use of LCS-UPP to transmit user plane positioning information, then the network supports the use of SUPL and LCS-UPP to transmit user plane positioning information.

[0497] Optionally, the AMF entity does not need to consider the bit information carried by the terminal device in the registration request message to indicate whether the terminal device supports the user plane positioning capability, and directly carries the second capability in the registration acceptance message.

[0498] One implementation method is that the AMF entity indicates the above-mentioned second capability in the 5GS network feature support IE.

[0499] Step 3-3: The AMF entity receives the location request message from the 5G network element, which carries information such as UE ID.

[0500] Step 3-4: The AMF entity selects an LMF entity and sends a location request confirmation message to the selected LMF entity, carrying the user plane positioning capability of the terminal device and the first capability.

[0501] Step 3-5: The LMF entity responds with a location request confirmation message received in step 3-4.

[0502] Step 3-6: The LMF entity saves the information in step 3-4. In addition, the LMF entity performs transmission protocol selection: considering the first capability and the transmission protocol supported by the LMF entity for transmitting user plane positioning information, a second designated protocol is determined, where the second designated protocol includes a transmission protocol specified by the LMF entity for transmitting user plane positioning information.

[0503] Optionally, the second designated protocol includes but is not limited to one of the following:

[0504] SUPL, LCS-UPP, SUPL or LCS-UPP, SUPL and LCS-UPP.

[0505] It should be noted that if the transmission protocol supported by the terminal for transmitting user plane positioning information does not overlap with the transmission protocol supported by the LMF entity for transmitting user plane positioning information, the LMF entity cannot initiate the establishment of a user plane positioning connection with the terminal.

[0506] Step 3-7, the LMF entity sends Namf_communication_N1N2 transmission (user plane positioning request message) to the AMF entity, requesting to establish a user plane positioning connection, carrying the second specified protocol.

[0507] Step 3-8, the AMF entity sends a downlink NAS transmission (i.e., a user plane positioning request message) to the terminal, carrying the second specified protocol.

[0508] The user plane positioning request message can be transmitted in one method by using the payload container IE in the downlink NAS transport (DL NAS TRANSPORT) message, or in another method by using a new IE in the downlink NAS transport (DL NAS TRANSPORT) message.

[0509] Step 3-9: The terminal device sends a user plane positioning reply message to the network side to confirm the user plane positioning request message of step 3-7 and establish user plane resources.

[0510] One method for transmitting the user plane location reply message is to use a new IE in an uplink NAS transport (UL NAS TRANSPORT) message.

[0511] Step 3-10: The AMF entity sends a confirmation message to the LMF entity, indicating whether the user plane positioning connection is successfully established.

[0512] Example 4: When the LMF entity initiates a user plane positioning request, there is no capability interaction. The LMF entity directly selects a transmission protocol for transmitting user plane positioning information. The UE can subsequently accept or reject it in the reply, which may specifically include part or all of the following steps 4-1 to 4-5, as shown in Figure 11.

[0513] Step 4-1: The LMF entity decides to use user plane positioning and selects a transmission protocol for transmitting user plane positioning information.

[0514] Step 4-2, the LMF entity sends a user plane positioning request message to the AMF entity, requesting to establish a user plane positioning connection, carrying a second specified protocol, where the second specified protocol includes a transmission protocol specified by the LMF entity for transmitting user plane positioning information.

[0515] Optionally, the second designated protocol includes but is not limited to one of the following:

[0516] SUPL, LCS-UPP, SUPL or LCS-UPP, SUPL and LCS-UPP.

[0517] Step 4-3, the AMF entity sends a user plane positioning request message to the terminal, carrying the second specified protocol.

[0518] The user plane positioning request message can be transmitted in one method by using the payload container IE in the downlink NAS transport (DL NAS TRANSPORT) message, or in another method by using a new IE in the downlink NAS transport (DL NAS TRANSPORT) message.

[0519] Step 4-4: The terminal device sends a user plane location reply message to the network side, including two types of messages: acceptance message and rejection message. Acceptance message confirms receipt of the user plane location request message in step 4-3 and establishment of user plane resources. Rejection message rejects the user plane location request message in step 4-3 and optionally carries a first cause value, where the first cause value is used to indicate the reason why the terminal device rejects the request initiated by the network to establish a user plane location connection.

[0520] Optionally, the first cause value includes but is not limited to one of the following: not supporting the second designated protocol, not supporting SUPL, and not supporting LCS-UPP.

[0521] Optionally, when the first message includes the first cause value, the first message also includes a transmission protocol supported by the terminal device for transmitting user plane positioning information.

[0522] One method for transmitting the user plane location reply message is to use a new IE in an uplink NAS transport (UL NAS TRANSPORT) message.

[0523] It should be noted that the AMF entity does not store the first capability and the second capability; wherein the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting user plane positioning information, and the second capability is used to indicate the transmission protocol supported by the network for transmitting user plane positioning information. If the LMF entity selects the transmission protocol based on the local policy, step 4-3 is sent to the terminal. In this way, after the terminal receives the step 4-3 message, if it finds that the second specified protocol is not supported locally, the first cause value is carried in the reply message.

[0524] Step 4-5: The AMF entity replies with an acceptance or rejection message to the LMF entity. Optionally, if the terminal device does not support the second specified protocol, the transmission protocol supported by the terminal device for transmitting the user plane positioning information is stored in the LMF entity or the AMF entity. If the transmission protocol supported by the terminal device for transmitting the user plane positioning information is provided in step 4-4, the LMF entity may carry the supported transmission protocol in a subsequent user plane positioning request.

[0525] The above text, in combination with Figures 5 to 11, describes in detail the method embodiment of the present application. The following text, in combination with Figures 12 to 14, describes in detail the device embodiment of the present application. It should be understood that the device embodiment and the method embodiment correspond to each other, and similar descriptions can refer to the method embodiment.

[0526] FIG12 shows a schematic block diagram of a positioning negotiation apparatus 500 according to an embodiment of the present application. As shown in FIG12 , the positioning negotiation apparatus 500 includes:

[0527] A sending unit 510 is configured to send a first message to a first core network device, where the first message is used to perform network registration or establish a user plane positioning connection;

[0528] The first message includes one or more of the following: a first capability, a first designated protocol, and a first confirmation message;

[0529] Among them, the first capability is used to indicate the transmission protocol supported by the positioning negotiation device 500 for transmitting user plane positioning information, the first specified protocol includes the transmission protocol expected by the positioning negotiation device 500 to use for transmitting user plane positioning information, and the first confirmation information is used to indicate that the positioning negotiation device 500 accepts or refuses to use the second specified protocol to transmit user plane positioning information, and the second specified protocol includes the transmission protocol specified by the first core network device or the second core network device for transmitting user plane positioning information.

[0530] In some embodiments, the first capability includes one of the following:

[0531] The positioning negotiation apparatus 500 supports transmitting user plane positioning information using a first transmission protocol;

[0532] The positioning negotiation apparatus 500 supports transmitting user plane positioning information using a second transmission protocol;

[0533] The positioning negotiation apparatus 500 supports transmitting user plane positioning information using a first transmission protocol and a second transmission protocol.

[0534] In some embodiments, the first specified protocol includes one of the following:

[0535] First transmission protocol, second transmission protocol, first transmission protocol or second transmission protocol, first transmission protocol and second transmission protocol.

[0536] In some embodiments, the second specified protocol includes one of the following:

[0537] First transmission protocol, second transmission protocol, first transmission protocol or second transmission protocol, first transmission protocol and second transmission protocol.

[0538] In some embodiments, when the first message includes the first confirmation information, and the first confirmation information indicates that the positioning negotiation device 500 refuses to use the second specified protocol to transmit user plane positioning information, the first message also includes a first cause value, wherein the first cause value is used to indicate the reason why the positioning negotiation device 500 rejects the request initiated by the network to establish a user plane positioning connection.

[0539] In some embodiments, the first cause value includes one of the following: the second specified protocol is not supported, the first transmission protocol is not supported, and the second transmission protocol is not supported.

[0540] In some embodiments, the first message further includes a transmission protocol supported by the positioning negotiation apparatus 500 for transmitting user plane positioning information.

[0541] In some embodiments, when the first message is used for network registration, the first message includes the first capability; or

[0542] In the case where the first message is used to establish a user plane positioning connection, the first message includes one or more of the following: the first capability, the first designated protocol, and the first confirmation information.

[0543] In some embodiments, the positioning negotiation apparatus 500 further includes:

[0544] The receiving unit 520 is configured to receive a second message from the first core network device, where the second message is used to perform network registration or establish a user plane positioning connection; wherein,

[0545] The second message includes one or more of the following: a second capability, the second specified protocol, and a second cause value;

[0546] The second capability is used to indicate a transmission protocol supported by the network for transmitting user plane positioning information, and the second cause value is used to indicate the reason why the network rejects the request for establishing a user plane positioning connection initiated by the positioning negotiation apparatus 500.

[0547] In some embodiments, when the first message includes the first capability, the second message is received by the positioning negotiation apparatus 500 after sending the first message, and the second message includes the second capability; or

[0548] In a case where the first designated protocol is included in the first message, the second message is received by the positioning negotiation apparatus 500 after sending the first message, and the second message is used to indicate acceptance of the request for establishing a user plane positioning connection initiated by the positioning negotiation apparatus 500, and the second message carries the second designated protocol; or, in a case where the first designated protocol is included in the first message, the second message is received by the positioning negotiation apparatus 500 after sending the first message, and the second message is used to indicate rejection of the request for establishing a user plane positioning connection initiated by the positioning negotiation apparatus 500, and the second message carries the second cause value; or,

[0549] In a case where the first message includes the first confirmation information, the second message is received by the positioning negotiation apparatus 500 before sending the first message, and the second message carries the second designated protocol.

[0550] In some embodiments, the second capability includes one of the following:

[0551] The network does not support user plane positioning capabilities;

[0552] The network supports transmission of user plane positioning information using a first transmission protocol;

[0553] The network supports transmission of user plane positioning information using a second transmission protocol;

[0554] The network supports transmission of user plane positioning information using a first transmission protocol and a second transmission protocol.

[0555] In some embodiments, the second capability characterizes that the network supports user plane positioning capability by supporting the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information.

[0556] In some embodiments, the second cause value includes at least one of the following: the first designated protocol is not supported, the first transmission protocol is not supported, the second transmission protocol is not supported, and the second core network device is congested.

[0557] In some embodiments, when the second cause value is carried in the second message, the second message also includes transmission protocol information supported by the network for transmitting user plane positioning information.

[0558] In some embodiments, when the second message is used for network registration, the second message includes the second capability; or

[0559] In the case where the second message is used to establish a user plane positioning connection, the second message includes one or more of the following: the second capability, the second designated protocol, and the second cause value.

[0560] In some embodiments, the second designated protocol is determined by the first core network device or the second core network device.

[0561] In some embodiments, the first transmission protocol is a user plane positioning transmission protocol not developed by the Third Generation Partnership Project 3GPP, and the second transmission protocol is a user plane positioning transmission protocol developed by the 3GPP.

[0562] In some embodiments, the sending unit and the receiving unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip.

[0563] It should be understood that the positioning negotiation device 500 according to the embodiment of the present application may correspond to the terminal device in the method embodiment of the present application, and the above-mentioned and other operations and / or functions of each unit in the positioning negotiation device 500 are respectively for implementing the corresponding processes of the terminal device in the method 200 shown in Figure 5. For the sake of brevity, they will not be repeated here.

[0564] FIG13 shows a schematic block diagram of a positioning negotiation apparatus 600 according to an embodiment of the present application. As shown in FIG13 , the positioning negotiation apparatus 600 includes:

[0565] A sending unit 610 is configured to send a second message to a terminal device, where the second message is used to perform network registration or establish a user plane positioning connection;

[0566] The second message includes one or more of the following: a second capability, a second designated protocol, and a second cause value;

[0567] Among them, the second capability is used to indicate the transmission protocol supported by the network for transmitting user plane positioning information, the second specified protocol includes the positioning negotiation device 600 or the transmission protocol specified by the second core network device for transmitting user plane positioning information, and the second reason value is used to indicate the reason why the network rejects the request initiated by the terminal device to establish a user plane positioning connection.

[0568] In some embodiments, the second capability includes one of the following:

[0569] The network does not support user plane positioning capabilities;

[0570] The network supports transmission of user plane positioning information using a first transmission protocol;

[0571] The network supports transmission of user plane positioning information using a second transmission protocol;

[0572] The network supports transmission of user plane positioning information using a first transmission protocol and a second transmission protocol.

[0573] In some embodiments, the second capability characterizes that the network supports user plane positioning capability by characterizing that the network supports transmission of user plane positioning information using the first transmission protocol and / or the second transmission protocol.

[0574] In some embodiments, the second cause value includes at least one of the following: support for the first specified protocol, support for the first transmission protocol, support for the second transmission protocol, and congestion of the second core network device;

[0575] The first designated protocol includes a transmission protocol that the terminal device expects to use for transmitting user plane positioning information.

[0576] In some embodiments, when the second cause value is carried in the second message, the second message also includes transmission protocol information supported by the network for transmitting user plane positioning information.

[0577] In some embodiments, the second designated protocol comprises one of the following: the first transmission protocol, the second transmission protocol, the first transmission protocol or the second transmission protocol, the first transmission protocol and the second transmission protocol.

[0578] In some embodiments, the second designated protocol is determined by the positioning negotiation apparatus 600 or the second core network device.

[0579] In some embodiments, when the second message is used for network registration, the second message includes the second capability; or

[0580] In the case where the second message is used to establish a user plane positioning connection, the second message includes one or more of the following: the second capability, the second designated protocol, and the second cause value.

[0581] In some embodiments, the positioning negotiation apparatus 600 further includes:

[0582] The receiving unit 620 is configured to receive a first message from the terminal device, where the first message is used to perform network registration or establish a user plane positioning connection;

[0583] The first message includes one or more of the following: a first capability, a first designated protocol, and a first confirmation message;

[0584] Among them, the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting user plane positioning information, the first specified protocol includes the transmission protocol that the terminal device expects to use for transmitting user plane positioning information, and the first confirmation information is used to indicate that the terminal device accepts or refuses to use the second specified protocol to transmit user plane positioning information.

[0585] In some embodiments, when the first message includes the first capability, the second message is sent by the positioning negotiation apparatus 600 after receiving the first message, and the second message includes the second capability; or

[0586] In the case where the first message includes the first designated protocol, the second message is sent by the positioning negotiation apparatus 600 after receiving the first message, and the second message is used to indicate acceptance of the request for establishing a user plane positioning connection initiated by the terminal device, and the second message carries the second designated protocol; or, in the case where the first message includes the first designated protocol, the second message is sent by the positioning negotiation apparatus 600 after receiving the first message, and the second message is used to indicate rejection of the request for establishing a user plane positioning connection initiated by the terminal device, and the second message carries the second cause value; or,

[0587] In a case where the first message includes the first confirmation information, the second message is sent by the positioning negotiation apparatus 600 before receiving the first message, and the second message carries the second designated protocol.

[0588] In some embodiments, the first capability includes one of the following:

[0589] The terminal device supports transmitting user plane positioning information using a first transmission protocol;

[0590] The terminal device supports transmitting user plane positioning information using a second transmission protocol;

[0591] The terminal device transmits user plane positioning information using a first transmission protocol and a second transmission protocol.

[0592] In some embodiments, the first designated protocol includes one of the following: a first transmission protocol, a second transmission protocol, the first transmission protocol or the second transmission protocol, the first transmission protocol and the second transmission protocol.

[0593] In some embodiments, when the first message includes the first confirmation information, and the first confirmation information indicates that the terminal device refuses to use the second specified protocol to transmit user plane positioning information, the first message also includes a first cause value; wherein the first cause value is used to indicate the reason why the terminal device refuses the request initiated by the network to establish a user plane positioning connection.

[0594] In some embodiments, the first cause value includes one of the following: the second specified protocol is not supported, the first transmission protocol is not supported, and the second transmission protocol is not supported.

[0595] In some embodiments, the first message also includes a transmission protocol supported by the terminal device for transmitting user plane positioning information.

[0596] In some embodiments, the positioning negotiation apparatus 600 further includes: a processing unit 630;

[0597] The processing unit 630 is configured to select, from the at least one second core network device, a second core network device to establish a user plane positioning connection with the terminal device based on the first capability and / or the first designated protocol, and a transmission protocol for transmitting user plane positioning information supported by the at least one second core network device; and / or,

[0598] The processing unit 630 is configured to determine the second designated protocol based on the first capability and / or the first designated protocol, and a transmission protocol supported by at least one second core network device for transmitting user plane positioning information.

[0599] In some embodiments, before the positioning negotiation apparatus 600 sends the second message, the receiving unit 620 is configured to receive a third message from a second core network device; wherein the third message is used to establish a user plane positioning connection, and the third message includes the second designated protocol.

[0600] In some embodiments, the sending unit 610 is further configured to send a fourth message to the second core network device;

[0601] The fourth message includes second confirmation information, and the second confirmation information is used to indicate that the terminal device accepts or refuses to use the second specified protocol to transmit user plane positioning information.

[0602] In some embodiments, when the second confirmation information represents that the terminal device refuses to use the second specified protocol to transmit user plane positioning information, the fourth message also includes a third cause value, and the third cause value is used to indicate the reason why the terminal device refuses to use the second specified protocol to transmit user plane positioning information.

[0603] In some embodiments, the third cause value includes one of the following: the second specified protocol is not supported, the first transmission protocol is not supported, and the second transmission protocol is not supported.

[0604] In some embodiments, the fourth message also includes the first capability.

[0605] In some embodiments, before the positioning negotiation apparatus 600 receives the third message, the sending unit 610 is further used to send a fifth message to the second core network device; wherein the fifth message is used to obtain the location information of the terminal device, and the fifth message includes the first capability.

[0606] In some embodiments, the second core network device is selected from the at least one second core network device according to the first capability and / or the first specified protocol, and the transmission protocol supported by at least one second core network device for transmitting user plane positioning information by the positioning negotiation device 600.

[0607] In some embodiments, when the first message is used for network registration, the first message includes the first capability; or

[0608] In the case where the first message is used to establish a user plane positioning connection, the first message includes one or more of the following: the first capability, the first designated protocol, and the first confirmation information.

[0609] In some embodiments, the first transmission protocol is a user plane positioning transmission protocol not developed by the Third Generation Partnership Project 3GPP, and the second transmission protocol is a user plane positioning transmission protocol developed by the 3GPP.

[0610] In some embodiments, the transmitting unit and receiving unit may be communication interfaces or transceivers, or input and output interfaces of a communication chip or a system on chip. The processing unit may be one or more processors.

[0611] It should be understood that the positioning negotiation device 600 according to the embodiment of the present application may correspond to the first core network device in the method embodiment of the present application, and the above-mentioned and other operations and / or functions of each unit in the positioning negotiation device 600 are respectively for implementing the corresponding processes of the first core network device in the method 300 shown in Figure 6. For the sake of brevity, they will not be repeated here.

[0612] FIG14 shows a schematic block diagram of a positioning negotiation apparatus 700 according to an embodiment of the present application. As shown in FIG14 , the positioning negotiation apparatus 700 includes:

[0613] The sending unit 710 is configured to send a third message to the first core network device;

[0614] The third message is used to establish a user plane positioning connection, and the third message includes a second specified protocol. The second specified protocol includes a transmission protocol specified by the positioning negotiation apparatus 700 for transmitting user plane positioning information.

[0615] In some embodiments, the second designated protocol comprises one of the following: the first transmission protocol, the second transmission protocol, the first transmission protocol or the second transmission protocol, the first transmission protocol and the second transmission protocol.

[0616] In some embodiments, the positioning negotiation apparatus 700 further includes:

[0617] The receiving unit 720 is configured to receive a fourth message from the first core network device;

[0618] The fourth message includes second confirmation information, and the second confirmation information is used to instruct the terminal device to accept or refuse to use the second specified protocol to transmit user plane positioning information.

[0619] In some embodiments, when the second confirmation information indicates that the terminal device refuses to use the second specified protocol to transmit user plane positioning information, the fourth message also includes a third cause value, and the third cause value is used to indicate the reason why the terminal device refuses to use the second specified protocol to transmit user plane positioning information.

[0620] In some embodiments, the third cause value includes one of the following: the second specified protocol is not supported, the first transmission protocol is not supported, and the second transmission protocol is not supported.

[0621] In some embodiments, the fourth message also includes a first capability, where the first capability is used to indicate a transmission protocol supported by the terminal device for transmitting user plane positioning information.

[0622] In some embodiments, before the positioning negotiation device 700 sends the third message, the receiving unit 720 is also used to receive a fifth message from the first core network device; wherein, the fifth message is used to obtain the location information of the terminal device, and the fifth message includes a first capability, and the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting user plane positioning information.

[0623] In some embodiments, the first capability includes one of the following:

[0624] The terminal device supports transmitting user plane positioning information using a first transmission protocol;

[0625] The terminal device supports transmission of user plane positioning information using a second transmission protocol;

[0626] The terminal device transmits user plane positioning information using a first transmission protocol and a second transmission protocol.

[0627] In some embodiments, the first transmission protocol is a user plane positioning transmission protocol not developed by the Third Generation Partnership Project 3GPP, and the second transmission protocol is a user plane positioning transmission protocol developed by the 3GPP.

[0628] In some embodiments, the sending unit and the receiving unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip.

[0629] It should be understood that the positioning negotiation device 700 according to the embodiment of the present application may correspond to the second core network device in the method embodiment of the present application, and the above-mentioned and other operations and / or functions of each unit in the positioning negotiation device 700 are respectively for implementing the corresponding processes of the second core network device in the method 400 shown in Figure 7. For the sake of brevity, they will not be repeated here.

[0630] Figure 15 is a schematic structural diagram of a communication device 800 provided in an embodiment of the present application. The communication device 800 shown in Figure 15 includes a processor 810, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0631] In some embodiments, as shown in FIG15 , the communication device 800 may further include a memory 820. The processor 810 may call and execute a computer program from the memory 820 to implement the method in the embodiment of the present application.

[0632] The memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .

[0633] In some embodiments, as shown in FIG15 , the communication device 800 may further include a transceiver 830 , and the processor 810 may control the transceiver 830 to communicate with other devices. Specifically, the transceiver 830 may send information or data to other devices, or receive information or data sent by other devices.

[0634] The transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of antennas may be one or more.

[0635] In some embodiments, the processor 810 may implement the functions of a processing unit in a terminal device, or the processor 810 may implement the functions of a processing unit in a core network device, which will not be described in detail here for the sake of brevity.

[0636] In some embodiments, the transceiver 830 may implement the functions of a transmitting unit and a receiving unit in a terminal device, which will not be described in detail here for the sake of brevity.

[0637] In some embodiments, the transceiver 830 may implement the functions of a transmitting unit and a receiving unit in a core network device, which will not be described in detail here for the sake of brevity.

[0638] In some embodiments, the communication device 800 may specifically be a core network device of an embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the core network device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0639] In some embodiments, the communication device 800 may specifically be a terminal device of an embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0640] Figure 16 is a schematic structural diagram of an apparatus according to an embodiment of the present application. The apparatus 900 shown in Figure 16 includes a processor 910, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0641] In some embodiments, as shown in FIG16 , the apparatus 900 may further include a memory 920. The processor 910 may call and execute a computer program from the memory 920 to implement the method in the embodiment of the present application.

[0642] The memory 920 may be a separate device independent of the processor 910 , or may be integrated into the processor 910 .

[0643] In some embodiments, the processor 910 may implement the functions of a processing unit in a terminal device, or the processor 910 may implement the functions of a processing unit in a core network device, which will not be described in detail here for the sake of brevity.

[0644] In some embodiments, the apparatus 900 may further include an input interface 930. The processor 910 may control the input interface 930 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips. Optionally, the processor 910 may be located inside or outside the chip.

[0645] In some embodiments, the input interface 930 may implement the function of a receiving unit in a terminal device, or the input interface 930 may implement the function of a receiving unit in a core network device.

[0646] In some embodiments, the apparatus 900 may further include an output interface 940. The processor 910 may control the output interface 940 to communicate with other devices or chips, specifically, to output information or data to other devices or chips. Optionally, the processor 910 may be located inside or outside the chip.

[0647] In some embodiments, the output interface 940 may implement the function of a sending unit in a terminal device, or the output interface 940 may implement the function of a sending unit in a core network device.

[0648] In some embodiments, the device can be applied to the core network equipment in the embodiments of the present application, and the device can implement the corresponding processes implemented by the core network equipment in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0649] In some embodiments, the apparatus can be applied to the terminal device in the embodiments of the present application, and the apparatus can implement the corresponding processes implemented by the terminal device in the various methods in the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0650] In some embodiments, the device mentioned in the embodiments of the present application may also be a chip, such as a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.

[0651] FIG17 is a schematic block diagram of a communication system 1000 provided in an embodiment of the present application. As shown in FIG17 , the communication system 1000 includes a terminal device 1010 and a core network device 1020 .

[0652] Among them, the terminal device 1010 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the core network device 1020 can be used to implement the corresponding functions implemented by the core network device (first core network device and / or second core network device) in the above method. For the sake of brevity, they will not be repeated here.

[0653] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0654] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. It should be noted that the memory described herein is intended to include but is not limited to these and any other suitable types of memory.

[0655] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0656] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0657] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0658] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0659] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0660] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0661] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. In view of this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0662] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A positioning negotiation method, comprising: The terminal device sends a first message to the first core network device, where the first message is used to perform network registration or establish a user plane positioning connection; The first message includes one or more of the following: a first capability, a first specified protocol, and a first confirmation message; Among them, the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting user plane positioning information, the first specified protocol includes the transmission protocol that the terminal device expects to use for transmitting user plane positioning information, the first confirmation information is used to indicate that the terminal device accepts or refuses to use the second specified protocol to transmit user plane positioning information, and the second specified protocol includes the transmission protocol for transmitting user plane positioning information specified by the first core network device or the second core network device.

2. The method according to claim 1, wherein: The first capability includes one of the following: The terminal device supports transmission of user plane location information using a first transmission protocol; The terminal device supports transmission of user plane location information using a second transmission protocol; The terminal device supports the use of a first transmission protocol and a second transmission protocol to transmit user plane positioning information.

3. The method according to claim 1, wherein: The first specified protocol includes one of the following: First transmission protocol, second transmission protocol, first transmission protocol or second transmission protocol, first transmission protocol and second transmission protocol.

4. The method according to claim 1, wherein: The second designated protocol includes one of the following: First transmission protocol, second transmission protocol, first transmission protocol or second transmission protocol, first transmission protocol and second transmission protocol.

5. The method according to claim 1, wherein: In the case where the first confirmation information is included in the first message, and the first confirmation information indicates that the terminal device refuses to use the second specified protocol to transmit user plane positioning information, the first message also includes a first cause value, wherein the first cause value is used to indicate the reason why the terminal device refuses the request initiated by the network to establish a user plane positioning connection.

6. The method according to claim 5, wherein: The first reason value includes one of the following: the second specified protocol is not supported, the first transmission protocol is not supported, and the second transmission protocol is not supported.

7. The method according to claim 6, wherein: The first message also includes a transmission protocol supported by the terminal device for transmitting user plane positioning information.

8. The method according to any one of claims 1 to 7, wherein: In the case where the first message is used for network registration, the first message includes the first capability; or, In the case where the first message is used to establish a user plane positioning connection, the first message includes one or more of the following: the first capability, the first designated protocol, and the first confirmation information.

9. The method according to any one of claims 1 to 8, further comprising: The terminal device receives a second message from the first core network device, where the second message is used to perform network registration or establish a user plane positioning connection; wherein the second message includes one or more of the following: a second capability, the second specified protocol, and a second cause value; The second capability is used to indicate a transmission protocol supported by the network for transmitting user plane positioning information, and the second cause value is used to indicate the reason why the network rejects the request initiated by the terminal device to establish a user plane positioning connection.

10. The method according to claim 9, wherein: In a case where the first capability is included in the first message, the second message is received by the terminal device after sending the first message, and the second message includes the second capability; or, In the case where the first message includes the first specified protocol, the second message is received by the terminal device after sending the first message, and the second message is used to indicate acceptance of the request for establishing a user plane positioning connection initiated by the terminal device, and the second message carries the second specified protocol; or In the case of including the first designated protocol, the second message is received by the terminal device after sending the first message, the second message is used to indicate the rejection of the request initiated by the terminal device to establish a user plane positioning connection, and the second message carries the second cause value; or, In a case where the first confirmation information is included in the first message, the second message is received by the terminal device before sending the first message, and the second message carries the second designated protocol.

11. The method according to claim 9 or 10, wherein: The second capability includes one of the following: The network does not support user plane positioning capabilities; The network supports transmission of user plane location information using a first transmission protocol; The network supports transmission of user plane location information using a second transmission protocol; The network supports transmission of user plane positioning information using a first transmission protocol and a second transmission protocol.

12. The method according to claim 11, wherein: The second capability characterizes that the network supports user plane positioning capability and that the network supports the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information.

13. The method according to claim 9 or 10, wherein: The second reason value includes at least one of the following: the first specified protocol is not supported, the first transmission protocol is not supported, the second transmission protocol is not supported, and the second core network device is congested.

14. The method according to claim 13, wherein: When the second cause value is carried in the second message, the second message also includes transmission protocol information supported by the network for transmitting user plane positioning information.

15. The method according to any one of claims 9 to 14, wherein: In the case where the second message is used for network registration, the second message includes the second capability; or, In the case where the second message is used to establish a user plane positioning connection, the second message includes one or more of the following: the second capability, the second specified protocol, and the second cause value.

16. The method according to any one of claims 1 to 15, wherein: The second designated protocol is determined by the first core network device or the second core network device.

17. The method of claim 2, 3, 4, 11 or 12, wherein: The first transmission protocol is a user plane positioning transmission protocol not formulated by the Third Generation Partnership Project 3GPP, and the second transmission protocol is a user plane positioning transmission protocol formulated by the 3GPP.

18. The method of claim 2, 3, 4, 11, 12 or 17, wherein: The first transmission protocol is a secure user plane positioning SUPL, and the second transmission protocol is a positioning service-user plane protocol LCS-UPP.

19. A method for positioning negotiation, comprising: The first core network device sends a second message to the terminal device, where the second message is used to perform network registration or establish a user plane positioning connection; The second message includes one or more of the following: a second capability, a second specified protocol, and a second cause value; Among them, the second capability is used to indicate the transmission protocol supported by the network for transmitting user plane positioning information, the second specified protocol includes the transmission protocol for transmitting user plane positioning information specified by the first core network device or the second core network device, and the second reason value is used to indicate the reason why the network rejects the request initiated by the terminal device to establish a user plane positioning connection.

20. The method according to claim 19, wherein: The second capability includes one of the following: The network does not support user plane positioning capabilities; The network supports transmission of user plane location information using a first transmission protocol; The network supports transmission of user plane location information using a second transmission protocol; The network supports transmission of user plane positioning information using a first transmission protocol and a second transmission protocol.

21. The method according to claim 20, wherein: The second capability characterizes that the network supports user plane positioning capability and that the network supports the use of the first transmission protocol and / or the second transmission protocol to transmit user plane positioning information.

22. The method according to claim 19, wherein: The second cause value includes at least one of the following: the first specified protocol is not supported, the first transmission protocol is not supported, the second transmission protocol is not supported, and the second core network device is congested; The first specified protocol includes the transmission protocol that the terminal device expects to use for transmitting user plane positioning information. Transmission agreement.

23. The method according to claim 22, wherein: When the second cause value is carried in the second message, the second message also includes transmission protocol information supported by the network for transmitting user plane positioning information.

24. The method according to claim 19, wherein: The second designated protocol includes one of the following: the first transmission protocol, the second transmission protocol, the first transmission protocol or the second transmission protocol, the first transmission protocol and the second transmission protocol.

25. The method of claim 19, wherein: The second designated protocol is determined by the first core network device or the second core network device.

26. The method according to any one of claims 19 to 25, wherein: In the case where the second message is used for network registration, the second message includes the second capability; or, In the case where the second message is used to establish a user plane positioning connection, the second message includes one or more of the following: the second capability, the second specified protocol, and the second cause value.

27. The method according to any one of claims 19 to 26, further comprising: The first core network device receives a first message from the terminal device, where the first message is used to perform network registration or establish a user plane positioning connection; The first message includes one or more of the following: a first capability, a first specified protocol, and a first confirmation message; Among them, the first capability is used to indicate the transmission protocol supported by the terminal device for transmitting user plane positioning information, the first specified protocol includes the transmission protocol that the terminal device expects to use for transmitting user plane positioning information, and the first confirmation information is used to indicate that the terminal device accepts or refuses to use the second specified protocol to transmit user plane positioning information.

28. The method according to claim 27, wherein: In a case where the first capability is included in the first message, the second message is sent by the first core network device after receiving the first message, and the second message includes the second capability; or, In the case where the first specified protocol is included in the first message, the second message is sent by the first core network device after receiving the first message, and the second message is used to indicate acceptance of the request for establishing a user plane positioning connection initiated by the terminal device, and the second message carries the second specified protocol; or, in the case where the first specified protocol is included in the first message, the second message is sent by the first core network device after receiving the first message, and the second message is used to indicate rejection of the request for establishing a user plane positioning connection initiated by the terminal device, and the second message carries the second reason value; or, In the case where the first confirmation information is included in the first message, the second message is sent by the first core network device before receiving the first message, and the second message carries the second specified protocol.

29. The method according to claim 27 or 28, wherein: The first capability includes one of the following: The terminal device supports transmission of user plane location information using a first transmission protocol; The terminal device supports transmission of user plane location information using a second transmission protocol; The terminal device transmits user plane positioning information using a first transmission protocol and a second transmission protocol.

30. The method according to claim 27 or 28, wherein: The first designated protocol includes one of the following: a first transmission protocol, a second transmission protocol, the first transmission protocol or the second transmission protocol, the first transmission protocol and the second transmission protocol.

31. The method according to claim 27 or 28, wherein: When the first confirmation information is included in the first message, and the first confirmation information indicates that the terminal device refuses to use the second specified protocol to transmit user plane positioning information, the first message also includes a first cause value; wherein the first cause value is used to indicate the reason why the terminal device refuses the request initiated by the network to establish a user plane positioning connection.

32. The method according to claim 31, wherein: The first reason value includes one of the following: the second specified protocol is not supported, the first transmission protocol is not supported, and the second transmission protocol is not supported.

33. The method of claim 32, wherein: The first message also includes a transmission protocol supported by the terminal device for transmitting user plane positioning information.

34. The method according to any one of claims 27 to 33, further comprising: The first core network device according to the first capability and / or the first specified protocol, and at least one second A transmission protocol for transmitting user plane positioning information supported by the core network device, selecting a second core network device to establish a user plane positioning connection with the terminal device from the at least one second core network device; and / or, The first core network device determines the second designated protocol based on the first capability and / or the first designated protocol, and a transmission protocol supported by at least one second core network device for transmitting user plane positioning information.

35. The method according to any one of claims 27 to 33, wherein: Before the first core network device sends the second message, the method further includes: The first core network device receives a third message from the second core network device; wherein the third message is used to establish a user plane positioning connection, and the third message includes the second specified protocol.

36. The method of claim 35, further comprising: The first core network device sends a fourth message to the second core network device; The fourth message includes second confirmation information, and the second confirmation information is used to indicate that the terminal device accepts or refuses to use the second specified protocol to transmit user plane positioning information.

37. The method of claim 36, wherein: In the case where the second confirmation information indicates that the terminal device refuses to use the second specified protocol to transmit user plane positioning information, the fourth message also includes a third cause value, and the third cause value is used to indicate the reason why the terminal device refuses to use the second specified protocol to transmit user plane positioning information.

38. The method of claim 37, wherein: The third reason value includes one of the following: the second specified protocol is not supported, the first transmission protocol is not supported, and the second transmission protocol is not supported.

39. The method of claim 38, wherein: The fourth message also includes the first capability.

40. The method according to any one of claims 35 to 39, wherein: Before the first core network device receives the third message, the method further includes: The first core network device sends a fifth message to the second core network device; wherein the fifth message is used to obtain location information of the terminal device, and the fifth message includes the first capability.

41. The method according to any one of claims 35 to 40, wherein: The second core network device is selected from at least one second core network device by the first core network device based on the first capability and / or the first specified protocol, and a transmission protocol supported by at least one second core network device for transmitting user plane positioning information.

42. The method according to any one of claims 27 to 41, wherein: In the case where the first message is used for network registration, the first message includes the first capability; or, In the case where the first message is used to establish a user plane positioning connection, the first message includes one or more of the following: the first capability, the first designated protocol, and the first confirmation information.

43. The method of claim 20, 21, 22, 23, 24, 29, 30, 32, 33, 38 or 39, wherein: The first transmission protocol is a user plane positioning transmission protocol not formulated by the Third Generation Partnership Project 3GPP, and the second transmission protocol is a user plane positioning transmission protocol formulated by the 3GPP.

44. The method of claim 20, 21, 22, 23, 24, 29, 30, 32, 33, 38, 39 or 43, wherein: The first transmission protocol is a secure user plane positioning SUPL, and the second transmission protocol is a positioning service-user plane protocol LCS-UPP.

45. A method for positioning negotiation, comprising: The second core network device sends a third message to the first core network device; The third message is used to establish a user plane positioning connection, the third message includes a second specified protocol, and the second specified protocol includes a transmission protocol specified by the second core network device for transmitting user plane positioning information.

46. ​​The method of claim 45, wherein: The second designated protocol includes one of the following: the first transmission protocol, the second transmission protocol, the first transmission protocol or the second transmission protocol, the first transmission protocol and the second transmission protocol.

47. The method according to claim 45 or 46, further comprising: The second core network device receives a fourth message from the first core network device; The fourth message includes second confirmation information, and the second confirmation information is used to indicate that the terminal device accepts or Refuse to use the second designated protocol to transmit user plane positioning information.

48. The method of claim 47, wherein: In the case where the second confirmation information indicates that the terminal device refuses to use the second specified protocol to transmit user plane positioning information, the fourth message also includes a third cause value, and the third cause value is used to indicate the reason why the terminal device refuses to use the second specified protocol to transmit user plane positioning information.

49. The method of claim 48, wherein: The third reason value includes one of the following: the second specified protocol is not supported, the first transmission protocol is not supported, and the second transmission protocol is not supported.

50. The method of claim 49, wherein: The fourth message also includes a first capability, where the first capability is used to indicate a transmission protocol supported by the terminal device for transmitting user plane positioning information.

51. A method according to any one of claims 45 to 50, wherein: Before the second core network device sends the third message, the method further includes: The second core network device receives a fifth message from the first core network device; wherein the fifth message is used to obtain location information of the terminal device, and the fifth message includes a first capability, and the first capability is used to indicate a transmission protocol supported by the terminal device for transmitting user plane positioning information.

52. The method according to claim 50 or 51, wherein: The first capability includes one of the following: The terminal device supports transmission of user plane location information using a first transmission protocol; The terminal device supports transmission of user plane location information using a second transmission protocol; The terminal device transmits user plane positioning information using a first transmission protocol and a second transmission protocol.

53. The method of claim 46, 49, 50 or 52, wherein: The first transmission protocol is a user plane positioning transmission protocol not formulated by the Third Generation Partnership Project 3GPP, and the second transmission protocol is a user plane positioning transmission protocol formulated by the 3GPP.

54. The method of claim 46, 49, 50, 52 or 53, wherein: The first transmission protocol is a secure user plane positioning SUPL, and the second transmission protocol is a positioning service-user plane protocol LCS-UPP.

55. A positioning negotiation device, comprising: A sending unit, configured to send a first message to a first core network device, where the first message is used to perform network registration or establish a user plane positioning connection; The first message includes one or more of the following: a first capability, a first specified protocol, and a first confirmation message; Among them, the first capability is used to indicate the transmission protocol supported by the positioning negotiation device for transmitting user plane positioning information, the first specified protocol includes the transmission protocol for transmitting user plane positioning information that the positioning negotiation device expects to use, the first confirmation information is used to indicate that the positioning negotiation device accepts or refuses to use the second specified protocol to transmit user plane positioning information, and the second specified protocol includes the transmission protocol for transmitting user plane positioning information specified by the first core network device or the second core network device.

56. A positioning negotiation device, comprising: A sending unit, configured to send a second message to a terminal device, wherein the second message is used to perform network registration or establish a user plane positioning connection; The second message includes one or more of the following: a second capability, a second specified protocol, and a second cause value; Among them, the second capability is used to indicate the transmission protocol supported by the network for transmitting user plane positioning information, the second specified protocol includes the transmission protocol for transmitting user plane positioning information specified by the positioning negotiation device or the second core network device, and the second reason value is used to indicate the reason why the network rejects the request initiated by the terminal device to establish a user plane positioning connection.

57. A positioning negotiation device, comprising: A sending unit, configured to send a third message to the first core network device; The third message is used to establish a user plane positioning connection, the third message includes a second specified protocol, and the second specified protocol includes a transmission protocol specified by the positioning negotiation device for transmitting user plane positioning information.

58. A terminal device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the method according to any one of claims 1 to 18 when executed by the processor.

59. A core network device, the core network device being a first core network device, wherein: The core network device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps in the method as described in any one of claims 19 to 44 when executed by the processor.

60. A core network device, the core network device being a second core network device, wherein: The core network device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps in the method as described in any one of claims 45 to 54 when executed by the processor.

61. A computer-readable storage medium, wherein: The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps in the method as claimed in any one of claims 1 to 18; or, implements the steps in the method as claimed in any one of claims 19 to 44; or, implements the steps in the method as claimed in any one of claims 45 to 54.

Images