Method and apparatus for channel listening in wireless communication system

Abstract

The invention provides a method, a system and equipment for channel monitoring in a wireless communication system. The method of user equipment comprises the following steps: receiving a first signaling for triggering a random access procedure; triggering a random access procedure in response to (received) the first signaling; transmitting the first transmission during the random access procedure; determining a third opportunity based at least on a first opportunity and the first time delay, wherein the first opportunity is an opportunity at which the first signaling ends; and in response to transmitting the first transmission, listening for the second transmission from the third opportunity.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims priority and the benefit of U.S. Provisional Patent Application No. 63 / 620,679, filed on Jan. 12, 2024, and U.S. Provisional Patent Application No. 63 / 563,235, filed on Mar. 8, 2024; each of the applications and disclosures listed and incorporated by reference herein are hereby incorporated by reference in their entirety. Field of the Invention

[0003] The present disclosure generally relates to wireless communication networks, and more particularly, to methods and apparatuses for channel monitoring in a wireless communication system. Background of the Invention

[0004] With the rapid growth in the demand for transmitting large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate using Internet Protocol (IP) packets. Such IP packet communication can provide IP-borne 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 above-mentioned IP-borne voice and multimedia services. Currently, the 3GPP standards organization is discussing new next-generation (e.g., 5G) radio technologies. Accordingly, changes to the current body of the 3GPP standards are currently being submitted and considered to evolve and complete the 3GPP standards. Summary of the Invention

[0006] Methods, systems, and apparatuses for channel monitoring in a wireless communication system are provided. An ambient Internet of Things (IoT) User Equipment (UE) can correctly perform initial access and reduce power consumption. Multiple ambient UEs can monitor a network response at a (common) start time determined based on trigger signaling, where the trigger signaling indicates that the multiple UEs trigger random access.

[0007] In various embodiments, a method of a UE in a wireless communication system includes: receiving first signaling that triggers a random access procedure; triggering the random access procedure in response to (receiving) the first signaling; transmitting a first transmission during the random access procedure; determining a third timing based at least on a first timing and a first time delay, wherein the first timing is the timing at which the first signaling ends; and listening for a second transmission starting from the third timing in response to transmitting the first transmission.

[0008] In various embodiments, a method of a UE in a wireless communication system includes: receiving first signaling that triggers a random access procedure; triggering the random access procedure in response to (receiving) the first signaling; transmitting a first transmission during the random access procedure; determining a third timing based at least on a second timing and a second time delay, wherein the second timing is the timing at which the first transmission ends and the second time delay is derived or calculated by the UE; and listening for a second transmission starting from the third timing in response to transmitting the first transmission.

[0009] In various embodiments, a method of a reader in a wireless communication system includes: transmitting first signaling for triggering one or more random access procedures for more than one UE; receiving at least one first transmission from at least one UE among the more than one UE in response to (transmitting) the first signaling; and transmitting at least one second transmission for at least one UE after or at a third timing in response to (receiving) the at least one first transmission, wherein the third timing is common to the more than one UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 FIGURES showing a wireless communication system according to an embodiment of the present invention.

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

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

[0013] Figure 4 is according to an embodiment of the present invention Figure 3 functional block diagram of the program code of

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

[0015] Figure 6 is in 3GPP TR 38.848 V18.0.0 Figure 4.2.1.2-1: Reproduction of Topology 2.

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

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

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

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

[0020] Figure 8 It is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-2: Reproduction of Fallback of CBRA with 2-step RA type.

[0021] Figure 9 It is an example diagram according to an embodiment of the present invention, showing that a UE can receive first signaling to trigger a random access procedure and transmit a first transmission (e.g., Msg1) in the random access procedure, and the UE can determine the start time (e.g., the third timing) for listening to a second transmission (e.g., Msg2) based on: the first timing of receiving the first signaling and the time delay, or the second timing of transmitting the first transmission and the time delay.

[0022] Figure 10 It is a flowchart of a method for a UE in a wireless communication system, the method including: initiating an RA procedure; transmitting a message containing the identification of the UE in the RA procedure; in response to transmitting the message, receiving a channel transmission; and determining that the RA procedure is successfully completed based on the channel transmission scrambled with the identification of the UE or the channel transmission indicating the identification of the UE.

[0023] Figure 11Flowchart of a method for a UE in a wireless communication system, the method comprising: initiating a RA procedure; transmitting a first message including an identifier of the UE in the RA procedure; in response to transmitting the first message, receiving a second message; and determining that the RA procedure is successfully completed based on the second message indicating the identifier of the UE.

[0024] Figure 12 Flowchart of a method for a UE in a wireless communication system, the method comprising: receiving signaling from the NW; in response to (receiving) the signaling, initiating a RA procedure; transmitting a first message; starting a first timer at a specific timing; while the first timer is running, listening to a channel; and in response to transmitting the first message, receiving a second message on the channel.

[0025] Figure 13 Flowchart of a method for a UE in a wireless communication system, the method comprising: receiving a first signaling triggering a random access procedure; in response to (receiving) the first signaling, triggering a random access procedure; transmitting a first transmission during the random access procedure; determining a third timing based at least on a first timing and a first time delay; and in response to transmitting the first transmission, starting to listen for a second transmission from the third timing.

[0026] Figure 14 Flowchart of a method for a UE in a wireless communication system, the method comprising: receiving a first signaling triggering a random access procedure; in response to (receiving) the first signaling, triggering a random access procedure; transmitting a first transmission during the random access procedure; determining a third timing based at least on a second timing and a second time delay; and in response to transmitting the first transmission, starting to listen for a second transmission from the third timing.

[0027] Figure 15 Flowchart of a method for a reader in a wireless communication system, the method comprising: transmitting a first signaling for triggering one or more random access procedures for more than one UE; in response to (transmitting) the first signaling, receiving at least one first transmission from at least one UE among the more than one UE; and in response to (receiving) the at least one first transmission, transmitting at least one second transmission for at least one UE after a third timing. Detailed Description

[0028] The present invention described herein can be applied to or implemented in the exemplary wireless communication systems and apparatuses described below. Additionally, the present invention is mainly described in the context of the 3GPP architecture reference model. However, it should be understood that, through the disclosed information, those skilled in the art can easily adapt to use and implement aspects of the present invention in 3GPP2 network architectures and other network architectures.

[0029] The exemplary wireless communication systems and devices described below use a wireless communication system that supports 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 technology.

[0030] Specifically, the exemplary wireless communication systems and devices described below can be designed to support one or more standards, such as those provided by an association named "Third Generation Partnership Project" and referred to herein as 3GPP, including: [1] RP-234058, "Study on solutions for Ambient Internet of Things (IoT) in NR"; [2] 3GPP TR38.848 V18.0.0 (2023-09) 3GPP; TSG RAN; Study on Ambient Internet of Things (IoT) in RAN (Release 18); [3] 3GPP TS 38.321 V17.6.0 (2023-09) 3GPP; TSG RAN; NR; MAC protocol specification (Release 17); [4] 3GPP TS 38.300 V17.6.0 (2023-09) 3GPP; TSG RAN; NR; General description of NR and NG-RAN (Release 17); and [5] 3GPP TS 38.213 V17.7.0 (2023-09) 3GPP; TSG RAN; NR; Physical layer procedures for control (Release 17). The standards and documents listed above are hereby expressly and fully incorporated herein by reference in their entirety.

[0031] Figure 1Shows a multi - access wireless communication system according to an embodiment of the present invention. The access network (AN) 100 includes a plurality of antenna groups, where one antenna group includes 104 and 106, another antenna group includes 108 and 110, and yet another antenna group includes 112 and 114. In Figure 1 , each antenna group shows only two antennas, however, each antenna group may utilize more or fewer antennas. The access terminal (AT) 116 communicates with antennas 112 and 114, where antennas 112 and 114 transmit information to the access terminal 116 via the forward link 120, and receive information from the AT 116 via the reverse link 118. The AT 122 communicates with antennas 106 and 108, where antennas 106 and 108 transmit information to the AT 122 via the forward link 126, and receive information from the AT 122 via the reverse link 124. In an FDD system, the communication links 118, 120, 124, and 126 may communicate using different frequencies. For example, the forward link 120 may use a frequency different from the frequency used by the reverse link 118.

[0032] Each antenna group and / or the antenna groups are designed to communicate in an area which 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.

[0033] In the communication via the forward links 120 and 126, the transmitting antennas of the access network 100 may utilize beamforming to improve the signal - to - noise ratio of the forward links for different access terminals 116 and 122. Additionally, compared to the access network transmitting to all of its access terminals via a single antenna, the access network using beamforming to transmit to access terminals randomly dispersed in its coverage area causes less interference to the access terminals in adjacent cells.

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

[0035] 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 a 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.

[0036] In one embodiment, each data stream is transmitted via a respective transmit antenna. The TX data processor 214 formats, encodes, and interleaves the traffic data of the data stream based on a particular coding scheme selected for each data stream to provide encoded data.

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

[0038] Then, the modulated symbols of all data streams are provided to the TX MIMO processor 220, which may further process the modulated symbols (e.g., for OFDM). Then, the TX MIMO processor 220 provides N T streams of modulated symbols to N T transmitters (TMTRs) 222a through 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to the symbols of the data stream and to the antennas from which the symbols are being transmitted.

[0039] Each transmitter 222 receives and processes the respective symbol stream to provide one or more analog signals and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. Then, N T modulated signals from transmitters 222a through 222t are transmitted from N T antennas 224a through 224t.

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

[0041] Then, the RX data processor 260 receives N R from NR receives and processes N R received symbol streams to provide N T "detected" symbol streams. Then, the RX data processor 260 demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing performed by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[0042] The processor 270 periodically determines which precoding matrix (discussed below) to use. The processor 270 formulates a reverse link message that includes a matrix index portion and a rank value portion.

[0043] The reverse link message may include various types of information about the communication link and / or the received data streams. Then, the reverse link message is processed by the TX data processor 238, modulated by the modulator 280, conditioned by the transmitters 254a to 254r, and transmitted back to the transmitter system 210, and the TX data processor also receives the traffic data of several data streams from the data source 236.

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

[0045] The memory 232 can be used to temporarily store some buffered / calculated data from 240 or 242 through the processor 230, store some buffered data from 212, or store some specific program code. And, the memory 272 can be used to temporarily store some buffered / calculated data from 260 through the processor 270, store some buffered data from 236, or store some specific program code.

[0046] Steering Figure 3 , this figure shows an alternative simplified functional block diagram of a communication device according to an embodiment of the present invention. As Figure 3 shown, the communication device 300 in a wireless communication system can be used to implement Figure 1UEs (or ATs) 116 and 122 therein, 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, program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308 to control the operation of the communication device 300. The communication device 300 may receive signals input by a user through the input device 302 such as a keyboard or keypad, and may output images and sounds through the output device 304 such as a listener or speaker. The transceiver 314 is used to receive and transmit wireless signals, deliver the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306.

[0047] Figure 4 is according to an embodiment of the present invention Figure 3 is a simplified block diagram of the program code 312 shown in. In this embodiment, the 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. The layer 3 portion 402 generally performs radio resource control. The layer 2 portion 404 generally performs link control. The layer 1 portion 406 generally performs physical connection.

[0048] For an LTE, LTE-A, or NR system, the layer 2 portion 404 may include a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer. The layer 3 portion 402 may include a Radio Resource Control (RRC) layer.

[0049] Any two or more of the following paragraphs, (sub) bullet points, key points, actions, or technical solutions described in each invention may be logically, reasonably, and appropriately combined to form a specific method.

[0050] Any sentence, paragraph, (sub) bullet point, key point, action, or technical solution described in each of the following invention paragraphs or sections can be implemented independently and separately to form a specific method or device. The correlations such as "based on", "more specifically", "example" in the following disclosure of the present invention are only one possible embodiment that does not limit a specific method or device.

[0051] The research project on Ambient IoT has been approved at the 102nd RAN Plenary Meeting. It is specified in [1] RP-234058 as follows:

[0052] ************************Start of citation [1]*******************************

[0053] 3 Argumentation

[0054] In recent years, IoT has attracted a great deal of attention in the wireless communication world. It is expected that more 'things' will be interconnected to improve productivity efficiency and increase life comfort. Further reduction in the size, complexity, and power consumption of IoT devices could enable the deployment of tens of billions or even hundreds of billions of IoT devices for various applications and provide added value throughout the value chain. It is not possible to power all IoT devices with batteries that require manual replacement or recharging, which results in high maintenance costs, serious environmental problems, and even safety hazards for some use cases (e.g., wireless sensors in the power and oil industries).

[0055] Most existing wireless communication devices are powered by batteries that require manual replacement or recharging. The automation and digitization of various industries have opened up many new markets that require new IoT technologies to support battery-free devices without energy storage capabilities or devices with energy storage that do not require manual replacement or recharging. The form factor of such devices must be quite small to convey the effectiveness of the target use case.

[0056] TR 22.840 is being developed by SA1 to capture the use cases, business scenarios, device constraints of the Internet of Things that support ambient power, 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., use capacitors) and provide energy by collecting radio waves, light, motion, heat, or any other power source that may be considered appropriate.

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

[0058] An example type of application in TR 22.840 is asset identification, which currently mainly has to adopt barcodes and RFID in most industries. The main advantages of these two technologies are the ultra-low complexity and small form factor of the tags. However, the limited reading range of a few meters usually requires handheld scanning, which results in labor-intensive and time-consuming operations, or requires RFID portals / gates, which results in high deployment costs. In addition, the lack of interference management schemes leads to severe interference and capacity issues between RFID readers, especially in the case of dense deployments. It is difficult for RFID to support large-scale seamless coverage networks.

[0059] TSG RAN has completed Rel-18 RAN-level SI on environmental IoT, which provides a terminology and scope framework for future discussions on environmental IoT. This has defined representative use cases, deployment scenarios, connection topologies, environmental IoT devices, design goals, and required functionality; it has also conducted a preliminary feasibility assessment and proposed recommendations for down-selection when setting up another WG-level research scope.

[0060] Since the 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, where the number of connections and / or device density can be several orders of magnitude higher than existing 3GPP IoT technologies. The new IoT technologies should offer an order 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 be otherwise met based on existing 3GPP LPWA IoT technologies.

[0061] 4 Objectives

[0062] 4.1 Objectives of SI or Core Part WI or Test Part WI

[0063] The objective of this study is to further evaluate environmental IoT, a new 3GPP IoT technology, at the RAN WG level, which is suitable for deployment in the 3GPP system and relies on ultra-low complexity devices with ultra-low power consumption for extremely low-end IoT applications. The study should provide a clear differentiation, 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).

[0064] General Ranges

[0065] The definitions provided in TR 38.848 are incorporated into this SI, and the following is the exclusive general scope:

[0066] A. The overall objective should be to study a harmonized air interface design with minimized differences (if necessary) to enable the following devices for ambient IoT:

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

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

[0069] ● X will be decided in the WG.

[0070] ● Coverage design objective: According to TR 38.848: “… the range that the WG can select among its sub - …”, the maximum distance from the indoor device is 10 - 50 m.

[0071] ● 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 (i.e., at least no cell selection / re - selection - like functions), no HARQ, no ARQ.

[0072] Note 1: It should be understood that “≤ a few 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 “≤ a few hundred μW” requirement.

[0073] B. Referring to the table in clause 4.2.2 of TR 38.848, deployment scenarios with the following characteristics:

[0074] ● Deployment scenario 1 with topology 1

[0075] ○ Base station and co - existence characteristics: Micro - cell, co - located

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

[0077] ○ Base station and co - existence characteristics: Macro - cell, co - located

[0078] ○ The location of the intermediate node is indoors

[0079] C. FR1 licensed spectrum in FDD.

[0080] D. Spectrum deployments within the NR band, within the LTE / NR guard band, and within a stand-alone frequency band.

[0081] E. Service types DO-DTT, DT, with a focus on rUC1 (indoor inventory) and rUC4 (indoor command).

[0082] ● From RAN#104, the study will evaluate whether the coordinated air interface design (per the above bullet 'A') can address the DO-A (device-initiated autonomous) use case, solely to identify which part(s) of the coordinated air interface design (per the above bullet 'A') are insufficient for the DO-A use case.

[0083] Transmissions from environmental IoT devices (including backscattering when in use) can occur at least in the UL spectrum.

[0084] Set the following objectives within the general scope:

[0085] …

[0086] 1. Study the necessary and feasible solutions for environmental IoT as specified in the general scope, including decisions on which functions, procedures, etc. are needed and not needed, and at least ensure the functionality required in Section 6.2 of TR 38.848.

[0087] …

[0088] ● RAN1-led:

[0089] For environmental IoT DL and UL:

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

[0091] ○ Fundamental parameters, bandwidth, and multiple access

[0092] ○ Waveform and modulation

[0093] ○ Channel coding

[0094] ○ Downlink channel / signal aspects

[0095] ○ Uplink channel / signal aspects

[0096] ○ Scheduling and timing relationships

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

[0098] For topology 2, the physical layer design has no difference from topology 1.

[0099] ●RAN2-led:

[0100] ○Research and determine what functions are required for the environmental IoT compact protocol stack and lightweight signaling procedures to implement DO-DTT and DT data transfer, and study these functions.

[0101] For example:

[0102] ■Paging

[0103] ■Random access

[0104] ■Data transfer including necessary radio resource control aspects complies with restrictions within a general scope

[0105] **************************Quotation ends**********************************

[0106] A description of the environmental IoT (e.g., regarding topology and assumptions) can be found in [2] 3GPP TR 38.848 V18.0.0 (2023-09).

[0107] **************************Quotation starts [2]********************************

[0108] 4.2.1 Connection topology

[0109] 4.2.1.0 Introduction

[0110] For research purposes, the following connection topologies for environmental IoT networks and devices are defined. In all these topologies, carriers can be provided to environmental IoT devices from other nodes inside or outside the topology. The links in each topology can be bidirectional or unidirectional.

[0111] BS, UE, auxiliary nodes, or intermediate nodes can be multiple BSs or UEs respectively. A mixture of indoor and outdoor placement of such nodes is considered a network implementation option. The potential impact on device or node complexity needs to be considered. In the connection topology, this does not mean the existence of multi-hop auxiliary or intermediate nodes.

[0112] 4.2.1.1

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

[0114] In Topology 1, the ambient IoT device communicates directly and bidirectionally with the base station. The communication between the base station and the ambient IoT device includes ambient IoT data and / or signaling. This topology includes the possibility that the BS for transmitting to the ambient IoT device is different from the BS for receiving from the ambient IoT device.

[0115] 4.2.1.2

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

[0117] In Topology 2, the ambient IoT device communicates bidirectionally with an intermediate node between the device and the base station. In this topology, the intermediate node can be a relay with ambient IoT capabilities, an IAB node, a UE, a repeater, etc. The intermediate node transmits ambient IoT data and / or signaling between the BS and the ambient IoT device.

[0118] *******************************Next citation*****************************

[0119] 4.3 Device Classification

[0120] Ambient IoT devices are characterized in the study according to their energy storage capacity and the ability to generate RF signals for their transmission.

[0121] The study assumes that the device has any of the following:

[0122] - No energy storage at all; or

[0123] - Limited energy storage

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

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

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

[0127] - Device C: Has energy storage, has independent signal generation, i.e., active RF components for transmission.

[0128] The limited energy storage can be different between an implementation within Device B and an implementation within Device C, and can be different between Device B and Device C. Such storage is expected to be several orders of magnitude smaller than the storage typically included in NB-IoT devices.

[0129] ********************************Quotation ended*****************************

[0130] The current random access (RA) procedure handling is specified in [3] 3GPP TS 38.321 V17.6.0 (2023-09). The (current) RA procedure will be executed by legacy UEs. The ambient IoT UE will execute (a part of) the current RA procedure.

[0131] ********************************Quotation started [3]**************************

[0132] 5.1 Random access procedure

[0133] 5.1.1 Random access procedure initialization

[0134] According to TS 38.300 [4], the random access procedure described in this clause is initiated by a PDCCH command, the MAC entity itself, or RRC for an event. In the MAC entity, there is only one ongoing random access procedure at any point in time. The random access procedure on an SCell will only be initiated by a PDCCH command where ra-PreambleIndex is different from 0b000000.

[0135] When initiating a random access procedure, the UE selects a random access resource set as specified in clause 5.1.1b and initializes the following parameters for the random access procedure according to the values configured by RRC for the selected random access resource set:

[0136] - prach-ConfigurationIndex: The set of available PRACH occasions for transmitting the random access preamble for Msg1. If the PRACH occasions are shared between 2-step RA type and 4-step RA type, these also apply to MSGA PRACH;

[0137] …

[0138] - msgA-prach-ConfigurationIndex: The set of available PRACH occasions for transmitting MSGA in 2-step RA type;

[0139] …

[0140] -ra-PreambleIndex: Random access preamble;

[0141] -ra-ssb-OccasionMaskIndex: Defines the PRACH occasions associated with the SSB where the MAC entity can transmit a random access preamble (see clause 7.4);

[0142] -msgA-SSB-SharedRO-MaskIndex: Indicates the subset of 4-step RA type PRACH occasions shared with the 2-step RA type PRACH occasions for each SSB. If the 2-step RA type PRACH occasions are shared with the 4-step RA type PRACH occasions and msgA-SSB-SharedRO-MaskIndex is not configured, then all 4-step RA type PRACH occasions can be used for the 2-step RA type (see clause 7.4);

[0143] -ssb-SharedRO-MaskIndex: Defines the PRACH occasions associated with the SSB where the MAC entity can transmit a random access preamble, at which preambles are allocated for a feature or combination of features (see clause 7.4);

[0144] -ra-OccasionList: Defines the PRACH occasions associated with CSI-RS where the MAC entity can transmit a random access preamble;

[0145] -ra-PreambleStartIndex: The starting index of the random access preamble for on-demand SI requests;

[0146] -startPreambleForThisPartition: The first preamble associated with the set of random access resources applicable to the random access procedure;

[0147] -preambleTransMax: The maximum number of random access preamble transmissions;

[0148] …

[0149] - Set of random access preambles and / or PRACH occasions for SI requests (if any);

[0150] - Set of random access preambles and / or PRACH occasions for beam failure recovery requests (if any);

[0151] - Set of random access preambles and / or PRACH occasions for synchronization reconfiguration (if any);

[0152] -ra-ResponseWindow: The time window for listening for RA responses (for SpCell only);

[0153] -ra-ContentionResolutionTimer: The contention resolution timer (for SpCell only);

[0154] -msgB-ResponseWindow: The time window for listening for RA responses of 2-step RA type (for SpCell only). ...

[0156] When initiating a random access procedure on the serving cell, the MAC entity shall:

[0157] …

[0158] 1> Select the set of random access resources applicable to the current random access procedure according to clause 5.1.1b;

[0159] 1> If the random access procedure is initiated by a PDCCH command and if the ra-PreambleIndex explicitly provided by the PDCCH is not 0b000000; or

[0160] 1> If the random access procedure is initiated for an SI request (as specified in TS 38.331) and the random access resources for the SI request have been explicitly provided by RRC; or

[0161] 1> If the random access procedure is initiated for beam failure recovery (as specified in clause 5.17) and the contention-free random access resources for the beam failure recovery request of 4-step RA type have been explicitly provided by RRC for the BWP selected for the random access procedure; or

[0162] 1> If the random access procedure is initiated for synchronous reconfiguration and the contention-free random access resources for 4-step RA type have been explicitly provided in rach-ConfigDedicated for the BWP selected for the random access procedure:

[0163] 2> Set RA_TYPE to 4-stepRA.

[0164] 1> Otherwise, if the BWP selected for the random access procedure is configured with 2-step and 4-step RA type random access resources within the selected set of random access resources (as specified in clause 5.1.1b) and the RSRP of the downlink path loss reference is higher than msgA-RSRP-Threshold; or

[0165] 1> If the BWP selected for the random access procedure is configured with only 2-step RA type random access resources within the selected random access resource set according to Clause 5.1.1b; or

[0166] 1> If a random access procedure is initiated for a synchronization reconfiguration and if contention-free random access resources of 2-step RA type have been explicitly provided in rach-ConfigDedicated for the BWP selected for the random access procedure, then:

[0167] 2> Set RA_TYPE to 2-stepRA.

[0168] 1> Otherwise:

[0169] 2> Set RA_TYPE to 4-stepRA.

[0170] 1> Perform the initialization of variables specific to the random access type as specified in Clause 5.1.1a;

[0171] 1> Set RA_TYPE to 2-stepRA:

[0172] 2> Perform the random access resource selection procedure for 2-step RA type (see Clause 5.1.2a).

[0173] 1> Otherwise:

[0174] 2> Perform the random access resource selection procedure (see Clause 5.1.2).

[0175] 5.1.2 Random Access Resource Selection

[0176] If the selected RA_TYPE is set to 4-stepRA, the MAC entity shall:

[0177] …

[0178] 2> Randomly select a random access preamble from the random access preambles associated with the selected SSB and the selected random access preamble group with equal probability;

[0179] 2> Set PREAMBLE_INDEX to the selected random access preamble.

[0180] …

[0181] 1> Otherwise, if an SSB is selected as above, then:

[0182] 2> Determine the next available PRACH occasion from the PRACH occasions corresponding to the ra-ssb-

[0183] OccasionMaskIndex (if configured) or ssb-SharedRO-MaskIndex (if configured), the selected SSB restricted by the given or PDCCH-indicated grant (in accordance with clause 8.1 of TS 38.213 [5], the MAC entity shall randomly select a PRACH occasion among consecutive PRACH occasions with equal probability, regardless of the FR2 UL gap corresponding to the selected SSB; the MAC entity may consider the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected SSB).

[0184] 1> Otherwise, if CSI-RS is selected as above:

[0185] 2> If there is no contention-free random access resource associated with the selected CSI-RS, then:

[0186] 3> Determine the next available PRACH occasion from the PRACH occasions, restricted by the OccasionMaskIndex (if configured), corresponding to the SSB in the candidateBeamRSList that is quasi-co-located with the selected CSI-RS specified in TS

[0187] 38.213 [5] clause 8.1, the MAC entity shall randomly select a PRACH occasion among consecutive PRACH occasions with equal probability, regardless of the FR2

[0188] UL gap corresponding to the SSB that is quasi-co-located with the selected CSI-RS; the MAC entity may consider the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the SSB that is quasi-co-located with the selected CSI-RS).

[0189]

[0190] 2> Otherwise:

[0191] 3> Determine the next available PRACH occasion in the ra-OccasionList from the PRACH occasions corresponding to the selected CSI-RS (the MAC entity shall randomly select a PRACH occasion among simultaneously occurring but on different subcarriers with equal probability, regardless of the FR2 UL gap corresponding to the selected CSI-RS; the MAC entity may consider the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected CSI-RS).

[0192] 1> Execute the random access preamble transmission procedure (see clause 5.1.3).

[0193] …

[0194] 5.1.2a Random access resource selection for 2-step RA typeIf the selected RA_TYPE is set to 2-stepRA, the MAC entity shall:

[0195] …

[0196] 2> Randomly select a random access preamble with equal probability from the 2-step RA type random access preambles associated with the selected SSB and the selected random access preamble group;

[0197] 2> Set PREAMBLE_INDEX to the selected random access preamble.

[0198] 1> Determine the next available PRACH occasion from the PRACH occasions, corresponding to the selected SSB permitted by the restrictions given by msgA-SSB-SharedRO-MaskIndex (if configured) or ra-ssb-OccasionMaskIndex (if configured) or ssb-SharedRO-MaskIndex (if configured) (According to clause 8.1 of TS 38.213 [5], the MAC entity shall randomly select a PRACH occasion with equal probability among the consecutive PRACH occasions allocated for 2-step RA type, regardless of the FR2 UL gap corresponding to the selected SSB; the MAC entity may consider the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected SSB).

[0199] 1> If the MAC entity does not select a random access preamble among the contention-based random access preambles:

[0200] 2> Select a PUSCH occasion from the PUSCH occasions in msgA-CFRA-PUSCH of the PRACH time slot corresponding to the selected PRACH occasion according to msgA-PUSCH-resource-Index corresponding to the selected SSB

[0201] ;

[0202] 2> Determine the UL grant and the associated HARQ information for the MSGA payload in the selected PUSCH occasion;

[0203] 2> Deliver the UL grant and the associated HARQ information to the HARQ entity.

[0204] 1> Otherwise:

[0205] 2> Select the PUSCH time corresponding to the selected preamble and PRACH time according to clause 8.1A of TS 38.213 [5];

[0206] 2> Determine the UL grant for the MSGA payload according to the PUSCH configuration associated with the selected random access preamble group, and determine the associated HARQ information;

[0207] 2> If the selected preamble and PRACH time are mapped to a valid PUSCH time, as specified in clause 8.1A of TS

[0208] 38.213 [5], then:

[0209] 3> Deliver the UL grant and the associated HARQ information to the HARQ entity.

[0210] 1> Execute the MSGA transmission procedure (see clause 5.1.3a).

[0211] …

[0212] 5.1.3 Random access preamble transmission

[0213] For each random access preamble, the MAC entity shall:

[0214] …

[0215] 1> Instruct the physical layer to transmit the random access preamble using the selected PRACH time, the corresponding RA-RNTI (if available), PREAMBLE_INDEX, and PREAMBLE_RECEIVED_TARGET_POWER.

[0216] …

[0217] 5.1.3a MSGA transmission

[0218] For each MSGA, the MAC entity shall:

[0219] …

[0220] 1> Indicate that the physical layer uses the selected PRACH occasion and the associated PUSCH resource of MSGA (if the selected preamble and PRACH occasion are mapped to a valid PUSCH occasion), use the corresponding RA-RNTI, MSGB-RNTI, PREAMBLE_INDEX, PREAMBLE_RECEIVED_TARGET_POWER, msgA-PreambleReceivedTargetPower, and transmit MSGA with the power ramping applied to the latest MSGA preamble transmission (i.e., (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP);

[0221] …

[0222] 5.1.4 Random access response reception

[0223] Once the random access preamble is transmitted, regardless of whether a measurement gap may occur, the MAC entity shall:

[0224] 1> If the contention-free random access preamble for beam failure recovery request is transmitted by the MAC entity:

[0225] 2> If the contention-free random access preamble for beam failure recovery request is transmitted in a non-terrestrial network, then:

[0226] 3> Start the ra-ResponseWindow configured in BeamFailureRecoveryConfig at the PDCCH occasion specified in TS 38.213 [5].

[0227] 2> Otherwise:

[0228] 3> Start the ra-ResponseWindow configured in BeamFailureRecoveryConfig at the first PDCCH occasion as specified in TS 38.213 [5] from the time when the random access preamble transmission ends.

[0229] ResponseWindow.

[0230] 2> When the ra-ResponseWindow is in operation, listen for PDCCH transmissions on the search space indicated by recoverySearchSpaceId of the SpCell identified by C-RNTI.

[0231] 1> Otherwise:

[0232] …

[0233] 3> Starting from the time when the transmission of the random access preamble ends, initiate the ra-ResponseWindow configured in RACH-ConfigCommon at the first PDCCH occasion as specified in TS 38.213 [5].

[0234] 2> When the ra-ResponseWindow is in operation, monitor the PDCCH of the SpCell for the random access response identified by the RA-RNTI.

[0235] …

[0236] 5.1.4a MSGB Reception and Contention Resolution for 2-Step RA Type

[0237] Once the MSGA preamble is transmitted, regardless of whether measurement gaps may occur, the MAC entity shall:

[0238] 1> Initiate the msgB-ResponseWindow at the PDCCH occasion as specified in TS 38.213 [5], clause 8.2A;

[0239] 1> When the msgB-ResponseWindow is in operation, monitor the PDCCH of the SpCell for the random access response identified by the MSGB-RNTI;

[0240] 1> If the C-RNTI MAC CE is included in MSGA, then:

[0241] 2> When the msgB-ResponseWindow is in operation, monitor the PDCCH of the SpCell for the random access response identified by the C-RNTI.

[0242] …

[0243] 6.1.5 MAC PDU (Random Access Response)

[0244] The MAC PDU consists of one or more MAC sub-PDUs and optionally padding. Each MAC sub-PDU consists of one of the following:

[0245] - A MAC sub-header with only a backoff indicator;

[0246] - A MAC sub-header with only a RAPID (i.e., confirmation for SI request);

[0247] - A MAC sub-header with a RAPID and a MAC RAR.

[0248] ***************************End of citation********************************

[0249] The general description of the random access procedure is specified in [4] 3GPP TS 38.300 V17.6.0 (2023-09): ***********************Start of citation [4]********************************

[0250] 9.2.6 Random access procedure

[0251] The random access procedure is triggered by multiple events:

[0252] - Initial access from RRC_IDLE;

[0253] …

[0254] Two types of random access procedures are supported: the 4-step RA type with MSG1 and the 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 in Figure 9 .2.6-1.

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

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

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

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

[0259] …

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

[0261] The MSGA of the two-step RA type contains a preamble on the PRACH and a payload on the PUSCH. After transmitting the MSGA, 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, as Figure 9 .2.6-1(d) as shown. For CBRA, if the contention resolution is successful after receiving the network response, the UE ends the random access procedure, as Figure 9 .2.6-1(b) as shown; 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 listens for contention resolution, as Figure 9 .2.6-2 as shown. If the contention resolution is unsuccessful after the (re)transmission of MSG3, the UE returns to MSGA transmission.

[0262] If the random access procedure with the two-step RA type is not completed after several MSGA transmissions, the UE can be configured to switch to CBRA with the four-step RA type.

[0263] Figure 7A is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1(a): Random access procedure, reproduction of CBRA with the four-step RA type.

[0264] Figure 7B is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1(b): Random access procedure, reproduction of CBRA with the two-step RA type.

[0265] Figure 7C is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1(c): Random access procedure, reproduction of CFRA with the four-step RA type.

[0266] Figure 7D is in 3GPP TS 38.300 V17.6.0 Figure 9.2.6 - 1(d): Reproduction of the random access procedure, CFRA with 2 - step RA type.

[0267] Figure 8 It is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6 - 2: Reproduction of the fallback of CBRA with 2 - step RA type.

[0268] ***************************End of citation********************************

[0269] In [5] 3GPP TS 38.213 V17.7.0 (2023 - 09), the RA response is specified.

[0270] ************************Start of citation [5]********************************

[0271] 8 Random access procedure

[0272] Before initiating the physical random access procedure, layer 1 receives a set of SS / PBCH block indices from the higher layer and provides the corresponding set of RSRP measurements to the higher layer.

[0273] Before initiating the physical random access procedure, layer 1 may receive an indication from the higher layer 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.

[0274] Before initiating the physical random access procedure, layer 1 receives the following information from the higher layer:

[0275] - Configuration of the physical random access channel (PRACH) transmission parameters (PRACH preamble format, time resources, and frequency resources for PRACH transmission).

[0276] - Parameters for determining the root sequence and its cyclic shift in the PRACH preamble sequence set (index of the logical root sequence list, cyclic shift (N CS ) and set type (unrestricted, restricted set A, or restricted set B)).

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

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

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

[0280] If the UE is configured with two UL carriers for the serving cell and the UE detects a PDCCH command, the UE uses the UL / SUL indicator field value from the detected PDCCH command to determine the UL carrier for the corresponding PRACH transmission.

[0281] 8.1 Random access preamble

[0282] After a request from the higher layers or a PDCCH command for a PRACH transmission, the physical random access procedure is triggered. The configuration by the higher layers for the PRACH transmission includes the following:

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

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

[0285] …

[0286] 8.2 Random access response - Type 1 random access procedure

[0287] 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 the higher layers [3, TS 38.321]. The window starts at the first symbol of the earliest CORESET, and the UE is configured to receive the PDCCH for the Type1-PDCCH CSS set as defined in clause 10.1, i.e., at least one symbol after the last symbol of the PUSCH moment corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for the Type1-PDCCH CSS set as defined in clause 10.1. If, as defined in [TS 38.211], or is non-zero, the window starts after an additional T TA +k mac milliseconds, where T TA is defined in [TS 38.211] and k mac is provided by kmac, or if kmac is not provided, then k mac = 0. Based on the SCS for the Type1-PDCCH CSS set, the length of the window in a number of time slots is provided by ra-ResponseWindow.

[0288] …

[0289] 8.2A Random access response - Type 2 random access procedure

[0290] In response to the transmission of a PRACH and a PUSCH, or in response to the transmission of only a PRACH in the case where the PRACH preamble is mapped to a valid PUSCH moment, the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding MsgB-RNTI during a window controlled by the higher layers [3, TS 38.321]. The window starts at the first symbol of the earliest CORESET, and the UE is configured to receive the PDCCH for the Type1-PDCCH CSS set as defined in clause 10.1, i.e., at least one symbol after the last symbol of the PUSCH moment corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for the Type1-PDCCH CSS set. If, as defined in [TS 38.211], or is non-zero, the window starts after an additional T TA +k mac milliseconds, where T TA is defined in [TS 38.211] and k mac is provided by kmac, or if kmac is not provided, then k mac= 0. Based on the SCS for the Type1-PDCCH CSS set, the length of the window in several time slots is provided by msgB-ResponseWindow.

[0291] In response to the transmission of the PRACH, if the PRACH preamble is not mapped to a valid PUSCH occasion, the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI during a window controlled by the higher layers [3, TS 38.321]. The window starts at the first symbol of the earliest CORESET where the UE is configured to receive the PDCCH for the Type1-PDCCH CSS set as defined in clause 10.1, i.e., at least one symbol after the last symbol of the PRACH occasion corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for the Type1-PDCCH CSS set. Based on the SCS for the Type1-PDCCH CSS set, the length of the window in several time slots is provided by msgB-ResponseWindow.

[0292] *************************End of citation [5]********************************

[0293] In the 3GPP RAN1#116 meeting, there are various protocols regarding the Ambient Internet of Things (A-IoT).

[0294] For the purpose of research, RAN1 uses the following terms:

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

[0296] - Device 2a: Peak power consumption of ≤ a few hundred μW, with energy storage, initial sampling frequency offset (SFO) up to 10 X ppm, and there is a DL and / or UL amplifier in the device. The UL transmission of the device backscatters on an externally provided carrier.

[0297] - Device 2b: ≤ a few hundred μW peak power consumption, with energy storage, an initial sampling frequency offset (SFO) of up to 10 X ppm, and DL and / or UL amplifiers in the device. The UL transmission of the device is generated internally within the device.

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

[0299] For A-IoT reader-to-(Environmental IoT) device (R2D) and (Environmental IoT) device-to-A-IoT reader (D2R) transmissions, at least the following time-domain frame structures have been studied.

[0300] - For R2D transmission,

[0301] -- Includes an R2D timing acquisition signal (e.g., R2D preamble) for at least timing acquisition and for indicating the start of R2D transmission in the time domain.

[0302] - For D2R transmission,

[0303] -- Includes a D2R timing acquisition signal (e.g., D2R preamble) for at least timing acquisition and for indicating the start of D2R transmission in the time domain.

[0304] - Other necessary components are to be further studied (FFS), e.g.,

[0305] midamble, postamble, periodic synchronization signal, control field, guard period.

[0306] For environmental IoT devices, the study of a dedicated physical broadcast channel for R2D, e.g., a Physical Broadcast Channel (PBCH)-like, is not considered.

[0307] For environmental IoT devices, at least for R2D data transmission, a physical channel (Physical Reader-to-(Environmental IoT) Device Channel (PRDCH)) has been studied,

[0308] - System information (if defined) is transmitted on the PRDCH.

[0309] - FFS whether / how control information is transmitted on the PRDCH.

[0310] - Note: For the purpose of the study, the naming of PRDCH is used.

[0311] For an environmental IoT device, at least for D2R data transfer, the physical channel (Physical (Environmental IoT) Device (to) Reader Channel (PDRCH)) is studied together with the following:

[0312] - Responses transmitted from the device to the reader during contention-based access procedures are transmitted on the PDRCH.

[0313] In recent years, it has been expected that more devices will be interconnected in the wireless communication world to improve productivity, efficiency, and increase the comfort of life. However, powering all IoT devices with batteries that require manual replacement or recharging results in high maintenance costs, environmental problems, and safety hazards for some use cases (e.g., wireless sensors in power). Further reduction in the size, complexity, and power consumption of IoT devices enables deployment for various applications (e.g., automated manufacturing, smart home).

[0314] On the other hand, barcodes and Radio-frequency Identification (RFID) have a limited reading range of several meters, which usually requires handheld scanning. This results in labor-intensive and time-consuming operations. Additionally, the lack of interference management schemes leads to severe interference and capacity problems among RFID readers, especially in the case of dense deployment. RFID has difficulty supporting large-scale seamless coverage networks. In contrast, research on environmental IoT has investigated the feasibility of new IoT technologies within the 3GPP system.

[0315] An ambient IoT device / User Equipment (UE) will have ultra-low complexity, extremely small device size, and long lifecycle. The ambient IoT device / UE will have complexity and power consumption several orders of magnitude lower than existing 3GPP Low Power Wide Area (LPWA) technologies (e.g., Narrowband Internet of Things (NB-IoT), enhanced Machine Type Communication (eMTC)). The ambient IoT device / UE may or may not have energy storage. The energy of the ambient IoT device / UE can be provided by collecting radio waves, light, motion, heat, or any other suitable power source. The energy and / or power source can be provided once (e.g., unexpectedly or non-periodically), periodically, or continuously. In one embodiment, the power / energy of the ambient IoT device / UE can be provided from a carrier from the network and / or intermediate node. In topology 1, the ambient IoT device / UE will communicate directly and bidirectionally with the base station. In topology 2, the ambient IoT device / UE communicates bidirectionally with an intermediate node (e.g., UE or relay node) between the ambient IoT device / UE and the base station. The UL transmission of the ambient IoT device / UE can be generated internally by the device / UE or backscattered on an externally provided carrier. More details about the ambient IoT (device / UE) can be found in research projects [1] RP-234058 and [2] 3GPP TR 38.848 V18.0.0 (2023-09).

[0316] Currently, the UE will trigger a Random Access (RA) procedure for initial access to connect to the network from the Radio Resource Control idle (RRC_IDLE) state. The initial access can be an RRC establishment procedure. The UE will transmit an RRC establishment request message (e.g., RRCSetupRequest) to the network. In response to transmitting the RRC establishment request message (e.g., RRCSetupRequest), the UE will receive an RRC setup message (e.g., RRCSetup) from the network. The RRC establishment request message (e.g., RRCSetupRequest) and the RRC setup message (e.g., RRCSetup) are Common Control Channel (CCCH) messages of the logical channel from the Radio Link Control (RLC) layer.

[0317] However, for environmental IoT UEs, there may be no RRC procedures, RRC states (transitions), and / or upper layers (e.g., RLC layer, Packet Data Convergence Protocol (PDCP) layer, Service Data Adaptation Protocol (SDAP) layer). The environmental IoT UE may be in (RRC) idle mode, (RRC) inactive mode, and / or (RRC) connected mode. The environmental IoT UE may not be in any / one / more of the (RRC) idle mode, (RRC) inactive mode, and / or (RRC) connected mode.

[0318] The UE (e.g., environmental IoT UE) may receive signaling from the NW, for example, via paging, System Information Block (SIB), Physical Downlink Control Channel (PDCCH) commands, PRDCH. In response to the (received) signaling, the UE may trigger the RA procedure. The signaling may be used to trigger (or indicate) the RA procedure (or initial access) of the UE. The signaling may be used to trigger (or indicate) the transmission (or reception) of the UE. The transmission from the UE may be (or include) a backscatter transmission (or reception), or may be internally generated by the UE. The signaling may be used to supply power and / or energy to the UE. The signaling may be (or include) any one of RRC signaling (e.g., RRC configuration message), Medium Access Control (MAC) signaling (e.g., MAC Control Element (CE)), or Physical Layer (PHY) signaling (e.g., PDCCH, Downlink Control Information (DCI)). The signaling may be (or include) a carrier (signal) and / or an interrogation signal.

[0319] The signaling may be public signaling or dedicated signaling. The public signaling may be (or include) cell-specific configuration. The public signaling may be (or include) configuration common to multiple UEs, a group of UEs, and / or a UE group. The public signaling may be (or include) broadcast signaling, system information, and / or paging. The dedicated signaling may be (or include) UE-specific configuration. The dedicated signaling may be (or include) configuration dedicated to a (single) UE. The dedicated signaling may be (or include) RRC signaling (e.g., RRC configuration message). The dedicated signaling may be (or include) MAC signaling (e.g., MAC CE). The dedicated signaling may be (or include) PHY signaling (e.g., PDCCH, Downlink Control Information (DCI)).

[0320] In a RA procedure (e.g., for environmental IoT), the UE may transmit a first transmission to the NW. The NW may transmit a second transmission to the UE in response to the reception / detection of the first transmission. In response to transmitting the first transmission or after transmitting the first transmission, the UE may receive the second transmission from the NW. In response to transmitting the first transmission or after transmitting the first transmission, the UE may monitor the PDCCH / PRDCH during a first duration for receiving the second transmission. In response to receiving the second transmission or after receiving the second transmission, the UE may or may not transmit a third transmission to the NW. In the case where the UE transmits a third transmission to the NW, in response to the reception of the third transmission, the NW may transmit a fourth transmission to the UE. In response to transmitting the third transmission or after transmitting the third transmission, the UE may receive the fourth transmission from the NW. In response to transmitting the third transmission or after transmitting the third transmission, the UE may monitor the PDCCH / PRDCH during a second duration for receiving the fourth transmission.

[0321] The first transmission may be a Message 1 (Msg1) (transmission) and / or a Message A (MSGA) (transmission). The first transmission may include a RA preamble transmission and / or a MSGA payload transmission. Preferably, in some embodiments, the first transmission may include a first preamble transmission and / or a first uplink data transmission. The first transmission may include a transmission via the Physical Random Access Channel (PRACH) and / or a transmission via the first Physical Uplink Shared Channel (PUSCH). Throughout this disclosure, the "first transmission" may be replaced by the "first message".

[0322] The second transmission may be a Message 2 (Msg2) (transmission), a Random Access Response (RAR) (transmission), and / or a Message B (MSGB) (transmission). The MSGB may include a fallback RAR (MAC sub-protocol Data Unit (subPDU)) or a success RAR (MAC subPDU). The second transmission may be a NW response to the first transmission. Preferably, in some embodiments, the second transmission may include a first downlink control transmission and / or a first downlink data transmission. The second transmission may include control information and / or data. The second transmission may include a transmission via the first PDCCH / PRDCH and / or the first Physical Downlink Shared Channel (PDSCH). The second transmission may provide / indicate a UL grant for scheduling UL resources. Throughout this disclosure, the "second transmission" may be replaced by the "second message".

[0323] The third transmission may be Message 3 (Msg3) (transmission). The third transmission may be an uplink transmission using the UL grant / resource provided / indicated by the second transmission. Preferably, in some embodiments, the third transmission may include a second uplink data transmission. The third transmission may include transmission via a second PUSCH. Throughout this disclosure, "third transmission" may be replaced by "third message".

[0324] The fourth transmission may be Message 4 (Msg4) (transmission). The fourth transmission may be an NW response to the third transmission. Preferably, in some embodiments, the fourth transmission may include a second downlink control transmission and / or a second downlink data transmission. The fourth transmission may include transmission via a second PDCCH / PRDCH and / or transmission via a second PDSCH. Throughout this disclosure, "fourth transmission" may be replaced by "fourth message".

[0325] Throughout this disclosure, UL transmission may be or include the first transmission, the third transmission, and / or subsequent UL transmissions. UL transmission may be or include Physical Uplink Control Channel (PUCCH), PDRCH, and / or PUSCH transmission. Subsequent UL transmissions may be UL transmissions after the first transmission or the third transmission. Subsequent UL transmissions may be UL transmissions after the RA procedure is completed. Throughout this disclosure, DL transmission may be or include the second transmission, the fourth transmission, and / or subsequent DL transmissions. DL transmission may be or include PDCCH, PRDCH, and / or PDSCH transmission. Subsequent DL transmissions may be DL transmissions after the second transmission or the fourth transmission. Subsequent DL transmissions may be DL transmissions after the RA procedure is completed.

[0326] The first duration may be the time when the first / second timer is running. The first duration may be a time window, e.g., to listen for an (RA / NW) response. The first timer, the first duration, and / or the response window (e.g., as described below) may be ra-ResponseWindow and / or a timer for an access procedure (e.g., for ambient IoT). The second timer, the first duration, and / or the response window (as described below) may be msgB-ResponseWindow and / or a timer for an access procedure (e.g., for ambient IoT). The first duration may start after the first transmission or in response to the first transmission. The first duration may be used to receive the second transmission for the UE. The first duration may be used to transmit the second transmission for the NW.

[0327] The second duration may be the time during which a third timer is running. The third timer and / or the second duration may be a contention resolution timer (e.g., ra-ContentionResolutionTimer) and / or a timer for an access procedure (e.g., for ambient IoT). The second duration may start after or in response to a third transmission. The second duration may be used to receive a fourth transmission for the UE. The second duration may be used to transmit a fourth transmission for the NW.

[0328] The above timers may be different timers.

[0329] Throughout this disclosure, "DL" may be replaced by "Reader to Device (R2D)". A DL transmission may be a transmission from the reader to the device and / or an R2D transmission, referred to as a transmission from the reader to the device and / or an R2D transmission, and / or supplemented by a transmission from the reader to the device and / or an R2D transmission. DL data may be data available on the reader side, data transmitted from the reader to the device, and / or R2D data, referred to as data available on the reader side, data transmitted from the reader to the device, and / or R2D data, and / or supplemented by data available on the reader side, data transmitted from the reader to the device, and / or R2D data. The DL transmission and / or DL data may include an indication, configuration, signal / signaling / signalling, and / or message from the reader.

[0330] Throughout this disclosure, "UL" may be replaced by "Device to Reader (D2R)". A UL transmission may be a transmission from the device to the reader and / or a D2R transmission, referred to as a transmission from the device to the reader and / or a D2R transmission, and / or supplemented by a transmission from the device to the reader and / or a D2R transmission. UL data may be data available on the device side, data transmitted from the device to the reader, and / or D2R data, referred to as data available on the device side, data transmitted from the device to the reader, and / or D2R data, and / or supplemented by data available on the device side, data transmitted from the device to the reader, and / or D2R data. The UL transmission and / or UL data may include an indication, signal / signaling, and / or message from the device. A UL grant may be one or more resources provided by the reader / NW / intermediate node, used by the device / UE, and / or for transmitting / executing a D2R transmission.

[0331] Throughout this disclosure, the reader may be an NW / intermediate node, a UE, and / or an intermediate node and / or replaced by an NW / intermediate node, a UE, and / or an intermediate node. Throughout this disclosure, the device may be a UE and / or an intermediate node and / or replaced by a UE and / or an intermediate node. The device may be referred to as an ambient IoT device. "UE" may include a reader and / or a device. "NW / intermediate node" may include a reader.

[0332] The UE / device may receive a carrier from the reader. The UE / device may receive a carrier from a node other than the reader.

[0333] Throughout this disclosure, the "random access (RA) procedure" may be an access procedure performed by an (ambient IoT) UE / device, replaced by an access procedure performed by an (ambient IoT) UE / device, and / or referred to as an access procedure performed by an (ambient IoT) UE / device. The resources and / or configurations for the access procedure may include, for example, PDRCH resources, time, frequency, and / or frequency band for D2R transmission. The resources and / or configurations for the access procedure may include, for example, parameters, random numbers, group numbers, and / or auxiliary information for D2R transmission.

[0334] Throughout this disclosure, "2-step RA" may be a 2-step access procedure performed by an (ambient IoT) UE / device, replaced by a 2-step access procedure performed by an (ambient IoT) UE / device, and / or referred to as a 2-step access procedure performed by an (ambient IoT) UE / device.

[0335] Throughout this disclosure, "4-step RA" may be a 4-step access procedure performed by an (ambient IoT) UE / device, replaced by a 4-step access procedure performed by an (ambient IoT) UE / device, and / or referred to as a 4-step access procedure performed by an (ambient IoT) UE / device.

[0336] The UE may execute procedures for RA, (initial) access, (ambient IoT) response / reporting, and / or (R2D / D2R) transmission. The procedures may be the procedures described above. The UE may access the NW / intermediate node via the procedures, receive signaling / messages / configurations, and / or transmit (D2R) data. The UE may receive signaling from the NW / intermediate node (e.g., from the reader). The signaling may be the signaling described above. The signaling may be a query, paging, indication, and / or R2D message.

[0337] In response to (receiving) a signaling, the UE may trigger / execute the said procedure and / or the following transmissions. In the said procedure, the UE may transmit a first transmission to the NW / intermediate node. In response to the reception / detection of the first transmission, the NW / intermediate node may transmit a second transmission to the UE. In response to transmitting the first transmission or after transmitting the first transmission, the UE may receive the second transmission from the NW / intermediate node. In response to (receiving) the second transmission, the UE may transmit a third transmission to the NW / intermediate node. In response to the reception of the third transmission, the NW / intermediate node may transmit a fourth transmission to the UE. In response to the reception of the third transmission, the NW / intermediate node may not transmit a fourth transmission to the UE. In response to transmitting the third transmission or after transmitting the third transmission, the UE may or may not receive the fourth transmission from the NW / intermediate node. In response to (receiving) the fourth transmission, the UE may transmit a fifth transmission to the NW / intermediate node.

[0338] The first transmission in the said procedure may be / include information on a random number, information on the number of preambles, and / or information on an (access) identity (ID) selected / generated / determined by the UE. The ID may be a random ID.

[0339] The second transmission in the said procedure may be a response and / or confirmation of the first transmission. The second transmission may indicate, identify, and / or correspond to the first transmission. The second transmission may provide resources for a subsequent D2R transmission (e.g., the third transmission).

[0340] The third transmission in the said procedure may be / include information on a device / UE ID, a report, auxiliary information, D2R data, and / or information from the UE.

[0341] The fourth transmission in the said procedure may be a response, confirmation, DL / R2D command, R2D data, and / or scheduling of the third transmission. The fourth transmission may indicate, identify, and / or correspond to the third transmission. The fourth transmission may provide resources for a subsequent D2R transmission. The fourth transmission may indicate, notify, and / or permit the fifth transmission.

[0342] The fifth transmission in the said procedure may be / include a feedback (of the fourth transmission), a report, auxiliary information, D2R data, and / or information from the UE.

[0343] The first transmission, the third transmission, and / or the fifth transmission may be a D2R transmission and / or a PDRCH transmission. The signaling, the second transmission, and / or the fourth transmission may be an R2D transmission and / or a PRDCH transmission. The signaling and / or the second transmission may be broadcast, provided, and / or transmitted to one or more UEs. The second transmission and / or the fourth transmission may be provided and / or transmitted to a dedicated UE. The fourth transmission and / or the fifth transmission may be subsequent transmissions during or after the said procedure.

[0344] Throughout this disclosure, Msg1 and / or MSGA may be replaced by a first transmission. Throughout this disclosure, Msg2, RAR, and / or MSGB may be replaced by a second transmission. Throughout this disclosure, MSGA and / or Msg3 may be replaced by a third transmission. Throughout this disclosure, MSGB and / or Msg4 may be replaced by a fourth transmission. Throughout this disclosure, Message 5 (Msg5) may be replaced by a fifth transmission.

[0345] The identification of the UE and / or the UE ID may be or include a random number, a temporary number, a preamble number (e.g., Random Access Preamble ID (RAPID)), and / or an ID selected / generated / determined by the UE. The identification of the UE and / or the UE ID may be or include the device ID of the UE, the UE ID, the group ID, the contention resolution identification, and / or the Radio Network Temporary Identifier (RNTI). The (access) ID included in the first transmission may be different from the device / UE ID included in the third transmission.

[0346] Throughout this disclosure, the following may be interchangeable: "initiate a procedure", "perform a procedure", "trigger a procedure", and / or "execute a procedure".

[0347] Throughout this disclosure, "CCCH", "PRACH", Random Access Channel ("RACH"), "PUSCH", and / or "PUCCH" may be "Physical Device-to-Reader Channel", a channel for transmission from a device to a reader, and / or PDRCH, constituted by "Physical Device-to-Reader Channel", a channel for transmission from a device to a reader, and / or PDRCH, replaced by "Physical Device-to-Reader Channel", a channel for transmission from a device to a reader, and / or PDRCH, and / or referred to as "Physical Device-to-Reader Channel", a channel for transmission from a device to a reader, and / or PDRCH. Throughout this disclosure, "PDSCH" and / or "PDCCH" may be "(physical) channel", "Physical Reader-to-Device Channel", a channel for transmission from a reader to a device, and / or PRDCH, constituted by "(physical) channel", "Physical Reader-to-Device Channel", a channel for transmission from a reader to a device, and / or PRDCH, replaced by "(physical) channel", "Physical Reader-to-Device Channel", a channel for transmission from a reader to a device, and / or PRDCH, and / or referred to as "(physical) channel", "Physical Reader-to-Device Channel", a channel for transmission from a reader to a device, and / or PRDCH. D2R transmission may be via PDRCH transmission. R2D transmission may be via PRDCH transmission.

[0348] Throughout this disclosure, "RA resource / configuration", "UL resource / configuration", and / or "resource / configuration" may be a resource / configuration for D2R transmission, replaced by a resource / configuration for D2R transmission, and / or referred to as a resource / configuration for D2R transmission (e.g., as described above). The resource and / or configuration may include, for example, PDRCH (transmission) resources, time instants, channel resources, frequency resources, and / or (sub)bands for D2R transmission. The resource and / or configuration may include, for example, parameters, random numbers, group numbers, and / or auxiliary information for D2R transmission.

[0349] The UE may listen for / receive PRDCH in procedures of RA, (initial) access, and / or (R2D / D2R) transmission.

[0350] A UE (e.g., an ambient IoT UE) may not transmit RRC messages and / or (UL) CCCH messages in the RA procedure. The UE may transmit a MAC CE to the network, e.g., for initial access. The UE may transmit the MAC CE via a first transmission and / or a third transmission. The UE may include the MAC CE in the first transmission and / or the third transmission. The UE may not include RRC messages and / or (UL) CCCH messages in the first transmission and / or the third transmission. The MAC CE may be and / or include first information. The MAC CE may be and / or include a UE ID, an indication of a cause, and / or auxiliary information. The MAC CE may be a UE ID MAC CE. The MAC CE may be a MAC CE for reporting first information. The MAC CE may be a MAC CE for requesting a resource for reporting first information. The MAC CE may be a UE contention resolution identity MAC CE. The UE may not trigger an RRC (establishment) procedure. The UE may not establish or set up an RRC connection.

[0351] The first information may be, include, or indicate one or more of the following:

[0352] UE Type (or Device Type)

[0353] The UE may indicate its UE type (or device type) (explicitly or implicitly) in a UL transmission.

[0354] There may be two or more types of UEs (or devices). The UE type (device type) may be distinguished at least by energy storage, a method for performing UL transmission, power level, and / or device size. Preferably, in some embodiments, the method for performing UL transmission may be backscattered on a carrier (signal) generated internally by the device / UE or provided externally.

[0355] For example, a first type of UE (or device) may be Device A or Device B, e.g., as considered in [2] 3GPP TR38.848 V18.0.0 (2023-09). The first type of UE (or device) may have (or be equipped with) a battery or energy storage. The first type of UE (or device) may not have (or be equipped with) a battery or energy storage. The first type of UE (or device) may not have (or be equipped with) a DL / UL amplifier. The first type of UE (or device) may be a passive or semi-passive device. The first type of UE (or device) may generate a UL transmission by backscattering. The first type of UE (or device) may perform a backscattering transmission. The first type of UE (or device) may not be able to (internally) generate a UL transmission by itself. The first type of UE (or device) may not have the ability to generate a signal without backscattering.

[0356] For example, the second type of UE (or device) may be Device C, as considered in [2] 3GPP TR 38.848 V18.0.0 (2023-09), for example. The second type of UE (or device) may have (or be equipped with) a battery or energy storage. The second type of UE (or device) may have (or be equipped with) a DL / UL amplifier. The second type of UE (or device) may be an active device. The second type of UE (or device) may generate UL transmissions through backscattering. The second type of UE (or device) may perform backscattering transmissions. The second type of UE (or device) itself may be capable of (internally) generating UL transmissions. The second type of UE (or device) may have the ability to generate signals without backscattering.

[0357] Power Level

[0358] The UE may indicate its power level (explicitly or implicitly) in UL transmissions. The UE may indicate a parameter related to the power level in the transmission.

[0359] The power level may include any one or more of the following embodiments. The power level may be the power state of the UE (represented by the power state of the UE). The UE may use the same or different power level embodiments for different RA resource selection (steps), for example, determining a Bandwidth Part (BWP), determining an RA resource / configuration group, determining an RA type, determining an RA preamble, determining a PDRCH time, determining a RACH time, and / or determining a PUSCH time. There may be one or more thresholds for the power level. The power level may be determined by the threshold. The threshold of the power level may be configured by the network or derived by the UE. The threshold of the power level may be determined based on the following embodiments and / or the (selected) RA resource / configuration.

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

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

[0362] In one embodiment, the power level may be the desired / derived / determined UE transmission power for backscattering transmissions (e.g., the first transmission and / or the third transmission).

[0363] In one embodiment, the power level may be the desired / derived / determined UE transmission power for UL transmissions generated internally by the UE (e.g., the first transmission and / or the third transmission).

[0364] In one embodiment, the power level may be the maximum UE transmission power (e.g., for the first transmission and / or the third transmission).

[0365] In one embodiment, the power level may be the amount of battery power / storage power / available power of the UE. The UE may estimate / determine / derive how much battery power / storage power / available power can be utilized / used to perform the (corresponding) RA procedure.

[0366] In one embodiment, the power level may be a predefined / (pre)-configured / indicated power. The indicated power may be indicated by the network or by a higher layer of the UE. Preferably, in some embodiments, the predefined / (pre)-configured / indicated power may be the guaranteed or required power (amount or capacity) for enabling / activating / initiating the (corresponding) RA procedure. Preferably, in some embodiments, the predefined / (pre)-configured / indicated power may be the desired / estimated power consumption (amount) for completing the (corresponding) RA procedure.

[0367] In one embodiment, the power level may be the power difference between the (downlink) path loss and the desired / derived / determined / maximum UE transmission power. The (downlink) path loss may be derived / determined based at least on the received power of a signal / channel from the network (e.g., a PRDCH, an R2D signal / channel, and / or a carrier (signal)). The desired / derived / determined UE transmission power may be used for backscatter transmissions or for UL transmissions generated internally by the UE.

[0368] In one embodiment, the power level may be the power difference between the battery power / storage power / available power and the desired / derived / determined / maximum UE transmission power. The desired / derived / determined UE transmission power may be used for backscatter transmissions or for UL transmissions generated internally by the UE. The UE may estimate / determine / derive how much battery power / storage power / available power can be utilized to perform the (corresponding) RA procedure.

[0369] In one embodiment, the power level may be the power difference between a predefined / (pre)-configured / indicated power and the desired / derived / determined / maximum UE transmission power. The indicated power may be indicated by the network or by a higher layer of the UE. Preferably, in some embodiments, the predefined / (pre)-configured / indicated power may be the guaranteed or required power (quantity or capacity) for enabling / activating / initiating the corresponding RA procedure. Preferably, in some embodiments, the predefined / (pre)-configured / indicated power may be the desired / estimated power consumption (quantity) for completing the corresponding RA procedure. The desired / derived / determined UE transmission power may be used for backscatter transmission or for UL transmission generated internally by the UE.

[0370] (UL) Data Type (or Transmission Type)

[0371] The UE may indicate (explicitly or implicitly) its data type (or transmission type) in UL transmission. The data type (or transmission type) may indicate the type of transmission (or data). The data type (or transmission type) may indicate use cases, traffic scenarios, service types, Quality of Service (QoS), logical channel (group), and / or topology. The data type (or transmission type) may be (or include): data, signaling, Device-Originated (DO), Device-Originated-Device-Terminated Triggered (DO-DTT), Device-Terminated (DT), single trigger, data burst, periodic, aperiodic, delay tolerant, and / or emergency.

[0372] (UL) Data types may be distinguished at least by use cases, traffic scenarios, service types, QoS, logical channel (group), and / or topology. (UL) Data types may be indicated by the network or by a higher layer of the UE. The UE may initiate or trigger an RA procedure for transmitting UL data.

[0373] (UL) Data Size

[0374] The UE may indicate (explicitly or implicitly) the data size in UL transmission.

[0375] (UL) The data size can be calculated / derived / determined by the UE. The (UL) data size can correspond to the (UL) data type. The UL data size can be the (potential) transport block size (TBS) of the MSGA payload and / or Msg3. The UL data size can be the (potential) TBS of the first transmission in the RA procedure. The (UL) data size can be the TBS of the ambient IoT information (or data). The UE can initiate or trigger the RA procedure for transmitting UL data.

[0376] UE ID

[0377] The UE can indicate its UE ID (explicitly or implicitly) in the UL transmission. The UE ID can be used to identify the UE (e.g., in the area). The UE ID can be stored by the UE. The UE ID can be a temporary ID.

[0378] A UE ID can be assigned to the UE. The UE ID can be predefined or (pre-)configured for the UE (e.g., by the NW). The UE ID can be configured or indicated to the UE (e.g., by the NW). The UE itself can calculate, select, derive, or determine the UE ID. The UE ID can be a random value. The UE ID can be a ue-Identity.

[0379] UE Group ID

[0380] The UE can indicate its UE group ID (explicitly or implicitly) in the UL transmission.

[0381] There can be multiple UE groups. The UE can be assigned to a UE group or associated with a UE group. The UE group can be predefined or (pre-)configured for the UE (e.g., by the UE). The UE group can be configured or indicated to the UE (e.g., by the NW). The UE can receive the group ID and / or value via paging, SIB, and / or PDCCH / PRDCH to derive / determine the group ID.

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

[0383] Multiple UEs may be assigned to different UE groups or associated with different UE groups based on the UE ID. For example, a UE may be assigned to or associated with a UE group, where the UE group ID of the UE group may be determined / derived / determined based at least on the UE ID and a value of the UE. Preferably, in some 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 / configured by the NW or be predefined or (pre)-configured. The UE group ID of the UE may be determined by a formula using the UE ID.

[0384] Multiple UEs may be assigned to different UE groups based on location. Preferably, in some embodiments, UEs in the same location and / or the same positioning range may be distributed to the same UE group. A UE may determine / derive its location or range based on the received carrier (signal), R2D signal / channel, and / or PRDCH. More specifically, a UE may determine / derive its location or range from a network / intermediate node based on the received power of the carrier (signal), R2D signal / channel, and / or PRDCH transmitted from the network / intermediate node. UEs in the same location and / or the same range may represent UEs having the same received power range of the carrier (signal), R2D signal / channel, and / or PRDCH. Preferably and / or alternatively, UEs in the same location and / or the same positioning range may be distributed to different UE groups. UEs within the range that can receive the same power supply, carrier, and / or NW signal (e.g., R2D signal / channel, PRDCH) may be (randomly) distributed to different UE groups.

[0385] Cause

[0386] The reason for (first or second) signaling (or transmission) may be provided (or indicated). The reason may indicate at least one or more of the following: DO-DTT (transmission), DT (transmission), DO transmission, first type of data (transmission), second type of data (transmission), (service / measurement / status) report (transmission), signaling (transmission), first type of UE (transmission), second type of UE (transmission), ambient IoT (transmission), and / or non-ambient IoT (transmission).

[0387] (The reason for (first or second) signaling (or transmission) may indicate the transmission type (e.g., DO-DTT, DT, DO). (The reason for (first or second) signaling (or transmission) may indicate the data type (as described above). (The reason for (first or second) signaling (or transmission) may indicate the UE type (as described above). (The reason for (first or second) signaling (or transmission) may indicate whether the UE is an ambient IoT UE or has the capability of ambient IoT.

[0388] Location or Position Information

[0389] The location (or position) of the UE can be provided (or indicated). The information can be (or include, or indicate) the coordinates of the UE. The information can be (or include, or indicate) the area where the UE is located. The information can be (or include, or indicate) the area ID. The area can be (or include) a cell, a tracking area, or a range of areas.

[0390] Information Related to (Data) Service

[0391] Information related to the (data) service of the UE can be provided (or indicated). The information can be (or include, or indicate) at least one or more of the following: service mode, time information related to the arrival of data (or packets), how long it is expected until the (next) data arrives, 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 arrival interval of the data, the data arrival period.

[0392] Information Related to UE Wake - up

[0393] Information related to the wake-up of the UE can be provided (or indicated). The information can be (or include, or indicate) at least one or more of the following: the (expected or preferred) wake-up time of the UE, time information related to the wake-up of the UE, information related to the active time of the UE, the time when the UE will wake up (or hopes to wake up), how long it is until the next wake-up of the UE. The wake-up of the UE can mean that the UE listens for DL / R2D signaling (e.g., carrier, R2D signal / channel) or PDCCH / PRDCH.

[0394] (Required) TB Size

[0395] Information related to the (required) Transport Block (TB) size for uplink transmission (e.g., Msg1, preamble, Msg3, MSGA, etc.) can be provided (or indicated). The UE may not perform data segmentation (e.g., RLC segmentation). It may be necessary to allocate (or schedule) a UL grant with a TB size that can accommodate the upper layer Service Data Unit (SDU). The (required) TB size can be the minimum size that the UE can use to perform (data) transmission. The TB size can be the preferred value that the UE can use to perform (data) transmission.

[0396] (Required) Repetition Count

[0397] Information related to the (required) number of repetitions for uplink transmission (e.g., Msg1, preamble, Msg3, MSGA, etc.) can be provided (or indicated).

[0398] Acknowledgment

[0399] Information for confirmation may be provided (or indicated). The confirmation may be used to confirm the reception of the (first) signaling. The confirmation may be used to confirm a previous reception (or transmission).

[0400] According to the research project on ambient IoT ([1] RP-234058), the ambient IoT UE has limited energy storage (or may even have no energy storage). Comparing the New Radio (NR) UE with the power consumption in mW (for example, the maximum UE transmission power of 23 dBm corresponds to 199.5 mW), the output power of the ambient IoT UE is typically from 1 μW to a few hundred μW. Considering the limited energy of the ambient IoT UE, this may not be a good choice for the ambient IoT UE that long-term monitors the PDCCH / PRDCH. In addition to the output power consumption, it may be necessary to enhance the power consumption caused by the PDCCH / PRDCH monitoring during the RA procedure (for example, during the first / second duration).

[0401] In traditional NR, the UE may receive paging to trigger the random access procedure. The UE transmits Msg1 at the selected PRACH occasion configured by the system information, and starts monitoring for the corresponding Msg2 at the earliest control resource set (CORESET) for the PDCCH after the transmission of Msg1. The CORESET is configured by the network in the RRC layer. In ambient IoT, it is assumed that there will be no occasion defined by the CORESET. After the ambient IoT UE receives the paging signaling to trigger the random access, the UE needs to decide when to monitor for the corresponding response to its Msg1 during the random access. Further considering the possibility that there will be multiple ambient IoT UEs performing random access using different time-domain resources in the same round (i.e., triggered by the same network signaling).

[0402] To solve the problem, a UE (e.g., an environmental IoT UE) may monitor PDCCH / PRDCH for DL / R2D transmissions (e.g., during an RA procedure) in a single or (finite / specific) duration (e.g., shorter than that of a traditional UE). The environmental IoT UE may monitor PDCCH / PRDCH for DL / R2D transmissions in a (finite / specific) duration. A traditional UE or a non-environmental IoT UE may monitor PDCCH / PRDCH for MSG2, MSGB, MSG4, and / or NW response / signals in another duration. Generally, (it is assumed / expected) that the other time duration is longer than the (finite / specific) duration. The UE may start monitoring PDCCH / PRDCH for DL / R2D transmissions at a specific timing. The network may transmit DL / R2D transmissions in a (finite / specific) duration. The DL / R2D transmissions may be the second transmission and / or the fourth transmission. The duration may be or include a first duration and / or a second duration. The (finite / specific) duration may start at a specific timing. The specific timing may be the start of the duration.

[0403] In one or more instances, the (finite / specific) duration may start at a specific timing after a (UL / D2R) transmission. The (UL / D2R) transmission may be or include the first transmission or the third transmission. The (UL / D2R) transmission may be the (UL / D2R) transmission that is first transmitted in a repeated and / or bundled form. The (UL / D2R) transmission may be the (UL / D2R) transmission that is last transmitted in a repeated and / or bundled form. If the UE performs repetition / bundling of the (UL / D2R) transmission, the specific timing may be derived / determined based on the first / initial one or the last one in the repetition / bundling of the (UL / D2R) transmission. The (UL / D2R) transmission may be a new / initial / first transmission in an RA procedure. The (UL / D2R) transmission may be a retransmission in an RA procedure. The duration may start in the symbol after a PDCCH / PRDCH timing and / or a UL transmission plus a time offset. The duration may start in the symbol at the end of a PDCCH / PRDCH timing and / or a (UL / D2R) transmission plus a time offset. The duration may start at the first PDCCH / PRDCH timing and / or in the symbol starting at the end of a (UL / D2R) transmission plus a time offset. The duration may start in the symbol after a PDCCH / PRDCH timing and / or at the end of a UL transmission plus a time offset. The duration may not start in the symbol after a (PDCCH / PRDCH timing and / or) corresponding (UL / D2R) transmission.

[0404] The UE may start listening to the PDCCH / PRDCH in the symbol(s) after adding a time offset to the (PDCCH / PRDCH time and / or) (UL / D2R) transmission. The UE may start listening to the PDCCH / PRDCH in the symbol(s) with a time offset added to the end of the PDCCH / PRDCH time and / or (UL / D2R) transmission. The UE may start listening to the PDCCH / PRDCH at the first PDCCH / PRDCH time and / or in the symbol(s) starting from the end of the (UL / D2R) transmission with a time offset added. The UE may start listening to the PDCCH / PRDCH in the symbol(s) after adding a time offset to the PDCCH / PRDCH time and / or after the end of the (UL / D2R) transmission.

[0405] The NW may start transmitting the PDCCH / PRDCH in the symbol(s) after adding a time offset to the (PDCCH / PRDCH time and / or) UL / D2R transmission. The NW may start transmitting the PDCCH / PRDCH in the symbol(s) with a time offset added to the end of the PDCCH / PRDCH time and / or (UL / D2R) transmission. The NW may start transmitting the PDCCH / PRDCH at the first PDCCH / PRDCH time and / or in the symbol(s) starting from the end of the (UL / D2R) transmission with a time offset added. The NW may start transmitting the PDCCH / PRDCH in the symbol(s) after adding a time offset to the PDCCH / PRDCH time and / or after the end of the (UL / D2R) transmission.

[0406] In one or more instances, the duration may start at a specific timing after receiving the NW signaling. The duration may start at the arrival time of the (next) NW signaling. The NW signaling may be or include the PRDCH, R2D signal / channel, paging, carrier (signal), and / or interrogation signal. The NW signaling may be the NW signaling received before the UE triggers the RA procedure. The NW signaling may be the NW signaling indicating that the UE triggers the RA procedure. The NW signaling may be the NW signaling received after the UE triggers the RA procedure. The NW signaling may be the NW signaling providing the UE with energy for, e.g., triggering the RA procedure, performing UL / D2R transmission, listening to the PDCCH / PRDCH, and / or receiving DL / R2D transmission. The NW signaling may be or include a second transmission. The duration may start in the symbol(s) after adding a time offset to the (PDCCH / PRDCH time and / or) received NW signaling. The duration may start in the symbol(s) with a time offset added to the end of the PDCCH / PRDCH time and / or NW signaling. The duration may start at the first PDCCH / PRDCH time and / or in the symbol(s) starting from the end of the NW signaling with a time offset added. The duration may start in the symbol(s) after adding a time offset to the PDCCH / PRDCH time and / or after the end of the NW signaling.

[0407] The UE may start monitoring the PDCCH / PRDCH in the symbol(s) after receiving the NW signaling plus a time offset at the (PDCCH / PRDCH time instant and / or). The UE may start monitoring the PDCCH / PRDCH in the symbol(s) at the PDCCH / PRDCH time instant and / or at the end of the NW signaling plus a time offset. The UE may start monitoring the PDCCH / PRDCH at the first PDCCH / PRDCH time instant and / or in the symbol(s) starting from the end of the NW signaling plus a time offset. The UE may start monitoring the PDCCH / PRDCH in the symbol(s) after the PDCCH / PRDCH time instant and / or at the end of the NW signaling plus a time offset. The UE may not start monitoring the PDCCH / PRDCH after the (corresponding) UL / D2R transmission.

[0408] The NW may start transmitting the PDCCH / PRDCH in the symbol(s) after transmitting the NW signaling plus a time offset at the (PDCCH / PRDCH time instant and / or). The NW may start transmitting the PDCCH / PRDCH in the symbol(s) at the PDCCH / PRDCH time instant and / or at the end of the NW signaling plus a time offset. The NW may start transmitting the PDCCH / PRDCH at the first PDCCH / PRDCH time instant and / or in the symbol(s) starting from the end of the NW signaling plus a time offset. The NW may start transmitting the PDCCH / PRDCH in the symbol(s) after the PDCCH / PRDCH time instant and / or at the end of the NW signaling plus a time offset. The NW may not start transmitting the PDCCH / PRDCH after receiving the UL / D2R transmission.

[0409] The UE may receive a first signaling to trigger a random access procedure and transmit a first transmission (e.g., Msg1) in the random access procedure. The UE may determine a start time (e.g., a third timing) for monitoring a second transmission (e.g., Msg2) based on: a first timing of receiving the first signaling and a time delay, or a second timing of transmitting the first transmission and a time delay. The time delay may be indicated by the network and / or derived or calculated by the UE. The first signaling may be a paging for ambient IoT. The first signaling is for more than one UE. The third timing for starting to monitor the second transmission may be common for more than one UE. In Figure 9 Examples are shown. More details are described below.

[0410] In one or more instances, the UE receives first signaling that triggers random access. The first signaling is paging for environmental IoT. The first signaling is for more than one UE. The first signaling indicates / triggers more than one UE to trigger / perform random access. The first signaling indicates at least the resources for the first transmission. The first signaling indicates the resources for the first transmission for more than one UE. The first signaling indicates one or more UE IDs, group IDs, and / or does not indicate IDs for more than one UE. In response to the first signaling, the UE triggers random access. The UE transmits the first transmission during random access. The first transmission includes at least a random ID. The UE determines a third timing based at least on a first timing and a first time delay. The first timing is the timing at which the first signaling ends. Preferably, in some embodiments, the first timing is the last moment of the first signaling or after the last moment of the first signaling. The first time delay is at least one of the following: a predefined value, indicated by the network (e.g., via the first signaling), derived or calculated by the UE, and / or derived or calculated by the UE based at least on the indication / configuration / resources provided by the first signaling and / or a predefined value. In response to transmitting the first transmission, the UE starts listening for a second transmission (e.g., on a channel) from the third timing. The third timing is the start time for listening for the second transmission (e.g., on a channel). The third timing is common for more than one UE. The third timing is determined based at least on the first timing plus the first time delay. Preferably, in some embodiments, the third timing is after the first timing plus the first time delay. The UE receives the second transmission (e.g., on a channel) when / after listening for the second transmission (e.g., on a channel). The second transmission corresponds to the first transmission. The second transmission includes at least a network response to at least the first transmission. The second transmission includes at least a random ID. The first signaling and / or the second transmission is received from a reader. The first transmission is transmitted to the reader. The reader is the network or another UE.

[0411] In one or more instances, the UE receives first signaling that triggers random access. The first signaling is paging for ambient IoT. The first signaling is for more than one UE. The first signaling indicates / triggers more than one UE to trigger / perform random access. The first signaling indicates at least the resources for at least a first transmission. The first signaling indicates the resources for a first transmission for more than one UE. The first signaling indicates one or more UE IDs, group IDs, and / or does not indicate IDs for more than one UE. In response to (receiving) the first signaling, the UE triggers random access. The UE transmits a first transmission during random access. The first transmission includes at least a random ID. The UE determines a third timing based at least on a second timing and a second time delay. The second timing is the timing at which the first transmission ends. Preferably, in some embodiments, the second timing is the last moment of the first transmission or after the last moment of the first transmission. The second time delay is derived or calculated by the UE. The second time delay is derived or calculated based on at least one of the following: indications / configurations / resources provided by the first signaling and / or predefined values, and / or the time correlation between the first transmission and a second transmission. In response to transmitting the first transmission, the UE starts listening for a second transmission (e.g., on a channel) from the third timing. The third timing is the start time for listening for the second transmission (e.g., on a channel). The third timing is common to more than one UE. The third timing is determined based at least on the second timing plus the second time delay. Preferably, in some embodiments, the third timing is after the second timing plus the second time delay. The UE receives the second transmission (e.g., on a channel) when / after listening for the second transmission (e.g., on a channel). The second transmission corresponds to at least the first transmission. The second transmission includes at least a network response to at least the first transmission. The second transmission includes at least a random ID. The first signaling and / or the second transmission is received from a reader. The first transmission is transmitted to the reader. The reader is a network or another UE.

[0412] In one or more instances, a reader, for example, transmits first signaling that triggers random access (procedure) to more than one UE. The first signaling is paging for ambient IoT. The first signaling indicates / triggers more than one UE to trigger / perform random access (procedure). The first signaling indicates at least the resources of at least the first transmission. The first signaling indicates the resources of the first transmission for more than one UE. The first signaling indicates one or more UE IDs, group IDs, and / or does not indicate IDs for more than one UE. In response to (transmitting) the first signaling, the reader receives at least one first transmission from at least one UE among more than one UE. The first transmission includes at least a random ID of at least one UE. In response to (receiving) at least one first transmission, the reader transmits at least one second transmission for at least one UE after a third timing. The third timing is common to more than one UE. The reader determines the third timing based at least on a first timing and a first time delay. The first timing is the timing when the first signaling ends. Preferably, in some embodiments, the first timing is the last moment of the first signaling or after the last moment of the first signaling. The first time delay is at least one of the following: a predefined value, indicated by the reader (e.g., via the first signaling), derived or calculated by the UE, and / or derived or calculated by the UE based at least on the indication / configuration / resources provided by the first signaling and / or the predefined value. The third timing is the start time for transmitting the second transmission. The third timing is common to more than one UE. The third timing is determined based at least on the first timing plus the first time delay. Preferably, in some embodiments, the third timing is after the first timing plus the first time delay. The second transmission corresponds to at least the first transmission. The second transmission includes at least a network response to at least the first transmission. The second transmission includes at least a random ID of at least one UE. The first signaling and the second transmission are transmitted to at least one UE and / or more than one UE. The first transmission is received from at least one UE and / or more than one UE. The reader is a network or another UE.

[0413] Parts or all of the above instances can be combined.

[0414] Throughout this disclosure, the time offset and / or the time difference can be the round trip time (RTT) and / or the time delay. A specific timing and / or a time offset can be indicated, (pre)defined, and / or (pre)configured by the network (e.g., via the network signaling as described above). A specific timing and / or a time offset can be specified in a specification (e.g., TS 38.213). A specific timing and / or a time offset can be associated with the indication and / or configuration provided by the network. A specific timing and / or a time offset can be calculated and / or derived by the UE. For multiple or a group of ambient IoT UEs (which receive the same NW signal), the specific timing and / or the time offset can be common. The specific timing and / or the time offset can be dedicated to / specific to each ambient IoT UE.

[0415] The UE may listen to the PDCCH / PRDCH / channel during a (finite / specific) duration, e.g., in response to the UE performing a corresponding UL / D2R transmission (e.g., the first transmission). The UE may receive a DL / R2D transmission on the PDCCH / PRDCH / channel or receive a DL / R2D transmission scheduled by the PDCCH / PRDCH / channel during the duration. The UE may not listen to the PDCCH / PRDCH / channel after a (corresponding) UL / D2R transmission. The UE may not listen to the PDCCH / PRDCH / channel before a specific timing. The UE may not receive a DL / R2D transmission outside the duration. The UE may not receive a DL / R2D transmission before a specific timing.

[0416] Alternatively and / or additionally, the UE may start a first timer, a second timer, and / or a third timer at a specific timing. The values of the first timer, the second timer, and / or the third timer of the environmental IoT UE may be shorter than those of a traditional UE. The values of the first timer, the second timer, and / or the third timer for the environmental IoT UE may be fixed. The values of the first timer, the second timer, and / or the third timer for the environmental IoT UE may be the shortest configurable values of the timer. When the first timer, the second timer, and / or the third timer is running, the UE may listen to the PDCCH / PRDCH. When the first timer, the second timer, and / or the third timer is not running, the UE may not listen to the PDCCH / PRDCH (e.g., for the second transmission or the fourth transmission). When the first timer, the second timer, and / or the third timer is not running, the NW may not transmit a DL / R2D transmission or response.

[0417] In one or more instances, the UE may transmit Msg1 to the network. After transmitting Msg1 or in response to transmitting Msg1, the UE may start a response window (e.g., ra-ResponseWindow) at a specific timing after the end of Msg1 transmission. The specific timing may be the first PDCCH / PRDCH moment starting from the end of Msg1 transmission plus a time offset. The specific timing may be the arrival time of the next NW signaling. The specific timing may be configured and / or indicated by the network (e.g., in the NW signaling). While the response window is in operation (or during the response window), the UE may monitor the PDCCH / PRDCH. While the response window is in operation (or during the response window), the UE may receive a RAR from the network. In response to (receiving) the RAR, the UE may transmit Msg3 to the network. After transmitting Msg3 or in response to transmitting Msg3, the UE may start a contention resolution timer (e.g., ra-ContentionResolutionTimer) at a specific timing after the end of Msg3 transmission. The specific timing may be the first symbol after the end of Msg3 transmission plus a time offset. The specific timing may be the arrival time of the next NW signaling. The specific timing may be configured and / or indicated by the network (e.g., in the NW signaling). While the contention resolution timer is in operation, the UE may monitor the PDCCH / PRDCH. While the contention resolution timer is in operation, the UE may receive Msg4 from the network.

[0418] In one or more instances, the UE may transmit MSGA to the network. After transmitting MSGA or in response to transmitting MSGA, the UE may start a response window (e.g., msgB-ResponseWindow) at a specific timing after the end of MSGA transmission. The specific timing may be the PDCCH / PRDCH moment of the end of MSGA transmission plus a time offset. The specific timing may be the arrival time of the next NW signaling. The specific timing may be configured and / or indicated by the network (e.g., in the NW signaling). While the response window is in operation (or during the response window), the UE may monitor the PDCCH / PRDCH. While the response window is in operation (or during the response window), the UE may receive MSGB from the network.

[0419] Alternatively and / or additionally, in response to a UL / D2R transmission, the UE may start a first timer, a second timer, and / or a third timer. In response to the UL / D2R transmission and / or the start of the first timer, the second timer, and / or the third timer, the UE may start a fourth timer. The fourth timer may be expressed as a time offset. The fourth timer may be a delay timer, a prohibition timer, and / or an inactivity timer. The fourth timer may end at a specific occasion. The fourth timer may expire at a specific occasion. When / if (at least) the fourth timer is running, the UE may not monitor the PDCCH / PRDCH. When the first timer, the second timer, and / or the third timer are running, and when / if (at least) the fourth timer is not running, the UE may monitor the PDCCH / PRDCH. When the fourth timer is running, the NW may not transmit a DL / R2D transmission or response.

[0420] In one or more instances, a UE may transmit Msg1 to the network. After transmitting Msg1 or in response to transmitting Msg1, the UE may start a response window (e.g., ra-ResponseWindow) at the first PDCCH / PRDCH moment starting from the end of the Msg1 transmission. The UE may start a fourth timer with a first value (e.g., a first time length value or a first value of Transmission Time Interval (TTI) / moment / symbol / millisecond) at the first PDCCH / PRDCH moment starting from the end of the Msg1 transmission. The UE may start the fourth timer at an opportunity configured and / or indicated by the network (e.g., in NW signaling). When the response window is in operation (or during the response window) and the fourth timer is not in operation, the UE may listen for PDCCH / PRDCH. When the fourth timer is not in operation, the UE may listen for PDCCH / PRDCH during the response window. The UE may receive a RAR from the network after the fourth timer expires. In response to (receiving) the RAR, the UE may transmit Msg3 to the network. After transmitting Msg3 or in response to transmitting Msg3, the UE may start a contention resolution timer (e.g., ra-ContentionResolutionTimer) at the first symbol after the end of the Msg3 transmission. The UE may start a fourth timer with a second value (e.g., a second time length value or a second value of TTI / moment / symbol / millisecond) at the first PDCCH / PRDCH moment starting from the end of the Msg3 transmission. The UE may start the fourth timer at an opportunity configured and / or indicated by the network (e.g., in NW signaling). When the contention resolution timer is in operation and the fourth timer is not in operation, the UE may listen for PDCCH / PRDCH. The UE may receive Msg4 from the network after the fourth timer expires. The first value and the second value may be the same. The first value and the second value may be different. The first value and the second value may be configured, indicated, and / or provided by the network. The first value and the second value may be derived by the UE.

[0421] In one or more instances, the UE may transmit Msg1 to the network. After transmitting Msg1 or in response to transmitting Msg1, the UE may start a response window (e.g., ra-ResponseWindow) at the first PDCCH / PRDCH moment starting from the end of the Msg1 transmission. The UE may start a fourth timer with a first value (e.g., a first time length value or a first value in terms of TTI / moment / symbol / millisecond) at the first PDCCH / PRDCH moment starting from the end of the Msg1 transmission. The UE may start the fourth timer at an opportunity configured and / or indicated by the network (e.g., in NW signaling). When the response window is in operation (or during the response window) and the fourth timer is not in operation, the UE may listen for PDCCH / PRDCH. When the fourth timer is not in operation, the UE may listen for PDCCH / PRDCH during the response window. The UE may receive a RAR from the network after the fourth timer expires. In response to (receiving) the RAR, the UE may transmit Msg3 to the network. After transmitting Msg3 or in response to transmitting Msg3, the UE may start a contention resolution timer (e.g., ra-ContentionResolutionTimer) at the first symbol after the end of the Msg3 transmission. The UE may start another fourth timer with a second value (e.g., a second time length value or a second value in terms of TTI / moment / symbol / millisecond) at the first PDCCH / PRDCH moment starting from the end of the Msg3 transmission. The UE may start the other / another fourth timer at an opportunity configured and / or indicated by the network (e.g., in NW signaling). When the contention resolution timer is in operation (or during the response window) and the other fourth timer is not in operation, the UE may listen for PDCCH / PRDCH. The UE may receive Msg4 from the network after the other fourth timer expires. The first value and the second value may be the same. The first value and the second value may be different. The first value and the second value may be configured, indicated, and / or provided by the network. The first value and the second value may be derived by the UE. The fourth timer and the other / another fourth timer may be the same timer. The fourth timer and the other / another fourth timer may be different timers.

[0422] In one or more instances, a UE may transmit an MSGA to the network. After transmitting the MSGA or in response to transmitting the MSGA, the UE may start a response window (e.g., msgB-ResponseWindow) at a PDCCH / PRDCH time instance after the MSGA transmission. The UE may start a fourth timer at a PDCCH / PRDCH time instance after the MSGA transmission. The UE may start the fourth timer at an opportunity configured and / or indicated by the network (e.g., in NW signaling). When the response window is in operation (or during the response window) and the fourth timer is not in operation, the UE may listen for the PDCCH / PRDCH. When the fourth timer is not in operation, the UE may listen for the PDCCH / PRDCH during the response window. The UE may receive an MSGB from the network after the fourth timer expires.

[0423] In one or more instances, a (finite / specific) duration is a TTI / time instance. Preferably, in some embodiments, the (finite / specific) duration may be / mean a specific opportunity. Preferably, in some embodiments, the specific opportunity may be a TTI / time instance.

[0424] Preferably, in some embodiments, when the UE performs a UL / D2R transmission, the UE may listen for the PDCCH / PRDCH at a specific opportunity for a corresponding DL / R2D transmission (for reception). Preferably, in some embodiments, when the NW receives a UL / D2R transmission, the NW may transmit the PDCCH / PRDCH at a specific opportunity for a corresponding DL / R2D transmission (for transmission).

[0425] Preferably, in some embodiments, the UE may derive / determine the specific opportunity based on the transmission opportunity of a UL / D2R transmission (e.g., a first transmission). Preferably, in some embodiments, the UE may derive / determine the specific opportunity based on a timing association / correspondence (e.g., a time difference) with the transmission opportunity of a UL / D2R transmission (e.g., a first transmission). Preferably, in some embodiments, the timing association / correspondence may be configured, indicated, and / or provided by the network (e.g., in NW signaling, via information in NW signaling). Preferably and / or alternatively, the timing association / correspondence may be predefined / fixed / specified / preconfigured.

[0426] Preferably, in some embodiments, if the UE performs a repetition / bundling of UL transmissions, the specific opportunity may be derived / determined based on the first / initial or last one among the repetitions / bundlings of the UL transmission.

[0427] Preferably, in some embodiments, a specific timing may be later than or equal to the transmission timing of the UL transmission plus a time offset (e.g., the time offset described above). Preferably, in some embodiments, for different types of UL transmissions, the time offset may be the same or different. Preferably, in some embodiments, for different types of UL transmissions, the timing correlation / correspondence between the transmission timing of the UL transmission and the corresponding specific timing may be the same or different. Preferably, in some embodiments, for different types of UL transmissions, the resource correlation / correspondence between the transmission resources of the UL transmission and the corresponding one or more specific resources may be the same or different.

[0428] In one or more instances, when the UE performs UL / D2R transmission, the UE may monitor the PDCCH / PRDCH on one or more specific resources (e.g., PDCCH / PRDCH resources, candidate PDCCH / PRDCH resources) at a specific timing or for a (finite / specific) duration. Preferably, in some embodiments, when the NW receives the UL / D2R transmission, the NW may transmit the PDCCH / PRDCH for the corresponding DL transmission on one of the one or more specific resources at a specific timing or for a (finite / specific) duration.

[0429] Preferably, in some embodiments, the UE may derive / determine one or more specific resources based on the resource correlation / correspondence with the transmission resources of the UL transmission (e.g., resource correlation / correspondence in the frequency domain, time domain, and / or code domain). Preferably, in some embodiments, the resource correlation / correspondence may be configured, indicated, and / or provided by the network (e.g., in NW signaling). Preferably and / or alternatively, the resource correlation / correspondence may be predefined / fixed / specified / preconfigured.

[0430] Preferably, in some embodiments, one or more specific resources may be (or include) a specific resource. In this case, the resource correlation / correspondence between the PDCCH / PRDCH resource and the transmission resources of the UL / D2R transmission (e.g., PRACH resource, PUSCH resource, PDRCH resource) may be one-to-one.

[0431] Preferably, in some embodiments, the transmission resources of the UL transmission may be / mean / include the lowest frequency unit of the transmission resources of the UL transmission (e.g., the lowest Physical Resource Block (PRB), the lowest Resource Element (RE), or the lowest subcarrier).

[0432] The above examples, methods, concepts, and / or embodiments that can be combined for PDCCH / PRDCH / channel monitoring. Preferably, in some embodiments, for different types of UL transmissions, different examples, methods, concepts, and / or embodiments for PDCCH / PRDCH monitoring can be correspondingly applied. Different types of UL / D2R transmissions can be distinguished based on the first information. Different types of UL / D2R transmissions can be associated with different UE types, power levels, data types, data sizes, UE IDs, UE group IDs, reasons, locations, and / or repetition counts.

[0433] After the UE triggers the RA procedure and / or performs UL transmission, since there may be conflicts when multiple UEs perform the RA procedure, the UE needs to determine the contention resolution of the RA procedure. For example, whether the UL transmission is successfully received by the network and whether the RA procedure can be considered successfully completed. Based on the current NR MAC specification TS 38.321, the UE determines the contention resolution in two cases: one is the case where the Cell Radio Network Temporary Identifier (C-RNTI) MAC CE is included in Msg3 or MSGA, and the other is the case where the CCCH SDU includes Msg3 or MSGA. However, for the environmental IoT UE, both cases may not apply (because the C-RNTI MAC CE or CCCH SDU may not exist in Msg3 or MSGA), or the determination of the contention resolution for at least one of the cases may not apply to the environmental IoT UE.

[0434] To solve the problem, the UE can receive PDCCH / PRDCH (command / transmission) as an NW response for UL / D2R transmission in the RA procedure. In response to transmitting the first transmission and / or the third transmission, the UE can receive PDCCH / PRDCH transmission without PDSCH transmission. The UE may not receive PDSCH (transmission), payload, MAC PDU, and / or TB. The UE may not receive MSGB and / or Msg4 (e.g., receive MSGB and / or Msg4 via PDSCH). The UE can receive PDCCH / PRDCH transmission as MSGB and / or Msg4. The PDCCH / PRDCH transmission can be addressed to a Random Access Radio Network Temporary Identifier (RA-RNTI), MSGB-RNTI, and / or Temporary Cell Radio Network Temporary Identifier (TC-RNTI). The PDCCH / PRDCH transmission can be scrambled with the UE ID. The PDCCH / PRDCH transmission can be scrambled with a part of the UE ID, e.g., the first x bits of the UE ID (e.g., x Least Significant Bit (LSB) bits or x Most Significant Bit (MSB) bits). The PDCCH / PRDCH transmission can indicate the UE ID. The PDCCH / PRDCH transmission can indicate a part of the UE ID, e.g., the first x bits of the UE ID (e.g., x LSB bits or x MSB bits). The PDCCH / PRDCH transmission can include a field indication of the UE ID. The PDCCH / PRDCH transmission can include a field indication of a part of the UE ID, e.g., the first x bits of the UE ID (e.g., x LSB bits or x MSB bits). The UE can regard the PDCCH / PRDCH transmission containing or scrambled with the UE ID (or a part thereof) as MSGB and / or Msg4.

[0435] Preferably, in some embodiments, the PDCCH / PRDCH transmission scrambled with the UE ID can mean / include that the PDCCH / PRDCH contains downlink control information, and the Cyclic Redundancy Check (CRC) bits of the downlink control information are scrambled with a part of the UE ID.

[0436] Preferably, in some embodiments, the PDCCH / PRDCH transmission indicated by a field including (a part of) the UE ID may mean / include that the PDCCH / PRDCH contains downlink control information, and the downlink control information includes a field indication of (a part of) the UE ID.

[0437] For example, the UE may include its UE ID in Msg3 and / or MSGA (e.g., via an RRC message, via a MAC CE). The UE may transmit Msg3 / MSGA with the UE ID. In response to transmitting Msg3 / MSGA, the UE may monitor the PDCCH / PRDCH (e.g., based on the above examples) and receive a PDCCH / PRDCH transmission. If (at least) or based on one or more combinations of the following conditions being met, the UE may consider contention resolution successful, consider RAR reception successful, and / or consider the RA procedure successfully completed:

[0438] - Receiving a notification of the reception of a PDCCH / PRDCH transmission from a lower layer (for a Special Cell (SpCell));

[0439] - The PDCCH / PRDCH transmission is addressed to the UE's RA-RNTI;

[0440] - The PDCCH / PRDCH transmission is addressed to the UE's TC-RNTI;

[0441] - The PDCCH / PRDCH transmission is addressed to the UE's MSGB-RNTI;

[0442] - The PDCCH / PRDCH transmission is scrambled with (a part of) the UE ID;

[0443] - The PDCCH / PRDCH transmission indicates (a part of) the UE ID;

[0444] - The PDCCH / PRDCH transmission includes (a part of) the UE ID;

[0445] - The indication in the PDCCH / PRDCH transmission matches (a part of) the UE ID;

[0446] - The PDCCH / PRDCH transmission indicates the RAPID, e.g., where the RAPID is transmitted via a first transmission;

[0447] - The UE is an environmental IoT UE;

[0448] - The RA procedure is initiated for environmental IoT; and / or

[0449] The - RA procedure is triggered by NW signaling (e.g., PRDCH signal, R2D signal / channel, carrier, interrogation signal).

[0450] The UE may receive configurations related to ambient IoT. The UE may receive RA configuration and / or RA resources. The RA resources may include BWP, RA resource / configuration group, RA preamble (group), PDRCH occasion, RACH occasion, and / or PUSCH occasion. The UE may receive the above configurations and / or resources via network signaling (as described above).

[0451] The above examples, methods, concepts, and / or embodiments for UL / D2R transmission, DL / R2D reception / transmission, PDCCH / PRDCH / channel monitoring, and / or contention resolution may be combined.

[0452] Throughout this disclosure, the following may be interchangeable: RACH occasion, PRACH occasion.

[0453] Throughout this disclosure, "RA procedure" may be replaced by "(initial) access procedure". The "(initial) access procedure" may be contention - based or contention - free.

[0454] Throughout this disclosure, "RA procedure" may be changed / represented / replaced by a UE (or ambient IoT) data transmission procedure, a UE (or ambient IoT) response procedure, or a UE (or ambient IoT) reporting procedure.

[0455] Throughout this disclosure, "RA" may be replaced by "access".

[0456] Throughout this disclosure, "MSGA" or "MSGA payload" may be replaced by "PDRCH data / transmission / signaling", "(uplink / D2R) data", and / or "(uplink / D2R) signaling".

[0457] Throughout this disclosure, "Msg1" may be replaced by "RA preamble".

[0458] Throughout this disclosure, "PRACH" may be replaced by "PDRCH", "channel for random access", or "PRACH for ambient IoT".

[0459] Throughout this disclosure, "PUSCH" may be replaced by "PDRCH", "uplink shared channel", or "PUSCH for ambient IoT", or "physical channel for D2R (data / control) transmission".

[0460] Throughout this disclosure, "PDCCH" may be replaced by "PRDCH", "downlink control channel", "downlink control information", or "PDCCH for ambient IoT", or "physical channel for R2D (data / control) transmission".

[0461] Throughout this disclosure, "PDSCH" may be replaced by "PRDCH", "downlink shared channel", or "PDSCH for ambient IoT", or "physical channel for R2D (data / control) transmission".

[0462] Throughout this disclosure, "BWP" may be replaced by "system bandwidth", "channel bandwidth", "transmission bandwidth", "occupied bandwidth", "sub-band of the cell / sub-band in the cell", or "subset of the total cell bandwidth of the cell".

[0463] Throughout this disclosure, "RACH" may be replaced by "PDRCH", "access channel", or "RACH for ambient IoT".

[0464] Throughout this disclosure, "cell" may be replaced by "intermediate node".

[0465] Throughout this disclosure, the network (node) may be changed / represented / replaced by an intermediate node.

[0466] Throughout this disclosure, "duration" may be replaced by "time period".

[0467] Throughout this disclosure, "CCCH message" may be replaced by "CCCH SDU".

[0468] Throughout this disclosure, "PDRCH" may be replaced by "physical channel for D2R (data) transmission".

[0469] Throughout this disclosure, "PRDCH" may be replaced by "physical channel for R2D (data) transmission".

[0470] Throughout this disclosure, the (data and / or signaling) transmission from the reader to the device / UE may be via PRDCH. Throughout this disclosure, the (data and / or signaling) transmission from the device / UE to the reader may be via PDRCH.

[0471] Throughout this disclosure, "downlink control information" may be replaced by R2D control information.

[0472] Throughout this disclosure, "uplink control information" may be replaced by D2R control information.

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

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

[0475] Throughout this disclosure, the UE may be an ambient IoT device / UE. The UE may be a device for ambient IoT. The UE may be a device having the capability of ambient IoT. The UE may be an NR device. The UE may be a Long Term Evolution (LTE) device. The UE may be an IoT device. The UE may be a wearable device. The UE may be a sensor. The UE may be a fixed device. The UE may be a tag. Throughout this disclosure, the following may be interchangeable: (ambient IoT) UE, (ambient IoT) device.

[0476] The UE may not be a traditional UE. A traditional UE may be a non-ambient IoT device / UE. A traditional UE may perform different (RA and / or initial access) procedures from those of an ambient IoT UE. The UE may be a traditional UE having the capability of performing ambient IoT procedures. Throughout this disclosure, the following may be interchangeable: normal UE, traditional UE. An ambient IoT UE may have the capability of ambient IoT. A traditional UE may or may not have the capability of ambient IoT procedures.

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

[0478] Various examples and embodiments of the present invention are described below. For the methods, alternatives, concepts, examples, and embodiments detailed above and herein, the following aspects and embodiments are possible.

[0479] Reference Figure 10 , by this and other concepts, systems, and methods of the present invention, a method 1000 for a UE in a wireless communication system includes: initiating an RA procedure (step 1002); transmitting a message containing the identification of the UE in the RA procedure (step 1004); receiving a channel transmission in response to transmitting the message (step 1006); and determining that the RA procedure is successfully completed (step 1008) based on the channel transmission scrambled with the identification of the UE or the channel transmission indicating the identification of the UE.

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

[0481] In various embodiments, the message is Msg1, Msg3, or MSGA.

[0482] In various embodiments, the message does not include a CCCH message and / or a C-RNTI.

[0483] In various embodiments, the identification of the UE is the ue-Identity and / or the UE contention resolution ID provided in the MAC CE.

[0484] In various embodiments, the identification of the UE is provided in the MAC CE or is the MAC CE.

[0485] In various embodiments, the channel transmission is addressed to a TC-RNTI or a MSGB-RNTI.

[0486] In various embodiments, the TC-RNTI is provided in the RAR or MSGB from the NW.

[0487] In various embodiments, the MSGB-RNTI is calculated by the UE.

[0488] Return reference Figure 3 and 4 and, in one or more embodiments, from the perspective of the UE in a wireless communication system, the apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) initiate an RA procedure; (ii) transmit a message including the identification of the UE in the RA procedure; (iii) receive a channel transmission in response to transmitting the message; and (iv) determine that the RA procedure is successfully completed based on the channel transmission scrambled with the identification of the UE or the channel transmission indicating the identification of the UE. In addition, the CPU 308 can execute the program code 312 to perform all the described actions, steps, and methods described above, below, or herein.

[0489] Reference Figure 11 and, by this and other concepts, systems, and methods of the present invention, a method 1010 for a UE in a wireless communication system includes: initiating an RA procedure (step 1012); transmitting a first message including the identification of the UE in the RA procedure (step 1014); receiving a second message in response to transmitting the first message (step 1016); and determining that the RA procedure is successfully completed based on the second message indicating or including the identification of the UE (step 1018).

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

[0491] In various embodiments, in response to (receiving) a first signaling, for example, paging for ambient IoT, the UE initiates an RA procedure.

[0492] In various embodiments, the first message is Msg1, Msg3, or MSGA.

[0493] In various embodiments, the first message does not include a CCCH message and / or a C-RNTI.

[0494] In various embodiments, the identification of the UE is a random number provided in the MAC CE (e.g., generated by the UE), ue-Identity, and / or UE contention resolution ID.

[0495] In various embodiments, the identification of the UE is provided in the MAC CE or is the MAC CE.

[0496] In various embodiments, the second message is transmitted via the PDSCH or the PRDCH.

[0497] In various embodiments, the second message is in response to the first message.

[0498] In various embodiments, the second message is Msg4 or MSGB.

[0499] In various embodiments, the second message includes a UE contention resolution ID MAC CE.

[0500] In various embodiments, the UE contention resolution ID MAC CE matches the identification of the UE.

[0501] In various embodiments, the second message does not include or indicate a Timing Advance Command (TAC), C-RNTI, ChannelAccess-CPext, Transmitter Power Control (TPC) command, an indication for Hybrid Automatic Repeat Request (HARQ) feedback, and / or an indication for PUCCH resources.

[0502] In various embodiments, the UE does not apply a Timing Advance (TA) value in response to (receiving) the second message.

[0503] In various embodiments, the UE does not set a C-RNTI in response to (receiving) the second message.

[0504] Return reference Figure 3 and 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 the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) initiate a RA procedure; (ii) transmit a first message including the identification of the UE in the RA procedure; (iii) receive a second message in response to transmitting the first message; and (iv) determine that the RA procedure is successfully completed based on the second message indicating or including the identification of the UE. In addition, the CPU 308 can execute the program code 312 to perform all the described actions, steps, and methods described above, below, or herein.

[0505] Reference Figure 12 , by this and other concepts, systems, and methods of the present invention, method 1020 for a UE in a wireless communication system includes: receiving signaling from the NW (step 1022); initiating a RA procedure in response to (receiving) the signaling (step 1024); transmitting a first message (step 1026); starting a first timer at a specific timing (step 1028); listening to a channel while the first timer is running (step 1030); and receiving a second message on the channel in response to transmitting the first message (step 1032).

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

[0507] In various embodiments, the signaling is a carrier and / or interrogation signal for ambient IoT.

[0508] In various embodiments, the first message is Msg1, Msg3, or MSGA.

[0509] In various embodiments, the first timer is a RA response window, a MSGB response window, or a contention resolution timer.

[0510] In various embodiments, the specific timing is the end of the first transmission plus a time offset, the end of the signaling reception plus a time offset, or the arrival time of another signaling.

[0511] In various embodiments, the second message is Msg2, Msg4, or MSGB.

[0512] In various embodiments, the time offset is related to the characteristics of the UE.

[0513] Return reference Figure 3 and 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 the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) receive signaling from the NW; (ii) initiate a RA procedure in response to the (received) signaling; (iii) transmit a first message; (iv) start a first timer at a specific timing; (v) listen to a channel while the first timer is running; and (vi) receive a second message on the channel in response to transmitting the first message. In addition, the CPU 308 can execute the program code 312 to perform all the described actions, steps, and methods described above, below, or elsewhere herein.

[0514] Return reference Figure 3 and 4 , in one or more embodiments, from the perspective of the NW in a wireless communication system, apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) transmit signaling to the UE; (ii) receive a first message from the UE; (iii) transmit a second message to the UE on the channel in response to receiving the first message. In addition, the CPU 308 can execute the program code 312 to perform all the described actions, steps, and methods described above, below, or elsewhere herein.

[0515] Reference Figure 13 , by this and other concepts, systems, and methods of the present invention, a method 1040 for a UE in a wireless communication system includes: receiving first signaling that triggers a random access procedure (step 1042); triggering a random access procedure in response to the (received) first signaling (step 1044); transmitting a first transmission during the random access procedure (step 1046); determining a third timing based at least on a first timing and a first time delay, where the first timing is the timing when the first signaling ends (step 1048); and listening for a second transmission starting from the third timing in response to transmitting the first transmission (step 1050).

[0516] In various embodiments, the first time delay is at least one of the following: a predefined value, indicated by the network, derived or calculated by the UE, and / or derived or calculated by the UE based at least on an indication provided by the first signaling and / or a predefined value.

[0517] In various embodiments, the first time delay is a predefined value or indicated by the network.

[0518] In various embodiments, the first time delay is derived or calculated by the UE, for example, based at least on an indication provided by the first signaling and / or a predefined value.

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

[0520] In various embodiments, the first signaling is for more than one UE.

[0521] In various embodiments, the first signaling triggers and / or indicates more than one UE to perform a random access procedure.

[0522] In various embodiments, the first signaling at least indicates the resources for the first transmission.

[0523] In various embodiments, the third timing is common for more than one UE.

[0524] In various embodiments, the third timing is for listening for the start time of the second transmission.

[0525] In various embodiments, the third timing is determined at least based on the first timing plus the first time delay, and / or the third timing is after the first timing plus the first time delay.

[0526] In various embodiments, the first timing is the last moment of the first signaling.

[0527] In various embodiments, the first timing is the first moment after the end of the first signaling.

[0528] In various embodiments, the first signaling and / or the second transmission is received from the reader.

[0529] In various embodiments, the first transmission is sent to the reader.

[0530] In various embodiments, the reader is a network or another UE.

[0531] In various embodiments, the UE receives the second transmission after the third timing.

[0532] In various embodiments, the first transmission at least includes the ID of the UE, for example, a random ID.

[0533] In various embodiments, the second transmission at least includes the ID of the UE.

[0534] Return reference Figure 3 and 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 the memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) receive a first signaling that triggers a random access procedure; (ii) trigger a random access procedure in response to (receiving) the first signaling; (iii) transmit a first transmission during the random access procedure; (iv) determine a third timing based at least on a first timing and a first time delay, where the first timing is the timing when the first signaling ends; and (v) start listening for a second transmission from the third timing in response to transmitting the first transmission. Additionally, the CPU 308 can execute the program code 312 to perform all the described actions, steps, and methods described above, below, or herein.

[0535] Reference Figure 14 , by this and other concepts, systems, and methods of the present invention, a method 1060 for a UE in a wireless communication system includes: receiving a first signaling that triggers a random access procedure (step 1062); triggering a random access procedure in response to (receiving) the first signaling (step 1064); transmitting a first transmission during the random access procedure (step 1066); determining a third timing based at least on a second timing and a second time delay, where the second timing is the timing when the first transmission ends, and the second time delay is derived or calculated by the UE (step 1068); and starting to listen for a second transmission from the third timing in response to transmitting the first transmission (step 1070).

[0536] In various embodiments, the second time delay is derived or calculated (e.g., by the UE) based at least on an indication provided by the first signaling and / or a predefined value.

[0537] In various embodiments, the second time delay is derived or calculated (e.g., by the UE) based on the time correlation between the first transmission and the second transmission.

[0538] In various embodiments, the first signaling is a paging for environmental IoT.

[0539] In various embodiments, the first signaling is for more than one UE.

[0540] In various embodiments, the first signaling at least indicates the resources of the first transmission.

[0541] In various embodiments, the third timing is common to more than one UE.

[0542] In various embodiments, the third timing is the start time for listening for the second transmission.

[0543] In various embodiments, the third timing is determined based at least on the second timing plus a second time delay, and / or the third timing is after the second timing plus the second time delay.

[0544] In various embodiments, the second timing is the last moment of the first transmission.

[0545] In various embodiments, the second timing is the first moment after the end of the first transmission.

[0546] In various embodiments, a first signaling and / or a second transmission are received from a reader.

[0547] In various embodiments, a first transmission is sent to a reader.

[0548] In various embodiments, the reader is a network or another UE.

[0549] In various embodiments, the UE receives a second transmission after the third timing.

[0550] In various embodiments, the first transmission includes at least the ID of the UE, e.g., a random ID.

[0551] In various embodiments, the second transmission includes at least the ID of the UE.

[0552] Return reference Figure 3 And 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 memory 310 of a transmitter. CPU 308 can execute program code 312 to: (i) receive a first signaling that triggers a random access procedure; (ii) in response to (receiving) the first signaling, trigger the random access procedure; (iii) transmit a first transmission during the random access procedure; (iv) determine a third timing based at least on a second timing and a second time delay, where the second timing is the timing of the end of the first transmission, and the second time delay is derived or calculated by the UE; and (v) in response to transmitting the first transmission, start listening for a second transmission from the third timing. Additionally, CPU 308 can execute program code 312 to perform all the described actions, steps, and methods described above, below, or herein.

[0553] Reference Figure 15, by this and other concepts, systems, and methods of the present invention, a method 1080 for a reader in a wireless communication system includes: transmitting first signaling for triggering one or more random access procedures for more than one UE (step 1082); in response to (transmitting) the first signaling, receiving at least one first transmission from at least one UE among the more than one UE (step 1084); and in response to (receiving) the at least one first transmission, transmitting at least one second transmission for at least one UE after or at a third timing, where the third timing is common to the more than one UE (step 1086).

[0554] In various embodiments, the third timing is determined based at least on a first timing and a first time delay, where the first timing is the timing when the first signaling ends.

[0555] In various embodiments, the first timing is the last moment of the first signaling.

[0556] In various embodiments, the first timing is the first moment after the first signaling ends.

[0557] In various embodiments, the first time delay is at least one of the following: a predefined value, indicated by the reader, and / or derived or calculated by the reader based at least on an indication provided by the first signaling and / or a predefined value.

[0558] In various embodiments, the first time delay is a predefined value or indicated by the reader.

[0559] In various embodiments, the first time delay is derived or calculated by the UE, for example, based at least on an indication provided by the first signaling and / or a predefined value.

[0560] In various embodiments, the third timing is determined based at least on the first timing plus the first time delay, and / or the third timing is after the first timing plus the first time delay.

[0561] In various embodiments, the third timing is the start time for transmitting at least one second transmission.

[0562] In various embodiments, the first signaling is a paging for environmental IoT.

[0563] In various embodiments, the first signaling triggers and / or indicates more than one UE to perform a random access procedure.

[0564] In various embodiments, the first signaling indicates at least one or more resources for at least one first transmission.

[0565] In various embodiments, the reader is a network or another UE.

[0566] In various embodiments, at least one first transmission includes at least the ID of the UE, e.g., a random ID.

[0567] In various embodiments, at least one second transmission includes at least the ID of the UE.

[0568] Return reference Figure 3 and 4 , in one or more embodiments, from the perspective of a reader in a wireless communication system, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) transmit first signaling for triggering one or more random access procedures for more than one UE; (ii) in response to (transmitting) the first signaling, receive at least one first transmission from at least one UE of the more than one UE; and (iii) in response to (receiving) at least one first transmission, transmit at least one second transmission for at least one UE after or at a third timing, where the third timing is common to the more than one UE. Additionally, CPU 308 can execute program code 312 to perform all of the described actions, steps, and methods described above, below, or herein.

[0569] Any combination of the concepts or teachings above or herein can be fully or partially combined together or formed into a new embodiment. The disclosed details and embodiments can be used to at least (but not limited to) solve the problems mentioned above and herein.

[0570] It should be noted that any one of the methods, alternatives, steps, examples, and embodiments presented herein can be applied independently, individually, and / or together with multiple methods, alternatives, steps, examples, and embodiments combined together.

[0571] The 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, function, or both disclosed herein are merely representative. Based on the teachings herein, those of ordinary skill in the art should appreciate that the aspects disclosed herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of the aspects set forth herein can be used to implement a device or practice a method. Additionally, such a device can be implemented or such a method can be practiced using other structures, functionality, or a combination of structures and functionality other than or different from one or more of the aspects set forth herein. As examples of some of the above concepts, in some aspects, parallel channels can be established based on the pulse repetition frequency. In some aspects, parallel channels can be established based on pulse positioning or offset. In some aspects, parallel channels can be established based on time-hopping sequences. In some aspects, parallel channels can be established based on the pulse repetition frequency, pulse positioning or offset, and hopping sequences.

[0572] Those of ordinary skill in the art should understand that any of a variety of different technologies and techniques can be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

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

[0574] In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within an integrated circuit ("IC"), access terminal, or access point, or performed by an integrated circuit, access terminal, or access point. The 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, outside the IC, or in both cases. The general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

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

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

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

Claims

1. A method for a user equipment, characterized in that Comprising: Receiving a first signaling for triggering a random access procedure; Triggering the random access procedure in response to the first signaling; Transmitting a first transmission during the random access procedure; Determining a third timing based at least on a first timing and a first time delay, wherein the first timing is the timing when the first signaling ends; And Listening for a second transmission starting from the third timing in response to transmitting the first transmission.

2. The method according to claim 1, characterized in that The first time delay is at least one of the following: A predefined value, Indicated by the network, Derived or calculated by the user equipment, or Derived or calculated by the user equipment based at least on an indication provided by the first signaling and / or the predefined value.

3. The method according to claim 1, wherein: The first signaling is a paging for the Internet of Things for the environment, and / or The first signaling is for more than one user equipment, and / or The first signaling at least indicates the resources for the first transmission.

4. The method according to claim 1, wherein The third timing is common to more than one user equipment, and / or the third timing is the start time for listening for the second transmission.

5. The method according to claim 1, wherein The third timing is determined based at least on the first timing plus the first time delay, and / or the third timing is after the first timing plus the first time delay.

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

7. A method for a user equipment, characterized in that, Comprising: Receiving a first signaling for triggering a random access procedure; Triggering the random access procedure in response to the first signaling; Transmitting a first transmission during the random access procedure; Determining a third timing based at least on a second timing and a second time delay, wherein the second timing is the timing when the first transmission ends, and the second time delay is derived or calculated by the user equipment; and Listening for a second transmission starting from the third timing in response to transmitting the first transmission.

8. The method according to claim 7, characterized in that The second time delay is derived or calculated based at least on an indication provided by the first signaling and / or a predefined value, and / or the second time delay is derived or calculated based on the time correlation between the first transmission and the second transmission.

9. The method according to claim 7, wherein: The first signaling is a paging for the Internet of Things for the environment, and / or The first signaling is for more than one user equipment, and / or The first signaling at least indicates the resources for the first transmission.

10. The method according to claim 7, characterized in that The third timing is common to more than one user equipment, and / or the third timing is the start time for listening for the second transmission.

11. The method according to claim 7, characterized in that, The third timing is determined based at least on the second timing plus the second time delay, and / or the third timing is after the second timing plus the second time delay.

12. The method according to claim 7, wherein The first signaling and / or the second transmission are received from a reader, and / or the first transmission is transmitted to the reader, wherein the reader is the network or another user equipment.

13. A method of a reader, characterized in that, Comprising: Transmitting a first signaling for triggering one or more random access procedures for more than one user equipment; Receiving at least one first transmission from at least one of the more than one user devices in response to the first signaling; and Transmitting at least one second transmission for the at least one user device after a third timing in response to the at least one first transmission, wherein the third timing is common to the more than one user devices.

14. The method according to claim 13, wherein The third timing is determined based at least on a first timing and a first time delay, wherein the first timing is the timing at which the first signaling ends.

15. The method according to claim 14, wherein The first time delay is at least one of the following: A predefined value, Indicated by the reader, or Derived or calculated by the reader based at least on an indication provided by the first signaling and / or the predefined value.

16. The method according to claim 14, wherein The third timing is determined based at least on the first timing plus the first time delay, and / or the third timing is after the first timing plus the first time delay.

17. The method according to claim 13, characterized in that, The first signaling is a paging for the Internet of Things in the environment, and / or the first signaling indicates at least one or more resources of the at least one first transmission.

18. The method according to claim 13, wherein The reader is a network or another user device.

19. The method according to claim 13, wherein The at least one first transmission at least includes an identifier of the at least one user device.

20. The method according to claim 13, wherein The at least one second transmission at least includes an identifier of the at least one user device.

Images