Amf assisted data collection for lmf
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-11
- Publication Date
- 2026-08-11
Smart Images
Figure CN122556099A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to wireless communications, and more particularly to apparatus for performing location management functions (LMF), apparatus for performing access and mobility management functions (AMF), methods for AMF-assisted data collection for LMF, and computer-readable media. Background Technology
[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). Additionally, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)).
[0003] In Rel 19, support will be provided for Location Management Functions (LMF) to use an artificial intelligence (AI) model operating on the LMF side to determine the UE's location. This AI model will have inputs (e.g., measurement or auxiliary information) collected from the UE or gNB. In some scenarios, the LMF can train its own LMF-side model and require the LMF to collect training data (e.g., ground truth UE location and associated measurement / auxiliary information) from the UE or gNB. Summary of the Invention
[0004] This disclosure relates to apparatus for performing location management functions (LMF), apparatus for performing access and mobility management functions (AMF), a method for AMF-assisted data collection for LMF, and a computer-readable medium. According to embodiments of this disclosure, the LMF can determine the appropriate UE for data collection with the assistance of the AMF.
[0005] In a first aspect, an apparatus for performing a location management function (LMF) is provided, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and configured such that the apparatus: sends a first message to an access and mobility management function (AMF), the first message requesting information relating to user equipment (UE) that meets one or more criteria; receives a second message from the AMF, the second message including information relating to a list of UEs that meet one or more criteria; and sends a third message to at least one of these UEs, the third message requesting at least one UE to report data.
[0006] In a second aspect, an apparatus for performing an Access and Mobility Management Function (AMF) is provided, the apparatus comprising: at least one memory; and at least one processor coupled to the at least one memory and configured such that the apparatus: receives a first message from a Location Management Function (LMF) requesting information relating to a User Equipment (UE) that meets one or more criteria; and sends a second message to the LMF to report data to the LMF, the second message including information relating to a list of UEs that meet one or more criteria.
[0007] In a third aspect, a method for performing a location management function (LMF) is provided, the method comprising: sending a first message to an access and mobility management function (AMF) requesting information relating to user equipment (UE) that meets one or more criteria; receiving a second message from the AMF, the second message including information relating to a list of UEs that meet one or more criteria; and sending a third message to at least one of the UEs requesting at least one UE to report data.
[0008] In a fourth aspect, 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 relating to a User Equipment (UE) that meets one or more criteria; and sending a second message to the LMF to report data to the LMF, the second message including information relating to a list of UEs that meet one or more criteria.
[0009] In a fifth aspect, a computer-readable medium is provided having instructions stored thereon that, when executed by a processor of a device, cause the device to perform a method according to any one of the third and fourth aspects of this disclosure.
[0010] In some implementations of the methods described herein, the apparatus for performing LMF, and 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 has the capability of a UE-based positioning method; the UE has the capability of the LTE Positioning Protocol (LPP); the UE has a mobility type; or the UE is located in an area of interest.
[0011] In some implementations of the methods described herein, the apparatus for performing LMF, and the apparatus for performing AMF, the information related to the list of UEs includes at least one of the following: UE identifier (ID); UE serving cell ID; information about whether the UE is a PRU; whether the UE has the capability of a UE-based positioning method and its corresponding positioning method; whether the UE has the capability of LPP; or the UE's mobility type.
[0012] In the methods described herein, the apparatus for performing LMF, and some implementations of the apparatus for performing AMF, the UE ID is a private ID or subscription permanent identifier (SUPI) assigned by the AMF.
[0013] In some implementations of the methods described herein, the apparatus for performing LMF, and the apparatus for performing AMF, the UE's serving cell ID includes: the first serving cell ID of the primary cell in the primary random access network (RAN) node, and the second serving cell ID of the primary cell in the secondary RAN node.
[0014] In some implementations of the method described herein, the apparatus for performing LMF, and the apparatus for performing AMF, the apparatus for performing LMF sends a fourth message to AMF, the fourth message being used to request the transmission of a third message to at least one UE.
[0015] In some implementations of the method described herein, the apparatus for performing LMF, and the apparatus for performing AMF, the first message is a subscription request message for subscribing to information related to UEs that meet one or more criteria; and the second message is a notification message that includes information related to a list of UEs that meet one or more criteria.
[0016] In some implementations of the methods, apparatus for performing LMF, and apparatus for performing AMF described herein, the first and second messages are based on the AMF's service for event exposure.
[0017] In the methods described herein, the apparatus for performing LMF, and some implementations of the apparatus for performing AMF, the list of UEs includes 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 some implementations of the methods described herein, the apparatus for performing LMF, and the apparatus for performing AMF, the first and second messages are based on a dedicated AMF service in a one-time request / response manner.
[0019] In some implementations of the methods described herein, the apparatus for performing LMF, and the apparatus for performing AMF, the third message includes at least one of the following: configuration related to truth determination; configuration of reference signals for measurement; an indicator regarding whether the UE should report its current serving cell; the reporting period; or the region of interest.
[0020] In some implementations of the method described herein, the apparatus for performing LMF, and the apparatus for performing AMF, the apparatus for performing AMF receives a fourth message from the LMF, which requests the transmission of a third message to at least one UE.
[0021] In the methods described herein, the apparatus for performing LMF, and some implementations of the apparatus for performing AMF, the apparatus for performing AMF triggers a service request to a list of UEs in Radio Resource Control (RRC) idle state triggered by the network (NW). Attached Figure Description
[0022] Figure 1 Examples of wireless communication systems in which some embodiments of the present disclosure may be implemented are illustrated.
[0023] Figure 2 The illustration shows an example of a processing flow in which an LMF requests data from a UE with the assistance of an AMF, according to some example embodiments of the present disclosure.
[0024] Figure 3 The illustration shows an example of an LMF requesting data from a UE via a subscription / notification method with the assistance of an AMF, according to some example embodiments of the present disclosure.
[0025] Figure 4 The illustration shows an example of an LMF requesting data from a UE via a one-time request / response method, in accordance with some example embodiments of the present disclosure.
[0026] Figure 5 Examples of devices suitable for implementing embodiments of the present disclosure are illustrated.
[0027] Figure 6 Examples of processors suitable for implementing some embodiments of the present disclosure are illustrated.
[0028] Figure 7A flowchart illustrating a method for performing an LMF according to various aspects of this disclosure is shown.
[0029] Figure 8 A flowchart illustrating a method for performing an AMF according to various aspects of this disclosure is shown.
[0030] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation
[0031] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The disclosure described herein can 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 commonly understood by one of ordinary skill in the art to which this disclosure pertains.
[0032] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the embodiments(s) described may include a particular feature, structure, or characteristic, but not every embodiment necessarily must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same(s) embodiments(s). Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will recognize that in conjunction with other embodiments (whether explicitly described or not) such a feature, structure, or characteristic may affect such a feature, structure, or characteristic within the scope of their knowledge.
[0033] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms. In some examples, values, processes, or apparatus are referred to as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that a selection can be made from a number of functional alternatives used, and that such selection does not need to be better, smaller, higher, or more preferred than other options.
[0034] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein are also intended to include the plural forms. Furthermore, it should be understood that the terms “comprising,” “including,” “having,” “comprising,” and / or “containing,” when used herein, specify the presence of the stated features, elements, and / or components, 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 understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of expressions such as “A and / or B” can mean “A only” or “B only” or “both A and B.” Other explicit and implicit definitions may be included below.
[0035] In Rel-19, the LMF will be supported in using an AI model operating on the LMF side to determine the UE location. This AI model will have inputs (e.g., measurement or auxiliary information) collected from the UE or gNB. In one scenario, the LMF can train the LMF-side model itself and require the LMF to collect training data (e.g., ground truth UE location and associated measurement / auxiliary information) from the UE or gNB.
[0036] However, in the traditional location services process, the LMF does not initiate location services and related LTE Location Protocol (LPP) sessions independently. Instead, it follows instructions / requests based on the AMF. For example, in the case of a Mobile-Terminated Location Request (MT-LR), the AMF receives a location service request from a Location Services (LCS) client for (multiple) related UEs, and then the AMF sends an Nlmf_Location_DetermineLocation message to the LMF to request UE location determination, where the UE is identified by an LCS relevance identifier. In the case of a Mobile-Initiated Location Request (MT-LR), the AMF receives an MT-LR request from the UE, and then the AMF sends an Nlmf_Location_DetermineLocation message to the LMF to request UE location determination, where the UE is identified by an LCS relevance identifier. In other words, the LMF does not know in advance which UEs are there, e.g., in the area of interest, and does not know which UE the LMF should initiate an LPP session with and begin data collection for. Furthermore, the LMF lacks detailed information about the UE (e.g., Subscription Permanent Identifier (SUPI), which cell the UE is connected to, etc.). The LMF distinguishes different UEs solely based on the LCS Relevance Identifier, which, as the name suggests, is only used for relevance. Therefore, the AMF needs a method to help it select appropriate UEs to establish (multiple) LPP sessions and begin data collection for AI operations.
[0037] In view of this, embodiments of the present disclosure provide a solution for AMF-assisted data collection against an LMF. In an example aspect, the LMF may send a request to the AMF for information about UEs that meet certain criteria. Upon receiving the request, the AMF may identify the UEs that meet the criteria and send information about the UEs to the LMF. The LMF may select at least one UE identified by the AMF and request the selected UE to report data. Various aspects of the present disclosure are described in the context of a wireless communication system.
[0038] In an example scenario, when the LMF wants to train / monitor an LMF-side artificial intelligence / machine learning (AI / ML) model capable of UE location estimation under certain applicability conditions, it will initiate an LPP procedure to the target UE and collect data for AI / ML model training / monitoring (e.g., ground truth UE location and related measurements). To do this, the LMF may need assistance from the AMF to determine which UEs exist and meet the applicability conditions for the AI / ML model. The LMF can then initiate an LPP procedure to these 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.
[0039] Figure 1 Examples of wireless communication systems 100 that may be implemented in some embodiments of this disclosure are illustrated. Wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. Wireless communication system 100 may support various radio access technologies. In some implementations, wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other implementations, wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. Wireless communication system 100 may support radio access technologies other than 5G. Additionally, 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).
[0040] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100. One or more network entities among the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RAN), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface. In a 3GPP non-terrestrial network (NTN), network entity 102, in satellite form, may communicate directly with UE 104 using an NR / LTE Uu interface. The satellite may be a transparent satellite or a regenerated satellite. For an NTN with transparent satellites, a base station on Earth may communicate with the UE via satellite. For an NTN with regenerated satellites, the base station may be on-board and communicate directly with the UE.
[0041] Network entity 102 can provide a geographic coverage area 112 for which it can support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within that geographic coverage area. For example, network entity 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 can be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas 112 can be associated with different network entities 102. The information and signals described herein can be represented using a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned in the description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.
[0042] One or more UEs 104 may be distributed across a geographical area of the wireless communication system 100. 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, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Alternatively or additionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, among other examples. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.
[0043] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1 It is shown in the middle. For example... Figure 1 As shown, UE 104 can communicate with various types of devices, such as network entity 102, other UE 104, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device). Alternatively or additionally, UE 104 can support communication with other network entities 102 or UE 104, which can act as relays in the wireless communication system 100.
[0044] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can support direct wireless communication with another UE 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, communication link 114 may be referred to as a side link. For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.
[0045] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). 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., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs). In some implementations, network entity 102 may include an entity for performing location management functions (LMF).
[0046] In some implementations, network entity 102 can be configured in a decomposed architecture that can utilize a protocol stack physically or logically distributed across 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., a Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC, a Non-RT RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.
[0047] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or TRP. One or more components of network entity 102 in the decomposed RAN architecture can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in the decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).
[0048] The functional division among CU, DU, and RU can be flexible and can 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 at the CU, DU, or RU. For example, the functional division of the protocol stack can be adopted between the CU and DU, such 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 can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC), Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.
[0049] Alternatively, or alternatively, the functional division of the protocol stack can be adopted between DU and RU, such that DU can support one or more layers of the protocol stack, and RU can support one or more different layers of the protocol stack. DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between CU and DU or between DU and RU can be within the protocol layer (e.g., some functions for the protocol layer can be performed by one of CU, DU, or RU, while other functions of the protocol layer are performed by a different one of CU, DU, or RU).
[0050] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via mid-range communication links (e.g., F1, F1c, F1-u), and the DUs can be connected to one or more RUs via front-end communication links (e.g., open front-end (FH) interfaces). In some implementations, the mid-range or front-end communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack, which are supported by corresponding network entities 102 communicating via such communication links.
[0051] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), and may include: a server 117 for performing location management functions (AMF), control plane entities for managing access and mobility (e.g., mobility management entity (MME), access and mobility management functions (AMF)), and user plane entities for routing or interconnecting packets to external networks (e.g., serving gateway (S-GW), packet data network (PDN) gateway (P-GW), or user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more network entities 102 associated with core network 106. LMF can be defined in core network 106 and / or network entity 102 to provide location functionality by determining the geographic location of UE 104 through radio signals used for downlink and uplink location measurements. Packet data network 108 may include application server 118.
[0052] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be one example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).
[0053] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more digital technologies.
[0054] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefix. The first digital technology (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first digital technique (e.g., ...) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. Second digital technologies (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. The third digital technology (e.g., μ =2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ =3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.
[0055] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.
[0056] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ =4) One time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe can be used, respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the digital technique. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes can depend on the digital technique. It should be understood that for the first digital technique (e.g., quantity) associated with the first subcarrier spacing (e.g., 15 kHz), μ The reference of =0 can be used interchangeably between subframes and time slots.
[0057] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. For example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names 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 entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for short-range, high-data-rate capabilities.
[0058] FR1 can be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 can be associated with the following: a first digital technology (e.g., μ =0), which includes a 15 kHz subcarrier spacing; second digital technology (e.g., μ =1), which includes a 30 kHz subcarrier spacing; third digital technology (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 can be associated with a third digital technology (e.g., μ =2), which includes a 60 kHz subcarrier spacing; fourth digital technology (e.g., μ =3), which includes a subcarrier spacing of 120 kHz.
[0059] Figure 2 The illustration shows an example of a processing flow 200 in which an LMF requests data from a UE with the assistance of an AMF, according to some exemplary embodiments of this disclosure. Processing flow 200 may involve an LMF 201, an AMF 202, and a UE 204. For simplicity, Figure 2 Network entities (e.g., base stations or gNBs) are omitted.
[0060] refer to Figure 1 Processing flow 200 can be applied to wireless communication system 100. For example, UE 204 can be any of UE 104. LMF 201 can be deployed at server 117 in core network 106 or at any of network entities 102. AMF 202 can be deployed at server 117 in core network 106. It should be understood that processing flow 200 can be applied to other communication scenarios, which will not be described in detail here.
[0061] At 210, LMF 201 sends a first message 215 to AMF 202, which requests information related to a UE that meets one or more criteria. Accordingly, at 220, AMF 202 receives the first message 215 from LMF 201.
[0062] The first message can instruct AMF 202 on criteria that the UE should meet, enabling AMF to identify the UE(s)(s) used for data collection against LMF 201. In some embodiments, the criteria may include one or more of the following: the UE is a Positioning Reference Unit (PRU); the UE has the capability of a positioning method based on the UE, such as Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Network-Assisted GNSS, NR Enhanced Cell ID (NR E-CID), Downlink Departure Angle (DL-AoD), Downlink Time Difference of Arrival (DL-TDOA), etc.; the UE has the capability of the LTE Positioning Protocol (LPP); the UE has a mobility type (e.g., static, mobile, or highly mobile); or the UE is located within an area of interest (e.g., represented by a list of cell IDs or an area ID).
[0063] At 230, AMF 202 sends a second message 235 to LMF 201, which includes information related to a list of UEs. Therefore, at 240, LMF 201 receives the second message from AMF 202. In some embodiments, AMF 202 may identify a list of UEs that meet the criteria indicated via first message 215 and provide relevant UE information via second message 235. In some embodiments, the UE information may include at least one of the following: UE identifier (ID); UE serving cell ID; information about whether the UE is a PRU; whether the UE has the capability of a positioning method based on the UE and its corresponding positioning method; whether the UE has LPP capability; or the UE's mobility type. In some embodiments, AMF 202 may trigger network (NW) triggered service requests to those UEs that are identified and in an RRC idle state.
[0064] After receiving information from a UE that meets the criteria via a second message 235, at 250, LMF 201 sends a third message 255 to at least one of the UEs, requesting at least one UE to report data. Accordingly, at 260, UE 204 receives the third message 255 from LMF 201. In some embodiments, prior to the transmission of the third message, LMF 201 may perform an LPP session procedure with UE 204. During the LPP session, LMF 201 may send a fourth message requesting the transmission of the third message to UE 204, for example, where the LPP message may be conveyed in a Namf_Communication_N1N2MessgageTransfer message.
[0065] The third message may be an LPP message. In some embodiments, the third message 255 may include information about the reporting configuration, such as configurations related to truth determination; reference signal configurations used for measurement; an indicator of whether the UE should report its current serving cell; the reporting period; or the region of interest. The UE 204 may then 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 truth UE location, which is either known to the UE 204 (if it is a PRU) or determined by other UE positioning methods (e.g., GPS, GNS, etc.). Alternatively or additionally, the reported data may include measurements of relevant reference signals, such as SSB, PRS, CSI-RS, etc. Furthermore, the reported data may include serving cell information and time information (e.g., represented by a UTC timestamp or by SFN / slot / symbol information).
[0066] Figure 3 The illustration shows an example of a processing flow in which an LMF, with the assistance of an AMF, requests data from a UE via a subscription / notification method according to some example embodiments of this disclosure. Processing flow 300 is Figure 2 The example implementation of processing flow 200 is shown.
[0067] exist Figure 3 In this process, LMF 201 requests AMF 202 to continuously provide or update UE list information that meets certain criteria, so that LMF 201 can collect the necessary AI / ML training / monitoring data from these UEs. In some embodiments, LMF 201 can request UE list information from AMF 202 via a subscription request message and can receive UE list information or updates to UE list information via a notification message. The subscription request and notification messages can be based on AMF's event exposure service.
[0068] At steps 1 and 2, LMF 201 sends a subscription request message (e.g., a Namf_EventExposure_Subscribe request) to AMF 202 to subscribe to any UE information that meets the criteria. The subscription request message may indicate the criteria to AMF 202, including any of the following: the UE is a PRU UE; the UE has the capability of a conventional UE-based positioning method, such as GNSS, GPS, network-assisted GNSS, NR E-CID, DL-AoD, DL-TDOA; the UE has LPP capability, mobility type (e.g., static, mobile, highly mobile); the UE is located in an area of interest represented by a list of cell IDs or multiple area IDs.
[0069] In this scenario, AMF 202 should subsequently notify LMF 201 of an update to the list of UEs that meet the requested criteria using, for example, the Namf_EventExposure_Notify service operation. The subscription itself can be defined as a new event ID for the Namf_EventExposure service used by AMF 202. Note that LMF 201 does not include any information related to the UE ID (e.g., SUPI) in the subscription request message, as LMF 202 is unaware of this. Table 1 below shows an example of the criteria indicated in the subscription request, where the event ID is "UEs of interest for data collection". Table 1
[0070] In step 3, after receiving the subscription request message, AMF 202 can identify UEs that meet the criteria and provide UE information to LMF 201 using the Namf_EventExposure_Notify service operation. The UE information may include multiple UE IDs, which can be private IDs assigned by the AMF itself (e.g., correlation IDs used only for correlation) or SUPIs. Additionally, for each UE ID, the UE information may include: the first serving cell identifier of the primary cell in the primary RAN node, and the second serving cell identifier of the primary cell in the secondary RAN node (when available based on a dual-connectivity scenario). Furthermore, the UE information may include information about whether the UE has the capability of a positioning method based on the UE, and this method may include GNSS, GPS, network-assisted GNSS, NR E-CID, DL-AoD, DL-TDOA. Additionally, the UE information may include information about whether the UE has LPP capability. Additionally, the UE information may include the UE's mobility type. Optionally, AMF 202 may autonomously trigger NW-triggered service requests to all possible UEs identified and in RRC idle state.
[0071] In steps 4 and 5, after receiving UE information that meets the criteria, LMF 201 can further determine from which UE LMF 201 should collect the required AI / ML model training / monitoring data. For these UEs, LMF 201 can trigger LPP session establishment, for example, by invoking the Namf_Communication_N1N2MessageTransfer service operation to AMF 202 to request the transmission of an LPP message to UE 204. In some embodiments, the Namf_Communication_N1N2MessageTransfer message can use the UE ID already provided in step 3 to identify the associated UE 204. Optionally, AMF 202 can trigger NW-triggered service requests to those selected UEs in RRC idle state.
[0072] At step 6, LMF 201 sends an LPP message containing information related to data collection to UE 204, requesting UE 204 to report data to LMF 201. The LPP message may include configurations related to truth determination, for example, if it is determined by any of the UE-based positioning methods, such as GNSS, GPS, network-assisted GNSS, NRE-CID, DL-AoD, DL-TDOA. Alternatively, the LPP message may include reference signal (RS) configurations that the UE should measure (e.g., Positioning Reference Signal (PRS), synchronization signal and PBCH block (SSB), Channel State Information RS (CSI-RS)). Alternatively, the LPP message may include information about whether the UE should report the currently serving cell to which the UE is connected. Alternatively, the LPP message may include the reporting period. Alternatively, the LPP message may include information about areas of interest (e.g., a list of cells) that the UE should collect and report when it is in the relevant area.
[0073] At steps 7 and 8, UE 204 may indicate the ongoing data collection session to gNB 203, and gNB 203 may configure UE 204 with a dedicated radio bearer (e.g., with a lower priority than other conventional radio bearers). Any subsequent LPP messages reporting the required data from UE 204 to LMF 201 are then transmitted via this dedicated radio bearer. At step 9, UE 204 may report the required data to LMF 201 as configured at step 6. In some embodiments, the data reported from UE 204 to LMF 201 may include a truth UE location, which is either known to UE 204 (if it is a PRU) or determined by other UE positioning methods (e.g., GPS, GNS, etc.). Alternatively or additionally, the reported data may include measurements of relevant reference signals, such as SSB, PRS, CSI-RS, etc. Furthermore, the reported data may include serving cell information and time information (e.g., represented by a UTC timestamp or by SFN / slot / symbol information).
[0074] At step 10, if any changes occur to the UE list information that meets the criteria, such as any UE no longer meeting the criteria or any new UE meeting the criteria, AMF 202 may send an 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, LMF 201 may determine whether to initiate an LPP session for data collection from UEs and to terminate the LPP session for data collection from old UEs. It should be understood that the subscription request message in step 1 (e.g., Namf_EventExposure_Subscribe request) can be considered as Figure 2 The first message in the process, and the notification message in step 3 (e.g., the Namf_EventExposure_Notify service operation) can be considered as... Figure 2 The second message in the series.
[0075] Figure 4 The illustration shows an example of a processing flow in which an LMF, with the assistance of an AMF, requests data from a UE via a one-time request / response method, according to some example embodiments of this disclosure. Processing flow 400 is Figure 2 The example implementation of the processing flow is shown.
[0076] For UEs that are PRUs or have static mobility, LMF 201 can request UE list information from AMF 202 in a one-time request / response manner, since the UE list information is not expected to change in the short term. In some embodiments, a new dedicated AMF service (e.g., the Namf_UEInformation service) can be defined, or an existing AMF service can be enhanced to serve this purpose. Figure 4 In this process, except for steps 1 and 2 which are based on a dedicated AMF service in a one-time request / response manner and there are no update steps (i.e., Figure 3 Apart from step 10), most details are related to Figure 3 resemblance.
[0077] According to the reference Figures 2 to 4 Some embodiments discussed present a process that enables the LMF to collect data from appropriate UEs that meet certain criteria with the help of the AMF.
[0078] Figure 5 Examples of devices suitable for implementing some embodiments of this disclosure are illustrated. Device 500 may be an example of an LMF or AMF as described herein. Device 500 may support wireless or wired communication with one or more network entities 102, UE 104, or any combination thereof. Device 500 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 502, memory 504, transceiver 506, and optional I / O controller 508). These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).
[0079] Processor 502, memory 504, transceiver 506, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the present disclosure described herein. For example, processor 502, memory 504, transceiver 506, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.
[0080] In some implementations, processor 502, memory 504, transceiver 506, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). 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, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 502 and memory 504 coupled to processor 502 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 504 by processor 502).
[0081] For example, according to the examples disclosed herein, processor 502 may support wireless or wired communication at device 500. Device 500 may be implemented to perform LMF (Light Filtering Function). Processor 502 may be configured to operate to support: components for sending a first message to the AMF, the first message requesting information related to a UE that meets one or more criteria; components for receiving a second message from the AMF, the second message including information related to a list of UEs that meet one or more criteria; and components for sending a third message to at least one UE in the list of UEs, the third message requesting at least one UE to report data.
[0082] Device 500 can be implemented for performing AMF. Processor 502 can be configured to support: components for receiving a first message from the Location Management Function (LMF) requesting information related to user equipment (UE) that meets one or more criteria; and components for sending a second message to the LMF to report data to the LMF, the second message including information related to a list of UEs that meet one or more criteria.
[0083] Processor 502 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 502 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 502. Processor 502 may be configured to execute computer-readable instructions stored in memory (e.g., memory 504) to cause device 500 to perform various functions of this disclosure.
[0084] Memory 504 may include random access memory (RAM) and read-only memory (ROM). Memory 504 may store computer-readable, computer-executable code, including instructions that, when executed by processor 502, cause device 500 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 502, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 504 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.
[0085] I / O controller 508 can manage input and output signals for device 500. I / O controller 508 can also manage peripheral devices not integrated into device 500. In some implementations, I / O controller 508 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 508 can utilize an operating system such as iOS®, Android®, MS Windows®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 508 can be implemented as part of a processor, such as processor 502. In some implementations, a user can interact with device 500 via I / O controller 508 or via hardware components controlled by I / O controller 508.
[0086] In some implementations, device 500 may include a single antenna 510. However, in other implementations, device 500 may have more than one antenna 510 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to transmit or receive multiple wireless transmissions concurrently. Transceiver 506 may communicate bidirectionally via one or more antennas 510, wired or wireless links, as described herein. For example, transceiver 506 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 506 may also include a modem for modulating packets, providing modulated packets to one or more antennas 510 for transmission, and demodulating packets received from one or more antennas 510. Transceiver 506 may include one or more transmit chains, one or more receive chains, or combinations thereof.
[0087] The transmission chain can 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 onto a carrier signal, preparing the signal for transmission over a wireless medium. 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 the air or wireless medium.
[0088] The receiver chain can be configured to receive signals (e.g., control information, data, packets) via a wireless medium. For example, the receiver chain may include one or more antennas 510 for receiving signals over the air or via a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and acquire transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the demodulated signal to receive the transmitted data.
[0089] Figure 6 An example of a processor 600 suitable for implementing some embodiments of the present disclosure is illustrated. Processor 600 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 600 may include a controller 602 configured to perform various operations according to the examples described herein. Processor 600 may optionally include at least one memory 604. Additionally or alternatively, processor 600 may optionally include one or more arithmetic logic units (ALUs) 606. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).
[0090] Processor 600 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., processor chipset-local or included memory (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.).
[0091] Controller 602 can be configured to manage and coordinate various operations of processor 600 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 600 to support various operations of the UE according to the examples described herein. For example, controller 602 can operate as a control unit of processor 600, generating control signals that manage the operation of various components of processor 600. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.
[0092] Controller 602 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 604 and determine subsequent instructions(s) to be executed, such that processor 600 supports various operations according to the examples described herein. Controller 602 may be configured to track the memory addresses of instructions associated with memory 604. Controller 602 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 602 may be configured to interpret instructions and determine control signals to be output to other components of processor 600, such that processor 600 supports various operations according to the examples described herein. Additionally or alternatively, controller 602 may be configured to manage data flow within processor 600. Controller 602 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 600.
[0093] Memory 604 may include one or more caches (e.g., memory local to processor 1000 or included in processor 1000) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 604 may reside within or on the processor chipset (e.g., locally on processor 600). In some other implementations, memory 604 may reside outside the processor chipset (e.g., remotely from processor 600).
[0094] Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 600, cause processor 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 602 and / or processor 600 may be configured to execute computer-readable instructions stored in memory 604 to cause processor 600 to perform various functions (e.g., functions or tasks supporting transmit power priority). For example, processor 600 and / or controller 602 may be coupled to or coupled to memory 604, and processor 600, controller 602, and memory 604 may be configured to perform the various functions described herein. In some examples, processor 600 may include multiple processors, and memory 604 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein.
[0095] One or more ALU 606s can be configured to support various operations as described in the examples herein. In some implementations, one or more ALU 606s may reside within or on the processor chipset (e.g., processor 600). In some other implementations, one or more ALU 606s may reside outside the processor chipset (e.g., processor 600). One or more ALU 606s can perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 606s can receive input operands and opcodes that determine the operation to be performed. One or more ALU 606s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU606s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU606s to handle conditional operations, comparisons, and bitwise operations.
[0096] Based on the examples disclosed herein, processor 600 may support wireless communication. Processor 600 may be implemented to perform an LMF (Local Management Function). Processor 600 may be configured or operable to support: components for sending a first message to the AMF requesting information related to user equipment (UEs) that meet one or more criteria; components for receiving a second message from the AMF, the second message including information related to a list of UEs that meet one or more criteria; and components for sending a third message to at least one UE in the list of UEs, the third message requesting at least one UE to report data.
[0097] Processor 600 may be implemented for performing AMF. Processor 600 may be configured or operable to support: components for receiving a first message from the Location Management Function (LMF) requesting information related to User Equipment (UE) that meets one or more criteria; and components for sending a second message to the LMF to report data to the LMF, the second message including information related to a list of UEs that meet one or more criteria.
[0098] Figure 7 A flowchart illustrating a method 700 for performing an LMF according to various aspects of this disclosure is shown. The operation of method 700 can be implemented by the device or components thereof described herein. For example, the operation of method 700 can be performed by a server or network entity in the core network described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the described functions.
[0099] At 710, the method may include sending a first message to the Access and Mobility Management Function (AMF) requesting information related to a User Equipment (UE) that meets one or more criteria. The operation of 710 can be performed according to the examples described herein. In some implementations, aspects of the operation of 710 may be derived from references... Figure 1 The server 117 or network entity 102 implemented in the core network 106 shall perform the above actions.
[0100] At 720, the method may include: receiving a second message from the AMF, the second message including information related to a list of UEs that meet one or more criteria. The operation at 720 can be performed according to the examples described herein. In some implementations, aspects of the operation at 720 may be derived from references... Figure 1 The server 117 or network entity 102 implemented in the core network 106 shall perform the above actions.
[0101] At 730, the method may include: sending a third message to at least one UE in a list of UEs, the third message requesting at least one UE to report data. The operation of 730 can be performed according to the examples described herein. In some implementations, aspects of the operation of 730 may be derived from references... Figure 1 The server 117 or network entity 102 implemented in the core network 106 shall perform the above actions.
[0102] Figure 8 A flowchart illustrating a method 1000 for performing an AMF according to various aspects of this disclosure is shown. The operation of method 800 can be implemented by the device or components thereof described herein. For example, the operation of method 800 can be performed by a server in a core network as described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the described functions.
[0103] At 810, the method may include: 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 operation of 810 can be performed according to the examples described herein. In some implementations, aspects of the operation of 810 may be derived from references... Figure 1 The server 117, implemented in the core network 106, performs the execution.
[0104] At 820, the method may include: sending a second message to the LMF to report data to the LMF, the second message including information related to a list of UEs that meet one or more criteria. The operation of 820 can be performed according to the examples described herein. In some implementations, aspects of the operation of 820 may be derived from references... Figure 1 The server 117, implemented in the core network 106, performs the execution.
[0105] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.
[0106] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The 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, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).
[0107] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.
[0108] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
[0109] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to refer to “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the use of “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two 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 and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” without departing from the scope of this disclosure could be based on both condition A and condition B. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein, including in the claims, “set” can include one or more elements.
[0110] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. An apparatus for performing a location management function (LMF), the apparatus comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the device: Send a first message to the Access and Mobility Management Function (AMF), the first message requesting information related to a User Equipment (UE) that meets one or more criteria; Receive a second message from the AMF, the second message including information related to a list of UEs that meet one or more criteria; as well as A third message is sent to at least one UE in the list of UEs, the third message requesting the at least one UE to report data.
2. The apparatus of claim 1, wherein the one or more criteria include at least one of the following: UE is a Positioning Reference Unit (PRU); The UE has the capability of positioning based on the UE; The UE has the capability of the LTE positioning protocol LPP; The UE has a mobility type; or The UE is located within the region of interest.
3. The apparatus of claim 1, wherein the information associated with the list of UEs includes at least one of the following: UE identifier ID; UE's serving cell ID; Information regarding whether the UE is a PRU; Does the UE possess the capability of positioning based on the UE and its corresponding positioning method? Does the UE have LPP capability? UE mobility type.
4. The apparatus of claim 3, wherein the UE ID is a private ID or subscription permanent identifier SUPI assigned by the AMF.
5. The apparatus of claim 3, wherein the serving cell ID of the UE comprises: The first serving cell ID of the primary cell in the primary random access network (RAN) node, and the second serving cell ID of the primary cell in the secondary RAN node.
6. The apparatus of claim 1, wherein the apparatus is further configured to: A fourth message is sent to the AMF, the fourth message being used to request the transmission of the third message to the at least one UE.
7. The apparatus according to claim 1, wherein... The first message is a subscription request message, which is used to subscribe to information related to a UE that meets one or more of the criteria; and The second message is a notification message, which includes the information related to a list of UEs that meet one or more of the criteria.
8. The apparatus of claim 7, wherein the first message and the second message are based on the AMF's service for event exposure.
9. The apparatus of claim 1, wherein the list of UEs includes one of the following: A list of all UEs that meet the stated criteria; A list of new UEs that meet the aforementioned criteria; or A list of old UEs that no longer meet the stated criteria.
10. The apparatus of claim 1, wherein the first message and the second message are based on a dedicated AMF service in a one-time request / response manner.
11. The apparatus of claim 1, wherein the third message comprises at least one of the following: Configuration related to truth value determination; Reference signal configuration for measurement; Indicators regarding whether the UE should report its current serving cell; Reporting cycle; or Area of interest.
12. An apparatus for performing Access and Mobility Management Functions (AMF), the apparatus comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the device: Receive a first message from the location management function (LMF), the first message requesting information related to a user equipment (UE) that meets one or more criteria; as well as A second message is sent to the LMF to report data to the LMF, the second message including information related to a list of UEs that meet one or more of the criteria.
13. The apparatus of claim 12, wherein the one or more criteria include at least one of the following: UE is a Positioning Reference Unit (PRU); The UE has the capability of positioning based on the UE; The UE has the capability of the LTE positioning protocol LPP; The UE has a mobility type; or The UE is located within the region of interest.
14. The apparatus of claim 12, wherein the information associated with the list of UEs includes at least one of the following: UE identifier ID; UE's serving cell ID; Information regarding whether the UE is a PRU; Does the UE possess the capability of UE-based positioning methods and their corresponding methods? Does the UE have LPP capability? UE mobility type.
15. The apparatus of claim 14, wherein the UE ID is a private ID or subscription permanent identifier SUPI assigned by the AMF.
16. The apparatus of claim 14, wherein a serving cell ID of the UE comprises: The first serving cell ID of the primary cell in the primary random access network (RAN) node, and the second serving cell ID of the primary cell in the secondary RAN node.
17. The apparatus of claim 12, wherein... The first message is a subscription request message, which is used to subscribe to information related to a UE that meets one or more of the criteria. The second message is a notification message, which includes the information related to a list of UEs that meet one or more of the criteria.
18. The apparatus of claim 12, wherein the list of UEs includes one of the following: A list of all UEs that meet the stated criteria; A list of new UEs that meet the aforementioned criteria; or A list of old UEs that no longer meet the stated criteria.
19. A method for performing a location management function (LMF), the method comprising: Send a first message to the Access and Mobility Management Function (AMF), the first message requesting information related to a User Equipment (UE) that meets one or more criteria; Receive a second message from the AMF, the second message including information related to a list of UEs that meet one or more criteria; as well as A third message is sent to at least one UE in the list of UEs, the third message requesting the at least one UE to report data.
20. A method for performing an Access and Mobility Management Function (AMF), the method comprising: Receive a first message from the location management function (LMF), the first message requesting information related to a user equipment (UE) that meets one or more criteria; as well as A second message is sent to the LMF to report data to the LMF, the second message including information related to a list of UEs that meet one or more of the criteria.