Method and apparatus for handling configuration of environmental internet of things devices

Abstract

A method and apparatus for handling resources or configurations of an environmental Internet of Things in a wireless communication system are provided, where the method of a user equipment / device comprises: receiving a first signaling triggering a random access procedure, where the first signaling is for more than one user equipment / device; and in response to receiving the first signaling, triggering a random access procedure and performing a first transmission of the random access procedure based on the first resource or the first configuration provided in the first signaling.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit and priority of U.S. Provisional Patent Application Serial No. 63 / 616,401, filed on December 29, 2023, and U.S. Provisional Patent Application Serial No. 63 / 616,424, filed on December 29, 2023; each of the applications and disclosures cited therein is hereby incorporated by reference in its entirety. Technical Field

[0003] This disclosure generally relates to wireless communication networks, and more particularly, to a method and apparatus for handling resources or configurations of Ambient Internet of Thing (Ambient IoT) devices 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 using Internet Protocol (IP) data packets. This 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 structure 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 standard organization is discussing next - generation (e.g., 5G) new radio access technologies. Therefore, changes to the current body of the 3GPP standard are currently being submitted and considered to evolve and complete the 3GPP standard. Summary of the Invention

[0006] Provided are a method, system, and apparatus for handling resources or configurations of Ambient Internet of Thing (Ambient IoT) in a wireless communication system. Thus, lightweight signaling procedures can be implemented for Ambient IoT user equipment (UE) / devices, for example, signaling overhead for data / signaling transmission can be reduced. The Ambient IoT UE / devices can perform a (random) access procedure triggered by the network and effectively acquire resources to perform transmission in the (random) access procedure.

[0007] In various embodiments, a method for a UE / device includes: receiving first signaling that triggers a random access procedure, where the first signaling is for more than one UE / device; and in response to receiving the first signaling, triggering the random access procedure and performing a first transmission of the random access procedure based on a first resource or a first configuration provided in the first signaling.

[0008] In various embodiments, a method for a reader includes: transmitting first signaling that triggers a random access procedure, where the first signaling is for more than one UE / device; and receiving a first transmission of the random access procedure from a UE / device, where the first transmission is triggered in response to the first signaling and where the first transmission is performed or received based on a first resource or a first configuration provided in the first signaling. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0011] Figure 3 is 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 functional block diagram of the program code of;

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

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

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

[0016] Figure 7B is in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6 - 1(b): Random Access Procedure, 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(c): Reproduction of the random access procedure, CFRA with 4-step RA type;

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

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

[0020] Figure 9 It is a flowchart of a method of a first UE in a wireless communication system according to an embodiment of the present invention, the method including determining or deriving (at least) a first configuration by a first method, wherein the first configuration is determined or derived by a second UE by a second method;

[0021] Figure 10 It is a flowchart of a method of a network node in a wireless communication system according to an embodiment of the present invention, the method including configuring a first UE with (at least) a first configuration by a first method and configuring a second UE with (at least) the first configuration by a second method;

[0022] Figure 11 It is a flowchart of a method of a first UE in a wireless communication system according to an embodiment of the present invention, the method including performing transmission or reception without at least the first configuration, wherein a second UE requires the first configuration to perform the transmission or reception;

[0023] Figure 12 It is a flowchart of a method of a network node in a wireless communication system according to an embodiment of the present invention, the method including configuring the second UE with (at least) a first configuration for the second UE to perform transmission or reception, and not configuring the first UE with (at least) the first configuration for the first UE to perform transmission or reception;

[0024] Figure 13 It is a flowchart of a method of a UE in a wireless communication system according to an embodiment of the present invention, the method including receiving signaling from a network and determining whether a first condition is satisfied in response to receiving the signaling;

[0025] Figure 14It is a flowchart of a method of a UE in a wireless communication system according to an embodiment of the present invention. The method includes receiving first signaling that triggers a random access procedure, and in response to receiving the first signaling, triggering the random access procedure and performing a first transmission of the random access procedure based on a first resource or a first configuration provided in the first signaling.

[0026] Figure 15 It is a flowchart of a method of a reader in a wireless communication system according to an embodiment of the present invention. The method includes transmitting first signaling that triggers a random access procedure and receiving a first transmission of the random access procedure from a UE. 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, through the disclosed information, those skilled in the art can easily adapt to use and implement aspects of the present invention in 3GPP2 network architectures and other network architectures.

[0028] The exemplary wireless communication systems and devices described below employ a wireless communication system that supports broadcast services. Wireless communication systems have been 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 systems and devices described below can be designed to support one or more standards, such as those provided by an association named "3rd Generation Partnership Project" (referred to herein as 3GPP), including: [1] RP-234058, "Study on Ambient IoT Solutions in NR"; [2] 3GPP TR38.848 V18.0.0 (2023-09); TSG RAN; Study on Ambient IoT in RAN (Release 18); [3] 3GPP TS 38.321 V17.6.0 (2023-09) 3GPP; TSG RAN; NR; MAC Protocol Specification (Release 17); [4] 3GPP TS 38.300 V17.6.0 (2023-09) 3GPP; TSG RAN; NR; General Description of NR and NG-RAN (Release 17); [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 herein by reference in their entireties.

[0030] Figure 1 FIG. shows a multi-access wireless communication system according to an embodiment of the present invention. The access network 100 (access network, AN) includes a plurality of antenna groups, one group including 104 and 106, another group including 108 and 110, and an additional group including 112 and 114. In Figure 1 FIG., only two antennas are shown for each antenna group; however, each antenna group may utilize more or fewer antennas. The access terminal (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] The antennas of each group and / or the regions in which they are designed to communicate are often referred to as sectors of the access network. In an embodiment, each group of antennas is designed to communicate with access terminals in a sector of the region covered by the access network 100.

[0032] In communication via the forward links 120 and 126, the transmitting antennas of the access network 100 can utilize beamforming to improve the signal-to-noise ratio of the forward links of different access terminals 116 and 122. Also, compared to an access network that transmits to all of its access terminals via a single antenna, the access network using beamforming to transmit to access terminals randomly scattered throughout the coverage area of the access network generally generates less interference to the access terminals in adjacent cells.

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

[0034] Figure 2 FIG. 10 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 a plurality of 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 transmitting antenna. The TX data processor 214 formats, encodes, and interleaves the traffic data of the data streams based on a specific encoding scheme selected for each data stream to provide encoded data.

[0036] The encoded data of each data stream can 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 data and the encoded data for the data stream are modulated (i.e., symbol mapped) based on a specific modulation scheme selected for each data stream (e.g., BPSK, QPSK, M-PSK, or M-QAM) to provide modulated symbols. The data rate, encoding, and modulation for each data stream can be determined by instructions executed by a processor 230. A memory 232 is coupled to the processor 230.

[0037] Next, the modulation symbols of all data streams are 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 N T streams of modulation symbols to N T transmitters (TMTRs) 222a through 222t. In certain embodiments, the TX MIMO processor 220 applies beamforming weights to the symbols of the data stream and the antennas from which the symbols are transmitted.

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

[0039] At the receiver system 250, the transmitted modulated signals are received by the N R antennas 252a through 252r, and the signals received from each antenna 252 are provided to the corresponding receivers (RCVRs) 254a through 254r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) the corresponding 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 N R received symbol streams from the N R receivers 254 based on specific receiver processing techniques to provide N T "detected" symbol streams. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing performed by the RX data processor 260 is complementary to the processing performed by the TX MIMO processor 220 and the TX data processor 214 at the transmitter system 210.

[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] Reverse link messages can include various types of information related to the communication link and / or the received data stream. The reverse link messages are then processed by the TX data processor 238, modulated by the modulator 280, conditioned by the transmitters 254a through 254r, and transmitted back to the transmitter system 210, where the TX data processor also receives traffic data for a plurality of data streams from the data source 236.

[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 by the receiver system 250. The processor 230 then 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 240 or 242 via 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 260 via 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 UEs (or ATs) 116 and 122 in Figure 1 can be implemented using the communication device 300 in a wireless communication system, and the wireless communication system is preferably an NR system. The communication device 300 can 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 via the CPU 308, thereby controlling the operation of the communication device 300. The communication device 300 can receive signals input by a user via the input device 302 (e.g., a keyboard or keypad) and can output images and sounds via the output device 304 (e.g., a monitor or speaker). The transceiver 314 is used to receive and transmit wireless signals, pass the received signals to the control circuit 306, and wirelessly output the signals generated by the control circuit 306.

[0046] Figure 4 is according to an embodiment of the present invention Figure 3Simplified block diagram of the program code 312 shown. In this embodiment, the program code 312 includes an application layer 400, a layer 3 section 402, and a layer 2 section 404, and is coupled to a layer 1 section 406. The layer 3 section 402 generally performs radio resource control. The layer 2 section 404 generally performs link control. The layer 1 section 406 generally performs physical connection.

[0047] For an LTE, LTE-A, or NR system, the layer 2 section 404 may include a Radio Link Control (RLC) layer and a Medium Access Control (MAC) layer. The layer 3 section 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 section 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 sections may be implemented independently and separately to form a specific method or device. The correlations such as "based on", "more specifically", "example", etc. in the following disclosure of the present invention are only a possible embodiment that does not limit a specific method or device.

[0050] The description of the research project of Ambient Internet of Things (Ambient IoT) is as follows in [1] RP-234058:

[0051] ****************************Quote start [1]******************************

[0052] 3 Reasons

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

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

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

[0056] Given the limited size and complexity required for the practical applications of battery - less 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 in most industries mainly has to adopt barcodes and RFID. The main advantages of these two technologies are the ultra - low complexity and small form factor of the tags. However, the limited read range of several meters usually requires hand - held scanning, which results in labor - intensive and time - consuming operations, or requires RFID portals / gates, which results in high deployment costs. In addition, the lack of interference management schemes leads to severe interference and capacity issues between RFID readers, especially in the case of dense deployments. RFID has difficulty supporting large - scale seamless coverage networks.

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

[0059] Since existing technologies do not meet all the requirements of the target use cases, new IoT technologies are recommended to open up new markets within the 3GPP system, with connection numbers and / or device densities that 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 otherwise be 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 ambient 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 otherwise be 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 harmonized air interface design with minimized differences (if necessary) to enable ambient 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, no DL amplification nor UL amplification 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 X ppm, with DL and / or UL amplification in the device. The UL transmission of the device can be generated internally by the device or backscattered on an externally provided carrier.

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

[0069] ● Coverage design objective: According to TR 38.848: “…the range within which the WG can make its sub-selection”, the maximum distance to an 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, and 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 scenarios with Topology 1

[0074] ○ Base station and coexistence characteristics: Microcell, co-located

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

[0076] ○ Base station and coexistence characteristics: Microcell, co-located

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

[0078] C. FR1 licensed spectrum in FDD

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

[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 for identifying 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 used) can occur at least in the UL spectrum.

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

[0084] …

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

[0086] The positioning study in Rel-19 is RAN3-led and is limited to functions with no or minimal specification impact (note: this does not imply any decisions related to WI creation).

[0087] Study the feasibility and required functions of proximity determination (coordination with SA3 is required for privacy aspects).

[0088] ● RAN1-led:

[0089] For environmental IoT DL and UL:

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

[0091] ○ Basic parameters, bandwidth and multiple access

[0092] ○ Waveform and modulation

[0093] ○ Channel coding

[0094] ○ Downlink channel / signal aspects

[0095] ○ Uplink channel / signal aspects

[0096] ○ Scheduling and timing relationships

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

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

[0099] ● RAN2-led:

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

[0101] For example:

[0102] ■ Paging

[0103] ■ Random access

[0104] ■ Data transfer including necessary radio resource control aspects complies with the general range of restrictions

[0105] ■ Interaction with the upper layer

[0106] For functions not listed above, these functions are only studied when necessary.

[0107] *******************************End of citation******************************

[0108] A description of the environmental IoT (e.g., regarding scenarios, topologies, and assumptions) can be found in TR 38.848 ([2] 3GPP TR38.848V18.0.0 (2023-09) 3GPP) as provided below:

[0109] ********************************Start of citation [2]**************************

[0110] 4.2.1 Connection Topologies

[0111] 4.2.1.0 Introduction

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

[0113] 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 topologies, this does not imply the existence of multi-hop assisting or intermediate nodes.

[0114] 4.2.1.1 Topology 1: IoT Device

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

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

[0117] 4.2.1.2 Topology 2: IoT Device

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

[0119] In Topology 2, the environmental IoT device communicates bidirectionally with the intermediate nodes between the device and the base station. In this topology, the intermediate nodes can be relays capable of environmental IoT, IAB nodes, UEs, repeaters, etc. The intermediate nodes transmit environmental IoT data and / or signaling between the BS and the environmental IoT device.

[0120] ********************************Next citation*****************************

[0121] 4.2.2 Deployment scenarios

[0122] 4.2.2.1 Deployment scenario 1: The device is indoors and the base station is indoors

[0123] In the case where the environmental IoT device is indoors and the base station is indoors, this deployment scenario is characterized according to Table 4.2.2.1-1.

[0124] Table 4.2.2.1-1: Characteristics of Deployment Scenario 1

[0125]

[0126] Note 1: The description may not apply to some devices (A, B).

[0127] 4.2.2.2 Deployment scenario 2: The device is indoors and the base station is outdoors

[0128] In the case where the environmental IoT device is indoors and the base station is outdoors, this deployment scenario is characterized according to Table 4.2.2.2-1.

[0129] Table 4.2.2.2-1: Characteristics of Deployment Scenario 2

[0130]

[0131] *******************************Next citation******************************

[0132] 4.3 Device classification

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

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

[0135] - No energy storage at all; or

[0136] - Finite energy storage

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

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

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

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

[0141] The implementation of finite 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.

[0142] *****************************End of citation********************************

[0143] The current random access (RA) procedure is described in TS 38.321 ([3] 3GPP TS 38.321 V17.6.0 (2023-09) 3GPP). The current RA procedure will be performed by a legacy UE.

[0144] *******************************Start of citation [3]***************************

[0145] 5.1 Random access procedure

[0146] 5.1.1 Random access procedure initialization

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

[0148] …

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

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

[0151] …

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

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

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

[0155] - rsrp-ThresholdSSB: The RSRP threshold for selecting an SSB for the 4-step RA type. If initiating a random access procedure for beam failure recovery, the rsrp-ThresholdSSB for selecting an SSB within candidateBeamRSList refers to the rsrp-ThresholdSSB in the BeamFailureRecoveryConfig IE;

[0156] - rsrp-ThresholdCSI-RS: The RSRP threshold for selecting a CSI-RS for the 4-step RA type. If initiating a random access procedure for beam failure recovery, rsrp-ThresholdCSI-RS is equal to the rsrp-ThresholdSSB in the BeamFailureRecoveryConfig IE;

[0157] - msgA-RSRP-ThresholdSSB: The RSRP threshold for selecting an SSB for the 2-step RA type;

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

[0159] -msgA-RSRP-Threshold: The RSRP threshold used for selecting between type 2-step and type 4-step RA when both type 2-step and type 4-step RA random access resources are configured in the UL BWP;

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

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

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

[0163] -msgA-TransMax: The maximum number of MSGAs transmitted when type 4-step and type 2-step RA random access resources are configured;

[0164] -candidateBeamRSList: The list of reference signals (CSI-RS and / or SSB) identifying candidate beams and associated random access parameters for recovery;

[0165] -recoverySearchSpaceId: The search space identifier for listening for the response to the beam failure recovery request;

[0166] -powerRampingStep: The power ramping factor;

[0167] -msgA-PreamblePowerRampingStep: The power ramping factor for the MSGA preamble;

[0168] -powerRampingStepHighPriority: The power ramping factor in the case of a prioritized random access procedure;

[0169] -scalingFactorBI: The scaling factor for a prioritized random access procedure;

[0170] -ra-PreambleIndex: The random access preamble;

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

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

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

[0174] -ra-OccasionList: Defines the PRACH occasions associated with CSI-RS on which the MAC entity can transmit random access preambles;

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

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

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

[0178] -ssb-perRACH-OccasionAndCB-PreamblesPerSSB: Defines the number of SSBs mapped to each PRACH occasion of the 4-step RA type and the number of contention-based random access preambles mapped to each SSB;

[0179] -msgA-CB-PreamblesPerSSB-PerSharedRO: Defines the number of contention-based random access preambles of the 2-step RA type mapped to each SSB when the PRACH occasion is shared between the 2-step and 4-step RA types;

[0180] -msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB: Defines the number of SSBs mapped to each PRACH occasion of the 2-step RA type and the number of contention-based random access preambles mapped to each SSB;

[0181] -numberOfPreamblesPerSSB-ForThisPartition: Defines the number of consecutive preambles mapping to the features or combinations of features for each SSB;

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

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

[0184] -msgA-PUSCH-resource-Index: Identifies the index of the PUSCH resource for MsgA in the case of contention-free random access of the two-step RA type;

[0185] …

[0186] -ra-ResponseWindow: The time window for listening to the RA response (only for the SpCell);

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

[0188] -msgB-ResponseWindow: The time window for listening to the RA response of the two-step RA type (only for the SpCell).

[0189] …

[0190] When starting the random access procedure on the serving cell, the MAC entity will:

[0191] 1> Clear the Msg3 buffer;

[0192] 1> Clear the MsgA buffer;

[0193] 1> Set the PREAMBLE_TRANSMISSION_COUNTER to 1;

[0194] 1> Set the PREAMBLE_POWER_RAMPING_COUNTER to 1;

[0195] 1> Set the PREAMBLE_BACKOFF to 0 ms;

[0196] 1> Set the POWER_OFFSET_2STEP_RA to 0 dB;

[0197] …

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

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

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

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

[0202] …

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

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

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

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

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

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

[0209] 1> Otherwise:

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

[0211] 1> Initialize variables specific to the random access type specified in, e.g., Clause 5.1.1a;

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

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

[0214] 1> Otherwise:

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

[0216] 5.1.1a Initialization of variables specific to the random access type

[0217] The MAC entity shall:

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

[0219] 2> Set PREAMBLE_POWER_RAMPING_STEP to msgA-PreamblePowerRampingStep;

[0220] 2> Set SCALING_FACTOR_BI to 1;

[0221] 2> Apply preambleTransMax included in RACH-ConfigGenericTwoStepRA;

[0222] …

[0223] 2> Set MSGA_PREAMBLE_POWER_RAMPING_STEP to

[0224] PREAMBLE_POWER_RAMPING_STEP.

[0225] 1> Otherwise (i.e., set RA_TYPE to 4-stepRA):

[0226] 2> Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStep;

[0227] 2> Set SCALING_FACTOR_BI to 1;

[0228] 2> Set preambleTransMax to preambleTransMax included in RACH-ConfigGeneric;

[0229] …

[0230] 5.1.1b Selection of the random access resource set for the random access procedure

[0231] The MAC entity shall:

[0232] 1> If the BWP configuration selected for the random access procedure has a random access resource set with msg3-Repetitions set to true and a random access resource set with msg3-Repetitions not set to true, and the RSRP of the downlink path loss reference is less than rsrp-ThresholdMsg3; or

[0233] 1> If the BWP selected for the random access procedure is only configured with a random access resource set with msg3-Repetitions set to true:

[0234] 2> Assume that Msg3 repetition applies to the current random access procedure.

[0235] 1> Otherwise:

[0236] 2> Assume that Msg3 repetition does not apply to the current random access procedure.

[0237] …

[0238] 1> If no contention-free random access resources and random access resources for SI request 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:

[0239] …

[0240] 2> If there is no random access resource set available for any feature applicable to the current random access procedure (as specified in Clause 5.1.1c):

[0241] 3> Select a random access resource set not associated with any feature indication for this random access procedure (as specified in Clause 5.1.1c).

[0242] 2> Otherwise if there is an available random access resource set that can be used to indicate all the features triggering this random access procedure:

[0243] 3> Select this random access resource set for this random access procedure.

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

[0245] 3>Select a set of random access resources from the available set 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.

[0246] 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 only one available set of random access resources configured with only RedCap indication:

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

[0248] 1>Otherwise:

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

[0250] 5.1.1c Availability of random access resource sets

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

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

[0253] 2>Consider the set of random access resources as not available for random access procedures for which RedCap does not apply.

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

[0255] 2>Consider the set of random access resources as not available for random access procedures that are not triggered for RA-SDT.

[0256] 1>If NSAG-List is configured for the set of random access resources:

[0257] 2>Unless the set of random access resources is triggered for any one of the NSAG-IDs in the NSAG-List, consider the set of random access resources as not available for random access procedures.

[0258] 1>If msg3-Repetitions is set to true for the set of random access resources:

[0259] 2>If Msg3 repetition does not apply, consider the set of random access resources as not available for random access procedures.

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

[0261] 2> Consider that the random access resource set is not associated with any feature.

[0262] 5.1.2 Random Access Resource Selection

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

[0264] …

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

[0266] 1> If ra-PreambleIndex is not 0b000000, then:

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

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

[0269] 1> Otherwise, if the contention-free random access resource associated with the SSB has been explicitly provided in rach-ConfigDedicated and at least one SSB with an SS-RSRP higher than rsrp-ThresholdSSB among the associated SSBs is available, then:

[0270] 2> Select the SSB among the associated SSBs with an SS-RSRP higher than rsrp-ThresholdSSB;

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

[0272] 1> Otherwise, if the contention-free random access resource associated with the CSI-RS has been explicitly provided in rach-ConfigDedicated and at least one CSI-RS with a CSI-RSRP higher than rsrp-ThresholdCSI-RS among the associated CSI-RSs is available:

[0273] 2> Select the CSI-RS among the associated CSI-RSs with a CSI-RSRP higher than rsrp-ThresholdCSI-RS;

[0274] 2> Set PREAMBLE_INDEX to the ra-PreambleIndex corresponding to the selected CSI-RS.

[0275] …

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

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

[0278] 3> Select the SSB with SS-RSRP higher than rsrp-ThresholdSSB.

[0279] 2> Otherwise:

[0280] 3> Select any SSB.

[0281] …

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

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

[0284] …

[0285] 1> Otherwise, if the SSB is selected above, then:

[0286] 2> Determine the next available PRACH occasion from the PRACH occasions, corresponding to the selected SSB permitted by the restrictions given by ra-ssb-OccasionMaskIndex (if configured) or ssb-SharedRO-MaskIndex (if configured) or 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).

[0287] 1> Otherwise, if the CSI-RS is selected above, then:

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

[0289] 3> Determine the next available PRACH occasion from the PRACH occasion, permitted by the restrictions given by ra-ssb-OccasionMaskIndex (if configured) and corresponding to the SSB in candidateBeamRSList that is quasi-co-located with the selected CSI-RS specified in TS 38.214 (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 SSB that is quasi-co-located with the selected CSI-RS; the MAC entity may consider the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the SSB that is quasi-co-located with the selected CSI-RS).

[0290] 2> Otherwise:

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

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

[0293] …

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

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

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

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

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

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

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

[0301] 3> Select an SSB with SS-RSRP higher than msgA-RSRP-ThresholdSSB.

[0302] 2> Otherwise:

[0303] 3> Select any SSB.

[0304] …

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

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

[0307] 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 with equal probability among the consecutive PRACH occasions allocated for the two-step RA type, regardless of the FR2 UL gap corresponding to the selected SSB; the MAC entity may consider the possible occurrence of measurement gaps and MUSIM gaps when determining the next available PRACH occasion corresponding to the selected SSB).

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

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

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

[0311] 2>Transfer the UL grant and associated HARQ information to the HARQ entity.

[0312] 1>Otherwise:

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

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

[0315] 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], then:

[0316] 3>Transfer the UL grant and associated HARQ information to the HARQ entity.

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

[0318] …

[0319] 5.1.3 Random access preamble transmission

[0320] For each random access preamble, the MAC entity will:

[0321] …

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

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

[0324] …

[0325] 5.1.3a MSGA transmission

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

[0327] …

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

[0329] 2>If the transmission is not for the CCCH logical channel, then:

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

[0331] …

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

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

[0334] 1> Indicate to the physical layer to use 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), use the corresponding RA-RNTI, MSGB-RNTI, PREAMBLE_INDEX, PREAMBLE_RECEIVED_TARGET_POWER, msgA-PreambleReceivedTargetPower, and the power ramping amount applied to the latest MSGA preamble transmission (i.e.,

[0335] (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP) to transmit the MSGA;

[0336] …

[0337] Note: The MSGA transmission includes the transmission of the PRACH preamble and the content of the MSGA buffer in the PUSCH resource corresponding to the selected PRACH occasion and PREAMBLE_INDEX (see TS 38.213 [6])

[0338] 5.1.4 Random access response reception

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

[0340] …

[0341] 3> Start the ra-ResponseWindow configured in RACH-ConfigCommon at the first PDCCH occasion as specified in TS 38.213 [6] from the end of the random access preamble transmission.

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

[0343] 1> If a notification of PDCCH transmission is received on the search space indicated by recoverySearchSpaceId from the lower layer on the serving cell from which the preamble was transmitted; and

[0344] 1> If the PDCCH transmission is addressed to C-RNTI; and

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

[0346] 2> Consider the random access procedure successfully completed.

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

[0348] 2> If the random access response contains a MAC sub-PDU with a backoff indicator, then:

[0349] 3> Set PREAMBLE_BACKOFF to the value of the BI field of the MAC sub-PDU multiplied by SCALING_FACTOR_BI using Table 7.2-1.

[0350] 2> Otherwise:

[0351] 3> Set PREAMBLE_BACKOFF to 0 ms.

[0352] 2> If the random access response contains a MAC sub-PDU with a random access preamble identifier corresponding to the transmitted PREAMBLE_INDEX (see Clause 5.1.3), then:

[0353] 3> Consider the reception of this random access response successful.

[0354] 2> If the reception of the random access response is considered successful:

[0355] 3> If the random access response contains only a MAC sub-PDU with RAPID, then:

[0356] 4> Consider the random access procedure successfully completed;

[0357] …

[0358] 3> Otherwise:

[0359] 4> Apply the following actions to the serving cell that transmits the random access preamble:

[0360] …

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

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

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

[0364] 4> Otherwise:

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

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

[0367] 6> If transmission is not performed for the CCCH logical channel, then:

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

[0369] …

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

[0371] …

[0372] 1> If the ra-ResponseWindow configured in RACH-ConfigCommon expires and if a random access response containing a random access preamble identifier that matches the transmitted PREAMBLE_INDEX has not been received:

[0373] 2> Consider the random access response reception unsuccessful;

[0374] 2> Increment the PREAMBLE_TRANSMISSION_COUNTER by 1;

[0375] 2> If PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1, then:

[0376] 3> If the random access preamble is transmitted on the SpCell, then:

[0377] 4> Indicate a random access problem to the upper layer;

[0378] 4> If this random access procedure is triggered for an SI request:

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

[0380] 3> Otherwise, if the random access preamble is transmitted on a SCell:

[0381] 4> Consider the random access procedure not successfully completed.

[0382] 2> If the random access procedure is not completed:

[0383] 3> Select a random backoff time according to a uniform distribution between 0 and PREAMBLE_BACKOFF;

[0384] 3> If the criteria for selecting contention-free random access resources (as defined in clause 5.1.2) are met during the backoff time:

[0385] 4> Perform the random access resource selection procedure (see clause 5.1.2).

[0386] 3> Otherwise, if a random access procedure for a SCell is performed on an uplink carrier for which pusch-Config is not configured, then:

[0387] 4> Delay subsequent random access transmissions until the random access procedure is triggered by a PDCCH command with the same ra-PreambleIndex, ra-ssb-OccasionMaskIndex, and UL / SUL indicator as in TS 38.212.

[0388] 3> Otherwise:

[0389] 4> Perform the random access resource selection procedure (see clause 5.1.2) after the backoff time.

[0390] After successfully receiving a random access response containing a random access preamble identifier that matches the transmitted PREAMBLE_INDEX, the MAC entity may stop the ra-ResponseWindow (and thus stop listening for random access responses).

[0391] …

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

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

[0394] 1> As specified in TS 38.213 [6], clause 8.2A, start msgB-ResponseWindow at the PDCCH occasion;

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

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

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

[0398] 1> If a receive notification of the PDCCH transmission of the SpCell is received from the lower layer, then:

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

[0400] …

[0401] 3> Otherwise, if the timeAlignmentTimer associated with PTAG is running; or

[0402] 3> If the CG-SDT procedure is in progress and the cg-SDT-TimeAlignmentTimer is running:

[0403] 4> If the PDCCH transmission is addressed to C-RNTI and contains a UL grant for a new transmission:

[0404] 5> Consider this random access response reception successful;

[0405] 5> Stop msgB-ResponseWindow;

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

[0407] 3> Otherwise:

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

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

[0410] 6> Process the received timing advance command (see clause 5.2);

[0411] 6> Consider the random access response reception successful;

[0412] 6> Stop msgB-ResponseWindow;

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

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

[0415] 3> If MSGB contains a MAC sub-PDU with a backoff indicator:

[0416] 4> Set PREAMBLE_BACKOFF to the value of the BI field of the MAC sub-PDU multiplied by SCALING_FACTOR_BI using Table 7.2-1.

[0417] 3> Otherwise:

[0418] 4> Set PREAMBLE_BACKOFF to 0 ms.

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

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

[0421] 4> Consider the random access response reception successful;

[0422] 4> Apply the following actions for the SpCell:

[0423] …

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

[0425] 6> Consider the random access procedure successfully completed;

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

[0427] 5> Otherwise:

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

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

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

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

[0432] …

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

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

[0435] 4> Stop the msgB-ResponseWindow;

[0436] …

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

[0438] 5> Apply the following actions for the SpCell:

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

[0440] 6> Indicate to the lower layer msgA-PreambleReceivedTargetPower and the amount of power ramping applied to the latest random access preamble transmission (i.e., (PREAMBLE_POWER_RAMPING_COUNTER - 1)

[0441] × PREAMBLE_POWER_RAMPING_STEP);

[0442] …

[0443] 4> Consider this random access response reception successful;

[0444] 4> Consider this random access process successfully completed;

[0445] 4> Complete the disassembly and demultiplexing of the MAC PDU.

[0446] 1> If the msgB-ResponseWindow expires and the random access response reception has not been considered successful based on the above description:

[0447] 2> Increment PREAMBLE_TRANSMISSION_COUNTER by 1;

[0448] 2> If PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1, then:

[0449] 3> Indicate a random access problem to the upper layer;

[0450] 3> If this random access procedure is triggered for an SI request:

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

[0452] 2> If the random access procedure is not completed:

[0453] 3> If msgA-TransMax is applied (see clause 5.1.1a) and

[0454] PREAMBLE_TRANSMISSION_COUNTER = msgA-TransMax + 1:

[0455] 4> Set RA_TYPE to 4-stepRA;

[0456] 4> Perform the initialization of variables specific to the random access type specified in clause 5.1.1a;

[0457] 4> If the Msg3 buffer is empty:

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

[0459] 4> Clear the HARQ buffer in the MSGA buffer for transmitting the MAC PDU;

[0460] 4> Discard the contention-free 2-step RA type random access resources explicitly transmitted (if any);

[0461] 4> Perform the random access resource selection procedure specified in clause 5.1.2.

[0462] 3> Otherwise:

[0463] 4> Select a random backoff time according to a uniform distribution between 0 and PREAMBLE_BACKOFF;

[0464] 4> If the criteria for selecting contention-free random access resources (defined in clause 5.1.2a) are met during the backoff time:

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

[0466] 4> Otherwise:

[0467] 5> Perform the random access resource selection procedure for a 2-step RA type random access after the backward time (see clause 5.1.2a).

[0468] After receiving the fallbackRAR, once the random access response is considered successfully received, the MAC entity may stop the msgB-ResponseWindow.

[0469] 5.1.5 Contention resolution

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

[0471] 1> If Msg3 is transmitted (i.e., initial transmission or HARQ retransmission) with PUSCH repetition type A scheduling:

[0472] …

[0473] 3> Start or restart the ra-ContentionResolutionTimer in the first symbol after all repetitions of the Msg3 transmission have ended.

[0474] …

[0475] 1> Otherwise:

[0476] 2> Start or restart the ra-ContentionResolutionTimer in the first symbol after the Msg3 transmission has ended.

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

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

[0479] 2> If the C-RNTI MAC CE is included in Msg3:

[0480] …

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

[0482] 3> If the 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:

[0483] 4> Consider this contention resolution successful;

[0484] 4> Stop ra-ContentionResolutionTimer;

[0485] 4> Discard TEMPORARY_C-RNTI;

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

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

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

[0489] 4> Stop ra-ContentionResolutionTimer;

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

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

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

[0493] …

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

[0495] 5> Discard TEMPORARY_C-RNTI;

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

[0497] 4> Otherwise:

[0498] 5> Discard TEMPORARY_C-RNTI;

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

[0500] 1> If ra-ContentionResolutionTimer expires, then:

[0501] …

[0502] 3> Discard TEMPORARY_C-RNTI;

[0503] 3> Consider the contention resolution unsuccessful.

[0504] 1> If contention resolution is considered unsuccessful:

[0505] 2> Clear the HARQ buffer in the Msg3 buffer for transmitting the MAC PDU;

[0506] 2> Increment PREAMBLE_TRANSMISSION_COUNTER by 1;

[0507] 2> If PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1, then:

[0508] 3> Indicate a random access problem to the upper layer.

[0509] …

[0510] 2> If the random access procedure is not complete:

[0511] 3> If RA_TYPE is set to 4-stepRA:

[0512] 4> Select a random backoff time according to the uniform distribution between 0 and PREAMBLE_BACKOFF;

[0513] 4> If the criterion for selecting contention-free random access resources (as defined in Clause 5.1.2) is satisfied during the backoff time:

[0514] 5> Execute the random access resource selection procedure (see Clause 5.1.2);

[0515] 4> Otherwise:

[0516] 5> Execute the random access resource selection procedure (see Clause 5.1.2) after the backoff time.

[0517] 3> Otherwise (i.e., RA_TYPE is set to 2-stepRA):

[0518] 4> If msgA-TransMax is applied (see Clause 5.1.1a) and PREAMBLE_TRANSMISSION_COUNTER = msgA-TransMax + 1:

[0519] 5> Set RA_TYPE to 4-stepRA;

[0520] 5> Initialize the variables specific to the random access type specified in Clause 5.1.1a;

[0521] 5> Clear the HARQ buffer in the MSGA buffer for transmitting the MAC PDU;

[0522] 5> Discard the contention - free 2 - step RA type random access resources transmitted explicitly (if any);

[0523] 5> Perform random access resource selection as specified in Clause 5.1.2.

[0524] 4> Otherwise:

[0525] 5> Select a random backoff time according to the uniform distribution between 0 and PREAMBLE_BACKOFF;

[0526] 5> If the criteria for selecting contention - free random access resources (as defined in Clause 5.1.2a) are met during the backoff time:

[0527] 6> Perform the random access resource selection process for the 2 - step RA type as specified in Clause 5.1.2a.

[0528] 5> Otherwise:

[0529] 6> Perform random access resource selection for the 2 - step RA type process after the backoff time (see Clause 5.1.2a).

[0530] 5.1.6 Completion of Random Access Procedure

[0531] After the random access procedure is completed, the MAC entity will:

[0532] 1> Discard any explicitly transmitted contention - free random access resources for the 2 - step RA type and 4 - step RA type, except for the 4 - step RA type contention - free random access resources for beam failure recovery requests (if any);

[0533] 1> Empty the HARQ buffers in the Msg3 buffer and the MSGA buffer for transmitting MAC PDUs.

[0534] *******************************Next Citation******************************

[0535] 5.15 Bandwidth Part (BWP) Operations

[0536] 5.15.1 Downlink and Uplink

[0537] …

[0538] After initiating a random access procedure on the serving cell, after selecting the carrier for performing the random access procedure as specified in Clause 5.1.1, the MAC entity will for the selected carrier of this serving cell:

[0539] 1> If the PRACH occasion is not configured to start the mid UL BWP:

[0540] …

[0541] 3> Switch the starting UL BWP to the BWP indicated by initialUplinkBWP.

[0542] 2> If the serving cell is a SpCell:

[0543] …

[0544] 4> Switch the starting DL BWP to the BWP indicated by initialDownlinkBWP.

[0545] 1> Otherwise:

[0546] 2> If the serving cell is a SpCell:

[0547] 3> If the starting DL BWP and the starting UL BWP do not have the same bwp-Id:

[0548] 4> Switch the starting DL BWP to the DL BWP that has the same bwp-Id as the starting UL BWP.

[0549] …

[0550] 1> Perform a random access procedure on the starting DL BWP of the SpCell and the starting UL BWP of this serving cell.

[0551] ******************************** Citation ends *****************************

[0552] A general description of the random access procedure is described in TS 38.300 ([4] 3GPP TS 38.300 V17.6.0 (2023-09) 3GPP):

[0553] ****************************** Citation starts [4] ****************************

[0554] 9.2.6 Random access procedure

[0555] …

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

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

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

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

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

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

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

[0563] 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, the dedicated preamble and PUSCH resources are configured for MSGA transmission, and after receiving the network response, the UE ends the random access procedure, as Figure 9 .2.6-1(d) shows. For CBRA, if contention resolution is successful after receiving the network response, the UE ends the random access procedure, as Figure 9as shown in Figure 9 .2.6-2. If contention resolution is not successful after the (re)transmission of MSG3, the UE returns to the transmission of MSGA.

[0564] If the random access procedure of the 2-step RA type is not completed after multiple transmissions of MSGA, the UE may be configured to switch to the 4-step RA type of CBRA.

[0565] Figure 7A as defined in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1(a): Reproduction of the random access procedure, CBRA with 4-step RA type.

[0566] Figure 7B as defined in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1(b): Reproduction of the random access procedure, CBRA with 2-step RA type.

[0567] Figure 7C as defined in 3GPP TS 38.300 V17.6.0 Figure 9 .2.6-1(c): Reproduction of the random access procedure, CFRA with 4-step RA type.

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

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

[0570] For random access in a cell configured with SUL, the network may explicitly transmit 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 the broadcast threshold. Before selecting between the 2-step and 4-step RA types, the UE performs carrier selection. The RSRP threshold for selecting between the 2-step and 4-step RA types can be configured separately for UL and SUL. Once started, all uplink transmissions of the random access procedure remain on the selected carrier.

[0571] *****************************End of citation********************************

[0572] Some configurations related to the access procedure, BWP, and SDT in the current standard are described in TS 38.331 ([5] 3GPP TS 38.331 V17.6.0 (2023-09) 3GPP):

[0573] ******************************Start of citation [5]****************************

[0574]

[0575]

[0576]

[0577]

[0578]

[0579]

[0580]

[0581] ********************************Next citation*****************************

[0582] -BWP-UplinkCommon

[0583] The IE BWP-UplinkCommon is used to configure the common parameters of the uplink BWP. The parameters are "cell-specific" and the network ensures the necessary alignment with the corresponding parameters of 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.

[0584]

[0585]

[0586]

[0587]

[0588]

[0589]

[0590]

[0591]

[0592]

[0593]

[0594]

[0595]

[0596]

[0597]

[0598]

[0599] *****************************Quotation ends********************************

[0600] In TS 38.213 ([6] 3GPP TS 38.213 V17.7.0 (2023-09) 3GPP), the synchronization process, RA process, uplink power control, and sidelink power control are described:

[0601] ****************************Quotation from [6] starts******************************

[0602] 4 Synchronization process

[0603] 4.1 Cell search

[0604] Cell search is the process by which the UE acquires time and frequency synchronization with the cell and detects the physical layer cell ID of the cell.

[0605] The UE receives the following synchronization signals (SS) to perform cell search: the primary synchronization signal (PSS) and the secondary synchronization signal (SSS) defined in [TS38.211].

[0606] The UE assumes that the reception opportunities of the physical broadcast channel (PBCH), PSS, and SSS are in consecutive symbols (as defined in [TS 38.211]) and form an SS / PBCH block. The UE assumes that the SSS, PBCH DM-RS, and PBCH data have the same EPRE.

[0607] 8 Random access procedure

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

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

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

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

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

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

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

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

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

[0617] 8.1 Random access preamble

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

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

[0620] - Preamble index, preamble SCS, P PRACH,target , corresponding RA-RNTI, and PRACH resources.

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

[0622] For type 1 random access procedure, the number N of SS / PBCH block indices associated with one PRACH occasion and the number R of contention-based preambles per SS / PBCH block index per valid PRACH occasion are provided to the UE by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0623] For type 2 random access procedure that has a common configuration of PRACH occasion with type 1 random access procedure, the number N of SS / PBCH block indices associated with one PRACH occasion is provided to the UE by ssb-perRACH-OccasionAndCB-PreamblesPerSSB and the number Q of contention-based preambles per SS / PBCH block index per valid PRACH occasion is provided by msgA-CB-PreamblesPerSSB-PerSharedRO. For the UE provided with a PRACH mask index by msgA-SSB-SharedRO-MaskIndex according to [3, TS 38.321], the PRACH transmission can be on a subset of PRACH occasions associated with the same SS / PBCH block index within the SSB-RO mapping cycle.

[0624] For a type 2 random access procedure with a separate configuration of PRACH occasions for a type 1 random access procedure, when provided, the number N of SS / PBCH block indices associated with one PRACH occasion and the number R of contention-based preambles per SS / PBCH block index per valid PRACH occasion are provided to the UE by msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB; otherwise, by ssb-perRACH-OccasionAndCB-PreamblesPerSSB.

[0625] For a random access procedure associated with a feature combination indicated by FeatureCombinationPreambles, when provided, the number N of SS / PBCH block indices associated with one PRACH occasion is provided by ssb-perRACH-OccasionAndCB-PreamblesPerSSB or msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB, and the number S of contention-based preambles per SS / PBCH block index per valid PRACH occasion is provided by startPreambleForThisPartition and numberOfPreamblesPerSSB-ForThisPartition. For a UE provided with a PRACH mask index by ssb-SharedRO-MaskIndex according to [3, TS 38.321], PRACH transmission can be on a subset of PRACH occasions associated with the same SS / PBCH block index within the SSB-RO mapping cycle.

[0626] For a type 1 random access procedure, or for a type 2 random access procedure with a separate configuration of PRACH occasions for a type 1 random access procedure, if N < 1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH occasions, and R contention-based preambles with consecutive indices associated with the SS / PBCH block index per valid PRACH occasion start from preamble index 0. If N ≥ 1, R contention-based preambles with consecutive indices associated with the SS / PBCH block index n (0 ≤ n ≤ N - 1) per valid PRACH occasion start from the preamble index begin, where For a Type 1 random access procedure, it is provided by totalNumberOfRA-Preambles, or for a Type 2 random access procedure that is separately configured with a PRACH occasion for the Type 1 random access procedure, it is provided by msgA-TotalNumberOfRA-Preambles, and is an integer multiple of N.

[0627] For a Type 2 random access procedure that is co-configured with a PRACH occasion for the Type 1 random access procedure, if N < 1, one SS / PBCH block index is mapped to 1 / N consecutive valid PRACH occasions, and Q contention-based preambles with consecutive indices associated with the SS / PBCH block index for each valid PRACH occasion start from preamble index R. If N ≥ 1, Q contention-based preambles with consecutive indices associated with the SS / PBCH block index n (0 ≤ n ≤ N - 1) for each valid PRACH occasion start from preamble index starting, where For a Type 1 random access procedure, it is provided by totalNumberOfRA-Preambles.

[0628] …

[0629] The SS / PBCH block indices provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon are mapped to valid PRACH occasions in the following order, where the parameters are described in [TS 38.211].

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

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

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

[0633] - Fourth, in ascending order of the index for the PRACH slot

[0634] The association period for mapping the SS / PBCH block index to the PRACH occasion starting from frame 0 is the minimum value in the set determined by the PRACH configuration period according to Table 8.1-1, such that the SS / PBCH block indices are mapped to the PRACH occasions within the association period at least once, where the UE obtains the value of ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon

[0635] For a PRACH transmission triggered by a PDCCH command via a UE, if the value of the random access preamble index field is not zero, the PRACH mask index field [TS 38.212] indicates the PRACH occasion for the 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 command. If the UE is provided with K by cellSpecificKoffset cell,offset , the PRACH occasion is in slot n + 2 μ ·K cell,offset after, where n is the slot of the UL BWP for the PRACH transmission, assuming T TA = 0, which overlaps with the end of the PDCCH command reception, and μ is the SCS configuration for the PRACH transmission.

[0636] For a PRACH transmission triggered by a higher layer, if an ssb-ResourceList is provided, the PRACH mask index is indicated by ra-ssb-OccasionMaskIndex, which indicates the PRACH occasion for the PRACH transmission, where the PRACH occasion is associated with the selected SS / PBCH block index.

[0637] The PRACH occasions are mapped continuously per SS / PBCH block index. Each mapping cycle of the consecutive PRACH occasions per SS / PBCH block index resets the index of the PRACH occasion indicated by the mask index value. The UE selects, for the PRACH transmission, the PRACH occasion indicated by the PRACH mask index value for the SS / PBCH block index indicated in the first available mapping cycle.

[0638] For the indicated preamble index, the ordering of the PRACH occasions is

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

[0640] - Second, in increasing order of the time resource index for time multiplexed PRACH occasions within the PRACH slot

[0641] - Third, in increasing order of the index of the PRACH slot

[0642] For PRACH transmission triggered after a request at a higher layer, if a csirs-ResourceList is provided, the value of ra-OccasionList [5, TS 38.331] indicates a list of PRACH occasions for PRACH transmission, where the PRACH occasions are associated with the selected CSI-RS indexes indicated by the csi-RS. The index of the PRACH occasion indicated by ra-OccasionList is reset every associated mode period.

[0643] Table 8.1-1: Mapping between PRACH configuration period and SS / PBCH block to PRACH occasion association period

[0644] PRACH configuration period (milliseconds) Association period (number of PRACH configuration periods) 10 {1,2,4,8,16} 20 {1,2,4,8} 40 {1,2,4} 80 {1,2} 160 {1}

[0645] … If the random access procedure is initiated by a PDCCH command, then if requested by a higher layer, the UE transmits a PRACH in the selected PRACH occasion, as described in [3, TS 38.321], where the time between the last symbol of the PDCCH command reception and the first symbol of the PRACH transmission is greater than or equal to N T,2 +Δ BWPSwitching +Δ Delay +T switch milliseconds, where

[0646] -N T,2 is the duration of N2 symbols corresponding to the PUSCH preparation time of the UE processing capability 1 [TS 38.214], assuming that μ corresponds to the minimum SCS configuration between the SCS configuration of the PDCCH command and the SCS configuration of the corresponding PRACH transmission

[0647] - If the activated UL BWP does not change and Δ BWPSwitching is defined in [TS 38.133], then Δ BWPSwitching = 0, otherwise

[0648] - For FR1, Δ Delay = 0.5 milliseconds, and for FR2, Δ Delay = 0.25 milliseconds

[0649] -T switch is the handover gap duration as defined in [TS 38.214]

[0650] …

[0651] 8.1A PUSCH for type 2 random access procedure

[0652] For a Type 2 random access procedure, when applicable, the UE transmits a PUSCH after transmitting a PRACH. The UE encodes the transport block provided for PUSCH transmission using redundancy version number 0. The PUSCH transmission is 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.

[0653] 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 in the PUSCH occasion. If the PRACH preamble is not mapped to a valid PUSCH occasion, the UE may transmit the PRACH preamble in a valid PRACH occasion.

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

[0655] The UE determines the time resources and frequency resources for the PUSCH occasion in the mid UL BWP from 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.

[0656] The UE determines the first interlace or the first RB for the first PUSCH occasion in the active UL BWP either from interlaceIndexFirstPO-MsgA-PUSCH or from frequencyStartMsgA-PUSCH that provides an offset from the first RB of the active UL BWP by the number of RBs in the active UL BWP. The PUSCH occasion includes the number of interlaces or the number of RBs provided by nrofInterlacesPerMsgA-PO or by nrofPRBs-perMsgA-PO, respectively. Successive PUSCH occasions in the frequency domain of the UL BWP are separated by a number of RBs provided by guardBandMsgA-PUSCH. The number N of PUSCH occasions in the frequency domain of the UL BWP f is provided by nrofMsgA-PO-FDM.

[0657] …

[0658] If the UE does not have a dedicated RRC configuration, or has the initial UL BWP as the active UL BWP, or is not provided with startSymbolAndLengthMsgA-PO, msgA-PUSCH-timeDomainAllocation provides the SLIV and the PUSCH mapping type for PUSCH transmission by indicating the following

[0659] - one of the first maxNrofUL-Allocations values from the PUSCH-TimeDomainResourceAllocationList, provided that the PUSCH-TimeDomainResourceAllocationList is provided in PUSCH-ConfigCommon

[0660] - one of the entries from Table 6.1.2.1.1-2 or Table 6.1.2.1.1-3 in [TS 38.214], provided that the PUSCH-TimeDomainResourceAllocationList is not provided in PUSCH-ConfigCommon

[0661] Otherwise, the UE is provided with the SLIV by startSymbolAndLengthMsgA-PO and the PUSCH mapping type by mappingTypeMsgA-PUSCH for PUSCH transmission.

[0662] To map one or more preambles of a PRACH slot to a PUSCH occasion associated with a DMRS resource, the UE determines a first slot for starting the first PUSCH occasion in the active UL BWP from msgA-PUSCH-TimeDomainOffset, where the msgA-PUSCH-TimeDomainOffset provides an offset in terms of the number of slots in the active UL BWP relative to the start of the PUSCH slot that contains the start of each PRACH slot. The UE does not expect to have PRACH preamble transmission and PUSCH transmission with msgA in the PRACH slot or the PUSCH slot, or overlapping msgA PUSCH occasions for MsgA PUSCH configuration. The UE expects the first PUSCH occasion in each slot to have the same SLIV for PUSCH transmission provided by startSymbolAndLengthMsgA-PO or msgA-PUSCH-timeDomainAllocation [TS 38.214].

[0663] Consecutive PUSCH occasions within each slot are separated by guardPeriodMsgA-PUSCH symbols and have the same duration. The number of time-domain PUSCH occasions N in each slot t is provided by nrofMsgA-PO-perSlot, and the number of consecutive slots N that contain PUSCH occasions s is provided by nrofSlotsMsgA-PUSCH.

[0664] …

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

[0666] Each consecutive number N of valid PRACH occasions in a PRACH slot preamble of preamble indices

[0667] - First, in ascending order of preamble indices within a single PRACH occasion

[0668] - Second, in ascending order of frequency resource indices for frequency multiplexed PRACH occasions

[0669] - Third, in ascending order of time resource indices for time multiplexed PRACH occasions within a PRACH slot

[0670] are mapped to valid PUSCH occasions and associated DMRS resources

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

[0672] - Second, in ascending order of the DMRS resource index within the PUSCH occasion, where the DMRS is first indexed by the DMRS port id in ascending order, and then the DMRS resource index is determined in ascending order of the DMRS sequence index

[0673] - Third, in ascending order of the time resource index t for the time multiplexed PUSCH occasion within the PUSCH time slot id in ascending order

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

[0675] where N preamble = ceil(T preamble / T PUSCH ), T preamble 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

[0676] 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. Additionally, for unpaired spectrum and for SS / PBCH blocks with indices provided by ssb-PositionsInBurst in SIB1 or by ServingCellConfigCommon

[0677] - If the UE is not provided with tdd-UL-DL-ConfigurationCommon, the PUSCH occasion is valid provided that the PUSCH occasion

[0678] - does not precede the SS / PBCH block in the PUSCH time slot, and

[0679] - starts at least N gap symbols after the last SS / PBCH block symbol, where N gapProvided in Table 8.1-2 and, if channelAccessMode = "semiStatic" is provided, does not overlap a set of consecutive symbols before the start of the next channel occupancy time when the UE is not transmitting.

[0680] - If the UE is provided with tdd-UL-DL-ConfigurationCommon, the PUSCH occasion is valid provided that the PUSCH occasion

[0681] - Is within a UL symbol, or

[0682] - Does not precede an SS / PBCH block in a PUSCH slot, and

[0683] - Starts at least N gap symbols after the last downlink symbol and starts at least N gap symbols after the last symbol of the SS / PBCH block, where N gap Is provided in Table 8.1-2 and, if channelAccessMode = "semiStatic" is provided, does not overlap a set of consecutive symbols before the start of the next channel occupancy time when the UE is not transmitting

[0684] ****************************End of citation [6]******************************

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

[0686] 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 result in labor-intensive and time-consuming operations. Moreover, the lack of interference management schemes will lead to severe interference and capacity problems between RFID readers, especially in the case of dense deployment. RFID is difficult to support large-scale seamless coverage networks. In contrast, research on environmental IoT has investigated the feasibility of new IoT technologies within the Third Generation Partnership Project (3GPP) system.

[0687] An environmental IoT device / user equipment (UE) has characteristics such as ultra-low complexity, extremely small device size, and long life cycle. The environmental IoT device / UE has complexity and power consumption that are several orders of magnitude lower than existing 3GPP low-power wide-area (LPWA) technologies (e.g., NarrowBand Internet of Things (NB-IoT), Enhanced Machine-Type Communication (eMTC)). The environmental IoT device / UE may or may not 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 an intermediate node. In topology 1, the environmental IoT device / UE communicates directly and bidirectionally with the base station. In topology 2, the environmental IoT device / UE communicates bidirectionally with an intermediate node (e.g., a UE or a relay node) between the environmental IoT device / UE and the base station. The uplink (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 about the environmental IoT (device / UE) can be found in research projects [1] RP-234058 and [2] 3GPP TR 38.848 V18.0.0.

[0688] To achieve data and / or signaling transmission or reception, the UE should be pre-configured with at least some configurations related to data / signaling transmission or reception. For example, the configuration can include resource configuration for data / signaling transmission or reception. For normal / legacy UEs in New Radio (NR), the UE can receive common configurations via system information and UE-specific configurations via dedicated signaling (e.g., Radio Resource Control (RRC) reconfiguration). However, for environmental IoT UEs, due to the characteristics of environmental IoT (e.g., ultra-low complexity and ultra-low power consumption), lightweight signaling procedures should be sought. It is assumed that the Physical Broadcast Channel (PBCH) and / or system information may not be applicable to environmental IoT devices. A method for an environmental IoT device / UE to obtain relevant configurations and / or resources for performing transmission (e.g., in response to a random access procedure for an inventory triggered by the network) should be designed.

[0689] The first UE determines (or derives) at least one configuration (e.g., the first configuration) by a first method, where the configuration (e.g., the first configuration) is determined (or derived) by a second UE by a second method. The configuration can be used for (data or signaling) transmission or reception. The configuration can be used for a random access (RA) procedure and / or initial entry.

[0690] The network node can configure the first UE with the (first) configuration by the first method. The network node can provide the (first) configuration to the first UE by the first method. The network node can not configure the first UE with the (first) configuration by the second method. The network node can not provide the (first) configuration to the first UE by the second method.

[0691] The network node can configure the second UE with the (first) configuration by the second method. The network node can provide the (first) configuration to the second UE by the second method. The network node can not configure the second UE with the (first) configuration by the first method. The network node can not provide the (first) configuration to the second UE by the first method.

[0692] The first UE can perform (data or signaling) transmission or reception without at least one configuration (e.g., the first configuration), where the second UE requires (or uses) the configuration (e.g., the first configuration) to perform (data or signaling) transmission or reception.

[0693] The network node can not configure the first UE with the (first) configuration, e.g., for the first UE to perform (data or signaling) transmission or reception. The network node can configure the second UE with the (first) configuration, e.g., for the second UE to perform (data or signaling) transmission or reception.

[0694] The first UE can determine (or derive) a configuration (e.g., the first configuration) by the first method. The first UE can not determine (or derive) a configuration (e.g., the first configuration) by the second method. The first UE can determine (or apply, or use) a first value of the configuration.

[0695] The second UE can determine (or derive) a configuration (e.g., the first configuration) by the second method. The second UE can not determine (or derive) a configuration (e.g., the first configuration) by the first method. The second UE can determine (or apply, or use) a second value of the configuration.

[0696] The first method and the second method can be different. The first method and the second method can be the same. The method (e.g., the first method, the second method) can be (or include) one or more of the following.

[0697] Receiving common signaling (e.g., from the network)

[0698] A UE (e.g., a first UE, a second UE, a device) may receive common signaling that includes at least a first configuration. The UE may apply the first configuration in response to receiving the common signaling that includes the first configuration. The UE may obtain the first configuration through the common signaling. The first configuration may be (or include) a cell-specific configuration. The first configuration may be (or include) a configuration that is common to multiple UEs, a group of UEs, and / or a UE group.

[0699] The common signaling may be (or include) broadcast signaling. The common signaling may be received by more than one UE. The common signaling may be received by multiple UEs (or a group of UEs) in a UE group, for example. The common signaling may be transmitted to more than one UE. The common signaling may be transmitted to multiple UEs (or a group of UEs) in a UE group, for example. The common signaling may be (or include) system information for environmental IoT, for example. The common signaling may be (or include) paging for environmental IoT, for example. The common signaling may be (or include) RRC signaling (e.g., an RRC configuration message), Medium Access Control (MAC) signaling (e.g., a MAC control element (CE)), layer 2 signaling, Physical Layer (PHY) signaling (e.g., a Physical Downlink Control Channel (PDCCH), Downlink Control Information (DCI)), or layer 1 signaling for environmental IoT, for example. The common signaling may be (or include) a carrier (signal) and / or an interrogation signal. The common signaling may be used to trigger (or indicate) a transmission (or reception) of a UE (e.g., a first UE, a second UE) and / or multiple UEs. A transmission from the UE may be (or include) a backscatter transmission (or reception), or may be generated internally by the UE. The common signaling may be used to supply power and / or energy to the UE. The common signaling may be used to trigger (or indicate) a (random) entry process (or initial access) of a UE and / or multiple UEs, for example.

[0700] Receiving dedicated signaling (e.g., from the network)

[0701] A UE (e.g., a first UE, a second UE, a device) may receive dedicated signaling that includes at least a first configuration. The UE may apply the first configuration in response to receiving the dedicated signaling that includes the first configuration. The UE may obtain the first configuration through the dedicated signaling. The first configuration may be (or include) a UE-specific configuration. The first configuration may be (or include) a configuration dedicated to a (single) UE.

[0702] The dedicated signaling may be (or include) UE-specific signaling. The dedicated signaling may be (or include) RRC signaling (e.g., RRC configuration message). The dedicated signaling may be (or include) MAC signaling (e.g., MAC CE). The dedicated signaling may be (or include) PHY signaling (e.g., PDCCH, DCI). The dedicated signaling may be (or include) a carrier (signal) and / or an interrogation signal. The dedicated signaling may 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 may be (or include) a backscatter transmission (or reception), or may be generated internally by the UE. The dedicated signaling may be used to supply power and / or energy to the UE. The dedicated signaling may be used to trigger (or indicate) the RA process (or initial access) of the UE.

[0703] Pre-configured or predefined

[0704] A UE (e.g., the first UE, the second UE, the device) may apply (or use) a pre-configured (or pre-defined, or fixed) value of a first configuration. The UE may apply (or use) a pre-configured (or pre-defined, or fixed) configuration of a first configuration. The UE may not receive signaling that includes at least the first configuration. The UE may apply (or use) the first configuration without receiving signaling that includes at least the first configuration. The signaling may be common signaling and / or dedicated signaling. The UE may apply a pre-configured (or pre-defined, or fixed) value or configuration for performing a backscatter transmission (or reception) or for performing a transmission generated internally by the UE. Preferably, in some embodiments, the UE may perform a transmission in response to the reception / detection of a carrier (signal).

[0705] Mixture of the above

[0706] A UE (e.g., the first UE, the second UE, the device) may determine the first configuration by a hybrid method. The UE may determine the first configuration by more than one of the above methods.

[0707] In one or more instances, multiple values (or configurations) may be pre-configured (or pre-defined) for the first configuration, and signaling (e.g., common, dedicated) may be used to indicate to the UE which of the multiple values (or configurations) to apply to the first configuration.

[0708] In one or more instances, the UE may receive a part of the first configuration via a first signaling (e.g., common signaling) and another part of the first configuration via a second signaling (e.g., dedicated signaling). The UE may apply the first configuration when / after receiving both or either of the first signaling and the second signaling / responsive to receiving both or either of the first signaling and the second signaling.

[0709] In one or more instances, if the UE does not receive signaling (e.g., common, dedicated), the UE may apply (or use) a preconfigured (or predefined, or fixed) value of the first configuration. When the UE receives signaling (e.g., common, dedicated), the UE may apply the first configuration indicated / provided by the signaling.

[0710] In one or more instances, when, during a first carrier (signal) duration, the UE detects / receives a first carrier (signal) and / or the UE has not received signaling (e.g., common, dedicated), the UE may apply (or use) a preconfigured (or predefined, or fixed) value to perform a first transmission, where the first transmission has the first carrier (signal) duration or is associated with the first carrier (signal) duration. The first transmission may be a backscatter transmission (or reception), or a transmission generated internally by the UE. When, during a second carrier (signal) duration, the UE detects / receives a second carrier (signal) and / or the UE receives a first signaling (e.g., common signaling, dedicated signaling), the UE may apply the first configuration indicated / provided by the first signaling to perform a second transmission, where the second transmission has the second carrier (signal) duration or is associated with the second carrier (signal) duration. The second transmission may be a backscatter transmission (or reception), or a transmission generated internally by the UE. When, during a third carrier (signal) duration, the UE detects / receives a third carrier (signal) and / or the UE receives a second signaling (e.g., common signaling, dedicated signaling), the UE may apply the first configuration indicated / provided by the second signaling to perform a third transmission, where the third transmission has the third carrier (signal) duration or is associated with the third carrier (signal) duration. The third transmission may be a backscatter transmission (or reception), or a transmission generated internally by the UE.

[0711] The carrier (signal) duration may be the duration when the UE can receive the carrier (signal). The carrier (signal) duration may start when the (new) carrier (signal) starts. The carrier (signal) duration may end when the carrier (signal) stops. The carrier (signal) duration may be detected by the UE or defined / configured by the network (NW).

[0712] To address this issue, the first signaling (e.g., common signaling) that triggers a transmission and / or a procedure (e.g., a random access procedure) may contain or indicate resources or configurations for more than one UE / device (e.g., a group of UE / devices) (or for use by more than one UE / device (e.g., a group of UE / devices)). In response to receiving the first signaling, the UE / device may initiate a random access procedure and perform a first transmission based on the resources or configurations provided or indicated in the first signaling, where the first signaling is for more than one UE / device. The first signaling is transmitted or provided to more than one UE / device.

[0713] In one or more instances, a first UE / device may receive, for example, from a network node or a second UE, a first signaling that triggers a transmission and / or a procedure (e.g., a (random) access procedure). The second UE may be an intermediate node, a reader, and / or a legacy UE. The first signaling may be common signaling. The first signaling may be used for more than one UE / device. The first signaling may be transmitted to more than one UE / device. The first signaling may be received by more than one UE / device. The first signaling may be used to trigger a transmission and / or a procedure (e.g., a random access procedure) of more than one UE / device. The first signaling may (be used to) indicate that more than one UE / device triggers a transmission and / or a procedure (e.g., a random access procedure). More than one UE / device may be a group of UE / devices. The first signaling may be a paging (message) for ambient IoT. The first signaling may indicate (at least) the first UE / device, for example, by including / indicating a device identifier (ID) of the first UE / device and / or a group ID of the first UE / device. The first signaling may indicate (at least) a third UE / device, for example, by including / indicating a device ID of the third UE / device and / or a group ID of the third UE / device. The first signaling may not indicate the third UE / device. More than one UE / device may include the first UE / device and / or the third UE / device. More than one UE / device may be ambient IoT UE / devices. Preferably, in some embodiments, the first signaling does not imply / include system information or a physical broadcast channel.

[0714] In response to receiving the first signaling, the first UE / device may trigger a random access procedure and perform a first transmission of the random access procedure based on a first resource and / or a first configuration provided in the first signaling. The first UE / device may transmit the first transmission to a network node or a second UE. The first signaling may include and / or indicate (at least) the first resource and / or the first configuration (e.g., for the first UE / device). The first resource and / or the first configuration may be used for, associated with, and / or related to the random access procedure. The first resource and / or the first configuration may be used by, associated with, and / or related to the first UE / device. The first resource and / or the first configuration may be associated with a device ID of the first UE / device. The first resource and / or the first configuration may be associated with a group ID of the first UE / device. The first resource may include (at least) a first frequency (domain) resource / occasion (set) and / or a first time (domain) resource / occasion (set). The first resource may be determined based on the first configuration and / or a pre-configuration.

[0715] In response to receiving the first signaling, the third UE / device may trigger another random access procedure and / or perform another first transmission of another random access procedure based on the second resource and / or the second configuration provided in the first signaling. The third UE / device may transmit the another first transmission to a network node or a second UE. The first signaling may include and / or indicate the second resource and / or the second configuration (e.g., for the third UE / device). The second resource and / or the second configuration may be used for, associated with, and / or related to another random access procedure. The second resource and / or the second configuration may be used by, associated with, and / or related to the third UE / device. The second resource and / or the second configuration may be associated with the device ID of the third UE / device. The second resource and / or the second configuration may be associated with the group ID of the third UE / device. The second resource may include (at least) a second frequency (domain) resource / occasion (set) and / or a second time (domain) resource / occasion (set). The second resource may be determined based on the second configuration and / or another pre-configuration.

[0716] Throughout this disclosure, when a UE determines a configuration, the UE may request, receive, derive, obtain, determine, store, apply, and / or use the configuration. The configuration (e.g., the first configuration) may be (or include) at least one or more of the following. The UE may determine different configurations by different methods. The configuration (e.g., the first configuration) may be one or more parameters of the following configurations.

[0717] Configuration related to Synchronization Signal Block (SSB) (or Channel State Information Reference Signal (CSI-RS))

[0718] The configuration may be (or include) any of the following: a reference signal received power (RSRP) threshold for an SSB (e.g., rsrp-ThresholdSSB, msgA-RSRP-ThresholdSSB), an RSRP threshold for a CSI-RS (e.g., rsrp-ThresholdCSI-RS), a beam failure recovery configuration, and / or ssb-PositionsInBurst.

[0719] For the RA procedure, a UE (e.g., an environmental IoT UE, a first UE, the same hereinafter) may not require SSB / CSI-RS related configurations, e.g., for (data or signaling) transmission or reception. The UE may not be allowed to configure SSB / CSI-RS related configurations. For the RA procedure, the UE may not perform SSB selection and / or CSI-RS selection, e.g., for (data or signaling) transmission or reception. For the RA procedure, the UE may not select SSB / CSI-RS, e.g., for (data or signaling) transmission or reception. The UE may not be configured with parameters associated with a beam. The SSB and / or CSI-RS may not be provided to the UE (explicitly). The RA resources / configurations may be (only) allowed to be associated with a specific or the same SSB. The UE may (always) select a specific or the same SSB.

[0720] For another type of UE (e.g., a non-environmental IoT UE, a second UE, the same hereinafter), the UE may receive the configuration via system information. The UE may require the configuration. For the RA procedure, the UE may perform SSB selection and / or CSI-RS selection, e.g., for (data or signaling) transmission or reception. The UE may be configured with parameters associated with a beam. The SSB and / or CSI-RS may be provided to the UE (explicitly).

[0721] Configuration related to Bandwidth Part (BWP) (or frequency resources)

[0722] The configuration may be related to frequency resources. The configuration may be (or include) any of the following: initialUplinkBWP, initialDownlinkBWP, BWP, subcarrierSpacing, BWP-Downlink, BWP-DownlnkCommon, BWP-DownlinkDedicated, BWP-Id, BWP-Uplink, BWP-UplinkCommon, BWP-UplinkDedicated.

[0723] A UE (e.g., an environmental IoT UE, a first UE, the same below) may be configured with one or more (initial) BWPs of a cell. Alternatively and / or additionally, a cell may comprise or indicate more than one (for environmental IoT) (initial) BWP. The UE may be configured with different initial BWPs in different frequency bands and / or frequencies of the cell. The UE may be configured with multiple BWPs that have an in-band spectrum deployment to an NR cell. Different / separate RA configurations and / or RA resources may be configured on more than one BWP. The RA configuration and / or RA resources may correspond to (one or more) UEs, UE groups, UE types, power levels, UL data types, and / or UL data sizes, associated with and / or used by them. The BWP may be a UL BWP.

[0724] Preferably, in some embodiments, a BWP (above or below) may be changed / represented / replaced by a frequency (sub)band, a set of frequency resources, or a frequency resource. The BWP, bandwidth, and / or frequency band may be used for reader to (environmental IoT) device (R2D) and / or (environmental IoT) device to reader (D2R).

[0725] Preferably, in some embodiments, when the UE receives / detects a carrier (signal), an R2D signal / channel, and / or a physical (environmental IoT) device to reader channel (PDRCH), the UE may derive / determine an (initial) BWP, an (initial) frequency (sub)band, or a set of (initial) frequency resources based at least on the frequency (e.g., a downlink (DL) carrier or a DL frequency band), such as the frequency of the received / detected carrier (signal), the R2D signal / channel, and / or a physical reader (to environmental IoT) device channel (PRDCH). Preferably, in some embodiments, the UE may derive / determine an (initial) BWP, an (initial) frequency (sub)band, or a set of (initial) frequency resources based at least on BWP, frequency (sub)band, or set of frequency resource information provided by the network.

[0726] For another type of UE (e.g., a non-environmental IoT UE, a second UE, the same below), the UE may receive configuration via system information and / or dedicated RRC signaling (e.g., RRC reconfiguration). The UE may be configured with one initial BWP.

[0727] Configuration related to RA and / or D2R transmission

[0728] The configuration may be (or include) any 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, RA preamble group configuration, RACH-ConfigCommon, PRACH configuration, RACH-ConfigCommonTwoStepRA, RACH-ConfigDedicated, RACH-ConfigGeneric, RACH-ConfigGenericTwoStepRA, and / or PDRCH configuration.

[0729] A UE (e.g., an environmental IoT UE / device, the first UE, the same below) may be configured with multiple RA configurations of a cell. Alternatively and / or additionally, the cell may provide or indicate multiple (for environmental IoT) RA configurations. The UE may be configured with multiple RA resource groups. Alternatively and / or additionally, the cell may provide or indicate multiple (for environmental IoT) RA resource groups. The UE may be configured with multiple RA configuration groups. Alternatively and / or additionally, the cell may provide or indicate multiple (for environmental IoT) RA configuration groups. 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 configuration, RA resource group, and / or RA configuration group may correspond to (one or more) UEs, UE groups, UE types, power levels, UL data types, and / or UL data sizes, be associated with, and / or be used by them.

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

[0731] Configuration related to downlink control signaling

[0732] The configuration may be (or include) any of the following: PDCCH configuration, PRDCH 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.

[0733] A UE (e.g., an environmental IoT UE, a first UE, the same hereinafter) may be configured with one (or more) PDCCH configurations, PRDCH configurations, CORESET configurations, and / or search space configurations. A UE may not be allowed to configure more than one PDCCH configuration, PRDCH configuration, CORESET configuration, and / or search space configuration. A UE may be pre-configured with one (or more) PDCCH configurations, PRDCH configurations, CORESET configurations, and / or search space configurations. A UE may use (or apply) the pre-configured (or fixed) values of the configurations. A UE may not require the configurations. A UE may not require network-provided configurations.

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

[0735] Configuration related to paging

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

[0737] A UE (e.g., an environmental IoT UE / device, a first UE, the same hereinafter) may be at least configured with paging-related configurations. A UE may be at least pre-configured with paging-related configurations. A UE may use (or apply) the pre-configured (or fixed) values of the configurations. A UE may not require paging-related configurations. A UE may not require network-provided paging-related configurations.

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

[0739] Configuration related to system information

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

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

[0742] For another type of UE (e.g., a non-environmental IoT UE, a second UE, the same hereinafter), the UE can receive configurations through system information.

[0743] Configuration related to data transmission or reception

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

[0745] A UE (e.g., an environmental IoT UE / device, a first UE, the same hereinafter) can be configured with at least configurations related to data transmission or reception. The UE can be pre-configured with the configurations. The UE can use (or apply) the pre-configured (or fixed) values of the configurations. The UE may not need the configurations. The UE may not need the network to provide configurations.

[0746] For another type of UE (e.g., a non-environmental IoT UE, a second UE, the same hereinafter), the UE can receive configurations through system information and / or dedicated RRC signaling (e.g., RRC reconfiguration).

[0747] Configuration related to small data transmission

[0748] The configuration can 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 Small Data Transmission (SDT) configuration.

[0749] A UE (e.g., an ambient IoT UE / device, the first UE, the same hereinafter) can be configured with at least configurations related to small data transmission. The UE can be pre-configured with at least the configurations. The UE can use (or apply) the pre-configured (or fixed) values of the configurations. The UE may not need the configurations. The UE may not need the network to provide configurations.

[0750] For another type of UE (e.g., a non-ambient IoT UE, the second UE, the same hereinafter), the UE can receive configurations via system information and / or dedicated RRC signaling (e.g., RRC re-configuration).

[0751] Others

[0752] The configurations can be (or include) any of the following: configurations related to uplink control information, PUCCH-ConfigCommon, scheduling request configurations, Sounding Reference Signal (SRS) configurations, Packet Data Convergence Protocol (PDCP) configurations, Radio Link Control (RLC) configurations, RLC channel configurations, logical channel configurations, radio bearer configurations, Buffer Status Report (BSR) configurations, Power Headroom Report (PHR) configurations, Discontinuous Reception (DRX) configurations, MAC-CellGroupConfig, timing advance configurations, Timing Advance (TA) timer configurations, TA report configurations, radio link monitoring configurations, measurement configurations, measurement interval configurations, measurement object configurations, and / or measurement report configurations.

[0753] A UE (e.g., an ambient IoT UE / device, the first UE, the same hereinafter) can be configured with at least the configurations. The UE can be pre-configured with at least the configurations. The UE can use (or apply) the pre-configured (or fixed) values of the configurations. The UE may not need the configurations. The UE may not need the network to provide configurations.

[0754] For another type of UE (e.g., a non-ambient IoT UE, the second UE, the same hereinafter), the UE can receive configurations via system information and / or dedicated RRC signaling (e.g., RRC re-configuration).

[0755] The first UE may be an ambient IoT UE / device. 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.

[0756] The second UE may not be an ambient IoT UE / device. The second UE may be a normal (or traditional) UE. The second UE may be a second type of UE. The second UE may be a second type of ambient IoT UE.

[0757] The first UE and the second UE may be different. The first UE and the second UE may have different UE types. The first UE (or UE type) and the second UE (or UE type) may be distinguished based at least on a first factor. The first factor may be one or more of the following.

[0758] UE type

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

[0760] For example, the first type of UE may be device A or device B, as considered in [2] 3GPP TR 38.848 V18.0.0 for example. The first type of UE may have (or be equipped with) a battery or energy storage. The first type of UE may not have (or be equipped with) a battery or energy storage. The first type of UE may not have (or be equipped with) DL / UL amplification. The first type of UE may be a passive or semi - passive device. The first type of UE may generate UL transmissions by backscattering. The first type of UE may perform backscattering transmissions. The first type of UE may not be able to generate UL transmissions alone (internally). The first type of UE may not have the ability to generate signals without backscattering.

[0761] For example, the second type of UE may be device C, as considered in [2] 3GPP TR 38.848 V18.0.0 for example. The second type of UE may have (or be equipped with) a battery or energy storage. The second type of UE may have (or be equipped with) DL / UL amplification. The second type of UE may be an active device. The second type of UE may generate UL transmissions by backscattering. The second type of UE may perform backscattering transmissions. The second type of UE may be able to generate UL transmissions alone (internally). The second type of UE may have the ability to generate signals without backscattering.

[0762] Power level

[0763] The power level may include any one or more of the following embodiments. The UE may use the same or different power level embodiments for different RA resource selection (steps), e.g., determining the BWP, determining the RA resource / configuration group, determining the RA type, determining the RA preamble, determining the Random Access Channel (RACH) occasion, determining the Physical Uplink Shared Channel (PUSCH) occasion, and / or determining the PDRCH 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.

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

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

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

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

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

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

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

[0771] In one embodiment, the power level may be the power difference between the (downlink) path loss and the expected / 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 expected / derived / determined UE transmission power may be used for backscatter transmission or for UL transmission generated internally by the UE.

[0772] In one embodiment, the power level may be the power difference between the battery power / stored power / available power and the expected / derived / determined / maximum UE transmission power. The expected / 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 process.

[0773] In one embodiment, the power level may be the power difference between the predefined / (pre)-configured / indicated power and the expected / 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 process. Preferably, in some embodiments, the predefined / (pre)-configured / indicated power may be the expected / estimated power consumption (amount) for completing the corresponding RA process. The expected / derived / determined UE transmission power may be used for backscatter transmission or for UL transmission generated internally by the UE.

[0774] (UL) Data type

[0775] (UL) data types may be differentiated at least by use case, traffic scenario, service type, Quality of Service (QoS), logical channel (group), and / or topology. The (UL) data types may be indicated by the network or by a higher layer of the UE. The UE may initiate or trigger an RA process for transmitting (UL) data.

[0776] (UL) Data size

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

[0778] UE ID

[0779] A UE ID can be assigned to the UE. The UE ID can be predefined or (pre-)configured for the UE (e.g., by the UE). The UE ID can be configured or indicated to the UE (e.g., by the NW). The UE can calculate, select, derive, or determine the UE ID by itself. The identification of the UE and / or the UE ID can be or include a random number, a temporary number, a preamble number, and / or an ID selected / generated / determined by the UE. The identification of the UE and / or the UE ID can be or include the device ID of the UE, the UE ID, the group ID, the application server (AS) ID, and / or the radio network temporary identifier (RNTI).

[0780] UE group

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

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

[0783] 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 based at least 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 the 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.

[0784] 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), R2D signal / channel, and / or PRDCH. More specifically, a UE can determine / derive its location or range from the network / intermediate node based on the received power of the carrier (signal), R2D signal / channel, and / or PRDCH transmitted from the network / intermediate node. UEs in the same location and / or the same range can represent UEs having the same received power range of the carrier (signal), R2D signal / channel, and / or PRDCH. 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 within the range that can receive the same power supply, carrier, R2D signal / channel, and / or PRDCH and / or NW signaling can be (randomly) distributed to different UE groups.

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

[0786] A UE can receive configurations related to environmental IoT. A UE can receive configurations and / or resources for (random) access (procedure). The resources / configurations can include, for example, BWP for D2R transmission, access resource / configuration group, access preamble (group), RACH occasion, PUSCH occasion, PDRCH occasion, frequency, and / or frequency band. The resources and / or configurations for the access procedure can include, for example, parameters for D2R transmission, random numbers, group numbers, and / or auxiliary information. Throughout this disclosure, the following can be interchangeable: RACH occasion, PRACH occasion, and / or PDRCH occasion. The PDRCH occasion can be the time and / or frequency resource for PDRCH transmission or D2R transmission.

[0787] The power level can represent the power state of the UE.

[0788] Throughout this disclosure, the "RA process" may be replaced by the "(initial) access process" and / or the access process performed by the (ambient IoT) UE / device. The (initial) access process may be contention-based or contention-free.

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

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

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

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

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

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

[0795] Throughout this disclosure, "PDSCH" may be replaced by "uplink shared channel", "PDSCH for ambient IoT", or "PRDCH".

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

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

[0798] Throughout this disclosure, the network (node) may be changed / represented / replaced by an intermediate node and / or a reader.

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

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

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

[0802] 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. The DL transmission and / or DL data may include an indication, configuration, signal / signaling, and / or message from the reader.

[0803] 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 transmitted from the device to the reader, and / or D2R data, referred to as data available on the device side, data transmitted from the device to the reader, and / or D2R data, and / or supplemented by data available on the device side, data transmitted from the device to the reader, and / or D2R data. The UL transmission and / or UL data may include an indication, signal / signaling, and / or message from the device. A UL grant may be one or more resources provided by the reader / NW intermediate node, used by the device / UE, and / or for transmitting / executing a D2R transmission.

[0804] The UE may be referred to as the UE, the RRC layer of the UE, the MAC entity of the UE, the physical layer of the UE, the AS layer of the UE, or the Ambient Internet of Things (A-IoT) layer of the UE.

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

[0806] A traditional UE can be a non-environmental IoT device. A traditional UE can perform processes different from those of an environmental IoT UE. A UE can be a traditional UE with the ability to execute environmental IoT processes. Throughout this disclosure, the following may be interchangeable: a normal UE, a traditional UE.

[0807] An environmental IoT UE can have the capabilities of environmental IoT. A traditional UE may or may not have the capabilities of environmental IoT processes.

[0808] The network can be a network node. The network (node) can be a base station. The network (node) can be an access point. The network (node) can be an evolved Node B (eNB). The network (node) can be a next-generation Node B (gNB). The network (node) can be a gateway. The network can be or include a reader.

[0809] Various examples and embodiments of the present invention are described below.

[0810] Reference Figure 9 , using this and other aspects, systems, and methods of the present invention, method 1000 for a first UE in a wireless communication system includes determining or deriving (at least) a first configuration by a first method, where the first configuration is determined or derived by a second UE by a second method (step 1002).

[0811] Return reference Figure 3 and Figure 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 a memory 310 of a transmitter. A CPU 308 can execute the program code 312 to: (i) determine or derive (at least) a first configuration by a first method, where the first configuration is determined or derived by a second UE by a second method. In addition, the CPU 308 can execute the program code 312 to perform all the described actions, steps, and methods described above, below, or elsewhere herein.

[0812] Reference Figure 10 , using this and other aspects, systems, and methods of the present invention, method 1010 for a network node in a wireless communication system includes configuring a first UE with (at least) a first configuration by a first method (step 1012), and configuring a second UE with (at least) a first configuration by a second method (step 1014).

[0813] Return reference Figure 3 and Figure 4, in one or more embodiments, from the perspective of a network node in a wireless communication system, apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) configure a first UE with (at least) a first configuration by a first method; and (ii) configure a second UE with (at least) a first configuration by a second method. In addition, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or elsewhere herein.

[0814] Reference Figure 11 , using this and other aspects, systems, and methods of the present invention, method 1020 for a first UE in a wireless communication system includes performing transmission or reception without at least a first configuration, where a second UE requires the first configuration to perform transmission or reception (step 1022).

[0815] Return reference Figure 3 and Figure 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 the memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) perform transmission or reception without at least a first configuration, where a second UE requires the first configuration to perform transmission or reception. In addition, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or elsewhere herein.

[0816] Reference Figure 12 , using this and other aspects, systems, and methods of the present invention, method 1030 for a network node in a wireless communication system includes configuring a second UE with (at least) a first configuration for the second UE to perform transmission or reception (step 1032), and not configuring a first UE with (at least) a first configuration for the first UE to perform transmission or reception (step 1032).

[0817] Return reference Figure 3 and Figure 4 , in one or more embodiments, from the perspective of a network node in a wireless communication system, apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) configure a second UE with (at least) a first configuration for the second UE to perform transmission or reception; and (ii) not configure a first UE with (at least) a first configuration for the first UE to perform transmission or reception. In addition, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or elsewhere herein.

[0818] In various embodiments, the first UE is an ambient IoT UE / device.

[0819] In various embodiments, the second UE is not an ambient IoT UE / device.

[0820] In various embodiments, the first UE determines or derives a first value of a first configuration.

[0821] In various embodiments, the second UE determines or derives a second value of the first configuration.

[0822] In various embodiments, the first method or the second method receives common signaling from a network node.

[0823] In various embodiments, the first method or the second method receives dedicated signaling from a network node.

[0824] In various embodiments, the first method or the second method pre-configures or pre-defines the first configuration.

[0825] In various embodiments, the first method and the second method are different.

[0826] In various embodiments, the first configuration includes a configuration related to an SSB or CSI-RS.

[0827] In various embodiments, the first configuration includes a configuration related to a BWP.

[0828] In various embodiments, the first configuration includes a configuration related to a random access procedure.

[0829] In various embodiments, the first configuration includes a configuration related to downlink control signaling.

[0830] In various embodiments, the first configuration includes a configuration related to paging or system information.

[0831] To enable data and / or signaling transmission, the (ambient IoT) UE may trigger an RA process and / or an initial access to the network. For example, the (ambient IoT) UE receives (first) signaling from the NW. In response to receiving the (first) signaling, the (ambient IoT) UE triggers an RA process.

[0832] (The first) signaling can be used to trigger (or indicate) the RA process (or initial access) of the UE, as described above. (The first) signaling can be used to trigger (or indicate) the transmission (or reception) of the UE. The transmission from the UE can be (or include) 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 any one of RRC signaling (e.g., RRC configuration message), MAC signaling (e.g., MAC CE), or PHY signaling (e.g., PDCCH, DCI). (The first) signaling can be (or include) a carrier (signal) and / or an interrogation signal.

[0833] (The first) signaling can be common signaling or dedicated signaling, as described above. Common signaling can be (or include) cell-specific configuration. Common signaling can be (or include) configuration common to multiple UEs, a group of UEs, and / or a UE group. Common signaling can be (or include), for example, broadcast signaling, system information, and / or paging for environmental IoT. Dedicated signaling can be (or include) UE-specific configuration. Dedicated signaling can be (or include) configuration dedicated to a (single) UE. Dedicated signaling can be (or include) RRC signaling (e.g., RRC configuration message). Dedicated signaling can be (or include) MAC signaling (e.g., MAC CE). Dedicated signaling can be (or include) PHY signaling (e.g., PDCCH, DCI).

[0834] Due to the characteristics of environmental IoT, such as ultra-low complexity and ultra-low power consumption, it is not always appropriate for environmental IoT UEs to initiate the RA process, for example, in response to receiving signaling. Environmental IoT UEs should check their ability to initiate the RA process, for example, in response to receiving signaling. In addition, in order to reduce power consumption, enhancements to RA should be sought to avoid conflicts between multiple environmental IoT UEs.

[0835] The UE can determine whether or when to initiate (or trigger, execute) the RA process in response to receiving NW signaling (e.g., the first signaling or paging (for environmental IoT)) or after receiving NW signaling (e.g., the first signaling or paging (for environmental IoT)). The NW signaling can be the (first) signaling described above. The UE can determine whether or when to initiate (or trigger, execute) the RA process based on a first condition.

[0836] The UE can check the first condition in response to receiving the NW signaling (or if the NW signaling is received, when the NW signaling is received, after the NW signaling is received). If the (at least) first condition is met, the UE can initiate, trigger, execute, continue, and / or resume the RA process. If the (at least) first condition is not met, the UE can refrain from initiating, triggering, and / or continuing the RA process. If the (at least) first condition is not met, the UE can stop, cancel, and / or suspend the RA process.

[0837] If the (at least) first condition is met after receiving the signaling or in response to receiving the signaling, the UE can initiate, trigger, execute, continue, and / or resume the RA process. If the (at least) first condition is not met after receiving the signaling or in response to receiving the signaling, the UE can refrain from initiating, triggering, and / or continuing the RA process. Before the (at least) first condition is met after receiving the signaling or in response to receiving the signaling, the UE can refrain from initiating, triggering, continuing, and / or resuming the RA process. If the (at least) first condition is not met after receiving the signaling or in response to receiving the signaling, the UE can stop, cancel, and / or suspend the RA process. After the UE receives the NW signaling or when the UE receives the NW signaling, the UE can check whether the first condition is met. Once the (at least) first condition is met or after the (at least) first condition is met, the UE can initiate the RA process. In response to receiving the NW signaling (or if the NW signaling is received, when the NW signaling is received, after the NW signaling is received), once the (at least) first condition is met, the UE can initiate, trigger, continue, and / or resume the RA process.

[0838] Alternatively and / or additionally, in response to receiving the NW signaling (or if the NW signaling is received, when the NW signaling is received, after the NW signaling is received), the UE can initiate, trigger, continue, and / or resume the RA process. The UE can determine whether or when to perform the RA resource selection process (or the RA preamble transmission process or the MSGA transmission process) (the initial or first time or first step) of the RA process based on the first condition.

[0839] When the RA process is pending, the UE can check the first condition. When the UE receives NW signaling and / or is triggered to initiate the RA process (e.g., by the upper layer), after the UE receives the NW signaling and / or is triggered to initiate the RA process (e.g., by the upper layer), or subsequent to the UE receiving the NW signaling and / or being triggered to initiate the RA process (e.g., by the upper layer), the RA process is pending. When the RA process is suspended, after the RA process is suspended, or subsequent to the RA process being suspended, the RA process is pending. If the first condition is met, the UE can perform the RA resource selection process (or RA preamble transmission process or MSGA transmission process) (the initial or first time or first step) of the RA process. If the first condition is not met, the UE may not perform the RA resource selection process (or RA preamble transmission process or MSGA transmission process) (the initial or first time or first step) of the RA process.

[0840] The UE can check the first condition in response to initiating, triggering, continuing, and / or resuming the RA process. If the first condition is met, the UE can perform the RA resource selection process (or RA preamble transmission process or MSGA transmission process) (the initial or first time or first step) of the RA process. If the first condition is not met, the UE may not perform the RA resource selection process (or RA preamble transmission process or MSGA transmission process) (the initial or first time or first step) of the RA process. If the first condition is not met, the UE can delay and / or suspend the RA process.

[0841] If, after initiating, triggering, continuing, and / or resuming the RA process or in response to initiating, triggering, continuing, and / or resuming the RA process, a first condition is satisfied, the UE may perform the RA resource selection process (or RA preamble transmission process or MSGA transmission process) (the initial or first time or first step) of the RA process. If, after initiating, triggering, continuing, and / or resuming the RA process or in response to initiating, triggering, continuing, and / or resuming the RA process, the first condition is not satisfied, the UE may not perform the RA resource selection process (or RA preamble transmission process or MSGA transmission process) (the initial or first time or first step) of the RA process. Before the first condition is satisfied after initiating, triggering, continuing, and / or resuming the RA process or in response to initiating, triggering, continuing, and / or resuming the RA process, the UE may not perform the RA resource selection process (or RA preamble transmission process or MSGA transmission process) (the initial or first time or first step) of the RA process. If, after initiating, triggering, continuing, and / or resuming the RA process or in response to initiating, triggering, continuing, and / or resuming the RA process, the first condition is not satisfied, the UE may delay and / or suspend the RA process. After or when the UE receives the NW signaling and initiates, triggers, continues, and / or resumes the RA process, the first condition may not be satisfied. Once the first condition is satisfied or after the first condition is satisfied, the UE may perform the RA resource selection process (or RA preamble transmission process or MSGA transmission process) (the initial or first time or first step) of the RA process. In response to initiating, triggering, continuing, and / or resuming the RA process (or if initiating, triggering, continuing, and / or resuming the RA process, at the time of initiating, triggering, continuing, and / or resuming the RA process, after initiating, triggering, continuing, and / or resuming the RA process), once the first condition is satisfied, the UE may perform the RA resource selection process (or RA preamble transmission process or MSGA transmission process) (the initial or first time or first step) of the RA process.

[0842] The first condition for determining whether or when to initiate (or trigger, execute) the RA process and the first condition for determining whether or when to perform the RA resource selection process (or RA preamble transmission process or MSGA transmission process) (the initial or first time or first step) of the RA process may be the same. Alternatively, the first condition for determining whether or when to initiate (or trigger, execute) the RA process and the first condition for determining whether or when to perform the RA resource selection process (or RA preamble transmission process or MSGA transmission process) (the initial or first time or first step) of the RA process may be (partially or completely) different.

[0843] As described above, for example, based on the first factor, one or more first conditions can be applied by the first UE and may not be applied by the second UE. The first UE and the second UE may have different configurations and / or values for one or more of the first conditions. The first UE and the second UE may be different UEs distinguished by the first factor, for example. The first UE and the second UE may be ambient IoT UEs. The UE may determine whether to use one or more of the first conditions based on the first factor. The UE may determine which value of one or more of the first conditions to use based on the first factor.

[0844] The first condition may be one or a combination of the following.

[0845] Power level

[0846] The first condition may include a satisfied power level, i.e., a threshold for the satisfied power level. For example, if at least the condition for the power level is satisfied, the first condition is satisfied. The power level may include any one or more of the following embodiments. There may be one or more thresholds for (determining whether the) power level is satisfied. The power level may be determined by a threshold. The threshold for the power level may be configured by the network or derived by the UE. The threshold for the power level may be determined based on the following embodiments and / or (selected) RA resources / configurations. The threshold for the power level may be indicated or configured by the NW. Alternatively, the threshold for the power level may be determined by the UE. Alternatively, the threshold for the power level may be fixed.

[0847] The threshold may be derived based on the peak transmit (TX) power of the UE. Alternatively and / or additionally, the threshold may be derived based on the number of repetitions of a transmission (e.g., Msg1, preamble, MSGA, Msg3, or UL transmission of an RA procedure) to be transmitted by the UE. Alternatively and / or additionally, the threshold may be derived based on the first factor.

[0848] In one or more embodiments or instances, the power level may be as described above (e.g., for the first factor specified above).

[0849] For example, the first condition may include that the received power is equal to or greater than a threshold.

[0850] For example, the first condition may include that the path loss is equal to or less than a threshold.

[0851] For example, the first condition may include that the expected / derived / determined transmit power of the UE is equal to or greater than a threshold.

[0852] For example, the first condition may include that the expected / derived / determined transmit power of the UE is equal to or greater than a threshold.

[0853] For example, the first condition may include that the maximum UE transmission power is equal to or greater than a threshold. Alternatively, the first condition may include that the maximum UE transmission power is equal to or less than a threshold.

[0854] For example, the first condition may include that the amount of the battery power / storage power / available power of the UE is equal to or greater than a threshold.

[0855] For example, the first condition may include that the UE transmission power is equal to or greater than a predefined / (pre-)configured / indicated power. For example, the first condition may include a value equal to or greater than a predefined / (pre-)configured / indicated power. The value may be derived / determined based on the expected / derived / determined / maximum UE transmission power and the number of repetitions, such as the value of "expected / derived / determined / maximum UE transmission power" multiplied by the "number of repetitions".

[0856] For example, the first condition may include that the power difference is equal to or less than a threshold or a value. The value may be derived / determined based on the expected / derived / determined / maximum UE transmission power and the number of repetitions, such as the value of "expected / derived / determined / maximum UE transmission power" multiplied by the "number of repetitions".

[0857] For example, the first condition may include that the power difference is equal to or greater than a threshold or a value. The value may be derived / determined based on the expected / derived / determined / maximum UE transmission power and the number of repetitions, such as the value of "expected / derived / determined / maximum UE transmission power" multiplied by the "number of repetitions".

[0858] For example, the first condition may include that the power difference is equal to or less than a threshold or a value. The value may be derived / determined based on the expected / derived / determined / maximum UE transmission power and the number of repetitions, such as the value of "expected / derived / determined / maximum UE transmission power" multiplied by the "number of repetitions".

[0859] UE group

[0860] The first condition may include receiving or indicating in the NW signaling information related to the UE group (ID) of the UE or the ID of the UE (as described above). The NW signaling may indicate and / or include the group ID of the UE and / or the ID of the UE. The information may be the UE group (ID) of the UE or a part of the ID of the UE. For example, (at least) if the UE group (ID) of the UE is received or indicated in the NW signaling, the first condition is satisfied (as described above). (At least) if the UE group (ID) of the UE satisfies a formula, the first condition is satisfied. The formula is predefined or (pre-)configured by the NW or the UE. The UE may determine the UE group (ID) of the UE based on a first factor.

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

[0862] Multiple UEs can be assigned to or associated with different UE groups based on UE type, UE ID, and / or location. More details can be as described above (e.g., for the first factor specified above).

[0863] Appropriate configuration

[0864] The first condition can include that a (suitable) configuration is received, available, and / or valid. For example, (at least) if a (suitable) configuration is received, available, and / or valid, the first condition is met. (At least) if the corresponding configuration for the first factor is received, available, and / or valid, the first condition is met. (At least) if the configuration related to the first factor is received, available, and / or valid, the first condition is met. (At least) if a configuration specific to one of the first factors is selected, the first condition is met. The configuration can be associated with the first factor. The configuration can be different based on the first factor. A UE can determine whether the configuration is suitable based on the first factor. The configuration can include any one or more of the configurations described above.

[0865] Time offset / delay

[0866] The first condition can include: after a first duration or current timing (e.g., when the UE receives NW signaling, determines to initiate an RA process and / or checks the first condition, when the RA process is pending or suspended) after the first duration. For example, (at least) if after a first duration or current timing after the first duration, the first condition is met. The first duration can be a time offset and / or a time delay. The first duration can be represented or counted by a first timer. The first duration can be the duration when the first timer is running. (At least) if the first timer expires, the first condition is met. The (maximum) value of the first duration can be configured, predefined, and / or provided by the NW (as described above) via NW signaling. The value of the first duration can be selected, derived, and / or calculated by the UE (e.g., between 0 and the maximum value) (randomly). A UE can determine the first duration based on the first factor.

[0867] The first duration can be used to delay (initiate, trigger, continue, and / or resume) the RA process. Alternatively and / or additionally, the first duration can be used to delay the RA resource selection process (or RA preamble transmission process or MSGA transmission process) (the initial or first time or first step) of performing the RA process. When an NW signaling is received, the RA process is triggered or pending, (one or more) first conditions are met, the UE determines to initiate the RA process, the UE initiates (or triggers or continues or resumes) the RA process, performs (one or more) RA resource selections (steps), and / or performs the transmission of (MSGA / msg1 / msg3), the first duration and / or the first timer can be started.

[0868] Prohibited timer

[0869] The first condition can include: after the second duration or the current timing (e.g., when the UE receives an NW signaling, determines to initiate the RA process and / or checks the first condition, when the RA process is pending or suspended) after the second duration. The second duration can be counted or represented by the second timer. For example, (at least) if the second timer is not running, the first condition is met. (At least) if the second timer expires, the first condition is met. The second timer can be a time window. The (maximum) value of the second duration can be configured, predefined, provided, and / or enabled by the NW (as described above) via NW signaling. The value of the second duration can be selected, derived, and / or calculated by the UE (e.g., between 0 and the maximum value) randomly. The UE can determine the second duration based on the first factor.

[0870] The second duration can be used to prohibit the UE from initiating and / or performing the RA process. The second duration can be used to prohibit the UE from initiating and / or performing the RA process after completing another RA process or within a short time (or immediately) before the RA process. When or in response to triggering the RA process, meeting (one or more) first conditions, the UE determines to initiate the RA process, performs (one or more) RA resource selections (steps), performs the data or signal transmission of (MSGA / msg3 / msg5), (is regarded as) (successfully) completing the RA process, the second duration can be started. The data or signal transmission can use the PUSCH resource of the MSGA provided by the NW and / or the UL grant. The data or signal transmission can be performed during the RA process or after completing the RA process.

[0871] Alternatively and / or additionally, the UE may set a timestamp. The first condition may include: the elapsed time or the current timing (e.g., when the UE receives NW signaling, determines to initiate the RA process and / or checks the first condition, when the RA process is pending or suspended) is after the timestamp. Or, the first condition may include: the elapsed time plus a second duration or the current timing (e.g., when the UE receives NW signaling, determines to initiate the RA process and / or checks the first condition, when the RA process is pending or suspended) is after the timestamp plus the second duration. The first condition is satisfied (at least) after the timestamp. The timestamp may be configured, predefined, provided, and / or enabled by the NW (as described above), e.g., via NW signaling. The timestamp may be selected, derived, and / or calculated by the UE (randomly). The timestamp may be set by the value of a second timer. The timestamp may be set by the remaining time of a second timer. The timestamp may be set by the time or date (e.g., epoch time) that triggers the RA process, satisfies the (one or more) first conditions, the UE determines to initiate the RA process, performs the (one or more) RA resource selection (steps), performs data or signal transmission of (MSGA / msg3 / msg5), and is (considered to be) (successfully) completed the RA process.

[0872] Alternatively and / or additionally, the UE may store the value (or remaining time) of the second duration or the timestamp, e.g., based on the power level. When, if, or in response to power-off, entering the idle state, and / or resetting the MAC, the UE may not clear the value (or remaining time) of the second duration or the timestamp. The UE may retrieve and / or restore the value (or remaining time) of the second duration or the timestamp, e.g., based on the power level.

[0873] The RA resource selection (step) may be (or include) the selection of one or more of the following:

[0874] - (Initial) (UL) BWP (for ambient IoT);

[0875] - RA resource / configuration (group) (for ambient IoT);

[0876] - RA type (for ambient IoT);

[0877] - RA preamble (group and / or index) (for ambient IoT);

[0878] - RACH occasion (for ambient IoT);

[0879] - PUSCH occasion (for ambient IoT); and / or

[0880] - PDRCH occasion (for ambient IoT).

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

[0882] In response to receiving the signaling, the UE can trigger / perform the process and / or the following transmission. During the process, the UE can transmit a first transmission to the NW / intermediate node. The NW / intermediate node can 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 can receive the second transmission from the NW / intermediate node. In response to receiving the second transmission, the UE can transmit a third transmission to the NW / intermediate node. In response to receiving the second transmission, the UE can not transmit a third transmission to the NW / intermediate node. The NW / intermediate node can transmit a fourth transmission to the UE in response to the reception of the third transmission. The NW / intermediate node can 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 can or can not receive the fourth transmission from the NW / intermediate node. In response to receiving the fourth transmission, the UE can transmit a fifth transmission to the NW / intermediate node.

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

[0884] The second transmission in the process can be a response and / or confirmation of the first transmission. The second transmission can indicate, identify, and / or correspond to the first transmission. The second transmission can provide resources for subsequent D2R transmissions, such as the third transmission.

[0885] The third transmission in the process can be / include information of a device / UE ID, a report, auxiliary information, D2R data, and / or information from the UE.

[0886] The fourth transmission in the process can be a response, confirmation, DL / R2D command, R2D data, and / or scheduling of the third transmission. The fourth transmission can indicate, identify, and / or correspond to the third transmission. The fourth transmission can provide resources for subsequent D2R transmissions. The fourth transmission can indicate, notify, and / or allow the fifth transmission.

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

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

[0889] Various examples and embodiments of the present invention are described below.

[0890] Reference Figure 13 , using this and other concepts, systems, and methods of the present invention, a method 1040 for a UE in a wireless communication system includes: receiving signaling from a network (step 1042); and in response to receiving the signaling, determining whether a first condition is satisfied, where: if or when the first condition is satisfied, initiating an RA process, or if the first condition is not satisfied, not initiating an RA process (step 1044).

[0891] In various embodiments, the signaling instructs the UE to trigger an RA process and / or perform a UL transmission.

[0892] In various embodiments, the first condition is based on the power level of the UE.

[0893] In various embodiments, the first condition is based on an indication in the signaling and / or the UE group ID of the UE.

[0894] In various embodiments, the first condition is based on the RA configuration for the UE.

[0895] In various embodiments, the first condition is based on a duration and / or a timer.

[0896] Return reference Figure 3 and Figure 4 , in one or more embodiments, from the perspective of a UE in a wireless communication system, a device 300 includes program code 312 stored in a memory 310 of a transmitter. A CPU 308 can execute the program code 312 to: (i) receive signaling from a network; and (ii) in response to receiving the signaling, determine whether a first condition is satisfied, where: if or when the first condition is satisfied, initiate an RA process, or if the first condition is not satisfied, not initiate an RA process. In addition, the CPU 308 can execute the program code 312 to perform all the described actions, steps, and methods described above, below, or elsewhere herein.

[0897] Reference Figure 14, using this and other aspects, 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 is for more than one UE (step 1052); and in response to receiving the first signaling, triggering the random access procedure and performing a first transmission of the random access procedure based on a first resource or a first configuration provided in the first signaling (step 1054).

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

[0899] In various embodiments, the first signaling indicates the device ID of the UE, and / or the first signaling indicates the group ID of the UE.

[0900] In various embodiments, the first resource includes at least a first frequency resource and / or a PDRCH occasion. In various embodiments, the first resource includes at least a first frequency resource and / or an access occasion.

[0901] In various embodiments, the first resource is determined based on a first configuration and / or a pre-configuration.

[0902] In various embodiments, the first configuration is related to the random access procedure, and / or the first configuration is associated with the UE and / or the UE group of the UE.

[0903] In various embodiments, the first configuration provides any one of a bandwidth part, one or more access resources, one or more access preambles, one or more PDRCH occasions, and / or one or more frequency resources for D2R transmission (e.g., the first transmission).

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

[0905] In various embodiments, the first transmission is transmitted to the reader during the random access procedure.

[0906] In various embodiments, the reader is any one of a network node, an intermediate node, or another UE. In various embodiments, the another UE is a non-ambient IoT UE. In various embodiments, the another UE is a legacy UE.

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

[0908] In various embodiments, more than one UE is an ambient IoT UE or an ambient IoT device.

[0909] Return reference Figure 3 and Figure 4, in one or more embodiments, from the perspective of a UE in a wireless communication system, the apparatus 300 includes program code 312 stored in the memory 310 of the transmitter. The CPU 308 may execute the program code 312 to: (i) receive first signaling that triggers a random access procedure, where the first signaling is for more than one UE / device; and (ii) in response to receiving the first signaling, trigger the random access procedure and perform a first transmission of the random access procedure based on a first resource or a first configuration provided in the first signaling. Additionally, the CPU 308 may execute the program code 312 to perform all the described actions, steps, and methods described above, below, or elsewhere herein.

[0910] Reference Figure 15 , using this and other aspects, systems, and methods of the present invention, a method 1060 for a reader in a wireless communication system includes: transmitting first signaling that triggers a random access procedure, where the first signaling is for more than one UE (step 1062); and receiving a first transmission of the random access procedure from the UE, where the first transmission is triggered in response to the first signaling and where the first transmission is performed or received based on a first resource or a first configuration provided in the first signaling (step 1064).

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

[0912] In various embodiments, the first signaling indicates the device ID of the UE, and / or the first signaling indicates the group ID of the UE.

[0913] In various embodiments, the first resource includes at least a first frequency resource and / or a PDRCH occasion. In various embodiments, the first resource includes at least a first frequency resource and / or an access occasion.

[0914] In various embodiments, the first resource is determined based on a first configuration and / or a pre-configuration.

[0915] In various embodiments, the first configuration is related to the random access procedure, and / or the first configuration is associated with the UE and / or the UE group of the UE.

[0916] In various embodiments, the first configuration provides any one of a bandwidth part for D2R transmission, one or more access resources, one or more access preambles, one or more PDRCH occasions, and / or one or more frequency resources.

[0917] In various embodiments, the reader is any one of a network node, an intermediate node, or another UE. In various embodiments, the other UE is a non-ambient IoT UE.

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

[0919] In various embodiments, more than one UE is an ambient IoT UE or an ambient IoT device.

[0920] Return reference Figure 3 and Figure 4 and, in one or more embodiments, from the perspective of a reader in a wireless communication system, the apparatus 300 includes program code 312 stored in a memory 310 of a transmitter. The CPU 308 may execute the program code 312 to: (i) transmit first signaling that triggers a random access procedure, where the first signaling is for more than one UE; and (ii) receive a first transmission of the random access procedure from the UE, where the first transmission is triggered in response to the first signaling and where the first transmission is performed or received based on a first resource or a first configuration provided in the first signaling. Additionally, the CPU 308 may execute the program code 312 to perform all of the described actions, steps, and methods described above, below, or elsewhere herein.

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

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

[0923] The 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 will 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 different ways. For example, any number of the aspects set forth herein can be used to implement an apparatus or practice a method. In addition, this apparatus 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 a time-hopping sequence. In some aspects, parallel channels can be established based on pulse repetition frequency, pulse position or offset, and a time-hopping sequence.

[0924] Those skilled 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.

[0925] Those of ordinary skill in the art will further understand 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 the interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps have generally been described above in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the particular application and the design constraints imposed on the overall system. Those skilled 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.

[0926] In addition, 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"), an access terminal, or an 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, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0927] 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 a sample order and are not intended to be limited to the specific order or hierarchy presented.

[0928] 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, such as those comprising 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 the alternative, the processor and the storage medium can reside as discrete components in a user device. Additionally, in some aspects, any suitable computer program product can include a computer-readable medium that includes code associated with one or more of the aspects of the present disclosure. In some aspects, the computer program product can include packaging material.

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

Claims

1. A method for processing resources or configuration of a user device of an ambient Internet of Things, characterized in that include: receiving first signaling triggering a random access procedure, wherein the first signaling is for more than one user equipment; as well as In response to receiving the first signaling, the random access procedure is triggered and a first transmission of the random access procedure is performed based on a first resource or a first configuration provided in the first signaling.

2. The method according to claim 1, characterized in that The first signaling is paging for the ambient Internet of Things, or the first signaling is a paging message.

3. The method according to claim 1, characterized in that The first signaling indicates a device identifier of the user equipment, or the first signaling indicates a group identifier of the user equipment.

4. The method according to claim 1, characterized in that: The first resource comprises at least a first frequency resource or a physical device-to-reader channel opportunity, or the first resource comprises at least the first frequency resource or an access opportunity.

5. The method according to claim 1, characterized in that The first resource is determined based on the first configuration or pre-configuration.

6. The method according to claim 1, characterized in that The first configuration is related to the random access procedure, or the first configuration is associated with the user equipment or a user equipment group of the user equipment.

7. The method according to claim 1, characterized in that The first configuration provides any of a bandwidth portion, one or more access resources, one or more access preambles, one or more physical device-to-reader channel opportunities, or one or more frequency resources for device-to-reader transmissions.

8. The method according to claim 1, characterized in that The first signaling is transmitted via a reader, or the first transmission is transmitted to the reader during the random access procedure.

9. The method according to claim 8, characterized in that The reader is any one of a network node, an intermediate node or another user equipment.

10. The method according to claim 1, characterized in that The user equipment is an environmental Internet of Things user equipment or an environmental Internet of Things device.

11. A method for processing a reader of resources or configurations of an ambient Internet of Things, characterized in that, include: transmitting a first signaling triggering a random access procedure, wherein the first signaling is for more than one user equipment; as well as A first transmission of the random access procedure is received from a user equipment, wherein the first transmission is triggered in response to the first signaling, and wherein the first transmission is performed or received based on a first resource or a first configuration provided in the first signaling.

12. The method according to claim 11, characterized in that The first signaling is paging for the ambient Internet of Things, or the first signaling is a paging message.

13. The method according to claim 11, characterized in that The first signaling indicates a device identifier of the user equipment, or the first signaling indicates a group identifier of the user equipment.

14. The method according to claim 11, characterized in that The first resource comprises at least a first frequency resource or a physical device-to-reader channel opportunity, or the first resource comprises at least the first frequency resource or an access opportunity.

15. The method according to claim 11, characterized in that The first resource is determined based on the first configuration or pre-configuration.

16. The method according to claim 11, characterized in that The first configuration is related to the random access procedure, or the first configuration is associated with the user equipment or a user equipment group of the user equipment.

17. The method according to claim 11, characterized in that The first configuration provides any of a bandwidth portion, one or more access resources, one or more access preambles, one or more physical device-to-reader channel opportunities, or one or more frequency resources for device-to-reader transmissions.

18. The method according to claim 11, characterized in that The reader is any one of a network node, an intermediate node or another user equipment.

19. The method according to claim 11, characterized in that The user equipment is an environmental Internet of Things user equipment or an environmental Internet of Things device.

20. A user device for processing resources or configurations of an environmental Internet of Things, characterized in that: include: Memory; as well as a processor operably connected 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 is for more than one user equipment; as well as In response to receiving the first signaling, the random access procedure is triggered and a first transmission of the random access procedure is performed based on a first resource or a first configuration provided in the first signaling.

Images