Services for environmental IoT devices

Abstract

Example embodiments of the present disclosure relate to a BS, a core network entity, an AIoT device, methods, apparatuses, and computer readable media for services of AIoT devices. In this solution, the BS can receive a first message from the core network entity, and the first message can indicate a type of a service associated with one or more AIoT devices. Accordingly, the base station can identify the first message for an AIoT service, and in addition, the base station can send a second message to the one or more AIoT devices to initiate a procedure of the service. Thus, the base station can distinguish the service of AIoT from the service of legacy UE, and can guarantee the service for AIoT devices.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more particularly to base stations (BS), core network entities, environmental IoT (AIoT) devices, methods, apparatuses, and computer-readable media for services for environmental Internet of Things (IoT) devices. Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations), which may also be referred to as eNodeB (eNB), next-generation NodeB (gNB), or other suitable terms. Each network communication device (such as a base station) may support wireless communication for one or more user communication devices, which may also be referred to as user equipment (UE), or other suitable terms. The wireless communication system may 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)). Additionally, the wireless communication system may support wireless communication across a variety of radio access technologies, including third-generation (3G) radio access technology, fourth-generation (4G) radio access technology, fifth-generation (5G) radio access technology, and other suitable radio access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] Research projects on Ambient Internet of Things (A-IoT or AIoT) have been launched in New Radio (NR) Release 18 (Rel-18 or R18) and will be further discussed in Release 19 (Rel-19 or R19). Services for AIoT devices are typically performed through base stations, in which case it is desirable for the base station to distinguish AIoT devices from traditional UEs, and solutions to this problem need to be investigated. Summary of the Invention

[0004] This disclosure relates to base stations, core network entities, AIoT devices, methods, apparatuses, processors, and computer-readable media for services for AIoT devices. According to embodiments of this disclosure, the type of service can be indicated to the base station in a first message, and accordingly, the base station can distinguish between (multiple) AIoT devices.

[0005] In some implementations, a base station is provided. The base station includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the base station: receives a first message from a core network entity, the first message indicating the type of service for one or more AIoT devices, wherein the service is associated with at least one of: an inventory request or a command request; and sends a second message to one or more AIoT devices, the second message including an indication of the type of procedure for initiating the service.

[0006] In some implementations, a core network entity is provided. The core network entity includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the core network entity: determines to initiate a service for one or more AIoT devices; and sends a first message to a base station indicating the type of service for the one or more AIoT devices, wherein the service is associated with at least one of: an inventory request or a command request.

[0007] In some implementations, an AIoT device is provided. The AIoT device includes at least one memory; and at least one processor coupled to the at least one memory and configured such that the AIoT device: receives a second message from a base station, the second message including an indication of the type of service for initiating a service procedure, wherein the service is associated with at least one of: an inventory request or a command request; and enables the service for the procedure.

[0008] In some implementations, a method performed by a base station is provided. The method includes: receiving a first message from a core network entity, the first message indicating the type of service for one or more AIoT devices, wherein the service is associated with at least one of: an inventory request or a command request; and sending a second message to the one or more AIoT devices, the second message including an indication of the type of procedure for initiating the service.

[0009] In some implementations, a method is provided that is performed by a core network entity. The method includes: determining to initiate a service for one or more AIoT devices; and sending a first message to a base station indicating the type of service for the one or more AIoT devices, wherein the service is associated with at least one of: an inventory request or a command request.

[0010] In some implementations, a method is provided that is performed by an AIoT device. The method includes: receiving a second message from a base station, the second message including an indication of the type of service for initiating a service procedure, wherein the service is associated with at least one of: an inventory request or a command request; and enabling the service for the procedure.

[0011] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to the at least one memory and configured to cause the processor to: receive a first message from a core network entity indicating a type of service for one or more AIoT devices, wherein the service is associated with at least one of: an inventory request or a command request; and send a second message to the one or more AIoT devices, the second message including an indication of a type of procedure for initiating the service.

[0012] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to the at least one memory and configured to cause the processor to: determine that a service is initiated for one or more AIoT devices; and send a first message to a base station indicating the type of service for the one or more AIoT devices, wherein the service is associated with at least one of: an inventory request or a command request.

[0013] In some implementations, a processor for wireless communication is provided. The processor includes at least one controller coupled to the at least one memory and configured to: receive a second message from a base station, the second message including an indication of the type of service for initiating a service procedure, wherein the service is associated with at least one of: an inventory request or a command request; and enable the service for the procedure.

[0014] Some implementations of the methods and base stations described herein also include: determining the completion time based on auxiliary information, and starting a timer for the process based on that completion time.

[0015] Some implementations of the methods and base stations described herein also include: determining, based on a first message, that energy harvesting is required for at least one of one or more AIoT devices.

[0016] Some implementations of the methods and base stations described herein also include: generating at least one radio frequency (RF) signal for energy harvesting; and transmitting at least one RF signal to at least one of one or more AIoT devices.

[0017] Some implementations of the methods and base stations described herein also include: sending an instruction to the energy harvesting source, the instruction instructing the source to send at least one RF signal for energy harvesting to at least one of one or more AIoT devices.

[0018] Some implementations of the methods and base stations described herein also include: receiving a third message from a first AIoT device, the third message including the identifier of the first AIoT device.

[0019] Some implementations of the methods and base stations described herein also include sending a fourth message to a first AIoT device, the fourth message indicating acknowledgment of the third message.

[0020] Receive a random access ID from the first AIoT device on a carrier used to send the second message; and send a random access response to the first AIoT device, the random access response indicating that the random access ID was successfully received.

[0021] Some implementations of the methods and base stations described in this paper also include receiving an indicator from a core network entity that indicates whether a process has been completed.

[0022] Some implementations of the methods and core network entities described in this paper also include sending an indicator to the base station that indicates whether the process for service has been completed.

[0023] The methods described herein and some implementations of AIoT devices also include receiving at least one RF signal for energy harvesting from a base station or energy harvesting source.

[0024] The methods described in this paper and some implementations of AIoT devices also include sending a third message to a base station, which includes the identifier of the AIoT device.

[0025] The methods described in this paper and some implementations of AIoT devices also include receiving a fourth message from a base station that indicates acknowledgment of the third message.

[0026] In some implementations of the methods and AIoT devices described herein, the method further includes disabling at least one operation at the AIoT device based on determining that a second indicator indicates the process is complete, wherein the at least one operation includes backscatter transmission or uplink transmission to a base station. For example, at least one operation also includes receiving from a base station.

[0027] The methods described herein and some implementations of AIoT devices also include: sending a random access ID to a base station on a carrier used for receiving a second message; and receiving a random access response from the base station indicating that the random access ID has been successfully received by the base station.

[0028] In some implementations of the methods, base stations, core network entities, and AIoT devices described in this paper, the service type includes one of the following: an inventory type for identifying each AIoT device among one or more AIoT devices; a command type for performing operations related to one or more AIoT devices; a read type for reading data from one or more AIoT devices; a write type for writing data to one or more AIoT devices; or a disable type for disabling one or more AIoT devices.

[0029] In some implementations of the methods, base stations, core network entities, and AIoT devices described in this paper, the first message also indicates the device type of one or more AIoT devices.

[0030] In some implementations of the methods, base stations, core network entities, and AIoT devices described herein, the device type includes one of the following: a type of AIoT device; a type of backscattering device; a first type of AIoT device having a power consumption value below a first threshold; a second type of AIoT device having a power consumption value in the range from the first threshold to a second threshold and having backscattering transmission on a carrier; or a third type of AIoT device having a power consumption value in the range from the first threshold to the second threshold and having internally generated transmission.

[0031] In some implementations of the methods, base stations, core network entities, and AIoT devices described in this paper, the first message includes auxiliary information for the service process.

[0032] In some implementations of the methods, base stations, core network entities, and AIoT devices described herein, auxiliary information indicates one of the following: the energy harvesting rate for the process at each of the one or more AIoT devices; the charging time for the process; the power consumption value for the process; the energy storage size for the process at each of the one or more AIoT devices; the energy stored or available at each of the one or more AIoT devices during the process; the start time of the process; the completion time of the process; the latency required for the process; or, in the case of a process associated with an inventory request, an inventory round indicator.

[0033] In some implementations of the methods, base stations, core network entities, and AIoT devices described herein, the first message includes a first indicator that indicates whether the antennas of one or more AIoT devices are shared between energy harvesting and communication.

[0034] In some implementations of the methods, base stations, core network entities, and AIoT devices described herein, a second message is sent after a time duration, wherein the time duration includes one of the following: a charging time indicated by the first message, a waiting time for receiving data from a core network entity or another core network entity, or a waiting time configured by Operations Management and Maintenance (OAM).

[0035] In some implementations of the methods, base stations, core network entities, and AIoT devices described herein, the fourth message includes a second indicator that indicates whether the process has been completed.

[0036] In some implementations of the methods, base stations, core network entities, and AIoT devices described in this paper, the fourth message includes a command request.

[0037] In some implementations of the methods, base stations, core network entities, and AIoT devices described in this paper, the third message also includes a random access ID.

[0038] In some implementations of the methods, base stations, core network entities, and AIoT devices described in this paper, the first message includes a Next Generation Application Protocol (NGAP) message, and the type of service is included in the paging reason information element of the NGAP message.

[0039] In some implementations of the methods, base stations, core network entities, and AIoT devices described in this paper, the first message includes messages dedicated to AIoT or dedicated to services.

[0040] In some implementations of the methods, base stations, core network entities, and AIoT devices described herein, the core network entity includes one of the following: an AIoT management function (AIMF); an access and mobility management function (AMF) that includes the AIMF; or an AMF that communicates with the AIMF. Attached Figure Description

[0041] Figure 1 Examples of wireless communication systems in which some embodiments of the present disclosure may be implemented are illustrated;

[0042] Figure 2A The diagram illustrates an example structure of an AIoT device with Device 1;

[0043] Figure 2B The illustration shows a schematic diagram of an example communication network in which some embodiments of the present disclosure may be implemented;

[0044] Figures 2C to 2E The illustration shows an example schematic diagram of a connection between a base station and a core network entity according to some example embodiments of the present disclosure;

[0045] Figure 3 The diagram illustrates a signaling process according to some example embodiments of the present disclosure;

[0046] Figures 4A to 4B The illustrations depict some example embodiments of the present disclosure. Figure 2C Signaling diagram of the associated communication process;

[0047] Figure 5 Examples of devices suitable for implementing embodiments of the present disclosure are illustrated;

[0048] Figure 6 Examples of processors suitable for implementing some embodiments of the present disclosure are illustrated;

[0049] Figure 7 The illustration shows a flowchart of an example method implemented at a base station according to various aspects of this disclosure;

[0050] Figure 8 The diagram illustrates a flowchart of an example method implemented at a core network entity according to various aspects of this disclosure;

[0051] Figure 9 The illustration shows flowcharts of example methods implemented in AIoT devices according to various aspects of this disclosure; and

[0052] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0053] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below. In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0054] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the embodiments(s) described may include a particular feature, structure, or characteristic, but not every embodiment necessarily must include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same(s) embodiments(s). Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, those skilled in the art will recognize that in conjunction with other embodiments (whether explicitly described or not) such a feature, structure, or characteristic may affect such a feature, structure, or characteristic within the scope of their knowledge.

[0055] It should be understood that although the terms “first” and “second” may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms. In some examples, values, processes, or apparatus are referred to as “best,” “lowest,” “highest,” “minimum,” “maximum,” etc. It should be understood that such descriptions are intended to indicate that selection can be made from a number of functional alternatives used, and that these selections are not necessarily better, smaller, higher, or otherwise preferred than other selections.

[0056] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein are also intended to include the plural forms. Furthermore, it should be understood that the terms “comprising,” “including,” “having,” “having,” “including,” and / or “containing,” when used herein, specify the presence of said features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. For example, the term “comprising” and variations thereof should be understood as open terms meaning “including, but not limited to.” The term “based on” should be understood as “at least partially based on.” The terms “one embodiment” and “embodiment” should be understood as “at least one embodiment.” The term “another embodiment” should be understood as “at least one other embodiment.” The use of expressions such as “A and / or B” can mean “A only” or “B only” or “both A and B.” Other explicit and implicit definitions may be included below.

[0057] Figure 1Examples of wireless communication systems 100 that may be implemented in some embodiments of this disclosure are illustrated. Wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network (CN) 106, and a packet data network 108. Wireless communication system 100 may support various radio access technologies. In some implementations, wireless communication system 100 may be a 4G network, such as a Long Term Evolution (LTE) network or an Advanced LTE (LTE-A) network. In some other implementations, wireless communication system 100 may be a 5G network, such as a New Radio (NR) network. In other implementations, 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. Wireless communication system 100 may support radio access technologies other than 5G. 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).

[0058] One or more network entities 102 may be distributed across a geographical area to form a wireless communication system 100. The network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RAN), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) via a Uu interface.

[0059] Network entity 102 may provide a geographic coverage area 112 for which it may support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within the geographic coverage area 112. For example, network entity 102 and UE 104 may support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 may be mobile, for example, a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but different geographic coverage areas 112 may be associated with different network entities 102. The information and signals described herein may be represented using a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned in the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0060] One or more UEs 104 may be distributed across a geographical area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, among other examples. Alternatively or additionally, 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, among other examples. In some implementations, UE 104 may be stationary within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0061] One or more UEs 104 can be devices of different forms or with different capabilities. Some examples of UEs 104 are shown in... Figure 1 It is shown in the middle. For example... Figure 1 As shown, UE 104 can communicate with various types of devices, such as network entity 102, other UE 104, or network devices (e.g., CN 106, packet data network 108, relay device, integrated access and backhaul (IAB) node, or another network device). Alternatively or additionally, UE 104 can support communication with other network entities 102 or UE 104, which can act as relays in the wireless communication system 100.

[0062] UE 104 can also support direct wireless communication with other UE 104s via communication link 114. For example, UE 104 can 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, communication link 114 may be referred to as a side link (SL). For example, UE 104 can support direct wireless communication with another UE 104 via a PC5 interface.

[0063] Network entity 102 may support communication with CN 106, or with another network entity 102, or both. For example, network entity 102 may interface with CN 106 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via CN 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio heads, smart radio heads, or transmit-receive points (TRPs).

[0064] In some implementations, network entity 102 can be configured in a decomposed architecture that can utilize a protocol stack physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of the following: a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a Near-RT RIC, a Non-RT RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0065] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). One or more components of network entity 102 in the decomposed RAN architecture can be co-located, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in the decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0066] The functional division among CU, DU, and RU can be flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU, or RU. For example, the functional division of the protocol stack can be adopted between the CU and DU, such that the CU can support one or more layers of the protocol stack, while the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and one or more DUs or RUs can host lower-layer protocol layer functions and signaling, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC), Media Access Control (MAC) layer), and each can be at least partially controlled by the CU 160.

[0067] Alternatively, or alternatively, the functional division of the protocol stack can be adopted between DU and RU, such that DU can support one or more layers of the protocol stack, while RU can support one or more different layers of the protocol stack. DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional division between CU and DU or between DU and RU can be within the protocol layer (e.g., some functions for the protocol layer can be performed by one of CU, DU, or RU, while other functions of the protocol layer are performed by a different one of CU, DU, or RU).

[0068] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can connect to one or more DUs via mid-range communication links (e.g., F1, F1c, F1-u), while the DUs can connect to one or more RUs via front-end communication links (e.g., open front-end (FH) interfaces). In some implementations, the mid-range or front-end communication links can be implemented based on interfaces (e.g., channels) between layers of a protocol stack, supported by corresponding network entities 102 communicating via such communication links.

[0069] CN 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. CN 106 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 or interconnect packets 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 stratum (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 network entities 102 associated with CN 106.

[0070] CN 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N3, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 can communicate with application server 118. UE 104 can establish a session with CN 106 via network entity 102 (e.g., Protocol Data Unit (PDU) session, etc.). CN 106 can use the established session (e.g., established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session can be one example of a logical connection between UE 104 and CN 106 (e.g., one or more network functions of CN 106).

[0071] In the wireless communication system 100, network entity 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 implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more digital technologies.

[0072] One or more digital technologies may be supported in the wireless communication system 100, and the digital technologies may include subcarrier spacing and cyclic prefix. The first digital technology (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15 kHz) and a normal cyclic prefix. In some implementations, the first digital technique (e.g., ...) associated with the first subcarrier spacing (e.g., 15 kHz) is... μ =0) can utilize one time slot per subframe. Second digital technologies (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30 kHz) and a normal cyclic prefix. The third digital technology (e.g., μ =2) can be associated with a third subcarrier spacing (e.g., 60 kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth digital technology (e.g., μ =3) can be associated with a fourth subcarrier spacing (e.g., 120 kHz) and a normal cyclic prefix. A fifth digital technology (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

[0073] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, for example, 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0074] Alternatively or concurrently, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include a certain number (e.g., quantity) of time slots. The number of time slots in each subframe may also depend on one or more digital technologies supported in the wireless communication system 100. For example, a first digital technology, a second digital technology, a third digital technology, a fourth digital technology, and a fifth digital technology (i.e., ...) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz. μ =0、 μ =1、 μ =2、 μ =3、 μ =4) 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 can be used respectively. Each time slot can include a certain number (e.g., quantity) of symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM) symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the digital technique. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60 kHz subcarrier spacing), a time slot can include 12 symbols. The relationship 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 can depend on the digital technique. It should be understood that for the first digital technique (e.g., quantity) associated with the first subcarrier spacing (e.g., 15 kHz), μ The reference of =0 can be used interchangeably between subframes and time slots.

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

[0076] FR1 can be associated with one or more digital technologies (e.g., at least three digital technologies). For example, FR1 can be associated with the following: a first digital technology (e.g., μ =0), which includes a 15 kHz subcarrier spacing; second digital technology (e.g., μ =1), which includes a 30 kHz subcarrier spacing; third digital technology (e.g., μ =2), which includes a subcarrier spacing of 60 kHz. FR2 can be associated with one or more digital technologies (e.g., at least two digital technologies). For example, FR2 can be associated with a third digital technology (e.g., μ =2), which includes a 60 kHz subcarrier spacing; fourth digital technology (e.g., μ =3), which includes a subcarrier spacing of 120 kHz.

[0077] Environmental IoT devices, which are devices with limited or no energy storage capacity, have garnered significant attention in the field of wireless communication. Compared to existing UEs (User Equipment), AIoT devices offer smaller size, lower complexity, lower power consumption, and greater quantity (e.g., hundreds of billions or even trillions). Considering capabilities, AIoT devices can include: - Device 1: Peak power consumption of approximately 1 µW with energy storage, initial sampling frequency offset (SFO) of up to 10. X The device operates at ppm and contains neither DL nor UL amplification. The UL transmission of the device is backscattered on an externally provided carrier. - Device 2a: Peak power consumption ≤ hundreds of µW with energy storage, initial sampling frequency offset (SFO) up to 10 X ppm, the device has both DL amplification and / or UL amplification. The UL transmission of the device is backscattered on an externally provided carrier. - Device 2b: Peak power consumption ≤ hundreds of µW with energy storage, initial sampling frequency offset (SFO) up to 10 X ppm, the device has both DL and / or UL amplification. The UL transmission of the device is generated internally by the device.

[0078] Figure 2A The diagram illustrates an example architecture of an AIoT device, Device 1. For example, the following blocks are used to study the architecture of Device 1.

[0079] Antennas for the RF energy harvester and receiver / transmitter can be shared or separate. A matching network is used to match the impedance between the antenna and other components, including the RF energy harvester and receiver-related blocks. The RF energy harvester may include a rectifier that performs RF signal (AC) to DC conversion. An energy storage device (e.g., a capacitor) stores the energy harvested from the RF energy harvester. A power management unit (PMU) manages the storage of energy from the energy harvester into the energy storage device and supplies power to active component functional blocks that require power. Digital block logic (BB) includes functional blocks such as encoders, decoders, controllers, etc. Memory may include two types of memory: 1) non-volatile memory (NVM), such as EEPROM, for permanently storing device IDs, etc.; and 2) registers for temporarily storing any information required for the operation of the energy storage device only when energy is available. A clock generator provides the required clock signals(s). Receive-related blocks: The RFBPF is used to improve selectivity; depending on the implementation, it may not be present, and RAN4 RF requirements (if any, e.g., ACS) and peak power consumption targets also need to be considered; the RF envelope detector converts the RF signal to baseband; the BB LPF filters out harmonics and high-frequency components to improve the quality of the input signal to the comparator; depending on the implementation, it may not be present, but its presence is assumed in this study; the comparator determines the high / low of the input signal. Transmission-related blocks: The backscatter modulator switches impedance to modulate the backscattered signal via the tx signal from the BB logic. The waveform / modulation type will be investigated.

[0080] AIoT devices are typically battery-free devices without energy storage capabilities, or devices with energy storage devices that do not require manual replacement or charging, where energy is provided by harvesting radio waves, light, motion, heat, or any other power source that can be considered suitable. AIoT services can be triggered by NW (such as core network entities). AIoT services are typically executed through base stations, in which case a solution for base stations to distinguish AIoT devices should be addressed.

[0081] Embodiments of this disclosure provide a solution for services for AIoT devices. In this solution, a base station can receive a first message from a core network entity, and the first message can indicate the type of service for one or more AIoT devices. Accordingly, the base station can identify that the first message is for an AIoT service, and additionally, the base station can send a second message to one or more AIoT devices to initiate the service process. Therefore, the base station can distinguish AIoT services from traditional UE services and can guarantee services for AIoT devices. The principles and implementation of this disclosure will now be described in detail with reference to the accompanying drawings.

[0082] Figure 2BThe illustration shows a schematic diagram of an example communication network in which some embodiments of this disclosure can be implemented. For example... Figure 2B As shown, the communication network 200 may include a BS 210, multiple AIoT devices 230, and a core network entity 250. (Reference) Figure 1 Base station 210 can be network entity 102. Core network (CN) entity 250 can be a network function (NF) in the CN (such as 5GC or 6G core network).

[0083] For example, core network entity 250 may include AIoT Management Function (AIMF) 251 and / or 5GC Access and Mobility Management Function (AMF) 252. Some examples related to AIMF 251 and AMF 252 are... Figures 2C to 2E As shown in the image.

[0084] like Figure 2C As shown, AIMF 251 is a logical entity in the CN that differs from AMF 252, and base station 210 communicates directly with AIMF 251. Figure 2D As shown, AIMF 251 is a logical entity in the CN that differs from AMF 252, and base station 210 communicates with AIMF 251 through AMF 252. Figure 2E As shown, AIMF 251 is a function (i.e., an internal function) in AMF 252, that is, AMF 252 includes AIMF 251.

[0085] In this disclosure, AIMF 251 may include some or all of the functions listed below: - AIoT device data processing, such as collecting raw data from AIoT devices, filtering and cleaning raw data, and putting raw data into a usable format for processing. - Device management, such as monitoring, managing, controlling, and coordinating AIoT devices and / or AIoT readers (e.g., base stations), where the AIoT reader is a device that uses radio frequency waves to read data from and write data to AIoT devices. For example: Inventory: Identifying each AIoT device. Commands: Communicate with the identified AIoT device to perform operations on the AIoT device, such as read (reading data from the AIoT device), write (writing data to the AIoT device), or disable (temporarily or permanently disabling the AIoT device). AIoT reader configuration: such as the configuration of RF receiver sensitivity or RF transmit power. - Service management, such as receiving queries from external entities and filtering results obtained from data retrieved from AIoT devices and / or AIoT readers.

[0086] Figure 3 The illustration shows a signaling diagram of a communication process 300 according to some example embodiments of the present disclosure. Process 300 may relate to references Figure 2B The discussion focuses on base station 210, AIoT device 230, and core network entity 250. It should be understood that process 300 can be applied to other communication scenarios, which will not be described in detail.

[0087] In process 300, at point 310, core network entity 250 sends a first message to base station 210. The first message indicates the type of service for AIoT device 230. In some implementations, the service may be associated with an inventory request, a command request, or a request for both inventory and command (i.e., both inventory and command requests). In some implementations, the type of service may also be referred to as a service operation type, and this disclosure is not limited in this respect.

[0088] In some implementations, a type (e.g., a service operation type) may include at least one of the following: a disk type for identifying each of one or more AIoT devices, a command type for performing operations associated with one or more AIoT devices, a read type for reading data from one or more AIoT devices, a write type for writing data to one or more AIoT devices, or a disable type for (e.g., temporarily or permanently) disabling one or more AIoT devices. In some embodiments, a disk may be used to identify individual AIoT devices, and a command may be used to perform operations on the AIoT devices. In some examples, a type may be a disk type and / or a command. For example, a type may be both a disk and a command (which may be considered a complete type or a complete service) indicating that operations(s) are performed after identifying the individual AIoT devices. In some examples, a type may be one or more of the following: disk, read, write, or disable.

[0089] In some embodiments, the first message may be an NGAP message. In some embodiments, the NGAP message includes a paging reason information element (IE), and the IE of the paging reason may include the type of service.

[0090] In some other embodiments, the first message may be a message dedicated to AIoT or a message dedicated to a service. In some examples, the first message may be an AIoT request message, an AIoT inventory message, an AIoT command message, etc.

[0091] In some examples, the first message may be an AIoT-specific message, such as an AIoT request message. In some cases, a type may be included in the AIoT request message, and the type may be at least one of the following: inventory, command, read, write, or disable. In some other cases, a type may not be included (e.g., missing) in the AIoT request message, and a default type may be preconfigured or predefined to be associated with the AIoT request message; for example, the default type may be inventory. However, it should be understood that this disclosure is not limiting in this respect.

[0092] In some examples, the first message may be a service-specific message, such as an AIoT inventory message. In some instances, an AIoT inventory message may include detailed inventory request information. In some instances, an AIoT inventory message may indicate the inventory type and may not include an explicit IE or field for that type.

[0093] In some examples, the first message can be a service-specific message, such as an AIoT command message. In some instances, an AIoT command message may include detailed command request information. In some instances, an AIoT command message may indicate the command type and may not include an explicit IE or field for that type.

[0094] In some implementations, the first message may indicate the device type. In some example embodiments, one or more AIoT devices of that device type can be identified and used for the service. In some implementations, the device type may be one or more of the following: AIoT device, AIoT device 1, AIoT device 2a, AIoT device 2b, or a backscatter device. In this case, base station 210 may recognize that the first message is for AIoT services rather than for a traditional UE.

[0095] In some examples, the device type can be an AIoT device, such as a device with limited energy storage capacity and powered by energy harvesting. In some examples, the device type can be a first-type AIoT device, i.e., device 1 as provided above. In some examples, the device type can be a second-type AIoT device, i.e., device 2a as provided above. In some examples, the device type can be a third-type AIoT device, i.e., device 2b as provided above. In some examples, the device type can be a backscattering device, such as a device with UL transmission that will perform backscattering on an externally provided carrier.

[0096] In some implementations, the first message may include auxiliary information for the process of the service. In some implementations, the auxiliary information may include some or all of the following: the energy harvesting rate for the process at each of the one or more AIoT devices; the charging time for the process; the power consumption value for the process; the energy storage size for the process at each of the one or more AIoT devices; the energy stored or available at each of the one or more AIoT devices during the process; the start time of the process; the completion time of the process; the latency required for the process; or, in the case of the process being associated with an inventory request, an inventory round indicator.

[0097] In some examples, auxiliary information may include the energy harvesting rate, which may indicate the rate at which energy is harvested, for example, the rate at which ambient energy present in an RF signal is converted into electrical energy to power an AIoT device.

[0098] In some examples, auxiliary information may include charging time, which may indicate the length of time or duration for charging the AIoT device.

[0099] In some examples, auxiliary information may include power consumption values, which may indicate the power consumption used for a disk storage round or the power consumption used for sending or receiving messages.

[0100] In some examples, auxiliary information may include energy storage size, which can indicate the amount of energy that an AIoT device can store.

[0101] In some examples, auxiliary information may include stored or available energy, which can indicate the amount of energy available to the AIoT device. For example, CN entity 250 can determine (e.g., calculate) the stored / available energy by subtracting the power consumption value from the energy storage size.

[0102] In some examples, auxiliary information may include time requirements for the service process. In some instances, time requirements may include start and / or finish times. For example, the start time may indicate when the inventory or command process begins. For example, the finish time may indicate the end time or duration of the process, such as how long base station 210 needs to complete the inventory or command process for multiple AIoT devices. In some instances, time requirements may include latency, which may indicate the delay required for the inventory or command process.

[0103] In some examples, auxiliary information may include a inventory round indicator that indicates the duration of time used for an inventory round. For example, the duration of time may be represented as multiple time units (such as time slots, symbols, frames, seconds, etc.), and the inventory round indicator may indicate the total number of multiple time units.

[0104] In some implementations, the first message may include a first indicator, which may indicate whether the antenna of the AIoT device is shared between energy harvesting and communication. For example, the first indicator may indicate whether the RF energy harvester and communication (e.g., receiver / transmitter) should or should not share the same antenna.

[0105] In some example embodiments, the first message may be an NGAP paging message, in which case the type of service (i.e., the service operation type) may be included in the paging reason, while the device type, auxiliary information, and first indicator may be included in the AIoT device capabilities or auxiliary data for paging in the first message.

[0106] In some example embodiments, the information indicated by the first message (such as device type, auxiliary information, and / or first indicator) can be determined by CN entity 250 (e.g., based on device capabilities). For example, device capabilities can be obtained from the AIoT device during the registration process (e.g., via a capability report).

[0107] From the BS's perspective, it can receive the first message from CN entity 250. In some implementations, the BS 210 can determine one or more AIoT devices 230 for service, for example, by considering the device type indicated by the first message.

[0108] Additionally, BS 210 can determine whether energy harvesting is required. In some examples, BS 210 can determine that an RF signal for energy harvesting needs to be sent to at least one AIoT device. In some embodiments, BS 210 can determine that energy harvesting is required if (1) the device type indicated by the first message is: an AIoT device, AIoT device 1, AIoT device 2a, AIoT device 2b, or a backscatter device; (2) the first message is a message dedicated to AIoT or dedicated to inventory / command; (3) the first indicator in the first message indicates that the antenna of the AIoT device used for RF energy harvesting and communication is shared; and / or (4) the auxiliary information in the first message indicates that the stored / available energy is less than the power consumption value. In other words, BS 210 can determine that an RF signal for energy harvesting should be sent to at least one AIoT device 230.

[0109] In some embodiments, BS 210 may (e.g., based on a first message) determine the duration of the RF signal used for energy harvesting. In some examples, auxiliary information in the first message may include charging time, and BS 210 may determine the duration of the RF signal used for energy harvesting based on that charging time. In some other examples, auxiliary information in the first message may include one or more of the following: energy harvesting rate, power consumption value, energy storage size, stored / available energy, and BS 210 may determine the duration of the RF signal used for energy harvesting based on one or more of the following: energy harvesting rate (e.g., denoted as...). R rate ), power consumption value (for example, expressed as E consumption ), energy storage size, stored / available energy (e.g., expressed as E stored As a non-limiting example, the duration of the RF signal used for energy harvesting can be expressed as: (1)

[0110] In some examples, the BS 210 can identify the source of the RF signal used for energy harvesting.

[0111] In some implementations, BS 210 can send an indication to a source (which may be another BS or UE) specifying that the source transmits an RF signal to at least one AIoT device for energy harvesting. In some examples, the indication to the source may include the duration of the RF signal for energy harvesting. Accordingly, the source can transmit the RF signal for energy harvesting based on the indication from BS 210.

[0112] In some other implementations, such as Figure 3 As shown, BS 210 can determine the RF signal for energy harvesting at 322 and further transmit the RF signal at 324. In some examples, BS 210 can determine that it is charging at least one AIoT device, i.e., the source is BS 210. In some examples, BS 210 can generate the RF signal and send it to an AIoT device for energy harvesting.

[0113] It should be understood that the above description of the RF signal used for energy harvesting is for illustrative purposes only and is not intended to be limiting. In some examples, BS 210 may be configured with a definition of default behavior upon receiving a first message from CN entity 250. For example, the default behavior may include: not providing an RF signal to the AIoT device. For example, the default behavior may include: sending a second message after a charging time or a waiting time, details of the transmission of the second message can be found in step 330. For example, the default behavior may include: sending (or providing) the RF signal to the AIoT device in the presence of a waiting time. For example, the waiting time may be pre-configured by OAM. For example, the waiting time may be indicated by CN entity 250 using a different message. For example, the waiting time may be indicated by another different CN entity.

[0114] In process 300, BS 210 sends a second message to one or more AIoT devices 230 at 330. In some implementations, the second message may be used as a trigger message for the process of initiating a service. In some examples, one or more AIoT devices 230 may be determined based on the first message (e.g., device type).

[0115] In some embodiments, BS 210 may send a second message after a time duration upon receiving the first message, wherein the time duration associated with the second message may include a charging time or a waiting time. For example, the time duration may be a charging time, indicated by auxiliary information in the first message. For example, the time duration may be a waiting time, which may be pre-configured by OAM or indicated by CN entity 250 or another CN entity. For example, the time duration may be the sum of the charging time and the waiting time. Therefore, the second message may not be sent until the charging time or the waiting time expires.

[0116] In some implementations, the second message can indicate the type of service, such as the service operation type discussed above.

[0117] In some examples, the second message may include an inventory cycle indicator, for example, which is included in the auxiliary information of the first message. In some examples, the second message may include (for example, included in the first message) detailed inventory information and / or detailed command information.

[0118] In some embodiments, the second message may be a RAN paging message. In some examples, a RAN paging message may be used to notify one or more AIoT devices. In some examples, the RAN paging message may explicitly include the service type, i.e., the service operation type. In some other examples, the RAN paging message may not include the service type, in which case a default type may be implicitly indicated. For example, the default type may be inventory.

[0119] In some embodiments, the second message may be an AIoT-specific message. In some examples, the second message may be an AIoT inventory trigger message or an AIoT command trigger message. In some examples, the second message may include a service type, which is command (or read, write, disable), indicating that the second message was generated due to a command service (or read service, write service, disable service). In some examples, the second message may not include a type, in which case a default type may be implicitly indicated. For example, the default type may be inventory, indicating that the second message was generated due to an inventory service.

[0120] Alternatively or concurrently, BS 210 may start a timer for the process. In some embodiments, auxiliary information in the first message may include a completion time, and BS 210 may start a timer that will expire at a time associated with the completion time. In some examples, auxiliary information in the first message may include a start time, in which case BS 210 may begin sending a second message based on the start time.

[0121] On the other side of the communication, each of the one or more AIoT devices 230 can receive the second message and, in addition, can execute the service process. Taking an AIoT device (such as the first AIoT device) as an example, the AIoT device can access BS 210 and activate the corresponding (multiple) operations.

[0122] Alternatively or concurrently, AIoT device 230 may send a third message to BS 210 at 342. The third message may include the identifier (ID) of AIoT device 230. For example, the third message may be sent on a carrier used to receive the second message.

[0123] In some implementations, the random access procedure can be performed (e.g., prior to step 342). In some example embodiments, AIoT device 230 can send a random access ID to BS 210, wherein the random access ID is transmitted on a carrier used to receive the second message. For example, AIoT device 230 can generate and send a random access ID. For example, the generated random access ID can be within a specific range, such as (0, ...). -1) or (1, Q can be a countdown round indicator included in the second message. For example, AIoT device 230 can load a random access ID into a timeslot counter, and if the timeslot counter value is zero, AIoT device 230 sends the random access ID to BS 210. Otherwise, AIoT device 230 can decrement the timeslot counter value by one upon receiving another message (e.g., another trigger message) until the value reaches zero, and send a random number to BS 210. In some example embodiments, BS 210 can send a random access ID response to AIoT device, for example, in response to receiving a random access ID. For example, BS 210 can monitor and receive the random access ID on the carrier used to send the second message. For example, the random access ID response can indicate that the random access ID was successfully received by BS 210. For example, BS 210 may not need to monitor on the carrier used to send the second message, for example, in the case where AIoT device 230 has device type device 2b.

[0124] In some implementations, the random access ID can be included in a third message. In this case, additional signaling for the random access ID may not be required, and overhead can be reduced.

[0125] In some examples, the third message can be implemented as an inventory response that includes the AIoT device ID (i.e., the AIoT device ID). In other examples, the third message may include a random access ID and an inventory response that includes the AIoT device ID.

[0126] For example, an AIoT device ID can be a protocol control for controlling the backscattering of AIoT device data, an extended protocol control for providing additional protocol control information, and / or an electronic product code for identifying the object to which the corresponding AIoT device is attached. However, it should be noted that the AIoT device ID can be implemented in another format, and this disclosure is not limited in this respect.

[0127] Alternatively or concurrently, BS 210 may send a fourth message to AIoT device 230 at point 344. In some examples, the fourth message may include an inventory confirmation, for example, when the third message is an inventory response. In some other examples, the fourth message may include a random access ID response and an inventory confirmation, for example, when the third message includes a random access ID and an inventory response. For example, the inventory confirmation may indicate that the AIoT device ID has been successfully received by BS 210.

[0128] In some examples, the fourth message may include a second indicator that indicates whether the service process has been completed. For example, the second indicator may be included in an inventory confirmation. For instance, the value of the second indicator may be set to "YES," indicating that the process between BS 210 and AIoT device 230 has been completed; in other words, no further commands (or data) will be sent to AIoT device 230, for example, if the service operation type is inventory. Alternatively, the value of the second indicator may be set to "NO," indicating that the process between BS 210 and AIoT device 230 has not been completed; in other words, no further commands (or data) will be sent to AIoT device 230, for example, if the service operation type is command (or read, write, disable).

[0129] In some examples, BS 210 may determine the value of the second indicator in the fourth message based on an indicator from CN entity 250; for example, the indicator from CN entity 250 may indicate whether a process has been completed. In some instances, BS 210 may provide the AIoT device ID to CN entity 250 upon receiving the AIoT device ID from AIoT device 230 (e.g., in a third message). CN entity 250 may determine whether the process associated with the AIoT device ID has been completed and send an indicator to BS 210.

[0130] In some examples, the fourth message may include detailed command information. For instance, if the second message indicates that the service operation type is a command (or read, write, disable), detailed command (or read, write, disable) information may be included in the fourth message. For example, detailed command information may be included in the inventory confirmation.

[0131] Alternatively or concurrently, AIoT device 230 may determine whether to disable (multiple) operations at AIoT device 230. As an illustrative example, such as... Figure 3 As shown, AIoT device 230 disables at least one operation at 350.

[0132] In some examples, if the service operation type indicated by the second message is disk storage, then deactivation can be performed by the AIoT device 230. In some examples, if the service operation type indicated by the second message is command (or read, write, disable), then deactivation can be performed by the AIoT device 230.

[0133] In some implementations, AIoT device 230 can determine whether to disable (or deactivate) the physical channels used to receive data from BS 210 and / or used to send data to BS 210.

[0134] In some examples, the downlink physical channel used to receive data from BS 210 will not be deactivated until inventory confirmation is received.

[0135] In some embodiments, step 350 may be performed before step 344. In this case, the uplink physical channel used to transmit data to BS210 may be deactivated, while the downlink physical channel used to receive data from BS210 remains active.

[0136] In some embodiments, step 350 may be performed after step 344. In some examples, both the uplink physical channel and the downlink physical channel are deactivated, for example, in response to receiving a fourth message as an inventory confirmation or including an inventory confirmation. In some examples, the fourth message may include a second indicator, and the AIoT device 230 may determine whether to activate (multiple) physical channels based on the second indicator. For example, if the value of the second indicator is “YES”, the AIoT device 230 may determine to perform deactivation. For example, if the value of the second indicator is “NO”, the AIoT device 230 may determine not to perform deactivation.

[0137] According to the reference Figure 3 In this embodiment, a process for enabling services for one or more AIoT devices can be achieved via BS 210. Specifically, a first message indicating the type of service can be sent from CN entity 250 to BS 210, thus enabling BS 210 to determine that the service is related to AIoT. Therefore, communication for one or more AIoT devices will be guaranteed.

[0138] It should be understood, for reference Figure 3 The embodiments described are for illustrative purposes only and are not limiting in any way. For example, Figure 3 Some or more steps in the process may be omitted, rearranged, modified, or combined, and may include further steps, which are not limited in this respect. The following provides... Figures 4A to 4B As a detailed example, where it is assumed Figure 2D There is a connection between AIMF 251 and AMF252.

[0139] Figure 4A The diagram illustrates a signaling process 410 involving AIoT device 230, BS 210, AMF 252, and AIMF 251.

[0140] In process 410, at point 411, AIMF 251 sends a request to AMF 252. In some examples, this request can be generated and sent if AIMF 251 wants to initiate or trigger a service for one or more AIoT devices. In some implementations, the request may indicate one or more of the following: service type, device type, assistance information, or a first indicator, details of which can be found above regarding... Figure 3 Those points have already been discussed, so this article will not repeat them.

[0141] In some embodiments, AIMF 251 may determine further information based on information already known to AIMF 252 about one or more AIoT devices. For example, the information already known to AIMF 252 may include device type and / or device capabilities. For example, the information determined by AIMF 252 may include device type, assistance information, and / or a first indicator.

[0142] In process 410, at point 412, AMF 251 sends the first message to BS 210. Details of the first message can be found in the section on... Figure 3 Those points have already been discussed, and therefore will not be repeated here. For example, the first message could be an NGAP message or another newly defined message.

[0143] In some examples, the information included in the first message may be the same as the information included in the request from AIMF 252. In some examples, the information included in the first message may be more than the information included in the request from AIMF 252. For example, AMF 251 may perform additional operations (such as calculations) to determine more information. For example, device capabilities may be used by AMF 251 to determine more information.

[0144] In process 410, at point 413, BS 210 determines the RF signal required for energy harvesting, which is consistent with... Figure 3 Step 342 is similar. Figure 4A As shown, at 414, BS 210 sends an RF signal for energy harvesting to AIoT device 230. However, it should be understood that the source of the RF signal for energy harvesting can be another device, such as another BS or UE, which is not in [the specified location]. Figure 4A As shown in the image.

[0145] In process 410, at point 415, BS 210 sends a second message (e.g., a trigger message) to AIoT device 230. Details of the second message can be found above regarding... Figure 3 Those points have already been discussed, and therefore will not be repeated here. In some embodiments, the BS 210 may start a timer associated with the completion time of the process.

[0146] In some embodiments, after step 415, option 1, option 2, or step 414 may be performed. In some embodiments, step 414 may be performed after option 1 or option 2.

[0147] Option 1 may include steps 416-420. At step 416, AIoT device 230 sends a random access ID to BS 210. For example, the random access ID may be transmitted on a carrier, on which a trigger message is received.

[0148] At step 417, BS 210 may send an access ID response to AIoT device 230, for example, based on a random access ID received from AIoT device 230. For example, the access ID response may include the received random access ID. In some instances, if the device type is one of the following: AIoT device, AIoT device 1, AIoT device 2a, or a backscatter device, BS 210 may monitor and receive the random access ID on the same carrier used to send the trigger message. In some instances, if the device type is AIoT device 2b, BS 210 does not need to monitor the same carrier. For example, a different carrier may be used by AIoT device 230 to send the random access ID.

[0149] At step 418, AIoT device 230 sends an inventory response to BS 210. The inventory response includes the AIoT device ID of AIoT device 230.

[0150] At step 419, AIoT device 230 determines whether to deactivate (or disable) the downlink physical channel and / or the uplink physical channel. For example, the default behavior of AIoT device 230 at 419 could be to deactivate the uplink physical channel while keeping the downlink physical channel active (i.e., not deactivated).

[0151] In some examples, the downlink physical channel may not be deactivated, i.e., it may be activated, and additionally, at step 420, BS 210 sends an inventory confirmation to AIoT device 230. For example, the inventory confirmation is sent in response to receiving the AIoT device ID, and may be included in the inventory response. In some instances, if the service operation type is a command (or read, write, or disable), detailed command information may be included in the inventory confirmation.

[0152] It should be noted that although step 420 is shown after step 419, in a real-world scenario, step 420 may be performed before step 419.

[0153] Option 2 may include steps 421 to 423. At step 421, AIoT device 230 sends a third message to BS 210, which includes a random access ID and an inventory response (the inventory response includes the AIoT device ID).

[0154] In some instances, if the device type is one of the following: AIoT device, AIoT device 1, AIoT device 2a, or a backscatter device, the third message can be transmitted on the carrier used to receive the trigger message. In some instances, if the device type is AIoT device 2b, the third message can be transmitted on the carrier used to receive the trigger message, or it can be transmitted on a different carrier.

[0155] At step 422, AIoT device 230 determines whether to deactivate (or disable) the downlink physical channel and / or the uplink physical channel. For example, the default behavior of AIoT device 230 at 422 could be to deactivate the uplink physical channel while keeping the downlink physical channel active (i.e., not deactivated).

[0156] In some examples, the downlink physical channel may not be deactivated, i.e., it may be activated. Additionally, at step 423, BS 210 sends a fourth message to AIoT device 230, which includes an access ID response and a storage confirmation. For example, the access ID response may indicate that a random access ID was successfully received, and the storage confirmation may indicate that an AIoT device ID was successfully received. For example, the access ID response may include the random access ID received at step 421. In some instances, if the service operation type is a command (or read, write, or disable), detailed command information may be included in the storage confirmation.

[0157] It should be noted that although step 423 is shown after step 422, in a real-world scenario, step 423 may be performed before step 422.

[0158] At step 424, AIoT device 230 may send a command acknowledgment to BS 210. In some embodiments, if detailed command information is received, for example, at steps 415, 420, or 423, AIoT device 230 may determine to send a command acknowledgment. For example, the command acknowledgment may be sent on a carrier used to receive detailed command information, for example, at steps 415, 420, or 423.

[0159] At step 425, BS 210 sends an AIoT service response to AIMF 251 via AMF 252. In some examples, if an AIoT device ID is received from an AIoT device (such as AIoT device 230), BS 210 may send an AIoT service response to AMF 252 at 425a, and correspondingly, AMF 252 may forward the AIoT service response to AIMF 251 at 425b. In some other examples, an AIoT service response is sent if an AIoT device ID from each of one or more AIoT devices is received and the completion time expires. In some other examples, an AIoT service response is sent if the delay expires.

[0160] It should be understood that Figure 4A The process 410 is for illustrative purposes only and has no limiting effect. In some examples, steps 416 to 420 of option 1 are performed, and steps 421 to 423 of option 2 are not performed. In some examples, steps 421 to 423 of option 2 are performed, and steps 416 to 420 of option 1 are not performed. In some examples, neither option 1 nor option 2 is performed, and step 424 is performed after step 415. In some examples, steps 418 to 420 of option 1 may be omitted; for example, steps 416 to 417 of option 1 are performed, and step 424 is performed after step 417. In some examples, step 424 may be omitted, and command confirmation may be combined with some other message. For example, the third message at 421 may include a random access ID and command confirmation. It should be understood that further embodiments are available, and these further embodiments are still within the scope of this disclosure.

[0161] Figure 4B The diagram illustrates a signaling process 450 involving AIoT device 230, BS 210, AMF 252, and AIMF 251.

[0162] Figure 4B Steps 411, 412, 413, 414, 415, 416, 417, 418, and 421 shown in the figure can be referenced. Figure 4A The details of the steps discussed in the previous section will not be repeated in this article.

[0163] At step 429, BS 210 sends an inventory confirmation to AIoT device 230.

[0164] In some examples, the inventory confirmation at step 429 may include a second indicator that indicates whether the service process has been completed. For example, the second indicator may be included in the inventory confirmation. For instance, the value of the second indicator may be set to "YES," indicating that the process between BS 210 and AIoT device 230 has been completed; in other words, no further commands (or data) will be sent to AIoT device 230, for example, if the service operation type is inventory. For instance, the value of the second indicator may be set to "NO," indicating that the process between BS 210 and AIoT device 230 has not been completed; in other words, no further commands (or data) will be sent to AIoT device 230, for example, if the service operation type is command (or read, write, disable) or both inventory and command (or read, write, disable).

[0165] In some examples, BS 210 may determine the value of the second indicator based on an indicator from CN entity 250, for example, the indicator from CN entity 250 may indicate whether a process has been completed. In some instances, BS 210 may provide the AIoT device ID to CN entity 250 upon receiving the AIoT device ID from AIoT device 230 (e.g., at step 418). CN entity 250 may determine whether the process associated with the AIoT device ID has been completed and send an indicator to BS 210.

[0166] At step 430, the AIoT device 230 determines whether to deactivate (or disable) the downlink physical channel and / or the uplink physical channel.

[0167] In some examples, if the inventory confirmation at 429 includes a second indicator with a value of "YES", the AIoT device 230 can determine to deactivate the downlink physical channel; alternatively, the AIoT device 230 can also deactivate or not deactivate (keep it active) the uplink physical channel. In some other examples, if the inventory confirmation at 429 includes a second indicator with a value of "NO", the AIoT device 230 can determine not to deactivate (keep it active) the downlink physical channel; alternatively, the AIoT device 230 can also deactivate or not deactivate (keep it active) the uplink physical channel.

[0168] At step 432, BS 210 sends a fourth message to AIoT device 230, which includes an access ID response and inventory confirmation.

[0169] In some examples, the fourth message may include a second indicator; for instance, the second indicator may be included in an inventory confirmation. Details regarding the second indicator can be found in the discussions above, and will not be repeated here.

[0170] At step 433, AIoT device 230 determines whether to deactivate (or disable) the downlink physical channel and / or the uplink physical channel, which is similar to step 430 in option 1.

[0171] At step 434, BS 210 sends an AIoT inventory response to AIMF 251 via AMF 252, wherein the AIoT inventory response may include the AIoT device ID.

[0172] At step 435, AIMF 251 sends AIoT commands to AIoT device 230 via AMF 252 and BS 210. In some examples, AIoT device 230 may perform multiple operations based on AIoT commands.

[0173] At step 436, AIoT device 230 sends a command confirmation to AIMF 251 via BS 210 and AMF 252.

[0174] It should be understood that Figure 4B Procedure 450 is for illustrative purposes only and has no limitations. In some examples, steps 416 to 418 and 429 to 430 of option 1 are performed, and steps 421 and 432 to 433 of option 2 are not performed. In some examples, steps 421 and 432 to 433 of option 2 are performed, and steps 416 to 418 and 429 to 430 of option 1 are not performed. In some examples, the trigger message at 415 in procedure 450 may not include detailed command information, which may be provided at step 435. In some examples, the trigger message at 415 in procedure 450 may be an NGAP message or a message dedicated to inventory services. In some examples, in option 1, steps 434, 435a, and 435b are performed before step 429, and step 435c is included in step 429. In some examples, in option 2, steps 434, 435a, and 435b are performed before step 432, and step 435c is included in step 432.

[0175] Based on some embodiments discussed above, a solution for supporting AIoT services is provided. The type of service and / or device type can be indicated, and thus the BS 210 can distinguish AIoT devices from traditional UEs. The behavior at the BS is defined, for example, based on the type of service (i.e., service operation type). For inventory services, the BS initiates an inventory process toward the AIoT device. The BS can forward the service operation type to the AIoT device. In other options, after receiving the AIoT device ID from the AIoT device, or after receiving a completion indication from the CN entity, the BS can send an indicator to the AIoT device indicating that the process has been completed. For command services, the BS can initiate an inventory process toward the AIoT device. After receiving the AIoT device ID through the inventory process, the BS forwards a detailed command message (e.g., in a NAS message) to the AIoT device. In other options, the BS can forward the command message to the AIoT device without initiating an inventory process. The behavior at the AIoT is defined, for example, based on the type of service received (i.e., service operation type). For command services, the AIoT device should remain active after the inventory process (e.g., activating physical channel transmission to receive / send data from the BS). Alternatively, after providing command confirmation to the BS, the AIoT device can deactivate physical channel transmission to receive / send data from the BS. For inventory services, after providing the AIoT device ID to the BS, the AIoT device can deactivate physical channel transmission to receive / send data from the BS. For full services, the AIoT device should remain active after the inventory process (e.g., activating physical channel transmission to receive / send data from the BS). Alternatively, the default behavior is to deactivate physical channel transmission to receive / send data from the BS after providing the AIoT device ID to the BS.

[0176] Figure 5 An example of a device 500 suitable for implementing embodiments of the present disclosure is illustrated. Device 500 may be an example of a UE or BS as described herein. Device 500 may support wireless communication with BS 210, AIoT device 230, CN entity 250, or any combination thereof. Device 500 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 502, memory 504, transceiver 506, and optional I / O controller 508. These components may communicate electronically or be otherwise coupled (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0177] Processor 502, memory 504, transceiver 506, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the present disclosure described herein. For example, processor 502, memory 504, transceiver 506, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0178] In some implementations, processor 502, memory 504, transceiver 506, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuitry system). The hardware may include a processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise supporting components for performing the functions described in this disclosure. In some implementations, processor 502 and memory 504 coupled to processor 502 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 504 by processor 502).

[0179] For example, according to the examples disclosed herein, processor 502 can support wireless communication at device 500. Processor 502 can be configured to be operable as a component to support the aforementioned actions.

[0180] Processor 502 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some implementations, processor 502 may be configured to use a memory controller to operate a memory array. In some other implementations, the memory controller may be integrated into processor 502. Processor 502 may be configured to execute computer-readable instructions stored in memory (e.g., memory 504) to cause device 500 to perform various functions of this disclosure.

[0181] Memory 504 may include random access memory (RAM) and read-only memory (ROM). Memory 504 may store computer-readable, computer-executable code, including instructions that, when executed by processor 502, cause device 500 to perform the various functions described herein. This code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 502, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 504 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0182] I / O controller 508 can manage input and output signals for device 500. I / O controller 508 can also manage peripheral devices not integrated into device 500. In some implementations, I / O controller 508 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 508 can utilize an operating system such as iOS®, ANDROID®, MS WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. In some implementations, I / O controller 508 can be implemented as part of a processor, such as processor 502. In some implementations, a user can interact with device 500 via I / O controller 508 or via hardware components controlled by I / O controller 508.

[0183] In some implementations, device 500 may include a single antenna 510. However, in other implementations, device 500 may have more than one antenna 510 (i.e., multiple antennas), including multiple antenna panels or antenna arrays, which may be able to transmit or receive multiple wireless transmissions concurrently. Transceiver 506 may communicate bidirectionally via one or more antennas 510, wired or wireless links, as described herein. For example, transceiver 506 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 506 may also include a modem for modulating packets, providing modulated packets to one or more antennas 510 for transmission, and demodulating packets received from one or more antennas 510. Transceiver 506 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0184] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium. 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 such as phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain 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. The transmission chain may also include one or more antennas 510 for transmitting the amplified signal into the air or wireless medium.

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

[0186] Figure 6 An example of a processor 600 suitable for implementing some embodiments of the present disclosure is illustrated. Processor 600 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 600 may include a controller 602 configured to perform various operations according to the examples described herein. Processor 600 may optionally include at least one memory 604, such as an L1 / L2 / L3 cache. Additionally or alternatively, processor 600 may optionally include one or more arithmetic logic units (ALUs) 606. 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).

[0187] Processor 600 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., processor chipset-local or included memory (e.g., processor 600)) or other memory (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), etc.).

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

[0189] Controller 602 may be configured to fetch (e.g., fetch, retrieve, receive) instructions from memory 604 and determine subsequent instructions(s) to be executed, such that processor 600 supports various operations according to the examples described herein. Controller 602 may be configured to track the memory addresses of instructions associated with memory 604. Controller 602 may be configured to decode instructions to determine the operations to be performed and the operands involved. For example, controller 602 may be configured to interpret instructions and determine control signals to be output to other components of processor 600, such that processor 600 supports various operations according to the examples described herein. Additionally or alternatively, controller 602 may be configured to manage data flow within processor 600. Controller 602 may be configured to control data transfers between registers, arithmetic logic unit (ALU), and other functional units of processor 600.

[0190] Memory 604 may include one or more caches (e.g., memory local to processor 600 or included in processor 600) or other memories such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, memory 604 may reside within or on the processor chipset (e.g., locally on processor 600). In other implementations, memory 604 may reside outside the processor chipset (e.g., remotely from processor 600).

[0191] Memory 604 may store computer-readable, computer-executable code, including instructions that, when executed by processor 600, cause processor 600 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. Controller 602 and / or processor 600 may be configured to execute computer-readable instructions stored in memory 604 to cause processor 600 to perform various functions. For example, processor 600 and / or controller 602 may be coupled to or coupled to memory 604, and processor 600, controller 602, and memory 604 may be configured to perform the various functions described herein. In some examples, processor 600 may include multiple processors, and memory 604 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 configured individually or collectively to perform the various functions described herein.

[0192] One or more ALU 606s can be configured to support various operations as described in the examples herein. In some implementations, one or more ALU 606s may reside within or on the processor chipset (e.g., processor 600). In other implementations, one or more ALU 606s may reside outside the processor chipset (e.g., processor 600). One or more ALU 606s can perform one or more operations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 606s can receive input operands and opcodes that determine the operation to be performed. One or more ALU 606s are configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operations. Alternatively or concurrently, one or more ALU 606s may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALU 606s to handle conditional operations, comparisons, and bitwise operations.

[0193] Based on the examples disclosed herein, processor 600 may support wireless communication. Processor 600 may be configured or operable to support components used in some embodiments of this disclosure.

[0194] Figure 7 A flowchart illustrating a method 700 performed by a UE according to various aspects of this disclosure is shown. The operation of method 700 can be implemented by the device or its components described herein. For example, the operation of method 700 can be performed by… Figure 2B The device executes BS 210. In some implementations, the device can execute an instruction set to control the functional elements of the device to perform the described functions. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the described functions.

[0195] At 710, the method may include: receiving a first message from a core network entity, the first message indicating the type of service for one or more AIoT devices, wherein the service is associated with at least one of: an inventory request or a command request. The operation of 710 can be performed according to the examples described herein. In some implementations, aspects of the operation of 710 may be derived from references... Figure 2B The aforementioned BS 210 is executed.

[0196] At 720, the method may include sending a second message to one or more AIoT devices, the second message including an indication of the type of procedure for initiating a service. The operation at 720 can be performed according to the examples described herein. In some implementations, aspects of the operation at 720 may be derived from references... Figure 2B The aforementioned BS 210 is executed.

[0197] Figure 8 A flowchart illustrating method 800 performed by a core network entity according to various aspects of this disclosure is provided. Operation of method 800 may be implemented by the devices or components thereof described herein. For example, operation of method 800 may be performed by… Figure 2B The CN entity 250 in the document executes the function. In some implementations, the device can execute an instruction set to control the functional elements of the device to perform the described function. Alternatively or concurrently, the device can use dedicated hardware to perform aspects of the described function.

[0198] At 810, the method may include: determining to initiate a service for one or more AIoT devices. The operation at 810 can be performed according to the examples described herein. In some implementations, aspects of the operation at 810 can be found in the references. Figure 2B The CN entity 250 described is executed.

[0199] At 820, the method may include: sending a first message to a base station, the first message indicating the type of service for one or more AIoT devices, wherein the service is associated with at least one of: an inventory request or a command request. The operation of 820 can be performed according to the examples described herein. In some implementations, aspects of the operation of 820 may be derived from references... Figure 2B The CN entity 250 described is executed.

[0200] Figure 9 A flowchart illustrating a method 900 performed by an AIoT device according to various aspects of this disclosure is shown. Operation of method 900 can be implemented by the device or its components described herein. For example, operation of method 900 can be performed by… Figure 2B The AIoT device 230 performs this function. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively or alternatively, the device can use dedicated hardware to perform aspects of the described function.

[0201] At 910, the method may include: receiving a second message from a base station, the second message including an indication of the type of service for initiating a service procedure, wherein the service is associated with at least one of: an inventory request or a command request. The operation of 910 can be performed according to the examples described herein. In some implementations, aspects of the operation of 910 may be derived from references... Figure 2B The AIoT device 230 performs the operation.

[0202] At 920, the method may include enabling the service used for the procedure. The operation at 920 can be performed according to the examples described herein. In some implementations, aspects of the operation at 920 may be derived from references. Figure 2B The AIoT device 230 performs the operation.

[0203] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0204] The various illustrative blocks and components disclosed herein can be implemented or executed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0205] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented at different physical locations.

[0206] Computer-readable media include both non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0207] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to refer to “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, including in the claims, the use of “or” in a list of items (e.g., a list of items beginning with phrases such as “at least one of…” or “one or more of…” or “one or two of…”) indicates an inclusive list, 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 closed set of conditions. For example, an example step described as “based on condition A” without departing from the scope of this disclosure could be based on both condition A and condition B. 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, including in the claims, “set” can include one or more elements.

[0208] The description provided herein is intended to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can 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 should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A base station, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the base station: A first message is received from the core network entity, indicating the type of service for one or more Ambient Internet of Things (AIoT) devices, wherein the service is associated with at least one of the following: an inventory request or a command request; and Send a second message to the one or more AIoT devices, the second message including an indication of the type of procedure for initiating the service.

2. The base station according to claim 1, wherein the type includes one of the following: Used to identify the inventory type of each of the one or more AIoT devices; Command types used to perform operations related to the one or more AIoT devices; The read type used to read data from the one or more AIoT devices; Write type used to write data to the one or more AIoT devices; or The disable type is used to disable one or more AIoT devices.

3. The base station according to claim 1, wherein the first message further indicates the device type of the one or more AIoT devices.

4. The base station according to claim 3, wherein the device type includes one of the following: Types of AIoT devices; Types of backscattering devices; AIoT devices of the first type with power consumption values ​​below a first threshold; A second type of AIoT device having power consumption values ​​within the range of the first threshold to the second threshold and having backscattered transmission on the carrier; or A third type of AIoT device has power consumption values ​​ranging from the first threshold to the second threshold and has internally generated transmission.

5. The base station according to claim 1, wherein the first message includes auxiliary information for the process of the service.

6. The base station according to claim 5, wherein the auxiliary information indicates one of the following: The energy harvesting rate for the process at each of the one or more AIoT devices; Charging time for the process; The power consumption value used in the process; The energy storage size for the process at each of the one or more AIoT devices; Energy stored or available at each of the one or more AIoT devices during the process; The start time of the process; The completion time of the process; The time delay required for the process; or Inventory round indicator when the process is associated with the inventory request.

7. The base station of claim 6, wherein the at least one processor is further configured to cause the base station to: Based on the completion time indicated by the auxiliary information, a timer for the process is started based on the completion time.

8. The base station of claim 1, wherein the first message includes a first indicator indicating whether the antennas of the one or more AIoT devices are shared between energy harvesting and communication.

9. The base station of claim 1, wherein the at least one processor is further configured to cause the base station to: Based on the first message, it is determined that energy harvesting is required for at least one of the one or more AIoT devices.

10. The base station of claim 9, wherein the at least one processor is further configured to cause the base station to: Generate at least one radio frequency (RF) signal for energy harvesting; and Send the at least one RF signal to at least one of the one or more AIoT devices.

11. The base station of claim 1, wherein the at least one processor is further configured to cause the base station to: Send an instruction to the energy harvesting source, the instruction instructing the source to send at least one RF signal for energy harvesting to at least one of the one or more AIoT devices.

12. The base station of claim 1, wherein the second message is sent after a time duration, wherein the time duration includes one of the following: The charging time indicated by the first message; The waiting time for data to be received from the core network entity or another core network entity; or Waiting time configured by Operations Management and Maintenance (OAM).

13. The base station of claim 1, wherein the at least one processor is further configured to cause the base station to: Receive an indicator from the core network entity, the indicator indicating whether the process has been completed.

14. A core network entity, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the core network entity: Determine to initiate a service for one or more Ambient Internet of Things (AIoT) devices; as well as A first message is sent to the base station, the first message indicating the type of service for the one or more AIoT devices, wherein the service is associated with at least one of the following: inventory request or command request.

15. An environmental Internet of Things (AIoT) device, comprising: At least one memory; as well as At least one processor, coupled to the at least one memory, and configured such that the AIoT device: A second message is received from the base station, the second message including an indication of the type of service for initiating a service procedure, wherein the service is associated with at least one of: an inventory request or a command request; and Enable the service used in the process.

16. The AIoT device of claim 15, wherein the at least one processor is further configured to cause the AIoT device to: Receive at least one radio frequency (RF) signal for energy harvesting from the base station or the energy harvesting source.

17. The AIoT device of claim 15, wherein the at least one processor is further configured to cause the AIoT device to: A third message is sent to the base station, the third message including the identifier of the AIoT device.

18. The AIoT device of claim 17, wherein the at least one processor is further configured to cause the AIoT device to: A fourth message is received from the base station, the fourth message indicating confirmation of the third message.

19. The AIoT device of claim 18, wherein the fourth message includes a second indicator indicating whether the process has been completed.

20. The AIoT device of claim 18, wherein the fourth message includes a command request.

Images