Patent Description:
In recent years, different communication technologies have been proposed to improve communication performances, such as, the New Radio (NR) (also referred to <NUM> generation (<NUM>)) system. Some new network architectures have been proposed. For the 3rd Generation Partnership Project (3GPP) Release <NUM> (Rel-<NUM>), the architecture for positioning user equipment (UE) basically relies on two core network entities, i.e., the Location Management Function (LMF) and the Access and Mobility Management Function (AMF).

In Rel-<NUM>, a solution where the next generation radio access network (NG-RAN) node is enhanced to support location management functionality has been proposed to achieve low latency and high-performance location services (LCS). As such, there may be situations where concurrent location requests for the same UE are handled by two nodes, for example, one being handled by the NG-RAN locally and the others being handled by the LMF in the core network. Therefore, it is desirable to coordinate such concurrent location requests.

The present invention provides for a device and corresponding method as claimed in the accompanying claims.

References in the present disclosure to "one embodiment," an embodiment," "an example embodiment," and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic.

As used herein, the term "communication network" refers to a network following any suitable communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (<NUM>), the second generation (<NUM>), <NUM>, <NUM>, the third generation (<NUM>), the fourth generation (<NUM>), <NUM>, the future fifth generation (<NUM>) communication protocols, and/or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio header (RH), a remote radio head (RRH), a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.

As mentioned above, in Rel-<NUM>, the UE positioning architecture is reliant on AMF and LMF, which are entities in the core network. <FIG> illustrates an example architecture <NUM> for positioning UE. In the example shown in <FIG>, the NG-RAN <NUM> comprises two network devices, such as ng-eNB <NUM>-<NUM> and gNB <NUM>-<NUM>, which communicate with each other over the Xn interface. AMF <NUM> communicates with the ng-eNB <NUM>-<NUM> and gNB <NUM>-<NUM> over NG-C interfaces and communicates with LMF <NUM> over the NLs interface. The UE <NUM> communicates with the ng-eNB <NUM>-<NUM> and gNB <NUM>-<NUM> over the LTE-Uu interface and the NR-Uu interface, respectively.

In such architecture <NUM>, the LMF <NUM> manages the overall co-ordination and scheduling of resources required for the location of a UE (e.g., the UE <NUM>) that is registered with or accessing the <NUM> core network. The AMF <NUM> receives a location request from another entity, e.g. Gateway Mobile Location Center (GMLC, not shown herein) in case of Mobile Terminated Location Request (MT-LR), or UE <NUM> in case of Mobile Originated Location Request (MO-LR). Alternatively, the AMF <NUM> decides itself to initiate a location request (in case of Network Induced Location Request (NI-LR)), selects an appropriate LMF (e.g., the LMF <NUM>) to handle the request, and transfers the request to the selected LMF. Location request from the NG-RAN <NUM> is not supported.

Specifically, the AMF <NUM> receives a request for some location service associated with the target UE <NUM> from another entity (e.g., GMLC) or the AMF <NUM> itself decides to initiate some location service on behalf of the target UE <NUM> (e.g., for an IMS emergency call from the UE <NUM>). The AMF <NUM> then sends a location services request to the LMF <NUM>. The LMF <NUM> processes the location services request which may include transferring assistance data to the target UE <NUM> to assist with UE-based and/or UE-assisted positioning and/or may include positioning of the target UE <NUM>. The LMF <NUM> then returns the result of the location service back to the AMF <NUM> (e.g., a position estimate for the UE <NUM>). In the case of a location service requested by an entity other than the AMF <NUM> (e.g., a GMLC), the AMF <NUM> returns the location service result to this entity.

In Rel-<NUM>, a solution to achieve low latency location services (LCS) where the NG-RAN node is enhanced to support "local" location management functionality is proposed. <FIG> illustrates an example environment <NUM> in which embodiments of the present disclosure may be implemented. The environment <NUM>, which is a part of a communication network, comprises a terminal device <NUM>, for example, a UE.

The environment <NUM> also comprises a radio access network (RAN) <NUM>, for example, a NG-RAN. The RAN <NUM> includes two network devices <NUM>-<NUM> and <NUM>-<NUM> (which may be referred to as network devices <NUM> collectively, or referred to as a network device <NUM> individually). Each of the two network devices <NUM>-<NUM> and <NUM>-<NUM> may comprise an ng-eNB or a gNB. The terminal device <NUM> can communicate with the network devices <NUM>-<NUM> and <NUM>-<NUM> in the RAN <NUM> over Uu interfaces. The communication between the terminal device <NUM> and the network device <NUM> may follow any suitable wireless communication standards or protocols and employs any suitable communication technologies. The communication standards or protocols and technologies may include those that already exist or are to be developed in the future. The scope of the present disclosure will not be limited in this regard.

As shown in <FIG>, the environment <NUM> further comprises an AMF <NUM> and an LMF <NUM>, which are entities in the core network (not shown). The AMF <NUM> may communicate with the network devices <NUM>-<NUM> and <NUM>-<NUM> in the RAN <NUM> over NG-C interfaces. The NLs interface, between the LMF <NUM> and the AMF <NUM>, is transparent to all UE related, gNB related and ng-eNB related positioning procedures. It is to be understood that the devices or functions are shown in <FIG> only for the purpose of illustration without suggesting any limitation to the scope of the present disclosure. The environment <NUM> may include any suitable other devices, functions or elements to enable coordination of location requests or to provide other services.

The RAN <NUM> may also comprise one or more location management component (LMC). As shown, the RAN <NUM> comprises an LMC <NUM>. One of the principle new use cases for the LMC <NUM> is to support location service requests that originate internal to the RAN <NUM>, e.g. for purposes such as Radio Resource Management (RRM), Minimization of Drive Tests (MDT), etc. This type of location request can be referred to as RAN Induced Location Request (RI-LR). The LMC <NUM> is ideally suited to handle RI-LR since the necessary operations are internal to the RAN <NUM> and can therefore be handled locally, avoiding the additional latency and network interface signaling that would be incurred if RI-LR was handled by the LMF <NUM>.

It is to be understood that the example architecture shown in <FIG> is only for purpose of illustration without any limitation. In some example embodiments, the LMC <NUM> may be implemented within each or one of the network devices <NUM>-<NUM> and <NUM>-<NUM>. For example, the LMC <NUM> may be implemented as part of an ng-eNB or a gNB. In some example embodiments, the LMC <NUM> may be implemented separately from the network devices <NUM>-<NUM> and <NUM>-<NUM>. For example, the LMC <NUM> may be implemented as or included in another network device separated from the network devices <NUM>-<NUM> and <NUM>-<NUM>. The scope of the present disclosure in this regard is not limited.

A general procedure for RI-LR handled locally by the LMC is now described with reference to <FIG> illustrates a flowchart illustrating an example process <NUM> for handling internal location request at NG-RAN <NUM> with an LMC. In this scenario, the UE <NUM> is assumed to be in connected mode prior to the beginning of the process <NUM>.

Some function in the NG-RAN <NUM> (e.g. RRM, MDT) requests some location service (e.g. positioning) for a target UE <NUM> to the LMC using signaling internal to the NG-RAN <NUM>. As such, a RI-LR is initiated <NUM>. The NG-RAN <NUM>, in particular the LMC, instigates <NUM> location procedures internal to the NG-RAN <NUM> node - e.g. to obtain positioning measurements or assistance data. The LMC may also instigate location procedures with neighbor NG-RAN node(s) - e.g. to obtain assistance data such as Positioning Reference Signal (PRS) configuration of Transmission Points (TPs) served by the neighbor NG-RAN node(s).

In addition, or alternatively, for downlink positioning NG-RAN <NUM> with the LMC instigates <NUM> location procedures with the UE <NUM> - e.g. to obtain a location estimate or positioning measurements or to transfer location assistance data to the UE <NUM>. The LMC provides <NUM> a location service response to the requesting function in the NG-RAN <NUM> and includes any needed results - e.g. success or failure indication and, if requested and obtained, a location estimate for the UE <NUM>. As can be seen, the AMF <NUM> in the core network is not involved in such a process <NUM>. Information about the RI-LR is not transmitted to the AMF <NUM>, which thus is not aware of the positioning operation performed at the NG-RAN <NUM>.

In deployments where there are NG-RAN nodes supporting an LMC, the LMC is unlikely to be used for all types of location requests. For example, it may be desirable to use the LMC only for location requests that require high level quality of service (QoS), e.g. low latency, while less demanding location requests continue to be served by the LMFs in the core network. This is due to the more limited resources (e.g. processing power) at the NG-RAN node.

The inventors have realized that a problem may occur when there are multiple concurrent location requests. Assuming RI-LR and low latency requests should be handled by the LMC, then there are different scenarios for concurrently handling other types of location requests (e.g. MT-LR with "normal" latency), where it is preferred to handle the other types of location requests in either the LMC or LMF depending on the scenario. For example, it may be preferred to handle non-latency sensitive location requests in the LMC only if there is an active/ongoing location session in the LMC (for a low latency request) since there may be efficiencies in handling both requests by the same node. Or, it may be preferred to always handle non-latency sensitive location requests in an LMF but ensure that the positioning method(s) and/or resource configurations are compatible with those simultaneously being used by the LMC.

Therefore, there is a need to coordinate RI-LR handled locally in the NG-RAN node with other location request types (e.g. MT-LR, MO-LR) for the same target UE that are received by the AMF.

In LTE, location service requests initiated by the RAN (e.g. RI-LR) are not supported, so the issue of coordinating location management in the RAN with location management in the core network did not exist in LTE.

RAN as an LCS Client has been previously proposed, where the RAN sends a location service request to the AMF which the AMF handles as any other location service request received from another entity, including LMC/LMF selection. However, LMC/LMF selection is undesirable in this case since the NG-RAN node can decide on its own to use the LMC and avoid latency introduced by AMF involvement.

The NG-RAN node is always allowed to reject requests received from an LMF via NR Positioning Protocol A (NRPPa). Therefore, one way to avoid uncoordinated actions between an LMC and an LMF is for the NG-RAN node to reject location sessions initiated by the LMF while a location session initiated by the LMC is ongoing. However, this results in a failed location request which is of course undesirable.

On the support of concurrent location requests, two cases where Concurrent Location Requests occur have been defined as the following. Concurrent Location Requests occur when any entity (e.g. UE, AMF, LMF, GMLC, NEF): receives/initiates multiple LCS requests (e.g. 5GC-MT LR, 5GC-MO LR, 5GC-NI LR) for the location estimate of the same target UE within a time period (Case A); or receives/initiates one or more new LCS request(s) (e.g. 5GC-MT LR, 5GC-MO LR, 5GC-NI LR) for the location estimate of the same target UE during the location session to support the old LCS request(s) (Case B).

In either case, if allowed by the QoS requirements and privacy settings, the entity may combine the concurrent location requests by fully executing one of the requests and using the ensuing location estimate result(s) to satisfy the other request(s) without fully executing the latter. When concurrent location requests are supported, each entity needs to ensure that it correlates each location/position response with the associated request and different concurrent location requests shall be treated separately without any dependency on one another by any entity.

In the above conventional solutions, the concurrent location requests cannot be coordinated in an efficient way. Therefore, a solution is needed to enable efficient coordination of concurrent location requests for a same target UE, for example, efficient coordination of RI-LR handled locally in the NG-RAN node with other location request types for the same target UE that are received by the AMF.

According to embodiments of the present disclosure, there is proposed a solution for coordination of concurrent location requests for the same target device. In the present disclosure, a terminal device may have a "local" location session handled by the LMC of the serving RAN (e.g., NG-RAN). The serving RAN provides information about the "local" location session to the AMF in the core network. The AMF stores this information in the context of the terminal device, and uses this information to efficiently handle new location service requests (e.g. MT-LR, MO-LR) that the AMF receives while the "local" location session is active/ongoing. Embodiments of the present disclosure can enable coordinated and efficient handling of concurrent location requests for the terminal device.

Principle and implementations of the present disclosure will be described in detail below with reference to <FIG>, which illustrates a flowchart illustrating an example process <NUM> for handling concurrent location requests according to some embodiments of the present disclosure. For the purpose of discussion, the process <NUM> will be described with reference to <FIG>. The process <NUM> may involve the terminal device <NUM>, the RAN <NUM>, the AMF <NUM>, and the LMF <NUM> as illustrated in <FIG>. Although the process <NUM> is described with respect to the RAN <NUM>, in some example embodiments, the actions described with respect to the RAN <NUM> may be specifically implemented at a network device in the RAN <NUM>. For example, in the case where the LMC <NUM> is implemented within the network device <NUM>, the actions may be implemented at the network device <NUM>. In the case where the LMC <NUM> is implemented as a further network device separated from the network device <NUM>, the actions may be implemented at the further network device.

Some function in the RAN <NUM> may request some location service (e.g. positioning) for the terminal device <NUM> to the LMC using signaling internal to the RAN <NUM>. As such, a RI-LR for the terminal device <NUM> is initiated <NUM>. In other word, a positioning operation of the terminal device <NUM> is started at the RAN <NUM>.

The RAN <NUM> transmits <NUM> information concerning the positioning operation at the RAN <NUM> to the AMF <NUM> in the core network. The information concerning the positioning operation may be also referred to as "location management information" herein. The location management information may be transmitted to the AMF <NUM> for example via a new or existing message, such as a NG Application Protocol (NGAP) message. Whenever the positioning operation or the RI-LR location session is started or changed or stopped for the terminal device <NUM>, the location management information may be transmitted or updated to the AMF <NUM>. In this way, the AMF <NUM> is aware of the positioning operation at the RAN <NUM>, for example aware of the RI-LR.

To better understand the coordination proposed herein, a description of the location management information is now given. The location management information may include a state indication of the positioning operation, for example to indicate the state of the "local" location session. The state indication may indicate that the positioning operation has been started or is being performed at the RAN <NUM> (e.g., "start"). When the positioning operation at the RAN <NUM> is terminated or stopped, the state indication may be updated or another state indication may be transmitted to indicate that the positioning operation has been stopped or terminated at the RAN <NUM> (e.g., "stop").

In addition to the state indication of the positioning operation, the location management information may include one or more attributes associated with the positioning operation that may be useful for the AMF <NUM>. For example, the location management information may comprise information about the internal location service request being handled by the LMC <NUM>. In case of the positioning operation being started, such information may comprise, but not limited to, Location Quality of Service information, e.g. LCS accuracy, response time (latency), QoS Class, etc.; type of the location service request, e.g. Location Immediate Request (LIR) or Location Deferred Request (LDR); LCS Client identity; start time, stop time; requested type of location, i.e. "current location", "current or last known location" or "initial location" applicable to LIR only; Type of Event, e.g. motion or periodic location, in case of "LDR"; velocity of the terminal device <NUM>; requested maximum age of location; and the like.

It is to be noted that a change of location management information can be treated as a different type of state indication of location session (e.g. "update"). Alternatively, the change of location management information can be more simply treated as the start of a new location session or of a new positioning operation (e.g. "start"). This implicitly means that the location session or positioning operation with the previous attributes has been stopped/replaced.

In some example embodiments, when the location session or positioning operation is terminated, the RAN <NUM> may transmit to the AMF <NUM> a state indication that the positioning operation is terminated at the RAN <NUM>, for example as part of the location management information. Additionally, the RAN <NUM> may further transmit the location estimate of the terminal device <NUM> as part of the location management information, for example if requested by the AMF <NUM>. In some example embodiments, the RAN <NUM> may also transmit information about other location service requests that are being handled by the LMC <NUM> but which the LMC <NUM> prefers to move to an LMF, e.g. the LMF <NUM>. Such location service requests may comprise for example MT-LR, MO-LR, or NI-LR. The information about the other location service requests may comprise similar attributes as described above with respect to the location management information.

Still refer to <FIG>. The location management information transmitted <NUM> by the RAN <NUM> may comprise a state indication of the positioning operation which is set to indicate that the location session is started and information about the location session at the RAN <NUM>. After receiving the location management information from the RAN <NUM>, the AMF <NUM> stores <NUM> the received location management information in the context of the terminal device <NUM>. The AMF <NUM> may not need to perform LMC/LMF selection and may not need to send any response or acknowledgement to the RAN <NUM>.

The RAN <NUM> then performs the positioning operation of the terminal device <NUM>. As shown in <FIG>, the RAN <NUM>, in particular the LMC <NUM>, instigates <NUM> location procedures internal to the RAN <NUM> to obtain positioning measurements or assistance data. The LMC <NUM> may also instigate location procedures with neighbor RAN node(s) as described with <FIG>. In addition, or alternatively, for downlink positioning RAN <NUM> with the LMC <NUM> instigates <NUM> location procedures with the terminal device <NUM>, for example to obtain a location estimate or positioning measurements or to transfer location assistance data to the terminal device <NUM>.

At the AMF <NUM>, based on the stored <NUM> location management information, the AMF <NUM> may take corresponding actions if it receives a new/concurrent location request (e.g. MO-LR, MT-LR, NI-LR) for the terminal device <NUM> while there is an active/ongoing location session at the LMC <NUM> for the terminal device <NUM>, i.e., the positioning operation is being performed at the RAN <NUM>.

The AMF receives <NUM>, from an LCS entity <NUM> in the 5GC, a location request for a location of the terminal device <NUM>, which will be referred to as location request or concurrent location request hereinafter. For example, the LCS entity <NUM> may transmit to the AMF <NUM> a location service request (e.g. positioning) for the terminal device <NUM>. It is to be understood that the LCS entity <NUM> may be any suitable LCS entity, for example the GMLC.

By checking the context of the terminal device <NUM>, the AMF <NUM> determines <NUM> that the positioning operation for the terminal device <NUM> is being performed at the RAN <NUM> and also the attributes of the positioning operation. In other words, the AMF <NUM> may be aware that a location session is active/ongoing at the LMC <NUM>, and also aware of the attributes of the active/ongoing location session. Then, the AMF <NUM> may handle the concurrent location request based on the stored location management information for the terminal device <NUM>. Blocks <NUM>, <NUM> and <NUM> refer to different example options A, B, C that can be utilized by the AMF <NUM> to handle this concurrent location request. These example embodiments are now described in detail.

In some example embodiments, the AMF <NUM> may transfer the concurrent location request (e.g.MT-LR) to the RAN <NUM> for handling by the LMC <NUM>. Such example embodiments are now described with respect to the actions in the block <NUM> only for purpose of illustration without any limitation. If the AMF <NUM> determines that the positioning operation of the terminal device <NUM> is being performed at the RAN <NUM>, the AMF <NUM> transmits <NUM> the concurrent location request to the RAN <NUM> to enable the RAN <NUM> (for example, the LMC <NUM>) to handle this location request.

Upon receiving the concurrent location request from the AMF <NUM>, the RAN <NUM>, for example the LMC <NUM> may handle both the concurrent location request and the internal location request (e.g. RI-LR) in a coordinated and efficient way. In some example embodiments, the RAN <NUM> may perform a further positioning operation to handle this concurrent location request, in order to determine the location information of the terminal device <NUM>. The further positioning operation is compatible with the positioning operation being performed to handle the internal location request. The further positioning operation may be selected from a variety of positioning methods, such as Enhanced Cell ID (E-CID) positioning method, Observed Time Difference of Arrival (OTDOA) positioning method, Global Navigation Satellite System (GNSS) positioning method, etc..

In some example embodiments, the RAN <NUM> may select a particular positioning method to concurrently handle both the location request received from the AMF <NUM> and the internal location request. The particular positioning method may be a positioning method which can satisfy the most demands of both requests.

Upon determining the location information of the terminal device <NUM>, the RAN <NUM> may generate the response to the concurrent location request based on the location information. Then, the RAN <NUM> transmits <NUM> to the AMF <NUM> the response to the concurrent location request, which is subsequently forwarded <NUM> by the AMF <NUM> to the LCS entity <NUM>.

In such example embodiments, the concurrent location request is handled by the same entity with the internal location request, i.e. the RAN <NUM>. The AMF <NUM> may select to transfer the concurrent location request to the RAN <NUM> as long as there is an active/ongoing location session at the LMC <NUM>.

In some example embodiments, the AMF <NUM> may handle the concurrent location request (e.g. MT-LR) itself. Such example embodiments are now described with respect to the actions in the block <NUM> only for purpose of illustration without any limitation. A query procedure <NUM> may be performed between the AMF <NUM> and the RAN <NUM>. For example, the AMF <NUM> may query the RAN <NUM> for the latest available location information of the terminal device <NUM>, if the ongoing location session at the RAN <NUM> has appropriate attributes in terms of e.g. accuracy, expected age, etc. Then, the RAN <NUM>, for example the LMC <NUM>, provides the already available location information of the terminal device <NUM> to the AMF <NUM>. The response to the concurrent location request is then generated and transmitted <NUM> to the requesting entity <NUM>.

As an example process of the option B as schematically shown in the block <NUM>, the AMF <NUM> may determine, based on the location management information and the concurrent location request, whether an attribute included in the concurrent location request matches a corresponding attribute of the positioning operation. For example, the AMF <NUM> may determine whether the internal location request at the RAN <NUM> has a same or similar positioning accuracy with the concurrent location request. If the AMF <NUM> determines that the attribute included in the concurrent location request matches the corresponding attribute of the positioning operation, for example, if the AMF <NUM> determines that the internal location request at the RAN <NUM> has a same positioning accuracy with the concurrent location request, the AMF <NUM> may transmit to the RAN <NUM> a request for the location information of the terminal device <NUM>. The RAN <NUM> may provide the AMF <NUM> with the location information of terminal device <NUM> which has been determined. The AMF <NUM> may then generate the response to the concurrent location request based on the received location information.

In such example embodiments, when the functionality of Concurrent Location Requests is supported at the AMF <NUM> (if allowed by the QoS requirements and privacy settings), the AMF <NUM> may indicate to the LMC <NUM> its capability of Concurrent Location Request handling. The LMC <NUM> will not initiate another session for the concurrent location request and will only report location estimate result of the terminal device <NUM> to the AMF <NUM> once it is available (for example, as a result of the ongoing RI-LR). The location estimate result will then be used by the AMF <NUM> for responding to the concurrent location request (e.g. 5GC-MT LR, 5GC-MO LR and 5GC-NI LR) that is subject to Concurrent Location Request handling at the AMF.

In such example embodiments, the location information of the terminal device which is already available at the LMC is leveraged, and thus no additional RAN resource is required. Also, transferring of the concurrent location request (e.g., non-latency-sensitive MT-LR) from the AMF to the LMC can be avoided.

In some example embodiments, the AMF <NUM> may select a LMF (for example, the LMF <NUM>) to handle the concurrent location request (e.g. MT-LR). In such example embodiments, the selected LMF <NUM> may be also referred to as an enhanced LMF, of which the functionality is enhanced compared to that of a conventional LMF. Such example embodiments are now described with respect to the actions in the block <NUM> only for purpose of illustration without any limitation.

The AMF <NUM> transmits <NUM> the concurrent location request to the selected LMF <NUM>, along with at least part of the location management information about the terminal device <NUM> which is previously received from the RAN <NUM>. The LMF <NUM> takes the location management information into account when handling the concurrent location request. The LMF <NUM> is able to request the latest available location information of the terminal device <NUM> from the LMC <NUM>, or manage the concurrent location request in a way that is compatible with the positioning operation at the LMC <NUM>.

The LMF <NUM> may perform a procedure <NUM> to obtain the location information of terminal device <NUM> to handle the concurrent location request. In some example embodiments, the LMF <NUM> may fetch the latest available location information of the terminal device <NUM> from the LMC <NUM>, if the ongoing location session has appropriate attributes in terms of e.g. accuracy, expected age, etc., similarly as described below with respect to the procedure <NUM>. Then, the LMC <NUM> provides the already available location information of the terminal device <NUM> to the LMF <NUM>.

As an example process, the LMF <NUM> may determine, based on the location management information and the concurrent location request, whether an attribute included in the concurrent location request matches a corresponding attribute of the positioning operation. For example, the LMF <NUM> may determine whether the internal location request at the RAN <NUM> has a same or similar positioning accuracy with the concurrent location request. If the LMF <NUM> determines that the attribute included in the concurrent location request matches the corresponding attribute of the positioning operation, for example, if the LMF <NUM> determines that the internal location request at the RAN <NUM> has a same positioning accuracy with the concurrent location request, the LMF <NUM> may transmit to the RAN <NUM> a request for the location information of the terminal device <NUM>. The RAN <NUM> may provide the LMF <NUM> with the location information of terminal device <NUM> which has been determined.

In some example embodiments, the LMF <NUM> may handle the concurrent location request (e.g., MT-LR) in an independent way that does not conflict with the positioning operation at the LMC <NUM>. For example, the LMF <NUM> may perform a further positioning operation to handle this concurrent location request, in order to determine the location information of the terminal device <NUM>. The further positioning operation is compatible with the positioning operation being performed at the RAN <NUM>. The further positioning operation may be selected from a variety of positioning methods, such as those mentioned above. Such example embodiments may make sense if the concurrent location request (e.g., MT-LR) does not require high accuracy, and thus the LMF <NUM> is able to handle the concurrent location request using for example E-CID that does not conflict with radio configurations being used by the LMC <NUM>.

After obtaining the location information of the terminal device <NUM> (received from the RAN <NUM> in some example embodiments, or determined using a positioning method), the response to the concurrent location request is generated based on the location information by the LMF <NUM> and transmitted <NUM> to the AMF <NUM>. The AMF <NUM> then transmits <NUM> to the LCS entity <NUM> the response to the concurrent location request.

The AMF <NUM> may select the LMF <NUM> to handle the concurrent location request when the concurrent location request does not require low latency. Such example embodiments can achieve many advantages. For example, since the concurrent location request is directly transferred to the LMF, no new functionality is required for the AMF. In other words, functional impact on the AMF can be minimized. Such example embodiments enables the LMC in the RAN to be used only for location requests that require high level QoS (e.g. low latency), while less demanding location requests continue to be served by LMFs in the core network. In this way, the limited resources (e.g. processing power) at the RAN (e.g. the NG-RAN) can be utilized in an efficient way to handle high demanding location requests.

In some example embodiments, if the positioning operation is terminated or the internal location request has been handled, the RAN <NUM> may transmit <NUM> to the AMF <NUM> an indication that the positioning operation is terminated. For example, the RAN <NUM> may transmit the "stop" state indication to the AMF <NUM>, as mentioned above. The AMF <NUM> then updates <NUM> the location management information stored in the context of the terminal device <NUM>. In the case where the concurrent location request for the terminal device <NUM> is being handled by the LMF <NUM>, the AMF <NUM> may further forward <NUM> this "stop" state indication to the LMF <NUM>, which can in turn adapt the handling of the concurrent location request if needed.

In some example embodiments, when the positioning operation is terminated, the location estimation (if requested by the AMF <NUM>) of the terminal device <NUM> and information about other location service request(s) that were being handled by the LMC <NUM> (e.g., MT-LR) can also be transmitted to the AMF <NUM>, for example, along with the "stop" state indication. The AMF <NUM> may then determine whether to transfer the location session for handling the other location request(s) from the LMC <NUM> to the LMF <NUM>, for example, based on local policy, load status, etc..

As an example, while a location session for obtaining the location information requested by the concurrent location request is activated between the RAN <NUM> and the AMF <NUM>, for example during the actions as shown in the block <NUM> or block <NUM>, the AMF <NUM> receives from the RAN <NUM> an indication that the positioning operation for the terminal device <NUM> is terminated at the RAN <NUM>. The AMF <NUM> may deactivate this location session and transmit the concurrent location request to an LMF (e.g. the LMF <NUM>) to enable the LMF to determine the location information. As such, the location session for handling the concurrent location request is transferred from the RAN <NUM> to the LMF.

It is to be noted that in <FIG> the location request from the LCS entity <NUM> is shown to be received after the location management information only for purpose of illustration without any limitation on the scope of the present disclosure. In some example embodiments, the concurrent location request from the LCS entity <NUM> (e.g., MO-LR, MT-LR, NI-LR) may be received before the location management information. Such example embodiments will be described with reference to <FIG>.

<FIG> illustrates a flowchart illustrating an example process <NUM> for handling concurrent location requests according to some embodiments of the present disclosure. For the purpose of discussion, the process <NUM> will be described with reference to <FIG>. The process <NUM> may involve the terminal device <NUM>, the RAN <NUM>, the AMF <NUM>, and the LMF <NUM> as illustrated in <FIG> and the LCS entity <NUM> as shown in <FIG>. Although the process <NUM> is described with respect to the RAN <NUM>, in some example embodiments, the actions described with respect to the RAN <NUM> may be specifically implemented at a network device in the RAN <NUM>. For example, in the case where the LMC <NUM> is implemented within the network device <NUM>, the actions may be implemented at the network device <NUM>. In the case where the LMC <NUM> is implemented as a further network device separated from the network device <NUM>, the actions may be implemented at the further network device.

The actions with the same reference signs (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) as those in <FIG> are similar with the corresponding actions described above with reference to <FIG> and thus description thereof will not be repeated. As shown in <FIG>, before receiving the location management information from the RAN <NUM>, the AMF <NUM> receives <NUM>, from the LCS entity <NUM>, a location request for a location of the terminal device <NUM>, which will be referred to a concurrent location request hereinafter. Then, the AMF <NUM> transmits <NUM> the concurrent location request to the LMF <NUM> for handling by the LMF <NUM>.

In such a case, when receiving from the RAN <NUM> the location management information, an active location session for the terminal device <NUM> already exists in the LMF <NUM>. In addition to storing <NUM> the location management information in the context of the terminal device <NUM>, the AMF <NUM> may forward the location management information to the LMF <NUM>. For example, if the AMF <NUM> determines that the concurrent location request has been transmitted to the LMF <NUM>, which means an active location session for the terminal device <NUM> existing in the LMF <NUM>, the AMF <NUM> transmits <NUM> the location management information to the LMF <NUM>.

The LMF <NUM> adapts <NUM> the handling of the concurrent location request based on the location management information. For example, the LMF <NUM> may fetch the location information of the terminal device <NUM> from the RAN <NUM> or may handle the concurrent location request in a way that does not conflict with the LMC <NUM>, as described above with respect to the block <NUM> of <FIG>. After obtaining the location information of the terminal device <NUM>, the response to the concurrent location request is generated and transmitted <NUM> to the AMF <NUM> by the LMF <NUM>. The AMF <NUM> then transmits <NUM> to the LCS entity <NUM> the response to the concurrent location request.

More details of the example embodiments in accordance with the present disclosure will be described with reference to <FIG>.

<FIG> shows a flowchart of an example method <NUM> according to some example embodiments of the present disclosure. The method <NUM> can be implemented at any suitable device. For example, the method <NUM> can be implemented at a device in the core network, e.g. at the AMF <NUM> as shown in <FIG>. For the purpose of discussion, the method <NUM> will be described with reference to <FIG>.

At block <NUM>, the AMF <NUM> receives, from the RAN <NUM>, information concerning a positioning operation of a terminal device <NUM>, wherein the positioning operation is performed at the RAN <NUM>. At block <NUM>, the AMF <NUM> receives a location request for a location of the terminal device <NUM>. At block <NUM>, the AMF <NUM> obtains a response to the location request based on the information concerning the positioning operation, the response including location information of the terminal device <NUM>.

In some example embodiments, the information concerning the positioning operation comprises one or more of the following: accuracy required for the positioning operation, a response time required for the positioning operation, a type of location required for the positioning operation, or a type of event triggering the positioning operation.

In some example embodiments, obtaining the response comprises: transmitting the information concerning the positioning operation and the location request to the LMF <NUM> to enable the LMF <NUM> to obtain the location information based on the information; and receiving, from the LMF <NUM>, the response to the location request.

In some example embodiments, the information concerning the positioning operation is received before the location request, and wherein the transmitting comprises: determining, based on the information concerning the positioning operation, whether the positioning operation is being performed at the RAN <NUM>; and in response to a determination that the positioning operation is being performed at the RAN <NUM>, transmitting the location request along with the information concerning the positioning operation to the LMF <NUM>.

In some example embodiments, the information concerning the positioning operation is received after the location request and the transmitting comprises: transmitting the location request to the LMF <NUM>; and in response to a determination that the location request has been transmitted, transmitting the information concerning the positioning operation to the LMF <NUM>.

In some example embodiments, obtaining the response comprises: determining, based on the information concerning the positioning operation, whether the positioning operation is being performed at the RAN <NUM>; in response to a determination that the positioning operation is being performed at the RAN <NUM>, transmitting the location request to the RAN <NUM> to enable the RAN <NUM> to determine the location information; and receiving, from the RAN <NUM>, the response to the location request.

In some example embodiments, obtaining the response comprises: determining, based on the information and the location request, whether an attribute included in the location request matches a corresponding attribute of the positioning operation; in response to a determination that the attribute included in the location request matches the corresponding attribute of the positioning operation, transmitting to the RAN <NUM> a request for the location information of the terminal device <NUM>; receiving the location information from the RAN <NUM>; and generating the response to the location request based on the received location information.

In some example embodiments, obtaining the response comprises: while a session for obtaining the response is activated between the RAN <NUM> and the AMF <NUM>, receiving from the RAN <NUM> an indication that the positioning operation is terminated at the RAN <NUM>; deactivating the session for obtaining the response; transmitting the location request to a LMF <NUM> to enable the LMF <NUM> to determine the location information; and receiving, from the LMF <NUM>, the response to the location request.

<FIG> shows a flowchart of an example method <NUM> according to some example embodiments of the present disclosure. The method <NUM> can be implemented at any suitable device. For example, the method <NUM> can be implemented at the RAN <NUM> as shown in <FIG>. For the purpose of discussion, the method <NUM> will be described with reference to <FIG>. It is to be noted that the method <NUM> may be implemented specifically at a network device in the RAN <NUM>, which incorporates the LMC.

At block <NUM>, the RAN <NUM> performs a positioning operation of a terminal device <NUM>. The positioning operation may be triggered locally in the RAN <NUM>, for example, may be responsive to a RI-LR. At block <NUM>, the RAN <NUM> transmits information concerning the positioning operation to an AMF <NUM>, to enable the AMF <NUM> to obtain a response to a location request for a location of the terminal device <NUM> based on the information concerning the positioning operation, the response including location information of the terminal device <NUM>.

In some example embodiments, the method <NUM> further comprises: in response to receiving the location request from the AMF <NUM>, determining the location information of the terminal device <NUM>; generating the response to the location request based on the location information; and transmitting to the AMF <NUM> the response to the location request.

In some example embodiments, determining the location information of the terminal device <NUM> comprises: performing a further positioning operation compatible with the positioning operation.

In some example embodiments, the method <NUM> further comprises receiving from the AMF <NUM> a request for the location information of the terminal device <NUM>; and transmitting to the AMF <NUM> the location information having been determined at the RAN <NUM>.

In some example embodiments, the method <NUM> further comprises: receiving the location request from the AMF <NUM>; in response to the positioning operation being terminated, transmitting to the AMF <NUM> an indication that the positioning operation is terminated; and transmitting the location request back to the AMF <NUM>.

<FIG> shows a flowchart of an example method <NUM> according to some example embodiments of the present disclosure. The method <NUM> can be implemented at a device in the core network for example at the LMF <NUM> as shown in <FIG>. For the purpose of discussion, the method <NUM> will be described with reference to <FIG>.

At block <NUM>, the LMF <NUM> receives, from an AMF <NUM>, information concerning a positioning operation of a terminal device <NUM>, wherein the positioning operation is performed at a RAN <NUM>. At block <NUM>, the LMF <NUM> receives, from the AMF <NUM>, a location request for a location of the terminal device <NUM>. At block <NUM>, the LMF <NUM> generates a response to the location request based on the information concerning the positioning operation, the response including location information of the terminal device <NUM>. At block <NUM>, LMF <NUM> transmits, to the AMF <NUM>, the response to the location request.

In some example embodiments, generating the response comprises: determining the location information by performing a further positioning operation of the terminal device <NUM>, the further positioning operation being compatible with the positioning operation at the RAN <NUM>; and generating the response to the location request based on the determined location information.

In some example embodiments, generating the response comprises: determining, based on the information and the location request, whether an attribute included in the location request matches a corresponding attribute of the positioning operation; in response to a determination that the attribute included in the location request matches the corresponding attribute of the positioning operation, transmitting to the RAN <NUM> a request for the location information of the terminal device <NUM>; receiving the location information from the RAN <NUM>; and generating the response to the location request based on the received location information.

In some example embodiments, an apparatus capable of performing the method <NUM> may comprise means for performing the respective steps of the method <NUM>. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In some example embodiments, the apparatus comprises: means for receiving, at a first network device from a second network device, information concerning a positioning operation of a terminal device, wherein the positioning operation is performed at the second network device; means for receiving a location request for a location of the terminal device; and means for obtaining a response to the location request based on the information concerning the positioning operation, the response including location information of the terminal device.

In some example embodiments, the means for obtaining the response comprises: means for transmitting the information concerning the positioning operation and the location request to a third network device to enable the third network device to obtain the location information based on the information; and means for receiving, from the third network device, the response to the location request.

In some example embodiments, the information concerning the positioning operation is received before the location request, and wherein the means for transmitting comprises: means for determining, based on the information concerning the positioning operation, whether the positioning operation is being performed at the second network device; and means for in response to a determination that the positioning operation is being performed at the second network device, transmitting the location request along with the information concerning the positioning operation to the third network device.

In some example embodiments, the information concerning the positioning operation is received after the location request and the means for transmitting comprises: means for transmitting the location request to the third network device; and means for in response to a determination that the location request has been transmitted, transmitting the information concerning the positioning operation to the third network device.

In some example embodiments, the means for obtaining the response comprises: means for determining, based on the information concerning the positioning operation, whether the positioning operation is being performed at the second network device; means for in response to a determination that the positioning operation is being performed at the second network device, transmitting the location request to the second network device to enable the second network device to determine the location information; and means for receiving, from the second network device, the response to the location request.

In some example embodiments, the means for obtaining the response comprises: means for determining, based on the information and the location request, whether an attribute included in the location request matches a corresponding attribute of the positioning operation; means for in response to a determination that the attribute included in the location request matches the corresponding attribute of the positioning operation, transmitting to the second network device a request for the location information of the terminal device; means for receiving the location information from the second network device; and means for generating the response to the location request based on the received location information.

In some example embodiments, the means for obtaining the response comprises: means for while a session for obtaining the response is activated between the second network device and the first network device, receiving from the second network device an indication that the positioning operation is terminated at the second network device; means for deactivating the session for obtaining the response; means for transmitting the location request to a third network device to enable the third network device to determine the location information; and means for receiving, from the third network device, the response to the location request.

In some example embodiments, the apparatus comprises an access and mobility management function, AMF.

In some example embodiments, the apparatus comprises: means for performing, at a second network device, a positioning operation of a terminal device; and means for transmitting information concerning the positioning operation to a first network device, to enable the first network device to obtain a response to a location request for a location of the terminal device based on the information concerning the positioning operation, the response including location information of the terminal device.

In some example embodiments, the apparatus further comprises: means for in response to receiving the location request from the first network device, determining the location information of the terminal device; means for generating the response to the location request based on the location information; and means for transmitting to the first network device the response to the location request.

In some example embodiments, the means for determining the location information of the terminal device comprises: means for performing a further positioning operation compatible with the positioning operation.

In some example embodiments, the apparatus further comprises means for receiving from the first network device a request for the location information of the terminal device; and means for transmitting to the first network device the location information having been determined at the second network device.

In some example embodiments, the apparatus further comprises: means for receiving the location request from the first network device; and means for in response to the positioning operation being terminated, transmitting to the first network device an indication that the positioning operation is terminated and transmitting the location request back to the first network device.

In some example embodiments, the apparatus comprises a location management component, LMC.

In some example embodiments, the apparatus comprises: means for receiving, at a third network device from a first network device, information concerning a positioning operation of a terminal device, wherein the positioning operation is performed at a second network device; means for receiving, from the first network device, a location request for a location of the terminal device; means for generating a response to the location request based on the information concerning the positioning operation, the response including location information of the terminal device; and means for transmitting, to the first network device, the response to the location request.

In some example embodiments, the means for generating the response comprises: means for determining the location information by performing a further positioning operation of the terminal device, the further positioning operation being compatible with the positioning operation at the second network device; and means for generating the response to the location request based on the determined location information.

In some example embodiments, the means for generating the response comprises: means for determining, based on the information and the location request, whether an attribute included in the location request matches a corresponding attribute of the positioning operation; means for in response to a determination that the attribute included in the location request matches the corresponding attribute of the positioning operation, transmitting to the second network device a request for the location information of the terminal device; means for receiving the location information from the second network device; and means for generating the response to the location request based on the received location information.

In some example embodiments, the apparatus comprises a location management function, LMF.

<FIG> is a simplified block diagram of a device <NUM> that is suitable for implementing embodiments of the present disclosure. The device <NUM> may be provided to implement the communication device, for example the network device <NUM> or the AMF <NUM>, the LMF <NUM> as shown in <FIG>. As shown, the device <NUM> includes one or more processors <NUM>, one or more memories <NUM> coupled to the processor <NUM>, and one or more communication modules <NUM> coupled to the processor <NUM>.

In some embodiments, the program <NUM> may be tangibly contained in a computer readable medium which may be included in the device <NUM> (such as in the memory <NUM>) or other storage devices that are accessible by the device <NUM>.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method <NUM>, <NUM> or <NUM> as described above with reference to <FIG>. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Claim 1:
A first network device (<NUM>), comprising:
at least one processor (<NUM>); and
at least one memory (<NUM>) including computer program codes;
the at least one memory (<NUM>) and the computer program codes are configured to, with the at least one processor (<NUM>), cause the first network device (<NUM>) at least to:
receive, from a second network device (<NUM>), information concerning a positioning operation of a terminal device (<NUM>), wherein the positioning operation is performed at the second network device (<NUM>);
receive a location request for a location of the terminal device (<NUM>);
characterised in that the at least one memory (<NUM>) and the computer program codes are configured to, with the at least one processor (<NUM>), cause the first network device at least to further:
make a determination about which of the first network device (<NUM>), the second network device (<NUM>) and a third network device (<NUM>) is to handle the location request; and
obtain a response to the location request based on the information concerning the positioning operation, the response including location information of the terminal device (<NUM>), wherein, based on the determination which of the first network device (<NUM>), the second network device (<NUM>) and the third network device (<NUM>) is to handle the location request, the response is generated by the first network device (<NUM>) or received by the first network device (<NUM>) from the second network device (<NUM>) or received by the first network device (<NUM>) from the third network device (<NUM>), respectively.