Positioning method and apparatus

Abstract

This application provides a positioning method and apparatus, relating to the field of communication technology. In this method, the Location Management Center (LMC) sends a registration request to a core network element, requesting registration with the core network element. The core network element, based on the registration request, sends a registration response to the LMC including first indication information. This first indication information indicates the positioning types supported by the LMC or whether the LMC supports a first positioning type. Thus, during the LMC registration process, the core network indicates the positioning types supported by the LMC, enabling the LMC to subsequently perform the corresponding positioning functions.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a positioning method and apparatus. Background Technology

[0002] To enable terminal location tracking, a location management function (LMF) entity can be deployed in the core network. The LMF entity can receive location requests from the access and mobility management function (AMF) entity, determine the method to be used for location measurement (this decision can be based on the capabilities of the terminal and the network, or on information contained in the location request, etc.), determine the network device to locate the terminal and request auxiliary information needed for location tracking from the network device or the terminal, send the auxiliary information needed for location tracking to the terminal or the network device, request measurement information from the terminal or the network device, and calculate the terminal's location, etc.

[0003] To enable faster terminal location, some or all of the LMF's functions can be deployed on network devices. An LMF deployed on a network device is called a local LMF (LLMF) or a location management component (LMC). The LMC coexists with the LMF in the core network. The LMC is not essential to network devices and is therefore only deployed on a subset of them. Currently, how to specifically implement the LMC's functions is a problem that urgently needs to be solved. Summary of the Invention

[0004] This application provides a positioning method and apparatus to solve the problem of realizing the function of LMC.

[0005] To achieve the above objectives, the embodiments of this application provide the following technical solutions:

[0006] Firstly, a positioning method is provided, comprising: an LMC sending a registration request to a core network element, the registration request being used to request registration with the core network element; the LMC receiving a registration response from the core network element, the registration response including first indication information, the first indication information being used to indicate the positioning types supported by the LMC; or, the first indication information being used to indicate whether the LMC supports a first positioning type. According to the method provided in the first aspect, during the LMC registration process, the core network can indicate the positioning types supported by the LMC, thereby enabling the LMC to subsequently perform corresponding positioning functions.

[0007] In one possible implementation, the LMC supports one or more of the following positioning types: NI-LR, MT-LR, MO-LR, and RI-LR. In this possible implementation, the LMC can support multiple positioning types, thereby expanding the application scope of this application.

[0008] In one possible implementation, the first positioning type includes any one of the following positioning types: NI-LR, MT-LR, MO-LR, and RI-LR. In this possible implementation, the LMF does not support the new positioning type RI-LR, while the LMC can support RI-LR. By authorizing the LMC with the RI-LR positioning type, the LMC's functionality can be made within the jurisdiction of the core network.

[0009] In one possible implementation, the core network element is an AMF or an LMF.

[0010] Secondly, a positioning method is provided, comprising: a core network element receiving a registration request from an LMC, the registration request being used to request registration with the core network element; the core network element sending a registration response to the LMC, the registration response including first indication information, the first indication information being used to indicate the positioning types supported by the LMC; or, the first indication information being used to indicate whether the LMC supports a first positioning type. According to the method provided in the second aspect, during the LMC registration process, the core network can indicate the positioning types supported by the LMC, thereby enabling the LMC to subsequently perform corresponding positioning functions.

[0011] In one possible implementation, the LMC supports one or more of the following positioning types: NI-LR, MT-LR, MO-LR, and RI-LR. In this possible implementation, the LMC can support multiple positioning types, thereby expanding the application scope of this application.

[0012] In one possible implementation, the first positioning type includes any one of the following positioning types: NI-LR, MT-LR, MO-LR, and RI-LR. In this possible implementation, the LMF does not support the new positioning type RI-LR, while the LMC can support RI-LR. By authorizing the LMC with the RI-LR positioning type, the LMC's functionality can be made within the jurisdiction of the core network.

[0013] In one possible implementation, the core network element is an AMF or an LMF.

[0014] Thirdly, a positioning method is provided, comprising: the LMC sending a registration request to a core network element, the registration request being used to request registration with the core network element; the LMC receiving a registration response from the core network element, the registration response including information on M1 network devices supporting a second positioning type, where M1 is an integer greater than 0; and the LMC sending second indication information corresponding to each of the M1 network devices, the second indication information being used to indicate that the corresponding network device supports the second positioning type. According to the method provided in the third aspect, by sending second indication information to network devices supporting the second positioning type, the LMC can authorize network devices to use the second positioning type to locate the terminal when positioning is required, thereby solving the problem of positioning initiated by network devices without LMC deployment.

[0015] In one possible implementation, the method further includes: the LMC sending its location information to each of the M1 network devices. In this possible implementation, the network devices can obtain the location of the LMC in order to subsequently initiate a location request to the LMC.

[0016] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0017] In one possible implementation, the method further includes: the LMC receiving update information from the core network element, the update information indicating whether the information of M2 network devices supporting the second positioning type has changed, where M2 is an integer greater than 0. In this possible implementation, the LMC can obtain information about network devices supporting the second positioning type's information changes.

[0018] In one possible implementation, the method further includes: the LMC sending third indication information to a first network device, the third indication information indicating whether the first network device supports the second positioning type, wherein the first network device is any one of the M2 network devices. In this possible implementation, the LMC can update the information regarding whether the network devices support the second positioning type, so that the network devices can send positioning requests based on the updated information.

[0019] In one possible implementation, the second location type is RI-LR.

[0020] Fourthly, a positioning method is provided, comprising: a network device receiving second indication information from an LMC (Local Management Center), the second indication information indicating that the network device supports a second positioning type; and when the network device needs to locate a service terminal, the network device sending a positioning request to the LMC. According to the method provided in the fourth aspect, by sending the second indication information to a network device that supports the second positioning type, the LMC can authorize the network device to use the second positioning type to locate the terminal when positioning is required, thereby solving the problem of network devices without an LMC initiating positioning.

[0021] In one possible implementation, the method further includes: the network device receiving the location information of the LMC from the LMC. In this possible implementation, the network device can obtain the location of the LMC in order to subsequently initiate a location request to the LMC.

[0022] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0023] In one possible implementation, the method further includes: the network device receiving third indication information from the LMC, the third indication information indicating whether the network device supports the second positioning type. In this possible implementation, the LMC can update the information in the network device regarding whether the network device supports the second positioning type, so that the network device can send a positioning request based on the updated information.

[0024] In one possible implementation, the second location type is RI-LR.

[0025] Fifthly, a positioning method is provided, comprising: a core network element determining second indication information corresponding to M3 network devices, the second indication information indicating that the corresponding network device supports a second positioning type, where M3 is an integer greater than 0; the core network element sending the second indication information corresponding to each of the M3 network devices. According to the method provided in the fifth aspect, by sending the second indication information to network devices that support the second positioning type, the core network element can authorize the network devices to use the second positioning type to locate the terminal when positioning is required, thereby solving the problem of positioning initiated by network devices without LMC deployment.

[0026] In one possible implementation, the method further includes: the core network element sending the LMC location information to each of the M3 network devices. In this possible implementation, the network devices can obtain the LMC location in order to subsequently initiate a location request to the LMC.

[0027] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0028] In one possible implementation, the method further includes: the core network element sending third indication information to a first network device, the third indication information indicating whether the first network device supports the second positioning type, wherein the first network device is any one of M4 network devices, and the M4 network devices are network devices whose information regarding whether they support the second positioning type has changed, where M4 is an integer greater than 0. In this possible implementation, the core network element can update the information regarding whether network devices support the second positioning type, so that the network devices can send positioning requests based on the updated information.

[0029] In one possible implementation, the second location type is RI-LR.

[0030] A sixth aspect provides a positioning method, comprising: a network device receiving second indication information from a core network element, the second indication information indicating that the network device supports a second positioning type; and when the network device needs to locate a service terminal, the network device sending a positioning request to an LMC (Local Management Center). According to the method provided in the sixth aspect, by sending the second indication information to a network device that supports the second positioning type, the core network element can authorize the network device to use the second positioning type to locate the terminal when it needs to locate the terminal, thereby solving the problem of network devices without deployed LMC initiating positioning.

[0031] In one possible implementation, the method further includes: the network device receiving the location information of the LMC from the core network element. In this possible implementation, the network device can obtain the location of the LMC in order to subsequently initiate a location request to the LMC.

[0032] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0033] In one possible implementation, the method further includes: the network device receiving third indication information from the core network element, the third indication information indicating whether the network device supports the second positioning type. In this possible implementation, the core network element can update the information in the network device regarding whether the network device supports the second positioning type, so that the network device can send a positioning request based on the updated information.

[0034] In one possible implementation, the second location type is RI-LR.

[0035] A seventh aspect provides a positioning method, comprising: an LMC sending a registration request to a core network element, the registration request being used to request registration with the core network element; the LMC receiving a registration response from the core network element, the registration response including information on N1 cells supporting a second positioning type, the N1 cells belonging to M5 network devices, where N1 and M5 are both integers greater than 0; the LMC sending fourth indication information corresponding to each of the M5 network devices, the fourth indication information being used to indicate one or more cells supporting the second positioning type, the cell indicated by the fourth indication information belonging to the network device corresponding to the fourth indication information. According to the method provided in the seventh aspect, by sending fourth indication information to the network devices to which cells supporting the second positioning type belong, the LMC can authorize network devices to use the second positioning type to locate terminals when it is necessary to locate terminals in certain cells, thereby solving the problem of network devices without deployed LMC initiating positioning.

[0036] In one possible implementation, the registration response may also include information about the M5 network devices.

[0037] In one possible implementation, the method further includes: the LMC sending its location information to each of the M5 network devices. In this possible implementation, the network devices can obtain the location of the LMC in order to subsequently initiate a location request to the LMC.

[0038] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0039] In one possible implementation, the method further includes: the LMC receiving update information from the core network element, the update information indicating whether it supports information changes in N2 cells of the second positioning type, where N2 is an integer greater than 0. In this possible implementation, the LMC can obtain information on whether it supports information changes in cells of the second positioning type.

[0040] In one possible implementation, the method further includes: the LMC sending fifth indication information to the second network device, the fifth indication information indicating whether a first cell of the second network device supports the second positioning type, wherein the first cell is any one or more cells from the N2 cells. In this possible implementation, the LMC can update the information in the network device regarding whether a cell supports the second positioning type, so that the network device can send a positioning request based on the updated information.

[0041] In one possible implementation, the second location type is RI-LR.

[0042] Eighthly, a positioning method is provided, comprising: a network device receiving fourth indication information from an LMC (Local Management Center), the fourth indication information indicating one or more cells supporting a second positioning type, the cells indicated by the fourth indication information belonging to the network device; and when the network device needs to locate a terminal in a cell supporting the second positioning type, the network device sending a positioning request to the LMC. According to the method provided in the eighth aspect, by sending the fourth indication information to the network device belonging to a cell supporting the second positioning type, the LMC can authorize the network device to use the second positioning type to locate terminals when it needs to locate terminals in certain cells, thereby solving the problem of network devices without an LMC initiating positioning.

[0043] In one possible implementation, the method further includes: the network device receiving the location information of the LMC from the LMC. In this possible implementation, the network device can obtain the location of the LMC in order to subsequently initiate a location request to the LMC.

[0044] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0045] In one possible implementation, the method further includes: the network device receiving fifth indication information from the LMC, the fifth indication information indicating whether a first cell of the network device supports the second positioning type, wherein the first cell is any one or more cells from N2 cells, and the N2 cells are cells whose information regarding whether they support the second positioning type has changed, where N2 is an integer greater than 0. In this possible implementation, the LMC can update the information in the network device regarding whether cells support the second positioning type, so that the network device can send a positioning request based on the updated information.

[0046] In one possible implementation, the second location type is RI-LR.

[0047] A ninth aspect provides a positioning method, comprising: a core network element determining fourth indication information corresponding to M6 network devices, the fourth indication information being used to indicate one or more cells supporting a second positioning type, the cell indicated by the fourth indication information belonging to the network device corresponding to the fourth indication information, and M6 being an integer greater than 0; the core network element sending the fourth indication information corresponding to each of the M6 ​​network devices. According to the method provided in the ninth aspect, by sending the fourth indication information to the network devices belonging to cells supporting the second positioning type, the core network element can authorize the network devices to use the second positioning type to locate terminals when it is necessary to locate terminals in certain cells, thereby solving the problem of positioning initiated by network devices without LMC deployment.

[0048] In one possible implementation, the method further includes: the core network element sending the location information of the LMC to each of the M6 ​​network devices. In this possible implementation, the network devices can obtain the location of the LMC in order to subsequently initiate a location request to the LMC.

[0049] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0050] In one possible implementation, the method further includes: the core network element sending fifth indication information to the second network device, the fifth indication information indicating whether a first cell of the second network device supports the second positioning type, wherein the first cell is any one or more cells from N3 cells, and the N3 cells are cells whose information regarding whether they support the second positioning type has changed, and N3 is an integer greater than 0. In this possible implementation, the core network element can update the information in the network device regarding whether cells support the second positioning type, so that the network device can send a positioning request based on the updated information.

[0051] In one possible implementation, the second location type is RI-LR.

[0052] A tenth aspect provides a positioning method, comprising: a network device receiving fourth indication information from a core network element, the fourth indication information indicating one or more cells supporting a second positioning type, the cells indicated by the fourth indication information belonging to the network device; and when the network device needs to locate a terminal in a cell supporting the second positioning type, the network device sending a positioning request to an LMC (Local Management Center). According to the method provided in the tenth aspect, by sending the fourth indication information to the network device belonging to a cell supporting the second positioning type, the core network element can authorize the network device to use the second positioning type to locate terminals in certain cells when positioning is required, thereby solving the problem of network devices without deployed LMC initiating positioning.

[0053] In one possible implementation, the method further includes: the network device receiving the location information of the LMC from the core network element. In this possible implementation, the network device can obtain the location of the LMC in order to subsequently initiate a location request to the LMC.

[0054] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0055] In one possible implementation, the method further includes: the network device receiving fifth indication information from the core network element, the fifth indication information indicating whether a first cell of the network device supports the second positioning type, wherein the first cell is any one or more cells from N3 cells, and the N3 cells are cells whose information regarding whether they support the second positioning type has changed, where N3 is an integer greater than 0. In this possible implementation, the core network element can update the information in the network device regarding whether cells support the second positioning type, so that the network device can send a positioning request based on the updated information.

[0056] In one possible implementation, the second location type is RI-LR.

[0057] Eleventhly, a positioning method is provided, comprising: the LMC sending a registration request to a core network element, the registration request being used to request registration with the core network element; the LMC receiving a registration response from the core network element, the registration response including information on Q1 terminals supporting a second positioning type, the Q1 terminals accessing M7 network devices, where Q1 and M7 are both integers greater than 0; the LMC sending sixth indication information corresponding to each of the M7 network devices, the sixth indication information being used to indicate one or more terminals supporting the second positioning type, the one or more terminals indicated by the sixth indication information accessing the network device corresponding to the sixth indication information. According to the method provided in the eleventh aspect, by sending sixth indication information to network devices serving terminals supporting the second positioning type, the LMC can authorize network devices to use the second positioning type to locate terminals when positioning of certain terminals is required, thereby solving the problem of network devices without deployed LMC initiating positioning.

[0058] In one possible implementation, the registration response also includes information about the M7 network devices.

[0059] In one possible implementation, the method further includes: the LMC sending its location information to each of the M7 network devices. In this possible implementation, the network devices can obtain the location of the LMC in order to subsequently initiate a location request to the LMC.

[0060] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0061] In one possible implementation, the method further includes: the LMC receiving update information from the core network element, the update information indicating whether it supports the relevant information of Q2 terminals whose information has changed for the second positioning type, where Q2 is an integer greater than 0. In this possible implementation, the LMC can obtain information on whether it supports terminals whose information has changed for the second positioning type.

[0062] In one possible implementation, the method further includes: the LMC sending seventh indication information to the third network device, the seventh indication information indicating whether a first terminal accessing the third network device supports the second positioning type, wherein the first terminal is any one or more of the Q2 terminals. In this possible implementation, the LMC can update the information on whether the terminals in the network device support the second positioning type, so that the network device can send a positioning request based on the updated information.

[0063] In one possible implementation, the second location type is RI-LR.

[0064] In a twelfth aspect, a positioning method is provided, comprising: a network device receiving sixth indication information from an LMC (Local Management Center), the sixth indication information indicating one or more terminals supporting a second positioning type, the one or more terminals indicated by the sixth indication information being connected to the network device; and when the network device needs to locate a terminal supporting the second positioning type, the network device sending a positioning request to the LMC. According to the method provided in the twelfth aspect, by sending the sixth indication information to a network device serving a terminal supporting the second positioning type, the LMC can authorize the network device to use the second positioning type to locate terminals when positioning is required, thereby solving the problem of network devices without an LMC initiating positioning.

[0065] In one possible implementation, the method further includes: the network device receiving the location information of the LMC from the LMC. In this possible implementation, the network device can obtain the location of the LMC in order to subsequently initiate a location request to the LMC.

[0066] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0067] In one possible implementation, the method further includes: the network device receiving seventh indication information from the LMC, the seventh indication information indicating whether a first terminal accessing the network device supports the second positioning type, wherein the first terminal is any one or more of Q2 terminals, and the Q2 terminals are terminals whose information regarding whether they support the second positioning type has changed, where Q2 is an integer greater than 0. In this possible implementation, the LMC can update the information regarding whether terminals in the network device support the second positioning type, so that the network device can send a positioning request based on the updated information.

[0068] In one possible implementation, the second location type is RI-LR.

[0069] In a thirteenth aspect, a positioning method is provided, comprising: a core network element determining sixth indication information corresponding to M8 network devices, the sixth indication information being used to indicate one or more terminals supporting a second positioning type, the one or more terminals indicated by the sixth indication information accessing the network device corresponding to the sixth indication information, where M8 is an integer greater than 0; the core network element sending the sixth indication information corresponding to each of the M8 network devices. According to the method provided in the thirteenth aspect, by sending the sixth indication information to network devices serving terminals supporting the second positioning type, the core network element can authorize network devices to use the second positioning type to locate terminals when positioning of certain terminals is required, thereby solving the problem of positioning initiated by network devices without LMC deployment.

[0070] In one possible implementation, the method further includes: the core network element sending the location information of the LMC to each of the M8 network devices. In this possible implementation, the network devices can obtain the location of the LMC in order to subsequently initiate a location request to the LMC.

[0071] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0072] In one possible implementation, the method further includes: the core network element sending seventh indication information to the third network device, the seventh indication information indicating whether a first terminal accessing the third network device supports the second positioning type, wherein the first terminal is any one or more of Q3 terminals, and the Q3 terminals are terminals whose information regarding whether they support the second positioning type has changed, and Q3 is an integer greater than 0. In this possible implementation, the core network element can update the information regarding whether terminals in the network device support the second positioning type, so that the network device can send a positioning request based on the updated information.

[0073] In one possible implementation, the sixth indication information is carried in the initial context establishment request. In this possible implementation, a method for implementing the sixth indication information is provided.

[0074] In one possible implementation, the second location type is RI-LR.

[0075] In one possible implementation, whether the terminal supports the second positioning type information is reported by the terminal to the core network element, or whether the terminal supports the second positioning type information is stored in the terminal's subscription information in the core network element. This possible implementation provides two methods for the core network element to obtain whether the terminal supports the second positioning type information.

[0076] In a fourteenth aspect, a positioning method is provided, comprising: a network device receiving sixth indication information from a core network element, the sixth indication information being used to indicate one or more terminals supporting a second positioning type, the one or more terminals indicated by the sixth indication information being connected to the network device; and when the network device needs to locate a terminal supporting the second positioning type, the network device sending a positioning request to an LMC (Local Management Center). According to the method provided in the fourteenth aspect, by sending the sixth indication information to a network device serving a terminal supporting the second positioning type, the core network element can authorize the network device to use the second positioning type to locate terminals when positioning is required, thereby solving the problem of network devices without deployed LMC initiating positioning.

[0077] In one possible implementation, the method further includes: the network device receiving the location information of the LMC from the core network element. In this possible implementation, the network device can obtain the location of the LMC in order to subsequently initiate a location request to the LMC.

[0078] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0079] In one possible implementation, the method further includes: the network device receiving seventh indication information from the core network element, the seventh indication information indicating whether a first terminal accessing the network device supports the second positioning type, wherein the first terminal is any one or more of Q3 terminals, and the Q3 terminals are terminals whose information regarding whether they support the second positioning type has changed, and Q3 is an integer greater than 0. In this possible implementation, the core network element can update the information regarding whether terminals in the network device support the second positioning type, so that the network device can send a positioning request based on the updated information.

[0080] In one possible implementation, the sixth indication information is carried in the initial context establishment request. In this possible implementation, a method for implementing the sixth indication information is provided.

[0081] In one possible implementation, the second location type is RI-LR.

[0082] In a fifteenth aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to send a registration request to a core network element via the communication unit, the registration request being used to request registration with the core network element; the processing unit is further configured to receive a registration response from the core network element via the communication unit, the registration response including first indication information, the first indication information being used to indicate a positioning type supported by the positioning device; or, the first indication information being used to indicate whether the positioning device supports a first positioning type.

[0083] In one possible implementation, the positioning device supports one or more of the following positioning types: NI-LR, MT-LR, MO-LR, RI-LR.

[0084] In one possible implementation, the first positioning type includes any one of the following positioning types: NI-LR, MT-LR, MO-LR, RI-LR.

[0085] In one possible implementation, the core network element is an AMF or an LMF.

[0086] In a sixteenth aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to receive a registration request from an LMC via the communication unit, the registration request being used to request registration with the positioning device; the processing unit is further configured to send a registration response to the LMC via the communication unit, the registration response including first indication information, the first indication information being used to indicate a positioning type supported by the LMC; or, the first indication information being used to indicate whether the LMC supports a first positioning type.

[0087] In one possible implementation, the LMC supports one or more of the following positioning types: NI-LR, MT-LR, MO-LR, RI-LR.

[0088] In one possible implementation, the first positioning type includes any one of the following positioning types: NI-LR, MT-LR, MO-LR, RI-LR.

[0089] In one possible implementation, the positioning device is an AMF or an LMF.

[0090] In a seventeenth aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to send a registration request to a core network element via the communication unit, the registration request being used to request registration with the core network element; the processing unit is further configured to receive a registration response from the core network element via the communication unit, the registration response including information on M1 network devices supporting a second positioning type, M1 being an integer greater than 0; the processing unit is further configured to send second indication information corresponding to each of the M1 network devices via the communication unit, the second indication information being used to indicate that the corresponding network device supports the second positioning type.

[0091] In one possible implementation, the processing unit is further configured to send the location information of the positioning device to each of the M1 network devices via the communication unit.

[0092] In one possible implementation, the location information of the positioning device is the identifier of the network device where the positioning device is located or the identifier of the positioning device.

[0093] In one possible implementation, the processing unit is further configured to receive update information from the core network element via the communication unit, the update information being used to indicate whether the information of M2 network devices of the second positioning type has changed, where M2 is an integer greater than 0.

[0094] In one possible implementation, the processing unit is further configured to send third indication information to the first network device through the communication unit, the third indication information being used to indicate whether the first network device supports the second positioning type, wherein the first network device is any one of the M2 network devices.

[0095] In one possible implementation, the second location type is RI-LR.

[0096] Eighteenthly, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to receive second indication information from an LMC via the communication unit, the second indication information being used to indicate that the positioning device supports a second positioning type; the processing unit is further configured to send a positioning request to the LMC via the communication unit when the positioning device needs to locate a service terminal.

[0097] In one possible implementation, the processing unit is further configured to receive the location information of the LMC from the LMC via the communication unit.

[0098] In one possible implementation, the location information of the LMC is the identifier of the positioning device where the LMC is located or the identifier of the LMC.

[0099] In one possible implementation, the processing unit is further configured to receive third indication information from the LMC via the communication unit, the third indication information being used to indicate whether the positioning device supports the second positioning type.

[0100] In one possible implementation, the second location type is RI-LR.

[0101] In a nineteenth aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to determine second indication information corresponding to M3 network devices, the second indication information being used to indicate that the corresponding network device supports a second positioning type, wherein M3 is an integer greater than 0; the communication unit is configured to send the corresponding second indication information to each of the M3 network devices.

[0102] In one possible implementation, the communication unit is further configured to send LMC location information to each of the M3 network devices.

[0103] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0104] In one possible implementation, the communication unit is further configured to send third indication information to the first network device, the third indication information being used to indicate whether the first network device supports the second positioning type, wherein the first network device is any one of M4 network devices, the M4 network devices are network devices whose information on whether they support the second positioning type changes, and M4 is an integer greater than 0.

[0105] In one possible implementation, the second location type is RI-LR.

[0106] In a twentieth aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to receive second indication information from a core network element via the communication unit, the second indication information being used to indicate that the positioning device supports a second positioning type; the processing unit is further configured to send a positioning request to an LMC via the communication unit when the positioning device needs to locate a terminal it serves.

[0107] In one possible implementation, the processing unit is further configured to receive the location information of the LMC from the core network element via the communication unit.

[0108] In one possible implementation, the location information of the LMC is the identifier of the positioning device where the LMC is located or the identifier of the LMC.

[0109] In one possible implementation, the processing unit is configured to receive third indication information from the core network element via the communication unit, the third indication information being used to indicate whether the positioning device supports the second positioning type.

[0110] In one possible implementation, the second location type is RI-LR.

[0111] In a twenty-first aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to send a registration request to a core network element via the communication unit, the registration request being used to request registration with the core network element; the processing unit is further configured to receive a registration response from the core network element via the communication unit, the registration response including information on N1 cells supporting a second positioning type, the N1 cells belonging to M5 network devices, where N1 and M5 are both integers greater than 0; the processing unit is further configured to send fourth indication information corresponding to each of the M5 network devices via the communication unit, the fourth indication information being used to indicate one or more cells supporting the second positioning type, the cell indicated by the fourth indication information belonging to the network device corresponding to the fourth indication information.

[0112] In one possible implementation, the registration response may also include information about the M5 network devices.

[0113] In one possible implementation, the processing unit is further configured to send the location information of the positioning device to each of the M5 network devices via the communication unit.

[0114] In one possible implementation, the location information of the positioning device is the identifier of the network device where the positioning device is located or the identifier of the positioning device.

[0115] In one possible implementation, the processing unit is further configured to receive update information from the core network element via the communication unit, the update information being used to indicate whether the information of N2 cells that have changed according to the second positioning type is supported, where N2 is an integer greater than 0.

[0116] In one possible implementation, the processing unit is further configured to send fifth indication information to the second network device through the communication unit, the fifth indication information being used to indicate whether the first cell of the second network device supports the second positioning type, wherein the first cell is any one or more of the N2 cells.

[0117] In one possible implementation, the second location type is RI-LR.

[0118] In a twenty-second aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to receive fourth indication information from an LMC via the communication unit, the fourth indication information indicating one or more cells supporting a second positioning type, the cells indicated by the fourth indication information belonging to the positioning device; the processing unit is further configured to send a positioning request to the LMC via the communication unit when the positioning device needs to locate a terminal in a cell supporting the second positioning type.

[0119] In one possible implementation, the processing unit is further configured to receive the location information of the LMC from the LMC via the communication unit.

[0120] In one possible implementation, the location information of the LMC is the identifier of the positioning device where the LMC is located or the identifier of the LMC.

[0121] In one possible implementation, the processing unit is further configured to receive fifth indication information from the LMC via the communication unit. The fifth indication information is used to indicate whether the first cell of the positioning device supports the second positioning type. The first cell is any one or more cells among N2 cells, and the N2 cells are cells whose information on whether the second positioning type is supported has changed. N2 is an integer greater than 0.

[0122] In one possible implementation, the second location type is RI-LR.

[0123] In a twenty-third aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to determine fourth indication information corresponding to M6 network devices, the fourth indication information being used to indicate one or more cells supporting a second positioning type, the cell indicated by the fourth indication information belonging to the network device corresponding to the fourth indication information, and M6 being an integer greater than 0; the communication unit is configured to send the corresponding fourth indication information to each of the M6 ​​network devices.

[0124] In one possible implementation, the communication unit is further configured to send the LMC location information to each of the M6 ​​network devices.

[0125] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0126] In one possible implementation, the communication unit is further configured to send fifth indication information to the second network device, the fifth indication information being used to indicate whether the first cell of the second network device supports the second positioning type, the first cell being any one or more cells from N3 cells, the N3 cells being cells whose information on whether the second positioning type is supported has changed, and N3 being an integer greater than 0.

[0127] In one possible implementation, the second location type is RI-LR.

[0128] In a twentieth aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to receive fourth indication information from a core network element via the communication unit, the fourth indication information being used to indicate one or more cells supporting a second positioning type, the cells indicated by the fourth indication information belonging to the communication device; the processing unit is further configured to send a positioning request to an LMC via the communication unit when the communication device needs to locate a terminal in a cell supporting the second positioning type.

[0129] In one possible implementation, the processing unit is further configured to receive the location information of the LMC from the core network element via the communication unit.

[0130] In one possible implementation, the location information of the LMC is the identifier of the communication device where the LMC is located or the identifier of the LMC.

[0131] In one possible implementation, the processing unit is further configured to receive fifth indication information from the core network element via the communication unit. The fifth indication information is used to indicate whether the first cell of the communication device supports the second positioning type. The first cell is any one or more cells among N3 cells, and the N3 cells are cells whose information on whether the second positioning type is supported has changed. N3 is an integer greater than 0.

[0132] In one possible implementation, the second location type is RI-LR.

[0133] In a twenty-fifth aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to send a registration request to a core network element via the communication unit, the registration request being used to request registration with the core network element; the processing unit is further configured to receive a registration response from the core network element via the communication unit, the registration response including information on Q1 terminals supporting a second positioning type, the Q1 terminals accessing M7 network devices, where Q1 and M7 are both integers greater than 0; the processing unit is further configured to send sixth indication information corresponding to each of the M7 network devices via the communication unit, the sixth indication information being used to indicate one or more terminals supporting the second positioning type, the one or more terminals indicated by the sixth indication information accessing the network device corresponding to the sixth indication information.

[0134] In one possible implementation, the registration response also includes information about the M7 network devices.

[0135] In one possible implementation, the processing unit is further configured to send the location information of the positioning device to each of the M7 network devices via the communication unit.

[0136] In one possible implementation, the location information of the positioning device is the identifier of the network device where the positioning device is located or the identifier of the positioning device.

[0137] In one possible implementation, the processing unit is further configured to receive update information from the core network element via the communication unit, the update information being used to indicate whether the information of Q2 terminals that have changed according to the second positioning type is supported, where Q2 is an integer greater than 0.

[0138] In one possible implementation, the processing unit is further configured to send a seventh indication information to a third network device through the communication unit. The seventh indication information is used to indicate whether a first terminal accessing the third network device supports the second positioning type. The first terminal is any one or more of the Q2 terminals.

[0139] In one possible implementation, the second location type is RI-LR.

[0140] In a twenty-sixth aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to receive sixth indication information from an LMC via the communication unit, the sixth indication information being used to indicate one or more terminals supporting a second positioning type, the one or more terminals indicated by the sixth indication information being connected to the communication device; the processing unit is further configured to send a positioning request to the LMC via the communication unit when the communication device needs to locate a terminal supporting the second positioning type.

[0141] In one possible implementation, the processing unit is further configured to receive the location information of the LMC from the LMC via the communication unit.

[0142] In one possible implementation, the location information of the LMC is the identifier of the communication device where the LMC is located or the identifier of the LMC.

[0143] In one possible implementation, the processing unit is further configured to receive seventh indication information from the LMC via the communication unit. The seventh indication information is used to indicate whether a first terminal accessing the communication device supports the second positioning type. The first terminal is any one or more of Q2 terminals, and the Q2 terminals are terminals whose information on whether they support the second positioning type has changed. Q2 is an integer greater than 0.

[0144] In one possible implementation, the second location type is RI-LR.

[0145] In a twenty-seventh aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to determine, through the communication unit, sixth indication information corresponding to M8 network devices, the sixth indication information being used to indicate one or more terminals supporting a second positioning type, the one or more terminals indicated by the sixth indication information accessing the network device corresponding to the sixth indication information, wherein M8 is an integer greater than 0; the processing unit is further configured to send the sixth indication information corresponding to each of the M8 network devices to each of the network devices through the communication unit.

[0146] In one possible implementation, the processing unit is further configured to send the LMC location information to each of the M8 network devices via the communication unit.

[0147] In one possible implementation, the location information of the LMC is the identifier of the network device where the LMC is located or the identifier of the LMC.

[0148] In one possible implementation, the processing unit is further configured to send a seventh indication information to a third network device through the communication unit. The seventh indication information is used to indicate whether a first terminal accessing the third network device supports the second positioning type. The first terminal is any one or more of Q3 terminals, and the Q3 terminals are terminals whose information on whether they support the second positioning type has changed. Q3 is an integer greater than 0.

[0149] In one possible implementation, the sixth instruction information is carried in the initial context establishment request.

[0150] In one possible implementation, the second location type is RI-LR.

[0151] In one possible implementation, the terminal may report the second location type information to the communication device, or the terminal may support the second location type information being stored in the terminal's subscription information stored by the communication device.

[0152] In a twentieth aspect, a positioning device is provided, comprising: a processing unit and a communication unit; the processing unit is configured to receive sixth indication information from a core network element via the communication unit, the sixth indication information being used to indicate one or more terminals supporting a second positioning type, the one or more terminals indicated by the sixth indication information accessing the communication device; the processing unit is further configured to send a positioning request to an LMC via the communication unit when the communication device needs to locate a terminal supporting the second positioning type.

[0153] In one possible implementation, the processing unit is further configured to receive the location information of the LMC from the core network element via the communication unit.

[0154] In one possible implementation, the location information of the LMC is the identifier of the communication device where the LMC is located or the identifier of the LMC.

[0155] In one possible implementation, the processing unit is further configured to receive seventh indication information from the core network element via the communication unit. The seventh indication information is used to indicate whether a first terminal accessing the communication device supports the second positioning type. The first terminal is any one or more of Q3 terminals, and the Q3 terminals are terminals whose information on whether they support the second positioning type has changed. Q3 is an integer greater than 0.

[0156] In one possible implementation, the sixth instruction information is carried in the initial context establishment request.

[0157] In one possible implementation, the second location type is RI-LR.

[0158] A twenty-ninth aspect provides a positioning device, comprising: a processor. The processor is connected to a memory for storing computer execution instructions, and the processor executes the computer execution instructions stored in the memory to implement any one of the methods provided in the first to fourteenth aspects. Exemplarily, the memory and the processor can be integrated together or are separate devices. In the latter case, the memory can be located within or outside the positioning device.

[0159] In one possible implementation, the processor includes logic circuitry, and at least one of an input interface and an output interface. For example, the output interface is used to perform a sending action in the corresponding method, and the input interface is used to perform a receiving action in the corresponding method.

[0160] In one possible implementation, the positioning device further includes a communication interface and a communication bus, with the processor, memory, and communication interface connected via the communication bus. The communication interface is used to perform the sending and receiving actions in the corresponding method. The communication interface can also be referred to as a transceiver. Optionally, the communication interface includes at least one of a transmitter and a receiver, in which case the transmitter is used to perform the sending action in the corresponding method, and the receiver is used to perform the receiving action in the corresponding method.

[0161] In one possible implementation, the positioning device exists in the form of a chip.

[0162] In a thirtieth aspect, a positioning device is provided, comprising a processor, a memory, and a computer program stored in the memory and running on the processor, wherein when the computer program is run, the positioning device performs any one of the methods provided in any one of the first to fourteenth aspects.

[0163] In a thirty-first aspect, a positioning device is provided, comprising: a processor and an interface, wherein the processor is coupled to a memory via the interface, and when the processor executes a computer program or computer execution instructions in the memory, any one of the methods provided in any one of the first to fourteenth aspects is executed.

[0164] In a thirty-second aspect, a computer-readable storage medium is provided, including computer-executable instructions that, when executed on a computer, cause the computer to perform any one of the methods provided in any one of the first to fourteenth aspects.

[0165] In a thirty-third aspect, a computer program product is provided, comprising computer execution instructions that, when executed on a computer, cause the computer to perform any one of the methods provided in any one of the first to fourteenth aspects.

[0166] The technical effects of any of the implementation methods in aspects 15 to 33 can be found in the technical effects of the corresponding implementation methods in aspects 1 to 14, and will not be repeated here.

[0167] It should be noted that, provided the solutions do not contradict each other, the solutions in the above aspects can be combined. Attached Figure Description

[0168] Figure 1 A schematic diagram of a network architecture provided for an embodiment of this application;

[0169] Figure 2 This is another network architecture diagram provided in the embodiments of this application;

[0170] Figure 3 This is another network architecture diagram provided in the embodiments of this application;

[0171] Figure 4 This is a schematic diagram of another network architecture provided in an embodiment of this application;

[0172] Figure 5 A flowchart illustrating a positioning method provided in an embodiment of this application;

[0173] Figure 6 A flowchart illustrating yet another positioning method provided in this application embodiment;

[0174] Figure 7 A flowchart illustrating yet another positioning method provided in this application embodiment;

[0175] Figure 8 A flowchart illustrating yet another positioning method provided in this application embodiment;

[0176] Figure 9 A flowchart illustrating yet another positioning method provided in this application embodiment;

[0177] Figure 10 A flowchart illustrating yet another positioning method provided in this application embodiment;

[0178] Figure 11 A flowchart illustrating yet another positioning method provided in this application embodiment;

[0179] Figure 12 A flowchart illustrating yet another positioning method provided in this application embodiment;

[0180] Figure 13 A flowchart illustrating another positioning method provided in the embodiments of this application;

[0181] Figure 14 This is a schematic diagram illustrating the composition of a positioning device provided in an embodiment of this application;

[0182] Figure 15 This is a schematic diagram of the hardware structure of a positioning device provided in an embodiment of this application;

[0183] Figure 16 This is a schematic diagram of the hardware structure of another positioning device provided in an embodiment of this application. Detailed Implementation

[0184] In the description of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. The "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. The terms "first," "second," etc., do not limit the quantity or order of execution, and "first," "second," etc., do not necessarily imply differences.

[0185] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0186] The method provided in this application can be applied to long-term evolution (LTE) systems, 5th-generation (5G) systems, new radio (NR) systems, wireless local area networks (WLAN) systems, and future evolution systems, or multiple converged communication systems. The 5G system can be a non-standalone (NSA) 5G system or a standalone (SA) 5G system. For ease of description, this application uses the application of the provided method to a 5G system or an NR system as an example to illustrate the method. When the method provided in this application is applied to other systems, simply replace the network elements in this application with network elements in the corresponding system that have the same or similar functions.

[0187] The access network for 5G or NR systems can be called a next-generation (NG) radio access network (RAN). An NG-RAN can include one or more network devices. A network device is an entity on the network side used to transmit or receive signals, or both, to provide wireless communication capabilities to terminals. Network devices included in an NG-RAN can be next-generation node base stations (gNBs), next-generation evolved NodeBs (ng-eNBs), etc.

[0188] Network devices can be complete entities or discrete architectures. In a discrete architecture, network devices include centralized units (CUs) and distributed units (DUs). The CU implements some of the network device's functions, and the DU implements others. For example, the CU is responsible for handling non-real-time protocols and services, implementing the functions of radio resource control (RRC) and the packet data convergence protocol (PDCP) layer. The DU is responsible for handling physical layer protocols and real-time services, implementing the functions of radio link control (RLC), media access control (MAC), and the physical (PHY) layer. Furthermore, the CU can also be a form where the user plane (UP) (hereinafter referred to as CU-UP) and the control plane (CP) (hereinafter referred to as CU-CP) are separated.

[0189] In 5G or NR systems, traditional positioning architectures can be found in [reference needed]. Figure 1In NG-RAN, network devices involved in terminal localization include gNB and ng-eNB. LMF and AMF reside in the core network. AMF serves as the interface between network devices and the core network, including functions related to access management and mobility management. It is primarily responsible for forwarding localization-related messages between the terminal and the LMF, as well as between network devices and the LMF. The LMF receives localization requests from the AMF, determines the method used for localization measurements (this decision can be based on the capabilities of the terminal and network, or on information contained in the localization request), determines the network device to locate the terminal, requests auxiliary information needed for localization from the network device or terminal, sends the auxiliary information needed for localization to the terminal or network device, requests measurement information from the terminal or network device, and calculates the terminal's location. Interfaces between various network elements can be found in [link to documentation]. Figure 1 I will not go into details.

[0190] based on Figure 1 The location architecture shown currently has three types of location services, depending on the initiator:

[0191] Mobile terminated location request (MT-LR): The location service originates from a location service entity in the core network (e.g., gateway mobile location center (GMLC)). This entity can specify a particular terminal for location tracking. Specifically, the location service entity sends a location service request (hereinafter referred to as the location request) to the AMF. Upon receiving the location request, the AMF sends it to the LMF. The LMF, upon receiving the location request, initiates and executes a location measurement process to obtain location measurement information. Based on this information, the LMF calculates the terminal's location and sends it to the AMF, which then forwards it to the location service entity.

[0192] Network-induced location request (NI-LR): The location service originates from the AMF (Agency Location Provider), meaning the operator's network initiates the location request itself. Specifically, if the AMF needs the terminal's location information, it sends a location request to the LMF (Local Location Provider). Upon receiving the location request, the LMF initiates and executes a location measurement process, obtains location measurement information through this process, calculates the terminal's location based on the location measurement information, and then sends the terminal's location information back to the AMF.

[0193] Mobile Originated Location Request (MO-LR): The location service originates from the terminal itself. The terminal sends a location request to the AMF, the AMF obtains the terminal's location information from the LMF (the specific process is similar to the MT-LR implementation process and will not be described in detail here), and then sends the terminal's location information back to the terminal.

[0194] To locate the terminal more quickly, such as Figure 2 As shown, an LMC can be deployed in a network device. In this case, the network device can directly send location requests to the deployed LMC, which differs from the traditional location architecture where the LMF receives location requests from the AMF. The location type of the location request sent by the network device can be called a RAN-induced location request (RI-LR). For ease of description, the embodiments in this application below will use this method. Figures 6 to 13 The scheme shown illustrates the method provided in this application by taking the network device sending a location request to the LMC as an example. In actual implementation, the network device can also send a location request to the AMF or LMF.

[0195] In this embodiment of the application, LMC can be deployed in NG-RAN. There are three possible ways to deploy LMC in NG-RAN:

[0196] Method 1: When the network device is a complete entity, LMC is deployed on the network device and is a functional module of the network device. See details for further information. Figure 2 .

[0197] Method 2: In the case of a discrete network device architecture, the LMC is deployed on the network device, and the LMC is an independent logical network element with a logical interface to the CU (or CU-CP) of the network device. For example... Figure 3 As shown, Figure 3 The diagram is illustrated using the example of an LMC having a logical interface with the CU of the network device it resides in.

[0198] Method 3: The LMC is an independent logical network element connected to multiple network devices (or the CUs or CU-CPs of network devices). See also Figure 4 , Figure 4 The example shown is an LMC connected to multiple network devices.

[0199] It should be noted that Figures 2 to 4The LMC deployment method shown is merely exemplary. In actual implementation, the number of network devices involved in terminal positioning can be greater, and the LMC deployment is not limited to the location shown in the figure. Any LMC deployment method can be applied to the method provided in this application embodiment.

[0200] It should be noted that, in the embodiments of this application, Figures 2 to 4 In the architecture shown, LMC supports not only RI-LR, but also any of NI-LR, MT-LR, and MO-LR.

[0201] When LMC supports NI-LR, MT-LR, or MO-LR, AMF does not send a positioning request to LMF, but instead sends a positioning request to LMC. After receiving the positioning request, LMC initiates and executes the positioning measurement process, obtains positioning measurement information through the positioning measurement process, calculates the terminal's position based on the positioning measurement information, and sends the terminal's position information to AMF.

[0202] Currently, there is no solution regarding how to configure the functions supported by LMC in the description of RI-LR. Furthermore, the core network LMF does not support network devices directly initiating location tracking; therefore, there is no solution for how network devices without LMC deployed can initiate location tracking.

[0203] To clarify the positioning functions possessed by LMC, this application provides a positioning method, such as... Figure 5 As shown, it includes:

[0204] 501. The LMC sends a registration request to the core network element. The registration request is used to request registration with the core network element. Correspondingly, the core network element receives the registration request from the LMC.

[0205] Optionally, the core network element can be either AMF or LMF.

[0206] In various embodiments of this application, the registration request may also be referred to as an LMC registration message.

[0207] 502. The core network element sends a registration response to the LMC. Correspondingly, the LMC receives the registration response from the core network element.

[0208] The registration response includes a first indication information, which indicates the location type supported by the LMC; or, the first indication information indicates whether the LMC supports a first location type.

[0209] In the case where the core network element is LMF, LMF and LMC can exchange information through AMF.

[0210] In various embodiments of this application, the registration response may also be referred to as an LMC registration ACK message.

[0211] Optionally, LMC supports one or more of the following positioning types: NI-LR, MT-LR, MO-LR, RI-LR.

[0212] The first indication information can directly indicate the location types supported by LMC. For example, the first indication information can be a list that includes information about the location types supported by LMC.

[0213] The first indication information can also consist of multiple bits, with the values ​​of these bits indicating which positioning types the terminal supports. For example, the multiple bits can be two bits. When both bits are 00, it indicates that the LMC supports NI-LR and MT-LR; when both bits are 10, it indicates that the LMC supports MT-LR and MO-LR; when both bits are 01, it indicates that the LMC supports MO-LR and RI-LR; and when both bits are 11, it indicates that the LMC supports NI-LR and RI-LR. As another example, the multiple bits can be four bits, with each of the four bits corresponding to a positioning type, and the value of one bit indicating whether the LMC supports the corresponding positioning type. For instance, if the first bit corresponds to NI-LR, the second bit to MT-LR, the third bit to MO-LR, and the fourth bit to RI-LR, and assuming that the value of one bit is 1, it indicates that the LMC supports the corresponding positioning type. Therefore, when the value of the four bits is 0001, it means that the LMC supports RI-LR but does not support NI-LR, MT-LR, and MO-LR. When the value of the four bits is 1110, it means that the LMC supports NI-LR, MT-LR, and MO-LR but does not support RI-LR.

[0214] Optionally, the first positioning type includes any one of the following positioning types: NI-LR, MT-LR, MO-LR, RI-LR.

[0215] For each location type, one bit can be used to indicate whether the LMC supports that location type. For example, the first indication information can use one bit to indicate whether RI-LR is supported. When the value of this bit is 0, it means that the LMC does not support RI-LR, and when the value of this bit is 1, it means that the LMC supports RI-LR. The reverse is also true.

[0216] Figure 5The method provided in the illustrated embodiment allows core network elements to indicate the location types supported by the LMC during LMC registration, enabling the LMC to subsequently perform corresponding location functions. Furthermore, since the LMF does not support the new location type RI-LR, while the LMC does, authorizing the LMC with the RI-LR location type ensures that the LMC's functionality remains within the core network's jurisdiction.

[0217] To address the issue of location initiation by network devices without LMC deployment, this application also provides a location method. This method can be implemented in several ways. In implementation 1, a network device supporting a certain location type (denoted as the second location type) can use the second location type to locate all terminals it serves. In implementation 2, a network device belonging to a cell supporting the second location type can use the second location type to locate all terminals within that cell. In implementation 3, a network device accessed by a terminal supporting the second location type can use the second location type to locate that terminal. The implementation process of these three methods is described in detail below.

[0218] Implementation method 1: Network devices that support the second positioning type can use the second positioning type to locate all terminals of the service.

[0219] In implementation mode 1, the LMC or core network element can instruct the network device to support the second positioning type. The positioning method provided in this application will be described below through scenario 1.1 (LMC instructs the network device to support the second positioning type) and scenario 1.2 (core network element instructs the network device to support the second positioning type).

[0220] Scenario 1.1: LMC indicates that the network device supports the second positioning type.

[0221] In scenario 1.1, see Figure 6 The positioning method includes:

[0222] 601. The LMC sends a registration request to the core network element. The registration request is used to request registration with the core network element. Correspondingly, the core network element receives the registration request from the LMC.

[0223] Optionally, the core network element can be either AMF or LMF.

[0224] 602. The core network element sends a registration response to the LMC. This registration response includes information about M1 network devices supporting the second positioning type, where M1 is a positive integer. Correspondingly, the LMC receives the registration response from the core network element.

[0225] In the case where the core network element is an LMF, the LMF and LMC can exchange information through the AMF. The information of the network device can be the network device's identifier or the information of the network device's cell (e.g., cell identifier).

[0226] Optionally, the second positioning type is RI-LR.

[0227] It should be noted that information about the M1 network devices can also be sent to the LMC through other messages exchanged between the core network elements and the LMC. These messages can include, for example, messages following registration completion (e.g., existing NG application protocol (NGAP) messages or newly defined NGAP messages), and are not limited to registration requests and responses. For ease of understanding, registration requests and responses are used as examples here.

[0228] 603. The LMC sends a second indication information corresponding to each of the M1 network devices, the second indication information being used to indicate that the corresponding network device supports the second positioning type. Accordingly, the M1 network devices receive the second indication information from the LMC.

[0229] For example, if M1 = 2, and the M1 network devices are network device 1 and network device 2 respectively, then the second indication information sent by LMC to network device 1 is used to indicate that network device 1 supports the second positioning type, and the second indication information sent by LMC to network device 2 is used to indicate that network device 2 supports the second positioning type.

[0230] In various embodiments of this application, the second indication information can be carried in an existing message (e.g., an existing Xn interface application protocol (XnAP) message) or a new message (e.g., an LMC service indication message). Optionally, in various embodiments of this application, the network device can also reply with a response to an existing message or a new message, wherein the response to a new message can be called an LMC service indication ACK message. The third, fourth, fifth, sixth, and seventh indication information described below are similar to the second indication information and will not be repeated hereafter. It should be noted that the LMC service indication message and the LMC service indication ACK message are merely examples of names for a new message, and other names are possible; this application does not impose any limitations.

[0231] 604. When any of the M1 network devices needs to locate the terminal being served, that network device sends a location request to the LMC.

[0232] Optional, see Figure 6 Before step 604, the method further includes:

[0233] The 603A and LMC send LMC location information to each of the M1 network devices. Correspondingly, the M1 network devices receive LMC location information from the LMC.

[0234] Optionally, the location information of the LMC can be the identifier of the network device in which the LMC is located (in this case, the LMC is deployed inside the network device) or the identifier of the LMC (in this case, the LMC can be deployed inside or outside the network device).

[0235] The second instruction information and the LMC location information can be carried in the same message or in different messages; this application does not impose any restrictions.

[0236] Upon receiving the location information from the LMC, the network device can determine which device to send a location request to when it needs to locate a terminal providing the service. It should be noted that the LMC's location information may not be sent to the network device by the LMC itself, but rather pre-configured within each network device; this application does not impose any restrictions on this.

[0237] Optional, see Figure 6 After step 602, the method further includes:

[0238] 605. The core network element sends update information to the LMC. This update information indicates whether the information of M2 network devices whose information has changed under the second positioning type is supported, where M2 is an integer greater than 0. Correspondingly, the LMC receives the update information from the core network element.

[0239] In various embodiments of this application, update information can be carried in existing messages or new messages (e.g., LMC function update messages). Similar to LMC service indication messages and LMC service indication confirmation messages, LMC function update messages are merely examples of new message names; other names are also possible, and this application does not impose any limitations.

[0240] In the first scenario, the updated information is the updated information of the network devices that support the second positioning type (e.g., the network device identifier). In this case, by comparing the network devices that support the second positioning type before and after the update, the LMC can determine which network devices have changed from supporting the second positioning type to not supporting it, and which network devices have changed from not supporting the second positioning type to supporting it.

[0241] For example, referring to Table 1, if the network devices that support the second positioning type before the update include network device 1 and network device 2, and the network devices that support the second positioning type after the update include network device 1 and network device 3, then LMC can determine that network device 2 has changed from supporting the second positioning type to not supporting the second positioning type, and network device 3 has changed from not supporting the second positioning type to supporting the second positioning type.

[0242] Table 1

[0243] Network devices that previously supported the second positioning type were not supported. The updated network devices support the second positioning type. Network device 1 Network device 1 Network device 2 Network device 3

[0244] In the second case, the update information is the information of M2 network devices whose support for the second positioning type has changed (e.g., the identifier of the network device). The LMC determines which network devices changed from supporting the second positioning type to not supporting the second positioning type, and which network devices changed from not supporting the second positioning type to supporting the second positioning type, based on the network devices that supported the second positioning type before the update and the update information.

[0245] For example, referring to Table 2, if the network devices that supported the second positioning type before the update included network device 1 and network device 2, and the M2 network devices whose information on supporting the second positioning type changed were network device 1 and network device 3, then LMC can determine that network device 2 changed from supporting the second positioning type to not supporting the second positioning type, and network device 3 changed from not supporting the second positioning type to supporting the second positioning type.

[0246] Table 2

[0247] In the third scenario, the updated information includes information about network devices that have changed from supporting the second positioning type to not supporting it (e.g., network device identifiers), and information about network devices that have changed from not supporting the second positioning type to supporting it (e.g., network device identifiers). Alternatively, the updated information includes information about M2 network devices whose support for the second positioning type has changed, and information on whether they support the second positioning type (specifically, which network devices changed from supporting the second positioning type to not supporting it, and which network devices changed from not supporting the second positioning type to supporting it). In this case, the LMC can directly determine, based on the updated information, which network devices changed from supporting the second positioning type to not supporting it, and which network devices changed from not supporting the second positioning type to supporting it.

[0248] For example, the update information can be found in Table 3. According to Table 3, LMC can determine that network device 1 and network device 2 have changed from supporting the second positioning type to not supporting the second positioning type, and network device 3 and network device 4 have changed from not supporting the second positioning type to supporting the second positioning type.

[0249] Table 3

[0250]

[0251]

[0252] The execution order of steps 605, 603, and 604 is not important.

[0253] Optionally, after step 605, the method further includes:

[0254] 606. The LMC sends a third indication message to the first network device, which indicates whether the first network device supports the second positioning type. The first network device is any one of the M2 network devices. Correspondingly, the first network device receives the third indication message from the LMC.

[0255] Specifically, if the first network device changes from supporting the second positioning type to not supporting it, the third indication information is specifically used to indicate that the first network device does not support the second positioning type. In this case, the first network device belongs to network device M1, and in subsequent processes, the first network device does not send a positioning request to the LMC. If the first network device changes from not supporting the second positioning type to supporting it, the third indication information is specifically used to indicate that the first network device supports the second positioning type. In this case, the first network device does not belong to network device M1, and in subsequent processes, when the first network device needs to locate the terminal it is serving, it sends a positioning request to the LMC.

[0256] Figure 6 The method provided in the illustrated embodiment allows LMC to authorize network devices to use the second positioning type to locate the terminal when positioning is required by sending second indication information to network devices that support the second positioning type, thereby solving the problem of positioning initiated by network devices that have not deployed LMC.

[0257] Scenario 1.2: Core network elements indicate that network devices support the second positioning type.

[0258] In scenario 1.2, see Figure 7 The positioning method includes:

[0259] 701. The core network element determines the second indication information corresponding to M3 network devices. The second indication information is used to indicate that the corresponding network device supports the second positioning type.

[0260] Optionally, the core network element can be either AMF or LMF.

[0261] Optionally, the second positioning type is RI-LR.

[0262] 702. The core network element sends a second indication message corresponding to each of the M3 network devices. Correspondingly, the M3 network devices receive the second indication message from the core network element. M3 is an integer greater than 0.

[0263] For example, if M3 = 2, and the M3 network devices are network device 1 and network device 2 respectively, then the second indication information sent by the core network element to network device 1 is used to indicate that network device 1 supports the second positioning type, and the second indication information sent by the core network element to network device 2 is used to indicate that network device 2 supports the second positioning type.

[0264] When the core network element is LMF, LMF and network devices can exchange information through AMF.

[0265] The second indication information may be carried in existing NGAP messages (e.g., AMF Configuration Update messages) or new NGAP messages that are exchanged between the AMF and network devices.

[0266] 703. When any of the M3 network devices needs to locate the terminal being served, that network device sends a location request to the LMC.

[0267] Optional, see Figure 7 Before step 703, the method further includes:

[0268] 702A. The core network element sends the LMC location information to each of the M3 network devices. Correspondingly, the M3 network devices receive the LMC location information from the core network element.

[0269] Optionally, the location information of the LMC can be the identifier of the network device in which the LMC is located (in this case, the LMC is deployed inside the network device) or the identifier of the LMC (in this case, the LMC can be deployed inside or outside the network device).

[0270] The second instruction information and the LMC location information can be carried in the same message or in different messages; this application does not impose any restrictions.

[0271] Upon receiving the location information from the LMC, the network device can determine which device to send a location request to when it needs to locate a terminal providing the service. It should be noted that the LMC location information may not be sent to the network device by the core network element, but rather pre-configured in each network device; this application does not impose any restrictions.

[0272] Optional, see Figure 7 Before step 703, the method further includes:

[0273] 702B, the core network element sends information about M3 network devices that support the second positioning type to the LMC.

[0274] In this case, LMC can process only the location requests sent by M3 network devices, and will not process the location requests sent by other network devices.

[0275] In a specific implementation of step 702B, the LMC can send a registration request to the core network element. The core network element receives the registration request from the LMC and sends a registration response to the LMC. The registration response may include information about the M3 network devices that support the second positioning type.

[0276] Of course, information about the M3 network devices can also be sent to the LMC through other messages exchanged between the core network elements and the LMC, such as messages after registration is complete (e.g., existing NGAP messages (e.g., AMF configuration update messages) or new NGAP messages), and is not limited to registration requests and registration responses. For ease of understanding, registration requests and registration responses are used as examples here.

[0277] The execution order of steps 702, 702A, and 702B is not important.

[0278] Optional, see Figure 7 After step 703, the method further includes:

[0279] 704. The core network element sends update information to the LMC. This update information indicates whether the information of M4 network devices whose information has changed under the second positioning type is supported, where M4 is a positive integer. Correspondingly, the LMC receives the update information from the core network element.

[0280] The specific implementation of step 704 is similar to that of step 605 above, and can be understood by referring to it, so it will not be described again.

[0281] Optionally, after step 703, the method further includes:

[0282] 705. The core network element sends third indication information to the first network device. The third indication information indicates whether the first network device supports the second positioning type, and the first network device can be any one of the M4 network devices. Correspondingly, the first network device receives the third indication information from the core network element.

[0283] For a description of the third instruction information, please refer to Scenario 1.1 above, which will not be repeated here. The execution order of steps 705 and 704 is not important.

[0284] Figure 7 The method provided in the illustrated embodiment allows core network elements to authorize network devices to use the second positioning type to locate terminals when they need to be located by sending second indication information to network devices that support the second positioning type, thereby solving the problem of network devices without LMC initiating positioning.

[0285] Implementation Method 2: Network devices belonging to a cell that supports the second positioning type can use the second positioning type to locate all terminals within that cell.

[0286] In implementation mode 2, the LMC or core network element can indicate to the network device a cell that supports the second positioning type. The positioning method provided in this application will be described below through scenario 2.1 (LMC indicating to the network device a cell that supports the second positioning type) and scenario 2.2 (core network element indicating to the network device a cell that supports the second positioning type).

[0287] Scenario 2.1: The LMC indicates to the network device that a cell supports the second positioning type.

[0288] In scenario 2.1, see Figure 8 The positioning method includes:

[0289] 801. The LMC sends a registration request to the core network element. The registration request is used to request registration with the core network element. Correspondingly, the core network element receives the registration request from the LMC.

[0290] Optionally, the core network element can be either AMF or LMF.

[0291] 802. The core network element sends a registration response to the LMC. This registration response includes information about N1 cells supporting the second positioning type. These N1 cells belong to M5 network devices, where N1 and M5 are both integers greater than 0. Correspondingly, the LMC receives the registration response from the core network element.

[0292] In the various embodiments of this application, a cell belonging to a network device can be understood as the network device supporting the cell.

[0293] Optionally, the registration response may also include information about M5 network devices. These M5 network devices correspond to N1 cells, allowing the LMC to determine the network device belonging to any one of the N1 cells based on this correspondence.

[0294] In the case where the core network element is LMF, LMF and LMC can exchange information through AMF. Cell information can include cell identifiers, etc.

[0295] Optionally, the second positioning type is RI-LR.

[0296] It should be noted that information about the N1 cells can also be sent to the LMC through other messages exchanged between the core network elements and the LMC, such as messages after registration is completed (e.g., existing NGAP messages (e.g., AMF configuration update messages) or new NGAP messages), and is not limited to registration requests and registration responses. For ease of understanding, registration requests and registration responses are used as examples here.

[0297] 803. The LMC sends a fourth indication information corresponding to each of the M5 network devices. This fourth indication information indicates one or more cells supporting the second positioning type, and the cell indicated by the fourth indication information belongs to the network device corresponding to that fourth indication information. Correspondingly, the M5 network devices receive the fourth indication information from the LMC.

[0298] For example, if N1 = 3, and the N1 cells are cell 1, cell 2 and cell 3 respectively, cell 1 and cell 2 belong to network device 1, and cell 3 belongs to network device 2, then the fourth indication information sent by LMC to network device 1 is used to indicate that cell 1 and cell 2 support the second positioning type, and the fourth indication information sent by LMC to network device 2 is used to indicate that cell 3 supports the second positioning type.

[0299] 804. When any of the M5 network devices needs to locate a terminal in a cell that supports the second positioning type, the network device sends a positioning request to the LMC.

[0300] Optional, see Figure 8 Before step 804, the method further includes:

[0301] The 803A and LMC send LMC location information to each of the M5 network devices. Correspondingly, the M5 network devices receive LMC location information from the LMC.

[0302] The description related to step 803A can be found in step 603A above, and will not be repeated here.

[0303] Optional, see Figure 8After step 802, the method further includes:

[0304] 805. The core network element sends update information to the LMC. This update information indicates whether the information for N2 cells where the second positioning type has changed is supported, where N2 is a positive integer. Correspondingly, the LMC receives the update information from the core network element.

[0305] The specific implementation of step 805 is similar to that of step 605. The only difference is that the information that changes in the second positioning type here is the information of the cell, not the information of the network device. For details, please refer to the relevant description of step 605. Specifically, you can understand it by replacing M2 network devices with N2 cells. I will not go into details here.

[0306] The execution order of steps 805, 803, and 804 is not important.

[0307] Optionally, after step 805, the method further includes:

[0308] 806. The LMC sends a fifth indication message to the second network device. This fifth indication message indicates whether the first cell of the second network device supports the second positioning type. The first cell can be any one or more cells from the N2 cells. Correspondingly, the second network device receives the fifth indication message from the LMC.

[0309] Specifically, if the first cell changes from supporting the second positioning type to not supporting it, the fifth indication information is used to indicate that the first cell does not support the second positioning type. In this case, the first cell belongs to N1 cells, and in subsequent processes, the second network device determines not to locate the terminal in the first cell. If the first cell changes from not supporting the second positioning type to supporting it, the fifth indication information is used to indicate that the first cell supports the second positioning type. In this case, the first cell does not belong to N1 cells, and in subsequent processes, when the second network device needs to locate the terminal in the first cell, it sends a positioning request to the LMC.

[0310] Figure 8 The method provided in the illustrated embodiment allows LMC to authorize network devices to use the second positioning type to locate terminals when it is necessary to locate terminals in certain cells by sending fourth indication information to the network devices belonging to cells that support the second positioning type, thereby solving the problem of network devices that have not deployed LMC initiating positioning.

[0311] Scenario 2.2: Core network elements indicate to network devices that a cell supports the second positioning type.

[0312] In scenario 2.2, see Figure 9The positioning method includes:

[0313] 901. The core network element determines the fourth indication information corresponding to M6 network devices. The fourth indication information is used to indicate one or more cells supporting the second positioning type, and the cell indicated by the fourth indication information belongs to the network device corresponding to the fourth indication information. M6 is an integer greater than 0.

[0314] Optionally, the core network element can be either AMF or LMF.

[0315] Optionally, the second positioning type is RI-LR.

[0316] 902. The core network element sends a fourth indication message corresponding to each of the M6 ​​network devices. Correspondingly, the network devices receive the fourth indication message from the core network element.

[0317] For example, if the fourth indication information indicates that one or more cells supporting the second positioning type are cell 1, cell 2 and cell 3, cell 1 and cell 2 belong to network device 1 and cell 3 belongs to network device 2, then the fourth indication information sent by the core network element to network device 1 is used to indicate that cell 1 and cell 2 support the second positioning type, and the fourth indication information sent by the core network element to network device 2 is used to indicate that cell 3 supports the second positioning type.

[0318] When the core network element is LMF, LMF and network devices can exchange information through AMF.

[0319] The fourth indication information can be carried in existing NGAP messages (e.g., AMF configuration update messages) or new NGAP messages that are exchanged between the AMF and network devices.

[0320] 903. When any of the M6 ​​network devices needs to locate a terminal in a cell that supports the second positioning type, the network device sends a positioning request to the LMC.

[0321] Optional, see Figure 9 Before step 903, the method further includes:

[0322] 902A. The core network element sends the LMC location information to each of the M6 ​​network devices. Correspondingly, the M6 ​​network devices receive the LMC location information from the core network element.

[0323] The description related to step 902A can be found in step 702A above, and will not be repeated here.

[0324] Optional, see Figure 9 Before step 903, the method further includes:

[0325] 902B, the core network element sends information about M6 network devices to the LMC.

[0326] In this scenario, LMC can process only the location requests sent by M6 network devices, and will not process the location requests sent by other network devices.

[0327] In specific implementation of step 902B, the LMC can send a registration request to the core network element. The core network element receives the registration request from the LMC and sends a registration response to the LMC. The registration response may include information about M6 network devices.

[0328] Of course, information about the M6 ​​network devices can also be sent to the LMC through other messages exchanged between the core network elements and the LMC, such as messages after registration is complete (e.g., existing NGAP messages (e.g., AMF configuration update messages) or new NGAP messages), and is not limited to registration requests and registration responses. For ease of understanding, registration requests and registration responses are used as examples here.

[0329] The execution order of steps 902, 902A, and 902B is not important.

[0330] Optional, see Figure 9 After step 903, the method further includes:

[0331] 904. The core network element sends update information to the LMC. This update information indicates whether the information for N3 cells where the second positioning type has changed is supported, where N3 is a positive integer. Correspondingly, the LMC receives the update information from the core network element.

[0332] The specific implementation of step 904 is similar to that of step 805 above, and can be understood by referring to it, so it will not be described again.

[0333] Optional, see Figure 9 After step 903, the method further includes:

[0334] 905. The core network element sends a fifth indication message to the second network device. This fifth indication message indicates whether the first cell of the second network device supports the second positioning type, where the first cell can be any one or more of the N3 cells. Correspondingly, the second network device receives the fifth indication message from the core network element.

[0335] For a description of the fifth instruction information, please refer to Scenario 2.1 above, which will not be repeated here.

[0336] Figure 9The method provided in the illustrated embodiment allows the core network element to send a fourth indication message to the network device belonging to the cell that supports the second positioning type. This authorizes the network device to use the second positioning type to locate the terminal when it is necessary to locate the terminal in certain cells, thereby solving the problem of network devices that have not deployed LMC initiating positioning.

[0337] Implementation method 3: Network devices that support the second positioning type of terminal access can use the second positioning type to locate the terminal.

[0338] In implementation mode 3, the LMC or core network element can indicate to the network device a terminal that supports the second positioning type, or the terminal can indicate to the network device whether it supports the second positioning type. The positioning method provided in this application will be described below through scenario 3.1 (LMC indicates to the network device a terminal that supports the second positioning type), scenario 3.2 (core network element indicates to the network device a terminal that supports the second positioning type), and scenario 3.3 (terminal indicates to the network device whether it supports the second positioning type).

[0339] Scenario 3.1: The LMC indicates to the network device that it supports terminals of the second positioning type.

[0340] In scenario 3.1, see Figure 10 The positioning method includes:

[0341] 1001. The LMC sends a registration request to the core network element. The registration request is used to request registration with the core network element. Correspondingly, the core network element receives the registration request from the LMC.

[0342] Optionally, the core network element can be either AMF or LMF.

[0343] 1002. The core network element sends a registration response to the LMC. This registration response includes information about Q1 terminals supporting the second positioning type, where Q1 terminals are connected to M7 network devices, and both Q1 and M7 are integers greater than 0. Correspondingly, the LMC receives the registration response from the core network element.

[0344] Optionally, the registration response may also include information about M7 network devices. These M7 network devices correspond to Q1 terminals, and the LMC can use this correspondence to determine the network device accessed by any one of the Q1 terminals.

[0345] Optionally, in one scenario, the information regarding whether the terminal supports the second positioning type is reported by the terminal to the core network element. For example, this information can be carried in the RRC setupComplete message (in which case the core network element is the AMF), in the LTE positioning protocol (LPP) message sent by the terminal to the LMF for terminal capability reporting (in which case the core network element is the LMF), or in other messages; this application does not impose any limitations. In another scenario, the information regarding whether the terminal supports the second positioning type is located in the terminal's subscription information stored in the core network element.

[0346] It should be noted that the information of the Q1 terminals can also be sent to the LMC through other messages exchanged between the core network elements and the LMC, such as messages after registration is completed (e.g., existing NGAP messages (e.g., AMF configuration update messages) or new NGAP messages), and is not limited to registration requests and registration responses. For ease of understanding, registration requests and registration responses are used as examples here.

[0347] Optionally, the second positioning type is RI-LR.

[0348] When the core network element is an LMF, the LMF and LMC can exchange information through the AMF. Terminal information can include terminal identifiers, etc.

[0349] 1003. The LMC sends a sixth indication message corresponding to each of the M7 network devices. This sixth indication message indicates that one or more terminals supporting the second positioning type are connected to the network device corresponding to the sixth indication message. Correspondingly, the M7 network devices receive the sixth indication message from the LMC.

[0350] For example, if Q1 = 3, and the Q1 terminals are terminal 1, terminal 2 and terminal 3 respectively, terminal 1 and terminal 2 are connected to network device 1, and terminal 3 is connected to network device 2, then the sixth indication information sent by LMC to network device 1 is used to indicate that terminal 1 and terminal 2 support the second positioning type, and the sixth indication information sent by LMC to network device 2 is used to indicate that terminal 3 supports the second positioning type.

[0351] 1004. When any of the M7 network devices needs to locate a terminal that supports the second positioning type, the network device sends a positioning request to the LMC.

[0352] Optional, see Figure 10 Before step 1004, the method further includes:

[0353] 1003A and LMC send LMC location information to each of the M7 network devices. Correspondingly, the M7 network devices receive LMC location information from LMC.

[0354] The description related to step 1003A can be found in step 603A above, and will not be repeated here.

[0355] Optional, see Figure 10 After step 1002, the method further includes:

[0356] 1005. The core network element sends update information to the LMC. This update information indicates whether the information of Q2 terminals whose second positioning type has changed is supported, where Q2 is a positive integer. Correspondingly, the LMC receives the update information from the core network element.

[0357] The specific implementation of step 1005 is similar to that of step 605. The only difference is that the information that changes in the second positioning type here is the terminal information, not the network device information. For details, please refer to the relevant description of step 605. Specifically, you can understand it by replacing M2 network devices with Q2 terminals. I will not go into details here.

[0358] The execution order of steps 1005, 1003, and 1004 is not important.

[0359] Optionally, after step 1005, the method further includes:

[0360] 1006. The LMC sends a seventh indication message to the third network device. This seventh indication message indicates whether the first terminal accessing the third network device supports the second positioning type. The first terminal can be any one or more of the Q2 terminals. Correspondingly, the third network device receives the seventh indication message from the LMC.

[0361] Specifically, if the first terminal changes from supporting the second positioning type to not supporting the second positioning type, the seventh indication information is specifically used to indicate that the first terminal does not support the second positioning type. In this case, the first terminal belongs to terminal Q1, and in subsequent processes, the second network device determines not to locate the first terminal. If the first terminal changes from not supporting the second positioning type to supporting the second positioning type, the seventh indication information is specifically used to indicate that the first terminal supports the second positioning type. In this case, the first terminal does not belong to terminal Q1, and in subsequent processes, when the second network device needs to locate the first terminal, it sends a positioning request to the LMC.

[0362] One possible scenario where the first terminal changes from supporting the second positioning type to no longer supporting it is when the first terminal moves out of the jurisdiction of the LMC. The jurisdiction of the LMC can be the coverage area of ​​all network devices capable of requesting positioning from the LMC. Another possible scenario where the first terminal changes from not supporting the second positioning type to supporting it is when the first terminal moves into the jurisdiction of the LMC.

[0363] Figure 10 The method provided in the illustrated embodiment allows LMC to authorize network devices to use the second positioning type to locate terminals when positioning is required by sending a sixth instruction message to network devices that support the second positioning type. This solves the problem of network devices without LMC initiating positioning.

[0364] Scenario 3.2: Core network elements indicate to network devices that terminals supporting the second positioning type are supported.

[0365] In scenario 3.2, see [link / reference]. Figure 11 The positioning method includes:

[0366] 1101. The core network element determines the sixth indication information corresponding to M8 network devices. The sixth indication information is used to indicate one or more terminals (denoted as Q4 terminals) supporting the second positioning type. The Q4 terminals indicated by the sixth indication information access the network device corresponding to the sixth indication information. M8 and Q4 are both integers greater than 0.

[0367] Optionally, the second positioning type is RI-LR.

[0368] Optionally, the core network element can be either AMF or LMF.

[0369] In the first implementation, the core network element can determine which terminals support the second positioning type itself. For example, information on whether each terminal supports the second positioning type is stored in the terminal's subscription information in the core network element, and the core network element determines which terminals support the second positioning type based on this information.

[0370] In the second implementation, core network elements can determine which terminals support the second positioning type based on information received from other core network elements. For example, information on whether a terminal supports the second positioning type is located in the terminal's subscription information stored in the UDM (User Depository), and the AMF (Application Function Provider) can obtain the terminal's subscription information from the UDM. In this case, when the core network element is the AMF, the AMF can determine which terminals support the second positioning type based on the subscription information of each terminal. When the core network element is the LMF (Local Management Function Provider), the LMF can obtain the terminal's subscription information from the AMF, and thus determine which terminals support the second positioning type based on the subscription information of each terminal.

[0371] In the third implementation, the core network element receives information about terminals that support the second positioning type from other core network elements. For example, when the core network element is an LMF, the AMF determines which terminals support the second positioning type, and the LMF can obtain this information from the AMF.

[0372] In the fourth implementation, the core network element determines which terminals support the second positioning type based on the information reported by the terminals regarding whether they support the second positioning type.

[0373] For example, information on whether the terminal supports the second positioning type can be carried in the RRC establishment completion message (in which case the core network element is AMF), or in the LTE positioning protocol message sent by the terminal to the LMF for terminal capability reporting (in which case the core network element is LMF), or in other messages. This application does not impose any restrictions.

[0374] 1102. The core network element sends a sixth indication message corresponding to each of the M8 network devices. Correspondingly, the M8 network devices receive the sixth indication message from the core network element.

[0375] For example, if Q4 = 3, and the four terminals are terminal 1, terminal 2 and terminal 3 respectively, terminal 1 and terminal 2 are connected to network device 1, and terminal 3 is connected to network device 2, then the sixth indication information sent by the core network element to network device 1 is used to indicate that terminal 1 and terminal 2 support the second positioning type, and the sixth indication information sent by the core network element to network device 2 is used to indicate that terminal 3 supports the second positioning type.

[0376] When the core network element is LMF, LMF and network devices can exchange information through AMF.

[0377] The sixth instruction information can be carried in the Initial Context Setup Request (IPR) exchanged between the AMF and the network device, or it can be carried in other messages exchanged between the AMF and the network device.

[0378] 1103. When any of the M8 network devices needs to locate a terminal that supports the second positioning type, the network device sends a positioning request to the LMC.

[0379] Optional, see Figure 11 Before step 1103, the method further includes:

[0380] 1102A. The core network element sends the LMC location information to each of the M8 network devices. Correspondingly, the M8 network devices receive the LMC location information from the core network element.

[0381] The description related to step 1102A can be found in step 702A above, and will not be repeated here.

[0382] Optional, see Figure 11 Before step 1103, the method further includes:

[0383] 1102B. Core network elements send information about M8 network devices to the LMC.

[0384] The description related to step 1102B can be found in step 902B above, and will not be repeated here.

[0385] Optional, see Figure 11 After step 1103, the method further includes:

[0386] 1104. The core network element sends update information to the LMC. This update information indicates whether the information of Q3 terminals whose second positioning type has changed is supported, where Q3 is a positive integer. Correspondingly, the LMC receives the update information from the core network element.

[0387] The specific implementation of step 1104 is similar to that of step 1005 above, and can be understood by referring to it, so it will not be repeated here.

[0388] Optional, see Figure 11 After step 1103, the method further includes:

[0389] 1105. The core network element sends a seventh indication message to the third network device. This seventh indication message indicates whether the first terminal accessing the third network device supports the second positioning type. The first terminal can be any one or more of the Q3 terminals. Correspondingly, the third network device receives the seventh indication message from the core network element.

[0390] For a description of the seventh instruction information, please refer to scenario 3.1 above, which will not be repeated here.

[0391] For possible scenarios where the first terminal changes from supporting the second positioning type to no longer supporting the second positioning type, or from not supporting the second positioning type to supporting the second positioning type, please refer to scenario 3.1 above, which will not be repeated here.

[0392] Figure 11 The method provided in the illustrated embodiment allows core network elements to authorize network devices to use the second positioning type to locate terminals when they need to be located by sending a sixth instruction message to network devices that support terminal services of the second positioning type. This solves the problem of network devices without LMC initiating positioning.

[0393] In scenario 3.2 above, the core network element can determine the terminals supporting the second positioning type all at once and indicate the supported terminals to the M8 network devices all at once. Alternatively, the core network element can indicate to the network devices whether the current terminal supports the second positioning type during each terminal's access to the core network. That is, if the aforementioned Q4 terminals are multiple terminals, the core network element will need a certain amount of time to complete the process of indicating the supported terminals to the M8 network devices. The following example, using the core network element as AMF and the process of one terminal accessing the core network, illustrates the process of indicating to the network devices whether the current terminal supports the second positioning type.

[0394] See Figure 12 The process includes:

[0395] 1201. The terminal sends an RRC establishment complete message to the network device. Correspondingly, the network device receives the RRC establishment complete message from the terminal.

[0396] 1202. The network device sends an Initial UE message to the AMF. Correspondingly, the AMF receives the Initial UE message from the network device.

[0397] 1203. The AMF sends an Initial Context Establishment Request to the network device, which carries the sixth indication information. Correspondingly, the network device receives the Initial Context Establishment Request from the AMF.

[0398] The sixth indication information is used to indicate whether the terminal supports the second positioning type. The process by which the AMF obtains whether the terminal supports the second positioning type can be found in the relevant description of step 1101, and will not be repeated here.

[0399] in, Figure 12 The function of each message in this application can be found in the prior art. The difference between this application and the prior art is that this application carries the sixth instruction information in the initial context establishment request.

[0400] Scenario 3.3: The terminal indicates to the network device whether it supports the second positioning type.

[0401] In scenario 3.3, see [link / reference]. Figure 13 The positioning method includes:

[0402] 1301. The terminal sends an eighth indication message to the network device. This eighth indication message indicates whether the terminal supports the second positioning type. Correspondingly, the network device receives the eighth indication message from the terminal.

[0403] During the process of accessing the network device, the terminal can send information on whether it supports the second positioning type to the network device, and the network device will store this information in the terminal context.

[0404] The eighth instruction information can be carried in the RRC establishment completion message or in other RRC messages.

[0405] 1302. When the eighth instruction information indicates that the terminal supports the second positioning type, a positioning request is sent to the LMC when the network device needs to locate the terminal.

[0406] Optionally, the network device can obtain the LMC location information through step 1003A or step 1102A above. For details, please refer to the above text for understanding, and it will not be repeated here.

[0407] Optionally, if the eighth indication information indicates that the terminal supports the second positioning type, and the terminal changes from supporting the second positioning type to not supporting the second positioning type, see [reference needed]. Figure 13 After step 1302, the method further includes:

[0408] 1303. The terminal sends a ninth indication message to the network device, indicating that the terminal does not support the second positioning type. Correspondingly, the network device receives the ninth indication message from the terminal. In this case, the network device determines not to perform positioning on the terminal.

[0409] Whether a terminal supports the second positioning type can be indicated by the core network for the terminal, pre-configured in the terminal, or determined by the terminal itself.

[0410] Figure 13 The method provided in the illustrated embodiment allows the terminal to indicate to the network device whether a second location type is supported, enabling the network device to use the second location type to locate certain terminals when it needs to locate them, thereby solving the problem of network devices without LMC initiating location.

[0411] The system architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will understand that, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0412] The foregoing mainly describes the solutions of the embodiments of this application from a methodological perspective. It is understood that each network element, such as the LMC, core network elements (e.g., SMF, AMF), network device, and terminal, includes at least one of the hardware structures and software modules corresponding to the execution of each function in order to achieve the above-mentioned functions. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software-driven hardware manner depends on the specific application and design constraints of the technical solution. Those skilled in the art 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.

[0413] This application embodiment can divide the LMC, core network elements (e.g., SMF, AMF), network devices, and terminals into functional units based on the above method examples. For example, each function can be divided into its own functional unit, or two or more functions can be integrated into one processing unit. The integrated unit can be implemented in hardware or as a software functional unit. It should be noted that the unit division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0414] For example, Figure 14 A possible structural diagram of the positioning device (denoted as positioning device 140) involved in the above embodiments is shown. The positioning device 140 includes a processing unit 1401 and a communication unit 1402. Optionally, it also includes a storage unit 1403. The positioning device 140 can be used to illustrate the structure of LMC, core network elements (e.g., SMF, AMF), network devices, and terminals in the above embodiments.

[0415] when Figure 14 The schematic diagram shown illustrates the structure of the LMC involved in the above embodiments. The processing unit 1401 is used to control and manage the actions of the LMC. For example, the processing unit 1401 is used to execute... Figure 5 All steps in the process, Figure 6 All steps in the process, Figure 7 702B, 703, and 704, Figure 8 All the steps in Figure 9 902B, 903, and 904, Figure 10 All steps in the process, Figure 11 1102B, 1103, and 1104 in the series, Figure 13The actions performed by the LMC in processes 1302 and / or other processes described in the embodiments of this application. Processing unit 1401 can communicate with other network entities via communication unit 1402, for example, with... Figure 5 The core network element communication in the LMC. Storage unit 1403 is used to store the LMC's program code and data.

[0416] when Figure 14 The structural diagram shown illustrates the structure of the core network elements (e.g., SMF, AMF) involved in the above embodiments. The processing unit 1401 is used to control and manage the actions of the core network elements. For example, the processing unit 1401 is used to execute... Figure 5 All steps in the process, Figure 6 601, 602, and 605 in the list, Figure 7 The numbers 701, 702, 702A, 702B, 704, and 705 are included. Figure 8 801, 802, and 805 in the series, Figure 9 The numbers 901, 902, 902A, 902B, 904, and 905 in the series are: Figure 10 Numbers 1001, 1002, and 1005 in the text are not provided. Figure 11 The numbers 1101, 1102, 1102A, 1102B, 1104, and 1105 in the original text are: Figure 12 The actions performed by the core network element in processes 1202 and 1203 (where the core network element is AMF) and / or other processes described in the embodiments of this application. The processing unit 1401 can communicate with other network entities via the communication unit 1402, for example, with... Figure 5 LMC communication in the network. Storage unit 1403 is used to store program code and data of core network elements.

[0417] when Figure 14 The schematic diagram shown illustrates the structure of the network device involved in the above embodiments. The processing unit 1401 is used to control and manage the actions of the network device. For example, the processing unit 1401 is used to execute... Figure 6 The network devices are 603A, 603, and 604 (in this case, any one of the M1 network devices). Figure 6 In the context of 606 (where the network device is the first network device), Figure 7 The 702, 702A, and 703 (in this case, the network device is any one of the M3 network devices), Figure 7 In the 705 (at this point, the network device is the first network device), Figure 8 The 803A, 803, and 804 (in this case, the network device is any one of the M5 network devices), Figure 8 In this context, 806 (at this point, the network device is the second network device) Figure 9 The three network devices are 902, 902A, and 903 (at this point, the network device is any one of the M6 ​​network devices). Figure 9 In the context of 905 (at this point, the network device is the second network device), Figure 10 In this context, 1003A, 1003, and 1004 (at this point, the network device is any one of the M7 network devices) Figure 10 In the context of 1006 (at this point, the network device is a third-party network device), Figure 11 In this context, 1102, 1102A, and 1103 (at this point, the network device is any one of the M8 network devices) Figure 11 In step 1105 (at this point, the network device is a third network device), Figure 12 1101 to 1103 in the middle, Figure 13 The actions performed by the network device in processes 1301 to 1303, and / or other processes described in the embodiments of this application. Processing unit 1401 can communicate with other network entities via communication unit 1402, for example, with... Figure 6 LMC communication in the network. Storage unit 1403 is used to store the program code and data of the network device.

[0418] when Figure 14 The schematic diagram shown illustrates the structure of the terminal involved in the above embodiments. The processing unit 1401 is used to control and manage the actions of the terminal. For example, the processing unit 1401 is used to execute... Figure 12 1201 in the middle, Figure 13 The actions performed by the terminal in processes 1301 and 1303, and / or other processes described in the embodiments of this application. Processing unit 1401 can communicate with other network entities via communication unit 1402, for example, with... Figure 12 The network device communicates within the terminal. Storage unit 1403 is used to store the terminal's program code and data.

[0419] For example, the positioning device 140 can be a device or a chip or chip system.

[0420] When the positioning device 140 is a single device, the processing unit 1401 can be a processor; the communication unit 1402 can be a communication interface, a transceiver, or an input interface and / or an output interface. Optionally, the transceiver can be a transceiver circuit. Optionally, the input interface can be an input circuit, and the output interface can be an output circuit.

[0421] When the positioning device 140 is a chip or chip system, the communication unit 1402 may be a communication interface, input interface and / or output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The processing unit 1401 may be a processor, processing circuit, or logic circuit.

[0422] Figure 14 If the integrated units in the process are implemented as software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. Storage media for storing computer software products include: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.

[0423] This application also provides a hardware structure diagram of a positioning device, see [link]. Figure 15 or Figure 16 The positioning device includes a processor 1501, and optionally, a memory 1502 connected to the processor 1501.

[0424] Processor 1501 can be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program according to the present application. Processor 1501 may also include multiple CPUs, and processor 1501 can be a single-core processor or a multi-core processor. Here, processor can refer to one or more devices, circuits, or processing cores used to process data (e.g., computer program instructions).

[0425] The memory 1502 can be a ROM or other type of static storage device capable of storing static information and instructions, RAM or other type of dynamic storage device capable of storing information and instructions, or it can be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer. This application embodiment does not impose any limitations on this. The memory 1502 can exist independently (in which case the processor can be located outside or inside the positioning device), or it can be integrated with the processor 1501. The memory 1502 can contain computer program code. The processor 1501 is used to execute the computer program code stored in the memory 1502 to implement the method provided in this application embodiment.

[0426] In the first possible implementation, see Figure 15 The positioning device also includes a transceiver 1503. The processor 1501, memory 1502, and transceiver 1503 are connected via a bus. The transceiver 1503 is used to communicate with other devices or communication networks. Optionally, the transceiver 1503 may include a transmitter and a receiver. The device in the transceiver 1503 that implements the receiving function can be considered as a receiver, and the receiver is used to perform the receiving steps in the embodiments of this application. The device in the transceiver 1503 that implements the transmitting function can be considered as a transmitter, and the transmitter is used to perform the transmitting steps in the embodiments of this application.

[0427] Based on the first possible implementation method Figure 15 The structural diagram shown can be used to illustrate the structure of LMC, core network elements (e.g., SMF, AMF), network devices and terminals involved in the above embodiments.

[0428] when Figure 15 The schematic diagram shown illustrates the structure of the LMC involved in the above embodiments. The processor 1501 is used to control and manage the actions of the LMC. For example, the processor 1501 is used to execute... Figure 5 All steps in the process, Figure 6 All steps in the process, Figure 7 702B, 703, and 704, Figure 8 All steps in the process, Figure 9902B, 903, and 904, Figure 10 All steps in the process, Figure 11 1102B, 1103, and 1104 in the series, Figure 13 The actions performed by the LMC in process 1302 and / or other processes described in the embodiments of this application. Processor 1501 can communicate with other network entities via transceiver 1503, for example, with... Figure 5 The core network element communication is handled by the LMC. Memory 1502 is used to store the LMC's program code and data.

[0429] when Figure 15 The schematic diagram shown illustrates the structure of the core network elements (e.g., SMF, AMF) involved in the above embodiments. The processor 1501 is used to control and manage the actions of the core network elements. For example, the processor 1501 is used to execute... Figure 5 All steps in the process, Figure 6 601, 602, and 605 in the list, Figure 7 The numbers 701, 702, 702A, 702B, 704, and 705 are included. Figure 8 801, 802, and 805 in the series, Figure 9 The numbers 901, 902, 902A, 902B, 904, and 905 in the series are: Figure 10 Numbers 1001, 1002, and 1005 in the text are not provided. Figure 11 The numbers 1101, 1102, 1102A, 1102B, 1104, and 1105 in the original text are: Figure 12 The actions performed by the core network element in processes 1202 and 1203 (where the core network element is AMF) and / or other processes described in the embodiments of this application. The processor 1501 can communicate with other network entities via the transceiver 1503, for example, with... Figure 5 LMC communication in the core network. Memory 1502 is used to store program code and data of core network elements.

[0430] when Figure 15 The schematic diagram shown illustrates the structure of the network device involved in the above embodiments. The processor 1501 is used to control and manage the actions of the network device. For example, the processor 1501 is used to execute... Figure 6 The network devices are 603A, 603, and 604 (in this case, any one of the M1 network devices). Figure 6 In the context of 606 (where the network device is the first network device), Figure 7 The 702, 702A, and 703 (in this case, the network device is any one of the M3 network devices), Figure 7 In the 705 (at this point, the network device is the first network device), Figure 8The 803A, 803, and 804 (in this case, the network device is any one of the M5 network devices), Figure 8 In this context, 806 (at this point, the network device is the second network device) Figure 9 The three network devices are 902, 902A, and 903 (at this point, the network device is any one of the M6 ​​network devices). Figure 9 In the context of 905 (at this point, the network device is the second network device), Figure 10 In this context, 1003A, 1003, and 1004 (at this point, the network device is any one of the M7 network devices) Figure 10 In the context of 1006 (at this point, the network device is a third-party network device), Figure 11 In this context, 1102, 1102A, and 1103 (at this point, the network device is any one of the M8 network devices) Figure 11 In step 1105 (at this point, the network device is a third network device), Figure 12 1101 to 1103 in the middle, Figure 13 The actions performed by the network device in processes 1301 to 1303, and / or other processes described in the embodiments of this application. Processor 1501 can communicate with other network entities via transceiver 1503, for example, with... Figure 6 LMC communication in the network. Memory 1502 is used to store the program code and data of the network device.

[0431] when Figure 15 The schematic diagram shown illustrates the structure of the terminal involved in the above embodiments. The processor 1501 is used to control and manage the actions of the terminal. For example, the processor 1501 is used to execute... Figure 12 1201 and Figure 13 The actions performed by the terminal in processes 1301 and 1303, and / or other processes described in the embodiments of this application. Processor 1501 can communicate with other network entities via transceiver 1503, for example, with... Figure 12 The network device communicates within the terminal. Memory 1502 is used to store the terminal's program code and data.

[0432] In a second possible implementation, the processor 1501 includes logic circuitry and at least one of an input interface and an output interface. For example, the output interface is used to perform a sending action in the corresponding method, and the input interface is used to perform a receiving action in the corresponding method.

[0433] Based on the second possible implementation, see Figure 16 , Figure 16 The structural diagram shown can be used to illustrate the structure of LMC, core network elements (e.g., SMF, AMF), network devices and terminals involved in the above embodiments.

[0434] when Figure 16 The schematic diagram shown illustrates the structure of the LMC involved in the above embodiments. The processor 1501 is used to control and manage the actions of the LMC. For example, the processor 1501 is used to execute... Figure 5 All steps in the process, Figure 6 All steps in the process, Figure 7 702B, 703, and 704, Figure 8 All steps in the process, Figure 9 902B, 903, and 904, Figure 10 All steps in the process, Figure 11 1102B, 1103, and 1104 in the series, Figure 13 The actions performed by the LMC in process 1302 and / or other processes described in the embodiments of this application. The processor 1501 can communicate with other network entities through at least one of the input and output interfaces, for example, with... Figure 5 The core network element communication is handled by the LMC. Memory 1502 is used to store the LMC's program code and data.

[0435] when Figure 16 The schematic diagram shown illustrates the structure of the core network elements (e.g., SMF, AMF) involved in the above embodiments. The processor 1501 is used to control and manage the actions of the core network elements. For example, the processor 1501 is used to execute... Figure 5 All steps in the process, Figure 6 601, 602, and 605 in the list, Figure 7 The numbers 701, 702, 702A, 702B, 704, and 705 are included. Figure 8 801, 802, and 805 in the series, Figure 9 The numbers 901, 902, 902A, 902B, 904, and 905 in the series are: Figure 10 Numbers 1001, 1002, and 1005 in the text are not provided. Figure 11 The numbers 1101, 1102, 1102A, 1102B, 1104, and 1105 in the original text are: Figure 12 The actions performed by the core network element in processes 1202 and 1203 (where the core network element is AMF) and / or other processes described in the embodiments of this application. The processor 1501 can communicate with other network entities through at least one of its input and output interfaces, for example, with... Figure 5 LMC communication in the core network. Memory 1502 is used to store program code and data of core network elements.

[0436] when Figure 16The schematic diagram shown illustrates the structure of the network device involved in the above embodiments. The processor 1501 is used to control and manage the actions of the network device. For example, the processor 1501 is used to execute... Figure 6 The network devices are 603A, 603, and 604 (in this case, any one of the M1 network devices). Figure 6 In the context of 606 (where the network device is the first network device), Figure 7 The 702, 702A, and 703 (in this case, the network device is any one of the M3 network devices), Figure 7 In the 705 (at this point, the network device is the first network device), Figure 8 The 803A, 803, and 804 (in this case, the network device is any one of the M5 network devices), Figure 8 In this context, 806 (at this point, the network device is the second network device) Figure 9 The three network devices are 902, 902A, and 903 (at this point, the network device is any one of the M6 ​​network devices). Figure 9 In the context of 905 (at this point, the network device is the second network device), Figure 10 In this context, 1003A, 1003, and 1004 (at this point, the network device is any one of the M7 network devices) Figure 10 In the context of 1006 (at this point, the network device is a third-party network device), Figure 11 In this context, 1102, 1102A, and 1103 (at this point, the network device is any one of the M8 network devices) Figure 11 In step 1105 (at this point, the network device is a third network device), Figure 12 1101 to 1103 in the middle, Figure 13 The actions performed by the network device in processes 1301 to 1303, and / or other processes described in the embodiments of this application. Processor 1501 can communicate with other network entities through at least one of its input and output interfaces, for example, with... Figure 6 LMC communication in the network. Memory 1502 is used to store the program code and data of the network device.

[0437] when Figure 16 The schematic diagram shown illustrates the structure of the terminal involved in the above embodiments. The processor 1501 is used to control and manage the actions of the terminal. For example, the processor 1501 is used to execute... Figure 12 1201 and Figure 13 Actions performed by the terminal in processes 1301 and 1303, and / or other processes described in the embodiments of this application. Processor 1501 can communicate with other network entities through at least one of its input and output interfaces, for example, with... Figure 12The network device communicates within the terminal. Memory 1502 is used to store the terminal's program code and data.

[0438] In implementation, each step of the method provided in this embodiment can be completed by integrated logic circuits in the processor or by instructions in software form. The steps of the method disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0439] This application also provides a computer-readable storage medium including computer-executable instructions that, when run on a computer, cause the computer to perform any of the methods described above.

[0440] This application also provides a computer program product comprising computer execution instructions that, when run on a computer, cause the computer to perform any of the methods described above.

[0441] This application also provides a communication system, including any one or more of the following: LMC, core network elements (e.g., SMF, AMF), network devices, and terminals.

[0442] This application also provides a positioning device, including a processor and an interface. The processor is coupled to a memory through the interface. When the processor executes a computer program or computer execution instructions in the memory, any of the methods provided in the above embodiments are executed.

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

[0444] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, the disclosure, and the appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0445] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the scope of protection of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the scope of protection of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and modifications.

Claims

1. A positioning method, characterized in that, include: The Location Management Component (LMC) sends a registration request to the core network element, the registration request being used to request registration with the core network element. The LMC receives a registration response from the core network element. The registration response includes information on M1 network devices that support the second positioning type, where M1 is an integer greater than 0. The LMC sends a second indication information corresponding to each of the M1 network devices, the second indication information being used to indicate that the network device corresponding to it supports the second positioning type; The LMC receives update information from the core network element. The update information is used to indicate whether the information of M2 network devices that have changed according to the second positioning type is supported, where M2 is an integer greater than 0.

2. The method according to claim 1, characterized in that, The method further comprises: The LMC sends its location information to each of the M1 network devices.

3. The method according to claim 2, characterized in that, The location information of the LMC is either the identifier of the network device where the LMC is located or the identifier of the LMC itself.

4. The method according to claim 1, characterized in that, The method further comprises: The LMC sends a third indication information to the first network device, the third indication information being used to indicate whether the first network device supports the second positioning type, the first network device being any one of the M2 network devices.

5. The method according to any one of claims 1-3, characterized in that, The second location type is Radio Access Network Initiated Location Request (RI-LR).

6. A positioning method, characterized in that, include: The network device receives fourth indication information from the Location Management Component (LMC), the fourth indication information being used to indicate one or more cells that support the second location type, and the cell indicated by the fourth indication information belonging to the network device; When the network device needs to locate a terminal in a cell that supports the second location type, the network device sends a location request to the LMC; The network device receives a fifth indication information from the LMC. The fifth indication information is used to indicate whether the first cell of the network device supports the second positioning type. The first cell is any one or more cells from N2 cells. The N2 cells are cells whose information on whether they support the second positioning type has changed. N2 is an integer greater than 0.

7. The method according to claim 6, characterized in that, The method further comprises: The network device receives the location information of the LMC from the LMC.

8. The method according to claim 7, characterized in that, The location information of the LMC is either the identifier of the network device where the LMC is located or the identifier of the LMC itself.

9. The method according to any one of claims 6-8, characterized in that, The second location type is Radio Access Network Initiated Location Request (RI-LR).

10. A positioning method, characterized in that, include: The Location Management Component (LMC) sends a registration request to the core network element, the registration request being used to request registration with the core network element. The LMC receives a registration response from the core network element. The registration response includes information on Q1 terminals that support the second positioning type. The Q1 terminals access M7 network devices, where Q1 and M7 are both integers greater than 0. The LMC sends a sixth indication information corresponding to each of the M7 network devices. The sixth indication information is used to indicate one or more terminals that support the second positioning type. The one or more terminals indicated by the sixth indication information access the network device corresponding to the sixth indication information. The LMC receives update information from the core network element. The update information is used to indicate whether the information of Q2 terminals that have changed according to the second positioning type is supported, where Q2 is an integer greater than 0.

11. The method according to claim 10, characterized in that, The registration response also includes information about the M7 network devices.

12. The method according to claim 10 or 11, characterized in that, The method further comprises: The LMC sends its location information to each of the M7 network devices.

13. The method according to claim 12, characterized in that, The location information of the LMC is either the identifier of the network device where the LMC is located or the identifier of the LMC itself.

14. The method according to claim 10, characterized in that, The method further comprises: The LMC sends a seventh indication message to the third network device. The seventh indication message is used to indicate whether the first terminal accessing the third network device supports the second positioning type. The first terminal is any one or more of the Q2 terminals.

15. The method according to claim 10 or 11, characterized in that, The second location type is Radio Access Network Initiated Location Request (RI-LR).

16. A positioning device, characterized in that, include: Processing unit and communication unit; The processing unit is configured to send a registration request to the core network element through the communication unit, the registration request being used to request registration with the core network element; The processing unit is further configured to receive a registration response from the core network element through the communication unit, wherein the registration response includes information on M1 network devices supporting the second positioning type, and M1 is an integer greater than 0; The processing unit is further configured to send a second indication information corresponding to each of the M1 network devices to each network device through the communication unit, wherein the second indication information is used to indicate that the network device corresponding to it supports the second positioning type; The processing unit is further configured to receive update information from the core network element through the communication unit. The update information is used to indicate whether the information of M2 network devices that have changed according to the second positioning type is supported, where M2 is an integer greater than 0.

17. The positioning device according to claim 16, characterized in that, The processing unit is also configured to send the location information of the positioning device to each of the M1 network devices through the communication unit.

18. The positioning device according to claim 17, characterized in that, The location information of the positioning device is the identifier of the network device where the positioning device is located or the identifier of the positioning device.

19. The positioning device according to claim 16, characterized in that, The processing unit is further configured to send third indication information to the first network device through the communication unit. The third indication information is used to indicate whether the first network device supports the second positioning type. The first network device is any one of the M2 network devices.

20. The positioning device according to any one of claims 16-18, characterized in that, The second location type is Radio Access Network Initiated Location Request (RI-LR).

21. A positioning device, characterized in that, include: Processing unit and communication unit; The processing unit is configured to receive fourth indication information from the location management component (LMC) via the communication unit. The fourth indication information is used to indicate one or more cells that support the second location type, and the cell indicated by the fourth indication information belongs to the location device. The processing unit is further configured to send a positioning request to the LMC through the communication unit when the positioning device needs to locate a terminal in a cell that supports the second positioning type; The processing unit is further configured to receive fifth indication information from the LMC via the communication unit. The fifth indication information is used to indicate whether the first cell of the positioning device supports the second positioning type. The first cell is any one or more cells among N2 cells. The N2 cells are cells whose information on whether the second positioning type is supported has changed. N2 is an integer greater than 0.

22. The positioning device according to claim 21, characterized in that, The processing unit is also configured to receive the location information of the LMC from the LMC via the communication unit.

23. The positioning device according to claim 22, characterized in that, The location information of the LMC is the identifier of the positioning device where the LMC is located or the identifier of the LMC itself.

24. The positioning device according to any one of claims 21-23, characterized in that, The second location type is Radio Access Network Initiated Location Request (RI-LR).

25. A positioning device, characterized in that, include: Processing unit and communication unit; The processing unit is configured to send a registration request to the core network element through the communication unit, the registration request being used to request registration with the core network element; The processing unit is further configured to receive a registration response from the core network element through the communication unit. The registration response includes information on Q1 terminals that support the second positioning type. The Q1 terminals access M7 network devices, where Q1 and M7 are both integers greater than 0. The processing unit is further configured to send a sixth indication information corresponding to each of the M7 network devices through the communication unit, the sixth indication information being used to indicate one or more terminals supporting the second positioning type, and the one or more terminals indicated by the sixth indication information accessing the network device corresponding to the sixth indication information; The processing unit is further configured to receive update information from the core network element through the communication unit. The update information is used to indicate whether the information of Q2 terminals that have changed according to the second positioning type is supported, where Q2 is an integer greater than 0.

26. The positioning device according to claim 25, characterized in that, The registration response also includes information about the M7 network devices.

27. The positioning device according to claim 25 or 26, characterized in that, The processing unit is also configured to send the location information of the positioning device to each of the M7 network devices through the communication unit.

28. The positioning device according to claim 27, characterized in that, The location information of the positioning device is the identifier of the network device where the positioning device is located or the identifier of the positioning device.

29. The positioning device according to claim 25, characterized in that, The processing unit is further configured to send a seventh indication information to the third network device through the communication unit. The seventh indication information is used to indicate whether the first terminal accessing the third network device supports the second positioning type. The first terminal is any one or more of the Q2 terminals.

30. The positioning device according to claim 25 or 26, characterized in that, The second location type is Radio Access Network Initiated Location Request (RI-LR).

31. A positioning device, characterized in that, include: processor; The processor is connected to a memory for storing computer execution instructions. The processor executes the computer execution instructions stored in the memory to enable the positioning device to implement the method as claimed in any one of claims 1-5, or any one of claims 6-9, or any one of claims 10-15.

32. A positioning device, characterized in that, include: A processor and an interface, the processor being coupled to a memory via the interface, wherein when the processor executes a computer program or computer execution instructions in the memory, the method of any one of claims 1-5, or any one of claims 6-9, or any one of claims 10-15 is performed.

33. A positioning device, characterized in that, The positioning device includes a processor, a memory, and a computer program stored in the memory and running on the processor, wherein when the computer program is run, the positioning device performs the method as claimed in any one of claims 1-5, or any one of claims 6-9, or any one of claims 10-15.

34. A computer-readable storage medium, characterized in that, Includes computer execution instructions, which, when executed on a computer, cause the computer to perform the method as claimed in any one of claims 1-5, or any one of claims 6-9, or any one of claims 10-15.

35. A computer program product, characterized in that, Includes computer execution instructions, which, when executed on a computer, cause the computer to perform the method as claimed in any one of claims 1-5, or any one of claims 6-9, or any one of claims 10-15.

Images