Methods for supporting transport of positioning data over streaming channel

Abstract

A method in a network node is disclosed. The method includes receiving an indication of an UL URI corresponding to a LMF. The method includes establishing a communication channel with the LMF using the URI, the communication channel bypassing an AMF. The method includes transmitting positioning information via the communication channel.

Description

METHODS FOR SUPPORTING TRANSPORT OF POSITIONING DATA OVER STREAMING CHANNEL FIELD

[0001] The present disclosure relates to wireless communications, and in particular, to supporting transport of positioning data over streaming channel.BACKGROUNDPositioning Architecture in 5G

[0002] Positioning in 3GPP New Radio (NR) is supported by the architecture shown in Figure 1. The Location Management Function (LMF) is the location server node in NR. There are also interactions between the LMF and the gNodeB via the NR Positioning Protocol A (NRPPa) protocol. The interactions between the gNodeB and the device is supported via the Radio Resource Control (RRC) protocol, while the LMF interfaces with the UE via the LTE positioning protocol (LPP). LPP is common to both NR and Long-Term Evolution (LTE).

[0003] Figure 1 shows user equipment (UE) Positioning Overall Architecture applicable to NG-Radio Access Network.

[0004] In positioning framework, the LMF interacts with the Access and Mobility Management Function (AMF), where AMF receives a request for some location service associated with a particular target UE from another entity (e.g., Gateway Mobile Location Centre (GMLC) or user equipment, UE) or the AMF itself decides to initiate some location service on behalf of a particular target UE (e.g., for an IP Multimedia Subsystem (IMS) emergency call from the UE) as described in TS 23.502 and TS 23.273. The AMF then sends a location services request to an LMF. The LMF processes the location services request which may include transferring assistance data to the target UE to assist with UE-based and / or UE-assisted positioning and / or may include positioning of the target UE. The LMF then returns the result of the location service back to the AMF (e.g. , a position estimate for the UE. In the case of a location service requested by an entity other than the AMF (e.g., a GMLC or UE), the AMF returns the location service result to this entity. The next generation (NG) control plane interface (NG-C) is defined between the NG-RAN and the AMF and facilitates signalling between the NG-RAN and the AMF.

[0005] Figure 2 shows Location Service Support by NG-RAN.

[0006] The positioning method may for example be multi-Round Trip Time (Multi-RTT) positioning, which involves both UE measurements (steps 3b in Fig 2-1) and gNBmeasurements (steps 3a in Fig2-1). Both UE and gNB measurements require DownLink Positioning Reference Signal (DL PRS) and UpLink Sounding Reference Signal (UL SRS). The UE is configured with UL SRS based on gNB, after receiving a recommendation from LMF. The UE shall measure the time difference between reception of PRS and transmission of SRS. The gNB shall measure the time difference between reception of SRS and transmission of PRS.

[0007] With Positioning Information Exchange procedures, LMF requests allocation of SRS resources from the gNB, e.g., as specified in 8.2.6.2 of 3GPP Technical Specification (TS) 38.455 vl 8.5.0. Figure 3 shows a Positioning Information Request procedure.

[0008] With the Measurement procedure, when sounding reference signal (SRS) resources are known in LMF after gNB decision on the configuration for UE’s SRS, the LMF requests measurements from one or more gNBs and for several transmission reception points (TRPs), e.g., as specified in 3GPP TS 38.455 vl 8.5.0. Figure 4 shows a measurement procedure.

[0009] The Measurement procedure, uses NG Application Protocol (NGAP) nonassociated signalling, meaning that the measurements are done using the SRS configuration and RAN is not aware of which UE the measurements are related to.

[0010] Measurements supported by the Measurement Procedure:• gNB-RxTxTimeDiffUL,• SRS-reference signal received power (SRS-RSRP),• Uplink angle of arrival (UL-AoA),• Uplink relative time of arrival (UL-RTOA),• Multiple UL-AoA,• UL SRS-reference signal received path power (SRS-RSRPP),• Uplink received signal code power (UL-RSCP).

[0011] The overall signalling for Multi-RTT is detailed in Figure 5, which shows details of NG-RAN and UE based procedures from Fig. 2.1 for UL SRS Measurement overall procedure.

[0012] There currently exist certain challenge(s). The positioning architecture and framework developed in 5G relies on interactions between the RAN and the core network (CN) for signalling exchanges that enable the positioning of a UE.

[0013] In particular, the LoCation System (LCS) framework is very dependent on interaction between AMF and LMF, and between AMF and gNB to trigger positioning request and report positioning messages. More specifically, the AMF transfers NRPPa messagesbetween the gNB and the LMF. This generates transport latency for propagation delays between nodes, as show below (from TR 38.857):Table 5.2.3.1.2-1: Latency Components

[0014] Also, for large measurement reports, e.g., device sensor data from multiple gNBs / TRPs, measurements from thousands of devices, Artificial Intelligence / Machine Learning (AI / ML) training data, or periodic measurements reports, etc., the AMF will have to handle the load generated by such communication, which may translate into long signalling sessions with considerable processing load. At the same time, the control plane interface between the RAN and the CN will have to handle high data rates. This may result into a bottleneck situation. The load on the AMF and NG control plane interface (NG-C) will become too high to handle to a point where the AMF’s and NG-C other regular functionalities, such as mobility, dynamic signalling with other network functions and context management will be impacted.

[0015] In general terms, a positioning framework where all positioning procedures imply a signalling interaction directly involving middle point functions, such as the AMF, or control plane interfaces not dimensioned for high load and long lasting sessions, may result into overload and failure issues.SUMMARY

[0016] A problem this disclosure addresses is how to maintain a positioning framework similar to what has been followed so far in 5G networks while removing the issues of overloads and bottlenecks at CN functions and over control plane interfaces.

[0017] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. In this disclosure, we present methods for transferring positioning measurement reports from the RAN, e.g. a gNB, to a location management function, e.g. the 5G LMF, without transferring these messages via a mid point function / node, such as the AMF. This is to eliminate the problem caused by the mid point function, e.g. the AMF, and the control plane interface towards it to quickly becoming a bottleneck for the larger positioning control traffic, e.g. NRPPa, and to reduce the latency incurred during long and periodic sessions.

[0018] At the same time, similar methods are introduced for the transferring of data from the location management function, e.g. the 5G LMF, to the RAN, e.g. the gNB, in cases such data transferring consists of e.g. frequent reporting of data for long durations of time.

[0019] One specific use case where such methods are applicable is data collection in AI / ML supported positioning use cases, where the RAN needs to acquire data from the LMF reflecting the location of one or more specific UEs for the purpose of, e.g. training AI / MLmodels aimed at inferring positioning measurements for such UE. In such cases a UE positioning session may need to be established, where the RAN needs to provide to the LMF frequent measurements, to enable the LMF to locate the UE and therefore provide UE positioning data to the RAN.

[0020] Another specific use case where such methods are applicable is the retrieval of UE positioning information at the RAN for, e.g. network performance optimization, resource management and mobility purposes. In this case, the RAN may need to collect frequent updates of the UE location for a number of UEs, hence resulting in the frequent uplink and downlink communication with the LMF described above.

[0021] Specifically, we propose that while a CN function such as the AMF, by enabling discovery between the LMF (e.g. identified by its routing ID) and the serving RAN, remains the control node in the establishment of positioning signalling transactions between the RAN and the LMF, e.g. NRPPa sessions, the LMF and the RAN can support procedures to configure new streaming communication channels for UL reporting, where the RAN is enabled to report measurements directly to the LMF via this UL channel.

[0022] This continuous communication channel is also used bidirectionally to transmit positioning data collection information in DL from the LMF to the RAN, where such data may consist of UE location information. Destination addresses for such streaming channels are exchanged between the RAN and the LMF by means of control interfaces, such as the NRPPa.

[0023] The methods in this application are valid for any communication system where interactions between a radio access network and a core network are envisaged for the purpose of positioning of a UE. For the sake of simplicity, the application describes the methods as applied to a 5G system. However, such description should not limit the scope of this disclosure, which might apply to other systems such as 6G systems, where equivalent nodes, interfaces and functions to those taken as example for a 5G oriented description, might be identified.Configuration method between RAN and Positioning function, e.g. over NRPPa:

[0024] The LMF transfers a first DL NRPPa message via the AMF and over NG-C to NG-RAN. The NRPPa message from LMF contains specific receiver's address information for the uplink communication channel, which can be called an Uplink Uniform Resource Identifier (UL URI), identifying the Streaming communication channel over which the positioning data will be streamed directly from NG-RAN to LMF in UL.

[0025] The NG-RAN transfers an UL NRPPa message to the LMF via the AMF and over NG-C to LMF. The NRPPa message from NG-RAN contains specific receiver's address information for the downlink communication channel, which can be called a Downlink Uniform Resource Identifier (DL URI), identifying the Streaming communication channel over which the positioning data will be streamed directly from LMF to NG-RAN in DL.Configuration method based on RAN-CN signalling, e.g. over NGAP:

[0026] The AMF alternatively signals over existing or new NGAP’s procedures for Tracing, configuration information instructing the RAN to signal positioning information to LMF via a streaming channel indicated by the UL URI in the Trace Activation IE defined in TS 38.413 with new indication.

[0027] Certain embodiments may provide one or more of the following technical advantage(s). This disclosure provides methods, systems, and devices to establish an “ad hoc” streaming channel to enable large data transfers between the NG-RAN and the LMF, to reduce the latency and high signalling loads over control plane signalling and without impacting AMF regular functionality.

[0028] According to one aspect of the present disclosure, a method in a network node is provided. The method includes receiving an indication of an Uplink (UL) Uniform Resource Identifier (URI) corresponding to a Location Management Function (LMF). The method includes establishing a communication channel with the LMF using the URI, the communication channel bypassing an Access and Mobility Management Function (AMF). The method includes transmitting positioning information via the communication channel.

[0029] According to another aspect of the present disclosure, a network node is provided. Network node is configured to receive an indication of an UL URI corresponding to a LMF. Network node is configured to establish a communication channel with the LMF using the URI, the communication channel bypassing an AMF. Network node is configured to transmit positioning information via the communication channel.

[0030] According to another aspect of the present disclosure, a method in an LMF is provided. The method includes transmitting an indication of an UL URI corresponding to the LMF. The method includes establishing a communication channel with a network node based on the URI, the communication channel bypassing an AMF. The method includes receiving positioning information via the communication channel.

[0031] According to another aspect of the present disclosure, an LMF is provided. LMF is configured to transmit an indication of an UL URI corresponding to the LMF. LMF is configured to establish a communication channel with a network node based on the URI, the communication channel bypassing an AMF. LMF is configured to receive positioning information via the communication channel.BRIEF DESCRIPTION OF THE DRAWINGS

[0032] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0033] Figure 1 is a schematic diagram of a UE Positioning Overall Architecture applicable to NG-Radio Access Network;

[0034] Figure 2 is a diagram of Location Service Support by NG-RAN;

[0035] Figure 3 is a diagram of a Positioning Information Request procedure;

[0036] Figure 4 is a diagram of a measurement procedure;

[0037] Figure 5 is a diagram of NG-RAN and UE based procedures from for UL SRS Measurement;

[0038] Figure 6 is a diagram of a configuration of DL and UL streaming channels for periodic positioning information data report and periodic report of measurements in accordance with some embodiments;

[0039] Figure 7 shows an example of a communication system in accordance with some embodiments;

[0040] Figure 8 is another example of a communication system in accordance with some embodiments;

[0041] Figure 9 is a schematic diagram of a wireless device in accordance with some embodiments;

[0042] Figure 10 is a schematic diagram of a network node in accordance with some embodiments;

[0043] Figure 11 is a schematic diagram of a virtualization environment in accordance with some embodiments;

[0044] Figure 12 is a flowchart of an example process in a network node in accordance with some embodiments; and

[0045] Figure 13 is a flowchart of an example process in an LMF in accordance with some embodiments.DETAILED DECRIPTIQNSome of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.NRPPA embodiments

[0046] In one embodiment, a first network node (e.g., the NG-RAN, LMF) receives an NRPPa message that contains an indication of the URI and the direction, (UL or DL) over which it can initiate reporting of the positioning information (e.g., measurements, training data, UE location, etc.) to a second network node (e.g., LMF, NG-RAN) for a UE.a. Example, the NG-RAN receives an NRPPa message with UL URI with indication to report measurements, and / or training data to the LMF (111) over the indicated UL streaming channel.b. Another example, the LMF receives an NRPPa message with DL URI, with indication to report UE location, ground truth or assistance information for training to the NG-RAN over the DL streaming channel.

[0047] In one embodiment, the first network node replies to the second network node with an NRPPa message to inform whether the reporting over the streaming channel can be successfully setup for the UE or has failed. The failure can be e.g., due to an interaction with a handover procedure, due to resource limitations or due to lack of support of such functionality. A specific cause for the failure may be added within the failure message.

[0048] In one embodiment, the first network node sends the requested positioning information, e.g., the NG-RAN signals positioning measurements needed to position the UE, over the streaming channel that has been setup. If the first network node receives an NRPPa message with a Deactivate Reporting indication from the second network node, it will stop the reporting in the indicated URI for the indicated UE.

[0049] In one embodiment, the second network node receives an update NRPPa message from the first network node to report different positioning information for data collection (e.g., UE location, measurements, ground truths) to first network node by indicating the URI and its direction.

[0050] In one embodiment the first network node triggers the exchange of streaming channel destination address information as part of or as a consequence of a request for UE location information such as the UE position or positioning measurements.a. In one dependent embodiment, such request may consist of periodic positioning information reporting.b. In one dependent embodiment the first node is a RAN node or function and the second node is a positioning function such as the LMF. c. In one dependent embodiment the first node includes in the request the frequency with which the UE position information shall be reported by the second node.d. In one dependent embodiment the first node includes in the request information about the duration of the overall reporting process. Such duration may be quantified as an amount of time during which reporting should be performed, or as a number of sampled for the positioning information requested (e.g. n samples of the UE positioning data).

[0051] In one embodiment, if the second network node cannot report the requested information according to the reporting configuration provided by the first node, e.g. according to the requested frequency / number of samples, one of the following messages can be generated by the second node towards the first node:a. The second node may reply to the first node that the requested reporting characteristics cannot be met. The second node reports to the first node the reporting characteristics that can be fulfilled and it reports according to such characteristics.b. The second node may reply with a failure message. Optionally, the second node may include in the failure message information concerning the reasons why the failure occurred, e.g. the requested reporting frequency cannot be fulfilled.

[0052] In one embodiment, the information to be signalled over the UL or DL streaming interfaces are pre-configured and defined in terms of e.g. structure, size, format. Knowledge of the structure of the information signalled can either be acquired by the first and second node by means of signalling preceding the establishment of the streaming interfaces or by means of pre-configuration.

[0053] In one embodiment, the first network node can be a NG-RAN, gNB-CU, or gNB-DU or LMF.

[0054] In one embodiment, the second network node can be a NG-RAN, gNB-CU, or gNB-DU or LMF.

[0055] In one embodiment, the above steps can be performed over F1AP.

[0056] In one embodiment, the above additions can be done in existing NRPPa Positioning Information exchange procedures or in new procedures defined in NRPPa spec TS 38.455. Figure 6 shows configuration of DL and UL streaming channels for periodic positioning information data report and periodic report of measurements.

[0057] One possible realization in signaling of the above embodiments for the message in step 4 of Figure 6 is shown below. The LMF 111 sends to the gNB a MEASUREMENT REQUEST message (Sec. 9.1.4.1 of TS 38.455) including the new UR7TE.

[0058] 9.1.4.1 MEASUREMENT REQUEST

[0059] This message is sent by the LMF 111 to request the NG-RAN node to configure a positioning measurement.

[0060] Direction: LMF 111 — > NG-RAN node.> <><>""""

[0061] 9.2.x (New)URI

[0062] This IE is an URL

[0063] The LMF 111 may also include the URI IE in a MEASUREMENT UPDATE message (Sec. 9.1.4.5 of TS 38.455) toward the gNB, to request a change in positioning measurement reporting from NRPPa to URI. This can be used to reduce the signaling load to the AMF 113 without interrupting an ongoing positioning session.

[0064] The URI IE can also be added to legacy NRPPa procedures (e.g. E-CID Measurement Initiation), especially for the case of periodic E-CID reporting. In this case, thesignaling load to the AMF 113 can be reduced even for legacy positioning measurement reporting without impacting the positioning method itself.NGAP embodiments

[0065] In one embodiment, the NG-RAN receives an NG-AP message from AMF 113 indicating the URI and positioning information to report to LMF 111. This can be via the legacy Trace Activation IE or via a new NRPPa Trace Activation IE in a new NGAP message as below:

[0066] 9.3.1.X NRPPa Trace Activation

[0067] This IE defines parameters related to a trace positioning session activation.

[0068] In the information above, the LMF 111 instructs the RAN to configure one or more UE to transmit specific reference signals such as SRS. The SRS configuration is provided to the RAN by the AMF 113.

[0069] In an alternative, not shown in the example above, the Trace Activation includes configurations for specific measurements the UE should take. Such measurements are then reported by the RAN over the streaming interface with destination address corresponding to the URI signalled to the RAN.

[0070] In one embodiment, the information contained in the legacy or new trace activation message is generated by the 0AM system and signalled to the RAN via the AMF 113, over NGAP.

[0071] Figure 7 shows an example of a communication system 100 in accordance with some embodiments.

[0072] In the example, the communication system 100 includes a telecommunications network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes or base stations of various types, access network nodes 110A and HOB are depicted (which may be collectively referred to as network nodes 110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 104 may include more than one access network technology. The network nodes 110 of access network 104 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 112A, 112B, 112C, and 112D (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0073] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network nodein the telecommunications network 102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 102, including one or more access network nodes 110 and / or core network nodes 108.

[0074] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies.

[0075] The network nodes 110 facilitate direct or indirect connection of one or more UEs 112 to the core network 106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0076] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with thenetwork nodes 110 and other communication devices. Similarly, the network nodes 108, 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 102) with the UEs 112 and / or with other network nodes or equipment in the telecommunications network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 102. More specifically, UEs 112 may send messages, data, and / or other signals to network nodes 108, 110 or other elements of the telecommunications network 102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 108, 110 may send messages, data, and other signals to UEs 1122, other network nodes 108, 110, and other devices in telecommunications network 102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 112 by transmitting the message to an access network node 110 that will then transmit the message to the intended UE 112. Similarly, a core network node 108 may receive a particular message from a UE 112 by receiving the message from an access network node 110 that itself received the message from the UE 112.

[0077] In the depicted example, the core network 106 connects elements of the access network 104 (e.g., one or more of the network nodes 110) to one or more host computing systems, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one or more core network nodes (e.g., core network node 108) of various types, one or more of which may be generally referred to as network nodes 108. Network nodes 108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDE), Unified DataManagement (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), Location Management Function (LMF) and / or a User Plane Function (UPF).

[0078] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunications network 102. The host 116 may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0079] As a whole, the communication system 100 of Figure 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 100 supporting different standards, protocols, or rule sets.

[0080] As one example, in certain embodiments, access network 104 may contain some access network nodes 110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 110 support (or the same access network nodes 110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 102 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple differentstandard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0081] Telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0082] In some examples, one or more of the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0083] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112C and / or 112D) and network nodes (e.g., network node HOB). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114.

[0084] As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0085] The hub 114 may have a constant / persistent or intermittent connection to the network node HOB. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112C and / or 112D), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node HOB. In other embodiments, the hub 114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0086] Figure 8 is another example of a communication system 200 according to some embodiments. As used herein, the communication system 200 includes multiple access points (APs) 210 (with three exemplary APs 210A, 210B, and 210C being depicted) and multiple wireless devices, referred to in the context of communication system 200 as stations (STAs) 212 (referred to individually as STA 212A, STA 212B, STA 212C, and STA 212D). STA 212A is served by AP 210A in a first basic service set (BSS) 220A. STA 212B and STA 212C are served by AP 210B in a second BSS, BSS 220B. STA 212D is served by AP 210C in a third BSS, BSS 220C. Stations 212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0087] Each of STAs 212 may connect through a radio link to one of APs 210. For example, depending on location or channel conditions experienced by a given STA 212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from afrequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0088] Each AP 210 may provide data connectivity to ST As 212 connected to a particular AP 210. As illustrated, APs 210 may be connected to a data network 230. In this way, APs 210 may also provide data connectivity between STAs 212 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 212 and its serving AP 210 may be used for providing various kinds of services to STA 212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 212 and / or on a device linked to STA 212. By way of example, Figure 8 illustrates an application service platform 232 provided in data network 230. The application(s) executed on STA 212 and / or on one or more other devices linked to STA 212 may use the radio link for data communication with one or more other STA 212 and / or the application service platform 232, thereby enabling utilization of the corresponding service(s) at STA 212.

[0089] Figure 9 shows a wireless device 300, which may be configured to operate in communication system 100 of Figure 7 or in communication system 200 of Figure 8. The wireless device 300 may be alternatively referred to as a UE 300, like a UE 112 within the context of communication system 100, or as a station (STA) 300 or as a non-access-point station (non-AP STA) 300, like a STA 212 within the context of the communication system 200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (FEE), laptop- mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0090] A wireless device 300 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 300 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 300 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0091] In particular embodiments, wireless device 300 includes processing circuitry 302 that is operatively coupled via a bus 304 to an input / output interface 306, a power source 308, a memory 310, a communication interface 312, and / or any other component, or any combination thereof. Certain embodiments of wireless device 300 may include all or a subset of the components shown in Figure 9. The level of integration between the components may vary from one embodiment of wireless device 300 to another. In general, in a particular embodiment of wireless device 300, processing circuitry 302, input / output interface 306, power source 308, memory 310, and communication interface 312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 300. Further, certain embodiments of wireless devices 300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0092] The processing circuitry 302 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 310. The processing circuitry 302 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 302 may include multiple central processing units (CPUs).

[0093] In the example, the input / output interface 306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or outputdevices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 300. Examples of an input device include a touch- sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0094] In some embodiments, the power source 308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 308 may further include power circuitry for delivering power from the power source 308 itself, and / or an external power source, to the various parts of wireless device 300 via input circuitry or an interface such as an electrical power cable. Power source 308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 300 to which power is supplied.

[0095] The memory 310 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 310 includes one or more programs 314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 316. The memory 310 may store, for use by wireless device 300, any of a variety of various operating systems or combinations of operating systems.

[0096] The memory 310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 310 may allow wireless device 300 to access instructions, programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 310, which may be or comprise a device -readable storage medium.

[0097] The processing circuitry 302 may be configured to communicate with an access network or other network via or using the communication interface 312. The communication interface 312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 322. The communication interface 312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 318 and / or a receiver 320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 318 and receiver 320 may be coupled to one or more antennas (e.g., antenna 322) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0098] In the illustrated embodiment, communication functions of the communication interface 312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol(TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0099] In particular embodiments, wireless device 300 may provide an output of data captured via a sensor, through its communication interface 312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 300 can be communicated through a wireless connection to a network node via another wireless device 300. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0100] As another example, wireless device 300 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 300 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0101] Wireless device 300, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 300 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT devicein addition to other components as described in relation to the example embodiment of wireless device 300 shown in Figure 9.

[0102] As yet another specific example, in an loT scenario, wireless device 300 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 300 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 300 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 300 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0103] In practice, any number of wireless devices 300 may be used together with respect to a single use case. For example, a first wireless device 300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 300 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 300 can also include more than one of the functionalities described above. For example, wireless device 300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0104] Figure 10 shows a network node 400 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 400 may be configured to operate in communication system 100 of Figure 7, like network nodes 108 or 110, or in communication system 200 of Figure 8, like an AP 210 or a station 212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0105] Network nodes 400 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro basestations, or macro base stations. Network node 400 may be a relay node or a relay donor node controlling a relay. Network nodes 400 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0106] Other examples of network nodes 400 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0107] In particular embodiments, network node 400 includes a processing circuitry 402, a memory 404, a communication interface 406, and a power source 408. In general, in a particular embodiment of network node 400, processing circuitry 402, memory 404, communication interface 406, and power source 408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 400.

[0108] The network node 400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 404 or portions of memory 404 for different RATs) and some components may be reused (e.g., a same antenna 410 may be shared by different RATs). The network node 400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 400.

[0109] The processing circuitry 402 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 404, to provide network node 400 functionality.

[0110] In some embodiments, the processing circuitry 402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 402 includes one or more of radio frequency (RF) transceiver circuitry 412 and baseband processing circuitry 414. In some embodiments, the RF transceiver circuitry 412 and the baseband processing circuitry 414 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 412 and baseband processing circuitry 414 may be on the same chip or set of chips, boards, or units.

[0111] The memory 404 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device -readable and / or computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 402. The memory 404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 402 and utilized by the network node 400. The memory 404 may be used to store any calculations made by the processing circuitry 402 and / or any data received via the communication interface 406. In some embodiments, the processing circuitry 402 and memory 404 is integrated.

[0112] The communication interface 406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 406 comprises port(s) / terminal(s) 416 tosend and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 400 may be capable of wireless communication and communication interface 406 may also include radio front-end circuitry that may be coupled to, or in certain embodiments a part of, an antenna 410. Particular embodiments of radio frontend circuitry include filter(s) 420 and amplifier(s) 422. The radio front-end circuitry may be connected to an antenna 410 and processing circuitry 402. The radio front-end circuitry may be configured to condition signals communicated between antenna 410 and processing circuitry 402. The radio front-end circuitry may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 420 and / or amplifiers 422. The radio signal(s) may then be transmitted via the antenna 410. Similarly, when receiving data, the antenna 410 may collect radio signals which are then converted into digital data by the radio front-end circuitry. The digital data may be passed to the processing circuitry 402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0113] In certain alternative embodiments, network node 400 may be capable of wireless communication but does not include separate radio front-end circuitry, instead, the processing circuitry 402 includes radio front-end circuitry and is connected to the antenna 410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 412 is part of the communication interface 406. In still other embodiments, the communication interface 406 includes one or more ports or terminals 416, the radio front-end circuitry, and the RF transceiver circuitry 412, as part of a radio unit (not shown), and the communication interface 406 communicates with the baseband processing circuitry 414, which is part of a digital unit (not shown).

[0114] The antenna 410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 410 may be coupled to the radio front-end circuitry and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 410 is separate from the network node 400 and connectable to the network node 400 through one or more interfaces or ports.

[0115] The antenna 410, communication interface 406, and / or the processing circuitry 402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 400. Any information, data and / or signals may be received from a UE, another network node and / or any other networkequipment. Similarly, the antenna 410, the communication interface 406, and / or the processing circuitry 402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0116] The power source 408 provides power to the various components of network node 400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 400 with power for performing the functionality described herein. For example, the network node 400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 408. As a further example, the power source 408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0117] Embodiments of the network node 400 may include additional components beyond those shown in Figure 10 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 400 may include user interface equipment to allow input of information into the network node 400 and to allow output of information from the network node 400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 400.

[0118] Figure 11 is a block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host.31Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0119] Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0120] Hardware 504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 508A and VM 508B (which may be collectively referred to as VMs 508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 508.

[0121] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0122] In the context of NFV, each of the VMs 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 508 on top of the hardware 504 and corresponds to an application 502.

[0123] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.

[0124] Figure 12 is a flowchart of an example process in a network node 110 according to some embodiments of the present disclosure. Network node 110 is configured to receive an indication of an UL URI corresponding to a LMF 111 (Block S100). Network node 110 is configured to establish a communication channel with the EMF 111 using the URI, the communication channel bypassing an AMF 113 (Block S102). Network node 110 is configured to transmit positioning information via the communication channel (Block SI 04).

[0125] In some embodiments, the network node 110 is further configured to transmit a DL URI, the DL URI being used for receiving positioning information from the LMF 111 via the communication channel.

[0126] In some embodiments, the indication is comprised in an NRPPa message.

[0127] In some embodiments, the indication is comprised in an NGAP message.

[0128] In some embodiments, the positioning information comprises at least one of: measurement information; training data; and location data associated with a user equipment.

[0129] Figure 13 is a flowchart of an example process in an LMF 111, e.g., of a core network node 108, according to some embodiments of the present disclosure. LMF 111 is configured to transmit an indication of an UL URI corresponding to the LMF 111 (Block S 106). LMF 111 is configured to establish a communication channel with a network node based on the URI, the communication channel bypassing an AMF 113 (Block S108). LMF 111 is configured to receive positioning information via the communication channel (Block SI 10).

[0130] In some embodiments, the LMF 111 is further configured to receive a DL URI, and transmitting positioning information via the communication channel based on the DL URI.

[0131] In some embodiments, the indication is comprised in an NRPPa message.

[0132] In some embodiments, the indication is comprised in an NGAP, message.

[0133] In some embodiments, the positioning information comprises at least one of: measurement information; training data; and location data associated with a user equipment.

[0134] EXAMPLE EMBODIMENTS

[0135] Group A Embodiments

[0136] Embodiment 1. A method performed by a wireless device for reporting positioning information to a network node, the method comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.

[0137] Group B Embodiments

[0138] Embodiment 4. A method performed by a network node for establishing a streaming communication channel for facilitating data transfers between NG-RAN and LMF 111 that bypass an AMF 113, the method comprising: receiving a message comprising an indication of a communication channel; and transmitting positioning information via the communication channel.

[0139] Embodiment 5. The method of any of the Group B embodiments, wherein the indication comprises a Uniform Resource Identifier (URI).

[0140] Embodiment 6. The method of any of the Group B embodiments, wherein the indication comprises at least one of: a downlink (DL) Uniform Resource Identifier (URI); and an uplink (UL) Uniform Resource Identifier (URI).

[0141] Embodiment 7. The method of any of the Group B embodiments, wherein transmitting the positioning information comprises transmitting the positioning information to a second network node.

[0142] Embodiment 8. The method of embodiment 7, wherein the second network node is a gNodeB.

[0143] Embodiment 9. The method of any of the embodiment 7, wherein the second network node is an LMF 111.

[0144] Embodiment 10. The method of any of the Group B embodiments, wherein the network node is a gNodeB.

[0145] Embodiment 11. The method of any of the Group B embodiments, wherein the network node is an LMF 111.

[0146] Embodiment 12. The method of any of the Group B embodiments, wherein the positioning information comprises at least one of: measurement information; training data; and location data associated with a user equipment.

[0147] Embodiment 13. The method of any of the Group B embodiments, wherein the message comprises an NR Positioning Protocol A (NRPPa) message.

[0148] Embodiment 14. The method of any of the Group B embodiments, wherein the message is received via an AMF 113.

[0149] Embodiment 15. The method of any of the Group B embodiments, wherein the message is received via an NG control plane interface.

[0150] Embodiment 16. The method of any of the Group B embodiments, wherein transmitting the positioning information via the communication channel comprises bypassing an AMF 113.

[0151] Embodiment 17. The method of any of the Group B embodiments, wherein transmitting the information via the communication channel comprises transmitting the positioning information directly to an LMF 111.

[0152] Embodiment 18. The method of any of the Group B embodiments, further comprising: in response to receiving the message, determining a setup failure associated with the communication channel; and based on receiving the message, transmitting an indication of the setup failure.

[0153] Embodiment 19. The method of embodiment 18, wherein the indication comprises a cause value associated with the setup failure.

[0154] Embodiment 20. The method of any of the Group B embodiments, further comprising: receiving a second message comprising an indication to deactivate reporting positioning information associated with a user equipment (UE).

[0155] Embodiment 21. The method of any of the Group B embodiments, wherein the message comprises a second indication of a direction associated with the streaming channel.

[0156] Embodiment 22. The method of any of the Group B embodiments, wherein the indication comprises a direction associated with the streaming channel.

[0157] Embodiment 23. The method of any of the Group B embodiments, wherein the direction associated with the streaming channel comprises at least one of a downlink direction and an uplink direction.

[0158] Embodiment 24. The method of any of the Group B embodiments, wherein the network node comprises a gNodeB Central Unit (gNB-CU).

[0159] Embodiment 25. The method of any of the Group B embodiments, wherein the network node comprises a gNodeB Distributed Unit (gNB-DU).

[0160] Embodiment 26. The method of any of the Group B embodiments, wherein the second network node comprises a gNodeB Central Unit (gNB-CU).

[0161] Embodiment 27. The method of any of the Group B embodiments, wherein the second network node comprises a gNodeB Distributed Unit (gNB-DU).

[0162] Embodiment 28. The method of any of the Group B embodiments, wherein the message comprises an NG Application Protocol (NGAP) message.

[0163] Embodiment 29. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

[0164] Group C Embodiments

[0165] Embodiment 30. A wireless device for reporting positioning information to a network node, comprising: processing circuitry configured to perform any of the operations of any of the Group A embodiments; and a power source configured to supply power to the processing circuitry.

[0166] Embodiment 31. A network node for establishing a streaming communication channel for facilitating data transfers between NG-RAN and LMF 111 that bypass an AMF 113, the network node comprising: processing circuitry configured to perform any of the operations of any of the Group B embodiments; a power source circuitry configured to supply power to the processing circuitry.

[0167] Embodiment 32. A wireless device for reporting positioning information to a network node, the wireless device comprising: one or more antennas; communication interface connected to the one or more antennas and to processing circuitry; the processing circuitry being configured to perform any of the operations of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a power source connected to the processing circuitry and configured to supply power to the UE.

[0168] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / orsoftware needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0169] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device -readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

Claims

Claims:

1. A method implemented in a network node (110), the method comprising: receiving (SI 00) an indication of an Uplink, UL, Uniform Resource Identifier, URI, corresponding to a Location Management Function, LMF (111);establishing (SI 02) a communication channel with the LMF (111) using the URI, the communication channel bypassing an Access and Mobility Management Function, AMF (113); andtransmitting (SI 04) positioning information via the communication channel.

2. The method of Claim 1, further comprising transmitting a Downlink, DL, URI, the DL URI being used for receiving positioning information from the LMF (111) via the communication channel.

3. The method of any of Claims 1-2, wherein the indication is comprised in a New Radio Positioning Protocol A, NRPPa, message.

4. The method of any of Claims 1-2, wherein the indication is comprised in a NG Application Protocol, NGAP, message.

5. The method of any of Claims 1-4, wherein the positioning information comprises at least one of: measurement information; training data; and location data associated with a user equipment.

6. A network node (110), the method comprising processing circuitry (402) configured to:receive an indication of an Uplink, UL, Uniform Resource Identifier, URI, corresponding to a Location Management Function, LMF (111);establish a communication channel with the LMF (111) using the URI, the communication channel bypassing an Access and Mobility Management Function, AMF (113); andtransmit positioning information via the communication channel.

7. The network node (110) of Claim 6, wherein the processing circuitry (402) is further configured to transmit a Downlink, DL, URI, the DL URI being used for receiving positioning information from the LMF (111) via the communication channel.

8. The network node (110) of any of Claims 6-7, wherein the indication is comprised in a New Radio Positioning Protocol A, NRPPa, message.

9. The network node (110) of any of Claims 6-7, wherein the indication is comprised in a NG Application Protocol, NGAP, message.

10. The network node (110) of any of Claims 6-9, wherein the positioning information comprises at least one of: measurement information; training data; and location data associated with a user equipment.

11. A method implemented in a Location Management Function, LMF, (111) the method comprising:transmitting (SI 06) an indication of an Uplink, UL, Uniform Resource Identifier, URI, corresponding to the LMF (111);establishing (S108) a communication channel with a network node based on the URI, the communication channel bypassing an Access and Mobility Management Function, AMF, (113); andreceiving (SI 10) positioning information via the communication channel.

12. The method of Claim 11, further comprising receiving a Downlink, DL, URI, and transmitting positioning information via the communication channel based on the DL URI.

13. The method of any of Claims 11-12, wherein the indication is comprised in a New Radio Positioning Protocol A, NRPPa, message.

14. The method of any of Claims 11-12, wherein the indication is comprised in a NG Application Protocol, NGAP, message.

15. The method of any of Claims 11-14, wherein the positioning informationcomprises at least one of: measurement information; training data; and location data associated with a user equipment.

16. A Location Management Function, LMF, (111) comprising processing circuitry (402) configured to:transmit an indication of an Uplink, UL, Uniform Resource Identifier, URI, corresponding to the LMF (111);establish a communication channel with a network node based on the URI, the communication channel bypassing an Access and Mobility Management Function, AMF (113); andreceive positioning information via the communication channel.

17. The LMF (111) of Claim 16, wherein the processing circuitry (402) is further configured to receive a Downlink, DL, URI, and transmitting positioning information via the communication channel based on the DL URI.

18. The LMF (111) of any of Claims 16-17, wherein the indication is comprised in a New Radio Positioning Protocol A, NRPPa, message.

19. The LMF (111) of any of Claims 16-17, wherein the indication is comprised in a NG Application Protocol, NGAP, message.

20. The LMF (111) of any of Claims 16-19, wherein the positioning information comprises at least one of: measurement information; training data; and location data associated with a user equipment.

Images