Random access procedure for ambient IoT devices

Abstract

Embodiments herein describe methods, systems, and apparatuses to enhance random access procedures Internet of Things (IoT) devices. An ambient IoT device may receive, from a reader, a synchronization signal block (SSB). The ambient IoT device may send the reader a Physical Random Access Channel (PRACH) transmission based on its device category type. The PRACH preamble, the RACH occasion used, and the timing of the PRACH transmission may be based on the device category type.

Description

RANDOM ACCESS PROCEDURE FOR AMBIENT IOT DEVICESTECHNICAL FIELD

[0001] This application relates generally to wireless communication systems, including random access procedures based on a device category type of an ambient powered device.BACKGROUND

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless communication device. Wireless communication system standards and protocols can include, for example. 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard for Wireless Local Area Networks (WLAN) (commonly known to industry groups as Wi-Fi®).

[0003] As contemplated by the 3GPP, different wireless communication systems' standards and protocols can use various radio access networks (RANs) for communicating between a base station of the RAN (which may also sometimes be referred to generally as a RAN node, a network node, or simply a node) and a wireless communication device known as a user equipment (UE). 3GPP RANs can include, for example, Global System for Mobile communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN). Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next-Generation Radio Access Network (NG-RAN).

[0004] Each RAN may use one or more radio access technologies (RATs) to perform communication between the base station and the UE. For example, the GERAN implements GSM and / or EDGE RAT, the UTRAN implements Universal Mobile Telecommunication System (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT (sometimes simply referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to herein as 5G RAT, 5G NR RAT, or simply NR). In certain deployments, the E-UTRAN may also implement NR RAT. In certain deployments, NG-RAN may also implement LTE RAT.

[0005] A base station used by a RAN may correspond to that RAN. One example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E- UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB). One example of an NG-RAN base station is a next generation Node B (also sometimes referred to as a g Node B or gNB).

[0006] A RAN provides its communication services with external entities through its connection to a core network (CN). For example, E-UTRAN may utilize an Evolved Packet Core (EPC) while NG-RAN may utilize a 5G Core Network (5GC).BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0007] To easily identify the discussion of any particular element or act. the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

[0008] FIG. 1 illustrates a table of design targets for an example set of loT device types.

[0009] FIG. 2 illustrates a signaling diagram of a RACH procedure in accordance with some embodiments.

[0010] FIG. 3 illustrates preamble subset to RO mapping where multiple device types can use one RO in accordance with some embodiments.

[0011] FIG. 4 illustrates preamble subset to RO mapping where multiple device types can be assigned dedicated ROs in accordance with some embodiments.

[0012] FIG. 5 illustrates preamble subset to RO mapping sequence where the device types are mapped to a same symbol on different frequency resources in accordance with some embodiments.

[0013] FIG. 6 illustrates preamble subset to RO mapping sequence where different device types are mapped across multiple symbols in accordance with some embodiments.

[0014] FIG. 7 illustrates a transmission timeline with an association duration in accordance with some embodiments.

[0015] FIG. 8 illustrates a transmission timeline with overlapping association durations for different ambient loT device ty pes in accordance with some embodiments.

[0016] FIG. 9 illustrates a transmission timeline with non-overlapping association durations for different ambient loT device types in accordance with some embodiments.

[0017] FIG. 10 illustrates a method for an ambient loT device in accordance with some embodiments.

[0018] FIG. 11 illustrates a method for a reader (e.g., base station) in accordance with some embodiments.

[0019] FIG. 12 illustrates an example architecture of a wireless communication system, according to embodiments disclosed herein.

[0020] FIG. 13 illustrates a system for performing signaling between a wireless device and a network device, according to embodiments disclosed herein.DETAILED DESCRIPTION

[0021] Various embodiments are described with regard to a UE. However, reference to a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to exchange information and data with the network. Therefore, the UE as described herein is used to represent any appropriate electronic component.

[0022] Additionally, embodiments herein are described with regard to Internet of Things (loT) devices. Reference to an loT device is merely provided for illustrative purposes, and the embodiments herein may be utilized with any device that has the capability to collect and exchange data. loT devices may be embedded with sensors, software, and network connectivity, allowing them to communicate with other devices and systems. loT devices can vary in size, complexity, and functionality. They can range from small, simple devices such as temperature sensors and smart home appliances to more complex devices like industrial machinery and autonomous vehicles.

[0023] Some loT devices include ambient loT devices. An ambient loT device is a device that is able to harvest energy from ambient sources. For example, some ambient loT devices may use radio frequency (RF) waves for power. To power such devices using RF, embodiments herein provide enhancements to a wireless communication system framework to introduce a new category of device(s) that is able to harvest energy from ambient sources. An ambient loT device may be referred to as an RF powered device. An ambient loT device may also be a UE device.

[0024] There may be multiple types of ambient loT devices that the wireless communication system may support. For instance, in terms of energy storage, somedevices may be batery -less devices with no energy storage capability at all, and completely dependent on the availability’ of an external source of energy. Some devices may include limited energy storage capability that do not need to be replaced or recharged manually, but can be charged by harvesting energy from ambient sources. In some embodiments, device categorization may be based on characteristics corresponding to a device (e.g. energy source, energy storage capability, passive / active transmission, etc.).

[0025] For example, FIG. 1 illustrates a table of design targets 102 for an example set of loT device types. As shown, some embodiments may include loT device type A, loT device type B and loT device type C. loT device type A may include no energy storage, harvests energy from ambient sources, and has no independent signal generation, but only backs catt ering transmission. loT device ty pe B may have energy' storage and may harvest energy from ambient sources, but does not perform independent signal generation, i.e. only backs cattering transmission. loT device type B's use of stored energy can include amplification for backscattered signals. loT device type C may have energy storage from harvesting ambient sources, and has independent signal generation (e.g., active RF component for transmission). Common aspects for all these device categories is that they have may have very low complexity and can rely on the harvested energy for transmission and reception. From a wireless communication system perspective, RF energy harvesting may be considered. For example, the devices may utilize the energy’ of the incoming signals from other nodes in the system.

[0026] Other aspects of the design targets 102 for example loT devices is shown in FIG. 1. For example, there may be specific targets for power consumption, coverage, message size, device density’, device complexity7, data-rate, positioning accuracy, and device mobility. These illustrate example design targets 102. Design targets 102 may vary based on actual implantation.

[0027] For example, in some embodiments, ambient loT devices may be categorized into different groups: lower-category loT devices, and higher-category loT devices. The lower- category may include devices between type A and type B from the previously described categorization. For example, the lower-category devices may have about 1 pW peak power consumption, energy storage but neither downlink nor uplink amplification in the device, and initial sampling frequency offset (SFO) can be up to thousands of ppm. Further, the device's uplink transmission may be backscattered on a carrier wave provided externally.

[0028] In some embodiments, higher-category devices may include devices between ty pe B and ty pe C from the previously described categorization. For example, the higher- category devices may have less than or equal to a few hundred pW peak power consumption. Further, the higher-category devices may have energy storage and both downlink and / or uplink amplification. The initial SFO may be up to thousands of ppm for the higher-category devices. The higher-category device's uplink transmission may be generated internally by the device, or be backscattered on a carrier wave provided externally.

[0029] Both lower-category loT device and higher category’ loT device categories may have very low complexity’. Further, the loT devices in both categories can rely on the harvested energy for transmission and reception. These qualities may facilitate mass deployment and increased scalability'. However, the lower complexity of the loT devices and the number of devices may lead to issues with random access procedures.

[0030] Embodiments herein consider the random access procedure for ambient loT devices. Issues for random access procedures may be a result of the large number of ambient loT devices that may want to access a channel, and that each ambient loT device may have limited power and / or limited duration within which it can respond to a received synchronization signal block (SSB).

[0031] Due to the limited power, the ambient loT device may need to respond (via Random-access channel (RACH)) to the received SSB without much gap between the response and the SSB. Otherwise, the network node may need to continuously transmit carrier wave to provide energy to devices so that they can send a response corresponding to the received SSB. A carrier wave may be used purely for energizing devices for the response. In some embodiments, the devices may partially use the energy from any downlink signal (e.g., SSB). In some embodiments, the SSB may contain one or more of signals including PSS, SSS and PBCH. Depending up on the device category, the content of SSB may vary’.

[0032] Embodiments herein provide solutions for following aspects considering the different device categories. Some embodiments, consider the Physical Random Access Channel (PRACH) preamble distribution. For example, embodiments describe how the PRACH preambles may be distributed in the time and frequency domains, and how the preambles may be associated with different device categories. Further, someembodiments describe the preamble to RACH occasion (RO) mapping, RO timefrequency mapping sequence, and association of SSB to the RO.

[0033] FIG. 2 illustrates a signaling diagram 208 of a RACH procedure in accordance with some embodiments. As shown, the network node 204 may transmit an SSB 206. The loT device 202 may receive the SSB 206. The SSB 206 may enable the loT device 202 to synchronize its timing with the network, identify the serving cell, and acquire key parameters for accessing the network, including RACH configurations.

[0034] The loT device 202 may transmit a PRACH preamble 210 based on the SSB 206. The network node 204 may receive the PRACH preamble 210 and transmit a random Access response 212 to the loT device 202. The loT device 202 and the network node 204 may proceed with a contention resolution procedure 214.

[0035] The RACH procedure may be enhanced for ambient loT devices. These enhancements may reduce contention between ambient loT devices. For ambient loT device, multiple subsets of PRACH preambles may be introduced, where each subset may be associated with a different category of ambient loT device type. For instance lower-category devices may use preambles from a first subset of PRACH preambles, and higher-category use preambles from a second subset of PRACH preambles

[0036] The network node 204 can identify the device category type of the loT device 202 based on the received preamble. For instance, if the loT device 202 sends a preamble from the second set of PRACH preambles, the network node 204 may determine that loT device 202 is a higher-category device. The network node 204 may use the device type to improve future transmissions with the loT device 202.

[0037] Further, ambient loT devices are not expected to use the PRACH preamble from the subset that is not associated with its device type. For the initial access for contention based random access, the loT device 202 may randomly select a preamble that belongs to the corresponding subset for its type. For a given subset of preambles, a certain type of devices may be allowed while other device types use other subsets thereby reducing contention.

[0038] Single indexing may split the PRACH preambles into multiple subsets. The PRACH preambles may be split into a number of subsets equal to the number of loT device types. For example, in some embodiments, the PRACH preambles may be split into three subsets corresponding to ambient IOT device type A, ambient IOT device type B, and ambient IOT device type C. For ambient loT device type A, a first subset ofPRACH preamble index range may be from index 0 to L. For ambient loT device type B, a second subset of PRACH preamble index range may be from L+l to M. For ambient loT device type C, a third subset of PRACH preamble index range is from M+l to N. A device maybe pre-configured with the entire range of PRACH preamble index, and also the applicable range for its type.

[0039] Additional or fewer preamble subsets may be used based on the number of supported device types. In some embodiments, the PRACH preambles may be split into two subsets corresponding to lower-category devices and higher-category devices. For instance, for a lower-category ambient loT device type, a first subset of PRACH preamble index range may be from index 0 to L. For a higher-category ambient loT device type, a second subset of PRACH preamble index range may be from L+l to M.

[0040] Preamble subsets may be mapped to one or more ROs. For example, FIG. 3 illustrates preamble subset to RO mapping where multiple device types can use one RO 308 in accordance with some embodiments. For ambient loT devices, a same RO 308 can be used for PRACH preamble transmission from device to a reader (e.g. base station) independent of the subset of preamble. In such embodiments, even if two ambient loT devices are assigned to different preamble subsets (e.g., higher-category device preamble subset, and lower-category device preamble subset), both can send their PRACH preamble transmission on the same RO 308.

[0041] In the illustrated embodiment, if two different ambient loT device types (ambient loT device type A 304 and ambient loT device type B 306) receive the same SSB 302 and that SSB 302 is associated with one RO 308, then both the device types can possibly transmit on the same RO 308 with their respective preambles selected from the corresponding preamble subset applicable for each device type. For instance, ambient loT device type A 304 and ambient loT device type B 306 both receive SSB 302. In the illustrated embodiment, SSB 302 is associated with RO 308. In this embodiment it does not matter the device ty pe, both ambient loT device ty pe A 304 and ambient loT device type B 306 use the same RO 308 based on the SSB 302.

[0042] Within the RO 308, the two ambient loT devices may' use their own respective preambles. For instance, ambient loT device type A 304 may use a random preamble from a first subset of PRACH preambles with an index range may be from index 0 to L. Similarly, ambient loT device type B 306 may use a random preamble from a second subset of PRACH preambles with an index range may be from index L+l to M. Whilethe illustrated embodiment describes the preamble subset to RO mapping for type A and type B. the devices may instead be categorized into a higher-category device type and a lower-category device type.

[0043] FIG. 4 illustrates preamble subset to RO mapping where multiple device types can be assigned dedicated ROs in accordance with some embodiments. For ambient loT devices, different ROs may be used for PRACH preamble transmission from device to reader (e.g. base station) depending up on the subset of preamble corresponding to the ambient loT device ty pe.

[0044] If two different ambient loT device types (e.g., ambient loT device type A 404 and ambient loT device type B 406) receive the same SSB 402 and that SSB 402 is associated with at least two ROs (first RO 408 and second RO 410), the different ROs may be used for different device types. The first RO 408 corresponds to one device type / one preamble subset (e.g.. ambient loT device type A 404). and the second RO 410 corresponds to another device type / other preamble subset (e.g., ambient loT device type B 406). Additional ROs may be used to support additional device types.

[0045] As shown, ambient loT device type A 404 may receive SSB 402 and use the first RO 408 for PRACH preamble transmission. Ambient loT device type B 406 may receive SSB 402 and use the second RO 410 for PRACH preamble transmission. While the illustrated embodiment describes the preamble subset to RO mapping for type A and type B. the devices may instead be categorized into a higher-category device type and a lower-category device type. Contention may be reduced because the different device ty pes use dedicated ROs.

[0046] FIG. 5 illustrates preamble subset to RO mapping sequence where the device types are mapped to a same symbol on different frequency resources in accordance with some embodiments. For ambient loT devices, when different ROs are used for PRACH preamble transmission from device to reader (e.g. base station) depending on the subset of preamble / device type, then the RO mapping sequence may be frequency first and time second within a period.

[0047] For example, in the illustrated embodiment, three devices of different types (e.g.. device type A 508, device type B 506. device type C 504) receive a same SSB 502. The SSB 502 may be associated with multiple ROs (e.g., RO1, RO2, RO3, RO4, RO5, RO6). The illustrated RO mapping sequence may provide each of the device ty pes with a first RO on the same symbol on a different frequency. If additional RO are needed forone or more of the device ty pes, the sequence mapping may provide device ty pes new ROs on the same frequencies on a next symbol.

[0048] For instance, as illustrated, device type A 508 is mapped to RO1 on symbol N and frequency resource 1. Device type B 506 is mapped to RO2 on symbol N and frequency resource 2. Device type C is mapped to RO3 on symbol N and frequency resource 3. For each of the device types the same sequence may be followed on symbol N+l and thereafter within a period. For example, device ty pe A 508 is mapped to RO4 on symbol N+l and frequency resource 1. Device ty pe B 506 is mapped to RO5 on symbol N+l and frequency resource 2. Device type C is mapped to RO6 on symbol N+l and frequency resource 3.

[0049] Additional or fewer ROs for each symbol may be used based on the number of device types. For instance, the devices may instead be categorized into a higher-category device type and a lower-category device type. Each of the devices may have a first RO on a same symbol at a different frequency. If multiple ROs are needed for a device type, the device ty pe may use the next symbol on the same frequency. This may provide an equal prioritization, in terms of latency, among the different device types.

[0050] FIG. 6 illustrates preamble subset to RO mapping sequence where different device ty pes are mapped across multiple symbols in accordance with some embodiments. For ambient loT devices, when different ROs are used for PRACH preamble transmission from device to reader (e.g. base station) depending on the subset of preamble which is dependent on the device type, then the RO mapping sequence may be time first and frequency second within a period.

[0051] For instance, each device type may be assigned a specific time (e.g.. symbol). Within each symbol, the device type that corresponds to that symbol may use one or more frequency resources for a desired number of ROs. This may allow device types to be prioritized in terms of latency.

[0052] In the illustrated embodiment, device type A 608, device type B 606, and device ty pe C 604 each receive the same SSB 602. The SSB 602 may be associated with multiple ROs (e g., RO1, RO2, RO3, RO4, RO5, RO6). The illustrated RO mapping sequence may associate specific symbols for ROs of different device types, and within each symbol, a device type may use one or more frequency resources for multiple ROs.

[0053] For instance, device ty pe A 608 may be mapped to RO1 on symbol N and frequency resource 1. Device type B 606 may be mapped to RO2 on symbol N+l andfrequency resource 1. Device type C 604 may be mapped to RO3 on symbol N+2 and frequency resource 1. The same sequence may be followed on frequency resource 2 and thereafter within a period. For example, device type A 608 may be mapped to RO4 on symbol N and frequency resource 2. Device type B 606 may be mapped to RO5 on symbol N+l and frequency resource 2. Device type C 604 may be mapped to RO6 on symbol N+2 and frequency resource 2.

[0054] Additional or fewer ROs for each symbol may be used based on the number of device types. For instance, the devices may instead be categorized into a higher-category device type and a lower-category device type. Each of the devices may have their ROs assigned at different symbols. If multiple ROs are needed for a device type, the device type may use the next frequency resource on an assigned symbol.

[0055] This may allow for prioritization, in terms of latency, across the different device types. For lower-category ambient loT devices (e.g., device type A), it may be desirable to minimize the gap between the SSB 602 and the RO since they may be more dependent on the carrier wave. Accordingly, lower-category devices may be assigned to the first symbol of the set of symbols.

[0056] In some embodiments, an association duration may be used to mark a maximum time duration after the SSB for which the ROs corresponding to the SSB are valid. For example. FIG. 7 illustrates a transmission timeline 710 with an association duration 704 in accordance with some embodiments. For ambient loT devices, an association duration 704 may be introduced for mapping the SSB 702 to corresponding RO(s) (e.g., valid ROs 706).

[0057] The association duration 704 may be the maximum time duration ' X ' during which the corresponding ROs are valid for PRACH preamble transmission corresponding to the SSB 702. The association duration 704 may start from the symbol after a given SSB beam (e.g., SSB 702) is received and ends at X symbols after the given SSB beam is received.

[0058] Any RO (e.g., invalid ROs 708) after the association duration 704 for a SSB beam may not be applicable for PRACH transmission for a device that received the corresponding SSB beams. If the device fails to access the valid ROs 706 in the association duration 704, then the device may attempt to receive a new SSB and send a PRACH transmission using ROs corresponding to the new SSB during the association duration of the new SSB. In some embodiments, mapping and mapping sequencesdescribed previously may be applicable to valid ROs 706 within the association duration 704.

[0059] In some embodiments, the association duration may be based on the device category type. For example, FIG. 8 illustrates a transmission timeline 802 with overlapping association durations for different ambient loT device types in accordance with some embodiments. For ambient loT devices, the association duration may be configured differently for different device category types corresponding to a given SSB beam.

[0060] For example, multiple devices from different device category' types may receive an SSB 804. In the illustrated embodiment, a first association duration 806 (e.g. XI) may be configured for device type A. The first association duration 806 may include the time between may start from the symbol after a given SSB beam (e g., SSB 804) is received and ends at XI symbols after the given SSB beam is received. The ROs during the first association duration 806 (e g., first set of ROs 810) are valid for both device type A and device type B.

[0061] A second association duration 808 (e.g. X2) may be configured for device type B. The second association duration 808 may include the time between may start from the symbol after a given SSB beam (e.g., SSB 804) is received and ends at X2 symbols after the given SSB beam is received. As shown, the second association duration 808 may overlap with and extend beyond the first association duration 806. The ROs that occur between the ending of the first association duration 806 and the ending of the second association duration 808 (e.g., second set of ROs 812) are invalid for device type A but valid for device type B.

[0062] Accordingly, in the illustrated embodiment, device type B may send a PRACH transmission on the first set of ROs 810 or on the second set of ROs 812. Device type A may send a PRACH transmission on the first set of ROs 810, but not on the second set of ROs 812. While the illustrated embodiments describe association durations with respect to type A and type B, the devices may instead be categorized into a higher-category device ty pe and a lower-category device type.

[0063] Additionally, more association durations may be configured for additional device types. For example, a third association duration may be configured for device type C. For device type B the second association duration may be length X2 which is greater than XI. An association duration for device ty pe C may be length X3 which isgreater than X2. The higher the category of device, the more relaxed the association duration may become. The more relaxed the association durations results in more opportunities, in terms of ROs, for PRACH transmission. In some embodiments, mapping and mapping sequences described previously may be applicable to ROs within the association durations.

[0064] FIG. 9 illustrates a transmission timeline 902 with non-overlapping association durations for different ambient loT device types in accordance with some embodiments. For ambient loT devices, the association position in time and / or duration (e.g., first association duration 906 and second association duration 908) may be configured differently for different device category type corresponding to a given SSB beam (e.g., SSB 904). Each of the association durations may correspond to a start time and end time and do not overlap with each other. In some embodiments, the length of each association duration may be the same. In some embodiments there may be no gap between the association durations

[0065] For example, a starting of an association duration for device type A (e.g., first association duration 906) may be LI and may end before Ll+Kl. Further, the starting of an association duration for device type B (e.g., second association duration 908) may be Ll+Kl and end is before L1+K1+K2. Additional non-overlapping association durations may be included to support additional device types. For example, the starting of an association duration for device type C may be L1+K1+K2 and end may be before L1+K1+K2+K3. While the illustrated embodiments describe association durations with respect to type A and type B. the devices may instead be categorized into a higher- category device ty pe and a lower-category device type. In some embodiments, the order of the non-overlapping association durations may be in order from lower-category7devices to higher-category devices to provide the smallest gap for lower categorydevices.

[0066] The ROs during the first association duration 906 (e.g., first set of ROs 910) are valid for SSB 904 for device type A. but invalid for device type B. Similarly, the ROs that occur between the ending of the first association duration 906 and the ending of the second association duration 908 (e.g., second set of ROs 912) are valid for SSB 904 for device type B, but invalid for device type A. Accordingly, in the illustrated embodiment, device type A may send a PRACH transmission on the first set of ROs 810. Device type B may send a PRACH transmission on the second set of ROs 812. By separating theassociation duration, a wireless communication system may reduce contention for the different device types.

[0067] FIG. 10 illustrates a method 1000 for an ambient loT device in accordance with some embodiments. The method 1000 includes receiving 1002, from a reader, a SSB. The method 1000 further includes generating 1004 a PRACH transmission. The PRACH transmission may comprise a PRACH preamble selected from a subset of PRACH preambles that correspond to a device type of the ambient loT device. The method 1000 further includes sending 1006 the PRACH transmission to the reader.

[0068] In some embodiments, the subset of PRACH preambles is different than a second subset of PRACH preambles corresponding to a second device type.

[0069] In some embodiments, the method 1000 further comprises transmitting on a same RO as a device of the second device type that received the same SSB.

[0070] In some embodiments, the method 1000 further comprises determining multiple ROs associated with the SSB; and determining which of the multiple ROs corresponds to the device type of the ambient loT device, wherein the ambient loT device sends the PRACH transmission using a RO corresponding to the device type.

[0071] In some embodiments, an RO mapping sequence for different device types is frequency first and time second within a period.

[0072] In some embodiments, an RO mapping sequence for different device types is time first and frequency second within a period.

[0073] In some embodiments, lower category devices are mapped to a first set of symbols that occurs before a second set of symbols mapped to higher category devices.

[0074] In some embodiments, the method 1000 further comprises determining an association duration corresponding to the SSB, wherein the association duration is a period of time during which ROs are valid to send the PRACH transmission for the SSB.

[0075] In some embodiments, the association duration is configured differently for difference device types.

[0076] In some embodiments, higher category devices are configured with a longer association duration than lower category devices.

[0077] In some embodiments, higher category devices are configured with a first association duration that occurs later than a second association duration for lower category devices.

[0078] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 1000. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1302 that is a UE, as described herein).

[0079] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 1000. This non-transitory computer- readable media may be, for example, a memory of a UE (such as a memory 1306 of a wireless device 1302 that is a UE, as described herein).

[0080] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry to perform one or more elements of the method 1000. This apparatus may be. for example, an apparatus of a UE (such as a wireless device 1302 that is a UE, as described herein).

[0081] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 1000. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 1302 that is a UE, as described herein).

[0082] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 1000.

[0083] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor is to cause the processor to carry out one or more elements of the method 1000. The processor may be a processor of a UE (such as a processor(s) 1304 of a wireless device 1302 that is a UE, as described herein). These instructions may be. for example, located in the processor and / or on a memory of the UE (such as a memory 1306 of a wireless device 1302 that is a UE, as described herein).

[0084] FIG. 11 illustrates a method 1100 for a reader (e.g., base station) in accordance with some embodiments. The method 1100 includes sending 1102, to an ambient loT device, a SSB. The method 1100 further includes receiving 1104 from the ambient loT device, a PRACH transmission. The PRACH transmission may comprise a PRACH preamble. The method 1100 further includes identifying 1106 a device category' type of the ambient loT device based on the PRACH preamble. A range of PRACH preamblesmay be split into multiple subsets where each subset corresponds to different device category types, and identifying the device category type may comprise determining to which of the subsets the PRACH preamble from the ambient loT device belongs.

[0085] In some embodiments, the subsets of the PRACH preambles comprise a first subset for lower category devices, and a second subset for higher category devices.

[0086] In some embodiments, the method 1100 further comprises receiving a second PRACH transmission from a second ambient loT device category type on a same RO as the PRACH transmission from the ambient loT device.

[0087] In some embodiments, there are multiple ROs associated with the SSB, and the multiple ROs correspond to the different device category types.

[0088] In some embodiments, an RO mapping sequence for different device types is frequency first and time second within a period.

[0089] In some embodiments, an RO mapping sequence for different device types is time first and frequency second within a period.

[0090] In some embodiments, lower category devices are mapped to a first set of symbols that occurs before a second set of symbols mapped to higher category devices.

[0091] In some embodiments, the method 1100 further comprises determining an association duration corresponding to the SSB, wherein the association duration is a period of time during which ROs are valid to send the PRACH transmission for the SSB.

[0092] In some embodiments, the association duration is configured differently for difference device types.

[0093] In some embodiments, higher category devices are configured with a longer association duration than lower category devices.

[0094] Embodiments contemplated herein include an apparatus comprising means to perform one or more elements of the method 1100. This apparatus may be, for example, an apparatus of a base station (such as a network device 1318 that is a base station, as described herein).

[0095] Embodiments contemplated herein include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of the method 1100. This non-transitory computer-readable media may be, for example, a memory of a base station (such as a memory 1322 of a network device 1318 that is a base station, as described herein).

[0096] Embodiments contemplated herein include an apparatus comprising logic, modules, or circuitry' to perform one or more elements of the method 1100. This apparatus may be. for example, an apparatus of a base station (such as a network device 1318 that is a base station, as described herein).

[0097] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform one or more elements of the method 1100. This apparatus may be, for example, an apparatus of a base station (such as a network device 1318 that is a base station, as described herein).

[0098] Embodiments contemplated herein include a signal as described in or related to one or more elements of the method 1100.

[0099] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out one or more elements of the method 1100. The processor may be a processor of a base station (such as a processor(s) 1320 of a network device 1318 that is a base station, as described herein). These instructions may be, for example, located in the processor and / or on a memory of the base station (such as a memory' 1322 of a network device 1318 that is a base station, as described herein).

[0100] FIG. 12 illustrates an example architecture of a wireless communication system 1200, according to embodiments disclosed herein. The following description is provided for an example wireless communication system 1200 that operates in conjunction with the LTE system standards and / or 5G or NR system standards as provided by 3GPP technical specifications.

[0101] As shown by FIG. 12, the wireless communication system 1200 includes UE 1202 and UE 1204 (although any number of UEs may be used). In this example, the UE 1202 and the UE 1204 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device configured for wireless communication.

[0102] The UE 1202 and UE 1204 may be configured to communicatively couple with a RAN 1206. In embodiments, the RAN 1206 may be NG-RAN. E-UTRAN, etc. The UE 1202 and UE 1204 utilize connections (or channels) (shown as connection 1208 and connection 1210, respectively) with the RAN 1206, each of which comprises a physical communications interface. The RAN 1206 can include one or more base stations (such as base station 1212 and base station 1214) that enable the connection 1208 and connection 1210.

[0103] In this example, the connection 1208 and connection 1210 are air interfaces to enable such communicative coupling, and may be consistent with RAT(s) used by the RAN 1206, such as. for example, an LTE and / or NR.

[0104] In some embodiments, the UE 1202 and UE 1204 may also directly exchange communication data via a sidelink interface 1216. The UE 1204 is shown to be configured to access an access point (shown as AP 1218) via connection 1220. By way of example, the connection 1220 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 1218 may comprise a Wi-Fi® router. In this example, the AP 1218 may be connected to another network (for example, the Internet) without going through a CN 1224.

[0105] In embodiments, the UE 1202 and UE 1204 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 1212 and / or the base station 1214 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an orthogonal frequency division multiple access (OFDMA) communication technique (e.g., for downlink communications) or a single carrier frequency division multiple access (SC-FDMA) communication technique (e g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0106] In some embodiments, all or parts of the base station 1212 or base station 1214 may be implemented as one or more software entities running on server computers as part of a virtual network. In addition, or in other embodiments, the base station 1212 or base station 1214 may be configured to communicate with one another via interface 1222. In embodiments where the wireless communication system 1200 is an LTE system (e.g., when the CN 1224 is an EPC), the interface 1222 may be an X2 interface. The X2interface may be defined between two or more base stations (e.g., two or more eNBs and the like) that connect to an EPC, and / or between two eNBs connecting to the EPC. In embodiments where the wireless communication system 1200 is an NR system (e.g., when CN 1224 is a 5GC), the interface 1222 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs and the like) that connect to 5GC, between a base station 1212 (e.g., a gNB) connecting to 5GC and an eNB. and / or between two eNBs connecting to 5GC (e.g.. CN 1224).

[0107] The RAN 1206 is shown to be communicatively coupled to the CN 1224. The CN 1224 may comprise one or more network elements 1226, which are configured to offer various data and telecommunications services to customers / subscribers (e.g.. users of UE 1202 and UE 1204) who are connected to the CN 1224 via the RAN 1206. The components of the CN 1224 may be implemented in one physical device or separate physical devices including components to read and execute instructions from a machine- readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0108] In embodiments, the CN 1224 may be an EPC, and the RAN 1206 may be connected with the CN 1224 via an SI interface 1228. In embodiments, the SI interface 1228 may be split into two parts, an SI user plane (Sl-U) interface, which carries traffic data between the base station 1212 or base station 1214 and a serving gateway (S-GW), and the SI -MME interface, which is a signaling interface between the base station 1212 or base station 1214 and mobility management entities (MMEs).

[0109] In embodiments, the CN 1224 may be a 5GC, and the RAN 1206 may be connected with the CN 1224 via an NG interface 1228. In embodiments, the NG interface 1228 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 1212 or base station 1214 and a user plane function (UPF), and the SI control plane (NG-C) interface, which is a signaling interface between the base station 1212 or base station 1214 and access and mobility' management functions (AMFs).

[0110] Generally, an application server 1230 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 1224 (e.g., packet switched data services). The application server 1230 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.)for the UE 1202 and UE 1204 via the CN 1224. The application server 1230 may communicate with the CN 1224 through an IP communications interface 1232.[OHl] FIG. 13 illustrates a system 1300 for performing signaling 1334 between a wireless device 1302 and a network device 1318, according to embodiments disclosed herein. The system 1300 may be a portion of a wireless communications system as herein described. The wireless device 1302 may be, for example, a UE of a wireless communication system. The network device 1318 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.

[0112] The wireless device 1302 may include one or more processor(s) 1304. The processor(s) 1304 may execute instructions such that various operations of the wireless device 1302 are performed, as described herein. The processor(s) 1304 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0113] The wireless device 1302 may include a memory 1306. The memory 1306 may be a non-transitory computer-readable storage medium that stores instructions 1308 (which may include, for example, the instructions being executed by the processor(s) 1304). The instructions 1308 may also be referred to as program code or a computer program. The memory 1306 may also store data used by, and results computed by, the processor(s) 1304.

[0114] The wireless device 1302 may include one or more transceiver(s) 1310 that may include radio frequency (RF) transmitter circuitry and / or receiver circuitry that use the antenna(s) 1312 of the wireless device 1302 to facilitate signaling (e.g., the signaling 1334) to and / or from the wireless device 1302 with other devices (e.g., the network device 1318) according to corresponding RATs.

[0115] The wireless device 1302 may include one or more antenna(s) 1312 (e.g., one, two, four, or more). For embodiments with multiple antenna(s) 1312, the wireless device 1302 may leverage the spatial diversity of such multiple antenna(s) 1312 to send and / or receive multiple different data streams on the same time and frequency resources. This behavior may be referred to as, for example, multiple input multiple output (MIMO) behavior (referring to the multiple antennas used at each of a transmitting device and areceiving device that enable this aspect). MIMO transmissions by the wireless device 1302 may be accomplished according to precoding (or digital beamforming) that is applied at the wireless device 1302 that multiplexes the data streams across the antenna(s) 1312 according to known or assumed channel characteristics such that each data stream is received with an appropriate signal strength relative to other streams and at a desired location in the spatial domain (e.g., the location of a receiver associated with that data stream). Certain embodiments may use single user MIMO (SU-MIMO) methods (where the data streams are all directed to a single receiver) and / or multi user MIMO (MU-MIMO) methods (where individual data streams may be directed to individual (different) receivers in different locations in the spatial domain).

[0116] In certain embodiments having multiple antennas, the wireless device 1302 may implement analog beamforming techniques, whereby phases of the signals sent by the antenna(s) 1312 are relatively adjusted such that the (joint) transmission of the antenna(s) 1312 can be directed (this is sometimes referred to as beam steering).

[0117] The wireless device 1302 may include one or more interface(s) 1314. The interface(s) 1314 may be used to provide input to or output from the wireless device 1302. For example, a wireless device 1302 that is a UE may include interface(s) 1314 such as microphones, speakers, a touchscreen, buttons, and the like in order to allow for input and / or output to the UE by a user of the UE. Other interfaces of such a UE may be made up of transmitters, receivers, and other circuitry' (e.g., other than the transceiver(s) 1310 / antenna(s) 1312 already described) that allow for communication between the UE and other devices and may operate according to known protocols (e.g., Wi-Fi®, Bluetooth®, and the like).

[0118] The wireless device 1302 may include a PRACH module 1316. The PRACH module 1316 may be implemented via hardware, software, or combinations thereof. For example, the PRACH module 1316 may be implemented as a processor, circuit, and / or instructions 1308 stored in the memory' 1306 and executed by the processor(s) 1304. In some examples, the PRACH module 1316 may be integrated within the processor(s) 1304 and / or the transceiver(s) 1310. For example, the PRACH module 1316 may be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardyvare components (e.g., logic gates and circuitry) within the processor(s) 1304 or the transceiver(s) 1310.

[0119] The PRACH module 1316 may be used for various aspects of the present disclosure, for example, aspects of FIGS. 1-12. The PRACH module 1316 is configured to generate, encode, and send a PRACH transmission in accordance with embodiments herein.

[0120] The network device 1318 may include one or more processor(s) 1320. The processor(s) 1320 may execute instructions such that various operations of the network device 1318 are performed, as described herein. The processor(s) 1320 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0121] The network device 1318 may include a memory 1322. The memory 1322 may be a non-transitory computer-readable storage medium that stores instructions 1324 (which may include, for example, the instructions being executed by the processor(s) 1320). The instructions 1324 may also be referred to as program code or a computer program. The memory 1322 may also store data used by, and results computed by, the processor(s) 1320.

[0122] The network device 1318 may include one or more transceiver(s) 1326 that may include RF transmitter circuitry and / or receiver circuitry that use the antenna(s) 1328 of the network device 1318 to facilitate signaling (e.g., the signaling 1334) to and / or from the network device 1318 with other devices (e.g.. the wireless device 1302) according to corresponding RATs.

[0123] The network device 1318 may include one or more antenna(s) 1328 (e.g., one, two, four, or more). In embodiments having multiple antenna(s) 1328, the network device 1318 may perform MIMO, digital beamforming, analog beamforming, beam steering, etc., as has been described.

[0124] The network device 1318 may include one or more interface(s) 1330. The interface(s) 1330 may be used to provide input to or output from the network device 1318. For example, a network device 1318 that is a base station may include interface(s) 1330 made up of transmitters, receivers, and other circuitry (e g., other than the transceiver(s) 1326 / antenna(s) 1328 already described) that enables the base station to communicate with other equipment in a core network, and / or that enables the base station to communicate with external networks, computers, databases, and the like forpurposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.

[0125] The network device 1318 may include a random access module 1332. The random access module 1332 may be implemented via hardware, software, or combinations thereof. For example, the random access module 1332 may be implemented as a processor, circuit, and / or instructions 1324 stored in the memory 1322 and executed by the processor(s) 1320. In some examples, the random access module 1332 may be integrated within the processor(s) 1320 and / or the transceiver(s) 1326. For example, the random access module 1332 may be implemented by a combination of software components (e.g.. executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the processor(s) 1320 or the transceiver(s) 1326.

[0126] The random access module 1332 may be used for various aspects of the present disclosure, for example, aspects of FIGS. 1-12. The random access module 1332 is configured to receive and decode a PRACH transmission, and identify a device category type of the wireless device 1302 based on the PRACH preamble.

[0127] For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and / or methods as set forth herein. For example, a baseband processor as described herein in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth herein.

[0128] Any of the above described embodiments may be combined with any other embodiment (or combination of embodiments), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

[0129] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executableinstructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and / or firmware.

[0130] It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.

[0131] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

[0132] Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

CLAIMS1. A method performed by an ambient Internet of Things (loT) device, the method comprising: receiving, from a reader, a synchronization signal block (SSB); generating a Physical Random Access Channel (PRACH) transmission, wherein the PRACH transmission comprises a PRACH preamble selected from a subset of PRACH preambles that correspond to a device type of the ambient loT device; and sending the PRACH transmission to the reader.

2. The method of claim 1, wherein the subset of PRACH preambles is different than a second subset of PRACH preambles corresponding to a second device type.

3. The method of claim 2, further comprising transmitting on a same RACH occasion (RO) as a device of the second device type that received a same SSB.

4. The method of claim 2, further comprising: determining multiple RACH occasions (ROs) associated with the SSB; and determining which of the multiple ROs corresponds to the device type of the ambient loT device, wherein the ambient loT device sends the PRACH transmission using a RO corresponding to the device type.

5. The method of claim 4, wherein an RO mapping sequence for different device types is frequency first and time second within a period.

6. The method of claim 4, wherein an RO mapping sequence for different device types is time first and frequency second within a period.

7. The method of claim 6, wherein lower category devices are mapped to a first set of symbols that occurs before a second set of symbols mapped to higher category devices.

8. The method of claim 1 , further comprising determining an association duration corresponding to the SSB, wherein the association duration is a period of time during which RACH occasions (ROs) are valid to send the PRACH transmission for the SSB.

9. The method of claim 8, wherein the association duration is configured differently for difference device types.

10. The method of claim 9, wherein higher category' devices are configured with a longer association duration than lower category devices.

11. The method of claim 9, wherein higher category devices are configured with a first association duration that occurs later than a second association duration for lower category devices.

12. A method performed by a network node, the method comprising: sending, to an ambient Internet of Things (loT) device, a synchronization signal block (SSB); receiving, from the ambient loT device, a Physical Random Access Channel (PRACH) transmission, wherein the PRACH transmission comprises a PRACH preamble; and identifying a device category type of the ambient loT device based on the PRACH preamble, wherein a range of PRACH preambles is split into multiple subsets where each subset corresponds to different device category types, and identifying the device category type comprises determining to which of the subsets the PRACH preamble from the ambient loT device belongs.

13. The method of claim 12, wherein the subsets of the PRACH preambles comprise a first subset for lower category devices, and a second subset for higher category devices.

14. The method of claim 13, further comprising receiving a second PRACH transmission from a second ambient loT device category type on a same RACH occasion (RO) as the PRACH transmission from the ambient loT device.

15. The method of claim 12, wherein there are multiple RACH occasions (ROs) associated with the SSB, and the multiple ROs correspond to the different device category types.

16. The method of claim 1 , wherein an RO mapping sequence for different device types is frequency first and time second within a period.

17. The method of claim 15, wherein an RO mapping sequence for different device types is time first and frequency second within a period.

18. The method of claim 17, wherein lower category devices are mapped to a first set of symbols that occurs before a second set of symbols mapped to higher category devices.

19. The method of claim 12, further comprising determining an association duration corresponding to the SSB, wherein the association duration is a period of time during which RACH occasions (ROs) are valid to send the PRACH transmission for the SSB.

20. The method of claim 19, wherein the association duration is configured differently for difference device types.

21. The method of claim 20, wherein higher category devices are configured with a longer association duration than lower category devices.

22. An apparatus comprising means to perform the method of any of claim 1 to claim 21.

23. A computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform the method of any of claim 1 to claim 21.

24. An apparatus comprising logic, modules, or circuitry to perform the method of any of claim 1 to claim 21.

25. A baseband processor for an ambient Internet of Things (loT) device, the baseband processor configured to cause the ambient loT device to perform the method of any of claim 1 to claim 11.

26. A baseband processor for a network node, the baseband processor configured to cause the network node to perform the method of any of claim 12 to claim 21.

Images