Method and apparatus for providing information of environmental IoT device in wireless communication system

Abstract

The present invention provides a method and apparatus for providing information of an environmental Internet of Things device in a wireless communication system, wherein the method of a user equipment comprises: receiving a first signaling that triggers a random access procedure; triggering a random access procedure in response to receiving the first signaling; performing a first transmission during the random access procedure; and providing, in the first transmission, energy information indicating at least one of whether a remaining energy of the user equipment is sufficient for one or more subsequent transmissions or receptions following the first transmission, the remaining energy of the user equipment being insufficient for one or more subsequent transmissions or receptions following the first transmission, whether the residual energy of the user equipment is sufficient to complete the random access procedure or not is judged, and / or the residual energy of the user equipment is insufficient to complete the random access procedure.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 565,231, filed on March 14, 2024, which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to wireless communication networks, and more particularly, to a method and apparatus for providing information of Ambient Internet of Things (A-IOT) devices in a wireless communication system. Background Art

[0004] With the rapidly growing demand for transferring large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that use Internet Protocol (IP) packet communications. This IP packet communication can provide IP-based voice, multimedia, multicast, and on-demand communication services to users of mobile communication devices.

[0005] An exemplary network architecture is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput to enable the aforementioned IP-based voice and multimedia services. Currently, the 3GPP standards organization is discussing new next-generation (e.g., 5G) radio technologies. Consequently, changes to the current body of 3GPP standards are currently being submitted and considered to evolve and complete the 3GPP standards. Summary of the Invention

[0006] Methods, systems, and apparatus are provided for providing information about ambient Internet of Things (IoT) devices in a wireless communication system. Ambient IoT user equipment (UE) / devices can execute and / or complete transmissions with limited power. The present invention allows ambient IoT UE / devices to indicate to the network whether they are able to execute or complete a procedure (e.g., a random access procedure) based on their remaining energy, thereby assisting the network in scheduling multiple procedures (e.g., triggered by a single service) for a large number of ambient IoT devices.

[0007] In various embodiments, the method of the UE includes: receiving first signaling that triggers a random access procedure; triggering the random access procedure in response to receiving the first signaling; performing a first transmission during the random access procedure; and providing energy information in the first transmission indicating at least one of the following: whether the UE's remaining energy is sufficient for one or more subsequent transmissions or receptions after the first transmission, the UE's remaining energy is insufficient for one or more subsequent transmissions or receptions after the first transmission, whether the UE's remaining energy is sufficient to complete the random access procedure, and / or the UE's remaining energy is insufficient to complete the random access procedure. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 A diagram illustrating a wireless communication system according to an embodiment of the present invention;

[0009] Figure 2 is a block diagram of a transmitter system (also referred to as an access network) and a receiver system (also referred to as a user equipment or UE) according to an embodiment of the present invention;

[0010] Figure 3 is a functional block diagram of a communication system according to an embodiment of the present invention;

[0011] Figure 4 According to an embodiment of the present invention Figure 3 Functional block diagram of the program code;

[0012] Figure 5 It is in 3GPP TR 38.848 V18.0.0 Figure 4 .2.1.1-1: Reproduction of topology 1;

[0013] Figure 6 It is in 3GPP TR 38.848 V18.0.0 Figure 4 .2.1.2-1: Reproduction of topology 2;

[0014] Figure 7A It is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1: Random Access Procedure - (a) Reproduction of CBRA with 4-step RA type;

[0015] Figure 7B It is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1: Random Access Procedure - (b) Reproduction of CBRA with 2-step RA type;

[0016] Figure 7C It is in 3GPP TS 38.300 V17.6.0 Figure 9.2.6-1: Random Access Procedure - (c) Reproduction of CFRA with 4-step RA type;

[0017] Figure 7D It is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1: Random Access Procedure - (d) Reproduction of CFRA with 2-step RA type;

[0018] Figure 8 [5]3GPP TS 38.331 V18.0.0 Figure 5 .7.4.1-1: Reproduction of UE assistance information;

[0019] Figure 9 is an example diagram showing that a network triggers an ambient IoT device to execute a first procedure according to an embodiment of the present invention, and in response to receiving a first signaling from the network, the ambient IoT device executes one or more D2R transmissions and / or R2D receptions during the first procedure;

[0020] Figure 10 is an example diagram showing that a network triggers an ambient IoT device to execute a first procedure according to an embodiment of the present invention, and in response to receiving a first signaling from the network, the ambient IoT device executes one or more D2R transmissions and / or R2D receptions during the first procedure;

[0021] Figure 11 is a flowchart of a method of a UE according to an embodiment of the present invention, the method comprising: receiving first signaling from a network; in response to receiving the first signaling, initiating a first procedure; transmitting a first transmission to the network; receiving a response corresponding to the first transmission from the network; generating and / or transmitting first information based on at least a condition; and transmitting a second transmission including the first information to the network;

[0022] Figure 12 This is a flowchart of a method for a UE in a wireless communication system according to an embodiment of the present invention, the method comprising: receiving a first signaling that triggers a random access procedure; triggering the random access procedure in response to receiving the first signaling; performing a first transmission during the random access procedure; and providing energy information in the first transmission indicating at least one of the following: whether the remaining energy of the UE is sufficient for one or more subsequent transmissions or receptions after the first transmission, whether the remaining energy of the UE is insufficient for one or more subsequent transmissions or receptions after the first transmission, whether the remaining energy of the UE is sufficient to complete the random access procedure, and / or the remaining energy of the UE is insufficient to complete the random access procedure. DETAILED DESCRIPTION

[0023] The present invention described herein may be applied to or implemented in the exemplary wireless communication systems and devices described below. Furthermore, the present invention is primarily described in the context of the 3GPP architecture reference model. However, it should be understood that, given the disclosed information, one skilled in the art can readily adapt and utilize various aspects of the present invention in the 3GPP2 network architecture, as well as other network architectures.

[0024] The exemplary wireless communication systems and devices described below employ wireless communication systems that support broadcast services. Wireless communication systems are widely deployed to provide various types of communications, such as voice, data, etc. These systems can be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP Long Term Evolution (LTE) radio access, 3GPP Long Term Evolution Advanced (LTE-A) radio access, 3GPP2 Ultra Mobile Broadband (UMB), 3GPP New Radio (NR) or some other modulation techniques.

[0025] Specifically, the exemplary wireless communication system apparatus described below may be designed to support one or more standards, such as those provided by an association named "3rd Generation Partnership Project" (referred to herein as 3GPP), including: [1] RP-234058, "Study of Solutions for Ambient Internet of Things (IoT) in NR"; [2] 3GPP TR 38.848 V18.0.0 (2023-09) 3GPP; TSG RAN; Study of Ambient Internet of Things (IoT) in RAN (Release 18); [3] 3GPP TS 38.300 V18.0.0 (2023-12) 3GPP; TSG RAN; NR; NR and NG-RAN General Description (Release 18); [4] 3GPP TS 38.321 V18.0.0 (2023-12) 3GPP; TSG RAN; NR; MAC Protocol Specification (Release 18); [5] 3GPP TS 38.331 V18.0.0 (2023-12) 3GPP; TSG RAN; NR; RRC protocol specification (Release 18); [6] 3GPP TS 38.213 V18.1.0 (2023-12) 3GPP; TSG RAN; NR; Physical layer procedures for control (Release 18). The standards and documents listed above are hereby expressly and entirely incorporated by reference in their entirety.

[0026] Figure 1 1. A multiple access wireless communication system according to an embodiment of the present invention is shown. An access network 100 (AN) includes multiple antenna groups, one of which includes antennas 104 and 106, another includes antennas 108 and 110, and another includes antennas 112 and 114. Figure 1 In the figure, only two antennas are shown for each antenna group, but each antenna group may utilize more or fewer antennas. Access terminal (AT) 116 communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 via forward link 120 and receive information from AT 116 via reverse link 118. AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to AT 122 via forward link 126 and receive information from AT 122 via reverse link 124. In an FDD system, communication links 118, 120, 124, and 126 may use different frequencies for communication. For example, forward link 120 may use a different frequency than that used by reverse link 118.

[0027] Each antenna group and / or the area in which they are designed to communicate is often referred to as a sector of the access network. In an embodiment, the antenna groups are each designed to communicate with access terminals in a sector of the area covered by the access network 100.

[0028] In communicating via forward links 120 and 126, the transmit antennas of access network 100 may utilize beamforming to improve the signal-to-noise ratio of the forward links for the different access terminals 116 and 122. Furthermore, an access network's use of beamforming to transmit to access terminals randomly dispersed throughout the access network's coverage area generally results in less interference to access terminals in neighboring cells than if the access network transmitted to all of its access terminals via a single antenna.

[0029] An AN may be a fixed station or base station for communicating with a terminal and may also be referred to as an access point, Node B, base station, enhanced base station, eNodeB, or some other term. An AT may also be referred to as user equipment (UE), a wireless communication device, a terminal, an access terminal, or some other term.

[0030] Figure 2 is a simplified block diagram of an embodiment of a transmitter system 210 (also referred to as an access network) and a receiver system 250 (also referred to as an access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for several data streams is provided from a data source 212 to a transmit (TX) data processor 214.

[0031] In one embodiment, each data stream is transmitted through a respective transmit antenna. TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

[0032] The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream are then modulated (e.g., symbol mapped) based on a particular modulation scheme selected for that data stream (e.g., BPSK, QPSK, M-PSK, or M-QAM) to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions executed by processor 230. Memory 232 is coupled to processor 230.

[0033] The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then converts the N T The modulation symbol stream is provided to N T transmitters (TMTR) 222a through 222t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

[0034] Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (eg, amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission via the MIMO channel. T The antennas 224a to 224t transmit N signals from transmitters 222a to 222t. T a modulated signal.

[0035] At the receiver system 250, N R The transmitted modulated signals are received by each antenna 252a through 252r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding "received" symbol stream.

[0036] RX data processor 260 then extracts the N R The receiver 254 receives and processes N R receive symbol streams to provide N T The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by the RX processor 260 is complementary to that performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0037] Processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

[0038] The reverse link message may include various types of information related to the communication link and / or the received data stream. The reverse link message is then processed by the TX data processor 238 (which also receives traffic data for a number of data streams from the data source 236), modulated by the modulator 280, conditioned by the transmitters 254a through 254r, and transmitted back to the transmitter system 210.

[0039] At transmitter system 210, the modulated signal from receiver system 250 is received by antenna 224, conditioned by receiver 222, demodulated by demodulator 240, and processed by RX data processor 242 to extract the reverse link message transmitted by receiver system 250. Processor 230 then determines which precoding matrix to use to determine the beamforming weights and then processes the extracted message.

[0040] The memory 232 may be used to temporarily store some buffered / calculated data from 240 or 242 via the processor 230, store some buffered data from 212, or store some specific program codes. Furthermore, the memory 272 may be used to temporarily store some buffered / calculated data from 260 via the processor 270, store some buffered data from 236, or store some specific program codes.

[0041] Steering Figure 3 , this figure shows an alternative simplified functional block diagram of a communication device according to one embodiment of the present invention. Figure 3 As shown in FIG, the communication device 300 in the wireless communication system can be used to implement Figure 1 UE (or AT) 116 and 122 in, and the wireless communication system is preferably an NR system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by the user through the input device 302 (for example, a keyboard or a keypad), and can output images and sounds through the output device 304 (for example, a display or a speaker). The transceiver 314 is used to receive and transmit wireless signals to transfer the received signals to the control circuit 306 and wirelessly output the signals generated by the control circuit 306.

[0042] Figure 4 According to one embodiment of the present invention Figure 3. In this embodiment, program code 312 includes an application layer 400, a layer 3 portion 402, and a layer 2 portion 404, and is coupled to a layer 1 portion 406. Layer 3 portion 402 generally performs radio resource control. Layer 2 portion 404 generally performs link control. Layer 1 portion 406 generally performs physical connectivity.

[0043] For LTE, LTE-A, or NR systems, layer 2 portion 404 may include a radio link control (RLC) layer and a medium access control (MAC) layer. Layer 3 portion 402 may include a radio resource control (RRC) layer.

[0044] Any two or more of the following paragraphs, (sub)bullets, points, actions or claims described in each invention paragraph or clause may be logically, reasonably and appropriately combined to form a specific method.

[0045] Any sentence, paragraph, (sub) bullet, point, action or claim described in each invention paragraph or clause below can be independently and individually implemented to form a specific method or device. The dependency in the following invention disclosure (for example, "based on", "more specifically", "example", etc.) is only a possible embodiment that does not limit a specific method or device.

[0046] The research project on Ambient Internet of Things (IoT) was approved at the RAN plenary meeting #102. The description is specified in [1] RP-234058 as follows:

[0047] ***************************** Quote begins [1]*****************************

[0048] 3 reasons

[0049] In recent years, the Internet of Things (IoT) has garnered significant attention in the world of wireless communications. It's expected that more "things" will be interconnected to improve productivity and enhance comfort. Further reductions in the size, complexity, and power consumption of IoT devices could enable the deployment of tens or even hundreds of billions of IoT devices for a variety of applications, providing added value across the entire value chain. Powering all IoT devices with batteries that require manual replacement or recharging is impossible, leading to high maintenance costs, serious environmental concerns, and even safety risks for some use cases (e.g., wireless sensors in the power and oil industries).

[0050] Most existing wireless communication devices are powered by batteries that require manual replacement or recharging. The automation and digitization of various industries are opening up new markets that require new IoT technologies that support battery-free devices without energy storage capabilities or devices with energy storage that does not require manual replacement or recharging. The physical size of such devices must be quite small to be effective in the target use cases.

[0051] TR 22.840 is being developed by SA1 to capture the use cases, business scenarios, device constraints for ambient power enabled IoT and identify new potential service requirements and new KPIs. SA1 is considering devices that are battery-free or have limited energy storage capabilities (i.e., using capacitors) and are powered by harvesting radio waves, light, motion, heat, or any other power source that may be deemed suitable.

[0052] Given the limited size and complexity required for practical applications in battery-free devices with no energy storage capabilities or devices with limited energy storage that do not require manual replacement or recharging, energy harvesters typically have output powers ranging from 1 μW to several hundred μW. Existing cellular devices may not perform well with energy harvesting due to their peak power consumption exceeding 10 mW.

[0053] The example application in TR 22.840 is asset identification, which currently relies primarily on barcodes and RFID in most industries. The primary advantages of these two technologies are the tags' ultra-low complexity and small physical size. However, the limited read range of several meters often requires either handheld scanning, which is labor-intensive and time-consuming, or RFID portals / gates, which lead to high deployment costs. Furthermore, the lack of interference management schemes leads to significant interference and capacity issues between RFID readers, especially in dense deployments. This makes it difficult for RFID to support large-scale, seamless coverage networks.

[0054] TSG RAN has completed the Rel-18 RAN-level SI on Ambient IoT, which provides a terminology and scope framework for future discussions on Ambient IoT. This has defined representative use cases, deployment scenarios, connectivity topologies, Ambient IoT devices, design goals, and required functionality; it also conducted a preliminary feasibility assessment and made recommendations for downward selection when setting the scope for another WG-level study.

[0055] Because existing technologies cannot meet all the requirements of the target use cases, new IoT technologies are recommended to open up new markets within the 3GPP system, with the number of connections and / or device density being orders of magnitude higher than existing 3GPP IoT technologies. New IoT technologies should offer orders of magnitude lower complexity and power consumption than existing 3GPP LPWA technologies (e.g., NB-IoT and eMTC), and should address use cases and scenarios that cannot otherwise be met based on existing 3GPP LPWA IoT technologies.

[0056] 4 goals

[0057] 4.1 Objectives of SI or Core WI or Test WI

[0058] The goal of this study is to further evaluate Ambient IoT, a new 3GPP IoT technology, at the RAN WG level, which is suitable for deployment in 3GPP systems that rely on ultra-low complexity devices with ultra-low power consumption for very low-end IoT applications. The study should provide a clear distinction, i.e. address use cases and scenarios that cannot be otherwise met based on existing 3GPP LPWA IoT technologies (e.g. NB-IoT with reduced peak Tx power).

[0059] General range

[0060] The definitions provided in TR 38.848 are incorporated into this SI, and the following are the general scopes of exclusivity:

[0061] A. The overall goal should be to develop a harmonized air interface design with minimal differences (where necessary) to enable ambient IoT to enable the following devices:

[0062] i. ~1μW peak power consumption, with energy storage, initial sampling frequency offset (SFO) up to 10 X ppm, there is neither DL nor UL amplifier in the device. The UL transmission of the device is backscattered on an externally provided carrier.

[0063] ii. ≤ several hundred μW peak power consumption1, with energy storage and initial sampling frequency offset (SFO) up to 10 X ppm, DL and / or UL amplifiers in the device. The UL transmission of the device can be generated internally by the device or backscattered on an externally provided carrier.

[0064] ●X will be decided in WG.

[0065] ● Coverage design target: According to TR 38.848: “…the range within which the WG can be selected”, the maximum distance to indoor devices is 10-50m.

[0066] • For topologies 1 and 2 according to TR 38.848 (UE as an intermediate node under NW control), there is no RRC state, no mobility (ie at least no cell selection / reselection type functionality), no HARQ, no ARQ.

[0067] NOTE 1: It should be understood that “≤ several hundred μW” means that the WG is not responsible for setting a specific value, and the WG discussion will determine whether the presented design with the corresponding power consumption meets the “≤ several hundred μW” requirement.

[0068] B. Refer to the table in clause 4.2.2 of TR 38.848 for deployment scenarios with the following characteristics:

[0069] ● Deployment scenario 1 with topology 1

[0070] ○ Base station and coexistence characteristics: micro cells, shared sites

[0071] ● Deployment scenario 2 with topology 2 and UE as intermediate node under network control

[0072] ○ Base station and coexistence characteristics: macro cell, co-site

[0073] ○The intermediate node is located indoors

[0074] C. FR1 licensed spectrum in FDD.

[0075] D. Spectrum deployment within the NR band, LTE / NR protection band, and independent frequency bands.

[0076] E. Business types DO-DTT, DT, with emphasis on rUC1 (indoor inventory) and rUC4 (indoor commands).

[0077] ●From RAN#104, the study will evaluate whether the coordinated air interface design (as per bullet ‘A’ above) can address the DO-A (Device-Initiated Autonomous) use case, and only identify which part(s) of the coordinated air interface design (as per bullet ‘A’ above) are not sufficient for the DO-A use case.

[0078] Transmissions from ambient IoT devices (including backscatter when used) may occur at least in the UL spectrum.

[0079] In general terms, set the following goals:

[0080] 1. Evaluate your assumptions

[0081] a) Summarize at least the following aspects of the design objectives left to the WG in clause 5 (RAN design objectives) of TR 38.848 [RAN1].

[0082] ○ Clause 5.3: Applicable maximum distance target value

[0083] ○ Clause 5.6: Refine the definition of latency suitable for use in RAN WG

[0084] ○ Clause 5.8: 2D Distribution of Devices

[0085] b) Define necessary further evaluation assumptions for deployment scenarios used for coverage and coexistence evaluations [RAN1, RAN4]

[0086] c) Identify the basic blocks / components of possible ambient IoT device architectures, taking into account state-of-the-art implementations of low-power, low-complexity devices that meet RAN design targets for power consumption and complexity. [RAN1]

[0087] d) Define the link budget calculation for coverage, including whether / how to model carriers from nodes inside or outside the connection topology.

[0088] …

[0089] 2. Study the necessary and feasible solutions for the IoT environment specified in the general scope, including decisions on which functions, procedures, etc. are required and which are not, and ensuring at least the required functions of Section 6.2 of TR 38.848.

[0090] …

[0091] RAN1-led:

[0092] For ambient IoT DL and UL:

[0093] ○Frame structure, synchronization and timing, random access

[0094] ○ Basic parameters, bandwidth and multiple access

[0095] ○Waveform and modulation

[0096] ○Channel decoding

[0097] ○ Downlink channel / signal aspects

[0098] ○ Uplink channel / signal aspects

[0099] ○ Scheduling and timing

[0100] ○ Study the necessary characteristics of the carrier waveform of the carrier provided externally to the ambient IoT device, including interference handling at the ambient IoT UL receiver and at the NR base station.

[0101] For topology 2, the physical layer design is no different from that of topology 1.

[0102] RAN2-led:

[0103] ○ Research and determine what features are needed for the ambient IoT compact protocol stack and lightweight signaling procedures to implement DO-DTT and DT data transmission, and study these features.

[0104] For example:

[0105] ■Paging

[0106] ■Random access

[0107] ■ Data transmission including necessary radio resource control aspects is subject to general scope restrictions

[0108] ****************************END OF QUOTE********************************

[0109] The description of ambient IoT can be found in [2] 3GPP TR 38.848 V18.0.0:

[0110] ***************************** Quote begins [2]**************************

[0111] 4.2.1 Connection Topology

[0112] 4.2.1.0 Introduction

[0113] For the purpose of this study, the following connection topologies for ambient IoT networks and devices are defined. In all of these topologies, ambient IoT devices can be provided with carriers from other nodes inside or outside the topology. Links in each topology can be bidirectional or unidirectional.

[0114] A base station, user equipment (UE), auxiliary node, or intermediate node can be multiple base stations or user equipment, respectively. A mix of indoor and outdoor placement of such nodes 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 multiple hops of auxiliary or intermediate nodes in the connectivity topology.

[0115] 4.2.1.1 Topology

[0116] Figure 5 It is in 3GPP TR 38.848 V18.0.0 Figure 4 .2.1.1-1: Reproduction of topology 1.

[0117] In Topology 1, ambient IoT devices communicate directly and bidirectionally with a base station. Communications between the base station and the ambient IoT devices include ambient IoT data and / or signaling. This topology allows for the possibility that the base station transmitting to the ambient IoT device may be different from the base station receiving from the ambient IoT device.

[0118] 4.2.1.2 Topology 2:

[0119] Figure 6 It is in 3GPP TR 38.848V18.0.0 Figure 4 .2.1.2-1: Reproduction of topology 2.

[0120] In Topology 2, ambient IoT devices communicate bidirectionally with an intermediate node between the device and the base station. In this topology, the intermediate node can be an ambient IoT-capable relay, an IAB node, a UE, or a repeater. The intermediate node transfers ambient IoT data and / or signaling between the base station and the ambient IoT device.

[0121] ****************************Next Quote*****************************

[0122] 4.3 Device Classification

[0123] Ambient IoT devices in the study are characterized by their energy storage capacity and ability to generate RF signals for their transmissions.

[0124] The study considers the device to have any of the following:

[0125] - no energy storage at all; or

[0126] -Limited energy storage

[0127] Depending on these storage capacities, the study considers the following set of environmental IoT devices:

[0128] - Device A: no energy storage, no independent signal generation / amplification, i.e. backscatter transmission.

[0129] - Device B: with energy storage, no independent signal generation, i.e. backscatter transmission. The use of the stored energy may include amplification of the reflected signal.

[0130] - Device C: has energy storage, has independent signal generation, ie active RF components for transmission.

[0131] The limited energy storage may differ between implementations within device B or within device C, and may differ between device B and device C. This storage is expected to be orders of magnitude smaller than what NB-IoT devices typically contain.

[0132] ****************************END OF QUOTE********************************

[0133] The general description of the current random access procedure is given in [3] 3GPP TS 38.300 V18.0.0:

[0134] ***************************** Quote begins [3]**************************

[0135] 9.2.6 Random Access Procedure

[0136] …

[0137] Two types of random access procedures are supported: 4-step RA type with MSG1 and 2-step RA type with MSGA. Both types of RA procedures support contention-based random access (CBRA) and contention-free random access (CFRA), as shown below: Figure 9 .2.6-1 shown.

[0138] The UE selects the random access type based on the network configuration when initiating the random access procedure:

[0139] -When CFRA resources are not configured, the RSRP threshold is used by the UE to select between 2-step RA type and 4-step RA type;

[0140] -When CFRA resources of 4-step RA type are configured, the UE performs 4-step RA type random access;

[0141] - When CFRA resources of 2-step RA type are configured, the UE performs random access of 2-step RA type.

[0142] The network will not configure CFRA resources for both 4-step and 2-step RA types of the Bandwidth Part (BWP). CFRA of the 2-step RA type is only supported for handover.

[0143] The MSG1 of the 4-step RA type consists of a preamble on the PRACH. After the MSG1 transmission, the UE listens for a response from the network within the configured window. For CFRA, a dedicated preamble for MSG1 transmission is assigned by the network, and after receiving a random access response from the network, the UE ends the random access procedure, as shown in the following example. Figure 9 For CBRA, after receiving the random access response, the UE sends MSG3 using the UL grant scheduled in the response and monitors contention resolution, as shown in .2.6-1(c). Figure 9 As shown in .2.6-1(a). If contention resolution is unsuccessful after MSG3 (re)transmission, the UE returns to MSG1 transmission.

[0144] The 2-step RA type of MSGA contains a preamble on PRACH and a payload on PUSCH. After the MSGA transmission, the UE listens for a response from the network within the configured window. For CFRA, dedicated preamble and PUSCH resources are configured for MSGA transmission, and after receiving the network response, the UE ends the random access procedure, such as Figure 9 .2.6-1(d). For CBRA, if the contention resolution is successful after receiving the network response, the UE ends the random access procedure, as shown in Figure 9 .2.6-1(b); and if a fallback indication is received in MSGB, the UE uses the UL grant scheduled in the fallback indication to perform MSG3 transmission and monitors contention resolution, as shown in FIG. Figure 9 If contention resolution is unsuccessful after MSG3 (re)transmission, the UE returns to MSG 4 transmission.

[0145] …

[0146] Figure 7A It is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1: Random Access Procedure - (a) Reproduction of CBRA with 4-step RA type.

[0147] Figure 7B It is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1: Random Access Procedure - (b) Reproduction of CBRA with 2-step RA type.

[0148] Figure 7C It is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1: Random Access Procedure - (c) Reproduction of CFRA with 4-step RA type.

[0149] Figure 7DIt is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1: Random Access Procedure - (d) Reproduction of CFRA with 2-step RA type.

[0150] ****************************END OF QUOTE********************************

[0151] Power Headroom Reporting (PHR) is described in [4] 3GPP TS 38.321 V18.0.0:

[0152] ***************************** Quote begins [4]**************************

[0153] 5.4.6 Power Headroom Report

[0154] The Power Headroom Reporting procedure is used to provide the following information to the serving gNB:

[0155] - Type 1 power headroom: the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission for the activated serving cell;

[0156] - Type 2 power headroom: the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH and PUCCH transmissions on the SpCell for other MAC entities (i.e., E-UTRA MAC entity in case of EN-DC, NE-DC and NGEN-DC);

[0157] - Type 3 power headroom: the difference between the nominal UE maximum transmit power and the estimated power for SRS transmission for the activated serving cell;

[0158] …

[0159] A Power Headroom Report (PHR) is triggered if any of the following events occurs:

[0160] - when a MAC entity has UL resources for a new transmission, phr-ProhibitTimer expires or has expired, and the pathloss change for at least one RS used as a pathloss reference for one activated serving cell of any MAC entity since the last transmission of a PHR in this MAC entity is greater than phr-Tx-PowerFactorChange dB, and the active DL BWP of said MAC entity is not a sleep BWP;

[0161] NOTE 1: The path loss variation for a cell evaluated above is the path loss measured at the current time on the current path loss reference and the path loss measured at the time of transmission of the last PHR transmitted on the then-current path loss reference, regardless of whether the path loss reference has changed in between. For this purpose, the current path loss reference does not include any path loss reference configured using pathlossReferenceRS-Pos in TS 38.331 [5].

[0162] -phr-PeriodicTimerExpires;

[0163] …

[0164] - When the MAC entity has UL resources for a new transmission, the phr-ProhibitTimer expires or has expired, and for any of the activated serving cells of any MAC entity with configured uplink, the following conditions hold:

[0165] - There are UL resources allocated for transmission or there is a PUCCH transmission on this cell, and when the MAC entity has UL resources allocated for transmission or a PUCCH transmission on this cell, the power management (such as P-MPR) of this cell since the last transmission of the PHR c The change in required power back-off caused by the Tx-PowerFactorChange parameter (as allowed, as specified in TS 38.101-1, TS 38.101-2 and TS 38.101-3) is greater than phr-Tx-PowerFactorChange dB.

[0166] …

[0167] If the MAC entity has allocated UL resources for a new transmission, then the MAC entity shall:

[0168] 1> If it is the first UL resource allocated for a new transmission since the last MAC reset:

[0169] 2>Start phr-PeriodicTimer.

[0170] 1> If the Power Headroom Reporting procedure determines that at least one PHR has been triggered and not cancelled; and

[0171] 1> If, due to the LCP as defined in clause 5.4.3.1, the allocated UL resources can accommodate the MAC CE of the PHR that the MAC entity is configured to transmit plus its subheader:

[0172] 2> If the configuration has the value true for multiplePHR:

[0173] 3> for each activated serving cell with configured uplink associated with any MAC entity whose active DL BWP is not a dormant BWP; and

[0174] 3> For each activated serving cell associated with an E-UTRA MAC entity with configured uplink:

[0175] …

[0176] 6> obtain the value of the Type 1 or Type 3 power headroom for the corresponding uplink carrier as specified in clause 7.7 of TS 38.213 [6] for NR serving cells and in clause 5.1.1.2 of TS 36.213 for E-UTRA serving cells.

[0177] …

[0178] 5> if this MAC entity has UL resources allocated for transmission on this serving cell; or

[0179] 5> If another MAC entity (if configured) has UL resources allocated for transmission on this serving cell, and phr-ModeOtherCG is set to true by upper layers, then:

[0180] 6> Get the corresponding P from the physical layer CMAX,f,c The value of the field.

[0181] …

[0182] 3> If this MAC entity is configured with mpe-Reporting-FR2-r17 or enhanced multi-entry PHR for multiple TRP MAC CE as defined in clause 6.1.3.51, if this MAC entity is configured with twoPHRMode or multi-entry PHR with assumed PUSCH MAC CE as defined in clause 6.1.3.78, if this MAC entity is configured with phr-AssumedPUSCH-eporting or multi-entry PHR MAC CE as defined in clause 6.1.3.9, then the enhanced multi-entry PHR as defined in clause 6.1.3.49 is generated and transmitted in other ways based on the value reported by the physical layer.

[0183] 2> Otherwise (i.e., using single-entry PHR format):

[0184] 3> If this MAC entity is configured with twoPHRMode:

[0185] 4> Obtain two values ​​of the type 1 power headroom of the corresponding uplink carrier of PCell from the physical layer.

[0186] 3> Otherwise:

[0187] 4> Obtain the value of the type 1 power headroom of the uplink carrier corresponding to the PCell from the physical layer.

[0188] …

[0189] 3> Get the corresponding P from the physical layer CMAX,f,c The value of the field;

[0190] …

[0191] 3> If this MAC entity is configured with mpe-Reporting-FR2-r17 or enhanced single-entry PHR for multiple TRP MAC CE as defined in clause 6.1.3.50, if this MAC entity is configured with twoPHRMode or single-entry PHR with assumed PUSCH MAC CE as defined in clause 6.1.3.78, if this MAC entity is configured with phr-AssumedPUSCH-eporting or single-entry PHR MAC CE as defined in clause 6.1.3.8, then the enhanced single-entry PHR as defined in clause 6.1.3.48 is generated and transmitted in another manner based on the value reported by the physical layer.

[0192] …

[0193] 2>Start or restart phr-PeriodicTimer;

[0194] 2>Start or restart phr-ProhibitTimer;

[0195] 2>Cancel all triggered PHRs.

[0196] ****************************END OF QUOTE********************************

[0197] The procedures and configurations related to auxiliary information in the current standard are described in [5] 3GPP TS 38.331 V18.0.0:

[0198] ***************************** Quote begins [5]**************************

[0199] 5.7.4 UE assistance information

[0200] 5.7.4.1 Overview

[0201] Figure 8 It is in 3GPP TS 38.331V18.0.0 Figure 5 .7.4.1-1: Reproduction of UE auxiliary information.

[0202] The purpose of this procedure is for the UE to inform the network:

[0203] …

[0204] - Configured grant assistance information for NR sidelink communications, or;

[0205] …

[0206] - the availability of data and / or signalling mapped to radio bearers not configured for SDT, or;

[0207] …

[0208] -UL business information, or;

[0209] …

[0210] 5.7.4.2 Initiation

[0211] …

[0212] A UE capable of providing configured grant assistance information for NR sidelink communication in RRC_CONNECTED may initiate the procedure in several situations, including after being configured to provide traffic mode information and after a change in traffic mode.

[0213] …

[0214] A UE capable of providing UL traffic information shall initiate the procedure when the information is available and after the UL traffic information has changed.

[0215] …

[0216] After initiating the procedure, the UE shall:

[0217] …

[0218] 1> If configured to provide configured grant assistance information for NR sidelink communication:

[0219] 2> Initiate transmission of the UEAssistanceInformation message according to 5.7.4.3 to provide the configured grant assistance information for NR sidelink communication;

[0220] …

[0221] 1> If configured to provide UL service information, then:

[0222] 2> if the UE has not transmitted a UEAssistanceInformation message with ul-TrafficInfo since it was configured to provide UL traffic information; or

[0223] 2> If the UL traffic information contained in the previous UEAssistanceInformation has changed since the last transmission of a UEAssistanceInformation message containing ul-TrafficInfo for at least one QoS flow for which timer T346x is not running:

[0224] 3> Initiate the transmission of the UEAssistanceInformation message according to 5.7.4.3 to provide UL service information.

[0225] …

[0226] 5.7.4.3 Actions related to the delivery of UEAssistanceInformation messages

[0227] The UE shall set the content of the UEAssistanceInformation message as follows:

[0228] …

[0229] 1> If the transmission of the UEAssistanceInformation message is initiated to provide UL service information according to 5.7.4.2, then:

[0230] 2> For each PDU session for which the UE wishes to provide UL service information in this UEAssistanceInformation message:

[0231] 3> Set pdu-SessionID to the value of the PDU session ID involved;

[0232] 3> For each QoS flow of this PDU session for which timer T346x is not running and for which the UE wishes to provide UL traffic information in this UEAssistanceInformation message:

[0233] 4> Start timer T346x associated with this QoS flow, where the timer value is set to the value of ul-TrafficInfoProhibitTimer;

[0234] 4> Set qfi to the value of the QFI involved;

[0235] 4> If jitter range measurement results are available; and

[0236] 4> If the UE has not provided a jitter range since it was configured to provide UL traffic information, or if the measured jitter range has changed since the last transmission of a UEAssistanceInformation message containing jitterRange:

[0237] 5> Set jitterRange to the latest measured value of the jitter range;

[0238] 4> if burst arrival time measurements are available; and

[0239] 4> If the UE has not provided the burst arrival time since it was configured to provide UL traffic information, or if the measured burst arrival time has changed since the last transmission of the UEAssistanceInformation message containing the burstArrivalTime:

[0240] 5> Set burstArrivalTime to the latest measured value of the burst arrival time;

[0241] 4> If business periodicity measurements are available; and

[0242] 4> If the UE has not provided traffic periodicity since it was configured to provide UL traffic information, or if the measured traffic periodicity has changed since the last transmission of a UEAssistanceInformation message containing trafficPeriodicity:

[0243] 5> Set trafficPeriodicity to the latest measured value of the traffic periodicity;

[0244] 4> If the UE has not provided pduSetIdentification since it was configured to provide UL traffic information, or if the information previously provided in pduSetIdentification has changed since the last transmission of a UEAssistanceInformation message containing pduSetIdentification:

[0245] 5> If the UE is able to identify the PDU set related information for the QoS flow:

[0246] 6>Set pduSetIdentification to true;

[0247] 5> Otherwise:

[0248] 6>Set pduSetIdentification to false.

[0249] …

[0250] The UE shall set the content of the UEAssistanceInformation message for the configured grant assistance information used for NR sidelink communication or NR sidelink positioning:

[0251] 1> If configured to provide configured grant assistance information for NR sidelink communication or NR sidelink positioning:

[0252] 2>Contains sl-UE-AssistanceInformationNR;

[0253] ****************************Next Quote*****************************

[0254] -UEAssistanceInformation

[0255] The UEAssistanceInformation message is used to indicate UE assistance information to the network.

[0256] …

[0257] Direction: UE to network

[0258] UEAssistanceInformation message

[0259]

[0260]

[0261]

[0262]

[0263]

[0264] …

[0265]

[0266] ****************************END OF QUOTE********************************

[0267] In [6] 3GPP TS 38.213 V18.1.0, RA procedures and power control are described.

[0268] **************************Quote [6] starts********************************

[0269] 7 Uplink Power Control

[0270] Uplink power control determines the power used for PUSCH, PUCCH, SRS and PRACH transmissions.

[0271] …

[0272] 7.1 Physical Uplink Shared Channel

[0273] 7.1.1UE Behavior

[0274] If a UE transmits a PUSCH on an active UL BWP b of carrier f in serving cell c using a parameter set configuration with index j and a PUSCH power control adjustment state with index l, the UE sets the PUSCH transmit power P at PUSCH transmission time instant i to PUSCH,b,f,c (i,j,q d ,l) is determined as

[0275]

[0276] …

[0277] 7.2 Physical Uplink Control Channel

[0278] 7.2.1UE Behavior

[0279] If a UE transmits a PUCCH on an active ULBWPb of carrier f of primary cell c using the PUCCH power control adjustment state with index 1, the UE sets the PUCCH transmit power P at PUCCH transmission time instant i to PUCCH,b,f,c (i,q u ,q d ,l) is determined as

[0280]

[0281] …

[0282] 7.3 Sounding Reference Signal

[0283] 7.3.1UE Behavior

[0284] If the UE transmits SRS on the active ULBWP b of carrier f of serving cell c based on the configuration implemented by SRS-ResourceSet using the SRS power control adjustment state with index l, then the UE sets the SRS transmission power P at SRS transmission time instant i to SRS,b,f,c (i,qs ,l) is determined as

[0285]

[0286] …

[0287] 7.4 Physical Random Access Channel

[0288] The UE sets the transmit power P of the physical random access channel (PRACH) on the active UL BWP b of carrier f of serving cell c to PRACH,b,f,c (i) Determined as

[0289] P PRACH，b，f，c (i) = min{P CMAX，f，c (i), P PRACH，target，f，c +PL b，f，c}[dBm],

[0290] Among them, P CMAX, f ,c (i) is the maximum output power of the UE configuration defined in [TS 38.101-1], [TS 38.101-2] and [TS 38.101-3] for carrier f of serving cell c at transmission time i, P PRACH,target, f ,c is the PRACH target received power PREAMBLE_RECEIVED_TARGET_POWER provided by higher layers [TS 38.321] for the active UL BWP b of carrier f serving cell c, and PL b,f,c is the path loss of the active UL BWP b for carrier f based on the DL RS associated with the PRACH transmission on the active DL BWP of serving cell c and calculated by the UE in dB as referenceSignalPower - higher layer filtered RSRP in dBm, where RSRP is defined in [TS 38.215] and the higher layer filter configuration is defined in [TS 38.331]. If the active DL BWP is the initial DL BWP and for SS / PBCH blocks and CORESET multiplexing mode 2 or 3, as described in clause 13, then the UE determines the PL based on the SS / PBCH blocks associated with the PRACH transmission. b,f,c .

[0291] …

[0292] 7.7 Power Headroom Report

[0293] The following are the types of UE power headroom reports: Type 1 UE power headroom PH valid for PUSCH transmission instant i on active UL BWP b of carrier f of serving cell c. Type 3 UE power headroom PH valid for SRS transmission instant i on active UL BWP b of carrier f of serving cell c.

[0294] The UE determines whether the power headroom report for the activated serving cell [TS 38.321] is based on the actual transmission or a reference format, the reference format being based on higher layer signaling of the configured grant and periodic / semi-static sounding reference signal transmission and downlink control information received by the UE prior to the PDCCH monitoring time and including the PDCCH monitoring time, wherein the UE detects the first DCI format or the DCI format of the initial transmission of the scheduled transport block, because if the power headroom report is reported on the PUSCH triggered by the first DCI format, then the power headroom report is triggered. Otherwise, the UE determines whether the power headroom report is based on the actual transmission or a reference format, the reference format being based on higher layer signaling of the configured grant and periodic / semi-static sounding reference signal transmission and the first uplink symbol of the configured PUSCH transmission minus T'. proc,2 =T proc,2 The downlink control information previously received by the UE, assuming d 2,1 =1,d 2,2 =0, T proc,2 Determined according to [TS 38.214], and wherein if power headroom reporting is reported on PUSCH using configured grants, then μ DL The subcarrier spacing corresponds to the active downlink BWP for the configured grant scheduling unit.

[0295] …

[0296] 7.7.1 Type 1 PH Report

[0297] If the UE determines that the Type 1 power headroom report of the activated serving cell is based on actual PUSCH transmission, then for PUSCH transmission time instant i on the active UL BWP b of carrier f of serving cell c, the UE calculates the Type 1 power headroom report as

[0298]

[0299] Among them, P CMAX,f,c (i) P O_PUSCH,b,f,c (j) α b,f,c (j), PL b,f,c (q d ),Δ TF,b,f,c (i) and f b,f,c (i,l) is defined in Clause 7.1.1.

[0300] …

[0301] 7.7.3 Type 3PH Report

[0302] If the UE determines that the Type 3 power headroom report of the activated serving cell is based on actual SRS transmission, and if the UE is not configured for PUSCH transmission on carrier f of serving cell c and the resources for SRS transmission are provided by SRS-Resource, then for SRS transmission time instant i on active UL BWP b of carrier f of serving cell c, the UE calculates the Type 3 power headroom report as

[0303] PH type3,b,f,c (i,q s )=P CMAX,f,c (i)-{P O_SRS,b,f,c (q s )+10log 10 (2 μ ·M SRS,b,f,c (i))+α SRS,b,f,c (q s )·PL b,f,c (q d )+h b,f,c (i)}[dB]

[0304] Among them, P CMAX,f,c (i) P O_SRS,b,f,c (q s ), M SRS,b,f,c (i), α SRS,b,f,c (q s ), PL b,f,c (q d ) and / or h b,f,c (i) In the clause

[0305] Defined in 7.3.1, where the corresponding value is provided by SRS-ResourceSet.

[0306] If the UE determines that the Type 3 power headroom report of the activated serving cell is based on the reference SRS transmission, and if the UE is not configured for SRS transmission time instant i on UL BWP b of carrier f of serving cell c and the resource for the reference SRS transmission is provided by SRS-Resource, then for SRS transmission time instant i on UL BWP b of carrier f of serving cell c, the UE calculates the Type 3 power headroom report as

[0307]

[0308] where q sis the SRS resource set corresponding to SRS-ResourceSetId=0 for UL BWP b, and is defined in clause 7.3.1 by the corresponding value obtained from SRS-ResourceSetId=0 for UL BWP b. O_SRS，b，f，c (q s ), α SRS,f,c (q s ), PL b,f,c (q d ) and h b,f,c (i) Assume that MPR = 0dB, A-MPR = 0dB, P-MPR = 0dB and ΔT C =0dB, calculate MPR, A-MPR, P-MPR and ΔT C Defined in [TS 38.101-1], [TS 38.101-2] and [TS 38.101-3].

[0309] …

[0310] 8 Random Access Procedure

[0311] Before initiating the physical random access procedure, Layer 1 receives a set of SS / PBCH block indices from higher layers and provides a set of corresponding RSRP measurement values ​​to the higher layers.

[0312] Before initiating the physical random access procedure, layer 1 may receive an indication from higher layers to perform a Type 1 random access procedure as described in clauses 8.1 to 8.4 or a Type 2 random access procedure as described in clauses 8.1 to 8.2A.

[0313] Before initiating the physical random access procedure, Layer 1 receives the following information from higher layers:

[0314] - Configuration of Physical Random Access Channel (PRACH) transmission parameters (PRACH preamble format, time resources, and frequency resources used for PRACH transmission).

[0315] - Parameters used to determine the root sequence and its cyclic shift in the PRACH preamble sequence set (index of the logical root sequence table, cyclic shift (N CS ) and the collection type (unrestricted, restricted collection A, or restricted collection B).

[0316] From the physical layer perspective, the Type 1 L1 random access procedure includes the transmission of a random access preamble (Msg1) in the PRACH, a random access response (RAR) message (Msg2) with PDCCH / PDSCH, and, when applicable, the transmission of a PUSCH scheduled by the RAR UL grant and a PDSCH for contention resolution.

[0317] From the physical layer perspective, the Type 2 L1 random access procedure includes the transmission of a random access preamble and PUSCH (MsgA) in PRACH and the reception of a RAR message (MsgB) with PDCCH / PDSCH, and, when applicable, the transmission of PUSCH scheduled by fallback RAR UL grant and PDSCH for contention resolution.

[0318] If the random access procedure is initiated by a PDCCH order to the UE, the PRACH transmission has the same SCS as the PRACH transmission initiated by higher layers.

[0319] …

[0320] 8.1 Random Access Preamble

[0321] The physical random access procedure is triggered after a request for PRACH transmission is issued by a higher layer or a PDCCH command. The configuration by higher layers for PRACH transmission includes the following:

[0322] - Configuration for PRACH transmission [TS 38.211].

[0323] -Preamble index, preamble SCS, P PRACH,目标 , corresponding to RA-RNTI and PRACH resources.

[0324] Use the selected PRACH format to transmit power P PRACH,b,f,c (i) Transmit PRACH on the indicated PRACH resources, as described in clause 7.4.

[0325] …

[0326] 8.1A PUSCH for Type 2 Random Access Procedure

[0327] For Type 2 random access procedure, the UE transmits PUSCH after transmitting PRACH, when applicable. The UE encodes the transport block provided for PUSCH transmission using redundancy version number 0. The PUSCH transmission follows at least N symbols after the PRACH transmission, where N = 2 for μ = 0 or μ = 1, N = 4 for μ = 2 or μ = 3, N = 16 for μ = 5, N = 32 for μ = 6, and μ is the SCS configuration for the active UL BWP.

[0328] If the PUSCH instance associated with the DMRS resource is not mapped to the preamble of a valid PRACH instance or if the associated PRACH preamble is not transmitted as described in clause 7.5 or clause 11.1 or clause 15 or clause 17.2, then the UE does not transmit PUSCH in the PUSCH instance. If the PRACH preamble is not mapped to a valid PUSCH instance, then the UE may transmit the PRACH preamble in the valid PRACH instance.

[0329] The mapping between one or more PRACH preambles and the PUSCH time instants associated with the DMRS resources is provided by MsgA-PUSCH-Resource according to the PUSCH configuration.

[0330] The UE determines the time and frequency resources for the PUSCH instants in the active UL BWP from the msgA-PUSCH-Config or separateMsgA-PUSCH-Config for the active UL BWP. If the active UL BWP is not the initial UL BWP and no msgA-PUSCH-Config or separateMsgA-PUSCH-Config is provided for the active UL BWP, the UE uses the msgA-PUSCH-Config or separateMsgA-PUSCH-Config provided for the initial UL BWP.

[0331] …

[0332] 8.2 Random Access Response - Type 1 Random Access Procedure

[0333] In response to a PRACH transmission, the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI during a window controlled by higher layers [TS 38.321]. The window starts at the first symbol of the earliest CORESET for which the UE is configured to receive a PDCCH for a Type 1-PDCCH CSS set as defined in clause 10.1, i.e., at least one symbol after the last symbol of the PRACH instant corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for a Type 1-PDCCH CSS set as defined in clause 10.1. If, as defined in [TS 38.211], or If it is not zero, the window will be TA +k mac milliseconds after the start, where T TA Defined in [TS 38.211] and k macProvided by kmacs, or if kmacs is not provided, then k mac = 0. Based on the SCS for the Type 1-PDCCH CSS set, the length of the window in several slots is provided by ra-ResponseWindow.

[0334] If the UE detects a DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI and the LSB of the SFN field in the DCI format 1_0 (if included and applicable) is the same as the corresponding LSB of the SFN in which the UE transmitted the PRACH, and the UE receives the transport block in the corresponding PDSCH within the window, the UE passes the transport block to the upper layer. The upper layer parses the transport block for the random access preamble identity (RAPID) associated with the PRACH transmission. If the upper layer identifies the RAPID in the RAR message of the transport block, the upper layer indicates an uplink grant to the physical layer. This is called a random access response (RAR) UL grant in the physical layer.

[0335] …

[0336] If the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order triggering a contention-free random access procedure for a SpCell [TS 38.321], the UE may assume that the PDCCH contains DCI format 1_0 and that the PDCCH order has the same DM-RS antenna port quasi-co-location property. If the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding RA-RNTI in response to a PRACH transmission initiated by a PDCCH order triggering a contention-free random access procedure for a secondary cell, the UE may assume that the DM-RS antenna port quasi-co-location property of the CORESET associated with the Type 1-PDCCH CSS set used to receive the PDCCH contains DCI format 1_0.

[0337] The RAR UL grant schedules the PUSCH transmission from the UE. The contents of the RAR UL grant starting with the MSB and ending with the LSB are given in Table 8.2-1.

[0338] …

[0339] Table 8.2-1: Random Access Response Grant Content Field Size

[0340]

[0341] ...Unless the UE is configured with SCS, the UE receives subsequent PDSCHs using the same SCS as that used to receive the PDSCH providing the RAR message.

[0342] …

[0343] 8.2A Random Access Response - Type 2 Random Access Procedure

[0344] In response to a transmission of PRACH and PUSCH, or in response to a transmission of PRACH only in the case where the PRACH preamble is mapped to a valid PUSCH instant, the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding MsgB-RNTI during a window controlled by higher layers [TS 38.321]. The window starts at the first symbol of the earliest CORESET for which the UE is configured to receive a PDCCH for a Type 1-PDCCH CSS set as defined in clause 10.1, i.e., at least one symbol after the last symbol of the PUSCH instant corresponding to the PRACH transmission, with a symbol duration corresponding to the SCS for the Type 1-PDCCH CSS set. If, as defined in [TS 38.211], or If it is not zero, the window will be TA +k mac milliseconds after the start, where T TA Defined in [TS 38.211] and k mac Provided by kmacs, or if kmacs is not provided, then k mac = 0. Based on the SCS for the Type 1-PDCCH CSS set, the length of the window in multiple slots is provided by msgB-ResponseWindow.

[0345] …

[0346] If the UE detects a DCI format 1_0 with a CRC scrambled by the corresponding MsgB-RNTI and the LSB of the SFN field in the DCI format 1_0 (if applicable) is identical to the corresponding LSB of the SFN in which the UE transmits a PRACH, and the UE receives the transport block in the corresponding PDSCH within the window, then the UE passes the transport block to the upper layer. The upper layer indicates to the physical layer an uplink grant, provided that the RAR message is for fallbackRAR and identifies the Random Access Preamble Identity (RAPID) associated with the PRACH transmission, and when the UE detects a RAR UL grant the UE procedure continues as described in clauses 8.2, 8.3 and 8.4, or

[0347] - Transmission of PUCCH with HARQ-ACK information with ACK value, provided that the RAR message is for successRAR, where

[0348] The PUCCH resource used for PUCCH transmission is indicated by the 4-bit PUCCH resource indicator field in the successRAR from the PUCCH resource set provided by pucch-ResourceCommon

[0349] -…

[0350] If the UE detects a transport block in DCI format 1_0 and the corresponding PDSCH with a CRC scrambled by the C-RNTI within the window, the UE transmits a PUCCH with HARQ-ACK information having an ACK value if the UE correctly detects the transport block or a NACK value if the UE incorrectly detects the transport block and the time alignment timer is running [TS38.321].

[0351] …

[0352] 8.3 PUSCH scheduled by RARUL

[0353] As described in clause 12 and [TS 38.211], for PUSCH transmissions scheduled by RAR UL grants, the active UL BWP with SCS configuration μ is indicated by higher layers.

[0354] …

[0355] Frequency domain resource allocation is performed according to uplink resource allocation type 1 [TS 38.214]. The UE processes the frequency domain resource assignment field as follows:

[0356] -if or for operation in FR1 with shared spectrum channel access, or for operation in In case of FR2-2 when ChannelAccessMode2-r17 is provided

[0357] -Truncate the frequency domain resource assignment field to its least significant bits and the truncated frequency resource assignment field is interpreted as the frequency resource assignment field for DCI format 0_0, as described in [TS 38.212].

[0358] -otherwise

[0359] -insert

[0360] - The most significant bit for operation in FR1 with shared spectrum channel access, or for FR2-2 when ChannelAccessMode2-r17 is provided

[0361] -otherwise, Most significant bits;

[0362] The value set to '0' is in the N UL,跃点 After the bit, if the frequency hopping flag is set to '0', then N UL,跃点 = 0, and if the transition flag is set to '1', then N is provided in Table 8.3-1 UL,跃点 , and interpret the extended frequency resource assignment field as the frequency resource assignment field in DCI format 0_0, as described in [TS 38.212]

[0363] -End of judgment

[0364] …

[0365] Table 8.3-1: Frequency offset of the second hop for a PUSCH transmission or Msg3 PUSCH retransmission with frequency hopping scheduled by an RAR UL grant

[0366]

[0367] The SCS used for PUSCH transmission is provided by the subcarrierSpacing in BWP-UplinkCommon. The UE transmits PRACH and PUSCH on the same uplink carrier of the same serving cell.

[0368] If the PUSCH transmission is not duplicated, the UE transmits the transport block in the PUSCH scheduled by the RAR UL grant in the corresponding RAR message using redundancy version 0. If the TC-RNTI is provided by higher layers, the scrambling initialization for the PUSCH corresponding to the RAR UL grant in clause 8.2 is performed by the TC-RNTI. Otherwise, the scrambling initialization for the PUSCH corresponding to the RAR UL grant in clause 8.2 is performed by the C-RNTI.

[0369] Msg3 PUSCH retransmissions of a transport block, if any, are scheduled by DCI format 0_0 with a CRC scrambled by the TC-RNTI provided in the corresponding RAR message [TS 38.321].

[0370] …

[0371] 8.4 PDSCH with UE Contention Resolution Identity

[0372] In response to a PUSCH transmission scheduled by a RAR UL grant when the UE is not provided with a C-RNTI, the UE attempts to detect DCI format 1_0 [TS 38.321] with a CRC scrambled by the corresponding TC-RNTI that schedules a PDSCH containing the UE's contention resolution identity. In response to a PDSCH reception with the UE's contention resolution identity, the UE transmits HARQ-ACK information in the PUCCH. The PUCCH transmission is within the same active UL BWP as the PUSCH transmission. The minimum time between the last symbol of the PDSCH reception and the first symbol of the corresponding PUCCH transmission with HARQ-ACK information is equal to N T,1 +0.5ms. When additional PDSCH DM-RS is configured, N T,1 is the duration of N1 symbols corresponding to the PDSCH processing time of UE processing capability 1. For μ=0, the UE assumes N 1,0 =14[TS 38.214].

[0373] When a DCI format is detected in response to a PUSCH transmission scheduled by a RAR UL grant, as described in [TS 38.321], or by a corresponding PUSCH retransmission scheduled by DCI format 0_0 with a CRC scrambled by the TC-RNTI provided in the corresponding RAR message [TS 38.321], the UE may assume that the PDCCH carrying the DCI format has the same DM-RS antenna port quasi-co-location property for the SS / PBCH blocks that the UE uses for PRACH association, as described in clause 8.1, regardless of whether the UE is provided with the TCI-State of the CORESET in which the UE received the PDCCH with the DCI format.

[0374] …

[0375] 16 UE procedures for sidelink

[0376] 16.2 Power Control

[0377] 16.2.0 S-SS / PSBCH Block

[0378] The power P at which the UE transmits the S-SS / PSBCH block in slot i on the active SL BWPb of carrier f S-SSB (i) Determined as

[0379]

[0380] …

[0381] 16.2.1 PSSCH

[0382] The power P that the UE will use for PSSCH transmission on the resource pool in symbol S-SSB (i) Determined as follows, where the corresponding PSCCH is not transmitted in the PSCCH-PSSCH transmission instant i on the active SL BWPb of carrier f:

[0383] P PSSCH (i) = min(P CMAX ,P MAX,CBR ,min(P PSSCH,D (i),P PSSCH,sL (i)))[dBm]

[0384] …

[0385] 16.2.2 PSCCH

[0386] The power P that the UE will use for PSCCH transmission on the resource pool at PSCCH-PSSCH transmission time i is PSCCH (i) Determined as

[0387]

[0388] …

[0389] 16.2.3 PSFCH

[0390] With N for HARQ-ACK information and collision information sch,Tx,PSFCH Scheduled PSFCH transmission, and can transmit a maximum of N max,PSFCH Number N of synchronized PSFCH transmissions N of a PSFCH UE on all resource pools at PSFCH transmission time i on active SL BWPb of carrier f Tx,PSFCH and for PSFCH transmission k(1≤k≤N Tx,PSFCH ) power P PSFCH,k (i) Determined as

[0391] - If dl-P0-PSFCH is provided, then

[0392] P PSFCH,一 =P O,PSFCH +10log 10 (2 μ )+α PSFCH PL [dBm]

[0393] …

[0394] -otherwise

[0395] P PSFCH,k (i) = P CMAX -10log 10 (N Tx,PSFCH )[dBm]

[0396] ***************************End of Quote******************************

[0397] In the 3GPP RAN1#116 meeting, there are some agreements on ambient Internet of Things (IoT).

[0398] For the purposes of this study, RAN1 uses the following terminology:

[0399] Device 1: ~1 μW peak power consumption, with energy storage, and initial sampling frequency offset (SFO) up to 10 X ppm, there is neither a downlink (DL) amplifier nor an uplink (UL) amplifier in the device. The UL transmission of the device is backscattered on an externally provided carrier.

[0400] Device 2a: ≤ several hundred μW peak power consumption, with energy storage, initial sampling frequency offset (SFO) up to 10 X ppm, the device has DL and / or UL amplifiers in it. The device's UL transmission is backscattered on an externally provided carrier.

[0401] ● Device 2b: ≤ several hundred μW peak power consumption, with energy storage, initial SFO up to 10 X ppm, the device has DL and / or UL amplifiers. The UL transmission of the device is generated internally by the device.

[0402] For research purposes, at least the following bandwidths are defined for Reader to Device (R2D):

[0403] ●Transmission bandwidth B from the reader's perspective tx,R2D : Frequency resources used to transmit R2D

[0404] ● Occupied bandwidth B from the reader's perspective occ,R2D : Frequency resources used for R2D transmission, and potential guard bands

[0405] ●B occ,R2D ≥B tx,R2D

[0406] ○FFS (for further study): further constraints, such as B occ,R2D =B tx,R2D .

[0407] ○The possible values ​​of each bandwidth are for further study

[0408] From a RAN1 perspective, an Ambient IoT (A-IoT) contention-based access procedure initiated by the reader is used, at least when responses from multiple devices intended to be identified are expected.

[0409] At least the following time-domain frame structures of A-IoT R2D and A-IoT device-to-reader (D2R) transmission are studied.

[0410] ●For R2D transmission,

[0411] o An R2D opportunity acquisition signal (eg, an R2D preamble) is included for at least opportunity acquisition and for indicating the start of R2D transmission in the time domain.

[0412] ●For D2R transmission,

[0413] o A D2R opportunity acquisition signal (eg, a D2R preamble) is included for at least opportunity acquisition and for indicating the start of D2R transmission in the time domain.

[0414] ●Other necessary components are for further study, such as midamble, postamble, periodic synchronization signal, control field, and guard period.

[0415] To further this discussion, the following terms are used in A-IoT to study the processing time aspects:

[0416] ●T R2D_min : The minimum time between an R2D transmission and its subsequent corresponding D2R transmission.

[0417] ●T D2R_min : Minimum time between a D2R transmission and its subsequent corresponding R2D transmission.

[0418] ●T R2D_R2D_min : Minimum time between two different consecutive R2D transmissions to the same A-IoT device.

[0419] ●T D2R_D2R_min : Minimum time between two different consecutive D2R transmissions from the same A-IoT device.

[0420] The study should consider at least the following aspects:

[0421] ○ Limitations of existing base station (BS) / user equipment (UE) implementation schemes.

[0422] ○[Is the processing time common or different for different A-IoT devices].

[0423] ○ [Processing time for different service types / command types (e.g., Device-Terminated (DT) or Device-Originated-Device-Terminated Trigger (DO-DTT)) and / or different use cases (e.g., manifest or command)].

[0424] Other timings require further study:

[0425] For ambient IoT devices, at least for R2D data transfer, a physical channel (Physical Reader (to Ambient IoT) Device Channel (PRDCH)) is studied.

[0426] o System information is transmitted on PRDCH (if defined).

[0427] o Whether / how to transmit control information on PRDCH is for further study.

[0428] ●Note: The nomenclature of PRDCH is used for research purposes.

[0429] For ambient IoT devices, at least for D2R data transfer, the physical channel (Physical (Ambient IoT) Device to Reader Channel (PDRCH)) is studied along with:

[0430] • Responses transmitted from the device to the reader during the contention-based access procedure are transmitted on the PDRCH.

[0431] ○For further study: Details of the response.

[0432] • Whether to transmit D2R control information on PDRCH (if defined) / how to transmit D2R control information on PDRCH (if defined) / what D2R control information to transmit on PDRCH (if defined) is for further study.

[0433] ●Note: The nomenclature of PDRCH is used for research purposes.

[0434] In recent years, there has been a growing expectation that more devices will be interconnected in a wirelessly connected world, improving productivity and increasing comfort. However, powering all IoT devices with batteries that require manual replacement or recharging leads to high maintenance costs, environmental concerns, and safety concerns in some use cases (e.g., wireless sensors in power systems). Further reductions in the size, complexity, and power consumption of IoT devices will enable their deployment in a variety of applications (e.g., automated manufacturing, smart homes).

[0435] On the other hand, barcodes and radio frequency identification (RFID) have a limited read range of several meters, which typically requires handheld scanning. This results in labor-intensive and time-consuming operations. Moreover, the lack of interference management schemes leads to severe interference and capacity issues between RFID readers, especially in dense deployments. RFID struggles to support large-scale, seamless coverage networks. In contrast, research on ambient IoT investigates the feasibility of new IoT technologies within the 3GPP system.

[0436] Ambient IoT devices / UEs will have ultra-low complexity, extremely small device size, and a long lifecycle. They will have complexity and power consumption orders of magnitude lower than existing 3GPP Low Power Wide Area (LPWA) technologies (e.g., Narrowband (NB)-IoT, enhanced Machine Type Communication (eMTC)). Ambient IoT devices / UEs may or may not have energy storage. Energy for the ambient IoT devices / UEs can be provided by harvesting carrier waves, radio waves, light, motion, heat, or any other suitable power source. Energy and / or power can be provided once (e.g., unexpectedly or aperiodically), periodically, or continuously. In one embodiment, power / energy for the ambient IoT devices / UEs can be provided by carrier waves from the network and / or intermediate nodes. In Topology 1, the ambient IoT devices / UEs will communicate directly and bidirectionally with the base station. In Topology 2, the ambient IoT devices / UEs will communicate bidirectionally with intermediate nodes (e.g., UEs or relay nodes) between the ambient IoT devices / UEs and the base station. The UL transmission of an ambient IoT device / UE can be generated internally by the device / UE or backscattered on an externally provided carrier. More details on ambient IoT (devices / UEs) can be found in the study project [1] RP-234058, [2] 3GPP TR 38.848 V18.0.0, and the agreement from the RAN1#116 meeting.

[0437] Because ambient IoT devices / UEs have limited power and computing / processing capabilities to perform transmissions, the network (NW) / reader may not be able to deterministically predict / know the power status, processing time / latency, and / or data type of the ambient IoT devices / UEs. This can make it difficult for the NW / reader to properly schedule transmissions for the ambient IoT devices / UEs.

[0438] The network will trigger the ambient IoT device to execute the first procedure (eg, random access procedure). Figure 9 and Figure 10As shown in , in response to receiving a first signaling (e.g., query, paging) from the network, the ambient IoT device will perform one or more D2R transmissions and / or R2D receptions during a first procedure (e.g., random access procedure). The ambient IoT device will transmit / perform one or more D2R transmissions and / or receive one or more R2D transmissions during the first procedure (e.g., random access procedure). Under limited energy capacity, the ambient IoT device may not always be able to perform transmissions. The network may not always be able to control the real-time energy status of all devices. If (at least) the network schedules an ambient IoT device that does not have enough energy to execute or complete the first procedure, then a transmission failure will occur. Such a failure not only affects network performance, but also generates unnecessary conflicts, data delays, and resource inefficiency. For example, the network may schedule additional resources for the failed device to re-access, and the resources cannot be used by devices with insufficient remaining energy.

[0439] In the following disclosure, "UE" may be, or may be replaced by, a "device," "ambient IoT device," or "ambient IoT UE." Hereinafter, "NW" may be, include, or be replaced by, a "network node," a "reader," an "intermediate node," or "another UE." Hereinafter, "reader" may be, or may be replaced by, a "NW" or a "legacy UE."

[0440] The UE may (at least) provide (or transmit) first information to the NW / reader, such as information about the UE's power state, processing time / delay, and / or (available) data (type). The UE may perform a D2R transmission carrying (or including) the first information. The UE may, for example, predict, calculate, derive, and / or determine the first information based on its power / energy state and / or processing time / delay. The first information may be (D2R) control information. The first information may be auxiliary information (of the ambient IoT). The first information may be, include, indicate, and / or relate to (at least) one or more of the following information:

[0441] UE / Device ID

[0442] The UE identity (ID) may be used to identify the UE (e.g., within an area). The UE identity and / or UE ID may be or include a random number / value (e.g., RN16), a temporary number, a preamble number (e.g., a Random Access Preamble Identifier (RAPID)), and / or an ID selected / generated / determined by the UE. The UE identity and / or UE ID may be or include the UE's device ID, UE ID, group ID, contention resolution identifier, and / or radio network temporary identifier (RNTI).

[0443] The UE ID may be stored by the UE. The UE ID may be a temporary ID. The UE ID may be assigned to the UE. The UE ID may be predefined or (pre)configured for the UE (e.g., by the UE). The UE ID may be configured or indicated to the UE (e.g., by a NW / reader). The UE may calculate, select, derive, or determine the UE ID itself. The UE ID may be a UE-Identity.

[0444] UE Group ID

[0445] Multiple UE groups may exist. A UE may be assigned or associated with a UE group. A UE group may be predefined or (pre)configured to the UE (e.g., by the UE). A UE group may be configured or indicated to the UE (e.g., by a NW / reader). The UE may receive a group ID and / or value via a query, paging, System Information Block (SIB), and / or PRDCH to derive / determine the group ID.

[0446] Multiple UEs can be assigned to different UE groups based on UE type. UEs of the same UE type can be in the same UE group. UEs of the same UE type can be in different UE groups. UE groups can include UEs of the same or different UE types.

[0447] Multiple UEs may be assigned to or associated with different UE groups based on their UE IDs. For example, a UE may be assigned to or associated with a UE group, wherein the UE group ID of the UE group may be determined / derived / determined based at least on the UE ID of the UE and a value. Preferably, in certain embodiments, the UE group ID of the UE may be determined / derived / determined by the UE ID modulo the value. The value may be the number of UE groups. The value may be provided by the NW / reader or may be predefined or (pre)configured. The UE group ID of the UE may be determined by a formula using the UE ID.

[0448] Multiple UEs can be assigned to different UE groups based on location. Preferably, in certain embodiments, UEs in the same location and / or in the same azimuth range can be distributed to the same UE group. The UE can determine / derive its location or range based on the received carrier (signal). More specifically, the UE can determine / derive its location or range relative to the network / reader based on the received power of the carrier (signal) transmitted from the network / reader. UEs in the same location and / or in the same range may mean UEs with carriers (signals) of the same received power range. Preferably and / or alternatively, in certain embodiments, UEs in the same location and / or in the same azimuth range can be distributed to different UE groups. UEs in the range that can receive the same power supply, carrier and / or NW / reader signal can be (randomly) distributed to different UE groups.

[0449] UE / Device Type

[0450] There may be two or more types of UEs. The UE types (or device types) may be distinguished by at least power consumption, energy storage, method of performing UL transmissions, power level and / or device size. Preferably, in certain embodiments, the method of performing UL transmissions may be generated internally by the device / UE or backscattered on an externally provided carrier (signal). The UE type (or device type) may be or include at least device 1, device 2a and / or device 2b, as described in the agreement of RAN1. The UE type (or device type) may be or include at least device A, device B and / or device C, as considered in [2] TR 38.848 V18.0.0.

[0451] For example, a first type UE (e.g., device 1, device A, device B) may have (or be equipped with) a battery or energy storage. A first type UE (or device) may not have (or be equipped with) a battery or energy storage. A first type UE (or device) may not have (or be equipped with) a DL / UL amplifier. A first type UE (or device) may be a passive or semi-passive device. A first type UE (or device) may generate an UL transmission via backscatter. A first type UE (or device) may perform backscatter transmission. A first type UE (or device) may not itself (internally) generate an UL transmission. A first type UE (or device) may not have the capability to generate a signal without backscatter.

[0452] For example, a second type of UE (e.g., device 2a, device 2b, device C) may have (or be equipped with) a battery or energy storage. A second type of UE (or device) may have (or be equipped with) a DL / UL amplifier. A second type of UE (or device) may be an active device. A second type of UE (or device) may generate UL transmissions via backscatter. A second type of UE (or device) may perform backscatter transmissions. A second type of UE (or device) may be capable of (internal) generating UL transmissions. A second type of UE (or device) may have the capability to generate signals without backscatter.

[0453] Energy or power related information

[0454] The information may include, for example, the (remaining / available) energy or power of the (UE's) energy storage. The information may be based on or related to the (remaining / available) energy / power of the UE after the D2R transmission carrying the first information. Alternatively, in certain embodiments, the information may be based on or related to the (remaining / available) energy / power of the UE before the D2R transmission carrying the first information. The information may be based on or related to the (remaining / available) energy / power after one or more D2R transmissions. The information may be represented by the power state or power level of the UE.

[0455] One or more bits may be used to indicate this information. For example, a bit (or information) set to a first value (e.g., 0) may mean that the UE's (remaining / available) energy / power (for subsequent D2R transmission and / or R2D reception) is insufficient. A bit (or information) set to a second value (e.g., 1) may mean that the UE's (remaining / available) energy / power (for subsequent D2R transmission and / or R2D reception) is sufficient. For example, a bit (or information) set to a first value may mean that the UE's (remaining / available) energy / power is at a first power level / state. A bit (or information) set to a second value may mean that the UE's (remaining / available) energy / power is at a second power level / state. The first and second values ​​may indicate indices of predefined power levels / states.

[0456] Power Level

[0457] The power level may include any one or more of the following embodiments. The UE may utilize the same or different power level embodiments for different resource selection steps, such as determination of the bandwidth part (BWP), determination of the (D2R) resource / configuration group, determination of the transmission type, determination of the (transmission) preamble, and / or determination of the PDRCH timing. This information may be indicated by (some fields of) the power headroom report (PHR). One or more thresholds for the power level may exist. The power level may be determined by a threshold. The power level threshold may be configured by the network or derived by the UE. The power level threshold may be determined based on the following embodiments and / or (selected) (D2R) resource / configuration. The power level threshold may be indicated or configured by the NW / reader. The power level threshold may be determined by the UE. The power level threshold may be fixed.

[0458] In one embodiment, the power level may be the received power of a signal / channel transmitted from the network.The power level may be the received power of a carrier (signal) transmitted from the network.

[0459] In one embodiment, the power level may be a (R2D) path loss derived / determined based on at least the received power of a signal / channel transmitted from the network. The power level may be a (downlink) path loss derived / determined based on at least the received power of a carrier (signal) transmitted from the network.

[0460] In one embodiment, the power level may be an expected / derived / determined UE transmit power for backscatter transmissions (eg, D2R transmissions).

[0461] In one embodiment, the power level may be an expected / derived / determined UE transmit power for D2R transmissions generated internally by the UE.

[0462] In one embodiment, the power level may be the maximum UE transmit power (eg, for D2R transmission).

[0463] In one embodiment, the power level may be the amount of battery power / stored power / available power of the UE. The UE may estimate / determine / derive how much battery power / stored power / available power is available / usable to perform the initial procedure and / or D2R transmission.

[0464] In one embodiment, the power level may be a predefined / (pre)configured / indicated power level. The indicated power level may be indicated by the network or by a higher layer of the UE. Preferably, in certain embodiments, the predefined / (pre)configured / indicated power level may be a guaranteed or required power level (amount or capacity) for enabling / activating / starting the (corresponding) initial procedure and / or D2R transmission. Preferably, in certain embodiments, the predefined / (pre)configured / indicated power level may be an expected / estimated power consumption level (amount) for completing the (corresponding) initial procedure and / or D2R transmission.

[0465] In one embodiment, the power level may be the power difference between the (R2D) path loss and the desired / derived / determined / maximum UE transmit power. The (R2D) path loss may be derived / determined based on at least a signal / channel from the network, such as the received power of a carrier (signal). The desired / derived / determined UE transmit power may be used for backscatter transmissions or for (D2R) transmissions generated internally by the UE.

[0466] In one embodiment, the power level may be the power difference between battery power / stored power / available power and the desired / derived / determined / maximum UE transmit power. The desired / derived / determined UE transmit power may be used for backscatter transmission or for D2R transmission generated internally by the UE. The UE may estimate / determine / derive how much battery power / stored power / available power is available for performing the (corresponding) initial procedure and / or D2R transmission.

[0467] In one embodiment, the power level may be the power difference between a predefined / (pre)configured / indicated power and an expected / derived / determined / maximum UE transmit power. The indicated power may be indicated by the network or by higher layers of the UE. Preferably, in certain embodiments, the predefined / (pre)configured / indicated power may be a guaranteed or required power (amount or capacity) for enabling / activating / starting the (corresponding) initial procedure and / or D2R transmission. Preferably, in certain embodiments, the predefined / (pre)configured / indicated power may be an expected / estimated power consumption (amount) for completing the (corresponding) initial procedure and / or D2R transmission. The expected / derived / determined UE transmit power may be used for backscatter transmission or for D2R transmission generated internally by the UE.

[0468] Data type (or transfer type)

[0469] The data type (or transmission type) may indicate the type of (D2R) transmission (or data). The data type (or transmission type) may indicate traffic information (e.g., TrafficInfo in [5] TS 38.331 V18.0.0), usage, traffic context, service type, quality of service (QoS), (logical) channel (group), and / or topology. The data type (or transmission type) may be (or include): 2-step, 4-step, initial, subsequent, data, signaling, device-originating (DO), device-originating-device-terminated triggered (DO-DTT), device-terminated (DT), single, data burst, periodic, aperiodic, delay tolerant, and / or urgent.

[0470] (D2R) data size

[0471] The (D2R) data size may be calculated / derived / determined by the UE. The (D2R) data size may correspond to the (D2R) data type. The (D2R) data size may be the (potential / pending) transport block size (TBS) for (D2R) transmission and / or PDRCH transmission. The (D2R) data size may be the (potential / pending) TBS for transmission in the first procedure. The (D2R) data size may be the TBS for ambient IoT information (or data). The (D2R) data size may be the minimum size available for the UE to perform (data) transmission. The (D2R) data size may be a preferred value available for the UE to perform (data) transmission. The (D2R) data size may be the pending, available, or remaining data size before the UE sleeps and / or suspends the first procedure.

[0472] Information related to (data) services

[0473] The information may be (or include or indicate) at least one or more of the following: business pattern, (expected) time information related to the arrival of data (or packet), how long it will take for the (next) data to arrive, the latency requirement of the data (or packet), the priority of the data (or packet), the importance of the data (or packet), the expected time of arrival of the (next) data, the (expected) data arrival interval, and the period of data arrival.

[0474] Information related to processing time / delays

[0475] The information may be (or include or indicate) at least one or more of the following: (required, expected, minimum) time information related to processing / calculation / measurement, how long the current / pending data is expected / able to be transmitted / reported, how long it will take for the (next) data to be transmitted, the (required / expected) time for the (next) data transmission, the (required / expected) cycle for data processing, the (required / expected) cycle for data transmission, an indication or flag for (delayed) processing, an indication or flag for indicating "ready to transmit / report" or "not ready to transmit / report", an indication or flag for indicating whether the transmission / report is delayed or not.

[0476] Information related to UE wake-up (or activity)

[0477] The information may be (or include or indicate) at least one or more of the following: the UE's (expected or preferred) wake-up time, time information related to UE wake-up, information related to the UE's active time (e.g., the estimated (minimum or maximum) remaining time until it will be active), information related to the UE's inactive time (e.g., the estimated (minimum or maximum) remaining time until it will go into sleep), the time the UE will wake up (or is expected to wake up), and the time until the UE next wakes up or goes into sleep. The UE being awake or active may mean that the UE is monitoring R2D signaling and / or PRDCH. The UE being about to go into sleep or being inactive may mean that the UE is not monitoring R2D signaling and / or PRDCH.

[0478] One or more bits may be used to indicate this information. For example, a bit (or information) set to a first value (eg, 0, 1) may mean that the UE will sleep, eg, after transmitting a transmission carrying the first information.

[0479] (Required) number of repetitions

[0480] The information may relate to the (required) number of repetitions (for) D2R transmission and / or PDRCH transmission. The repetitions may include an initial transmission and (subsequent) retransmissions. The repetitions may be or include bundled transmissions.

[0481] Number of transmissions

[0482] The number of transmissions may be how many additional (in terms of Transmission Time Interval (TTI) / time or size) D2R transmissions may be performed (eg, based on remaining / available energy / power). The additional D2R transmissions may be in addition to or after the D2R transmission carrying the first information.

[0483] The number of transmissions may be how many additional (in terms of TTI / time or size) R2D reception / listening may be performed (eg based on remaining / available energy / power). The additional R2D reception / listening may be R2D reception in addition to or after the first signaling (as described below).

[0484] The number of transmissions may be how many additional pairs of D2R transmissions and R2D receptions / listening may be performed (eg, based on remaining / available energy / power). The additional pairs of transmissions / receptions may be transmissions in addition to or after the D2R transmission carrying the first information and the first signaling (as described below).

[0485] The number of transmissions may be timeslots / TTIs / times, number of bits or bytes, amount of data, number of (completed) transmissions / receptions, number of PDRCH transmissions, and / or number of PRDCH receptions / monitorings. The number of transmissions may or may not include repetitions.

[0486] The size can be in bits or bytes. The size can be in transport blocks (TB) or TTI.

[0487] Direction or location information

[0488] The information may be (or include or indicate) the coordinates of the UE. The information may be (or include or indicate) the area in which the UE is located. The information may be (or include or indicate) an area ID. An area may be (or include) a cell, a tracking area, or a range of areas.

[0489] Time information for next / corresponding R2D reception

[0490] The time information may be, include, be replaced by, be referred to as, be expressed as and / or be indicated as a duration, a timer (value) and / or an indication (e.g., of a duration level). The time information may be the (minimum) (required) time for energy or power accumulation for the next / corresponding R2D reception or listening for R2D transmission (e.g., after the D2R transmission carrying the first information). In other words, the UE may not perform the (next) R2D reception or listen for the (next) R2D transmission before the time indicated by the information expires. The time information may be Figure 9 The time information may be T1 and / or T3 in (as described below). Figure 10 T3 in (as described below).

[0491] The time indicated by this information may start after the end of the D2R transmission carrying this information (in the first TTI / time instant).

[0492] If the (required) time is greater than the required (minimum) processing time, the first information (e.g., time information) may be provided. If the (required) time is not greater than the required (minimum) processing time, the first information (e.g., time information) may not be provided. If the (required) time is less than or equal to the required (minimum) processing time, the first information (e.g., time information) may not be provided.

[0493] If the time information for the next / corresponding R2D reception is greater than the (pre)configured / specified minimum processing time, the first information (e.g., the time information for the next / corresponding R2D reception) may be provided. If the time information for the next / corresponding R2D reception is not greater than (i.e., less than or equal to) the (pre)configured / specified minimum processing time, the first information (e.g., the time information for the next / corresponding R2D reception) may not be provided. The (pre)configured / specified minimum processing time may be / mean the minimum time between a D2R transmission and a subsequent corresponding R2D transmission, for example, denoted as T D2R_min .

[0494] The duration may be represented by a number of TTIs / time instants.

[0495] Time information for the next D2R transmission

[0496] The time information may be, include, be replaced by, be referred to as, be expressed as and / or be indicated as a duration, a timer (value) and / or an indication (e.g., of a duration level). The time information may be the (minimum) (required) time for energy or power accumulation for the next D2R transmission (e.g., after the D2R transmission carrying the first information). In other words, the UE may not (expectedly) perform the (next) D2R transmission before the time indicated by this information has expired. The time information may be Figure 9 The time information may be T2 and / or T4 in (as described below). Figure 10 T4 in (as described below).

[0497] The time indicated by this information may start after the end of the D2R transmission carrying this information (in the first TTI / time instant).

[0498] If the (required) time is greater than the required (minimum) processing time, the first information (e.g., time information) may be provided. If the (required) time is not greater than the required (minimum) processing time, the first information (e.g., time information) may not be provided. If the (required) time is less than or equal to the required (minimum) processing time, the first information (e.g., time information) may not be provided.

[0499] If the time information for the next D2R transmission is greater than the (pre)configured / specified minimum processing time, the first information (e.g., the time information for the next D2R transmission) may be provided. If the time information for the next D2R transmission is not greater than (i.e., less than or equal to) the (pre)configured / specified minimum processing time, the first information (e.g., the time information for the next D2R transmission) may not be provided. The (pre)configured / specified minimum processing time may be / mean the minimum time between two different consecutive D2R transmissions from the same UE, e.g., denoted as T D2R_D2R_min .

[0500] The duration may be represented by a number of TTIs / time instants.

[0501] Time information for suggesting (or preferring) R2D reception and / or suggesting D2R transmission

[0502] The time information may be, include, be replaced by, be referred to as, be expressed as and / or be indicated as a duration, a timer (value) and / or an indication (eg, of a duration level).

[0503] The time information may indicate a recommended (or expected / preferred) time (duration) or expiration / expiration time for receiving / listening for an acknowledgment (ACK), a NW / reader response, a response to a D2R transmission, and / or the next or subsequent R2D reception. The time information may indicate a time for scheduling the next or subsequent D2R transmission (e.g., Figure 9 or Figure 10 The recommended (or expected / preferred) time (duration) or expiration time of the third transmission in the R2D transmission. The scheduling of subsequent D2R transmissions may be provided for R2D transmissions (e.g., Figure 9 ACK or subsequent R2D transmission, or Figure 10 Before the time starts, the UE may not (expect) receive or listen for an ACK, NW / reader response, a response to a D2R transmission, a next or subsequent R2D reception, and / or a scheduling of a next or subsequent D2R transmission. After the time ends or after the expiration time, the UE may not (expect) receive or listen for an ACK, NW / reader response, a response to a D2R transmission, a next or subsequent R2D reception, and / or a scheduling of a next or subsequent D2R transmission. The time information may be Figure 9 The time information can be Ta and / or Tc in (as described below). Figure 10 Tc in (as described below).

[0504] The time information may indicate the time for the next or subsequent D2R transmission (eg, Figure 9 The second and / or third transmission in Figure 10The recommended (or expected / preferred) time (duration) or expiration time of the third transmission in the time interval. Before the time interval starts, the UE may not (expectedly) perform the next or subsequent D2R transmission. After the time interval ends or after the expiration time, the UE may not (expectedly) perform the next or subsequent D2R transmission. The time information may be Figure 9 The time information may be Tb and / or Td in (as described below). Figure 9 Td in (as described below).

[0505] The time information may indicate a start point of time (eg, TTI). The time information may indicate a length of time (eg, TTI). The time information may indicate an end point of time (eg, TTI).

[0506] cause

[0507] The cause may indicate at least one or more of the following: DO-DTT (Device Initiated-Device Terminated Trigger) (transmission), DT (Device Terminated) (transmission), DO (Device Initiated) transmission, ambient IoT (transmission), non-ambient IoT (transmission), reason for terminating the first procedure, status of the first information, satisfaction of the condition, whether the first signaling is required.

[0508] It should be noted that any of the methods, alternatives, concepts, examples and embodiments described above and herein may be combined in whole or in part, or applied simultaneously or individually.

[0509] The UE may receive first signaling (e.g., paging) to trigger a first procedure (e.g., a random access procedure). During the first procedure (e.g., the random access procedure), the UE may provide energy information in a first transmission, thereby indicating whether the UE's remaining energy is sufficient for (at least) one or more (subsequent) transmissions or receptions after the first transmission. The energy information may indicate at least one of the following: whether the UE's remaining energy is sufficient (insufficient) for one or more (subsequent) transmissions or receptions after the first transmission, whether the UE's remaining energy is insufficient for one or more (subsequent) transmissions or receptions after the first transmission, or whether the UE's remaining energy is insufficient to complete the random access procedure.

[0510] The first transmission may be a D2R transmission during a first procedure (e.g., a random access procedure). One or more (subsequent) transmissions or receptions may be or include one or more D2R transmissions and R2D receptions during the first procedure (e.g., a random access procedure). If, when, in response to, and / or based on the UE having sufficient remaining energy, the energy information may indicate a first value. If, when, in response to, and / or based on the UE having insufficient remaining energy, the energy information may indicate a second value. If, when, in response to, and / or based on the UE having sufficient remaining energy, the UE may not provide energy information. If, when, in response to, and / or based on the UE having insufficient remaining energy, the UE may provide energy information. After providing energy information indicating insufficient remaining energy of the UE, if, when, in response to, and / or based on providing energy information indicating insufficient remaining energy of the UE, the UE may stop the first procedure (e.g., a random access procedure).

[0511] like Figure 9 and Figure 10 As shown in , the UE may execute, for example, a first procedure for ambient IoT. The first procedure may be contention-based or contention-free. The first procedure may include both contention-based transmission and contention-free transmission. The first procedure may be a (ambient IoT) data transmission procedure, a (ambient IoT) response procedure, or a (ambient IoT) reporting procedure. The first procedure may be a procedure for random access (RA), (initial) access, (ambient IoT) response / report, and / or (R2D / D2R) transmission. The first procedure may be and / or include transmission. The UE may access the NW / reader, receive signaling / messages / configuration, and / or transmit (D2R) data via the procedure.

[0512] The UE may receive a first signaling from the NW / reader. The UE may execute (or initiate) a first procedure in response to (or based on) the first signaling.

[0513] The first signaling may be a query, paging, a system information block (SIB), a radio resource control (RRC) message (e.g., an RRC setup request), a medium access control (MAC) signaling (e.g., a MAC control element (CE)), and / or physical (PHY) signaling (e.g., PRDCH, physical downlink control channel (PDCCH), downlink control information (DCI)). The first signaling may be (or include) a carrier (signal), an R2D signal / channel, and / or an inquiry signal. The first signaling may be (or include) common signaling. The first signaling may be (or include) cell-specific signaling. The first signaling may be (or include) broadcast signaling. The first signaling may be received by, for example, multiple UEs (or a group of UEs) in a UE group. The first signaling may be (or include) dedicated signaling. The first signaling may be (or include) UE-specific signaling.

[0514] The first signaling may be used to trigger (or instruct) a (random) access procedure, transmission, and / or reception by the UE. The transmission from the UE may be (or include) a backscatter transmission (or reception), or may be generated internally by the UE. The first signaling may indicate which response(s) the UE should make to the first signaling. The first signaling may indicate which UE(s) are permitted to perform (or initiate) an access procedure, transmission, and / or reception. The first signaling may indicate a configuration to be used for (subsequent) (data) transmission or reception (or procedure).

[0515] like Figure 9 As shown, in response to receiving the first signaling, the UE may transmit a first transmission to the NW / reader, for example, based on a first condition. In response to receiving / detecting / decoding the first transmission, the NW / reader may transmit an ACK to the UE. In response to transmitting the first transmission, or after transmitting the first transmission, the UE may receive an ACK from the NW / reader. In response to receiving, recognizing, and / or decoding the ACK, the UE may transmit a second transmission to the NW / reader. In response to receiving / detecting / decoding the second transmission, the NW / reader may transmit a subsequent R2D transmission to the UE, for example, if there is a subsequent R2D and / or D2R transmission. In response to transmitting the second transmission, or after transmitting the second transmission, the UE may or may not receive a subsequent R2D transmission from the NW / reader. In response to receiving the subsequent R2D transmission, the UE may transmit a third transmission to the NW / reader.

[0516] like Figure 10As shown, in response to receiving the first signaling, the UE may transmit a second transmission to the NW / reader, for example, based on a second condition. In response to receiving / detecting / decoding the second transmission, the NW / reader may transmit a subsequent R2D transmission to the UE, for example, if there is a subsequent R2D and / or D2R transmission. In response to or after transmitting the second transmission, the UE may or may not receive a subsequent R2D transmission from the NW / reader. In response to receiving the subsequent R2D transmission, the UE may transmit a third transmission to the NW / reader.

[0517] The first condition may differ (partially or completely) from the second condition.

[0518] In response to receiving the first signaling, the UE may determine to perform the first transmission based at least on whether the first condition is satisfied. In response to receiving the first signaling, the UE may determine to perform the second transmission based at least on whether the second condition is satisfied.

[0519] Alternatively, in some embodiments, the second condition may be the same as the first condition.

[0520] In response to receiving the first signaling, the UE may determine to perform the first transmission based at least on satisfying the first condition, and the UE may determine to perform the second transmission based at least on not satisfying the first condition.

[0521] The first condition may be one or more of the following:

[0522] - the first signaling includes an indication (e.g., (full) UE ID);

[0523] - performing a first procedure for the UE at a first time (e.g., after the UE is powered on or becomes active);

[0524] - the UE has not yet performed the first procedure (e.g., after the UE is powered on or becomes active);

[0525] - receiving a first signaling at a first time (e.g., after the UE is powered on or becomes active);

[0526] - the UE powers on or becomes active, for example in response to the first signaling;

[0527] - the first transmission has not yet been transmitted to the NW (e.g. after the UE is powered on or becomes active);

[0528] - the UE ID has not yet been transmitted to the NW / reader (e.g. after the UE is powered on or becomes active);

[0529] - the ACK (for the first transmission) has not yet been received and / or decoded by the UE (e.g., after the UE is powered on or becomes active);

[0530] - the last first procedure, the last first transmission or the last reception of an ACK (for a first transmission) has expired;

[0531] - the duration between the current time and the execution of the last first procedure, the last first transmission or the last reception of an ACK (for a first transmission) is higher than a threshold;

[0532] - the timer is not running or has expired; and / or

[0533] - The (last) first program or the (last) first transmission is invalid (or not valid).

[0534] The second condition can be one or more of the following:

[0535] - the first signaling includes an indication (e.g., (full) UE ID);

[0536] - not executing the first procedure for the UE at a first time (e.g., after the UE is powered on or becomes active);

[0537] - the UE has performed the first procedure (e.g., after the UE is powered on or becomes active);

[0538] - the first signaling is not received at a first time (e.g., after the UE is powered on or becomes active);

[0539] - the first transmission has been transmitted to the NW / reader (e.g. after the UE is powered on or becomes active);

[0540] - the UE ID has been transmitted to the NW / reader (e.g. after the UE is powered on or becomes active);

[0541] - the ACK (for the first transmission) has been received and / or decoded by the UE (e.g., during execution of a / a previous first procedure and / or after the UE is powered on or becomes active);

[0542] - the last first procedure, the last first transmission or the last reception of an ACK (for a first transmission) has been retained and / or is not outdated;

[0543] - the duration between the current time and the execution of the last first procedure, the last first transmission or the last reception of an ACK (for a first transmission) is not higher than a threshold;

[0544] - the timer is running or has not expired; and / or

[0545] - The (last) first program or the (last) first transfer is valid.

[0546] The threshold value may be configured / indicated by the NW / reader or derived / determined by the UE. The threshold value may be fixed or predefined. The threshold value may be a time offset or a duration.

[0547] The timer may be associated with the first procedure. The timer may be a validity timer. The timer may be a prohibit timer. The timer may be started in response to performing the first transfer. The timer may be started in response to receiving an ACK for the first transfer. The timer may be started in response to triggering the first procedure.

[0548] Preferably, in some embodiments, the D2R transmission carrying the first information may be any one of the first transmission, the second transmission, the third transmission and / or the subsequent D2R transmission.

[0549] In one or more examples, a UE / device may receive first signaling (e.g., paging) from a NW / reader. The first signaling may instruct the UE / device to trigger a first procedure (e.g., a random access procedure). In response to receiving the first signaling, the UE may trigger the first procedure. In response to receiving the first signaling, the UE may transmit a first transmission to the NW / reader, for example, during the first procedure. The UE may provide first information (e.g., energy information) in the first transmission. If (at least) the UE's remaining energy is sufficient, for example, to receive a response to the first transmission and / or transmit a second transmission, the first information may indicate a first value. If (at least) the UE's remaining energy is insufficient, for example, to receive a response to the first transmission and / or transmit the second transmission, the first information may indicate a second value. If (at least) the UE's remaining energy is sufficient, for example, to receive a response to the first transmission and / or transmit the second transmission, the UE may not provide the first information. If (at least) the UE's remaining energy is insufficient, for example, to receive a response to the first transmission and / or transmit the second transmission, the UE may provide the first information. In response to providing the first information, the UE may stop or pause the first procedure. The UE may not stop or suspend the first procedure in response to providing the first information.The UE may stop the first procedure in response to the first information indicating the second value.

[0550] In one or more examples, a UE / device may receive first signaling (e.g., paging) from a NW / reader. The first signaling may instruct the UE / device to trigger a first procedure (e.g., a random access procedure). In response to receiving the first signaling, the UE may trigger the first procedure. In response to receiving the first signaling, the UE may transmit a first transmission to the NW / reader, for example, during the first procedure. In response to receiving / detecting / decoding the first transmission, the NW / reader may transmit a response to the UE. In response to or after transmitting the first transmission, the UE may receive a response to the first transmission from the NW / reader. In response to receiving the response to the first transmission, recognizing the response to the first transmission, and / or decoding the response to the first transmission, the UE may transmit a second transmission to the NW / reader. The UE may provide first information (e.g., energy information) in the second transmission. The first information may indicate a first value if (at least) the UE's remaining energy is sufficient, for example, to receive a response to the second transmission and / or transmit a third transmission. If (at least) the remaining energy of the UE is insufficient, for example, to receive a response to the second transmission and / or transmit the third transmission, the first information may indicate the second value. If (at least) the remaining energy of the UE is sufficient, for example, to receive a response to the second transmission and / or transmit the third transmission, the UE may not provide the first information. If (at least) the remaining energy of the UE is insufficient, for example, to receive a response to the second transmission and / or transmit the third transmission, the UE may provide the first information. The UE may stop or suspend the first procedure in response to providing the first information. The UE may not stop or suspend the first procedure in response to providing the first information. The UE may stop the first procedure in response to the first information indicating the second value.

[0551] In one or more examples, a UE / device may receive first signaling (e.g., paging) from a NW / reader. The first signaling may instruct the UE / device to trigger a first procedure (e.g., a random access procedure). In response to receiving the first signaling, the UE may trigger the first procedure. In response to receiving the first signaling, the UE may transmit a first transmission to the NW / reader, for example, during the first procedure. In response to receiving / detecting / decoding the first transmission, the NW / reader may transmit a response to the UE. In response to transmitting the first transmission, or after transmitting the first transmission, the UE may receive a response to the first transmission from the NW / reader. In response to receiving the response to the first transmission, recognizing the response to the first transmission, and / or decoding the response to the first transmission, the UE may transmit a second transmission to the NW / reader. In response to receiving / detecting / decoding the second transmission, the NW / reader may transmit a subsequent R2D transmission (e.g., a response to the second transmission) to the UE, for example, if a subsequent R2D and / or D2R transmission exists (is available). In response to or after transmitting the second transmission, the UE may or may not receive a subsequent R2D transmission from the NW / reader. In response to receiving the subsequent R2D transmission, the UE may transmit a third transmission to the NW / reader. The UE may provide first information (e.g., energy information) in the third transmission. If (at least) the UE's remaining energy is sufficient, for example, to receive a response to the third transmission and / or transmit a fourth transmission, the first information may indicate a first value. If (at least) the UE's remaining energy is insufficient, for example, to receive a response to the third transmission and / or transmit a fourth transmission, the first information may indicate a second value. If (at least) the UE's remaining energy is sufficient, for example, to receive a response to the third transmission and / or transmit a fourth transmission, the UE may not provide the first information. If (at least) the UE's remaining energy is insufficient, for example, to receive a response to the third transmission and / or transmit a fourth transmission, the UE may provide the first information. The UE may stop or suspend the first procedure in response to providing the first information. The UE may not stop or suspend the first procedure in response to providing the first information. The UE may stop the first procedure in response to the first information indicating the second value.

[0552] Throughout this disclosure, a subsequent (D2R / R2D) transfer may at least be and / or include, for example, a subsequent (D2R / R2D) transfer after a first transfer.The first transfer may be a D2R transfer during a first procedure.

[0553] Based on the indication / information in the first signaling, there may be one or more subsequent (D2R / R2D) transmissions.Based on the arrival of data at the device / reader, there may be one or more subsequent (D2R / R2D) transmissions.

[0554] The first transmission may be / include information of a random number, information of a preamble number, and / or information of an (access) ID selected / generated / determined by the UE.

[0555] The ACK may be an (initial) response to the first transmission. The ACK may indicate, identify and / or correspond to the first transmission. The ACK may provide and / or indicate resources for subsequent D2R transmissions, such as the second transmission and / or the third transmission.

[0556] The second transmission may be / include information of a device / UE ID, a report, assistance information, D2R data and / or information from the UE.

[0557] The subsequent R2D transmission may be a response, (R2D) command, R2D data, and / or schedule to the second transmission. The subsequent R2D transmission may indicate, identify, and / or correspond to the second transmission. The subsequent R2D transmission may provide resources for a subsequent D2R transmission, such as a third transmission. The subsequent R2D transmission may indicate, notify, and / or allow the third transmission.

[0558] The third transmission may be / include feedback (of a subsequent R2D transmission), a report, assistance information, D2R data, and / or information from the UE.

[0559] The first transmission, the second transmission, and the third transmission may be D2R transmissions and / or PDRCH transmissions. The third transmission may be a subsequent D2R transmission. The first signaling, ACK, and subsequent R2D transmissions may be R2D transmissions and / or PRDCH transmissions. The first signaling and ACK may be broadcast, provided, and / or transmitted to one or more UEs. The ACK and subsequent R2D may be provided and / or transmitted to a dedicated UE. During and / or after the first procedure, one or more subsequent R2D transmissions and / or subsequent D2R transmissions may occur.

[0560] The UE may transmit the first information via the first transmission, the second transmission, and / or the third transmission. The first information may be carried by the first transmission, the second transmission, and / or the third transmission. The UE may not transmit the first information via the first transmission. The first information may not be carried by the first transmission. The UE may monitor the PDRCH based on the first information. The NW may schedule and / or perform an ACK, a second transmission, a subsequent R2D transmission, and / or a third transmission based on the first information. The NW may transmit R2D transmission and / or scheduling to the UE based on the first information.

[0561] The UE may determine to transmit the first information (e.g., in the first procedure) based on (at least) satisfying the second condition. The second condition may be one or more of the following:

[0562] - a status of the first information (e.g., a specific status / type / value of the first information) is derived by the UE and / or indicated by the NW (e.g., via first signaling);

[0563] - whether the first information is available;

[0564] - whether the remaining energy / power is insufficient to complete a procedure (e.g., a first procedure), receive an R2D transmission / response, and / or transmit the remaining / available data;

[0565] - whether the (expected) power level is or will be below a power level threshold;

[0566] - Whether the available (remaining) data size is greater than the threshold value of TBS (as described below);

[0567] - whether the (required) processing time is or will be above a time threshold (as described below);

[0568] - whether the UE is expected to sleep, e.g. before completing the remaining transmission and / or the first procedure;

[0569] - Whether the UE has not received an R2D transmission at or before the timing of T1, T3, Ta and / or Tc; and / or

[0570] - Whether the (required) time for energy / power accumulation for the next reception, transmission or listening is greater than the (required) processing time or a time threshold.

[0571] T1 and T3 (e.g., in Figure 9 or Figure 10 T2 and T4 (e.g., in Figure 9 or Figure 10 (in) may be the (expected or prohibited or delayed) time interval between two (consecutive) D2R transmissions. Ta to Tc (e.g., in Figure 9 or Figure 10 (in) may be the (expected / required / minimum) time interval for receiving the (corresponding) R2D transmission (e.g., after performing the D2R transmission). Tb to Td (e.g., in Figure 9 or Figure 10 (in) may be the (expected / required / minimum) time interval for transmitting the (corresponding) R2D transmission (eg, after performing the D2R transmission).

[0572] T1 may be the duration between the first transmission and (the expected, prohibited, or delayed arrival time of) the ACK. T1 may indicate the expected, prohibited, or delayed arrival time of the ACK for the first transmission. The UE may begin or expect to receive the ACK after / at the time the first transmission (ends) plus T1. The UE may (begin) monitoring the PRDCH after / at the time the first transmission (ends) plus T1.

[0573] T2 may be the duration between the first transmission and (the expected, prohibited, or delayed transmission time of) the second transmission. T2 may indicate the expected, prohibited, or delayed transmission time of the second transmission. The UE may begin or expect to transmit the second transmission after / at the time that the first transmission (ends) is added to T2. The UE may receive a schedule for the second transmission, wherein the schedule indicates PDRCH resources after / at the time that the first transmission (ends) is added to T2.

[0574] T3 may be the duration between the second transmission and (the expected, prohibited, or delayed arrival time of) the subsequent R2D transmission. T3 may indicate the expected, prohibited, or delayed arrival time of the subsequent R2D transmission. The UE may begin or expect to receive the subsequent R2D transmission after / at the time T3 is added to (the end of) the second transmission. The UE may (begin) monitoring the PRDCH after / at the time T3 is added to (the end of) the first transmission.

[0575] T4 may be the duration between the second transmission and (the expected, prohibited, or delayed transmission time of) the third transmission. T4 may indicate the expected, prohibited, or delayed transmission time of the third transmission. The UE may begin or expect to transmit the third transmission after / at the time that the second transmission (ends) is added to T4. The UE may receive a schedule for the third transmission, wherein the schedule indicates PDRCH resources after / at the time that the second transmission (ends) is added to T4.

[0576] Ta may be the duration when the UE expects to receive an ACK. Ta may indicate the expected arrival time of the ACK for the first transmission. The UE may monitor the PRDCH during the duration of Ta.

[0577] Tb may be a duration when the UE expects to transmit the second transmission. Tb may indicate an expected transmission time of the second transmission. The UE may receive a schedule for the second transmission, wherein the schedule indicates PDRCH resources during the duration of Tb.

[0578] Tb may be the duration when the UE expects to receive the subsequent R2D transmission. Tc may indicate the expected arrival time of the subsequent R2D transmission. The UE may monitor the PRDCH during the duration of Tc.

[0579] Td may be a duration when the UE expects to transmit the third transmission. Td may indicate an expected transmission time of the third transmission. The UE may receive a schedule for the third transmission, wherein the schedule indicates PDRCH resources during a duration of Td.

[0580] If at least the third condition is met, the UE may, for example, determine to suspend, delay, stop, terminate, or pause the first procedure based on the third condition. If at least the third condition is met, the UE may, for example, transmit a request to suspend, stop, terminate, or pause the first procedure based on the third condition (e.g., to the NW or to the reader). The third condition may be (or include or relate to) whether the remaining / available energy / power is insufficient to complete the procedure, receive the R2D transmission / response, and / or transmit the remaining / pending / available data. The third condition may be (or include or relate to) the first information and / or processing time. If at least the third condition is not met, the UE may, for example, determine to resume the first procedure based on the third condition. If at least the third condition is met, the UE may, for example, transmit a request to resume the first procedure based on the third condition (e.g., to the NW or to the reader).

[0581] In one example, if the (expected) remaining / available energy / power is or will be insufficient to perform the remaining transmissions (e.g., the second transmission, the third transmission, the subsequent R2D / D2R transmission), the UE may stop, terminate, or suspend the first procedure. If the (expected) remaining / available energy / power is or will be sufficient to perform the remaining transmissions (e.g., the second transmission, the third transmission, the subsequent R2D / D2R transmission), the UE may resume the first procedure.

[0582] In one example, if the (expected / available) power level is or will be below a power level threshold, the UE may stop, terminate, or suspend the first procedure (as described above). If the (expected / available) power level is or will be above (or equal to) the power level threshold, the UE may resume the first procedure (as described above).

[0583] In one example, if the available / pending (remaining) data size is greater than a threshold value for the TBS, the UE may stop, terminate, or suspend the first procedure. The threshold value may be determined or associated with a power level. The threshold value may be configured / indicated by the network or derived / determined by the UE. The threshold value may be fixed or predefined.

[0584] In one example, if the (expected / required) processing time is or will be above a time threshold, the UE may stop, terminate, or suspend the first procedure. The threshold may be determined or associated with a power level. The threshold may be configured / indicated by the network or derived / determined by the UE. The threshold may be fixed or predefined.

[0585] In one example, if the UE is expected to sleep, for example, before completing the remaining transmissions (e.g., the second transmission, the third transmission, the subsequent R2D / D2R transmission) and / or the first procedure, the UE may stop, terminate, or suspend the first procedure. If the UE is expected to wake up, the UE may resume the first procedure.

[0586] In one example, if the UE does not receive an R2D transmission at or before the timing indicated by T1, T3, Ta, and / or Tc, the UE may stop, terminate, or suspend the first procedure.

[0587] In one example, if a specific status / type / value of the first information is indicated by the NW, such as via query, paging, and / or PRDCH, the UE may stop, terminate, or suspend the first procedure.

[0588] When or in response to stopping, terminating, or pausing the first procedure, the UE may transmit the first information and / or the second information to the NW / reader. The UE may transmit the first information and / or the second information before stopping, terminating, or pausing the first procedure. For example, the UE may determine to stop, terminate, or suspend the first procedure. In response to the determination, the UE may transmit the first information and / or the second information via D2R transmission, for example, during the first procedure. In response to the transmission of the first information and / or the second information, the UE may stop, terminate, or suspend the first procedure. In the request to stop, terminate, or suspend the first procedure, the UE may transmit the first information and / or the second information to the NW / reader.

[0589] The second information may include at least one of the following:

[0590] - pending data available (or not);

[0591] - the reason / cause for stopping or suspending the first procedure;

[0592] - the reason / causes for delaying or suspending the first proceeding;

[0593] - need to (later) query / paging again (or not);

[0594] - whether the first procedure needs to be executed again (later) (or not);

[0595] - the recommended / preferred / expected / required waiting time before performing the first procedure again; and / or

[0596] - The recommended / preferred / expected / required wait time before being queried / paged again.

[0597] Any of the methods, alternatives, concepts, examples and embodiments above and herein may be combined in whole or in part, or applied simultaneously or individually.

[0598] Throughout this disclosure, the following are used interchangeably: DL and / or R2D. An R2D transmission may be a transmission from a reader to a device. R2D data may be (available) data on the reader side and / or data to be transmitted from the reader to the device. R2D transmissions and / or R2D data may include instructions, configurations, signaling, and / or messages from the reader. An R2D reception may be the receipt of an R2D transmission.

[0599] Throughout this disclosure, the following may be used interchangeably: UL and / or D2R. A D2R transmission may be a transmission from a device to a reader. D2R data may be (available) data on the device side and / or data to be transmitted from the device to the reader. D2R transmissions and / or D2R data may include instructions, signaling, and / or messages from the device. D2R resources and / or PDRCH resources may be or include UL grants and / or resources provided from a reader / NW / intermediate node, used by a device / UE, and / or used to transmit / perform D2R transmissions.

[0600] Throughout this disclosure, a reader may be and / or be replaced by a network network (NW), a user equipment terminal (UE), and / or an intermediate node. Throughout this disclosure, a device may be and / or be replaced by a user equipment terminal (UE) and / or an intermediate node. A device may be referred to as an ambient IoT device. A "UE" may include a reader and / or a device. A "NW" may include a reader. A UE / device may receive a carrier wave from a reader. A UE / device may receive a carrier wave from a node other than a reader.

[0601] Throughout this disclosure, the following are used interchangeably: RA, access, initial access, and / or (ambient IoT) transmission. Resources and / or configurations for the access procedure may include, for example, PDRCH resources, PDRCH timing, frequency, and / or frequency band for D2R transmission. Resources and / or configurations for the access procedure may include, for example, parameters, random numbers, group numbers, and / or auxiliary information for D2R transmission.

[0602] Throughout this disclosure, the following may be used interchangeably: Physical Random Access Channel (PRACH), Random Access Channel (RACH), Physical Uplink Shared Channel (PUSCH), Physical Uplink Control Channel (PUCCH), and / or PDRCH. The PDRCH may be or be referred to as a channel used for transmissions from a device to a reader. The PDRCH may be or be referred to as a (physical) channel for ambient IoT. The PDRCH may be or be referred to as a (physical) channel used for D2R (data / control) transmissions. The PDRCH may include PRACH, RACH, PUSCH, and / or PUCCH. R2D transmissions may be transmitted via the PRDCH. Transmissions (data and / or signaling) from a reader to a device / UE may be transmitted via the PRDCH.

[0603] Throughout this disclosure, the following may be used interchangeably: Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), and / or PRDCH. PRDCH may be or be referred to as a channel used for transmission from a reader to a device. PRDCH may be or be referred to as a (physical) channel for ambient IoT. PRDCH may be or be referred to as a (physical) channel used for R2D (data / control) transmission. PRDCH may include PDSCH and / or PDCCH. D2R transmissions may be transmitted via PDRCH. Transmissions (data and / or signaling) from a device / UE to a reader may be transmitted via PDRCH.

[0604] The UE may receive a configuration related to the IoT environment. The UE may receive a configuration and / or resources for executing the first procedure. The resources and / or configuration may include, for example, PDRCH (transmission) resources, time, channel resources, frequency resources, and / or (sub)band for D2R transmission. The resources and / or configuration may include, for example, parameters, random numbers, group numbers, and / or auxiliary information for D2R transmission. The UE may monitor / receive the PRDCH in the first procedure.

[0605] Throughout this disclosure, time information may include a duration value, a value / indication of a (start) timing (e.g., Universal Time Coordinated (UTC) time, TTI), a time offset (e.g., for transmission), and / or an indication / index of a time / duration level / state. The time information may be related to the first information, processing delay / time, energy / power accumulation, data type / size, wake-up time, sleep time, PRDCH monitoring, R2D reception, D2R transmission, and / or a configuration / indication provided by the NW. The time information may be an expected, preferred, required, or recommended time calculated by the UE based on power / energy and / or processing time.

[0606] Throughout this disclosure, a schedule may be one or more PDRCH resources for D2R transmission and / or one or more PRDCH resources for R2D reception. The schedule may be (an indication of) timing and / or frequency.

[0607] Throughout this disclosure, the following are used interchangeably: recommended, preferred, expected, desired, and / or estimated.

[0608] Throughout this disclosure, the following are used interchangeably: "initiator," "executor," "trigger," and / or "executor."

[0609] Throughout this disclosure, “BWP” may be replaced with “system bandwidth,” “channel bandwidth,” “transmission bandwidth,” “occupied bandwidth,” “sub-band of / in a cell,” “frequency (resource),” “frequency band,” and / or “a subset of the total cell bandwidth of a cell.”

[0610] Throughout this disclosure, “reader” may be / mean or be replaced by “network node” or “intermediate node.” The intermediate node may be a traditional UE.

[0611] Throughout this disclosure, “cell” may be replaced with “intermediate node”.

[0612] Throughout this disclosure, networks (nodes) may be changed / represented / replaced with intermediate nodes.

[0613] Throughout this disclosure, “downlink control information” may be replaced with R2D control information.

[0614] Throughout this disclosure, “uplink control information” may be replaced with D2R control information.

[0615] Throughout this disclosure, downlink control information may be transmitted via PRDCH or R2D commands.

[0616] Throughout this disclosure, a TTI / time instant may be a (time) instant, a symbol, a set of symbols, a time slot, a set of time slots, and / or a subframe.

[0617] Throughout this disclosure, "transmission" may be replaced with "message."

[0618] UE may be referred to as UE, RRC layer of UE, MAC entity of UE, or physical layer of UE.

[0619] Throughout this disclosure, a UE may be a device for ambient IoT. A UE may be a device with ambient IoT capabilities. A UE may be a NR device. A UE may be a Long Term Evolution (LTE) device. A UE may be an IoT device. A UE may be a wearable device. A UE may be a sensor. A UE may be a fixed device. A UE may be a tag. Throughout this disclosure, the following are interchangeable: (ambient IoT) UE, (ambient IoT) device. Throughout this disclosure, the following are interchangeable: ordinary UE, traditional UE.

[0620] The UE may not be a legacy UE. A legacy UE may be a non-ambient IoT device. A legacy UE may execute different programs than an ambient IoT UE. The UE may be a legacy UE capable of executing ambient IoT programs. A legacy UE may be a NR UE.

[0621] The network may be a network node. The network (node) may be a base station. The network (node) may be an access point. The network (node) may be an evolved Node B (eNB). The network (node) may be a next-generation Node B (gNB). The network (node) may be a gateway.

[0622] Various examples and embodiments of the present invention are described below.With respect to the methods, alternatives, concepts, examples and embodiments described above and in detail herein, the following aspects and embodiments are possible.

[0623] See Figure 11 , through this and other concepts, systems and methods of the present invention, a method 1000 for a UE in a wireless communication system includes: receiving first signaling from a network (step 1002); initiating a first procedure in response to receiving the first signaling (step 1004); transmitting a first transmission to the network (step 1006); receiving a response corresponding to the first transmission from the network (step 1008); generating and / or transmitting first information based on at least a conditional determination (step 1010); and transmitting a second transmission including the first information to the network (step 1012).

[0624] In various embodiments, the first signaling is a broadcast message, query and / or paging to the ambient IoT.

[0625] In various embodiments, the first signaling instructs the UE to perform a first procedure.

[0626] In various embodiments, the first procedure is a (random) access procedure (for the ambient IoT), a transmission procedure (for the ambient IoT), an information exchange procedure (for the ambient IoT), a reporting procedure and / or a response procedure (for the ambient IoT).

[0627] In various embodiments, the first transmission includes an identification of the UE.

[0628] In various embodiments, the UE's identity is a random number generated by the UE.

[0629] In various embodiments, the response indicates the identity of the UE.

[0630] In various embodiments, the response is an acknowledgement that is specific to the UE.

[0631] In various embodiments, the condition is that the remaining energy / power of the UE is insufficient to complete the first procedure.

[0632] In various embodiments, the condition is that the remaining energy / power of the UE is insufficient to perform transmission and / or reception after the second transmission.

[0633] In various embodiments, the first information includes device identification, power information, energy status, time information, and / or data type.

[0634] In various embodiments, the UE is an ambient IoT device.

[0635] In various embodiments, the network is an ambient IoT reader, an intermediate node, a gNB and / or another UE.

[0636] In various embodiments, the other UE is a legacy UE.

[0637] Return to view Figure 3 and Figure 4 In one or more embodiments, from the perspective of a UE in a wireless communication system, apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. CPU 308 can execute program code 312 to: (i) receive first signaling from a network; (ii) initiate a first procedure in response to receiving the first signaling; (iii) transmit a first transmission to the network; (iv) receive a response corresponding to the first transmission from the network; (v) generate and / or transmit first information based on at least a conditional determination; and (vi) transmit a second transmission including the first information to the network. Furthermore, CPU 308 can execute program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

[0638] Return to view Figure 3 and Figure 4 In one or more embodiments, from the perspective of a network in a wireless communication system, apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. CPU 308 can execute program code 312 to: (i) transmit first signaling to a UE; (ii) receive the first transmission from the UE; (iii) transmit a response corresponding to the first transmission to the UE; and (iv) receive a second transmission including the first information from the UE. Furthermore, CPU 308 can execute program code 312 to perform all described actions, steps, and methods described above, below, or otherwise herein.

[0639] See Figure 12, through this and other concepts, systems and methods of the present invention, a method 1020 for a UE in a wireless communication system includes: receiving first signaling that triggers a random access procedure (step 1022); triggering the random access procedure in response to receiving the first signaling (step 1024); performing a first transmission during the random access procedure (step 1026); and providing energy information in the first transmission indicating at least one of the following: whether the UE's remaining energy is sufficient for one or more subsequent transmissions or receptions after the first transmission, the UE's remaining energy is insufficient for one or more subsequent transmissions or receptions after the first transmission, whether the UE's remaining energy is sufficient to complete the random access procedure, and / or the UE's remaining energy is insufficient to complete the random access procedure (step 1028).

[0640] In various embodiments, when the remaining energy of the UE is sufficient, the energy information indicates a first value, and when the remaining energy of the UE is insufficient, the energy information indicates a second value.

[0641] In various embodiments, when the remaining energy of the UE is sufficient, energy information is not provided in the first transmission (or the first transmission does not provide or includes energy information), and when the remaining energy of the UE is insufficient, energy information is provided in the first transmission (or the first transmission provides or includes energy information).

[0642] In various embodiments, the energy information is one bit.

[0643] In various embodiments, energy information means power information.

[0644] In various embodiments, the energy information is the power state of the UE or the energy state of the UE.

[0645] In various embodiments, the method further comprises stopping or pausing the random access procedure in response to providing the energy information (indicating that the remaining energy of the UE is insufficient).

[0646] In various embodiments, the first transmission is a D2R transmission during a random access procedure.

[0647] In various embodiments, the one or more subsequent transmissions or receptions include performing (at least) a D2R transmission and / or receiving (at least) an R2D transmission during a random access procedure.

[0648] In various embodiments, the UE performs the first transmission in response to receiving the first signaling.

[0649] In various embodiments, the first signaling is a paging for the ambient IoT.

[0650] In various embodiments, the first signaling is used to include more than one UE, and / or the first signaling at least indicates more than one UE.

[0651] In various embodiments, the first signaling is received from a reader and / or the first transmission is transmitted to a reader, and wherein the reader is a network or another UE.

[0652] In various embodiments, the UE is an ambient IoT device.

[0653] In various embodiments, the other UE is a legacy UE.

[0654] Return to view Figure 3 and Figure 4 In one or more embodiments, from the perspective of a UE in a wireless communication system, the apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 can execute the program code 312 to: (i) receive first signaling that triggers a random access procedure; (ii) trigger the random access procedure in response to receiving the first signaling; (iii) perform a first transmission during the random access procedure; and (iv) provide energy information in the first transmission that indicates at least one of the following: whether the UE's remaining energy is sufficient for one or more subsequent transmissions or receptions after the first transmission, whether the UE's remaining energy is insufficient for one or more subsequent transmissions or receptions after the first transmission, whether the UE's remaining energy is sufficient to complete the random access procedure, and / or whether the UE's remaining energy is insufficient to complete the random access procedure. In addition, the CPU 308 can execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

[0655] Return to view Figure 3 and Figure 4 In one or more embodiments, from the perspective of a reader in a wireless communication system, the apparatus 300 includes program code 312 stored in a memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) transmit first signaling to a UE triggering a random access procedure; (ii) receive a first transmission from the UE during the random access procedure; and (iii) obtain energy information in the first transmission indicating at least one of the following: whether the UE's remaining energy is sufficient for one or more subsequent transmissions or receptions after the first transmission, whether the UE's remaining energy is insufficient for one or more subsequent transmissions or receptions after the first transmission, whether the UE's remaining energy is sufficient to complete the random access procedure, and / or whether the UE's remaining energy is insufficient to complete the random access procedure. In addition, the CPU 308 can execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or otherwise herein.

[0656] Any combination of the concepts or teachings above or herein can be combined or formed into new embodiments in whole or in part. The disclosed details and embodiments can be used to solve at least (but not limited to) the problems mentioned above and herein.

[0657] It should be noted that any of the methods, alternatives, steps, examples and embodiments presented herein may be applied independently, individually and / or in combination with multiple methods, alternatives, steps, examples and embodiments.

[0658] Various aspects of the present disclosure have been described above. It should be understood that the teachings herein can be implemented in a wide variety of forms, and any specific structure, functionality, or both disclosed herein are merely representative. Based on the teachings herein, those skilled in the art will appreciate that the aspects disclosed herein can be implemented independently of any other aspects, and that two or more of these aspects can be combined in various ways. For example, a device or method can be implemented using any number of the aspects described herein. Furthermore, the device or method can be implemented using other structures, functionality, or structures and functionality in addition to or different from one or more of the aspects described herein. As an example of some of the above concepts, in some aspects, parallel channels can be established based on pulse repetition frequency. In some aspects, parallel channels can be established based on pulse position or offset. In some aspects, parallel channels can be established based on a time hopping sequence. In some aspects, parallel channels can be established based on pulse repetition frequency, pulse position or offset, and a time hopping sequence.

[0659] Those skilled in the art will understand that information and signals 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 above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0660] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in connection with the various aspects disclosed herein can be implemented as electronic hardware (e.g., digital implementations, analog implementations, or a combination of the two, which can be designed using source decoding or some other technique), and various forms of programs or design code with instructions (which, for convenience, may be referred to herein as "software" or "software modules"), or a combination of the two. To clearly illustrate this interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in varying ways for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0661] Furthermore, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or performed by an integrated circuit ("IC"), an access terminal, or an access point. An IC may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute code or instructions residing within the IC, external to the IC, or both. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, for example, a DSP in combination with a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration.

[0662] It should be understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. It should be understood that based on design preferences, the specific order or hierarchy of steps in a process can be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order and are not meant to be limited to the specific order or hierarchy presented.

[0663] The steps of the methods or algorithms described in conjunction with the various aspects disclosed herein can be implemented directly in hardware, in software modules executed by a processor, or in a combination of the two. Software modules (e.g., containing executable instructions and associated data) and other data can reside in a data storage device, such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of computer-readable storage medium known in the art. An example storage medium can be coupled to a machine such as a computer / processor (for convenience, the machine may be referred to herein as a "processor") so that the processor can read information (e.g., code) from the storage medium and write information to the storage medium. An example storage medium can be integrated with the processor. The processor and storage medium can reside in an ASIC. The ASIC can reside in a user device. In an alternative, the processor and storage medium can reside in a user device as discrete components. In addition, in some aspects, any suitable computer program product may include a computer-readable medium that includes code related to one or more of the various aspects of the present disclosure. In some aspects, the computer program product may include packaging materials.

[0664] Although the present invention has been described in conjunction with various aspects and examples, it will be understood that the invention is capable of further modification. This application is intended to cover any variations, uses or adaptations of the invention that generally follow the principles of the invention and include such deviations from the present disclosure as come within the scope of known and customary practice in the art to which the invention pertains.

Claims

1. A method for providing user equipment with environmental IoT device information, characterized in that: include: receiving a first signaling triggering a random access procedure; triggering the random access procedure in response to receiving the first signaling; performing a first transmission during the random access procedure; as well as providing, in the first transmission, energy information indicative of at least one of: whether the remaining energy of the user equipment is sufficient for one or more subsequent transmissions or receptions after the first transmission; the remaining energy of the user equipment being insufficient for the one or more subsequent transmissions or receptions after the first transmission; whether the remaining energy of the user equipment is sufficient to complete the random access procedure; or The remaining energy of the user equipment is insufficient to complete the random access procedure.

2. The method according to claim 1, characterized in that When the remaining energy of the user equipment is sufficient, the energy information indicates a first value, and when the remaining energy of the user equipment is insufficient, the energy information indicates a second value.

3. The method according to claim 1, characterized in that When the remaining energy of the user equipment is sufficient, the energy information is not provided in the first transmission, and when the remaining energy of the user equipment is insufficient, the energy information is provided in the first transmission.

4. The method according to claim 1, wherein: The energy information is one bit or one digit, The energy information means power information, or The energy information is the power status of the user equipment or the energy status of the user equipment.

5. The method according to claim 1, characterized in that Further comprising stopping or pausing the random access procedure in response to providing the energy information indicating that the remaining energy of the user equipment is insufficient.

6. The method according to claim 1, wherein The first transmission is a device-to-reader transmission during the random access procedure.

7. The method according to claim 1, characterized in that The one or more subsequent transmissions or receptions include at least performing a device-to-reader transmission or at least receiving a reader-to-device transmission during the random access procedure.

8. The method according to claim 1, characterized in that The user equipment performs the first transmission in response to receiving the first signaling.

9. The method according to claim 1, characterized in that The first signaling is a paging for the environmental Internet of Things, the first signaling is used for more than one user equipment including the user equipment, and the first signaling at least indicates the more than one user equipment, or the user equipment is an environmental Internet of Things device.

10. The method according to claim 1, characterized in that The first signaling is received from a reader, or the first transmission is transmitted to the reader, and wherein the reader is a network or another user equipment.

11. A user device for providing information about an environmental IoT device, characterized in that: include: Memory; as well as a processor operatively coupled to the memory, wherein the processor is configured to execute program code to: receiving a first signaling triggering a random access procedure; triggering the random access procedure in response to receiving the first signaling; performing a first transmission during the random access procedure; as well as providing, in the first transmission, energy information indicative of at least one of: whether the remaining energy of the user equipment is sufficient for one or more subsequent transmissions or receptions after the first transmission; the remaining energy of the user equipment being insufficient for the one or more subsequent transmissions or receptions after the first transmission; whether the remaining energy of the user equipment is sufficient to complete the random access procedure; or The remaining energy of the user equipment is insufficient to complete the random access procedure.

12. The user equipment according to claim 11, wherein: When the remaining energy of the user equipment is sufficient, the energy information indicates a first value, and when the remaining energy of the user equipment is insufficient, the energy information indicates a second value.

13. The user equipment according to claim 11, wherein: When the remaining energy of the user equipment is sufficient, the energy information is not provided in the first transmission, and when the remaining energy of the user equipment is insufficient, the energy information is provided in the first transmission.

14. The user equipment according to claim 11, wherein: The energy information is one bit or one digit, The energy information means power information, or The energy information is the power status of the user equipment or the energy status of the user equipment.

15. The user equipment according to claim 11, wherein: The processor is further configured to execute the program code to: in response to providing the energy information indicating that the remaining energy of the user equipment is insufficient, stop or pause the random access procedure.

16. The user equipment according to claim 11, wherein: The first transmission is a device-to-reader transmission during the random access procedure.

17. The user equipment according to claim 11, wherein: The one or more subsequent transmissions or receptions include at least performing a device-to-reader transmission or at least receiving a reader-to-device transmission during the random access procedure.

18. The user equipment according to claim 11, wherein: The user equipment performs the first transmission in response to receiving the first signaling.

19. The user equipment according to claim 11, wherein: The first signaling is a paging for the environmental Internet of Things, the first signaling is used for more than one user equipment including the user equipment, and the first signaling at least indicates the more than one user equipment, or the user equipment is an environmental Internet of Things device.

20. The user equipment according to claim 11, wherein: The first signaling is received from a reader, or the first transmission is transmitted to the reader, and wherein the reader is a network or another user equipment.

Images