The process is processed

Abstract

Various aspects of the present disclosure relate to processing of processes, such as Ambient Internet of Things (AIoT) processes. In an aspect, a first device determines that a link between the first device and a second device is unavailable for data transmission. The first device suspends, based on the determination, an operational process for at least one third device. Based on a determination that the link becomes available, the first device transmits, via a transceiver, to the second device, data associated with one or more of the at least one third device stored during the suspension of the operational process. In this way, a solution for processing processes is presented, in particular, a solution for AIoT intermediate nodes to handle AIoT processes in case the NR Uu link is unavailable for data transmission is presented, thereby improving communication performance, such as in AIoT communications.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically, to the processing of operational processes (e.g., environmental Internet of Things (AIoT) processes). Background Technology

[0002] A wireless communication system may include one or more network communication devices (such as base stations (BS)), 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 with one or more user communication devices, which may also be referred to as user equipment (UE) or other suitable terms. The wireless communication system 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)). Furthermore, 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 beyond 5G (e.g., sixth-generation (6G)).

[0003] In recent years, the Internet of Things (IoT) has garnered significant attention in the field of wireless communication. The expectation is for more interconnected "things" to improve productivity and enhance quality of life. Further reductions in the size, complexity, and power consumption of IoT devices could enable the deployment of hundreds of billions or even trillions of IoT devices across a wide range of applications, providing added value throughout the value chain. However, it is impossible to power all IoT devices with batteries that require manual replacement or recharging. Therefore, several issues related to communication devices, such as Ambient Internet of Things (A-IoT) devices, remain to be addressed. Summary of the Invention

[0004] This disclosure relates to methods, apparatus, and systems for supporting the processing of processes such as environmental Internet of Things (IoT) processes.

[0005] Some implementations of the methods and apparatus described herein include: determining that a link between a first device and a second device is unavailable for data transmission; based on this determination, suspending an operation process for at least one third device; and based on the determination that the link becomes available, transmitting, via a transceiver, data associated with one or more of the at least one third device that was stored during the suspended operation process to the second device.

[0006] In some implementations of the methods and devices described herein, a link unavailability is determined based on one or more of the following: a first module in the first device for communicating with the second device determines that the link is unavailable; the first module determines that data from one of at least one third device failed to be sent to the second device; or the first module uses a model to predict that the link will be unavailable.

[0007] Some implementations of the methods and devices described herein may include: sending a first indication from a first module to a second module in a first device, the first indication indicating that the link is unavailable. The first module may be used to communicate with the second device, and the second module may be used to communicate with at least one third device.

[0008] Some implementations of the methods and devices described herein may include sending a reason for link unavailability from a first module to a second module in a first device. The first module may be used to communicate with the second device, and the second module may be used to communicate with at least one third device.

[0009] In some implementations of the methods and devices described herein, the cause may include one of the following: radio link failure (RLF) in the link between the first device and the second device; handover of the first device; re-establishment of the link; the first device being in an idle or inactive state without small data transmission configuration; or random access failure of the first device.

[0010] Some implementations of the methods and devices described herein may include pausing the operation process after the second module receives the first instruction or after the first module determines that the link is unavailable for data transmission.

[0011] Some implementations of the methods and devices described herein may include pausing the operation process at the following points in time: when the second module receives the first instruction; at the end of an access opportunity, completing an operation process with one of at least one third device in the first device during that access opportunity; or at the end of an access round that includes multiple access opportunities, wherein the multiple access opportunities include access opportunities.

[0012] Some implementations of the methods and devices described herein may include performing the operation based on one or more of the following: receiving a reported device identifier (ID) from at least one of the at least three third devices; receiving data from at least one of the at least three third devices; sending an acknowledgment (ACK) to at least one of the at least three third devices; or sending a second indication to at least one of the at least three third devices indicating the end of the operation at the access point.

[0013] In some implementations of the methods and devices described herein, the time point is determined based on one or more of the following: configuration information indicating the time point; resource configuration information for the operation process; or the caching capability of the second module.

[0014] Some implementations of the methods and devices described herein may include: continuing an operation process in an access timing after the second module receives the first instruction and before pausing the operation process, in which the first device performs an operation process with one of at least one third device and a link unavailability occurs; or an operation process in an access round comprising multiple access timings, wherein the multiple access timings include access timings.

[0015] In some implementations of the methods and apparatus described herein, the operation process continues during the access timing, and some implementations of the methods and apparatus described herein may include sending a second indication via a transceiver to at least one third device, the second indication indicating the end of the operation process during the access timing.

[0016] In some implementations of the methods and devices described herein, the second indication is an acknowledgment (ACK) of data received from one of at least one third device.

[0017] Some implementations of the methods and devices described herein may include continuing the operation process in an access round by: determining the end of an access opportunity based on receiving data from one of at least one third device during the access opportunity; and initiating a subsequent access opportunity in which the first device performs the operation process with another of at least one third device.

[0018] Some implementations of the methods and devices described herein may include pausing the operation process by: avoiding sending subsequent messages via transceiver to at least one third device associated with the operation process of one of the at least one third device; avoiding sending via transceiver to at least one third device a message for initiating a subsequent access timing in which the first device performs an operation process with another of the at least one third device; or avoiding sending via transceiver to at least one third device a message for initiating a subsequent access round after an access round in which link unavailability occurs.

[0019] Some implementations of the methods and devices described herein may include sending a third instruction via a transceiver to at least one third device, the third instruction indicating that the operation process is suspended.

[0020] Some implementations of the methods and devices described herein may include storing data received from one or more third devices, at least one of which are third devices, after the pause operation process and before data transmission.

[0021] Some implementations of the methods and devices described herein may include starting a timer based on one of the following: determining to pause the operation process; pausing the operation process; a second module in the first device for communicating with at least one third device receiving a first indication that the link is unavailable; or a first module in the first device for communicating with the second device determining that the link is unavailable for data transmission.

[0022] Some implementations of the methods and devices described in this document may include receiving one or more values ​​of a timer from a second device via a transceiver.

[0023] In some implementations of the methods and devices described in this paper, one or more values ​​of the timer are specific to the reason why the link is unavailable.

[0024] Some implementations of the methods and devices described herein may include stopping a timer based on one or more of the following: a second module in the first device for communicating with at least one third device receives a fourth indication that a link is available for data transmission; a first module in the first device for communicating with a second device determines that a link is available for data transmission; data is successfully transmitted to the second device during the pause operation; or an uplink transmission between the first device and the second device is available.

[0025] Some implementations of the methods and devices described herein may include: transmitting data stored during the pause operation process to a second device via a transceiver when the timer is stopped.

[0026] Some implementations of the methods and devices described in this article may include terminating the operation process upon the expiration of a timer.

[0027] Some implementations of the methods and apparatus described herein may include terminating the operation process by: sending a fifth indication indicating that the operation process has been terminated to at least one third device via a transceiver; and releasing data stored in the first device.

[0028] Some implementations of the methods and apparatus described herein may include: starting a timer at one of the following: the radio resource control (RRC) layer of a second module in a first device for communicating with at least one third device; or the media access control (MAC) layer of the second module.

[0029] Some implementations of the methods and apparatus described herein may include: receiving a third instruction from a first device via a transceiver, the third instruction indicating that an operation process performed by the first device for the third device is suspended; and, based on the third instruction, stopping at least one operation associated with the operation process.

[0030] Some implementations of the methods and devices described in this article may include setting a third device to a waiting state.

[0031] In some implementations of the methods and devices described herein, the operation process is performed at multiple access times, and some implementations of the methods and devices described herein may include receiving, via a transceiver, a second indication from a first device that the operation process at one of the multiple access times has ended.

[0032] Some implementations of the methods and apparatus described herein may include receiving, via a transceiver, a fifth indication that the operation process has been terminated from a first device.

[0033] Some implementations of the methods and devices described herein may include: sending one or more values ​​of a timer at the first device to the first device via a transceiver, wherein the one or more values ​​are associated with a time length during which the operation performed by the first device is paused. Attached Figure Description

[0034] Figure 1A An example of a wireless communication system supporting the Internet of Things (AIoT) process processing according to various aspects of this disclosure is illustrated.

[0035] Figure 1B An example of Topology 1 associated with various aspects of this disclosure is illustrated.

[0036] Figure 1C An example of Topology 2 associated with various aspects of this disclosure is illustrated.

[0037] Figure 1D An example of topology 3 associated with various aspects of this disclosure is illustrated.

[0038] Figure 1E Another example of topology 3 associated with various aspects of this disclosure is illustrated.

[0039] Figure 1F An example of topology 4 associated with various aspects of this disclosure is illustrated.

[0040] Figure 2 The illustration shows an example signaling diagram illustrating an example flow of environmental Internet of Things (AIoT) process processing according to various aspects of this disclosure.

[0041] Figure 3An example of a device supporting the Internet of Things (AIoT) process according to various aspects of this disclosure is illustrated.

[0042] Figure 4 An example of a processor for supporting environment Internet of Things (AIoT) process processing according to various aspects of this disclosure is illustrated.

[0043] Figure 5 The diagram illustrates a flowchart of a method for processing Internet of Things (AIoT) processes in a supporting environment according to various aspects of this disclosure.

[0044] Figure 6 The diagram illustrates a flowchart of a method for processing Internet of Things (AIoT) processes in a supporting environment according to various aspects of this disclosure.

[0045] Figure 7 The diagram illustrates a flowchart of a method for processing Internet of Things (AIoT) processes in a supporting environment according to various aspects of this disclosure. Detailed Implementation

[0046] 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 impose any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below.

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

[0048] References to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., in this disclosure indicate that the described embodiments(s) may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, these 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) affecting such a feature, structure, or characteristic is within the scope of their knowledge.

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

[0050] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. Unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” used herein also include the plural forms. Furthermore, it should be understood that the terms “comprises,” “comprising,” “has,” “having,” “includes,” and / or “including” as used herein specify the presence of the stated 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.

[0051] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as 5G New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between user equipment and network equipment in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, and / or any other communication protocols currently known or to be developed in the future. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will be future types of communication technologies and systems in which this disclosure can be embodied. This should not be construed as limiting the scope of this disclosure to the systems described above.

[0052] As used herein, the term "network device" generally refers to a node in a communication network through which user equipment can access and receive services. Network devices can refer to base stations (BS) or access points (APs), such as Node B (NodeB or NB), Radio Access Network (RAN) nodes, Evolved Node B (eNodeB or eNB), NRNB (also known as gNB), Remote Radio Unit (RRU), Radio Header (RH), infrastructure equipment for Vehicle-to-Everything (V2X) communication, Transmitter Receiver Point (TRP), Receiver Point (RP), Remote Radio Header End (RRH), relay, Integrated Access and Backhaul (IAB) nodes, and low-power nodes (such as femtocells (BS), picocells, etc.), depending on the terminology and technology applied. Network devices can also refer to network functions (NFs) in the core network, such as SMF, AMF, PCF, UPF, or devices with similar functions in future network architectures.

[0053] As used herein, the term “user equipment (UE)” generally refers to any terminal device capable of wireless communication. By way of example and not limitation, a user equipment may also be referred to as a communication device, terminal device, end-user equipment, subscriber station (SS), unmanned aerial vehicle (UAV), portable subscriber station, mobile station (MS), or access terminal (AT). User equipment may include, but is not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable user devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture user devices (such as digital cameras), gaming user devices, music storage and playback devices, in-vehicle wireless user devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices (e.g., remote surgical equipment), industrial equipment (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "user equipment", "communication equipment", "terminal" and "user equipment" are used interchangeably.

[0054] As used herein, the term "Ambient Internet of Things (A-IoT) device" refers to a device without a battery or with limited energy storage capacity. For A-IoT devices, energy is provided by harvesting radio waves, light, motion, heat, or any other suitable source. A-IoT devices may also be referred to as zero-power terminals, near-zero-power terminals, passive IoT devices, ambient backscatter communication (AmBC) devices, tags, etc. Compared to low-power, wide-coverage services such as narrowband (NB) IoT and enhanced machine-type communication (eMTC), A-IoT offers lower complexity and lower power consumption, and is suitable for a wider range of applications.

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

[0056] Figure 1AAn example of a wireless communication system (or communication network) 100 supporting environment Internet of Things (AIoT) process processing according to various aspects of this disclosure is illustrated. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the 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, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies, including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies beyond 5G. 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).

[0057] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. One or more of the network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceiver stations, access points, NodeBs, eNodeBs (eNBs), next-generation NodeBs (gNBs), or other suitable terms. Alternatively, network entity 102 may be a UE-type device, such as an intermediate node in some embodiments. Network entity 102 and UE 104 may communicate via communication link 110, which may be a wireless or wired connection. For example, network entity 102 and UE 104 may perform wireless communication (e.g., receive signaling, send signaling) through a communication interface.

[0058] Network entity 102 may provide a geographic coverage area 112 for which network entity 102 supports 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 wireless 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 any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0059] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. 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, etc. 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.

[0060] One or more UEs 104 can be devices of different forms or with different capabilities. Figure 1A The diagram illustrates some examples of UE 104. UE 104 is capable of communicating with various types of devices, such as network entity 102, other UEs 104, or network devices (e.g., core network 106, packet data network 108, relay equipment, integrated access and backhaul (IAB) node, or another network device). Figure 1A As shown. Alternatively or concurrently, UE 104 may support communication with other network entities 102 or UE 104 that may be used as relays in wireless communication system 100.

[0061] 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 sidechain. For example, UE 104 can support direct wireless communication with another UE 104 via a communication interface.

[0062] Network entity 102 may support communication with core network 106 or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, 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 core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). An 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 headends, smart radio headends, or transmit-receive points (TRPs)).

[0063] In some implementations, network entity 102 can be configured with a decomposed architecture that can utilize protocol stacks physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open Radio Access Network (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 a Central Unit (CU), Distributed Unit (DU), Radio Unit (RU), RAN Intelligent Controller (RIC) (e.g., near real-time RIC, non-real-time RIC), Service Management and Orchestration (SMO) system, or any combination thereof.

[0064] An RU can also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit-receive point (TRP). In a decomposed RAN architecture, one or more components of network entity 102 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 a decomposed RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0065] The functional decomposition between CU, DU, and RU can be flexible and can support different functions based on the functions performed at the CU, DU, or RU (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof). For example, a protocol stack functional decomposition can be used between the CU and DU, allowing the CU to support one or more layers of the protocol stack and the DU to 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., 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) layer, MAC layer), and each can be at least partially controlled by the CU.

[0066] Alternatively, a functional split of the protocol stack can be employed between the DU and RU, allowing the DU to support one or more layers of the protocol stack and the RU to support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional split between the CU and DU, or between the DU and RU, can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by different items in the CU, DU, or RU).

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

[0068] Core network 106 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 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 packets or interconnects 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.) of one or more UEs 104 served by one or more network entities 102 associated with core network 106.

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

[0070] 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 basic configurations.

[0071] The wireless communication system 100 may support one or more digital basic configurations, and the digital basic configurations may include subcarrier spacing and cyclic prefixes. A first digital basic configuration (e.g., μ =0) can be associated with the first subcarrier spacing (e.g., 15kHz) and the normal cyclic prefix. In some implementations, the first digital basic configuration (e.g., ) associated with the first subcarrier spacing (e.g., 15kHz) is... μ =0) can utilize one time slot per subframe. Second digital basic configuration (e.g., μ =1) can be associated with the second subcarrier spacing (e.g., 30kHz) and the normal cyclic prefix. The third digital basic configuration (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 basic configuration (e.g., μ =3) can be associated with the fourth subcarrier spacing (e.g., 120kHz) and a normal cyclic prefix. The fifth digital basic configuration (e.g., μ =4) can be associated with the fifth subcarrier spacing (e.g., 240 kHz) and the normal cyclic prefix.

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

[0073] 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 basic configurations supported in the wireless communication system 100. For example, a first digital basic configuration, a second digital basic configuration, a third digital basic configuration, a fourth digital basic configuration, and a fifth digital basic configuration (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., OFDM symbols). In some implementations, the number (e.g., quantity) of time slots in a subframe can depend on the digital basic configuration. For a normal cyclic prefix, a time slot can include 14 symbols. For an extended cyclic prefix (e.g., for a 60kHz 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 basic configuration. It should be understood that for a first digital basic configuration (e.g., quantity) associated with a first subcarrier spacing (e.g., 15kHz), μ The reference of =0 can be used interchangeably between subframes and time slots.

[0074] 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 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). 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, along with 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, along with other devices or apparatuses, for short-range, high data rate capabilities.

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

[0076] In recent years, the Internet of Things (IoT) has attracted widespread attention in the field of wireless communication. It is anticipated that more "things" will be interconnected to improve productivity and increase comfort. Most wireless IoT devices are powered by batteries that require manual replacement or charging. Automation and digitalization across various industries have opened up many new markets, requiring new IoT technologies to support battery-free devices without energy storage capabilities or devices with energy storage that do not require manual replacement or charging.

[0077] Within 3GPP, the 3GPP Technical Specification Group (TSG) SA WG1 (SA1) is developing TR 22.840 to capture use cases, service scenarios, and device constraints for ambient power-enabled IoT, and to identify new potential service requirements and new key performance indicators (KPIs). The TSG Radio Access Network (RAN) has completed the Rel-18 RAN-level Study Project (SI) on ambient IoT, providing a terminology and scope framework for future discussions on ambient IoT. At the RAN#102 meeting, a new Study Project Description (SID) was approved for ongoing research on such wireless IoT devices, termed Ambient IoT Devices. One goal is to design a compact protocol stack and corresponding procedures, such as paging, random access, and data transmission.

[0078] The study investigates and determines the functionalities required for a compact protocol stack and lightweight signaling processes in the IoT environment to enable Device Initiation-Device Termination Trigger (DO-DTT) and Device Termination (DT) data transmission, and studies these functionalities. Examples include paging, random access, data transmission, including necessary radio resource control aspects, respecting general scope limitations, and interaction with upper layers. Functionality not listed above will only be studied if deemed necessary. The SID also approved the general scope for the following aspects A through E.

[0079] For aspect A, the overall objective should be to study a coordinated air interface design that minimizes environmental IoT variations (where necessary) to enable devices (i) and (ii) as follows. Device (i) has approximately 1 µ Peak power consumption of W, with energy storage, up to 10 X The initial sampling frequency offset (SFO) is ppm, and the device has neither downlink (DL) amplification nor uplink (UL) amplification. The UL transmission of device (i) is backscattered on an externally provided carrier. Device (ii) has no more than a few hundred ppm. µ Peak power consumption of W, with energy storage, up to 10X The initial sampling frequency offset (SFO) is ppm, and the device has both DL and / or UL amplification. The UL transmission of device (ii) can be generated internally by device (ii) or backscattered on an externally provided carrier. X will be determined in WG. According to TR 38.848, the coverage design objective is a maximum distance of 10-50m for indoor devices. For topologies 1 and 2 (UE as an intermediate node under network (NW) control) according to TR 38.848, there is no RRC state, no mobility (i.e., at least no cell selection / reselection function), no HARQ, and no ARQ. It should be understood that "not exceeding several hundred μW" means that WG does not undertake the task of setting specific values, and it will be determined by WG discussion whether the presented design with the corresponding power consumption meets the requirement of "not exceeding several hundred μW".

[0080] For aspect B, it is approved in deployment scenarios with the following characteristics, referring to Table 4.2.2 of TR 38.848, such as deployment scenario 1 with topology 1 and deployment scenario 2 with topology 2. In deployment scenario 1 with topology 1, the base station and coexistence characteristics can be microcells or co-site. In deployment scenario 2 with topology 2, the UE acts as an intermediate node under network control. The base station and coexistence characteristics can be macrocells or co-site. The intermediate node is located indoors.

[0081] For aspect C, it is approved in the FR1 licensed spectrum of FDD. For aspect D, it is approved in in-band to NR spectrum deployment, in guard band to LTE / NR spectrum deployment, and in one or more independent frequency bands. For aspect E, it is approved in service types DO-DTT and DT, focusing on rUC1 (indoor inventory) and rUC4 (indoor command). Starting with RAN#104, this study will evaluate whether the coordinated air interface design (according to aspect A above) can address the DO-A (device-initiated autonomy) use case, to identify only which(s) of the coordinated air interface design (according to aspect A above) is insufficient for the DO-A use case. Transmissions from environmental IoT devices (including backscattering during use) can occur at least in the UL spectrum.

[0082] Two sets or levels of groups are defined for some representative use cases (or purposes), where group A is based on one or more deployment environments described for use cases in TR 22.840, and group B is based on functions / applications described in TR 22.840. Group A may include: indoor, outdoor, and indoor / outdoor. Group B may include: inventory, sensors, positioning, and commands. Deployment scenarios for environmental IoT are studied based on a series of characteristics and one or more representative use cases applicable to the scenarios. Deployment scenarios may include deployment scenarios 1 to 5 as shown in Tables 1 to 5, respectively. Deployment scenario 1 involves indoor devices and indoor base stations. Deployment scenario 2 involves indoor devices and outdoor base stations. Deployment scenario 3 involves indoor devices and UE-based readers. Deployment scenario 4 involves outdoor devices and outdoor base stations. Deployment scenario 5 involves outdoor devices and UE-based readers.

[0083] In the case of indoor IoT devices and indoor base stations, deployment scenario 1 is characterized according to Table 1. It should be noted that the descriptions in Table 1 may not apply to some devices (A, B).

[0084] Table 1

[0085] In the case of indoor IoT devices and outdoor base stations, deployment scenario 2 is characterized according to Table 2. It should be noted that the descriptions in Table 2 may not apply to some devices (A, B).

[0086] Table 2

[0087] In the case of indoor IoT devices and UE-based readers, deployment scenario 3 is characterized according to Table 3. It should be noted that the descriptions in Table 3 may not apply to some devices (A, B).

[0088] Table 3

[0089] In the case of outdoor IoT devices and outdoor base stations, deployment scenario 4 is characterized according to Table 4. It should be noted that the descriptions in Table 4 may not apply to some devices (A, B).

[0090] Table 4

[0091] In the case of outdoor IoT devices and UE-based readers, deployment scenario 5 is characterized according to Table 5. It should be noted that the descriptions in Table 5 may not apply to some devices (A, B).

[0092] Table 5

[0093] The following describes the device classification. Environmental IoT devices are characterized based on their energy storage capacity and their ability to generate RF signals for transmission. A device is considered to have no energy storage at all; or limited energy storage. Based on these storage capacities, consider the following group of environmental IoT devices (device A, device B, and device C). Device A has no energy storage and no independent signal generation / amplification, i.e., backscatter transmission. Device B has energy storage and no independent signal generation, i.e., backscatter transmission. Use of stored energy may include amplification of reflected signals. Device C has energy storage and independent signal generation, i.e., active RF components for transmission. Limited energy storage may vary between implementations within device B and within device C, and also between devices B and C. Such storage is expected to be orders of magnitude smaller than that typically included in NB-IoT devices. Devices A, B, and C are capable of demodulating control, data, etc., from relevant entities in the RAN, depending on the connectivity topology.

[0094] like Figures 1B to 1F As shown, several connection topologies for environmental IoT networks and devices are defined. In all these topologies, environmental IoT devices can be provided with carriers from (multiple) other nodes inside or outside the topology. Links in each topology can be bidirectional or unidirectional. BS, UE, auxiliary nodes, or intermediate nodes can be multiple BSs or UEs, respectively. Such a mix of indoor and outdoor node placement is considered a network implementation choice. The potential impact on device or node complexity needs to be considered. This does not imply the presence of multi-hop auxiliary or intermediate nodes in the connection topologies.

[0095] Figure 1B An example scenario of Topology 1 associated with various aspects of this disclosure is illustrated. For example... Figure 1B As shown, in topology 1, the environmental IoT device 121 communicates directly and bidirectionally with the base station (BS) 122. Communication between the BS 122 and the environmental IoT device 121 includes environmental IoT data and / or signaling. This topology includes the possibilities for transmissions from the BS 122 to the environmental IoT device 121, as well as different possibilities for transmissions from the environmental IoT device 121 to the BS 122.

[0096] Figure 1C An example scenario of Topology 2 associated with various aspects of this disclosure is illustrated. For example... Figure 1CAs shown, in topology 2, the environmental IoT device 131 communicates bidirectionally with an intermediate node 132 (or intermediate device) located between the environmental IoT device 131 and the base station 133. In this topology, the intermediate node 132 can be a relay node, IAB node, UE, repeater, etc., capable of environmental IoT. The intermediate node 132 transmits environmental IoT data and / or signaling between the BS 133 and the environmental IoT device 131. An example of the intermediate node 132 can be the first device 201 described below. An example of the environmental IoT device 121 can be the third device 203 described below. An example of the BS 122 can be the second device 202 described below.

[0097] Figure 1D An example of topology 3 associated with various aspects of this disclosure is illustrated. For example... Figure 1D As shown, in topology 3 with downlink assistance, environmental IoT device 141 receives data and / or signaling from auxiliary node 142 and sends data and / or signaling to BS 143. Figure 1E Another example of topology 3 associated with various aspects of this disclosure is illustrated. For example... Figure 1E As shown, in topology 3 with uplink assistance, environmental IoT device 141 receives data and / or signaling from BS 143 and sends data / signaling to auxiliary node 142. Auxiliary node 142 can be a relay node, IAB node, UE, repeater, etc., capable of environmental IoT.

[0098] Figure 1F An example of topology 4 associated with various aspects of this disclosure is illustrated. For example... Figure 1F As shown, in topology 4, the environmental IoT device 151 and the UE 152 communicate bidirectionally. The communication between the UE 152 and the environmental IoT device 151 includes environmental IoT data and / or signaling.

[0099] In Topology 2 above, there is an intermediate node (e.g., intermediate node 132) between the BS (e.g., base station 133) and the AIoT device (e.g., shown as environmental IoT device 131). The intermediate node (e.g., a UE) acts as a reader, referred to herein as an intermediate UE, I-UE, or UE reader. The I-UE has two modules: one is an NR module that communicates with one of the BS, gNB, or eNB via an NR Uu interface; and the other is an AIoT module that communicates with one or more AIoT devices via an AIoT Uu interface. The NR Radio Resource Control (RRC) layer of the NR module in the I-UE needs to maintain an RRC connection mode so that it can send AIoT-related information to the network in a timely manner, which will affect AIoT-side processes. For example, the AIoT device identifier (ID) needs to be sent to the network when the I-UE receives it, so that the network will determine the next command, such as whether to operate the AIoT device (write, read, terminate (e.g., shut down), etc.) or determine to inventory the next AIoT device. In some cases, the NR module may not maintain RRC connection mode, such as when a radio link failure, handover, RRC re-establishment, or entry into RRC_IDLE mode occurs. In these cases, the RRC connection is unavailable, and AIoT-related information cannot be transmitted to the network in a timely manner. Therefore, it is necessary to define how to handle the AIoT process, and to address issues such as how the NR module indicates to the AIoT module that the RRC connection is unavailable, what the I-UE behavior is if the RRC connection is unavailable, and what the I-UE behavior is before the RRC connection is restored. Based on the above discussion and analysis, some embodiments of this disclosure propose solutions. Details will be described below with reference to some embodiments.

[0100] Figure 2 The illustration shows an example signaling diagram illustrating an example process of environmental Internet of Things (AIoT) process processing according to various aspects of this disclosure. Figure 2The illustrated process 200 involves a first device 201, a second device 202, and at least one third device 203. The third device 203 is shown as an example. In some embodiments, an example of the first device 201 may be an intermediate node (e.g., an intermediate UE, or simply I-UE) between a BS and an AIoT device. The second device 202 may be an access network device, core network device, or server for the AIoT device. As an example, the second device 202 may be a BS, such as BS 133. The third device 203 may be an AIoT device, such as AIoT device 131. In some examples, the AIoT device may communicate with an intermediate node connected to the network via the BS. The I-UE may have two modules; for example, one module is an NR module that communicates with the BS / gNB / eNB via an NR Uu interface. The other module is an AIoT module that communicates with one or more AIoT devices via an AIoT Uu interface.

[0101] In process 200, first device 201 may determine (210) that the link between first device 201 and second device 202 is unavailable for data transmission. In some examples, the link between first device 201 and second device 202 may be referred to as an NRUu link. In some examples, first device 201 may determine the link is unavailable via its processor. In some examples, first device 201 may determine the link is unavailable based on a first module in first device 201 used for communicating with second device 202. In some other examples, first device 201 may determine the link is unavailable based on a first module determining that data from one of at least three third devices 203 failed to be sent to second device 202. In some further examples, first device 201 may determine the link is unavailable based on a model predicted by the first module that the link will be unavailable. In some other examples, one or more of the above methods may be combined. First device 201 may suspend (212) the operation process for at least one third device 203 based on this determination. In some examples, the first device 201 may, for example, send a first indication indicating that the link is unavailable from the first module to the second module via its processor. The first module (e.g., an NR module) is used to communicate with the second device 202. The second module (e.g., an AIoT module) is used to communicate with at least one third device 203.

[0102] For example, if the NR RRC layer in the NR module determines that the NR Uu link is unavailable for data transmission, the NR RRC layer can indicate to the AIoT module that the NR Uu link is unavailable or that a problem has occurred or will occur with the NR Uu link. Alternatively, when the AIoT module delivers AIoT-related data to the NR module, if the NR module determines that the data cannot be sent due to the NR Uu link being unavailable for data transmission, the NR RRC layer can indicate to the AIoT module that the NR Uu link is unavailable. Alternatively, if an AI module predicts that the link may be unavailable in the near future, the NR RRC layer can indicate to the AIoT module that the NR Uu link is unavailable.

[0103] Additionally or alternatively, the first device 201 may, for example, send a reason for link unavailability from the first module to the second module via its processor within the first device 201. In some embodiments, the reason includes a radio link failure (RLF) in the link between the first device 201 and the second device 202, or a handover of the first device 201, or a link re-establishment, or the first device 201 being in an idle or inactive state without small data transmission configuration, or a random access failure of the first device 201.

[0104] For example, an NR Uu link may be unavailable for data transmission due to factors such as radio link failure, handover, RRC re-establishment, or the absence of UL transmission resources during an RRC idle / inactive state. Therefore, a cause can be indicated to explain why the RRC connection is unavailable, such as RLF, handover, re-establishment, idle state, or random access failure. Specifically, the cause can be indicated from the NR RRC layer in the NR module to the AIoT module, explaining why the NR Uu link is unavailable, such as RLF, handover, re-establishment, idle state, or random access failure.

[0105] As an example, the network (i.e., the second device 202) sends a message to the I-UE, such as an AIoT inventory or AIoT paging, which triggers the I-UE to begin an AIoT process, such as paging, random access, etc. During the random access process, there are one or more access rounds. In one round, multiple AIoT devices will respond via TDM. Additional rounds are used to receive responses from AIoT devices that did not respond in the previous round, for example, due to collisions or other reasons. In one access round, there are multiple access opportunities, and in one access opportunity, the I-UE will utilize one AIoT device to perform the AIoT process. The AIoT process can be an example of an operational procedure.

[0106] In some examples, the first device 201 may, for example, suspend the operation process via its processor after receiving the first indication from the second module or after the first module determines that the link is unavailable for data transmission. Additionally, the first device 201 may suspend the operation process at a certain point in time. In some examples, this point in time may be when the second module receives the first indication. For example, the I-UE may immediately suspend the AIoT process. Specifically, as an example, if the indication (i.e., the first indication) is received after the AIoT module receives a random access message (MSG) 1 from the AIoT device, the I-UE will not send message 2 to the AIoT device. Alternatively, if the indication is received after the AIoT module sends random access message 2 to the AIoT device, the I-UE will receive random access message 3 from the AIoT device but will not send message 4 to the AIoT device.

[0107] In some other examples, this point in time could be the end of an access timing, during which the first device 201 completes its operation with one of at least one third device 203. For example, the I-UE can pause the AIoT process at the end of the current access timing. In other words, the I-UE continues the AIoT process until the current access timing ends. For example, if the indication is received after the AIoT module receives random access message 1 from the AIoT device, the I-UE will continue sending message 2 and receiving message 3 from the AIoT device. The I-UE will send a message to the AIoT device (e.g., an ACK for the received message 3) to indicate the end of the access process. Or, in another example, if the indication is received after the AIoT module sends DL data to the AIoT device, the I-UE will continue receiving all subsequent UL data from that AIoT device. And the I-UE will not send a message to start the next access timing; that is, it will not process the next AIoT device.

[0108] In some examples, this point in time may be at the end of an access round that includes multiple access opportunities. These multiple access opportunities may include the access opportunities described above. For example, the I-UE may pause the AIoT process at the end of the current access round. In other words, the I-UE may continue the AIoT process until the current access round ends. For example, if the indication is received during an access opportunity, the I-UE will determine the end of the current access opportunity after receiving the AIoT device ID (access message 3) from the AIoT device and send a message to the AIoT device indicating access completion. The I-UE will then continue the AIoT process, for example, by sending a message to start the next access opportunity to process the next AIoT device. In some examples, this point in time may be determined based on configuration information used to indicate this point in time, or resource configuration information used for the operation process, or the caching capability of the second module, or any combination thereof. Further details can be found in the examples below, such as the descriptions of options 1 through 3 below.

[0109] In some examples, the first device 201 may perform the operation based on: receiving a reported device identifier (ID) from at least one of the third devices 203, or receiving data from at least one of the third devices 203, or sending an acknowledgment (ACK) to at least one of the third devices 203, or sending a second indication to at least one of the third devices 203 indicating the end of the operation process at the access point, or any combination thereof. On the third device 203 side, the third device 203 may receive the second indication.

[0110] In some examples, after the second module receives the first indication and before suspending the operation process, the first device 201 may, for example via its processor, continue the operation process during the access time in which the first device 201 performs an operation process with one of at least one third device 203 and a link unavailability occurs. Additionally, the first device 201 may, for example via its processor, send (e.g., via its transceiver) a second indication to the at least one third device 203 indicating the end of the operation process during the access time. In some examples, the second indication may be an acknowledgment (ACK) of data received from one of the at least one third device 203.

[0111] In some examples, after the second module receives the first instruction and before pausing the operation process, the first device 201 may, for example, continue the operation process in an access round comprising multiple access opportunities via its processor. The multiple access opportunities include the aforementioned access opportunities. In some examples, the first device 201 may continue the operation process in an access round by determining the end of the access opportunity based on receiving data from one of at least one of the third devices 203 during the access opportunity. In some other examples, the first device 201 may continue the operation process in an access round by initiating a subsequent access opportunity in which the first device 201 performs the operation process with another of the at least one third device 203.

[0112] The first device 201 may suspend the operation process in various ways. For example, the first device 201 may avoid sending, for example via its transceiver, subsequent messages associated with the operation process of at least one of the at least three third devices 203 to at least one third device 203. Alternatively, the first device 201 may avoid sending, for example via its transceiver, a message for initiating a subsequent access opportunity in which the first device 201 performs an operation process with another of the at least three third devices 203. Alternatively, the first device 201 may avoid sending, for example via its transceiver, a message for initiating a subsequent access round after an access round in which link unavailability occurs.

[0113] In some examples, the first device 201 may send (212a) a third instruction 205a indicating that the operation process is suspended to at least one third device 203 via its transceiver. On the third device 203 side, the third device 203 may receive (212b) the third instruction 205a from the first device 201, for example, via its transceiver. The third device 203 may then stop (216a) at least one operation associated with the operation process based on the third instruction 205a. In some examples, after suspending the operation process and before sending data 205, the first device 201 may store data 205 received from one or more of the at least one third device 203. On the third device 203 side, after receiving the third instruction 205a, the third device 203 may be in a waiting state. For example, the processor of the third device 203 may set the third device 203 to a waiting state.

[0114] As an example of some aspects related to the suspension of the operation process (e.g., the AIoT process) of the first device 201 above, when the AIoT module receives an indication (e.g., the first indication) of an NR Uu link problem (i.e., the NR Uu link is not available for data transmission), the I-UE may suspend the AIoT process in various ways, such as options 1 to 3 below.

[0115] In Option 1, the I-UE can immediately pause the AIoT process, for example, by not sending the next message to (multiple) AIoT devices. In some examples, the I-UE can send a message (example of the third indication) to the AIoT device to indicate that the AIoT process is paused (or pending), and the AIoT device stops the AIoT process and returns to a waiting state. Alternatively, in Option 2, the I-UE can continue the AIoT process until the current access timing ends, for example, upon receiving an AIoT device ID or receiving UL data from an AIoT device, and will not send a message to start the next access timing, i.e., will not process the next AIoT device. The I-UE will send a message to the AIoT device (example of the second indication) to indicate the end of the access process, for example, an ACK for the received AIoT device ID. Alternatively, in Option 3, the I-UE can continue the AIoT process until the access round ends, for example, by not sending a message to start the next access round. When an AIoT device ID is received and a problem occurs on the NR Uu link, the I-UE will determine that the current access timing has ended and send an indication to the AIoT device. I-UE will continue to process the next AIoT device (or in other words, begin the next access timing).

[0116] In some examples, the AIoT module determines which option to use based on the network configuration. For example, the AIoT module receives AIoT configuration from the BS indicating the current time of uncertainty, and then if a pause is determined, the AIoT module uses option 2 above to implement the pause. In some examples, the AIoT module determines which option to use based on resource configuration performed by the BS. For example, if the AIoT module receives resource configuration from the BS for AIoT communication in an access round, then if a pause is determined, the AIoT module can use option 3 above to implement the pause. In some examples, the AIoT module determines which option to use based on the caching capability of the I-UE's AIoT module. For the above examples, the I-UE can store all received AIoT-related information during the AIoT pause process (example in data 205). The received AIoT-related information includes, for example, AIoT device IDs received from one or more AIoT devices.

[0117] In some examples, the first device 201 may start a timer based on determining that the operation process should be paused, or based on pausing the operation process, or based on a second module in the first device 201 used for communicating with at least one third device 203 receiving a first indication that the link is unavailable, or based on the first module in the first device 201 used for communicating with the second device determining that the link is unavailable for data transmission. For example, if the I-UE determines that the AIoT process should be paused, or the AIoT module receives an indication of an NR Uu link problem (i.e., the first indication), the I-UE will start a timer in the AIoT module. In some examples, the first device 201 may start a timer in the first device 201 at the Radio Resource Control (RRC) layer of the second module used for communicating with at least one third device 203, or at the Media Access Control (MAC) layer of the second module. For example, if the I-UE determines that the AIoT process should be paused, the I-UE will start a timer in the AIoT module (e.g., the AIoT RRC layer or the AIoT Media Access Control (MAC) layer).

[0118] In some examples, the second device 202 may, for example, send (214a) one or more values ​​205b of a timer at the first device 201 to the first device 201 via its transceiver. On the first device 201 side, the first device 201 may, for example, receive (214b) one or more values ​​205b of the timer from the second device 202 via its transceiver. The one or more values ​​205b of the timer may be associated with the length of time during which an operation performed by the first device 201 is paused. In some examples, the one or more values ​​205b of the timer may be specific to the reason for the link unavailability. For example, the timer values ​​may differ for different reasons for NR Uu link unavailability configured by the network.

[0119] In some examples, the first device 201 may stop the timer based on the following: a second module in the first device 201, used for communicating with at least one third device 203, receiving a fourth indication that the link is available for data transmission; or a first module in the first device 201, used for communicating with the second device 202, determining that the link is available for data transmission; or data 205 being successfully transmitted to the second device 202 during the pause operation process; or uplink transmission between the first device 201 and the second device 202 being available; or any combination thereof. For example, if the AIoT module receives an indication that the NR Uu link is available for data transmission (referred to as the fourth indication), or the data stored by the AIoT module is successfully transmitted during the pending period, or NR Uu UL transmission is available (e.g., configured with pre-configured uplink resources (PUR), small data transmission under idle / inactive mode (SDT), etc.), the I-UE will stop the timer. In some examples, if the timer is stopped, the first device 201 may, for example, send the data 205 stored during the pause operation process to the second device 202 via its transceiver. For example, if the timer is stopped, the I-UE sends all AIoT-related information stored during the pause period to the network.

[0120] In some examples, if the timer expires, the first device 201 may terminate the operation process. During termination, the operation process may include, for example, sending a fifth indication indicating the termination of the operation process to at least one third device 203 via the transceiver of the first device 201, and releasing the data 205 stored in the first device 201. On the third device 203 side, the third device 203 may receive the fifth indication from the first device 201, for example, via the transceiver of the third device 203. For example, if the timer expires, the I-UE terminates the AIoT-side process, for example, by sending a termination / end indication (i.e., the fifth indication) to all AIoT devices. The I-UE releases all outstanding AIoT-related data (data 205 received from AIoT devices during the pause).

[0121] In some embodiments, a timer is maintained for AIoT processes suspended by the AIoT module. For example, a timer is started when an indication is received that the NR Uu link is unavailable for data transmission. The timer stops when the NR Uu link is restored. When the timer expires, the AIoT process terminates and is determined to have failed.

[0122] Based on the determination (214) that the link has become available, the first device 201 may, for example, send (216) data 205, which was stored during the pause operation and associated with one or more of the at least one third device 203, to the second device 202 via the transceiver of the first device 201. On the second device 202 side, the second device 202 may receive (218) the data 205.

[0123] In some embodiments of this disclosure, a solution for processing is proposed, particularly a solution for AIoT intermediate nodes to process AIoT processes when the NR Uu link is unavailable for data transmission, thereby improving communication performance in applications such as AIoT communication.

[0124] Figure 3 An example of device 300 supporting environment Internet of Things (AIoT) process processing according to various aspects of this disclosure is illustrated. Device 300 may be an example of UE 104 as described herein. Device 300 may support wireless communication with one or more node entities 102, UE 104, or any combination thereof. Device 300 may include components for bidirectional communication, including components for transmitting and receiving communications (such as processor 302, memory 304, transceiver 306, and optional I / O controller 308). These components may communicate electronically or be otherwise coupled (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more interfaces (e.g., bus).

[0125] Processor 302, memory 304, transceiver 306, 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 302, memory 304, transceiver 306, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0126] In some implementations, processor 302, memory 304, transceiver 306, 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 302 and memory 304 coupled to processor 302 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in memory 304 by processor 302).

[0127] For example, according to the examples disclosed herein, processor 302 may support wireless communication at device 300. In some examples, processor 302 may be configured to support: components for determining that a link between a first device and a second device is unavailable for data transmission; components for suspending an operation process for at least one third device based on the determination; and components for, based on the determination, making the link available for transmitting data associated with one or more of the at least one third device stored during the suspended operation process to the second device via a transceiver. Processor 302 may be configured to support other components for other implementations of method 500. In some other examples, processor 302 may be configured to support: components for receiving from the first device via a transceiver a third indication that an operation process for a third device performed by the first device is suspended; and components for stopping at least one operation associated with the operation process based on the third indication. Processor 302 may be configured to support other components for other implementations of method 600. In some other examples, processor 302 may be configured to support components for transmitting one or more values ​​of a timer at the first device via a transceiver to the first device, wherein the one or more values ​​are associated with the length of time during which an operation performed by the first device is paused. Processor 302 may be configured to support additional components for other implementations of method 700.

[0128] Processor 302 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 302 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 302. Processor 302 may be configured to execute computer-readable instructions stored in memory (e.g., memory 304) to cause device 300 to perform various functions of this disclosure.

[0129] Memory 304 may include random access memory (RAM) and read-only memory (ROM). Memory 304 may store computer-readable, computer-executable code, including instructions that, when executed by processor 302, cause device 300 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. In some implementations, the code may not be directly executed by processor 302, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 304 may include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0130] I / O controller 308 can manage the input and output signals of device 300. I / O controller 308 can also manage peripheral devices not integrated into device 300. In some implementations, I / O controller 308 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 308 can utilize an operating system such as iOS®, Android®, MS Windows®, OS / 2®, UNIX®, Linux®, or other known operating systems. In some implementations, I / O controller 308 can be implemented as part of a processor, such as processor 302. In some implementations, a user can interact with device 300 via I / O controller 308 or via hardware components controlled by I / O controller 308.

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

[0132] 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 310 for transmitting the amplified signal into the air or wireless medium.

[0133] 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 310 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.

[0134] Figure 4 An example of a processor 400 supporting an Internet of Things (AIoT) process according to various aspects of this disclosure is illustrated. Processor 400 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 400 may include a controller 402 configured to perform various operations according to the examples described herein. Processor 400 may optionally include at least one memory 404. Additionally or alternatively, processor 400 may optionally include one or more arithmetic logic units (ALUs) 406. 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).

[0135] Processor 400 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., memory local to the processor chipset or included in the processor chipset (e.g., processor 400)) 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.).

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

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

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

[0139] Memory 404 may store computer-readable, computer-executable code, including instructions that, when executed by processor 400, cause processor 400 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 402 and / or processor 400 may be configured to execute computer-readable instructions stored in memory 404 to cause processor 400 to perform various functions (e.g., functions or tasks supporting transmit power priority). For example, processor 400 and / or controller 402 may be coupled to or coupled to memory 404, and processor 400, controller 402, and memory 404 may be configured to perform the various functions described herein. In some examples, processor 400 may include multiple processors, and memory 404 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.

[0140] One or more ALUs 406 can be configured to support a variety of operations as described in the examples herein. In some implementations, one or more ALUs 406 may reside within or on a processor chipset (e.g., processor 400). In some other implementations, one or more ALUs 406 may reside outside the processor chipset (e.g., processor 400). One or more ALUs 406 can perform one or more calculations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALUs 406 can receive input operands and an opcode that determines the operation to be performed. One or more ALUs 406 are configured with a variety of logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Additionally or alternatively, one or more ALUs 406 may support logical operations such as AND, OR, XOR, NOR, and NAND, enabling one or more ALUs 406 to handle conditional operations, comparisons, and bitwise operations.

[0141] According to the examples disclosed herein, processor 400 may support wireless communication. In some examples, processor 402 may be configured or operable to support: components for determining that a link between a first device and a second device is unavailable for data transmission; components for suspending an operation process for at least one third device based on the determination; and components for, based on the determination, making the link available for transmission via a transceiver to the second device of data associated with one or more of the at least one third device stored during the suspended operation process. Processor 400 may be configured or operable to support other components for other implementations of method 500. In some other examples, processor 402 may be configured or operable to support: components for receiving via a transceiver from the first device a third indication that an operation process for a third device performed by the first device is suspended; and components for stopping at least one operation associated with the operation process based on the third indication. Processor 400 may be configured or operable to support other components for other implementations of method 600. In some examples, processor 402 may be configured or operable to support components for transmitting one or more values ​​of a timer at the first device via a transceiver to the first device, wherein the one or more values ​​are associated with the length of time during which an operation performed by the first device is paused. Processor 400 may be configured or operable to support other components for other implementations of method 700.

[0142] Figure 5 A flowchart illustrating a method 500 for processing an Internet of Things (AIoT) process according to various aspects of this disclosure is provided. The operation of method 500 can be implemented by a device or component thereof as described herein. For example, the operation of method 500 can be performed by a first device 201 or I-UE as described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device can use dedicated hardware to perform aspects of the described functions.

[0143] At step 505, the method includes determining that the link between the first device and the second device is unavailable for data transmission. The operation at step 505 can be performed according to the examples described herein. In some implementations, aspects of the operation at step 505 can be derived from references... Figure 1A or Figure 2 The device described is used to perform the execution.

[0144] At point 510, the method includes, based on this determination, suspending the operation process for at least one third device. The operation at 510 can be performed according to examples as described herein. In some implementations, aspects of the operation at 510 can be derived from, as referenced... Figure 1A or Figure 2 The device described is used to perform the execution.

[0145] At 515, the method includes determining that the link becomes available to send data associated with one or more of at least one third device that was stored during the pause operation process to the second device. The operation of 515 can be performed according to the examples described herein. In some implementations, aspects of the operation of 515 can be derived from references... Figure 1A or Figure 2 The device described is used to perform the execution.

[0146] Figure 6 A flowchart illustrating a method 600 for processing Internet of Things (AIoT) processes according to various aspects of this disclosure is provided. Operation of method 600 may be implemented by a device or its components as described herein. For example, operation of method 600 may be performed by a third device 203 or an AIoT device as described herein. In some implementations, the device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or additionally, the device may use dedicated hardware to perform aspects of the described functions.

[0147] At 605, the method includes receiving a third instruction from the first device, the third instruction indicating that an operation performed by the first device on the third device is suspended. The operation at 605 can be performed according to the examples described herein. In some implementations, aspects of the operation at 605 can be derived from, as referenced... Figure 1A or Figure 2 The device described is used to perform the execution.

[0148] At 610, the method may include stopping at least one operation associated with the operation process based on a third instruction. The operation at 610 can be performed according to examples as described herein. In some implementations, aspects of the operation at 610 may be determined by reference to [reference needed]. Figure 1A or Figure 2 The device described is used to perform the execution.

[0149] Figure 7 A flowchart illustrating a method for processing Internet of Things (AIoT) processes according to various aspects of this disclosure is provided. The operation of method 700 can be implemented by a device or component thereof as described herein. For example, the operation of method 700 can be performed by a second device 202 or a network device (e.g., a base station) as described herein. In some implementations, the device can execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively or separately, the device can use dedicated hardware to perform aspects of the described functions.

[0150] At 705, the method includes sending one or more values ​​of a timer at the first device, wherein the one or more values ​​are associated with a time length during which the operation performed by the first device is paused. The operation at 705 can be performed according to the examples described herein. In some implementations, aspects of the operation at 705 can be derived from references... Figure 1A or Figure 2 The device described is used to perform the execution.

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

[0152] 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).

[0153] 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, hardwiring, 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 in different physical locations.

[0154] 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. For 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 can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0155] As used herein, including in the claims, the article “a” preceding an element is unrestricted and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, 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.

[0156] 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 apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first device, comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: It was determined that the link between the first device and the second device was unusable for data transmission. Based on the determination, the operation process targeting at least one third device is suspended; as well as Based on the determination that the link has become available, the transceiver sends data associated with one or more of the at least one third device that was stored during the suspension of the operation process to the second device.

2. The first device of claim 1, wherein the processor is configured to determine that the link is unavailable based on at least one of the following: A first module in the first device, used for communicating with the second device, determines that the link is unavailable; The first module determines that data from one of the at least one third device failed to be sent to the second device; or The first module uses a model to predict that the link will be unavailable.

3. The first device according to claim 1, wherein the processor is further configured to: In the first device, a first indication is sent from a first module to a second module, the first indication indicating that the link is unavailable, wherein the first module is used to communicate with the second device, and the second module is used to communicate with the at least one third device.

4. The first device according to any one of claims 1 to 3, wherein the processor is further configured to: The first device sends the reason for the link unavailable from the first module to the second module, wherein the first module is used to communicate with the second device, and the second module is used to communicate with the at least one third device.

5. The first device according to claim 4, wherein the cause includes one of the following: The radio link failure (RLF) occurs in the link between the first device and the second device. Switching of the first device; The link was re-established; The first device is in an idle or inactive state without small data transmission configuration; or Random access to the first device failed.

6. The first device of claim 3, wherein the processor is configured to suspend the operation process after the second module receives the first instruction or after the first module determines that the link is unavailable for the data transmission.

7. The first device of claim 6, wherein the processor is configured to pause the operation process at the following time points: When the second module receives the first instruction; At the end of the access opportunity, during which the first device completed the operation process with one of the at least one third device; or At the end of the access round, the access round includes multiple access opportunities, wherein the multiple access opportunities include the access opportunity.

8. The first device of claim 3, wherein the processor is further configured to continue one of the following after the second module receives the first instruction and before suspending the operation process: The operation process during the access timing occurs when the first device and one of the at least one third device perform the operation process and the link becomes unavailable; or The operation process in the access round includes multiple access opportunities, wherein the multiple access opportunities include the access opportunity.

9. The first device of claim 8, wherein the operation process continues during the access timing, and wherein the processor is further configured to: A second instruction is sent to the at least one third device via the transceiver, the second instruction indicating the end of the operation process during the access timing.

10. The first device of claim 1, wherein the processor is configured to suspend the operation process by one of the following: To avoid sending subsequent messages related to the operation process of one of the at least one third device to the at least one third device via the transceiver; Avoid sending a message for initiating a subsequent access timing to the at least one third device via the transceiver, in which the first device and another of the at least one third device perform the operation process; or Avoid sending a message via the transceiver to the at least one third device to initiate a subsequent access round after the access round, in which the link becomes unavailable.

11. The first device according to claim 1, wherein the processor is further configured to: A third instruction is sent via the transceiver to the at least one third device, indicating that the operation process is suspended.

12. The first device according to claim 1, wherein the processor is further configured to: After pausing the operation process and before sending the data, the data received from the one or more third devices among the at least one third device is stored.

13. The first device of claim 1, wherein the processor is further configured to start a timer based on one of the following: Determine whether to pause the operation process; Pause the operation process; The second module in the first device, used for communicating with the at least one third device, receives a first indication indicating that the link is unavailable; or A first module in the first device, used for communicating with the second device, determines that the link is unavailable for the data transmission.

14. The first device of claim 13, wherein the processor is further configured to: Receive one or more values ​​of the timer from the second device via the transceiver.

15. The first device of claim 13, wherein the processor is further configured to stop the timer based on at least one of the following: The second module in the first device, used for communicating with the at least one third device, receives a fourth indication indicating that the link can be used for the data transmission; A first module in the first device, used for communicating with the second device, determines that the link is available for the data transmission; The data was successfully sent to the second device during the pause of the operation process; or Uplink transmission between the first device and the second device is available; and wherein: The processor is also configured to: When the timer is stopped, the data stored during the pause of the operation process is sent to the second device via the transceiver.

16. The first device according to any one of claims 13, wherein the processor is further configured to: If the timer expires, the operation process is terminated.

17. A third device, comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: Receives a third instruction from the first device via the transceiver, the third instruction indicating that the operation performed by the first device on the third device is suspended; and Based on the third instruction, at least one operation associated with the operation process is stopped.

18. The third device of claim 17, wherein the processor is further configured to: Set the third device to a standby state.

19. A second device, comprising: processor; as well as A transceiver, which is coupled to the processor, The processor is configured as follows: One or more values ​​of a timer at the first device are sent to the first device via the transceiver, wherein the one or more values ​​are associated with a time length during which the operation performed by the first device is paused.

20. A processor for wireless communication, comprising: At least one memory; as well as A controller, coupled to the at least one memory, and configured such that the controller: It was determined that the link between the first device and the second device was unusable for data transmission. Based on the determination, the operation process targeting at least one third device is suspended; as well as Based on the determination that the link has become available, the data associated with one or more of the at least one third device that was stored during the suspension of the operation process is sent to the second device.

Images