AMF secondary data collection for LMF
Patent Information
- Application Number
- KR1020267022520
- Authority / Receiving Office
- KR · KR
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-01-11
- Publication Date
- 2026-09-09
Smart Images
Figure PCT00003_ABST
Abstract
Description
Technology Field
[0001] The present disclosure relates to wireless communication, and more specifically to an apparatus for performing a location management function (LMF), an apparatus and methods for performing an access and mobility management function (AMF), and a computer-readable medium for collecting AMF auxiliary data for the LMF. Background Technology
[0002] A wireless communication system may include one or more network communication devices, such as base stations, which may be otherwise known by eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Each network communication device, such as a base station, may support wireless communication with one or more user communication devices, such as user equipment (UEs) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, etc.)) or frequency resources (e.g., subcarriers, carriers). Additionally, a wireless communication system may support wireless communication through various wireless access technologies, including third-generation (3G) wireless access technology, fourth-generation (4G) wireless access technology, and fifth-generation (5G) wireless access technology, and other suitable wireless access technologies beyond 5G, particularly sixth-generation (6G) wireless access technology.
[0003] In Rel 19, it will be supported for a location management function (LMF) to determine the UE location using an artificial intelligence (AI) model operating on the LMF side with inputs (e.g., measurements or auxiliary information) collected from the UE or gNB. In some scenarios, the LMF may train the LMF-side model itself, which will require the LMF to collect training data (e.g., actual UE location and associated measurements / auxiliary information) from the UE or gNB.
[0004] The present disclosure relates to an apparatus for performing a location management function (LMF), an apparatus and methods for performing an access and mobility management function (AMF), and a computer-readable medium for AMF-assisted data collection for the LMF. According to embodiments of the present disclosure, the LMF can determine appropriate UEs for data collection with the assistance of the AMF.
[0005] In a first embodiment, a device for performing a location management function (LMF) is provided, the device comprises at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to cause the device to transmit a first message to an access and mobility management function (AMF) requesting information related to a user equipment (UE) that meets one or more criteria; to receive a second message from the AMF containing information related to a list of UEs that meet one or more criteria; and to transmit a third message to at least one of the UEs requesting the at least one UE to report data.
[0006] In a second embodiment, an apparatus for performing an access and mobility management function (AMF) is provided, the apparatus comprises at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to cause the apparatus to receive a first message requesting information related to a user equipment (UE) that meets one or more criteria from a location management function (LMF); and to transmit to the LMF a second message containing information related to a list of UEs that meet one or more criteria in order to report data to the LMF.
[0007] In a third embodiment, a method for performing a location management function (LMF) is provided, the method comprising: transmitting a first message to an access and mobility management function (AMF) requesting information related to a user device (UE) that meets one or more criteria; receiving from the AMF a second message containing information related to a list of UEs that meet one or more criteria; and transmitting a third message to at least one of the UEs requesting at least one UE to report data.
[0008] In a fourth embodiment, a method for performing an access and mobility management function (AMF) is provided, the method comprising: receiving a first message from a location management function (LMF) requesting information related to a user device (UE) that meets one or more criteria; and transmitting a second message to the LMF containing information related to a list of UEs that meet one or more criteria in order to report data to the LMF.
[0009] In a fifth embodiment, a computer-readable medium storing instructions is provided, and when the instructions are executed by a processor of the device, the device enables the device to perform a method according to any one of the third and fourth embodiments of the present disclosure.
[0010] In the methods described herein, the apparatus for performing LMF, and some implementations of the apparatus for performing AMF, one or more criteria include at least one of the following: the UE is a positioning reference unit (PRU); the UE is capable of UE-based positioning methods; the UE is capable of LTE positioning protocol (LPP); the UE is of a mobility type; or the UE is within a region of interest.
[0011] In the methods described herein, the apparatus for performing LMF, and some implementations of the apparatus for performing AMF, the information relating to the list of UEs includes: a UE identity (ID); a serving cell ID of the UE; information regarding whether the UE is a PRU; whether the UE is capable of a UE-based positioning method and its corresponding positioning method; whether the UE is capable of LPP; or at least one of the mobility type of the UE.
[0012] In the methods, apparatus for performing LMF, and some implementations of the apparatus for performing AMF described herein, the UE ID is a dedicated ID or subscription persistent identifier (SUPI) assigned by the AMF.
[0013] In the methods, apparatus for performing LMF, and some implementations of apparatus for performing AMF described herein, the serving cell ID of the UE includes a first serving cell ID of a primary cell at a master random access network (RAN) node and a second serving cell ID of a primary cell at a secondary RAN node.
[0014] In the methods, apparatus for performing LMF, and some implementations of the apparatus for performing AMF described herein, the apparatus for performing LMF transmits a fourth message to the AMF requesting the transmission of a third message to at least one UE.
[0015] In the methods, apparatus for performing LMF, and some implementations of apparatus for performing AMF described herein, the first message is a subscription request message for subscribing to information related to a UE that meets one or more criteria; and the second message is a notification message containing information related to a list of UEs that meet one or more criteria.
[0016] In the methods, apparatus for performing LMF, and some implementations of apparatus for performing AMF described herein, the first message and the second message are based on the service of the AMF for event exposure.
[0017] In the methods, apparatus for performing LMF, and some embodiments of apparatus for performing AMF described herein, the list of UEs comprises one of the following: a list of all UEs that meet the criteria; a list of new UEs that meet the criteria; or a list of old UEs that no longer meet the criteria.
[0018] In the methods, apparatus for performing LMF, and some implementations of the apparatus for performing AMF described herein, the first message and the second message are based on a dedicated AMF service of a one-time request / response method.
[0019] In the methods described herein, the apparatus for performing LMF, and some implementations of the apparatus for performing AMF, the third message comprises a configuration related to determining actual data; a reference signal configuration for measurements; an indicator of whether the UE should report its current serving cell; periodicity of the report; or at least one of a region of interest.
[0020] In the methods, apparatus for performing LMF, and some implementations of the apparatus for performing AMF described herein, the apparatus for performing AMF receives a fourth message from the LMF requesting the transmission of a third message to at least one UE.
[0021] In the methods, apparatus for performing LMF, and some implementations of the apparatus for performing AMF described herein, the apparatus for performing AMF triggers a network (NW) trigger service request for a list of UEs in a radio resource control (RRC) idle state. Brief explanation of the drawing
[0022] FIG. 1 illustrates an example of a wireless communication system in which some embodiments of the present disclosure may be implemented. FIG. 2 illustrates an example of a process flow in which an LMF requests data from a UE with the help of an AMF, according to some exemplary embodiments of the present disclosure. FIG. 3 illustrates an example of a process flow in which an LMF requests data from a UE with the help of an AMF through a subscription / notification method, according to some exemplary embodiments of the present disclosure. FIG. 4 illustrates an example of a process flow in which an LMF requests data from a UE with the help of an AMF through a one-time request / response method, according to some exemplary embodiments of the present disclosure. FIG. 5 illustrates an example of a device suitable for implementing some embodiments of the present disclosure. FIG. 6 illustrates an example of a processor suitable for implementing some embodiments of the present disclosure. FIG. 7 illustrates a flowchart of a method for performing LMF according to embodiments of the present disclosure. FIG. 8 illustrates a flowchart of a method for performing AMF according to embodiments of the present disclosure. Throughout the drawings, identical or similar reference numbers represent identical or similar elements. Specific details for implementing the invention
[0023] The principles of the present disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and do not imply any limitation to the scope of the present disclosure, but are intended to help a person skilled in the art understand and implement the present disclosure. The disclosures described herein may be implemented in various ways other than those described below. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as generally understood by a person skilled in the art to which the present disclosure pertains.
[0024] References to “one embodiment,” “exemplary embodiment,” “one embodiment,” “some embodiments,” etc. in this disclosure indicate that while the described embodiment(s) may include specific features, structures, or characteristics, not all embodiments are required to include specific features, structures, or characteristics. Furthermore, these phrases do not necessarily refer to the same embodiment(s). In addition, when specific features, structures, or characteristics are described in relation to one embodiment, it is considered to be within the knowledge of a person skilled in the art to have an effect on such features, structures, or characteristics in relation to other embodiments, whether explicitly described or not.
[0025] It should be understood that while terms such as "first" and "second" may be used in this specification to describe various elements, these elements are not to be limited by these terms. These terms are used solely to distinguish one element from another. For example, without departing from the scope of the embodiments, the first element may also be referred to as the second element, and similarly, the second element may also be referred to as the first element. As used in this specification, the term "and / or" includes any and all combinations of one or more of the listed terms. In some examples, values, procedures, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It will be understood that these descriptions are intended to indicate that a selection may be made among many functional alternatives used, and that such selection does not need to be better, smaller, higher, or otherwise more desirable than other selections.
[0026] The terms used herein are intended only to describe specific embodiments and are not intended to limit the embodiments. As used herein, singular forms (“a,” “an,” and “the”) are intended to include plural forms unless the context clearly indicates otherwise. It will be further understood that when used herein, the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” specify the presence of the mentioned features, elements, components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “comprising” and variations thereof should be read as open terms meaning “comprising, but not limited thereto.” The term “based on” should be read as “at least partially based.” The terms “one embodiment” and “one embodiment” should be read as “at least one embodiment.” The term "other embodiments" should be read as "at least one other embodiment." The use of expressions such as "A and / or B" may mean "only A," "only B," or "both A and B." Other explicit and implicit definitions may be included below.
[0027] In Rel-19, support will be provided for an LMF to determine the UE location using an AI model operating on the LMF side with inputs (e.g., measurements or auxiliary information) collected from the UE or gNB. In one scenario, the LMF can train its own LMF-side model, which will require the LMF to collect training data (e.g., actual UE location data and associated measurements / auxiliary information) from the UE or gNB.
[0028] However, in legacy procedures for location services, the LMF will follow commands / requests based on the AMF instead of autonomously initiating location services and associated LTE Positioning Protocol (LPP) session procedures. For example, in the case of a Mobile Incoming Location Request (MT-LR), the AMF receives a location service request from a Location Service (LCS) client for the relevant UE(s), and then the AMF sends an Nlmf_Location_DetermineLocation message to the LMF requesting UE location determination, where the UE is identified by an LCS correlation identifier; in the case of a Mobile Outgoing Location Request (MT-LR), the AMF receives an MO-LR request from the UE, and then the AMF sends an Nlmf_Location_DetermineLocation message to the LMF requesting UE location determination, where the UE is identified by an LCS correlation identifier. In other words, the LMF does not know in advance which UEs are present there, for example, within the region of interest, nor does it know which UE the LMF should initiate an LPP session toward and begin data collection. Furthermore, the LMF does not know detailed information about the UE (e.g., Subscription Persistent Identifier (SUPI), which cell UE is connected, etc.), and the LMF distinguishes different UEs based solely on the LCS correlation identifier, which is used for correlation purposes as the name suggests. Therefore, methods are required to enable the AMF to assist the LMF in selecting appropriate UEs to establish LPP session(s) and initiate data collection for AI operations.
[0029] With this in mind, embodiments of the present disclosure provide solutions for AMF auxiliary data collection for an LMF. In an exemplary embodiment, the LMF may transmit a request to the AMF for information regarding UEs that meet specific criteria. Upon receipt of the request, the AMF may discover UEs that meet the criteria and transmit information regarding the UEs to the LMF. The LMF may select at least one of the UEs identified by the AMF and request the selected UE to report data. Aspects of the present disclosure are described in the context of a wireless communication system.
[0030] In an exemplary scenario, when an LMF wishes to train / monitor an AI / ML model capable of estimating UE locations under specific applicability conditions, he / she will initiate LPP procedures toward target UEs and collect data (e.g., actual UE locations and related measurement results) for training / monitoring the AI / ML model. To do so, the LMF may require assistance from the AMF to determine which UEs are present there and satisfy the applicability conditions of the AI / ML model. Subsequently, the LMF may initiate LPP procedures toward those specific UEs for data collection. It is worth noting that embodiments of this disclosure are also applicable to scenarios different from AI / ML model data collection.
[0031] FIG. 1 illustrates an example of a wireless communication system (100) in which some embodiments of the present disclosure may be implemented. The wireless communication system (100) may include one or more network entities (102) (also referred to as network equipment (NE)), one or more UEs (104), a core network (106), and a packet data network (108). The wireless communication system (100) may support various wireless access technologies. In some implementations, the wireless communication system (100) may be a 4G network, such as an LTE network or an LTE-A (LTE-Advanced) network. In some other implementations, the wireless communication system (100) may be a 5G network, such as an NR network. In other implementations, the wireless communication system (100) may be a combination of a 4G network and a 5G network, or other suitable wireless access technology including IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system (100) may support wireless access technologies beyond 5G. Additionally, the wireless communication system (100) may support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).
[0032] One or more network entities (102) may be distributed across a geographical area to form a wireless communication system (100). One or more of the network entities (102) described herein may be network nodes, base stations, network elements, wireless access networks (RAN), base transceiver stations, access points, NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other appropriate terms, or may include or be referred to as such. Network entities (102) and UEs (104) may communicate through a communication link (110) which may be wireless or wired connection. For example, network entities (102) and UEs (104) may perform wireless communication (e.g., receive signaling, transmit signaling) through a Uu interface. In a 3GPP non-terrestrial network (NTN), a network entity (102) in the form of a satellite can communicate directly with a UE (104) using an NR / LTE Uu interface. The satellite can be a transparent satellite or a regenerative satellite. In the case of an NTN with a transparent satellite, a base station on Earth can communicate with the UE via the satellite. In the case of an NTN with a regenerative satellite, the base station can be on board and can communicate directly with the UE.
[0033] A network entity (102) may provide a geographic coverage area (112) in which the network entity (102) can support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs (104) within the geographic coverage area (112). For example, the network entity (102) and the UE (104) may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or more wireless access technologies. In some implementations, the network entity (102) may be mobile and may be, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas (112) associated with the same or different wireless access technologies may overlap, but different geographic coverage areas (112) may be associated with different network entities (102). The information and signals described herein may be represented using any of the various different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0034] One or more UEs (104) may be distributed across the entire geographical area of the wireless communication system (100). The UE (104) may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, the UE (104) may be referred to as a unit, station, terminal, or client, among other examples. Additionally or alternatively, the UE (104) may be referred to as an Internet-of-Things (IoT) device, Internet-of-Everything (IoE) device, or Machine-Type Communication (MTC) device, among other examples. In some implementations, the UE (104) may be stationary within the wireless communication system (100). In some other implementations, the UE (104) may move within the wireless communication system (100).
[0035] One or more UEs (104) may be devices having different forms or different capabilities. Some examples of UEs (104) are illustrated in FIG. 1. As illustrated in FIG. 1, the UE (104) may communicate with various types of devices, such as network entities (102), other UEs (104), or network equipment (e.g., a core network (106), a packet data network (108), a relay device, an integrated access and backhaul (IAB) node, or other network equipment). Additionally, or alternatively, the UE (104) may support communication with other network entities (102) or UEs (104) that can act as relays in the wireless communication system (100).
[0036] The UE (104) may also support direct wireless communication with other UEs (104) via a communication link (114). For example, the UE (104) may support direct wireless communication with other UEs (104) via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular-V2X deployments, the communication link (114) may be referred to as a side link. For example, the UE (104) may support direct wireless communication with other UEs (104) via a PC5 interface.
[0037] A network entity (102) may support communication with a core network (106), other network entities (102), or both. For example, a network entity (102) may interface with the core network (106) through one or more backhaul links (116) (e.g., through S1, N2, N2 or other network interfaces). Network entities (102) may communicate with each other through backhaul links (116) (e.g., through X2, Xn or other network interfaces). In some implementations, network entities (102) may communicate directly with each other (e.g., between network entities (102)). In some other implementations, network entities (102) may communicate with each other or indirectly (e.g., through the core network (106)). In some implementations, one or more network entities (102) may include subcomponents such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs (104) through one or more other access network transmitting entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs). In some implementations, the network entity (102) may include an entity for performing a location management function (LMF).
[0038] In some implementations, the network entity (102) may be configured as a non-aggregated architecture that can be configured to utilize protocol stacks physically or logically distributed between two or more network entities (102), such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., Cloud RAN (C-RAN)). For example, the network entity (102) may include one or more of a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., Near-RT RIC, Non-RT RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.
[0039] The RU may also be referred to as a radio head, smart radio head, remote radio head (RRH), remote radio unit (RRU), or transmit receiving point (TRP). One or more components of network entities (102) within a non-aggregated RAN architecture may be juxtaposed, or one or more components of network entities (102) may be located at distributed locations (e.g., separate physical locations). In some implementations, one or more network entities (102) of a non-aggregated RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0040] The partitioning of functions between the CU, DU, and RU can be flexible and may support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed in the CU, DU, or RU. For example, a partitioning of functions of the protocol stack may be used between the CU and the DU so that the CU can support one or more layers of the protocol stack and the DU can support one or more different layers of the protocol stack. In some implementations, the CU may host higher protocol layer functions (e.g., Layer 3 (L3), Layer 2 (L2)) and signaling (e.g., Radio Resource Control (RRC), Data Adaptation Protocol for Services (SDAP), Packet Data Convergence Protocol (PDCP)). A CU may be connected to one or more DUs or RUs, and one or more DUs or RUs may host lower protocol layers such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Wireless Link Control (RLC) layer, Media Access Control (MAC) layer) functionality and signaling, and each may be controlled at least partially by the CU (160).
[0041] Additionally, or alternatively, a functional partition of the protocol stack may be utilized between the DU and the RU so that the DU can support one or more layers of the protocol stack and the RU can support one or more different layers of the protocol stack. The DU may support one or more different cells (e.g., through one or more RUs). In some implementations, the functional partition between the CU and the DU, or between the DU and the RU, may exist within the protocol layer (e.g., some functions of the protocol layer may be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by a different of the CU, DU, or RU).
[0042] The CU can be functionally further subdivided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via midhaul communication links (e.g., F1, F1-c, F1-u), and the DUs can be connected to one or more RUs via fronthaul communication links (e.g., open fronthaul (FH) interfaces). In some implementations, the midhaul communication links or fronthaul communication links may be implemented according to an interface (e.g., a channel) between layers of the protocol stack supported by each network entity (102) communicating through these communication links.
[0043] The core network (106) may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network (106) may be an advanced packet core (EPC) or 5G core (5GC) that may include a server (117) for performing location management functions (LMF), control plane entities that manage access and mobility (e.g., mobility management entities (MME), access and mobility management functions (AMF)), and user plane entities that route packets or interconnects to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane functions (UPF)). In some implementations, a control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc.), for one or more UEs (104) served by one or more network entities (102) associated with a core network (106). An LMF may be defined in the core network (106) and / or network entity (102) to provide positioning functionality by means of determining the geographic location of the UE (104) based on downlink and uplink positioning radio signals. The packet data network (108) may include an application server (118).
[0044] The core network (106) may communicate with the packet data network (108) through one or more backhaul links (116) (e.g., through S1, N2, N2 or other network interfaces). The packet data network (108) may include an application server (118). In some implementations, one or more UEs (104) may communicate with the application server (118). The UE (104) may establish a session (e.g., a Protocol Data Unit (PDU) session) with the core network (106) through a network entity (102). The core network (106) may route traffic (e.g., control information, data, etc.) between the UE (104) and the application server (118) using the established session (e.g., an established PDU session). A PDU session may be an example of a logical connection between the UE (104) and the core network (106) (e.g., one or more network functions of the core network (106)).
[0045] In a wireless communication system (100), network entities (102) and UEs (104) can perform various operations (e.g., wireless communication) using the resources of the wireless communication system (100) (e.g., time resources (e.g., symbol, slot, subframe, frame, etc.) or frequency resources (e.g., subcarrier, carrier)). In some implementations, network entities (102) and UEs (104) may support different resource structures. For example, network entities (102) and UEs (104) may support different frame structures. In some implementations, e.g., 4G, network entities (102) and UEs (104) may support a single frame structure. In some other implementations, e.g., 5G and among other suitable wireless access technologies, network entities (102) and UEs (104) may support various frame structures (i.e., multiple frame structures). Network entities (102) and UEs (104) can support various frame structures based on one or more numerologies.
[0046] One or more numerologies may be supported in the wireless communication system (100), and the numerologies may include a subcarrier interval and a cyclic prefix. A first numerology (e.g., μ=0) may be associated with a first subcarrier interval (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first numerology (e.g., μ=0) associated with the first subcarrier interval (e.g., 15 kHz) may utilize one slot per subframe. A second numerology (e.g., μ=1) may be associated with a second subcarrier interval (e.g., 30 kHz) and a normal cyclic prefix. A third numerology (e.g., μ=2) may be associated with a third subcarrier interval (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. The fourth numerology (e.g., μ = 3) may be associated with a fourth subcarrier interval (e.g., 120 kHz) and a normal cyclic prefix. The fifth numerology (e.g., μ = 4) may be associated with a fifth subcarrier interval (e.g., 240 kHz) and a normal cyclic prefix.
[0047] Time intervals of a resource (e.g., a communication resource) can be organized according to frames (also referred to as wireless frames). Each frame may have a duration, for example, 10 milliseconds (ms). In some implementations, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a duration, for example, 1ms. In some implementations, each frame may have the same duration. In some implementations, each subframe of a frame may have the same duration.
[0048] Additionally or alternatively, time intervals of a resource (e.g., a communication resource) may be organized according to slots. For example, a subframe may contain a number of (e.g., quantity) slots. The number of slots within each subframe may also depend on one or more numerologies supported by the wireless communication system (100). For example, first, second, third, fourth, and fifth numerologies (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with each subcarrier interval of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may each utilize a single slot per subframe, two slots per subframe, four slots per subframe, eight slots per subframe, and sixteen slots per subframe, respectively. Each slot may contain a number of (e.g., quantity) symbols (e.g., OFDM symbols). In some implementations, the number of slots (e.g., quantity) for a subframe may depend on the numerology. For a normal cyclic prefix, a slot may contain 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier interval), a slot may contain 12 symbols. The relationship between the number of symbols per slot, the number of slots per subframe, and the number of slots per frame for the normal cyclic prefix and the extended cyclic prefix may depend on the numerology. It should be understood that a reference to a first numerology (e.g., μ=0) associated with a first subcarrier interval (e.g., 15 kHz) may be used interchangeably between subframes and slots.
[0049] In a wireless communication system (100), the electromagnetic (EM) spectrum may be divided into various classes, frequency bands, frequency channels, etc. based on frequency or wavelength. For example, the wireless communication system (100) may support one or more operating frequency bands such as frequency range designations FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4 (52.6 GHz - 114.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), and FR5 (114.25 GHz - 300 GHz). In some implementations, network entities (102) and UEs (104) may perform wireless communication through one or more of the operating frequency bands. In some implementations, FR1 may be used by network entities (102) and UEs (104), in particular among other equipment or devices, for cellular communication traffic (e.g., control information, data). In some implementations, FR2 may be used by network entities (102) and UEs (104), in particular among other equipment or devices, for short-range, high data rate capabilities.
[0050] FR1 may be associated with one or more numerologies (e.g., at least three numerologies). For example, FR1 may be associated with a first numerology including a 15 kHz subcarrier interval (e.g., μ=0); a second numerology including a 30 kHz subcarrier interval (e.g., μ=1); and a third numerology including a 60 kHz subcarrier interval (e.g., μ=2). FR2 may be associated with one or more numerologies (e.g., at least two numerologies). For example, FR2 may be associated with a third numerology including a 60 kHz subcarrier interval (e.g., μ=2); and a fourth numerology including a 120 kHz subcarrier interval (e.g., μ=3).
[0051] FIG. 2 illustrates an example of a process flow (200) in which an LMF requests data from a UE with the assistance of an AMF, according to some exemplary embodiments of the present disclosure. The process flow (200) may involve an LMF (201), an AMF (202), and a UE (204). For brevity, network entities (e.g., base stations or gNBs) are omitted in FIG. 2.
[0052] The process flow (200) can be applied to a wireless communication system (100) with reference to FIG. 1, for example, the UE (204) may be any of the UEs (104). The LMF (201) may be in or placed in a server (117) within the core network (106) or in any of the network entities (102). The LMF (201) may be placed in a server (117) within the core network (106) or in any of the network entities (102). The AMF (202) may be placed in a server (117) within the core network (106). It will be understood that the process flow (200) may be applied to other communication scenarios that will not be described in detail.
[0053] In 210, the LMF (201) sends a first message (215) to the AMF (202) requesting information related to a UE that meets one or more criteria. Accordingly, in 220, the AMF (202) receives the first message (215) from the LMF (201).
[0054] The first message may indicate to the AMF (202) the criteria that the UE must satisfy so that the AMF can identify the UE(s) for data collection for the LMF (201). In some embodiments, the criteria may include one or more of the following criteria: the UE is a positioning reference unit (PRU); the UE is capable of UE-based positioning methods such as GNSS (global navigation satellite system), GPS (global positioning system), network-assisted GNSS, NR E-CID (NR enhanced Cell-ID), DL-AoD (downlink-angle of departure), DL-TDOA (downlink-time difference of arrival); the UE is capable of LTE positioning protocol (LPP); the UE is of a mobility type (e.g., static, mobile, or high mobility); or the UE is within a region of interest (e.g., represented by a list of cell IDs or a region ID).
[0055] In 230, the AMF (202) transmits a second message (235) containing information related to a list of UEs to the LMF (201). Thus, in 240, the LMF (201) receives the second message from the AMF (202). In some embodiments, the AMF (202) may identify a list of UEs that meet the criteria indicated by the first message (215) and provide relevant UE information through the second message (235). In some embodiments, the UE information may include at least one of the UE identity (ID); the UE's serving cell ID; information regarding whether the UE is a PRU; whether the UE is capable of a UE-based positioning method and its corresponding positioning method; whether the UE is capable of LPP; or the UE's mobility type. In some embodiments, the AMF (202) may trigger a network (NW) trigger service request for identified and RRC idle UEs.
[0056] After receiving information about UEs that meet the criteria through the second message (235), at 250, the LMF (201) sends a third message (255) to at least one of the UEs to request that at least one UE report data. Thus, at 260, the UE (204) receives the third message (255) from the LMF (201). In some embodiments, before sending the third message, the LMF (201) may perform an LPP session procedure with the UE (204). In the LPP session procedure, the LMF (201) may send a fourth message to request the transmission of the third message to the UE (204), and the LPP message may be conveyed, for example, in the Namf_Communication_N1N2MessageTransfer message.
[0057] The third message may be an LPP message. In some embodiments, the third message (255) may include information regarding reporting configurations, e.g., configurations related to determining actual data, reference signal configurations for measurements; an indicator of whether the UE should report its current serving cell; periodicity of the report; or a region of interest. Subsequently, the UE (204) may report data to the LMF (201) based on the information in the third message (255). In some embodiments, the data reported from the UE (204) to the LMF (201) may include the actual data UE location known by the UE (204) (in the case of a PRU) or determined by other UE positioning methods (e.g., GPS, GNS, etc.). Additionally or alternatively, the reported data may include the measurement results of related reference signals such as SSB, PRS, CSI-RS, etc. Additionally, the reported data may include serving cell information and time information (e.g., expressed by a UTC timestamp, or by SFN / slot / symbol information).
[0058] FIG. 3 illustrates an example of a process flow in which an LMF requests data from a UE with the help of an AMF through a subscription / notification method, according to some exemplary embodiments of the present disclosure. The process flow (300) is an exemplary implementation of the process flow (200) illustrated in FIG. 2.
[0059] In FIG. 3, LMF (201) requests AMF (202) to continuously provide or update UE list information that meets specific criteria, so that such LMF (201) can collect necessary AIML training / monitoring data from such UEs. In some embodiments, LMF (201) may request UE list information from AMF (202) via a subscription request message and receive UE list information or updates to UE list information via a notification message. The subscription request and notification messages may be based on AMF's service for event exposure.
[0060] In steps 1 and 2, the LMF (201) sends a subscription request message (e.g., Namf_EventExposure_Subscribe Request) to the AMF (202) to subscribe to any UE information that meets the criteria. The subscription request message may indicate to the AMF (202) the criteria that include any of the following: the UE is a PRU UE; the UE is capable of standard UE-based positioning methods such as GNSS, GPS, network-assisted GNSS, NR E-CID, DL-AoD, DL-TDOA; the UE is capable of LPP; the type of mobility (e.g., static, mobile, high mobility); or the UE is within a region of interest represented by a list of cell IDs or area ID(s).
[0061] In this case, AMF (202) must notify LMF (201) about updates to the list of UEs that meet the criteria requested in subsequent procedures, for example, using the Namf_EventExposure_Notify service operation. Such a subscription may be defined as a new event ID for AMF (202)'s Namf_EventExposure service. It should be noted that in the subscription request message, LMF (201) does not include any information regarding the UE ID (e.g., SUPI), as LMF (202) does not know it. Table 1 below shows examples of the criteria indicated in the subscription request, along with the event ID of the "UE of interest for data collection."
[0062]
[0063] In step 3, after receiving a subscription request message, the AMF (202) may identify UEs that meet the criteria and provide UE information to the LMF (201) using the Namf_EventExposure_Notify service operation. The UE information may include UE ID(s), which may be a dedicated ID assigned by the AMF itself (e.g., a correlation ID used only for correlation) or a SUPI. Additionally, for each UE ID, the UE information may include, when available based on dual connectivity scenarios, a first serving cell identity of the primary cell at the master RAN node and a second serving cell identity of the primary cell at the secondary RAN node. Furthermore, the UE information may include information regarding whether the UE is capable of UE-based positioning methods such as GNSS, GPS, network-assisted GNSS, NR E-CID, DL-AoD, and DL-TDOA. Additionally, the UE information may include information regarding whether the UE is capable of LPP. Additionally, UE information may include the mobility type of the UE. Optionally, the AMF (202) may autonomously trigger NW trigger service requests for all possible UEs that are identified and in an RRC idle state.
[0064] In steps 4 and 5, after receiving UE information that meets the criteria, LMF (201) can further determine which of them the necessary AI / ML model training / monitoring data should be collected from. Toward such UEs, LMF (201) can trigger an LPP session setup by calling the Namf_Communication_N1N2MessageTransfer service operation toward AMF (202) to request, for example, the transmission of an LPP message to UE (204). In some embodiments, the Namf_Communication_N1N2MessageTransfer message may use the UE ID provided in step 3 to identify the associated UE (204). Optionally, AMF (202) can trigger an NW trigger service request for selected UEs that are in an RRC idle state.
[0065] In step 6, the LMF (201) transmits an LPP message to the UE (204) containing information related to data collection, requesting the UE (204) to report data to the LMF (201). The LPP message may include configurations related to determining actual data, for example, if it is determined by any of UE-based positioning methods such as GNSS, GPS, network-assisted GNSS, NR E-CID, DL-AoD, DL-TDOA. Additionally or alternatively, the LPP message may include reference signal (RS) configurations that the UE must measure (e.g., positioning reference signal (PRS), synchronization signal and PBCH block (SSB), channel state information-RS (CSI-RS)). Additionally or alternatively, the LPP message may include information on whether the UE must report its current serving cell to which the UE is connected. Additionally or alternatively, the LPP message may include periodicity of reporting. Additionally or alternatively, the LPP message may include information about the regions of interest (e.g., a list of cells) where the UE needs to collect and report data when the UE is in the relevant region.
[0066] In steps 7 and 8, the UE (204) may indicate to the gNB (203) regarding an ongoing data collection session, and the gNB (203) may configure the UE (204) as a dedicated radio bearer (e.g., with a lower priority than other regular radio bearers). Then, any subsequent LPP message reporting the necessary data from the UE (204) to the LMF (201) is transmitted by this dedicated radio bearer. In step 9, the UE (204) may report the necessary data to the LMF (201) as configured in step 6. In some embodiments, the data reported from the UE (204) to the LMF (201) may include actual data UE locations known by the UE (204) (if it is a PRU) or determined by other UE positioning methods (e.g., GPS, GNS, etc.). Additionally or alternatively, the reported data may include measurement results of relevant reference signals such as SSB, PRS, CSI-RS, etc. Additionally, the reported data may include serving cell information and time information (e.g., expressed by a UTC timestamp, or by SFN / slot / symbol information).
[0067] In step 10, in the event of any change in the UE list information that meets the criteria, e.g., any UE that no longer meets the criteria or any new UE that meets the criteria, the AMF (202) may transmit the updated UE list and related information as described in step 3. In some embodiments, the updated UE list may be a list of all UEs that meet the criteria, a list of new UEs that meet the criteria, or a list of old UEs that no longer meet the criteria. Based on the updated UE list information, the LMF (201) may decide to initiate LPP sessions for data collection from new UEs and terminate LPP sessions for data collection from old UEs. It should be understood that the subscription request message in step 1 (e.g., Namf_EventExposure_Subscribe Request) may be considered as the first message in FIG. 2, and the notification message in step 3 (e.g., Namf_EventExposure_Notify service operation) may be considered as the second message in FIG. 2.
[0068] FIG. 4 illustrates an example of a process flow in which an LMF requests data from a UE with the help of an AMF through a one-time request / response method, according to some exemplary embodiments of the present disclosure. The process flow (400) is an exemplary implementation of the process flow illustrated in FIG. 2.
[0069] For PRUs or UEs of static mobility type, LMF (201) may request UE list information from AMF (202) in a one-time request / response manner because the UE list information is not expected to change within a short period of time. In some embodiments, a new dedicated AMF service (i.e., Namf_UEInformation service) may be defined, or an existing AMF service may be enhanced to achieve the purpose. In FIG. 4, most details are similar to FIG. 3, except that steps 1 and 2 are based on a dedicated AMF service in a one-time request / response manner, and there is no update step, i.e., step 10 of FIG. 3.
[0070] According to some embodiments discussed with reference to FIGS. 2 to 4, procedures are proposed that enable the LMF to collect data from suitable UEs that meet specific criteria with the help of the AMF.
[0071] FIG. 5 illustrates an example of a device suitable for implementing some embodiments of the present disclosure. The device (500) may be an example of an LMF or AMF as described herein. The device (500) may support wireless or wired communication with one or more network entities (102), UEs (104), or any combination thereof. The device (500) may include components for bidirectional communication, such as a processor (502), memory (504), a transceiver (506), and optionally an I / O controller (508), for transmitting and receiving communication. These components may communicate electronically through one or more interfaces (e.g., a bus) or be combined in other ways (e.g., operablely, communically, functionally, electronically, electrically).
[0072] A processor (502), memory (504), transceiver (506), or various combinations thereof or various components thereof may be examples of means for carrying out various aspects of the present disclosure as described herein. For example, a processor (502), memory (504), transceiver (506), or various combinations thereof or components thereof may support a method for carrying out one or more of the operations described herein.
[0073] In some implementations, the processor (502), memory (504), transceiver (506), or various combinations or components thereof may be implemented in hardware (e.g., as a communication management circuit). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, individual gate or transistor logic, individual hardware components, or any combination thereof, configured as a means to perform or otherwise support the functions described in this disclosure. In some implementations, the processor (502) and the memory (504) coupled with the processor (502) may be configured to perform one or more of the functions described herein (e.g., executing instructions stored in the memory (504) by the processor (502).
[0074] For example, the processor (502) may support wireless or wired communication in the device (500) according to examples as disclosed in this specification. The device (500) may be implemented to perform LMF. The processor (502) may be configured to operate to support means for transmitting a first message to the AMF requesting information related to a UE that meets one or more criteria; means for receiving a second message from the AMF containing information related to a list of UEs that meet one or more criteria; and means for transmitting a third message to at least one UE in the list of UEs requesting at least one UE to report data.
[0075] The device (500) may be implemented to perform AMF. The processor (502) may be configured to operate to support means for receiving a first message requesting information related to a user device (UE) that meets one or more criteria from a location management function (LMF); and means for transmitting a second message to the LMF that includes information related to a list of UEs that meet one or more criteria in order to report data to the LMF.
[0076] The processor (502) may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, an individual gate or transistor logic component, an individual hardware component, or any combination thereof). In some implementations, the processor (502) may be configured to operate a memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor (502). The processor (502) may be configured to execute computer-readable instructions stored in memory (e.g., memory (504)) to enable the device (500) to perform various functions of the present disclosure.
[0077] Memory (504) may include random access memory (RAM) and read-only memory (ROM). Memory (504) may store computer-readable, computer-executable code containing instructions that enable the device (500) to perform various functions described herein when executed by the processor (502). The code may be stored in a non-transient computer-readable medium, such as system memory or other types of memory. In some implementations, the code may not be directly executable by the processor (502), but may enable the computer to perform the functions described herein (e.g., when compiled and executed). In some implementations, memory (504) may include a basic I / O system (BIOS) capable of controlling basic hardware or software operations, such as interactions with peripheral components or devices.
[0078] The I / O controller (508) can manage input and output signals for the device (500). The I / O controller (508) can also manage peripherals that are not integrated into the device (500). In some implementations, the I / O controller (508) may represent a physical connection or port to an external peripheral. In some implementations, the I / O controller (508) may use an operating system such as iOS®, ANDROID®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or other known operating systems. In some implementations, the I / O controller (508) may be implemented as part of a processor such as a processor (502). In some implementations, a user may interact with the device (500) through the I / O controller (508) or through hardware components controlled by the I / O controller (508).
[0079] In some implementations, the device (500) may include a single antenna (510). However, in some other implementations, the device (500) may have two or more antennas (510) (i.e., multiple antennas) comprising multiple antenna panels or antenna arrays capable of simultaneously transmitting or receiving multiple wireless transmissions. The transceiver (506) may communicate bidirectionally through one or more antennas (510), wired or wireless links as described herein. For example, the transceiver (506) may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver (506) may also include a modem that modulates packets, provides the modulated packets to one or more antennas (510) for transmission, and demodulates packets received from one or more antennas (510). The transceiver (506) may include one or more transmission chains, one or more reception chains, or a combination thereof.
[0080] A transmission chain may be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data over a carrier signal and preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas (510) for transmitting the amplified signal into air or a wireless medium.
[0081] A receiving chain may be configured to receive signals (e.g., control information, data, packets) through a wireless medium. For example, a receiving chain may include one or more antennas (510) for receiving signals through air or a wireless medium. A receiving chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. A receiving chain may include at least one demodulator configured to obtain transmitted data by demodulating the received signal and inverting the modulation technique applied during the transmission of the signal. A receiving chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.
[0082] FIG. 6 illustrates an example of a processor (600) suitable for implementing some embodiments of the present disclosure. The processor (600) may be an example of a processor configured to perform various operations according to examples as described herein. The processor (600) may include a controller (602) configured to perform various operations according to examples as described herein. The processor (600) may optionally include at least one memory (604). Additionally or alternatively, the processor (600) may optionally include one or more arithmetic logic units (ALUs) (606). One or more of these components may be electronically communicated through one or more interfaces (e.g., buses) or otherwise coupled (e.g., operablely, communically, functionally, electronically, electrically).
[0083] The processor (600) may be a processor chipset and may include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, acquiring, searching, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) according to examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., processor (600)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), etc.).
[0084] The controller (602) may be configured to manage and coordinate various operations of the processor (600) (e.g., signaling, receiving, acquiring, searching, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) so that the processor (600) supports various operations according to examples described herein. For example, the controller (602) may operate as a control unit of the processor (600) and generate control signals that manage the operations of various components of the processor (600). These control signals include enabling or disabling function units, selecting data paths, initiating memory access, and coordinating the timing of operations.
[0085] The controller (602) may be configured to fetch instructions from memory (604) (e.g., acquire, retrieve, receive) and to determine subsequent instruction(s) to be executed in order to enable the processor (600) to support various operations according to examples described herein. The controller (602) may be configured to track the memory addresses of instructions associated with memory (604). The controller (602) may be configured to decode instructions to determine the operations to be performed and the accompanying operands. For example, the controller (602) may be configured to interpret instructions and determine control signals to be output to other components of the processor (600) so that the processor (600) can support various operations according to examples described herein. Additionally or alternatively, the controller (602) may be configured to manage the flow of data within the processor (600). The controller (602) may be configured to control the transfer of data between the registers, arithmetic logic units (ALUs), and other functional units of the processor (600).
[0086] Memory (604) may include one or more caches (e.g., memory local to or contained in the processor (600)), or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory (604) may be located within or on the processor chipset (e.g., local to the processor (600)). In some other implementations, memory (604) may be located outside the processor chipset (e.g., remote to the processor (600)).
[0087] Memory (604) may store computer-readable, computer-executable code containing instructions that, when executed by the processor (600), cause the processor (600) to perform the various functions described herein. The code may be stored in a non-transient computer-readable medium, such as system memory or other types of memory. The controller (602) and / or the processor (600) may be configured to execute the computer-readable instructions stored in the memory (604) to cause the processor (600) to perform various functions (e.g., functions or tasks that support transmission power prioritization). For example, the processor (600) and / or the controller (602) may be coupled with or connected to the memory (604), and the processor (600), the controller (602), and the memory (604) may be configured to perform the various functions described herein. In some examples, the processor (600) may include multiple processors, and the memory (604) may include multiple memories. One or more of the multiple processors may be combined with one or more of the multiple memories, and they may be configured to perform various functions of this specification individually or collectively.
[0088] One or more ALUs (606) may be configured to support various operations according to examples as described herein. In some implementations, one or more ALUs (606) may be located within or on a processor chipset (e.g., processor (600)). In some other implementations, one or more ALUs (606) may be located outside the processor chipset (e.g., processor (600)). One or more ALUs (606) may perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs (606) may receive input operands and an operation code that determines the operation to be executed. One or more ALUs (606) are composed of various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, for processing and manipulating data according to the operation. Additionally, or alternatively, one or more ALUs (606) may support logical operations such as AND, OR, XOR (exclusive-OR), NOR (not-OR), and NAND (not-AND), thereby enabling one or more ALUs (606) to handle conditional operations, comparisons, and bitwise operations.
[0089] The processor (600) may support wireless communication according to examples as disclosed in this specification. The processor (600) may be implemented to perform LMF. The processor (600) may be configured or operable to support means for transmitting a first message to an AMF requesting information related to a user equipment (UE) that meets one or more criteria; means for receiving a second message from the AMF containing information related to a list of UEs that meet one or more criteria; and means for transmitting a third message to at least one UE among the list of UEs requesting at least one UE to report data.
[0090] A processor (600) may be implemented to perform an AMF. The processor (600) may be configured or operable to support means for receiving a first message requesting information related to a user equipment (UE) that meets one or more criteria from a location management function (LMF); and means for transmitting a second message to the LMF that includes information related to a list of UEs that meet one or more criteria in order to report data to the LMF.
[0091] FIG. 7 illustrates a flowchart of a method (700) for performing LMF according to embodiments of the present disclosure. Operations of the method (700) may be implemented by a device or its components as described herein. For example, operations of the method (700) may be performed by a server or network entity within a core network as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally or alternatively, the device may use special-purpose hardware to perform embodiments of the described functions.
[0092] In 710, the method may include the step of transmitting a first message to an access and mobility management function (AMF) requesting information related to a user equipment (UE) that meets one or more criteria. The operations of 710 may be performed according to examples as described herein. In some implementations, aspects of the operations of 710 may be performed by a server (117) implemented within a core network (106) or by a network entity (102) as described with reference to FIG. 1.
[0093] In 720, the method may include the step of receiving a second message from the AMF containing information regarding a list of UEs that meet one or more criteria. The operations of 720 may be performed according to examples as described herein. In some implementations, aspects of the operations of 720 may be performed by a server (117) implemented within the core network (106) or by a network entity (102) as described with reference to FIG. 1.
[0094] In 730, the method may include the step of sending a third message to at least one UE in a list of UEs requesting at least one UE to report data. The operations of 730 may be performed according to examples as described herein. In some implementations, aspects of the operations of 730 may be performed by a server (117) implemented within a core network (106) or a network entity (102) as described with reference to FIG. 1.
[0095] FIG. 8 illustrates a flowchart of a method (1000) for performing AMF according to embodiments of the present disclosure. Operations of the method (800) may be implemented by a device or its components as described herein. For example, operations of the method (800) may be performed by a server within a core network as described herein. In some implementations, the device may execute a set of instructions to control functional elements of the device to perform the described functions. Additionally, or alternatively, the device may use special-purpose hardware to perform embodiments of the described functions.
[0096] In 810, the method may include the step of receiving a first message from a location management function (LMF) requesting information related to a user equipment (UE) that meets one or more criteria. The operations of 810 may be performed according to examples as described herein. In some implementations, aspects of the operations of 810 may be performed by a server (117) implemented within a core network (106) as described with reference to FIG. 1.
[0097] In 820, the method may include the step of transmitting a second message to the LMF containing information related to a list of UEs that meet one or more criteria for reporting data to the LMF. The operations of 820 may be performed according to examples as described herein. In some implementations, aspects of the operations of 820 may be performed by a server (117) implemented within the core network (106) as described with reference to FIG. 1.
[0098] It should be noted that the methods described in this specification describe possible implementations, and that operations and steps may be rearranged or modified in other ways, and that other implementations are possible. Additionally, aspects from two or more of the methods may be combined.
[0099] The various exemplary blocks and components described in connection with the disclosure of this specification may be implemented or performed by a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, individual gate or transistor logic, individual hardware components, or any combination thereof, designed to perform the functions described in this specification. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor), a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration.
[0100] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions may be stored or transmitted as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of the software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functions may also be physically located at various locations, including distributed so that parts of the functions are implemented at different physical locations.
[0101] Computer-readable media include both non-transient computer storage media and communication media, comprising any medium that facilitates the transfer of a computer program from one place to another. A non-transient storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer. For example, non-transient computer-readable media may include RAM, ROM, EEPROM (electrically erasable programmable ROM), flash memory, CD (compact disk) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transient medium that can be used to carry or store a desired means of program code in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor.
[0102] As used herein, including in the claims, the article "a" preceding an element is understood to refer to "at least one" of such elements or "one or more" of such elements without limitation. The terms "one," "at least one," "one or more," and "at least one of one or more" may be interchangeable. As used herein, including in the claims, the word "or" as used in a list of items (e.g., a list of items preceded by phrases such as "at least one of," "one or more of," or "one or both of") indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A, B, and C). Additionally, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an exemplary step described as “based on Condition A” may be based on both Condition A and Condition B without departing from the scope of this disclosure. That is, as used herein, the phrase “based on” should be interpreted in the same way as the phrase “based at least partially on”. Additionally, as used herein, including in claims, “set” may include one or more elements.
[0103] The description in this specification is provided to enable a person skilled in the art to practice or use the present disclosure. Various modifications to the present disclosure will be apparent to a person skilled in the art, and the general principles defined in this specification may be applied to other variations without departing from the scope of the present disclosure. Accordingly, the present disclosure is not limited to the examples and designs described in this specification, but should be given the broadest scope consistent with the principles and novel features disclosed in this specification.
Claims
Claim 1 A device for performing a location management function (LMF), comprising at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to cause the device to transmit a first message requesting information related to a user equipment (UE) that meets one or more criteria to an access and mobility management function (AMF); to receive a second message from the AMF containing information related to a list of UEs that meet one or more criteria; and to transmit a third message requesting the at least one UE to report data to at least one UE among the list of UEs. Claim 2 A device according to claim 1, wherein the one or more criteria include at least one of: the UE is a positioning reference unit (PRU); the UE is capable of UE-based positioning methods; the UE is capable of LTE positioning protocol (LPP); the UE is of a mobility type; or the UE is within a region of interest. Claim 3 In claim 1, the information relating to the list of UEs comprises: a UE identity (ID); a serving cell ID of the UE; information regarding whether the UE is a PRU; whether the UE is capable of a UE-based positioning method and its corresponding positioning method; whether the UE is capable of LPP; or at least one of the mobility type of the UE. Claim 4 In paragraph 3, the device, wherein the UE ID is a dedicated ID assigned by the AMF, or a subscription persistent identifier (SUPI). Claim 5 In paragraph 3, the device wherein the serving cell ID of the UE comprises a first serving cell ID of a primary cell at a master random access network (RAN) node and a second serving cell ID of a primary cell at a secondary RAN node. Claim 6 In claim 1, the device further transmits a fourth message to the AMF requesting the transmission of the third message to the at least one UE. Claim 7 A device according to claim 1, wherein the first message is a subscription request message for subscribing to information related to a UE satisfying one or more criteria; and the second message is a notification message containing information related to a list of UEs satisfying one or more criteria. Claim 8 In paragraph 7, the device, wherein the first message and the second message are based on the service of the AMF for event exposure. Claim 9 An apparatus according to claim 1, wherein the list of UEs comprises one of: a list of all UEs satisfying the criteria; a list of new UEs satisfying the criteria; or a list of old UEs that no longer satisfy the criteria. Claim 10 In claim 1, the device, wherein the first message and the second message are based on a dedicated AMF service of a one-time request / response method. Claim 11 In claim 1, the third message comprises at least one of: a configuration related to determining actual measurement data; a reference signal configuration for measurements; an indicator of whether the UE should report its current serving cell; periodicity of the report; or a region of interest. Claim 12 A device for performing an access and mobility management function (AMF), comprising at least one memory; and at least one processor coupled to the at least one memory, wherein the at least one processor is configured to cause the device to receive a first message requesting information related to a user equipment (UE) that meets one or more criteria from a location management function (LMF); and to transmit to the LMF a second message containing information related to a list of UEs that meet one or more criteria in order to report data to the LMF. Claim 13 In paragraph 12, the device comprises at least one of the following criteria: the UE is a positioning reference unit (PRU); the UE is capable of UE-based positioning methods; the UE is capable of LTE positioning protocol (LPP); the UE is of a mobility type; or the UE is within a region of interest. Claim 14 In paragraph 12, the above information relating to a list of UEs comprises: a UE identity (ID); a serving cell ID of the UE; information regarding whether the UE is a PRU; whether the UE is capable of a UE-based positioning method and its corresponding positioning method; whether the UE is capable of LPP; or at least one of the mobility types of the UE. Claim 15 In paragraph 14, the device, wherein the UE ID is a dedicated ID assigned by the AMF, or a subscription persistent identifier (SUPI). Claim 16 In paragraph 14, the device wherein the serving cell ID of the UE comprises a first serving cell ID of a primary cell at a master random access network (RAN) node and a second serving cell ID of a primary cell at a secondary RAN node. Claim 17 A device according to claim 12, wherein the first message is a subscription request message for subscribing to information related to a UE satisfying one or more criteria; and the second message is a notification message containing information related to a list of UEs satisfying one or more criteria. Claim 18 In paragraph 12, the device comprises one of the following: a list of UEs that satisfies all UEs that meet the criteria; a list of new UEs that meet the criteria; or a list of old UEs that no longer meet the criteria. Claim 19 A method for performing a location management function (LMF), comprising: transmitting a first message to an access and mobility management function (AMF) requesting information related to a user device (UE) that meets one or more criteria; receiving a second message from the AMF containing information related to a list of UEs that meet the one or more criteria; and transmitting a third message requesting at least one UE among the list of UEs to report data to the at least one UE. Claim 20 A method for performing an access and mobility management function (AMF), comprising: receiving a first message from a location management function (LMF) requesting information related to a user device (UE) that meets one or more criteria; and transmitting a second message to the LMF containing information related to a list of UEs that meet one or more criteria in order to report data to the LMF.