WO2021146924A1 - 一种定位方法及对应装置 - Google Patents

一种定位方法及对应装置 Download PDF

Info

Publication number
WO2021146924A1
WO2021146924A1 PCT/CN2020/073532 CN2020073532W WO2021146924A1 WO 2021146924 A1 WO2021146924 A1 WO 2021146924A1 CN 2020073532 W CN2020073532 W CN 2020073532W WO 2021146924 A1 WO2021146924 A1 WO 2021146924A1
Authority
WO
WIPO (PCT)
Prior art keywords
positioning
access network
network device
lmc
terminal
Prior art date
Application number
PCT/CN2020/073532
Other languages
English (en)
French (fr)
Inventor
张宏平
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2020/073532 priority Critical patent/WO2021146924A1/zh
Publication of WO2021146924A1 publication Critical patent/WO2021146924A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management

Definitions

  • This application relates to the field of wireless communication technology, and in particular to a positioning method and corresponding device.
  • LTE long term evolution
  • NR New Radio
  • Rel release, Rel
  • LMF location management function
  • AMF access and mobility management function
  • the 3rd generation partnership project (3rd generation partnership project, 3GPP) approved a research project to study the positioning function (the function of the LMF) on the side of the access network, which is called the location management component (location management component). component, LMC).
  • 3GPP has no specific plans for how the target client initiates a location request to the LMC and how the LMC returns location information to the target client.
  • This application provides a positioning method and corresponding device to clarify the specific process of when an access network device locates a terminal based on LMC, the terminal initiates a positioning request to the access network device and the access network device returns the positioning result to the terminal, and can Ensure low positioning delay and improve user experience.
  • an embodiment of the present application provides a positioning method, including: an access network device receives a positioning request from a terminal, wherein the access network device supports positioning based on a positioning management component LMC; The positioning request, and positioning the terminal based on the LMC; the access network device sends a positioning result to the terminal.
  • the terminal directly initiates a positioning request to the access network device supporting the LMC, and the access network device directly returns the positioning result to the terminal after positioning the terminal based on the LMC.
  • the embodiment of the application clarifies the specific process of the terminal initiating a positioning request to the access network device and the access network device returning the positioning result to the terminal, and at the same time, it can avoid that the positioning request and the positioning result are sent to the core network and then returned to the access network device. It can ensure low positioning delay.
  • the access network device may also send first indication information to the terminal, where the first indication information is used to indicate the location request.
  • the access network equipment supports LMC-based positioning.
  • the access network device indicates to the terminal the first indication information that it supports LMC positioning, so that the terminal can determine whether to initiate a positioning request or determine whether to initiate a positioning request based on LMF based on the first indication information, thereby enabling the terminal to determine whether to initiate a positioning request or whether to initiate a positioning request based on LMF Avoid the situation where the terminal initiates a corresponding positioning request but the access network device does not support LMC, which results in positioning failure.
  • the first indication information may include: system information broadcast by the access network device; or, response information returned by the access network device in response to the terminal's inquiry request,
  • the query request is used to query whether the access network device supports positioning based on the LMC.
  • the access network device can send the indication information that it supports the positioning of the LMC to the terminal by broadcasting or responding to the inquiry request of the terminal, which improves the reliability and flexibility of the solution.
  • the positioning request may also include positioning service quality QoS information of the terminal, and/or positioning capability information of the terminal; wherein, the QoS information includes: time delay, accuracy At least one of a QoS level or a positioning method; the positioning capability information includes: a positioning method supported by the terminal, and a measurement capability corresponding to the positioning method supported by the terminal.
  • the access network device does not need to initiate an additional process of acquiring the positioning QoS information and/or positioning capability information of the terminal, which can save system overhead and further reduce time delay.
  • the positioning result may include second indication information of the location information of the terminal.
  • the positioning request is carried in an LTE positioning protocol LPP message or RRC message.
  • the positioning request is carried in the LPP message or the RRC message, which can reduce the system overhead.
  • the access network device and the LMC are connected through a first interface. After the access network device receives the positioning request from the terminal, the access network device may also forward the positioning request to the LMC through the first interface. Before the access network device sends the positioning result to the terminal, the access network device may also receive the positioning result from the LMC through the first interface.
  • the LMC is an independent component and is connected to the access network device.
  • the LMC can interact with the access network device through the first interface, ensuring that the access network device can efficiently locate the terminal based on the LMC and reduce the positioning delay .
  • the access network device may also send a first interface establishment request message to the LMC for requesting establishment of the access network The first interface between the device and the LMC; the access network device receives the first interface establishment response message returned by the LMC, where the first interface establishment response message carries the QoS information provided by the LMC.
  • the LMC can establish a first interface with the access network device, thereby enabling the access network device to interact with the LMC, and ensuring that the access network device can locate the terminal based on the LMC.
  • the access network device by carrying the QoS information provided by the LMC in the first interface establishment response message, it is possible to prevent the access network device from initiating an additional process of obtaining the QoS information provided by the LMC, further saving system overhead and reducing positioning delay.
  • the access network device may also send to the core network third indication information that the access network device supports LMC-based positioning.
  • the access network device can actively inform the connected core network of the third indication information that it supports LMC, so that the core network can decide whether to allow the access network device/LMC to locate the terminal based on LMC .
  • the third indication information may be carried in an interface establishment request message sent by the access network device to the core network.
  • the core network can no longer initiate an additional process for obtaining whether the access network device supports LMC-based positioning, which can further save system overhead and reduce positioning delay.
  • the third indication information may include one or more of the following information: the identification ID of the LMC; the positioning method of the LMC; the time delay of the LMC; Describe the positioning accuracy of the LMC.
  • the core network device can learn more detailed information that the access network device supports LMC positioning, which can further save system overhead and improve the management capability of the core network.
  • the access network device may also receive a core network sent by the core network whether the core network allows the access network device to use LMC Fourth indication information for positioning the terminal; before the access network device locates the terminal based on the LMC, the access network device may also determine that the fourth indication information is used to indicate the core The network allows the access network device to use the LMC to locate the terminal.
  • the access network device can initiate LMC-based positioning of the terminal only when it receives the indication information from the core network that the access network device allows the access network device to use the LMC to locate the terminal, which can effectively protect the privacy and security of the terminal.
  • the fourth indication information is carried in a terminal context establishment request message sent by the core network to the access network device.
  • the access network device does not need to initiate an additional process of acquiring the fourth indication information, which further saves system overhead and reduces positioning delay.
  • the access network device may also send the fourth indication information to the access network device after the terminal handover.
  • the access network device after the handover can know in time whether the core network allows the access network device to use the LMC to locate the terminal, which further guarantees the privacy and security of the terminal.
  • an embodiment of the present application provides a positioning method, including: a terminal sends a positioning request to an access network device, where the access network device supports positioning based on a positioning management component LMC; and the terminal receives the access The positioning result sent by the network device.
  • the terminal may also receive first indication information sent by the access network device, where the first indication information is used to indicate The access network equipment supports LMC-based positioning.
  • the first indication information may include: system information broadcast by the access network device; or, response information returned by the access network device in response to the terminal's inquiry request,
  • the query request is used to query whether the access network device supports positioning based on the LMC.
  • the positioning request may include positioning service quality QoS information of the terminal, and/or positioning capability information of the terminal; wherein, the QoS information may include: time delay, accuracy At least one of a QoS level or a positioning method; the positioning capability information may include: a positioning method supported by the terminal, and a measurement capability corresponding to the positioning method supported by the terminal.
  • the positioning result may include second indication information of the location information of the terminal.
  • the positioning request may be carried in an LTE positioning protocol LPP message or RRC message.
  • an embodiment of the present application provides a positioning method, including: a positioning management component LMC receives a positioning request sent by an access network device; the LMC responds to the positioning request, and locates the terminal based on the LMC; The LMC sends the positioning result to the access network device, so that the access network device forwards the positioning result to the terminal.
  • the access network device is connected to the LMC through a first interface;
  • the LMC receiving a positioning request sent by the access network device includes: the LMC receives the access network device through the first interface The sent positioning request;
  • the LMC sending the positioning result to the access network device includes: the LMC sending the positioning result to the access network device through the first interface.
  • the LMC may also receive a first interface establishment request message sent by the access network device, where the first interface establishment request message The request message is used to request the establishment of the first interface between the access network device and the LMC; the LMC sends a first interface establishment response message to the access network device, wherein the first interface establishment response message Carry the QoS information provided by the LMC.
  • an embodiment of the present application provides a positioning method, including: a core network device receives an initial UE message sent by an access network device, wherein the access network device supports positioning based on a positioning management component LMC; The access network device sends fourth indication information, where the fourth indication information is used to indicate whether to allow the access network device or the LMC to locate the terminal device based on the LMC.
  • the core network may also receive the access network device that supports LMC-based The third indication information for positioning.
  • the third indication information may also be carried in an interface establishment request message sent by the access network device to the core network.
  • the third indication information may include one or more of the following information: the identification ID of the LMC; the positioning method of the LMC; the time delay of the LMC; Describe the positioning accuracy of the LMC.
  • the fourth indication information may be carried in a terminal device context establishment request message sent by the core network to the access network device.
  • the content of the fourth indication information may include one or more of the following items: yes/no to allow LMC-based MO-LR positioning; yes/no to allow LMC-based RI -LR positioning; Yes/No allows LMC-based MT-LR positioning; Yes/No allows LMC-based NI-LR positioning.
  • an embodiment of the present application provides an access network device, including a unit/module for executing the method described in the first aspect of the embodiment of the present application.
  • the receiving unit is configured to receive a positioning request from the terminal, where the access network device supports positioning based on the positioning management component LMC;
  • a processing unit configured to respond to the positioning request and locate the terminal based on the LMC
  • the sending unit is used to send the positioning result to the terminal.
  • an embodiment of the present application provides a terminal including a unit/module for executing the method described in the second aspect of the embodiment of the present application.
  • a sending unit configured to send a positioning request to an access network device, where the access network device supports positioning based on the positioning management component LMC;
  • the receiving unit is configured to receive the positioning result sent by the access network device.
  • an embodiment of the present application provides a location management component LMC, including a unit/module for executing the method described in the third aspect of the embodiment of the present application.
  • LMC location management component
  • the receiving unit is used to receive the positioning request sent by the access network device
  • a processing unit configured to respond to the positioning request and locate the terminal based on the LMC
  • the sending unit is configured to send the positioning result to the access network device, so that the access network device forwards the positioning result to the terminal.
  • an embodiment of the present application further provides a core network device, including a unit/module for executing the method described in the fourth aspect of the embodiment of the present application.
  • a core network device including a unit/module for executing the method described in the fourth aspect of the embodiment of the present application.
  • a receiving unit configured to receive an initial UE message sent by an access network device, where the access network device supports positioning based on the positioning management component LMC;
  • the sending unit is configured to send fourth indication information to the access network device, where the fourth indication information is used to indicate whether to allow the access network device or the LMC to locate the terminal device based on the LMC.
  • an embodiment of the present application provides a communication device, including:
  • At least one processor and a memory and a communication interface communicatively connected with the at least one processor;
  • the memory stores instructions that can be executed by the at least one processor, and the at least one processor executes the instructions such as the first aspect, the second aspect, and the third aspect of the embodiment of the present application by executing the instructions stored in the memory.
  • an embodiment of the present application provides a computer-readable storage medium, including a program or instruction.
  • the program or instruction runs on a computer, it executes the first, second, and third aspects of the embodiments of the present application.
  • an embodiment of the present application provides a chip, which is coupled with a memory, and is used to read and execute program instructions stored in the memory to implement the first aspect, second aspect, and second aspect of the embodiment of the present application.
  • Figure 1 is a schematic diagram of the positioning architecture in LTE and NR Rel-16;
  • Figure 2 is a schematic diagram of the protocol stack involved in the interaction between the LMF and the terminal;
  • FIG. 3 is a flowchart of a positioning method based on the positioning architecture shown in FIG. 1;
  • Figure 4 is a flowchart of a method based on LMF positioning in a MO-RL scenario
  • 5A, 5B, and 5C are schematic diagrams of three possible network architectures applicable to the embodiments of this application.
  • 6A and 6B are schematic diagrams of protocol stacks involved when the LMC interacts with the terminal;
  • FIG. 7 is a flowchart of a positioning method provided by an embodiment of the application.
  • Figure 8 is a flowchart of a positioning method in the Alternative 1 scenario
  • Figure 9 is a flowchart of a positioning method in Alternative 2 and Alternative 3 scenarios.
  • Figure 10 is a flowchart of another positioning method in Alternative 2 and Alternative 3 scenarios
  • Figure 11 is a flow chart of a method for a base station to inform the core network of its own LMC support information
  • FIG. 12 is a flowchart of a method for the core network to indicate whether to allow the base station to perform LMC-based positioning for the terminal;
  • Figure 13 is a flowchart of a method for a source base station to transmit instruction information to a target base station
  • FIG. 14 is a schematic structural diagram of an apparatus 1400 provided by an embodiment of the application.
  • FIG. 15 is a schematic structural diagram of an apparatus 1500 provided by an embodiment of this application.
  • FIG. 16 is a schematic structural diagram of an apparatus 1600 provided by an embodiment of this application.
  • FIG. 17 is a schematic structural diagram of an apparatus 1700 according to an embodiment of the application.
  • FIG. 18 is a schematic structural diagram of an apparatus 1800 provided by an embodiment of this application.
  • the terminal equipment involved in the embodiments of this application which can also be called a terminal, is an entity on the user side that is used to receive or transmit signals, and is used to send uplink signals to or receive from network equipment. Downlink signal. It includes devices that provide users with voice and/or data connectivity. For example, it may include a handheld device with a wireless connection function or a processing device connected to a wireless modem. The terminal device can communicate with the core network via a radio access network (RAN), and exchange voice and/or data with the RAN.
  • RAN radio access network
  • the terminal equipment may include user equipment (UE), V2X terminal equipment, wireless terminal equipment, mobile terminal equipment, device-to-device communication (device-to-device, D2D) terminal equipment, machine-to-machine/machine-type communication ( machine-to-machine/machine-type communications, M2M/MTC) terminal equipment, Internet of things (IoT) terminal equipment, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile station) , Remote station (remote station), access point (access point, AP), remote terminal (remote terminal), access terminal (access terminal), user terminal (user terminal), user agent (user agent), or user equipment (user device), wearable devices, in-vehicle devices, etc.
  • IoT Internet of things
  • subscriber unit subscriber unit
  • subscriber station subscriber station
  • mobile station mobile station
  • Remote station remote station
  • access point access point
  • AP remote terminal
  • remote terminal remote terminal
  • access terminal access terminal
  • user terminal user terminal
  • user agent
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices or smart wearable devices, etc. It is a general term for using wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes Wait.
  • a wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. Wearable devices are not only a kind of hardware device, but also realize powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized, complete or partial functions that can be achieved without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, and need to cooperate with other devices such as smart phones.
  • Use such as all kinds of smart bracelets, smart helmets, smart jewelry, etc. for physical sign monitoring.
  • the various terminal devices described above if they are located on the vehicle (for example, placed in the vehicle or installed in the vehicle), can be regarded as vehicle-mounted terminal equipment, for example, the vehicle-mounted terminal equipment is also called on-board unit (OBU). ).
  • OBU on-board unit
  • the core network involved in the embodiments of this application may include network equipment that processes and forwards user signaling and data.
  • it includes core network equipment such as AMF, session management function (session management function, SMF), and user plane gateway.
  • the user plane gateway can be a server with functions such as mobility management, routing, and forwarding of user plane data, and is generally located on the network side, such as a serving gateway (SGW) or a packet data network gateway (PGW) ) Or user plane network element function entity (user plane function, UPF), etc.
  • SGW serving gateway
  • PGW packet data network gateway
  • UPF user plane network element function entity
  • AMF and SMF are equivalent to mobility management entities (MME) in the LTE system.
  • AMF is mainly responsible for access
  • SMF is mainly responsible for session management.
  • the core network may also include other network elements, which are not listed here.
  • the NG-RAN involved in the embodiments of this application may include one or more access network devices.
  • the access network equipment in NG-RAN may also be called a base station, or RAN node, or RAN equipment.
  • Access network equipment is an entity on the network side that is used to transmit and/or receive signals. It can be used to convert received air frames and Internet protocol (IP) packets to each other, as a terminal and access network Between the rest of the router, where the rest of the access network can include IP networks and so on.
  • IP Internet protocol
  • the access network equipment can also coordinate the attribute management of the air interface.
  • the access network equipment may be an evolved Node B (eNB or e-NodeB) in LTE, and an eNB is a device deployed in a radio access network that meets the 4G standard and provides wireless communication functions for the UE.
  • the access network equipment can also be a new radio controller (NR controller), a gNode B (gNB) in a 5G system, a centralized unit, a new radio base station, and It is a remote radio module, which can be a micro base station (also called a small station), a relay, a distributed unit, a macro base station in various forms, and a transmission and reception Point (transmission reception point, TRP), transmission measurement function (transmission measurement function, TMF) or transmission point (transmission point, TP) or any other wireless access equipment, or base station in next-generation communications, but this embodiment does not Limited to this.
  • NR controller new radio controller
  • gNB gNode B
  • TRP transmission and reception Point
  • TMF transmission measurement function
  • TP transmission point
  • a base station (such as gNB) can be composed of a centralized unit (CU) and a distributed unit (DU), that is, the function of the base station in the original LTE access network is split, and the function of the base station in the original LTE access network is split. Part of the functions of the base station are deployed in one CU, and the remaining functions are deployed in the DU. Multiple DUs share the same CU, which can save costs and facilitate network expansion.
  • the segmentation of the CU and the DU can be segmented according to the protocol stack.
  • the RRC layer, the SDAP layer, and the PDCP layer are deployed in the CU, and the remaining radio link control RLC layer, MAC layer, and PHY layer are deployed in the DU.
  • CU and DU can be connected through F1 interface.
  • CU represents the gNB connected to the core network through the NG interface
  • CU represents the gNB connected to other gNBs through the Xn interface.
  • the CU can also be divided into CU-control plane (CP) and CU-user plan (UP).
  • CU-CP is responsible for the control plane function, mainly including RRC and PDCP corresponding to the control plane, namely PDCP-C.
  • PDCP-C is mainly responsible for encryption and decryption of control plane data, integrity protection, data transmission, etc.
  • CU-UP is responsible for user plane functions, mainly including SDAP and PDCP corresponding to the user plane, namely PDCP-U.
  • SDAP is mainly responsible for processing the data of the core network and mapping the flow to the bearer.
  • PDCP-U is mainly responsible for data encryption and decryption, integrity protection, header compression, serial number maintenance, data transmission, etc.
  • CU-CP and CU-UP are connected through the E1 interface.
  • CU-CP represents that gNB is connected to the core network through the NG interface.
  • the CU-UP is connected to the DU through the F1 interface user plane, namely F1-U.
  • PDCP-C is also in CU-UP.
  • system and “network” in the embodiments of this application can be used interchangeably.
  • plurality means two or more.
  • and/or describes the association relationship of the associated objects, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone.
  • the character "/”, unless otherwise specified, generally indicates that the associated objects before and after are in an "or" relationship.
  • FIG 1 is a schematic diagram of the positioning architecture in LTE and NR Rel-16. As shown in Figure 1, the network elements/modules involved mainly include the next generation radio access network (NGRAN), terminal and core Three parts of the net.
  • NGRAN next generation radio access network
  • the core network includes location management function (LMF), access and mobility management function (AMF), service location protocol (service location protocol, SLP), and evolution service mobile location center ( evolved serving mobile location centre, E-SMLC) and so on.
  • the location server that is, the location management function (LMF) is connected to the AMF, and the LMF and the AMF are connected through the NLs interface.
  • LMF is responsible for supporting different types of location services related to the terminal, including the positioning of the terminal and the delivery of auxiliary data to the terminal.
  • AMF can receive terminal-related location service requests from the 5th generation core network location services (5GC LCS) entity, or AMF itself can initiate some location services on behalf of specific terminals and forward location service requests To LMF. After obtaining the location information returned by the terminal, the relevant location information is returned to the 5GC LCS entity.
  • 5GC LCS 5th generation core network location services
  • the NG RAN may include next generation node B (gNB), next generation evolved nodeB (ng-eNB), and so on.
  • gNB next generation node B
  • ng-eNB next generation evolved nodeB
  • the gNB and the ng-eNB are connected through the Xn interface, and the LMF and the ng-eNB/gNB are connected through the NG-C interface.
  • the terminal can measure downlink signals from NG RAN and other sources to support positioning.
  • the gNB/ng-eNB can provide measurement information for the terminal and convey this information to the LMF.
  • the possible information exchanges between the LMF and the terminal include the following: 1) The information exchange between the LMF and the ng-eNB/gNB through the NR positioning protocol a (NR positioning protocol a, NRPPa) message, such as obtaining positioning reference signals (positioning reference) signals, PRS), sounding reference signal (sounding reference signal, SRS) configuration information, cell timing, cell location information, etc.; 2) LMF and terminal transfer terminal capability information through LTE positioning protocol (LTE positioning protocol, LPP) messages , Auxiliary information transmission, measurement information transmission, etc.
  • NR positioning protocol a NR positioning protocol a, NRPPa
  • LMF and terminal transfer terminal capability information through LTE positioning protocol (LTE positioning protocol, LPP) messages , Auxiliary information transmission, measurement information transmission, etc.
  • FIG. 2 is a schematic diagram of the protocol stack involved in the interaction between the LMF and the terminal.
  • the protocol stack used by the terminal to interact with the NG RAN includes from top to bottom: LPP, non-access layer (non-access layer) -access stratum, NAS), radio resource control (radio resource control, RRC), packet data convergence protocol (packet data convergence protocol, PDCP), radio link control (radio link control, RLC), medium access control (medium access) control, MAC), layer (layer, L) 1,
  • the protocol stack used by the NG RAN to interact with the terminal includes from top to bottom: RRC, PDCP, RLC, MAC, L1; NG-RAN and AMF pass NG- C interface connection
  • the protocol stack used to interact with AMF on the NG RAN side includes from top to bottom: NG interface application protocol (NGAP), stream control transmission protocol (SCTP), internet interconnection Protocol (NGAP), packet data convergence protocol (packet data convergence protocol, PDCP), radio link control (radio
  • the interaction information between the LMF and the terminal can be carried by the LPP message.
  • the LPP message is sent through the Uu interface and the NG-C interface.
  • the LPP message will be encapsulated as NAS signaling.
  • the base station receives the NAS signaling of the terminal (the base station does not Know that the terminal is sending an LPP message) and then forward it to the AMF.
  • the AMF obtains the LPP message and delivers it to the LMF.
  • the LPP message sent from the LMF side is encapsulated as a NAS signaling and sent to the base station. After receiving the NAS signaling, it is directly transferred to the terminal (the base station does not know the LPP message contained in the received NAS signaling).
  • the information exchanged between the LMF and the base station is carried by NRPPa messages and sent through the NG-C interface.
  • Fig. 3 is a flowchart of a method for performing positioning based on the positioning architecture shown in Fig. 1, including:
  • Steps 1a/1b the positioning client requests to obtain the location of the terminal and sends the request to the AMF, or the service AMF of the terminal needs to obtain the location of the terminal due to some reasons (such as emergency calls).
  • Step 2 If the terminal is in the idle state, the AMF sends a page to make the terminal enter the connected state, and the AMF sends a positioning request to the LMF;
  • Step 3a/3b LMF initiates the positioning process, for example, LMF obtains the positioning capability of the terminal from the terminal, obtains positioning measurement or auxiliary information from the serving base station, obtains the position or positioning measurement result from the terminal, or sends positioning auxiliary information to the terminal, etc. ;
  • Step 4 The LMF calculates the position of the terminal based on the measurement result of the terminal or the base station, and sends the position of the terminal to the AMF in the positioning service response message;
  • Steps 5a/5b The AMF sends the location of the terminal to the positioning client, or uses the location of the terminal for emergency calls.
  • MO-LR mobile originated location request
  • MT-LR mobile terminated location request
  • NI-LR network induced location request
  • 4 RI-LR RAN induced location request
  • RAN induced location request is a terminal's access network (such as a base station) initiating a request to obtain the terminal's location information.
  • FIG. 4 shows a flow chart of LMF-based positioning in the MO-RL scenario.
  • the process of the terminal initiating a positioning request is: the terminal sends a NAS message, It is used to indicate to the AMF to request the location information of the terminal, and then the AMF interacts with the LMF.
  • the process of AMF returning location information is: after the AMF obtains the location of the terminal, the AMF sends a NAS corresponding message to the terminal, carrying the location information.
  • LMC location management component
  • the embodiment of the present application provides a positioning method: the terminal sends a request message to the AMF via the base station to request the location information of the terminal, and the AMF sends the request to the LMC (for Alternative 2 and Alternative 3, the AMF is sent to the base station, The base station then sends it to the LMC); after the LMC obtains the location information, the LMC first sends a response message carrying the location information to the AMF, and the AMF sends the response message to the terminal through the base station.
  • the above process is similar to the LMF-based positioning process, so the positioning request and the positioning result still need to pass through the core network AMF, and the positioning process passes through many nodes and the delay overhead is relatively large.
  • the embodiment of the present application also provides another positioning method: the terminal directly initiates a positioning request to the base station supporting LMC through the LPP message or the RRC message, and the base station performs the specific positioning process of the terminal (that is, the process of obtaining the location information of the terminal). )
  • the LPP process is still used; after the base station obtains the location information of the terminal, it directly returns the location information to the terminal through an LPP message or an RRC message. In this way, it can avoid that the positioning request and the position information are first sent to the core network and then looped back to the base station, thereby greatly reducing the overall delay of the positioning process.
  • the base station may also send the indication information of whether or not it supports LMC-based positioning to the terminal and to the core network, so as to avoid positioning failure due to the base station not supporting LMC-based positioning.
  • the core network may also send instruction information to the base station to indicate whether or not to allow the base station supporting LMC to perform LMC-based positioning for the terminal, so as to protect the privacy of the terminal.
  • the positioning method provided in the embodiments of this application can be applied to various communication systems, such as long term evolution (LTE) systems, 5th generation (5G) systems, such as NR, and next-generation communication systems. Such as 6G system and so on.
  • LTE long term evolution
  • 5G 5th generation
  • next-generation communication systems such as 6G system and so on.
  • the technical solutions of the embodiments of the present application can also be applied to other communication systems, as long as the communication system has a positioning requirement for the terminal.
  • FIG. 5A is a network architecture to which the embodiments of this application are applicable.
  • the communication system includes a core network, NG-RAN, and terminals.
  • the core network includes network elements/modules such as LMF, AMF, SLP, and E-SMLC.
  • NGRAN includes network elements/modules such as gNB and ng-eNB. Among them, LMF, AMF, SLP, E-SMLC, gNB, and ng-eNB networks
  • LMF, AMF, SLP, E-SMLC, gNB, and ng-eNB The specific functions of the element/module and the connection relationship between the various network elements/modules can be referred to the introduction of the relevant part of Figure 1 above, and will not be repeated here.
  • Fig. 5A The difference from Fig. 1 is that in the network architecture shown in Fig. 5A, an LMC is added to the NG-RAN, and the specific deployment method of the LMC is set in the base station, such as set in the gNB or set in the ng-ENB.
  • LMC is a function inside the base station, so there is no need to introduce a new interface.
  • the network architecture shown in Figure 5A is referred to as Alternative 1 in this document.
  • Fig. 5B is another network architecture applicable to the embodiment of this application.
  • the communication system also includes a core network, an NG-RAN, and a terminal.
  • the LMC in the network architecture shown in Figure 5B acts as an independent logical node in the NG-RAN and is connected to the base station through a new interface.
  • the LMC is connected to the gNB-CU through the interface Itf. Connected.
  • this article refers to the network architecture solution shown in FIG. 5B as Alternative2.
  • Fig. 5C is another network architecture applicable to the embodiment of this application.
  • the communication system also includes the core network, NG-RAN and terminal.
  • the LMC acts as an independent logical node in the NG-RAN, which is similar to Fig. 5B. The difference is that the LMC can connect to multiple base stations at the same time through the new interface as shown in Figure 5C.
  • Figure 5C takes the LMC being connected to two base stations at the same time as an example. In specific implementation, the LMC can also be connected to more base stations.
  • this article refers to the network architecture solution shown in FIG. 5B as Alternative3.
  • FIG. 5A, FIG. 5B, and FIG. 5C are only exemplary illustrations, and do not specifically limit the types, numbers, and connection modes of the network elements included in the communication system to which this application applies.
  • Fig. 6A and Fig. 6B show the protocol stack involved when the LMC interacts with the terminal.
  • the LMC and the terminal are connected through the interface NR-Uu, and the protocol stack on the terminal side includes from top to bottom: LPP, RRC, PDCP, RLC, MAC, L1; gNB/
  • the protocol stack on the LMC side includes from top to bottom: LPP, RRC, PDCP, RLC, MAC, L1.
  • the protocol stack on the terminal side includes from top to bottom: LPP, RRC, PDCP, RLC, MAC, L1; the gNB side faces the terminal
  • the protocol stack from top to bottom includes: RRC, PDCP, RLC, MAC, L1;
  • the protocol stack facing the LMC from the gNB side includes: XPAP, SCTP, IP, L2, L1;
  • the protocol stack on the LMC side is from top to bottom
  • the positioning interaction between the LMC and the terminal can use the LPP protocol or other protocols.
  • FIG. 7 Please refer to FIG. 7 for a positioning method provided by an embodiment of this application. The method may be applied to the communication system shown in FIG. 5A or FIG. 5B or FIG. 5C.
  • a terminal device sends a positioning request to an access network device, where the access network device can support LMC-based positioning.
  • the access network equipment is equipment in the NG RAN, such as gNB, ng-eNB, or LMC in Alternative 2 and Alternative 3, and there is no restriction here.
  • the access network device is the base station where the LMC is located. After the access network device receives the positioning request, it responds to the terminal Directly initiate positioning based on LMC.
  • the access network device is any base station connected to the LMC.
  • the access network device needs to forward the positioning request to the LMC through the first interface, and then the LMC locates the terminal in response to the positioning request.
  • the access network device In order for the access network device to forward the positioning request, before forwarding the positioning request to the LMC, it needs to establish a connection with the first interface of the LMC.
  • the specific process for the access network device to establish the first interface with the LMC includes: access network The device sends a first interface establishment request message to the LMC to request the establishment of the first interface between the access network device and the LMC; after receiving the first interface establishment request message, the LMC sends the first interface to the access network device Create a response message.
  • the first interface establishment response message may carry quality of service (QoS) information provided by the LMC, so that when the access network device establishes the first interface with the LMC, it also obtains the QoS information of the LMC. In this way, the access network device can no longer initiate an additional process of acquiring the QoS information of the LMC, which can further reduce the time delay.
  • QoS quality of service
  • the positioning request may be (or carried by) an LPP message or an RRC message.
  • the positioning request may be directly sent to the access network device without passing through the core network.
  • the LPP layer of the terminal If the location request is carried in an LPP message, the LPP layer of the terminal generates an LPP message and sends it to the access network device to request the location of the terminal.
  • the location request can be presented as an information element of LPP; if the location request is carried in an RRC message , The RRC layer of the terminal generates an RRC message to the access network device to request the location of the terminal.
  • the location request can be presented as an RRC information element.
  • the positioning request may also include positioning QoS information of the terminal, such as positioning accuracy requirements, response time requirements, and positioning QoS levels.
  • positioning QoS information of the terminal such as positioning accuracy requirements, response time requirements, and positioning QoS levels.
  • the access network equipment can provide better positioning services for the terminal based on the terminal's positioning QoS information.
  • the positioning request may also include positioning capability information of the terminal, for example, positioning methods supported by the terminal, and respective measurement capabilities of each positioning method.
  • positioning capability information of the terminal for example, positioning methods supported by the terminal, and respective measurement capabilities of each positioning method.
  • the access network device may first send first indication information to the terminal, which is used to indicate whether the access network device or the cell to which the terminal belongs supports LMC-based positioning, so that the terminal has only
  • first indication information is initiated to the access network device.
  • the terminal determines whether to initiate a positioning request or determines whether to initiate a positioning request based on the LMF based on the first indication information, which can prevent the terminal from initiating a corresponding positioning request but the access network device does not support the LMC causing positioning failure.
  • the base station may broadcast the first indication information in the system information of the cell, which is used to indicate whether the current cell/base station supports LMC-based positioning, or whether the current serving base station is connected to an LMC.
  • the first indication information can be 1 bit, for example, a value of 1 means support, and a value of 0 means not support; or when the information element of the first indication information is included in the system information, it means support, but not when it is not included in the system information. Indicates that it does not support.
  • the access network device can also send another indication information, which can be through the LPP protocol, the RRC protocol, or System information is used to indicate whether LMF-based positioning is supported; or the access network device combines the indication information indicating whether LMF-based positioning is supported and the indication information indicating whether LMC-based positioning is supported into one indication information (cell), such as one
  • LMC when the enumeration value is LMC, it means that only LMC is supported; when the enumeration value is LMF, it means that only LMF is supported; when the enumeration value is BOTH, it means that both LMC and LMF are supported.
  • the first indication information may also be the response information returned by the access network device in response to the terminal's inquiry request, that is, before the terminal initiates a positioning request, the terminal first sends an inquiry request to the access network device to inquire whether the access network device supports For the positioning of the LMC, the terminal initiates a positioning request when it receives the response information from the access network device that the access network device supports LMC. If the terminal does not receive the response information or the received response information indicates that the access network device does not support it LMC does not initiate a positioning request or does not initiate a positioning request based on LMC.
  • the access network device may also inform the core network of the indication information (third indication information) whether the access network device supports LMC or not, for use in MO-LR, MT-LR In the NI-LR or RI-LR scenario, the core network decides whether to initiate LMC-based positioning (or whether to initiate LMC-based positioning or LMF-based positioning).
  • the indication information third indication information
  • the core network decides whether to initiate LMC-based positioning (or whether to initiate LMC-based positioning or LMF-based positioning).
  • the third indication information may be explicit indication information or implicit, and there is no restriction here.
  • the third indication information carries LMC-related information, indicating support, and not carrying indicates not supporting, and there is no specific restriction here.
  • the third indication information may also include: the ID of the LMC, which is used to identify the LMC; the QoS information that the LMC can provide, such as the positioning method of the LMC, the time delay of the LMC, and the positioning accuracy of the LMC.
  • the third indication information can be carried in the access network device and the second interface establishment request message of the core network and sent to the core network, or sent to the core network in the RAN configuration update message, or a new message is introduced to send For the core network, there are no restrictions here.
  • the access network device may also receive fourth indication information sent by the core network whether to allow the access network device to use the LMC to locate the terminal, and the access network device Only when the fourth instruction information is received and it is determined that the fourth instruction information is used to instruct the core network to allow the access network device to use LMC to locate the terminal, the LMC-based positioning access network device is initiated for the terminal, which can protect the terminal's Privacy and security.
  • the fourth indication information may be carried in the terminal context establishment request message sent by the core network to the access network device.
  • the access network device may send the fourth indication information to the access network device after the terminal handover, so that the access network device after the handover can be timely Know whether the LMC can be used to locate the terminal, so as to better protect the privacy and security of the terminal.
  • the access network device receives the positioning request, responds to the positioning request, and locates the terminal based on the LMC.
  • the access network device initiates the LPP positioning process to obtain the location information of the terminal, which can be similar to the existing LMF-based positioning process.
  • the access network device obtains the location of the terminal through the LPP Capability Transfer (LPP Capability Transfer) process.
  • LPP Capability Transfer Ability to send assistance information to the terminal through the LPP Assistance Data Transfer process, order the terminal to perform positioning measurement through the LPP Location Information Transfer process, and receive the positioning measurement result from the terminal, and access the network
  • the device calculates the location information of the terminal based on the positioning measurement result, etc., which will not be repeated here.
  • the access network device sends a positioning result to the terminal.
  • the positioning result includes the second indication information of the location information of the terminal.
  • the positioning result can be carried in the LPP message or the RRC message. If the positioning request is carried in the LPP message, the positioning result is also carried in the LPP message; if the positioning request is carried in the RRC message, the positioning result is also carried in the RRC message.
  • the LMC As mentioned earlier, if the deployment plan of the LMC is Alternative1 shown in Figure 5A, that is, the LMC is a function inside the base station, and the access network equipment is the base station where the LMC is located, the LMC will directly locate the terminal after obtaining the positioning result. The positioning result is returned to the terminal. If the deployment plan of the LMC is Alternative 2 shown in Figure 5B or Alternative 3 shown in Figure 5C, that is, the LMC is connected to one or more base stations as a logical node, then the access network equipment is any base station connected to the LMC. In this case, after the LMC obtains the positioning result for the terminal positioning, it first forwards the positioning result to the access network device through the first interface, and then the access network device returns the positioning result to the terminal.
  • the terminal can know whether the positioning message is from the LMF (the NAS layer is submitted to the LPP layer) or the LMC (the RRC layer is submitted to the LPP layer) through the transmission path of the LPP message. ), or in the interactive LPP message, add an indication information to indicate whether the positioning server is LMC or LMF.
  • a possible example is to add an enumeration value lmc to the Initiator in the LPP-TransactionID cell of the LPP message.
  • lmc is the locationServer, it is indicated as LMF, and when the value is lmc, it is indicated as LMC.
  • the terminal requests the LMC-based MO-LR positioning through the LPP message or the RRC message, which can effectively reduce the positioning delay.
  • the access network device sends the indication information whether to support LMC-based positioning to the terminal and the core network, which can avoid positioning failures that occur because the access network device does not support LMC-based positioning.
  • the core network also sends instruction information to the base station to indicate whether to allow the LMC-based positioning of the access network device/LMC for the terminal, which can protect the privacy of the terminal.
  • the method includes:
  • the base station sends indication information to the terminal, for example, broadcasts the indication information in the system information of the cell, which is used to indicate whether the current cell/base station supports LMC-based positioning, or whether the current serving base station is connected to an LMC.
  • the indication information can be 1 bit, for example, a value of 1 means support, a value of 0 means not support; or when the information element of the indication information is included in the system information, it means support, not included (default) In the system information, it means it is not supported.
  • the terminal can determine whether to initiate LMC-based positioning and whether to initiate LMF-based positioning based on this information, so as to avoid a situation where the corresponding positioning is initiated but the network does not support it.
  • the operator will no longer deploy LMF after deploying LMC, or deploy both. Therefore, optionally, broadcast another indication information in the system information of the cell to indicate whether LMF-based positioning is supported; or Combined with the previous indication (whether LMC is supported) into one indication (cell), such as an enumerated parameter, when the enumerated value is LMC, it means that only LMC is supported, and when the enumerated value is LMF , Which means that only LMF is supported.
  • the enumeration value is BOTH, it means that both LMC and LMF are supported.
  • the terminal learns whether it can initiate the MO-LR positioning based on the LMC by receiving the system information of the cell. Optionally, it can also be known whether LMF-based MO-LR positioning can be initiated. When the terminal needs to initiate MO-LR positioning, the terminal selects positioning based on LMC or LMF according to requirements such as positioning time delay and the support of LMC or LMF. If LMC-based positioning is selected, it is determined to initiate the LMC-based positioning process.
  • the terminal sends a positioning request to the base station through an LPP message or an RRC message to request to obtain the position of the terminal.
  • Method 1 The LPP layer of the terminal generates an LPP message Location Request and sends it to the base station.
  • the Location Request message may also carry terminal positioning QoS information, such as positioning accuracy requirements, response time requirements, positioning QoS levels, etc., which can avoid the process of obtaining the QoS information of the terminal positioning by the LMC, thereby further reducing time delay.
  • terminal positioning QoS information such as positioning accuracy requirements, response time requirements, positioning QoS levels, etc.
  • the LMC needs to know the positioning capability of the terminal to determine the positioning method to be adopted. Therefore, the terminal can also carry positioning capability information in the Location Request message to avoid the process of acquiring terminal capabilities between the LMC and the terminal. So as to further reduce the time delay.
  • the LPP message here is a newly introduced message, so the message name Location Request is only an example of the message name of the LPP message, and is not a limitation.
  • the Location Request can be a newly introduced LPP message, or it can be based on an existing LPP message, such as a ProvideCapabilities message. Add an indication to the message, or set endTransaction to false to indicate that the terminal needs to obtain the location. Information, or the first message received by the default LMC is ProvideCapabilities, which means that the location needs to be obtained, and there is no restriction here.
  • Method 2 The RRC layer of the terminal generates an RRC message Location Request and sends it to the base.
  • the Location Request message in Method 2 can also carry QoS information for terminal positioning, such as positioning accuracy requirements, response time requirements, and positioning QoS levels. All of these information can be presented as RRC information elements. In this way, the process of obtaining the QoS information of the terminal positioning by the LMC can be avoided, thereby further reducing the time delay.
  • the LMC needs to know the positioning capabilities of the terminal to determine the positioning method to be used. Therefore, the terminal can also carry an LPP PDU in the Location Request message.
  • This LPP PDU is a ProvideCapabilities message that carries the positioning capability of the terminal to avoid LMC The process of acquiring terminal capabilities with the terminal, thereby further reducing time delay.
  • the RRC message in method 2 is a newly introduced message, so the message name Location Request is only an example of the message name of the RRC message, and is not a limitation.
  • the base station initiates an LPP positioning process to obtain the position of the terminal, which may be similar to the existing LMF-based positioning process, and will not be repeated here.
  • the terminal can know whether the positioning message is from the LMF (the NAS layer is submitted to the LPP layer) or the LMC (the RRC layer is submitted to the LPP layer) through the transmission path of the LPP message. ), or in the interactive LPP message, add an indication information to indicate whether the positioning server is LMC or LMF.
  • One method is to add an enumeration value lmc to the Initiator in the LPP-TransactionID cell of the LPP message , When the value is locationServer, it means LMF, when the value is lmc, it means LMC.
  • the RRC layer of the base station informs the LPP layer of the base station that the terminal needs to be positioned (and can also submit related positioning QoS information).
  • the base station After obtaining the location of the terminal, the base station returns a positioning result to the terminal through a downlink RRC message or an LPP message.
  • the base station after obtaining the location of the terminal, the base station generates an LPP message Location Response message to send to the terminal, and this message carries the location of the terminal obtained in step 4.
  • the message name Location Response is only an example of the LPP message name, and it is not a limitation.
  • the Location Response may be a newly introduced LPP message, or it may be based on an existing LPP message, such as a Provide Location Information (Provide Location Information) message, using Provide Location Information as a response message to send the location result to the terminal.
  • Provide Location Information Provide Location Information
  • ProvideLocationInformation is a message sent by the terminal to the LMF for the terminal to send the positioning measurement result to the LMF, and the ProvideLocationInformation as the Location Response message here has a different sending direction, which is sent from the LMC to the terminal.
  • the base station after the base station obtains the location of the terminal, the base station generates an RRC message Location Response message to send to the terminal, and the message carries the location of the terminal obtained in step S1304.
  • the RRC message here is a newly introduced message, so the message name Location Response is only an example of the message name of the RRC message, and it is not a limitation.
  • the method includes:
  • the base station/CU sends an interface establishment request message to the LMC to request the establishment of an interface between the two.
  • the base station can actively initiate an interface establishment process to the LMC, which can avoid the appearance of the pseudo LMC and improve the security performance.
  • the interface establishment request message may carry indication information indicating whether the base station/cell under the base station supports positioning reference signals.
  • the LMC sends an interface establishment response message to the base station/CU.
  • the interface establishment response message may carry QoS information that the LMC can provide, such as information such as delay, accuracy, and supported positioning methods.
  • the base station sends indication information to the terminal, for example, broadcasts the indication information in the system information of the cell, which is used to indicate whether the current cell/base station supports LMC-based positioning, or whether the current serving base station is connected to an LMC.
  • step S801 in FIG. 8 The specific implementation method is the same as step S801 in FIG. 8, and will not be repeated here.
  • S904 The terminal initiates a positioning process based on the LMC.
  • step S802 in FIG. 8 The specific implementation method is the same as step S802 in FIG. 8, and will not be repeated here.
  • S905 The LPP layer of the terminal generates an LPP message Location Request and sends it to the LMC to request the location of the terminal.
  • the Location Request message can carry terminal positioning QoS information, such as positioning accuracy requirements, response time requirements, positioning QoS levels, etc. This can avoid the process of LMC obtaining QoS information for terminal positioning, thereby further reducing delay.
  • the LMC needs to know the positioning capability of the terminal to determine the positioning method to be adopted, so the terminal can also carry the terminal positioning capability information in the Location Request message, which can avoid the process of acquiring the terminal capability between the LMC and the terminal. So as to further reduce the time delay.
  • the Location Request here can be a newly introduced LPP message. Alternatively, it can also be based on an existing LPP message, such as the ProvideCapabilities message, adding an indication information to the message, or setting endTransaction to false for Indicate that the terminal needs to obtain location information, or by default, the first message received by the LMC is ProvideCapabilities, indicating that the location needs to be obtained.
  • the ProvideCapabilities message adding an indication information to the message, or setting endTransaction to false for Indicate that the terminal needs to obtain location information, or by default, the first message received by the LMC is ProvideCapabilities, indicating that the location needs to be obtained.
  • the LMC initiates the LPP positioning process to obtain the position of the terminal, which may be similar to the existing LMF-based positioning process, and will not be repeated here.
  • the LMC After the LMC obtains the location of the terminal, the LMC generates an LPP message Location Response message and sends it to the terminal, and the message carries the location of the terminal obtained in step S906.
  • FIG. 9 shows a positioning method in which the terminal initiates a positioning request based on the LPP message, and the base station/LMC returns the positioning result based on the LPP message.
  • the terminal can also initiate a positioning request based on the RRC message, and the base station/LMC returns a positioning result based on the RRC message.
  • the method includes:
  • the base station/CU sends an interface establishment request message to the LMC to request the establishment of an interface between the two.
  • the LMC sends an interface establishment response message to the base station/CU.
  • the base station sends indication information to the terminal, for example, broadcasts the indication information in the system information of the cell, which is used to indicate whether the current cell/base station supports LMC-based positioning, or whether the current serving base station is connected to an LMC.
  • the terminal initiates a positioning process based on the LMC.
  • the RRC layer of the terminal generates an RRC message Location Request and sends it to the base station/CU to request the location of the terminal.
  • the Location Request message may carry terminal positioning QoS information, such as positioning accuracy requirements, response time requirements, positioning QoS levels, etc., to avoid the process of obtaining the QoS information of the terminal positioning by the LMC, thereby further reducing time delay.
  • the LMC also needs to know the positioning capability of the terminal to determine the positioning method to be adopted. Therefore, the terminal can also carry an LPP PDU in the Location Request message.
  • This LPP PDU is a ProvideCapabilities message that carries the positioning capability of the terminal. In order to avoid the process of acquiring terminal capabilities between the LMC and the terminal, thereby further reducing the time delay.
  • the RRC message here is a newly introduced message, so the message name Location Request is only an example of the message name of the RRC message, and is not a limitation.
  • the base station/CU sends an interface message Location Request between the two to the LMC to request the location of the terminal.
  • the message may carry terminal positioning QoS information and/or terminal positioning capability information.
  • the LMC initiates the LPP positioning process to obtain the position of the terminal, which may be similar to the existing LMF-based positioning process, which will not be repeated here.
  • the LMC After obtaining the location of the terminal, the LMC generates an interface message Location Response message between the LMC and the base station/CU, and sends it to the base station/CU. The message carries the location of the terminal obtained in step S1007.
  • the base station/CU generates an RRC message Location Response message, and sends it to the terminal, which carries the location of the terminal.
  • the third embodiment focuses on the privacy and security of the terminal, and mainly describes whether the core network can (for example, based on the terminal's subscription and other information) control whether the base station/LMC is allowed to locate the terminal (based on the LMC), for example, the base station is not allowed to be sensitive to the terminal.
  • Terminal to locate The core network sends indication information (used to indicate whether or not to allow the base station/LMC to locate the terminal based on LMC) to the base station, and the base station determines whether to accept the LMC-based positioning initiated by the terminal or determines the base station based on the indication information Can I initiate LMC-based positioning for the terminal?
  • indication information used to indicate whether or not to allow the base station/LMC to locate the terminal based on LMC
  • the core network can decide whether to perform positioning based on LMC or LMF, but the core network needs to know whether the current serving base station of the terminal supports LMC.
  • LMC the base station actively informs the connected core network of its own LMC support information, so that the core network can decide whether to allow the base station/LMC to locate the terminal based on LMC.
  • This information may include one or more of the following: 1) Whether the base station supports LMC (or whether it supports LMC-based positioning), it can be explicit indication information or implicit, such as carrying LMC-related information , Indicates support, and does not carry indicates not support; 2) The QoS that the LMC can provide, including information such as delay, accuracy, and supported positioning methods; 3) LMC ID, used to identify the LMC.
  • the base station may send information about whether to support LMC to the core network in the process of establishing the NG interface.
  • the information about whether to support LMC may also be sent to the core network during the RAN configuration update process.
  • a new message may also be newly introduced to send.
  • the embodiment of the present application does not specifically limit the manner in which the base station informs the core network.
  • the core network (specifically, the AMF in the core network) may carry indication information in the context establishment request message, which is used to indicate whether the base station is allowed to perform LMC-based positioning for the terminal.
  • the terminal initiates initial access and establishes an air interface RRC connection.
  • the base station sends an initial UE message ((Initial UE Message) to the AMF.
  • the AMF sends a UE Context Setup Request message (UE Context Setup Request) to the terminal, requesting the base station to establish the context of the terminal.
  • the message carries indication information for indicating whether to allow the base station/LMC to locate the terminal based on the LMC.
  • the indication information can be subdivided into whether to allow LMC-based MO-LR positioning (that is, UE as client positioning), whether to allow LMC-based RI-LR positioning (that is, RAN as client positioning), and so on.
  • the base station saves the indication information, and in a subsequent process, determines whether it can support LMC-based positioning for the UE based on the indication information.
  • the base station will not deliver the LPP message to the LPP layer or not send it to the LPP after receiving the LPP message sent by the UE.
  • LMC the air interface may send a message to indicate that the LPP message has failed, carrying a cause value, for example, the cause value is not allowing positioning.
  • the base station For RI-LR positioning, if the indication information indicates that it is not allowed, the base station cannot initiate positioning for the UE.
  • the base station may directly execute the relevant positioning process, and is not limited by the above indication information.
  • the base station sends a UE context setup response message (UE Context Setup Response) to the core network.
  • UE Context Setup Response UE Context Setup Response
  • the above-mentioned indication information may be transmitted by the source base station to the target base station, and the target base station will continue to use the indication information to perform the above-mentioned step S1604 processing subsequently.
  • the flow chart is as follows:
  • the source base station decides to switch the base station of the terminal to the target base station.
  • the source base station sends a handover request (Handover Request) message to the target base station, where the handover request message carries indication information whether the base station/LMC is allowed to perform LMC-based positioning for the terminal;
  • Handover Request handover request
  • the target base station saves the indication information.
  • the target base station sends a handover request acknowledgment (Handover Request ACK) message to the source base station.
  • Handover Request ACK handover request acknowledgment
  • the core network sends indication information to the base station to indicate whether to allow the base station/LMC to position the terminal based on the LMC, thereby protecting the privacy of the terminal.
  • the method provided in the embodiments of the present application is introduced from the perspective of interaction between the terminal, the access network device, the core network, and the LMC.
  • the terminal, access network device, core network, and LMC may include a hardware structure and/or software module, and a hardware structure, a software module, or a hardware structure plus a software module may be used.
  • a hardware structure, a software module, or a hardware structure plus a software module may be used.
  • the apparatus 1400 may be an access network device or a device in an access network device.
  • the apparatus 1400 includes a unit/module for executing the method executed by the access network device in the foregoing method embodiment, for example, including:
  • the receiving unit 1401 is configured to receive a positioning request from a terminal, where the access network device supports positioning based on the positioning management component LMC;
  • the processing unit 1402 is configured to respond to the positioning request and locate the terminal based on the LMC;
  • the sending unit 1403 is configured to send the positioning result to the terminal.
  • the sending unit 1403 is further configured to:
  • the receiving unit 1401 Before the receiving unit 1401 receives the positioning request from the terminal, it sends first indication information to the terminal, where the first indication information is used to indicate that the access network device supports LMC-based positioning.
  • the first indication information includes:
  • the system information broadcast by the access network device or,
  • the response information returned by the access network device in response to the inquiry request of the terminal where the inquiry request is used to inquire whether the access network device supports positioning based on the LMC.
  • the positioning request includes positioning service quality QoS information of the terminal, and/or positioning capability information of the terminal;
  • the QoS information includes: at least one of time delay, accuracy, QoS level, or positioning method;
  • the positioning capability information includes: positioning methods supported by the terminal, and measurement capabilities corresponding to the positioning methods supported by the terminal.
  • the positioning result includes second indication information of the location information of the terminal.
  • the positioning request is carried in an LTE positioning protocol LPP message or RRC message.
  • the access network device is connected to the LMC through a first interface
  • the sending unit 1403 is further configured to: after the receiving unit 1401 receives the positioning request from the terminal, forward the positioning request to the LMC through the first interface;
  • the receiving unit 1401 is further configured to: before the sending unit 1403 sends the positioning result to the terminal, receive the positioning result from the LMC through the first interface.
  • the sending unit 1403 is further configured to: before the receiving unit 1401 receives the positioning request from the terminal, send a first interface establishment request message to the LMC for requesting to establish the connection.
  • the receiving unit 1401 is further configured to receive a first interface establishment response message returned by the LMC, wherein the first interface establishment response message carries the QoS information provided by the LMC.
  • the method before the access network device receives the positioning request from the terminal, the method further includes:
  • the access network device sends third indication information that the access network device supports LMC-based positioning to the core network.
  • the third indication information is carried in an interface establishment request message sent by the sending unit 1403 to the core network.
  • the third indication information includes one or more of the following information:
  • the identity identification ID of the LMC is the identity identification ID of the LMC
  • the receiving unit 1401 is further configured to: before receiving a positioning request from the terminal, receive a core network sent by the core network whether or not the core network allows the access network device to use the LMC to Fourth indication information for terminal positioning;
  • the processing unit 1402 is further configured to: before locating the terminal based on the LMC, determine that the fourth indication information is used to instruct the core network to allow the access network device to use the LMC to locate the terminal.
  • the fourth indication information is carried in a terminal context establishment request message sent by the core network to the access network device.
  • the sending unit 1403 is further configured to send the fourth instruction information to the access network device after the terminal handover when the terminal performs the handover of the access network device.
  • the apparatus 1500 may be a terminal or a device in the terminal.
  • the apparatus 1500 includes a unit/module for executing the method executed by the terminal in the foregoing method embodiment, for example, including:
  • the sending unit 1501 is configured to send a positioning request to an access network device, where the access network device supports positioning based on the positioning management component LMC;
  • the receiving unit 1502 is configured to receive the positioning result sent by the access network device.
  • the receiving unit 1502 is further configured to: before the sending unit 1501 sends a positioning request to the access network device, receive the first indication information sent by the access network device, where the The first indication information is used to indicate that the access network device supports LMC-based positioning.
  • the first indication information may include: system information broadcast by the access network device; or, response information returned by the access network device in response to the terminal's inquiry request,
  • the query request is used to query whether the access network device supports positioning based on the LMC.
  • the positioning request may include positioning service quality QoS information of the terminal, and/or positioning capability information of the terminal; wherein the QoS information includes: delay, accuracy, At least one of a QoS level or a positioning method; the positioning capability information includes: a positioning method supported by the terminal, and a measurement capability corresponding to the positioning method supported by the terminal.
  • the positioning result includes second indication information of the location information of the terminal.
  • the positioning request is carried in an LTE positioning protocol LPP message or RRC message.
  • FIG. 16 there is shown a schematic structural diagram of an apparatus 1600 provided by an embodiment of the present application.
  • the apparatus 1600 may be an LMC or a device in the LMC.
  • the apparatus 1600 includes a unit/module for executing the method executed by the LMC in the foregoing method embodiment, for example, including:
  • the receiving unit 1601 is configured to receive a positioning request sent by an access network device
  • the processing unit 1602 is configured to respond to the positioning request and locate the terminal based on the LMC;
  • the sending unit 1603 is configured to send the positioning result to the access network device, so that the access network device forwards the positioning result to the terminal.
  • the access network device is connected to the LMC through a first interface
  • the receiving unit 1601 is specifically configured to: receive a positioning request sent by the access network device through the first interface;
  • the sending unit 1603 is specifically configured to send the positioning result to the access network device through the first interface.
  • the receiving unit 1601 is further configured to: before receiving the positioning request sent by the access network device, receive the first interface establishment request message sent by the access network device, wherein the first interface establishment request message is sent by the access network device.
  • An interface establishment request message is used to request the establishment of a first interface between the access network device and the LMC;
  • the sending unit 1603 is further configured to send a first interface establishment response message to the access network device, wherein the first interface establishment response message carries the QoS information provided by the LMC.
  • FIG. 17 there is shown a schematic structural diagram of an apparatus 1700 provided by an embodiment of the present application.
  • the apparatus 1700 may be a core network or a device in the core network.
  • the apparatus 1700 includes units/modules for executing the methods executed by the core network in the foregoing method embodiments, for example, including:
  • the receiving unit 1701 is configured to receive an initial UE message sent by an access network device, where the access network device supports positioning based on the positioning management component LMC;
  • the sending unit 1702 is configured to send fourth indication information to the access network device, where the fourth indication information is used to indicate whether to allow the access network device or the LMC to locate the terminal device based on the LMC .
  • the receiving unit 1701 is further configured to: before receiving the initial UE message sent by the access network device, receive the access network device from the access network device that supports the LMC-based The third indication information for positioning.
  • the third indication information may also be carried in an interface establishment request message sent by the access network device to the core network.
  • the third indication information may include one or more of the following information: the identification ID of the LMC; the positioning method of the LMC; the time delay of the LMC; Describe the positioning accuracy of the LMC.
  • the fourth indication information may be carried in a terminal device context establishment request message sent by the core network to the access network device.
  • the content of the fourth indication information may include one or more of the following items: yes/no to allow LMC-based MO-LR positioning; yes/no to allow LMC-based RI -LR positioning; Yes/No allows LMC-based MT-LR positioning; Yes/No allows LMC-based NI-LR positioning.
  • FIG. 18 shows a schematic structural diagram of a communication device 1800 provided by an embodiment of the present application, including:
  • At least one processor 1801 and a memory 1802 that is communicatively connected with the at least one processor 1801; a communication interface 1803;
  • the memory 1802 stores instructions that can be executed by the at least one processor 1801, and the at least one processor 1801 executes the instructions stored in the memory 1802 to execute the terminal and the access network device in the foregoing method embodiment.
  • connection medium between the communication interface 1803, the processor 1801, and the memory 1802 is not limited in the embodiment of the present application.
  • the communication interface 1803, the processor 1801, and the memory 1802 are connected by a bus 1804.
  • the bus is represented by a thick line in FIG. 18.
  • the connection mode between other components is only for schematic illustration. , Is not limited.
  • the bus can be divided into an address bus, a data bus, a control bus, and so on. For ease of presentation, only a thick line is used in Figure 18 to represent it, but it does not mean that there is only one bus or one type of bus.
  • the processor 1801 may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and may implement or execute the The disclosed methods, steps and logic block diagrams.
  • the general-purpose processor may be a microprocessor or any conventional processor or the like. The steps of the method disclosed in combination with the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the memory 1802 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., and may also be a volatile memory (volatile memory), such as random access memory (random access memory). -access memory, RAM).
  • the memory is any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this.
  • the memory in the embodiments of the present application may also be a circuit or any other device capable of realizing a storage function for storing program instructions and/or data.
  • the communication interface 1803 is used for communication between the device 1800 and other modules, and it can be a circuit, a device, an interface, a bus, a software module, a transceiver, or any other device that can realize communication.
  • embodiments of the present application provide a computer-readable storage medium, including a program or instruction.
  • the program or instruction runs on a computer
  • the terminal, access network device, and core network in the foregoing method embodiment are executed. Or the method performed by the LMC.
  • an embodiment of the present application provides a chip, which is coupled with a memory, and is used to read and execute program instructions stored in the memory to implement the terminal, access network device, and core in the foregoing method embodiment.
  • the method performed by the net or LMC.
  • embodiments of the present application also provide a wireless communication system, which includes the terminal, access network equipment, LMC, and core network involved in the embodiments of the present application.
  • this application can be provided as methods, systems, or computer program products. Therefore, this application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种定位方法及对应装置，方法包括：接入网设备从终端接收定位请求，其中所述接入网设备支持基于定位管理组件LMC的定位；所述接入网设备响应所述定位请求，并基于所述LMC对所述终端定位；所述接入网设备向所述终端发送定位结果。本申请明确了接入网设备基于LMC对终端定位时，终端向接入网设备发起定位请求以及接入网设备返回定位结果给终端的具体过程，该过程可以避免定位请求以及定位结果先发送到核心网再绕回到接入网设备，能够保证较低的定位时延。

Description

一种定位方法及对应装置 技术领域
本申请涉及无线通信技术领域，尤其涉及一种定位方法及对应装置。
背景技术
在传统的定位架构中，如长期演进(long term evolution，LTE)、新空口(New Radio，NR)版本(release，Rel)R-16的定位架构，定位管理功能(location management function，LMF)连接在核心网的接入和移动性管理功能(access and mobility management function，AMF)侧，因此在对终端执行定位的过程中，LMF与终端之间的消息交互必须要经过AMF和基站，导致时延较大。
为了减少时延，第三代合作伙伴计划(3rd generation partnership project，3GPP)批准了一个研究项目，研究将定位功能(LMF的功能)放到接入网侧，称之为定位管理组件(location management component，LMC)。但是，目前3GPP对于目标客户如何向LMC发起定位请求，以及LMC如何返回位置信息给目标客户，还没有具体方案。
发明内容
本申请提供一种定位方法及对应装置，用于明确接入网设备基于LMC对终端定位时，终端向接入网设备发起定位请求以及接入网设备返回定位结果给终端的具体过程，并且可以保证具有较低的定位时延，提高用户体验。
第一方面，本申请实施例提供一种定位方法，包括：接入网设备从终端接收定位请求，其中所述接入网设备支持基于定位管理组件LMC的定位；所述接入网设备响应所述定位请求，并基于所述LMC对所述终端定位；所述接入网设备向所述终端发送定位结果。
本申请实施例中，终端直接向支持LMC的接入网设备发起定位请求，接入网设备基于LMC对终端定位后，直接将定位结果返回给终端。本申请实施例明确了终端向接入网设备发起定位请求以及接入网设备返回定位结果给终端的具体过程，同时可以避免定位请求以及定位结果先发送到核心网再返回到接入网设备，能够保证较低的定位时延。
在一种可能的实施方式中，在接入网设备从终端接收定位请求之前，所述接入网设备还可以向所述终端发送第一指示信息，其中所述第一指示信息用于指示所述接入网设备支持基于LMC的定位。
通过本实施方式，接入网设备通过向终端指示自身支持LMC的定位的第一指示信息，可以使得终端基于第一指示信息来确定是否发起定位请求或者确定是否发起基于LMF的定位请求，进而能够避免终端发起对应的定位请求但是接入网设备不支持LMC导致定位失败的情况发生。
在一种可能的实施方式中，所述第一指示信息可以包括：所述接入网设备广播的系统信息；或者，所述接入网设备响应所述终端的询问请求所返回的应答信息，其中所述询问请求用于询问所述接入网设备是否支持基于所述LMC的定位。
通过本实施方式，接入网设备可以通过广播或者响应所述终端的询问请求的方式将自身支持LMC的定位的指示信息发送给终端，提高了方案的可靠性和灵活性。
在一种可能的实施方式中，所述定位请求中还可以包含所述终端的定位服务质量QoS信息，和/或所述终端的定位能力信息；其中，所述QoS信息包括：时延、精度、QoS等级或定位方法中的至少一项；所述定位能力信息包括：所述终端支持的定位方法，所述终端支持的定位方法对应的测量能力。
通过本实施方式，接入网设备可以不用额外发起获取终端的定位QoS信息和/或定位能力信息的过程，可以节省系统开销，进一步降低时延。
在一种可能的实施方式中，所述定位结果中可以包含所述终端的位置信息的第二指示信息。
通过本实施方式，可以保证终端从接入网设备接收到自身的位置信息，保证方案可靠性。
在一种可能的实施方式中，所述定位请求携带于LTE定位协议LPP消息或者RRC消息中。
通过本实施方式，将定位请求携带于LPP消息或者RRC消息，可以减少系统开销。
在一种可能的实施方式中，所述接入网设备与所述LMC通过第一接口连接。在接入网设备从终端接收定位请求之后，所述接入网设备还可以通过所述第一接口将所述定位请求转发给所述LMC。在所述接入网设备向所述终端发送定位结果之前，所述接入网设备还可以通过所述第一接口从所述LMC接收所述定位结果。
通过本实施方式，LMC作为独立的组件并与接入网设备相连接，LMC可以通过第一接口与接入网设备交互，保证接入网设备能够高效地基于LMC对终端定位，降低定位时延。
在一种可能的实施方式中，在接入网设备从终端接收定位请求之前，所述接入网设备还可以向所述LMC发送第一接口建立请求消息，用于请求建立所述接入网设备和所述LMC之间的第一接口；所述接入网设备接收所述LMC返回的第一接口建立响应消息，其中所述第一接口建立响应消息中携带所述LMC提供的QoS信息。
通过本实施方式，可以实现LMC与接入网设备建立第一接口，进而使得接入网设备能够与LMC交互，保证接入网设备能够基于LMC对终端定位。同时，通过在第一接口建立响应消息中携带LMC提供的QoS信息，可以避免接入网设备额外发起获取LMC提供的QoS信息的流程，进一步节省系统开销，降低定位时延。
在一种可能的实施方式中，在接入网设备从终端接收定位请求之前，所述接入网设备还可以向核心网发送所述接入网设备支持基于LMC的定位的第三指示信息。
通过本实施方式，接入网设备可以将自身支持LMC的第三指示信息主动告知给连接的核心网，以用于核心网能决定是否允许接入网设备/LMC针对该终端的基于LMC的定位。
在一种可能的实施方式中，所述第三指示信息可以携带于所述接入网设备发送给所述核心网的接口建立请求消息中。
通过本实施方式，核心网可以不再额外发起获取接入网设备是否支持基于LMC的定位的流程，可以进一步节省系统开销，降低定位时延。
在一种可能的实施方式中，所述第三指示信息可以包括以下信息中的一项或多项：所述LMC的身份标识ID；所述LMC的定位方法；所述LMC的时延；所述LMC的定位精度。
通过本实施方式，核心网设备能够获知更详细的接入网设备支持LMC定位的信息， 可以进一步节省系统开销，提高核心网的管理能力。
在一种可能的实施方式中，在接入网设备从终端接收定位请求之前，所述接入网设备还可以接收核心网发送的所述核心网是/否允许所述接入网设备使用LMC对所述终端定位的第四指示信息；在所述接入网设备基于所述LMC对所述终端定位之前，所述接入网设备还可以确定所述第四指示信息用于指示所述核心网允许所述接入网设备使用LMC对所述终端定位。
通过本实施方式，接入网设备只有接收到核心网允许该接入网设备使用LMC对终端定位的指示信息时，才可以对终端发起基于LMC的定位，这样可以有效保护终端的隐私安全。
在一种可能的实施方式中，所述第四指示信息携带于所述核心网发送给所述接入网设备的终端上下文建立请求消息中。
通过本实施方式，接入网设备可以不用额外发起获取第四指示信息的流程，进一步节省系统开销，降低定位时延。
在一种可能的实施方式中，当所述终端执行接入网设备切换时，所述接入网设备还可以将所述第四指示信息发送给所述终端切换后的接入网设备。
通过本实施方式，切换后的接入网设备能够及时获知核心网是/否允许接入网设备使用LMC对所述终端定位，进一步保障终端的隐私安全。
第二方面，本申请实施例提供一种定位方法，包括：终端向接入网设备发送定位请求，其中所述接入网设备支持基于定位管理组件LMC的定位；所述终端接收所述接入网设备发送的定位结果。
在一种可能的实施方式中，在终端向接入网设备发送定位请求之前，所述终端还可以接收所述接入网设备发送的第一指示信息，其中所述第一指示信息用于指示所述接入网设备支持基于LMC的定位。
在一种可能的实施方式中，所述第一指示信息可以包括：所述接入网设备广播的系统信息；或者，所述接入网设备响应所述终端的询问请求所返回的应答信息，其中所述询问请求用于询问所述接入网设备是否支持基于所述LMC的定位。
在一种可能的实施方式中，所述定位请求中可以包含所述终端的定位服务质量QoS信息，和/或所述终端的定位能力信息；其中，所述QoS信息可以包括：时延、精度、QoS等级或定位方法中的至少一项；所述定位能力信息可以包括：所述终端支持的定位方法，所述终端支持的定位方法对应的测量能力。
在一种可能的实施方式中，所述定位结果中可以包含所述终端的位置信息的第二指示信息。
在一种可能的实施方式中，所述定位请求可以携带于LTE定位协议LPP消息或者RRC消息中。
第三方面，本申请实施例提供一种定位方法，包括：定位管理组件LMC接收接入网设备发送的定位请求；所述LMC响应所述定位请求，并基于所述LMC对所述终端定位；所述LMC将定位结果发送给所述接入网设备，以使所述接入网设备将所述定位结果转发给终端。
在一种可能的实施方式中，所述接入网设备与所述LMC通过第一接口连接；LMC接收接入网设备发送的定位请求，包括：LMC接收接入网设备通过所述第一接口发送的定位 请求；所述LMC将定位结果发送给所述接入网设备，包括：所述LMC将定位结果通过所述第一接口发送给所述接入网设备。
在一种可能的实施方式中，在LMC接收接入网设备发送的定位请求之前，所述LMC还可以接收所述接入网设备发送的第一接口建立请求消息，其中所述第一接口建立请求消息用于请求建立所述接入网设备和所述LMC之间的第一接口；所LMC向所述接入网设备发送第一接口建立响应消息，其中所述第一接口建立响应消息中携带所述LMC提供的QoS信息。
第四方面，本申请实施例提供一种定位方法，包括：核心网设备接收接入网设备发送的初始UE消息，其中所述接入网设备支持基于定位管理组件LMC的定位；核心网设备向所述接入网设备发送第四指示信息，所述第四指示信息用于指示是否允许所述接入网设备或所述LMC针对所述终端设备基于LMC定位。
在一种可能的实施方式中，在核心网设备接收接入网设备发送的初始UE消息之前，所述核心网还可以接收所述接入网设备发送的所述接入网设备支持基于LMC的定位的第三指示信息。
在一种可能的实施方式中，所述第三指示信息还可以携带于所述接入网设备发送给所述核心网的接口建立请求消息中。
在一种可能的实施方式中，所述第三指示信息可以包括以下信息中的一项或多项：所述LMC的身份标识ID；所述LMC的定位方法；所述LMC的时延；所述LMC的定位精度。
在一种可能的实施方式中，所述第四指示信息可以携带于所述核心网发送给所述接入网设备的终端设备上下文建立请求消息中。
在一种可能的实施方式中，所述第四指示信息的内容可以包括以下几项中的一项或多项：是/否允许基于LMC的MO-LR定位；是/否允许基于LMC的RI-LR定位；是/否允许基于LMC的MT-LR定位；是/否允许基于LMC的NI-LR定位。
第五方面，本申请实施例提供一种接入网设备，包括用于执行本申请实施例第一方面所述的方法的单元/模块。例如：
接收单元，用于从终端接收定位请求，其中所述接入网设备支持基于定位管理组件LMC的定位；
处理单元，用于响应所述定位请求，并基于所述LMC对所述终端定位；
发送单元，用于向所述终端发送定位结果。
第六方面，本申请实施例提供一种终端，包括用于执行本申请实施例第二方面所述的方法的单元/模块。例如：
发送单元，用于向接入网设备发送定位请求，其中所述接入网设备支持基于定位管理组件LMC的定位；
接收单元，用于接收所述接入网设备发送的定位结果。
第七方面，本申请实施例提供一种定位管理组件LMC，包括用于执行本申请实施例第三方面所述的方法的单元/模块。例如：
接收单元，用于接收接入网设备发送的定位请求；
处理单元，用于响应所述定位请求，并基于所述LMC对所述终端定位；
发送单元，用于将定位结果发送给所述接入网设备，以使所述接入网设备将所述定位 结果转发给终端。
第八方面，本申请实施例还提供一种核心网设备，包括用于执行本申请实施例第四方面所述的方法的单元/模块。示例性的：
接收单元，用于接收接入网设备发送的初始UE消息，其中所述接入网设备支持基于定位管理组件LMC的定位；
发送单元，用于向所述接入网设备发送第四指示信息，所述第四指示信息用于指示是/否允许所述接入网设备或所述LMC针对所述终端设备基于LMC定位。
第九方面，本申请实施例提供一种通信装置，包括：
至少一个处理器；以及与所述至少一个处理器通信连接的存储器、通信接口；
其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述至少一个处理器通过执行所述存储器存储的指令，执行如本申请实施例第一方面、第二方面、第三方面或第四方面中任意一种可能的实施方式所述的方法。
第十方面，本申请实施例提供一种计算机可读存储介质，包括程序或指令，当所述程序或指令在计算机上运行时，执行如本申请实施例第一方面、第二方面、第三方面或第四方面中任意一种可能的实施方式所述的方法。
第十一方面，本申请实施例提供一种芯片，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，实现如本申请实施例第一方面、第二方面、第三方面或第四方面中任意一种可能的实施方式所述的方法。
附图说明
图1为LTE和NR Rel-16中的定位架构的示意图；
图2为LMF与终端交互所涉及的协议栈的示意图；
图3为基于图1所示定位架构的定位方法的流程图；
图4为MO-RL场景下基于LMF定位的方法流程图；
图5A、图5B、图5C为本申请实施例适用的三种可能的网络架构的示意图；
图6A、图6B为LMC与终端交互时所涉及的协议栈的示意图；
图7为本申请实施例提供的一种定位方法的流程图；
图8为Alternative 1场景下的一种定位方法的流程图；
图9为Alternative 2和Alternative3场景下的一种定位方法的流程图；
图10为Alternative 2和Alternative3场景下的另一种定位方法的流程图；
图11为基站将自身支持LMC的信息告知给核心网的方法流程图；
图12为核心网指示是否允许基站针对终端执行基于LMC定位的方法流程图；
图13为源基站将指示信息传输给目标基站的方法流程图；
图14为本申请实施例提供的一种装置1400的结构示意图；
图15为本申请实施例提供的一种装置1500的结构示意图；
图16为本申请实施例提供的一种装置1600的结构示意图；
图17为本申请实施例提供的一种装置1700的结构示意图；
图18为本申请实施例提供的一种装置1800的结构示意图。
具体实施方式
以下，对本申请实施例中的部分用语进行解释说明，以便于本领域技术人员理解。
1)、本申请实施例中所涉及的终端设备，又可以称之为终端，是用户侧的一种用于接收或发射信号的实体，用于向网络设备发送上行信号，或从网络设备接收下行信号。包括向用户提供语音和/或数据连通性的设备，例如可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的处理设备。该终端设备可以经无线接入网(radio access network，RAN)与核心网进行通信，与RAN交换语音和/或数据。该终端设备可以包括用户设备(user equipment，UE)、V2X终端设备、无线终端设备、移动终端设备、设备到设备通信(device-to-device，D2D)终端设备、机器到机器/机器类通信(machine-to-machine/machine-type communications，M2M/MTC)终端设备、物联网(internet of things，IoT)终端设备、订户单元(subscriber unit)、订户站(subscriber station)，移动站(mobile station)、远程站(remote station)、接入点(access point，AP)、远程终端(remote terminal)、接入终端(access terminal)、用户终端(user terminal)、用户代理(user agent)、或用户装备(user device)、可穿戴设备、车载设备等。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备或智能穿戴式设备等，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能头盔、智能首饰等。
而如上介绍的各种终端设备，如果位于车辆上(例如放置在车辆内或安装在车辆内)，都可以认为是车载终端设备，车载终端设备例如也称为车载单元(on-board unit，OBU)。
2)、本申请实施例中所涉及的核心网，可以包括对用户的信令和数据进行处理和转发的网络设备。例如包括AMF、会话管理功能(session management function，SMF)以及用户面网关等核心网设备。其中用户面网关可以是具有对用户面数据进行移动性管理、路由、转发等功能的服务器，一般位于网络侧，如服务网关(serving gateway，SGW)或分组数据网络网关(packet data network gateway，PGW)或用户面网元功能实体(user plane function，UPF)等。AMF以及SMF相当于LTE系统中的移动管理实体(mobility management entity，MME)。AMF主要负责准入方面，SMF主要负责会话管理。当然，核心网中也可以包括其他网元，这里不一一列举。
3)、本申请实施例中所涉及的NG-RAN，可以包括一个或多个接入网设备。NG-RAN中的接入网设备又可以称为基站，或者RAN节点，或者RAN设备。接入网设备是网络侧的一种用于发射和/或接收信号的实体，可以用于将收到的空中帧与网络协议(internet protocol，IP)分组进行相互转换，作为终端与接入网的其余部分之间的路由器，其中接入网的其余部分可以包括IP网络等。接入网设备还可以协调对空中接口的属性管理。例如，接入网设备可以是LTE中的演进型基站(evolutional Node B，eNB或e-NodeB)，eNB是一种部署在无线接入网中满足4G标准的为UE提供无线通信功能的装置。接入网设备还可以是新无线控制器(new radio controller，NR controller)，可以是5G系统中的gNode B (gNB)，可以是集中式网元(centralized unit)，可以是新无线基站，可以是射频拉远模块，可以是微基站(也称为小站)，可以是中继(relay)，可以是分布式网元(distributed unit)，可以是各种形式的宏基站，可以是传输接收点(transmission reception point，TRP)、传输测量功能(transmission measurement function，TMF)或传输点(transmission point，TP)或者任何其它无线接入设备，或者下一代通信中的基站，但本申请实施例不限于此。
在一些部署中，基站(如gNB)可以由集中式单元(centralized unit,CU)和分布式单元(distributed unit,DU)构成，即对原LTE接入网中的基站的功能进行拆分，将基站的部分功能部署在一个CU，将剩余功能部署在DU，多个DU共用一个CU，可以节省成本，以及易于网络扩展。CU和DU的切分可以按照协议栈切分，将RRC层、SDAP层以及PDCP层部署在CU，其余的无线链路控制RLC层、MAC层以及PHY层部署在DU。CU和DU之间可以通过F1接口连接。CU代表gNB通过NG接口和核心网连接，CU代表gNB通过Xn接口和其他gNB连接。
更进一步，CU还可以划分为CU-控制面(control plane，CP)和CU-用户面(user plan，UP)。其中CU-CP负责控制面功能，主要包含RRC和控制面对应的PDCP即PDCP-C。PDCP-C主要负责控制面数据的加解密，完整性保护，数据传输等。CU-UP负责用户面功能，主要包含SDAP和用户面对应的PDCP即PDCP-U。其中SDAP主要负责将核心网的数据进行处理并将flow映射到承载。PDCP-U主要负责数据面的加解密，完整性保护，头压缩，序列号维护，数据传输等。其中CU-CP和CU-UP通过E1接口连接。CU-CP代表gNB通过NG接口和核心网连接。通过F1接口控制面即F1-C和DU连接。CU-UP通过F1接口用户面即F1-U和DU连接。当然还有一种可能的实现是PDCP-C也在CU-UP。
4)、本申请实施例中的术语“系统”和“网络”可被互换使用。术语“多个”是指两个或两个以上。术语“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，字符“/”，如无特殊说明，一般表示前后关联对象是一种“或”的关系。
图1为LTE和NR Rel-16中的定位架构的示意图，如图1所示，涉及的网元/模块主要包括下一代无线接入网络(next generation radio access network，NG RAN)、终端和核心网三部分。
其中，核心网包括定位管理功能(location management function，LMF)、接入和移动性管理功能(access and mobility management function，AMF)、服务定位协议(service location protocol，SLP)以及演进服务移动定位中心(evolved serving mobile location centre，E-SMLC)等。定位服务器即定位管理功能(location management function，LMF)连接到AMF，LMF和AMF之间通过NLs接口连接。LMF负责支持有关终端的不同类型的位置服务，包括对终端的定位和向终端传递辅助数据。AMF可以从第5代核心网络定位服务(5th generation core network location services，5GC LCS)实体接收与终端相关的位置服务请求，或者AMF本身也可代表特定终端启动一些位置服务，并将位置服务请求转发给LMF。得到终端返回的位置信息后，将相关位置信息返回给5GC LCS实体。
NG RAN可以包括下一代节点B(next generation node B，gNB)、下一代演进型基站(next generation evolved nodeB，ng-eNB)等。gNB、ng-eNB之间通过Xn接口连接，LMF与ng-eNB/gNB通过NG-C接口连接。
终端可以测量来自NG RAN和其他来源的下行链路信号以支持定位。gNB/ng-eNB可 以为终端提供测量信息，并将此信息传达给LMF。
LMF和终端可能进行的信息交互包括以下几种：1)LMF与ng-eNB/gNB之间通过NR定位协议a(NR positioning protocol a，NRPPa)消息进行信息交互，例如获取定位参考信号(positioning reference signals，PRS)、探测参考信号(sounding reference signal，SRS)配置信息、小区定时、小区位置信息等；2)LMF与终端之间通过LTE定位协议(LTE positioning protocol，LPP)消息进行终端能力信息传递、辅助信息传递、测量信息传递等。
图2为LMF与终端交互所涉及的协议栈示意图。如图2所示，终端和NG RAN之间通过NR-Uu接口或LTE-Uu接口连接，终端侧用于与NG RAN交互的协议栈从上至下依次包括：LPP、非接入层(non-access stratum，NAS)、无线资源控制(radio resource control，RRC)、包数据汇聚协议(packet data convergence protocol，PDCP)、无线链路控制(radio link control，RLC)、媒体接入控制(medium access control，MAC)、层(layer，L)1，NG RAN侧用于与终端交互的协议栈从上至下依次包括：RRC、PDCP、RLC、MAC、L1；NG RAN与AMF之间通过NG-C接口连接，NG RAN侧用于与AMF交互的协议栈从上至下依次包括：NG接口应用协议(NG application protocol，NGAP)、流控制传输协议(stream control transmission protocol，SCTP)、网际互连协议(internet protocol，IP)、L2、L1，AMF侧用于与NG RAN交互的协议栈从上至下依次包括：NAS、NGAP、SCTP、IP、L2、L1；AMF与LMF之间通过NLs接口连接，AMF侧用于与LMF交互的协议栈从上至下依次包括：超文本传输协议2.0((hyper text transfer protocol，HTTP2.0)、传输层安全(transport layer security，TLS)、传输控制协议(transmission control protocol，TCP)、IP、L2、L1，LMF侧用于与AMF交互的协议栈从上至下依次包括：LPP、HTTP2.0、TLS、TCP、IP、L2、L1。
LMF与终端之间的交互信息可以通过LPP消息承载，LPP消息通过Uu接口和NG-C接口发送，在终端侧LPP消息将被封装为NAS信令，基站收到终端的NAS信令(基站不知道终端发的是LPP消息)后转给AMF，AMF解析NAS信令后获得LPP消息并将其交给LMF，类似的，从LMF侧发出的LPP消息封装为一个NAS信令发给基站，基站收到NAS信令之后直接转到终端(基站不知道收到的NAS信令包含的LPP消息)。LMF与基站之间的交换信息通过NRPPa消息承载，通过NG-C接口进行发送。
图3为基于图1所示定位架构执行定位的方法流程图，包括：
步骤1a/1b、定位客户请求获取终端的位置，将请求发送给AMF，或者终端的服务AMF由于一些原因(比如紧急呼叫)需要获取到终端的位置。
步骤2、如果终端处于空闲态，则AMF发送寻呼使终端进入连接态，AMF发送定位请求给LMF；
步骤3a/3b、LMF发起定位过程，比如，LMF从终端获取终端的定位能力，从服务基站获取到定位测量或辅助信息，从终端获取到位置或定位测量结果，或发送定位辅助信息给终端等；
步骤4、LMF基于终端或基站的测量结果计算得到终端的位置，在定位业务响应消息中将终端的位置发送给AMF；
步骤5a/5b、AMF将终端的位置发送给定位客户，或者将终端的位置用于紧急呼叫。
其中，根据定位发起方(即定位客户)的不同，有下列几种定位场景：1)MO-LR(mobile originated location request)，是终端自己发起请求来获取自己的位置信息；2)MT-LR(mobile  terminated location request)，是第三方发起请求来获取终端的位置信息；3)NI-LR(network induced location request)，是终端的服务核心网AMF发起请求来获取到该终端的位置信息；4)RI-LR(RAN induced location request)，是终端的接入网(如基站)发起请求来获取该终端的位置信息。
示例性的，图4示出了MO-RL场景下基于LMF的定位流程图，如图4所示，基于LMF的MO-LR定位中，终端发起定位请求的过程为：终端发送一个NAS消息，用于向AMF指示请求获取终端的位置信息，然后AMF与LMF交互。AMF返回位置信息的过程为：AMF在获取到终端的位置后，AMF向终端发送NAS相应消息，携带位置信息。
通过图3和图4所示的流程可以看出：在传统的定位架构中，LMF与终端之间的消息交互需要经过AMF和基站，导致时延较大。
为了减少时延，3GPP批准了一个研究项目，研究将定位功能(LMF的功能)放到接入网，称之为定位管理组件(location management component，LMC)。但是，目前，对于目标客户如何向LMC发起定位请求，以及LMC如何返回位置信息给目标客户，还没有具体方案。
为此，本申请实施例提供一种定位方法：终端经由基站发送请求消息给AMF，用于请求终端的位置信息，AMF再将请求发送给LMC(对于Alternative 2和Alternative 3，AMF发送给基站，基站再发送给LMC)；LMC在获取到位置信息后，LMC先将携带位置信息的响应消息发送给AMF，AMF再通过基站将响应消息发送给终端。
但是，上述过程类似于基于LMF的定位流程，因此定位请求和定位结果仍然需要经过核心网AMF，定位过程经过的节点较多，时延开销较大。
为此，本申请实施例还提供另一种定位方法：终端通过LPP消息或RRC消息直接向支持LMC的基站发起定位请求，而基站对终端的具体的定位过程(即获取终端的位置信息的过程)仍然使用LPP过程；基站获取到终端的位置信息后，直接通过LPP消息或RRC消息将位置信息返回给终端。这样，可以避免定位请求以及位置信息先发送到核心网再绕回到基站，从而较大程度地降低定位过程的整体时延。
进一步的，基站还可以将自身是/否支持基于LMC的定位的指示信息发送给终端以及发送给核心网，以避免由于基站不支持基于LMC的定位而发生的定位失败。
进一步的，核心网还可以发送指示信息给基站来指示是/否允许支持LMC的基站针对该终端执行基于LMC的定位，以保护终端的隐私安全。
本申请实施例提供的定位方法可以应用于各种通信系统，例如：长期演进(long term evolution，LTE)系统、第五代(5th generation，5G)系统，如NR，及下一代的通信系统，如6G系统等。当然，本申请实施例的技术方案也可以应用于其它的通信系统，只要该通信系统存在对终端的定位需求即可。
图5A为本申请实施例适用的一种网络架构，通信系统包括核心网、NG-RAN和终端。核心网包括LMF、AMF、SLP以及E-SMLC等网元/模块，NG RAN包括gNB、ng-eNB等网元/模块，其中LMF、AMF、SLP、E-SMLC、gNB以及ng-eNB等网元/模块的具体功能、各个网元/模块之间的连接关系可以参见上文图1相关部分的介绍，这里不再赘述。
与图1不同的是，图5A所示的网络架构中NG-RAN中增加了LMC，LMC的具体部署方式是设置在基站内部，如设置在gNB中或设置在ng-ENB中。在这种网络架构中，LMC作为是基站内部的一个功能，因此不需要引入新的接口。为了便于描述，本文将图5A所 示网络架构方案称为备选方案(Alternative)1。
图5B为本申请实施例适用的另一种网络架构，如图5B所示，通信系统同样包括核心网、NG-RAN和终端。与Alternative1不同的是，图5B所示的网络架构中的LMC在NG-RAN中作为一个独立的逻辑节点，通过一个新接口与基站相连接，例如图5B中，LMC通过接口Itf与gNB-CU相连。为了便于描述，本文将图5B所示网络架构方案称为Alternative2。
图5C为本申请实施例适用的另一种网络架构，如图5C所示，通信系统同样包括核心网、NG-RAN和终端，LMC在NG-RAN中作为一个独立的逻辑节点，与图5B不同的是，LMC可以图5C经过新接口同时与多个基站连接。图5C以LMC与两个基站同时相连为例，在具体实施时LMC还可以与更多的基站相连。为了便于描述，本文将图5B所示网络架构方案称为Alternative3。
应理解，上述图5A、图5B、图5C仅是一种示例性说明，并不对本申请适用的通信系统所包括网元的类型、数量、连接方式等进行具体限定。
下面介绍LMC与终端交互时所涉及的协议栈。
图6A、图6B示出了LMC与终端交互时所涉及的协议栈。如图6A所示，LMC作为基站内部的一个功能时，LMC与终端通过接口NR-Uu连接，终端侧的协议栈从上至下包括：LPP、RRC、PDCP、RLC、MAC、L1；gNB/LMC侧的协议栈从上至下包括：LPP、RRC、PDCP、RLC、MAC、L1。如图6B所示，LMC作为一个逻辑节点经过接口可以与一个或多个基站连接时，终端侧的协议栈从上至下包括：LPP、RRC、PDCP、RLC、MAC、L1；gNB侧面向终端的协议栈从上至下包括：RRC、PDCP、RLC、MAC、L1；gNB侧面向LMC的协议栈从上至下包括：XPAP、SCTP、IP、L2、L1；LMC侧的协议栈从上至下包括：LPP、XPAP、SCTP、IP、L2、L1。
需要指出的是，为了便于描述，本文中将gNB与LMC的接口的名称表示为“XP”，gNB与LMC的接口协议表示为“XPAP”，在实际应用中，gNB与LMC的接口的名称以及对应的接口协议还可以是其他具体的表示形式，这里不做限制。
LMC与终端之间的定位交互可以使用LPP协议，也可以是其他协议，下文以LPP协议为例进行描述。
为了使本申请的目的、技术方案和优点更加清楚，下面结合本申请实施例中的附图对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅是本申请的一部分实施例，而不是全部的实施例。
请参见图7，为本申请实施例提供的一种定位方法，该方法可以应用于图5A或图5B或图5C所示的通信系统。
S701、终端设备向接入网设备发送定位请求，其中所述接入网设备能够支持基于LMC的定位。
接入网设备是NG RAN中的设备，例如gNB、ng-eNB，或者Alternative2和Alternative3中的LMC等，这里不做限制。
如前文所述，如果LMC的部署方案为图5A所示的Alternative1，即LMC作为基站内部的一个功能，则接入网设备为LMC所在的基站，接入网设备接收到定位请求后，对终端直接发起基于LMC的定位。
如果LMC的部署方案为图5B所示的Alternative2或图5C所示的Alternative3，即LMC作为一个逻辑节点与一个或多个基站连接，则接入网设备为与LMC连接的任意一个基站。 在这种情况下，接入网设备在接收到定位请求后，需要将定位请求通过第一接口转发给LMC，然后LMC响应于该定位请求对终端定位。接入网设备为了实现对定位请求的转发，在将定位请求转发给LMC之前，需要建立与LMC的第一接口的连接，接入网设备与LMC建立第一接口的具体过程包括：接入网设备向LMC发送第一接口建立请求消息，用于请求建立接入网设备和LMC之间的第一接口；LMC接收到第一接口建立请求消息后，向所述接入网设备发送第一接口建立响应消息。可选的，第一接口建立响应消息中可以携带LMC提供的服务质量(quality of service，QoS)信息，使得接入网设备在与LMC建立第一接口时，一并获取到LMC的QoS信息，这样接入网设备就可以不再额外发起获取LMC的QoS信息的流程，可以进一步减少时延。
作为一种可选的实施方式，定位请求可以是(或者说，承载于)LPP消息或者RRC消息，这样，定位请求可以直接发送至接入网设备，不再需要经过核心网。如果定位请求承载于LPP消息中，则终端的LPP层生成LPP消息发送给接入网设备，用于请求获取终端的位置，定位请求可以作为LPP的信元呈现；如果定位请求承载于RRC消息中，则终端的RRC层产生RRC消息给接入网设备，用于请求获取终端的位置，定位请求可以作为RRC的信元呈现。
作为一种可选的实施方式，定位请求中还可以包含终端的定位QoS信息，例如定位精度要求，响应时间要求，定位QoS等级等。这样，接入网设备可以基于终端的定位QoS信息，为终端提供更好的定位服务。
作为一种可选的实施方式，所述定位请求中还可以包含终端的定位能力信息，例如该终端支持的定位方法，以及每种定位方法各自的测量能力等。这样，接入网设备可以不再额外发起获取终端能力的过程，从而进一步降低时延。
作为一种可选的实施方式，在步骤S701之前，接入网设备可以先向终端发送第一指示信息，用于指示接入网设备或者终端所属的小区是否支持基于LMC的定位，使得终端只有在接收到第一指示信息且根据第一指示信息确定该接入网设备支持基于LMC的定位时，才向该接入网设备发起定位请求。终端基于第一指示信息来确定是否发起定位请求或者确定是否发起基于LMF的定位请求，能够避免终端发起对应的定位请求但是接入网设备不支持LMC导致定位失败的情况发生。
作为一种示例，基站可以在小区的系统信息中广播第一指示信息，用于指示当前的小区/基站是否支持基于LMC的定位，或者当前的服务基站是否连接了一个LMC。第一指示信息可以是1bit，比如，取值为1代表支持，取值为0代表不支持；或者当第一指示信息的信元包含在系统信息中时表示支持，不包含在系统信息中时表示不支持。
有可能运营商在部署了LMC后，就不再部署LMF，或者两者都部署，因此，作为另一种示例，接入网设备还可以发送另一个指示信息，可以通过LPP协议，RRC协议或者系统信息，用于指示是否支持基于LMF的定位；或者接入网设备将指示是否支持基于LMF的定位与指示是否支持基于LMC的定位的指示信息合并为一个指示信息(信元)，比如是一个枚举型的参数，当枚举值为LMC时，表示只支持LMC，当枚举值为LMF时，表示只支持LMF，当枚举值为BOTH时，表示既支持LMC又支持LMF。
当然，第一指示信息除了以广播的方式发送给终端外，也可以是通过其它形式发送，本申请实施例对第一指示信息的发送方式不做具体限制。例如第一指示信息还可以是接入网设备响应终端的询问请求所返回的应答信息，即终端在发起定位请求之前，终端先向接 入网设备发送询问请求，询问接入网设备是否支持基于所述LMC的定位，终端在收到接入网设备的应答信息为接入网设备支持LMC时再发起定位请求，如果终端未收到应答信息或者收到的应答信息标识接入网设备不支持LMC，则不发起定位请求或者不发起基于LMC的定位请求。
作为一种可选的实施方式，接入网设备还可以将该接入网设备是/否支持LMC的指示信息(第三指示信息)告知给核心网，用于在MO-LR、MT-LR、NI-LR或RI-LR场景下，核心网决定是否发起基于LMC的定位(或者说是发起基于LMC的定位还是发起基于LMF的定位)。
第三指示信息可以是显式的指示信息，也可以是隐式的，这里不做限制。例如，第三指示信息携带了LMC相关的信息，表示支持，不携带表示不支持，这里不做具体限制。
第三指示信息中还可以包括：LMC的ID，用于标识该LMC；LMC能提供的QoS信息，如LMC的定位方法、LMC的时延、LMC的定位精度等信息。
第三指示信息可以携带于接入网设备和核心网的第二接口建立请求消息中发送给核心网，或者是在RAN配置更新消息中发送给核心网，或者是新引入一个新的消息来发送给核心网，这里不做限制。
进一步的，接入网设备从终端接收定位请求之前，接入网设备还可以接收核心网发送的是/否允许该接入网设备使用LMC对该终端定位的第四指示信息，接入网设备只有接收到第四指示信息且确定第四指示信息用于指示核心网允许该接入网设备使用LMC对终端定位时，才对该终端发起基于LMC的定位接入网设备，这样可以保护终端的隐私安全。
第四指示信息可以携带于核心网发送给接入网设备的终端上下文建立请求消息中。
作为一种可选的实施方式，当终端执行接入网设备切换时，接入网设备可以将第四指示信息发送给终端切换后的接入网设备，使得切换后的接入网设备能够及时获知能否使用LMC对该终端进行定位，进而更好的保护终端的隐私安全。
S702、接入网设备接收该定位请求，并响应该定位请求，基于LMC对终端定位。
具体的，接入网设备发起LPP定位过程来获取终端的位置信息，可以类似于现有的基于LMF的定位过程，比如，接入网设备通过LPP能力传输(LPP Capability Transfer)过程获取终端的定位能力，通过LPP辅助数据传输(LPP Assistance Data Transfer)过程向终端发送辅助信息，通过LPP位置信息传输(LPP Location Information Transfer)过程命令终端进行定位测量，并从终端接收到定位测量结果，接入网设备基于定位测量结果计算出终端的位置信息等，这里不再一一赘述。
S703、接入网设备向终端发送定位结果。
定位结果包含终端的位置信息的第二指示信息。
定位结果可以携带于LPP消息或者RRC消息中。如果定位请求携带于LPP消息中，则定位结果也携带于LPP消息中；如果定位请求携带于RRC消息中，则定位结果也携带于RRC消息中。
如前文所述，如果LMC的部署方案为图5A所示的Alternative1，即LMC作为基站内部的一个功能，则接入网设备为LMC所在的基站，则LMC对终端定位获得定位结果后，直接将定位结果返回给终端。如果LMC的部署方案为图5B所示的Alternative2或图5C所示的Alternative3，即LMC作为一个逻辑节点与一个或多个基站连接，则接入网设备为与LMC连接的任意一个基站，在这种情况下，LMC对终端定位获得定位结果后，先将定 位结果通过第一接口转发给接入网设备，再由接入网设备将定位结果返回给终端。
需要指出的是，由于LMF和LMC均使用LPP协议，终端可以通过LPP消息的传递途径获知定位消息是从LMF来的(NAS层递交给LPP层)，还是LMC来的(RRC层递交给LPP层)，或者在交互的LPP消息里，增加一个指示信息，用于指明定位服务器是LMC还是LMF。
一种可能的示例，在LPP消息的LPP-TransactionID信元里的Initiator里新增一个枚举值lmc，当lmc取值为locationServer表明为LMF，当取值为lmc表明为LMC。
本申请实施例中，通过LPP消息或RRC消息来实现终端请求基于LMC的MO-LR定位，可以有效减少定位的时延。接入网设备将是否支持基于LMC的定位的指示信息发送给终端和核心网，可以避免由于接入网设备不支持基于LMC的定位而发生的定位失败。另外，核心网还发送指示信息给基站来指示是否允许接入网设备/LMC针对该终端的基于LMC的定位，可以保护终端的隐私安全。
为了更好地理解本申请技术方案，下面列举几个具体的实施例对本申请技术方案进行更详细的说明。
实施例一
本实施例讲述Alternative 1场景下的具体定位过程。参见图8，方法包括：
S801、基站向终端发送指示信息，例如，在小区的系统信息中广播该指示信息，用于指示当前的小区/基站是否支持基于LMC的定位，或者当前的服务基站是否连接了一个LMC。
具体的，该指示信息可以是1bit，比如，取值为1代表支持，取值为0代表不支持；或者当该指示信息的信元包含在系统信息中时表示支持，不包含(缺省)在系统信息中时表示不支持。终端可以基于这个信息来确定是否发起基于LMC定位，是否发起基于LMF定位，以避免发起对应的定位但是网络不支持的情况发生。
有可能运营商在部署了LMC后，不再部署LMF，或者两者都部署，因此，可选的，在小区的系统信息中广播另一个指示信息，用于指示是否支持基于LMF的定位；或者与前一个(是否支持LMC的)指示信息合并为一个指示信息(信元)，比如是一个枚举型的参数，当枚举值为LMC时，表示只支持LMC，当枚举值为LMF时，表示只支持LMF，当枚举值为BOTH时，表示既支持LMC又支持LMF。
S802、终端通过接收小区的系统信息获知是否能发起基于LMC的MO-LR定位。可选的，也可获知是否能发起基于LMF的MO-LR定位。当终端需要发起MO-LR定位时，终端根据定位的时延等要求，以及LMC或LMF的支持情况，选择基于LMC或LMF定位。如果选择了基于LMC的定位，则确定发起基于LMC的定位过程。
S803、终端通过LPP消息或RRC消息向基站发送定位请求用于请求获取终端的位置。
方式1，终端的LPP层产生LPP消息Location Request发送给基站。
可选的，该Location Request消息中还可以携带终端定位的QoS信息，比如定位精度要求，响应时间要求，定位QoS等级等，可以避免LMC获取终端定位的QoS信息的过程，从而进一步降低时延。在定位过程中，LMC需要知道终端的定位能力，以决定采用的定位方法，因此，终端在该Location Request消息中还可携带定位能力信息，以避免LMC与终端之间的获取终端能力的过程，从而进一步降低时延。
应理解，这里的LPP消息是一个新引入的消息，所以消息名Location Request只是LPP消息的消息名的一个示例，并不作为限定。
Location Request可以是一个新引入的LPP消息，也可以基于现有的LPP消息，比如提供能力(ProvideCapabilities)消息，在该消息中增加一个指示信息，或者endTransaction设为false，用于指示终端需要获取位置信息，或者默认LMC收到的第一个消息是ProvideCapabilities表示需要获取位置，这里不做限制。
方式2、终端的RRC层产生RRC消息Location Request发送给基。
同理，方式2中的Location Request消息中还可以携带终端定位的QoS信息，比如定位精度要求，响应时间要求，定位QoS等级等，这些信息均可以作为RRC的信元呈现。这样，可以避免LMC获取终端定位的QoS信息的过程，从而进一步降低时延。
在定位过程中，LMC需要知道终端的定位能力，以决定采用的定位方法，因此终端还可以在Location Request消息中携带一个LPP PDU，这个LPP PDU是携带终端的定位能力的ProvideCapabilities消息，以避免LMC与终端之间的获取终端能力的过程，从而进一步降低时延。
方式2中的RRC消息是一个新引入的消息，所以消息名Location Request只是RRC消息的消息名的一个示例，并不作为限定。
S804、基站发起LPP定位过程来获取终端的位置，可以类似于现有的基于LMF的定位过程，这里不再一一赘述。
需要说明的是，由于LMF和LMC均使用LPP协议，终端通过LPP消息的传递途径能获知定位消息是从LMF来的(NAS层递交给LPP层)，还是LMC来的(RRC层递交给LPP层)，或者在交互的LPP消息里，增加一个指示信息，用于指明定位服务器是LMC还是LMF，一种方法是，在LPP消息的LPP-TransactionID信元里的Initiator里新增一个枚举值lmc，当取值为locationServer表明为LMF，当取值为lmc表明为LMC。
Initiator＝ENUMERATED{
locationServer,
targetDevice,
…
lmc
}
如果终端是通过RCC消息基站发起定位请求，则基站收到该RRC消息后，基站的RRC层通知基站的LPP层该终端需要进行定位(同时还可以递交相关的定位QoS信息)。
S805、基站在获取到终端的位置后，通过下行RRC消息或LPP消息返回定位结果给终端。
对应上述方式1，基站在获取到终端的位置后，产生LPP消息Location Response消息发送给终端，该消息中携带步骤4中获取到的终端的位置。
同理，由于LPP响应消息是一个新引入的消息，所以消息名Location Response只是LPP消息名的一个示例，并不作为限定。Location Response可以是一个新引入的LPP消息，也可以基于现有的LPP消息，比如提供位置信息(ProvideLocationInformation)消息，使用ProvideLocationInformation来作为响应消息，以发送定位结果给终端。
需要指出的是，在相关技术中，ProvideLocationInformation是终端发送给LMF的消息， 用于终端将定位测量结果发送给LMF，而这里作为Location Response消息的ProvideLocationInformation的发送方向不同，是从LMC发往终端。
对应上述方式2，基站在获取到终端的位置后，基站产生RRC消息Location Response消息发送给终端，该消息中携带步骤S1304中获取到的终端的位置。
同理，这里的RRC消息是一个新引入的消息，所以消息名Location Response只是RRC消息的消息名的一个示例，并不作为限定。
实施例二
本实施例讲述Alternative 2和Alternative3场景下的具体定位过程。参见图9，方法包括：
S901、基站/CU向LMC发送接口建立请求消息，用于请求建立两者之间的接口。
在本申请实施例中，基站可以主动向LMC发起接口建立过程，这样可以避免伪LMC的出现，提高安全性能。
可选的，该接口建立请求消息中可携带该基站/基站下的小区是/否支持定位参考信号的指示信息。
S902、LMC向基站/CU发送接口建立响应消息。
可选的，该接口建立响应消息中可以携带该LMC能提供的QoS信息，如时延、精度、支持的定位方法等信息。
S903、基站向终端发送指示信息，例如在小区的系统信息中广播该指示信息，用于指示当前的小区/基站是否支持基于LMC的定位，或者当前的服务基站是否连接了一个LMC。
具体实现方法同图8中的步骤S801，这里不再赘述。
S904、终端发起基于LMC的定位过程。
具体实现方法同图8中的步骤S802，这里不再赘述。
S905、终端的LPP层产生LPP消息Location Request发送给LMC，用于请求获取终端的位置。
可选的，Location Request消息中可以携带终端定位的QoS信息，比如定位精度要求，响应时间要求，定位QoS等级等，这样可以避免LMC获取终端定位的QoS信息的过程，从而进一步降低时延。在定位过程中，LMC需要知道终端的定位能力，以决定采用的定位方法，所以终端还可以在Location Request消息中携带终端定位能力信息，这样可以避免LMC与终端之间的获取终端能力的过程，从而进一步降低时延。
应理解，这里的Location Request可以是一个新引入的LPP消息，可替换地，也可以基于现有的LPP消息，比如ProvideCapabilities消息，在该消息中增加一个指示信息，或endTransaction设为false，用于指示终端需要获取位置信息，或者默认LMC收到的第一个消息是ProvideCapabilities表示需要获取位置。
S906、LMC发起LPP定位过程来获取终端的位置，可以类似于现有的基于LMF的定位过程，这里不再一一赘述。
S907、LMC在获取到终端的位置后，LMC产生LPP消息Location Response消息发送给终端，该消息中携带步骤S906中获取到的终端的位置。
这里Location Response的具体实现方式可以参见上述步骤S805中Location Response的具体实现方式，这里不再赘述。
图9示出了终端基于LPP消息发起定位请求，基站/LMC基于LPP消息返回定位结果的定位方法。在具体实施时，终端也可以基于RRC消息发起定位请求，基站/LMC基于RRC消息返回定位结果的定位方法，参见图10，方法包括：
S1001、基站/CU向LMC发送接口建立请求消息，用于请求建立两者之间的接口。
S1002、LMC向基站/CU发送接口建立响应消息。
S1003、基站向终端发送指示信息，例如在小区的系统信息中广播该指示信息，用于指示当前的小区/基站是否支持基于LMC的定位，或者当前的服务基站是否连接了一个LMC。
S1004、终端发起基于LMC的定位过程。
上述S1001-S1004的具体实现方式可以参见上述S901-S904的具体实现方式，这里不再赘述。
S1005、终端的RRC层产生RRC消息Location Request发送给基站/CU，用于请求获取终端的位置。
可选的，该Location Request消息中可以携带终端定位的QoS信息，比如定位精度要求、响应时间要求、定位QoS等级等，以避免LMC获取终端定位的QoS信息的过程，从而进一步降低时延。进一步的，在定位过程中，LMC还要知道终端的定位能力，以决定采用的定位方法，所以终端在Location Request消息中还可以携带一个LPP PDU，这个LPP PDU是携带终端的定位能力的ProvideCapabilities消息，以避免LMC与终端之间的获取终端能力的过程，从而进一步降低时延。
应理解，这里的RRC消息是一个新引入的消息，所以消息名Location Request只是RRC消息的消息名的一个示例，并不作为限定。
S1006、基站/CU向LMC发送两者之间的接口消息Location Request，用于请求获取终端的位置。
可选的，该消息中可以携带终端定位的QoS信息和/或终端定位能力信息。
S1007、LMC发起LPP定位过程来获取终端的位置，可以类似于现有的基于LMF的定位过程，这里不再一一赘述。
S1008、LMC在获取到终端的位置后，产生LMC与基站/CU之间的接口消息Location Response消息，并发送给基站/CU，该消息中携带步骤S1007中获取到的终端的位置。
S1009、基站/CU产生RRC消息Location Response消息，并发送给终端，该消息中携带终端的位置。
实施例三
本实施例三聚焦在终端的隐私安全，主要讲述核心网能(比如，基于终端的签约等信息)控制是否允许基站/LMC针对该终端的(基于LMC的)定位，比如，不允许基站对敏感的终端进行定位。核心网将(用于指示是/否允许基站/LMC针对该终端的基于LMC的定位的)指示信息发送给基站，基站基于该指示信息来确定是否接受终端发起的基于LMC的定位，或者确定基站自己是否能发起针对该终端的基于LMC的定位。
对于NI-LR和MT-LR定位，核心网收到定位请求后，核心网可以决定是基于LMC进行定位还是基于LMF进行定位，但是核心网需要先知道终端的当前的服务基站是否支持LMC。一种可能的设计是，当基站支持LMC时，基站将自身支持LMC的信息主动告知给连接的核 心网，以用于核心网能决定是否允许基站/LMC针对该终端的基于LMC的定位。这些信息可能包括下面一项或多项：1)基站是否支持LMC(或者说是否支持基于LMC的定位)，可以是显式的指示信息，也可以是隐式的，比如携带了LMC相关的信息，表示支持，不携带表示不支持；2)该LMC能提供的QoS，包括时延、精度、支持的定位方法等信息；3)LMC ID，用于标识该LMC。
作为一种示例，参见图11中的步骤S1101a和S1101b，基站可以在建立NG接口的过程中将是否支持LMC的信息发送给核心网。作为另一种示例，参见图11中的步骤S1102a和S1102b，也可以在RAN配置更新过程中将是否支持LMC的信息发送给核心网。当然，还可以是新引入一个新的消息来发送，本申请实施例对基站如何告知核心网的方式不做具体限制。
参见图12，核心网(具体可以是核心网中的AMF)可以在上下文建立请求消息中携带指示信息，用于指示是否允许基站针对该终端执行基于LMC的定位。
S1201、终端发起初始接入，建立空口的RRC连接。
S1202、基站向AMF发送初始UE消息((Initial UE Message)。
S1203、AMF向终端发送UE上下文建立请求消息(UE Context Setup Request)，请求基站建立该终端的上下文。该消息中携带指示信息，用于指示是否允许基站/LMC针对该终端的基于LMC的定位。
进一步地，指示信息，可以细分为是否允许基于LMC的MO-LR定位(即UE as client的定位)，是否允许基于LMC的RI-LR定位(即，RAN as client的定位)等。
S1204、基站保存该指示信息，并且在后续的过程中，基于该指示信息来确定是否能支持针对该UE的基于LMC的定位。
对于MO-LR定位，如果指示信息指示不允许基于LMC的定位(或不允许基于LMC的MO-LR定位)，则基站在收到该UE发送的LPP消息后不递交给LPP层或不发送给LMC。可选的，空口可以发送一个消息用于指示LPP消息失败，携带一个原因值，比如，原因值是不允许定位。
对于RI-LR定位，如果指示信息指示不允许，则基站不能发起针对该UE的定位。
可选的，对于核心网发送给基站的MT-LR和NI-LR定位请求，基站可以直接执行相关的定位过程，不受限于上述指示信息的限制。
S1205、基站向核心网发送UE上下文建立响应消息(UE Context Setup Response)。
参见图13，当终端的基站切换发生时，上述指示信息可以由源基站传递给目标基站，目标基站后续继续使用该指示信息来进行上述步骤S1604的处理。流程图如下：
S1301、源基站决定将终端的基站切换至目标基站；
S1302、源基站向目标基站发送切换请求(Handover Request)消息，该切换请求消息中携带是否允许基站/LMC针对该终端执行基于LMC的定位的指示信息；
S1303、目标基站保存该指示信息；
S1304、目标基站向源基站发送切换请求确认(Handover Request ACK)消息。
本实施例通过核心网发送指示信息给基站来指示是否允许基站/LMC针对该终端的基于LMC的定位，从而可以保护终端的隐私安全。
以上各实施例可以相互结合以实现不同的技术效果。
上述本申请提供的实施例中，从终端、接入网设备、核心网和LMC之间交互的角度 对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，终端、接入网设备、核心网和LMC可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。
参见图14，示出了本申请实施例提供的一种装置1400的结构示意图，装置1400是可以是接入网设备，也可以是接入网络设备中的装置。装置1400包括用于执行上述方法实施例中接入网设备执行的方法的单元/模块，例如包括：
接收单元1401，用于从终端接收定位请求，其中所述接入网设备支持基于定位管理组件LMC的定位；
处理单元1402，用于响应所述定位请求，并基于所述LMC对所述终端定位；
发送单元1403，用于向所述终端发送定位结果。
在一种可能的实施方式中，所述发送单元1403还用于：
在所述接收单元1401从终端接收定位请求之前，向所述终端发送第一指示信息，其中所述第一指示信息用于指示所述接入网设备支持基于LMC的定位。
在一种可能的实施方式中，所述第一指示信息包括：
所述接入网设备广播的系统信息；或者，
所述接入网设备响应所述终端的询问请求所返回的应答信息，其中所述询问请求用于询问所述接入网设备是否支持基于所述LMC的定位。
在一种可能的实施方式中，所述定位请求中包含所述终端的定位服务质量QoS信息，和/或所述终端的定位能力信息；
其中，所述QoS信息包括：时延、精度、QoS等级或定位方法中的至少一项；
所述定位能力信息包括：所述终端支持的定位方法，所述终端支持的定位方法对应的测量能力。
在一种可能的实施方式中，所述定位结果中包含所述终端的位置信息的第二指示信息。
在一种可能的实施方式中，所述定位请求携带于LTE定位协议LPP消息或者RRC消息中。
在一种可能的实施方式中，所述接入网设备与所述LMC通过第一接口连接；
所述发送单元1403还用于：在所述接收单元1401从终端接收定位请求之后，通过所述第一接口将所述定位请求转发给所述LMC；
所述接收单元1401还用于：在所述发送单元1403向所述终端发送定位结果之前，通过所述第一接口从所述LMC接收所述定位结果。
在一种可能的实施方式中，所述发送单元1403还用于：在所述接收单元1401从终端接收定位请求之前，向所述LMC发送第一接口建立请求消息，用于请求建立所述接入网设备和所述LMC之间的第一接口；
所述接收单元1401还用于：接收所述LMC返回的第一接口建立响应消息，其中所述第一接口建立响应消息中携带所述LMC提供的QoS信息。
在一种可能的实施方式中，在接入网设备从终端接收定位请求之前，所述方法还包括：
所述接入网设备向核心网发送所述接入网设备支持基于LMC的定位的第三指示信息。
在一种可能的实施方式中，所述第三指示信息携带于所述发送单元1403发送给所述 核心网的接口建立请求消息中。
在一种可能的实施方式中，所述第三指示信息包括以下信息中的一项或多项：
所述LMC的身份标识ID；
所述LMC的定位方法；
所述LMC的时延；
所述LMC的定位精度。
在一种可能的实施方式中，所述接收单元1401还用于：在从终端接收定位请求之前，接收核心网发送的所述核心网是/否允许所述接入网设备使用LMC对所述终端定位的第四指示信息；
所述处理单元1402还用于：在基于所述LMC对所述终端定位之前，确定所述第四指示信息用于指示所述核心网允许所述接入网设备使用LMC对所述终端定位。
在一种可能的实施方式中，所述第四指示信息携带于所述核心网发送给所述接入网设备的终端上下文建立请求消息中。
在一种可能的实施方式中，所述发送单元1403还用于：当所述终端执行接入网设备切换时，将所述第四指示信息发送给所述终端切换后的接入网设备。
参见图15，示出了本申请实施例提供的一种装置1500的结构示意图，装置1500是可以是终端，也可以是终端中的装置。装置1500包括用于执行上述方法实施例中终端执行的方法的单元/模块，例如包括：
发送单元1501，用于向接入网设备发送定位请求，其中所述接入网设备支持基于定位管理组件LMC的定位；
接收单元1502，用于接收所述接入网设备发送的定位结果。
在一种可能的实施方式中，所述接收单元1502还用于：在所述发送单元1501向接入网设备发送定位请求之前，接收所述接入网设备发送的第一指示信息，其中所述第一指示信息用于指示所述接入网设备支持基于LMC的定位。
在一种可能的实施方式中，所述第一指示信息可以包括：所述接入网设备广播的系统信息；或者，所述接入网设备响应所述终端的询问请求所返回的应答信息，其中所述询问请求用于询问所述接入网设备是否支持基于所述LMC的定位。
在一种可能的实施方式中，所述定位请求中可以包含所述终端的定位服务质量QoS信息，和/或所述终端的定位能力信息；其中，所述QoS信息包括：时延、精度、QoS等级或定位方法中的至少一项；所述定位能力信息包括：所述终端支持的定位方法，所述终端支持的定位方法对应的测量能力。
在一种可能的实施方式中，所述定位结果中包含所述终端的位置信息的第二指示信息。
在一种可能的实施方式中，所述定位请求携带于LTE定位协议LPP消息或者RRC消息中。
参见图16，示出了本申请实施例提供的一种装置1600的结构示意图，装置1600是可以是LMC，也可以是LMC中的装置。装置1600包括用于执行上述方法实施例中LMC执行的方法的单元/模块，例如包括：
接收单元1601，用于接收接入网设备发送的定位请求；
处理单元1602，用于响应所述定位请求，并基于所述LMC对所述终端定位；
发送单元1603，用于将定位结果发送给所述接入网设备，以使所述接入网设备将所述 定位结果转发给终端。
在一种可能的实施方式中，所述接入网设备与所述LMC通过第一接口连接；
所述接收单元1601具体用于：接收接入网设备通过所述第一接口发送的定位请求；
所述发送单元1603具体用于：将定位结果通过所述第一接口发送给所述接入网设备。
在一种可能的实施方式中，所述接收单元1601还用于：在接收接入网设备发送的定位请求之前，接收所述接入网设备发送的第一接口建立请求消息，其中所述第一接口建立请求消息用于请求建立所述接入网设备和所述LMC之间的第一接口；
所述发送单元1603还用于：向所述接入网设备发送第一接口建立响应消息，其中所述第一接口建立响应消息中携带所述LMC提供的QoS信息。
参见图17，示出了本申请实施例提供的一种装置1700的结构示意图，装置1700是可以是核心网，也可以是核心网中的装置。装置1700包括用于执行上述方法实施例中核心网执行的方法的单元/模块，例如包括：
接收单元1701，用于接收接入网设备发送的初始UE消息，其中所述接入网设备支持基于定位管理组件LMC的定位；
发送单元1702，用于向所述接入网设备发送第四指示信息，所述第四指示信息用于指示是/否允许所述接入网设备或所述LMC针对所述终端设备基于LMC定位。
在一种可能的实施方式中，所述接收单元1701还用于：在接收接入网设备发送的初始UE消息之前，接收所述接入网设备发送的所述接入网设备支持基于LMC的定位的第三指示信息。
在一种可能的实施方式中，所述第三指示信息还可以携带于所述接入网设备发送给所述核心网的接口建立请求消息中。
在一种可能的实施方式中，所述第三指示信息可以包括以下信息中的一项或多项：所述LMC的身份标识ID；所述LMC的定位方法；所述LMC的时延；所述LMC的定位精度。
在一种可能的实施方式中，所述第四指示信息可以携带于所述核心网发送给所述接入网设备的终端设备上下文建立请求消息中。
在一种可能的实施方式中，所述第四指示信息的内容可以包括以下几项中的一项或多项：是/否允许基于LMC的MO-LR定位；是/否允许基于LMC的RI-LR定位；是/否允许基于LMC的MT-LR定位；是/否允许基于LMC的NI-LR定位。
请参见图18，示出了本申请实施例提供的一种通信装置1800的结构示意图，包括：
至少一个处理器1801；以及与所述至少一个处理器1801通信连接的存储器1802、通信接口1803；
其中，所述存储器1802存储有可被所述至少一个处理器1801执行的指令，所述至少一个处理器1801通过执行所述存储器1802存储的指令，执行上述方法实施例中终端、接入网设备、核心网或LMC所执行的方法。
需要指出的是，本申请实施例中不限定上述通信接口1803、处理器1801以及存储器1802之间的具体连接介质。本申请实施例在图18中以通信接口1803、处理器1801以及存储器1802之间通过总线1804连接，总线在图18中以粗线表示，其它部件之间的连接方式，仅是进行示意性说明，并不引以为限。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图18中仅用一条粗线表示，但并不表示仅有一根总线或一种类 型的总线。
处理器1801可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
存储器1802可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储程序指令和/或数据。
通信接口1803用于装置1800和其它模块进行通信，其可以是电路、器件、接口、总线、软件模块、收发器或者其它任意可以实现通信的装置。
基于同一技术构思，本申请实施例提供一种计算机可读存储介质，包括程序或指令，当所述程序或指令在计算机上运行时，执行上述方法实施例中终端、接入网设备、核心网或LMC所执行的方法。
基于同一技术构思，本申请实施例提供一种芯片，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，实现上述方法实施例中终端、接入网设备、核心网或LMC所执行的方法。
基于同一技术构思，本申请实施例还提供一种无线通信系统，该无线通信系统包括本申请实施例中所涉及的终端、接入网设备、LMC以及核心网。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机 或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的保护范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (29)

  1. 一种定位方法，其特征在于，包括：
    接入网设备从终端接收定位请求，其中所述接入网设备支持基于定位管理组件LMC的定位；
    所述接入网设备响应所述定位请求，并基于所述LMC对所述终端定位；
    所述接入网设备向所述终端发送定位结果。
  2. 如权利要求1所述的方法，其特征在于，在接入网设备从终端接收定位请求之前，还包括：
    所述接入网设备向所述终端发送第一指示信息，其中所述第一指示信息用于指示所述接入网设备支持基于LMC的定位。
  3. 如权利要求2所述的方法，其特征在于，所述第一指示信息包括：
    所述接入网设备广播的系统信息；或者，
    所述接入网设备响应所述终端的询问请求所返回的应答信息，其中所述询问请求用于询问所述接入网设备是否支持基于所述LMC的定位。
  4. 如权利要求1所述的方法，其特征在于，所述定位请求中包含所述终端的定位服务质量QoS信息，和/或所述终端的定位能力信息；
    其中，所述QoS信息包括：时延、精度、QoS等级或定位方法中的至少一项；
    所述定位能力信息包括：所述终端支持的定位方法，所述终端支持的定位方法对应的测量能力。
  5. 如权利要求1所述的方法，其特征在于，所述定位结果中包含所述终端的位置信息的第二指示信息。
  6. 如权利要求1-5中任一项所述的方法，其特征在于，所述定位请求携带于LTE定位协议LPP消息或者RRC消息中。
  7. 如权利要求1-5中任一项所述的方法，其特征在于，所述接入网设备与所述LMC通过第一接口连接；
    在接入网设备从终端接收定位请求之后，所述方法还包括：
    所述接入网设备通过所述第一接口将所述定位请求转发给所述LMC；
    在所述接入网设备向所述终端发送定位结果之前，所述方法还包括：
    所述接入网设备通过所述第一接口从所述LMC接收所述定位结果。
  8. 如权利要求7所述的方法，其特征在于，在接入网设备从终端接收定位请求之前，所述方法还包括：
    所述接入网设备向所述LMC发送第一接口建立请求消息，用于请求建立所述接入网设备和所述LMC之间的第一接口；
    所述接入网设备接收所述LMC返回的第一接口建立响应消息，其中所述第一接口建立响应消息中携带所述LMC提供的QoS信息。
  9. 如权利要求1-5中任一项所述的方法，其特征在于，在接入网设备从终端接收定位请求之前，所述方法还包括：
    所述接入网设备向核心网发送所述接入网设备支持基于LMC的定位的第三指示信息。
  10. 如权利要求9所述的方法，其特征在于，所述第三指示信息携带于所述接入网设 备发送给所述核心网的接口建立请求消息中。
  11. 如权利要求9所述的方法，其特征在于，所述第三指示信息包括以下信息中的一项或多项：
    所述LMC的身份标识ID；
    所述LMC的定位方法；
    所述LMC的时延；
    所述LMC的定位精度。
  12. 如权利要求1-5中任一项所述的方法，其特征在于，在接入网设备从终端接收定位请求之前，所述方法还包括：
    所述接入网设备接收核心网发送的所述核心网是/否允许所述接入网设备使用LMC对所述终端定位的第四指示信息；
    在所述接入网设备基于所述LMC对所述终端定位之前，所述方法还包括：
    所述接入网设备确定所述第四指示信息用于指示所述核心网允许所述接入网设备使用LMC对所述终端定位。
  13. 如权利要求11所述的方法，其特征在于，所述第四指示信息携带于所述核心网发送给所述接入网设备的终端上下文建立请求消息中。
  14. 如权利要求11所述的方法，其特征在于，所述方法还包括：
    当所述终端执行接入网设备切换时，所述接入网设备将所述第四指示信息发送给所述终端切换后的接入网设备。
  15. 一种定位方法，其特征在于，包括：
    终端向接入网设备发送定位请求，其中所述接入网设备支持基于定位管理组件LMC的定位；
    所述终端接收所述接入网设备发送的定位结果。
  16. 如权利要求15所述的方法，其特征在于，在终端向接入网设备发送定位请求之前，还包括：
    所述终端接收所述接入网设备发送的第一指示信息，其中所述第一指示信息用于指示所述接入网设备支持基于LMC的定位。
  17. 如权利要求16所述的方法，其特征在于，所述第一指示信息包括：
    所述接入网设备广播的系统信息；或者
    所述接入网设备响应所述终端的询问请求所返回的应答信息，其中所述询问请求用于询问所述接入网设备是否支持基于所述LMC的定位。
  18. 如权利要求15所述的方法，其特征在于，所述定位请求中包含所述终端的定位服务质量QoS信息，和/或所述终端的定位能力信息；
    其中，所述QoS信息包括：时延、精度、QoS等级或定位方法中的至少一项；
    所述定位能力信息包括：所述终端支持的定位方法，所述终端支持的定位方法对应的测量能力。
  19. 如权利要求15所述的方法，其特征在于，所述定位结果中包含所述终端的位置信息的第二指示信息。
  20. 如权利要求15-19中任一项所述的方法，其特征在于，所述定位请求携带于LTE定位协议LPP消息或者RRC消息中。
  21. 一种定位方法，其特征在于，包括：
    定位管理组件LMC接收接入网设备发送的定位请求；
    所述LMC响应所述定位请求，并基于所述LMC对所述终端定位；
    所述LMC将定位结果发送给所述接入网设备，以使所述接入网设备将所述定位结果转发给终端。
  22. 如权利要求21所述的方法，其特征在于，所述接入网设备与所述LMC通过第一接口连接；
    LMC接收接入网设备发送的定位请求，包括：
    LMC接收接入网设备通过所述第一接口发送的定位请求；
    所述LMC将定位结果发送给所述接入网设备，包括：
    所述LMC将定位结果通过所述第一接口发送给所述接入网设备。
  23. 如权利要求21所述的方法，其特征在于，在LMC接收接入网设备发送的定位请求之前，所述方法还包括：
    所述LMC接收所述接入网设备发送的第一接口建立请求消息，其中所述第一接口建立请求消息用于请求建立所述接入网设备和所述LMC之间的第一接口；
    所LMC向所述接入网设备发送第一接口建立响应消息，其中所述第一接口建立响应消息中携带所述LMC提供的QoS信息。
  24. 一种接入网设备，其特征在于，包括：
    接收单元，用于从终端接收定位请求，其中所述接入网设备支持基于定位管理组件LMC的定位；
    处理单元，用于响应所述定位请求，并基于所述LMC对所述终端定位；
    发送单元，用于向所述终端发送定位结果。
  25. 一种终端，其特征在于，包括：
    发送单元，用于向接入网设备发送定位请求，其中所述接入网设备支持基于定位管理组件LMC的定位；
    接收单元，用于接收所述接入网设备发送的定位结果。
  26. 一种定位管理组件LMC，其特征在于，包括：
    接收单元，用于接收接入网设备发送的定位请求；
    处理单元，用于响应所述定位请求，并基于所述LMC对所述终端定位；
    发送单元，用于将定位结果发送给所述接入网设备，以使所述接入网设备将所述定位结果转发给终端。
  27. 一种通信装置，其特征在于，包括：
    至少一个处理器；以及与所述至少一个处理器通信连接的存储器、通信接口；
    其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述至少一个处理器通过执行所述存储器存储的指令，执行如权利要求1-14、15-20或21-23中任一项所述的方法。
  28. 一种计算机可读存储介质，其特征在于，包括程序或指令，当所述程序或指令在计算机上运行时，执行如权利要求1-14、15-20或21-23中任一项所述的方法。
  29. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，实现如权利要求1-14、15-20或21-23中任一项所述的方法。
PCT/CN2020/073532 2020-01-21 2020-01-21 一种定位方法及对应装置 WO2021146924A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/073532 WO2021146924A1 (zh) 2020-01-21 2020-01-21 一种定位方法及对应装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/073532 WO2021146924A1 (zh) 2020-01-21 2020-01-21 一种定位方法及对应装置

Publications (1)

Publication Number Publication Date
WO2021146924A1 true WO2021146924A1 (zh) 2021-07-29

Family

ID=76992015

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/073532 WO2021146924A1 (zh) 2020-01-21 2020-01-21 一种定位方法及对应装置

Country Status (1)

Country Link
WO (1) WO2021146924A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10327109B1 (en) * 2018-08-29 2019-06-18 Qualcomm Incorporated Methods and systems for location determination of a mobile device using partial RF bands
CN109951867A (zh) * 2019-03-29 2019-06-28 腾讯科技（深圳）有限公司 一种事件处理方法和设备以及系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10327109B1 (en) * 2018-08-29 2019-06-18 Qualcomm Incorporated Methods and systems for location determination of a mobile device using partial RF bands
CN109951867A (zh) * 2019-03-29 2019-06-28 腾讯科技（深圳）有限公司 一种事件处理方法和设备以及系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: ""Proposed Corrections to the LMC Description"", 3GPP TSG-RAN WG3 #105BIS, R3-195863, 4 October 2019 (2019-10-04), XP051792881 *

Similar Documents

Publication Publication Date Title
CN108605383B (zh) 无线通信系统中执行用于基于网络切片的nr的小区规范过程的方法和装置
KR101645106B1 (ko) 무선 통신 네트워크 내의 소규모 데이터 통신
KR102293786B1 (ko) 릴레이 가능 사용자 장비(ue)를 통하여 원격 ue 및 통신 네트워크 사이의 접속을 확립하는 방법 및 시스템
US20190007921A1 (en) Pdu session management
WO2019214729A1 (zh) 数据处理的方法和设备
WO2022028034A1 (zh) 一种定位方法及通信装置
WO2019184651A1 (zh) 一种通信方法及装置
US10034173B2 (en) MTC service management using NFV
JP2019512903A (ja) 無線通信方法、及び装置
TWI724775B (zh) 傳輸協定選擇方法及使用者設備
US20230156833A1 (en) Packet Forwarding Method, Apparatus, and System
US20210258275A1 (en) Low latency messaging service for the 5gc
CN108605378B (zh) 一种数据传输方法、装置及相关设备
WO2021047454A1 (zh) 位置信息获取、位置服务配置方法和通信设备
WO2017121224A1 (zh) 一种数据传输方法、装置及系统
WO2021146924A1 (zh) 一种定位方法及对应装置
WO2022236598A1 (zh) 信息处理方法及装置、通信设备及存储介质
CN114503625B (zh) 一种通信方法、装置以及系统
WO2021134763A1 (zh) 一种恢复传输的方法、装置及设备
CN113853809A (zh) 用于处置ue类别信息的ue、网络节点
WO2022152241A1 (en) Systems and methods for device triggering for 5g devices
WO2014110763A1 (zh) 设备到设备通信的信息上报方法、用户设备以及基站
WO2019029297A1 (zh) 建立数据通道的方法、设备及非易失性计算机可读存储介质
WO2024027299A1 (zh) 消息路由方法和装置
WO2022257733A1 (zh) 一种网络共享场景下的通信处理方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20914849

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20914849

Country of ref document: EP

Kind code of ref document: A1