Ambient internet of things data forwarding over ue

Abstract

Example embodiments of the present disclosure provide solutions for Ambient Internet of Things (AIoT) data forwarding over user equipment (UE) In an example method, a terminal device transmits capability information indicating at least one AIoT data uplink (UL) method supported by the terminal device. The terminal device receives, from a base station, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method. The terminal device transmits, to an AIoT function (AIoTF), AIoT data using the AIoT data UL method indicated by the AIoT session request message

Description

AMBIENT INTERNET OF THINGS DATA FORWARDING OVER UEFIELD

[0001] Example embodiments of the present disclosure generally relate to the field of communication, and in particular, to terminal devices, network devices, methods, apparatuses, and computer readable media for Ambient Internet of Things (AIoT) data forwarding over user equipment (UE).BACKGROUND

[0002] A communication network can be seen as a facility that enables communications between two or more communication devices, or provides communication devices access to a data network. A mobile or wireless communication network is one example of a communication network. Such communication networks operate in accordance with standards, such as those promulgated by 3 GPP (Third Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of such standards include the so-called 5G (5th Generation) standard or other standards promulgated by 3GPP.

[0003] A new study item on solutions for Ambient Internet of Things (AIoT) in new radio (NR) was recently approved. This study targets a further assessment at RAN (Radio Access Networks) WG (Work Group)-level of AIoT, 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. The study shall provide clear differentiation, i.e. addressing use cases and scenarios that cannot otherwise be fulfilled based on existing 3GPP LPWA (Low-Power Wide-Area) loT technology e.g. new band (NB)-IoT including with reduced peak transmission (Tx) power.SUMMARY

[0004] In general, embodiments of the present disclosure provide solutions for AIoT data forwarding over UE.

[0005] In a first aspect, there is provided a terminal device. The terminal device comprises at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: transmit capabilityinformation indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by the terminal device; receive, from a base station, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method; and transmit, to an AIoT Function (AIoTF), AIoT data using the AIoT data UL method indicated by the AIoT session request message.

[0006] In a second aspect, there is provided a base station comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to: receive, from an Ambient Internet of Things (AIoT) Function (AIoTF), an AIoT session request message including capability information of a terminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data uplink (UL) method supported by the terminal device; select, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method; and transmit the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

[0007] In a third aspect, there is provided a network device comprising an Ambient Internet of Things (AIoT) Function (AIoTF), the network device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to: obtain capability information indicating at least one AIoT data uplink (UL) method supported by a terminal device; receive, from an application function (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements; and transmit, to a base station, an AIoT session request message including capability information of the terminal device and AIoT service requirements.

[0008] In a fourth aspect, there is provided a method comprising: receiving, from an Ambient Internet of Things (AIoT) Function (AIoTF), an AIoT session request message including capability information of a terminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data uplink (UL) method supported by the terminal device; selecting, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method; and transmitting the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

[0009] In a fifth aspect, there is provided a method comprising: receiving, from an Ambient Internet of Things (AIoT) Function (AIoTF), an AIoT session request message including capability information of a terminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data uplink (UL) method supported by the terminal device; selecting, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method; and transmitting the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

[0010] In a sixth aspect, there is provided a method obtaining capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by a terminal device; receiving, from an application function (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements; and transmitting, to a base station, an AIoT session request message including capability information of the terminal device and AIoT service requirements.

[0011] In a seventh aspect, there is provided an apparatus comprising: means for transmitting capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by the terminal device; means for receiving, from a base station, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method; and means for transmitting, to an AIoT Function (AIoTF), AIoT data using the AIoT data UL method indicated by the AIoT session request message.

[0012] In an eighth aspect, there is provided an apparatus comprising: means for receiving, from an Ambient Internet of Things (AIoT) Function (AIoTF), an AIoT session request message including capability information of a terminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data uplink (UL) method supported by the terminal device; means for selecting, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method; and means for transmitting the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

[0013] In an ninth aspect, there is provided an apparatus comprising: means for obtaining capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by a terminal device; means for receiving, from an applicationfunction (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements; and means for transmitting, to a base station, an AIoT session request message including capability information of the terminal device and AIoT service requirements.

[0014] In a tenth aspect, there is provided a computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least: transmitting capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by the terminal device; receiving, from a base station, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method; and transmitting, to an AIoT Function (AIoTF), AIoT data using the AIoT data UL method indicated by the AIoT session request message.

[0015] In a eleventh aspect, there is provided a computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least: receiving, from an Ambient Internet of Things (AIoT) Function (AIoTF), an AIoT session request message including capability information of a terminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data uplink (UL) method supported by the terminal device; selecting, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method; and transmitting the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

[0016] In a twelfth aspect, there is provided a computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least: obtaining capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by a terminal device; receiving, from an application function (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements; and transmitting, to a base station, an AIoT session request message including capability information of the terminal device and AIoT service requirements.

[0017] In a thirteenth aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: transmitting capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL)method supported by the terminal device; receiving, from a base station, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method; and transmitting, to an AIoT Function (AIoTF), AIoT data using the AIoT data UL method indicated by the AIoT session request message.

[0018] In a fourteenth aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: receiving, from an Ambient Internet of Things (AIoT) Function (AIoTF), an AIoT session request message including capability information of a terminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data uplink (UL) method supported by the terminal device; selecting, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method; and transmitting the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

[0019] In a fifteenth aspect, there is provided a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to: obtaining capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by a terminal device; receiving, from an application function (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements; and transmitting, to a base station, an AIoT session request message including capability information of the terminal device and AIoT service requirements.

[0020] In a sixteenth aspect, there is provided a terminal device. The terminal device comprises: a transmitting circuitry configured to transmit capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by the terminal device; a receiving circuitry configured to receive, from a base station, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method, wherein the transmitting circuitry is further configured to transmit, to an AIoT Function (AIoTF), AIoT data using the AIoT data UL method indicated by the AIoT session request message.

[0021] In a seventeenth aspect, there is provided a base station. The base station comprises: an receiving circuitry configured to receive, from an Ambient Internet of Things (AIoT) Function (AIoTF), an AIoT session request message including capability information of aterminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data uplink (UL) method supported by the terminal device; a selection circuitry configured to select, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method; and a transmitting circuitry configured to transmit the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

[0022] In an eighteenth aspect, there is provided a network device comprising an Ambient Internet of Things (AIoT) Function (AIoTF). The network device comprises: a obtaining circuitry configured to obtain capability information indicating at least one AIoT data uplink (UL) method supported by a terminal device; a receiving circuitry configured to receive, from an application function (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements; and a transmitting circuitry configured to transmit, to a base station, an AIoT session request message including capability information of the terminal device and AIoT service requirements.

[0023] It is to be understood that the summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Some embodiments will now be described with reference to the accompanying drawings, in which:

[0025] FIG. 1 illustrates a topology where an AIoT device directly and bidirectionally communicates with a base station;

[0026] FIG. 2 illustrates a topology where an AIoT device communicates bidirectionally with an intermediate node between the device and a base station;

[0027] FIG. 3 illustrates an example network environment in which some embodiments of the present disclosure can be implemented;

[0028] FIG. 4 illustrates an example of a process flow in accordance with some embodiments of the present disclosure;

[0029] FIG. 5 illustrates an example of another process flow in accordance with some embodiments of the present disclosure;

[0030] FIG. 6 illustrates an example of a Non-Access Stratum (NAS) procedure to transfer AIoT data in accordance with some embodiments of the present disclosure;

[0031] FIG. 7 illustrates an example flowchart of a method implemented at a terminal device according to embodiments of the present disclosure;

[0032] FIG. 8 illustrates an example flowchart of a method implemented at a network device comprising an AIoTF according to embodiments of the present disclosure;

[0033] FIG. 9 illustrates an example flowchart of a method implemented at a network device comprising an Access and Mobility management Function (AMF) according to embodiments of the present disclosure;

[0034] FIG. 10 illustrates an example flowchart of a method implemented at a terminal device according to embodiments of the present disclosure;

[0035] FIG. 11 illustrates an example flowchart of a method implemented at a base station according to embodiments of the present disclosure;

[0036] FIG. 12 illustrates an example flowchart of a method implemented at a network device comprising an AIoTF according to embodiments of the present disclosure;

[0037] FIG. 13 illustrates an example simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure; and

[0038] FIG. 14 illustrates an example block diagram of an example computer readable medium in accordance with some embodiments of the present disclosure.

[0039] Throughout the drawings, the same or similar reference numerals represent the same or similar elements.DETAILED DESCRIPTION

[0040] Principles of the present disclosure will now be described with reference to some embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Thedisclosure described herein can be implemented in various manners other than the ones described below.

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

[0042] References in the present disclosure 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.

[0043] 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 embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0044] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of 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. As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0045] As used in this application, the term “circuitry” may refer to one or more or all of the following:(a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and(b) combinations of hardware circuits and software, such as (as applicable):(i) a combination of analog and / or digital hardware circuit(s) with software / firmware and(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and(c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor s), that requires software (for example, firmware) for operation, but the software may not be present when it is not needed for operation.

[0046] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0047] As used herein, the term “network”, “communication network” or “data network” refers to a network following any suitable communication standards, such as long term evolution (LTE), LTE-advanced (LTE-A), wideband code division multiple access (WCDMA), high-speed packet access (HSPA), wireless fidelity (Wi-Fi), narrow band Internet of things (NB-IoT), satellite, enhanced machine-type communication (eMTC), nonterrestrial communication, terrestrial communication, and so on. Furthermore, the communications between a terminal device and a network device / element in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the fourth generation (4G), 4.5G, the fifth generation (5G), the sixth generation (6G), new radio (NR), IEEE 802.11 communication protocols, and / or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will ofcourse also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

[0048] As used herein, the term “network device” may refer to a device comprising or performing a core network function. For instance, a network device may refer to a device comprising or performing network functions, including but not limited to, Access and Mobility Management Function (AMF), Session Management Function (SMF), Application Function (AF), Network Exposure Function (NEF), AIoF Function (AIoTF), Policy Control Function (PCF), Unified Data Management / Repository (UDM / UDR), Traffic Steering Function (TSF), among others things.

[0049] It is understood that references in the above to various network functions (e.g., to an AMF, an SMF, TNF etc.) may be implemented by apparatus (e.g., network apparatus) that performs at least some of the functionality associated with those network functions. Further, an apparatus configured to implement a network function may further be configured to implement a virtual network function instance of that network function.

[0050] In some embodiments, the apparatus may be or comprise a network function, such as an AF, NEF, UDM / UDR, AMF, etc. In the present disclosure, an apparatus being / comprising a network function refers to an apparatus / device configured to provide / perform at least part of functionalities of that network function.

[0051] The term “network device” may refer also to a network node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP) or a transmission and reception point (TRP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also referred to as a gNB), a remote radio unit (RRU), a radio header (RH), a remote radio head (RRH), a WiFi (Wireless Fidelity) device, a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology. In the following description, the terms “network device”, “AP device”, “AP” and “access point” may be used interchangeably.

[0052] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS), a station (STA) or station device, or anaccess terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (for example, remote surgery), an industrial device and applications (for example, a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. In the following description, the terms “station”, “station device”, “STA”, “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably.

[0053] The term “transceiver” may refer to any device that may be coupled to one or more antennas or antenna ports to wirelessly transmit and / or receive communication signals. The antennas or antenna ports may be the same or different types. The antennas or antenna ports may be located in different positions of an apparatus. One or more transceivers allow the apparatus to communicate with other devices that may be wired and / or wireless. The one or more transceivers may include processors, controllers, radios, sockets, plugs, buffers, or the like circuits to form one or more communication channels to one or more radio frequency units. The one or more transceivers may be integrated in an apparatus or a system, for example a cellular communication apparatus or system, a satellite communication apparatus or system, a WLAN system, or a short ranging system for example Bluetooth system.

[0054] Ambient Internet of Things (AIoT) refers to loT devices powered by energy harvesting, making them either battery-less or equipped with limited energy storage capabilities (e.g., using a capacitor). AIoT is necessary to complement existing loT technologies like NB (Narrowband Internet of Things)-IoT / Emtc (enhanced Machine Type Communication) and NR RedCap defined by 3GPP. It aims to cover additional use cases that demand more cost-effective, power-efficient, and particularly battery-less functionalities.

[0055] The number of loT devices is anticipated to be enormous in the future and the lifespan of them should be very long like more than 5 years. Charging or regularly replacing batteries for all these loT devices would be impractical, considering the significant consumption of manpower and materials.

[0056] Some use cases leveraging AIoT devices include: ID tags (replacing radio frequency identification, RFID, with a wider range), sensors (e.g., temperature, humidity, etc.), healthcare devices (monitoring personal medical information), logistics (tracking objects), and others.

[0057] Components of the system architecture for AIoT at least include: an activator (or illuminator), AIoT devices (radios), and a reader (or receiver). The activator sends an activation signal to wake up passive radios (AIoT devices) by providing energy that allows AIoT devices to transmit their messages. The AIoT devices are loT devices powered by energy harvesting. The reader listens and detects the passive radio signals. The reader may or may not be collocated with the activator. By incorporating AIoT technology into the loT ecosystem, various use cases can be addressed while reducing the dependency on conventional power sources.

[0058] In some embodiments, several topologies for AIoT technology are supported, including Topology 1 and Topology 2 separately shown in FIGS. 1 and 2. FIG. 1 illustrates the Topology 1 where an AIoT device directly and bidirectionally communicates with a base station (BS). In FIG. 1, the communication between the BS and the AIoT device includes AIoT data and / or signalling. The link between BS and the AIoT device in downlink is referred to as R2D. The link between AIoT device and the BS is referred to as D2R.

[0059] FIG. 2 illustrates Topology 2 where an AIoT device communicates bidirectionally with an intermediate node between the device and a base station. In this topology, the intermediate node can be a relay, Integrated Access and Backhaul (IAB) node, UE, repeater, etc. which is capable of supporting AIoT. The intermediate node transfers AIoT data and / or signalling between the BS and the AIoT device. The link between intermediate node and the AIoT device in downlink is referred to as R2D. The link between AIoT device and the intermediate node is referred to as D2R.

[0060] FIG. 3 illustrates an example network environment in which some embodiments of the present disclosure can be implemented. As shown in FIG. 3, the communication network 300 may include a UE 310, a BS 320 (e.g., a gNB, which can be interchangeably used in thisdisclosure), AIoT device(s) 380, and a core network including an Access and Management Function (AMF) 330, an AIoT Function (AIoTF) 340, and an Application Function (AF). The core network may include other network functions (NFs) which are not shown for brevity.

[0061] The UE 310 may be within coverage of the BS 320, for example, the UE 310 can communicate with the BS 320 over Uu interface. In some cases, a location of the BS 320 may be outdoor or indoor, a location of the UE 310 may be outdoor or indoor, and a location of the AIoT device(s) 380 may be outdoor or indoor. The communication network 300 may be used in use cases such as inventory or command.

[0062] As shown in FIG. 3, the UE 310 may act as an intermediate node for (bidirectional) communication between the AIoT device 380 and the BS 320. In this disclosure, the UE 310 may also be interchangeably referred as an intermediate node (I-node). It is to be understood that loT enabled devices other than UE, such as a relay, IAB node, repeater, etc., may also act as the I-node. It is to be understood that the numbers of UEs or AIoT devices or CN entities shown in FIG. 3 are only for ease of illustration. The communication network 300 may include any suitable numbers of devices.

[0063] As illustrated, the UE 310 may bidirectionally communicate with the AMF 330 over N1 interface, a logical interface between the UE 310 and the AMF 330. The N1 interface may carry Non-Access Stratum (NAS) messages between the UE 310 and the AMF 330. Additionally or alternatively, the UE may bidirectionally communicates with the AMF 330 via the BS 320 over Uu interface and N2 interface.

[0064] In Topology 2, the UE 310 act acts as an intermediate node, between the network and the AIoT device. The AIoT data from the AIoT devices are transferred by the UE to the network. For instance, the AF 350 may transmit an AIoT service request associated with the UE 310 to the AIoTF 340, which then forwards the request targeting the UE 310 to the AMF 330. The UE 310 may receive the request from the AMF 330 over N1 interface, or over N2 and Uu interfaces via BS 320. In response to the request, the UE 310, as a UE reader, collects AIoT data from the AIoT device 380 and forwards the AIoT data to the AF 350 in UL transmission.

[0065] There are multiple methods that the UE forwards data received from the AIoT devices to the network, including, for example, over user plane, over control plane where the UE reader in RRC CONNECT state (e.g., UL NAS), and over control plane where theUE in RRC INACTIVE state (i.e., Small Data Transfer (SDT)). Therefore, an optimal method needs be deployed between the UE and the network to transfer the data from the AIoT devices to the network. This depends on various factors and for each of the factors, the advantages and disadvantages are described below. In this disclosure, a method for UE to forward AIoT data to network can be referred as an AIoT data forwarding method or an AIoT data UL method, which could be interchangeably used.

[0066] Regarding latency requirements, the user plane method is suitable for applications requiring low latency and high data rates, as it allows for direct data transfer. The UL NAS method typically has higher latency compared to the user plane method, but might be adequate for less time-sensitive data. The SDT method is designed for small data bursts and can provide lower latency without full Radio Resource Control (RRC) connection setup, making it efficient for small, infrequent data transmissions.

[0067] Regarding data volume, the user plane method might be ideal for large data volumes since it supports higher throughput. The UL NAS method is more appropriate for moderate data volumes, where full control signaling is acceptable. The SDT method is best for small data payloads, as it avoids the overhead of establishing and maintaining an RRC connection.

[0068] Regarding energy efficiency, the user plane method generally consumes more power due to continuous connection and data transfer. The UL NAS method might offer a balance between power consumption and connectivity requirements. The SDT method is optimized for low power consumption, making it suitable for battery-operated loT devices with small data needs.

[0069] Regarding network load and efficiency, the user plane method can increase network load due to continuous connections but is efficient for large data transfers. The UL NAS method introduces additional signaling overhead, which can affect network efficiency. The SDT reduces signaling overhead and network load, beneficial for networks with many small, sporadic data transmissions.

[0070] Regarding QoS (Quality of Service) requirements, the user plane method Offers better support for QoS management, ensuring data prioritization and reliability. The UL NAS method may not provide the same level of QoS granularity as the user plane method but can still ensure reliable delivery. The SDT method has limited QoS capabilities but can be sufficient for non-critical small data transmissions.

[0071] Regarding application specific needs, the user plane method is suitable for applications needing continuous and high-throughput data exchange, such as streaming orreal-time analytics. The UL NAS method is appropriate for less frequent but still critical data communications. The SDT method may be ideal for applications with intermittent small data transmissions, such as sensor readings or status updates.

[0072] Hence the network must employ the right mechanism to transfer AIoT data from the devices to the network depending on the requirements. But there is no means currently to identify the UE capabilities in terms of AIoT data transfer methods supported and for the network to decide the optimal transfer method.

[0073] In a nutshell, the present disclosure provides means for the UE to indicate the supported AIoT data transfer methods, means for the AF to indicate the AIoT data transfer requirements to AIoTF, means for the AIoTF to select a AIoT transfer method based on UE’s supported methods and AF’s requirement, a means for the core network entities to indicate the selected AIoT transfer method. Alternatively, the present disclosure provides means for the core network to indicate the guidance, requirements from the AF to the BS (e.g, gNB), and means for the BS to select a suitable method for AIoT data transfer.

[0074] FIG. 4 illustrates an example of a process flow 400 in accordance with some embodiments of the present disclosure. For ease of understanding, the process flow 400 will be described with reference to FIGS. 2 and 3, It would be appreciated that although the process flow 400 has been described referring to the communication network 300 of FIG. 3 and the topology of FIG. 2, the process flow 400 may be likewise applied to other similar communication scenarios.

[0075] The process flow 400 involves AIoT device(s) 380, a UE 310, a gNB 320, an AMF 330, an AIoTF 340, and an AF 350. The UE 310 is configured to act as an intermediate node between the AIoT device 380 and the network (RAN and core network). The UE 310 may transmit downlink signals such as AIoT data request to AIoT device 380 and receive uplink signals including AIoT data from the wireless device 330. In some embodiments, the AIoTF 340 may communicate with and / or acquire information / messages / data / services from other network entities via (a network device comprising) network exposure function (NEF).

[0076] As shown in FIG. 4, at step 401, the UE 310 performs UE registration with 5GC. When the UE 310 registers with the 5GC, it provides its capability information, indicating which AIoT data forwarding (UL) methods it supports. For example, the capability information of the UE 310 may be provided to / shared with at least one of the NEF, the AMF 330, the AIoTF 340. The supported AIoT data forwarding method may include one or moreof AIoT data transfer over user plane (UP), AIoT data transfer via uplink Non-Access Stratum (UL NAS), and / or AIoT data transfer via Small Data Transfer (SDT).

[0077] The UE 310 may transmit the capability information to the core network, e.g. the AMF 330. In some embodiments, the AMF 330 may receive the capability information during the UE registration and store the capability information or forward the capability information to one or more network functions (NFs). For example, the capability information can be stored at the AMF 330 or NF(s) such as PCF, UDM / UDR, and others. By doing this, the AIoTF 340 may retrieve the capability information from these NF(s) (via the NEF).

[0078] At step 402, the AF 350 transmits an AIoT service (e.g., inventory or command) request message to the 5GC. This message may contain the AIoT service requirements such as maximum latency, reliability level, energy level etc.

[0079] At step 403, the AIoTF 340 may select the AIoT data forwarding method to be used by the UE 310 based on the AIoT service requirements given in step 402 and the UE capability information indicated in step 401. In some embodiments, the AIoTF 340 may obtain the capability information locally if UE capability has been stored in the AIoTF 340 during UE registration. Alternatively, the AIoTF 340 may retrieve the capability information from other NFs storing the UE capability, for example, the AMF 330, the PCF or the UDM / UDR. The AIoTF 340 may select one of the supported AIoT forwarding method which satisfies the AIoT service requirements as an optimal method for the UE 310 to use.

[0080] At step 404a, the AIoTF 340 may send an AIoT session request message targeting the UE 310 to the gNB 320 over N2 interface. The AIoT session request message may include an indication of the AIoT data UL method selected from the at least one AIoT data UL method.

[0081] In some embodiments, the gNB 320 may forward the AIoT session request message to the UE 310, such that the UE 310 can know which one of the supported methods will be used for AIoT data forwarding.

[0082] In some embodiment, upon / when / after / if receiving the AIoT session request message from the AIoTF 340, the AMF 330 may create a new request including the indication of AIoT data UL method and send the new request to the gNB 320 via N2 interface. From the perspective of the UE 310, it receives the message from the AMF 330.

[0083] In some embodiments, at step 404b, the AIoTF 340 may send an AIoT session request message to the UE 310 over N1 interface, indicating the selected AIoT data forwarding method. In some embodiments, upon / when / after / if receiving the AIoT session request message from the AIoTF 340, the AMF 330 may encapsulate the message in an N1 container and send it to the UE 310. In this case, the message originator is AIoTF 340 and the message container is transparent to the AMF 340. From the perspective of the UE 310, it receives the message from the AIoTF 340.

[0084] At step 406, the UE 310 performs AIoT communication with the AIoT device 380 to collect AIoT data.

[0085] At step 407a, when / if the UP method is selected, the UE 310 may establish a Packet Data Unit (PDU) session targeting to the AIoTF 340 or directly Data Network (DN), using user plane mechanism to forward the AIoT data.

[0086] At 407b, when / if the UL NAS method is selected, the UE 310 may forward the AIoT data to the AMF 330, which then delivers the message to the AIoTF 340. In some embodiments, the UE 301 may transmit N1 message including AIoT data (using N1 container) to the AMF 330 for forwarding to the AIoTF 340 and to the AF 350.

[0087] At 407c, when / if the SDT method is selected, the UE 310 may forward the AIoT data to the gNB 320 in the RRC RESUME request message. The gNB 320 then further forwards the AIoT data in the message to the AIoTF 340 over the AMF 330, and further to the AF 350. The AMF 330 may receive the AIoT data via N2 interface and forward the received AIoT data to the AIoTF 340 identified with the AIoT session ID in the N2 message.

[0088] FIG. 5 illustrates an example of a process flow 500 in accordance with some embodiments of the present disclosure. For ease of understanding, the process flow 500 will be described with reference to FIGS. 2 and 3, It would be appreciated that although the process flow 500 has been described referring to the communication network 300 of FIG. 3 and the topology of FIG. 2, the process flow 500 may be likewise applied to other similar communication scenarios. In general, the process flow 500 differs from the process flow 400 in that the gNB 320, instead of the AIoTF 340, determines which forwarding method is to be used by the UE 310 for AIoT data.

[0089] At step 501, the UE 310 performs UE registration with 5GC. This step is similar as the step 401 in FIG. 4. After the UE registration, the capability information indicating AIoTforwarding method(s) supported by the UE 310 is stored in NF(s) of the core network (e.g. UDR / UDM and / or PCF).

[0090] At step 502, the AF 350 transmits an AIoT service (e.g., inventory or command) request message to the 5GC. The request may contain AIoT service requirements such as maximum latency, reliability level, energy level etc. This step is similar as the step 402 in FIG. 4.

[0091] At step 503, as an alternative to step 403, the AIoTF 340 may not select the AIoT data forwarding method, but only provide necessary information, including the UE capability and the AIoT service requirements to the gNB 320. In some embodiments, the AIoTF 340 transmits an AIoT session request message including the capability information and the AIoT service requirements to the AMF 320, which then forwards the AIoT session request message to the gNB 320 over N2 interface. The AIoTF 340 may obtain the capability information similarly as described with reference to FIG. 4.

[0092] At step 504, the gNB 320 selects the AIoT data forwarding method to be used by the UE 310 based on the information given in step 503.

[0093] At step 505, the gNB 320 may send an AIoT session request message to the UE 310, indicating the selected AIoT data forwarding method. The AIoT session request message may include an indication of the selected AIoT data forwarding method.

[0094] At step 506, the UE 310 performs AIoT communication(s) with the AIoT device 380 to collect AIoT data.

[0095] At step 507a, when / if the UP method is selected, the UE 310 may establish a Packet Data Unit (PDU) session targeting to the AIoTF 340 or directly Data Network (DN), using user plane mechanism to forward the AIoT data.

[0096] At 507b, when / if the UL NAS method is selected, the UE 310 may forward the AIoT data to the AMF 330, which then delivers the message to the AIoTF 340. In some embodiments, the UE 301 may transmit N1 message including AIoT data (using N1 container) to the AMF 330 for forwarding to the AIoTF 340 and to the AF 350.

[0097] At 507c, when / if the SDT method is selected, the UE 310 may forward the AIoT data to the gNB 320 in the RRC RESUME request message. The gNB 320 then further forwards the AIoT data in the message to the AIoTF 340 over the AMF 330, and further to the AF 350.

[0098] FIG. 6 illustrates an example of a Non-Access Stratum (NAS) procedure 600 to transfer AIoT data in accordance with some embodiments of the present disclosure. The procedure 600 is applicable when the UL NAS method is selected. In FIG. 6, the steps 601, 602 and 603 are similar as steps 401, 402 and 403 described in FIG. 4 or steps 501, 502 and 503 in FIG. 5.

[0099] At step 604, the UE 310 in RRC CONNECTED state decides to forward AIoT data over NAS according to the guidance information by network.

[0100] At step 605, the UE 310 transmits a UL NAS TRANSPORT message including the AIoT data to the AMF 330, which then at step 606, forwarding the received AIoT data to the AIoTF 340 and to the AF 350.

[0101] In some embodiments, the UL NAS TRANSPORT message is re-used by the UE 310 to forward the AIoT data to the AMF 330. To achieve this, a (new) value for the payload container type parameter in the message is defined as “AIoT data”. When / if the AMF 330 receives the UL NAS TRANSPORT message and the payload container type is set to “AIoT data”, the AMF 330 forwards / transmits / sends the AIoT data to the AIoTF 340 identified with the AIoT session ID in the UL NAS TRANSPORT message.

[0102] FIG. 7 illustrates a flowchart of an example method 700 implemented at a terminal device (such as UE) in accordance with some other embodiments of the present disclosure. For ease of understanding, the method 700 will be described from the perspective of the UE 310 with reference to FIG. 4.

[0103] At block 710, the terminal device transmits capability information indicating at least one AIoT data UL method supported by the terminal device. For example, the capability information may be transmitted to / shared with core network, such as AMF, NEF, UDR, UDM, PCF, AIoTF, . . . , etc. At block 720, the terminal device receives, from an AMF or an AIoTF, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method. At block 730, the terminal device transmits, to the AIoTF, AIoT data using / based on the AIoT data UL method indicated by the AIoT session request message.

[0104] In some embodiments, to receive, the AIoT session request message including the indication of the AIoT data UL method selected from the at least one AIoT data UL method, the terminal device may receive, from the AMF, the AIoT session request message via a network node.

[0105] In some embodiments, to receive, the AIoT session request message including the indication of the AIoT data UL method selected from the at least one AIoT data UL method, the terminal device may receive, from the AIoTF, the AIoT session request message via N1 interface.

[0106] In some embodiments, the at least one AIoT data UL method comprises one or more of: AIoT data transfer over user plane; AIoT data transfer via UL NAS; or AIoT data transfer via SDT.

[0107] In some embodiments, the indicated AIoT data UL method is AIoT data transfer via UL NAS, and the terminal device may transmit a UL NAS TRANSPORT message including the AIoT data to the AMF for forwarding the AIoT data to the AIoTF.

[0108] In some embodiments, a payload container type parameter in the UL NAS TRANSPORT message is set to an AIoT data type.

[0109] In some embodiments, the indicated AIoT data UL method is AIoT data transfer via SDT, and the terminal device may transmit a RRC RESUME request message including the AIoT data to a network node for forwarding to the AIoTF over the AMF.

[0110] In some embodiments, the capability information is transmitted during registration with a core network.

[0111] In some embodiments, the terminal device comprises a UE reader as an intermediate node between an AIoT device and a network.

[0112] FIG. 8 illustrates a flowchart of an example method 800 implemented at a network device comprising an AIoTF in accordance with some embodiments of the present disclosure. For ease of understanding, the method 800 will be described from the perspective of the AIoTF 340 with reference to FIG. 4.

[0113] At block 810, the network device obtains capability information indicating at least one AIoT data UL method supported by the terminal device. At block 820, the network device receives, from an application function (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements. At block 830, the network device selects, based on the AIoT service requirements and terminal device capability information, an AIoT data UL method from the at least one AIoT data UL method. At block 840, the network device transmits, to a network node serving the terminal device, an AIoT session request message associatedwith the terminal device, wherein the AIoT session request message includes an indication of an AIoT data UL method selected from the at least one AIoT data UL method. At block 850, the network device transmits, to the terminal device, the AIoT session request message including the indication of the AIoT data UL method selected from the at least one AIoT data UL method.

[0114] In some embodiments, the AIoT session request message including the indication of the selected AIoT data UL method is transmitted to the terminal device and the network node via an AMF.

[0115] In some embodiments, the at least one AIoT data UL method comprise one or more of: AIoT data transfer over user plane; AIoT data transfer via UL NAS; or AIoT data transfer via SDT.

[0116] In some embodiments, the AIoT service requirements include at least one of: a maximum latency; a reliability level; or an energy level.

[0117] FIG. 9 illustrates a flowchart of an example method 900 implemented at a network device comprising an AMF in accordance with some embodiments of the present disclosure. For ease of understanding, the method 900 will be described from the perspective of the AMF 330 with reference to FIG. 4.

[0118] At block 910, the network device receives, from an Ambient Internet of Things (AIoT) function (AIoTF), an AIoT session request including an indication of an AIoT data UL method selected from at least one AIoT data UL method supported by a terminal device. At block 920, the network device forwards the AIoT session request message including the indication of the selected AIoT data UL method to a network node serving the terminal device. At block 930, the network device forwards / transmits the AIoT session request message including the indication of the selected AIoT data UL method to the terminal device.

[0119] In some embodiments, the network device may receive, during registration of the terminal device, capability information indicating at least one AIoT data UL method supported by the terminal device; and store the capability information or forward the capability information to one or more network functions.

[0120] In some embodiments, to forward the AIoT session request message including the indication of the selected AIoT data UL method to the network node, the network device may transmit the AIoT session request message to the network node over N2 interface.

[0121] In some embodiments, to forward the AIoT session request message including the indication of the selected AIoT data UL method to the terminal device, the network device may transmit the AIoT session request message to the terminal device over N1 interface.

[0122] In some embodiments, the at least one AIoT data UL method comprises one or more of: AIoT data transfer over user plane; AIoT data transfer via UL NAS; or AIoT data transfer via SDT.

[0123] In some embodiments, the network device may receive a UL NAS TRANSPORT message including AIoT data from the terminal device via N1 interface, wherein a payload container type parameter in the UL NAS TRANSPORT message is set to an AIoT data type.

[0124] In some embodiments, the network device may receive, from a network node, a message including AIoT data over N2 interface.

[0125] In some embodiments, the network device may forward / transmit the AIoT data to the AIoTF identified with an AIoT session ID in the UL NAS TRANSPORT message or the message received over N2 interface.

[0126] In some embodiments, an apparatus capable of performing the method 700 (for example, a terminal device) may comprise means for performing the respective steps of the method 700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[0127] In some embodiments, the apparatus comprises: means for transmitting capability information indicating at least one AIoT data UL method supported by the terminal device; means for receiving, from an AMF or an AIoTF, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method; and means for transmitting, to the AIoTF, AIoT data using the AIoT data UL method indicated by the AIoT session request message.

[0128] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 700. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[0129] In some embodiments, an apparatus capable of performing the method 800 (for example, a network device) may comprise may comprise means for performing therespective steps of the method 800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[0130] In some embodiments, the apparatus comprises: means for obtaining, from a terminal device, capability information indicating at least one AIoT data UL method supported by the terminal device; means for receiving, from an AF, an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements; means for selecting, based on the AIoT service requirements and terminal device capability information, an AIoT data UL method from the at least one AIoT data UL method; means for transmitting, to a network node serving the terminal device, an AIoT session request message associated with the terminal device, wherein the AIoT session request message includes an indication of an AIoT data UL method selected from the at least one AIoT data UL method; and means for transmitting, to the terminal device, the AIoT session request message including the indication of the AIoT data UL method selected from the at least one AIoT data UL method.

[0131] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 800. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[0132] In some embodiments, an apparatus capable of performing the method 900 (for example, a network device) may comprise may comprise means for performing the respective steps of the method 900. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[0133] In some embodiments, the apparatus comprises: means for receiving, from an AIoTF, an AIoT session request message including an indication of an AIoT data UL method selected from at least one AIoT data UL method supported by a terminal device; means for forwarding the AIoT session request message including the indication of the selected AIoT data UL method to a network node serving the terminal device; and means for forwarding the AIoT session request message including the indication of the selected AIoT data UL method to the terminal device.

[0134] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 900. In some embodiments, the means comprisesat least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[0135] FIG. 10 illustrates a flowchart of an example method 100 implemented at a terminal device (such as UE 310 in FIG. 3) in accordance with some other embodiments of the present disclosure. For ease of understanding, the method 700 will be described from the perspective of the UE 310 with reference to FIG. 5.

[0136] At block 1010, the terminal device transmit capability information indicating at least one AIoT data UL method supported by the terminal device. At block 1020, the terminal device receives, from a base station, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method. At block 1030, the terminal device transmits, to an AIoT function (AIoTF), AIoT data using the AIoT data UL method indicated by the AIoT session request message.

[0137] In some embodiments, the at least one AIoT data UL method comprises one or more of AIoT data transfer over user plane; AIoT data transfer via UL NAS; or AIoT data transfer via SDT.

[0138] In some embodiments, the indicated AIoT data UL method is AIoT data transfer via UL NAS, and the terminal device may transmit a UL NAS TRANSPORT message including the AIoT data to the AMF for forwarding the AIoT data to the AIoTF.

[0139] In some embodiments, a payload container type parameter in the UL NAS TRANSPORT message is set to an AIoT data type.

[0140] In some embodiments, the indicated AIoT data UL method is AIoT data transfer via SDT, and the terminal device may transmit a Radio Resource Control (RRC) RESUME request message including the AIoT data to the base station for forwarding to the AIoTF over an AMF.

[0141] In some embodiments, the capability information is transmitted during a registration procedure with a core network.

[0142] In some embodiments, the terminal device comprises a UE reader as an intermediate node between an AIoT device and a network.

[0143] FIG. 11 illustrates a flowchart of an example method 1100 implemented at a base station (e.g. a gNB, RAN, NG-RAN) in accordance with some embodiments of the presentdisclosure. For ease of understanding, the method 1100 will be described from the perspective of the gNB 330 with reference to FIG. 5.

[0144] At block 1110, the base station receives, from an Ambient Internet of Things (AIoT) function (AIoTF), an AIoT session request message including capability information of a terminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data UL method supported by the terminal device. At block 1120, the base station selects, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method. At block 1130, the base station transmits the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

[0145] In some embodiments, the at least one AIoT data UL method comprises one or more of: AIoT data transfer over user plane; AIoT data transfer via UL NAS; or AIoT data transfer via SDT.

[0146] In some embodiments, the AIoT service requirements include at least one of: a maximum latency; a reliability level; or an energy level.

[0147] In some embodiments, the base station may receive, from the terminal device, a RRC RESUME request message including AIoT data; and forward the AIoT data to the AIoTF over an AMF.

[0148] FIG. 12 illustrates a flowchart of an example method 1200 implemented at a network device comprising an AIoTF in accordance with some embodiments of the present disclosure. For ease of understanding, the method 1200 will be described from the perspective of the AIoTF 340 with reference to FIG. 5.

[0149] At block 1210, the network device obtains capability information indicating at least one AIoT data UL method supported by a terminal device. At block 1220, the network device receives, from an application function (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements. At block 1230, the network device transmits, to a base station, an AIoT session request message including capability information of the terminal device and AIoT service requirements.

[0150] In some embodiments, the AIoT session request message is forwarded to the base station via the AMF.

[0151] In some embodiments, the at least one AIoT data UL method comprises one or more of: AIoT data transfer over user plane; AIoT data transfer via UL NAS; or AIoT data transfer via SDT.

[0152] In some embodiments, the AIoT service requirements include at least one of: a maximum latency; a reliability level; or an energy level.

[0153] In some embodiments, an apparatus capable of performing the method 1000 (for example, a terminal device) may comprise means for performing the respective steps of the method 1000. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[0154] In some embodiments, the apparatus comprises: means for transmitting capability information indicating at least one AIoT data UL method supported by the terminal device; means for receiving, from a base station, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method; and means for transmitting, to an AIoTF, AIoT data using the AIoT data UL method indicated by the AIoT session request message.

[0155] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1000. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[0156] In some embodiments, an apparatus capable of performing the method 1100 (for example, a base station) may comprise may comprise means for performing the respective steps of the method 1100. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[0157] In some embodiments, the apparatus comprises: means for receiving, from an AIoTF, an AIoT session request message including capability information of a terminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data UL method supported by the terminal device; means for selecting, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method; and means for transmitting the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

[0158] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1100. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[0159] In some embodiments, an apparatus capable of performing the method 1200 (for example, a network device) may comprise may comprise means for performing the respective steps of the method 1200. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

[0160] In some embodiments, the apparatus comprises: means for obtaining capability information indicating at least one AIoT data UL method supported by a terminal device; means for receiving, from an application function (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements; and means for transmitting, to a base station, an AIoT session request message including capability information of the terminal device and AIoT service requirements.

[0161] In some embodiments, the apparatus further comprises means for performing other steps in some embodiments of the method 1200. In some embodiments, the means comprises at least one processor and at least one memory including computer program code, the at least one memory and computer program code configured to, with the at least one processor, cause the performance of the apparatus.

[0162] FIG. 13 illustrates a simplified block diagram of a device 1300 that is suitable for implementing some embodiments of the present disclosure. The device 1300 may be provided to implement a communication device, for example, the network devices, base stations, or the terminal devices as shown in FIGS. 3 to 6. As shown, the device 1300 includes one or more processors 1310, one or more memories 1320 coupled to the processor 1310, and one or more communication modules 1340 coupled to the processor 1310.

[0163] The communication module 1340 is for bidirectional communications. The communication module 1340 has at least one antenna to facilitate communication. The communication interface may represent any interface that is necessary for communication with other network elements.

[0164] The processor 1310 may be of any type suitable to the local technical network andmay include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1300 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

[0165] The memory 1320 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1324, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 1322 and other volatile memories that will not last in the power-down duration.

[0166] A computer program 1330 includes computer executable instructions that are executed by the associated processor 1310. The program 1330 may be stored in the ROM 1324. The processor 1310 may perform any suitable actions and processing by loading the program 1330 into the RAM 1322.

[0167] The embodiments of the present disclosure may be implemented by means of the program 1330 so that the device 1300 may perform any process of the disclosure as discussed with reference to FIGS. 7 to 12. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0168] In some embodiments, the program 1330 may be tangibly contained in a computer- readable medium which may be included in the device 1300 (such as in the memory 1320) or other storage devices that are accessible by the device 1300. The device 1300 may load the program 1330 from the computer-readable medium to the RAM 1322 for execution. The computer-readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.

[0169] FIG. 14 illustrates a block diagram of an example of a computer-readable medium 1400 in accordance with some embodiments of the present disclosure. The computer- readable medium 1400 has the program 1330 stored thereon. It is noted that although the computer-readable medium 1400 is depicted in form of CD or DVD in FIG. 14, the computer-readable medium 1400 may be in any other form suitable for carry or hold the program 1330.

[0170] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0171] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or methods 700 to 1200 as described above with reference to FIGS. 7 to 12. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

[0172] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

[0173] In the context of the present disclosure, the computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal,computer-readable medium, and the like.

[0174] The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer-readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0175] Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

[0176] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

WHAT IS CLAIMED IS:

1. A terminal device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: transmit capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by the terminal device; receive, from a base station, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method; and transmit, to an AIoT function (AIoTF), AIoT data using the AIoT data UL method indicated by the AIoT session request message.

2. The terminal device of claim 1, wherein the at least one AIoT data UL method comprises one or more of:AIoT data transfer over user plane;AIoT data transfer via uplink Non-Access Stratum (UL NAS); or AIoT data transfer via Small Data Transfer (SDT).

3. The terminal device of claim 2, wherein the indicated AIoT data UL method is AIoT data transfer via UL NAS, and the terminal device is caused to: transmit a UL NAS TRANSPORT message including the AIoT data to the AMF for forwarding the AIoT data to the AIoTF.

4. The terminal device of claim 3, wherein a payload container type parameter in the UL NAS TRANSPORT message is set to an AIoT data type.

5. The terminal device of claim 2, wherein the indicated AIoT data UL method is AIoT data transfer via SDT, and the terminal device is caused to: transmit a Radio Resource Control (RRC) RESUME request message including the AIoT data to the base station for forwarding to the AIoTF over an AMF.

6. The terminal device of any of claims 1 to 5, wherein the capability information is transmitted during a registration procedure with a core network.

7. The terminal device of any of claim 1 to 6, wherein the terminal device comprises a user equipment (UE) reader as an intermediate node between an AIoT device and a network.

8. A base station comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to: receive, from an Ambient Internet of Things (AIoT) function (AIoTF), an AIoT session request message including capability information of a terminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data uplink (UL) method supported by the terminal device; select, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method; and transmit the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

9. The base station of claim 8, wherein the at least one AIoT data UL method comprise one or more of:AIoT data transfer over user plane;AIoT data transfer via uplink Non-Access Stratum (UL NAS); orAIoT data transfer via Small Data Transfer (SDT).

10. The base station of claim 8 or 9, wherein the AIoT service requirements include at least one of: a maximum latency; a reliability level; or an energy level.

11. The base station of any of claims 8 to 10, wherein the base station is further caused to: receive, from the terminal device, a Radio Resource Control (RRC) RESUME request message including AIoT data; and forward the AIoT data to the AIoTF over an AMF.

12. A network device comprising an Ambient Internet of Things (AIoT) function (AIoTF), the network device comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to: obtain capability information indicating at least one AIoT data uplink (UL) method supported by a terminal device; receive, from an application function (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements; and transmit, to a base station, an AIoT session request message including capability information of the terminal device and AIoT service requirements.

13. The network device of claim 12, wherein the AIoT session request message is forwarded to the base station via the AMF.

14. The network device of claim 12 or 13, wherein the at least one AIoT data UL method comprises one or more of:AIoT data transfer over user plane;AIoT data transfer via uplink Non-Access Stratum (UL NAS); orAIoT data transfer via Small Data Transfer (SDT).

15. The network device of any of claim 12 to 14, wherein the AIoT service requirements include at least one of: a maximum latency; a reliability level; or an energy level.

16. A method comprising: transmitting capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by the terminal device; receiving, from a base station, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method; and transmitting, to an AIoT function (AIoTF), AIoT data using the AIoT data UL method indicated by the AIoT session request message.

17. A method comprising: receiving, from an Ambient Internet of Things (AIoT) function (AIoTF), an AIoT session request message including capability information of a terminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data uplink (UL) method supported by the terminal device; selecting, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method; and transmitting the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

18. A method comprising: obtaining capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by a terminal device; receiving, from an application function (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements; and transmitting, to a base station, an AIoT session request message including capability information of the terminal device and AIoT service requirements.

19. An apparatus comprising: means for transmitting capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by the terminal device;means for receiving, from a base station, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method; and means for transmitting, to an AIoT function (AIoTF), AIoT data using the AIoT data UL method indicated by the AIoT session request message.

20. An apparatus comprising: means for receiving, from an Ambient Internet of Things (AIoT) function (AIoTF), an AIoT session request message including capability information of a terminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data uplink (UL) method supported by the terminal device; means for selecting, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method; and means for transmitting the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

21. An apparatus comprising: means for obtaining capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by a terminal device; means for receiving, from an application function (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements; and means for transmitting, to a base station, an AIoT session request message including capability information of the terminal device and AIoT service requirements.

22. A computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least: transmitting capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by the terminal device; receiving, from a base station, an AIoT session request message including an indication of an AIoT data UL method selected from the at least one AIoT data UL method; andtransmitting, to an AIoT function (AIoTF), AIoT data using the AIoT data UL method indicated by the AIoT session request message.

23. A computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least: receiving, from an Ambient Internet of Things (AIoT) function (AIoTF), an AIoT session request message including capability information of a terminal device and AIoT service requirements, wherein the capability information indicates at least one AIoT data uplink (UL) method supported by the terminal device; selecting, based on the AIoT service requirements, an AIoT data UL method from the at least one AIoT data UL method; and transmitting the AIoT session request message including an indication of the selected AIoT data UL method to the terminal device.

24. A computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least: obtaining capability information indicating at least one Ambient Internet of Things (AIoT) data uplink (UL) method supported by a terminal device; receiving, from an application function (AF), an AIoT service request message associated with the terminal device, wherein the AIoT service request message includes AIoT service requirements; and transmitting, to a base station, an AIoT session request message including capability information of the terminal device and AIoT service requirements.

Images