Method for supporting location service and apparatus therefor

Abstract

A method of supporting location service, a method of transmitting information related to location service, and a base station and user equipment using the same are disclosed. To efficiently support location services, a base station receives an uplink, UL, message from a user equipment, UE. The base station determines whether the UL message includes a positioning protocol message associated with a positioning protocol for exchanging information related to the location service. In a first case, in response to determining that the UL message includes a positioning protocol message, the base station sends the positioning protocol message to a local entity that implements the location service. In a second case, in response to determining that the message does not include any positioning protocol message, the base station transmits at least some of the data included in the UL message to the remote node.

Description

[0001] This application is a divisional application of the invention patent application filed on April 5, 2019, with application number 201980096839.0 and invention title "Supporting Location Services at Base Stations". Technical Field

[0002] This disclosure relates generally to wireless communications, and more specifically to location-based services operating in wireless communication systems. Background Technology

[0003] This background description is provided for the purpose of generally presenting the context of this disclosure. The work of the currently named inventor, to the extent described in this background section, and in any aspect of the description that may not be worthy of being considered prior art at the time of filing, is neither expressly nor implied to be recognized as prior art to this disclosure.

[0004] For example, when a UE cannot determine its location due to limited hardware capabilities, when the UE receives insufficient satellite or other beacon signals, or when a base station attempts to locate the UE in an emergency, Location Service (LCS) allows the user equipment unit (UE) and / or the base station to determine the UE's geographical location.

[0005] For example, entities supporting LCS in the core network (CN) include the Location Management Function (LMF) and the Evolved Services Mobile Location Center (E-SMLC). The UE can exchange messages with the LMF using a positioning protocol such as the LTE Positioning Protocol (LPP) described in the 3GPP TS 36.355 v15.2.0 standard. According to another standard (3GPP TS 24.501), the UE sends an LPP message to the Access Management Function (AMF) operating in the CN in an uplink (UL) Non-Access Stratum (NAS) transport message. The AMF then forwards the LPP message to either the LMF or the E-SMLC. In the downlink direction, the AMF uses a DL NAS transport message to send the LPP message from the LMF or E-SMLC to the UE.

[0006] The recent 3GPP technical document R2-1816955 proposes implementing a "local LCS," specifically a local LMF operating in a radio access network (RAN). However, implementing this architecture using available messaging schemes leads to increased message latency, excessive transmission overhead, and inefficient use of network links. Summary of the Invention

[0007] The base station of this disclosure efficiently transmits location service-related messages (e.g., LTE Location Protocol (LPP) messages, NR Location Protocol (NRPP) messages, or other suitable location protocol messages) received from or addressed to a UE. As an example, the base station of this disclosure directly sends certain location protocol messages to an LCS entity operating in the RAN, without routing these messages through a CN, thereby reducing the latency of these location protocol messages. Furthermore, the base station and UE of this disclosure reduce the overhead of transmitting these messages by layering at least some of the location protocol messages directly on the protocol used to control radio resources, without relying on an intermediate layer. Some of the location protocol messages with reduced overhead are transmitted between the UE and nodes in the RAN, and some are transmitted between the UE and the CN.

[0008] When used herein, “sending a message” can refer to transmitting a message to another node via a wireless or wired interface (e.g., a radio access technology (RAT) such as 5G NR, an Xn interface for interconnecting base stations, or an NG interface for interconnecting base stations and 5GC), as well as sending a message to another entity located on the same node. Furthermore, when used herein, “transmitting a message” can refer to layering (i.e., encapsulating) a message on one or more underlying protocols and sending it to the appropriate recipient on the same or different nodes.

[0009] Furthermore, these technologies allow the UE to selectively access RAN-based LCS, CN-based LCS, or both. Specifically, the wireless communication network may include an LMF or E-SMLC implemented in a CN node to provide CN-based LCS, and / or an LMF implemented in a RAN node (e.g., a base station or other device operating in the RAN) to provide RAN-based LCS. For all LCS services and / or messages of the positioning protocol, or only some services and / or messages, the UE can choose between RAN-based and CN-based LCS based on its capabilities. In some implementations, the base station determines whether the RAN supports local LCS before receiving uplink positioning protocol messages and provides the UE with an appropriate indication of that determination. The base station may also provide the UE with an indication of whether the CN supports LCS, or the UE may expect the CN to support LCS by default.

[0010] In one implementation, the base station supports at least partial processing of the NAS message to determine whether the UL NAS message includes a location protocol message. When the UL NAS message includes a location protocol message, the base station sends the location protocol message to the local LMF (or more generally to the local LCS entity); otherwise, the base station sends the UL NAS message to a remote node at the CN.

[0011] In another example implementation, when the RAN supports a local LCS, the UE and base station layer location protocol messages directly at the Radio Resource Control (RRC) layer. In yet another implementation, the UE layers some location protocol messages at the NAS / RRC layer, while layering others directly at the RRC layer. The base station thus determines whether a location protocol message should be routed to a local LCS or a remote LCS entity based on whether it is layered at the NAS or directly at the RRC layer.

[0012] An example embodiment of these technologies is a method for supporting location services. This method can be implemented by processing hardware at a base station and includes receiving a UL message from a user equipment (UE) and determining whether the UL message includes a location protocol message associated with a location protocol used to exchange information related to the location service. In a first case, in response to determining that the UL message includes a location protocol message, the method includes sending the location protocol message to a local entity implementing the location service. In a second case, in response to determining that the message does not include any location protocol message, the method includes sending at least some of the data included in the UL message to a remote node.

[0013] Another example embodiment of these technologies is a base station that includes processing hardware and is configured to implement the methods described above.

[0014] Another example embodiment of these technologies is a method for transmitting location service-related information. This method can be implemented by processing hardware at the UE and includes generating a location protocol message associated with a location protocol used to exchange location service-related information, generating a UL RRC message, including layering the location protocol message directly on the RRC layer of the UL RRC message, and transmitting the UL RRC message to a base station via a radio interface.

[0015] Another example embodiment of these technologies is a method for transmitting location service-related information. This method can be implemented by processing hardware at the UE and includes generating a location protocol message associated with a location protocol used to exchange location service-related information and determining whether the location protocol message addresses to a RAN node or a CN node. In a first case, the method includes, in response to determining that the location protocol message addresses to a RAN node, including the location protocol message in a first lower-layer message and transmitting the first lower-layer message to a base station via a radio interface. In a second case, the method includes, in response to determining that the location protocol message addresses to a CN node, including the location protocol message in a second lower-layer message and transmitting the second lower-layer message to the base station via a radio interface.

[0016] Another example embodiment of these technologies is a UE that includes processing hardware and is configured to implement one of the methods described above.

[0017] Another example embodiment of these technologies is a computer program product that includes instructions that, when executed by a computing device, cause the computing device to perform one of the methods described above.

[0018] Furthermore, according to another aspect of this disclosure, a method for supporting location services is provided. The method includes, at a base station: receiving an uplink UL radio resource control (RRC) message from a user equipment (UE); determining whether the UL message includes a location protocol message associated with a location protocol used for exchanging information related to location services, and the location protocol message is directly layered on the RRC without an intermediate protocol layer; in a first case, in response to determining that the UL message includes the location protocol message, sending the location protocol message to a local entity implementing the location service in a radio access network (RAN); and in a second case, in response to determining that the UL message does not include any location protocol message, sending at least some data included in the UL message to a core network.

[0019] According to another aspect of this disclosure, a base station that implements the above method is provided.

[0020] Furthermore, according to another aspect of this disclosure, a method for transmitting location service-related information is provided. The method includes, at a UE: generating a location protocol message associated with a location protocol used for exchanging location service-related information; generating a UL RRC message, including layering the location protocol message directly on the RRC layer of the UL RRC message; transmitting the UL RRC message to a base station via a radio interface; receiving from the base station (i) an indication that the base station supports a first location service at a radio access network (RAN) node, and (ii) an indication that the CN supports a second location service at a node operating in the CN; addressing the UL RRC message to the first location service in response to determining that the first location service has a higher priority than the second location service; and addressing the UL RRC message to the second location service in response to determining that the second location service has a higher priority than the first location service.

[0021] According to another aspect of this disclosure, a user device that implements the above-described method is provided.

[0022] Furthermore, according to another aspect of this disclosure, a method for transmitting location service-related information is provided. The method includes, at a UE: generating a location protocol message associated with a location protocol used for exchanging location service-related information; determining whether the location protocol message addresses a radio access network (RAN) node or a core network (CN) node. In a first case: in response to determining that the location protocol message addresses the RAN node, the location protocol message is included in a first lower-layer message, wherein the location protocol message is layered directly on the RRC without intermediate protocol layers, and the first lower-layer message is transmitted to a base station via a radio interface. In a second case: in response to determining that the location protocol message addresses the CN node, the location protocol message is included in a second lower-layer message, the second lower-layer message differing from the first lower-layer message in at least one aspect of message type or protocol layering, wherein the location protocol message is layered on the NAS, and the second lower-layer message is transmitted to the base station via the radio interface.

[0023] According to another aspect of this disclosure, a user device that implements the above-described method is provided. Attached Figure Description

[0024] Figure 1 This is a block diagram of an example wireless communication network in which a base station and a UE, according to the technology of this disclosure, can communicate with an LCS entity implemented in the RAN;

[0025] Figure 2 It is a block diagram of a known protocol stack in which the UE, base station, and core network can exchange information related to location services.

[0026] Figure 3 This is a block diagram of an example protocol stack according to which the base station operates to transmit LPP messages layered on the NAS to the local LMF;

[0027] Figure 4 This is a block diagram of an example protocol stack of a base station operating according to the present disclosure to transmit LPP messages layered on the NAS to a local LMF co-located with the base station.

[0028] Figure 5 It is possible Figure 1 A flowchart of an example method implemented in a base station for hierarchically transmitting LPP messages to the local LMF or AMF in the uplink direction;

[0029] Figure 6A It is possible Figure 1 A flowchart of an example method implemented in a UE for generating LPP messages using different NAS messages for transmission to a local LMF or a remote node;

[0030] Figure 6B It is possible Figure 1 A flowchart of an example method implemented in a base station for transmitting LPP messages from an LCS entity to a UE in the downlink direction using different NAS messages;

[0031] Figure 6C It is possible Figure 1 A flowchart of an example method implemented in a base station for transmitting messages from the local LMF or core network to the UE in the downlink direction;

[0032] Figure 7A It is possible Figure 1 A flowchart of another example method implemented in a UE for generating LPP messages using different RRC messages for transmission to a local LMF or a remote node;

[0033] Figure 7B It is possible Figure 1 A flowchart of an example method implemented in a base station for transmitting LPP messages from an LCS entity to a UE in the downlink direction using different RRC messages;

[0034] Figure 7C It is possible Figure 1 A flowchart of an example method implemented in a base station for transmitting messages from the local LMF or core network to the UE in the downlink direction;

[0035] Figure 8 This is a block diagram of an example protocol stack according to which the base station operates to transmit LPP messages layered directly on the RRC to the local LMF;

[0036] Figure 9 This is a block diagram of an example protocol stack of a base station operating according to the present disclosure to transmit LPP messages layered directly on the RRC to a local LMF co-located with the base station.

[0037] Figure 10A It is possible Figure 1 A block diagram of an example protocol stack for a UE operating in a wireless communication network, the UE having two LPP modules for supporting different corresponding transport mechanisms;

[0038] Figure 10B It is possible Figure 1 A block diagram of an example protocol stack for a UE operating in a wireless communication network, the UE having a single LPP module supporting two different corresponding transmission mechanisms;

[0039] Figure 11 It is possible Figure 1A flowchart of an example method implemented in a base station for transmitting LPP messages, which are layered directly on RRC messages, to the local LMF or AMF in the uplink direction;

[0040] Figure 12A This occurs after the base station notifies UE 102 that it supports RAN-based LCS. Figure 1 A message passing diagram of an example scenario in which the UE and the base station exchange LPP messages directly layered on the NAS via RRC;

[0041] Figure 12B Is it in it? Figure 1 The UE and the base station exchange LPP messages layered on the NAS, and the CN notifies the UE of a message graph of an example scenario supporting CN-based LCS.

[0042] Figure 13 It is possible Figure 1 A flowchart of an example method implemented in a UE for determining whether to execute a RAN-based LCS or a CN-based LCS;

[0043] Figure 14 Is it in it? Figure 1 A message passing diagram of an example scenario in which the UE and the base station exchange LPP messages layered on RRC or NAS;

[0044] Figure 15 This is a message passing diagram of an example scenario in which the UE performs the positioning process with the assistance of the local LMF;

[0045] Figure 16 This is a message passing diagram of an example scenario in which the UE performs a location process related to a location request (MO-LR) initiated by the mobile device;

[0046] Figure 17 This is a message passing diagram of an example scenario in which the UE performs a location process related to the termination of the location request (MT-LR) by the mobile device;

[0047] Figure 18 This is a message passing diagram of an example scenario in which the UE performs a location process related to a network-initiated location request (NI-LR);

[0048] Figure 19 This is a message passing diagram of an example scenario in which the UE performs a location reporting process triggered by an event;

[0049] Figure 20 It is possible Figure 1 A flowchart of an example method implemented in a base station for transmitting uplink location messages to a local LCS entity;

[0050] Figure 21It is possible Figure 1 A flowchart of an example method implemented in a UE for sending location protocol messages to a local or more LCS entities via a base station; and

[0051] Figure 22 It is possible Figure 1 A flowchart of another example method implemented in the UE for sending location protocol messages to local or more LCS entities via a base station. Detailed Implementation

[0052] Figure 1 An example wireless communication network 100 is depicted, wherein, using the messaging techniques of this disclosure, UE 102 generates and receives location service-related messages, and base station 104 transmits location service-related messages. UE 102 can generate and receive these messages according to a location protocol such as LPP. As discussed below, UE 102 and base station 104 can layer these location protocol messages at lower-level protocols to reduce transmission overhead and efficiently address and / or transmit these messages to nodes in the RAN and / or CN.

[0053] Base station 104 can operate as a 5G Node B (gNB) supporting NR cell 108. In another embodiment, base station 104 operates as a Next Generation Evolved Node B eNB (ng-eNB), and cell 108 supports the Evolved Universal Terrestrial Radio Access (EUTRA) radio interface. In either case, base station 104 is connected (directly or indirectly) to 5G core network (5GC) 110 to access various core network functions, services, components, etc., including AMF 112 and LMF / E-SMLC 114. Depending on the implementation, component 114 includes LMF (which may be referred to as “non-local LMF” in this document for clarity), E-SMLC, or both. In some embodiments, base station 104 can be a disaggregated base station consisting of centralized units (CU) and distributed units (DU).

[0054] Base station 104 can connect to a separate device or node implementing local LMF 120. In another embodiment, the local LMF is co-located with base station 104 and operates as a software and / or hardware component of base station 104. Another base station 106, operating as a gNB or ng-eNB, can also connect to 5GC 110 and support the same cell 108 or another cell. In some embodiments, base station 106 can also access the local LMF 120.

[0055] In operation, the local LMF 120 can generate (i.e., derive or calculate) location information using positioning results and map information from the UE 102. Alternatively, the local LMF 120 can use positioning results and other location information to generate (i.e., derive or calculate) location information that can indicate a reference location (e.g., the location of the local LMF 120). As a further example, the local LMF 120 can receive an LPP-provided location information message (which may be referred to as the first LPP-provided location information message) and another LPP-provided location information message (which may be referred to as the second LPP-provided location information message) from the UE 102. The local LMF 120 can use the positioning results from the first LPP-provided location information message and the positioning results from the second LPP-provided location information message to generate location information to obtain more accurate location information.

[0056] Components 104, 106, and 120 operate as components of RAN 130. Therefore, in Figure 1 In the example configuration, UE 102 can access at least two entities providing location services: one entity operating in RAN 130 (i.e., local LMF 120) and another entity operating in 5GC 110 (i.e., LMF / E-SMLC 114). In at least some implementations, local LMF 120 and E-SMLC 114 support the same location protocol, such as LPP or NRPP. For convenience, the following discussion of various systems, protocol stacks, scenarios, flowcharts, etc., primarily concerns LPP. However, these techniques are similarly applicable to NRPP and other suitable location protocols.

[0057] Although the following examples primarily involve EUTRA, NR, and 5GC, broadly similar technologies can be applied to other radio access and / or core network technologies.

[0058] like Figure 1 As shown, UE 102 is equipped with processing hardware 120, which may include one or more general-purpose processors (such as a central processing unit (CPU)) and a non-transitory computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors and / or dedicated processing units. In the example embodiment, processing hardware 120 includes an LCS controller 152 that generates location-related outbound (uplink) messages, processes location-related inbound (downlink) messages, and performs various location-related procedures.

[0059] In some implementations, the LCS controller 152 uses LCS configuration 154, which can indicate preferences or priorities for, for example, RAN-based or CN-based LCS. UE 102 can receive LCS configuration 154 from 5GC 110, RAN 130, Universal Subscriber Identity Module (USIM), UE 102's operating system settings, user input, or any other suitable source.

[0060] The ng-eNB 104 is equipped with processing hardware 160, which may also include one or more general-purpose processors (such as a CPU) and non-transitory computer-readable memory storing machine-readable instructions executable on one or more general-purpose processors and / or dedicated processing units. In this embodiment, the processing hardware 160 includes an LCS message router 162, which determines where the base station 104 should direct uplink positioning protocol messages and how the base station 104 should format downlink positioning protocol messages. For this purpose, the LCS message router 162 can use input from an LPP message recognizer 164 that determines the type of LPP messages and a NAS message recognizer 166 that determines the type of NAS messages. Furthermore, in some embodiments or scenarios, the LCS message router 162 can receive information about the type and content of RRC messages from the RRC controller 168 and provide information about the type and content of outbound RRC messages to the RRC controller 168.

[0061] Now for reference Figure 2 In known wireless communication systems, the UE and gNB / ng-eNB support the physical layer (PHY) 202 of EUTRA or NR. PHY layer 202 provides transport channels to the Media Access Control (MAC) sublayer 204, which in turn provides logical channels to the Radio Link Control (RLC) sublayer 206, and the RLC sublayer provides RLC channels to the Packet Data Convergence Protocol (PDCP) sublayer 208. Sublayer 208, the PDCP sublayer, provides signaling radio bearers (SRBs) and / or data radio bearers (DRBs) to the Radio Resource Control (RRC) sublayer 210.

[0062] UEs and AMFs operating in the core network exchange Non-Access Stratum (NAS) sublayer 212 messages via gNB / ng-eNB, and UEs and LMFs / E-SMLCs also operating in the core network exchange LPP layer 214 messages via gNB / ng-eNB and AMF. In other words, UEs and LMFs / E-SMLCs encapsulate LPP messages within NAS messages and NAS messages within RRC messages. Based on this architecture, the gNB / ng-eNB simply provides tunnels to layers 212 and 214 and does not route or otherwise process messages at layers 212 and 214.

[0063] Next, Figure 3-1 Section 2 illustrates several examples of protocol architectures that the UE 102 and base station 104 of this disclosure can operate to efficiently support local and / or non-local LCS services, as well as corresponding methods that the UE 102 and base station 104 can implement.

[0064] First refer to Figure 3 Base station 104 implements at least part of the processing capabilities of NAS layer 212 according to protocol architecture 300. Specifically, base station 104 can parse NAS messages to determine whether the message includes an LPP message (without having to process all other information in the NAS message). According to this architecture, UE 102 generates an LPP message, includes the LPP message in a UL NAS message, includes the generated NAS message in a UL RRC message, and sends the UL RRC message to base station 104. Figure 3 As shown, UL 102 layers the UL RRC message at PDCP, RLC, MAC, and PHY. When base station 104 receives the UL RRC message, it extracts the UL NAS message from the UL RRC message and then extracts the LPP message from the UL message.

[0065] Base station 104 then sends the LPP message to local LMF 120, which processes the LPP message. For example, local LMF 120 can extract the payload by processing the LPP message according to the LPP protocol. In this embodiment, local LMF 120 operates as a node separate from base station 104 in RAN 130. Therefore, in order to transmit the LPP message, base station 104 sends the LPP message via a network link. However, in other embodiments discussed below, for example, local LMF 120 is co-located with base station 104, and transmitting the LPP message to the local LMF may involve using inter-process communication (IPC) technology to send the LPP message to another task or software entity.

[0066] When the local LMF 120 generates an LPP message for UE 102, it sends the LPP message to base station 104. Base station 104 includes the LPP message in a DL NAS message, includes the DL NAS message in a DL RRC message, and sends the DL RRC message to UE 102 via the radio interface. Similar to the UL RRC message discussed above, base station 104 can layer the DL RRC message at PDCP, RLC, MAC, and PHY. UE 102 receives the DL RRC message, extracts the DLNAS message from the DL RRC message, and extracts the LPP message from the DL NAS message. UE 102 then processes the LPP message according to the LPP protocol.

[0067] However, when base station 104 extracts the UL NAS message from the UL RRC message and determines that the UL NAS message does not include the LPP message, base station 104 sends the UL NAS message to AMF 112. Since it is sufficient for base station 104 to only determine whether the UL NAS message includes the LPP message, base station 104 in this embodiment does not necessarily need to determine the type of non-LPP message encapsulated in the UL NAS message.

[0068] Generally speaking, Protocol Architecture 300 supports low-latency location management functions with minimal impact on the overall architecture.

[0069] Figure 4 Another protocol architecture 400 is shown that is generally similar to protocol architecture 300, except that here the local LMF 120 and base station 104 are co-located at the same node and / or device. In this case, base station 104 similarly extracts UL NAS messages from UL RRC messages, extracts LPP messages from UL messages, and sends LPP messages to local LMF 120, for example, using an appropriate IPC mechanism.

[0070] Next, Figure 5-7C It is shown that UE 102 or base station 104 can implement according to Figure 3 and Figure 4 Several example methods for operating on the protocol architecture.

[0071] First refer to Figure 5 Method 500 begins at block 502, where base station 104 receives UL RRC messages from UE 102 via a radio interface. Figure 3 and Figure 4 As shown, UL RRC messages can be layered sequentially on PDCP, RLC, MAC, and PHY.

[0072] At block 504, base station 104 extracts the UL NAS message from the received UL RRC message. To do this, base station 104 can process the RRC header, determine the UL RRC encapsulation of the UL NAS message, and remove the header, trailer, etc., from the RRC message. More generally, base station 104 can implement any suitable message processing technique to extract the NAS message from lower-level messages. As mentioned above, base station 104 does not necessarily need to support AMF or the full NAS functionality specified by the corresponding standard (e.g., 3GPP Technical Specification 24.501). Return to Reference Figure 1Alternatively, base station 104 may include a NAS message identifier 166 for determining whether a UL NAS message includes an LPP message. In some embodiments, base station 104 may also implement functionality for generating downlink (DL) NAS messages to transmit LPP messages from local LMF 120 to UE 102, which is discussed in more detail below.

[0073] Refer again Figure 5 At block 506, base station 104 determines whether the UL NAS message includes an LPP message. In some embodiments, the UL NAS message is a dedicated message specifically defined to carry an LPP message. More specifically, the dedicated NAS message may have a specific NAS message type to identify a message type that carries or encapsulates only LPP messages (i.e., cannot carry any other type of message). The dedicated NAS message may also include a field that includes an LPP message. In this embodiment, the dedicated message (or NAS message type) indicates to base station 104 that the UL NAS message includes an LPP message. In another embodiment or scenario, the UL NAS message includes an information element (IE) indicating whether the UL NAS message includes an LPP message. For example, the UL NAS message may be a UL NAS transport, which may carry an LPP message or other higher-layer messages.

[0074] Alternatively, at base station 104 (see...) Figure 1 The RRC controller 168, operating within the system, relies on the RRC layer to determine how the base station 140 should process the received UL RRC message. The UL RRC message may include an indication of whether the UL NAS message carries an LPP message. For example, the RRC message may be a dedicated message specifically defined to carry a UL NAS message, which in turn carries an LPP message (i.e., an LPP message layered on top of the NAS). Generally similar to the dedicated NAS messages discussed above, the dedicated RRC message may have a specific RRC message type to identify a message type that carries only or encapsulates LPP messages (i.e., it cannot carry any other type of message). In this embodiment, the dedicated message (or RRC message type) indicates to the base station 104 that the RRC message includes an LPP message layered on top of the NAS.

[0075] In another implementation or scenario, the UL RRC message includes an IE indicating whether the UL RRC message is included in the LPP message layered on the NAS. For example, in this case, the UL RRC message could be ULInformationTransfer.

[0076] Refer again Figure 5When base station 104 determines that the UL NAS message does not include the LPP message, the process proceeds to block 508. Otherwise, when base station 104 determines that the UL NAS message includes the LPP message, the process proceeds to block 510.

[0077] At block 508, base station 104 sends a UL NAS message to AMF 102. For this purpose, for example, base station 104 may remove information at or below RRC layer 210 and encapsulate the UL NAS message with a protocol that supports message transmission over the NG interface. In other words, base station 104 transmits to AMF 102 at least some data (e.g., user plane data or control plane information or messages) included in the received UL RRC message.

[0078] On the other hand, at box 510, base station 104 extracts the LPP message from the UL NAS message and then sends the UL NAS message to the local LMF 120 at box 512. This depends on whether the local LMF 120 is set up in a separate node (see...). Figure 3 It is still co-located with base station 104 (see...) Figure 4 Base station 104 uses a protocol stack or an appropriate mechanism for transmitting messages within the same node to connect base station 104 to the communication link of local LMF 120.

[0079] In Figure 3 and 4 In some implementations consistent with the protocol architecture, UE 102 can be similar to Figure 2 The prior art UE operation is shown. Therefore, UE 102 can send LPP messages in the uplink direction and receive LPP messages in the downlink direction, regardless of whether base station 104... Figure 2 , 3 This can be implemented as shown in Figure 4, regardless of whether RAN 130 supports the local LCS function. However, in other implementations, UE 102 may implement additional functionality to specifically address LPP messages to the local LMF 120 or the non-local LMF / E-SMLC 114 (e.g., directly or via AMF 112).

[0080] Figure 6A One such technology is shown in the figure. LCS controller 152 (see...) Figure 1 Another suitable component of UE 102 may implement method 600 for generating LPP messages to be transmitted to a local LMF or a remote node.

[0081] Method 600 begins at box 602, where UE 102 generates an LPP message. Next, at box 610, UE 102 determines whether it should address the LPP message to a RAN-based LCS entity (e.g., local LMF 120) or a CN-based LCS entity (e.g., non-local LMF / E-SMLC 114). If the LPP message is directed to a RAN-based LCS entity, the process proceeds to box 612. Otherwise, if the LPP message is directed to a CN-based LCS entity, the process proceeds to box 622.

[0082] At block 612, UE 102 includes the LPP message in a first-type UL NAS message. For example, UE 102 may include the LPP message in a UL NAS message of a type dedicated to carrying LPP messages. UE 102 then sends the UL NAS message to base station 104 at block 614. In one implementation, UE 102 layers the UL NAS message across RRC, PDCP, RLC, MAC, and PHY.

[0083] At box 622, UE 102 includes the LPP message in a second type of UL NAS message. For example, UE 102 can include the LPP message in a UL NAS transport message, which, as mentioned above, can also be used to carry messages unrelated to LCS. At box 624, UE 102 then sends the UL NAS message to base station 104. UE 102 can similarly layer the UL NAS message across RRC, PDCP, RLC, MAC, and PHY.

[0084] Figure 6B An example method 650 is shown that base station 104 (e.g., LCS message router 162) can implement to transmit LPP messages in the downlink direction. At block 652, base station 104 receives an LPP message from either a RAN-based LCS entity or a CN-based LCS entity. Next, at block 654, base station 104 determines whether the LPP message arrived from a RAN-based LCS entity (e.g., local LMF 120). If the LPP message arrived from a RAN-based LCS entity, the process proceeds to block 662; otherwise, the process proceeds to block 672.

[0085] At block 662, base station 104 includes the LPP message in a first type of DL NAS message. For example, base station 104 may include the LPP message in a DL NAS message of a type dedicated to carrying LPP messages. At block 664, base station 104 then sends the DL NAS message to UE 102. In one implementation, base station 104 layers the DL NAS message across RRC, PDCP, RLC, MAC, and PHY.

[0086] At block 672, base station 104 includes the LPP message in a second type of DL NAS message. For example, base station 104 may include the LPP message in a DL NAS transport message, which, as mentioned above, can also be used to carry messages unrelated to LCS. At block 674, base station 104 sends the DL NAS message to UE 102. Base station 104 may similarly layer the DL NAS message at RRC, PDCP, RLC, MAC, and PHY.

[0087] Figure 6C An example method 680 is shown whereby base station 104 can implement message transmission from a local LMF and a core network in the downlink direction. At block 682, base station 104 receives a message from either a local LMF (e.g., local LMF 120) or a core network (e.g., 5GC 110). Next, at block 684, base station 104 determines whether the message arrived from the local LMF. If the message arrived from the local LMF (i.e., the message is an LPP message), the process proceeds to block 686; otherwise (i.e., the message is a DL NAS message from the core network), the process proceeds to step 692. For example, the DL NAS message could be a 5G system mobility management (5GMM) message or a 5G system session management (5GSM) message. A 5GMM message could be a registration acceptance, service acceptance, service rejection, identity request, configuration update command, authentication request, security mode command, deregistration request, notification, 5GMM status, deregistration acceptance, or DL ​​NAS transmission. In some cases, DL NAS transmissions may include LPP messages from a non-local LMF / E-SMLC 114. In other cases, DL NAS transmissions may include information other than LPP messages (e.g., short message service messages). 5GSM messages may be PDU session establishment acceptance, PDU session authentication request, PDU session modification acceptance, PDU session modification command, PDU session release request, PDU session release completion, or 5GSM status.

[0088] At block 686, base station 104 includes the message in a DL NAS message. Then, at block 688, base station 104 sends the DL NAS message to UE 102. In one implementation, base station 104 layers the DL NAS message across RRC, PDCP, RLC, MAC, and PHY. In one example, the DL NAS message may be a DL NAS transport message. In another example, the DL NAS message may be a type of DL NAS message specifically designed to carry LPP messages from a local LMF.

[0089] At box 692, base station 104 sends a message to UE 102. Base station 104 can similarly layer messages on RRC, PDCP, RLC, MAC, and PHY.

[0090] As Figure 6A Another alternative to this method, a suitable component of the LCS controller 152 or UE 102 can be used to implement it. Figure 7A Method 700 is used to generate LPP messages for transmission to a local LMF or a remote node. According to method 700, UE 102 instructs base station 104 where the LPP message should be sent, similar to method 600. However, unlike method 600, method 700 selects the type of UL RRC message instead of the type of UL NAS message.

[0091] Specifically, method 700 begins at box 702, where UE 702 generates an LPP message. Similar to the determination at box 610 discussed above, UE 102 determines at box 710 whether it should address the LPP message to a RAN-based LCS entity (e.g., local LMF 120) or a CN-based LCS entity (e.g., non-local LMF / E-SMLC 114). If the LPP message is addressed to a RAN-based LCS entity, the process proceeds to box 712. Otherwise, if the LPP message is addressed to a CN-based LCS entity, the process proceeds to box 722.

[0092] At box 712, UE 102 includes the LPP message in a first-type UL RRC message. For example, UE 102 can include the LPP message in a UL RRC message of a type dedicated to carrying LPP messages. UE 102 then sends the UL RRC message to base station 104 at box 714. UE 102 can layer the UL RRC message at PDCP, RLC, MAC, and PHY.

[0093] At box 722, UE 102 includes the LPP message in a second type of UL message. For example, UE 102 can include the LPP message in a ULInformationTransfer message, which can also be used to carry messages unrelated to LCS. At box 724, UE 102 then sends the UL NAS message to base station 104. UE 102 can layer the UL RRC message at PDCP, RLC, MAC, and PHY.

[0094] Figure 7B An example method 750 is shown where base station 104 (e.g., LCS message router 162) can implement the transmission of LPP messages in the downlink direction using different RRC messages. At block 752, base station 104 receives an LPP message from an LCS entity, which may be a local LMF 120 or another suitable RAN-based LCS entity, or a non-local LMF / E-SMLC 114 or another suitable CN-based LCS entity. If the LPP message arrives from a RAN-based LCS entity such as a local LMF 120 (block 760), the process proceeds to block 762. Otherwise, if the LPP message arrives from a CN-based LCS entity, the process proceeds to block 772.

[0095] At block 762, base station 104 includes the LPP message in a first-type DL RRC message. For example, base station 104 may include the LPP message in a DL RRC message of a type dedicated to carrying LPP messages. Then, at block 764, base station 104 sends the DL RRC message to UE 102. Base station 104 may layer the DL RRC message at PDCP, RLC, MAC, and PHY.

[0096] At block 772, base station 104 includes the LPP message in a second type of DL RRC message. For example, base station 104 may include the LPP message in a DLInformationTransfer message, which can also be used to carry messages unrelated to LCS. At block 774, base station 104 sends the DL RRC message to UE 102. For example, base station 104 may layer the DL RRC message at PDCP, RLC, MAC, and PHY.

[0097] Figure 7CAn example method 780 is shown whereby base station 104 can implement message transmission from a local LMF and a core network in the downlink direction. At block 782, base station 104 receives a message from either the local LMF (e.g., local LMF 120) or the core network (e.g., 5GC 110). Next, at block 784, base station 104 determines whether the message arrived from the local LMF. If the LPP message arrived from the local LMF (i.e., the message is an LPP message), the process proceeds to block 786. Otherwise (i.e., the message is a DL NAS message from the core network), the process proceeds to block 792. A DL NAS message is as follows... Figure 6C As shown.

[0098] At block 786, base station 104 includes the LPP message in a first-type DL RRC message. Then, at block 788, base station 104 sends the first DL RRC message to UE 102. Base station 104 may layer the DL RRC message at PDCP, RLC, MAC, and PHY. In some implementations, the first DL RRC message may be a DL RRC message of a type specifically designed to carry LPP messages from a local LMF. As a result, UE 102 determines (or learns) that the first DL RRC message carries an LPP message because the received DL RRC message is a first-type DL RRC message. UE 102 then extracts the LPP message from the DL RRC message and processes the LPP message according to the LPP protocol. In other implementations, the first DL RRC message may be a DL RRC message (e.g., DLInfoformationTransfer) that includes a specific indicator (i.e., an RRC field or RRC IE) indicating that the LPP message is included in the DL RRC message. As a result, UE 102 determines the first DL RRC message carrying the LPP message based on a specific indicator, extracts the LPP message from the DL RRC message, and processes the LPP message according to the LPP protocol.

[0099] At block 792, base station 104 includes the message (i.e., the DL NAS message) in a second type of DL RRC message. At block 794, base station 104 sends the second type of DL RRC message to UE 102. For example, base station 104 may layer the second DL RRC message on PDCP, RLC, MAC, and PHY. In some implementations, the second DL RRC message may be a type of DL RRC message specifically designed to carry DL NAS messages. For example, the DL RRC message is a DLInformationTransfer message. In this case, the second DL RRC message does not have the same specific indicator as the first DL RRC message. As a result, UE 102 determines (or learns) that the second DL RRC message carries a DL NAS message because the second DL RRC message is a type of DL RRC message specifically designed to carry DL NAS messages. UE 102 then processes the DL NAS message according to the NAS protocol.

[0100] Next, Figure 8 Another protocol architecture 800 is shown, in which UE 102 can layer LPP messages directly on RRC layer 214 without relying on the NAS layer, and base station 104 can correspondingly transmit such messages in both the uplink and downlink directions. Therefore, base station 104 can provide low-latency location management functionality without implementing the NAS protocol.

[0101] Specifically, UE 102 generates LPP messages according to this protocol architecture and directly layers the LPP messages at RRC layer 210. The resulting UL RRC message therefore has no intermediate layer (e.g., NAS layer 212). That is, the UL RRC message directly encapsulates the LPP message. Then, UE 102 sends the UL RRC message to base station 104. Figure 8 As shown, UL 102 layers the UL RRC message at PDCP, RLC, MAC, and PHY. When base station 104 receives the UL RRC message, it extracts the LPP message from it. Then, base station 104 sends the LPP message to the local LMF 120, which processes the LPP message.

[0102] In the downlink direction, the local LMF 120 generates an LPP message and sends it to the base station 104. The base station 104 layers the LPP message on top of the DL RRC message and sends the DL RRC message to the UE 102 via the radio interface. The base station 104 layers the DL RRC message at PDCP, RLC, MAC, and PHY. After the UE 102 receives the DL RRC message, it processes the DL RRC message according to the RRC layer 210 and extracts the LPP message.

[0103] However, when UE 102 layers the NAS message on the RRC, base station 104 receives the UL RRC message, determines that the UL RRC message includes the UL NAS message, and sends the UL NAS message to AMF 112 of CN 110. When base station 104 receives the DLNAS message from AMF 112, base station 104 layers the DL NAS message on the RRC and sends the resulting DL RRC message to UE 102.

[0104] exist Figure 8 In the example, the local LMF 120 is in RAN 130 but operates in a node separate from base station 104. Figure 9 In another example protocol architecture 900 depicted, the local LMF 120 and base station 104 are co-located. Therefore, base station 104 uses any suitable IPC technology to send LPP messages to the local LMF 120 and receive LPP messages from the local LMF 120.

[0105] When according to Figure 8 and Figure 9 In some implementations, UE 102 supports not only layering LPP directly on the RRC, but also layering LPP on the RRC through an intermediate layer (e.g., NAS layer 212). In these implementations, UE 102 can... Figure 2 -7 and Figure 8-9 The protocol architecture allows UE 102 to operate when RAN-based LCS is available, CN-based LCS is available, or both RAN-based and CN-based LCS are available. In the latter case, UE 102 can determine whether it should use RAN-based or CN-based LCS based on its configuration, the type of LCS procedure it wishes to perform, and indications of which LCS appears to provide more reliable and / or faster information.

[0106] Figure 10AThis is a block diagram of an example protocol stack 1000 that UE 102 can implement to support both RAN-based LCS and CN-based LCS. In this implementation, UE 102 implements LPP module (or task) 214A, which layers outbound LPP messages on NAS and extracts inbound LPP messages from DL NAS messages; and LPP module 214B, which directly layers outbound LPP messages on RRC and extracts inbound LPP messages from DL RRC messages. LPP module 214A can communicate with a non-local LMF / E-SMLC 114, and LPP module 214B can communicate with a local LMF 120. In this implementation, each of LPP modules 214A and 214B can operate independently of each other using a separate context. In another implementation, LPP modules 214A and 214B can cooperate to perform certain LCS procedures.

[0107] In some implementations, LPP modules 214A and 214B support the same set of LPP functions. In other implementations, LPP modules 214A and 214B support different sets of functions. Furthermore, some functions supported by LPP modules 214A and 214B are implemented differently to account for the differences between RAN-based LCSs and CN-based LCSs.

[0108] Figure 10B This is a block diagram of another example protocol stack 1010 that UE 102 can implement to support both RAN-based LCS and CN-based LCS. In this implementation, UE 102 implements a single LPP module 214 that layers some outbound LPP messages on NAS and extracts some inbound LPP messages from DL NAS messages, and layers other outbound LPP messages directly on RRC and extracts other inbound LPP messages from DL RRC messages.

[0109] Next, Figure 11 The base station 104 is shown to be able to implement according to Figure 8 and Figure 9 This is an example method that operates on the protocol architecture and sends LCS-related messages to a local LCS entity (e.g., local LMF 120) or a remote LCS entity (e.g., non-local LMF / E-SMLC 114). Therefore, according to method 1100, base station 104 transmits location protocol messages for processing at a RAN-based LCS or a CN-based LCS.

[0110] Method 1100 begins at block 1102, where base station 104 receives UL RRC messages from UE 102 via a radio interface. (See diagram below.) Figure 3 and Figure 4As shown, UL RRC messages can be layered at PDCP, RLC, MAC, and PHY. Next, at box 1104, base station 104 determines whether the UL RRC message includes LPP messages that are directly layered at RRC or UL NAS messages. For simplicity, Figure 11 The discussion refers to LPP messages that are layered directly on the RRC as "LPP messages". When the UL RRC message includes an LPP message, the process proceeds to box 1106. Otherwise, when the UL RRC message does not include LPP messages that are layered directly on the RRC, the process proceeds to box 1108. At box 1106, base station 104 sends the LPP message to local LMF 120. At box 1108, base station 104 sends the UL NAS message to AMF 112.

[0111] In some scenarios, UL NAS messages may include LPP messages from UE 102 addressing to non-local LCS entities such as LMF / E-SMLC 114. For example, a UL NAS message may be UL NAS transport information. Base station 104 does not... Figure 11 In one scenario, LPP messages are processed because AMF 112 extracts LPP messages from UL NAS messages and forwards them to the non-local LMF / E-SMLC 114. In another scenario, UL NAS messages do not include LPP messages. For example, UL NAS messages can be 5GMM messages or 5GSM messages other than UL NAS transmissions. 5GMM messages can be registration requests, registration complete, service requests, configuration update complete, identity responses, authentication responses, security mode rejections, deregistration requests, notification responses, security mode complete, 5GMM status, or deregistration accepted. 5GSM messages can be PDU session establishment requests, PDU session authentication complete, PDU session modification requests, PDU session modification complete, PDU session modification command rejection, PDU session release requests, PDU session release complete, or 5GSM status.

[0112] In some implementations, base station 104 determines which signaling radio bearer (SRB) the UL RRC message is associated with (i.e., on which SRB the UL RRC message arrives at base station 104). Generally, the UE and base station utilize several types of SRBs, referred to as SRB1, SRB2, SRB3, etc. Base station 104 can determine whether the UL RRC message is associated with SRB1 or SRB2; for example, if the UL RRC message is associated with SRB1, the appropriate RRC procedure is performed, while if the UL RRC message is associated with SRB2, the appropriate procedure is performed. Figure 11In another implementation, base station 104 does not consider the SRBs arriving on it for the UL RRC message. When performing method 1100, if base station 104 determines that the UL RRC message does not include either an LPP message or a UL NAS message, base station 104 performs an appropriate RRC procedure to process the UL RRC message. As a more specific example, the UL RRC message may be a MeasurementReport or a UEAssistanceInformation.

[0113] Similar to the examples discussed above, the UL RRC message processed by base station 104 according to method 1100 can be a ULInformationTransfer message or a dedicated UL RRC message specifically defined to carry LPP messages. Similarly, in the downlink direction, base station 104 can use DL RRC messages, which are either DLInformationTransfer messages or DL ​​RRC messages specifically designed to carry LPP messages.

[0114] Similar to the example above, in base station 104 (see...) Figure 1 The RRC controller 168 operating in the RRC layer can rely on the RRC layer to determine how the base station 140 should process the received UL RRC message. The UL RRC message may include an indication of whether the UL RRC message carries an LPP message. For example, the RRC message may be a dedicated message specifically and directly defined as carrying an LPP message (i.e., an LPP message layered on top of the RRC). The dedicated message may be a specific RRC message type message. This dedicated message may not be used to carry a UL NAS message. In this embodiment, the dedicated message (or RRC message type) indicates to the base station 104 that the RRC message includes an LPP message layered on top of the RRC. When the base station 104 determines that the RRC message carries an LPP message over the RRC, the base station 104 transmits the LPP message to the local LMF 120. If the base station determines that the UL RRC message is not a dedicated message and includes a UL NAS message, the base station extracts the UL NAS message from the UL RRC message and sends the UL NAS message to the AMF 112. In one case, the UL NAS message may include an LPP message as described above. In another scenario, the UL NAS message may exclude the LPP message and include the 5GMM message or 5GSM message as described above.

[0115] In another implementation, the UL RRC message includes a specific first field (e.g., a field of a first type) containing the LPP message and / or another second field (e.g., a field of a second type) containing the UL NAS message. When base station 104 determines that the UL RRC message includes a field of the first type, base station 104 extracts the LPP message from the UL RRC message. Then, base station 104 sends the LPP message to local LMF 120. When base station 104 determines that the UL RRC message includes a field of the second type, base station 104 extracts the UL NAS message from the UL RRC message and sends the UL NAS message to AMF 112.

[0116] In addition, the UL RRC message may include information in the form of IE, field identifier, IE identifier, etc., indicating whether the UL RRC message includes an LPP message. When base station 104 determines that the UL RRC message includes this information, base station 104 extracts the LPP message from the UL RRC message and sends the LPP message to the local LMF 120. When base station 104 determines that the UL RRC message does not include this information, base station 104 extracts the UL NAS message from the UL RRC message and sends the UL NAS message to the AMF 112. Finally, when the UL RRC message does not indicate that the UL RRC message includes an LPP message or a UL NAS message that is directly layered on the RRC, the base station processes the UL RRC message locally.

[0117] In some implementations, RAN 130 and / or CN 110 provide indications as to whether the wireless communication network supports RAN-based LCS, CN-based LCS, or both. UE 102 can use these indications to select the appropriate procedure, format outbound LPP messages, and receive inbound LPP messages.

[0118] Figure 12A and 12B Example scenarios are shown in which UE 102 determines which LCS entity UE 102 should send LPP messages to and in what format. These scenarios can occur sequentially or independently. For clarity, the following discussion refers to the sequence of LPP messages 1, 2, 3, and 4, where messages 1 and 3 are transmitted from UE 102 to the corresponding LCS entity, while messages 2 and 4 are transmitted from the LCS entity to UE 102.

[0119] First refer to Figure 12A According to scenario 200, base station 104 provides RAN 1202 130 with first indication of RAN-based LCS support. More specifically, base station 104 can determine whether it is connected to a local LMF or whether it is incorporated into a local LMF with a co-located instance. Base station 104 can be in cell 140 (see Figure 1In one embodiment, base station 104 may send dedicated RRC messages to UE 102, such as RRC establishment, RRC reconfiguration, RRC recovery, or RRC reconstruction. In yet another embodiment, UE 102 may receive broadcast or UE-specific instructions from another base station, such as base station 106.

[0120] After receiving the first instruction, UE 102 determines 1210 to perform a procedure using RAN-based LCS. Based on the first instruction, UE 102 generates a UL RRC message including a first LPP message layered directly on the RRC (without an intermediate layer such as NAS), and transmits the UL RRC message 1220 to base station 104. The first LPP message may be, for example, LPP request assistance data. Base station 104 extracts the first LPP message 1222 from the UL RRC message and sends the first LPP message 1224 to local LMF 120. Local LMF 120 then sends a second LPP message 1230 to base station 104. The second LPP message may be, for example, LPP provide assistance data. Base station 104 then layers the second LPP message directly on the DL RRC message 1232 and sends the DL RRC message 1234 to UE 102 via the radio interface.

[0121] When UE 102 does not receive the first indication (event 1202), or when UE 102 receives the second indication that CN 110 supports a CN-based LCS, UE 102 may perform the procedure of using a CN-based LCS. In some implementations, when UE 102 receives two indications (i.e., RAN-based LCS and CN-based LCS are available), UE 102 selects between the RAN-based LCS and the CN-based LCS based on the relative priorities of these services as described above. In still other implementations, UE 102 assumes that a CN-based LCS is available and does not expect the corresponding indication.

[0122] exist Figure 12B In the illustrated implementation, AMF 112 or another entity operating in CN 110 provides an indication (second indication) that 1242 supports CN-based LCS, and UE 102 determines that 1250 performs a procedure for using CN-based LCS. AMF 112 may send the second indication in a DL NAS message such as registration acceptance in response to a registration request received from the UE via base station 104 or base station 106.

[0123] Based on the second instruction, UE 102 generates a UL NAS message that includes a third LPP message layered on the NAS, includes the UL NAS in a UL RRC message, and sends the UL RRC message including the UL NAS message to base station 104 at 1260. The third LPP message may be, for example, an LPP request for auxiliary data. Base station 104 extracts the UL NAS message 1262 from the RRC message and sends the UL NAS message including the third LPP message 1264 to AMF 112. AMF 112 extracts the LPP message 1266 from the UL NAS message and sends the third LPP message 1268 to non-local LMF / E-SMLC 114.

[0124] In response, the non-local LMF / E-SMLC 114 sends a fourth LPP message 1270 to the AMF 112. The AMF 112 includes (encapsulates) the fourth LPP message 1272 in a DL NAS message. The AMF sends the DL NAS message 1274 to the base station 104, and then the base station 104 includes the DL NAS message 1276 in a DL RRC message and sends the DL RRC message 1278 to the UE 102 via the radio interface.

[0125] When UE 102 receives both the first and second indications, UE 102 can select to execute either a RAN-based LCS or a CN-based LCS according to its configuration. One example configuration of UE 102 assigns a higher priority to the RAN-based LCS than the CN-based LCS. As another example, the UE's configuration may specify that UE 102 should use the RAN-based LCS when performing a procedure related to a specific (first) LCS service, and should use the CN-based LCS when performing a procedure related to another (second) service. In some implementations, the UE 102 manufacturer specifies these parameters, and UE 102 retrieves these parameters from persistent memory. In another implementation, the USIM stores this configuration. In yet another implementation, UE 102 receives this configuration from a server in the CN 110 or the operator's network.

[0126] Figure 13This is a flowchart of an example method 1300, which can be implemented in UE 102, for determining whether to execute a RAN-based LCS or a CN-based LCS. According to this example method, the RAN-based LCS has a higher priority than the CN-based LCS. Therefore, when both options are available, UE 102 selects the RAN-based LCS. However, in other implementations or scenarios, the CN-based LCS may have a higher priority than the RAN-based LCS, or the CN-based LCS and the RAN-based LCS may have the same priority (and UE 102 may, for example, select between these services based on the timing of corresponding indications).

[0127] Method 1300 begins at block 1302, where UE 102 determines whether it has received an indication from RAN 130 that it supports RAN-based LCS. If UE 102 has received such an indication, the process proceeds to block 1304, and UE 102 performs the procedure for using RAN-based LCS. Otherwise, if UE 102 has not received the indication, the process proceeds to block 1306.

[0128] At block 1306, UE 102 determines whether it has received an indication from CN 110 that it supports CN-based LCS. If UE 102 has received such an indication, the process proceeds to block 1308, and UE 102 performs the procedure for using CN-based LCS. Otherwise, if UE 102 has not received the indication, the process proceeds to block 1310, where UE 102 chooses not to perform the LCS procedure.

[0129] Next, Figure 14 An example scenario 1400 is shown in which UE 102 determines how it should layer LPP messages based on the encapsulation technology in the downlink direction.

[0130] Specifically, base station 104 receives a first LPP message 1404 from local LMF 120 and encapsulates the first LPP message 1406 in a DL RRC message without an intermediate layer, i.e., directly layering the first LPP message on the RRC. The first message may be, for example, an LPP request for capability. UE 102 receives a DL RRC message 1408 from base station 104. Because the first LPP message is directly layered on the RRC, UE 102 determines that UE 102 should directly layer a second LPP on the RRC, which may be in response to the first LPP (e.g., LPP providing capability). UE 102 may also determine that the first LPP message arrived from a RAN-based LCS entity rather than a CN-based LCS entity based on the direct layering of the first LPP message on the RRC.

[0131] UE 102 generates a second LPP message 1410 and layers the second LPP message directly on the RRC in the UL RRC message. Then, UE 102 sends the UL RRC message 1440 to base station 104. Base station 104 extracts the second LPP message 1442 and sends the second LPP message 1444 to local LMF 120.

[0132] Subsequently, the non-local LMF / E-SMLC 114 sends a third LPP message to AMF 112 at 1450. AMF 112 then layers the third LPP message on the NAS at 1452 to generate a DL NAS message. The third LPP message may be, for example, an LPP request capability. AMF 112 then sends a DL NAS message including the third LPP message to base station 104 at 1454. Base station 104 then layers the DL NAS message on the RRC at 1456 to generate a DL RRC message. Base station 104 then sends the DL RRC message to UE 102 via the radio interface at 1458.

[0133] After UE 102 receives the DL RRC message 1458, UE 102 determines, based on the encapsulation of the third LPP message 1460, that it should respond with a fourth LPP message layered on the NAS rather than directly on the RRC. The fourth LPP message could be, for example, an LPP provisioning capability. UE 102 sends the fourth LPP message layered on the NAS to base station 104 in the UL RRC message 1462. Base station 104 extracts the NAS message 1464 from the UL RRC message and sends the UL NAS message 1466 to AMF 112. AMF 112 then extracts the fourth LPP message 1466 from the UL NAS message and sends the fourth LPP message 1469 to the non-local LMF / E-SMLC 114.

[0134] Therefore, in Figure 14 In the scenario where the LPP message from the LCS entity is directly layered on the RRC, UE 102 responds to the LPP message from the LCS entity with the LPP message directly layered on the RRC. And if the LPP message from the LCS entity is directly layered on the NAS, UE 102 responds to the LPP message from the LCS entity with the LPP message directly layered on the NAS.

[0135] To further clarify, several example positioning techniques will be discussed below.

[0136] first, Figure 15A positioning procedure 1500 involving UE 102 and RAN 130 is illustrated, with base station 104 and local LMF 120 operating within RAN 130. In some embodiments, RAN 130 includes another base station (e.g., base station 106). Figure 15 In the example, UE 102 can therefore communicate with the local LMF 120 via any suitable base station or one or more base stations. Furthermore, although... Figure 15 The discussion involves the local LMF 120, but in other implementations, other components such as the Location Management Component (LMC) can provide RAN-based LCS. The LCS service in scenario 1500 is RAN-based, therefore UE 102 does not need to exchange LPP messages with the core network.

[0137] In this scenario, the local LMF 120 is initially unaware of the LPP / LCS capabilities of the UE 102. To determine these capabilities, the local LMF 120 sends an LPP capability request message 1502 to the UE via base station 104, and base station 104 transmits this request in a DL RRC message 1504. In response, the UE 102 transmits an LPP capability provision response 1506 to base station 104, and base station 104 then sends this response 1508 to the local LMF 120.

[0138] Local LMF 120 sends an LPP Request Location Information message to UE 102 via base station 104 at 1510 (event 1512) to request positioning results from UE 102. When UE 102 needs auxiliary information for positioning, UE 102 sends an LPP Request Location Information message to local LMF 120 via base station 104 at 1520 (event 1522). In response, local LMF 120 sends an LPP Provide Assistance Data message including auxiliary information to UE 102 at 1524 (again via base station 104; event 1526). UE 102 performs positioning at 1530 using the auxiliary information (if it has been provided), stored auxiliary information, or without using any auxiliary information (i.e., UE 102 may perform positioning in some cases without any auxiliary information from local LMF 120). UE 102 generates a positioning result of 1532 and sends an LPP location information message (1534, event 1536) including the positioning result (e.g., location measurement data and / or location estimation) to local LMF 120 via base station 104.

[0139] In various scenarios, UE 102, including the local LMF 120 (or LMC) and one or more base stations (e.g., base stations 104, 106), RAN 130 and CN 110 can exchange LPP messages for location reports triggered by events such as Mobile Device-Initiated Location Request (MO-LR), Mobile Device-Terminated Location Request (MT-LR), Network-Initiated Location Request (NI-LR), or events as described below. Figure 16-19 For convenience, RAN 130 is shown as separate from local LMF 120; however, as mentioned above, local LMF 120 can be directly connected to base station 104 and provide RAN-based LCS.

[0140] like Figure 16 As shown, UE 102 sends an MO-LR request message 1602 to CN 110 via RAN 130 (event 1604) to perform the MO-LR procedure. CN 110, in response to the MO-LR request message, sends a location request message 1610 to local LMF 120. In response, local LMF 120 then sends an LPP request location information message 1612 to UE 102 via RAN 130. In some cases, local LMF 120 may send an LPP request capability message in response to the location request message and receive an LPP provision capability message in response before sending the LPP request location information message 1614 as described above. UE 102 performs positioning 1620 to obtain positioning results (e.g., location measurement data and / or location estimation) and generates an LPP provision location information message 1622 including the positioning results in response to the LPP request location information message. In response to the LPP Request for Location Information message, UE 102 sends an LPP Provide Location Information message 1624 to local LMF 120 via RAN 130 (event 1626). In some cases, UE 102 may send an LPP Request for Assistance data message to local LMF 120 and receive the LPP Provide Assistance data message before performing positioning 1620 as described above.

[0141] In response to the LPP providing location information message, the local LMF 120 generates a location response message. In some implementations, the local LMF 120 includes the location result in the location response message. In other implementations, the local LMF 120 generates (i.e., derives or calculates) location information based on the location result. The local LMF 120 includes the location information in the location response message and sends the location response message 1628 to CN 110. The process that begins with CN 110 sending a location request 1610 to the local LMF 120 and ends with CN 110 receiving a location response 1628 can be referred to as the location acquisition process 1630.

[0142] CN 110 generates an MO-LR response message in response to the location response message and sends the MO-LR response message to UE 102 via RAN 130 at 1640 (event 1642). CN 110 may include the positioning result or location information in the MO-LR response message.

[0143] Based on the techniques discussed above, UE 102 can encapsulate the MO-LR request message in a UL NAS message and then encapsulate the UL NAS message in a UL RRC message. UE 102 can then send the UL RRC message to the RAN. RAN 130 extracts the UL NAS message from the UL RRC message and sends it to CN 110. CN 110 can encapsulate the MO-LR response message in a DL NAS message and send it to the RAN. RAN 130 can encapsulate the DL NAS message in a DL RRC message and send it to UE 102. UE 102 can then extract the DL NAS message from the DL RRC message and extract the MO-LR response message from the DL NAS message.

[0144] exist Figure 17 In this scenario, CN 110 sends a location call message (1706) for the MT-LR procedure to UE 102 via RAN 130 (event 1708). UE 102, RAN 130, local LMF 120, and CN 110 then perform actions similar to those described in the reference above. Figure 16 The location acquisition process discussed in step 1630 is similar to the location acquisition process in step 1730. Figure 16 In this scenario, UE 102, RAN 130, local LMF 120 and CN 110 can use the LPP encapsulation and transmission technology disclosed herein.

[0145] exist Figure 18 In this scenario, UE 102 establishes an emergency call 1802 with CN 110 via RAN 130. UE 102, RAN 130, local LMF 120, and CN 110 then perform actions similar to those described in the reference above. Figure 16 The location acquisition process discussed in step 1630 is similar to the location acquisition process in step 1830. Figure 16 In this scenario, UE 102, RAN 130, local LMF 120 and CN 110 can use the LPP encapsulation and transmission technology disclosed herein.

[0146] Figure 19An example scenario is shown in which CN 110 sends a periodic trigger event call 1902 message to UE 102 via RAN 130 (Event 1904). UE 102 sends a periodic trigger event call acknowledgment 1906 to CN 110 via RAN 130 (Event 1908). When UE 102 detects an appropriate event 1910, UE 102 sends an LCSMO-LR call message 1912 to CN 110 via RAN 130 (Event 1914). UE 102, RAN 130, local LMF 120, and CN 110 then perform actions similar to those described in the reference above. Figure 16 The location acquisition process discussed in step 1630 is similar to the location acquisition process in step 1930. Figure 16 In this scenario, UE 102, RAN 130, local LMF 120, and CN 110 can use the LPP encapsulation and transmission technology disclosed herein. CN 110 then generates an MO-LR return result message and sends it to UE 102 via RAN 130 at event 1940 (event 1942). CN 110 may include the positioning result or location information in the MO-LR return result message.

[0147] According to the technology disclosed herein, UE 102 can encapsulate the MO-LR call message in a UL NAS message and encapsulate the UL NAS message in a UL RRC message. Then, UE 102 sends the UL RRC message to RAN 130. RAN 130 extracts the UL NAS message from the UL RRC message and sends the UL NAS message to CN 110. CN 110 can encapsulate the MO-LR return result message in a DL NAS message and send the DL RRC message to RAN 130. RAN 130 can encapsulate the DL NAS message in a DLRRC message and send the DL RRC message to UE 102. UE 102 can then extract the DL NAS message from the DL RRC message and extract the MO-LR return result message from the DL NAS message.

[0148] Next, refer to Figure 20-22 Consider several example methods that can be implemented by base station 104 and UE 102.

[0149] first, Figure 20 An example method 2000 for transmitting uplink location messages to a local LCS entity is shown, which can be implemented in base station 104 or another suitable base station. The method begins at block 2002, where base station 104 receives a UL message (e.g., Figure 5 Event 504 Figure 11 (Event 1102).

[0150] At frame 2004, base station 104 determines whether the UL message includes a location protocol message. Figure 5 Event 506). If base station 104 determines that the UL message includes a location protocol message, the process proceeds to block 2010, where base station 104 transmits the location protocol message to the local entity implementing the location service (e.g., local LMF 120). Figure 5 Event 512 Figure 11 Event 1106). Otherwise, when base station 104 determines that the UL message does not include the positioning protocol message, the process proceeds to box 2012, where base station 104 transmits at least some of the data in the UL message to a remote node (e.g., AMF 112). Figure 5 Event 508 Figure 5 (1108).

[0151] Figure 21 An example method 2100 for sending location protocol messages to local or more LCS entities via a base station is shown, which can be implemented in UE 102 or another suitable UE. At block 2102, UE 102 generates location protocol messages (e.g., LPP messages, NRPP messages) (e.g., ... Figure 6A Event 602 Figure 7A Event 702). Then, UE 102 determines 2104 whether UE 102 should address the location protocol message to the RAN node (e.g., LMF 120) or the CN node (e.g., AMF 112) (e.g., event 702). Figure 6A Event 610 Figure 7A Event 710). When UE 102 determines that it should address the location protocol message to the local node, UE 102 includes the location protocol message in a first lower-layer message (e.g., a first-type UL NAS message, a first-type RRC message in which the location message is layered on the NAS, an RRC message in which the location protocol message is layered directly on the RRC, etc.) at box 2110. Figure 6A Event 612 Figure 7A (Event 712).

[0152] Otherwise, when UE 102 determines that it should address the location protocol message to the CN node, the process proceeds to block 2112, where UE 102 includes the location protocol message in a second lower-layer message (e.g., a second type of UL NAS message, a second type of RRC message where the location message is layered on the NAS, etc.). Figure 6A Event 622 Figure 7A Event 722). Next, at box 2120, UE 102 sends the first or second lower-layer message to base station 104 ( Figure 6A Event 614 or 624 Figure 7A Event 714 or 724).

[0153] Figure 22 This is a flowchart of another example method for sending location protocol messages to local or more LCS entities via a base station, which can be implemented in UE 102 or another suitable UE.

[0154] At box 2202, UE 102 generates a location protocol message, such as an LPP message or an NRPP message. Figure 6A Event 602 Figure 7A Event 702). Next, at box 2204, UE 102 generates a UL RRC message, in which the positioning protocol message is directly layered on the RRC ( Figure 6A Event 612 Figure 7A Event 712). At box 2206, UE 102 transmits the UL RRC message to base station 104 ( Figure 6A Event 614 Figure 7A (Event 714).

[0155] Referring broadly to the examples above, the UL RRC message used by UE 102 to transmit LPP messages to a local LCS entity or a remote LCS entity can be a UL InformationTransfer message or a UL RRC message specifically defined to encapsulate LPP messages. Furthermore, the UL NAS message used by UE 102 to transmit LPP messages can be a UL NAS transmission message or a UL NAS message specifically defined to encapsulate LPP information. The DL RRC message used by base station 104 can be a DL InformationTransfer message or a DL RRC message specifically defined to encapsulate LPP information. Additionally, the DL NAS message used by base station 104 can be a DL NAS transmission message or a DL NAS message specifically defined to encapsulate LPP information.

[0156] In some cases, UE 102 may use one type of UL RRC message to transmit LPP messages layered directly on RRC and another type of UL RRC message to transmit NAS messages. In other cases, UE 102 uses the same type of UL RRC message in both cases. Similarly, base station 104 may use the same or different types of DL RRC messages to transmit LPP messages layered directly on RRC or to transmit NAS messages.

[0157] Referring further to the above examples, in some implementations, UE 102 and base station 104 can directly layer LPP messages and / or NAS messages on PDCP layer 208 without using RRC layer 210 (see...). Figure 2-4 Therefore, in some implementations, UE 102 and base station 104 can directly layer LPP messages on PDCP without using the RRC layer or NAS layer, or layer the NAS layer on PDCP without using the RRC layer.

[0158] Furthermore, UE 102 and base station 104 can implement protocols specifically defined for transmitting LPP, NRPP, or other location protocol messages. For example, UE 102 and base station 104 can layer messages of this protocol on RRC or PDCP. In some cases, UE 102 and base station 104 can use this protocol to transmit RAN-based LCS-related messages and use NAS to transmit CN-based LCS-related location protocol messages.

[0159] The following additional considerations apply to the foregoing discussion.

[0160] User equipment (e.g., UE 102) in which the technologies of this disclosure can be implemented can be any suitable device capable of wireless communication, such as a smartphone, tablet computer, laptop computer, mobile game console, point-of-sale (POS) terminal, health monitoring device, drone, camera, media streaming dongle or other personal media device, wearable device such as a smartwatch, wireless hotspot, femtocell, or broadband router. Furthermore, in some cases, the user equipment can be embedded with electronic systems, such as a head unit in a vehicle or an advanced driver assistance system (ADAS). Further still, the user equipment can operate as an Internet of Things (IoT) device or a mobile internet device (MID). Depending on the type, the user equipment may include one or more general-purpose processors, computer-readable storage, a user interface, one or more network interfaces, one or more sensors, etc.

[0161] Certain embodiments described in this disclosure are included as comprising logic or multiple components or modules. A module may be a software module (e.g., code or machine-readable instructions stored on a non-transitory machine-readable medium) or a hardware module. A hardware module is a tangible unit capable of performing a particular operation and may be configured or arranged in a particular manner. A hardware module may include permanently configured dedicated circuitry or logic (e.g., as a dedicated processor, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also include programmable logic or circuitry (e.g., contained within a general-purpose processor or other programmable processor) temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

[0162] When implemented in software, these technologies can be provided as part of an operating system, a library used by multiple applications, or a specific software application. This software can be executed by one or more general-purpose processors or one or more dedicated processors.

[0163] Upon reading this disclosure, those skilled in the art will understand additional and alternative structural and functional designs for restoring RRC connections using the principles disclosed herein. Therefore, while specific embodiments and applications have been shown and described, it should be understood that the disclosed embodiments are not limited to the precise structures and components disclosed herein. Various modifications, alterations, and variations that will be apparent to those skilled in the art may be made to the arrangement, operation, and details of the methods and apparatus disclosed herein without departing from the spirit and scope defined in the appended claims.

Claims

1. A method for supporting location services, the method comprising, at a base station: Receive uplink UL radio resource control (RRC) messages from user equipment (UE); Determine whether the UL message includes a location protocol message associated with a location protocol used to exchange information related to location services, and whether the location protocol message is directly layered on RRC without an intermediate protocol layer; In a first case, in response to determining that the UL message includes the location protocol message, the location protocol message is sent to the local entity implementing the location service in the radio access network RAN; and In the second case, in response to determining that the UL message does not include any location protocol messages, at least some of the data included in the UL message is sent to the core network.

2. The method according to claim 1, wherein, The location protocol message is an uplink location protocol message, and the method further includes: Receive downlink DL positioning protocol messages from the local entity; and The DL positioning protocol message is sent to the UE.

3. The method according to claim 1, further comprising: Receive DL positioning protocol messages from the local entity; Sending the DL positioning protocol message in a DL message includes layering the DL positioning protocol message directly on top of the protocol layer used to control radio resources, without any intermediate protocol layer.

4. The method according to claim 1, wherein: The uplink message is a first uplink message associated with a protocol for controlling radio resources, and the location protocol message is a first location protocol message that is layered directly on the protocol for controlling radio resources without any intermediate protocol layer. The method further includes: Receive a second uplink message associated with a protocol for controlling radio resources, the second uplink message including a second positioning protocol message layered on the NAS.

5. The method according to claim 4, further comprising: The second location protocol message is sent to a remote node in the core network.

6. The method according to claim 1, further comprising: Receive a first DL positioning protocol message from the local entity; and Include the first DL positioning protocol message in the DL Radio Resource Control (RRC) message.

7. The method according to claim 6, further comprising: Receive a second DL positioning protocol message from the remote node; and Include the second DL positioning protocol message in the DL NAS message.

8. The method of claim 1, further comprising, before receiving the UL message including the positioning protocol message: Send the UE an indication that the location service is available on the local entity.

9. The method according to claim 8, wherein, Sending the instruction includes broadcasting the instruction in cells covered by the base station.

10. The method according to claim 1, wherein, Determine whether the UL message includes the location protocol message based on the type of the UL message.

11. The method according to claim 1, wherein, Determining whether the UL message includes the positioning protocol message is based on the type of the lower-level message that includes the UL message.

12. The method according to claim 1, wherein, Determining whether the UL message includes the location protocol message includes: determining whether the UL message includes an information element (IE) indicating the presence of the location protocol message.

13. The method according to claim 1, wherein, Determining whether the UL message includes the location protocol message includes: determining whether the lower-level message including the UL message includes an information element (IE) indicating the presence of the location protocol message.

14. The method according to claim 1, further comprising: Determine whether the location protocol message corresponds to a first message type or a second message type; and In the third case, in response to determining that the UL message includes a location protocol message of the second message type, the location protocol message is sent to the remote node; In the first case, the location protocol message corresponds to the first message type.

15. A base station including processing hardware and configured to implement the method according to any one of the preceding claims.

16. The base station according to claim 15, further comprising: The local entity that implements the location service.

17. The base station according to claim 15, wherein, The local entity is implemented in the radio access network (RAN) and in the node connected to the base station via a network link.

18. A method for transmitting information related to location services, the method comprising, at a UE: Generate location protocol messages associated with the location protocol used to exchange location-related information; Generating a UL RRC message includes layering the positioning protocol message directly on the RRC layer of the UL RRC message; The UL RRC message is sent to the base station via the radio interface; Receive from the base station (i) the base station supports a first location service at a radio access network (RAN) node, and (ii) the CN supports a second location service at a node operating in the CN; In response to determining that the first location service has a higher priority than the second location service, the UL RRC message is addressed to the first location service; and In response to determining that the second location service has a higher priority than the first location service, the UL RRC message is addressed to the second location service.

19. The method according to claim 18, wherein, The location protocol message is a first location protocol message, and the method further includes: Generate a second location protocol message associated with the aforementioned location protocol; Generate a UL NAS message including the second positioning protocol message; and The UL NAS message is sent to the base station via the radio interface.

20. The method of claim 18, further comprising: Receive an indication of which of the first location service and the second location service has higher priority.

21. A user equipment, including processing hardware and configured to implement the method according to any one of claims 18-20.

22. A method for transmitting information related to location services, the method comprising, at a UE: Generate location protocol messages associated with the location protocol used to exchange location-related information; Determine whether the location protocol message addresses a Radio Access Network (RAN) node or a Core Network (CN) node; In the first case: In response to determining that the location protocol message addresses the RAN node, the location protocol message is included in a first lower-layer message, wherein, The location protocol messages are layered directly on RRC without an intermediate protocol layer, and The first lower-layer message is sent to the base station via the radio interface; In the second case: In response to determining that the location protocol message addresses the CN node, the location protocol message is included in a second lower-layer message, the second lower-layer message differing from the first lower-layer message in at least one aspect of message type or protocol layering, wherein the location protocol message is layered on the NAS, and The second lower-layer message is sent to the base station via the radio interface.

23. The method of claim 22, further comprising receiving from the base station an indication that the base station supports location services at the RAN node.

24. The method according to claim 22, wherein, The first lower-layer message and the second lower-layer message correspond to the NAS layer.

25. The method of claim 22, further comprising: The base station receives an indication that the RAN supports location services, wherein, in the first case, the location protocol message is included in a first lower-layer message in response to the indication.

26. The method of claim 25, wherein, The instruction is received in a broadcast within the cell covered by the base station.

27. A user equipment, including processing hardware and configured to implement the method according to any one of claims 22-26.

28. A computer-readable medium comprising instructions that, when executed by a computing device, cause the computing device to perform the method according to any one of claims 18-20 or 22-26.

Images