Method and apparatus for providing assistance information of environmental internet of things in wireless communication system

Abstract

The present invention provides a method, system and apparatus for providing auxiliary information for environmental Internet of Things in a wireless communication system, where the method of a user equipment comprises: receiving a first signaling that triggers a random access procedure, where the first signaling indicates first information associated with a particular one of device types; and in response to receiving the first signaling, determining whether to trigger a random access procedure based at least on whether the user equipment belongs to the specific device type associated with the first information.

Description

[0001] Cross - reference to related applications

[0002] This application claims the priority and benefit of U.S. Provisional Patent Application No. 63 / 616,328, filed on December 29, 2023, U.S. Provisional Patent Application No. 63 / 616,478, filed on December 29, 2023, U.S. Provisional Patent Application No. 63 / 620,656, filed on January 12, 2024, and U.S. Provisional Patent Application No. 63 / 563,130, filed on March 8, 2024; each of the listed and cited applications and disclosures is incorporated herein by reference in its entirety. Technical Field

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

[0004] With the rapid growth in the demand for transferring large amounts of data to and from mobile communication devices, traditional mobile voice communication networks have evolved into networks that communicate with Internet Protocol (IP) data packets. Such IP packet communication can provide IP bearer voice, multimedia, multicast, and on-demand communication services for 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 bearer voice and multimedia services. Currently, the 3GPP standards organization is discussing new next-generation (e.g., 5G) radio technologies. Therefore, 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 devices for providing auxiliary information for ambient Internet of Things (IoT) in a wireless communication system. For a specific device type indicated by a network (NW), a user equipment (UE) having the specific device type may trigger random access with appropriate resources. The NW may provide resources (for performing random access) for different device types in each paging. Alternatively and / or additionally, in response to signaling for triggering random access, the UE may indicate its capabilities in transmission generation and its device, which may assist the NW in scheduling device-to-receiver (D2R) transmissions. Ambient IoT UEs / devices may access the NW and / or transmit data using appropriate resources.

[0007] In various embodiments, a method of a UE includes: receiving first signaling that triggers a random access procedure, wherein the first signaling indicates first information associated with a specific device type in a device type; and determining whether to trigger the random access procedure in response to (receiving) the first signaling, based at least on whether the UE belongs to the specific device type associated with the first information.

[0008] In various embodiments, a method of a UE includes: receiving first signaling that triggers a random access procedure; triggering the random access procedure in response to (receiving) the first signaling; and performing a transmission that indicates or provides third information during the random access procedure, wherein the third information indicates the device type of the UE, and the device type of the UE is distinguished or associated with any of the following: a method of performing the transmission, equipped with an amplifier, energy storage, power level, and / or device size. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0010] Figure 2 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.

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

[0012] Figure 4 is according to an embodiment of the present invention Figure 3 of the program code.

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

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

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

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

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

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

[0019] 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

[0020] Figure 9 It is an example diagram showing that a first UE according to an embodiment of the present invention can provide (or transmit) (first) information to a network node (or a second UE) (at least).

[0021] Figure 10 It is a flowchart of a method of a first UE according to an embodiment of the present invention, including initiating or performing a transmission to a network node (or a second UE), where the transmission at least includes (first) information

[0022] Figure 11 It is a flowchart of a method of a UE according to an embodiment of the present invention, the method including: initiating an RA procedure; transmitting a message including the identification of the UE in the RA procedure; receiving a PDCCH transmission in response to transmitting the message; and determining that the RA procedure is successfully completed based on the PDCCH transmission scrambled with the identification of the UE or the PDCCH transmission indicating the identification of the UE

[0023] Figure 12is a flowchart of a method of a UE according to an embodiment of the present invention. The method includes: initiating a RA procedure; transmitting a first message including an identifier of the UE in the RA procedure; receiving a second message in response to transmitting the first message; and determining that the RA procedure is successfully completed based on the second message indicating the identifier of the UE.

[0024] Figure 13 is a flowchart of a method of a UE according to an embodiment of the present invention. The method includes: receiving signaling from the NW; initiating a RA procedure in response to receiving the signaling; transmitting a first message; starting a first timer at a specific timing; listening for a PDCCH while the first timer is running; and receiving a second message on the PDCCH in response to transmitting the first message.

[0025] Figure 14 is a flowchart of a method of a UE according to an embodiment of the present invention. The method includes: receiving first signaling triggering a random access procedure, where the first signaling indicates first information associated with a specific device type in a device type; and determining whether to trigger the random access procedure in response to receiving the first signaling, at least based on whether the UE belongs to the specific device type associated with the first information.

[0026] Figure 15 is a flowchart of a method of a UE according to an embodiment of the present invention. The method includes: receiving first signaling triggering a random access procedure; triggering the random access procedure in response to receiving the first signaling; and performing transmission indicating or providing third information during the random access procedure, where the third information indicates the device type of the UE, and the device type of the UE is distinguished or associated with any one of the following: the method of performing the transmission, equipped with an amplifier, energy storage, power level, and / or device size. Detailed implementation

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

[0028] The exemplary wireless communication systems and devices described below employ 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 techniques.

[0029] Specifically, the exemplary wireless communication system devices described below can be designed to support one or more standards, such as those provided by an association named "Third Generation Partnership Project" (referred to as 3GPP in this document), including: [1] RP-234058, "Study on Solutions for Internet of Things (IoT) in the Environment in NR"; [2] 3GPP TR38.848 V18.0.0 (2023-09) 3GPP; TSG RAN; Study on Internet of Things (IoT) in the Environment 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); [5] 3GPP TS 38.331 V17.6.0 (2023-09) 3GPP; TSG RAN; NR; RRC Protocol Specification (Release 17); and [6] 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 by reference in their entirety.

[0030] Figure 1A multi-access wireless communication system according to an embodiment of the present invention is shown. The access network 100 (AN) 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 only two antennas are shown for each antenna group, but 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 use different frequencies for communication. For example, the forward link 120 may use a frequency different from the frequency used by the reverse link 118.

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

[0032] 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 of different access terminals 116 and 122. Also, compared to the access network transmitting to all of its access terminals through a single antenna, the access network using beamforming to transmit to access terminals randomly scattered throughout the coverage area of the access network generally causes less interference to the access terminals in adjacent cells.

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

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

[0035] 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 to provide encoded data based on a particular encoding scheme selected for each data stream.

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

[0037] The modulation symbols of all data streams are then provided to the TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). The TX MIMO processor 220 then provides NT streams of modulation symbols to NT transmitters (TMTR) 222a through 222t. In some embodiments, the TX MIMO processor 220 applies beamforming weights to the symbols of the data stream and the antennas for transmitting the symbols.

[0038] 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 via the MIMO channel. The NT modulated signals from transmitters 222a through 222t are then transmitted from the NT antennas 224a through 224t, respectively.

[0039] At the receiver system 250, the transmitted modulated signals are received by NR antennas 252a through 252r, and the signals received from each antenna 252 are provided to a respective receiver (RCVR) 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.

[0040] The RX data processor 260 then receives and processes the NR received symbol streams from the NR receivers 254 based on specific receiver processing techniques to provide NT "detected" symbol streams. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data of the data stream. The processing performed by the RX 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.

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

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

[0043] 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 through 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.

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

[0045] 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 the 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, thereby controlling the operation of the communication device 300. The communication device 300 may receive signals input by a user through the input device 302 (e.g., a keyboard or keypad), and may output images and sounds through the output device 304 (e.g., a display or a speaker). The transceiver 314 is used to receive and transmit wireless signals to deliver the received signals to the control circuit 306 and wirelessly output the signals generated by the control circuit 306.

[0046] Figure 4 is a simplified block diagram of the program code 312 shown in Figure 3 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.

[0047] For an LTE, LTE-A, or NR system, the layer 2 portion 404 may include a radio link control (RLC) layer and a media access control (MAC) layer. The layer 3 portion 402 may include a radio resource control (RRC) layer.

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

[0049] Any sentence, paragraph, (sub) bullet point, key point, action, or claim described in each of the following inventive paragraphs or clauses may be implemented independently and separately to form a specific method or device. The dependencies (e.g., "based on", "more specifically", "example", etc.) in the following inventive disclosures are merely illustrative and do not limit the possible embodiments of a specific method or device.

[0050] The research project on the Internet of Things (IoT) for the environment has been approved at the RAN Plenary 102 meeting. It is described in [1] RP-234058 as follows:

[0051] *************************** Citation start [1] ******************************

[0052] 3 Reasons

[0053] In recent years, IoT has drawn a great deal of attention in the wireless communication world. More 'things' are expected to be interconnected to improve productivity efficiency and increase the comfort of life. Further reduction in the size, complexity, and power consumption of IoT devices can 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 leads to high maintenance costs, serious environmental problems, and even safety hazards for some use cases (e.g., wireless sensors in the power and oil industries).

[0054] 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 energy-storing devices 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 cases.

[0055] 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 as well as new KPIs. SA1 is considering devices that are battery-free or have limited energy storage capabilities (i.e., using capacitors) and are powered by collecting radio waves, light, motion, heat, or any other power source that may be considered suitable.

[0056] 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 a few hundred μW. Existing cellular devices may not perform well in energy harvesting due to their peak power consumption above 10 mW.

[0057] 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 leads to high deployment costs. In addition, the lack of interference management schemes results in severe interference and capacity problems between RFID readers, especially in the case of dense deployments. It is difficult for RFID to support large-scale seamless coverage networks.

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

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

[0060] 4 Objectives

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

[0062] 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 in addressing 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).

[0063] General range

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

[0065] A. The overall objective should be to study a coordinated air interface design with minimized differences (if necessary) to enable environmental IoT to achieve the following devices:

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

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

[0068] ● X will be determined in the WG.

[0069] ● Coverage design objective: According to TR 38.848: “… the WG may choose the range within which …”, the maximum distance from the indoor device is 10 - 50 m.

[0070] ● 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 / reselection - like functions), no HARQ, no ARQ.

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

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

[0073] ● Deployment scenario 1 with topology 1

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

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

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

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

[0078] C. FR1 licensed spectrum in FDD.

[0079] D. Spectrum deployment within the NR band, within the LTE / NR guard band, and in an independent frequency band.

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

[0081] ● Starting from RAN#104, the study will evaluate whether the coordinated air - interface design (according to the above bullet point ‘A’) can solve the DO - A (device - initiated autonomous) use case, solely to identify which part(s) of the coordinated air - interface design (according to the above bullet point ‘A’) is / are insufficient for the DO - A use case.

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

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

[0084] 1. Evaluate assumptions

[0085] …

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

[0087] …

[0088] ● RAN2-led:

[0089] ○ Research and decide on the functions required for the environmental IoT compact protocol stack and lightweight signaling procedures to enable DO-DTT and DT data transmissions, and research these functions.

[0090] For example:

[0091] ■ Paging

[0092] ■ Random access

[0093] ■ Data transmissions including the necessary radio resource control aspects comply with the limitations within the general scope

[0094] ■ Interaction with the upper layer

[0095] *****************************Quotation ends********************************

[0096] A description of environmental IoT can be found in TR 38.848 ([2] 3GPP TR 38.848 V18.0.0 (2023-09)):

[0097] *****************************Quotation starts [2]*****************************

[0098] 4.2.1 Connection topology

[0099] 4.2.1.0 Introduction

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

[0101] A BS, UE, assisting node, or intermediate node can be multiple BSs or UEs respectively. A mix 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 assisting or intermediate nodes.

[0102] 4.2.1.1 Topology 1:

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

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

[0105] 4.2.1.2 Topology 2:

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

[0107] In Topology 2, the environmental 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 environmental IoT capabilities, an IAB node, a UE, a repeater, etc. The intermediate node transmits environmental IoT data and / or signaling between the BS and the environmental IoT device.

[0108] ********************************Next citation*****************************

[0109] 4.3 Device Classification

[0110] Environmental IoT devices are characterized in the research according to their energy storage capacity and the ability to generate RF signals for their transmission.

[0111] The research assumes that the device has any of the following:

[0112] - There is no energy storage; or

[0113] - There is limited energy storage

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

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

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

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

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

[0119] *********************************End of citation****************************

[0120] The current random access (RA) procedure is specified in TS 38.321 ([3] 3GPP TS 38.321 V17.6.0 (2023-09)). The (current) RA procedure will be executed by legacy UEs:

[0121] *********************************Beginning of citation [3]**************************

[0122] 5.1 Random access procedure

[0123] 5.1.1 Random access procedure initialization

[0124] According to TS 38.300 [2], the random access procedure described in this clause is initiated by a PDCCH command, the MAC entity itself, or an RRC event. In the MAC entity, there is only one ongoing random access procedure at any point in time.

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

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

[0127] …

[0128] - msgA-PRACH-ConfigurationIndex: The set of available PRACH occasions for transmitting the random access preamble of MSGA in 2-step RA type;

[0129] - preambleReceivedTargetPower: The initial random access preamble power for 4-step RA type;

[0130] - msgA-PreambleReceivedTargetPower: The initial random access preamble power for 2-step RA type;

[0131] …

[0132] - msgA-RSRP-ThresholdSSB: The RSRP threshold for selecting SSB for 2-step RA type.

[0133] - rsrp-ThresholdSSB-SUL: The RSRP threshold for selection between NUL carrier and SUL carrier;

[0134] - msgA-RSRP-Threshold: The RSRP threshold for selection between 2-step RA type and 4-step RA type when random access resources of both 2-step and 4-step RA types are configured in ULBWP;

[0135] - rsrp-ThresholdMsg3: The RSRP threshold for Msg3 repetition (see Clause 5.1.1b);

[0136] - FeatureCombination: The feature or combination of features associated with the set of random access resources;

[0137] - featurePriorities: The priorities of features, such as RedCap, Slicing, etc. (see Clause 5.1.1d);

[0138] - msgA-TransMax: The maximum number of transmissions of MSGA when random access resources of 4-step and 2-step RA types are configured;

[0139] …

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

[0141] -ra-ssb-OccasionMaskIndex: Defines the PRACH occasions associated with an SSB, where the MAC entity may 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 2-step RA type PRACH occasions for each SSB. If 2-step RA type PRACH occasions are shared with 4-step RA type PRACH occasions and msgA-SSB-SharedRO-MaskIndex is not configured, then all 4-step RA type PRACH occasions are available for 2-step RA type (see clause 7.4);

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

[0144] -ra-OccasionList: Defines the PRACH occasions associated with CSI-RS where the MAC entity may 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 a set of random access resources applicable to the random access procedure;

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

[0148] …

[0149] -msgA-PUSCH-ResourceGroupA: Defines the MSG A PUSCH resources that the UE will use when performing MSG A transmission using random access preamble group A;

[0150] -msgA-PUSCH-ResourceGroupB: Defines the MSG A PUSCH resources that the UE will use when performing MSG A transmission using random access preamble group B;

[0151] -msgA-PUSCH-resource-Index: Index identifying the PUSCH resource for MSG A in the case of contention-free random access of type 2-step RA;

[0152] …

[0153] -ra-ResponseWindow: Time window for listening for RA response (SpCell only);

[0154] -ra-ContentionResolutionTimer: Contention resolution timer (SpCell only);

[0155] -msgB-ResponseWindow: Time window for listening for RA response of type 2-step RA (SpCell only).

[0156] …

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

[0158] …

[0159] 1> Perform the BWP operation as specified in Clause 5.15;

[0160] 1> Select a set of random access resources applicable to the current random access procedure according to Clause 5.1.1b;

[0161] …

[0162] 1> Initialize the variables specific to the random access type as specified in Clause 5.1.1a;

[0163] 1> If RA_TYPE is set to 2-step RA:

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

[0165] 1> Otherwise:

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

[0167] 5.1.1b Selection of the set of random access resources for the random access procedure

[0168] The MAC entity shall:

[0169] …

[0170] 1> If no contention - free random access resources and random access resources for SI requests are provided for this random access procedure, and one or more of the features including RedCap and / or slicing and / or SDT and / or MSG3 repetition apply to this random access procedure:

[0171] …

[0172] 2> If no set of random access resources is available for any feature applicable to the current random access procedure (as specified in clause 5.1.1c):

[0173] 3> Select a set of random access resources not associated with any feature indication for this random access procedure (as specified in clause 5.1.1c).

[0174] 2> Otherwise, if there is an available set of random access resources that can be used to indicate all features triggering this random access procedure:

[0175] 3> Select this set of random access resources for this random access procedure.

[0176] 2> Otherwise (i.e., there is one or more available sets of random access resources configured with indications of a subset of all features triggering this random access procedure):

[0177] 3> Select a set of random access resources from the available sets of random access resources based on the priority order indicated by the upper layer as specified in clause 5.1.1d for this random access procedure.

[0178] 1> Otherwise, if contention - free random access resources have been provided for this random access procedure and RedCap applies to the current random access procedure and there is an available set of random access resources configured only with RedCap indication:

[0179] 2> Select this set of random access resources for this random access procedure.

[0180] 1> Otherwise:

[0181] 2> Select a set of random access resources not associated with any feature indication for the current random access procedure (as specified in clause 5.1.1c).

[0182] 5.1.1c Availability of random access resource sets

[0183] For each configured set of random access resources for 4 - step RA type and for each configured set of random access resources for 2 - step RA type, the MAC entity will:

[0184] 1> If redCap is set to true for the set of random access resources:

[0185] 2> Consider the random access resource set as not available for random access procedures not applicable to RedCap.

[0186] 1> If for the random access resource set, smallData is set to true:

[0187] 2> Consider the random access resource set as not available for random access procedures not triggered for RA-SDT.

[0188] 1> If the NSAG-List is configured for the random access resource set:

[0189] 2> Consider the random access resource set as not available for random access procedures unless triggered for any of the NSAG-IDs in the NSAG-List.

[0190] 1> If for the random access resource set, msg3-Repetitions is set to true:

[0191] 2> If Msg3 repetitions are not applicable, consider the random access resource set as not available for random access procedures.

[0192] 1> If the random access resource set is not configured with FeatureCombination:

[0193] 2> Consider the random access resource set as not associated with any feature.

[0194] 5.1.2 Random Access Resource Selection

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

[0196] …

[0197] 1> Otherwise, if ra-PreambleIndex has been explicitly provided by the PDCCH; and

[0198] 1> If ra-PreambleIndex is not 0b000000:

[0199] 2> Set PREAMBLE_INDEX to the transmitted ra-PreambleIndex;

[0200] 2> Select the SSB transmitted by the PDCCH.

[0201] …

[0202] 1> Otherwise (i.e., for contention-based random access preamble selection):

[0203] 2> If at least one SSB with SS-RSRP higher than rsrp-ThresholdSSB is available:

[0204] 3> Select an SSB with SS-RSRP higher than rsrp-ThresholdSSB.

[0205] 2> Otherwise:

[0206] 3> Select any SSB.

[0207] …

[0208] 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;

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

[0210] …

[0211] 1> Otherwise, if the SSB is selected as above:

[0212] 2> Determine the next available PRACH occasion according to the PRACH occasion, corresponding to the selected SSB given by ra-ssb-

[0213] OccasionMaskIndex (if configured) or ssb-SharedRO-MaskIndex (if configured) or permitted by the restrictions indicated by the PDCCH (According to Clause 8.1 of TS 38.213 [6], the MAC entity will 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).

[0214] …

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

[0216] …

[0217] 5.1.2a Random access resource selection for 2-step RA type

[0218] If the selected RA_TYPE is set to 2-stepRA, the MAC entity will:

[0219] 1> If contention-free two-step RA type resources associated with the SSB are explicitly provided in rach-ConfigDedicated and at least one SSB with SS-RSRP higher than msgA-RSRP-ThresholdSSB is available among the associated SSBs:

[0220] 2> Select the SSB among the associated SSBs with SS-RSRP higher than msgA-RSRP-ThresholdSSB;

[0221] 2> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected SSB.

[0222] 1> Otherwise (i.e., for contention-based random access preamble selection):

[0223] 2> If at least one SSB with SS-RSRP higher than msgA-RSRP-ThresholdSSB is available:

[0224] 3> Select the SSB with SS-RSRP higher than msgA-RSRP-ThresholdSSB.

[0225] 2> Otherwise:

[0226] 3> Select any SSB.

[0227] …

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

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

[0230] 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 [6], the MAC entity will randomly select a PRACH occasion among the consecutive PRACH occasions allocated for the two-step RA type 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).

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

[0232] 2> Select a PUSCH timing from the PUSCH timings in msgA-CFRA-PUSCH configured in the PRACH time slot corresponding to the selected PRACH timing, according to the msgA-PUSCH-Resource-Index corresponding to the selected SSB;

[0233] 2> Determine a UL grant and associated HARQ information for the MSGA payload at the selected PUSCH timing;

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

[0235] 1> Otherwise:

[0236] 2> Select a PUSCH timing corresponding to the selected preamble and PRACH timing according to clause 8.1A of TS 38.213 [6];

[0237] 2> Determine a 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;

[0238] 2> If the selected preamble and PRACH timing are mapped to a valid PUSCH timing, as specified in clause 8.1A of TS 38.213 [6]:

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

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

[0241] …

[0242] 5.1.3 Random access preamble transmission

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

[0244] 1> If the PREAMBLE_TRANSMISSION_COUNTER is greater than one; and

[0245] 1> If no notification to suspend the power ramp counter has been received from the lower layer; and

[0246] 1> If no LBT failure indication for the last random access preamble transmission has been received from the lower layer; and

[0247] …

[0248] 2>Increment PREAMBLE_POWER_RAMPING_COUNTER by 1.

[0249] …

[0250] 1>Calculate the RA-RNTI associated with the PRACH occasion in which the random access preamble is transmitted, except for the contention-free random access preamble used for beam failure recovery requests;

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

[0252] …

[0253] 5.1.3a MSGA Transmission

[0254] For each MSGA, the MAC entity will:

[0255] 1>If PREAMBLE_TRANSMISSION_COUNTER is greater than one; and

[0256] 1>If no notification to suspend the power ramping counter has been received from the lower layer; and

[0257] 1>If no LBT failure indication for the last MSGA random access preamble transmission has been received from the lower layer; and

[0258] 1>If the selected SSB has not changed from the selection in the last random access preamble transmission:

[0259] 2>Increment PREAMBLE_POWER_RAMPING_COUNTER by 1.

[0260] …

[0261] 1>If this is the first MSGA transmission within this random access procedure:

[0262] 2>If not transmitting for the CCCH logical channel:

[0263] 3>Indicate to the multiplexing and aggregation entity to include the C-RNTI MAC CE in subsequent uplink transmissions.

[0264] 2>If spCell-BFR-CBRA for which the random access procedure is initiated for SpCell beam failure recovery and the configured value is true:

[0265] 3> If there is at least one serving cell of this MAC entity configured with two BFD-RS sets:

[0266] 4> Indicate to the multiplexing and aggregation entity to include an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE in subsequent uplink transmissions.

[0267] 3> Otherwise:

[0268] 4> Indicate to the multiplexing and aggregation entity to include a BFR MAC CE or a truncated BFR MAC CE in subsequent uplink transmissions.

[0269] 2> Otherwise, if a random access procedure is initiated for beam failure recovery of two BFD-RS sets for the SpCell:

[0270] 3> Indicate to the multiplexing and aggregation entity to include an enhanced BFR MAC CE or a truncated enhanced BFR MAC CE in subsequent uplink transmissions.

[0271] 2> Obtain the MAC PDU to be transmitted from the multiplexing and aggregation entity according to the HARQ information determined for the MSGA payload (see Clause 5.1.2a) and store it in the MSGA buffer.

[0272] 1> Calculate the MSGB-RNTI associated with the PRACH occasion in which the random access preamble is transmitted;

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

[0274] …

[0275] 5.1.4 Random access response reception

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

[0277] …

[0278] 3> Starting from the end of the random access preamble transmission, the ra-ResponseWindow configured in RACH-ConfigCommon is started at the first PDCCH time as specified in TS 38.213 [6].

[0279] 2> While ra-ResponseWindow is running, monitor the PDCCH of SpCell for the random access response identified by RA-RNTI.

[0280] 1> If notification of a PDCCH transmission is received on the search space indicated by recoverySearchSpaceId from lower layers on the serving cell where the preamble is transmitted; and

[0281] 1> if the PDCCH transmission is addressed to the C-RNTI; and

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

[0283] 2> The random access procedure is considered to be completed successfully.

[0284] 1> Otherwise, if a valid (as specified in TS 38.213 [6]) downlink assignment has been received on the PDCCH for the RA-RNTI and the received TB was successfully decoded:

[0285] …

[0286] 2> If the random access response contains a random access

[0287] MAC sub-PDU with preamble identifier (see clause 5.1.3):

[0288] 3> This random access response is considered to be received successfully.

[0289] 2> If the random access response is considered to be received successfully:

[0290] 3> If the Random Access Response contains a MAC sub-PDU with only RAPID:

[0291] 4> The random access procedure is considered to be successfully completed;

[0292] 4>Indicate to the upper layer that confirmation of SI request has been received.

[0293] 3> Otherwise:

[0294] 4> Apply the following actions for the serving cell in which the random access preamble is transmitted:

[0295] …

[0296] 6>Process the received UL grant value and indicate the value to the lower layer.

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

[0298] 5>Consider the random access procedure successfully completed.

[0299] 4>Otherwise:

[0300] 5>Set the TEMPORARY_C-RNTI to the value received in the random access response;

[0301] 5>If this is the first successfully received random access response within this random access procedure:

[0302] 6>If not transmitted for the CCCH logical channel:

[0303] 7>Indicate to the multiplexing and aggregation entity to include the C-RNTI MAC CE in subsequent uplink transmissions.

[0304] …

[0305] 6>Obtain the MAC PDU for transmission from the multiplexing and aggregation entity and store it in the Msg3 buffer.

[0306] …

[0307] 5.1.4a MSGB reception and contention resolution for 2-step RA type

[0308] Once the MSGA preamble is transmitted, regardless of whether a measurement gap may occur, the MAC entity will:

[0309] 1>Start the msgB-ResponseWindow at the PDCCH occasion as specified in clause 8.2A of TS 38.213 [6];

[0310] 1>While the msgB-ResponseWindow is running, listen for the PDCCH of the SpCell for the random access response identified by the MSGB-RNTI;

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

[0312] 2>While the msgB-ResponseWindow is running, listen for the PDCCH of the SpCell for the random access response identified by the C-RNTI.

[0313] 1> If a reception notification of the PDCCH transmission for the SpCell is received from a lower layer:

[0314] 2> If the C-RNTI MAC CE is included in the MSGA:

[0315] 3> If a random access procedure is initiated for SpCell beam failure recovery or for beam failure recovery of the BFD-RS set for the SpCell (as specified in Clause 5.17) and the PDCCH transmission is addressed to the C-RNTI:

[0316] 4> Consider the reception of this random access response successful;

[0317] 4> Stop the msgB-ResponseWindow;

[0318] 4> Consider this random access procedure successfully completed.

[0319] …

[0320] 3> Otherwise:

[0321] 4> If a downlink assignment has been received on the PDCCH for the C-RNTI and the received TB is successfully decoded:

[0322] 5> If the MAC PDU contains an absolute timing advance command MAC CE:

[0323] 6> Process the received timing advance command (see Clause 5.2);

[0324] 6> Consider the reception of this random access response successful;

[0325] 6> Stop the msgB-ResponseWindow;

[0326] 6> Consider this random access procedure successfully completed and end the disassembly and demultiplexing of the MAC PDU.

[0327] 2> If a valid (as specified in TS 38.213 [6]) downlink assignment has been received on the PDCCH for the MSGB-RNTI and the received TB is successfully decoded:

[0328] …

[0329] 3> If the MSGB contains a fallbackRAR MAC sub-PDU; and

[0330] 3> If the random access preamble identifier in the MAC sub-PDU matches the transmitted PREAMBLE_INDEX (see Clause 5.1.3a):

[0331] 4> Consider that the random access response is successfully received;

[0332] 4> Apply the following actions to the SpCell:

[0333] …

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

[0335] 6> Consider that the random access procedure is successfully completed;

[0336] 6> Process the received UL grant value and indicate the value to the lower layer.

[0337] 5> Otherwise:

[0338] 6> Set the TEMPORARY_C-RNTI to the value received in the random access response;

[0339] 6> If the Msg3 buffer is empty:

[0340] 7> Obtain the MAC PDU to be transmitted from the MSGA buffer and store it in the Msg3 buffer;

[0341] 6> Process the received UL grant value and indicate the value to the lower layer and continue with Msg3 transmission.

[0342] …

[0343] 3> Otherwise if MSGB contains a successRAR MAC sub-PDU; and

[0344] 3> If the CCCH SDU is included in MSGA, and the UE contention resolution identity in the MAC sub-PDU matches the CCCH SDU:

[0345] 4> Stop the msgB-ResponseWindow;

[0346] …

[0347] 5> Set the C-RNTI to the value received in the successRAR;

[0348] …

[0349] 4> Consider that this random access response is successfully received;

[0350] 4> Consider that this random access procedure is successfully completed;

[0351] …

[0352] 5.1.5 Contention Resolution

[0353] Once Msg3 is transmitted, the MAC entity shall:

[0354] …

[0355] 1> Otherwise, if Msg3 is transmitted (i.e., initial transmission or HARQ retransmission) over a non-terrestrial network:

[0356] 2> Start or restart the ra-ContentionResolutionTimer in the first symbol after the end of Msg3 transmission plus the UE-gNB RTT.

[0357] 1> Otherwise:

[0358] 2> After the end of Msg3 transmission, start or restart the ra-

[0359] ContentionResolutionTimer in the first symbol.

[0360] 1> Irrespective of whether a measurement gap may occur, monitor the PDCCH while the ra-ContentionResolutionTimer is running;

[0361] 1> If a reception notification of the PDCCH transmission of the SpCell is received from the lower layer:

[0362] 2> If a C-RNTI MAC CE is included in Msg3:

[0363] …

[0364] 3> If a random access procedure is initiated by a PDCCH command and the PDCCH transmission is addressed to the C-

[0365] RNTI; or

[0366] 3> If a random access procedure is initiated by the MAC sublayer itself or by the RRC sublayer and the PDCCH transmission is addressed to the C-RNTI and contains a UL grant for a new transmission:

[0367] 4> Consider this contention resolution as successful;

[0368] 4> Stop the ra-ContentionResolutionTimer;

[0369] 4> Discard the TEMPORARY_C-RNTI;

[0370] 4> Consider this random access procedure as successfully completed.

[0371] 2> Otherwise, if a CCCH SDU is included in Msg3 and the PDCCH transmission is addressed to its TEMPORARY_C-RNTI:

[0372] 3> If the MAC PDU is successfully decoded:

[0373] 4> Stop the ra-ContentionResolutionTimer;

[0374] 4> If the MAC PDU contains a UE contention resolution identity MAC CE; and

[0375] 4> If the UE contention resolution identity in the MAC CE matches the CCCH SDU transmitted in Msg3:

[0376] 5> Consider this contention resolution successful and end the disassembly and demultiplexing of the MAC PDU;

[0377] …

[0378] 6> Set the C-RNTI to the value of TEMPORARY_C-RNTI;

[0379] 5> Discard the TEMPORARY_C-RNTI;

[0380] 5> Consider this random access procedure successfully completed.

[0381] 4> Otherwise:

[0382] 5> Discard the TEMPORARY_C-RNTI;

[0383] 5> Consider this contention resolution unsuccessful and discard the successfully decoded MAC PDU.

[0384] ******************************** Citation ends *****************************

[0385] The general description of the RA procedure is specified in TS 38.300 ([4] 3GPP TS 38.300 V17.6.0 (2023-09)): ******************************* Citation starts [4] ***************************

[0386] 9.2.6 Random access procedure

[0387] The random access procedure is triggered by several events:

[0388] - Initial access from RRC_IDLE;

[0389] …

[0390] - SDT in RRC_INACTIVE (see Clause 18);

[0391] …

[0392] Supports two types of random access procedures: 4-step RA type with MSG1 and 2-step RA type with MSGA. Both types of RA procedures support contention-based random access (CBRA) and contention-free random access (CFRA), as shown in Figure 9 .2.6-1.

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

[0394] - 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;

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

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

[0397] The network does not configure CFRA resources for both the 4-step and 2-step RA types of a bandwidth part (BWP) simultaneously. CFRA for the 2-step RA type is only supported for handover.

[0398] 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 shown in Figure 9 .2.6-1(c). 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 shown in Figure 9 .2.6-1(a). If contention resolution is not successful after the (re)transmission of MSG3, the UE returns to MSG1 transmission.

[0399] MSGA of the 2-step RA type contains a preamble on the PRACH and a payload on the PUSCH. After transmitting 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 shown in Figure 9As shown in .2.6-1(d). For CBRA, if contention resolution is successful after receiving the network response, the UE ends the random access procedure, as shown in Figure 9 .2.6-1(b); while if a fallback indication is received in MSG B, the UE uses the UL grant scheduled in the fallback indication to perform MSG3 transmission and listens for contention resolution, as shown in Figure 9 .2.6-2. If contention resolution is not successful after MSG3 (re)transmission, the UE returns to MSG A transmission.

[0400] If the random access procedure with a 2-step RA type is not completed after several MSG A transmissions, the UE may be configured to switch to CBRA with a 4-step RA type.

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

[0402] Figure 7B is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1: Random access procedure - (b) Reproduction of CBRA with a 2-step RA type.

[0403] Figure 7C is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1: Random access procedure - (c) Reproduction of CFRA with a 4-step RA type.

[0404] Figure 7D is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1: Random access procedure - (d) Reproduction of CFRA with a 2-step RA type.

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

[0406] For random access in a cell configured with SUL, the network may explicitly signal which carrier (UL or SUL) to use. Otherwise, the UE selects the SUL carrier if and only if the measured quality of the DL is below a broadcast threshold. The UE performs carrier selection before choosing between 2-step and 4-step RA types. The RSRP thresholds for choosing between 2-step and 4-step RA types may be configured separately for UL and SUL. Once started, all uplink transmissions of the random access procedure are maintained over the selected carrier.

[0407] The network may associate a set of RACH resources with characteristics applicable to the random access procedure: network slice (see clause 16.3), RedCap (see clause 16.13), SDT (see clause 18), and NR coverage enhancement (see clause 19). The set of RACH resources associated with a characteristic is only valid for random access procedures applicable to at least that characteristic; and the set of RACH resources associated with several characteristics is only valid for random access procedures having at least all of those characteristics. After uplink carrier (i.e., NUL or SUL) and BWP selection and before RA type selection, the UE selects the applicable set of RACH resources.

[0408]

[0409]

[0410] -BWP-UplinkCommon

[0411] The IE BWP-UplinkCommon is used to configure the common parameters of the uplink BWP. It is "per cell" and the network ensures the necessary alignment of the corresponding parameters with other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides the common parameters via dedicated signaling.

[0412] BWP-UplinkCommon information element

[0413]

[0414]

[0415] In TS 38.213 ([6] 3GPP TS 38.213 V17.7.0 (2023-09)), the RA procedures are specified:

[0416] ******************************** Citation of [6] starts **************************

[0417] 8 Random access procedure

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

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

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

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

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

[0423] From the perspective of the physical layer, the type 1 L1 random access procedure includes 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, if applicable, the transmission of PUSCH scheduled by the RAR UL grant and PDSCH for contention resolution.

[0424] From the perspective of the physical layer, the type 2 L1 random access procedure includes 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, if applicable, the transmission of PUSCH scheduled by the fallback RAR UL grant and PDSCH for contention resolution.

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

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

[0427] 8.1 Random access preamble

[0428] The physical random access procedure is triggered after a high layer or PDCCH instruction requests PRACH transmission. The configuration by the high layer for PRACH transmission includes the following:

[0429] - Configuration for PRACH transmission [4, TS 38.211].

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

[0431] Transmit the PRACH with the selected PRACH format at power P PRACH,b,f,c (i) Transmit the PRACH on the indicated PRACH resources as described in Clause 7.4.

[0432] …

[0433] For PRACH transmission triggered by a PDCCH instruction by the UE, if the value of the random access preamble index field is not zero, the PRACH mask index field [5, TS 38.212] indicates the PRACH occasion for PRACH transmission, where the PRACH occasion is associated with the SS / PBCH block index indicated by the SS / PBCH block index field of the PDCCH instruction. If the UE provides K 小区,偏移 via cellSpecificKoffset, the PRACH occasion is after slot n + 2 μ ·K 小区,偏移 , where n is the slot of the UL BWP for PRACH transmission, assuming T TA = 0, which overlaps with the end of the PDCCH instruction reception, and μ is the SCS configuration for PRACH transmission. If the PDCCH reception for the PDCCH instruction contains two PDCCH candidates from two linked search space sets based on searchSpaceLinkingId as described in Clause 10.1, the last symbol of the PDCCH reception is the last symbol of the later-ending PDCCH candidate. The PDCCH reception also contains the two PDCCH candidates when the UE does not need to monitor one of the two PDCCH candidates, as described in Clauses 10 (except Clause 10.4), 11.1, 11.1.1, and 17.2.

[0434] …

[0435] For the indicated preamble index, the order of the PRACH occasions is

[0436] - First, in increasing order of the frequency resource index for frequency multiplexed PRACH occasions

[0437] - Second, in ascending order of the time resource index for time-division multiplexed PRACH occasions within a PRACH slot

[0438] - Third, in ascending order of the index for the PRACH slot

[0439] …

[0440] 8.1A PUSCH for Type 2 random access procedure

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

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

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

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

[0445] …

[0446] The PUSCH occasion for PUSCH transmission is defined by frequency resources and time resources and is associated with DMRS resources. The DMRS resources are provided by msgA-DMRS-Config.

[0447] Each consecutive number N of valid PRACH occasions in a PRACH slot 前导码 of the preamble index

[0448] - First, in ascending order of the preamble index within a single PRACH occasion

[0449] - Second, in ascending order of the frequency resource index for frequency multiplexed PRACH occasions

[0450] - Third, in ascending order of the time resource index for time multiplexed PRACH occasions within a PRACH slot

[0451] Mapped to valid PUSCH occasions and associated DMRS resources

[0452] - First, in ascending order of the frequency resource index f for frequency multiplexed PUSCH occasions id of

[0453] - Second, in ascending order of the DMRS resource index within a PUSCH occasion, where the DMRS resource index DMRS is determined first in ascending order of the DMRS port index and second in ascending order of the DMRS sequence index id [4,TS 38.211]

[0455] - Third, in ascending order of the time resource index for time multiplexed PUSCH occasions within a PUSCH slot

[0456] t id of

[0457] - Fourth, in ascending order of the index for N s PUSCH slots

[0458] where N 前导码 = the cell (T 前导码 / T PUSCH ), T 前导码 is the total number of valid PRACH occasions per associated mode multiplied by the number of preambles per valid PRACH occasion provided by rach-ConfigCommonTwoStepRA, and T PUSCH is the total number of valid PUSCH occasions per PUSCH configuration per associated mode period multiplied by the number of DMRS resource indices per valid PUSCH occasion provided by msgA-DMRS-Config.

[0459] If the PUSCH occasion does not overlap in time and frequency with any valid PRACH occasion associated with a Type 1 random access procedure or a Type 2 random access procedure, then the PUSCH occasion is valid.

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

[0461] In response to the PRACH transmission, the UE attempts to detect DCI format 1_0 with CRC scrambled by the corresponding RA-RNTI during a window controlled by the higher layers [11, TS 38.321]. The window starts at the first symbol of the earliest CORESET where the UE is configured to receive 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 as defined in clause 10.1. If, as defined in [4, TS 38.211], or is non-zero, the window starts after an additional T TA + k mac milliseconds, where T TA is defined in [4, 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 multiple time slots is provided by ra-ResponseWindow.

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

[0463] …

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

[0465] If the value of the hopping flag is 0, the UE transmits the PUSCH without hopping; otherwise, the UE transmits the PUSCH with hopping.

[0466] The UE determines the MCS for PUSCH transmission from the first sixteen indices of the applicable MCS index table for PUSCH as described in [6, TS 38.214].

[0467] …

[0468] Table 8.2-1: Random access response grant content field sizes

[0469]

[0470] …

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

[0472] In response to the transmission of the PRACH and PUSCH, or in response to the transmission of only the PRACH in the case where the PRACH preamble is mapped to a valid PUSCH time, the UE attempts to detect DCI format 1_0 [11, TS 38.321] with CRC scrambled by the corresponding MsgB - RNTI during a window controlled by the higher layer. 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 time corresponding to the PRACH transmission, where the symbol duration corresponds to the SCS for the Type1 - PDCCH CSS set. If as defined in [4, TS 38.211], or is non - zero, the window starts after an additional T TA + k mac milliseconds, where T TA is defined in [4, 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 multiple time slots is provided by msgB - ResponseWindow.

[0473] 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 higher layers [11, TS 38.321]. The window starts at the first symbol of the earliest CORESET where the UE is configured to receive 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 multiple slots is provided by msgB-ResponseWindow.

[0474] If the UE detects DCI format 1_0 with CRC scrambled by the corresponding MsgB-RNTI and the LSB (if applicable) of the SFN field in DCI format 1_0 is the same as the corresponding LSB of the SFN in which the UE transmits the PRACH, and the UE receives a transport block in the corresponding PDSCH within the window, the UE passes the transport block to the higher layers. The higher layers indicate to the physical layer

[0475] - an uplink grant, provided that the RAR message is for fallbackRAR and identifies the random access preamble identity (RAPID) associated with the PRACH transmission, and the UE procedure continues as described in Clauses 8.2, 8.3, and 8.4 when the UE detects the RAR UL grant, or

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

[0477] - the PUCCH resource for the transmission of the PUCCH is indicated by the 4-bit PUCCH resource indicator field in successRAR from the set of PUCCH resources provided by pucch-ResourceCommon

[0478] - …

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

[0480] If the UE detects a DCI format 1_0 with a CRC scrambled by the corresponding MsgB-RNTI and receives a transport block within the window in the corresponding PDSCH, as described in [6, TS 38.214], the UE may assume the same DM-RS antenna port quasi-co-location property for the SS / PBCH block associated with the UE's PRACH, as described in clause 8.1, regardless of whether the UE is provided with the TCI-State of the CORESET in which the UE receives the PDCCH with DCI format 1_0.

[0481] …

[0482] 8.3 PUSCH Scheduled by RAR UL Grant

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

[0484] …The frequency-domain resource allocation is according to the uplink resource allocation type 1 [6, TS 38.214]. For the initial uplink BWP size of RB, the UE processes the frequency-domain resource assignment field as follows

[0485] -…

[0486] If the PUSCH transmission has no repetitions, the UE uses the redundancy version number 0 to transmit the transport block in the PUSCH scheduled by the RAR UL grant in the corresponding RAR message. If the TC-RNTI is provided by the higher layers, the scrambling initialization for the PUSCH corresponding to the RAR UL grant in clause 8.2 is done by the TC-RNTI. Otherwise, the scrambling initialization for the PUSCH corresponding to the RAR UL grant in clause 8.2 is done by the C-RNTI.

[0487] The Msg3 PUSCH retransmission of the transport block (if any) is scheduled by DCI format 0_0 with a CRC scrambled by the TC-RNTI provided in the corresponding RAR message [11, TS 38.321].

[0488] …

[0489] 8.4 PDSCH with UE Contention Resolution Identity

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

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

[0492] ******************************End of citation [6]****************************

[0493] The following abbreviation table is provided for parts of the following disclosure:

[0494] D2R: Device to Reader for (Ambient Internet of Things (A-IoT));

[0495] PDRCH: Physical (Environmental IoT) Device (to) Reader Channel;

[0496] PRDCH: Physical Reader (to Environmental IoT) Device Channel; and

[0497] R2D: Reader to (Environmental IoT) Device.

[0498] In the 3GPP RAN1 #116 meeting, there are some protocols regarding Environmental IoT:

[0499] For research purposes, RAN1 uses the following terms:

[0500] ● 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.

[0501] ● Device 2a: Peak power consumption ≤ a few hundred μW, with energy storage, initial 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.

[0502] ● Device 2b: Peak power consumption ≤ a few hundred μW, with energy storage, initial SFO up to 10 X ppm, and there is a DL and / or UL amplifier in the device. The UL transmission of the device is generated internally by the device.

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

[0504] For the A-IoT contention-based access procedure, at least access based on slotted ALOHA is studied.

[0505] For Environmental IoT devices, a dedicated physical broadcast channel for R2D, such as a Physical Broadcast Channel (PBCH)-like one, is not considered for research.

[0506] For Environmental IoT devices, at least a physical channel (PRDCH) is studied for R2D data transmission:

[0507] ● Transmit system information (if defined) on the PRDCH.

[0508] ● Whether / how to transmit control information on the PRDCH remains to be further studied.

[0509] ● Note: For research purposes, the naming of the PRDCH is used.

[0510] For environmental IoT devices, at least for D2R data transfer, study the Physical Data Rate Control Channel (PDRCH) along with the following:

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

[0512] ○ To be further studied: Details of the responses.

[0513] ● Whether D2R control information (if defined) / how D2R control information (if defined) / what D2R control information (if defined) is transmitted on the PDRCH remains to be further studied (for further research).

[0514] ● Note: For research purposes, the naming of the PDRCH is used.

[0515] In recent years, there has been a desire for more devices to be interconnected in the wireless communication world to increase productivity, efficiency, and enhance the comfort of life. However, powering all IoT devices with batteries that require manual replacement or recharging will result in high maintenance costs, environmental problems, and security risks for some use cases such as wireless sensors in power grids. Further reduction in the size, complexity, and power consumption of IoT devices enables the deployment for various applications (e.g., automated manufacturing, smart home).

[0516] On the other hand, barcodes and Radio Frequency Identification (RFID) have a limited reading range of several meters, which usually requires handheld scanning. This will lead to labor-intensive and time-consuming operations. Moreover, the lack of interference management schemes will result in severe interference and capacity problems between RFID readers, especially in the case of dense deployments. RFID is difficult to support large-scale seamless coverage networks. In contrast, the research on environmental IoT investigates the feasibility of new IoT technologies within the 3rd Generation Partnership Project (3GPP) system.

[0517] The environmental IoT device / user equipment (UE) will have ultra-low complexity, extremely small device size, and long lifecycle. The environmental IoT device / UE will have complexity and power consumption that are several orders of magnitude lower than existing 3GPP Low Power Wide Area (LPWA) technologies (e.g., Narrowband (NB)-IoT, enhanced Machine-Type Communication (eMTC)). The environmental IoT device / UE may not have energy storage or may have energy storage. The energy of the environmental 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 environmental IoT device / UE can be provided from a carrier from the network and / or intermediate node. In topology 1, the environmental IoT device / UE will communicate directly and bidirectionally with the base station. In topology 2, the environmental IoT device / UE will communicate bidirectionally with an intermediate node (e.g., UE or relay node) between the environmental IoT device / UE and the base station. The UL transmission of the environmental IoT device / UE can be generated internally by the device / UE or backscattered on an externally provided carrier. More details regarding the environmental IoT (device / UE) can be found in research projects [1] RP-234058 and [2] 3GPP TR38.848 V18.0.0.

[0518] The service types of the environmental IoT UE can be Device Originated-Device Terminated Triggered (DO-DTT) or Device Terminated (DT). The DO-DTT or DT transmission of the environmental IoT UE is triggered by the network (or an external device). In New Radio (NR), the paging procedure can be used to trigger Mobile Terminated (MT) transmission. However, for the environmental IoT UE, the paging procedure may not be suitable (or not practically applicable) for triggering DO-DTT or DT transmission. The reasons may include: the environmental IoT UE may not listen for paging due to power consumption (at least for a relatively long period of time), the environmental IoT UE may not be able to listen for paging due to lack of configurations such as 5G-S-Temporary Mobile Subscription Identifier (5G-S-TMSI) used to derive the paging moment, the environmental IoT UE may not be able to successfully decode traditional paging messages due to large message sizes, and the environmental IoT UE may not be able to establish a Radio Resource Control (RRC) connection in response to paging due to no (possible) RRC state. Therefore, how to trigger DO-DTT or DT transmission for the environmental IoT UE should be considered.

[0519] Since the environmental IoT UE will have extremely low capabilities, it is important for the network to schedule these UEs to perform data transmission properly, for example, by providing appropriate frequency resources and / or repetition times. Different environmental IoT UEs will have different capabilities in terms of transmission (e.g., downlink (DL) / uplink (UL) amplification, methods of generating transmissions). It will be beneficial for the Network (NW) to have some knowledge of the UEs for which it determines transmission resources.

[0520] The first UE can receive (a first) signaling from a network node (or a second UE). The first UE can perform (or initiate) a transmission (or a procedure) in response to (or based on) the (first) signaling.

[0521] The network node can transmit the (first) signaling to the first UE. The second UE can transmit the (first) signaling to the first UE. The (first) signaling can be used to trigger the first UE to perform (or initiate) a transmission (or a procedure).

[0522] The transmission (or procedure) can be (or include) an uplink transmission, a sidelink transmission, a transmission to a network node, and / or a transmission to a second UE. The network node can receive a transmission from the first UE. The second UE can receive a transmission from the first UE.

[0523] The transmission (or procedure) can be (or include) data transmission, DT transmission, DO - DTT transmission, Small Data Transmission (SDT), and / or Random Access (RA) transmission or procedure. The transmission can be associated with a procedure.

[0524] (The first) signaling can be (or include) common signaling. (The first) signaling can be (or include) cell - specific signaling. (The first) signaling can be (or include) broadcast signaling. (The first) signaling can be received by, for example, multiple UEs (or a group of UEs) in a UE group. (The first) signaling can be (or include) system information. (The first) signaling can be (or include) paging.

[0525] (The first) signaling can be (or include) dedicated signaling. (The first) signaling can be (or include) UE - specific signaling. (The first) signaling can be (or include) RRC signaling (e.g., RRC configuration message).

[0526] (The first) signaling can be (or include) Non - Access Stratum (NAS) signaling. (The first) signaling can be (or include) RRC signaling (e.g., RRC configuration message). (The first) signaling can be (or include) Medium Access Control (MAC) signaling (e.g., MAC Control Element (CE)). (The first) signaling can be (or include) Physical Layer (PHY) signaling (e.g., Physical Downlink Control Channel (PDCCH), Downlink Control Information (DCI)). (The first) signaling can be (or include) PDCCH commands.

[0527] (The first) signaling can be (or include) a carrier (signal) and / or an interrogation signal. (The first) signaling can be used to trigger (or indicate) the transmission (or reception) of a UE (e.g., the first UE, the second UE). The transmission from the UE can be (or include) a backscatter transmission (or reception), or can be generated internally by the UE. (The first) signaling can be used to supply power and / or energy to the UE. (The first) signaling can be used to trigger (or indicate) the RA procedure (or initial access) of the UE.

[0528] One or more information may be included in the (first) signaling. The information may (be used to) indicate which / what (type of) UE should respond to the (first) signaling. The information may (be used to) indicate which / what (type of) UE is allowed to perform (or initiate) (data) transmission or reception, e.g., (data) transmission or reception in response to the (first) signaling or information. The information may (be used to) indicate the configuration to be used for (subsequent) (data) transmission or reception (or procedure).

[0529] One or more of the following information may be included in the (first) signaling:

[0530] UE set

[0531] The information may (at least) indicate a set of UEs. The information may be (or include) a series of UE Identities (IDs).

[0532] The information may (at least) indicate a distance range of UEs, e.g., UEs having the distance range. The information may be (or include) a distance range and / or a reception power range of the signaling. The information may indicate a threshold (for reception power or path loss). A UE may determine / derive the distance range based on the reception power of the signaling. A UE may determine / derive whether the UE belongs to the set of UEs based on a comparison between the reception power (of the signaling) and the threshold, e.g., if the reception power is equal to or greater than the threshold, the UE determines that the UE belongs to the set of UEs. A UE may determine / derive whether the UE belongs to the set of UEs based on a comparison between the estimated path loss (based on the signaling) and the threshold, e.g., if the estimated path loss is equal to or less than the threshold, the UE determines that the UE belongs to the set of UEs. The distance range may be centered on a network node or a second UE.

[0533] The information may (at least) indicate a group of UEs. The information may (at least) indicate a UE group. The information may be (or include) a group ID.

[0534] The information may (at least) indicate a set of UE groups. The information may be (or include) a series of UE group IDs.

[0535] The information may be used to identify a set of UEs. The information may indicate which UE (set) should respond to the (first) signaling.

[0536] Specific UE

[0537] The information may (at least) indicate a specific UE. The information may be (or include) a UE ID.

[0538] The information may be used to identify a UE. The information may indicate which UE should respond to the (first) signaling.

[0539] Auxiliary information

[0540] The information may (at least) indicate the UE type. The information may (at least) indicate the device type.

[0541] The information may (at least) indicate the power level (threshold).

[0542] The information may (at least) indicate UL transmissions, such as the repetition times of Msg1, preambles, Msg3, MSGA, etc.

[0543] The information may (at least) indicate the (UL) data type. The information may (at least) indicate the (UL) data size.

[0544] The information may (at least) indicate the area range.

[0545] The information may indicate which (type of) UE should respond to the (first) signaling. For example, a UE that meets the conditions indicated by the information should respond to the (first) signaling. A UE that does not meet the conditions indicated by the information should not respond to the (first) signaling. For example, a UE that belongs to what is indicated by the information should respond to the (first) signaling. A UE that does not belong to what is indicated by the information should not respond to the (first) signaling.

[0546] Scheduling information

[0547] The information may (at least) indicate scheduling information. The information may (at least) indicate the resources for (subsequent) (data) transmission or reception. The information may be (or include) a UL grant. The information may be (or include) a configured grant. The information may be (or include) a DL assignment.

[0548] RA - related information

[0549] The information may (at least) indicate information related to the random access procedure. The information may be (or include) a dedicated preamble and / or a preamble / Random Access Channel (RACH) timing.

[0550] The UE may execute (or initiate) an RA procedure in response to (receiving) the (first) signaling. The UE may execute (or initiate) an RA procedure based on the information.

[0551] Configuration

[0552] The information may (at least) indicate which set of configurations to be used (or applied). The UE may be pre-configured with multiple sets of configurations. The UE may determine to use a specific set of configurations in response to (receiving) the (first) signaling. The UE may determine to use a specific set of configurations based on the information.

[0553] One or more parameters of the following configuration may be included in the (first) signaling:

[0554] Configuration related to RA

[0555] The configuration may be (or include) any one of the following: 4-step RA configuration, 2-step RA configuration, contention-based RA configuration, contention-free RA configuration, RA resource configuration, RA preamble configuration, dedicated preamble, RA preamble group configuration, RACH-ConfigCommon, Physical Random Access Channel (PRACH) configuration, RACH-ConfigCommonTwoStepRA, RACH-ConfigDedicated, RACH-ConfigGeneric, and / or RACH-ConfigGenericTwoStepRA.

[0556] The UE (e.g., an environmental IoT UE, a first UE) may be configured with multiple RA configurations for a cell. Alternatively and / or additionally, the cell may provide or indicate multiple RA configurations (for environmental IoT). The UE may be configured with multiple RA resource groups. Alternatively and / or additionally, the cell may provide or indicate multiple RA resource groups (for environmental IoT). The UE may be configured with multiple RA configuration groups. Alternatively and / or additionally, the cell may provide or indicate multiple RA configuration groups (for environmental IoT). The multiple RA configurations, RA resource groups, and / or RA configuration groups may be configured on different Bandwidth Parts (BWPs). The multiple RA configurations, RA resource groups, and / or RA configuration groups may be configured on the same BWP. The RA configurations, RA resource groups, and / or RA configuration groups may correspond to, be associated with, and / or be used by one or more UEs and / or a first factor.

[0557] Configuration related to downlink control signaling

[0558] The configuration may be (or include) any one of the following: PDCCH configuration, Control Resource Set (CORESET) configuration, search space configuration, PDCCH-Config, PDCCH-ConfigCommon, PDCCH-ConfigSIB1, PDCCH-ServingCellConfig, ControlResourceSet, ControlResourceSetId, ControlResourceSetZero, SearchSpace, SearchSpaceId, and / or SearchSpaceZero.

[0559] A UE (e.g., an ambient IoT UE, a first UE) may be configured with one (or more) PDCCH configurations, CORESET configurations, and / or search space configurations. It may not be allowed for the UE to configure more than one PDCCH configuration, CORESET configuration, and / or search space configuration. The UE may be pre-configured with one (or more) PDCCH configurations, CORESET configurations, and / or search space configurations. The UE may use (or apply) pre-configured (or fixed) values for the configurations. The UE may not need the configurations. The UE may not need the network to provide the configurations.

[0560] Configuration related to paging

[0561] The configuration may be (or include) any of the following: a paging cycle configuration, a paging frame configuration, a paging occasion configuration, a PCCH-config, and / or a (default) PagingCycle.

[0562] A UE (e.g., an ambient IoT UE, a first UE) may be at least configured with paging-related configurations. The UE may be at least pre-configured with paging-related configurations. The UE may use (or apply) pre-configured (or fixed) values for the configurations. The UE may not need paging-related configurations. The UE may not need the network to provide paging-related configurations.

[0563] Configuration related to system information

[0564] The configuration may be (or include) any of the following: a system information scheduling configuration, a system information modification configuration, a system information request configuration, a BCCH-config, an SI-SchedulingInfo, and / or an SI-RequestConfig.

[0565] A UE (e.g., an ambient IoT UE, a first UE) may be at least configured with system information-related configurations. The UE may be at least pre-configured with system information-related configurations. The UE may use (or apply) pre-configured (or fixed) values for the configurations. The UE may not need system information-related configurations. The UE may not need the network to provide system information-related configurations.

[0566] Configuration related to data transmission or reception

[0567] The configuration may be (or include) any one of the following: PUSCH-Config, PUSCH-ConfigCommon, PUSCH-ServingCellConfig, PDSCH-Config, PDSCH-ConfigCommon, PDSCH-ServingCellConfig, Semi-Persistent Scheduling (SPS) configuration, configured grant configuration, and / or Hybrid Automatic Repeat Request (HARQ) configuration.

[0568] The UE (e.g., an environmental IoT UE, a first UE) may be at least configured with a configuration related to data transmission or reception. The UE may be at least pre-configured with the configuration. The UE may use (or apply) a pre-configured (or fixed) value for the configuration. The UE may not require the configuration. The UE may not require the network to provide the configuration.

[0569] Configuration related to small data transmission

[0570] The configuration may be (or include) any one of the following: SDT-Config, SDT-MAC-PHY-CG-Config, SDT-ConfigCommonSIB, MT-SDT-ConfigCommonSIB, CG-SDT-Configuration, and / or SDT configuration.

[0571] The UE (e.g., an environmental IoT UE, a first UE) may be at least configured with a configuration related to small data transmission. The UE may be at least pre-configured with the configuration. The UE may use (or apply) a pre-configured (or fixed) value for the configuration. The UE may not require the configuration. The UE may not require the network to provide the configuration.

[0572] Miscellaneous

[0573] The configuration may be (or include) any one of the following: a configuration related to uplink control information, PUCCH-ConfigCommon, scheduling request configuration, and / or Sounding Reference Signal (SRS) configuration.

[0574] The configuration may be (or include): Packet Data Convergence Protocol (PDCP) configuration, Radio Link Control (RLC) configuration, RLC channel configuration, logical channel configuration, and / or radio bearer configuration.

[0575] The configuration may be (or include): Buffer Status Report (BSR) configuration, Power Headroom Report (PHR) configuration, Discontinuous Reception (DRX) configuration, MAC-CellGroupConfig, Timing Advance configuration, Timing Advance (TA) timer configuration, TA report configuration, and / or Radio Link Monitoring configuration.

[0576] The configuration may be (or include): measurement configuration, measurement gap configuration, measurement object configuration, and / or measurement report configuration.

[0577] The UE (e.g., an environmental IoT UE, a first UE) may be at least configured with the configuration. The UE may be at least pre-configured with the configuration. The UE may use (or apply) a pre-configured (or fixed) value for the configuration. The UE may not need the configuration. The UE may not need the network to provide the configuration.

[0578] The configurations described above may be for each of one or more BWPs of a cell for the UE. Alternatively, the configurations described above may be common for one or more RBSPs of a cell for the UE.

[0579] For another type of UE (e.g., a normal UE, a non-environmental IoT UE, a second UE), the UE may receive the configuration via system information and / or dedicated RRC signaling (e.g., RRC reconfiguration).

[0580] The traffic type of the environmental IoT UE may be DO-DTT or DT. The DO-DTT or DT transmission of the environmental IoT UE is triggered by the network (or an external device). For DT transmission, the network may know when the DT data arrives and the data size, so that the network can appropriately trigger and schedule the DT transmission. However, for DO-DTT transmission, the network may not know when the data has arrived and the corresponding data size. The network may not appropriately trigger and schedule the DO-DTT transmission.

[0581] The first UE may (at least) provide (or transmit) (first) information to a network node (or a second UE). The (first) information may be included in the (second) signaling. The (first) information and / or the (second) signaling may be transmitted by the first UE to the network node (or the second UE). In Figure 9 Examples are shown.

[0582] The first UE may perform (or initiate) the transmission of (first) information. The transmission may be (second) signaling. The transmission may be data transmission. The first UE may transmit (first) information and / or (second) signaling in response to (or based on) (first) signaling. The first UE may transmit (first) information and / or (second) signaling during a procedure. The procedure may be triggered by (first) signaling. The procedure may be a random access procedure. The procedure may be a small data transmission procedure.

[0583] (Second) signaling may be (or include) an RRC message (e.g., an RRC setup request). (Second) signaling may be (or include) MAC signaling (e.g., a MAC CE). (Second) signaling may be (or include) PHY signaling (e.g., a Physical Uplink Control Channel (PUCCH), Uplink Control Information (UCI)). (Second) signaling may be (or include) uplink control information. (Second) signaling may be (or include) an NAS message.

[0584] The first UE may receive (first) signaling from a network node (or a second UE). The first UE may perform (or initiate) a transmission (or a procedure) in response to (or based on) (first) signaling.

[0585] The network node may transmit (first) signaling to the first UE. The second UE may transmit (first) signaling to the first UE. (First) signaling may be used to trigger the first UE to perform (or initiate) an (uplink) transmission (or a procedure).

[0586] The transmission (or the procedure) may be (or include) an uplink transmission, a sidelink transmission, a transmission to a network node, and / or a transmission to a second UE. The network node may receive the transmission from the first UE. The second UE may receive the transmission from the first UE.

[0587] The transmission (or the procedure) may be (or include) data transmission, DT transmission, DO-DTT transmission, SDT, and / or RA transmission or procedure. The transmission may be associated with a procedure.

[0588] (First) signaling may be (or include) common signaling. (First) signaling may be (or include) cell-specific signaling. (First) signaling may be (or include) broadcast signaling. (First) signaling may be received by multiple UEs (or a group of UEs) in a UE group, for example. (First) signaling may be (or include) system information. (First) signaling may be (or include) paging.

[0589] (The first) signaling may be (or include) dedicated signaling. (The first) signaling may be (or include) UE-specific signaling. (The first) signaling may be (or include) RRC signaling (e.g., RRC configuration message).

[0590] (The first) signaling may be (or include) RRC signaling (e.g., RRC configuration message). (The first) signaling may be (or include) MAC signaling (e.g., MAC CE). (The first) signaling may be (or include) PHY signaling (e.g., PDCCH, DCI). (The first) signaling may be (or include) PDCCH commands.

[0591] (The first) signaling may be (or include) a carrier (signal) and / or an interrogation signal. (The first) signaling may be used to trigger (or indicate) transmission (or reception) by a UE (e.g., a first UE, a second UE). Transmission from the UE may be (or include) backscatter transmission (or reception), or may be internally generated by the UE. (The first) signaling may be used to supply power and / or energy to the UE. (The first) signaling may be used to trigger (or indicate) the RA procedure (or initial access) of the UE.

[0592] One or more pieces of information may be included in (the first) signaling. The information may (be used to) indicate which / what (type of) UE should respond to (the first) signaling. The information may (be used to) indicate which / what (type of) UE is allowed to perform (or initiate) (data) transmission or reception, e.g., (data) transmission or (second) signaling in response to (the first) signaling or information. The information may (be used to) indicate the configuration to be used for (subsequent) (data) transmission or reception (or procedure).

[0593] (The first) information and / or the first factor may be (or include or indicate or relate to) one or more of the following information. (The first) information may be used to derive one or more of the following information. (The first) information may indicate one or more of the following information. A network node (or a second UE) may derive one or more of the following information based on (the first) information. Alternatively and / or additionally, one or more of the auxiliary information mentioned above (e.g., the auxiliary information included in (the first) signaling) is described in more detail below. Whether (the first) information includes or indicates one or more of the following information may depend on whether one or more of the following information has changed compared to the previously provided (or transmitted) (the first) information, e.g., if the same, it does not include or indicate one or more of the following information. (The first) information may include or indicate one or more of the following information (omitted here) that is the same as the previously provided (or transmitted).

[0594] UE type (or device type)

[0595] The UE may indicate its UE type (or device type) explicitly or implicitly during transmission.

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

[0597] For example, the first type of UE (or device) can be device A or device B as considered in [2] 3GPP TR 38.848 V18.0.0. 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) can be a passive or semi-passive device. The first type of UE (or device) can generate UL transmission through backscattering. The first type of UE (or device) can perform backscattering transmission. The first type of UE (or device) itself may not be able to generate UL transmission internally. The first type of UE (or device) may not have the ability to generate a signal without backscattering.

[0598] For example, the second type of UE (or device) can be device C as considered in [2] 3GPP TR 38.848 V18.0.0. 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) can be an active device. The second type of UE (or device) can generate UL transmission through backscattering. The second type of UE (or device) can perform backscattering transmission. The second type of UE (or device) itself may be able to generate UL transmission internally. The second type of UE (or device) may have the ability to generate a signal without backscattering.

[0599] Power level

[0600] The UE may indicate its power level explicitly or implicitly during transmission. The UE may indicate a parameter related to the power level during transmission.

[0601] The power level may include any one or more of the following embodiments. The UE may utilize the same or different power level embodiments for different RA resource selection (steps), such as determination of the BWP, determination of the RA resource / configuration group, determination of the RA type, determination of the RA preamble, determination of the RACH occasion, and / or determination of the Physical Uplink Shared Channel (PUSCH) occasion. 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.

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

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

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

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

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

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

[0608] 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 the 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 / starting 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.

[0609] 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 a signal / channel from the network, such as the received power of a carrier (signal). The desired / derived / determined UE transmission power may be used for backscatter transmission or for UL transmission generated internally by the UE.

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

[0611] 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 (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. The desired / derived / determined UE transmission power may be used for backscatter transmission or for UL transmission generated internally by the UE.

[0612] (UL) Data type (or transmission type)

[0613] The UE may indicate (explicitly or implicitly) its data type (or transmission type) during transmission. The data type (or transmission type) may indicate the type of transmission (or data). The data type (or transmission type) may indicate the use case, traffic scenario, service type, Quality of Service (QoS), logical channel (group), and / or topology. The data type (or transmission type) may be (or include): data, signaling, DO, DO-DTT, DT, single-shot, data burst, periodic, aperiodic, delay-tolerant, and / or emergency.

[0614] (UL) data types may be distinguished at least by use case, traffic scenario, service type, QoS, logical channel (group), and / or topology. The (UL) data type 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.

[0615] (UL) Data size

[0616] The UE may indicate the data size (explicitly or implicitly) during transmission.

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

[0618] UE ID

[0619] The UE may indicate its UE ID (explicitly or implicitly) during transmission. The UE ID may be used to identify the UE (e.g., in a region). The UE ID may be stored by the UE. The UE ID may be a temporary ID.

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

[0621] UE group (ID)

[0622] The UE may indicate its UE group ID (explicitly or implicitly) during transmission.

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

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

[0625] Multiple UEs can be assigned to different UE groups or associated with different UE groups based on the UE ID. For example, a UE can be assigned to or associated with a UE group, where the UE group ID of the UE group can be determined / derived / determined at least based on the UE ID of the UE and a value. Preferably, in some embodiments, the UE group ID of the UE can be determined / derived / determined by the UE ID modulo a value. The value can be the number of UE groups. The value can be provided by the NW or be predefined or (pre)-configured. The UE group ID of the UE can be determined by a formula using the UE ID.

[0626] Multiple UEs can be assigned to different UE groups based on location. Preferably, in some embodiments, UEs in the same location and / or the same location range can be distributed to the same UE group. A UE can determine / derive its location or range based on the received carrier (signal). More specifically, a UE can determine / derive its location or range based on the received power of the carrier (signal) transmitted from the network / intermediate node and determine / derive it according to the network / intermediate node. UEs in the same location and / or the same range can represent UEs having the same received power range of the carrier (signal). Preferably and / or alternatively, in some embodiments, UEs in the same location and / or the same location range can be distributed to different UE groups. UEs that can receive the same power source, carrier, and / or NW signal among the ranges can be (randomly) distributed to different UE groups.

[0627] Reason

[0628] The reason for (first or second) signaling (or transmission) can be provided (or indicated). The reason can indicate at least one or more of the following: DO-DTT (transmission), device termination (DT) (transmission), device originator (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).

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

[0630] Location or position information

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

[0632] Information related to (data) service

[0633] 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 until the (next) data is expected to arrive, latency requirements for data (or packets), priority of data (or packets), importance of data (or packets), expected time of arrival of (next) data, expected interval between data arrivals, period of data arrival.

[0634] Information related to UE wake - up

[0635] 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: (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, time when the UE will wake up (or hopes to wake up), how long until the next wake-up of the UE. The wake-up of the UE can mean that the UE listens for DL signaling (e.g., carrier) or PDCCH.

[0636] (Required) TB size

[0637] Information related to the size of the (required) transport block (TB) 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) to the UE. The (required) TB size can be the minimum size that the UE can use to perform (data) transmission. The TB size can be a preferred value that the UE can use to perform (data) transmission.

[0638] (Required) Number of repetitions

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

[0640] Acknowledgment

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

[0642] The threshold of the first factor may be indicated or configured by the NW. Alternatively, the threshold may be determined by the UE. Alternatively, the threshold may be fixed.

[0643] The first UE may be an ambient IoT UE. The first UE may not be a normal (or traditional) UE. The first UE may be a first type of UE. The first UE may be a first type of ambient IoT UE.

[0644] The second UE may not be an ambient IoT UE. The second UE may be a normal (or traditional) UE. The second UE may be an intermediate node. The second UE may be a second type of UE. The second UE may be a second type of ambient IoT UE.

[0645] The first UE and the second UE may be different. The first UE and the second UE may have different UE types.

[0646] The first UE (or UE type) and the second UE (or UE type) may be distinguished at least based on the first factor. The first factor may be one or more of the (auxiliary) information mentioned above.

[0647] To solve the problem, the UE (e.g., the ambient IoT UE) may determine whether to trigger a random access procedure based on whether the UE belongs to the device type indicated in the first signaling. In response to the first signaling (received) triggering the random access procedure, the UE may determine whether to trigger the random access procedure based on whether the UE belongs to the device type indicated in the first signaling.

[0648] Alternatively and / or additionally, the UE (e.g., the ambient IoT UE) may trigger the random access procedure and indicate whether it can generate a transmission and / or whether the UE is equipped with a (DL / UL) amplifier. In response to the first signaling (received) triggering the random access procedure, the UE may trigger the random access procedure and perform a first transmission, and the first transmission provides information indicating whether the UE itself can generate the (said) transmission and / or whether the UE is equipped with a (DL / UL) amplifier.

[0649] In one example, a UE may receive first signaling that triggers a random access procedure, where the first signaling indicates first information of a device type. In response to the first signaling, the UE may determine whether to trigger the random access procedure based on whether the UE belongs to the device type. There may be more than one type of ambient IoT device. The first signaling may indicate which UE is allowed to trigger the random access procedure. In response to the first signaling, if at least the UE belongs to the device type, the UE may trigger the random access procedure. In response to the first signaling, if at least the UE does not belong to the device type, the UE may not trigger the random access procedure.

[0650] In one example, a UE may receive first signaling that triggers a random access procedure. In response to the first signaling, the UE may trigger the random access procedure and perform a transmission that indicates or provides third information during the random access procedure. The third information may indicate whether the UE itself is capable of generating the transmission. The third information may indicate whether the UE is equipped with a (DL / UL) amplifier. The third information may indicate which type of more than one type of ambient IoT device the UE belongs to.

[0651] In the above two examples, the first signaling may be an ambient IoT paging message. The first signaling may indicate second information of a group ID of the UE. The UE may be an ambient IoT device. More than one type of ambient IoT device may be distinguished by the method of performing the transmission. The (more than one) device types may at least include a first device type and a second device type. Devices of the first device type may be capable of generating a transmission by themselves. Devices of the second device type may generate a transmission by backscattering. Devices of the first device type may have or be equipped with a (DL / UL) amplifier. Devices of the second device type may not have or may not be equipped with a (DL / UL) amplifier.

[0652] In one example, a UE receives first signaling that triggers a random access procedure, where the first signaling indicates first information associated with a (specific) device type among (multiple device types). In response to the first signaling, the UE determines whether to trigger the random access procedure based on whether the UE belongs to the (specific) device type associated with the first information.

[0653] The first signaling is an ambient IoT paging message and / or a paging message. The random access procedure is an ambient IoT random access procedure.

[0654] The first signaling is transmitted from a reader. The reader is a network node, an intermediate node, or another UE.

[0655] In one instance, in response to (receiving) the first signaling, if at least the UE belongs to a (specific) device type associated with the first information, the UE triggers a random access procedure. In response to (receiving) the first signaling, if at least the UE does not belong to a (specific) device type associated with the first information, the UE does not trigger a random access procedure.

[0656] In one instance, the UE receives second information indicated by the first signaling, where the second information indicates a group ID of the UE or a set of UEs. In response to (receiving) the first signaling, if at least the UE belongs to a specific device type associated with the first information, the UE triggers a random access procedure, where the first signaling indicates the second information of the group ID of the UE and / or the UE belongs to the set of UEs.

[0657] In one instance, the UE receives the first signaling indicating the second information of the group ID of the UE. In response to (receiving) the first signaling, if at least the UE belongs to a (specific) device type associated with the first information and the first signaling indicates the second information of the group ID of the UE, the UE triggers a random access procedure. In response to (receiving) the first signaling, if the UE does not belong to a (specific) device type associated with the first information, or if the first signaling does not indicate the second information of the group ID of the UE, the UE does not trigger a random access procedure.

[0658] In one instance, the UE receives the first signaling indicating the second information, where the second information indicates a set of UEs. In response to (receiving) the first signaling, if at least the UE belongs to a (specific) device type associated with the first information and the UE belongs to the set of UEs, the UE triggers a random access procedure. In response to (receiving) the first signaling, if the UE does not belong to a (specific) device type associated with the first information, or if the UE does not belong to the set of UEs, the UE does not trigger a random access procedure.

[0659] In one instance, the UE receives the first signaling indicating which one or which UEs are allowed to trigger a random access procedure. In response to (receiving) the first signaling, if at least the UE belongs to a (specific) device type associated with the first information and the UE belongs to one or more UEs, the UE triggers a random access procedure. In response to (receiving) the first signaling, if the UE does not belong to a (specific) device type associated with the first information, or if the UE does not belong to one or more UEs, the UE does not trigger a random access procedure.

[0660] In one instance, the device type includes at least one of a first device type and a second device type.

[0661] In one instance, a UE belonging to the first device type can generate (the) transmission by itself. A UE belonging to the second device type generates (the) transmission by backscattering.

[0662] In one example, a UE belonging to a first device type has or is equipped with an amplifier. A UE belonging to a second device type does not have or is not equipped with an amplifier.

[0663] In one example, the first and second device types are distinguished by at least any one of energy storage, power level, and / or device size.

[0664] In one example, the UE receives first signaling that triggers a random access procedure. In response to the first signaling, the UE triggers the random access procedure. The UE performs a transmission that indicates or provides third information during the random access procedure. The third information indicates the device type of the UE. The device type of the UE is distinguished by or associated with any one of the method of performing the transmission, being equipped with an amplifier, energy storage, power level, and / or device size. The first signaling is an ambient IoT paging message and / or a paging message. The random access procedure is an ambient IoT random access procedure. The first signaling is transmitted from a reader. The first transmission is transmitted to the reader during the random access procedure. The reader is a network node, an intermediate node, or another UE.

[0665] In one example, the third information indicates which type of more than one type of ambient IoT device the UE belongs to. More than one type of ambient IoT device is distinguished by any one of the method of performing the transmission, being equipped with an amplifier, energy storage, power level, and / or device size.

[0666] In one example, the third information indicates the device type of the UE including any one of the following: generating the transmission itself or generating the transmission by backscattering, being equipped with an amplifier or not being equipped with an amplifier, or being distinguished by energy storage, power level, and / or device size.

[0667] The UE may explicitly indicate via the first transmission whether it is an ambient IoT UE or a legacy UE. The UE may explicitly indicate via the first transmission which UE type it is. The UE may implicitly indicate whether it is an ambient IoT UE or a legacy UE by selecting a BWP, RA resource, RA group, RA type, RA preamble (group), and / or RACH occasion. The UE may implicitly indicate which UE type it is by selecting a BWP, RA resource, RA group, RA type, RA preamble (group), and / or RACH occasion.

[0668] The UE may receive configurations related to ambient IoT. The UE may receive RA configurations and / or RA resources. The RA resources may include a BWP, an RA resource / configuration group, an RA preamble (group), a RACH occasion, and / or a PUSCH occasion.

[0669] As mentioned above, in the RA procedure, the UE may fallback or switch the RA resource (selection). If, when, or in response to the transmission counter (e.g., PREAMBLE_TRANSMISSION_COUNTER) being higher than or equal to the configured value, receiving a second or fourth transmission including an indication, and / or in response to the response window (e.g., msgB-ResponseWindow, ra-ResponseWindow) and / or the contention resolution timer (e.g., ra-ContentionResolutionTimer) expiring, the UE may fallback or switch the RA resource (selection). The UE may select another RA resource and / or perform another RA resource selection (step).

[0670] Throughout this disclosure, the "RA procedure" may be replaced by the "(initial) access procedure".

[0671] Throughout this disclosure, the "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.

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

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

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

[0675] Throughout this disclosure, "PUSCH" may be replaced by "uplink shared channel" or "PUSCH for ambient IoT".

[0676] Throughout this disclosure, "PDCCH" may be replaced by "downlink control channel", "downlink control information", or "PDCCH for ambient IoT".

[0677] Throughout this disclosure, the Physical Downlink Shared Channel ("Physical Downlink Shared Channel, PDSCH") may be replaced by "downlink shared channel" or "PDSCH for ambient IoT".

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

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

[0680] Throughout this disclosure, a "cell" may be replaced by a "middle node".

[0681] Throughout this disclosure, a network (node) may be changed / represented / replaced by a middle node.

[0682] A UE may be referred to as a UE, the access spectrum (AS) layer of the UE, the A-IoT layer of the UE, the RRC layer of the UE, the MAC entity of the UE, or the physical layer of the UE.

[0683] Throughout this disclosure, a UE may be an environmental IoT device / UE. A UE may be a device for environmental IoT. A UE may be a device with the ability of environmental IoT. A UE may be an NR device. A UE may be a Long Term Evolution (LTE) device. A UE may be an IoT device. A UE may be a wearable device. A UE may be a sensor. A UE may be a fixed device. A UE may be a tag. Throughout this disclosure, the following may be interchangeable: (environmental IoT) UE, (environmental IoT) device. Throughout this disclosure, the following may be interchangeable: ordinary UE, traditional UE.

[0684] A UE may not be a traditional UE. A traditional UE may be a non-environmental IoT device. A traditional UE may execute different programs from those of an environmental IoT UE. A UE may be a traditional UE with the ability to execute environmental IoT programs.

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

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

[0687] See Figure 10 , by this and other concepts, systems, and methods of the present invention, a method 1000 for a first UE in a wireless communication system includes initiating or performing a transmission to a network node (or a second UE), where the transmission includes at least (first) information (step 1002).

[0688] In various embodiments, the (first) information includes a device type and / or a UE type.

[0689] In various embodiments, the (first) information includes a data type and / or a data size.

[0690] In various embodiments, the (first) information includes a UE ID and / or a UE group ID.

[0691] In various embodiments, the (first) information includes a cause value.

[0692] In various embodiments, the (first) information includes location information.

[0693] In various embodiments, the (first) information includes time information (related to data arrival).

[0694] In various embodiments, the (first) information includes time information (related to UE wake-up).

[0695] In various embodiments, the (first) information includes the required TB size.

[0696] In various embodiments, the (first) information includes an acknowledgement.

[0697] Return to reference Figure 3 and 4 , in one or more embodiments, from the perspective of a first UE 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) initiate or perform a transmission to a network node (or a second UE), where the transmission includes at least the (first) information. In addition, CPU 308 can execute program code 312 to perform all the described actions, steps, and methods described above, below, or elsewhere herein.

[0698] Return to 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) initiate or perform a transmission to a network node (or a second UE), where the transmission includes at least the (first) information. In addition, CPU 308 can execute program code 312 to perform all the described actions, steps, and methods described above, below, or elsewhere herein.

[0699] Currently, when initiating the RA procedure, the UE selects a carrier (e.g., Supplementary Uplink (SUL), Normal Uplink (NUL)), performs BWP operations and then sets the RA type (e.g., 2-step RA, 4-step RA). The UE sets the RA type based on the RA configuration with reference to the downlink path loss and the Reference Signal Received Power (RSRP). The UE will select a Synchronization Signal Block (SSB) (or Channel State Information Reference Signal (CSI-RS)). The selected SSB (or CSI-RS) can be used as a downlink path loss reference. For example, the UE derives / determines the DL path loss based on the RSRP of the selected SSB (or CSI-RS). The UE will select an RA preamble and a RACH occasion associated with the selected SSB (or CSI-RS). The UE will select an RA preamble from two RA preamble groups based on the UL data size.

[0700] Due to the characteristics of the ambient IoT UE, the RA procedure and RA resources will be different from those of traditional UEs. In the RA procedure (e.g., for ambient IoT), the UE (e.g., ambient IoT UE / device) 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. Alternatively, there is no response to the first transmission. In other words, the RA procedure is completed in response to transmitting the first transmission. 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, the NW may transmit a fourth transmission to the UE in response to the reception of the third transmission. In response to transmitting the third transmission or after transmitting the third transmission, the UE may receive the fourth transmission from the NW.

[0701] The first transmission may be Msg1 and / or MSGA (transmission). The first transmission may include an RA preamble transmission and / or an 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 PRACH and / or a transmission via the PUSCH.

[0702] The second transmission may be Msg2, RAR, and / or MSGB (transmission). The second transmission may be an 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 comprise transmission via PDCCH and / or PDSCH. The second transmission may provide / indicate a UL grant for scheduling UL resources.

[0703] The third transmission may be Msg3 (transmission). The third transmission may be an uplink transmission using the UL grant / resources provided / indicated by the second transmission. Preferably, in some embodiments, the third transmission may include a second uplink data transmission. The third transmission may comprise transmission via PUSCH.

[0704] The fourth transmission may be 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 comprise transmission via PDCCH and / or PDSCH.

[0705] RA resource selection (step) may be performed in any order. The second type of RA resource selection (step) may depend on the first type of RA resource selection (step). RA resource selection (step) may be performed before the first transmission. RA resource selection (step) may be performed after initiating or triggering an RA procedure, when initiating or triggering an RA procedure, or in response to initiating or triggering an RA procedure.

[0706] In an RA procedure (e.g., for ambient IoT), the UE may not perform UL carrier selection. The UE may not select a UL carrier (e.g., SUL, NUL). The UE may not be configured with supplementary uplink. The UE may not utilize the RSRP threshold of SUL (e.g., rsrp-ThresholdSSB-SUL) to evaluate the RSRP of the downlink path loss reference. The UE may determine the UL carrier based on the non-selection of the RA resource. Preferably, in some embodiments, the UE may determine the UL carrier based on the frequency of the received / detected carrier (signal) (e.g., DL carrier or DL band). For example, the UL carrier is associated with or corresponds to the frequency of the received / detected carrier (signal) (e.g., DL carrier or DL band).

[0707] In an RA procedure (e.g., for environmental IoT), the UE may not perform SSB selection and / or CSI-RS selection. The UE may not select SSB / CSI-RS. The UE may not be configured with parameters associated with a beam. The SSB and / or CSI-RS may not be (explicitly) provided to the UE. The UE may not evaluate the Synchronization Signal Reference Signal Received Power (SS-RSRP) using the RSRP threshold of the SSB (e.g., rsrp-ThresholdSSB, msgA-RSRP-ThresholdSSB). The UE may not evaluate the CSI-RSRP using the RSRP threshold of the CSI-RS (e.g., rsrp-ThresholdCSI-RS). The UE may not select RA resources based on the SSB / CSI-RS. Alternatively, (only) RA resources / configurations associated with a specific or the same SSB are allowed. The UE may (always) select a specific or the same SSB.

[0708] One or more of the above RA resource selection / steps may be combined.

[0709] The above RA resource selection (step) may be performed based on a first factor. The first factor may be one or more of the following information as described above: UE type, power level, data type, data size, UE ID, and / or UE group.

[0710] The association between the first factor and the RA resource may be indicated or configured by the NW. Alternatively, the association may be determined by the UE. Alternatively, the association may be fixed.

[0711] One or more of the above embodiments, concepts, methods, and examples of the first factor may be combined.

[0712] Throughout this disclosure, the BWP may be referred to as the initial BWP and / or replaced by the initial BWP.

[0713] The UE can be configured with one or more BWPs of a cell. Alternatively and / or additionally, the cell can include or indicate more than one BWP (for environmental IoT). The BWP can be a BWP configured with RA resources and / or an RA configuration (for environmental IoT). The BWP can be a BWP configured with a PRACH occasion (for environmental IoT). The BWP can be a BWP on which the UE can execute an RA procedure. The BWP can be the initialUplinkBWP. The UE can be configured with different BWPs in different bands and / or frequencies of the cell. The UE can be configured with multiple BWPs that have an in-band spectrum deployment to an NR cell. Different / separate RA configurations and / or RA resources can be configured on more than one BWP. The RA configuration and / or RA resources can correspond to, be associated with, and / or be used by the (one or more) UEs and / or a first factor. The BWP can be a UL BWP.

[0714] The UE can perform BWP selection in an RA procedure, e.g., after triggering the RA procedure or in response to triggering the RA procedure. After selecting the initial BWP or in response to selecting the initial BWP, the UE can perform other kinds of RA resource selection (steps) (e.g., based on the selected initial BWP) and / or perform a first transmission (e.g., on the selected BWP). When the UE selects a BWP of a cell, the UE can switch the (in-activation) BWP of the cell. When the UE selects a BWP of a cell, the UE can deactivate the current BWP and / or activate the selected BWP of the cell. The UE can select a BWP based on a first factor. After selecting a BWP of a cell, the UE does not switch the BWP of the cell during the RA procedure. Alternatively, the UE is allowed to switch the BWP of the cell during the RA procedure, e.g., based on a first factor.

[0715] For example, if at least the UE is a first type of UE, the UE can select a first BWP of the cell. If at least the UE is a second type of UE, the UE can select a second BWP of the cell.

[0716] For example, the UE can select a BWP based on one or more thresholds of power levels. The UE can select a first BWP of the cell or a second BWP of the cell based on different power levels. If at least the (power level) threshold is satisfied, the UE can select a BWP. If the threshold is not at least satisfied, the UE can not select a BWP. Once the threshold is satisfied, the UE can select a BWP. The UE can not select a BWP until the threshold is satisfied. Preferably, in some embodiments, if a second threshold is satisfied, the UE can select a second initial BWP. If the second threshold is not satisfied and / or if the first threshold is satisfied, the UE can select a first initial BWP.

[0717] For example, the UE may select a first BWP of a cell for a first UL data type. The UE may select a second BWP of the cell for a second UL data type.

[0718] For example, the UE may select a BWP based on a threshold of UL data size. The UE may select a first BWP of the cell or a second BWP of the cell based on different UL data sizes.

[0719] For example, the UE may select a BWP based on its UE ID (using a formula of its UE ID). The UE may select a first BWP of the cell or a second BWP of the cell based on its UE ID (using a formula of its UE ID). For example, the modulo (of the UE ID) of (the number of BWPs of the cell in which the UE will select a BWP) may be used to derive or may be equal to the index of the BWP that the UE will select.

[0720] For example, the UE may select a BWP based on its UE group (ID) (using a formula of its UE group (ID)). The UE may select a first BWP of the cell or a second BWP of the cell based on its UE group (ID). The UE may select a first BWP of the cell or a second BWP of the cell based on a formula using its UE group ID. For example, the modulo (of the UE group ID) of (the number of BWPs of the cell in which the UE will select a BWP) may be used to derive or may be equal to the index of the BWP that the UE will select.

[0721] For example, the UE may select a BWP based on its UE ID and its UE group (ID) (using a formula of its UE ID and its UE group (ID)).

[0722] For example, the UE may randomly (with equal probability) select a BWP from more than one BWP of a cell.

[0723] Preferably, in some embodiments, the BWP (above or below) may be changed / represented / replaced by a frequency (sub)-band or a set of frequency resources.

[0724] Preferably, in some embodiments, when the UE receives / detects a carrier (signal), the UE may derive / determine a BWP, an (initial) frequency (sub)-band, or an (initial) set of frequency resources at least based on the frequency (e.g., a DL carrier or a DL band). Preferably, in some embodiments, the UE may derive / determine a BWP, an (initial) frequency (sub)-band, or an (initial) set of frequency resources at least based on the BWP, frequency (sub)-band, or frequency resource set information provided by the network.

[0725] Throughout this disclosure, an RA configuration may be referred to as an RA configuration group, an RA resource, and / or an RA resource group, and / or may be replaced by an RA configuration group, an RA resource, and / or an RA resource group.

[0726] The UE may be configured with multiple RA configurations for a cell. Alternatively and / or additionally, the cell may provide or indicate multiple RA configurations (for ambient IoT). The UE may be configured with multiple RA resource groups. Alternatively and / or additionally, the cell may provide or indicate multiple RA resource groups (for ambient IoT). The UE may be configured with multiple RA configuration groups. Alternatively and / or additionally, the cell may provide or indicate multiple RA configuration groups (for ambient IoT). The multiple RA configurations, RA resource groups, and / or RA configuration groups may be configured on different BWPs. The multiple RA configurations, RA resource groups, and / or RA configuration groups may be configured on the same BWP. The RA configurations, RA resource groups, and / or RA configuration groups may correspond to, be associated with, and / or be used by one or more UEs and / or a first factor.

[0727] The RA configuration / resource group may be defined, configured, or selected based on a first factor. The RA configuration / resource group may be associated with a power level, e.g., determined by one or more thresholds. Each power level may be associated with a (separate) RA configuration of the cell or a set of RA resources and / or be configured with a (separate) RA configuration of the cell or a set of RA resources. The RA configuration group may be associated with a data size level, e.g., determined by one or more thresholds. Each data size level may be associated with a (separate) RA configuration of the cell or a set of RA resources and / or be configured with a (separate) RA configuration of the cell or a set of RA resources.

[0728] The UE may, for example, select an RA configuration, an RA resource group, and / or an RA configuration group after triggering an RA procedure, selecting a BWP, selecting an RA type, or in response to triggering an RA procedure, selecting a BWP, selecting an RA type. After selecting an RA configuration or in response to selecting an RA configuration, the UE may perform other kinds of RA resource selection steps (e.g., based on the selected RA configuration) and / or perform a first transmission (e.g., using the selected RA configuration). The UE may select an RA configuration, an RA resource group, and / or an RA configuration group of a cell based on a first factor.

[0729] For example, if at least the UE is a first type of UE, the UE may select a first RA configuration of the cell. If at least the UE is a second type of UE, the UE may select a second RA configuration of the cell.

[0730] For example, the UE may select an RA configuration based on one or more thresholds of the power level. The UE may select a first RA configuration of a cell or a second RA configuration of the cell based on different power levels. The UE may select a first RA configuration of a cell, a second RA configuration of the cell, or a third RA configuration of the cell based on different power levels. If at least the (power level) threshold is satisfied, the UE may select an RA configuration. If the threshold is not at least satisfied, the UE may not select an RA configuration. Once the threshold is satisfied, the UE may select an RA configuration. The UE may not select an RA configuration until the threshold is satisfied. Preferably, in some embodiments, if a second threshold is satisfied, the UE may select a second RA configuration. If the second threshold is not satisfied and / or if a first threshold is satisfied, the UE may select a first RA configuration.

[0731] For example, the UE may select a first RA configuration of a cell for a first UL data type. The UE may select a second RA configuration of a cell for a second UL data type.

[0732] For example, the UE may select an RA configuration based on a threshold of the UL data size. The UE may select a first RA configuration of a cell or a second RA configuration of the cell based on different UL data sizes. The UE may select a first RA configuration of a cell, a second RA configuration of the cell, and / or a third RA configuration of the cell based on different UL data sizes.

[0733] For example, the UE may select an RA configuration based on its UE ID (using a formula of its UE ID). The UE may select a first RA configuration of a cell or a second RA configuration of the cell based on its UE ID (using a formula of its UE ID). For example, the modulo (of the UE ID) (with the number of RA configurations of the cell in which the UE will select an RA configuration) may be used to derive or may be equal to the index of the RA configuration to be selected by the UE.

[0734] For example, the UE may select an RA configuration based on its UE group (ID) (using a formula of its UE group (ID)). The UE may select a first RA configuration of a cell or a second RA configuration of the cell based on its UE group (ID). The UE may select a first RA configuration of a cell or a second RA configuration of the cell based on a formula using its UE group ID. For example, the modulo (of the UE group ID) (with the number of RA configurations of the cell in which the UE will select an RA configuration) may be used to derive or may be equal to the index of the BWP to be selected by the UE.

[0735] For example, the UE may select an RA configuration based on its UE ID and its UE group (ID) (using a formula of its UE ID and its UE group (ID)).

[0736] For example, the UE may randomly (with equal probability) select an RA configuration from multiple RA configurations of a cell.

[0737] The UE may be configured with 2-step RA and / or 4-step RA. Alternatively and / or additionally, the cell may include or indicate a 2-step RA configuration and / or a 4-step RA configuration (for environmental IoT). The UE may (always) be configured with both 2-step RA and 4-step RA. The UE may (always) be configured with 2-step RA and not 4-step RA. The UE may not use or support 4-step RA. The UE may not (be allowed to) configure 4-step RA. Alternatively and / or additionally, the cell may not (be allowed to) include or indicate a 4-step RA configuration (for environmental IoT). The UE may perform 2-step RA for the RA procedure. The 2-step RA may not include a third transmission or a fourth transmission. The UE may perform 4-step RA for the RA procedure. The 2-step RA may be an RA type having (at least) a first transmission and a second transmission. The 4-step RA may be an RA type having (at least) a first transmission, a second transmission, a third transmission, and a fourth transmission. In the 2-step RA procedure, the UE may transmit UL data / signaling in the first transmission. In the 4-step RA procedure, the UE may not transmit UL data / signaling in the first transmission. In the 4-step RA procedure, the UE may transmit UL data / signaling in the third transmission. The RA type may correspond to (one or more) UEs and / or a first factor, be associated with and / or used by (one or more) UEs and / or a first factor.

[0738] The UE may, for example, select an RA type after triggering the RA procedure, selecting a BWP, selecting an RA configuration / resource group, or in response to triggering the RA procedure, selecting a BWP, selecting an RA configuration / resource group. After selecting the RA type or in response to selecting the RA type, the UE may perform other kinds of RA resource selection steps (e.g., based on the selected RA type) and / or perform the first transmission. The UE may (always) select 2-step RA. The UE may not select an RA type based on the RSRP of the downlink path loss reference. The UE may not select an RA type based on the RSRP of the downlink path loss reference. The UE may not select an RA type based on an RSRP threshold, e.g., (msgA-RSRP-Threshold). The UE may select an RA type based on a first factor.

[0739] For example, the UE may select a first RA type for a first type of UE. The UE may select a second RA type for a second type of UE. When / if the UE is a first type of UE, the UE may select a first RA type for the first type of UE. When / if the UE is a second type of UE, the UE may select a second RA type for the second type of UE.

[0740] For example, the UE may select an RA type based on one or more thresholds of the power level. The UE may select a first RA type or a second RA type based on different power levels. If the threshold is met, the UE may select an RA type. If the threshold is not met, the UE may not select an RA type. Once the threshold is met, the UE may select an RA type. The UE may not select an RA type until the threshold is met.

[0741] For example, the UE may select a first RA type for a first UL data type. The UE may select a second RA type for a second UL data type.

[0742] For example, the UE may select an RA type based on a threshold of the UL data size. The UE may select a first RA type or a second RA type based on different UL data sizes.

[0743] For example, the UE may select a first RA type or a second RA type based on a formula using its UE ID.

[0744] For example, the UE may select a first RA type or a second RA type based on its UE group (ID). The UE may select a first RA type or a second RA type based on a formula using its UE group ID.

[0745] The UE may be configured with one or more RA preamble groups of the cell, e.g., in the RA configuration. The RA preamble group(s) may correspond to and / or be associated with and / or be used by one or more UEs and / or a first factor. The RA preamble group may contain a set of RA preambles or an RA preamble index.

[0746] The UE may perform RA preamble (group) selection in the RA procedure, for example, after triggering the RA procedure, selecting a BWP, selecting an RA configuration / resource group, setting the RA type, or in response to triggering the RA procedure, selecting a BWP, selecting an RA configuration / resource group, setting the RA type. The UE may select an RA preamble group and then (randomly) select an RA preamble (index) among the selected RA preamble group. After selecting the RA preamble (group) or in response to selecting the RA preamble (group), the UE may perform other types of RA resource selection steps (e.g., based on the selected RA preamble (group)) and / or perform a first transmission (e.g., using the selected RA preamble). The UE may select an RA preamble (group) based on an NW indication, e.g., via SIB, paging, or PDCCH. The UE may select an RA preamble (group) based on a first factor.

[0747] For example, if at least the UE is a first type of UE, the UE may select a first RA preamble group of a cell (in the RA configuration). If at least the UE is a second type of UE, the UE may select a second RA preamble group of a cell (in the RA configuration).

[0748] For example, the UE may select an RA preamble group based on one or more thresholds of power levels. The UE may select a first RA preamble group of a cell (in the RA configuration) or a second RA preamble group of a cell (in the RA configuration) based on different power levels. The UE may select a first RA preamble group of a cell (in the RA configuration), a second RA preamble group of a cell (in the RA configuration), and / or a third RA preamble group of a cell (in the RA configuration) based on different power levels. If at least the threshold is met, the UE may select an RA preamble (group or index). If the threshold is not at least met, the UE may not select an RA preamble (group or index). Once the threshold is met, the UE may select an RA preamble (group or index). The UE may not select an RA preamble (group or index) until the threshold is met. Preferably, in some embodiments, if a second threshold is met, the UE may select a second RA preamble (group or index). If the second threshold is not met and / or if a first threshold is met, the UE may select a first RA preamble (group or index).

[0749] For example, the UE may select a first RA preamble group of a cell (in the RA configuration) for a first UL data type. The UE may select a second RA preamble group of a cell (in the RA configuration) for a second UL data type. The UE may select a third RA preamble group of a cell (in the RA configuration) for a third UL data type.

[0750] For example, the UE may select an RA preamble group based on a threshold of UL data size. The UE may select a first RA preamble group of a cell (in the RA configuration) or a second RA preamble group of a cell (in the RA configuration) based on different UL data sizes. The UE may select a first RA preamble group of a cell (in the RA configuration), a second RA preamble group of a cell (in the RA configuration), and / or a third RA preamble group of a cell (in the RA configuration) based on different UL data sizes.

[0751] For example, a UE may select a RA preamble (group or index) based on its UE ID (using a formula for its UE ID). The UE may select a first RA preamble (group or index) of a cell (in the RA configuration) or a second RA preamble (group or index) of the cell (in the RA configuration) based on its UE ID. The UE may select a first RA preamble (group or index) of a cell (in the RA configuration), a second RA preamble (group or index) of the cell (in the RA configuration), and / or a third RA preamble (group or index) of the cell (in the RA configuration) based on its UE ID. For example, the UE ID modulo (the number of RA preamble groups in the cell in which the UE will select a RA preamble group (in the RA configuration)) may be used to derive or may be equal to the index of the RA preamble group that the UE will select. For example, the UE ID modulo (the number of RA preamble indices in the cell in which the UE will select a RA preamble index (in the RA preamble group) (in the RA configuration)) may be used to derive or may be equal to the index of the RA preamble index that the UE will select.

[0752] For example, a UE may select a RA preamble (group or index) based on its UE group (ID) (using a formula for its UE group (ID)). The UE may select a first RA preamble (group or index) of a cell (in the RA configuration) or a second RA preamble (group or index) of the cell (in the RA configuration) based on its UE group ID. The UE may select a first RA preamble (group or index) of a cell (in the RA configuration), a second RA preamble (group or index) of the cell (in the RA configuration), and / or a third RA preamble (group or index) of the cell (in the RA configuration) based on its UE group ID. The UE may select a first RA preamble (group or index) of a cell (in the RA configuration) or a second RA preamble (group or index) of the cell (in the RA configuration) based on a formula using its UE group ID. The UE may select a first RA preamble (group or index) of a cell (in the RA configuration), a second RA preamble (group or index) of the cell (in the RA configuration), and / or a third RA preamble (group or index) of the cell (in the RA configuration) based on a formula using its UE group ID. For example, the UE group ID modulo (the number of RA preamble groups in the cell in which the UE will select a RA preamble group (in the RA configuration)) may be used to derive or may be equal to the index of the RA preamble group that the UE will select. For example, the UE group ID modulo (the number of RA preamble indices in the cell in which the UE will select a RA preamble index (in the RA preamble group) (in the RA configuration)) may be used to derive or may be equal to the index of the RA preamble index that the UE will select.

[0753] For example, the UE may select a RA preamble (group or index) based on its UE ID and its UE group ID (using a formula of its UE ID and its UE group ID).

[0754] For example, the UE may randomly (with equal probability) select a RA preamble group from more than one RA preamble group (in the RA configuration) of the cell.

[0755] For example, the UE may randomly (with equal probability) select a RA preamble index from more than one RA preamble index (in the RA preamble group) (in the RA configuration) of the cell.

[0756] The number of RA preambles may be different in each RA preamble group.

[0757] If the UE has a lower power based on, for example, the power level, the UE may use a RA preamble group with more RA preambles. If the UE has a higher power based on, for example, the power level, the UE may use a RA preamble group with more RA preambles. If the UE has more critical data based on, for example, the data type, the UE may use a RA preamble group with more RA preambles. If the UE has less available data based on, for example, the UL data size, the UE may use a RA preamble group with more RA preambles. If the UE has more available data based on, for example, the UL data size, the UE may use a RA preamble group with more RA preambles. If the UE is in a UE group with more UEs based on, for example, the UE group ID, the UE may use a RA preamble group with more RA preambles.

[0758] If the UE has a higher power based on, for example, the power level, the UE may use a RA preamble group with fewer RA preambles. If the UE has a lower power based on, for example, the power level, the UE may use a RA preamble group with fewer RA preambles. If the UE has less critical data based on, for example, the data type, the UE may use a RA preamble group with fewer RA preambles. If the UE has less available data based on, for example, the UL data size, the UE may use a RA preamble group with fewer RA preambles. If the UE has more available data based on, for example, the UL data size, the UE may use a RA preamble group with fewer RA preambles. If the UE is in a UE group with fewer UEs based on, for example, the UE group ID, the UE may use a RA preamble group with fewer RA preambles.

[0759] The RACH occasion (RO) and / or the PUSCH occasion may be configured / included in the RA configuration (of the cell). The RACH occasion and / or the PUSCH occasion may correspond to and / or be associated with and / or be used by one or more UEs and / or a first factor. The RACH occasion may be a time / frequency resource for RACH transmission. The PUSCH occasion may be a time / frequency resource for PUSCH transmission.

[0760] The UE may, for example, perform RO and / or PUSCH occasion selection in the RA procedure after triggering the RA procedure, selecting a BWP, selecting an RA configuration / resource group, setting the RA type, selecting an RA preamble, selecting an RO, or in response to triggering the RA procedure, selecting a BWP, selecting an RA configuration / resource group, setting the RA type, selecting an RA preamble, selecting an RO. After selecting the RO and / or PUSCH occasion or in response to selecting the RO and / or PUSCH occasion, the UE may perform other kinds of RA resource selection steps (e.g., based on the selected RO and / or PUSCH occasion) and / or perform a first transmission (e.g., using the selected RO and / or PUSCH occasion). The UE may select an RO and / or PUSCH occasion based on the selected RA preamble (group or index) and / or an RO and / or PUSCH occasion associated with the selected RA preamble (group or index). The UE may select an RO and / or PUSCH occasion based on the selected RA resource / configuration and / or the nearest RO and / or PUSCH occasion associated with the selected RA resource / configuration. The UE may (randomly) select an RO and / or PUSCH occasion based on the selected RA resource / configuration and / or an RO and / or PUSCH occasion associated with the selected RA resource / configuration among the nearest N ROs and / or PUSCH occasions. N may be indicated or configured by the NW. Alternatively, N may be determined by the UE. Alternatively, N may be fixed. N may be related to the number of UE groups. N may be an integer and / or greater than 1 (or 2 or 3). The UE may select an RO and / or PUSCH occasion based on a first factor.

[0761] For example, if at least the UE is a first type of UE, the UE may select the first RO and / or PUSCH occasion (in the RA configuration) of the cell. If at least the UE is a second type of UE, the UE may select the second RO and / or PUSCH occasion (in the RA configuration) of the cell.

[0762] For example, the UE may select the RO and / or PUSCH timing based on one or more thresholds of the power level. The UE may select the first RO and / or PUSCH timing of the cell (in the RA configuration) or the second RO and / or PUSCH timing of the cell (in the RA configuration) based on different power levels. The UE may select the first RO and / or PUSCH timing of the cell (in the RA configuration), the second RO and / or PUSCH timing of the cell (in the RA configuration), and / or the third RO and / or PUSCH timing of the cell (in the RA configuration) based on different power levels. If at least the threshold is met, the UE may select the RO and / or PUSCH timing. If the threshold is not at least met, the UE may not select the RO and / or PUSCH timing. Once the threshold is met, the UE may select the RO and / or PUSCH timing. The UE may not select the RO and / or PUSCH timing until the threshold is met. Preferably, in some embodiments, if a second threshold is met, the UE may select the second RO and / or PUSCH timing. If the second threshold is not met and / or if the first threshold is met, the UE may select the first RO and / or PUSCH timing.

[0763] For example, the UE may select the first RO and / or PUSCH timing of the cell (in the RA configuration) for a first UL data type. The UE may select the second RO and / or PUSCH timing of the cell (in the RA configuration) for a second UL data type. The UE may select the third RO and / or PUSCH timing of the cell (in the RA configuration) for a third UL data type.

[0764] For example, the UE may select the RO and / or PUSCH timing based on a threshold of the UL data size. The UE may select the first RO and / or PUSCH timing of the cell (in the RA configuration) or the second RO and / or PUSCH timing of the cell (in the RA configuration) based on different UL data sizes. The UE may select the first RO and / or PUSCH timing of the cell (in the RA configuration), the second RO and / or PUSCH timing of the cell (in the RA configuration), and / or the third RO and / or PUSCH timing of the cell (in the RA configuration) based on different UL data sizes.

[0765] For example, the UE may select RO and / or PUSCH moments based on its UE ID (using a formula of its UE ID). The UE may select the first RO and / or PUSCH moment (in the RA configuration) or the second RO and / or PUSCH moment (in the RA configuration) of the cell based on its UE ID (using a formula of its UE ID). The UE may select the first RO and / or PUSCH moment (in the RA configuration), the second RO and / or PUSCH moment (in the RA configuration), and / or the third RO and / or PUSCH moment (in the RA configuration) of the cell based on its UE ID (using a formula of its UE ID). For example, the modulo (of the UE ID) of (the number of RO and / or PUSCH moments of the cell in which the UE will select RO and / or PUSCH moments (in the RA configuration)) may be used to derive or may be equal to the index of the RO and / or PUSCH moment that the UE will select.

[0766] For example, the UE may select RO and / or PUSCH moments based on its UE group ID (using a formula of its UE group ID). The UE may select the first RO and / or PUSCH moment (in the RA configuration) or the second RO and / or PUSCH moment (in the RA configuration) of the cell based on its UE group ID (using a formula of its UE group ID). The UE may select the first RO and / or PUSCH moment (in the RA configuration), the second RO and / or PUSCH moment (in the RA configuration), and / or the third RO and / or PUSCH moment (in the RA configuration) of the cell based on its UE group ID (using a formula of its UE group ID). For example, the modulo (of the UE group ID) of (the number of RO and / or PUSCH moments of the cell in which the UE will select RO and / or PUSCH moments (in the RA configuration)) may be used to derive or may be equal to the index of the RO and / or PUSCH moment that the UE will select.

[0767] For example, the UE may select RO and / or PUSCH moments based on its UE ID and its UE group ID (using a formula of its UE ID and its UE group ID).

[0768] For example, the UE may randomly (with equal probability) select RO and / or PUSCH moments from (several) RO and / or PUSCH moments of the cell (in the RA configuration).

[0769] In the RA procedure (e.g., for ambient IoT), the UE may perform one or more selections (steps) of the following types of RA resources (e.g., resource selection for the first transmission):

[0770] -(Initial) (UL) BWP (for environmental IoT);

[0771] -RA resources / configurations (group) (for environmental IoT);

[0772] -RA / transmission type (for environmental IoT), e.g., based on a first factor;

[0773] -RA preamble (group and / or index) (for environmental IoT);

[0774] -RACH timing (for environmental IoT);

[0775] -PUSCH timing (for environmental IoT); and / or

[0776] -PDRCH timing (for environmental IoT).

[0777] Throughout this disclosure, "DL" may be replaced by "Reader to Device (R2D)". A DL transmission may be a transmission from a reader to a device and / or an R2D transmission, referred to as a transmission from a reader to a device and / or an R2D transmission, and / or supplemented by a transmission from a reader to a 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. A DL transmission and / or DL data may include an indication, configuration, signal / signaling / signalling, and / or message from the reader.

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

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

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

[0781] Throughout this disclosure, a "random access (RA) procedure" can 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. Resources and / or configurations for the access procedure can include, for example, PDRCH resources, time, frequency, and / or frequency band for D2R transmission. Resources and / or configurations for the access procedure can include, for example, parameters, random numbers, group numbers, and / or auxiliary information for D2R transmission.

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

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

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

[0785] In response to (receiving) a signaling, the UE may trigger / execute the procedure and / or the following transmissions. In the procedure, the UE may transmit a first transmission to the NW / intermediate node. The NW / intermediate node 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 / intermediate node. In response to (receiving) the second transmission, the UE may transmit a third transmission to the NW / intermediate node. 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 the reception of the third transmission. 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.

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

[0787] The second transmission in the 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, such as the third transmission.

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

[0789] The fourth transmission in the 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.

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

[0791] The first transmission, the third transmission, and the fifth transmission may be D2R transmissions and / or PDRCH transmissions. The signaling, the second transmission, and the fourth transmission may be R2D transmissions and / or PRDCH transmissions. The signaling and the second transmission may be broadcast, provided, and / or transmitted to one or more UEs. The second transmission and 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 procedure.

[0792] 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, Msg5 may be replaced by a fifth transmission.

[0793] 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., 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, UEID, group ID, contention resolution identification, and / or 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.

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

[0795] Throughout this disclosure, the "Common Control Channel (CCCH)", "PRACH", "RACH", "PUSCH", and / or "PUCCH" may be the "Physical Device-to-Reader Channel", a channel for transmission from the device to the reader, and / or PDRCH, composed of the "Physical Device-to-Reader Channel", a channel for transmission from the device to the reader, and / or PDRCH, replaced by the "Physical Device-to-Reader Channel", a channel for transmission from the device to the reader, and / or PDRCH, and / or referred to as the "Physical Device-to-Reader Channel", a channel for transmission from the device to the reader, and / or PDRCH. Throughout this disclosure, the "PDSCH" and / or "PDCCH" may be the "Physical Reader-to-Device Channel", a channel for transmission from the reader to the device, and / or PRDCH, composed of the "Physical Reader-to-Device Channel", a channel for transmission from the reader to the device, and / or PRDCH, replaced by the "Physical Reader-to-Device Channel", a channel for transmission from the reader to the device, and / or PRDCH, and / or referred to as the "Physical Reader-to-Device Channel", a channel for transmission from the reader to the device, and / or PRDCH. The D2R transmission may be via the PDRCH transmission. The R2D transmission may be via the PRDCH transmission.

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

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

[0798] The UE may select (steps) (e.g., determination of PDRCH time instants) for different RA resources using the same or different power level embodiments.

[0799] The UE may determine / deduce its location or range based on the R2D signal / channel and / or PRDCH. More specifically, the UE may determine / deduce its location or range from the network / intermediate node based on the 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 R2D signal / channel and / or PRDCH. Preferably and / or alternatively, in some embodiments, UEs in the same location and / or the same location range may be distributed into different UE groups. UEs that can receive the same NW signal (e.g., R2D signal / channel, PRDCH) among the ranges may be (randomly) distributed into different UE groups.

[0800] Preferably, the BWP (above or below) may be changed / represented / replaced by the system bandwidth / band and / or the transmission bandwidth / band. The BWP, bandwidth, and / or band may be used for R2D and / or D2R.

[0801] Preferably, in some embodiments, when the UE receives / detects the PRDCH and / or the R2D signal / channel, the UE may deduce / determine the BWP, (initial) frequency (sub)band, or (initial) frequency resource set based at least on the frequency (e.g., DL carrier or DL band).

[0802] The RACH occasion (RO) or PDRCH occasion can be configured / included in the RA configuration (of the cell). The RACH occasion and / or PDRCH occasion can correspond to one or more UEs and / or a first factor, be associated with and / or used by one or more UEs and / or a first factor. The RACH occasion can be a time and / or frequency resource for RACH transmission or D2R transmission. The PDRCH occasion can be a time and / or frequency resource for PDRCH transmission or D2R transmission. Hereinafter, the RO can be replaced by the PDRCH occasion.

[0803] The PDRCH occasion can be configured / included in the RA configuration (of the cell). The PDRCH occasion can correspond to one or more UEs and / or a first factor, be associated with and / or used by one or more UEs and / or a first factor. The PDRCH occasion can be a time / frequency resource for PDRCH transmission or D2R transmission.

[0804] The UE can perform PDRCH occasion selection in the RA procedure, for example, after triggering the RA procedure, selecting the BWP, selecting the RA configuration / resource group, setting the RA type, selecting the RA preamble, selecting the RO, or in response to triggering the RA procedure, selecting the BWP, selecting the RA configuration / resource group, setting the RA type, selecting the RA preamble, selecting the RO. After selecting the PDRCH occasion or in response to selecting the PDRCH occasion, the UE can perform other types of RA resource selection steps (e.g., based on the selected PDRCH occasion) and / or perform a first transmission (e.g., using the selected PDRCH occasion). The UE can select a PDRCH occasion based on the selected RA preamble (group or index) and / or RO, and / or a PDRCH occasion associated with the selected RA preamble (group or index) and / or RO. The UE can select a PDRCH occasion based on the selected RA resource / configuration (RA preamble, RO), and / or the nearest PDRCH occasion associated with the selected RA resource / configuration (RA preamble, RO). The UE can (randomly) select a PDRCH occasion based on the selected RA resource / configuration (RA preamble, RO) and / or a PDRCH occasion associated with the selected RA resource / configuration (RA preamble, RO) among the nearest N PDRCH occasions. N can be indicated or configured by the NW. Alternatively, N can be determined by the UE. Alternatively, N can be fixed. N can be related to the number of UE groups. N can be an integer and / or greater than 1 (or 2 or 3). The UE can select a PDRCH occasion based on a first factor.

[0805] For example, if at least the UE is a first type of UE, the UE may select a first PDRCH moment of the cell (in the RA configuration). If at least the UE is a second type of UE, the UE may select a second PDRCH moment of the cell (in the RA configuration).

[0806] For example, the UE may select a PDRCH moment based on one or more thresholds of the power level. The UE may select a first PDRCH moment of the cell (in the RA configuration) or a second PDRCH moment of the cell (in the RA configuration) based on different power levels. The UE may select a first PDRCH moment of the cell (in the RA configuration), a second PDRCH moment of the cell (in the RA configuration), and / or a third PDRCH moment of the cell (in the RA configuration) based on different power levels. If at least the threshold is satisfied, the UE may select a PDRCH moment. If the threshold is not at least satisfied, the UE may not select a PDRCH moment. Once the threshold is satisfied, the UE may select a PDRCH moment. The UE may not select a PDRCH moment until the threshold is satisfied. Preferably, in some embodiments, if a second threshold is satisfied, the UE may select a second PDRCH moment. If the second threshold is not satisfied and / or if a first threshold is satisfied, the UE may select a first PDRCH moment.

[0807] For example, the UE may select a first PDRCH moment of the cell (in the RA configuration) for a first UL data type. The UE may select a second PDRCH moment of the cell (in the RA configuration) for a second UL data type. The UE may select a third PDRCH moment of the cell (in the RA configuration) for a third UL data type.

[0808] For example, the UE may select a PDRCH moment based on a threshold of the UL data size. The UE may select a first PDRCH moment of the cell (in the RA configuration) or a second PDRCH moment of the cell (in the RA configuration) based on different UL data sizes. The UE may select a first PDRCH moment of the cell (in the RA configuration), a second PDRCH moment of the cell (in the RA configuration), and / or a third PDRCH moment of the cell (in the RA configuration) based on different UL data sizes.

[0809] For example, a UE may select a PDRCH moment based on its UE ID (using a formula of its UE ID). The UE may select the first PDRCH moment (in the RA configuration) of a cell or the second PDRCH moment (in the RA configuration) of a cell based on its UE ID (using a formula of its UE ID). The UE may select the first PDRCH moment (in the RA configuration) of a cell, the second PDRCH moment (in the RA configuration) of a cell, and / or the third PDRCH moment (in the RA configuration) of a cell based on its UE ID (using a formula of its UE ID). For example, the modulo (of the UE ID) of (the number of PDRCH moments of the cell in which the UE will select a PDRCH moment (in the RA configuration)) may be used to derive or may be equal to the index of the RO that the UE will select.

[0810] For example, a UE may select a PDRCH moment based on its UE group (ID) (using a formula of its UE group (ID)). The UE may select the first PDRCH moment (in the RA configuration) of a cell or the second PDRCH moment (in the RA configuration) of a cell based on its UE group (ID) (using a formula of its UE group (ID)). The UE may select the first PDRCH moment (in the RA configuration) of a cell, the second PDRCH moment (in the RA configuration) of a cell, and / or the third PDRCH moment (in the RA configuration) of a cell based on its UE group (ID) (using a formula of its UE group (ID)). For example, the modulo (of the UE group ID) of (the number of PDRCH moments of the cell in which the UE will select a PDRCH moment (in the RA configuration)) may be used to derive or may be equal to the index of the RO that the UE will select.

[0811] For example, a UE may select a PDRCH moment based on its UE ID and its UE group (ID) (using a formula of its UE ID and its UE group (ID)).

[0812] For example, a UE may randomly (with equal probability) select a PDRCH moment from (several) ROs (in the RA configuration) of a cell.

[0813] RA resources may include PDRCH moments.

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

[0815] Throughout this disclosure, "PRACH" may be replaced by "PDRCH".

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

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

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

[0819] Throughout this disclosure, "BWP" may be replaced by "system bandwidth", "channel bandwidth", "transmission bandwidth", "occupied bandwidth".

[0820] Throughout this disclosure, "RACH" may be replaced by "PDRCH".

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

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

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

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

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

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

[0827] A UE (e.g., an ambient IoT UE) may receive NW signaling, for example, via paging, SIB, PDCCH instruction. In response to (receiving) the NW signaling, the UE may trigger an 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 generated internally 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), MAC signaling (e.g., MAC CE), or PHY signaling (e.g., PDCCH, DCI). The signaling may be (or include) a carrier (signal) and / or an interrogation signal.

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

[0829] Throughout this disclosure, the UL transmission can be or can include the first transmission, the third transmission, and / or subsequent UL transmissions. A subsequent UL transmission can be a UL transmission after the first transmission or the third transmission. A subsequent UL transmission can be a UL transmission after the RA procedure is completed. Throughout this disclosure, the DL transmission can be or can include the second transmission, the fourth transmission, and / or subsequent DL transmissions. A subsequent DL transmission can be a DL transmission after the second transmission or the fourth transmission. A subsequent DL transmission can be a DL transmission after the RA procedure is completed.

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

[0831] The second duration can be the time when the third timer is running. The third timer and / or the second duration can be a contention resolution timer (e.g., ra-ContentionResolutionTimer). The second duration can start after the third transmission or in response to the third transmission. The second duration can be used to receive the fourth transmission for the UE. The second duration can be used to transmit the fourth transmission for the NW.

[0832] A UE (e.g., an ambient IoT UE) may transmit an RRC message and / or a CCCH message in the RA procedure. The CCCH may be a UL CCCH. The UE may transmit the RRC message and / or the CCCH message to the network, e.g., for initial access. The UE may transmit the RRC message and / or the CCCH message via a first transmission and / or a third transmission. The UE may include the RRC message and / or the CCCH message in the first transmission and / or the third transmission. The RRC message and / or the CCCH message may be an RRC establishment request message (e.g., RRC Setup Request). The RRC message and / or the CCCH message may not be an RRC establishment request message. The RRC message and / or the CCCH message may be a (new) message containing first information. The (new) message may include a UE ID, an indication of a cause, and / or auxiliary information. The (new) message may be transmitted via the CCCH. The (new) message may not be transmitted via the CCCH. The UE may trigger an RRC (establishment) procedure. The UE may not trigger an RRC (establishment) procedure. The UE may establish or set up an RRC connection. The UE may not establish or set up an RRC connection. The RRC message and / or the CCCH message may be transmitted in the RRC (establishment) procedure. The RRC message and / or the CCCH message may be transmitted without an RRC (establishment) procedure. The RRC message and / or the CCCH message may be transmitted in an initial access (procedure) without triggering or establishing an RRC procedure and / or an RRC connection.

[0833] A UE (e.g., an ambient IoT UE) may not transmit an RRC message and / or a CCCH message 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 the RRC message and / or the CCCH message in the first transmission and / or the third transmission. The MAC CE may be and / or may 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.

[0834] According to the research project on environmental IoT ([1] RP-234058), the environmental IoT UE has limited energy storage (and may even have no energy storage). Comparing the 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 environmental IoT UE is typically from 1 μW to several hundred μW. Considering the limited energy of the environmental IoT UE, this may not be a good choice for the environmental IoT UE that long-term monitors the PDCCH. In addition to the output power consumption, it may be necessary to enhance the power consumption caused by PDCCH monitoring during the RA procedure (for example, in the first / second duration).

[0835] To solve the problem, the UE (for example, the environmental IoT UE) can monitor the PDCCH to receive DL transmissions (for example, during the RA procedure) in a single or (finite / specific) duration (shorter than the duration of the traditional UE). The environmental IoT UE can monitor the PDCCH for (receiving) DL transmissions in a (finite / specific) duration. The traditional UE or non-environmental IoT UE can monitor the PDCCH for (receiving) MSG2, MSGB, MSG4, and / or NW responses in another duration. Generally, (assuming / expecting) the other time duration is longer than the (finite / specific) duration. The UE can start monitoring the PDCCH to receive DL transmissions at a specific timing. The network can transmit DL transmissions in a (finite / specific) duration. The DL transmission can be the second transmission and / or the fourth transmission. The duration can be or can include the first duration and / or the second duration. The (finite / specific) duration can start at a specific timing. The specific timing can be the starting point of the duration.

[0836] In one or more instances, a (finite / specific) duration may start at a specific timing after a UL transmission. The UL transmission may be or may include a first transmission or a third transmission. The UL transmission may be the first UL transmission to be transmitted in a repetitive and / or bundled form. The UL transmission may be the last UL transmission to be transmitted in a repetitive and / or bundled form. If the UE performs repetition / bundling of the UL 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 transmission. The UL transmission may be a new / initial transmission in the RA procedure. The UL transmission may be a retransmission in the RA procedure. The duration may start in the symbol(s) after a (PDCCH timing and / or) UL transmission plus a time offset. The duration may start in the symbol at the end of the PDCCH timing and / or UL transmission plus a time offset. The duration may start in the first PDCCH timing and / or in the symbol starting at the end of the UL transmission plus a time offset. The duration may start in the symbol(s) after the PDCCH timing and / or UL transmission plus a time offset. The duration may not start in the symbol(s) after a (PDCCH timing and / or) (corresponding) UL transmission.

[0837] The UE may start listening for the PDCCH in the symbol(s) after a (PDCCH timing and / or) UL transmission plus a time offset. The UE may start listening for the PDCCH in the symbol at the end of the PDCCH timing and / or UL transmission plus a time offset. The UE may start listening for the PDCCH in the first PDCCH timing and / or in the symbol starting at the end of the UL transmission plus a time offset. The UE may start listening for the PDCCH in the symbol(s) after the PDCCH timing and / or UL transmission plus a time offset.

[0838] The NW may start transmitting the PDCCH in the symbol(s) after a (PDCCH timing and / or) UL transmission plus a time offset. The NW may start transmitting the PDCCH in the symbol at the end of the PDCCH timing and / or UL transmission plus a time offset. The NW may start transmitting the PDCCH in the first PDCCH timing and / or in the symbol starting at the end of the UL transmission plus a time offset. The NW may start transmitting the PDCCH in the symbol(s) after the PDCCH timing and / or UL transmission plus a time offset.

[0839] 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 a carrier (signal) and / or an 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 will trigger 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 that provides the UE with energy for, e.g., triggering the RA procedure, performing UL transmission, monitoring the PDCCH, and / or receiving DL transmission. The NW signaling may be or include a second transmission. The duration may start in the symbol after (the PDCCH moment and / or) receiving the NW signaling plus a time offset. The duration may start in the symbol at the PDCCH moment and / or at the end of the NW signaling transmission plus a time offset. The duration may start in the symbol at the first PDCCH moment and / or starting from the end of the NW signaling transmission plus a time offset. The duration may start in the symbol after the PDCCH moment and / or at the end of the NW signaling transmission plus a time offset.

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

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

[0842] Throughout this disclosure, the time offset may be the Round-Trip Time (RTT) and / or the time delay. The specific timing and / or time offset may be indicated, (pre-)defined, and / or (pre-)configured by the network. The specific timing and / or time offset may be specified in a specification, such as TS 38.213 ([6] 3GPP TS 38.213 V17.7.0). The specific timing and / or time offset may be calculated and / or derived by the UE. For a group of ambient IoT UEs that receive the same NW signal, the specific timing and / or time offset may be common. The specific timing and / or time offset may be dedicated to / specific to each ambient IoT UE. The UE may listen for the PDCCH during a (limited / specific) duration, e.g., in response to the UE performing the corresponding UL transmission. The UE may receive DL transmissions on the PDCCH during the duration or receive DL transmissions scheduled by the PDCCH. The UE may not listen for the PDCCH after the (corresponding) UL transmission (starts). The UE may not listen for the PDCCH before a specific timing. The UE may not receive DL transmissions outside the duration. The UE may not receive DL transmissions before a specific timing.

[0843] Alternatively and / or additionally, the UE may start the first timer, the second timer, and / or the third timer at a specific timing. The values of the first timer, the second timer, and / or the third timer of the ambient IoT UE may be shorter than those of the legacy UE. The values of the first timer, the second timer, and / or the third timer for the ambient IoT UE may be fixed. The values of the first timer, the second timer, and / or the third timer for the ambient 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 for the PDCCH. When the first timer, the second timer, and / or the third timer is not running, the UE may not listen for the PDCCH (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 DL transmissions or responses.

[0844] 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 a specific timing after the end of Msg1 transmission. The specific timing may be the first PDCCH occasion 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. 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. While the contention resolution timer is in operation, the UE may receive Msg4 from the network.

[0845] In one or more instances, a 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 occasion 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. While the response window is in operation (or during the response window), the UE may receive MSGB from the network.

[0846] Alternatively and / or additionally, the UE may start a first timer, a second timer, and / or a third timer in response to a UL transmission. The UE may start a fourth timer in response to the UL transmission and / or the start of the first timer, the second timer, and / or the third timer. The fourth timer may be expressed as a time offset. The fourth timer may be a delay timer, a prohibition timer, and / or a non-active timer. The fourth timer may end at a specific timing. The fourth timer may expire at a specific timing. When / if (at least) the fourth timer is running, the UE may not monitor the PDCCH. 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. When the fourth timer is running, the NW may not transmit a DL transmission or response.

[0847] 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 occasion 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 TTI / occasion / symbol / millisecond) at the first PDCCH occasion starting from the end of the Msg1 transmission. The UE may start the fourth timer at a timing configured and / or indicated by the network (e.g., in NW signaling). When the response window is running (or during the response window) and the fourth timer is not running, the UE may monitor the PDCCH. When the fourth timer is not running, the UE may monitor the PDCCH 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 in TTI / occasion / symbol / millisecond) at the first PDCCH occasion starting from the end of the Msg3 transmission. The UE may start the fourth timer at a timing configured and / or indicated by the network (e.g., in NW signaling). When the contention resolution timer is running and the fourth timer is not running, the UE may monitor the PDCCH. 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.

[0848] 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 occasion 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 / occasion / symbol / millisecond) at the first PDCCH occasion starting from the end of the Msg1 transmission. The UE may start the fourth timer at an occasion 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 monitor the PDCCH. When the fourth timer is not in operation, the UE may monitor the PDCCH 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 / occasion / symbol / millisecond) at the first PDCCH occasion starting from the end of the Msg3 transmission. The UE may start the other / another fourth timer at an occasion 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 / another fourth timer is not in operation, the UE may monitor the PDCCH. The UE may receive Msg4 from the network after the other / another 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.

[0849] In one or more instances, a 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 the PDCCH occasion after the MSGA transmission. The UE may start a fourth timer at the PDCCH occasion after the MSGA transmission. The UE may start the fourth timer at an occasion 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 monitor the PDCCH. When the fourth timer is not in operation, the UE may monitor the PDCCH during the response window. The UE may receive MSGB from the network after the fourth timer expires.

[0850] In one or more instances, the (finite / specific) duration is a TTI / moment. Preferably, in some embodiments, the (finite / specific) duration may be / mean a specific occasion. Preferably, in some embodiments, the specific occasion may be a TTI / moment.

[0851] Preferably, in some embodiments, when the UE performs UL transmission, the UE may monitor the PDCCH for receiving the corresponding DL transmission at a specific occasion. Preferably, in some embodiments, when the NW receives the UL transmission, the NW may transmit the PDCCH at a specific occasion for transmitting the corresponding DL transmission.

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

[0853] Preferably, in some embodiments, if the UE performs repetition / bundling of UL transmission, the specific occasion may be derived / determined based on the first / initial one or the last one among the repetition / bundling of the UL transmission.

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

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

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

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

[0858] 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 PRB, the lowest Resource Element (RE), or the lowest subcarrier).

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

[0860] After the UE triggers the RA procedure and / or performs the 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, e.g., 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 ([3] 3GPP TS 38.321 V17.6.0), 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 is included in Msg3 or MSGA. However, for the environmental IoT UE, both cases may not be applicable (because there may be no C-RNTI MAC CE or CCCH SDU in Msg3 or MSGA), or the determination of the contention resolution for at least one of the cases may not be suitable for the environmental IoT UE.

[0861] To solve the problem, the UE may receive a PDCCH (command / transmission) as an NW response for UL transmission in the RA procedure. In response to transmitting the first transmission and / or the third transmission, the UE may receive a PDCCH transmission without a PDSCH transmission. The UE may not receive a 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 may receive a PDCCH transmission as MSGB and / or Msg4. The PDCCH transmission may 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 transmission may be scrambled with the UE ID. The PDCCH transmission may 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 transmission may indicate the UE ID. The PDCCH transmission may 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 transmission may include a field indication of the UE ID. The PDCCH transmission may 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 may regard a PDCCH transmission containing or scrambled with the UE ID (or a part thereof) as MSGB and / or Msg4.

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

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

[0864] For example, the UE may include its UE ID in Msg3 and / or MSGA (e.g., via an RRC message, via MAC CE). The UE may transmit Msg3 / MSGA with the UE ID. In response to transmitting Msg3 / MSGA, the UE may monitor the PDCCH (e.g., based on the above examples) and receive a PDCCH transmission. If (at least) or based on one or a combination 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:

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

[0866] -The PDCCH transmission is addressed to the UE's RA-RNTI / TC-RNTI / MSGB-RNTI;

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

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

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

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

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

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

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

[0874] -The RA procedure is triggered by NW signaling (e.g., a carrier, an interrogation signal).

[0875] Ambient IoT UEs may not need to maintain TA values. The UE may not receive a Timing Advance Command (TAC) in the RA procedure. The RAR and / or MSGB (e.g., for ambient IoT UEs) may not contain a TAC. In the RA procedure, the UE may not receive the fourth information. The fourth information includes a TAC, C-RNTI, ChannelAccess-CPext, Transmit Power Control (TPC) command, HARQ feedback timing indicator, and / or PUCCH resource indicator. In the RA procedure, the NW may not provide the fourth information. The UE may not apply the fourth information in the RA procedure. The UE may not indicate the fourth information to the lower layer.

[0876] During or after the RA procedure, the UE may not have subsequent transmissions. During or after the RA procedure, the UE may not transmit or receive transmissions other than the first, second, third, and / or fourth transmissions. The UE may not need to set the C-RNTI. The UE may not set the C-RNTI to the value of the TC-RNTI. The UE may not set the C-RNTI received in the successRAR (MAC sub-PDU). The UE may not receive the C-RNTI in the RA procedure.

[0877] The above examples, methods, concepts, and / or embodiments for contention resolution may be combined. Contention resolution may mean or indicate successful completion of the RA procedure, successful completion of initial access, and / or successful completion of one or more transmissions. Contention resolution may mean or indicate that the UE has successfully completed the RA procedure, transmitted UL data (e.g., the first information) to the NW, and / or accessed / responded to the NW.

[0878] The above examples, methods, concepts, and / or embodiments for transmission, reception, PDCCH monitoring, and / or contention resolution may be combined.

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

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

[0881] See Figure 11, through this and other concepts, systems, and methods of the present invention, method 1010 for a UE in a wireless communication system includes: initiating a RA procedure (step 1012); transmitting a message containing the identification of the UE in the RA procedure (step 1014); in response to transmitting the message, receiving a PDCCH transmission (step 1016); and determining that the RA procedure is successfully completed based on a PDCCH transmission scrambled with the identification of the UE or a PDCCH transmission indicating the identification of the UE (step 1018).

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

[0883] Return to refer Figure 3 and 4 , in one or more embodiments, from the perspective of a UE in a wireless communication system, device 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 message containing the identification of the UE in the RA procedure; (iii) in response to transmitting the message, receive a PDCCH transmission; and (iv) determine that the RA procedure is successfully completed based on a PDCCH transmission scrambled with the identification of the UE or a PDCCH 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.

[0884] Refer Figure 12 , through this and other concepts, systems, and methods of the present invention, method 1020 for a UE in a wireless communication system includes: initiating a RA procedure (step 1022); transmitting a first message containing the identification of the UE in the RA procedure (step 1024); in response to transmitting the first message, receiving a second message (step 1026); and determining that the RA procedure is successfully completed based on the second message indicating the identification of the UE (step 1028).

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

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

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

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

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

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

[0891] Return to reference Figure 3 and 4 and, in one or more embodiments, from the perspective of the UE in a wireless communication system, apparatus 300 includes program code 312 stored in memory 310 of the transmitter. The CPU 308 can execute the program code 312 to: (i) initiate an 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 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.

[0892] Refer to Figure 13 and, by this and other concepts, systems, and methods of the present invention, a method 1030 for a UE in a wireless communication system includes: receiving signaling from the NW (step 1032); initiating an RA procedure in response to (receiving) the signaling (step 1034); transmitting a first message (step 1036); starting a first timer at a specific timing (step 1038); monitoring the PDCCH while the first timer is running (step 1040); and receiving a second message on the PDCCH in response to transmitting the first message (step 1042).

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

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

[0895] In various embodiments, the second message is received while the first timer is running.

[0896] Return to 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 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) monitor the PDCCH while the first timer is running; and (vi) receive a second message on the PDCCH in response to transmitting the first message. In addition, CPU 308 can execute program code 312 to perform all the described actions, steps, and methods described above, below, or elsewhere herein.

[0897] See Figure 14 , by this and other concepts, systems, and methods of the present invention, a method 1050 for a UE in a wireless communication system includes: receiving first signaling that triggers a random access procedure, where the first signaling indicates first information associated with a specific device type in a device type (step 1052); and determining whether to trigger the random access procedure in response to the (received) first signaling, at least based on whether the UE belongs to the specific device type associated with the first information (step 1054).

[0898] In various embodiments, the first signaling is an ambient IoT paging message or a paging message, and / or where the random access procedure is an ambient IoT random access procedure.

[0899] In various embodiments, the method further includes: receiving second information indicated by the first signaling, where the second information indicates a group ID of the UE or a set of UEs; and triggering the random access procedure in response to the (received) first signaling if at least the UE belongs to the specific device type associated with the first information, where the first signaling indicates the second information of the group ID of the UE and / or the UE belongs to the set of UEs.

[0900] In various embodiments, the set of UEs is allowed to trigger the random access procedure.

[0901] In various embodiments, the method further includes: not triggering the random access procedure in response to the (received) first signaling if the UE does not belong to the specific device type associated with the first information, and / or if the first signaling does not indicate the second information of the ID or group ID of the UE, and / or the UE does not belong to the set of UEs indicated by the first signaling.

[0902] In various embodiments, the device types include at least a first device type and a second device type, and at least one of the following exists: the first device type can generate transmissions by itself, and the second device type generates transmissions through backscattering, and / or the first device type has or is equipped with an amplifier, and the second device type does not have or is not equipped with an amplifier, and / or the first device type and the second device type are distinguished by at least any one of energy storage, power level, and / or device size.

[0903] In various embodiments, the method further includes: in response to (receiving) a first signaling, if at least the UE belongs to a specific device type associated with the first information, triggering a random access procedure; and / or in response to (receiving) the first signaling, if at least the UE does not belong to the specific device type associated with the first information, not triggering the random access procedure.

[0904] In various embodiments, the first signaling is transmitted from a reader.

[0905] In various embodiments, the reader is a network node, an intermediate node, or another UE.

[0906] Return to reference Figure 3 and 4 and, in one or more embodiments, from the perspective of a UE in a wireless communication system, the device 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 triggering a random access procedure, where the first signaling indicates first information associated with a specific device type among the device types; and (ii) in response to (receiving) the first signaling, determine whether to trigger the random access procedure based at least on whether the UE belongs to the specific device type associated with the first information. 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.

[0907] Return to reference Figure 3 and 4 and, in one or more embodiments, from the perspective of a reader in a wireless communication system, the device 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 a first signaling triggering a random access procedure, where the first signaling indicates first information associated with a specific device type among the device types. 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.

[0908] See Figure 15, 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 first signaling that triggers a random access procedure (step 1062); triggering a random access procedure in response to (receiving) the first signaling (step 1064); and performing a transmission that indicates or provides third information during the random access procedure, where the third information indicates the device type of the UE, and the device type of the UE is differentiated or associated with any of the following: the method of performing the transmission, equipped with an amplifier, energy storage, power level, and / or device size (step 1066).

[0909] In various embodiments, the third information indicates which type of more than one type of ambient IoT device the UE belongs to, where the more than one type of ambient IoT device is differentiated by any of the following: the method of performing the transmission, equipped with an amplifier, energy storage, power level, and / or device size.

[0910] In various embodiments, the third information indicates the device type of the UE including any of the following: generating the transmission itself or generating the transmission by backscattering, and / or equipped with an amplifier or not equipped with an amplifier, and / or differentiated by energy storage, power level, and / or device size.

[0911] In various embodiments, the first signaling is an ambient IoT paging message and / or a paging message, and / or where the random access procedure is an ambient IoT random access procedure.

[0912] In various embodiments, the first signaling is transmitted from a reader, and / or where the transmission is transmitted to the reader during the random access procedure, and / or where the reader is a network node, an intermediate node, or another UE.

[0913] Return to reference Figure 3 and 4 , in one or more embodiments, from the perspective of a UE in a wireless communication system, device 300 includes program code 312 stored in memory 310 of a transmitter. CPU 308 can execute program code 312 to: (i) receive first signaling that triggers a random access procedure; (ii) trigger a random access procedure in response to (receiving) the first signaling; and (iii) perform a transmission that indicates or provides third information during the random access procedure, where the third information indicates the device type of the UE, and the device type of the UE is differentiated or associated with any of the following: the method of performing the transmission, equipped with an amplifier, energy storage, power level, and / or device size. Additionally, CPU 308 can execute program code 312 to perform all the described actions, steps, and methods described above, below, or herein.

[0914] Return to referenceFigure 3 and 4 In one or more embodiments, from the perspective of a reader in a wireless communication system, device 300 includes program code 312 stored in memory 310 of the transmitter. CPU 308 can execute program code 312 to: (i) transmit first signaling that triggers a random access procedure; and (ii) receive a transmission that indicates or provides third information during the random access procedure, where the third information indicates the device type of the UE, and the device type of the UE is distinguished or associated with any of the following: the method of performing the transmission, being equipped with an amplifier, energy storage, power level, and / or device size. In addition, CPU 308 can execute program code 312 to perform all the described actions, steps, and methods described above, below, or elsewhere herein.

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

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

[0917] Various aspects of the present disclosure have been described above. It should be clear 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 skilled in the art should understand 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. In addition, this device can be implemented or this method can be practiced by using other structures, functionality, or structures and functionality in addition to 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 pulse repetition frequency. In some aspects, parallel channels can be established based on pulse position or offset. In some aspects, parallel channels can be established based on time-hopping sequences. In some aspects, parallel channels can be established based on pulse repetition frequency, pulse position or offset, and time-hopping sequences.

[0918] Those of ordinary skill in the art will 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.

[0919] Those of ordinary skill in the art will further appreciate that the various illustrative logical blocks, modules, processors, components, circuits, and algorithm steps described in connection with the aspects disclosed herein can be implemented as electronic hardware (e.g., digital implementations, analog implementations, or combinations of both, which can be designed using source coding or some other technique), various forms of program or design code with instructions (for convenience, which may be referred to herein as “software” or “software modules”), or combinations of both. To clearly illustrate this interchangeability of hardware and software, the functionality of the various illustrative components, blocks, modules, circuits, and steps has been described generally in terms of their functionality above. Whether the 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.

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

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

[0922] The steps of a method or algorithm described in connection with the aspects disclosed herein can 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 can 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. An example storage medium can be coupled to a machine, such as a computer / processor (for convenience, the machine can 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 example storage medium can be integral with the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user device. In an alternative, the processor and the storage medium can reside in the user device as discrete components. Additionally, in some aspects, any suitable computer program product can 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 can include packaging material.

[0923] Although the invention has been described in connection with various aspects and examples, it should be understood that the invention is capable of further modification. This application is intended to cover any changes, 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: include: receiving first signaling triggering a random access procedure, wherein the first signaling indicates first information associated with a specific device type among the device types; as well as In response to receiving the first signaling, determining whether to trigger the random access procedure is based at least on whether the user equipment belongs to the specific device type associated with the first information.

2. The method according to claim 1, characterized in that The first signaling is an ambient Internet of Things paging message or a paging message, and / or the random access procedure is an ambient Internet of Things random access procedure.

3. The method according to claim 1, characterized in that Further including: receiving second information indicated by the first signaling, wherein the second information indicates a group identifier of the user equipment or a set of user equipments; and / or In response to receiving the first signaling, the random access procedure is triggered if at least the user equipment belongs to the specific device type associated with the first information, wherein the first signaling indicates the second information of the group identifier of the user equipment and / or that the user equipment belongs to the user equipment set.

4. The method according to claim 3, characterized in that The set of user equipments is allowed to trigger the random access procedure.

5. The method according to claim 1, characterized in that Further including: In response to receiving the first signaling, if the user equipment does not belong to the specific device type associated with the first information, and / or if the first signaling does not indicate the second information of the identity or group identity of the user equipment, and / or the user equipment does not belong to the user equipment set indicated by the first signaling, the random access procedure is not triggered.

6. The method according to claim 1, characterized in that The device type includes at least a first device type and a second device type, wherein at least one of the following situations exists: The first device type is capable of generating transmissions itself and the second device type generates transmissions by backscattering, and / or The first device type has or is equipped with an amplifier, and the second device type does not have or is not equipped with an amplifier, and / or The first device type and the second device type are distinguished by at least any one of energy storage, power level, and / or device size.

7. The method according to claim 1, characterized in that Further including: In response to receiving the first signaling, if at least the user equipment belongs to the specific device type associated with the first information, triggering the random access procedure; and / or In response to receiving the first signaling, if at least the user equipment does not belong to the specific device type associated with the first information, the random access procedure is not triggered.

8. The method according to claim 1, characterized in that The first signaling is transmitted from a reader, wherein the reader is a network node, an intermediate node, or another user equipment.

9. A method for a user device, characterized in that: include: receiving a first signaling triggering a random access procedure; In response to receiving the first signaling, triggering the random access procedure; as well as A transmission indicating or providing third information is performed during the random access procedure, wherein the third information indicates a device type of the user equipment, and the device type of the user equipment is distinguished or associated with any of the following: a method for performing the transmission, an amplifier equipped, energy storage, power level and / or device size.

10. The method according to claim 9, characterized in that The third information indicates which type of more than one type of ambient IoT devices the user equipment belongs to, wherein the more than one type of ambient IoT devices are distinguished by any one of the following: a method of performing the transmission, being equipped with an amplifier, energy storage, power level and / or device size.

11. The method according to claim 9, characterized in that The third information indicates the device type of the user equipment including any one of the following: generating the transmission itself or by backscattering, and / or With or without an amplifier, and / or Differentiate by energy storage, power level and / or device size.

12. The method according to claim 9, characterized in that The first signaling is an ambient Internet of Things paging message and / or a paging message, and / or the random access procedure is an ambient Internet of Things random access procedure.

13. The method according to claim 9, characterized in that The first signaling is transmitted from a reader, and / or wherein said transmission is transmitted to said reader during said random access procedure, and / or The reader is a network node, an intermediate node or another user equipment.

14. A user equipment, characterized in that: include: Memory; as well as a processor operatively coupled to the memory, wherein the processor is configured to execute program code to: receiving first signaling triggering a random access procedure, wherein the first signaling indicates first information associated with a specific device type among the device types; and In response to receiving the first signaling, determining whether to trigger the random access procedure is based at least on whether the user equipment belongs to the specific device type associated with the first information.

15. The user equipment according to claim 14, characterized in that: The first signaling is an ambient Internet of Things paging message or a paging message, and / or the random access procedure is an ambient Internet of Things random access procedure.

16. The user equipment according to claim 14, characterized in that The processor is further configured to execute the program code to: receiving second information indicated by the first signaling, wherein the second information indicates a group identifier of the user equipment or a set of user equipments; and / or In response to receiving the first signaling, the random access procedure is triggered if at least the user equipment belongs to the specific device type associated with the first information, wherein the first signaling indicates the second information of the group identifier of the user equipment and / or that the user equipment belongs to the user equipment set.

17. The user equipment according to claim 16, characterized in that The set of user equipments is allowed to trigger the random access procedure.

18. The user equipment according to claim 14, characterized in that The processor is further configured to execute the program code to: In response to receiving the first signaling, if the user equipment does not belong to the specific device type associated with the first information, and / or if the first signaling does not indicate the second information of the identity or group identity of the user equipment, and / or the user equipment does not belong to the user equipment set indicated by the first signaling, the random access procedure is not triggered.

19. The user equipment according to claim 14, characterized in that The device type includes at least a first device type and a second device type, wherein at least one of the following situations exists: The first device type is capable of generating transmissions itself and the second device type generates transmissions by backscattering, and / or The first device type has or is equipped with an amplifier, and the second device type does not have or is not equipped with an amplifier, and / or The first device type and the second device type are distinguished by at least any one of energy storage, power level, and / or device size.

20. The user equipment according to claim 14, characterized in that The processor is further configured to execute the program code to: In response to receiving the first signaling, if at least the user equipment belongs to the specific device type associated with the first information, triggering the random access procedure; and / or In response to receiving the first signaling, if at least the user equipment does not belong to the specific device type associated with the first information, the random access procedure is not triggered.

Images