Apparatus and method for ambient iot communication in wireless communication system

Abstract

Various aspects of the disclosure relate to methods, devices, and apparatuses for wireless communication. A user equipment (UE) can transmit (1102) a registration request message including an indication of a capability of the UE as an ambient Internet of Things (AIoT) intermediate node. The UE can receive (1104) a registration response message including an AIoT policy that enables the UE as the AIoT intermediate node for AIoT services.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically, to environmental Internet of Things (AIoT) communication in wireless communication systems. Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as base stations, which can support wireless communication with one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. The wireless communication system can support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers, etc.)). Furthermore, the wireless communication system can support wireless communication across various radio access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable radio access technologies above 5G (e.g., sixth-generation (6G)). Summary of the Invention

[0003] The article “a(a)” preceding an element is not limited and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein (included in the claims), “or” as used in a list of items (for example, a list of items followed by phrases such as “at least one of…” or “one or more of…” or “one or both of…”) indicates a list of inclusion, such that (for example) a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a set of closed conditions. For example, an exemplary step described as “based on condition A” could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Furthermore, as used herein (included in the claims), "group" may comprise one or more elements.

[0004] Various aspects of this disclosure relate to wireless communication, including improved methods and devices supporting AIoT communication in wireless communication systems. A UE can transmit a registration request message containing an indication of the UE's capability as an AIoT intermediary node. The UE can also receive a registration response message including an AIoT policy that enables the UE to act as the AIoT intermediary node for AIoT services. Attached Figure Description

[0005] Figure 1 Illustrated examples of wireless communication systems according to various aspects of this disclosure.

[0006] Figure 2 The diagram illustrates an example of a first topology of a wireless network according to various aspects of this disclosure.

[0007] Figure 3 The diagram illustrates an example of a second topology for a wireless network according to various aspects of this disclosure.

[0008] Figure 4 Illustrated examples of block diagrams for environmental Internet of Things (AIoT) systems according to various aspects of this disclosure.

[0009] Figure 5 Illustrated examples of procedures in an AIoT system according to various aspects of this disclosure.

[0010] Figure 6 The illustration shows another example of a procedure in an AIoT system according to various aspects of this disclosure.

[0011] Figure 7 This illustration shows yet another example of a procedure in an AIoT system according to various aspects of this disclosure.

[0012] Figure 8 Illustrated examples of UEs based on various aspects of this disclosure.

[0013] Figure 9 Illustrated examples of processors according to various aspects of this disclosure.

[0014] Figure 10 Illustrated examples of network equipment (NE) according to various aspects of this disclosure.

[0015] Figure 11 The diagram illustrates a flowchart of a method performed by a UE according to various aspects of this disclosure.

[0016] Figure 12 The diagram illustrates a flowchart of a method performed by an NE according to various aspects of this disclosure. Detailed Implementation

[0017] Various aspects of this disclosure relate to AIoT communication in wireless communication systems. AIoT communication can be supported by a UE acting as (e.g., operating as) an AIoT reader. AIoT communication can occur on the control plane. For example, a wireless device such as a UE may output (e.g., transmit) a request to register with the wireless communication system based at least in part on the wireless device's desire to become an intermediary node for AIoT communication (e.g., AIoT data transmission). However, in some cases, the wireless device may be incompatible and / or unable to act as an intermediary node, and the signaling associated with the request may result in wasted time, communication resources, and power consumption (e.g., battery life). To address these drawbacks, a wireless device capable of AIoT communication may be configured (e.g., enabled) with policy information to determine when and how to receive data or signaling from the network in the downlink and transmit it to the AIoT device, and to receive data or signaling from the AIoT device in the uplink and transmit it to the network. The auxiliary information for the request can provide improved transmission efficiency, less use of communication resources, and more efficient use of time.

[0018] Various aspects of this disclosure are described in the context of wireless communication systems.

[0019] Figure 1 The illustration depicts examples of a wireless communication system 100 according to various aspects of this disclosure. The wireless communication system 100 may include one or more NEs 102, one or more UEs 104, and a core network (CN) 106. The wireless communication system 100 may support various radio access technologies. In some embodiments, the wireless communication system 100 may be a 4G network, such as an LTE network or an advanced LTE (LTE-A) network. In some other embodiments, the wireless communication system 100 may be a new radio (NR) network, such as a 5G network, an advanced 5G (5G-A) network, or a 5G ultra-wideband (5G-UWB) network. In other embodiments, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G, such as 6G. In addition, the wireless communication system 100 can support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0020] One or more NEs 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the NEs 102 described herein may be, include, or be referred to as a network node, base station, network element, network function, network entity, radio access network (RAN), NodeB, eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. NEs 102 and UEs 104 may communicate via a communication link, which may be a wireless or wired connection. For example, NEs 102 and UEs 104 may perform wireless communication (e.g., receiving signaling, transmitting signaling) via a Uu interface.

[0021] NE 102 can provide a geographic coverage area, and NE 102 can support service to one or more UEs 104 within the geographic coverage area. For example, NE 102 and UE 104 can support wireless communication of signals related to services (e.g., voice, video, packet data, message sending and receiving, broadcasting, etc.) according to one or more radio access technologies. In some embodiments, NE 102 can be mobile, such as a satellite associated with an NTN. In some embodiments, different geographic coverage areas associated with the same or different radio access technologies can overlap, but different geographic coverage areas can be associated with different NEs 102.

[0022] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a remote unit, mobile device, wireless device, remote device, subscriber device, transmitter device, receiver device, or some other suitable term. In some embodiments, UE 104 may be referred to as a unit, station, terminal, or client, and other instances thereof. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, and other instances thereof.

[0023] UE 104 may be able to support direct wireless communication with other UE 104 via a communication link. For example, UE 104 may support direct wireless communication with another UE 104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular V2X deployments, the communication link may be referred to as a sidelink. For example, UE 104 may support direct wireless communication with another UE 104 via a UE-to-UE interface (PC5 interface).

[0024] NE 102 may support communication with CN 106, another NE 102, or both. For example, NE 102 may interface with other NE 102 or CN 106 via one or more backhaul links (e.g., S1, N2, N2, or network interfaces). In some embodiments, NE 102 may communicate directly with each other. In other embodiments, NE 102 may communicate with each other or indirectly (e.g., via CN 106). In some embodiments, one or more NE 102 may include sub-components such as access network entities, which may be instances of access node controllers (ANCs). The ANC may communicate with one or more UE 104s via one or more other access network transport entities, which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs).

[0025] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN106 can be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route packets or interconnections to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access plane (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.) for one or more UEs 104 served by one or more NEs 102 associated with CN106.

[0026] CN 106 may communicate with the packet data network via one or more backhaul links (e.g., via S1, N2, N2, or another network interface). The packet data network may contain an application server. In some implementations, one or more UEs 104 may communicate with the application server. UE 104 may establish a session (e.g., a Protocol Data Unit (PDU) session, etc.) with CN 106 via NE 102. CN 106 may use the established session (e.g., an established PDU session) to route services (e.g., control information, data, etc.) between UE 104 and the application server. A PDU session may be an instance of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0027] In the wireless communication system 100, NE 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some embodiments, NE 102 and UE 104 can support different resource structures. For example, NE 102 and UE 104 can support different frame structures. In some embodiments, such as in 4G, NE 102 and UE 104 can support a single frame structure. In some other embodiments, such as in 5G and other suitable radio access technologies, NE 102 and UE 104 can support various frame structures (i.e., multiple frame structures). NE 102 and UE 104 can support various frame structures based on one or more parameter sets (numerologies).

[0028] The wireless communication system 100 may support one or more parameter sets, and the parameter sets may include subcarrier spacing and cyclic prefixes. A first parameter set (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some embodiments, the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one time slot per subframe. A second parameter set (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. A third parameter set (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth parameter set (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth parameter set (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240 kHz) and a normal cyclic prefix.

[0029] Time intervals for resources (e.g., communication resources) can be organized according to frames (also referred to as radio frames). Each frame may have a certain duration, such as 10 milliseconds (ms). In some embodiments, each frame may contain multiple subframes. For example, each frame may contain 10 subframes, and each subframe may have a certain duration, such as 1 ms. In some embodiments, each frame may have the same duration. In some embodiments, each subframe of a frame may have the same duration.

[0030] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may contain a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more parameter sets supported in the wireless communication system 100. For example, a first parameter set, a second parameter set, a third parameter set, a fourth parameter set, and a fifth parameter set (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize one time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may contain a certain number (e.g., quantity) of symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols). In some embodiments, the number (e.g., quantity) of time slots in a subframe may depend on the parameter set. For a normal cyclic prefix, a time slot may contain 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot may contain 12 symbols. The relationships between the number of symbols per time slot, the number of time slots per subframe, and the number of time slots per frame for both normal and extended cyclic prefixes may depend on the parameter set. It should be understood that a reference to the first parameter set (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) may be used interchangeably between subframes and time slots.

[0031] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, channels, etc., based on frequency or wavelength. By way of example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency ranges specified as FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), FR4 (52.6 GHz to 114.25 GHz), FR4a or FR4-1 (52.6 GHz to 71 GHz), and FR5 (114.25 GHz to 300 GHz). In some embodiments, NE 102 and UE 104 can perform wireless communication on one or more of the said operating frequency bands. In some embodiments, FR1 can be used by NE 102 and UE 104, as well as other equipment or devices for cellular communication services (e.g., control information, data). In some implementations, FR2 may be used by NE 102 and UE 104, as well as other equipment or devices for short-range, high-data-rate capabilities.

[0032] FR1 may be associated with one or more parameter sets (e.g., at least three parameter sets). For example, FR1 may be associated with a first parameter set containing a 15 kHz subcarrier spacing (e.g., μ=0), a second parameter set containing a 30 kHz subcarrier spacing (e.g., μ=1), and a third parameter set containing a 60 kHz subcarrier spacing (e.g., μ=2). FR2 may be associated with one or more parameter sets (e.g., at least two parameter sets). For example, FR2 may be associated with a third parameter set containing a 60 kHz subcarrier spacing (e.g., μ=2) and a fourth parameter set containing a 120 kHz subcarrier spacing (e.g., μ=3).

[0033] In a wireless communication system (also known as a wireless network), such as a 5G system (5GS), cellular IoT services can be provided to devices with reduced capabilities. The system may include simplified devices referred to as AIoT devices. These AIoT devices can be a new type of IoT device that is powered by harvesting energy from various sources, such as radio frequency (RF) energy, solar energy, wind energy, etc. Unlike traditional IoT devices, AIoT devices may not rely on batteries and may have limited energy storage capabilities, typically using internal capacitors for energy storage. RF energy can be harvested from transmissions carried out by the network itself. AIoT devices can transmit and / or receive data through AIoT communication with other devices.

[0034] RF energy harvesting enables environmental IoT devices to harvest energy from RF signals available in their surroundings, such as those transmitted from mobile networks or nearby Wi-Fi networks. RF energy harvesting can be a technology that enables self-sustaining wireless IoT networks and analyzes the energy harvesting performance of Wi-Fi-based IoT networks.

[0035] For an environmental IoT device used to transmit data, it can first receive an RF signal that provides sufficient power to power the device. This RF signal is often referred to as a trigger signal or trigger message. The trigger message can be transmitted by a base station (BS) or a UE (UE-AIoT-I) acting as an intermediate node acting as an AIoT reader. It can be assumed that both the BS and the UE-AIoT-I are very close to the AIoT device.

[0036] Several connectivity topologies can be used to enable AIoT devices to communicate with mobile networks (e.g., 5GS). For Figure 2 and 3 The AIoT network and device connectivity topology shown is usable within 3GPP. In such instances, AIoT devices can be provided with carriers from other nodes inside or outside the topology. Links within each topology can be bidirectional or unidirectional.

[0037] Figure 2 The diagram illustrates an example of a first topology 200 of a wireless network according to various aspects of this disclosure. The first topology 200 includes a BS 202 (e.g., BS 202 ↔ AIoT device 204) that communicates directly with an AIoT device 204 via a link 206. Communication between the BS 202 and the AIoT device 204 includes receiving AIoT data and / or signaling 208 from or to the core network.

[0038] Figure 3 The diagram illustrates an example of a second topology 300 of a wireless network according to various aspects of this disclosure. The second topology 300 includes a BS 302 that communicates bidirectionally with an intermediate node 304 (e.g., a UE) between a BS 302 and an AIoT device 306 via communication links 308 and 310. This is represented as "BS ↔ Intermediate Node ↔ AIoT Device". The intermediate node 304 may be a specific UE capable of transmitting and receiving data and / or signaling 310 with the AIoT device 306. For a UE capable of AIoT communication as an intermediate node 304, the intermediate node 304 as a UE may be simply referred to as "UE-AIoT-I". The UE-AIoT-I may receive and transmit AIoT-related data and / or signaling 312 to the core network via the base station 302.

[0039] Figure 4 The diagram illustrates an example of a block diagram of an AIoT system 400 according to various aspects of this disclosure. The AIoT system 400 can be used for AIoT services (e.g., functions and / or services provided by AIoT devices) for automated warehouse inventory counting. Inventory counting can utilize request-response operations. Another example of the AIoT service can utilize sensor monitoring, where the network may need to read and write data to the AIoT device. At 402, a truck is unloaded and goods with embedded AIoT devices enter the warehouse via an AIoT device reader. The AIoT device reader is shown as a door at 404. According to a first topology 200, the AIoT device reader can be a BS. According to a second topology 300, the AIoT device reader can be a UE-AIoT-I. At 406, goods with embedded AIoT devices are stored in the warehouse. During this time, goods with embedded AIoT devices can be accessed by the BS. At 408, goods with embedded AIoT devices leave the warehouse via an AIoT device reader. At 410, goods with embedded AIoT devices pass through the AIoT device reader and are loaded onto a truck.

[0040] At locations 404, 406, and 408, the AIoT device can be functionalized, and the network (to which the AIoT reader is connected) can communicate with the device and read its AIoT device identifier (ID). Therefore, the network can determine the location of the AIoT device and the corresponding goods and / or inventory.

[0041] The specific instances in this article may use a connectivity topology where AIoT readers (or Figure 4 The gates at 404 and 408 are implemented as UEs capable of AIoT communication as intermediate nodes (e.g., UE-AIoT-I) (e.g., second topology 300, where the intermediate node is denoted as UE-AIoT-I). For this purpose, the UE-AIoT-I node can register with the network and AIoT data and / or signaling can pass through the UE-AIoT-I node.

[0042] In various instances, in order to allow the UE to act as an intermediate node (e.g., UE-AIoT-I node) for AIoT data and / or signaling transmission to communicate with AIoT devices and the network (e.g., via the Uu interface), the following can be determined: how to configure the UE-AIoT-I to perform AIoT communication, and how to send and / or receive AIoT data and / or signaling between the UE-AIoT-I and the network's core network (CN).

[0043] Figure 5 The illustration depicts an example of program 500 in an AIoT system according to various aspects of this disclosure. In some implementations, program 500 may be implemented as described in the reference. Figure 1 The described aspects of the wireless communication system 100, or aspects thereof, are implemented by the wireless communication system. Program 500 may include AIoT device 502 (or multiple AIoT devices), AIoT device reader 503 (including UE-AIoT-I 504 and Radio Access Network (RAN) 506), CN 507 (including AIoT-GW, Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF) 508, Unified Data Repository (UDR) / Unified Data Management (UDM) 510 and Charging Function (CHF) 512), Operation, Management and Maintenance (OAM) 514, and AIoT Application Function (AF) and / or Application Server (AS) 516. In the following description of program 500, operations may be transmitted in a different order than the exemplary order shown, or operations may be performed in a different order or at different times. Some operations may be omitted from program 500, and other operations may be added to program 500. AIoT device 502 communicates with AIoT device reader 503.

[0044] Specifically Figure 5 This diagram illustrates the deployment and configuration overview of AIoT services in a communication network. Figure 5 Demonstrate the steps (or phases) for deploying AIoT services, including the configuration of network entities and AIoT transmitters, as well as communication services for transmitting AIoT data and / or signaling.

[0045] exist Figure 5 In this context, the CN control plane (CP) (or user plane) NF can be used for the purpose of AIoT services in a 3GPP network. Such an NF may be referred to as an AIoT gateway 508 (AIoT-GW) or an AIoT NF. The AIoT-GW 508 can: store AIoT service parameters and configure UE-AIoT-I 504, RAN 506, and / or BS or CP NF for AIoT services; receive AIoT data and / or signaling from and / or transmit AIoT data and / or signaling to the AIoT AS 516; receive AIoT data and / or signaling from and / or transmit AIoT data and / or signaling to the AIoT reader (e.g., RAN 506 and / or BS or UE-AIoT-I 504); perform storage and forwarding functionality for AIoT data and / or signaling; create billing data for AIoT data and / or signaling and transmit the data to CHF 512; and / or verify the identity of the AIoT device 502.

[0046] During the service provisioning phase 517, at point 518, the AIoT AF and / or AS 516 are configured with at least one of the following information: a list of AIoT device IDs (to which data and / or signaling must be transmitted or to which an inventory check operation must be performed), a service ID (which identifies the AIoT service), and credentials for the service and the AIoT device. AIoT devices can be identified using a group ID.

[0047] At 520, the configuration of AIoT device 502 may exist, including at least one of device ID, service ID, and credentials. At 522, service provisioning or a service level agreement (SLA) is established between AIoT AF / AS 516 and network CN 597. Information such as a list of AIoT device IDs, service ID, credentials, service area, and service operation type is provisioned to the network. Two instances of signaling can be used. In one instance, AIoT AF / AS 516 sends AIoT provisioning data to OAM 514, and OAM 514 provides the data to UDM / UDR 510. In another instance, AIoT AF / AS 516 sends data directly to UDM / UDR 510 (e.g., via Network Exposure Function (NEF)).

[0048] The service provisioning phase 517 may also include an AIoT device management program, which is used to manage the network and the AIoT status in AIoT AF / AS516.

[0049] During configuration phase 523, AIoT device reader 503 (e.g., RAN 506 or UE-AIoT-I 504) is configured to act as a general AIoT reader or an AIoT reader for a specific AIoT service. This configuration may also include the configuration of the CN 507 entity to serve a specific AIoT service. At 524, RAN 506 may optionally register its AIoT capabilities and / or service area with CN 507, where CN 507 is responsible for AIoT communications. At 526, UE-AIoT-I 504 may register with CN 507 and indicate its AIoT capabilities and / or service area to the CN 507 entity responsible for AIoT communications. At 524 and 526, the CN 507 responsible for AIoT communications may configure or enable AIoT device reader 503 to serve a specific AIoT service. At 528, the CN 507 NF responsible for AIoT communications may exchange information to configure or activate parameters related to a specific AIoT service. At 530, CN 507 NF, which is responsible for AIoT communication, can exchange information with AIoT AF / AS 516 for further service parameter configuration or updates.

[0050] During AIoT service procedure phase 531, AIoT data and / or signaling are transmitted between AIoT AF / AS 516 and AIoT device 502. For this phase, it can be assumed that the AIoT service agreement has been established and the network and AIoT device are configured with the necessary information. It can also be assumed that procedures for the AIoT service are initiated from the network to support device termination (DT) and device-initiated (DO) - device termination triggered (DTT) service types. This phase may also include authentication and / or authorization of AIoT device 502 or AIoT device ID. At 532, the AIoT service provider (e.g., denoted as AF or AS) sends the data or signaling to be transmitted in AIoT device 502. One or more entities in CN 507 may store, process, and prepare the data and / or signaling for transmission to AIoT device reader 503. At 534, CN 507 may transmit AIoT data and / or signaling to AIoT device reader 503. AIoT device reader 503 can transmit AIoT data and / or signaling to AIoT device 502, which can backscatter or actively transmit signals back to AIoT device reader 503. AIoT device reader 503 can transmit AIoT data and / or signaling to CN 507. At 536, the CN 507 entity responsible for AIoT can collect AIoT data and / or signaling and prepare AIoT data reports. The CN 507 entity responsible for AIoT transmits the AIoT data reports to AIoT AF / AS 516. Additionally, at 538, the CN 507 entity responsible for AIoT can collect billing data and transmit it to CHF 512 for billing purposes.

[0051] In one instance, parameters for the AIoT service (e.g., referred to as AIoT service parameters) may be used in the UE-AIoT-I 504 in one of the following ways: pre-configured in the Mobile Equipment (ME) portion of the UE-AIoT-I 504; configured in the Universal Integrated Circuit Card (UICC) portion of the UE-AIoT-I 504; pre-configured in the ME portion of the UE-AIoT-I 504 and configured in the UICC portion of the UE-AIoT-I 504; provided or updated by the AIoT-AF / AS 516 via the Policy Control Function (PCF) and / or user plane communication; or provided or updated to the UE-AIoT-I 504 by the PCF.

[0052] Figure 6 The illustration shows another example of a procedure in an AIoT system 600 according to various aspects of this disclosure. In some implementations, procedure 600 may be implemented as described in the references. Figure 1The described aspects of the wireless communication system 100, or aspects thereof, may be implemented by the wireless communication system. Program 600 may include an AIoT device reader 602 (including UE-AIoT-I 604), a CN 606 (including AMF, SMF 608, UPF 610, PCF 612, and UDR / UDM 614), and an AIoT AF / AS 616. In the following description of program 600, operations may be transmitted in a different order than the exemplary order shown, or operations may be performed in a different order or at different times. Some operations may be omitted from program 600, and other operations may be added to program 600.

[0053] Specifically Figure 6 At a high-level perspective, this demonstrates how the AIoT AF / AS 616 transmits AIoT policies to the UE-AIoT-I 604, which acts as an AIoT device reader 602. At 618, the AIoT AF / AS 616 can store information (or parameters) related to the operation of AIoT services in the communication network. At 620, the AIoT AF / AS 616 can use services exposed by the control plane (CP) of the CN to provision service parameters or application parameters in the CN, more specifically in the PCF 612 or UDR / UDM 614. At 622, the AIoT AF / AS 616 can send policy-related information directly or via the UDM / UDR 614 to the CN, more specifically to the PCF 612. Based on the received information, the PCF 612 can create an AIoT policy specific to the UE-AIoT-I 604. PCF 612 transmits UE-related AIoT policies to UE-AIoT-I 604 (e.g., via serving AMF 608) and / or transmits access and mobility (AM) related AIoT policies to serving AMF 608.

[0054] At position 624, the AIoT policy is transmitted via the application layer between UE-AIoT-I 604 and AIoT AF / AS 616. The AIoT policy can be carried via the user plane and can be transparent to the communication network (e.g., to 5GS).

[0055] In a specific instance, a UE (e.g., UE-AIoT-I604) capable of communicating with AIoT devices as an intermediate node is configured with an AIoT policy. The UE uses the AIoT policy to configure (e.g., enable, disable, reconfigure) its operation on the interface with the AIoT device. This policy can be configured at different levels: at the Non-Access Plane (NAS) level from the AMF or at the UE level from the PCF. The policy can be associated with a specific AIoT service used for transmitting AIoT data and / or signaling. Furthermore, the UE may be able to:

[0056] A. Transmitting an indication to the AMF that the UE can perform AIoT communication while acting as an intermediate node (e.g., in a registration request message); and

[0057] B. Receive one or more instructions regarding whether to allow (or disallow) operation as an AIoT intermediary node and which AIoT services are allowed to be served (e.g., contained in signaling from AMF or PCF).

[0058] In one instance, the AMF can handle UE-AIoT-I registration. More specifically, the AMF can: receive (e.g., from the UE) a registration request indicating the AIoT capabilities of an intermediate node; receive (e.g., from the UDM) UE subscription data indicating AIoT service authorization and / or service identifier; select an appropriate PCF capable of AIoT configuration; transmit an indication containing AIoT service authorization to the selected PCF; and / or transmit an indication to the UE indicating that one or more AIoT services are enabled or disabled (e.g., in a registration acceptance message or UE configuration command message).

[0059] In another instance, the PCF can create policies for UE-AIoT-I nodes. More specifically, the PCF can: receive (e.g., from the AMF) requests for AM policy association or UE policy association, including instructions that the UE is authorized to perform one or more AIoT services; receive (e.g., from the UDR or Application Function (AF)) notifications regarding AIoT (e.g., service or subscriber) configuration parameters that can be used to derive AM or UE policies specific to AIoT operations for a UE acting as an intermediary node; create the following policy types: UE-related policies for implementing AIoT services as an intermediary node (e.g., including AIoT policies and / or customized UE Routing Policy (URSP) rules) or AM-related policies for AIoT services (e.g., specific data network name (DNN) selection and replacement, specific service area restrictions for AIoT intermediary nodes); transmit UE-related AIoT policies or modified URSP rules to the UE (e.g., via the AMF); and / or transmit AM-related policies to the AMF.

[0060] The UE-AIoT-I can serve one or more AIoT services or applications that transmit AIoT data and / or signaling to different groups of AIoT devices. In other words, the UE-AIoT-I can implement one or more AIoT service clients. The AIoT policy may contain information transmitted to the UE that indicates how to map the services of different AIoT services to PDU sessions.

[0061] In some instances, the AIoT policy sent from the PCF to the UE-AIoT-I may include:

[0062] A. An indication of whether operation as an AIoT intermediate node is permitted (or not permitted);

[0063] B. A list of one or more AIoT services, wherein the one or more AIoT services are permitted to be served by a UE for transmitting to AIoT devices. The AIoT service may be identified by an AIoT application ID or an AIoT service ID, and may include a group ID identifying the group of AIoT devices to which the AIoT data is sent and / or received;

[0064] C. Configuration regarding how to transmit AIoT data and / or signaling to AIoT devices via a radio interface (e.g., Uu) (e.g., communication parameters for AIoT devices). This may include the signal strength to be used for transmission, the carrier frequency to be used for backscatter transmission, how to schedule AIoT devices for transmission, etc.

[0065] C-1. A type of AIoT service, configured for operation by the UE. The type of AIoT service may be one of the following: (A) Inventory counting service for discovering what goods (e.g., boxes, containers, packages, tools) are present in a specific area. The network may transmit a request within the specific area, and the AIoT device (attached to the goods) reports an identifier associated with the goods, possibly supplemented with other information such as status, measurement results, and / or location. (B) Sensor data collection service for transmitting sensor data from the AIoT device to the network. The transmission may be performed periodically when the AIoT device has sufficient power for transmission or when the AIoT device is triggered by the network. (C) Asset tracking service for determining the location of goods to which the AIoT device is attached. The AIoT device attached to these goods reports an identifier associated with the goods and associated location information. (D) Actuator control service used by the network to transmit (actuator) commands to the AIoT device. The AIoT device may store the commands and act accordingly;

[0066] D. A service area that allows AIoT transmissions to and / or from AIoT devices. The service area may include a geographic region (e.g., a destination region identified by Global Positioning (GPS) coordinates) or a network topology region (e.g., a Tracking Area Indicator (TAI) or a cell ID). The service area may be associated with an AIoT service ID, enabling the configuration of the service area for the UE based on the AIoT service ID;

[0067] E. Network identifier (e.g., PLMN), where the UE is authorized to perform AIoT communication with the AIoT device;

[0068] F. RATs that allow residency on the Uu interface, where AIoT communication is permitted on the interface used for communicating with AIoT devices;

[0069] G. Instructions on whether to allow the UE to perform AIoT communication when the UE is not served by Evolved Universal Terrestrial Radio Access (E-UTRA) and not by NR;

[0070] H. Map AIoT services to a set of parameters used to establish a PDU session, including: PDU session type (e.g., Internet Protocol (IP) type or unstructured type), transport layer protocol (e.g., UDP or Transmission Control Protocol (TCP), applicable only to IP PDU session types), Session and Service Continuity (SSC) mode, Single Network Slice Selection Auxiliary Information (S-NSSAI) and / or DNN; and

[0071] I. The effective time of AIoT strategy.

[0072] Figure 7 The illustration depicts yet another example of procedure 700 in an AIoT system according to various aspects of this disclosure. In some implementations, procedure 700 may be implemented as described in the reference. Figure 1 The described aspects of the wireless communication system 100, or aspects thereof, are implemented by the wireless communication system. Program 700 may include UE 702 (e.g., AIoT-I), RAN 704, AMF 706, PCF 708, and UDR / UDM 710. In the following description of program 700, operations may be transmitted in a different order than the exemplary order shown, or operations may be performed in a different order or at different times. Some operations may be omitted from program 700, and other operations may be added to program 700.

[0073] Specifically Figure 7This section describes the signaling flow of procedure 700, which demonstrates how to configure AIoT policies (e.g., for AIoT services) in UE 702 using PCF 708. PCF 708 can be a specific type of PCF capable of configuring AIoT policies. One or more PCF 708s may exist (e.g., specific AIoT services for specific AIoT customers). For this purpose, PCF 708 can self-register with the NRF and indicate its capabilities for AIoT policies. For example, PCF 708 can use the Nnrf_NFManagement_NFRegister service operation with AIoT capability indication as input parameters.

[0074] PCF 708 can be a UE-PCF (e.g., responsible for creating UE-specific policies), an AM PCF (e.g., responsible for creating AM-specific policies for AMF 706 and RAN 704), or a Session Management (SM) PCF (e.g., responsible for creating SM-specific policies for PDU sessions).

[0075] At 712, UE 702 implements the capability to act as an intermediate node in AIoT, having the ability to transmit to AIoT devices. UE 702 can be represented as UE-AIoT-I. Additionally, UE 702 can store various parameters for AIoT services, represented as AIoT service parameters, which can be stored in the ME portion and / or the UICC portion.

[0076] At 714, UDM / UDR 710 may store relevant UE subscription data and / or AIoT application subscription data. UE subscription data may contain information related to AIoT services. For example, UE subscription data may contain at least one of the following: UE 702 is permitted to operate at an intermediate AIoT device; the AIoT services permitted for UE 702; AIoT gateway (GW) selection information; permitted and / or subscribed control plane (CP) / user plane (UP) transmissions for the permitted AIoT services, etc. UE subscription data (e.g., application subscription data, SM subscription data, AIoT UP configuration data) may contain information about the association between UE 702 and AIoT AF / AS or AIoT service ID.

[0077] Application subscription data may contain, for example, the received AIoT configuration information. It should be noted that the use of AIoT services in this disclosure implies the communication services provided by the network to the AIoT devices and / or AIoT AF / AS for the exchange of AIoT data and / or signaling. An AIoT service may be identified by an AIoT service ID, which can be used in signaling between the AIoT AF / AS and the network's CN. This may mean that the network's CN (e.g., UDR / UDM 710) may store the association between the AIoT service ID and related service parameters (e.g., service area, transmission time, or periodicity, etc.), the associated AIoT application ID, group credentials associated with network layer security, a list of one or more AIoT devices, and a list of UEs acting as intermediate readers permitted to serve this AIoT service.

[0078] At 716, UE 702 may initiate the registration process. The registration request message (e.g., a Non-Access Layer (NAS) message) may include: UE 702's ability to act as an intermediary node for AIoT communication; whether UE 702 can receive AIoT data from the network via CP or UP transmission; and AIoT capabilities (e.g., supported frequency bands, communication range, power mode, mobile or fixed, indoor, outdoor, etc.). Indications may be implemented in the NAS protocol as a Mobility Management (MM) capability container sent from UE 702 to AMF 706, or the indication may be transmitted as a separate information element within the NAS message.

[0079] At 718, AMF 706 can process registration request messages and successful UE 702 authentication and authorization. AMF 706 can send request messages to retrieve the UE's subscription data from UDM / UDR 710. AMF 706 can use the Subscription Permanent Identifier (SUPI) as a reference identifier.

[0080] The response message from UDM / UDR 710 may include at least one of the following indications: UE 702 is authorized or enabled and / or disabled as an AIoT intermediate node; a list of one or more AIoT services that are allowed to transmit AIoT data and / or signaling to AIoT devices; AIoT-GW selection information; and / or whether CP or UP transmissions for each of the allowed services are preferred (or configured).

[0081] AIoT services can be identified by an identifier (ID) or a combination of a DNN and / or S-NSSAI. If different AIoT-GWs are deployed for different AIoT services, then an AIoT service identifier may be required.

[0082] At 720, AMF 706 may optionally support PCF 708 for creating policies for AIoT configuration. AMF 706 may use a local policy for PCF selection, or AMF 706 may use an NRF service, or UDR / UDM 710 may have already indicated information for PCF selection. PCF 708 may have self-registered with the NRF. When AMF 706 sends a request for PCF selection to the NRF, AMF 706 may include an indication that PCF 708 should support AIoT capabilities.

[0083] At 722, AMF 706 can send a request message to PCF 708 to establish an AM policy association (e.g., AM-PCF) with PCF 708. AMF 706 can use the Npcf_AMPolicyControl_Create service operation. AMF 706 may contain: SUPI (e.g., as UE ID), a list of TAIs for the registration area, access type, indication that UE 702 has subscribed to (or been authorized to) an AIoT service, the AIoT service (or application) ID that UE 702 has subscribed to, and UE location information or whether the UE is located indoors or outdoors.

[0084] PCF 708 can specifically create AM-related AIoT policies for UE 702, which may include: applying a specific RAT / Frequency Selection Priority (RFSP) index for operation as an AIoT intermediate node; specific DNN selection and / or DNN replacement policies; specific CHF selection; specific SMF selection for AIoT DNN and / or S-NSSAI; specific service area restrictions for AIoT intermediate nodes; policies for operation as indoor AIoT intermediate nodes or for operation as outdoor intermediate nodes, and other policies. The policy 'specific service area restrictions for AIoT intermediate nodes' may include network topology information (e.g., NR cell ID or TAI, or LTE cell ID or TAI), geographic information (e.g., GPS coordinates, altitude), or indications of indoor or outdoor restrictions when the UE is allowed to operate as an AIoT intermediate node.

[0085] At 724, AMF 706 may send a registration acceptance message (or, in various scenarios, a UE configuration update command (UCU)), which may contain one or more indications regarding whether operation as an AIoT intermediary node is allowed (or not allowed) and which AIoT service IDs are allowed to be served.

[0086] When AMF 706 creates a registration area for UE 702, AMF 706 may consider service area restrictions for AIoT intermediary node policies. Alternatively, AMF 706 may designate (e.g., in addition to the registration area) an AIoT service area in which the UE is permitted to operate as an AIoT intermediary node.

[0087] In addition, AMF 706 can also send AIoT service area restrictions to RAN 704 as part of the UE context for UEs operating as AIoT intermediate nodes. For example, when RAN 704 is identified as the target for UE mobility, RAN 704 can implement restriction policies.

[0088] At 726, PCF 708 can request application subscription data and / or UE subscription data (e.g., related to policy creation) from UDR / UDM 710. PCF 708 can instruct that the application subscription data should be associated with the AIoT service ID that UE 702 has subscribed to or authorized to use.

[0089] The UDR / UDM 710 can send response messages containing application subscription data for one or more applications associated with the AIoT Service ID.

[0090] At 728, PCF 708 can subscribe to UDR / UDM 710 to receive notifications when application subscription data changes. For example, PCF 708 can use Nudr_DM_Subscribe to request service operations. PCF 708 may include at least one of the following parameters: application data changes for AIoT services and / or UE subscription data change requests.

[0091] At 730, PCF 708 can create a policy for a UE (e.g., UE-AIoT-I) that acts as an intermediate node for AIoT transmission. The transmission of the UE AIoT policy can be completed at 734.

[0092] UE policies may include at least one of the following parameters:

[0093] A. Configuration regarding how to transmit AIoT data and / or signaling to AIoT devices via Uu (e.g., communication parameters for AIoT devices). This may include the frequency and / or power level for radio transmission to AIoT devices. Alternatively, configuration regarding how to transmit AIoT data and / or signaling to the network, such as whether to use control plane transmission or user plane transmission;

[0094] B. Among them, UE 702 is authorized to perform AIoT communication on a public terrestrial mobile network (PLMN);

[0095] C. Instructions regarding whether UE 702 should be allowed to perform AIoT communication when it is not served by E-UTRA and not by NR; and / or

[0096] D. Allow UE 702 to perform AIoT communication in one or more AIoT service areas. For example, AIoT service areas can be identified by network topology information (e.g., a list of TAIs, a list of cell IDs) or by geographical information (e.g., a polygon using GPS coordinates). Each AIoT service area can be associated with an AIoT service ID.

[0097] At 732, PCF 708 allows the creation of one or more URSP rules specific to an AIoT application. For example, URSP rules can be identified by the AIoT application ID, the AIoT-AS fully qualified domain name (FQDN) or IP address, or a 5-tuple of the destination traffic destined for the AIoT-AS. The routing descriptor (RSD) may contain S-NSSAI and / or DNN, as well as validity information specific to the AIoT application (e.g., location validity, time validity).

[0098] At position 734, PCF 708 can transmit UE AIoT policies and / or URSP policies to UE 702. Policy information can be encapsulated in an N1 UE policy container. In one instance, a new type of N1 UE policy container can be used to indicate that the UE policy is of the AIoT type. PCF 708 can use Namf_Communication_N1N2MessageTransfer or a similar service to transmit the UE policy container.

[0099] At 736, AMF 706 includes the N1 UE policy container in the NAS DL delivery message and sends the NAS message to UE 702.

[0100] At 738, UE 702 can respond by creating an N1 UE policy container and including it in a NAS UL delivery message. UE 702 can indicate whether the policy has been accepted, which part of the policy has been accepted, etc.

[0101] At 740, the AIoT AF 742 (and / or AIoT AS) can use existing or new services exposed by the 5GC (e.g., Network Exposure Function (NEF) 744) to send AIoT service (or subscriber) configuration parameters to the 5GC. In one instance, an existing service may be Nnef_ServiceParameter_Create / Update for service parameter provisioning (e.g., parameters provisioned to UE subscription data in UDR / UDM 710). In another instance, a new NEF service may be dedicated to AIoT service parameter provisioning (e.g., Nnef_AIoT_ServiceProvisioning for service parameters provisioned to application-level subscription data in UDR / UDM 710).

[0102] Information sent from AIoT AF 742 to 5GC may include at least one of the following: an AIoT application external identifier; a UE external identifier; a list of one or more AIoT service IDs that UE 702 is allowed to serve; a specific S-NSSAI or DNN that will be configured in UE 702 for use in sending AIoT services to AIoT AF 742; one or more AIoT (service or subscriber) configuration parameters (e.g., including the type of AIoT service), etc.

[0103] AIoT (service or subscriber) configuration parameters may include at least one of the following:

[0104] A. AM policy for applications identified by the AIoT service ID (e.g., any AIoT reader and / or transmitter that will be applied to this AIoT service);

[0105] B. AM policies for individual UEs (e.g., applied independently of conditions related to application services); and / or

[0106] C. Parameters or auxiliary information used to create an AIoT strategy for UE 702 in 5GC (e.g., PCF 708).

[0107] NEF 744 can select UDR / UDM 710 serving UE 710 and / or AIoT applications to pre-provision the requested service from AIoT AF 742 to UDR / UDM 710.

[0108] If AIoT AF 742 is a trusted entity and can directly contact PCF 708 (e.g., without using NEF 744 services or APIs), then AIoT AF 742 may need to select PCF 708 by first sending a request to the Binding Support Function (BSF) to resolve services for UE 702, DNN, or S-NSSAI.

[0109] At 746, if PCF 708 has subscribed to a notification from UDR / UDM 710 when the UE subscription data or application subscription data in UDR / UDM 710 changes, then UDR / UDM 710 can use the Nudr_DM_Notify service to transfer the changed subscription data to PCF 708. It should be noted that 740 and 746 can be executed at any time during procedure 700 when UE 702 registers with the network.

[0110] At 748, PCF 708 can create new AIoT policies or update existing stored AIoT policies for a specific UE. PCF 708 can perform the steps described herein to configure UE AIoT policies.

[0111] At 750, AIoT AF 742 can use existing or new services exposed by 5GC (e.g., PCF) to send AIoT service (or subscriber) configuration parameters to PCF 752. In one instance, an existing service could be the Npcf_AMPolicyAuthorization service, which is used by trusted application functions (AFs) to create or update application policies at PCF 752. AIoT AF 742 may contain the application policy information described herein.

[0112] In one implementation, AIoT AF 742 may contain a policy container to be transmitted to UE 702. This can be a new type of information sent from AIoT AF 702 to PCF 752, a policy container from AIoT AF 742 to UE 702. It can be considered an application policy container containing intermediate node AIoT policies. PCF 752 may store this application policy container and forward it to UE 702, which contains it in the N1 UE policy container.

[0113] At 754, PCF 752 can perform AM policy association modifications with AMF 706. Considering the policy update, AMF 706 can reconfigure UE 702 and RAN 704 serving UE 702.

[0114] It should be noted that Figure 7The examples shown can be applied to public networks (e.g., PLMNs) or private networks (e.g., non-public networks (NPNs) or standalone NPNs (SNPNs)). Furthermore, Figure 7 The benefit of this example is that it enables dynamic configuration of UE-related AIoT policies for UE 702 and AM-related AIoT policies for AMF 706 and RAN 704.

[0115] Figure 8 The illustration depicts an example of a UE 800 according to various aspects of this disclosure. The UE 800 may include a processor 802, a memory 804, a controller 806, and a transceiver 808. The processor 802, memory 804, controller 806, or transceiver 808, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0116] Processor 802, memory 804, controller 806, or transceiver 808, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure.

[0117] Processor 802 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, field-programmable gate array (FPGA), or any combination thereof). In some embodiments, processor 802 may be configured to operate memory 804. In some other embodiments, memory 804 may be integrated into processor 802. Processor 802 may be configured to execute computer-readable instructions stored in memory 804, thereby enabling UE 800 to perform various functions of this disclosure.

[0118] Memory 804 may include volatile or non-volatile memory. Memory 804 may store computer-readable, computer-executable code containing instructions that, when executed by processor 802, cause UE 800 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 804 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media, wherein the communication media includes any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media may be any available medium accessible by a general-purpose or special-purpose computer.

[0119] In some implementations, processor 802 and memory 804 coupled to processor 802 may be configured to cause UE 800 to perform one or more of the functions described herein (e.g., processor 802 executing instructions stored in memory 804). For example, according to the examples disclosed herein, processor 802 may support wireless communication at UE 800. For example, processor 802 coupled to memory 804 may be configured to cause UE 800 to transmit a registration request message containing an indication of the UE's capability as an AIoT intermediary node. UE 800 may also receive a registration response message including an AIoT policy that enables the UE to act as an AIoT intermediary node for AIoT services.

[0120] Controller 806 manages the input and output signals of UE 800. Controller 806 can also manage peripheral devices not integrated into UE 800. In some embodiments, controller 806 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 806 may be implemented as part of processor 802.

[0121] In some embodiments, UE 800 may include at least one transceiver 808. In other embodiments, UE 800 may have more than one transceiver 808. Transceiver 808 may represent a wireless transceiver. Transceiver 808 may include one or more receiver chains 810, one or more transmitter chains 812, or a combination thereof.

[0122] Receiver chain 810 may be configured to receive signals (e.g., control information, data, packets) via wireless media. For example, receiver chain 810 may include one or more antennas for receiving signals via air or wireless media. Receiver chain 810 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 810 may include at least one demodulator configured to demodulate the received signal and obtain transmitted data by reversing the modulation technique applied during signal transmission. Receiver chain 810 may include at least one decoder for decoding and processing the demodulated signal to receive transmitted data.

[0123] Transmitter chain 812 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 812 may include at least one modulator for modulating data onto a carrier signal, thereby preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 812 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 812 may also include one or more antennas for transmitting the amplified signal over the air or in the wireless medium.

[0124] Figure 9 The illustration depicts an example of a processor 900 according to various aspects of this disclosure. The processor 900 may be an example of a processor configured to perform various operations according to the examples described herein. The processor 900 may include a controller 902 configured to perform various operations according to the examples described herein. The processor 900 may optionally include at least one memory 904, which may be, for example, an L1 / L2 / L3 cache memory. Additionally or alternatively, the processor 900 may optionally include one or more arithmetic logic units (ALUs) 906. One or more of these components may be electronically communicated or otherwise coupled (e.g., operative ground, communicative ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., buses).

[0125] Processor 900 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) according to the examples described herein. The processor chipset may include one or more cores, one or more cache memories (e.g., memory native to or contained within the processor chipset (e.g., processor 900), or other memories (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), and others)).

[0126] The controller 902 can be configured to manage and coordinate various operations of the processor 900 (e.g., signaling, receiving, acquiring, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable the processor 900 to support various operations according to the examples described herein. For example, the controller 902 can operate as a control unit of the processor 900, thereby generating control signals that manage the operation of various components of the processor 900. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating operating timing.

[0127] Controller 902 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from memory 904 and determine subsequent instructions to be executed to enable processor 900 to support various operations according to the examples described herein. Controller 902 may be configured to track the memory addresses of instructions associated with memory 904. Controller 902 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, controller 902 may be configured to interpret instructions and determine control signals to be output to other components of processor 900, thereby enabling processor 900 to support various operations according to the examples described herein. Alternatively or additionally, controller 902 may be configured to manage data flow within processor 900. Controller 902 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 900.

[0128] Memory 904 may include one or more cache memories (e.g., memory native to or contained therein of processor 900, or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some embodiments, memory 904 may reside within or on the processor chipset (e.g., native to processor 900). In some other embodiments, memory 904 may reside external to the processor chipset (e.g., remote from processor 900).

[0129] Memory 904 may store computer-readable, computer-executable code containing instructions that, when executed by processor 900, cause processor 900 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium (e.g., system memory or another type of memory). Controller 902 and / or processor 900 may be configured to execute the computer-readable instructions stored in memory 904, thereby causing processor 900 to perform various functions. For example, processor 900 and / or controller 902 may be coupled together with or to memory 904, and processor 900, controller 902, and memory 904 may be configured to perform the various functions described herein. In some instances, processor 900 may include multiple processors and memory 904 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be individually or jointly configured to perform the various functions described herein.

[0130] One or more ALU 906s may be configured to support various operations according to the examples described herein. In some embodiments, one or more ALU 906s may reside within or on a processor chipset (e.g., processor 900). In some other embodiments, one or more ALU 906s may reside external to the processor chipset (e.g., processor 900). One or more ALU 906s may perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 906s may receive input operands and an opcode, the opcode determining the operation to be performed. One or more ALU 906s are configured with various logic and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively, one or more ALU 906s may support logical operations such as AND, OR, XOR, NOR, and NAND, thereby enabling one or more ALU 906s to handle conditional operations, comparisons, and bitwise operations.

[0131] Based on the examples disclosed herein, processor 900 may support wireless communication. Processor 900 may be configured or operable to support components for performing: transmitting a registration request message containing an indication of the UE's capability as an AIoT intermediary node, and receiving a registration response message including an AIoT policy that enables the UE to act as an AIoT intermediary node for AIoT services.

[0132] Figure 10The diagram illustrates an example of an NE 1000 according to various aspects of this disclosure. The NE 1000 may include a processor 1002, a memory 1004, a controller 1006, and a transceiver 1008. The processor 1002, memory 1004, controller 1006, or transceiver 1008, or various combinations thereof, or various components thereof, may be examples of components for performing the various aspects of this disclosure as described herein. These components may be coupled via one or more interfaces (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground).

[0133] Processor 1002, memory 1004, controller 1006, or transceiver 1008, or various combinations or components thereof, may be implemented in hardware (e.g., a circuit system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), or other programmable logic device, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure.

[0134] Processor 1002 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, or any combination thereof). In some embodiments, processor 1002 may be configured to operate memory 1004. In some other embodiments, memory 1004 may be integrated into processor 1002. Processor 1002 may be configured to execute computer-readable instructions stored in memory 1004, thereby enabling NE 1000 to perform various functions of this disclosure. For example, processor 1002 coupled to memory 1004 may be configured to cause NE 1000 to: receive a request message for an AIoT policy, wherein the request message includes an indication that the UE is authorized as an AIoT intermediary node for AIoT services; determine an AIoT policy for the UE, the AIoT policy enabling the UE as an AIoT intermediary node for AIoT services; and transmit a response message including the AIoT policy.

[0135] Memory 1004 may include volatile or non-volatile memory. Memory 1004 may store computer-readable, computer-executable code containing instructions that, when executed by processor 1002, cause NE 1000 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as memory 1004 or another type of memory. Computer-readable media includes both non-transitory computer storage media and communication media, wherein the communication media includes any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media may be any available medium accessible by a general-purpose or special-purpose computer.

[0136] In some implementations, processor 1002 and memory 1004 coupled to processor 1002 may be configured to cause NE 1000 to perform one or more of the functions described herein (e.g., processor 1002 executing instructions stored in memory 1004). For example, according to the examples disclosed herein, processor 1002 may support wireless communication at NE 1000.

[0137] Controller 1006 manages the input and output signals of NE 1000. Controller 1006 can also manage peripheral devices not integrated into NE 1000. In some embodiments, controller 1006 may utilize an operating system such as iOS®, ANDROID®, WINDOWS®, or other operating systems. In some embodiments, controller 1006 may be implemented as part of processor 1002.

[0138] In some embodiments, NE 1000 may include at least one transceiver 1008. In other embodiments, NE 1000 may have more than one transceiver 1008. Transceiver 1008 may represent a wireless transceiver. Transceiver 1008 may include one or more receiver chains 1010, one or more transmitter chains 1012, or a combination thereof.

[0139] Receiver chain 1010 may be configured to receive signals (e.g., control information, data, packets) via wireless media. For example, receiver chain 1010 may include one or more antennas for receiving signals via air or wireless media. Receiver chain 1010 may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. Receiver chain 1010 may include at least one demodulator configured to demodulate the received signal and obtain transmitted data by reversing the modulation technique applied during signal transmission. Receiver chain 1010 may include at least one decoder for decoding the processed and demodulated signal to receive transmitted data.

[0140] Transmitter chain 1012 can be configured to generate and transmit signals (e.g., control information, data, packets). Transmitter chain 1012 may include at least one modulator for modulating data onto a carrier signal, thereby preparing the signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase shift keying (PSK) or quadrature amplitude modulation (QAM). Transmitter chain 1012 may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. Transmitter chain 1012 may also include one or more antennas for transmitting the amplified signal over the air or in the wireless medium.

[0141] Figure 11 The diagram illustrates a flowchart of method 100 according to various aspects of this disclosure. Operation of method 1100 may be implemented by a first device (e.g., a UE) as described herein. In some embodiments, the UE 1100 may execute a set of instructions to control functional elements of a processor to perform the described functions.

[0142] At 1102, the method may include transmitting a registration request message, the registration request message containing an indication of the UE's capability as an AIoT intermediary node. The operation of 1102 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 1102 may be provided by reference to... Figure 8 The described UE is used to execute.

[0143] At point 1104, the method may include receiving a registration response message including an AIoT policy that enables the UE to act as an AIoT intermediary node for AIoT services. The operation of point 1104 may be performed according to the examples described herein. In some embodiments, aspects of the operation of point 1104 may be derived from references... Figure 8 The described UE is used to execute.

[0144] Figure 12 The diagram illustrates a flowchart of another method 1200 according to various aspects of this disclosure. Operation of method 1200 may be implemented by a second device (e.g., NE) as described herein. In some embodiments, the NE 1000 may execute a set of instructions to control the functional elements of a processor to perform the described functions.

[0145] At 1202, the method may include receiving a request message for an AIoT policy, wherein the request message includes an indication that the UE is authorized as an AIoT intermediary node for AIoT services. The operation of 1202 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 1202 may be provided by reference to... Figure 10 The NE described is used to execute.

[0146] At point 1204, the method may include determining an AIoT policy for the UE, the AIoT policy enabling the UE as an AIoT intermediary node for AIoT services. The operation of point 1204 may be performed according to the examples described herein. In some embodiments, aspects of the operation of point 1204 may be provided by reference to... Figure 10 The NE described is used to execute.

[0147] At 1206, the method may include transmitting a response message including an AIoT policy. The operation of 1206 may be performed according to the examples described herein. In some embodiments, aspects of the operation of 1206 may be as described in references... Figure 10 The NE described is used to execute.

[0148] It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible.

[0149] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but is given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE) comprising: At least one memory; as well as At least one processor, coupled to and configured to enable the UE to: Transmit a registration request message, the registration request message including an indication of the UE's capability as an intermediate node in the AIoT (Artificial Intelligence of Things) environment; and Receive a registration response message including an AIoT policy, which enables the UE to act as an AIoT intermediate node for AIoT services.

2. The UE according to claim 1, wherein the AIoT policy includes one or more of the following: a UE policy for the UE as an AIoT intermediate node or a UE routing selection policy (URSP) for routing AIoT communication by the UE as an AIoT intermediate node.

3. The UE according to claim 1, wherein the AIoT policy is based on one or more of the following: the UE's application subscription data or session management SM subscription data, which includes AIoT user plane UP configuration data.

4. The UE according to claim 1, wherein the AIoT policy is based on one or more of the following: the UE's application subscription data or session management (SM) policy data, which includes AIoT user plane (UP) configuration data.

5. The UE of claim 1, wherein the AIoT strategy for the UE comprises one or more of the following: Instructions to enable or disable the UE as an AIoT intermediate node; A list of one or more AIoT services or AIoT applications supported by the UE, which serves as the AIoT intermediate node; Configuration for one or more of the AIoT data or signaling transmissions to AIoT devices via the radio interface; At least one coverage area that allows AIoT communication with the AIoT device; or The network identifier associated with the permitted AIoT communication with the AIoT device.

6. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: The UE is enabled as an AIoT intermediate node at least in part based on the AIoT strategy; or The UE is disabled as an intermediate node of the AioT, at least in part, based on the AioT policy.

7. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: The coverage area suitable for AIoT communication with AIoT devices is determined at least in part based on the AIoT strategy; and The AIoT communication with the AIoT device is performed within the coverage area applicable to the AIoT communication.

8. The UE of claim 1, wherein the at least one processor is further configured to cause the UE to: Identify, at least in part, one or more of the service identifier associated with at least one AIoT service or the application identifier associated with at least one AIoT application, based on the AIoT strategy; and Perform AIoT communications associated with one or more of the at least one AIoT service or the at least one AIoT application.

9. A processor for wireless communication, comprising: At least one controller, coupled to at least one memory and configured to enable the processor to: Transmit a registration request message, the registration request message containing an indication of the UE's capability as an intermediate node in the AIoT (Artificial Intelligence of Things) environment; and Receive a registration response message including an AIoT policy, which enables the user equipment (UE) to act as the AIoT intermediate node for AIoT services.

10. The processor of claim 9, wherein the AIoT policy includes one or more of the following: a UE policy for the UE as an AIoT intermediate node or a UE routing selection policy (URSP) for routing AIoT communication by the UE as an AIoT intermediate node.

11. The processor of claim 9, wherein the AIoT policy is based on one or more of the following: the UE's application subscription data or session management SM subscription data, which includes AIoT user plane UP configuration data.

12. The processor of claim 9, wherein the AIoT policy is based on one or more of the following: the UE's application subscription data or session management (SM) policy data, wherein the UE contains AIoT user plane (UP) configuration data.

13. A method for equipping a user (UE), the method comprising: Transmit a registration request message, the registration request message containing an indication of the UE's ability to act as an intermediate node in the AIoT (Artificial Intelligence of Things) environment; and Receive a registration response message including an AIoT policy, which enables the UE to act as an AIoT intermediate node for AIoT services.

14. An apparatus for performing network functions, the apparatus comprising: At least one memory; as well as At least one processor, coupled to and configured to enable the device to: Receive a request message for an environmental Internet of Things (AIoT) policy, wherein the request message includes an indication that the user equipment (UE) is authorized as an AIoT intermediate node for AIoT services; Determine the AIoT policy for the UE, the AIoT policy enabling the UE as the AIoT intermediate node for the AIoT service; and The transmission includes a response message containing the AIoT strategy.

15. The device of claim 14, wherein the network function includes a policy control function (PCF).

16. The device of claim 15, wherein the PCF includes a PCF for creating UE-specific policies or a PCF for creating access and mobility policies for an Access and Mobility Management Function (AMF).

17. The device of claim 14, wherein the AIoT policy includes one or more of the following: a UE policy for the UE as an AIoT intermediate node or a UE routing selection policy (URSP) for routing AIoT communication by the UE as an AIoT intermediate node.

18. The device of claim 14, wherein the AIoT policy is determined based on one or more of the following: the UE's application subscription data or session management SM subscription data, which includes AIoT user plane UP configuration data.

19. The device of claim 14, wherein the AIoT policy is determined based on one or more of the following: the UE's application subscription data or session management (SM) policy data, wherein the UE contains AIoT user plane (UP) configuration data.

20. The device of claim 14, wherein the AIoT strategy for the UE comprises one or more of the following: Instructions to enable or disable the UE as an AIoT intermediate node; A list of one or more AIoT services or AIoT applications supported by the UE, which serves as the AIoT intermediate node; Configuration for one or more of the AIoT data or signaling transmissions to AIoT devices via the radio interface; At least one coverage area that allows AIoT communication with the AIoT device; or The network identifier associated with the permitted AIoT communication with the AIoT device.

Images