Methods for internet of things communication

Abstract

The present disclosure provides a method (800) in a Network Function, NF, for Internet of Things, IoT, communication. The method (800) includes: receiving (810), from an Access and Mobility Management Function, AMF, or a Next Generation Radio Access Network, NG-RAN, node, a first message containing a device Identifier, ID, of an Internet of Things, IoT, device and uplink data from the IoT device; and transmitting (820), to a Network Exposure Function, NEF, a second message containing the device ID, the uplink data, and an Application Function, AF, ID or AF address associated with the IoT device.

Description

[0001] METHODS FOR INTERNET OF THINGS COMMUNICATION

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to communication technology, and more particularly, to devices, network nodes, and methods therein for Internet of Things (loT) communication.

[0004] BACKGROUND

[0005] Wireless loT devices are often battery powered and both the need to change battery and the battery lifetime may be concerns for many potential applications such as asset tracking or environmental / industrial sensors. For this reason, the wireless communications industry has been interested in so-called Zero-Energy (ZE) devices. ZE devices refer to wireless loT devices that do not require battery replacement, and often harvest energy from the environment. In some use cases, such as monitoring the temperature of foodstuffs, the ZE devices may have small batteries that are disposable (e.g., organic, compostable batteries), rechargeable or have very limited capacity.

[0006] These ZE loT devices can in addition be of very small form factor and could even be printable. They have ultralow power consumption to enable operations based on either energy-harvesting from ambient sources or back- scattering communication (like Radio Frequency Identification (RFID)). That is, instead of being provided by a battery, the energy for communication may be harvested from an ambient source, such as vibration, solar power, RF, etc., (harvesting), or a charge carrier wave may be provided to the device, which is modulated and reflected back to a reader (back-scattering communication). This enables energy autonomous operations during the lifetime of the device without the need for either manual replacement or charging of the batteries. Compared with existing radio access technologies, this imposes new requirements on radio interfaces and protocols.

[0007] In the 3rdGeneration Partnership Project (3GPP) Radio Access Network (RAN) plenary (3GPP RAN #102), a “New SID: Study on solutions for Ambient loT (Internet of Things) in NR' was approved, see RP-234058, 3GPP TSG RAN Meeting #102, Edinburgh, UK, December 11-15, 2023, which is incorporated herein by reference in its entirety. This study targets a further assessment at RAN Work Group (WG)-level of Ambient loT, a new 3GPP loT technology, suitable for deployment in a 3GPP system, which relies on ultra-low complexity devices with ultra-low power consumption for the very-low end loT applications.

[0008] In 3GPP System Aspects (SA) plenary (3GPP SA#102), a “New SID: Study on Architecture support of Ambient power-enabled Internet of Things” was approved, see SP-231803, 3GPP SA#102, Edinburgh, UK, December 11 - 15, 2023, which is incorporated herein by reference in its entirety. This Study Item Description (SID) studies the architecture support of ambient power-enabled loT devices, based on the services requirements defined in 3GPP SA1.

[0009] The 3GPP Technical Specification (TS) 22.369, V19.0.0, which is incorporated herein by reference in its entirety, specifies functional service requirements and performance service requirements for ambient power-enabled loT.

[0010] SUMMARY

[0011] The Ambient loT devices are characterized as ultra-low complexity devices with ultra-low power consumption for very-low end loT applications. It has been agreed that in the RAN plenary, passive and semi-passive Ambient loT devices will be the focus. The Ambient loT devices cannot generate independent RF signals, which means it would predominantly utilize a Carrier Wave (CW) for uplink access, like RFID, rather than traditional 3GPP User Equipment (UE) solution.

[0012] According to the RAN SID, it is assumed that no Radio Resource Control (RRC) states, no mobility (i.e., at least no cell selection / re-selection-like function), no Hybrid Automatic Repeat reQuest (HARQ), and no Automatic Repeat reQuest (ARQ) is provided for Ambient loT devices. Thus, in the Core Network, quite many procedures are not applicable to Ambient loT devices as well. For example, without RRC states, Connection Management (CM) states may not be differentiated. Without cell selection / re-selection, concepts such as tracking area, registration area, and RAN notification area are no longer applicable to Ambient loT devices as well.

[0013] Ambient loT devices are expected to work as tags, while NG-RAN is expected to work as a reader. The current 3GPP solution is too heavy for Ambient loT devices. The Ambient loT devices (tags) may not be able to afford the complex logic handling for the complete Access Stratum (AS) and Non-Access Stratum (NAS) stack, from the perspective of e.g., processing capability, memory usage, power consumption, and / or cost.

[0014] It is an object of the present disclosure to provide devices, network nodes, and methods therein, capable of implementing a light-weighted solution for loT devices such as Ambient loT devices in a core network.

[0015] According to a first aspect of the present disclosure, a method in an loT device is provided. The method includes transmitting, to a Next Generation Radio Access Network (NG-RAN) node, a signaling message to be handled by a core network node. The signaling message is an AS message.

[0016] In an embodiment, the signaling message may be a registration request. In an embodiment, the registration request may be an initial registration request, or the registration request may be a mobility registration request and the NG-RAN node may be a target NG-RAN node.

[0017] In an embodiment, the method may further include receiving, from the NG-RAN node, a response to the signaling message. The response may be an AS message.

[0018] According to a second aspect of the present disclosure, a method in an NG-RAN node. The method includes receiving, from an loT device, a first signaling message to be handled by a core network node. The first signaling message is an AS message. The method further includes transmitting, to an Access and Mobility Management Function (AMF) or a Network Function (NF) for loT communication, a second signaling message based on the first signaling message.

[0019] In an embodiment, the first signaling message may be a registration request, and the second signaling message may be a request for registration on behalf of the loT device.

[0020] In an embodiment, the method may further include transmitting, to the loT device, a response to the first signaling message. The response is an AS message.

[0021] According to a third aspect of the present disclosure, a method in a target NG-RAN node is provided. The method includes receiving, from an loT device, a mobility registration request as an AS message. The method further includes fetching a device context of the loT device from a source NG-RAN node.

[0022] In an embodiment, the method may further include transmitting, to an AMF or an NF for loT communication, a message containing a device Identifier (ID) of the loT device.

[0023] According to a fourth aspect of the present disclosure, a method in an AMF is provided. The method includes receiving a request for registration for an loT device. The request contains a device ID of the loT device. The method further includes selecting an NF for loT communication based on the device ID. The method further includes transmitting, to the NF for loT communication, a registration request containing the device ID.

[0024] According to a fifth aspect of the present disclosure, a method in an NF for loT communication is provided. The method includes receiving, from an AMF or an NG-RAN node, a registration request containing a device ID of an loT device. The method further includes registering for the loT device towards a Unified Data Management (UDM) or Unified Data Repository (UDR). In an embodiment, the method may further include retrieving, from the UDM or UDR, subscription data of the loT device, the subscription data including an Application Function (AF) ID or AF address associated with the loT device.

[0025] According to a sixth aspect of the present disclosure, a method in an NF for loT communication is provided. The method includes receiving, from an AMF or an NG-RAN node, a first message containing a device ID of an loT device and uplink data from the loT device. The method further includes transmitting, to a Network Exposure Function (NEF), a second message containing the device ID, the uplink data, and an AF ID or AF address associated with the loT device.

[0026] According to a seventh aspect of the present disclosure, a method in an NF for loT communication is provided. The method includes receiving, from a NEF, a first message containing a device ID of an loT device and downlink data destined to the loT device. The method includes transmitting, to an AMF or an NG-RAN node, a second message containing the device ID and the downlink data.

[0027] In an embodiment, the first message may further contain an AF ID or AF address associated with the loT device. The method may further include: transmitting, to a UDM or UDR, a request to update subscription data of the loT device with the AF ID or AF address.

[0028] In an embodiment, the first message may further contain a transaction ID for uplink-downlink association. The method may further include receiving, from the AMF or the NG-RAN node, a third message containing the device ID, the transaction ID, and uplink data from the loT device as a response to the downlink data.

[0029] In an embodiment, the first message may further contain an additional AF ID or AF address for receiving the uplink data.

[0030] According to an eighth aspect of the present disclosure, a method in an AF is provided. The method includes transmitting a request to an NEF. The request requests for responses from loT devices in an area, and the request contains information on the area. Alternatively, the request requests for a response from an loT device in an area, and the request contains information on the area and a device ID of the loT device.

[0031] In an embodiment, the request may request for responses from loT devices belonging to a device group or device type in the area, and the request may further contain at least one of: an ID of the device group or information on the device type; a transaction ID for uplink-downlink association; and downlink data. In an embodiment, the downlink data may contain a command to be executed by each of the loT devices.

[0032] In an embodiment, the method may further include receiving a response from the NEF. The response may be based on the ID of the device group or information on the device type.

[0033] According to a ninth aspect of the present disclosure, a method in a first NF or an NG-RAN node is provided. The method includes receiving, from an AF or a second NF, a first request for responses from loT devices in an area. The first request contains information on the area. The method further includes transmitting, to each of one or more third NFs based on the information on the area, a second request for responses from the loT devices in the area. The second request contains the information on the area.

[0034] In an embodiment, the first request and the second request may each request for responses from loT devices belonging to a device group or device type in the area, and the first request and the second request may each further contain at least one of: an ID of the device group or information on the device type; a transaction ID for uplink-downlink association; and downlink data.

[0035] In an embodiment, the downlink data may contain a command to be executed by each of the loT devices.

[0036] In an embodiment, the method may further include receiving responses from the one or more third NFs, the responses each being based on the ID of the device group or information on the device type. The method may further include transmitting an aggregated response obtained by aggregating the responses to the AF or the second NF.

[0037] According to a tenth aspect of the present disclosure, a method in a first NF or an NG-RAN node is provided. The method includes receiving, from an AF or a second NF, a first request for a response from an loT device in an area. The first request contains information on the area and a device ID of the loT device. The method further includes transmitting, to each of one or more third NFs based on the information on the area, a second request for a response from the loT device in the area. The second request contains the information on the area and the device ID.

[0038] In an embodiment, the first request and the second request may each further contain a transaction ID for uplinkdownlink association and downlink data.

[0039] In an embodiment, the downlink data may contain a command to be executed by the loT device. In an embodiment, the method may further include receiving a response from one of the one or more third NFs and transmitting the response to the AF or the second NF.

[0040] According to an eleventh aspect of the present disclosure, a method in an loT device is provided. The method includes receiving, from an NG-RAN node, a first message including a transaction ID for uplink-downlink association and downlink data containing a command to be executed by the loT device. The method further includes transmitting, to the NG-RAN node, a second message including the transaction ID and a response generated by executing the command.

[0041] According to a twelfth aspect of the present disclosure, an loT device is provided. The loT device includes a communication interface, a processor, and a memory. The memory contains instructions executable by the processor whereby the loT device is operative to perform the method according to the above first or eleventh aspect.

[0042] According to a thirteenth aspect of the present disclosure, a computer-readable storage medium is provided. The computer-readable storage medium has computer-readable instructions stored thereon. The computer-readable instructions, when executed by a processor of an loT device, configure the loT device to perform the method according to the above first or eleventh aspect.

[0043] According to a fourteenth aspect of the present disclosure, a network node is provided. The network node includes a communication interface, a processor, and a memory. The memory contains instructions executable by the processor whereby the network node is operative to: when implementing an NG-RAN node, perform the method according to the second aspect, or when implementing a target NG-RAN node, perform the method according to the third aspect, or when implementing an AMF, perform the method according to the fourth aspect, or when implementing an NF for loT communication, perform the method according to the fifth, sixth, or seventh aspect, or when implementing an AF, perform the method according to the eighth aspect, or when implementing a first NF or an NG-RAN node, perform the method according to the ninth or tenth aspect.

[0044] According to a fifteenth aspect of the present disclosure, a computer-readable storage medium is provided. The computer-readable storage medium has computer-readable instructions stored thereon. The computer-readable instructions, when executed by a processor of a network node, configure the network node to: when implementing an NG-RAN node, perform the method according to the second aspect, or when implementing a target NG-RAN node, perform the method according to the third aspect, or when implementing an AMF, perform the method according to the fourth aspect, or when implementing an NF for loT communication, perform the method according to the fifth, sixth, or seventh aspect, or when implementing an AF, perform the method according to the eighth aspect, or when implementing a first NF or an NG-RAN node, perform the method according to the ninth or tenth aspect.

[0045] With the embodiments of the present disclosure, a new NF for loT communication is introduced for routing uplink / downlink messages from / to an loT device and interacting with other NFs for procedures related to the loT device. The embodiments of the present disclosure enable support of loT devices (e.g., Ambient loT devices, including passive and semi-passive Ambient loT devices) in the 5thGeneration System (5GS), considering the characteristics of loT devices such low-power, low-capacity, and low-complexity.

[0046] BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The above and other objects, features and advantages will be more apparent from the following description of embodiments with reference to the figures, in which:

[0048] Fig. 1 is a schematic diagram showing an architecture for loT communication according to an embodiment of the present disclosure;

[0049] Fig. 2 is a schematic diagram showing an architecture for loT communication according to another embodiment of the present disclosure;

[0050] Fig. 3 is a flowchart illustrating a method in an loT device according to an embodiment of the present disclosure;

[0051] Fig. 4 is a flowchart illustrating a method in an NG-RAN node according to an embodiment of the present disclosure;

[0052] Fig. 5 is a flowchart illustrating a method in a target NG-RAN node according to an embodiment of the present disclosure;

[0053] Fig. 6 is a flowchart illustrating a method in an AMF according to an embodiment of the present disclosure;

[0054] Fig. 7 is a flowchart illustrating a method in an NF for loT communication according to an embodiment of the present disclosure;

[0055] Fig. 8 is a flowchart illustrating a method in an NF for loT communication according to another embodiment of the present disclosure;

[0056] Fig. 9 is a flowchart illustrating a method in an NF for loT communication according to yet another embodiment of the present disclosure;

[0057] Fig. 10 is a flowchart illustrating a method in an AF according to an embodiment of the present disclosure;

[0058] Fig. 11 is a flowchart illustrating a method in a first NF or an NG-RAN node according to an embodiment of the present disclosure; Fig. 12 is a flowchart illustrating a method in a first NF or an NG-RAN node according to another embodiment of the present disclosure;

[0059] Fig. 13 is a flowchart illustrating a method in an loT device according to another embodiment of the present disclosure;

[0060] Fig. 14 is a sequence diagram showing an example of an initial registration procedure in Architecture- 1;

[0061] Fig. 15 is a sequence diagram showing an example of an initial registration procedure in Architecture- 2;

[0062] Fig. 16 is a sequence diagram showing an example of a mobility registration procedure in Architecture- 1;

[0063] Fig. 17 is a sequence diagram showing an example of a mobility registration procedure in Architecture- 2;

[0064] Fig. 18 is a sequence diagram showing an example of a DO-A procedure in Architecture-1;

[0065] Fig. 19 is a sequence diagram showing an example of a DO-A procedure in Architecture-2;

[0066] Fig. 20 is a sequence diagram showing an example of a DT procedure in Architecture-1;

[0067] Fig. 21 is a sequence diagram showing an example of a DT procedure in Architecture-2;

[0068] Fig. 22 is a sequence diagram showing an example of a DO-DTT procedure in Architecture-1;

[0069] Fig. 23 is a sequence diagram showing an example of a DO-DTT procedure in Architecture-2;

[0070] Fig. 24 is a sequence diagram showing a use case of asking reporting for all devices in a certain area in Architecture-1;

[0071] Fig. 25 is a sequence diagram showing a use case of asking reporting for all devices in a certain area in Architecture-2;

[0072] Fig. 26 is a sequence diagram showing a use case of asking reporting for a device in a certain area in Architecture-1;

[0073] Fig. 27 is a sequence diagram showing a use case of asking reporting for a device in a certain area in Architecture-2;

[0074] Fig. 28 is a block diagram of an loT device according to an embodiment of the present disclosure;

[0075] Fig. 29 is a block diagram of a network node according to an embodiment of the present disclosure;

[0076] Fig. 30 shows an example of a communication system in accordance with some embodiments of the present disclosure;

[0077] Fig. 31 shows an exemplary User Equipment (UE) in accordance with some embodiments of the present disclosure.

[0078] Fig. 32 shows an exemplary network node in accordance with some embodiments of the present disclosure. Fig. 33 is a block diagram of an exemplary host, which may be an embodiment of the host of Fig. 30, in accordance with various aspects described herein.

[0079] Fig. 34 is a block diagram illustrating an exemplary virtualization environment in which functions implemented by some embodiments may be virtualized.

[0080] Fig. 35 shows a communication diagram of an exemplary host communicating via an exemplary network node with an exemplary UE over a partially wireless connection in accordance with some embodiments of the present disclosure.

[0081] DETAILED DESCRIPTION

[0082] In the present disclosure, a network function, or NF (i.e., NF instance), can be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g. on a cloud infrastructure. The term "network node” refers to any physical or virtual node configured to implement a network function.

[0083] References in the specification to "one embodiment," "an embodiment," "an example embodiment," and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0084] It shall be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0085] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "comprising", "has", "having", "includes" and / or "including", when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0086] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

[0087] In the following, the embodiments of the present disclosure will be described taking Ambient loT devices as an example. It can be appreciated that the embodiments of the present disclosure are applicable to loT devices in general, and more particularly to loT devices with ultra-low complexity, ultra-low power consumption, and / or very- low end loT applications.

[0088] In the following description and claims, communication between an Ambient loT device and an NG-RAN may be direct communication or indirect communication via an intermediate node (e.g., UE, gateway, or relay node), depending on communication modes.

[0089] Figure 1

[0090] Fig. 1 is a schematic diagram showing an architecture (referred to as Architecture-1) for loT communication according to an embodiment of the present disclosure. As shown, in Architecture-1 a new NF for loT communication, referred to as Ambient loT Function (AIOTF), is introduced. The AIOTF is responsible for routing uplink (UL) and downlink (DL) messages between an NG-RAN node and an AF (optionally via an NEF), as well as interacting with a CHF for charging. Here, the AMF is responsible for termination of RAN Control Plane (CP) interface, registration management, access authentication / authorization, and transport of data for the Ambient loT device. The UDM / UDR may store subscription data of the Ambient loT device, including e.g., an AF ID or AF address associated with the Ambient loT device. The introduction of the AIOTF in Architecture-1 brings flexibility and modularity towards the 5GS for supporting of Ambient loT devices, e.g., the AIOTF allows limited impacts on the current 5GS NFs and allows scaling products differently compared to NFs handling UEs in the current 5GS.

[0091] Figure 2

[0092] Fig. 2 is a schematic diagram showing an architecture (referred to as Architecture-2) for loT communication according to another embodiment of the present disclosure. In Architecture-2, an AIOTF replaces the AMF. Accordingly, in addition to its functionalities in Architecture-1, the AIOTF also takes over some of the AMF's responsibilities, e.g., termination of RAN CP interface, registration management, and access authentication / authorization. The replacement of AMF in Architecture-2 brings further simplified solution towards the 5GS for supporting of Ambient loT devices.

[0093] In Architecture-2, the AOITF supports Ambient loT functionality, and the AOITF is selected by other Core Network (ON) NFs in the similar way as an AMF i.e., either via UDM (i.e. the AIOTF register itself to the UDM) or via Network Repository Function (NRF) (i.e. the AIOTF register its NF Profile towards the NRF. In Architecture-2, the AIOTF is selected by the NG-RAN in similar way as AMFs, with the following possible differences. o The AIOTF may indicate Served GUAMI List (as AMF does in NG SETUP RESPONSE, see chapter 9.2.6.2 in TS 38.413 and AMF CONFIGURATION UPDATE, see chapter 9.2.67 in TS 38.413), and / or indicate instead or in addition:

[0094] Served Ambient IOT devices (list of IDs) or range of Ambient IOT devices (list of ID ranges), served Ambient IOT device groups / types.

[0095] Support of Ambient loT or Ambient loT communication / services

[0096] In Architecture-2, in the similar way the NG-RAN can indicate to the AIOTF / AMF in NG SETUP, see chapter 9.2.6.2 in TS 38.413 and RAN CONFIGURATION UPDATE, see chapter 9.2.6.4 in TS 38.413: o NG-RAN support of Ambient loT (i.e. in such case the AIOTF would only select and send AIOTF related communication to NG-RAN nodes indicated this support) o Supported locations (list of identifiers related to locations e.g., Tracking Area Identity (TAI) I Tracking Area Code (TAO) or strings / values related to known location like geographical location, city, specific warehouse etc.).

[0097] Some procedures are provided in connection with the two architectures:

[0098] Initial registration (first time being read): The procedure indicates the device is first time being read by the network, or the device actively registers towards the network. In this case, mutual authentication needs to be performed between the device and the network. Logically, it is equivalent to the initial registration procedure. It can be triggered by Registration command from the device to the network, or some other messages that trigger the mutual authentication.

[0099] Mobility registration (being read by a new NG-RAN): The procedure indicates the device is being read by a new NG-RAN, or the device actively performs mobility registration. In this case, Core Network is updated about the NG-RAN for the device. Logically, it is equivalent to the mobility registration procedure for normal UE. It can be triggered by Mobility Registration command from the device to the network, or some other messages that trigger the update of the association of the serving NG-RAN.

[0100] DO-A (Device-originated autonomous): UL Data Transmission

[0101] DT (Device-terminated): DL Data Transmission

[0102] DO-DTT (Device-originated - device-terminated triggered): UL Data transmission triggered by DL Data or Carrier Wave.

[0103] For these procedures:

[0104] Initial registration (first time being read): • mutual authentication is simplified

[0105] • AIOTF is involved in the flow.

[0106] D In Architecture-1 , NG-RAN selects AMF which supports Ambient loT. AMF query NRF to select AIOTF based on e.g. device ID.

[0107] D In Architecture-2, NG-RAN selects AIOTF based on local configuration and / or information received from NG SETUP, and establishes connection via NGAR

[0108] D AIOTF get / subscribe device information from UDM / UDR based on device ID.

[0109] D AIOTF register towards UDM / UDR for the device ID, so that NEF can discover it in future.

[0110] • It further proposes an option to allow the Registration Request, Registration Accept, Registration Complete to be AS command, and let NG-RAN to utilize N2 message to communicate with AMF on behalf of device.

[0111] Mobility registration (being read by a new NG-RAN):

[0112] • AIOTF is involved in the flow:

[0113] D In Arch i tecuture- 1 , AMF update towards AIOTF when there is AMF re-allocation.

[0114] D In Architecture-2, NG-RAN update AIOTF when the serving NG-RAN is changed. If there is

[0115] AIOTF re-allocation, new AIOTF fetch the device context from the old AIOTF, and the new AIOTF updates UDM / UDR.

[0116] • It further proposes an option to allow the Registration Request, Registration Accept, Registration Complete to be AS command, and let NG-RAN to utilize N2 message to communicate with AMF on behalf of device. In this case, NG-RAN may respond Registration Accept to the device and notify AMF for the NG-RAN reallocation.

[0117] DO-A (Device-originated autonomous):

[0118] • AIOTF is involved in the flow.

[0119] D In Architecture-1 , AMF sends the UL Message to AIOTF. In Architecture-2, NG-RAN sends the UL Message to AIOTF.

[0120] D The AIOTF get the AF ID / address from UDM / UDR based on subscription data (which may be preconfigured). AIOTF provides the UL Message and AF ID / address to the NEF (for AFs outside trusted domain) or send to AF(for AFs in trusted domain).

[0121] • Implicit "Mobility Registration” may be triggered when the device is read by a new NG-RAN.

[0122] • AIOTF triggers Charging for UL Message towards CHF.

[0123] • It further proposes to let device put the data into a container. The container could be a NAS container to be consumed by AMF or AIOTF, or an application layer container to be consumed by the AF. DT (Device-terminated):

[0124] • AIOTF is involved in the flow.

[0125] D In both Architectures, NEF / AF discovers AIOTF from UDM. AIOTF receives data from NEF and deliver it to AM F.

[0126] • AIOTF triggers Charging for DL Message towards CHF.

[0127] • AF may provide AF I D / address, which could be different from the requesting AF. The device subscription data in UDM / UDR may be updated for the AF ID / address.

[0128] • It further proposes to let the data to be included in a container. If it is a NAS container, AMF or AIOTF is responsible for the container handling. For application layer container, AF is responsible for that.

[0129] DO-DTT (Device-originated - device-terminated triggered): It can be regarded as a combination of DT and DO.

[0130] • Transaction ID is proposed so that each handling NF (including NG-RAN) can associate the UL Message with the DL Message to avoid ambiguities concerning colliding transactions and to ensure that aggregation does not span across multiple requests. AIOTF provides the transaction ID to CHF, so that CHF may be able to perform appropriate charging accordingly.

[0131] • The AF ID / address provided by AF can be used to receive the UL message from the device.

[0132] For the DO-DTT procedure, two use cases are provided:

[0133] Ask reporting for all devices in a certain area

[0134] Ask reporting for a device in a certain area (e.g., find lost wallet).

[0135] For these use cases:

[0136] Ask reporting for all devices in a certain area:

[0137] • AF provides transaction ID, device group ID, device type, geographical area information, DL data, AF ID / address, aggregation period, report after aggregation period in the request;

[0138] • NEF translates external geographical area information to internal geographical area information.

[0139] • NEF (for AFs outside trusted domain) and AF (for AF inside trusted domain) discover serving AIOTFs based on geographical area (device group ID and device type may be considered as well). NEF / AF duplicate / fork the request and forward the request to one or more AIOTFs.

[0140] • In Architecture-1 , based on area information, AIOTFs query NRF for the AMFs in the area that supports Ambient loT. They duplicate / fork the request and send it to one or more AMFs, and AMFs sends it to one or more NG-RANs.

[0141] • In Architecture-2, based on area information, the AIOTFs duplicate / fork the request and send it to one or more NG-RANs. • NG-RANs, AMFs, AIOTFs, NEF may aggregate the reports from Ambient loT devices within the aggregation period, and send to AF via response or notification. The reports received later than the aggregation period will be notified to AF separately, if AF request is to subscribe for further reports.

[0142] • The aggregation (handling the reports within the aggregation period) and the notification (handling the reports later than the aggregation period) may include filtering out information of the reports to include only requested and authorized information.

[0143] • It can be utilized to let AF to provide command to NG-RANs in a specific geographical area. In this case, NG-RANs process the command in DL data and generate response, instead of devices.

[0144] Asking reporting for a device in a certain area (e.g., find lost wallet):

[0145] • AF provides transaction ID, device ID, geographical area information, , DL data, AF I D / address, response period in the request;

[0146] • NEF translates external geographical area information to internal geographical area information.

[0147] • NEF (for AFs outside trusted domain) and AF (for AF inside trusted domain) discover AIOTF via UDM based on device ID. NEF / AF may discover AIOTFs via NRF, if no serving AIOTF in UDM.

[0148] • NEF / AF may try AIOTF from UDM firstly. If no response, NEF / AF try AIOTFs from NRF.

[0149] • In Architecture-1 , based on area information, AIOTF query NRF to get AMFs within the area and duplicate / forks the requests to those AMFs. AMFs duplicate / forks the requests to NG-RANs. If there is a response from Ambient loT device to AIOTF via NG-RAN and AMF, AIOTF sends a success response or notification to AF. Otherwise, after response period, AIOTF may send a failure response or notification to AF.

[0150] • In Architecture-2, based on area information, AIOTFs duplicate / forks the requests to NG-RANs. If there is a response from Ambient loT device to NEF via NG-RAN, AIOTF, NEF sends a success response or notification to AF. Otherwise, after response period, NEF may send a failure response or notification to AF.

[0151] Further details of these procedures and use cases will be described later.

[0152] Figure 3

[0153] Fig. 3 is a flowchart illustrating a method 300 according to an embodiment of the present disclosure. The method 300 can be performed by an loT device, e.g., an Ambient loT device.

[0154] At block 310, the loT device transmits, to an NG-RAN node, a signaling message to be handled by a core network node. The signaling message is an AS message. For example, the signaling message may be a registration request. The registration request may be an initial registration request, or the registration request may be a mobility registration request and the NG-RAN node may be a target NG-RAN node.

[0155] In an example, the loT device may further receive, from the NG-RAN node, a response to the signaling message. The response may be an AS message.

[0156] Figure 4

[0157] Fig. 4 is a flowchart illustrating a method 400 according to an embodiment of the present disclosure. The method 400 can be performed by an NG-RAN node.

[0158] At block 410, the NG-RAN node receives, from an loT device, a first signaling message to be handled by a core network node. The first signaling message is an AS message.

[0159] At block 420, the NG-RAN node transmits, to an AMF or an NF for loT communication (e.g., AIOTF), a second signaling message based on the first signaling message.

[0160] In an example, the first signaling message may be a registration request, and the second signaling message may be a request for registration on behalf of the loT device.

[0161] In an example, the NG-RAN node may further transmit, to the loT device, a response to the first signaling message. The response may be an AS message.

[0162] Figure 5

[0163] Fig. 5 is a flowchart illustrating a method 500 according to an embodiment of the present disclosure. The method 500 can be performed by a target NG-RAN node, e.g., in a mobility scenario.

[0164] At block 510, the target NG-RAN node receives, from an loT device, a mobility registration request as an AS message.

[0165] At block 520, the target NG-RAN node fetches a device context of the loT device from a source NG-RAN node.

[0166] In an example, the target NG-RAN node may transmit, to an AMF or an NF for loT communication (e.g., AIOTF), a message containing a device ID of the loT device. Fig. 6 is a flowchart illustrating a method 600 according to an embodiment of the present disclosure. The method 600 can be performed by an AMR

[0167] At block 610, the AMF receives a request for registration for an loT device. The request contains a device ID of the loT device.

[0168] At block 620, the AMF selects an NF for loT communication (e.g., AIOTF) based on the device ID.

[0169] The selection may be based on an additional criterion, such as based on the request being for Ambient loT. For example, the request may include a device type indicating that the request is from an Ambient loT device, or the device ID may indicate a device type of Ambient loT.

[0170] At block 630, the AMF transmits, to the NF for loT communication, a registration request containing the device ID.

[0171] Figure 7

[0172] Fig. 7 is a flowchart illustrating a method 700 according to an embodiment of the present disclosure. The method 700 can be performed by an NF for loT communication (e.g., AIOTF).

[0173] At block 710, the NF for loT communication receives, from an AMF or an NG-RAN node, a registration request containing a device ID of an loT device.

[0174] At block 720, the NF for loT communication registers for the loT device towards a UDM or UDR.

[0175] In an example, the NF for loT communication may retrieve, from the UDM or UDR, subscription data of the loT device. The subscription data may include an AF ID or AF address associated with the loT device.

[0176] Figure 8

[0177] Fig. 8 is a flowchart illustrating a method 800 according to an embodiment of the present disclosure. The method 800 can be performed by an NF for loT communication (e.g., AIOTF).

[0178] At block 810, the NF for loT communication receives, from an AMF or an NG-RAN node, a first message containing a device ID of an loT device and uplink data from the loT device.

[0179] At block 820, the NF for loT communication transmits, to a NEF, a second message containing the device ID, the uplink data, and an AF ID or AF address associated with the loT device. Figure 9

[0180] Fig. 9 is a flowchart illustrating a method 900 according to an embodiment of the present disclosure. The method 900 can be performed by an NF for loT communication (e.g., AIOTF).

[0181] At block 910, the NF for loT communication receives, from a NEF, a first message containing a device ID of an loT device and downlink data destined to the loT device.

[0182] At block 920, the NF for loT communication transmits, to an AMF or an NG-RAN node, a second message containing the device ID and the downlink data.

[0183] In an example, the first message may further contain an AF ID or AF address associated with the loT device. The NF for loT communication may transmit, to a UDM or UDR, a request to update subscription data of the loT device with the AF ID or AF address.

[0184] In an example, the first message may further contain a transaction ID for uplink-downlink association. The NF for loT communication may receive, from the AMF or the NG-RAN node, a third message containing the device ID, the transaction ID, and uplink data from the loT device as a response to the downlink data.

[0185] In an example, the first message may further contain an additional AF ID or AF address for receiving the uplink data.

[0186] Figure 10

[0187] Fig. 10 is a flowchart illustrating a method 1000 according to an embodiment of the present disclosure. The method 1000 can be performed by an AF.

[0188] At block 1010, the AF transmits a request to a NEF. Here, the request requests for responses from loT devices in an area, and the request contains information on the area. Alternatively, the request requests for a response from an loT device in an area, and the request contains information on the area and a device ID of the loT device.

[0189] In an example, the request may request for responses from loT devices belonging to a device group or device type in the area, and the request may further contain at least one of: an ID of the device group or information on the device type; a transaction ID for uplink-downlink association; and downlink data. Here, the downlink data may contain a command to be executed by each of the loT devices. In an example, the AF may receive a response from the NEF. The response may be based on the ID of the device group or information on the device type.

[0190] Figure 11

[0191] Fig. 11 is a flowchart illustrating a method 1100 according to an embodiment of the present disclosure. The method 1100 can be performed by a first NF or an NG-RAN node. The first NF may be e.g., NEF, NF for loT communication, or AMR

[0192] At block 1110, the first NF or NG-RAN node receives, from an AF, or a second NF, a first request for responses from loT devices in an area. The first request contains information on the area.

[0193] At block 1120, the first NF or NG-RAN node transmits, to each of one or more third NFs based on the information on the area, a second request for responses from the loT devices in the area. The second request contains the information on the area.

[0194] In an example, the first request and the second request may each request for responses from loT devices belonging to a device group or device type in the area, and the first request and the second request may each further contain at least one of: an ID of the device group or information on the device type; a transaction ID for uplink-downlink association; and downlink data. Here, the downlink data may contain a command to be executed by each of the loT devices.

[0195] In an example, the first NF or NG-RAN node may further receive responses from the one or more third NFs. The responses may each be based on the ID of the device group or information on the device type. The first NF or NG-RAN node may transmit an aggregated response obtained by aggregating the responses to the AF or the second NF.

[0196] Here, the operation of aggregating may be performed within an aggregation period, and after the aggregation period, responses from the loT devices may be transmitted individually. In either case, information in the responses may be filtered to include only requested and authorized information, including e.g., filtering out responses from unintended devices and unauthorized information (e.g., device ID) the AF is not authorized to receive.

[0197] Figure 12

[0198] Fig. 12 is a flowchart illustrating a method 1200 according to an embodiment of the present disclosure. The method 1200 can be performed by a first NF or an NG-RAN node. The first NF may be e.g., NEF, NF for loT communication, or AMR At block 1210, the first NF or NG-RAN node receives, from an AF or a second NF, a first request for a response from an loT device in an area. The first request contains information on the area and a device ID of the loT device.

[0199] At block 1220, the first NF or NG-RAN node transmits, to each of one or more third NFs based on the information on the area, a second request for a response from the loT device in the area. The second request contains the information on the area and the device ID.

[0200] In an example, the first request and the second request may each further contain a transaction ID for uplinkdownlink association and downlink data. Here, the downlink data may contain a command to be executed by the loT device.

[0201] In an example, the first NF or NG-RAN node may further receive a response from one of the one or more third NFs, and transmit the response to the AF or the second NF. Once the response is received, the first NF or NG- RAN node may stop transmitting the second request.

[0202] Figure 13

[0203] Fig. 13 is a flowchart illustrating a method 1300 according to an embodiment of the present disclosure. The method 1300 can be performed by an loT device, e.g., an Ambient loT device.

[0204] At block 1310, the loT device receives, from a Next Generation Radio Access Network, NG-RAN, node, a first message including a transaction ID for uplink-downlink association and downlink data containing a command to be executed by the loT device.

[0205] At block 1320, the loT device transmits, to the NG-RAN node, a second message including the transaction ID and a response generated by executing the command.

[0206] In the following, the above methods 300-1300 will be further explained with Figs. 14-27.

[0207] Figure 14

[0208] Fig. 14 shows an initial registration procedure in 1. The initial registration is needed, as Ambient loT devices and Network need to perform mutual authentication and come into "secured” mode as RFID tag / reader. As shown, the procedure includes the following steps: 1 . Ambient loT device performs Registration towards the Network with device ID and data containing the device secret information.

[0209] 2. NG-RAN selects an AMF supporting Ambient loT communication (NG-RAN is either configured by Operations, Administration, and Maintenance (OAM) which AMFs to use, e.g., default AMF for Ambient loT, or the AMF indicates its support during the NG SETUP or Configuration Update procedures).

[0210] 3. NG-RAN sends N2 message (e.g. Initial UE Message) to AMF. Besides the information from the device, NG-RAN may further include its own information, e.g., optional RAN ID, optional position information (User Location Info (ULI)), etc.

[0211] The "Registration” may be a NAS message from Ambient loT device to AMF in step 1 to step 3. It is also possible to be an AS command from Ambient loT device to NG-RAN in step 1, and NG-RAN sends a new N2 message to request authentication / authorization for the device. The Ambient loT device may send the message unsolicited or based upon request by the NG-RAN. For example, Ambient loT device sends "Registration Request” AS command to NG-RAN. NG-RAN handles the request and sends a new NG-AP message (e.g., "Device Registration Request” or "Device Authentication Request”) to AMF to perform the registration on behalf of the device.

[0212] 4. AMF, Authentication Server Function (AUSF), UDM / UDR performs authentication and authorization for the Ambient loT device. The AUSF, UDM / UDR may be external credential server.

[0213] 5. AMF performs Get / Subscribe operations for the device towards UDM (Subscriber Data Management (SDM)).

[0214] 6. AMF queries NRF to select AIOTF based on device ID and information from UDM / UDR, e.g., special subscribed Single Network Slice Selection Assistance Information (S-NSSAI). Some additional criteria for selection could be based on the N2 message, e.g., a device type in the message indicating the request is from an Ambient loT device or a device type in the device ID indicating that the device ID an Ambient loT device.

[0215] 7. AMF sends Registration Request towards AIOTF with the device ID and received NG-RAN information.

[0216] 8. AIOTF performs Get / Subscribe operations for the device towards UDM (SDM). From UDM, AIOTF may get the device group ID, AF ID or AF address of the device, which are preconfigured as subscription data of the device. 9. AIOTF performs Registration for the device towards UDM (UE Context Management (UECM)).

[0217] 10. AIOTF sends Registration Response to AMF.

[0218] 11 . AMF allocates a Core Network device ID so that the device can use the Core Network device ID afterwards to locate the AMF, as well as the UE context stored in AMF. AMF sends N2 message (e.g., Initial Context Setup Request) to NG-RAN with the authentication / authorization result, device context, and security context, Core Network device ID.

[0219] 12. NG-RAN allocates a RAN device ID. NG-RAN sends Registration Accept to UE, containing, e.g., authentication / authorization result, security context, RAN device ID, Core Network device ID.

[0220] In steps 11-12, the "Registration Accept” may be a NAS message for success authentication / authorization ("Registration Reject” for failure). It is also possible that AMF sends the information to NG-RAN, and NG-RAN sends an AS command to Ambient loT device with the needed information, i.e., without UE receiving a NAS message as in TS 24.501 . For example, AMF sends a new NG-AP message (e.g., "Device Registration Accept” or "Device Authentication Result”) to NG-RAN with the information to both NG-RAN and Ambient loT device. NG- RAN handles the message and sends "Registration Accept” AS command with the information to the device.

[0221] 13. The device authenticates the network.

[0222] 14. The device sends "Registration Complete” towards Network or acknowledges that the device has received the information and accepted the network and is in secured mode.

[0223] 15. The NG-RAN sends N2 message (e.g. Initial Context Setup Response) with the "Registration Complete” or acknowledgement to AMF.

[0224] Step 15 can take place prior to step 14, so that "Registration Complete” will be sent via a separate N2 message to AMF.

[0225] The "Registration Complete” may be a NAS message. It is also possible that Ambient loT device sends an AS command to NG-RAN, and NG-RAN indicates the final step of registration towards AMF via a new N2 message.

[0226] After the procedure, the Ambient loT device is in "Secured” mode to communicate with the Network. Figure 15

[0227] Fig. 15 shows an initial registration procedure in Architecture-2. The initial registration is needed, as Ambient loT devices and Network need to perform mutual authentication and come into "secured” mode as RFID tag / reader. As shown, the procedure includes the following steps:

[0228] 1 . Ambient loT device performs Registration towards the Network with device ID and data containing the device secret information.

[0229] 2. NG-RAN selects an AIOTF.

[0230] 3. NG-RAN sends N2 message (e.g. Initial UE Message) to AIOTF. Besides the information from the device, NG-RAN may further include its own information, e.g., optional RAN ID, optional position information (ULI), etc.

[0231] The "Registration” may be a NAS message from Ambient loT device to AIOTF in step 1 to step 3. It is also possible to be an AS command from Ambient loT device to NG-RAN in step 1, and NG-RAN sends a new N2 message to request authentication / authorization for the device. The Ambient loT device may send the message unsolicited or based upon request by the NG-RAN. For example, Ambient loT device sends "Registration Request” AS command to NG-RAN. NG-RAN handles the request and sends a new NG-AP message (e.g., "Device Registration Request” or "Device Authentication Request”) to AMF to perform the registration on behalf of the device.

[0232] 4. AIOTF, AUSF, UDM / UDR performs authentication and authorization for the Ambient loT device. The AUSF, UDM / UDR may be external credential server.

[0233] 5. AIOTF performs Get / Subscribe operations for the device towards UDM (SDM). From UDM, AIOTF may get the device group ID, AF ID or AF address of the device, which are preconfigured as subscription data of the device.

[0234] 6. AIOTF performs Registration for the device towards UDM (UECM).

[0235] 7. AIOTF may allocate a Core Network device ID so that the device can use the Core Network device ID afterwards to locate the AMF, as well as the UE context stored in AMR AIOTF sends N2 message (e.g. Initial Context Setup Request) to NG-RAN with the authentication / authorization result, device context, and security context, Core Network device ID. 8. NG-RAN allocates a RAN device ID, NG-RAN sends Registration result to UE, containing authentication / authorization result, security context, RAN device ID, Core Network device ID.

[0236] In steps 7-8, the "Registration Accept” may be a NAS message for success authentication / authorization ("Registration Reject” for failure). It is also possible that AIOTF sends the information to NG-RAN, and NG-RAN sends an AS command to Ambient loT device with the needed information, i.e., without UE receiving a NAS message as in TS 24.501 . For example, AMF sends a new NG-AP message (e.g., "Device Registration Accept” or "Device Authentication Result”) to NG-RAN with the information to both NG-RAN and Ambient loT device. NG- RAN handles the message and sends "Registration Accept” AS command with the information to the device.

[0237] 9. The device authenticates the network.

[0238] 10. The device sends "Registration Complete” towards Network or acknowledges that the device has received the information and accepted the network and is in secured mode.

[0239] 11 . The NG-RAN sends N2 message (e.g. Initial Context Setup Response) with the "Registration Complete” or acknowledgement to AIOTF.

[0240] Step 11 can take place prior to step 10, so that "Registration Complete” will be send via a separate N2 message to AMF.

[0241] The "Registration Complete” may be a NAS message. It is also possible that Ambient loT device sends an AS command to NG-RAN, and NG-RAN indicates the final step of registration towards AIOTF via a new N2 message.

[0242] After the procedure, the Ambient loT device is in "Secured” mode to communicate with Network.

[0243] Figure 16

[0244] Fig. 16 shows a mobility registration procedure in Architecture-1. When Ambient loT device is read by a new reader, the device may notify the network, so that the network can deliver the DL data to the device successfully, or NG-RAN may trigger the device to perform such updates towards the network. Otherwise, the last served NG- RAN may be contacted for DL data transmission. It can be regarded as mobility registration procedure from a network perspective. As shown, the procedure includes the following steps: 1 . Ambient loT device performs Mobility Registration towards Network with device ID. The device ID may be a CN allocated ID (e.g. similar as Globally Unique Temporary UE Identity (GUTI) so that the serving NF with the device context can be identified).

[0245] 2. The new (target) NG-RAN validates the device ID.

[0246] If mobility registration is AS command, and the new NG-RAN can fetch device context from old (source) NG-RAN, steps 3 -5 are executed:

[0247] 3. The new NG-RAN fetches device context from old NG-RAN (the old NG-RAN node is selected based on an ID previously provided by the old NG-RAN node, e.g. device ID, Radio Network Temporary Identifier (RNTI) or similar).

[0248] 4. The new NG-RAN selects the AMF e.g. based on device context, or if not reachable based on device ID (the device ID previously received from the AMF), and sends N2 message (e.g., "Path Switch Request” or "Serving RAN Update”) to AMF. Besides the information from the device, the new NG-RAN may further include its own information, e.g. optional RAN ID, optional position information (ULI), etc. The AMF responds.

[0249] 5. The new NG-RAN respond to the device for the mobility registration.

[0250] Otherwise (i.e. , if mobility registration is NAS message, or the new NG-RAN cannot fetch device context from old NG-RAN if mobility registration is AS message), the following steps are executed:

[0251] 6. The new NG-RAN selects the AMF e.g. based on device ID (the device previously received from the AMF) and sends N2 message (e.g. Initial UE Message) to AMF. Besides the information from the device, the new NG-RAN may further include its own information, e.g. optional RAN ID, optional position information, etc.

[0252] 7. If there is AMF re-allocation, the new AMF fetches the device contexts from the old AMF.

[0253] 8. If there is AMF re-allocation, the new AMF needs to update AIOTF for the serving AMF update.

[0254] 9. AMF may allocate a new Core Network device ID to obsolete the old one for the device to use in future. AMF sends N2 message (e.g. Initial Context Setup Request) to the new NG-RAN with the mobility registration result, device context, and optional security context (if AS security applies), optional new Core Network device ID. 10. NG-RAN sends Registration Accept to UE. If the mobility registration is a NAS message, NG-RAN forwards the NAS "Registration Accept” sent by AMF to the device. If it is a AS message, NG-RAN sends the AS "Registration Accept” to the device.

[0255] 11 . The device sends Registration Complete towards Network or acknowledges that the device has received the information and accepted the network and is in secured mode.

[0256] 12. The NG-RAN sends N2 message (e.g. Initial Context Setup Response) with the "Registration Complete” or acknowledgement to AMF.

[0257] 13. The AMF interacts with the old NG-RAN to release the device context.

[0258] Step 12 can take place prior to step 11, so that "Registration Complete” will be sent via a separate N2 message to AMF.

[0259] The "Registration Complete” may be a NAS message. It is also possible that Ambient loT device sends a AS command to NG-RAN, and NG-RAN indicates the final step of registration towards AMF via a new N2 message.

[0260] It is also possible that device does not send "Registration Complete”, but NG-RAN acknowledges AMF via an N2 message.

[0261] Figure 17

[0262] Fig. 17 shows a mobility registration procedure in Architecture-2. When Ambient loT device is read by a new reader, the device may notify the network, so that the network can deliver the DL data to the device successfully, or NG-RAN may trigger the device to perform such updates towards the network. Otherwise, the last served NG- RAN may be contacted for DL data transmission. It can be regarded as mobility registration procedure from network perspective. As shown, the procedure includes the following steps:

[0263] 1 . Ambient loT device perform Mobility Registration towards Network with device ID. The device ID may be a CN allocated ID (e.g. similar as GUTI so that the serving NF with the device context can be identified).

[0264] 2. The new (target) NG-RAN validates the device ID.

[0265] If mobility registration is AS command, and the new NG-RAN can fetch device context from old (source) NG-RAN, step 3 -5 are executed: 3. The new NG-RAN fetches device context from old NG-RAN (the old NG-RAN node is selected based on an ID previously provided by the old NG-RAN node, e.g. device ID, RNTI or similar).

[0266] 4. The new NG-RAN selects the AIOTF e.g. based on device context, or if not reachable based on device ID (the device ID previously received from the AIOTF), and sends N2 message (e.g. "Path Switch Request” or "Serving RAN Update”) to AIOTF. Besides the information from the device, the new NG-RAN may further include its own information, e.g. optional RAN ID, optional position information (ULI), etc. The AIOTF responds.

[0267] 5. The new NG-RAN respond to the device for the mobility registration.

[0268] Otherwise (i.e. if mobility registration is NAS message, or the new NG-RAN cannot fetch device context from old NG-RAN if mobility registration is AS message), the following steps are executed:

[0269] 6. The new NG-RAN selects the AIOTF e.g. based on device ID (the device previously received from the AIOTF) and sends N2 message (e.g. Initial UE Message) to AIOTF. Besides the information from the device, the new NG-RAN may further include its own information, e.g. optional RAN ID, optional position information, etc.

[0270] 7. If there is AIOTF re-allocation, the new AIOTF fetches the device contexts from the old AIOTF.

[0271] 8. If there is AIOTF re-allocation, the new AIOTF needs to update UDM for the serving AIOTF update.

[0272] 9. AIOTF may allocate a new Core Network device ID to obsolete the old one for the device to use in future. AIOTF sends N2 message (e.g. Initial Context Setup Request) to the new NG-RAN with the mobility registration result, device context, and optional security context (if AS security applies), optional new Core Network device ID.

[0273] 10. NG-RAN sends Registration Accept to UE. If the mobility registration is a NAS message, NG-RAN forwards the NAS "Registration Accept” sent by AIOTF to the device. If it is an AS message, NG-RAN sends the AS "Registration Accept” to the device.

[0274] 11 . The device sends Registration Complete towards Network or acknowledges that the device has received the information and accepted the network and is in secured mode. 12. The NG-RAN sends N2 message (e.g. Initial Context Setup Response) with the "Registration Complete” or acknowledgement to AIOTF.

[0275] 13. The AIOTF interacts with the old NG-RAN to release the device context.

[0276] Figure 18

[0277] Fig. 18 shows a DO-A procedure in Architecture-1. As shown, the procedure includes the following steps:

[0278] 1 . Ambient loT device includes device ID and device data towards Network when being read by NG-RAN, or originated from the device actively. The device ID may be a CN allocated ID (e.g. similar as GUTI so that the serving NF with the device context can be identified). The device can include the data into a container to be consumed by the AF. The container may be a NAS container, so that NG-RAN will not read the data in the container. The container could also be an application layer container to be consumed by AF, so that NG-RAN and Core Network NFs should not read the data inside the container.

[0279] 2. The NG-RAN validates device ID and data if NG-RAN has device context. Otherwise, it needs to fetch device context from old NG-RAN or AMF as described in "Mobility Registration”. It can be regarded as an implicit "Mobility Registration” within the network.

[0280] 3. NG-RAN sends N2 message (e.g. UL NAS Transport) to AMF. Besides the information from the device, NG-RAN may further include its own information, e.g., optional RAN ID, optional position information, etc.

[0281] 4. The AMF updates NG-RAN association if needed, e.g., when the Ambient loT device is read by another reader.

[0282] 5. The AMF selects AIOTF and forwards the message to AIOTF with the information received from the device and NG-RAN.

[0283] 6. The AIOTF stores the information, and forwards the message to NEF, and further includes the AF ID or AF address to the NEF, which was fetched from UDM.

[0284] 7. The AIOTF sends charging request towards CHF to charge for the UL message.

[0285] 8. The NEF notifies the AF about the UL data, based on AF ID or AF address received. For step 6, if AF is deployed in trusted domain, AIOTF may notify the AF directly, so that NEF is not mandated. It requires AF register towards AIOTF prior to the notification. Also, the AF may need to subscribe to being notified of the information.

[0286] Figure 19

[0287] Fig. 19 shows a DO-A procedure in Architecture-2. As shown, the procedure includes the following steps:

[0288] 1 . Ambient loT device includes device ID and device data towards Network when being read by NG-RAN, or originated from the device actively. The device ID may be a ON allocated ID (e.g. similar as GUTI so that the serving NF with the device context can be identified). The device can include the data into a container to be consumed by the AF. The container may be a NAS container, so that NG-RAN will not read the data in the container. The container could also be an application layer container to be consumed by AF, so that NG-RAN and Core Network NFs should not read the data inside the container.

[0289] 2. The NG-RAN validate device ID and data if NG-RAN has device context. Otherwise, it needs to fetch device context from old NG-RAN or AIOTF as described in "Mobility Registration”. It can be regarded as an implicit "Mobility Registration” within the network.

[0290] 3. NG-RAN sends N2 message (e.g. UL NAS Transport) to AIOTF. Besides the information from the device, NG-RAN may further include its own information, e.g., optional RAN ID, optional position information, etc.

[0291] 4. The AMF updates NG-RAN association if needed, e.g., when the Ambient loT device is read by another reader.

[0292] 5. If there is AIOTF re-allocation, new AIOTF fetches device context from old AIOTF.

[0293] 6. If there is AIOTF re-allocation, new AIOTF register towards UDM (UECM) for the serving NF change.

[0294] 7. The AIOTF stores the information, and forwards the message to NEF, and further includes the AF ID or AF address to the NEF, which was fetched from UDM.

[0295] 8. The AIOTF sends charging request towards CHF to charge for the UL message.

[0296] 9. The NEF notifies the AF about the UL data, based on AF ID or AF address received. For step 7, if AF is deployed in trusted domain, AF may notify the AF directly, so that NEF is not mandated. It requires AF register towards AIOTF prior to the notification. Also, the AF may need to subscribe to being notified of the information.

[0297] Figure 20

[0298] Fig. 20 shows a DT procedure in Architecture-1 . As shown, the procedure includes the following steps:

[0299] 1 . AF sends DL Message to the NEF, including the device ID and the DL data, which may contain the command to be executed in the Ambient loT device. AF may provide AF ID or AF address.

[0300] 2. The NEF discovers the serving AIOTF from UDM based on device ID (the serving AIOTF has registered towards the UDM).

[0301] 3. After discovery, the NEF forwards the DL Message to the AIOTF.

[0302] 4. The AIOTF may update the device subscription data for AF ID or AF address.

[0303] 5. The AIOTF selects AMF and forwards the DL Message to the AMF.

[0304] 6. The AIOTF sends Charging Request to the CHF for the charging of the DL Message.

[0305] 7. The AMF sends N2 message (e.g. DL NAS Transport) to the NG-RAN together with the DL Message.

[0306] 8. The NG-RAN delivers the DL Message to the Ambient loT device.

[0307] In step 1, for AF in trusted domain, it may query UDM for AIOTF discovery and sends DL Message to AIOTF directly, without mandating NEF.

[0308] For the data delivered from AF to device, it may be included in a container. The container could be a NAS container or an application layer container. If it is a NAS container, AMF or AIOTF includes the data in the container. If it is an application layer container, AF includes the data in the container.

[0309] Figure 21

[0310] Fig. 21 shows a DT procedure in Architecture-2. As shown, the procedure includes the following steps: 1 . AF sends DL Message to the NEF, including the device ID and the DL data, which may contain the command to be executed in the Ambient loT device, optional AF ID or AF address.

[0311] 2. The NEF discovers the serving AIOTF from UDM based on device ID (the serving AIOTF has registered towards the UDM).

[0312] 3. After discovery, the NEF forwards the DL Message to the AIOTF.

[0313] 4. The AIOTF may update subscription data in UDM for AF ID or AF address.

[0314] 5. The AIOTF sends N2 message (e.g. DL NAS Transport) to the NG-RAN together with the DL Message.

[0315] 6. The AIOTF sends Charging Request to the CHF for the charging of the DL Message.

[0316] 7. The NG-RAN delivers the DL Message to the Ambient loT device.

[0317] In step 1, for AF in trusted domain, it may query UDM for AIOTF discovery and sends DL Message to AIOTF directly, without mandating NEF.

[0318] For the data delivered from AF to device, it may be included in a container. The container could be a NAS container or an application layer container. If it is a NAS container, AIOTF includes the data in the container. If it is an application layer container, AF includes the data in the container.

[0319] Figure 22

[0320] Fig. 22 shows a DO-DTT procedure in Architecture-1 . As shown, the procedure includes the following steps:

[0321] 1 . AF sends DL Message to the NEF, including the transaction ID , device ID, the DL data (which may contain the command to be executed in the Ambient loT device), and optional the additional AF ID or address for response receiving.

[0322] 2. The NEF discovers the serving AIOTF from UDM based on device ID (the serving AIOTF has registered towards the UDM).

[0323] 3. After discovery, the NEF forwards the DL Message to the AIOTF. 4. AIOTF may update subscription data in UDM for AF ID or AF address.

[0324] 5. The AIOTF selects AMF and forwards the DL Message to the AMF.

[0325] 6. The AIOTF sends Charging Request to the CHF for the charging of the DL Message, providing the transaction ID.

[0326] 7. The AMF sends N2 message (e.g. DL NAS Transport) to the NG-RAN together with the DL Message.

[0327] 8. The NG-RAN delivers the DL Message to the Ambient loT device.

[0328] 9. The device sends the response data (or the result of the execution of the command) to the NG-RAN, including the transaction ID if received.

[0329] 10. The NG-RAN sends N2 message (e.g. UL NAS Transport) to the AMF. Besides the information from the device, NG-RAN may further include its own information, e.g. optional RAN ID, optional position information, etc.

[0330] 11. The AM F sends the Response Message to the Al OTF.

[0331] 12. The AIOTF sends Response Message to NEF. It can be a response message for the request in step 3, or a separate notify message.

[0332] 13. The AIOTF sends Charging Request to the CHF for the charging of the Response Message, providing the transaction ID.

[0333] 14. The NEF sends the Response Message to the AF. It can be a response message for the request in step 1, or a separate notify message. If the additional AF address is provided in step 1, the notify message will be sent to this address.

[0334] If AF is in trusted domain, it may skip step 1 and query UDM for AIOTF discovery and sends DL Message to AIOTF directly, without mandating NEF. In step 12, AIOTF may also sends Response Message to AF directly via a response message or notify message.

[0335] Figure 23

[0336] Fig. 23 shows a DO-DTT procedure in Architecture-2. As shown, the procedure includes the following steps: 1 . AF sends DL Message to the NEF, including the transaction ID, device ID, the DL data (which may contain the command to be executed in the Ambient loT device), and optional the additional AF ID or AF address for response receiving.

[0337] 2. The NEF discovers the serving AIOTF from UDM based on device ID(the serving AIOTF has registered towards the UDM).

[0338] 3. After discovery, the NEF forwards the DL Message to the AIOTF.

[0339] 4. The AIOTF may update the subscription data in UDM for AF ID or AF address.

[0340] 5. The AIOTF sends N2 message (e.g. DL NAS Transport) to the NG-RAN together with the DL Message.

[0341] 6. The AIOTF sends Charging Request to the CHF for the charging of the DL Message, providing the transaction ID.

[0342] 7. The NG-RAN delivers the DL Message to the Ambient loT device.

[0343] 8. The device sends the response data (or the result of the execution of the command) to the NG-RAN, including the transaction ID if received.

[0344] 9. The NG-RAN sends N2 message (e.g. UL NAS Transport) to the AIOTF. Besides the information from the device, NG-RAN may further include its own information, e.g. optional RAN ID, optional position information, etc.

[0345] 10. The AIOTF sends Response Message to NEF. It can be a response message for the request in step 3, or a separate notify message.

[0346] 11. The AIOTF sends Charging Request to the CHF for the charging of the Response Message, providing the transaction ID.

[0347] 12. The NEF sends the Response Message to the AF. It can be a response message for the request in step 1, or a separate notify message. If the additional AF address is provided in step 1, the notify message will be sent to this address. If AF is in trusted domain, it may skip step 1 and query UDM for AIOTF discovery and sends DL Message to AIOTF directly, without mandating NEF. In step 10, AIOTF may also sends Response Message to AF directly via a response message or notify message.

[0348] Figures 24-25

[0349] Figs. 24 and 25 show a use case of asking reporting for all devices in a certain area in Architecture-1 and Architecture-2, respectively. The use case can be built upon DO-DTT in Architecture-1 and Architecture-2. Compared with the basic DO-DTT solution, the DL Message contains the command to be sent to a number of devices in a certain area, instead of one specific Ambient loT device.

[0350] Besides that, AF may specify aggregation period to allow downlink NFs (including NG-RANs) to aggregate the response message from the Ambient loT devices. If not provided, the NFs may have locally configured aggregation period, so that multiple received response data within the aggregation period can be aggregated and send to uplink NFs in one message.

[0351] The aggregation (handling the reports within the aggregation period) and the notification (handling the reports later than the aggregation period) may include filtering out information of the reports to include only requested and authorized information, which including filtering the reports from unintended devices, and filtering the unauthorized information (e.g. device ID), if AF is not authorized to receive.

[0352] As shown in Fig. 24, the procedure for the use case of asking reporting for all devices in a certain area in Architecture-1 includes the following steps.

[0353] 1 . AF sends DL Message to the NEF, including the transaction ID, device group IDs, device types, the DL data (which may contain the command to be executed in the Ambient loT device), optional the additional AF ID / address for response receiving, external geographical area (mandatory), and optional aggregation period, report after aggregation period.

[0354] 2. The NEF translates the external geographical area to internal geographical area.

[0355] 3. The NEF discovers the serving AIOTF from NRF based on the internal geographical area, and device group ID, device type may be considered as well, i.e. the AIOTF has registered its NF profile in the NRF to handle a certain area (can be whole network) and a set of device group IDs (can be all groups or a subset) and / or device type. 4. After discovery, the NEF duplicates / forks the request and forwards the DL Message to one or more AIOTFs, including the transaction ID, device group ID, device type, DL data, internal geographical area, aggregation period, and report after aggregation period.

[0356] 5. The AIOTF query NRF for the AMFs in the area that supports the functionality to handle the request.

[0357] 6. The AIOTF duplicates / forks the request and forwards the DL Message to the one or more AMFs in the area, including the transaction ID, device group ID, device type, DL data, internal geographical area, aggregation period.

[0358] 7. The AIOTF sends Charging Request to the CHF for the charging of the DL Message.

[0359] 8. The AMF duplicates / forks the request and sends N2 message (e.g. DL NAS Transport) to the NG-RANs in the area together with the DL Message, including the transaction ID, device group ID, device type, DL data, internal geographical area, aggregation period, report after aggregation period.

[0360] 9. The NG-RANs deliver the DL Message to the Ambient loT devices (e.g. devicel) in the area.

[0361] 10. The NG-RANs deliver the DL Message to the Ambient loT devices (e.g. device2) in the area.

[0362] 11 . The devicel sends the response data (or the result of the execution of the command) to the NG-RAN, including the transaction ID if received. The device ID may be included as well.

[0363] 12. The device2 sends the response data (or the result of the execution of the command) to the NG-RAN, including the transaction ID if received. The device ID may be included as well.

[0364] 13. The NG-RAN aggregates the Response Data within the aggregation period, e.g., based on transaction ID, or based on the combination of transaction ID and group I D / device type, etc. If aggregation period is not provided, it may be locally configured. After the aggregation period, the response data will be sent separately without aggregation, if AF request to report after aggregation period.

[0365] 14. The NG-RAN sends N2 message (e.g. UL NAS Transport) to the AMF. Besides the aggregated response from the device, NG-RAN may further include its own information, e.g. optional RAN ID, optional position information, etc. 15. The AMF may further aggregate the response from multiple NG-RANs within the aggregation period, e.g., based on transaction ID, or based on the combination of transaction ID and group I D / device type, etc. If aggregation period is not provided, it may be locally configured. After the aggregation period, the response data will be sent separately without aggregation, if AF requests to report after aggregation period.

[0366] 16. The AMF sends aggregated Response data to AIOTF.

[0367] 17. The AIOTF may further aggregate the response from multiple AMFs within the aggregation period, e.g., based on transaction ID, or based on the combination of transaction ID and group I D / device type, etc. If aggregation period is not provided, it may be locally configured. After the aggregation period, the response data will be sent separately without aggregation, if AF request to report after aggregation period.

[0368] 18. The AIOTF sends aggregated Response data to NEF.

[0369] 19. The AIOTF sends Charging Request to the CHF for the charging of the aggregated Response Message.

[0370] 20. The NEF may further aggregate the response, e.g., based on transaction ID, or based on the combination of transaction ID and group I D / device type, etc., and sends the aggregated Response Message to the AF within the aggregation period. It can be a response message for the request in step 1, or a separate notify message. If the additional AF address is provided in step 1 , the notify message will be sent to this address. If aggregation period is not provided, it may be locally configured. After the aggregation period, the response data will be sent separately without aggregation, if AF request to report after aggregation period.

[0371] If AF is in trusted domain, it may skip step 1 and AF can query NRF for AIOTF discovery and sends DL Message to AIOTF directly providing the internal geographical area, without mandating NEF. In step 18, AIOTF may also sends Response Message to AF directly via a response message or notify message.

[0372] In steps 13, 15, 17, and 20, the aggregation (handling the reports within the aggregation period) and the notification (handling the reports later than the aggregation period) may include filtering out information of the reports to include only requested and authorized information, which including filtering the reports from unintended devices, and filtering the unauthorized information (e.g. device ID), if AF is not authorized to receive.

[0373] It can be utilized to ask NG-RANs in an area to provide some data back to AF, instead of devices. The differences are: in step 1 , the DL data contains the commands towards NG-RANs instead of devices;

[0374] NG-RANs will not execute step 9 to 12; in step 13, NG-RANs process the command and generate the response. The command and response may be applicable to specific device group ID and / or device type if provided.

[0375] As shown in Fig. 25, the procedure for the use case of asking reporting for all devices in a certain area in Architecture-2 includes the following steps.

[0376] 1 . AF sends DL Message to the NEF, including the transaction ID device group ID, device type, the DL data (which may contain the command to be executed in the Ambient loT device), optional the additional AF ID / address for response receiving, external geographical area (mandatory), and optional aggregation period, report after aggregation period.

[0377] 2. The NEF translates the external geographical area to internal geographical area. Device group ID may be considered as well in the discovery if provided.

[0378] 3. The NEF discovers the serving AIOTF from NRF based on geographical area, and the device group ID and device type may be considered as well, i.e. the AIOTF has registered its NF profile in the NRF to handle a certain area (can be whole network) and a set of device group IDs (can be all groups or a subset) and / or device type.

[0379] 4. After discovery, the NEF duplicates / forks the request and forwards the DL Message to one or more AIOTFs, including the transaction ID, device group ID, device type, DL data, internal geographical area, aggregation period, and report after aggregation period.

[0380] 5. The AIOTF duplicates / forks the request and sends N2 message (e.g. DL NAS Transport) to the NG- RANs in the area together with the DL Message, including the transaction ID, device group ID, device type, DL data, internal geographical area, aggregation period, report after aggregation period.

[0381] 6. The AIOTF sends Charging Request to the CHF for the charging of the DL Message.

[0382] 7. The NG-RAN delivers the DL Message to the Ambient loT devices (e.g. devicel) in the area.

[0383] 8. The NG-RAN delivers the DL Message to the Ambient loT devices (e.g. device2) in the area. 9. The devicel sends the response data (or the result of the execution of the command) to the NG-RAN, including the transaction ID if received. The device ID may be included as well.

[0384] 10. The device2 sends the response data (or the result of the execution of the command) to the NG-RAN, including the transaction ID if received. The device ID may be included as well.

[0385] 11. The NG-RAN aggregates the Response Data, e.g., based on transaction ID, or based on the combination of transaction ID and group I D / device type, etc. within the aggregation period. If aggregation period is not provided, it may be locally configured. After the aggregation period, the response data will be sent separately without aggregation, if AF requests to report after aggregation period.

[0386] 12. The NG-RAN sends N2 message (e.g. UL NAS Transport) to the AIOTF. Besides the aggregated response from the device, NG-RAN may further include its own information, e.g. optional RAN ID, optional position information, etc.

[0387] 13. The AIOTF may further aggregate the response from multiple NG-RANs, e.g., based on transaction ID, or based on the combination of transaction ID and group I D / device type, etc. within the aggregation period. If aggregation period is not provided, it may be locally configured. After the aggregation period, the response data will be sent separately without aggregation, if AF request to report after aggregation period.

[0388] 14. The AIOTF sends aggregated Response data to NEF.

[0389] 15. The AIOTF sends Charging Request to the CHF for the charging of the aggregated Response Message.

[0390] 16. The NEF may further aggregate the response from multiple AIOTFs, e.g., based on transaction ID, or based on the combination of transaction ID and group ID / device type, etc. within the aggregation period. If aggregation period is not provided, it may be locally configured. After the aggregation period, the response data will be sent separately without aggregation, if AF request to report after aggregation period.

[0391] 17. The NEF sends the aggregated Response Message to the AF. It can be a response message for the request in step 1, or a separate notify message. If the additional AF address is provided in step 1, the notify message will be sent to this address. . After the aggregation period, the response data will be sent separately without aggregation, if AF request to report after aggregation period. If AF is in trusted domain, it may skip step 1 and AF can query NRF for AIOTF discovery and duplicates and sends DL Message to AIOTF directly providing the internal geographical area, without mandating NEF. In step 14, AIOTF may also sends Response Message to AF directly via a response message or notify message.

[0392] In steps 11, 13, and 16, the aggregation (handling the reports within the aggregation period) and the notification (handling the reports later than the aggregation period) may include filtering out information of the reports to include only requested and authorized information, which including filtering the reports from unintended devices, and filtering the unauthorized information (e.g. device ID), if AF is not authorized to receive.

[0393] It can be utilized to ask NG-RANs in an area to provide some data back to AF, instead of devices. The differences are: in step 1 , the DL data contains the commands towards NG-RANs instead of devices;

[0394] NG-RANs will not execute step 7 to 10; in step 11, NG-RANs process the command and generate the response. The command and response may be applicable to specific device group ID and / or device type if provided.

[0395] Figures 26-27

[0396] Figs. 26 and 27 show a use case of asking reporting for a device in a certain area in Architecture-1 and Architecture-2, respectively. The use case can be built upon DO-DTT in Architecture-1 and Architecture-2. Compared with the basic DO-DTT solution, the DL Message contains the command need to be sent to a certain area, so that the device may be found if not reachable.

[0397] As shown in Fig. 26, the procedure for the use case of asking reporting for a device in a certain area in Architecture-1 includes the following steps.

[0398] 1 . AF sends DL Message to the NEF, including the transaction ID, device ID, the DL data (which may contain the command to be executed in the Ambient loT device), optional the additional AF address for response receiving, external geographical area, and optional response period.

[0399] 2. The NEF translates the external geographical area to internal geographical area.

[0400] 3. The NEF discovers the serving AIOTF from UDM based on the device ID. If there is no AIOTF registered in the UDM, the NEF uses the NRF as in the above use case of asking reporting for all devices in a certain area, in which case the NEF may need to invoke one or more AIOTFs depending on the geographical area requested by the AF and supported by the AIOTFs. 4. After discovery, the NEF forwards the DL Message to the AIOTF, including the transaction ID, device ID, DL data, internal geographical area, and optional response period.

[0401] 5. The AIOTF query NRF for the AMFs in the area.

[0402] 6. The AIOTF duplicates / forks and forwards the DL Message to the one or more AMFs in the area, including the transaction ID, device ID, DL data, internal geographical area.

[0403] 7. The AIOTF sends Charging Request to the CHF for the charging of the DL Message.

[0404] 8. The AMF duplicates / forks and sends N2 message (e.g. DL NAS Transport) to the NG-RANs (e.g. RAN1) in the area together with the DL Message, including the transaction ID, device ID, DL data, internal geographical area.

[0405] 9. The AMF duplicates / forks and sends N2 message (e.g. DL NAS Transport) to the NG-RANs (e.g. RAN2) in the area together with the DL Message, including the transaction ID, device ID, DL data, internal geographical area. Step 8 - 9 are repeated for all NG-RANs in the area or until a response from a device is received.

[0406] 10. The NG-RAN (RAN1) delivers the DL Message to the Ambient loT device (e.g. device) in the area. Other NG-RANs including RAN2 also try to deliver but no response from the device, as the device is not in their coverage in this case.

[0407] 11 . The devicel sends the response data (or the result of the execution of the command) to the NG-RAN, including the transaction ID if received.

[0408] 12. The NG-RAN sends N2 message (e.g. UL NAS Transport) to the AMF. Besides the response from the device, NG-RAN may further include its own information, e.g. optional RAN ID, optional position information, etc.

[0409] 13. The AMF sends Response data to AIOTF, containing the information received from device and NG-RAN.

[0410] 14. The AIOTF sends Response data to NEF, via response or notify message. If the AIOTF cannot receive response within the response period, AIOTF may generate a failure response towards AF and send to NEF.

[0411] 15. The AIOTF sends Charging Request to the CHF for the charging of the Response Message. 16. The NEF sends the Response Message to the AF. It can be a response message for the request in step 1, or a separate notify message. If the additional AF address is provided in step 1, the notify message will be sent to this address. If the NEF has sent the AF request to more than one AIOTF the NEF waits for an AIOTFs to provide a response from the device and only in case all AIOTs provides a failure the NEF reports failure to the AF.

[0412] If AF is in trusted domain, it may skip step 1 and AF can query UDM for AIOTF discovery and sends DL Message to AIOTF directly providing the internal geographical area, without mandating NEF. In step 14, AIOTF may also sends Response Message to AF directly via a response message or notify message.

[0413] It is also an option that NEF / AF queries UDM to get the serving AIOTF in step 3 and execute steps 4-15 via this AIOTF firstly. If no response from the device, NEF / AF queries NRF to get AIOTFs in the geographical area in step 3 and execute steps 4-15 via those AIOTFs.

[0414] As shown in Fig. 27, the procedure for the use case of asking reporting for a device in a certain area in Architecture-2 includes the following steps.

[0415] 1 . AF sends DL Message to the NEF, including the transaction ID, device ID, the DL data (which may contain the command to be executed in the Ambient loT device), optional the additional AF address for response receiving, external geographical area, and optional response period.

[0416] 2. The NEF translates the external geographical area to internal geographical area.

[0417] 3. The NEF discovers the serving AIOTF from UDM based on the device ID or query NRF for discovering the AIOTFs in the area e.g. if there is no AIOTF registered in the UDM.

[0418] 4. After discovery, the NEF duplicates / forks and forwards the DL Message to one or more AIOTFs, including the transaction ID, device ID, DL data, internal geographical area.

[0419] 5. The AIOTF duplicates / forks and sends N2 message (e.g. DL NAS Transport) to NG-RANs (e.g. RAN1) in the area, including the transaction ID, device ID, DL data, internal geographical area.

[0420] 6. The AIOTF duplicates / forks and sends N2 message (e.g. DL NAS Transport) to the NG-RANs (e.g. RAN2) in the area together with the DL Message, including the transaction ID, device ID, DL data, internal geographical area. Step 5 - 6 are repeated for all NG-RANs in the area or until a response from a device is received.

[0421] 7. The AIOTF sends Charging Request to the CHF for the charging of the DL Message.

[0422] 8. The NG-RAN (RAN1) delivers the DL Message to the Ambient loT device (e.g. device) in the area. Other NG-RANs including RAN2 also try to deliver but no response from the device, as the device is not in their coverage in this case.

[0423] 9. The device sends the response data (or the result of the execution of the command) to the NG-RAN, including the transaction ID if received.

[0424] 10. The NG-RAN sends N2 message (e.g. UL NAS Transport) to the AIOTF. Besides the response from the device, NG-RAN may further include its own information, e.g. optional RAN ID, optional position information, etc.

[0425] 11 . The AIOTF sends Response data to NEF, via response or notify message.

[0426] 12. The AIOTF sends Charging Request to the CHF for the charging of the Response Message.

[0427] 13. The NEF sends the Response Message to the AF. It can be a response message for the request in step

[0428] I, or a separate notify message. If the additional AF address is provided in step 1, the notify message will be sent to this address. If the NEF cannot receive response within the response period, NEF may generate a failure response towards AF. If the NEF has sent the AF request to more than one AIOTF the NEF waits for an AIOTFs to provide a response from the device and only in case all AIOTs provides a failure the NEF reports failure to the AF.

[0429] If AF is in trusted domain, it may skip step 1 and AF can query NRF for AIOTFs discovery and duplicates and sends DL Message to AIOTFs directly providing the internal geographical area, without mandating NEF. In step

[0430] II, AIOTF may also sends Response Message to AF directly via a response message or notify message.

[0431] It is also an option that NEF / AF queries UDM to get the serving AIOTF in step 3 and execute steps 4-12 via this AIOTF firstly. If no response from the device, NEF / AF queries NRF to get AIOTFs in the geographical area in step 3 and execute steps 4-12 via those AIOTFs. Figure 28

[0432] Fig. 28 is a block diagram of an loT device 2800 according to an embodiment of the present disclosure.

[0433] The loT device 2800 includes a communication interface 2810, a processor 2820 and a memory 2830.

[0434] The memory 2830 may contain instructions executable by the processor 2820 whereby the loT device 2800 is operative to perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 3. Particularly, the memory 2830 may contain instructions executable by the processor 2820 whereby the loT device 2800 is operative to: transmit, to an NG-RAN node, a signaling message to be handled by a core network node. The signaling message is an AS message.

[0435] In an embodiment, the signaling message may be a registration request.

[0436] In an embodiment, the registration request may be an initial registration request, or the registration request may be a mobility registration request and the NG-RAN node may be a target NG-RAN node.

[0437] In an embodiment, the memory 2830 may further contain instructions executable by the processor 2820 whereby the loT device 2800 is operative to receive, from the NG-RAN node, a response to the signaling message. The response may be an AS message.

[0438] Alternatively, the memory 2830 may contain instructions executable by the processor 2820 whereby the loT device 2800 is operative to perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 13. Particularly, the memory 2830 may contain instructions executable by the processor 2820 whereby the loT device 2800 is operative to: receive, from an NG-RAN node, a first message including a transaction ID for uplinkdownlink association and downlink data containing a command to be executed by the loT device. The memory 2830 may further contain instructions executable by the processor 2820 whereby the loT device 2800 is operative to: transmit, to the NG-RAN node, a second message including the transaction ID and a response generated by executing the command.

[0439] Figure 29

[0440] Fig. 29 is a block diagram of a network node 2900 according to an embodiment of the present disclosure.

[0441] The network node 2900 includes a communication interface 2910, a processor 2920 and a memory 2930. The memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing an NG-RAN node, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 4. Particularly, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing an NG-RAN node: receive, from an loT device, a first signaling message to be handled by a core network node. The first signaling message is an AS message. The memory 2930 may further contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing the NG-RAN node: transmit, to an AMF or an NF for loT communication, a second signaling message based on the first signaling message.

[0442] In an embodiment, the first signaling message may be a registration request, and the second signaling message may be a request for registration on behalf of the loT device.

[0443] In an embodiment, the memory 2930 may further contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing the NG-RAN node: transmit, to the loT device, a response to the first signaling message. The response is an AS message.

[0444] Alternatively, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing a target NG-RAN node, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 5. Particularly, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing a target NG-RAN node: receive, from an loT device, a mobility registration request as an AS message. The method further includes fetching a device context of the loT device from a source NG-RAN node.

[0445] In an embodiment, the memory 2930 may further contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing the target NG-RAN node: transmit, to an AMF or an NF for loT communication, a message containing a device Identifier (ID) of the loT device.

[0446] Alternatively, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing an AMF, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 6. Particularly, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing an AMF: receive a request for registration for an loT device, the request containing a device ID of the loT device; select an NF for loT communication based on the device ID; and transmit, to the NF for loT communication, a registration request containing the device ID. Alternatively, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing an NF for loT communication, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 7. Particularly, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing an NF for loT communication: receive, from an AMF or an NG-RAN node, a registration request containing a device ID of an loT device; and register for the loT device towards a UDM or UDR.

[0447] In an embodiment, the memory 2930 may further contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing the NF for loT communication: retrieve, from the UDM or UDR, subscription data of the loT device, the subscription data including an AF ID or AF address associated with the loT device.

[0448] Alternatively, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing an NF for loT communication, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 8. Particularly, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing an NF for loT communication: receive, from an AMF or an NG-RAN node, a first message containing a device ID of an loT device and uplink data from the loT device; and transmit, to a NEF, a second message containing the device ID, the uplink data, and an AF ID or AF address associated with the loT device.

[0449] Alternatively, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing an NF for loT communication, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 9. Particularly, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing an NF for loT communication: receive, from a NEF, a first message containing a device ID of an loT device and downlink data destined to the loT device; and transmit, to an AMF or an NG-RAN node, a second message containing the device ID and the downlink data.

[0450] In an embodiment, the first message may further contain an AF ID or AF address associated with the loT device. The memory 2930 may further contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing the NF for loT communication: transmit, to a UDM or UDR, a request to update subscription data of the loT device with the AF ID or AF address.

[0451] In an embodiment, the first message may further contain a transaction ID for uplink-downlink association. The memory 2930 may further contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing the NF for loT communication: receivie, from the AMF or the NG-RAN node, a third message containing the device ID, the transaction ID, and uplink data from the loT device as a response to the downlink data.

[0452] In an embodiment, the first message may further contain an additional AF ID or AF address for receiving the uplink data.

[0453] Alternatively, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing an AF, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 10. Particularly, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing an AF: transmit a request to an NEF. The request requests for responses from loT devices in an area, and the request contains information on the area. Alternatively, the request requests for a response from an loT device in an area, and the request contains information on the area and a device ID of the loT device.

[0454] In an embodiment, the request may request for responses from loT devices belonging to a device group or device type in the area, and the request may further contain at least one of: an ID of the device group or information on the device type; a transaction ID for uplink-downlink association; and downlink data.

[0455] In an embodiment, the downlink data may contain a command to be executed by each of the loT devices.

[0456] In an embodiment, the memory 2930 may further contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing the AF: receive a response from the NEF. The response may be based on the ID of the device group or information on the device type.

[0457] Alternatively, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing a first NF or an NG-RAN node, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 11. Particularly, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing a first NF or an NG-RAN node: receive, from an AF or a second NF, a first request for responses from loT devices in an area, the first request containing information on the area; and transmit, to each of one or more third NFs based on the information on the area, a second request for responses from the loT devices in the area, the second request containing the information on the area. In an embodiment, the first request and the second request may each request for responses from loT devices belonging to a device group or device type in the area, and the first request and the second request may each further contain at least one of: an ID of the device group or information on the device type; a transaction ID for uplink-downlink association; and downlink data.

[0458] In an embodiment, the downlink data may contain a command to be executed by each of the loT devices.

[0459] In an embodiment, the memory 2930 may further contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing the first NF or NG-RAN node: receive responses from the one or more third NFs, the responses each being based on the ID of the device group or information on the device type; and transmit an aggregated response obtained by aggregating the responses to the AF or the second NF.

[0460] Alternatively, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing a first NF or an NG-RAN node, perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 12. Particularly, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing a first NF or an NG-RAN node: receive, from an AF or a second NF, a first request for a response from an loT device in an area, the first request containing information on the area and a device ID of the loT device; and transmit, to each of one or more third NFs based on the information on the area, a second request for a response from the loT device in the area, the second request containing the information on the area and the device ID.

[0461] In an embodiment, the first request and the second request may each further contain a transaction ID for uplinkdownlink association and downlink data.

[0462] In an embodiment, the downlink data may contain a command to be executed by the loT device.

[0463] In an embodiment, the memory 2930 may contain instructions executable by the processor 2920 whereby the network node 2900 is operative to, when implementing the first NF or NG-RAN node: receive a response from one of the one or more third NFs and transmit the response to the AF or the second NF.

[0464] The present disclosure also provides at least one computer program product in the form of a non-volatile or volatile memory, e.g., a non-transitory computer readable storage medium, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a flash memory and a hard drive. The computer program product includes a computer program. The computer program includes: code / computer readable instructions, which when executed by the processor 2820 causes the loT device 2800 to perform the actions, e.g., of the procedure described earlier in conjunction with Fig. 3 or 13; or code / computer readable instructions, which when executed by the processor 2920 causes the network device 2900 to perform the actions, e.g., of the procedure described earlier in conjunction with any of Figs. 4-12.

[0465] The computer program product may be configured as a computer program code structured in computer program modules. The computer program modules could essentially perform the actions of the flow illustrated in any of Figs. 3-13.

[0466] The processor may be a single CPU (Central Processing Unit), but could also comprise two or more processing units. For example, the processor may include general purpose microprocessors; instruction set processors and / or related chips sets and / or special purpose microprocessors such as Application Specific Integrated Circuits (ASICs). The processor may also comprise board memory for caching purposes. The computer program may be carried in a computer program product connected to the processor. The computer program product may comprise a non-transitory computer readable storage medium on which the computer program is stored. For example, the computer program product may be a flash memory, a Random Access Memory (RAM), a Read-Only Memory (ROM), or an EEPROM, and the computer program modules described above could in alternative embodiments be distributed on different computer program products in the form of memories.

[0467] Figure 30

[0468] Fig. 30 shows an example of a communication system QQ100 in accordance with some embodiments.

[0469] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non- 3GPP access point. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0470] 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 QQ100 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 QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0471] The UEs QQ112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network QQ102.

[0472] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. 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 QQ106 includes one more core network nodes (e.g., core network node QQ108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node QQ108. Example core network nodes include functions of one or more of a Network Repository Function (NRF), 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 (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0473] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more services. 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.

[0474] As a whole, the communication system QQ100 of Fig. 30 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 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 (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for M I crowave Access (WIMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LIFI, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0475] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 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.

[0476] In some examples, the UEs QQ112 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 QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. Additionally, a UE may be configured for operating in single- or multi-RAT or multistandard 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).

[0477] In the example, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 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 QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 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 QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0478] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d), and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 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 QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0479] Figure 31

[0480] Fig. 31 shows a UE QQ200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE 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 (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0481] A UE 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, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE 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, a UE 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).

[0482] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Fig. 31 . The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0483] The processing circuitry QQ202 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 QQ210. The processing circuitry QQ202 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 QQ202 may include multiple central processing units (CPUs).

[0484] In the example, the input / output interface QQ206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. 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 the UE QQ200. 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.

[0485] In some embodiments, the power source QQ208 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. The power source QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0486] The memory QQ210 may be or be configured to include memory such as random access memory (RAM), readonly 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 QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0487] The memory QQ210 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 (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.' The memory QQ210 may allow the UE QQ200 to access instructions, application 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 QQ210, which may be or comprise a device-readable storage medium.

[0488] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 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 UE or a network node in an access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g. , antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0489] In the illustrated embodiment, communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, 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 in 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.

[0490] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The 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).

[0491] As another example, a UE 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, the UE 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.

[0492] A UE, 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, city 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 head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), 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. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Fig. 31.

[0493] As yet another specific example, in an loT scenario, a UE 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 UE and / or a network node. The UE 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, the UE may implement the 3GPP NB-loT standard. In other scenarios, a UE 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.

[0494] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone's speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE 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 UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0495] Figure 32

[0496] Fig. 32 shows a network node QQ300 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 telecommunication network. 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)).

[0497] Base stations 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 base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units 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).

[0498] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multistandard 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).

[0499] The network node QQ300 includes a processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308. The network node QQ300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node QQ300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components 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 QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, for example GSM, WCDMA, LTE, NR, WiFi, 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 QQ300.

[0500] The processing circuitry QQ302 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 network node QQ300 components, such as the memory QQ304, to provide network node QQ300 functionality. In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 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 QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0501] The memory QQ304 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 computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 00302. The memory 00304 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 00302 and utilized by the network node 00300. The memory 00304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0502] The communication interface QQ306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 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 QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310. Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0503] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio front-end circuitry and is connected to the antenna QQ310.

[0504] Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0505] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio front-end circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0506] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0507] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 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 QQ308. As a further example, the power source QQ308 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. Embodiments of the network node QQ300 may include additional components beyond those shown in Fig. 32 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 QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0508] Figure 33

[0509] Fig. 33 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Fig. 30, in accordance with various aspects described herein. As used herein, the host QQ400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host QQ400 may provide one or more services to one or more UEs.

[0510] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Fig. 31 and Fig. 32, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0511] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (WC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAG, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs QQ414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. Figure 34

[0512] Fig. 34 is a block diagram illustrating a virtualization environment QQ500 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 QQ500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

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

[0514] Hardware QQ504 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 QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0515] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, 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.

[0516] In the context of NFV, a VM QQ508 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 QQ508, and that part of hardware QQ504 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 VMs QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0517] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 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 QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 is coupled to one or more radio units that each includes 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 QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0518] Figure 35

[0519] Fig. 35 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Fig. 30 and / or UE QQ200 of Fig. 31), network node (such as network node QQ110a of Fig. 30 and / or network node QQ300 of Fig. 32), and host (such as host QQ116 of Fig. 30 and / or host QQ400 of Fig. 33) discussed in the preceding paragraphs will now be described with reference to Fig. 35.

[0520] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0521] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Fig. 30) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0522] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 and executable by the UE's processing circuitry. The software includes a client application, such as a web browser or operatorspecific "app” that may be operable to provide a service to a human or non-human user via UE QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection QQ650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection QQ650.

[0523] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0524] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602. In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0525] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, extended battery lifetime.

[0526] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host QQ602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0527] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection QQ650 between the host QQ602 and UE QQ606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

[0528] SOME EMBODIMENTS

[0529] Some of the embodiments that have been described above may be summarized in the following manner:

[0530] 1 . A method (300) in an Internet of Things, loT, device, comprising: transmitting (310), to a Next Generation Radio Access Network, NG-RAN, node, a signaling message to be handled by a core network node, the signaling message being an Access Stratum, AS, message.

[0531] 2. The method (300) of embodiment 1 , wherein the signaling message is a registration request.

[0532] 3. The method (300) of embodiment 2, wherein the registration request is an initial registration request, or the registration request is a mobility registration request and the NG-RAN node is a target NG-RAN node.

[0533] 4. The method (300) of any one of embodiment 1-3, further comprising: receiving, from the NG-RAN node, a response to the signaling message, the response being an AS message.

[0534] 5. A method (400) in a Next Generation Radio Access Network, NG-RAN, node, comprising: receiving (410), from an Internet of Things, loT, device, a first signaling message to be handled by a core network node, the first signaling message being an Access Stratum, AS, message; and transmitting (420), to an Access and Mobility Management Function, AMF, or a Network Function, NF, for loT communication, a second signaling message based on the first signaling message. 6. The method (400) of embodiment 5, wherein the first signaling message is a registration request, and the second signaling message is a request for registration on behalf of the loT device.

[0535] 7. The method (400) of embodiment 5 or 6, further comprising: transmitting, to the loT device, a response to the first signaling message, the response being an AS message.

[0536] 8. A method (500) in a target Next Generation Radio Access Network, NG-RAN, node, comprising: receiving (510), from an Internet of Things, loT, device, a mobility registration request as an Access Stratum, AS, message; and fetching (520) a device context of the loT device from a source NG-RAN node.

[0537] 9. The method (500) of embodiment 8, further comprising: transmitting, to an Access and Mobility Management Function, AMF, or a Network Function, NF, for loT communication, a message containing a device Identifier, ID, of the loT device.

[0538] 10. A method (600) in an Access and Mobility Management Function, AMF, comprising: receiving (610) a request for registration for an Internet of Things, loT, device, the request containing a device Identifier, ID, of the loT device; selecting (620) a Network Function, NF, for loT communication based on the device ID; and transmitting (630), to the NF for loT communication, a registration request containing the device ID.

[0539] 11. A method (700) in a Network Function, NF, for Internet of Things, loT, communication, the method comprising: receiving (710), from an Access and Mobility Management Function, AMF, or a Next Generation Radio Access Network, NG-RAN, node, a registration request containing a device Identifier, ID, of an Internet of Things, loT, device; and registering (720) for the loT device towards a Unified Data Management, UDM, or Unified Data Repository, UDR.

[0540] 12. The method (700) of embodiment 11, further comprising: retrieving, from the UDM or UDR, subscription data of the loT device, the subscription data including an Application Function, AF, ID or AF address associated with the loT device. 13. A method (800) in a Network Function, NF, for Internet of Things, loT, communication, the method comprising: receiving (810), from an Access and Mobility Management Function, AMF, or a Next Generation Radio Access Network, NG-RAN, node, a first message containing a device Identifier, ID, of an Internet of Things, loT, device and uplink data from the loT device; and transmitting (820), to a Network Exposure Function, NEF, a second message containing the device ID, the uplink data, and an Application Function, AF, ID or AF address associated with the loT device.

[0541] 14. A method (900) in a Network Function, NF, for Internet of Things, loT, communication, the method comprising: receiving (910), from a Network Exposure Function, NEF, a first message containing a device Identifier, ID, of an Internet of Things, loT, device and downlink data destined to the loT device; and transmitting (920), to an Access and Mobility Management Function, AMF, or a Next Generation Radio Access Network, NG-RAN, node, a second message containing the device ID and the downlink data.

[0542] 15. The method (900) of embodiment 14, wherein the first message further contains an Application Function, AF, ID or AF address associated with the loT device, and wherein the method further comprises: transmitting, to a Unified Data Management, UDM, or Unified Data Repository, UDR, a request to update subscription data of the loT device with the AF ID orAF address.

[0543] 16. The method (900) of embodiment 14, wherein the first message further contains a transaction ID for uplink-downlink association, and wherein the method further comprises: receiving, from the AMF or the NG-RAN node, a third message containing the device ID, the transaction ID, and uplink data from the loT device as a response to the downlink data.

[0544] 17. The method (900) of embodiment 14, wherein the first message further contains an additional AF ID or AF address for receiving the uplink data.

[0545] 18. A method (1000) in an Application Function, AF, comprising: transmitting (1010) a request to a Network Exposure Function, NEF, wherein the request requests for responses from Internet of Things, loT, devices in an area, and the request contains information on the area, or the request requests for a response from an loT device in an area, and the request contains information on the area and a device ID of the loT device. 19. The method (1000) of embodiment 18, wherein the request requests for responses from loT devices belonging to a device group or device type in the area, and the request further contains at least one of:

[0546] - an ID of the device group or information on the device type;

[0547] - a transaction ID for uplink-downlink association; and

[0548] - downlink data.

[0549] 20. The method (1000) of embodiment 19, wherein the downlink data contains a command to be executed by each of the loT devices.

[0550] 21. The method (1000) of embodiment 19 or 20, further comprising: receiving a response from the NEF, the response being based on the ID of the device group or information on the device type.

[0551] 22. A method (1100) in a first Network Function, NF, or a Next Generation Radio Access Network, NG-RAN, node, comprising: receiving (1110), from an Application Function, AF, or a second NF, a first request for responses from Internet of Things, loT, devices in an area, the first request containing information on the area; and transmitting (1120), to each of one or more third NFs based on the information on the area, a second request for responses from the loT devices in the area, the second request containing the information on the area.

[0552] 23. The method (1100) of embodiment 22, wherein the first request and the second request each request for responses from loT devices belonging to a device group or device type in the area, and the first request and the second request each further contain at least one of:

[0553] - an ID of the device group or information on the device type;

[0554] - a transaction ID for uplink-downlink association; and

[0555] - downlink data.

[0556] 24. The method (1100) of embodiment 23, wherein the downlink data contains a command to be executed by each of the loT devices.

[0557] 25. The method (1100) of embodiment 23 or 24, further comprising: receiving responses from the one or more third NFs, the responses each being based on the ID of the device group or information on the device type; and transmitting an aggregated response obtained by aggregating the responses to the AF or the second NF. 26. A method (1200) in a first Network Function, NF, or a Next Generation Radio Access Network, NG-RAN, node, comprising: receiving (1210), from an Application Function, AF, or a second NF, a first request for a response from an Internet of Things, loT, device in an area, the first request containing information on the area and a device ID of the loT device; and transmitting (1220), to each of one or more third NFs based on the information on the area, a second request for a response from the loT device in the area, the second request containing the information on the area and the device ID.

[0558] 27. The method (1200) of embodiment 26, wherein the first request and the second request each further contain:

[0559] - a transaction ID for uplink-downlink association; and

[0560] - downlink data.

[0561] 28. The method (1200) of embodiment 27, wherein the downlink data contains a command to be executed by the loT device.

[0562] 29. The method (1200) of embodiment 27 or 28, further comprising: receiving a response from one of the one or more third NFs; and transmitting the response to the AF or the second NF.

[0563] 30. A method (1300) in an Internet of Things, loT, device, comprising: receiving (1310), from a Next Generation Radio Access Network, NG-RAN, node, a first message including a transaction ID for uplink-downlink association and downlink data containing a command to be executed by the loT device; and transmitting (1320), to the NG-RAN node, a second message including the transaction ID and a response generated by executing the command.

[0564] 31 . An Internet of Things, loT, device (2800), comprising a communication interface (2810), a processor (2820), and a memory (2830), the memory (2830) comprising instructions executable by the processor (2820) whereby the loT device (2800) is operative to perform the method according to any one of embodiment 1-4 or 30. 32. A computer-readable storage medium having computer-readable instructions stored thereon, the computer-readable instructions, when executed by a processor of an Internet of Things, loT, device, configure the loT device to perform the method according to any one of embodiment 1-4 or 30.

[0565] 33. A network node (2900), comprising a communication interface (2910), a processor (2920), and a memory (2930), the memory (2930) comprising instructions executable by the processor (2920) whereby the network node (2900) is operative to: when implementing a Next Generation Radio Access Network, NG-RAN, node, perform the method according to any one of embodiment 5-7, or when implementing a target NG-RAN node, perform the method according to embodiment 8 or 9, or when implementing an Access and Mobility Management Function, AMF, perform the method according to embodiment 10, or when implementing a Network Function, NF, for loT communication, perform the method according to any one of embodiment 11-12, 13, or 14-17, or when implementing an Application Function, AF, perform the method according to any one of embodiment 18-21, or when implementing a first NF or an NG-RAN node, perform the method according to any one of embodiment 22-25 or 26-29.

[0566] 34. A computer-readable storage medium having computer-readable instructions stored thereon, the computer-readable instructions, when executed by a processor of a network node, configure the network node to: when implementing a Next Generation Radio Access Network, NG-RAN, node, perform the method according to any one of embodiment 5-7, or when implementing a target NG-RAN node, perform the method according to embodiment 8 or 9, or when implementing an Access and Mobility Management Function, AMF, perform the method according to embodiment 10, or when implementing a Network Function, NF, for loT communication, perform the method according to any one of embodiment 11-12, 13, or 14-17, or when implementing an Application Function, AF, perform the method according to any one of embodiment 18-21, or when implementing a first NF or an NG-RAN node, perform the method according to any one of 22-25 or 26- 29. 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 / or software 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.

[0567] 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.

[0568] The disclosure has been described above with reference to embodiments thereof. It should be understood that various modifications, alternations and additions can be made by those skilled in the art without departing from the spirits and scope of the disclosure. Therefore, the scope of the disclosure is not limited to the above particular embodiments but only defined by the claims as attached.

Claims

CLAIMSWhat is claimed is:1 . A method (300) in an Internet of Things, loT, device, comprising: transmitting (310), to a Next Generation Radio Access Network, NG-RAN, node, a signaling message to be handled by a core network node, the signaling message being an Access Stratum, AS, message.

2. The method (300) of claim 1 , wherein the signaling message is a registration request.

3. The method (300) of claim 2, wherein the registration request is an initial registration request, or the registration request is a mobility registration request and the NG-RAN node is a target NG-RAN node.

4. The method (300) of any of claims 1 -3, further comprising: receiving, from the NG-RAN node, a response to the signaling message, the response being an AS message.

5. A method (400) in a Next Generation Radio Access Network, NG-RAN, node, comprising: receiving (410), from an Internet of Things, loT, device, a first signaling message to be handled by a core network node, the first signaling message being an Access Stratum, AS, message; and transmitting (420), to an Access and Mobility Management Function, AMF, or a Network Function, NF, for loT communication, a second signaling message based on the first signaling message.

6. The method (400) of claim 5, wherein the first signaling message is a registration request, and the second signaling message is a request for registration on behalf of the loT device.

7. The method (400) of claim 5 or 6, further comprising: transmitting, to the loT device, a response to the first signaling message, the response being an AS message.

8. A method (500) in a target Next Generation Radio Access Network, NG-RAN, node, comprising: receiving (510), from an Internet of Things, loT, device, a mobility registration request as an Access Stratum, AS, message; and fetching (520) a device context of the loT device from a source NG-RAN node.

9. The method (500) of claim 8, further comprising: transmitting, to an Access and Mobility Management Function, AMF, or a Network Function, NF, for loT communication, a message containing a device Identifier, ID, of the loT device.

10. A method (600) in an Access and Mobility Management Function, AMF, comprising: receiving (610) a request for registration for an Internet of Things, loT, device, the request containing a device Identifier, ID, of the loT device; selecting (620) a Network Function, NF, for loT communication based on the device ID; and transmitting (630), to the NF for loT communication, a registration request containing the device ID.

11. A method (700) in a Network Function, NF, for Internet of Things, loT, communication, the method comprising: receiving (710), from an Access and Mobility Management Function, AMF, or a Next Generation Radio Access Network, NG-RAN, node, a registration request containing a device Identifier, ID, of an Internet of Things, loT, device; and registering (720) for the loT device towards a Unified Data Management, UDM, or Unified Data Repository, UDR.

12. The method (700) of claim 11, further comprising: retrieving, from the UDM or UDR, subscription data of the loT device, the subscription data including an Application Function, AF, ID or AF address associated with the loT device.

13. A method (800) in a Network Function, NF, for Internet of Things, loT, communication, the method comprising: receiving (810), from an Access and Mobility Management Function, AMF, or a Next Generation Radio Access Network, NG-RAN, node, a first message containing a device Identifier, ID, of an Internet of Things, loT, device and uplink data from the loT device; and transmitting (820), to a Network Exposure Function, NEF, a second message containing the device ID, the uplink data, and an Application Function, AF, ID or AF address associated with the loT device.

14. A method (900) in a Network Function, NF, for Internet of Things, loT, communication, the method comprising: receiving (910), from a Network Exposure Function, NEF, a first message containing a device Identifier, ID, of an Internet of Things, loT, device and downlink data destined to the loT device; andtransmitting (920), to an Access and Mobility Management Function, AMF, or a Next Generation Radio Access Network, NG-RAN, node, a second message containing the device ID and the downlink data.

15. The method (900) of claim 14, wherein the first message further contains an Application Function, AF, ID or AF address associated with the loT device, and wherein the method further comprises: transmitting, to a Unified Data Management, UDM, or Unified Data Repository, UDR, a request to update subscription data of the loT device with the AF ID orAF address.

16. The method (900) of claim 14, wherein the first message further contains a transaction ID for uplinkdownlink association, and wherein the method further comprises: receiving, from the AMF or the NG-RAN node, a third message containing the device ID, the transaction ID, and uplink data from the loT device as a response to the downlink data.

17. The method (900) of claim 14, wherein the first message further contains an additional AF ID or AF address for receiving the uplink data.

18. A method (1000) in an Application Function, AF, comprising: transmitting (1010) a request to a Network Exposure Function, NEF, wherein the request requests for responses from Internet of Things, loT, devices in an area, and the request contains information on the area, or the request requests for a response from an loT device in an area, and the request contains information on the area and a device ID of the loT device.

19. The method (1000) of claim 18, wherein the request requests for responses from loT devices belonging to a device group or device type in the area, and the request further contains at least one of:- an ID of the device group or information on the device type;- a transaction ID for uplink-downlink association; and- downlink data.

20. The method (1000) of claim 19, wherein the downlink data contains a command to be executed by each of the loT devices.

21. The method (1000) of claim 19 or 20, further comprising: receiving a response from the NEF, the response being based on the ID of the device group or information on the device type.

22. A method (1100) in a first Network Function, NF, or a Next Generation Radio Access Network, NG-RAN, node, comprising: receiving (1110), from an Application Function, AF, or a second NF, a first request for responses from Internet of Things, loT, devices in an area, the first request containing information on the area; and transmitting (1120), to each of one or more third NFs based on the information on the area, a second request for responses from the loT devices in the area, the second request containing the information on the area.

23. The method (1100) of claim 22, wherein the first request and the second request each request for responses from loT devices belonging to a device group or device type in the area, and the first request and the second request each further contain at least one of:- an ID of the device group or information on the device type;- a transaction ID for uplink-downlink association; and- downlink data.

24. The method (1100) of claim 23, wherein the downlink data contains a command to be executed by each of the loT devices.

25. The method (1100) of claim 23 or 24, further comprising: receiving responses from the one or more third NFs, the responses each being based on the ID of the device group or information on the device type; and transmitting an aggregated response obtained by aggregating the responses to the AF or the second NF.

26. A method (1200) in a first Network Function, NF, or a Next Generation Radio Access Network, NG-RAN, node, comprising: receiving (1210), from an Application Function, AF, or a second NF, a first request for a response from an Internet of Things, loT, device in an area, the first request containing information on the area and a device ID of the loT device; and transmitting (1220), to each of one or more third NFs based on the information on the area, a second request for a response from the loT device in the area, the second request containing the information on the area and the device ID.

27. The method (1200) of claim 26, wherein the first request and the second request each further contain:- a transaction ID for uplink-downlink association; and- downlink data.

28. The method (1200) of claim 27, wherein the downlink data contains a command to be executed by the loT device.

29. The method (1200) of claim 27 or 28, further comprising: receiving a response from one of the one or more third NFs; and transmitting the response to the AF or the second NF.

30. A method (1300) in an Internet of Things, loT, device, comprising: receiving (1310), from a Next Generation Radio Access Network, NG-RAN, node, a first message including a transaction ID for uplink-downlink association and downlink data containing a command to be executed by the loT device; and transmitting (1320), to the NG-RAN node, a second message including the transaction ID and a response generated by executing the command.31 . An Internet of Things, loT, device (2800), comprising a communication interface (2810), a processor (2820), and a memory (2830), the memory (2830) comprising instructions executable by the processor (2820) whereby the loT device (2800) is operative to perform the method according to any of claims 1-4 or 30.

32. A computer-readable storage medium having computer-readable instructions stored thereon, the computer-readable instructions, when executed by a processor of an Internet of Things, loT, device, configure the loT device to perform the method according to any of claims 1-4 or 30.

33. A network node (2900), comprising a communication interface (2910), a processor (2920), and a memory (2930), the memory (2930) comprising instructions executable by the processor (2920) whereby the network node (2900) is operative to: when implementing a Next Generation Radio Access Network, NG-RAN, node, perform the method according to any of claims 5-7, or when implementing a target NG-RAN node, perform the method according to claim 8 or 9, or when implementing an Access and Mobility Management Function, AMF, perform the method according to claim 10, or when implementing a Network Function, NF, for loT communication, perform the method according to any of claims 11-12, 13, or 14-17, or when implementing an Application Function, AF, perform the method according to any of claims 18-21, orwhen implementing a first NF or an NG-RAN node, perform the method according to any of claims 22-25 or 26-29.

34. A computer-readable storage medium having computer-readable instructions stored thereon, the computer-readable instructions, when executed by a processor of a network node, configure the network node to: when implementing a Next Generation Radio Access Network, NG-RAN, node, perform the method according to any of claims 5-7, or when implementing a target NG-RAN node, perform the method according to claim 8 or 9, or when implementing an Access and Mobility Management Function, AMF, perform the method according to claim 10, or when implementing a Network Function, NF, for loT communication, perform the method according to any of claims 11-12, 13, or 14-17, or when implementing an Application Function, AF, perform the method according to any of claims 18-21, or when implementing a first NF or an NG-RAN node, perform the method according to any of claims 22-25 or 26-29.

Images