Method and apparatus for determining intermediate terminal device

Abstract

Embodiments of the present disclosure provide method and apparatus for determining intermediate terminal device A method performed by a first network node may comprise receiving from a second network node a first message comprising first information identifying at least one candidate terminal device. The method may comprise determining whether at least one terminal device can be used based on the first information. The method may comprise sending to the second network node a second message comprising information identifying the determined at least one terminal device to be used.

Description

METHOD AND APPARATUS FOR DETERMINING INTERMEDIATE TERMINAL DEVICETECHNICAL FIELD

[0001] The non-limiting and exemplary embodiments of the present disclosure generally relate to the technical field of communications, and specifically to methods and apparatuses for determining intermediate terminal device.BACKGROUND

[0002] This section introduces aspects that may facilitate abetter understanding of the disclosure. Accordingly, the statements of this section are to be read in this light and are not to be understood as admissions about what is in the prior art or what is not in the prior art.

[0003] In communication networks such as fifth generation system (5GS) as defined by 3rd Generation Partnership Project (3GPP), it may support various Internet of Things (loT) devices. For example, the loT devices may comprise zero-energy (ZE) loT (ZE-IoT) devices or Ambient loT (A-IoT or AIoT) devices, etc.

[0004] For example, Ambient loT can support many different use cases such as inventory taking, sensor data collection, asset tracking, actuator control, etc. Ambient loT devices are expected to be able to communicate with the network (such as 5GS) using Ambient loT Indirect Network Communication. Ambient loT Indirect Network Communication may represent communication between the Ambient loT device and the network where there is an Ambient loT capable terminal device helping in conveying information between the Ambient loT device and the network.SUMMARY

[0005] This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0006] Solution#! 1 in 3GPP Technical report (TR) 23.700-13 V0.3.0, the disclosure of which is incorporated by reference herein in its entirety, describes 5G core network (5GC) support for application function (AF) to communicate with AIoT devices. It is proposed to let Ambient loT Function (AIOTF) query Access and Mobility Management Function (AMF), Unified Data Management (UDM) and network data analytics function (NWDAF) to generate the candidate Intermediate user equipment (UE) list. AIOTF may pass the candidate intermediate UE list to Next Generation Radio Access Network (NG-RAN), and NG-RAN may generate the determined Intermediate UE list.

[0007] In S2-2404492, KI #1, #2, #3, New Solution: Support AIoT Devices for Topology 2 using AIOTF, 3GPP SA WG2 Meeting #162, Changsha, China, April 15 - 19, 2024, the disclosure of which is incorporated by reference herein in its entirety, AIOTF keeps track of Intermediate UEs,and generates the determined Intermediate UE list based on the position of the UEs and the intended area.

[0008] When the network receives a request from AF for a device or a group of devices in an intended area, there may be some Intermediate UEs in the intended area. Network needs to be able to select at least one of the Intermediate UEs to be used. Those UEs may / should support the frequency to be used for the devices. Those UEs may / should be able to cover a part of the whole intended area, and the interferences among those UEs may / should be minimized. For example, if two Intermediate UEs are very close to each other, only one of them may / should be chosen. If both of them are used, it may not extend the coverage, but may bring interferences in radio interface.

[0009] The core network (CN) (e.g., AIOTF) could generate the candidate UE list and pass it to a radio access network node. The radio access network node can make the final decision considering the UE position, UE radio resource situation, UE load situation, etc., so that the selection of Intermediate UEs could be more accurate.

[0010] When determining the Intermediate UE list, those Radio Resource Control (RRC) CONNECTED and RRC INACTIVE UEs can be utilized by CN (e.g. AIOTF). But for those RRC_IDLE UEs, the location and the last serving radio access network node recorded in the network may be not trustable. Those UEs may move out of the radio access network node notification area or even the coverage of the last serving radio access network node. Based on the last known location, CN (e.g. AIOTF) may not be able to make a correct decision.

[0011] With the help from the radio access network node, the selection of Intermediate UEs may be more accurate. But it does not include those RRC IDLE UEs. If CN (e g. AIOTF) passes an Intermediate UE list containing RRC_IDLE UEs to the radio access network node and expects the radio access network node to make the final decision, the radio access network node cannot take those RRC_IDLE UEs into consideration, as the radio access network node does not hold any information of those RRC IDLE UEs.

[0012] If there are plenty of RRC IDLE Intermediate UEs but limited RRC CONNECTED and RRC_INACTIVE UEs, the determination by the radio access network node may be hard as there might not be enough UEs to completely cover the intended area. In worst cases, if all Intermediate UEs are in RRC IDLE state, the radio access network node may find out that no Intermediate UEs can be utilized.

[0013] To overcome or mitigate at least one of above mentioned problems or other problems, the embodiments of the present disclosure propose a solution for determining intermediate terminal device.

[0014] In a first aspect of the disclosure, there is provided a method performed by a first network node. The method may comprise receiving from a second network node a first message comprising first information identifying at least one candidate terminal device. The method may comprise determining whether at least one terminal device can be used based on the first information. The method may comprise sending to the second network node a second message comprising information identifying the determined at least one terminal device to be used. The at least one candidate terminal device may be in a first state that a Radio Resource Control (RRC) connection has been established, or a part of the at least one candidate terminal device may be in a secondstate that no RRC connection is established, the part of the at least one candidate terminal device is to be paged.

[0015] In a second aspect of the disclosure, there is provided a method performed by a second network node. The method may comprise sending to a first network node a first message comprising first information identifying at least one candidate terminal device. The method may comprise receiving from the first network node a second message comprising information identifying at least one terminal device which is determined based on the first information. The at least one candidate terminal device may be in a first state that an RRC connection has been established, or a part of the at least one candidate terminal device may be in a second state that no RRC connection is established, the part of the at least one candidate terminal device is to be paged.

[0016] In a third aspect of the disclosure, there is provided a method performed by a third network node. The method may comprise sending to a second network node a seventh message comprising the first information identifying at least one candidate terminal device. The method may comprise receiving from the second network node an eighth message comprising information identifying at least one terminal device which is determined based on the first information. The at least one candidate terminal device may be in a first state that an RRC connection has been established, or a part of the at least one candidate terminal device may be in a second state that no RRC connection is established, the part of the at least one candidate terminal device is to be paged.

[0017] In a fourth aspect of the disclosure, there is provided a first network node, said first network node is operative to perform any of the methods of the first aspect of the disclosure.

[0018] In a fifth aspect of the disclosure, there is provided a second network node, said second network node is operative to perform any of the methods of the second aspect of the disclosure.

[0019] In a sixth aspect of the disclosure, there is provided a third network node, said third network node is operative to perform any of the methods of the third aspect of the disclosure.

[0020] In another aspect of the disclosure, there is provided a computer program product comprising instructions which when executed by at least one processor, cause the at least one processor to perform any of the methods according to any one of the first or second or third aspect.

[0021] In another aspect of the disclosure, there is provided a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to perform any of the methods according to any one of the first or second or third aspect.

[0022] Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows. In some embodiments herein, the proposed solution can avoid Intermediate UEs in RRC_IDLE state when the first network node such as NG-RAN determines Intermediate UEs. In some embodiments herein, the proposed solution can enable the first network node such as NG-RAN to make a correct decision and possible enable a better coverage for a service such as AIoT service. The embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The above and other aspects, features, and benefits of various embodiments of the present disclosure will become more fully apparent, by way of example, from the following detaileddescription with reference to the accompanying drawings, in which like reference numerals or letters are used to designate like or equivalent elements. The drawings are illustrated for facilitating better understanding of the embodiments of the disclosure and not necessarily drawn to scale, in which:

[0024] FIG.1 a shows 5GS enhancement to support AIoT Devices for Topology 2;

[0025] FIG. lb shows information Flow for AIoT data retrieval;

[0026] FIG. 1c shows information Flow for selecting I-node based on location of target devices from AF;

[0027] FIG. Id shows information Flow for selection of I-nodes based on list of I-nodes from AF;

[0028] FIG.2a shows the architecture for supporting AIoT Devices using AIOTF for Topology 2;

[0029] FIG.2b shows Protocol Stack for Supporting AIoT Devices using AIOTF for Topology 2;

[0030] FIG.2c shows Inventory Procedure;

[0031] FIG.2d shows Command Procedure;

[0032] FIGs.3a-3c, 4a-4f and 5a-5b show flowcharts of methods according to embodiments of the present disclosure;

[0033] FIG.6a shows a flowchart of registration procedure according to another embodiment of the present disclosure;

[0034] FIG.6b shows a flowchart of Option 1 according to another embodiment of the present disclosure;

[0035] FIG.6c shows a flowchart of Option 2a according to another embodiment of the present disclosure;

[0036] FIG.6d shows a flowchart of Option 2b according to another embodiment of the present disclosure;

[0037] FIG.6e shows a flowchart of Option 3a according to another embodiment of the present disclosure;

[0038] FIG.6f shows a flowchart of Option 3b according to another embodiment of the present disclosure;

[0039] FIG.7 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure;

[0040] FIG.8 shows an example of a communication system in accordance with some embodiments;

[0041] FIG.9 shows a UE in accordance with some embodiments;

[0042] FIG. 10 shows a network node in accordance with some embodiments;

[0043] FIG. 11 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;

[0044] FIG. 12 shows Inventory Procedure according to another embodiment of the present disclosure; and

[0045] FIG. 13 shows Command Procedure according to another embodiment of the present disclosure.DETAILED DESCRIPTION

[0046] The embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled persons in the art to better understand and thus implement the present disclosure, rather than suggesting any limitations on the scope of the present disclosure. Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present disclosure should be or are in any single embodiment of the disclosure. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Furthermore, the descnbed features, advantages, and characteristics of the disclosure may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the disclosure.

[0047] As used herein, the term “network” refers to a network following any suitable communication standards such as new radio (NR), long term evolution (LTE), LTE-Advanced, wideband code division multiple access (WCDMA), high-speed packet access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Address (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency-Division Multiple Access (OFDMA), Single carrier frequency division multiple access (SC-FDMA) and other wireless networks. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), etc UTRA includes WCDMA and other variants of CDMA. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash- OFDMA, Ad-hoc network, wireless sensor network, etc. In the following description, the terms “network” and “system” can be used interchangeably. Furthermore, the communications between two devices in the network may be performed according to any suitable communication protocols, including, but not limited to, the communication protocols as defined by a standard organization such as 3GPP. For example, the communication protocols may comprise the first generation (1G), 2G, 3G, 4G, 4.5G, 5G, 6G communication protocols, and / or any other protocols either currently known or to be developed in the future.

[0048] The term “network device” or “network node” or “network function” refers to any suitable function which can be implemented in a network entity (physical or virtual) of a communication network. For example, the network function 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. For example, the 5G system (5GS) may comprise a plurality of NFs such as Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Service Function (AUSF), Unified Data Management (UDM), Policy Control Function (PCF),Application Function (AF), Network Exposure Function (NEF), User plane Function (UPF) and Network Repository Function (NRF), radio access network (RAN), service communication proxy (SCP), network data analytics function (NWDAF), network slice Selection Function (NSSF), network slice-Specific Authentication and Authorization Function (NSSAAF), etc. In other embodiments, the network function may comprise different types of NFs for example depending on a specific network. For example, the 4G system (such as Long Term Evolution (LTE)) may include Mobile Management Entity (MME), home subscriber server (HSS), PCRF (Policy and Charging Rules Function), PGW (Packet Data Network Gateway), PGW control plane (PGW-C), PGW user plane (PGW-U) Serving gateway (SGW), SGW control plane (SGW-C), SGW user plane (SGW-U), E-UTRAN Node B (eNB), etc. In other embodiments, the network function may comprise different types of NFs for example depending on a specific network.

[0049] The network device may be an access network device with accessing function in a communication network via which a terminal device accesses to the network and receives services therefrom. The access network device may include a base station (BS), an access point (AP), a multi-cell / multicast coordination entity (MCE), a controller or any other suitable device in a wireless communication network. The BS may be, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a next generation NodeB (gNodeB or gNB), a remote radio unit (RRU), a radio header (RH), an Integrated Access and Backhaul (IAB) node, a remote radio head (RRH), a relay, a low power node such as a femto, a pico, and so forth.

[0050] Y et further examples of the access network device comprise multi-standard radio (MSR) radio 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, positioning nodes and / or the like. More generally, however, the network node may represent any suitable device (or group of devices) capable, configured, arranged, and / or operable to enable and / or provide a terminal device access to a wireless communication network or to provide some service to a terminal device that has accessed to the wireless communication network.

[0051] The term “terminal device” refers to any end device that can access a communication network and receive services therefrom. By way of example and not limitation, the terminal device refers to a mobile terminal, user equipment (UE), or other suitable devices. The UE may be, for example, a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a portable computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and a playback appliance, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet, a wearable device, a personal digital assistant (PDA), a portable computer, a desktop computer, a wearable terminal device, a vehiclemounted wireless terminal device, a wireless endpoint, a mobile station, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a USB dongle, a smart device, a wireless customer-premises equipment (CPE) and the like. In the following description, the terms “terminal device”, “terminal”, “user equipment” and “UE” may be used interchangeably. As one example, a terminal device may represent a UE configured for communication in accordance with one or more communication standards promulgated by the 3 GPP (3rd Generation Partnership Project),such as 3GPP LTE standard or NR standard. As used herein, a “user equipment” or “UE” may not necessarily have a “user” in the sense of a human user who owns and / or operates the relevant device. In some embodiments, a terminal device may be configured to transmit and / or receive information without direct human interaction. For instance, a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the communication network. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but that may not initially be associated with a specific human user.

[0052] As yet another example, in an Internet of Things (loT) scenario, a terminal device 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 terminal device and / or network equipment. The terminal device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as a machine-type communication (MTC) device. As one particular example, the terminal device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances, for example refrigerators, televisions, personal wearables such as watches etc. In other scenarios, a terminal device may represent a vehicle or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

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

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

[0055] As used herein unless expressly stated to the contrary, the phrase “at least one of A and B” or “at least one of A or B” should be understood to mean any of the following “only A, only B, or both A and B.” The phrase “A and / or B” should be understood to mean any of the following “only A, only B, or both A and B”.

[0056] As used herein unless expressly stated to the contrary, the phrase “a plurality of’ followed by a conjunctive list of enumerated items (e.g, “A and B ”, “A, B, and C”) is intended to mean “multiple items, with each item selected from the list consisting of’ the enumerated items. For example, “a plurality of A and B” is intended to mean any of the following: more than one A; more than one B; or at least one A and at least one B.

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

[0058] It is noted that these terms as used in this document are used only for ease of description and differentiation among nodes, devices or networks etc. With the development of the technology, other terms with the similar / same meanings may also be used.

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

[0060] 3GPP TR 23.700-13 v0.3.0

[0061] 3GPP TR 23.700-13 v0.3.0 “Study on Architecture support of Ambient power-enabled Internet of Thing (Release-19)” was agreed in 3GPP SA2 162. The following content is from 3GPP TR 23.700-13 vO.3.0.

[0062] Within the 3GPP TR 23.700-13 v0.3.0, the architecture assumptions and requirements, 3 key issues were agreed and included. There are some solutions which are relevant with topology 2 (e.g. solution#! 1 in the 3GPP TR 23.700-13 v0.3.0).

[0063] Clause of 4.1 of 3GPP TR 23.700-13 v0.3.0 describes Architectural Assumptions as below.

[0064] - The following traffic types for Ambient loT Device are to be studied:

[0065] - DT : Device-terminated; and

[0066] - DO-DTT : Device-originated - device-terminated triggered.

[0067] - The following two connectivity topologies as defined in TR 38.848 [7] are to be studied:

[0068] - Topology 1: BS <--> Ambient loT Device;

[0069] - Topology 2: BS <-> intermediate node <-> Ambient loT Device: Only a UE can act as an intermediate node which is under the network control.

[0070] - The communication spectrum is assumed to be licensed.

[0071] - Handover is not supported.

[0072] - RRC states are not supported by AIoT Devices (see TR 38.769 [8])

[0073] - No mobility (i.e. at least no cell selection / re-selection-like function) supported byAIoT Devices (see TR 38.769 [8])

[0074] The meaning of no mobility is to be clarified by RAN in TR 38.769 [8],

[0075] Clause of 4.2 of 3GPP TR 23.700-13 v0.3.0 describes Architectural Requirements as below.

[0076] The following architectural requirements are applicable to this study:

[0077] - Support for AIoT Services needs to adhere to the nature of the AIoT Devices (e.g. ultra-low complexity, power, cost and resource-constrained).

[0078] - Support of the security aspects needs to consider the nature of the AIoT Devices (e.g. ultra-low complexity power, cost and resource-constrained) while addressing e.g. confidentiality, integrity, etc.

[0079] Clause of 6.11 of 3GPP TR 23.700-13 v0.3.0 describes Solution #11: 5GC support for AF to communicate with AIoT devices as below.

[0080] This solution address aspects of key issue #3 on Support of Ambient loT Services.

[0081] This solution enables the AF to communicate with the target AIoT devices for DO-DTT and DT traffic types via 5GC, dedicated for only Topology 2.

[0082] This solution considers scenarios in which an application service provider has prior information about intermediate nodes (abbreviated as I-node) expected to be located in specific places (e.g. intermediate nodes being used only in particular warehouses). Additionally, scenarios where the provider knows candidate locations for the target AIoT devices (e.g. the AIoT devices attached to goods are expected to be in particular warehouses or retail markets) are also considered.

[0083] The assumption and high-level procedures of this solution are as follows:

[0084] - The AIoT device ID is defined by the external application and provided by the AF to the 5GC when requesting the AIoT-related services. The uniqueness of the AIoT device ID per application is assumed to be guaranteed by the application itself, such as by adhering to standards like EPC (Electronic Product Code) and utilizing EPCglobal allocation, which manages a global registry for unique prefixes among different companies.

[0085] - AIoT devices are not registered with the 5GC.

[0086] - AIoT Devices are provisioned with AIoT Device ID and associated security materials.

[0087] - A UE, additionally capable of directly communicating with the AIoT devices, is acting as the intermediate node.

[0088] - A UE acting as an intermediate node is registered with 5GC using the existing mechanism, with some enhancements to indicate its capability of acting as an intermediate node, and is authorized as an intermediate node (UE) during the registration procedure.

[0089] - The AF possesses information about the candidate location(s) of the target AIoT devices or about the preferred intermediate node (i.e. external UE ID) and provides them when requesting the AIoT related services to 5GC.

[0090] - If the AF is in the 3rd party domain, the AF can communicate with the 5GC via NEF that can be combined with the AIoT NF.

[0091] - When information about the preferred intermediate node is provided while it is not operational, or when the location(s) of the target AIoT devices are given, the 5GC selects the intermediate node based on the network information. The process of selecting such an intermediate node is not within the scope of this solution. This means that this solution supports both static and dynamic binding with the intermediate node.

[0092] - How to support security between each entity (e.g. between AIoT device and I-node, and AIoT device and CN) involved in the procedures (e.g. relying on application security or providing network security based on the information provided by the application) is assumed to be addressed by SA WG3.

[0093] - The Uu interface between the intermediate node and the gNB is assumed to be used, while anew protocol stack, defined by RAN, is assumed to be used between the AIoT device and the intermediate node.

[0094] - For DO-DTT traffic (e.g response from the AIoT device to the network), it can be sent over the NAS of the intermediate node.

[0095] FIG. la shows 5GS enhancement to support AIoT Devices for Topology 2, which is same as Figure 6.11.1-1 of 3GPP TR 23.700-13 v0.3.0.

[0096] FIG. lb shows information Flow for AIoT data retrieval, which is same as Figure 6.11.2.1-1 of 3GPP TR 23.700-13 vO.3.0.

[0097] Clause 6.11.2.1 of 3GPP TR 23.700-13 v0.3.0 describes communication with AIoT devices as below.

[0098] To facilitate communication between an external AF with AIoT devices for data retrieval, this solution proposes certain measures to be taken:

[0099] 0. It is assumed that the AF requesting 5GC to communicate with specific AIoT devices possesses their AIoT device IDs, either defined by the device manufacturer or the AF itself, along with candidate locations of the AIoT devices or information (e.g. external ID) of the intermediate node covering the target AIoT devices.

[0100] 1. The intermediate node is a UE with the capability to directly communicate with the AIoT devices. The intermediate UE performs the registration procedure as specified in clause 4.2.2.2 of TS 23.502 [5] with the following enhancement:

[0101] - The UE indicates AIoT support in the MM capability.

[0102] - The subscription data of the UE is also enhanced to indicate whether the UE is allowed to perform the AIoT operation.

[0103] - The Registration Accept message also indicates whether the UE has been authorized to perform the AIoT operation. Validity information may also be included for the AIoT operation. Validity information can be time validity information (defined by start and end times) to indicate when the UE is allowed to perform the AIoT operation or location validity information (defined by TAI or cell ID) to indicate where the UE is allowed to performed the AIoT operation.

[0104] 2. The AF sends a request to 5GC to communicate with the target AIoT devices for either DT or DO-DTT traffic type. The AF's request includes following parameters: the target AIoT device IDs defined by the external application and installed in the AIoT devices, the candidate locations of the target AIoT devices or the external ID (i.e. external UE ID) of the intermediate node that can directly communicate with the target AIoT devices, "command" information (e g., read / write), optionally specific target data to be read by the AF.

[0105] 3. Upon receiving the AF request, the NEF authorizes the AF request based on SLA.

[0106] 4. The NEF translates the external ID (e.g. GPSI) of the intermediate node, if provided, to the SUPI via UDM and verifies whether the UE possessing the translated SUPIs is authorized to function as intermediate node through UDM. The NEF translates the location, if provided by the AF, into 3GPP based location information (Tracking areas TA(s), cell ID(s), etc). The NEF identifies the serving AMF(s) via UDM by utilizing the SUPI of the intermediate node, if applicable, or by considering the candidate locations of the AIoT devices. The NEF selects AIoTF that can be a standalone NF or collocated with the NEF.

[0107] 5. An AIOT service request message is sent to the AIoTF, including the following parameters: AIoT session ID, the target AIoT devices, candidate locations or the SUPI of the intermediate node, Serving AMF(s) as derived in step 4, "command" information (e.g., read / write), optional Requested target data.

[0108] 6. The AIoTF may select the intermediate node based on the information provided in step 5 to communicate with the target AIoT devices. The detailed procedures for selecting the intermediate node are described in clause 6.11.2.2.

[0109] 7. The AIoTF requests the serving AMF to initiate the communication, which includes AIoT session ID, the target AIoT device IDs, candidate locations or SUPI of the selected intermediate node, "command" information (e.g., read / write) and optional Requested target data.

[0110] 8. The AMF identifies the serving gNB by utilizing the SUPI of the intermediate node, if applicable, or by considering the candidate locations (i.e., a list of TAIs and cell IDs) of the AIoT devices. The AMF then requests the gNB to send a AIoT service request, which contains the target AIoT device IDs, candidate locations or UE NGAP ID of the selected intermediate node, "command" information (e.g., read / write), and optional Requested target data, to the selected I- node. For example, the paging request message or DL NAS Transport message can be used with some extensions to convey the AMF request.

[0111] 9. The gNB requests the selected intermediate node to communicate with the AIoT data, providing the target AIoT device IDs, "command" information (e.g., read / write), and the Requested target data (if applicable). For example, RRC paging message can be used by the gNB to send the request to the intermediate node. When RRC paging is used, the gNB may restrict the paging area only to the identified cells for optimization, if available.

[0112] 10. The selected intermediate node sends out a request which includes the target AIoT device IDs and the Requested target data (if applicable).

[0113] 11. The AIoT devices check whether their device IDs match any of the target AIoT device IDs included in the received request. If there's no match, the AIoT devices do not react.

[0114] 12. If there's a match, the AIoT devices check the presence of Requested target data within the request as well as "command" information to check whether DT or DO-DTT traffic type is requested. In case of DO-DTT type requested, if the Requested target data is absent, the AIoT devices send a response message incorporating only their device IDs. If the Requested target data is present, the AIoT devices send a response message including their device IDs and only the data requested to the intermediate node.

[0115] 13. The intermediate node receives the response message from the AIoT devices. If the AIoT device ID within the received message corresponds to any of the target AIoT device IDs obtained in step 10, the intermediate node assesses which AIoT devices, from the list of expected AIoT devices, have provided a response. The intermediate node may aggregate the response messages from the AIoT devices according to the configuration information if it was provided by the CN in advance. The intermediate node then forwards this information, encompassing AIoT device data (if applicable) and the AIoT device ID(s), to the AF via gNB, AMF, AIoTF and NEF. The AMF or AIoTF may aggregate response messages from some or all of the targeted AIoT devices during the forwarding procedures.

[0116] FIG. 1c shows information Flow for selecting I-node based on location of target devices from AF, which is same as Figure 6.11.2.2-1 of 3GPP TR 23.700-13 v0.3.0.

[0117] Clause 6.11.2.2 of 3GPP TR 23.700-13 v0.3.0 describes Selection of intermediate nodes as below.

[0118] The selection of the intermediate node can be performed based on the geographical location of the target AIoT devices or the identity of the intermediate node from AF. The procedure for selection of intermediate nodes based on geographical location is depicted in Figure 6.11.2.2-1.

[0119] 1-4. Step 2 to 5 in clause 6.11.2.1 of 3GPP TR 23.700-13 v0.3.0 are performed.

[0120] 5. The AIOTF collects necessary information from relevant NFs, for I-node selection, based on the requested location info.

[0121] a. The AIOTF first discovers the UEs present in the requested location and may also retrieve the UE related information from AMF, including connection status and reachability.

[0122] b. The AIOTF may retrieve information related to the UEs discovered in step 5a from UDM. This information enables checking, for example, whether the UEs are registered, authenticated, authorized to act as I-nodes. Additionally, the information from UDM can include the Expected UE behaviour, as described in clause 4.15.6.3 of TS 23.502 [5], that can be used to check the battery indication, stationary indication among other parameters.

[0123] c. The AIOTF may retrieve information related to the UEs discovered in step 5a from NWDAF. This information enables checking, for example, if the discovered UEs are not too much loaded to serve the devices, function well without anomalies, or will not move out of the coverage for a significant period based on the UE related analytics as specified in clause 6.7 of TS 23.288

[0013] ,

[0124] 6. The AIOTF, based on the information collected in step 5, selects a list(s) of potential I-nodes.

[0125] 7 In case no I-nodes could be selected at step 6, AIOTF sends AIOT Response with the failure reason to the AF, and the subsequent steps are skipped.

[0126] 8. The AIoTF requests the serving AMF to initiate the communication with the AIoT devices, which includes the target AIoT device IDs, and the selected I-node IDs.

[0127] 9. The AMF forwards the AIOT read request to gNB along with the target AIOT device IDs and the selected I-node IDs.

[0128] 10. The gNB performs additional validation to assess if the received I-nodes are optimal for serving the AIoT devices, considering its local conditions such as response time, etc. Subsequently, the gNB makes the final selection on the best I-node. It is also possible that the gNB does not select any of the requested I-nodes if local conditions are not satisfied.

[0129] 11. The gNB may respond to the AIOTF via AMF with the final list of selected I-nodes. In case the gNB does not selection any I-node, the response may indicate there is no available UE.

[0130] FIG. Id shows: information Flow for selection of I-nodes based on list of I-nodes from AF, which is same as Figure 6.11.2.2-2 of 3GPP TR 23.700-13 v0.3.0.

[0131] Clause 6.11.2.2 of 3GPP TR 23.700-13 v0.3.0 describes Selection of intermediate nodes as below.

[0132] 1-4. Step 2 to 5 in clause 6.11.2.1 of 3GPP TR 23.700-13 v0.3.0 are performed.

[0133] 5. The AIOTF collects necessary network information related to the requested UEs from relevant NFs.

[0134] a The AIOTF may retrieve information related to the requested UE from UDM. This information enables checking, for example, whether the UEs are registered, authenticated, authorized to act as I-nodes. Additionally, the information from UDM can include the Expected UE behaviour, as described in clause 4.15.6.3 of TS 23.502 [5], that can be used to check the battery indication, stationary indication among other parameters.

[0135] b. The AIOTF may retrieve information related to the requested UE from NWDAF. This information enables checking, for example, if the discovered UEs are not too much loaded to serve the devices, function well without anomalies, or will not move out of the coverage for a significant period based on the UE related analytics as specified in clause 6.7 of TS 23.288

[0013] ,

[0136] c. The AIOTF may retrieve information related to the requested UE from AMF, including its location, connection status and reachability.

[0137] 6. The AIOTF, based on the information collected in step 5, validates whether the requested UE ID provided in the AF request can serve as an intermediate node.

[0138] 7. If the requested UE is not operational and other "I-nodes allowed" flag was not set in the AF request, AIOTF sends AIOT Response with the failure reason to the AF, and the subsequent steps are skipped.

[0139] 8. If the validation of the requested I-node fails and the 'other I-nodes allowed' flag was set in the AF request, the AIOTF may select a different list of UEs for the requested operation than the UE requested by the AF. This can be achieved by performing the step 5 in the Figure 6.11.2.2-1 with the location set to the location information of the requested UE retrieved from AMF in step 5 c.

[0140] 9. The AIoTF requests the serving AMF to initiate the communication with the AIoT devices, which includes the target AIoT device IDs, and the selected I-node IDs.

[0141] 10. The AMF forwards the AIOT read request to gNB along with the target AIOT device IDs and the selected I-node IDs.

[0142] 11. The gNB performs additional validation to assess if the received I-nodes are optimal for serving the AIoT devices, considering its local conditions such as response time, received signal strength, etc. Subsequently, the gNB makes the final selection on the best I-node. It is also possible that the gNB does not select any of the requested I-nodes if local conditions are not satisfied.

[0143] 12. The gNB may respond to the AIOTF via AMF with the final list of selected I-nodes.

[0144] Clause 6.11.3 of 3GPP TR 23.700-13 vO 3.0 describes impacts on services, entities and interfaces as below.

[0145] NEF:

[0146] - Supports exposing a new API to AF for AIoT services.

[0147] UDM:

[0148] - Supports validating if a UE is authorized to act as an I-node.

[0149] AMF:

[0150] - Supports forwarding the AIOTF requests to gNB.

[0151] gNB:

[0152] - Supports handling new AIoT related services.

[0153] - Supports making the final selection of the I-node.

[0154] UE (I-node):

[0155] - Supports indicating its capability to support AIoT services during UE registration.

[0156] - Supports communicating with AIoT devices.

[0157] New NF:

[0158] - AIOTF:

[0159] - This can be a standalone NF or combined with NEF.

[0160] - Supports necessary network information for specific UEs or specific location from multiple NFs (e.g., AMF, UDM, NWDAF)

[0161] - Supports selecting or validating I-nodes.

[0162] - Supports forwarding the AF requests to AMF.

[0163] S2-2404492

[0164] S2-2404492 was proposed to SA2#162 as a new solution for topology 2. The following content is from S2-2404492.

[0165] 6.X Solution #X: Support AIoT Devices using AIOTF for Topology 2

[0166] 6.X.1 Description

[0167] This solution proposes an complementary solution to Solution #8. It enables the support of Ambient loT devices for topology 2, which addresses KI#1, KI# 2 and KI#3. Together with Solution #8 which focus on Topology 1, the solutions can support both AIoT devices for both Topologies.

[0168] In this solution, it is AIOTF who is in charge of the intermediate UE for the Ambient loT operations, including determining intermediate UEs, sending operation commands to and receiving results from intermediate UEs. As the licensed spectrum is owned by MNO, it is proposed to let network provide the radio resource information towards the intermediate UEs about the spectrum information for the over-the-air interface between Intermediate UEs and AIoT devices.

[0169] FIG.2a shows the architecture for supporting AIoT Devices using AIOTF for Topology 2, which is same as Figure 6.X. 1.1-1 of S2-2404492.

[0170] 6.X.1. 1 Reference Architecture

[0171] This solution focuses on Topology 2, which works together with Solution #8 addressing Topology 1.

[0172] The functional entities defined in Solution #8 and TS 23.501 [4] are reused with the exception for the following additions:

[0173] - UDM / UDR: The authorization information of Intermediate UE for AIoT is stored in UE subscription data

[0174] - AMF: Receive AIoT capability information from UE and authorize based on the subscription data in UDM / UDR.

[0175] - NG-RAN: Provide spectrum information towards authorized intermediate UE.

[0176] - Intermediate UE:

[0177] - Provide Ambient loT capability information to AIOTF and receive the authorization information

[0178] - Receive the instruction from AIOTF and perform Ambient loT operations (e.g., inventory, command, etc.) on the proper spectrum. The radio resource information is received from NG-RAN

[0179] - Ambient loT Function (AIOTF): AIOTF is introduced to support AIoT services, with some AMF's functionalities integrated, which includes:

[0180] - Inventory handling and device context management.

[0181] - Command delivery.

[0182] - Authentication and authorization for the access, which triggers interaction with AUSF / UDM

[0183] - Collect charging data and interact with CHF for charging.

[0184] - Routing the request from AF (via NEF) to Intermediate UEs, for DO-DTT / DT traffic types.

[0185] - Routing the response from Intermediate UEs to AF (via NEF) for DO-DTT traffic type.

[0186] FIG.2b shows Protocol Stack for Supporting AIoT Devices using AIOTF for Topology 2, which is same as Figure 6.X. 1.2-1 of S2-2404492.

[0187] 6.X.1.2 Protocol Stack

[0188] Within the protocol stack, the AIOT Device NAS layer, AIOT AS layer and App layer are defined as Solution #8.

[0189] As UE reader is used in Topology 2, which is different form the RAN reader in Topology 1, the following layer is proposed specific in this solution:

[0190] -AIOT UE NAS layer: The NAS protocol between AIOTF and UE readers. Besides the 5GMM NAS and 5GSM NAS, it can be defined as a new NAS (e.g. 5GAIOT NAS) which is transmitted within the 5GMM NAS.

[0191] 6.X.2 Procedures

[0192] NOTE: The message names in the procedures below are descriptive. It is assumed that the names are updated with corresponding SBI based names where applicable during the normative phase.

[0193] 6.X.2. 1 AIoT Service Authorization for Intermediate UE

[0194] The Registration procedure for UE is performed as defined in clause 4.2 2.2 of 3GPP TS 23.502 with the following additions:

[0195] - UE includes the AIoT Intermediate node capability as part of “5GMM capability” in Registration Request message.

[0196] - The AMF obtains the AIoT Subscription data as part of the user subscription data from UDM using Nudm_SDM service

[0197] - The AMF determines whether the UE is authorized to work as Intermediate UE for AIoT based on UE’s AIoT Intermediate node capability and the AIoT Subscription data The AMF includes the authorization information as part of UE context in NGAP message sent to NG-RAN.

[0198] In Service Request procedure, N2 Handover procedure, Xn Handover procedure, and when receiving Subscriber Data Update to AMF, the AMF includes the authorization information in NGAP message sent to NG-RAN.

[0199] 6.X.2.2 AIOTF Keep Track of Intermediate UE

[0200] For authorized Intermediate UEs (Those Ambient loT Capable UEs which have been authorized by the AMF as described in clause 6.X.2.1), in Initial Registration procedure as defined in clause 4.2.2.2 of TS 23.502 [5] with the following additions:

[0201] -The AMF sends Registration Request to the AIOTF for the Intermediate UE, so that the AIOTF may select the Intermediate UE for AIoT operations.

[0202] In Deregistration procedure as defined in clause 4.2.2.3 of TS 23.502 [5], the following additions are performed:

[0203] - The AMF sends Deregistration Request to the AIOTF for the Intermediate UE, so that the Intermediate UE will no longer be used.

[0204] The AIOTF can subscribe the UE mobility event of the Intermediate UE towards the AMF to be updated for the location information.

[0205] FIG.2c shows Inventory Procedure, which is same as Figure 6.X.2.3-1 of S2-2404492.

[0206] 6.X.2.3 Application Inventory Procedure

[0207] The Inventory procedure can be initiated by the AF to discover one or more AIoT devices in a specific area via Intermediate UEs.

[0208] 1. AF sends Inventory Request to the AIOTF, which is the same as step 1 - 4 in Figure 6.8.2.1-1 in Solution #8.

[0209] 2. The AIOTF determines the Intermediate UEs to be used, based on the location information for the Intermediate UEs, as well as area information provided by the AF.

[0210] 3. The AIOTF creates and sends the 5GAIOT NAS message to request the Intermediate UE to perform the Inventory. The 5GAIOT NAS message is delivered via the AMF and the NG- RAN.

[0211] 4. The Intermediate UE determines radio resource or requests NG-RAN to determine radio resource, which is used between AIoT Devices and Intermediate UE.

[0212] 5. The Intermediate UE initiates inventory based on device information as well as the inventory strategy information provided by the AF. The Intermediate UE may provide reader identity information to enable the AIoT devices to understand they are read by which Intermediate UE. Considering the mobility of the Intermediate UE, the reader identity information can be a combination of a UE ID and the location information.

[0213] 6. The AIoT Device reports the device ID to the Intermediate UE. If the Inventory procedure indicates delta inventory only, and the AIoT Device has performed the inventoiy procedure towards this reader, it should skip the reporting. The device capability index can be provided by AIoT device optionally.

[0214] 7. The Intermeidate UE creates the 5GAIOT NAS message and sends towards the AIOTF to transmit the AIoT Device ID and optional device capability index. The Intermediate UE may further provide location information (ULI) of the device, if requested from the AIOTF and allowed by local policy. The Intermediate UE may further provide an end indicator to inform the AIOTF whether it is the last inventory response for the inventory round.

[0215] 8. The AIOTF validates the concealed device ID via interacting with AUSF and UDM. The AIOTF may further get the device capability information from the device capability profile stored in the UDM based on the device capability index provided by the device.

[0216] 9. The AIOTF together with AUSF and UDM, triggers authentication and authorization procedures (i.e., like the authentication request / response between UE and network) towards the AIoT device. In Topology 2, the message between the AIOTF and the AIOT device is transmitted via the Intermediate UE over 5GAIOT NAS.

[0217] Based on the device capability information from UDM, if the AIoT device is capable of persistent received parameters, step 10 - step 11 are executed:

[0218] 10. The security mode negotiation and security parameter exchanges are performed (i.e., like the security mode command / complete between UE and network). In Topology 2, the message between the AIOTF and the AIOT device is transmitted via the Intermediate UE over 5GAIOT NAS.

[0219] 11. The AIOTF may further allocate CN device ID and sends to the AIoT device.

[0220] 12. The AIOTF registers with the UDM (UECM) for the device access.

[0221] 13. The AIOTF may further aggregate the reported device IDs and send to AF via the NEF, as step 14 - 16 in Figure 6.8.2. 1-1.

[0222] 6.X.2.4 Periodic Inventory

[0223] The periodic inventory may be requested by the AF, so that network can trigger the inventory periodically without the request from the AF directly.

[0224] Considering the movement of the Intermediate UE, and the inventory is based on area information, the periodic inventory should be initiated by the CN (i.e., the AIOTF), which follows the instructions from the AF. When the period expires in the AIOTF, the AIOTF determines the Intermediate UEs based on the area information from the AF and the location information for the Intermediate UEs. Steps 2 - 10 in FIG.2c are executed.

[0225] FIG.2d shows Command Procedure, which is same as Figure 6.X.2.5-1 of S2-2404492.

[0226] 6.X.2.5 Command Procedure

[0227] The command procedure is initiated by the AF to request one or more specific AIoT devices or a group of AIoT devices in an area to execute the command. The command can be read, write, enable, disable, or execution request from the AF. The command result from the devices may or may not be required.

[0228] The command for enable / disable is to be studied by SA3, and to be aligned with SA3.

[0229] 1. The AF sends Command Request to the NEF, containing the command to be executed, area information, device information, optional inventory strategy information, and optional report aggregation info.

[0230] - The command is to be executed in the AIoT devices. It contains the command (e.g., read, write, execute, etc.) together with the command parameters. The command specific parameters (e.g. what to be executed) are to be included in an app layer container between AF and AIOT devices.

[0231] - The area information could be the external geographical area information.

[0232] - The device information could be device ID, device group ID, and / or external device type.

[0233] - The location required indicates whether the AF requests the location information of the AIoT devices provided.

[0234] - The report aggregation info indicates whether the reports need to be aggregated or not for a specific aggregation period, and whether the reports are needed after the aggregation period.

[0235] 2. The NEF authorizes the request from the AF and perform the area translation to translate external area information to the internal area information. Within the authorization, the NEF further check whether the AF is authorized to get the location information of the device. The NEF map the external device type to internal device type (i.e., device 1, device 2a, device 2b, etc.).

[0236] Depending on whether area information is provided, step 3a or step 3b is performed:

[0237] 3a. If area information is provided, the NEF sends NRF query with internal area information to query AIOTFs serving the area.

[0238] 3b. If area information is not provided, and device ID(s) are provided, the NEF query the serving AIOTF from UDM.

[0239] 4. The NEF sends the Command Request to the AIOTFs with the command, internal area information, device information, device type, and optional location required information.

[0240] 5. The AIOTF allocates a Transaction ID for the command, which is unique per command. The AIOTF creates the AIOT Device NAS request message for the devices, based on the command information from the AF. The AIOTF get the registered devices, which match the device information. If no registered devices, step 6 - 13 are skipped.

[0241] 6. The AIOTF creates the 5GAIOT NAS request message and sends to the Intermediate UE to deliver the Command. The 5GAIOT NAS request message contains the AIOT Device NAS message, CN allocated device IDs for the registered devices, the Transaction ID, and optional location required information. The 5GAIOT NAS message is delivered via the AMF and the NG- RAN.

[0242] 7. The Intermediate UE determines radio resource or requests NG-RAN to determine radio resource, which is used between AIoT Devices and Intermediate UE.

[0243] 8. The Intermediate UE initiates command delivery for the AIOT Device NAS request message based on CN allocated device IDs, using dedicated signaling. Transaction ID is also included.

[0244] 9. The AIoT Device executes the command, creates an AIOT Device NAS response message containing the command result and delivers the AIOT Device NAS response message, if the result needs to be sent back. The application specific result can be included in an app layer container.

[0245] 10. The Intermediate UE creates the 5GAIOT NAS response message, including the AIOT Device NAS response message, and sends to the AIOTF. The Intermediate UE may further provide location information (ULI) of the device, if requested from the AIOTF and allowed by local policy. The 5GAIOT NAS message is delivered via the NG-RAN and the AMF.

[0246] 11. The AIOTF gets the command result from the AIOT Device NAS response message. The AIOTF may perform aggregation for the device ID, based on the report aggregation information provided by the AF. Within the aggregation period, the AIOTF will buffer the command results reported from the AIoT devices. The AIOTF may stop buffering and send report immediately, if it receives end indicator from the Intermediate UE in step 10. When the aggregation period expires, the AIOTF sends the report. For those command result after theaggregation period, if it is needed by the AF, the AIOTF sends the report. Otherwise, it will be dropped.

[0247] 12. The AIOTF sends Command Response or Notification Request towards the NEF for the command result or the aggregated command result information.

[0248] 13. The NEF sends Command Response or Notification Request towards the AF for the command result or the aggregated command result information.

[0249] If the AIOTF determines all required devices have executed the command (e.g. when AF provide the device ID(s) and those devices have executed the command in step 7 - 8), the following steps are skipped.

[0250] 14. For those unregistered devices(s), the AIOTF initiate Inventory procedure as steps 2 - 12 in FIG.2c (steps 11 - 12 will be skipped, if the device is not able to persistent received information). In the inventory the Transaction ID is delivered, so that the registered devices which have executed command do not respond this inventory request from the Intermediate UE.

[0251] 15. The AIOTF creates the 5GAIOT NAS request message and sends to the Intermediate UE to deliver the Command to the responded device. The 5GAIOT NAS request message contains the AIOT Device NAS request message, AIoT device ID and optional location required information. The 5GAIOT NAS request message is delivered via the AMF and the NG-RAN.

[0252] 16. The Intermediate UE determines radio resource or requests NG-RAN to determine radio resource, which is used between AIoT Devices and Intermediate UE.

[0253] 17. The Intermediate UE initiates command delivery for the AIOT Device NAS request message to the device.

[0254] 18. The AIoT Device executes the command, creates an AIOT Device NAS response message containing the command result and delivers the AIOT Device NAS response message, if the result needs to be sent back. The application specific result can be included in an app layer container.

[0255] 19. The Intermediate UE creates the 5GAIOT NAS response message, including the AIoT Device NAS response message, and sends to the AIOTF. The Intermediate UE may further provide location information (ULI) of the device, if requested from the AIOTF and allowed by local policy. The 5GAIOT NAS message is delivered via the NG-RAN and the AMF.

[0256] 20. As step 11 - 13, the AIOTF get the command result from the AIOT Device NAS response message. It may perform the aggregation and send to NEF. The NEF delivers to the AF.

[0257] Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a communication system complied with the exemplary system architecture illustrated in FIGs. la and 2a. For simplicity, the system architecture of FIGs. la and 2a only depict some exemplary elements. In practice, a communication system may further include any additional elements suitable to support communication between terminal devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or terminal device. The communication system may provide communication and various types of services to one or more terminal devices to facilitate the terminal devices’ access to and / or use of the services provided by, or via, the communication system.

[0258] FIG.3a shows a flowchart of a method according to an embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 300 as well as means or modules or circuits for accomplishing other processes in conjunction with other components.

[0259] At block 302, the first network node may receive from a second network node a first message comprising first information identifying at least one candidate terminal device.

[0260] The first network node may be deployed in any suitable network. In an embodiment, the first network node may be deployed in EPS, a 5GS or a 6G system (6GS) as defined by 3GPP.

[0261] The first network node may be any suitable network device or network node or network function. For example, the first network node may implement radio access network function.

[0262] In an embodiment, the first network node may comprise a radio access network node. For example, the radio access network node may be same as or similar to radio access network node (such as eNB or gNB) as described in various 3GPP specifications such as 3GPP TS 23.501 V18.5.0 or 3GPP TS 23.682 V18.0.0 or 3GPP 6G specification.

[0263] The second network node may be deployed in any suitable network. In an embodiment, the second network node may be deployed in EPS, 5GS or 6GS as defined by 3GPP.

[0264] The second network node may be any suitable network device or network node or network function. For example, the second network node may implement access and mobility management function.

[0265] In an embodiment, the second network node may comprise an access and mobility management node. For example, the access and mobility management node may be same as or similar to access and mobility management node (such as MME or AMF) as described in various 3GPP specifications such as 3GPP TS 23.501 VI 8.5.0 or 3GPP TS 23.682 V18.0.0 or 3GPP 6G specification.

[0266] The at least one candidate terminal device may be any suitable terminal device In an embodiment, the at least one candidate terminal device may have a capability of directly communicating with an Internet of Things (loT) device. For example, the at least one candidate terminal device may be candidate intermediate node (I-node) as described in 3GPP TR 23.700-13 V0.3.0. For example, the first network node may select appropriate I-node(s) based on the at least one candidate I-node.

[0267] The loT device may be any loT device. In an embodiment, the loT device may comprise an Ambient loT Device as described in 3GPP TR 23.700-13 V0.3.0.

[0268] In an embodiment, the at least one candidate terminal device may be in a first state that a Radio Resource Control (RRC) connection has been established.

[0269] In an embodiment, the first state may comprise at least one of RRC CONNECTED state and RRC_INACTIVE state as described in various 3GPP specifications such as 3GPP TS 23.501 V18.5.0 or 3GPP TS 38.331 V18.1.0.

[0270] In an embodiment, if a candidate terminal device is in the RRC_INACTIVE state, the candidate terminal device may be paged to let the candidate terminal device in the RRC_CONNECTED state. For example, the first network node or the second network node may page the candidate terminal device to let it in the RRC CONNECTED state.

[0271] In an embodiment, the at least one candidate terminal device may be kept by the first network node in the first state. For example, if the first network node knows that a terminal device is a candidate terminal device (such as candidate I-node), the first network node may keep the candidate terminal device in the first state. For example, the first network node does not release the candidate terminal device to the second state such as RRC_IDLE state.

[0272] In an embodiment, the at least one candidate terminal device sent by the second network node may be in the first state. For example, the second network node may know the state of a candidate terminal device (such as candidate I-node). The second network node may send the first information identifying at least one candidate terminal device in the first state to the first network node. For example, the second network node may remove the candidate terminal device(s) in the second state such as RRC IDLE state from one or more candidate terminal devices to generate a list of the at least one candidate terminal device. For example, the second network node may page the candidate terminal devices in the second state such as RRC IDLE state. After paging is finished, the second network node may remove the candidate terminal devices in the second state from one or more candidate terminal devices to generate a list of the at least one candidate terminal device.

[0273] In an embodiment, the at least one candidate terminal device sent by the second network node may be in the RRC CONNECTED state or the RRC INACTIVE state.

[0274] In an embodiment, a part of the at least one candidate terminal device may be in a second state that no RRC connection is established.

[0275] In an embodiment, the second state may comprise an RRC IDLE state as described in various 3GPP specifications such as 3GPP TS 23.501 V18.5.0 or 3GPP TS 38.331 V18.1.0.

[0276] In an embodiment, the first network node may cause the part of the at least one candidate terminal device to be paged. For example, the first network node may send a message to the second network node to indicate the second network node to page the part of the at least one candidate terminal device. Alternatively, the first network node may directly page the part of the at least one candidate terminal device.

[0277] The first message may be any suitable message such as existing message or new message. In an embodiment, the first message may be a Determine UE Request. The first message may indicate the first network node such as NG-RAN to select / determine / pick up appropriate candidate terminal device(s) based on the at least one candidate terminal device.

[0278] The first information may be any suitable information which can identify the at least one candidate terminal device. For example, the first information may be a list of the at least one candidate terminal device.

[0279] The at least one candidate terminal device may be determined by the second network node. Alternatively, the second network node may receive a list of the at least one candidate terminal device from another node such as AF.

[0280] At block 304, the first network node may determine whether at least one terminal device can be used based on the first information.

[0281] The at least one terminal device may be determined further based on any other selection conditions. In an embodiment, the at least one terminal device may be determined further based on at least one of:area information, a radio condition of a candidate terminal device, a position of a candidate terminal device, a radio resource situation of a candidate terminal device, a RRC connection state of a candidate terminal device, or a load situation of a candidate terminal device.

[0282] The area information may be an intended area in which a target device or a group of target devices are located. There may be some candidate terminal devices (e.g. Intermediate UEs) in the intended area. The first network node needs to be able to select some of them to be used (e g. directly communicate with at least one target device (such as AIoT device) in the intended area).

[0283] In an embodiment, the first network node may determine the at least one terminal device to serve at least one target device (such as AIoT device) based on the first information. For example, the determined at least one terminal device currently can directly communicate with at least one target device (such as AIoT device).

[0284] The first network node may determine at least one terminal device based on the first information in various ways. For example, the first message may further comprise any other suitable information which can be used by the first network node to determine the at least one terminal device. For example, the selection / determination of the at least one terminal device (e g. intermediate node) can be performed based on the geographical location of the target devices (such as AIoT devices) or the identity of the intermediate node or radio condition of a candidate terminal device, etc.

[0285] The first network node may perform additional validation to assess if the received at least one candidate terminal device is optimal for serving at least one target device (such as AIoT device), e g. considering its local conditions such as response time, etc. It is also possible that the first network node does not select any of the received candidate terminal devices if selection conditions (e g. local conditions) are not satisfied.

[0286] In an embodiment, the first message may further comprise area information (e.g. intended area). In this case, the at least one terminal device may be determined further based on the area information. For example, there may be some candidate terminal devices (e.g., Intermediate UEs) in the intended area. The first network node may need to be able to determine the at least one terminal device (e.g. selecting some of them to be used). The first network node such as NG-RAN can make a decision considering other information such as the terminal device position, terminal device radio resource situation, terminal device load situation, etc., so that the selection of Intermediate nodes / UEs could be more accurate.

[0287] For example, the first network node such as NG-RAN, can make a decision considering the state of the terminal device. For example, when determining the Intermediate UE list, those RRC_CONNECTED and RRC_INACTIVE UEs can be considered by the first network node.

[0288] In an embodiment, the at least one candidate terminal device may be in a first state that a RRC connection has been established. In this case, the first network node such as NG-RAN, can make a decision considering all the at least one candidate terminal device in the first state.

[0289] In an embodiment, if a candidate terminal device is in RRC INACTIVE state, the first network node may page the candidate terminal device in RRC INACTIVE state to let the candidate terminal device in the RRC_CONNECTED state. Then block 304 may be performed.

[0290] At block 306, the first network node may send to the second network node a second message comprising information identifying the determined at least one terminal device to be used.

[0291] The second message may be any suitable message such as existing message or new message. In an embodiment, the second message may be a Determine UE Response.

[0292] The information may be any suitable information which can identify the determined at least one terminal device. For example, the information may be a list of the determined at least one terminal device.

[0293] The second message may further comprise information indicating whether the intended area can be covered by the determined at least one terminal device or a coverage area of the determined at least one terminal device or which target device (e.g. AIoT device) can be served by the determined at least one terminal device, etc.

[0294] FIG.3b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 310 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0295] At block 312, the first network node may receive from a second network node a first message comprising first information identifying at least one candidate terminal device. Block 312 is similar to block 302.

[0296] At block 314, if a part of the at least one candidate terminal device is in a second state that no RRC connection is established, the first network node may cause the part of the at least one candidate terminal device to be paged.

[0297] In an embodiment, if a part of the at least one candidate terminal device is in the second state that no RRC connection is established and a remaining part of the at least one candidate terminal device is not sufficient to cover an intended area (or for serving at least one target device (e.g. AIoT device)), the first network node may cause the part of the at least one candidate terminal device to be paged.

[0298] In a first embodiment, the first network node may send to the second network node a fourth message comprising third information identifying the part of the at least one candidate terminal device and fourth information indicating the second network node to page the part of the at least one candidate terminal device.

[0299] The fourth message may be any suitable message such as existing message or new message. In an embodiment, the fourth message may be a Determine UE Response or a page request.

[0300] The third information may be any suitable information which can identify the part of the at least one candidate terminal device. For example, the third information may be a list of the part of the at least one candidate terminal device.

[0301] The fourth information may be any suitable information which can indicate the second network node to page the part of the at least one candidate terminal device. For example, the fourth information may be a failure cause. For example, the failure cause may indicate limited candidate terminal devices in Connection Management (CM)-CONNECTED state, and optional the candidate terminal devices without terminal device contexts in the first network node such as NG- RAN.

[0302] In an embodiment, the first network node may re-receive from the second network node the first message comprising the first information identifying the at least one candidate terminal device. For example, when the page procedure is finished, or there are sufficient UEs to cover the intended area, or after a configurable period, the first network node may re-receive from the second network node the first message. Then the first network node may perform block 316.

[0303] In an embodiment, the first network node may not re-receive from the second network node the first message. In this case, the first network node may wait until the page procedure is finished or there are sufficient UEs to cover the intended area, or after a configurable period. Then the first network node may perform block 316.

[0304] In a second embodiment, the first network node may (e.g. directly) page the part of the at least one candidate terminal device. In this case, the first network node may wait until the page procedure is finished or there are sufficient UEs to cover the intended area, or after a configurable period. Then the first network node may perform block 316.

[0305] In an embodiment, the first message may further comprise information to enable the first network node to page the part of the at least one candidate terminal device. For example, the first message may further comprise any suitable information in an existing paging message as described in 3GPP TS 38.413 VI 8.1.0, the disclosure of which is incorporated by reference herein in its entirety, such as information to determine Paging Occasions, and UE Radio Capability for Paging, etc.

[0306] The candidate terminal device may perform the service request procedure in response to a reception of a page message, so that the second network node may update the state of the candidate terminal device to the first state such as CM-CONNECTED state, and the first network node such as NG-RAN may setup the candidate terminal device context.

[0307] The paging procedure may stop if there are sufficient UEs to cover the intended area, or after a configurable period.

[0308] At block 316, the first network node may determine whether at least one terminal device can be used based on the first information.

[0309] At block 318, the first network node may send to the second network node a second message comprising information identifying the determined at least one terminal device to be used.

[0310] Block 316 and 318 may be similar to blocks 304 and 306.

[0311] FIG.3c shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a first network node or communicatively coupled to the first network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 320 as well as means or modules or circuits for accomplishing other processes in conjunction with other components.For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0312] At block 322, the first network node may receive from the second network node a third message comprising second information identifying a terminal device is authorized as an intermediate terminal device which has a capability of directly communicating with an Internet of Things (loT) device.

[0313] In an embodiment, the third message may be received from the second network node during at least one of: a registration procedure, a Service Request procedure, or a Handover procedure, or a Subscriber Data Update Notification procedure.

[0314] The third message may be any suitable message such as existing message or new message. In an embodiment, the third message may be a Next Generation Application Protocol (NGAP) message from the second network node such as AMF.

[0315] In an embodiment, the second information may be authorization information of Intermediate UE for AIoT which may be stored in UE subscription data. For example, the authorization information may be same as the authorization information of Intermediate UE for AIoT of 3GPP TR 23.700-13 v0.3.0.

[0316] The first network node may receive from the second network node the authorization information in various ways such as during UE registration procedure, Service Request procedure, handover procedure (such as N2 Handover procedure, Xn Handover procedure) or Subscriber Data Update Notification procedure as described in 3GPP TS 23.502 V18.5.0).

[0317] For example, the registration procedure for UE may be performed as defined in clause4.2.2.2 of 3GPP TS 23.502 V18.5.0 with the following additions:

[0318] - UE includes the AIoT Intermediate node capability as part of “5GS mobility management (5GMM) capability” in Registration Request message.

[0319] - The AMF obtains the AIoT Subscription data as part of the user subscription data from UDM using Nudm_SDM service

[0320] - The AMF determines whether the UE is authorized to work as Intermediate UE for AIoT based on UE’s AIoT Intermediate node capability and the AIoT Subscription data. The AMF includes the authorization information as part of UE context in NGAP message sent to NG-RAN, and also in Registration Accept message towards UE.

[0321] After NG-RAN receives the authorization information in the NGAP message from the AMF that the UE authorized as an Intermediate UE, it does not release the UE to RRC IDLE state afterwards. The UE does not have to be kept in RRC CONNECTED state, and it may be released to RRC INACTIVE when needed.

[0322] For example, in Service Request procedure, N2 Handover procedure, Xn Handover procedure, and when receiving Subscriber Data Update, the AMF may include the authorization information in NGAP message sent to NG-RAN. After NG-RAN receives the authorization information, it does not release UE to RRC_IDLE state afterwards (or considers the informationand releases the UEs only if the UE is not needed for complete coverage of the Ambient loT services).

[0323] In the NGAP, the information can be provided as part of the RRC Inactive Assistance Information (as called in 3GPP TS 23.501 V18.5.0, and called " Core Network Assistance Information for RRC INACTIVE " in the 3GPP TS 38.413 VI 8.1.0) or outside that Information Element while in the same NGAP messages.

[0324] At block 324, the first network node may perform at least one of: keep the terminal device in the first state based on the second information; keep the terminal device in the second state if needed and the terminal device is not needed for a coverage of an loT service; keep the terminal device in the first state if the terminal device is in an area that it can directly communicate with an loT device; keep the terminal device in the second state if needed and the terminal device is in an area that it cannot directly communicate with an loT device; keep the terminal device in the second state if needed and another intermediate terminal device can replace the terminal device to directly communicate with an loT device; and keep the terminal device in the second state if needed and the terminal device is estimated not to directly communicate with an loT device.

[0325] In an embodiment, the terminal device does not have to be kept in RRC_CONNECTED state, and it may be released to RRC INACTIVE when needed.

[0326] FIG.4a shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 400 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0327] At block 402, the second network node may send to a first network node a first message comprising first information identifying at least one candidate terminal device.

[0328] At block 404, the second network node may receive from the first network node a second message comprising information identifying at least one terminal device which is determined based on the first information.

[0329] In an embodiment, the first message may further comprise area information.

[0330] In an embodiment, the at least one terminal device may be determined further based on at least one of: area information, a radio condition of a candidate terminal device, a position of a candidate terminal device, a radio resource situation of a candidate terminal device, a RRC connection state of a candidate terminal device, or a load situation of a candidate terminal device.

[0331] In an embodiment, the at least one candidate terminal device may be in a first state that a Radio Resource Control (RRC) connection has been established.

[0332] In an embodiment, if a part of the at least one candidate terminal device is in a second state that no RRC connection is established, the part of the at least one candidate terminal device is caused to be paged.

[0333] The second network node may send to the first network node the first message due to various reasons. For example, the second network node may receive a determine UE request comprising a list of one or more candidate terminal devices from another network node such as AF, then the second network node may send to the first network node the first message. After receiving the second message, the second network node may send a message comprising information identifying the at least one terminal device to another network node such as AF.

[0334] In an embodiment, the at least one candidate terminal device may be kept by the first network node in the first state.

[0335] In an embodiment, the at least one candidate terminal device sent by the second network node may be in the first state.

[0336] In an embodiment, the at least one candidate terminal device may have a capability of directly communicating with an loT device.

[0337] In an embodiment, the loT device may comprise an Ambient loT Device.

[0338] In an embodiment, the first state may comprise at least one of RRC CONNECTED state and RRC INACTIVE state.

[0339] In an embodiment, if a candidate terminal device is in the RRC_INACTIVE state, the candidate terminal device may be paged to let the candidate terminal device in the RRC_CONNECTED state. For example, the first network node or the second network node may page the candidate terminal device to let it in the RRC CONNECTED state.

[0340] In an embodiment, the second state may comprise a RRC IDLE state.

[0341] In an embodiment, the first network node may comprise a radio access network node.

[0342] In an embodiment, the second network node may comprise an access and mobility management node.

[0343] FIG.4b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 410 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0344] At block 412, the second network node may obtain second information identifying a terminal device is authorized as an intermediate terminal device which has a capability of directly communicating with an loT device.

[0345] At block 414, the second network node may send to the first network node a third message comprising the second information.

[0346] The second network node may obtain the second information in various ways. For example, the second network node may obtain intermediate terminal device related informationfrom at least one of the terminal device, another second network node, or subscription data of the terminal device, etc. and then determine the second information. Alternatively, the second network node may obtain the second information from another network node such as another second network node.

[0347] In an embodiment, the second network node may obtain subscription data of the terminal device e.g. from UDM / Unified Data Repository (UDR). The second network node may obtain intermediate node capability of the terminal device e.g. from the terminal device. The second network node may determine the second information based on the subscription data and the intermediate node capability.

[0348] In an embodiment, the third message may be sent to the first network node during at least one of: a registration procedure, a Service Request procedure, or a Handover procedure, or a Subscriber Data Update Notification procedure.

[0349] For example, the registration procedure may be similar to the corresponding procedure as described in clause 4.2.2.2 of 3GPP TS 23.502 V18.5.0. The service request procedure may be similar to the corresponding procedure as described in clause 4.2.3 of 3GPP TS 23.502 V18.5.0. The handover procedure may be similar to the corresponding Handover procedure (such as N2 Handover procedure or Xn Handover procedure) as described in clause 4.9.1 of 3GPP TS 23.502 V18.5.0.

[0350] For example, the terminal device may include the AIoT Intermediate node capability as part of “5GS mobility management (5GMM) capability” in Registration Request message. The second network node such as AMF may obtain the AIoT Subscription data as part of the user subscription data from UDM using Nudm_SDM service. The second network node such as AMF may determine whether the terminal device is authorized to work as Intermediate UE for AIoT based on UE’s AIoT Intermediate node capability and the AIoT Subscription data. The second network node such as AMF may include the authorization information as part of UE context in NGAP message sent to the first network node such as NG-RAN, and also in Registration Accept message towards the terminal device.

[0351] FIG.4c shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 420 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0352] At block 422, the second network node may check respective states of one or more candidate terminal devices.

[0353] For example, a list of the one or more candidate terminal devices may be received from another network node such as AF. Then the second network node may check respective states ofone or more candidate terminal devices. The second network node may store or know the respective states of one or more candidate terminal devices.

[0354] At block 424, the second network node may page at least one candidate terminal device in the second state based on a checking result.

[0355] For example, the second network node may page the terminal device using the procedure as defined in clause 4.2.3.3 of 3GPP TS 23.502 V18.5.0. The terminal device may respond to the page with Service Request procedure as defined in clause 4.2.3.3 of 3GPP TS 23.502 VI 8.5.0.

[0356] At block 426, the second network node may update the state of the at least one candidate terminal device.

[0357] For example, if the second network node such as AMF has paged the terminal device and the terminal device triggers the Service Request Procedure, the second network node such as AMF may initiate the UE configuration update procedure as defined in clause 4.2.4.2 of 3GPP TS 23.502 V18.5.0. The second network node such as AMF may update the terminal device state to CM-CONNECTED state, and the first network node such as NG-RAN setup the UE context. If the UE response in the Service Request includes a Reject Paging Indication, the AMF triggers the release of the UE as specified in clause 4.2.3.2 of 3GPP TS 23.502 V18.5.0.

[0358] At block 428, the second network node may generate the at least one candidate terminal device by removing all candidate terminal devices in the second state from the one or more candidate terminal devices.

[0359] FIG.4d shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 430 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0360] At block 432, the second network node may receive from a third network node a fifth message comprising information identifying one or more candidate terminal devices and information indicating the second network to page a terminal device in the second state.

[0361] The third network node may be deployed in any suitable network. In an embodiment, the third network node may be deployed in EPS, 5GS or 6GS as defined by 3GPP.

[0362] The third network node may be any suitable network device or network node or network function. For example, the third network node may implement loT service function.

[0363] In an embodiment, the third network node may comprise a network node supporting loT service function. For example, the third network node may be same as or similar to AIOTF as described in 3GPP TR 23.700-13 v0.3.0.

[0364] The fifth message may be any suitable message such as existing message or new message. In an embodiment, the fifth message may be an Enable Reachability Request.

[0365] The information identifying one or more candidate terminal devices may be any suitable information which can identify the one or more candidate terminal devices. For example, the information may be a list of the one or more candidate terminal devices.

[0366] The information indicating the second network to page a terminal device in the second state may be any suitable information. For example, the fifth message may be used for indicating the second network to page a terminal device in the second state.

[0367] The list of the one or more candidate terminal devices may be received by the third network node from another network node such as AF, or AF via NEF.

[0368] After receiving the fifth message, method 420 may be performed and the at least one candidate terminal device may be generated.

[0369] At block 434, the second network node may send to the third network node a sixth message comprising information identifying the at least one candidate terminal device.

[0370] The sixth message may be any suitable message such as existing message or new message. In an embodiment, the sixth message may be an Enable Reachability Response.

[0371] FIG.4e shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 440 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0372] At block 442, the second network node may receive from a third network node a seventh message comprising information identifying at least one candidate terminal device.

[0373] The seventh message may be any suitable message such as existing message or new message. In an embodiment, the seventh message may be a Determine UE request.

[0374] In an embodiment, the seventh message may further comprise area information.

[0375] In an embodiment, the at least one terminal device may be determined further based on at least one of: area information, a radio condition of a candidate terminal device, a position of a candidate terminal device, a radio resource situation of a candidate terminal device, a RRC connection state of a candidate terminal device, or a load situation of a candidate terminal device.

[0376] In an embodiment, after receiving the seventh message, method 400 may be performed or methods 400 and 420 may be performed.

[0377] In an embodiment, method 430 may be performed before method 440. In this case, method 420 may be skipped after receiving the seventh message.

[0378] At block 444, the second network node may send to the third network node an eighth message comprising information identifying the determined at least one terminal device.

[0379] The eighth message may be any suitable message such as existing message or new message. In an embodiment, the eighth message may be a Determine UE response.

[0380] FIG.4f shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a second network node or communicatively coupled to the second network node. As such, the apparatus may providemeans or modules or circuits for accomplishing various parts of the method 450 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0381] At block 452, the second network node may receive from the first network node a fourth message comprising third information identifying a part of the at least one candidate terminal device and fourth information indicating the second network node to page the part of the at least one candidate terminal device.

[0382] In an embodiment, the fourth message may comprise a failure cause.

[0383] At block 454, the second network node may page the part of the at least one candidate terminal device.

[0384] At block 456, optionally, the second network node may re-send to the first network node the first message comprising the first information identifying the at least one candidate terminal device. For example, when the page procedure is finished, or there are sufficient candidate terminal devices to cover the intended area, or after a configurable period, the second network node may re-send to the first network node the first message.

[0385] FIG.5a shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a third network node or communicatively coupled to the third network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 500 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0386] At block 502, the third network node may send to a second network node a seventh message comprising the first information identifying at least one candidate terminal device.

[0387] For example, the third network node may send to the second network node the seventh message in response to receiving an Inventory Request from an AF as described in steps 1 - 4 in Figure 6.8.2. 1-1 in Solution #8 of 3GPP TR 23.700-13 v0.3.0.

[0388] In an embodiment, the at least one candidate terminal device may be in a first state that a Radio Resource Control (RRC) connection has been established.

[0389] In an embodiment, if a part of the at least one candidate terminal device is in a second state that no RRC connection is established, the part of the at least one candidate terminal device may be caused to be paged.

[0390] In an embodiment, the at least one candidate terminal device may be kept by a first network node in the first state.

[0391] In an embodiment, the at least one candidate terminal device sent by the second network node may be in the first state.

[0392] In an embodiment, the first network node may comprise a radio access network node.

[0393] In an embodiment, the second network node may comprise an access and mobility management node.

[0394] In an embodiment, the third network node may comprise a network node supporting Internet of Things (loT) service function.

[0395] In an embodiment, the seventh message may further comprise area information.

[0396] In an embodiment, the at least one terminal device may be determined further based on at least one of: area information, a radio condition of a candidate terminal device, a position of a candidate terminal device, a radio resource situation of a candidate terminal device, a RRC connection state of a candidate terminal device, or a load situation of a candidate terminal device.

[0397] In an embodiment, the at least one candidate terminal device may have a capability of directly communicating with an loT device.

[0398] In an embodiment, the loT device may comprise an Ambient loT Device.

[0399] In an embodiment, the first state may comprise at least one of RRC CONNECTED state and RRC_INACTIVE state.

[0400] In an embodiment, if a candidate terminal device is in the RRC_INACTIVE state, the candidate terminal device may be paged to let the candidate terminal device in the RRC_CONNECTED state. For example, the first network node or the second network node may page the candidate terminal device to let it in the RRC CONNECTED state.

[0401] In an embodiment, the second state may comprise a RRC IDLE state.

[0402] At block 504, the third network node may receive from the second network node an eighth message comprising information identifying at least one terminal device which is determined based on the first information.

[0403] FIG.5b shows a flowchart of a method according to another embodiment of the present disclosure, which may be performed by an apparatus implemented in or at or as a third network node or communicatively coupled to the third network node. As such, the apparatus may provide means or modules or circuits for accomplishing various parts of the method 510 as well as means or modules or circuits for accomplishing other processes in conjunction with other components. For some parts which have been described in the above embodiments, the description thereof is omitted here for brevity.

[0404] At block 512, the third network node may send to the second network node a fifth message comprising information identifying one or more candidate terminal devices and information indicating the second network to page a terminal device in the second state.

[0405] At block 514, the third network node may receive from the second network node a sixth message comprising information identifying the at least one candidate terminal device.

[0406] In an embodiment, method 510 may be performed before method 500.

[0407] Other embodiments

[0408] In an embodiment, to resolve the issue that Intermediate UEs in RRC IDLE states cannot be utilized by the first network node such as NG-RAN when determining the Intermediate UE list, it could be solved in different ways:

[0409] Option 1: the first network node such as NG-RAN does not release those UEs to RRC_IDLE state (only release to RRC_INACTIVE state when needed)

[0410] Option 2: the second network node such as AMF pages those RRC IDLE (CM-IDLE) UEs back to CM-CONNECTED state before the first message is sent to the first network node such as NG-RAN.

[0411] Option 3: After the first network node such as NG-RAN receives the first message, if it determines the Intermediate UEs are not sufficient for the operation, it may request the second network node such as AMF to page those RRC_IDLE UEs and then try again.

[0412] In an embodiment, it proposes 3 options to enable the first network node such as NG- RAN to determine intermediate UEs in RRC IDLE states:

[0413] Option 1: when the first network node such as NG-RAN understands that the UE is an authorized Intermediate UE, the first network node such as NG-RAN does not release the UE to RRC_IDLE state. The first network node such as NG-RAN may release the UE to RRC_INACTIVE when needed.

[0414] Option 2: Before the second network node such as AMF requests the first network node such as NG-RAN to determine the Intermediate UEs, the second network node such as AMF pages those UEs in RRC IDLE state.

[0415] Option 3: After the second network node such as AMF requests the first network node such as NG-RAN to determine the Intermediate UEs, if the first network node such as NG-RAN determines the Intermediate UEs are not sufficient for the coverage of an intended area, the first network node such as NG-RAN may request the second network node such as AMF to page Intermediate UEs in RRC_IDLE state. Alternatively, the first network node such as NG-RAN may page Intermediate UEs in RRC IDLE state.

[0416] In an embodiment, a solution is proposed based on S2-2404492, but similar enhancements can be added to other similar solutions.

[0417] As shown in Inventory Procedure of FIG.2c, step 2 is to determine Intermediate UEs to be used, based on the location information for the Intermediate UEs, as well as area information provided by the AF.

[0418] As described in Periodic Inventory of S2-2404492, when the period expires in the AIOTF, the AIOTF determines the Intermediate UEs based on the area information from the AF and the location information for the Intermediate UEs. Steps 2 - 10 in FIG.2c are executed.

[0419] As shown in command procedure of FIG.2d, in step 14, it refers to step 2 - 12 in inventory procedure, and AIOTF needs to determine Intermediate UEs.

[0420] In an embodiment, the AIOTF may be located within the AMF or deployed as a separate NF.

[0421] Option 1: NG-RAN does not release Intermediate UEs to RRC_IDLE state

[0422] 6.X.2. 1 AIoT Service Authorization for Intermediate UE

[0423] The Registration procedure for UE is performed as defined in clause 4.2 2.2 of 3GPP TS 23.502 V18.5.0 with the following additions:

[0424] - UE includes the AIoT Intermediate node capability as part of “5GMM capability” in Registration Request message.

[0425] - The AMF obtains the AIoT Subscription data as part of the user subscription data from UDM using Nudm_SDM service

[0426] - The AMF determines whether the UE is authorized to work as Intermediate UE for AIoT based on UE’s AIoT Intermediate node capability and the AIoT Subscription data. The AMF includes the authorization information as part of UE context in NGAP message sent to NG-RAN, and also in Registration Accept message towards UE.

[0427] After NG-RAN receives the authorization information in the NGAP message from the AMF that the UE authorized as an Intermediate UE, it does not release the UE to RRC IDLE state afterwards. The UE does not have to be kept in RRC_CONNECTED state, it may be released to RRC_INACTIVE when needed.

[0428] FIG.6a shows a flowchart of registration procedure according to another embodiment of the present disclosure, which is similar to Figure 4.2.2.2.2-1 of 3GPP TS 23.502 V18.5.0.

[0429] In step 1 and step 3, UE includes the AIoT Intermediate node capability as part of “5GMM capability” in Registration Request message.

[0430] In step 14b, the AMF obtains the AIoT Subscription data as part of the user subscription data from UDM using Nudm SDM service.

[0431] In step 21, the AMF determines whether the UE is authorized to work as Intermediate UE for AIoT based on UE’s AIoT Intermediate node capability and the AIoT Subscription data. The AMF includes the authorization information as part of UE context in NGAP message sent to NG-RAN, and also in Registration Accept message towards UE. After NG-RAN receives the authorization information, it does not release UE to RRC IDLE state afterwards. The UE does not have to be kept in RRC CONNECTED state, it may be released to RRC_INACTIVE when needed.

[0432] The other steps have been described in clause 4 2.2.2.2 of 3GPP TS 23.502 V18.5.0, the description thereof is omitted here for brevity.

[0433] In an embodiment, in Service Request procedure, N2 Handover procedure, Xn Handover procedure as described in 3GPP TS 23.502 V18.5.0, and when receiving Subscriber Data Update from UDM, the AMF includes the authorization information in NGAP message sent to NG-RAN. After NG-RAN receives the authorization information, it does not release UE to RRC IDLE state afterwards (or considers the information and releases the UEs only if the UE is not needed for complete coverage of the Ambient loT services).

[0434] In an embodiment, in the NGAP the information can be provided as part of the RRC Inactive Assistance Information (as called in 3GPP TS 23.501 VI 8.5.0, and called " Core Network Assistance Information for RRC INACTIVE " in the 3GPP TS 38.413 V18.1.0) or outside that Information Element while in the same NGAP messages.

[0435] FIG.6b shows a flowchart of Option 1 according to another embodiment of the present disclosure.

[0436] Option 1: NG-RAN does not release Intermediate UEs to RRC_IDLE state.

[0437] Step 2a. the AIOTF generates candidate UE list based on the intended area, which is received from the AF.

[0438] Step 2b. the AIOTF sends Determine UE request to the AMF with the candidate UE list, and the intended area.

[0439] Step 2c. the AMF sends N2 Message: Determine UE request to the NG-RAN with the candidate UE list, and the intended area. It may send to multiple NG-RANs within the intended area.

[0440] Step 2d, the NG-RAN picks up the most appropriate UEs based on the candidate UE list and the intended area The NG-RAN needs to consider the location of the UE, and other aspects, e.g., the radio condition of the UE, the radio resource situation of the UE, the load situation of the UE, the spectrum support of the UE, etc., to ensure the coverage of the area with less interference among the UEs. Before determining the appropriate UEs to be used, the NG-RAN may perform RAN paging to those RRC INACTIVE UEs.

[0441] Step 2e, the NG-RAN sends N2 Message: Determine UE response to the AMF with the determined UE list.

[0442] Step 2f, the AMF aggregates the responses and sends Determine UE response to the AIOTF with the determined UE list.

[0443] After that the AIOTF sends NAS message towards those Intermediate UEs for AIoT service operations (e.g., inventory or command).

[0444] FIG.6c shows a flowchart of Option 2a according to another embodiment of the present disclosure.

[0445] Option 2a: AIOTF requests AMF to page RRC IDLE UEs

[0446] Step 2a. the AIOTF generates candidate UE list based on the intended area, which is received from the AF

[0447] Step 2b. the AIOTF sends Enable Reachability Request to the AMF with all the UEs in the candidate UE list.

[0448] Step 2c. the AMF checks the CM states of those UEs. For the UEs in CM-IDLE state, step 2d and 2e are executed.

[0449] Step 2d. The AMF pages the UEs in CM-IDLE state.

[0450] Step 2e. The UE performs the Service Request procedure, so that AMF updates its CM state to CM-CONNECTED state, and the NG-RAN setups the UE context.

[0451] Step 2f. The AMF sends Enable Reachability Response to the AIOTF with the UEs in CM-CONNECTED state.

[0452] In another option, AMF may send Enable Reachability Response to the AIOTF after step 2c, for the CM-CONNECTED UEs without paging. And in step 2f, those UEs which are paged back can be delivered to the AIOTF via Enable Reachability Notify Request.

[0453] In another option, e.g. if the AMF does not support the Enable Reachability service above, the AIOTF after step 2a sends a NAS message to each of the UEs in the candidate UE list determined in step 2a using AMF service for sending Non-Access Stratum (NAS) message to the UE e.g. Namf_Communication_NlN2MessageTransfer with information to ensure the AMF pages the UE in case the UE is in CM-IDLE e g. a suitable value set for the Paging Policy Indicator.

[0454] Step 2g. the AIOTF sends Determine UE request to the AMF with the updated candidate UE list, including the UEs in CM-CONNECTED state (i.e., remove those UEs still in RRC_IDLE state from the candidate UE list), and the intended area.

[0455] Step 2h. the AMF sends N2 Message: Determine UE request to the NG-RAN with the updated candidate UE list, and the intended area. It may send to multiple NG-RANs within the intended area.

[0456] Step 2i, the NG-RAN pick up the most appropriate UEs based on the updated candidate UE list and the intended area. The NG-RAN needs to consider the location of the UE, and other aspects, e.g., the radio condition of the UE, the radio resource situation of the UE, the load situation of the UE, the spectrum support of the UE, etc., to ensure the coverage of the area with less interference among the UEs. Before determining the appropriate UEs to be used, the NG- RAN may perform RAN paging to those RRC_INACTIVE UEs.

[0457] Step 2j, the NG-RAN sends N2 Message: Determine UE response to the AMF with the determined UE list.

[0458] Step 2k, the AMF aggregates the responses and sends Determine UE response to the AIOTF with the determined UE list.

[0459] After that the AIOTF sends NAS message towards those Intermediate UEs for AIoT service operations (e.g., inventory or command).

[0460] NOTE: in another option, the AMF may include the NG-RAN information in Enable Reachability Response / Notify together with the UEs. The AIOTF can generate N2 message towards NG-RAN directly and request AMF to deliver the N2 message via Namf_Communication_NlN2MessageTransfer.

[0461] FIG.6d shows a flowchart of Option 2b according to another embodiment of the present disclosure.

[0462] Option 2b: AMF page RRC IDLE UEs without explicit request.

[0463] Step 2a. the AIOTF generates candidate UE list based on the intended area, which is received from the AF.

[0464] Step 2b. the AIOTF sends Determine UE request to the AMF with the candidate UE list, and the intended area

[0465] Step 2c. the AMF checks the CM states of those UEs. For the UEs in CM-IDLE state, step 2d and 2e are executed.

[0466] Step 2d. The AMF pages the UEs in CM-IDLE state.

[0467] Step 2e. The UE performs the Service Request procedure, so that AMF updates its CM state to CM-CONNECTED state, and the NG-RAN setups the UE context.

[0468] Step 2f. The AMF generates the updated candidate UE list to include UEs in CM- CONNECTED state (i.e., remove those UEs still in RRC_IDLE state from the candidate UE list). The AMF sends N2 Message: Determine UE request to the NG-RAN with the updated candidate UE list, and the intended area. It may send to multiple NG-RANs within the intended area.

[0469] Step 2g, the NG-RAN picks up the most appropriate UEs based on the updated candidate UE list and the intended area. The NG-RAN needs to consider the location of the UE, and other aspects, e.g., the radio condition of the UE, the radio resource situation of the UE, the load situation of the UE, the spectrum support of the UE, etc., , to ensure the coverage of the area with less interference among the UEs. Before determining the appropriate UEs to be used, the NG- RAN may perform RAN paging to those RRC IN ACTIVE UEs.

[0470] In another option, in step 2f, the AMF may send the candidate UE list to the NG-RAN (including UEs in CM-CONNECTED and / or CM-IDLE states), and in step 2g, the NG-RAN ignore those UEs in CM-IDLE state, due to lacking of UE contexts. Or as an option, the NG-RAN uses the N2 message as a paging message and initiates paging for the UEs listed as being in CM- IDLE.

[0471] Step 2h, the NG-RAN sends N2 Message: Determine UE response to the AMF with the determined UE list.

[0472] Step 2i, the AMF aggregates the responses and sends Determine UE response to the AIOTF with the determined UE list.

[0473] After that the AIOTF sends NAS message towards those Intermediate UEs for AIoT service operations (e.g., inventory or command).

[0474] FIG.6e shows a flowchart of Option 3a according to another embodiment of the present disclosure.

[0475] Option 3a: NG-RAN triggers the paging for RRC_IDLE UEs via core network (CN).

[0476] Step 2a. the AIOTF generates candidate UE list based on the intended area, which is received from the AF.

[0477] Step 2b. the AIOTF sends Determine UE request to the AMF with the candidate UE list, and the intended area.

[0478] Step 2c. the AMF sends N2 Message: Determine UE request to the NG-RAN with the candidate UE list, and the intended area. It may send to multiple NG-RANs within the intended area.

[0479] Step 2d. the NG-RAN picks up the most appropriate UEs based on the candidate UE list and the intended area The NG-RAN needs to consider the location of the UE, and other aspects, e.g., the radio condition of the UE, the radio resource situation of the UE, the load situation of the UE, the spectrum support of the UE, etc., , to ensure the coverage of the area with less interference among the UEs. Before determining the appropriate UEs to be used, the NG-RAN may perform RAN paging to those RRC INACTIVE UEs.

[0480] If NG-RAN fails due to limited UEs in RRC CONNECTED, then NG-RAN pages the appropriate UEs in RRC INACTIVE (not shown in the figure) and determines whether these are enough to ensure the coverage of intended area. If the UEs are not sufficient to cover the intended area, step 2e to step 2j are executed as to get also UEs in CM-IDLE into RRC_CONNECTED state.

[0481] Step 2e. the NG-RAN sends N2 Message: Determine UE response to the AMF. The failure cause indicate limited UEs in CM-CONNECTED state, and optional the UEs without UE contexts in NG-RAN

[0482] Step 2f. The AMF pages the UEs in CM-IDLE state.

[0483] Step 2g. The UE performs the Service Request procedure, so that AMF updates its CM state to CM-CONNECTED state, and the NG-RAN setups the UE context.

[0484] Step 2h - 2i. the AMF triggers the NG-RAN to determine again as step 2c - 2d.

[0485] Step 2j, the NG-RAN sends N2 Message: Determine UE response to the AMF with the determined UE list.31

[0486] Step 2k, the AMF aggregates the responses and sends Determine UE response to the AIOTF with the determined UE list.

[0487] After that the AIOTF sends NAS message towards those Intermediate UEs for AIoT service operations (e.g., inventory or command).

[0488] NOTE: as another option, in step 2e, NG-RAN may send another N2 message (e g. Page UE Request) to the AMF with the UEs without UE context, and in step 2h, the AMF may use another N2 message (e.g. Page UE Response) to the NG-RAN.

[0489] FIG.6f shows a flowchart of Option 3b according to another embodiment of the present disclosure.

[0490] Option 3b: NG-RAN triggers the paging for RRC IDLE or RRC INACTIVE UEs directly.

[0491] Step 2a. the AIOTF generates candidate UE list based on the intended area, which is received from the AF.

[0492] Step 2b. the AIOTF sends Determine UE request to the AMF with the candidate UE list, and the intended area.

[0493] Step 2c. the AMF sends N2 Message: Determine UE request to the NG-RAN with the candidate UE list, and the intended area. For those CM-IDLE UEs, information to determine Paging Occasions, and UE Radio Capability for Paging if stored in AMF are also included (as per existing Paging message in 3GPP TS 38.413 V18.1.0). It may send to multiple NG-RANs within the intended area.

[0494] Step 2d. the NG-RAN picks up the most appropriate UEs based on the candidate UE list and the intended area The NG-RAN needs to consider the location of the UE, and other aspects, e.g., the radio condition of the UE, the radio resource situation of the UE, the load situation of the UE, the spectrum support of the UE, etc., , to ensure the coverage of the area with less interference among the UEs. Before determining the appropriate UEs to be used, the NG-RAN may perform RAN paging to those RRC INACTIVE UEs.

[0495] If NG-RAN fails due to limited UEs in RRC CONNECTED state the NG-RAN performs RAN Paging for the UE in RRC_INACTIVE state to get them into RRC_CONNECTED and get their location, and if there are still not sufficient UEs to cover the intended area, step 2e to step 2j are executed.

[0496] Step 2e. the NG-RAN pages RRC_INACTIVE UEs and determines if they are enough to complete the request (not shown in the figure) and if not enough the NG-RAN pages RRC_IDLE UEs using the Paging Occasion information and intended area provided in step 2c.

[0497] Step 2f The UE performs the Service Request procedure, so that AMF updates its CM state to CM-CONNECTED state, and the NG-RAN setups the UE context.

[0498] Step 2g. The NG-RAN constantly evaluate whether there are sufficient UEs to cover the intended area when more and more UEs are moved from RRC IDLE to RRC CONNECTED state. Step 2f-2g may be repeated till there are sufficient UEs to cover the intended area, or after a configurable period, NG-RAN stops waiting and return the best result (i.e., the current determined UE list even though those UEs cannot cover the intended area).

[0499] Step 2h, the NG-RAN sends N2 Message: Determine UE response to the NG-RAN with the determined UE list, e

[0500] Step 2i, the AMF aggregates the responses and sends Determine UE response to the AIOTF with the determined UE list.

[0501] After that the AIOTF sends NAS message towards those Intermediate UEs for AIoT service operations (e.g., inventory or command).

[0502] Embodiments herein may provide many advantages, of which a non-exhaustive list of examples follows. In some embodiments herein, the proposed solution can avoid Intermediate UEs in RRC_IDLE state when the first network node such as NG-RAN determines Intermediate UEs. In some embodiments herein, the proposed solution can enable the first network node such as NG-RAN to make a correct decision and possible enable a better coverage for a service such as AIoT service. The embodiments herein are not limited to the features and advantages mentioned above. A person skilled in the art will recognize additional features and advantages upon reading the following detailed description.

[0503] FIG.7 is a block diagram showing an apparatus suitable for practicing some embodiments of the disclosure. For example, the first network node, the second network node or the third network node described above may be implemented as or through the apparatus 700.

[0504] The apparatus 700 comprises at least one processor 721, such as a digital processor (DP), and at least one memory (MEM) 722 coupled to the processor 721. The apparatus 700 may comprise a transmitter TX and receiver RX 723 coupled to the processor 721. The MEM 722 stores a program (PROG) 724. The PROG 724 may include instructions that, when executed on the associated processor 721, enable the apparatus 700 to operate in accordance with the embodiments of the present disclosure. A combination of the at least one processor 721 and the at least one MEM 722 may form processing means 725 adapted to implement various embodiments of the present disclosure.

[0505] Various embodiments of the present disclosure may be implemented by computer program executable by one or more of the processor 721, software, firmware, hardware or in a combination thereof.

[0506] The MEM 722 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memories and removable memones, as non-limiting examples.

[0507] The processor 721 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples

[0508] In an embodiment where the apparatus is implemented as or at the first network node, the memory 722 contains instructions executable by the processor 721, whereby the first network node operates according to any of the methods performed by the first network node as described above.

[0509] In an embodiment where the apparatus is implemented as or at the second network node, the memory 722 contains instructions executable by the processor 721, whereby the second network node operates according to any of the methods performed by the second network node as described above.

[0510] In an embodiment where the apparatus is implemented as or at the third network node, the memory 722 contains instructions executable by the processor 721, whereby the third network node operates according to any of the methods performed by the third network node as described above.

[0511] Further, the exemplary overall commutation system including the terminal device and the network node (such as the first network node, the second network node or the third network node) will be introduced as below.

[0512] FIG. 8 shows an example of a communication system 800 in accordance with some embodiments.

[0513] In the example, the communication system 800 includes a telecommunication network 802 that includes an access network 804, such as a radio access network (RAN), and a core network 806, which includes one or more core network nodes 808. The access network 804 includes one or more access network nodes, such as network nodes 810a and 810b (one or more of which may be generally referred to as network nodes 810), or any other similar 3rd Generation Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 802 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 802, including one or more network nodes 810 and / or core network nodes 808.

[0514] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU- CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or anon-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an O-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes 810 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 812a, 812b, 812c, and 812d (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections.

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

[0516] The UEs 812 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 810 and other communication devices. Similarly, the network nodes 810 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 812 and / or with other network nodes or equipment in the telecommunication network 802 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 802.

[0517] In the depicted example, the core network 806 connects the network nodes 810 to one or more host computing systems, such as host 816. 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 806 includes one more core network nodes (e.g., core network node 808) 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 808. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

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

[0519] As a whole, the communication system 800 of FIG. 8 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 Microwave 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.

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

[0521] In some examples, the UEs 812 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 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804. Additionally, a UE may be configured for operating in single- or multi-RAT or multi -standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

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

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

[0524] FIG. 9 shows a UE 900 in accordance with some embodiments. The UE 900 presents additional details of some embodiments of the UE 812 of FIG. 8. 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 / playback device, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), an Augmented Reality (AR) or Virtual Reality (VR) device, wireless customer-premise equipment (CPE), vehicle, 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-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0525] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP 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).

[0526] The UE 900 includes processing circuitiy 902 that is operatively coupled via a bus 904 to an input / output interface 906, a power source 908, a memory 910, a communication interface 912, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 9. 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.

[0527] The processing circuitry 902 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 910. The processing circuitry 902 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 902 may include multiple central processing units (CPUs).

[0528] In the example, the input / output interface 906 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 900. 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.

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

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

[0531] The memory 910 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 m-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integratedUICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 910 may allow the UE 900 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 910, which may be or comprise a device-readable storage medium.

[0532] The processing circuitry 902 may be configured to communicate with an access network or other network using the communication interface 912. The communication interface 912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 922. The communication interface 912 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 918 and / or a receiver 920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 918 and receiver 920 may be coupled to one or more antennas (e.g., antenna 922) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0533] In the illustrated embodiment, communication functions of the communication interface 912 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 / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0534] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 912, 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 eveiy 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).

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

[0536] 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 wearabletechnology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. 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 900 shown in FIG. 9.

[0537] 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-IoT 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.

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

[0539] FIG. 10 shows a network node 1000 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)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0540] 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, distributed units (e.g., in an O-RAN access node) and / or remote radiounits (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).

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

[0542] The network node 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008. The network node 1000 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 1000 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 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, 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 1000.

[0543] The processing circuitry 1002 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 1000 components, such as the memory 1004, to provide network node 1000 functionality.

[0544] In some embodiments, the processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the radio frequency (RF) transceiver circuitry 1012 and the baseband processing circuitry 1014 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 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.

[0545] The memory 1004 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mountedmemory, 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 1002. The memory 1004 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 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 is integrated.

[0546] The communication interface 1006 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 1006 comprises port(s) / terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. The communication interface 1006 also includes radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, the antenna 1010. Radio front-end circuitry 1018 comprises filters 1020 and amplifiers 1022. The radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002. The radio front-end circuitry 1018 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio frontend circuitry 1018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1020 and / or amplifiers 1022. The radio signal may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed to the processing circuitry 1002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0547] In certain alternative embodiments, the network node 1000 does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitiy and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).

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

[0549] The antenna 1010, communication interface 1006, and / or the processing circuitry 1002 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 1010, the communication interface 1006, and / or the processing circuitry 1002 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.

[0550] The power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein. For example, the network node 1000 may be connectable to an external power source (e g., the power grid, an electricity outlet) via an input circuity or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1008. As a further example, the power source 1008 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.

[0551] Embodiments of the network node 1000 may include additional components beyond those shown in FIG. 10 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000. In some embodiments providing a core network node, such as core network node 108 of FIG. 8, some components, such as the radio front-end circuitry 1018 and the RF transceiver circuitry 1012 may be omitted.

[0552] FIG. 11 is a block diagram illustrating a virtualization environment 1100 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 1100 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. In some embodiments, the virtualization environment 1100 includes components defined by the O-RAN Alliance, such as an O-Cloud environmentorchestrated by a Service Management and Orchestration Framework via an 0-2 interface. Virtualization may facilitate distributed implementations of a network node, UE, core network node, or host.

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

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

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

[0556] In the context of NFV, a VM 1108 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 1108, and that part of hardware 1104 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 1108 on top of the hardware 1104 and corresponds to the application 1102.

[0557] Hardware 1104 may be implemented in a standalone network node with generic or specific components. Hardware 1104 may implement some functions via virtualization. Alternatively, hardware 1104 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 1110, which, among others, oversees lifecycle management of applications 1102. In some embodiments, hardware 1104 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, somesignaling can be provided with the use of a control system 1112 which may alternatively be used for communication between hardware nodes and radio units.

[0558] Although the computing devices described herein (e.g., UEs, network nodes) 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.

[0559] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memoiy, 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.

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

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

[0562] The term unit or module may have conventional meaning in the field of electronics, electrical devices and / or electronic devices and may include, for example, electncal and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and / or displaying functions, and so on, as such as those that are described herein.

[0563] According to an aspect of the disclosure it is provided a computer program product being tangibly stored on a computer readable storage medium and including instructions which, when executed on at least one processor, cause the at least one processor to carry out any of the methods as described above.

[0564] According to an aspect of the disclosure it is provided a computer-readable storage medium storing instructions which when executed by at least one processor, cause the at least one processor to carry out any of the methods as described above.

[0565] In addition, the present disclosure may also provide a carrier containing the computer program as mentioned above, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium. The computer readable storage medium can be, for example, an optical compact disk or an electronic memory device like a RAM (random access memory), a ROM (read only memory), Flash memory, magnetic tape, CD-ROM, DVD, Blue-ray disc and the like.

[0566] The techniques described herein may be implemented by various means so that an apparatus implementing one or more functions of a corresponding apparatus described with an embodiment comprises not only prior art means, but also means for implementing the one or morefunctions of the corresponding apparatus described with the embodiment and it may comprise separate means for each separate function, or means that may be configured to perform two or more functions. For example, these techniques may be implemented in hardware (one or more apparatuses), firmware (one or more apparatuses), software (one or more modules), or combinations thereof. For a firmware or software, implementation may be made through modules (e.g., procedures, functions, and so on) that perform the functions described herein.

[0567] Exemplary embodiments herein have been described above with reference to block diagrams and flowchart illustrations of methods and apparatuses. It will be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by various means including computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus create means for implementing the functions specified in the flowchart block or blocks.

[0568] 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 subject matter described herein, 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.

[0569] While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any implementation or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular implementations. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

[0570] It will be obvious to a person skilled in the art that, as the technology advances, the inventive concept can be implemented in various ways. The above described embodiments are given for describing rather than limiting the disclosure, and it is to be understood that modifications and variations may be resorted to without departing from the spirit and scope of the disclosure as those skilled in the art readily understand. Such modifications and variations areconsidered to be within the scope of the disclosure and the appended claims. The protection scope of the disclosure is defined by the accompanying claims.

[0571] The abbreviations given in 3GPP TR 21.905 VI 8.0.0 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 V18.0.0.AIoT Ambient loTDO-A Device-originated - autonomousDO-DTT Device-originated - device-terminated triggeredDT Device-terminatedEPC Electronic Product CodeRFID Radio-Frequency IDentification

[0572] In an embodiment, it will provide KI #1, #2, #3, New Solution: Support AIoT Devices for Topology 2 using AIOTF to a 3 GPP meeting as below.Abstract of the contribution: The contribution discusses and proposes anew solution for supporting AIOT Devices for Topology 2 using AIOTF, which works together with Solution #8 which focuses on Topology 1. It was S2-2404492 in SA2 162.1. IntroductionAmbient loT devices are loT devices powered by energy harvesting, being either battery-less or with limited energy storage capability (e g. using a capacitor). It can have, e.g., lower complexity, smaller size, reduced capabilities and lower power consumption than previously defined 3GPP loT devices. The data rate of Ambient loT devices is usually low.Solution#8 “Inventory for AIoT Devices using AIOTF” was included in the TR 23.700-13 in SA2 161. In this solution, the system architecture and the solution for topology 1 are described.This pCR proposes an aligned solution to enable the support of Ambient loT devices for topology 2.Update in SA2 163:Step 2 in clause 6.X.2.3 is to let AIOTF determine Intermediate UEs based on UE location and the area information provided by AF.When determining Intermediate UEs, AIOTF is not aware of the CM state of the Intermediate UEs. In case Intermediate UEs are in CM-IDLE state, the location information may not be accurate. Some Intermediate UEs may move out from the intended area, so that they cannot be used as Intermediate UEs for the AF request.[Proposal-1] NG-RAN does not release authorized Intermediate UEs to RRC_IDLE state, to ensure that AIOTF can determine Intermediate UEs properly.There is an EN in step 2:AIOTF is aware of the location information of the Intermediate UEs, so AIOTF can choose the candidate Intermediate UEs. However, as NG-RAN understands UE better on the aspects likeUE radio condition, NG-RAN can make the further optimization in determining Intermediate UEs, to ensure larger coverage and less interference.[Proposal-2] Involve NG-RAN in the determining Intermediate UEs.2. ProposalIt is proposed to agree the following changes to 3GPP TR 23.700-13 v0.2.0:6.0 Mapping of Solutions to Key IssuesTable 6.0-1: Mapping of Solutions to Key Issues6.X Solution #X: Support AIoT Devices using AIOTF for Topology 26.X. 1 DescriptionThis solution proposes a complementary solution to Solution #8. It enables the support of Ambient loT devices for topology 2, which addresses KI#1, KJ#2 and KI#3. Together with Solution #8 which focus on Topology 1, the solutions can support AIoT devices for both Topologies.In this solution, it is AIOTF who is in charge of the intermediate UE for the Ambient loT operations, including determining intermediate UEs, sending operation commands to and receiving results from intermediate UEs. As the licensed spectrum is owned by MNO, it is proposed to let network provide the radio resource information towards the intermediate UEs about the spectrum information for the over-the-air interface between Intermediate UEs and AIoT devices.6. X. 1. 1 Reference ArchitectureFIG.2a illustrates the architecture for supporting AIoT Devices using AIOTF for Topology 2: This solution focuses on Topology 2, which works together with Solution #8 addressing Topology 1.The functional entities defined in Solution #8 and TS 23.501 [4] are reused with the exception for the following additions:- UDM / UDR: The authorization information of Intermediate UE for AIoT is stored in UE subscription data- AMF: Receive AIoT capability information from UE and authorize based on the subscription data in UDM / UDR.- NG-RAN: Provide spectrum information towards authorized intermediate UE.- Intermediate UE:- Provide Ambient loT capability information to AIOTF and receive the authorization informationReceive the instruction from AIOTF and perform Ambient loT operations (e.g., inventory, command, etc.) on the proper spectrum. The radio resource information is received from NG-RAN- Ambient loT Function (AIOTF): AIOTF is introduced to support AIoT services, with some AMF's functionalities integrated, which includes:- Inventory handling and device context management.- Command delivery.- Authentication and authorization for the access, which triggers interaction with AUSF / UDM.- Collect charging data and interact with CHF for charging.- Routing the request from AF (via NEF) to Intermediate UEs, for DO-DTT / DT traffic types.- Routing the response from Intermediate UEs to AF (via NEF) for DO-DTT traffic type.6.X.1.2 Protocol StackFIG.2c illustrates the protocol stack for AF based solution:Within the protocol stack, the AIOT Device NAS layer, AIOT AS layer and App layer are defined as Solution #8.As UE reader is used in Topology 2, which is different form the RAN reader in Topology 1 , the following layer is proposed specific in this solution:-AIOT UE NAS layer: The NAS protocol between AIOTF and UE readers. Besides the 5GMM NAS and 5GSM NAS, it can be defined as a new NAS (e.g. 5GAIOT NAS) which is piggybacked in 5GMM NAS transport messages.6.X.2 ProceduresNOTE: The message names in the procedures below are descriptive. It is assumed that the names are updated with corresponding SBI based names where applicable during the normative phase.6.X.2.1 AIoT Service Authorization for Intermediate UEThe Registration procedure for UE is performed as defined in clause 4.2.2.2 of TS 23.502 with the following additions:- UE includes the AIoT Intermediate node capability as part of “5GMM capability” in Registration Request message.- The AMF obtains the AIoT Subscription data as part of the user subscription data from UDM using Nudm_SDM service- The AMF determines whether the UE is authorized to work as Intermediate UE for AIoT based on UE’s AIoT Intermediate node capability and the AIoT Subscription data. The AMF includes the authorization information as part of UE context in NGAP message sent to NG-RAN.In Service Request procedure, N2 Handover prodcure, Xn Handover procedure, and when receiving Subscriber Data Update to AMF, the AMF includes the authorization information in NGAP message sent to NG-RAN.After NG-RAN receives the authorization information in the NGAP message from the AMF that the UE authorized as an Intermediate UE, it does not release the UE to RRC_IDLE state afterwards. The UE can be released to RRC INACTIVE when needed.6.X.2.2 AIOTF Keep Track of Intermediate UEFor authorized Intermediate UEs (Those Ambient loT Capable UEs which have been authorized by the AMF as described in clause 6.X.2. 1), in Initial Registration procedure as defined in clause 4.2.2.2 of TS 23.502 [5] with the following additions:- The AMF sends Registration Request to the AIOTF for the Intermediate UE, so that the AIOTF may select the Intermediate UE for AIoT operations.In Deregistration procedure as defined in clause 4.2.2.3 of TS 23.502 [5], the following additions are performed:- The AMF sends Deregistration Request to the AIOTF for the Intermediate UE, so that the Intermediate UE will no longer be used.The AIOTF can subscribe the UE mobility event of the Intermediate UE towards the AMF to be updated for the location information.6.X.2.3 Application Inventory ProcedureThe Inventory procedure can be initiated by the AF to discover one or more AIoT devices in a specific area via Intermediate UEs.FIG.12 shows Inventory Procedure according to another embodiment of the present disclosure.1. AF sends Inventory Request to the AIOTF, which is the same as step 1 - 4 in Figure 6.8.2. 1-1 in Solution #8.2a. The AIOTF generates the candidate UE list for the Intermediate UEs to be used, based on the location information for the Intermediate UEs, as well as area information provided by the AF.2b. The AIOTF sends Determine UE Request to the AMF with the candidate UE list and the area information.2c. The AMF sends N2 message: Determine UE Request to the NG-RAN with the candidate UE list and the area information. The AMF may send to multiple NG-RANs within the area.2d. The NG-RAN selects the most appropriate UEs based on the candidate UE list and the area info. The NG-RAN needs to consider the location of the UE, and other aspects, e.g., the radio condition of the UE, the radio resource situation of the UE, the load situation of the UE, the spectrum support of the UE, etc., , to ensure the coverage of the area with less interference among the UEs. Before determining the appropriate UEs to be used, the NG-RAN may perform RAN paging to those RRC_INACTIVE UEs.2e. The NG-RAN sends N2 Message: Determine UE response to the AMF with the determined UE list.2f. The AMF aggregates the responses and send Determine UE response to the AIOTF with the determined UE list3. The AIOTF creates and sends the 5GAI0T NAS message to request the Intermediate UE in the determined UE list to perform the Inventory. The 5GAI0T NAS message is delivered via the AMF and the NG-RAN.4. The Intermediate UE determines radio resource or requests NG-RAN to determine radio resource, which is used between AIoT Devices and Intermediate UE.5. The Intermediate UE initiates inventory based on device information as well as the inventory strategy information provided by the AF. The Intermediate UE may provide reader identity information to enable the AIoT devices to understand they are read by which Intermediate UE. Considering the mobility of the Intermediate UE, the reader identity information can be a combination of a UE ID and the location information.6. The AIoT Device reports the device ID to the Intermediate UE. If the Inventory procedure indicates delta inventory only, and the AIoT Device has performed the inventory procedure towards this reader, it should skip the reporting. The device capability index can be provided by AIoT device optionally.7. The Intermediate UE creates the 5GAI0T NAS message and sends it towards the AIOTF, including the AIoT Device ID and optional device capability index. The Intermediate UE may further provide location information (ULI) of the device, if requested from the AIOTF and allowed by local policy. The Intermediate UE may further provide an end indicator to inform the AIOTF whether it is the last inventory response for the inventory round.8. The AIOTF validates the concealed device ID via interacting with AUSF and UDM. The AIOTF may further get the device capability information from the device capability profile stored in the UDM based on the device capability index provided by the device.9. The AIOTF together with AUSF and UDM, triggers authentication and authorization procedures (i.e. , like the authentication request / response between UE and network) towards the AIoT device. In Topology 2, the message between the AIOTF and the AIOT device is transmitted via the Intermediate UE over 5GAIOT NAS.Based on the device capability information from UDM, if the AIoT device is capable of persistent received parameters, step 10 - step 11 are executed:10. The security mode negotiation and security parameter exchanges are performed (i.e., like the security mode command / complete between UE and network). In Topology 2, the message between the AIOTF and the AIOT device is transmitted via the Intermediate UE over 5GAIOT NAS.11. The AIOTF may further allocates CN device ID and sends to the AIoT device.12. The AIOTF registers with the UDM (UECM) for the device access.13. The AIOTF may further aggregate the reported device IDs and send to AF via the NEF, as step 14 - 16 in Figure 6.8.2. 1-1.6.X.2.4 Periodic InventoryThe periodic inventory may be requested by the AF, so that network can trigger the inventory periodically without the request from the AF directly.Considering the movement of the Intermediate UE, and the inventory is based on area information, the periodic inventory should be initiated by the CN (i.e., the AIOTF), which follows the instructions from the AF. When the period expires in the AIOTF, the AIOTF determines the Intermediate UEs based on the area information from the AF and the location information for the Intermediate UEs. Steps 2-10 in FIG. 12 are executed.6.X.2.5 Command ProcedureThe command procedure is initiated by the AF to request one or more specific AIoT devices or a group of AIoT devices in an area to execute the command. The command can be read, write, enable, disable, or execution request from the AF. The command result from the devices may or may not be required.FIG. 13 shows Command Procedure according to another embodiment of the present disclosure.1. The AF sends Command Request to the NEF, containing the command to be executed, area information, device information, optional inventory strategy information, and optional report aggregation info.- The command is to be executed in the AIoT devices. It contains the command (e.g., read, write, execute, etc.) together with the command parameters. The command specific parameters (e.g. what to be executed) are to be included in an app layer container between AF and AIOT devices.- The area information could be the external geographical area information.- The device information could be device ID, device group ID, and / or external device type.- The location required indicates whether the AF requests the location information of the AIoT devices provided.- The report aggregation info indicates whether the reports need to be aggregated or not for a specific aggregation period, and whether the reports are needed after the aggregation period.2. The NEF authorizes the request from the AF and perform the area translation to translate external area information to the internal area information. Within the authorization, the NEF further check whether the AF is authorized to get the location information of the device. The NEF map the external device type to internal device type (i.e., device 1, device 2a, device 2b, etc.)Depending on whether area information is provided, step 3a or step 3b is performed:3a. If area information is provided, the NEF sends NRF query with internal area information to query AIOTFs serving the area.3b. If area information is not provided, and device ID(s) are provided, the NEF query the serving AIOTF from UDM.4. The NEF sends the Command Request to the AIOTFs with the command, internal area information, device information, device type, and optional location required information.5. The AIOTF allocates a Transaction ID for the command, which is unique per command. The AIOTF creates the AIOT Device NAS request message for the devices, based on the command information from the AF. The AIOTF get the registered devices, which match the device information. If no registered devices, step 6 - 13 are skipped.6. The AIOTF creates the 5GAIOT NAS request message and sends to the Intermediate UE to deliver the Command. The 5GAIOT NAS request message containsthe AIOT Device NAS message, CN allocated device IDs for the registered devices, the Transaction ID, and optional location required information. The 5GAI0T NAS message is delivered via the AMF and the NG-RAN.7. The Intermediate UE determines radio resource or requests NG-RAN to determine radio resource, which is used between AIoT Devices and Intermediate UE.8. The Intermediate UE initiates command delivery for the AIOT Device NAS request message based on CN allocated device IDs, using dedicated signalling. Transaction ID is also included.9. The AIoT Device executes the command, creates an AIOT Device NAS response message containing the command result and delivers the AIOT Device NAS response message, if the result needs to be sent back. The application specific result can be included in an app layer container.10. The Intermediate UE creates the 5GAIOT NAS response message, including the AIOT Device NAS response message, and sends to the AIOTF. The Intermediate UE may further provide location information (ULI) of the device, if requested from the AIOTF and allowed by local policy. The 5GAIOT NAS message is delivered via the NG-RAN and the AMF.11. The AIOTF gets the command result from the AIOT Device NAS response message. The AIOTF may perform aggregation for the device ID, based on the report aggregation information provided by the AF. Within the aggregation period, the AIOTF will buffer the command results reported from the AIoT devices. The AIOTF may stop buffering and send report immediately, if it receives end indicator from the Intermediate UE in step 10. When the aggregation period expires, the AIOTF sends the report. For those command result after the aggregation period, if it is needed by the AF, the AIOTF sends the report. Otherwise, it will be dropped.12. The AIOTF sends Command Response or Notification Request towards the NEF for the command result or the aggregated command result information.13. The NEF sends Command Response or Notification Request towards the AF for the command result or the aggregated command result information.If the AIOTF determines all required devices have executed the command (e.g. when AF provide the device ID(s) and those devices have executed the command in step 7 - 8), the following steps are skipped.14. For those unregistered devices(s), the AIOTF initiate Inventory procedure as steps 2a - 12 in FIG.12 (steps 11 - 12 will be skipped, if the device is not able to persistent received information). In the inventory the Transaction ID is delivered, so that the registered devices which have executed command do not respond this inventory request from the Intermediate UE.15. The AIOTF creates the 5GAIOT NAS request message and sends to the Intermediate UE to deliver the Command to the responded device. The 5GAI0T NAS request message contains the AIOT Device NAS request message, AIoT device ID and optional location required information. The 5GAI0T NAS request message is delivered via the AMF and the NG-RAN.16. The Intermediate UE determines radio resource or requests NG-RAN to determine radio resource, which is used between AIoT Devices and Intermediate UE.17. The Intermediate UE initiates command delivery for the AIOT Device NAS request message to the device.18. The AIoT Device executes the command, creates an AIOT Device NAS response message containing the command result and delivers the AIOT Device NAS response message, if the result needs to be sent back. The application specific result can be included in an app layer container.19. The Intermediate UE creates the 5GAI0T NAS response message, including the AIoT Device NAS response message, and sends to the AIOTF. The Intermediate UE may further provide location information (ULI) of the device, if requested from the AIOTF and allowed by local policy. The 5GAI0T NAS message is delivered via the NG-RAN and the AMF.20. As step 11 - 13, the AIOTF get the command result from the AIOT Device NAS response message. It may perform the aggregation and send to NEF. The NEF delivers to the AF.6.X.3 Impacts on services, entities and interfaces

Claims

WHAT IS CLAIMED IS:

1. A method (300) performed by a first network node, comprising: receiving (302, 312) from a second network node a first message comprising first information identifying at least one candidate terminal device; determining (304, 316) whether the at least one candidate terminal device can be used based on the first information; and sending (306, 318) to the second network node a second message comprising information identifying the at least one candidate terminal device determined to be used, wherein the at least one candidate terminal device is in a first state that a Radio Resource Control (RRC) connection has been established, or wherein a part of the at least one candidate terminal device is in a second state that no RRC connection is established, and the part of the at least one candidate terminal device is to be paged.

2. The method according to claim 1, wherein the at least one candidate terminal device is kept by the first network node in the first state, or the at least one candidate terminal device identified by the information comprised in the first message is in the first state.

3. The method according to claim 1 or 2, further comprising: receiving (322) from the second network node a third message comprising second information identifying a terminal device is authorized as an intermediate terminal device which has a capability of directly communicating with an Internet of Things (foT) device; and performing (324) at least one of: keeping the terminal device in the first state based on the second information; keeping the terminal device in the second state if needed and the terminal device is not needed for a coverage of an loT service; keeping the terminal device in the first state if the terminal device is in an area that it can directly communicate with an loT device; keeping the terminal device in the second state if needed and the terminal device is in an area that it cannot directly communicate with an loT device; keeping the terminal device in the second state if needed and another intermediate terminal device can replace the terminal device to directly communicate with an loT device; and keeping the terminal device in the second state if needed and the terminal device is estimated not to directly communicate with an loT device.

4. The method according to claim 3, wherein the third message is received from the second network node during at least one of: a registration procedure, a Service Request procedure, a Handover procedure, and a Subscriber Data Update Notification procedure.

5. The method according to any of claims 1-4, wherein the first message further comprises area information and / or the at least one terminal device is determined further based on at least one of: the area information, a radio condition of a candidate terminal device, a position of a candidate terminal device, a radio resource situation of a candidate terminal device, a RRC connection state of a candidate terminal device, or a load situation of a candidate terminal device.

6. The method according to any of claims 1-5, wherein that the part of the at least one candidate terminal device is to be paged comprises: if a remaining part of the at least one candidate terminal device is not sufficient to cover an intended area, the part of the at least one candidate terminal device is to be paged.

7. The method according to claim 6, wherein that the part of the at least one candidate terminal device is to be paged further comprises: sending to the second network node a fourth message comprising third information identifying the part of the at least one candidate terminal device and fourth information indicating the second network node to page the part of the at least one candidate terminal device.

8. The method according to claim 7, further comprising: re-receiving from the second network node the first message comprising the first information identifying the at least one candidate terminal device, wherein the fourth message comprises a failure cause.

9. The method according to any of claims 1-8, if a part of the at least one candidate terminal device is in a second state that no RRC connection is established, and the part of the at least one candidate terminal device is to be paged, the method further comprises: paging the part of the at least one candidate terminal device, wherein the first message further comprises information to enable the first network node to page the part of the at least one candidate terminal device.

10. The method according to any of claims 1-9, wherein the at least one candidate terminal device has a capability of directly communicating with an Internet of Things (loT) device.

11. The method according to claim 10, wherein the loT device comprises an Ambient loT Device.

12. The method according to any of claims 1-11, wherein the first state comprises at least one of RRC_CONNECTED state and RRC INACTIVE state, wherein if a candidate terminal device is in the RRC_INACTIVE state, the candidate terminal device is paged to be kept in the RRC_CONNECTED state, and / or the second state comprises an RRC IDLE state.

13. The method according to any of claims 1-12, wherein the first network node comprises a radio access network node, and / or the second network node comprises an access and mobility management node.

14. A method (400) performed by a second network node, comprising: sending (402) to a first network node a first message comprising first information identifyingat least one candidate terminal device; and receiving (404) from the first network node a second message comprising information identifying at least one terminal device which is determined based on the first information, wherein the at least one candidate terminal device is in a first state that a Radio Resource Control (RRC) connection has been established, or wherein a part of the at least one candidate terminal device is in a second state that no RRC connection is established, and the part of the at least one candidate terminal device is to be paged.

15. The method according to claim 14, further comprising: obtaining (412) second information identifying a terminal device is authorized as an intermediate terminal device which has a capability of directly communicating with an Internet of Things (loT) device; and sending (414) to the first network node a third message comprising the second information.

16. The method according to claim 15, wherein obtaining the second information comprises: obtaining subscription data of the terminal device; obtaining intermediate node capability of the terminal device; and determining the second information based on the subscription data and the intermediate node capability.

17. The method according to any of claims 14-16, further comprising: checking (422) respective states of one or more candidate terminal devices; paging (424) at least one candidate terminal device in the second state based on a checking result; updating (426) the state of the at least one candidate terminal device; and generating (428) the at least one candidate terminal device by removing all candidate terminal devices in the second state from the one or more candidate terminal devices.

18. The method according to claim 17, further comprising: receiving (432) from a third network node a fifth message comprising information identifying the one or more candidate terminal devices and information indicating the second network to page a terminal device in the second state; and sending (434) to the third network node a sixth message comprising information identifying the at least one candidate terminal device.

19. The method according to any of claims 14-18, further comprising: receiving (442) from a third network node a seventh message comprising information identifying at least one candidate terminal device; and sending (444) to the third network node an eighth message comprising information identifying the determined at least one terminal device.

20. The method according to claim 18 or 19, wherein the third network node comprises a network node supporting loT service function.

21. The method according to claim 20, wherein the first message and the seventh message further comprise area information and / or the at least one terminal device is determined further based on at least one of: the area information, a radio condition of a candidate terminal device,a position of a candidate terminal device, a radio resource situation of a candidate terminal device, a RRC connection state of a candidate terminal device, or a load situation of a candidate terminal device.

22. The method according to any of claims 14-21, further comprising: receiving (452) from the first network node a fourth message comprising third information identifying a part of the at least one candidate terminal device and fourth information indicating the second network node to page the part of the at least one candidate terminal device; and paging (454) the part of the at least one candidate terminal device.

23. The method according to claim 22, further comprising: re-sending (456) to the first network node the first message comprising the first information identifying the at least one candidate terminal device, wherein the fourth message comprises a failure cause.

24. A method (500) performed by a third network node, comprising: sending (502) to a second network node a seventh message comprising the first information identifying at least one candidate terminal device; and receiving (504) from the second network node an eighth message compnsing information identifying at least one terminal device which is determined based on the first information, wherein the at least one candidate terminal device is in a first state that a Radio Resource Control (RRC) connection has been established, or wherein a part of the at least one candidate terminal device is in a second state that no RRC connection is established, and the part of the at least one candidate terminal device is to be paged.

25. The method according to claim 24, further comprising: sending (512) to the second network node a fifth message comprising information identifying one or more candidate terminal devices and information indicating the second network to page a terminal device in the second state; and receiving (514) from the second network node a sixth message comprising information identifying the at least one candidate terminal device.

26. The method according to claim 24 or 25, wherein the third network node comprises a network node supporting Internet of Things (loT) service function.

27. The method according to any of claims 24-26, wherein the seventh message further comprise area information and / or the at least one terminal device is determined further based on at least one of: the area information, a radio condition of a candidate terminal device, a position of a candidate terminal device, a radio resource situation of a candidate terminal device, a RRC connection state of a candidate terminal device, or a load situation of a candidate terminal device.

28. A first network node (700), comprising: a processor (721); and a memory (722) coupled to the processor (721), said memory (722) containing instructionsexecutable by said processor (721), whereby said first network node (700) is operative to: receive from a second network node a first message comprising first information identifying at least one candidate terminal device; determine whether at least one terminal device can be used based on the first information; and send to the second network node a second message comprising information identifying the determined at least one terminal device to be used, wherein the at least one candidate terminal device is in a first state that a Radio Resource Control (RRC) connection has been established, or wherein a part of the at least one candidate terminal device is in a second state that no RRC connection is established, and the part of the at least one candidate terminal device is to be paged.

29. The first network node according to claim 28, wherein the first network node is further operative to perform the method of any one of claims 2 to 13.

30. A second network node (700), comprising: a processor (721); and a memory (722) coupled to the processor (721), said memory (722) containing instructions executable by said processor (721), whereby said second network node (700) is operative to: send to a first network node a first message comprising first information identifying at least one candidate terminal device; and receive from the first network node a second message comprising information identifying at least one terminal device which is determined based on the first information, wherein the at least one candidate terminal device is in a first state that a Radio Resource Control (RRC) connection has been established, or wherein a part of the at least one candidate terminal device is in a second state that no RRC connection is established, and the part of the at least one candidate terminal device is to be paged.

31. The second network node according to claim 30, wherein the second network node is further operative to perform the method of any one of claims 15 to 23.

32. A third network node (700), comprising: a processor (721); and a memory (722) coupled to the processor (721), said memory (722) containing instructions executable by said processor (721), whereby said third network node (700) is operative to: send to a second network node a seventh message comprising the first information identifying at least one candidate terminal device; and receive from the second network node an eighth message comprising information identifying at least one terminal device which is determined based on the first information, wherein the at least one candidate terminal device is in a first state that a Radio Resource Control (RRC) connection has been established, or wherein a part of the at least one candidate terminal device is in a second state that no RRC connection is established, and the part of the at least one candidate terminal device is to be paged.

33. The third network node according to claim 32, wherein the third network node is further operative to perform the method of any one of claims 25 to 27.

34. A computer program product comprising instructions which when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 27.

Images