Enhanced positioning service in 5G

Abstract

Systems, methods, apparatuses, and computer program products for enhanced positioning services in 5G are provided. A method may include storing, at a network node, with a location management function (LMF) profile or in an LMF profile, at least one of a data network access identifier (DNAI), an indication of a service area (s), and / or slice information supported by the LMF. The method may also include sending, to a consumer network function (NF), an LMF profile having the DNAI, an indication of the service area (s), or slice information supported by the LMF.

Description

[0001] This application is a divisional application of the invention patent application with application date of October 8, 2021, application number 202111172708.1, and invention name “Enhanced Positioning Service in 5G”. Technical Field

[0002] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or other communication systems. For example, certain embodiments may relate to systems and / or methods for enhanced positioning services. Background Art

[0003] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE-Advanced (LTE-A), MulteFire, LTE-A Pro and / or fifth generation (5G) radio access technology or new radio (NR) access technology. 5G wireless systems refer to next generation (NG) radio systems and network architectures. 5G systems are primarily built on 5G New Radio (NR), but 5G (or NG) networks may also be built on E-UTRA radio. It is estimated that NR provides bit rates of the order of 10-20 Gbit / s or higher, and can support at least service categories such as enhanced mobile broadband (EMBB) and ultra-reliable low latency communications (URLLC) and massive machine type communications (mMTC). NR is expected to provide extreme broadband and ultra-robust, low latency connections and large-scale networking to support the Internet of Things (IoT). As IoT and machine-to-machine (M2M) communications become more prevalent, there will be an increasing need for networks that meet the demands for lower power, low data rates, and long battery life. The Next Generation Radio Access Network (NG-RAN) represents the RAN of 5G, which can provide both NR and LTE (and LTE-Advanced) radio access. Note that in 5G, a node that can provide radio access functions to user equipment (i.e., similar to a Node B, NB in ​​UTRAN or an evolved NB, eNB in ​​LTE) can be named a Next Generation NB (gNB) when built on an NR radio, and can be named a Next Generation eNB (NG-eNB) when built on an E-UTRA radio. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] For a proper understanding of the example embodiments, reference should be made to the accompanying drawings, in which:

[0005] Figure 1A shows an example signaling diagram according to an example embodiment;

[0006] Figure 1B shows examples of additional information that may be stored at a network node or a network repository function (NRF) according to an embodiment;

[0007] Figure 1C shows examples of additional information that may be stored at a network node or a network repository function (NRF) according to an embodiment;

[0008] Figure 2 An example system diagram illustrating a UE mobility scenario with edge network selection is shown according to one embodiment;

[0009] Figure 3 An example system diagram illustrating a UE mobility scenario with edge network selection is shown according to one embodiment;

[0010] Figure 4A An example flow chart of a method according to an embodiment is shown;

[0011] Figure 4B An example flow chart of a method according to an embodiment is shown;

[0012] Figure 4C An example flow chart of a method according to an embodiment is shown;

[0013] Figure 5A An example block diagram of an apparatus according to an embodiment is shown;

[0014] Figure 5B An example block diagram showing an apparatus according to an embodiment; and

[0015] Figure 5C An example block diagram of an apparatus according to an embodiment is shown. DETAILED DESCRIPTION

[0016] It can be easily understood that the components of certain example embodiments as generally described and illustrated in the accompanying drawings herein can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of some example embodiments of systems, methods, devices, and computer program products for enhanced positioning services in 5G is not intended to limit the scope of certain embodiments, but rather represents selected example embodiments.

[0017] The features, structures, or characteristics of the example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, throughout this specification, the use of the phrases "certain embodiments," "some embodiments," or other similar language refers to the fact that a particular feature, structure, or characteristic described in conjunction with an embodiment may be included in at least one embodiment. Thus, throughout this specification, the appearance of the phrases "certain embodiments," "in some embodiments," "in other embodiments," or other similar language does not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

[0018] In addition, if desired, the different functions or processes discussed below can be performed in different orders and / or simultaneously with each other. In addition, if desired, one or more of the described functions or processes can be optional or can be combined. Therefore, the following description should be considered as an explanation of the principles and teachings of some example embodiments, rather than a limitation thereof.

[0019] The Location Management Function (LMF), the Gateway Mobile Location Center (GMLC), and the Access and Mobility Management Function (AMF) are some of the entities having functions related to Location Services (LC) (e.g., see 3GPP TS23.501, TS23.502, TS23.273, TS 38.455, TS 38.305).

[0020] To achieve low latency and high performance LCS, it may be beneficial to have the involved LMF and AMF at the network edge close to the UE in order to minimize the delay caused by the signaling between the Radio Access Network (RAN) and the Core Network (CN) (i.e., gNB and AMF) and between CN entities (i.e., AMF and LMF).

[0021] One deployment scenario of interest for low latency and high performance LCS is the Local Area Data Network (LADN). A LADN is a data network (DN) accessible only by UEs in a specific location, which provides connectivity to a specific Data Network Name (DNN) and its availability is provided to the UE.

[0022] Currently, it is not possible for the AMF and other network functions (NFS) to dynamically know which LMF (if any) is serving the edge network or LADN. This may prevent the AMF (and other NFs) from potentially selecting the best LMF located at the edge and / or relocating the LMF in the event that the UE moves to the edge network.

[0023] Furthermore, currently, the AMF selection as part of the UE mobility procedure (which may be triggered due to UE mobility) does not take into account the LMF requirements. There is no mechanism to ensure the continuity of ongoing LCS sessions and / or to ensure that the target AMF is selected taking into account the availability of the edge LMF in case the UE at the target location (i.e., target-RAN) requires low-latency positioning services.

[0024] The AMF load balancing function allows a UE entering an AMF area / AMF set to be directed to the appropriate AMF in a way that achieves load balancing between AMFs. This is achieved by setting a weight factor for each AMF so that the probability of 5G-AN selecting an AMF is proportional to the weight factor of the AMF. The weight factor is typically set based on the capacity of the AMF node relative to other AMF nodes. The weight factor is sent from the AMF to the 5G-AN via an NGAP message.

[0025] It is also possible that the LMF selection is performed by the AMF based on specific criteria such as duration of event reporting, RAN configuration information, LMF load, etc. However, there are currently no details or defined procedures for selecting the LMF with respect to the LADN or edge data network access identifier (DNAI).

[0026] Accordingly, certain example embodiments may address and overcome, for example, at least the above-mentioned problems or disadvantages, as well as solve other possible problems.

[0027] Some example embodiments discussed herein may provide enhanced LMF profile support at a Network Repository Function (NRF). Note that an NRF may refer to a network node that maintains profiles of available Network Function (NF) instances and supports services in a 5G Core Network (5GC), which allows consumer NF instances to discover NF instances of other providers in the 5GC. In addition, the NRF may allow NF instances to track the status of other NF instances.

[0028] An embodiment provides that the NRF may additionally maintain certain attributes specific to the LMF profile, which the consumer NF (e.g., in this case, the AMF and / or LMF) may then use when selecting the best LMF. These additional attributes may include DNAI and (one or more) network slice information, etc. This may then be used, for example, based on the Nnrf_Discovery service of the AMF and other 5G core network functions for different purposes, such as for the best LMF selection in the case of edge application scenarios.

[0029] Embodiments may also provide updates to the UE mobility process (e.g., N2 handover process) to select the best target-AMF and LMF for the serving edge network. This can ensure the continuity of ongoing LCS sessions and / or ensure that the target AMF is selected taking into account the availability of the edge LMF in the event that the UE at the target location (i.e., target-RAN) requires low-latency positioning services. Note that N2 (also known as NG) refers to the control plane interface between the access network (e.g., NG-RAN or WLAN) and the 5GC.

[0030] As introduced above, certain embodiments may provide enhanced LMF profile support at the NRF for optimal LMF selection. Various factors that may be considered during LMF selection, such as requested QoS information, LMF load, LMF location, and RAN configuration information, have been previously specified. However, it has not been previously specified that any DNAI information, (one or more) service area information, and slice-specific information be provided in the LMF selection criteria list. However, DNAI information, (one or more) service area information, and slice-specific information are important, for example, for ensuring that the most suitable LMF is selected for the edge network and providing positioning services to LCS clients located close to a specific DNAI.

[0031] It is also specified that the LMF selection can be performed at the AMF or LMF based on locally available information, i.e., the LMF profile is configured locally at the AMF or LMF, or by querying the NRF. However, the LMF profile at the NRF does not provide any information about what DNAIs and / or network slices the LMF supports. Due to the unavailability of this information, it is not possible, for example, to know and therefore make the best LMF selection by the requesting NF consumer, if a specific LMF is optimal for an edge network or a Local Access Data Network (LADN) or for a UE supporting a specific slice. Another example could be the use case where an LCS client requests a delay-critical location service. In this case, the AMF will select a LMF that supports a slice specific to URLLC if support for that slice for a specific LMF is indicated in the LMF profile provided by the NRF (to the AMF).

[0032] Thus, in certain embodiments, the LMF profile in the NRF may be enhanced to include information about the supported DNAI(s), service areas about the Tracking Area Identifier (TAI), and / or supported network slice(s). The NF consumer (e.g., AMF and / or LMF) may then retrieve this information using, for example, the Nnrf_NFDiscovery service operation. In an embodiment, the LMF profile may be configured and stored at the NRF using Operation, Administration, and Maintenance (OAM) procedures, and / or the LMF instance may register itself with the NRF providing this information.

[0033] Figure 1A FIG. 1 shows an example signaling diagram showing LMF profile discovery of (one or more) consumer NFs according to an example embodiment. More specifically, Figure 1A An example LMF profile retrieval process from an NRF by a consumer NF(s) (such as an AMF and / or LMF) is shown. Figure 1A As shown in the example of , at 110, the NRF may maintain or store additional information as part of the LMF profile. For example, the additional information may include (one or more) DNAIs, (one or more) service areas or (one or more) TAIs, and / or supported (one or more) slice information. Then, at 120, the consumer NF may query the NRF for the LMF profile and / or (one or more) DNAIs, (one or more) service areas / (one or more) TAIs and / or supported (one or more) slice information. Also as shown in Figure 1A As shown in the example of , at 130, the NRF may provide the requested LMF profile to the consumer NF, including (one or more) DNAIs, (one or more) service areas or (one or more) TAIs, and / or supported (one or more) slice information.

[0034] Figure 1B and Figure 1C An example of additional information that may be stored at the NRF as part of the LMF profile is shown. Figure 1B As shown, NRF can maintain a single network slice selection auxiliary information (S-NSSAI) supported by LMF and a parameter list (dnnLmfInfoList) for each DNN supported by LMF. Figure 1C As shown, the NRF may also maintain a list of supported DNNs and data network access identifiers (dnaiList) supported by the LMF for the DNNs.

[0035] Some example embodiments may involve AMF relocation taking into account location service requirements. Embodiments provide enhancements to the AMF selection process to enable the serving AMF (e.g., in the case where the AMF is relocated due to UE mobility and the UE ends up camping on the target-RAN) to select the most suitable AMF that can better serve the service requested by the edge client (e.g., LCS client). This scenario may support UE mobility and requesting edge network or LADN type services. Selecting (one or more) AMF instances and LMF services that support and are best positioned to serve edge network or LADN services can additionally help offload core network traffic and reduce or avoid signaling deep into the core network.

[0036] Figure 2An example system diagram is shown showing a UE mobility scenario with edge network selection according to one embodiment. Certain embodiments may provide updates to the UE mobility process (e.g., N2 handover process) to select the best target AMF and LMF serving the edge network. This ensures the continuity of ongoing LCS sessions and / or ensures that the target AMF is selected taking into account the availability of the edge LMF in the event that the UE at the target location (i.e., target-RAN) requires low-latency positioning services.

[0037] like Figure 2 As shown in the example of FIG. 2 , the UE 201 before the movement is connected to the source-RAN 205, which selects the AMF 211 located deep in the network 250 and is referred to as the "central AMF" herein. The AMF 211 can also serve the LCS client 215 requests, such as Figure 2 In addition, Figure 2 The UE mobility scenario is also highlighted, whereby the S-RAN 205 can trigger AMF relocation via the N2 interface due to the mobility of the UE 201. During the handover process, the source AMF 211 can decide and select the target AMF 220 that can better serve the target-RAN 217. According to an embodiment, the source AMF 211 can also take into account any delay-critical location service requests or requests specific to the edge network and LMFs in the edge network (such as Figure 2 The example of LMF224 is shown in Figure 1 as its AMF selection criteria, along with other criteria that may have been configured in addition. This is useful in reducing round-trip latency, helping to keep signaling local (i.e., within the edge network), better serving latency-critical location (and other) service requests, etc.

[0038] Figure 3 An example signaling diagram of AMF relocation considering location service requirements according to an embodiment is shown. More specifically, Figure 3 An example embodiment of an N2 handover process with AMF relocation is shown, which AMF relocation additionally considers delay-critical location service requests or LMF availability in the edge network as its AMF selection criteria. In some embodiments, the LMF availability in the edge network can be determined by the LMF profile received from the NRF.

[0039] like Figure 3As shown in the example of , the source RAN (S-RAN) may decide to initiate an N2-based handover to the target RAN (T-RAN) at 300. The decision to initiate the handover may be, for example, due to new radio conditions caused by UE mobility or load balancing, if there is no Xn connection to the T-RAN, an error indication from the T-RAN after an unsuccessful Xn-based handover (i.e., no IP connection between the T-RAN and the S-UPF), or based on dynamic information learned by the S-RAN, etc.

[0040] like Figure 3 As further shown in the example of , at 310, the S-RAN may send a handover required message to the source AMF (S-AMF), which may include, for example, a target ID, a source-to-target transparent container, a SM N2 information list, a PDU session ID, an intra-system handover indication, etc. In an embodiment, at 320a, the S-AMF may send a discovery request (Nnrf_NFDiscovery_Request) to the NRF, and at 320b, one or more matching LMF profiles may be obtained in the (Nnrf_NFDiscovery_Request) response message, which indicates whether any LMF is serving the T-RAN area, i.e., TAI, local DNAI, etc.

[0041] exist Figure 3 In the example of , at 330, the S-AMF may select a target AMF (T-AMF) based on the "AMF selection function". When selecting the T-AMF, the S-AMF additionally considers the availability of LMFs in the candidate T-AMFs based on the service area indication in the T-AMF profile. Figure 3 As shown in the example of , at 340, the S-AMF may send a request to create a UE context (Namf_Communication_CreateUEContext Request) to the T-AMF.

[0042] like Figure 3As further shown in the example of , at 350, the remainder of the handover preparation process can be performed. For example, the handover preparation process performed at 350 can include a process as specified in 3GPP TS 23.502v16.5.1. At 360, a create UE context response (Namf_Communication_CreateUEContext Response) can be sent by the T-AMF to the S-AMF. At 370, a handover command can be sent by the S-AMF to the S-RAN. Then, at 380, a handover command can be provided from the S-RAN to the UE, and at 390, a handover execution process can be performed. Again, as an example, the handover execution process performed at 390 can include a process as specified in 3GPP TS23.502v16.5.1.

[0043] Figure 4A An example flow chart of a method for maintaining certain attributes specific to an LMF profile according to an embodiment is shown, which may be used to select an optimal LMF. In some example embodiments, Figure 4A The flowchart may be performed by a network entity or a network node in a communication system such as LTE or 5G NR. In some example embodiments, the execution Figure 4A The network entity of the method may include or be included in: a base station, an access node, a Node B, an eNB, a gNB, a NG RAN node, etc. In an example embodiment, Figure 4A The method may be performed by a network repository function (NRF) or other node that maintains a profile of available NF instances, such as Figure 1A or Figure 3 An example of NRF is shown in Figure 2.

[0044] like Figure 4A As shown in the example of , the method may include, at 405, storing one or more data network access identifiers (DNAIs), an indication of (one or more) service areas (e.g., regarding TAI), and / or slice information supported by the LMF in the LMF profile. For example, storing 405 may include storing Figure 1B and / or Figure 1C In some embodiments, storage 405 may include storing an LMF profile using an OAM process or via registration of an LMF instance that provides information about supported (one or more) DNAIs, (one or more) service areas (e.g., TAIs), and / or slice information.

[0045] As in Figure 4AAs further shown in the example of , the method may include, at 410, sending the LMF profile and (one or more) DNAIs, an indication of (one or more) service areas or slice information supported by the LMF to the consumer NF. According to some examples, the consumer NF may be an AMF and / or an LMF. According to some embodiments, sending 410 may include sending the LMF profile in response to receiving an LMF discovery request (e.g., Nnrf_NFDiscovery service request) from the consumer NF.

[0046] Figure 4B An example flow chart of a method for selecting an AMF that can best serve a service requested by an edge client (e.g., an LCS client) according to an embodiment is shown. In some example embodiments, Figure 4B The flowchart may be performed by a network entity or a network node in a communication system such as LTE or 5G NR. In some example embodiments, the execution Figure 4B The network entity of the method may include or be included in: a base station, an access node, a Node B, an eNB, a gNB, a NG RAN node, etc. In an example embodiment, Figure 4B The method can be executed by consumers NF, AMF, LMF, etc., for example Figure 1A The example diagram shows a consumer NF or Figure 3 The source AMF is shown in FIG.

[0047] like Figure 4B As shown in the example of , the method may include, at 450, receiving a handover required message from the S-RAN. For example, the handover may include an N2 handover procedure. The method may also include, at 455, sending a LMF discovery request, such as an Nnrf_NFDiscovery request, to a network node. In an embodiment, the network node to which the LMF discovery request is sent may include an NRF. As an example, the sending 455 of the LMF discovery request may be performed in response to receiving a handover required message from the S-RAN.

[0048] In some embodiments, Figure 4B As shown in the example of , the method may also include, at 460, receiving at least one LMF profile for one or more LMFs from the network node. According to an example embodiment, receiving 460 may include receiving (one or more) LMF profiles of (one or more) LMFs that can serve the edge network or LADN corresponding to the new location of the UE. The at least one LMF profile may include at least one of the following DNAI: an indication of (one or more) service areas (e.g., TAI) and / or slice information supported by the LMF. As Figure 4BAs further illustrated in the example of , the method may include, at 465, selecting a T-AMF in the edge network based at least on the DNAI, an indication of (one or more) service areas, and / or slice information received together with at least one LMF profile. According to certain embodiments, selecting 465 may also include selecting the T-AMF by also considering whether there are (one or more) delay-critical location services or LMFs in the edge network. For example, the availability of the LMF in the edge network may be determined by the LMF profile received at 460. In addition, in some embodiments, the method may include selecting an LMF serving the edge network. According to an embodiment, Figure 4B The method may include, at 470, sending a UE context request to the selected T-AMF.

[0049] Figure 4C An example flow chart of a method for selecting an AMF that can best serve a service requested by an edge client (e.g., an LCS client) according to one embodiment is shown. In some example embodiments, Figure 4C The flowchart may be performed by a network entity or a network node in a communication system such as LTE or 5G NR. In some example embodiments, the execution Figure 4C The network entity of the method may include the following or be included therein: a base station, an access node, a Node B, an eNB, a gNB, a NGRAN node, etc. In an example embodiment, Figure 4C The method can be executed by consumers NF, AMF, LMF, etc., for example Figure 1A The example diagram shows a consumer NF or Figure 3 The source AMF is shown in FIG.

[0050] like Figure 4C As shown in the example of , the method may include, at 480, sending a LMF discovery request to a network node. For example, in an embodiment, the LMF discovery request may be a Nnrf_NFDiscovery request. In an embodiment, the network node to which the LMF discovery request is sent may include an NRF. In some embodiments, as Figure 4C As shown in the example of , the method may also include, at 490, receiving at least one LMF profile for one or more LMFs from the network node, wherein the at least one LMF profile may include at least one of the following: DNAI, an indication of (one or more) service areas (e.g., TAI), and / or slice information supported by the LMF. According to an example embodiment, receiving 490 may include receiving (one or more) LMF profiles of (one or more) LMFs that can serve an edge network or LADN corresponding to the new location of the UE.

[0051] Figure 5AAn example of an apparatus 10 according to an embodiment is shown. In an embodiment, the apparatus 10 may be a node, a host, or a server in a communication network or serving such a network. For example, the apparatus 10 may be a satellite, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point, a next generation Node B (NG-NB or gNB), a transmission reception point (TRP), a high altitude platform station (HAPS), an integrated access and backhaul (IAB) node, and / or a WLAN access point associated with a radio access network such as an LTE network, 5G or NR. In an example embodiment, the apparatus 10 may represent a control node in an S-RAN, such as Figure 3 shown.

[0052] It should be understood that in some example embodiments, the device 10 may include an edge cloud server as a distributed computing system, wherein the server and the radio nodes may be independent devices that communicate with each other via a radio path or via a wired connection, or wherein they may be located in the same entity and communicate via a wired connection. For example, in certain example embodiments where the device 10 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functionality. In such an architecture, the CU may be a logical node that includes gNB functionality, such as transmission of user data, mobility control, radio access network sharing, positioning and / or session management. The CU may control the operation of (one or more) DUs via a fronthaul interface. Depending on the functional splitting option, the DU may be a logical node that includes a subset of gNB functionality. It should be noted that a person of ordinary skill in the art will understand that the device 10 may include Figure 5A Components or features not shown.

[0053] like Figure 5A As shown in the example of , the device 10 may include a processor 12 for processing information and executing instructions or operations. The processor 12 may be any type of general or special purpose processor. In fact, as an example, the processor 12 may include one or more of the following, as examples: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture or any other processing component.

[0054] although Figure 5A A single processor 12 is shown in FIG. 1 , but according to other example embodiments, multiple processors may be utilized. For example, it should be understood that in some embodiments, apparatus 10 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in which case processor 12 may represent a multiprocessor). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0055] Processor 12 may perform functions associated with the operation of device 10, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 10, including processing related to communication resource management.

[0056] The device 10 may also include or be coupled to a memory 14 (internal or external), which may be coupled to the processor 12 for storing information and instructions that may be executed by the processor 12. The memory 14 may be one or more memories, and may be any type of memory suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and / or removable memory. For example, the memory 14 may include any combination of the following: random access memory (RAM), read-only memory (ROM), static storage such as a magnetic disk or optical disk, a hard disk drive (HDD) or any other type of non-transient machine or computer readable medium, or other suitable storage components. The instructions stored in the memory 14 may include program instructions or computer program code that, when executed by the processor 12, enables the device 10 to perform the tasks described herein.

[0057] In an embodiment, the device 10 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software executed by the processor 12 and / or the device 10.

[0058] In some embodiments, the device 10 may also include or be coupled to one or more antennas 15 for sending and receiving signals and / or data to and from the device 10. The device 10 may also include or be coupled to a transceiver 18 configured to send and / or receive information. The transceiver 18 may include, for example, multiple radio interfaces that may be coupled to (multiple) antennas 15, or may include any other suitable transceiver components. In some embodiments, the radio interface may correspond to a variety of radio access technologies, including one or more of the following: GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, Radio Frequency Identifier (RFID), Ultra-Wideband (UWB), MulteFire, etc. According to an example embodiment, the radio interface may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, Fast Fourier Transform (FFT) modules, etc., to, for example, generate symbols or signals for transmission via one or more downlinks and receive symbols (e.g., via an uplink).

[0059] Thus, the transceiver 18 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 15, and to demodulate information received via the antenna(s) 15 for further processing by other elements of the apparatus 10. In other example embodiments, the transceiver 18 is capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some embodiments, the apparatus 10 may include input devices and / or output devices (I / O devices) or input / output components.

[0060] In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. These modules may include, for example, an operating system that provides operating system functionality for device 10. Memory may also store one or more functional modules, such as applications or programs, to provide additional functionality to device 10. The components of device 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[0061] According to some embodiments, the processor 12 and the memory 14 may be included in or may form part of a processing circuit or a control circuit. Furthermore, in some embodiments, the transceiver 18 may be included in or may form part of a transceiver circuit.

[0062] As used herein, the term "circuit" may refer to a hardware circuit implementation only (e.g., analog and / or digital circuits), a combination of hardware circuits and software, a combination of analog and / or digital hardware circuits and software / firmware, any portion of a hardware processor(s) with software (including a digital signal processor) that work together to enable a device (e.g., device 10) to perform various functions, and / or hardware circuit(s) and / or processor(s), or portions thereof, which operate using software but which may not be present when software is not required for operation. As another example, as used herein, the term "circuit" may also cover an implementation of a hardware circuit or processor only (or multiple processors), or a portion of a hardware circuit or processor and its accompanying software and / or firmware. The term circuit may also cover, for example, a baseband integrated circuit in a server, a cellular network node or device, or other computing or network device.

[0063] As described above, in some embodiments, the apparatus 10 may be a network node or a RAN node, such as a base station, an access point, a Node B, an eNB, a gNB, a TRP, a HAPS, an IAB node, a WLAN access point, etc. In an example embodiment, the apparatus 10 may be a network node in an S-RAN, for example, Figure 3 For example, in some embodiments, the apparatus 10 may be configured to perform one or more processes described in any of the flowcharts or signaling diagrams described herein, such as those shown in Figures 1, 3, or 4A, 4B, or 4C. In some embodiments, as discussed herein, the apparatus 10 may be configured to perform processes related to LMF selection and / or AMF relocation, for example.

[0064] In some embodiments, the device 10 may be controlled by the memory 14 and the processor 12 to decide to trigger relocation, for example, via an N2 handover process. According to an embodiment, the device 10 may then be controlled by the memory 14 and the processor 12 to send a handover required message to the S-AMF (i.e., the AMF associated with the source network). According to certain embodiments, the device 10 may be controlled by the memory 14 and the processor 12 to receive a handover command from the S-AMF and provide the handover command to the UE so that the handover can be performed.

[0065] Figure 5BAn example of an apparatus 20 according to another embodiment is shown. In an embodiment, the apparatus 20 may be a node or element in a communication network or associated with such a network, such as a satellite, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point, a next generation Node B (NG-NB or gNB) and / or a WLAN access point associated with a radio access network such as an LTE network, 5G or NR. According to one embodiment, the apparatus 20 may be or may be included in: a network repository function (NRF) or other node that maintains a profile of available NF instances, such as Figure 1A or Figure 3 An example of NRF is shown in Figure 2.

[0066] It should be understood that in some example embodiments, the device 20 may include an edge cloud server as a distributed computing system, where the server and the radio nodes may be independent devices that communicate with each other via a radio path or via a wired connection, or they may be located in the same entity and communicate via a wired connection. For example, in certain example embodiments where the device 20 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides the gNB functions. In such an architecture, the CU may be a logical node that includes gNB functions such as transmission of user data, mobility control, radio access network sharing, positioning and / or session management. The CU may control the operation of (one or more) DUs via a fronthaul interface. Depending on the functional splitting option, the DU may be a logical node that includes a subset of gNB functions. It should be noted that a person of ordinary skill in the art will understand that the device 20 may include Figure 5B Components or features not shown.

[0067] In some example embodiments, the apparatus 20 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage device, etc.), one or more radio access components (e.g., modem, transceiver, etc.), and / or a user interface. In some embodiments, the apparatus 20 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technology. It should be noted that one of ordinary skill in the art will appreciate that the apparatus 20 may include Figure 5B Components or features not shown.

[0068] like Figure 5BAs shown in the example of , the device 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general or special purpose processor. In fact, as examples, the processor 22 may include one or more of the following, as examples: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 5B A single processor 22 is shown in FIG. 1 , but according to other embodiments, multiple processors may be utilized. For example, it should be understood that in some embodiments, the apparatus 20 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in which case the processor 22 may represent a multiprocessor). In some embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0069] Processor 22 may perform functions associated with the operation of device 20 including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 20, including processing related to communication resource management.

[0070] The device 20 may also include or be coupled to a memory 24 (internal or external), which may be coupled to the processor 22 for storing information and instructions that may be executed by the processor 22. The memory 24 may be one or more memories, and may be any type of memory suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and / or removable memory. For example, the memory 24 may include any combination of the following: random access memory (RAM), read-only memory (ROM), static storage such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transient machine or computer readable medium. The instructions stored in the memory 24 may include program instructions or computer program code that, when executed by the processor 22, enables the device 20 to perform the tasks described herein.

[0071] In an embodiment, the device 20 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software executed by the processor 22 and / or the device 20.

[0072] In some embodiments, the device 20 may also include or be coupled to one or more antennas 25 for receiving downlink signals and transmitting from the device 20 via an uplink. The device 20 may also include a transceiver 28 configured to send and receive information. The transceiver 28 may also include a radio interface (e.g., a modem) coupled to the antenna 25. The radio interface may correspond to a variety of radio access technologies, including one or more of the following: GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components, such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or uplink, such as OFDM symbols.

[0073] For example, the transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 25, and demodulate information received via the antenna(s) 25 for further processing by other elements of the device 20. In other embodiments, the transceiver 28 is capable of directly sending and receiving signals or data. Additionally or alternatively, in some embodiments, the device 20 may include input and / or output devices (I / O devices). In some embodiments, the device 20 may also include a user interface, such as a graphical user interface or a touch screen.

[0074] In an embodiment, the memory 24 stores software modules that provide functionality when executed by the processor 22. These modules may include, for example, an operating system that provides operating system functionality for the device 20. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality to the device 20. The components of the device 20 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, the device 20 may optionally be configured to communicate with the device 10 or the device 30 via a wireless or wired communication link or interface 70 according to any radio access technology (such as NR).

[0075] According to some embodiments, the processor 22 and the memory 24 may be included in a processing circuit or a control circuit or may form a part of a processing circuit / component or a control circuit / component. In addition, in some embodiments, the transceiver 28 may be included in a transceiver circuit or a transceiver component or may form a part of a transceiver circuit or a transceiver component.

[0076] As described above, according to some embodiments, for example, the device 20 may be a network repository function (NRF) or other node that maintains a profile of available NF instances. According to certain embodiments, the device 20 may be controlled by the memory 24 and the processor 22 to perform functions associated with the example embodiments described herein. For example, in some embodiments, the device 20 may be configured to perform one or more processes described in any of the flowcharts or signaling diagrams described herein, such as those shown in Figures 1, 3, 4A, 4B, or 4C. In certain embodiments, the device 20 may include or represent an NRF, such as one or more NRFs shown in the accompanying drawings and discussed elsewhere herein. According to an embodiment, for example, the device 20 may be configured to perform processes related to LMF selection and / or AMF relocation.

[0077] In some embodiments, the apparatus 20 may be controlled by the memory 24 and the processor 22 to store in the LMF profile: at least one or more DNAIs, an indication of (one or more) service areas (e.g., about TAI) and / or slice information supported by the LMF. For example, the apparatus 20 may be controlled by the memory 24 and the processor 22 to store Figure 1B and / or Figure 1C In some embodiments, the device 20 can be controlled by the memory 24 and the processor 22 to store an LMF profile using an OAM process or via registration of an LMF instance, which provides information about supported (one or more) DNAIs, (one or more) service areas (e.g., TAIs) and / or slice information.

[0078] According to an embodiment, the device 20 may be controlled by the memory 24 and the processor 22 to send a LMF profile including (one or more) DNAIs, an indication of (one or more) service areas, or slice information supported by the LMF to the consumer NF. According to some examples, the consumer NF may be an AMF and / or an LMF. According to some embodiments, in response to receiving an LMF discovery request (e.g., an Nnrf_NFDiscovery service request) from the consumer NF, the device 20 may be controlled by the memory 24 and the processor 22 to send the LMF profile.

[0079] Figure 5CAn example of an apparatus 30 according to another example embodiment is shown. In an example embodiment, the apparatus 30 may be a node or element in a communication network or associated with such a network, such as a satellite, a base station, a Node B, an evolved Node B (eNB), a 5G Node B or access point, a next generation Node B (NG-NB or gNB) and / or a WLAN access point associated with a radio access network such as an LTE network, 5G or NR. According to one embodiment, the apparatus 30 may be or may be included in: a consumer NF, such as an AMF or LMF.

[0080] In some example embodiments, the apparatus 30 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage device, etc.), one or more radio access components (e.g., modem, transceiver, etc.), and / or a user interface. In some example embodiments, the apparatus 30 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, MulteFire, and / or any other radio access technology. It should be noted that a person of ordinary skill in the art will understand that the apparatus 30 may include Figure 5C Components or features not shown.

[0081] like Figure 5C As shown in the example of , the device 30 may include or be coupled to a processor 32 for processing information and executing instructions or operations. The processor 32 may be any type of general or special purpose processor. In fact, as examples, the processor 32 may include one or more of the following, as examples: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although Figure 5C A single processor 32 is shown in FIG. 1 , but according to other example embodiments, multiple processors may be utilized. For example, it should be understood that in some example embodiments, the apparatus 30 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in which case the processor 32 may represent a multiprocessor). In some example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0082] Processor 32 may perform functions associated with the operation of device 30 including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 30, including processing related to communication resource management.

[0083] The device 30 may also include or be coupled to a memory 34 (internal or external), which may be coupled to the processor 32 for storing information and instructions that may be executed by the processor 32. The memory 34 may be one or more memories, and may be any type of memory suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and / or removable memory. For example, the memory 34 may include any combination of the following: random access memory (RAM), read-only memory (ROM), static storage such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transient machine or computer readable medium. The instructions stored in the memory 34 may include program instructions or computer program code that, when executed by the processor 32, enables the device 30 to perform the tasks described herein.

[0084] In an example embodiment, the device 30 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store a computer program or software executed by the processor 32 and / or the device 30.

[0085] In some example embodiments, the apparatus 30 may also include or be coupled to one or more antennas 35 for receiving downlink signals and transmitting from the apparatus 30 via an uplink. The apparatus 30 may also include a transceiver 38 configured to send and receive information. The transceiver 38 may also include a radio interface (e.g., a modem) coupled to the antenna 35. The radio interface may correspond to a variety of radio access technologies, including one or more of the following: GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, BT-LE, RFID, UWB, etc. The radio interface may include other components, such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or uplink, such as OFDM symbols.

[0086] For example, the transceiver 38 may be configured to modulate information onto a carrier waveform for transmission by the antenna(s) 35, and demodulate information received via the antenna(s) 35 for further processing by other elements of the apparatus 30. In other example embodiments, the transceiver 28 is capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some example embodiments, the apparatus 30 may include input and / or output devices (I / O devices). In certain example embodiments, the apparatus 30 may also include a user interface, such as a graphical user interface or a touch screen.

[0087] In an example embodiment, the memory 34 stores software modules that provide functionality when executed by the processor 32. These modules may include, for example, an operating system that provides operating system functionality for the device 30. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality to the device 30. The components of the device 30 may be implemented in hardware, or as any suitable combination of hardware and software. According to an example embodiment, the device 30 may optionally be configured to communicate with the device 10 via a wireless or wired communication link or interface 70 and / or communicate with the device 20 via a wireless or wired communication link or interface 72 according to any radio access technology (such as NR).

[0088] According to some example embodiments, the processor 32 and the memory 34 may be included in or may form part of a processing circuit or a control circuit. In addition, in some example embodiments, the transceiver 38 may be included in or may form part of a transceiver circuit.

[0089] As described above, according to some example embodiments, for example, the apparatus 30 may be a consumer NF, such as an AMF or LMF. According to some example embodiments, the apparatus 30 may be controlled by the memory 34 and the processor 32 to perform functions associated with the example embodiments described herein. For example, in some example embodiments, the apparatus 30 may be configured to perform one or more processes shown in any of the diagrams or signaling flow diagrams described herein, such as the processes shown in Figures 1, 3, 4A, 4B, or 4C. As an example, the apparatus 30 may correspond to or represent an S-AMF, such as Figures 1 or 4C. Figure 3 According to some example embodiments, for example, the apparatus 30 may be configured to perform processes related to LMF selection and / or AMF relocation.

[0090] In some embodiments, the device 30 may be controlled by the memory 34 and the processor 32 to receive a handover required message from the S-RAN. For example, the handover may include an N2 handover process. According to an embodiment, the device 30 may be controlled by the memory 34 and the processor 32 to send an LMF discovery request, such as an Nnrf_NFDiscovery request, to a network node. In an embodiment, the network node to which the LMF discovery request is sent may include an NRF. As an example, in response to receiving a handover required message from the S-RAN, the device 30 may be controlled by the memory 34 and the processor 32 to send an LMF discovery request.

[0091] In some embodiments, the device 30 may be controlled by the memory 34 and the processor 32 to receive at least one LMF profile for one or more LMFs from a network node. In an example embodiment, the (one or more) LMFs may include those LMFs serving an edge network or LADN corresponding to the new location of the UE. The at least one LMF profile may include at least one of the following: a DNAI, an indication of (one or more) service areas (e.g., a TAI), and / or slice information supported by the LMF. According to an embodiment, the device 30 may be controlled by the memory 34 and the processor 32 to select a T-AMF in an edge network based at least on the DNAI, the indication of (one or more) service areas, and / or the slice information received together with the at least one LMF profile. In some embodiments, the device 30 may be controlled by the memory 34 and the processor 32 to select an LMF serving an edge network. According to an embodiment, the device 30 may be controlled by the memory 34 and the processor 32 to send a UE context request to the selected T-AMF.

[0092] In some embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20 and / or apparatus 30) may include components for performing the methods or any processes or variations discussed herein, such as those described in reference to Figure 4A , 4B Examples of components may include one or more processors, memories, and / or computer program code for causing operations to be performed.

[0093] Therefore, certain example embodiments provide several technical improvements, enhancements and / or advantages over prior art processes, and constitute improvements in at least the technical field of wireless network control and management. For example, as discussed in detail above, certain example embodiments provide enhanced LMF profile support to achieve optimal LMF selection. In addition, some example embodiments provide for AMF relocation, for example, considering location service requirements. Therefore, the advantage of certain embodiments is that it is possible to select the best LMF, select the most suitable AMF that can best serve the service requested by the edge client. In other words, certain embodiments result in the selection of (one or more) AMF instances and LMF services that are supported and optimally positioned to serve the edge network or LADN service to help unload core network services and reduce or avoid signaling deep into the core network. In addition, certain embodiments can ensure the continuity of ongoing LCS sessions, and / or, in the case where the UE is at the target location, ensure that the target AMF is selected considering the availability of the edge LMF. In addition, some embodiments can reduce round-trip delays, help keep signaling local (e.g., within the edge network), and better serve delay-critical location (and other) service requests. Thus, use of certain example embodiments results in improved functionality of a communication network and its nodes (such as base stations, eNBs, gNBs and / or IoT devices, UEs or mobile stations).

[0094] In some example embodiments, the functionality of any method, process, signaling diagram, algorithm, or flow chart described herein may be implemented by software and / or computer program code or portion of code stored in a memory or other computer-readable or tangible medium and executed by a processor.

[0095] In some example embodiments, the apparatus may include or be associated with at least one of the following: a software application, module, unit, or entity configured for (multiple) arithmetic operations, or configured as a program or program portion (including added or updated software routines) that can be executed by at least one computing processor or controller. A program (also referred to as a program product or computer program, including software routines, applets, and macros) may be stored in any apparatus-readable data storage medium and may include program instructions for performing specific tasks.

[0096] The computer program product may include one or more computer executable components that are configured to perform some example embodiments when the program is run. The one or more computer executable components may be at least one software code or code portion. Modifications and configurations required to implement the functionality of the example embodiments may be performed as (multiple) routines that may be implemented as (multiple) software routines that are added or updated. In one example, (multiple) software routines may be downloaded to a device.

[0097] As an example, software or computer program code or code portions may be in source code form, object code form, or some intermediate form, and may be stored in some carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. For example, such a carrier may include a recording medium, a computer memory, a read-only memory, an optoelectronic and / or electrical carrier signal, a telecommunications signal, and / or a software distribution package. Depending on the processing power required, the computer program may be executed in a single electronic digital computer, or may be distributed among multiple computers. The computer readable medium or computer readable storage medium may be a non-transient medium.

[0098] In other example embodiments, the functions of the example embodiments may be performed by hardware or circuitry included in a device, such as by using an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functions of the example embodiments may be implemented as a signal carried by an electromagnetic signal downloaded from the Internet or other network, such as by non-tangible means.

[0099] According to example embodiments, an apparatus such as a node, a device or a corresponding component may be configured as a circuit, a computer or a microprocessor such as a single-chip computer element, or as a chipset, which may include at least a memory for providing storage capacity for (multiple) arithmetic operations and / or an operation processor for performing (multiple) arithmetic operations.

[0100] The example embodiments described herein may apply to both singular and plural implementations, regardless of whether singular or plural language is used in conjunction with describing certain embodiments. For example, an embodiment describing the operation of a single network node is also applicable to an embodiment including multiple instances of the network node, and vice versa.

[0101] Those skilled in the art will readily appreciate that the example embodiments discussed above may be implemented using processes in a different order and / or hardware elements that are different from the disclosed configurations. Therefore, although some embodiments have been described based on these example embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative configurations will be apparent while remaining within the spirit and scope of the example embodiments.

Claims

1. A method comprising: At the network node, storing in a positioning management function profile at least one of: one or more data network access identifiers, an indication of one or more service areas, or slice information supported by the positioning management function; as well as Sending the positioning management function profile having at least one of the following to a consumer network function: one or more data network access identifiers, an indication of one or more service areas, or slice information supported by the positioning management function.

2. The method according to claim 1, wherein the sending comprises: The location management function profile is sent in response to receiving a location management function discovery request from the customer network function.

3. The method according to claim 1 or 2, wherein the storing comprises: The positioning management function profile is stored using operations, administration and maintenance procedures or via registration of a positioning management function instance to the network node.

4. The method of any one of claims 1-3, wherein the indication of the one or more service areas comprises a tracking area identifier.

5. The method according to any one of claims 1-4, wherein the network node comprises a network repository function.

6. The method according to any one of claims 1-5, wherein the consumer network function comprises at least one of the following: an access and mobility management function or a positioning management function or any other 5G core network function.

7. A method comprising: Sending a location management function discovery request to a network node; as well as At least one positioning management function profile of one or more positioning management functions is received from the network node, wherein the at least one positioning management function profile includes at least one of the following: one or more data network access identifiers, indications of one or more service areas, or slice information supported by the positioning management function.

8. The method according to claim 7, further comprising: A target access and mobility management function is selected based at least on one or more data network access identifiers, indications of one or more service areas, or slice information received along with the at least one positioning management function profile.

9. The method according to claim 7 or 8, further comprising: A user equipment context request is sent to the selected target access and mobility management function.

10. The method according to any one of claims 7 to 9, wherein the sending of the positioning management function discovery request comprises: The positioning management function discovery request is sent when a handover required message is received from a source radio access network.

Images