Providing a serving node indication to facilitate LALS for international inbound roamers

Abstract

The present disclosure provides a method by a Lawful Intercept Location Services (LI- LCS) client (110) for providing an indication to an LCS server (112) about an identity of a serving node to which the target device is connected to in so that the LCS server 112 does not broadcast the location request to all the Access and Mobility Functions (AMFs) or Mobility Management Entities (MMEs) of the network in order to determine the location of the target device The method includes receiving a serving node indication from one of a Mediation and Delivery Function (MF / DF2) (108) or a Network Function (NF) (202) where the serving node indication comprises an identifier associated with a serving node to which the target device is connected. Then the method includes providing the serving node indication to the LCS server (112).

Description

PROVIDING A SERVING NODE INDIC A TION TO FACILITA TE LALS FOR INTERNATIONAL INBOUND ROAMERSTechnical Field

[0001] The present disclosure relates to providing a serving node indication to facilitate Lawful Access Location Services (LALS) performed by a Lawful Intercept Location Services (LI-LCS) client for international inbound roamers in a wireless communications system. The disclosure also relates to a network node, a computer program and a carrier containing the computer program.Background

[0002] Lawful Access Location Services (LALS) provides lawful access to the target's location. LALS is based on the Location Services (LCS) capabilities defined in Third Generation Partnership Project (3GPP) Technical Specification (TS) 23.271, TS 23.273 and in Open Mobile Alliance (OMA) Mobile Location Protocol (MLP). See for example: 3GPP TS 33.127 V18.5.0 (2023-03).

[0003] The LCS supporting LALS shall be able to provide priority to LALS requests. The subscriber location privacy settings shall be overridden for LALS by setting the privacy override indicator to "override" in the Lawful Intercept (LI) Location Services (LCS) client profile in the Gateway Mobile Location Center (GMLC).

[0004] For inbound roaming targets, the Visited Public Land Mobile Network (VPLMN) LCS functional entities that fulfill LALS requests by default shall not communicate with the target's Home Public Land Mobile Network (HPLMN), as it may cause detectability issues, where the HPLMN or some other entity may determine that the target device is a the subject of an LI procedure. Instead, the GMLC shall be able to determine the serving Access and Mobility Management Function (AMF) or Mobile Management Entity (MME) from which it can acquire the inbound roaming target's location. Detectability issues may also exist when LALS is invoked for outbound roaming targets. This means that by default the GMLC shall refrain from performing the positioning of an outbound roaming target.

[0005] The visited GMLC may send the location request to all the AMF / MME of the VPLMN. If the visited GMLC has knowledge of the last AMF / MME serving the target User Equipment (UE), it may use that one in the first attempt.

[0006] The parameters controlling the LALS output are either delivered per warrant over an LI_X1 interface from the Administration Function (ADMF) to the LI-LCS Client, or to the Location Triggering Function (LTF), or are pre-configured in the LI-LCS Client.

[0007] The LI-LCS Client is a special type of Intercept Related Information (IRI) Point of Intercept (POI) in the Communication Service Provider (CSP) network fulfilling the role of the LCS client for LALS purposes.

[0008] There are two types of the location interception:• target positioning which determines the target's location independently of the services used by the target.• triggered location which determines the LALS based location of the target when specific network or service events related to the target occur.

[0009] In target positioning, the location provision variants are immediate location, where the location is to be determined and / or passed on to the Lawful Enforcement Monitoring Facility (LEMF) immediately, or periodic location, where periodic updates to the location of the target device are provisioned.

[0010] The LI-LCS client shall include an IRI-POI that has the LI capabilities to generate the target UE's location related IRI.

[0011] Figure 1 is a block diagram of an exemplary Lawful Access Location Services (LALS) architecture according to one or more embodiments of the present disclosure.

[0012] Figure 1 shows the architecture for LALS where the LI-LCS client 110 provides the target's location and associated information towards the Mediation and Delivery Function (MF / DF2) 108 over the LI_X2 interface as per the ADMF 106 request for target positioning delivered to the LI-LCS Client 110 and the MF / DF2 108 over the LI_X1 interface.

[0013] In Immediate Location Provisioning, the request for immediate location provision is delivered to the LI-LCS client 110 over the LI_X1 interface. Upon receiving the request, the LI-LCS client 110 initiates a Location Immediate Request to the LCS Server 112 supporting LALS over the Le interface and reports the acquired location to the MF / DF2 108 over LI_X2.

[0014] The resulting immediate location information shall be delivered by the LI-LCS client 110 as xIRI over LI_X2 to the MF / DF2 108. The MF / DF2 108 generates and delivers the IRI messages based on received xIRI to the LEMF 104 over LI_H2.

[0015] For Periodic Location Provisioning, the request for periodic location provision is delivered to the LI-LCS client 110 over the LI_X1 interface.

[0016] The request for periodic location from the ADMF 106 to the LI-LCS client 110 may include a set of parameters defining the duration of reporting, report periodicity, etc. The periodic location result shall be delivered by the LI-LCS client 110 as xIRI over LI_X2 to the MF / DF2 108. The MF / DF2 108 generates and delivers the IRI messages based on received xIRI to the LEMF 104 over LI_H2.

[0017] It is to be appreciated that the LCS server 112 may be a GMLC in some embodiments, but for simplicity, is just referred to as LCS server 112 herein.

[0018] The periodicity of the LALS reports shall be controlled by the LI-LCS client 110. The LI-LCS client 110 shall issue a series of Location Immediate Requests at required time intervals.

[0019] The triggered location provisioning is the capability of providing LALS based location information when specific network or service events related to the target occur. While IRI generated by the event that also triggers the LALS may have the location information included (in the form of cell ID), LALS may provide additional location parameters, such as the target geo-location, velocity, etc. The triggered location reporting utilizes the immediate location variant.

[0020] The LALS triggered location architecture in Figures 2 and 3 that depict the Location Triggering Function (LTF) 206 that can be located at either a network function (NF) 202 as in Figure 2, or in the MF / DF2 108 as in Figure 3.

[0021] The LTF 206 is an IRI triggering function (TF) and resides in the same NF (e.g., AMF) that has the IRI-POI 204 or in an MF / DF2 108. The LTF 206 is responsible for triggering the IRI-POI in the LI-LCS Client 110 when a specific event related to the target is observed at the co-located IRI-POI 204 or received at the MF / DF2 108 in which the LTF 206 is residing.

[0022] In case of triggered location, the LTF 206 (present in either an NF 202 hosting an IRI-POI 204 or in a MF / DF2 108) is provisioned by the ADMF 106 over the LI_X1 interface.

[0023] As part of this request, the ADMF 106 provides the address for the LTF 206 to reach the LI-LCS client 110 for use on the LI_T2 interface. The IRI-POI 204 or the MF / DF2 108 then arm the LTF 206. The LTF 206 triggers the LI-LCS client 110 over the LI_T2 interface.

[0024] The LALS result is delivered to MF / DF2 108 from the LI-LCS Client 110 as xIRI over the LI_X2 interface asynchronously with the associated IRI events delivered by the IRI-POI. To enable correlation between the LALS reports and the associated IRI events, the LTF 206 shall include the correlation information of the IRI event, if provided by the IRI-POI 204, into the LI_T2 trigger.

[0025] The following information is to be delivered from the LI-LCS Client 110 to MF / DF2 108 in order to enable the MF / DF2 108 to format and deliver LALS intercept product to the LEMF 104:• Target identity.• Target reported location(s).• Date / time(s) location(s) established by reporting function.• Additional location parameters based on operator policy.• Correlation information.

[0026] An object of the invention is to enable Lawful Access Location Services (LALS) for inbound roaming devices.

[0027] The present disclosure provides a method for providing an indication to a Location Services (LCS) server about an identity of a serving node to which the target device is connected to in so that the LCS server does not broadcast the location request to all the Access and Mobility Functions (AMFs) or Mobility Management Entities (MMEs) of the network in order to determine the location of the target device. The method includes receiving a serving node indication from a Location Triggering Function located at one of a Mediation and Delivery Function (MF / DF2) or a Network Function (NF) where the serving node indication comprises an identifier associated with a serving node to which the target device is connected. Then the method includes providing the serving node indication to the LCS server.

[0028] In an embodiment, a method is provided that includes providing a serving node indication to a LCS server to facilitate LALS, performed by a Lawful Intercept (LI) Location Services (LCS) client. The method includes receiving the serving node indication from one of a MF / DF2 or a NF wherein the serving node indication comprises an identifier associated with a serving node to which a target device is connected. The method also includes providing the serving node indication to the LCS server.

[0029] In an embodiment the serving node indication is received from the MF / DF2.

[0030] In an embodiment, the method includes storing the serving node indication and providing the serving node indication to the LCS server prior to providing a location request message to the LCS server.

[0031] In an embodiment, the providing the location request message to the LCS server is in response to receiving a request for location provisioning from an Administrative Function (ADMF).

[0032] In an embodiment, the method includes receiving the request for location provisioning from the ADMF at periodic intervals.

[0033] In an embodiment, the providing the serving node indication to the LCS server is in response to a trigger event occurring.

[0034] In an embodiment, the method includes receiving an indication of the trigger event occurring from a Location Triggering Function (LTF) at the MF / DF2 or the NF.

[0035] In an embodiment, the method includes receiving updated serving node indications from the MF / DF2 or the NF in response to the target device connecting to a different serving node.

[0036] In an embodiment, the providing the serving node indication to the LCS server comprises providing a latest serving node indication to the LCS server.

[0037] In an embodiment, the method includes receiving from the LCS server, location information associated with the target device and providing to the MF / DF2, the location information.

[0038] In an embodiment, the method includes providing a Location Immediate Request to the LCS server that comprises the serving node indication.

[0039] In an embodiment, a network node is provided that implements a LI-LCS client that is configured to provide a serving node indication to a LCS server to facilitate LALS. The network node includes a processor that is configured to cause the network node to receive the serving node indication from one of a MF / DF2 or a NF wherein the serving node indication comprises an identifier associated with a serving node to which a target device is connected and provide the serving node indication to the LCS server.

[0040] In an embodiment, a computer program is provided that includes instructions which, when executed on at least one processor, cause the processor to carry out the above methods. A carrier containing the computer program is also provided, where thecarrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.

[0041] An advantage provided by the techniques in the present disclosures is that the method exploits the information available from the network to provide a hint to the positioning system about the serving node that is serving the inbound roamer target device so as to avoid the use of the broadcast mechanism which is highly time / resource consuming and in addition is more detectable for fraudulent usage by the not authorized personnel, which is against the main LI requirements.Brief Description of the Drawings

[0042] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0043] Figure 1 is a block diagram of an exemplary Lawful Access Location Services (LALS) architecture according to one or more embodiments of the present disclosure;

[0044] Figure 2 is a block diagram of an exemplary LALS architecture with a Location Triggering Function (LTF) in a Network Function (NF) according to one or more embodiments of the present disclosure;

[0001] Figure 3 is a block diagram of an exemplary LALS architecture with a LTF in a Mediation and Delivery Function (MF / DF2) according to one or more embodiments of the present disclosure;

[0002] Figure 4 is a block diagram of an exemplary LALS architecture with optional LTFs according to one or more embodiments of the present disclosure;

[0003] Figure 5 is a message sequence chart of an embodiment for on-demand and periodical positioning according to one or more embodiments of the present disclosure;

[0004] Figure 6 is a message sequence chart of an embodiment for event based positioning with an LTF in an MF / DF2 according to one or more embodiments of the present disclosure;

[0005] Figure 7 is a message sequence chart of an embodiment for event based positioning with an LTF in an NF according to one or more embodiments of the present disclosure;

[0006] Figure 8 illustrates one example of a cellular communications system according to some embodiments of the present disclosure;

[0007] Figure 9 is a schematic block diagram of network node according to some embodiments of the present disclosure;

[0008] Figure 10 is a schematic block diagram that illustrates a virtualized embodiment of the network node of Figure 11 according to some embodiments of the present disclosure; and

[0009] Figure 11 is a schematic block diagram of the network node of Figure 9 according to some other embodiments of the present disclosure.Detailed Description

[0045] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0046] Network Node: As used herein, a "network node" is any type of node in a Communication Service Provider network or any node that implements a core network function. Some examples of a core network node include, e.g., an Lawful Intercept (LI) Location Services (LCS) client, LCS server, Mediation and Delivery Function (MF / DF2), Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing an Access and Mobility Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

[0047] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a Third Generation Partnership Project (3GPP) network, aMachine Type Communication (MTC) device, and an Internet of Things (loT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The wireless communication device may be a portable, handheld, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and / or data via a wireless connection.

[0048] The present disclosure provides a method for providing an indication to an Location Services (LCS) server about an identity of a serving node to which the target device is connected to in so that the LCS server does not broadcast the location request to all the Access and Mobility Functions (AMFs) or Mobility Management Entities (MMEs) of the network in order to determine the location of the target device. The method includes receiving a serving node indication from one of a Mediation and Delivery Function (MF / DF2) or a Network Function (NF) where the serving node indication comprises an identifier associated with a serving node to which the target device is connected. Then the method includes providing the serving node indication to the LCS server.

[0049] The current LI standard specification (3GPP TS 33.127 V18.3.0 (2023-03)) clearly states that for inbound roaming targets, the Visited Public Land Mobile Network (VPLMN) LCS functional entities fulfilling LALS requests, by default, shall not communicate with the target's Home Public Land Mobile Network (HPLMN), as it may cause detectability issues, i.e., target of interception in the visited network country are visible in the home network country.

[0050] The visited Gateway Mobile Location Center (GMLC) shall be able to determine the serving AMF / MME from which it can acquire the inbound roaming target's location by broadcasting the location request to all the AMF / MME of the VPLMN. If the visited GMLC has knowledge of the last AMF / MME serving the target UE, it may use that one in the first attempt.

[0051] The above broadcast approach has several disadvantages compared to the direct contact with the actual serving node of the inbound roaming target.• overloaded network signaling., with large consumption of hardware resources, like processor, memory;• delay in determining the positioning of the target, especially in case of large networks with many potentials serving nodes;• additional delays may be caused in case serving nodes are visited one after the other; and• most importantly, detectability issues: if network operation personnel observe frequent positioning request for the same target on every serving node, it can be easily deduced that it is due to Lawful Intercept, especially if the broadcasted target belongs to a foreign network.

[0052] The proposed solution disclosed herein introduces more efficient and less time I signaling consuming mechanisms to execute the international inbound roamers, by overcoming the need for the GMLC to send the location request to all the AMF / MME of the VPLMN to determine the serving AMF / MME from which it can acquire the inbound roaming target's location.

[0053] Furthermore, an advantage provided by the proposed solution includes using the information available from the network to provide a hint to the positioning system about the Network Function serving the inbound roamer target so avoiding the use of broadcast mechanism which is highly time / resource consuming and in addition to that is more detectable for fraudulent usage by the not authorized personnel, which is against the main LI requirements.

[0054] The proposed solution is based on an information element, a Serving Node Indication, which can be provided to the LCS server via the LI-LCS client as a hint about the serving node where the target is connected at the time of the positioning request.

[0055] It is to be appreciated that the LCS server as referred to herein may be a GMLC in some embodiments, but for simplicity, is just referred to as LCS server 112 herein.

[0056] Figure 4 is a block diagram of an exemplary LALS architecture with optional LTFs according to one or more embodiments of the present disclosure.

[0057] Figure 4 shows the enhanced architecture for LALS where the LI-LCS client 110 provides the target's location and associated information towards the MF / DF2 108 over the LI_X2 interface as per the Administration Function (ADMF) 106 request for target positioning delivered over LI_X1 interface. In the exemplary architecture shown in Figure 4, the LTF 206 could optionally be located at the NF 202 (alongside the Intercept Related Information (IRI) Point of Intercept (POI)) or in the MF / DF2 108. Themessage sequence charts in Figures 5-7 can be interpreted in view of the exemplary architecture in Figure 4. Figure 4 also depicts the service nodes 402-402n to which one of the service nodes is communicably connected or associated with target device 404. The serving node 402 to which the target device 404 is communicably connected can be, for example, an AMF or MME. The LCS server 112, based on serving node indication received from the LI-LCS client 110, can directly send the Location Request to the serving node 402 to which the target device 404 is communicably connected, rather than broadcasting the Location Request to all of the serving nodes, thus complying with LI and LALS requirements.

[0058] Figure 5 is a message sequence chart of an embodiment for on-demand and periodical positioning according to one or more embodiments of the present disclosure.

[0059] Based on a warrant for an interception on the target device 404 received from a Law Enforcement Agency (LEA) that specifies whether immediate provisioning or periodical provisioning is being requested, the ADMF 106 can activate the LI process for the target device 404 at the NF 202 at step 502.

[0060] At step 504, the NF 202 can provide to the MF / DF2 108, the serving node indication associated with the target device 404, where the serving node indication can include a latest serving node name (e.g., name of an AMF / MME or other core network node to which the target device 404 is connected), known target identities, any occurrence of events relating to the target, e.g., network attach, connection, ... is reported by the involved NF 202 to MF / DF2 108 via the X2 connection including the known target identities (Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI)), the time stamp and any other relevant access network data. In an embodiment, the serving node indication could be part of a Request / Modify for Location Provisioning.

[0061] At step 506, the MF / DF2 108 can send the serving node indication to the LI- LCS client 110 over the Le connection.

[0062] At step 508, the LI-LCS client 110 can send the received serving node indication the LCS server 112. In one embodiment, the LI-LCS client 110 sends the Serving Node Indication to the LCS Server 112 as soon as it is received from the MF / DF2 108 without storing it. In another embodiment, the LI-LCS client 110 can temporarily store (e.g., step 510) and keeps the Serving Node Indication. Such data isthen delivered to the LCS Server 112 by means of a new message just before a Location Immediate Request to the LCS server 112 is sent. In other embodiments, the Serving Node Indication is sent with the Location Immediate Request. Additionally, it is to be appreciated that the Location Immediate Request referred to here throughout, can be a Standard Location Immediate Request (SLIR) that is part of the Mobile Location Protocol (MLP) specification.

[0063] In an embodiment, the LEA can require the Immediate Positioning for the target of interception. This can occur any time during the life cycle of a warrant.

[0064] In an embodiment, the request for immediate location provision is delivered immediately by ADMF 106 to the LI-LCS client 110 over the LI_X1 interface. Instead, in case of periodical positioning, ADMF 106 sends the request of immediate location provision to the LI-LCS client 110 according to the scheduled time for the given target e.g., at step 512).

[0065] At steps 514 and 516, in response to receive the request for location provisioning from the ADMF 106, the LI-LCS client 110 can send the serving node indication (including whatever updates to the serving node indication may have been received from the MF / DF2 108) to the LCS server 112 (step 514) then subsequently send the Location Request to the LCS server 112 at step 516, both the serving node indication and the Location Request being sent over the Le interface. In an embodiment, the serving node indication at step 514 can be sent with the Location request (e.g., the SLIR) at step 516.

[0066] At step 518, the LCS server 112 can report back the location to the LI-LCS client 110, which can then report it to the MF / DF2 108 as xIRI over LI_X2 connection at step 520. The MF / DF2 108 can then generate and deliver the IRI messages based on the received xIRI to the LEMF 104 over the LI_H2 connection.

[0067] Figure 6 is a message sequence chart of an embodiment for event based positioning with an LTF in an MF / DF2 according to one or more embodiments of the present disclosure.

[0068] Based on a warrant for an interception on the target device 404 received from a LEA that specifies whether immediate provisioning or periodical provisioning is being requested, the ADMF 106 can provision the target interception on the NF 202 and the LTF 206 activate the LI process for the target device 404 at the NF 202 and the MF / DF2 108 at step 502.

[0069] At step 504, the NF 202 can provide to the LTF 206 at the MF / DF2 108, the serving node indication associated with the target device 404, where the serving node indication can include a latest serving node name (e.g., name of an AMF / MME or other core network node to which the target device 404 is connected), known target identities, any occurrence of events relating to the target, e.g., network attach, connection, ... is reported by the involved NF 202 to MF / DF2 108 via the X2 connection including the known target identities (Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI)), the time stamp and any other relevant access network data.

[0070] At step 602, if the received LI_X2 events from the NF 202 in step 504, corresponds to one of the events configured for triggered positioning, MF / DF2 108 sends the request for immediate location provisioning to the LI-LCS client 110 over the LI_T2 interface. In an embodiment the request for immediate location provisioning can also embed the serving node indication. At step 60, either before or in response to step 602, the MF / DF2 108 can also provide the serving node indication to the LI-LCS client 110 over the LI_X2 interface.

[0071] Upon receiving the request, at step 606, the LI-LCS client 110 initiates a Location Immediate Request to the LCS Server 112 supporting LALS over the Le interface, and at step 608, the LI-LCS client 110 can also provide the serving node indication to the LCS server 112. In an embodiment, the serving node indication at step 608 is sent with the Location request (e.g., the SLIR) at step 606.

[0072] At step 518, the LCS server 112 can report back the location to the LI-LCS client 110, which can then report it to the MF / DF2 108 as xIRI over LI_X2 connection at step 520. The MF / DF2 108 can then generate and deliver the IRI messages based on the received xIRI to the LEMF 104 over the LI_H2 connection.

[0073] Figure 7 is a message sequence chart of an embodiment for event based positioning with an LTF in an NF according to one or more embodiments of the present disclosure.

[0074] Based on a warrant for an interception on the target device 404 received from a Law Enforcement Agency (LEA) that specifies whether immediate provisioning or periodical provisioning is being requested, the ADMF 106 can provision the targetinterception on the NF 202 and the LTF 206 activate the LI process for the target device 404 at the NF 202 at step 502.

[0075] At step 702, the LTF 206 can provide a request for location provisioning to the LI-LCS client 110 over the LI-T2 interface in response to detecting a triggering event by the target device 404 (e.g., if the received LI_X2 events corresponds to one of the events configured for triggered positioning). The request for location provisioning can also optionally include the serving node indication.

[0076] At step 704, the NF 202 and LTF 206 can provide to the LI-LCS client 110, the serving node indication associated with the target device 404, where the serving node indication can include a latest serving node name (e.g., name of an AMF / MME or other core network node to which the target device 404 is connected), known target identities, any occurrence of events relating to the target, e.g., network attach, connection, ... via the X2 connection including the known target identities (Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Subscriber Identity (IMSI), International Mobile Equipment Identity (IMEI)), the time stamp and any other relevant access network data.

[0077] Upon receiving the request, at step 706, the LI-LCS client 110 initiates a Location Immediate Request to the LCS Server 112 supporting LALS over the Le interface, and at step 708, the LI-LCS client 110 can also provide the serving node indication to the LCS server 112. In an embodiment, the serving node indication at step 708 is sent with the Location request (e.g., the SLIR) at step 706.

[0078] At step 518, the LCS server 112 can report back the location to the LI-LCS client 110, which can then report it to the MF / DF2 108 as xIRI over LI_X2 connection at step 520. The MF / DF2 108 can then generate and deliver the IRI messages based on the received xIRI to the LEMF 104 over the LI_H2 connection.

[0079] In an embodiment, one additional impact on the ETSI TS 103 221-2 - Lawful Interception (LI); Internal Network Interfaces; Part 2: X2 / X3 is related to the format of the NFID, Network Function ID field. To be aligned with the Open Mobile Alliance (OMA) Mobile Location Protocol (MLP), the format of the Network Function Identifier (NFID) shall be the same of what is currently available on the OMA MLP to transport the target_serving_node allowed elements.• E.g., amf_name, mme_name• with format: Char String• Defined values: Fully Qualified Domain Name (FQDN)

[0080] Figure 8 illustrates one example of a cellular communications system 800 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 800 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC) or an Evolved Packet System (EPS) including an Evolved Universal Terrestrial RAN (E-UTRAN) and an Evolved Packet Core (EPC). In this example, the RAN includes base stations 802-1 and 802-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to the 5GC) and in the EPS include eNBs, controlling corresponding (macro) cells 804-1 and 804-2. The base stations 802- 1 and 802-2 are generally referred to herein collectively as base stations 802 and individually as base station 802. Likewise, the (macro) cells 804-1 and 804-2 are generally referred to herein collectively as (macro) cells 804 and individually as (macro) cell 804. The RAN may also include a number of low power nodes 806-1 through 806-4 controlling corresponding small cells 808-1 through 808-4. The low power nodes 806-1 through 806-4 can be small base stations (such as pico or femto base stations) or RRHs, or the like. Notably, while not illustrated, one or more of the small cells 808-1 through 808-4 may alternatively be provided by the base stations 802. The low power nodes 806-1 through 806-4 are generally referred to herein collectively as low power nodes 806 and individually as low power node 806. Likewise, the small cells 808-1 through 808-4 are generally referred to herein collectively as small cells 808 and individually as small cell 808. The cellular communications system 800 also includes a core network 810, which in the 5G System (5GS) is referred to as the 5GC. The base stations 802 (and optionally the low power nodes 806) are connected to the core network 810.

[0081] The core network 810 can include the network node 1100 that implements the LI-LCS client 110 and / or MF / DF2 device 108, or LCS Server 112 that are disclosed herein, and provide the functionality described of providing a serving node indication to facilitate LALS.

[0082] The base stations 802 and the low power nodes 806 provide service to wireless communication devices 812-1 through 812-5 in the corresponding cells 804 and 808. The wireless communication devices 812-1 through 812-5 are generally referred to herein collectively as wireless communication devices 812 and individually as wirelesscommunication device 812. In the following description, the wireless communication devices 812 are oftentimes UEs, but the present disclosure is not limited thereto.

[0083] Figure 9 is a schematic block diagram of a network node 900 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 900 may be, for example, a network node that implements all or part of the functionality LI-LCS client 110 and / or MF / DF2 device 108, or LCS Server 112 as described herein. As illustrated, the network node 900 includes a control system 902 that includes one or more processors 904 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and / or the like), memory / computer readable storage medium 906, and a network interface 908. The one or more processors 904 are also referred to herein as processing circuitry.

[0084] The one or more processors 904 operate to provide one or more functions of a radio access node 900 as described herein. In some embodiments, the function(s) are implemented in one or more computer programs 910 that are stored, e.g., in the memory 906 and executed by the one or more processors 904.

[0085] Figure 10 is a schematic block diagram that illustrates a virtualized embodiment of the network node 900 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. Further, other types of network nodes may have similar virtualized architectures. Again, optional features are represented by dashed boxes.

[0086] As used herein, a "virtualized" network node is an implementation of the network node 900 in which at least a portion of the functionality of the network node 900 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the network node 900 may include the control system 902 and / or the one or more radio units 910, as described above. The control system 902 may be connected to the radio unit(s) 910 via, for example, an optical cable or the like. The network node 900 includes one or more processing nodes 1000 coupled to or included as part of a network(s) 1002. If present, the control system 902 or the radio unit(s) are connected to the processing node(s) 1000 via the network 1002. Each processing node 1000 includes one or more processors 1004 (e.g., CPUs, ASICs, FPGAs, and / or the like), memory / computer readable storage medium 1006, and a network interface 1008.

[0087] In this example, functions 1010 of the network node 900 described herein are implemented at the one or more processing nodes 1000 or distributed across the one or more processing nodes 1000 and the control system 902 and / or the radio unit(s) 910 in any desired manner. In some particular embodiments, some or all of the functions 1010 of the network node 900 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 1000. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 1000 and the control system 902 is used in order to carry out at least some of the desired functions 1010. Notably, in some embodiments, the control system 902 may not be included, in which case the radio unit(s) 910 communicate directly with the processing node(s) 1000 via an appropriate network interface(s).

[0088] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of network node 900 or a node (e.g., a processing node 1000) implementing one or more of the functions 1010 of the network node 900 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0089] Figure 11 is a schematic block diagram of the network node 900 according to some other embodiments of the present disclosure. The network node 900 includes one or more modules of the LI-LCS client 110 which is implemented in software. The module(s) LI-LCS client 110 provides the functionality of the network node 900 described herein. This discussion is equally applicable to the processing node 1000 of Figure 10 where the module LI-LCS client 110 may be implemented at one of the processing nodes 1000 or distributed across multiple processing nodes 1000 and / or distributed across the processing node(s) 1000 and the control system 1102.

[0090] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry,which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

[0091] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0092] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

Claims1. A method for providing a serving node indication to a Location Services, LCS, server (112) to facilitate Lawful Access Location Services, LALS, performed by a Lawful Intercept Location Services, LI-LCS, client (110), the method comprising: receiving (506, 604, 704) the serving node indication from one of a Mediation and Delivery Function, MF / DF2, (108) or a Network Function, NF, (202) wherein the serving node indication comprises an identifier associated with a serving node (402) to which a target device (404) is connected; and providing (508, 514, 608, 708) the serving node indication to the LCS server (112).

2. The method of claim 1, wherein the serving node indication is received from the MF / DF2 (108).

3. The method of claim 1, further comprising: storing (510) the serving node indication; and providing (514) the serving node indication to the LCS server (112) prior to providing a location request message to the LCS server (112).

4. The method of claim 3, wherein the providing the location request message to the LCS server (112) is in response to receiving a request for location provisioning from an Administrative Function, ADMF (106).

5. The method of claim 4, further comprising: receiving (512) the request for location provisioning from the ADMF (106) at periodic intervals.

6. The method of any of claims 1 to 3, wherein the providing the serving node indication to the LCS server (112) is in response to a trigger event occurring.

7. The method of claim 4, further comprising:receiving (602, 702) an indication of the trigger event occurring from a Location Triggering Function, LTF, (206) at the MF / DF2 (108) or the NF (202).

8. The method of any of claims 1 to 7, further comprising: receiving (506, 604, 704) updated serving node indications from the MF / DF2 (108) or the NF (202) in response to the target device (404) connecting to a different serving node (402).

9. The method of claim 8, wherein the providing the serving node indication to the LCS server (112) comprises providing a latest serving node indication to the LCS server (112).

10. The method of any of claims 1 to 9, further comprising: receiving (518) from the LCS server (112), location information associated with the target device (404); and providing (520) to the MF / DF2 (108), the location information.

11. The method of any of claims 1 to 10, further comprising: providing (516, 606, 706) a Location Immediate Request to the LCS server (112) that comprises the serving node indication.

12. A network node (900) that implements a Lawful Intercept Location Services, LI- LCS, client (110) that is configured to provide a serving node indication to a Location Services, LCS, server (112) to facilitate Lawful Access Location Services, LALS, the network node (900) comprising a processor (904) configured to cause the network node (900) to: receive (506, 604, 704) the serving node indication from one of a Mediation and Delivery Function, MF / DF2, (108) or a Network Function, NF, (202) wherein the serving node indication comprises an identifier associated with a serving node (402) to which a target device (404) is connected; and provide (508, 514, 608, 708) the serving node indication to the LCS server (112).

13. The network node of claim 12, wherein the serving node indication is received from the MF / DF2 (108).

14. The network node of claim 12, wherein the processor (904) is further configured to: store (510) the serving node indication; and provide (514) the serving node indication to the LCS server (112) prior to providing a location request message to the LCS server (112).

15. The network node of claim 14, wherein the providing the location request message to the LCS server (112) is in response to receiving a request for location provisioning from an Administrative Function, ADMF (106).

16. The network node of claim 15, wherein the processor (904) is further configured to: receive (512) the request for location provisioning from the ADMF (106) at periodic intervals.

17. The network node of any of claims 12 to 14, wherein the providing the serving node indication to the LCS server (112) is in response to a trigger event occurring.

18. The network node of claim 15, wherein the processor (904) is further configured to: receive (602, 702) an indication of the trigger event occurring from a Location Triggering Function, LTF, (206) at the MF / DF2 (108) or the NF (202).

19. The network node of any of claims 12 to 18, wherein the processor (904) is further configured to: receive (506, 604, 704) updated serving node indications from the MF / DF2 (108) or the NF (202) in response to the target device (404) connecting to a different serving node (402).

20. The network node of claim 19, wherein the providing the serving node indication to the LCS server (112) comprises providing a latest serving node indication to the LCS server (112).

21. The network node of any of claims 12 to 20, wherein the processor (904) is further configured to: receive (518) from the LCS server (112), location information associated with the target device (404); and provide (520) to the MF / DF2 (108), the location information.

22. The network node of any of claims 12 to 21, wherein the processor (904) is further configured to: provide (516, 606, 706) a Location Immediate Request to the LCS server (112) that comprises the serving node indication.

23. A computer program (910) comprising instructions which, when executed on at least one processor (904), cause the processor (904) to carry out the method according to any of claims 1 to 11.

24. A carrier containing the computer program (910) of claim 23, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (906).

Images