Methods for collision avoidance for ambient IoT

Abstract

Embodiments herein comprise systems, methods, and apparatuses for reducing collisions between ambient Internet of Things (IoT) devices. Some embodiments include an ambient IoT device that maintains and monitors a timer or counter. A reader, such as a base station, may provide a value for the counter or timer. The value may indicate when the ambient IoT device is allowed to access the reader.

Description

METHODS FOR COLLISION AVOIDANCE FOR AMBIENT IOTTECHNICAL FIELD

[0001] This application relates generally to wireless communication systems, including collision avoidance maneuvers for signaling between a base station and ambient powered devices. The signaling can be transmitted directly between base station and the ambient powered devices and / or via an intermediate node, e.g., a user equipment.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 3 GPP 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 in accordance with some embodiments.

[0009] FIG. 2 illustrates a signal flow diagram for an ambient loT device using counter-based access to a reader in accordance with some embodiments.

[0010] FIG. 3 illustrates a transmission timeline for an ambient loT device using counter-based access for communication with a reader in accordance with some embodiments.

[0011] FIG. 4 illustrates a signal flow diagram for an ambient loT device using timerbased access to a reader in accordance with some embodiments.

[0012] FIG. 5 illustrates a transmission timeline for an ambient loT device using timerbased access for communication with a reader in accordance with some embodiments.

[0013] FIG. 6 illustrates a method for an ambient IOT device in accordance with some embodiments.

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

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

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

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

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

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

[0020] There may be multiple types of ambient loT devices that the wireless communication system may support. For instance, in terms of energy storage, some devices may be battery-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 orrecharged 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.).

[0021] For example. FIG. 1 illustrates a table of design targets 102 for an example set of loT device types in accordance with some embodiments. 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 backscattering transmission. loT device type B may have energy storage and may harvest energy from ambient sources, but does not perform independent signal generation, i.e., only backscattering 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 are 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.

[0022] 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 complexity, data-rate. positioning accuracy, and device mobility. These illustrate example design targets 102. Design targets 102 may vary based on actual implantation.

[0023] 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 ty pe A and ty pe 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.

[0024] In some embodiments, higher-category devices may include devices between type B and type 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 .

[0025] Both lower- category loT device and higher category loT device categories may have very7low complexity7. 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 scalability7. As the ambient loT devices may be densely deployed, transmissions from the devices may be more susceptible to collisions and contentions.

[0026] In some embodiments, it is expected that up to 100 devices per 100 m2area are served indoors. This implies that large number of devices may7be quite densely concentrated and served by one base station. Therefore, one issue that may result in the use of ambient loT devices, especially with passive and semi-passive devices, is how to handle collisions between these devices for access to the network. Since the ambient loT devices may be passive, it is expected that the devices are not able to maintain tight synchronization with network when not connected / communi eating with the network. For instance, the ambient loT devices may communicate with a base station via separate rounds of communication. After each round of communication, the ambient loT device may not have sufficient capabilities (e.g., small memory, no oscillator clock, etc.) to maintain synchronization with the base station. Accordingly, new rounds of communication may use a new access procedure.

[0027] As a result, an ambient loT device may not know whether it is expected to access the network or not and therefore, all the devices may try to access the network. For example, the devices may use a same RACH occasions and may cause collision to each other. Embodiments herein include methods to reduce the collision among devices, especially when accessing the network in a contention-based manner. Some embodiments herein introduce implicit or explicit methods for an ambient loT device to determine when it may or may not be required to access the base station.

[0028] In some embodiments, the ambient loT device may communicate with a reader. The reader may be a base station, a UE, or other device. While some embodiments andillustrations are specifically discussed with relation to a base station as a reader, other devices may be used substituted as the reader.

[0029] FIG. 2 illustrates a signal flow diagram 202 for an ambient loT device 204 using counter-based access to a reader 206 in accordance with some embodiments. The reader 206 may be a base station, UE. or other device configured to communicate with the ambient loT device 204. The ambient loT device 204 may use counter-based access to reduce collisions with other devices communicating with the reader 206.

[0030] The ambient loT device 204, in order to determine whether it should initiate an access to the reader 206 (e.g., base station), may be pre-configured with a default counter value. For example, the default counter value may be set to zero. The ambient loT device 204 may maintain a counter value, and whenever the counter value is the same as the default value, the ambient loT device 204 is allowed to access the reader 206. The default value may be pre-configured for the ambient loT device 204.

[0031] For example, in some embodiments, if the ambient loT device 204 receives a synchronization signal block (SSB) 212 from the network (e.g., reader 206), then the ambient loT device 204 checks 208 its current counter value. The ambient loT device 204 may compare the current counter value to the default value to determine if it should access the reader 206. If the current counter value is the same as the default value, then the ambient loT device 204 may respond on the random-access channel (RACH) occasion (RO) corresponding to the received SSB 212 (e.g., RO transmission 214). For example, the ambient loT device 204 may send a RO transmission 214 and perform the rest of the access procedure 216. If the value of the counter is different than the default value, then the ambient loT device 204 is not expected to respond to the received SSB 212. In some embodiments, the counter may be initialized with a value equal to or greater than the default value.

[0032] Upon successful completion of access to the reader 206 (e.g.. base station), the reader 206 may set a value for the counter that is different than the default value of the counter that is pre-configured to the ambient loT device. The reader 206 may provide a counter value 218 to the ambient loT device 204. The counter value 218 may be used to determine when the ambient loT device 204 can send a next RO transmission 222. For example, the counter value 218 may be reduced for each SSB the ambient loT device 204 receives. The ambient loT device 204 may check 210 after each SSB 220 the currentcounter value. In some embodiments, once the counter reaches zero or a default value, the ambient loT device 204 may transmit the RO transmission 222 on the next RO.

[0033] In some embodiments, the ambient loT device 204 may be configured with multiple counters and corresponding values. Different transmission types (e.g., PRACH transmission, PUCCH transmission, PUSCH transmission, etc.) may have different counters. For example, each counter may be associated with different transmission types corresponding to one specific reader identifier (ID) (e.g., Physical Cell ID in case of base station as a reader).

[0034] In some embodiments, the ambient loT device 204 may be configured with multiple counters and corresponding value, where each counter is associated with a specific reader ID. For example, the multiple counters may be associated with Physical Cell IDs in the case of the base station as the reader 206. The counter values may be updated independently based on corresponding access to the associated reader ID. If a counter value is the default value (e.g., zero) for one reader ID, then the ambient loT device 204 may access that reader, but if the counter value is different than the default for another reader ID the ambient loT device 204 may not access the other reader.

[0035] For counter based access, the ambient loT device 204 may update the value of the counter based on network conditions. For instance, after the reader 206 (e.g., base station) sets a counter value for the device upon successful completion of the access, then the ambient loT device 204 may reduce the counter value by one every time the ambient loT device 204 receives a transmission from the reader 206. Once the counter value reaches default value, e.g., zero, then the ambient loT device 204 is allowed to again access the reader.

[0036] The counter reduction may be based on a received SSB and associated Ros. In some embodiments, every time an SSB is received by the ambient loT device 204, the ambient loT device 204 deducts the counter value by one, but the ambient loT device 204 does not access with PRACH transmission on RO unless the counter reaches default value (e.g., zero). In some embodiments, only one SSB reception within a period is considered for counter value reduction.

[0037] Accordingly, the reader 206 may set the counter value 218 to control the number of times the ambient loT device 204 attempts to access the reader 206. For example, the network may set the counter value 218 to a high value to cause the ambient loT device 204 to only send the RO transmission after multiple rounds of SSB. The counter value218 may be configured based on a desired implementation. In some embodiments, the reader 206 may select the counter value 218 based on the device type of the ambient loT device 204, the information provided by the ambient loT device 204, the device type of the reader 206, the density of the ambient loT devices, or other factors.

[0038] FIG. 3 illustrates a transmission timeline 302 for an ambient loT device using counter-based access for communication with a reader in accordance with some embodiments. In the illustrated embodiment, the ambient loT device is referred to in the illustration as a UE, and the reader is a base station (BS). As shown, the ambient loT device receives a first SSB 304. The ambient loT device may check the counter value, and since the counter value equals zero (e.g., a preconfigured default value), the ambient loT device transmits in the first RO 306. The base station receives the RO transmission, and the rest of the access procedure is performed.

[0039] Upon completion of the access procedure, the base station may set the counter value to a target value. In the illustrated embodiment, the base station sets the counter value to one. The ambient loT device receives the second SSB 308. The second SSB 308 triggers the ambient loT device to check the counter value. As the counter value is set to one, the ambient loT device does not transmit in the second RO 310, and reduces the counter value by one which results in the counter value being zero.

[0040] The ambient loT device receives a third SSB 312. The SSB causes the ambient loT device to check the counter value. As the counter value is equal to zero at this point, the ambient loT device transmits on the next transmission occasion (e.g., third RO 314). The base station receives the RO transmission, and the rest of the access procedure is performed. Upon completion of the access procedure, the base station may set the counter value to a second target value. In the illustrated embodiment, the base station sets the counter value to two. Accordingly, the ambient loT device will skip the next two transmission occasions before the counter is once again reduced to zero.

[0041] In some embodiments, after the counter is reduced to the default value (e.g., zero) and a transmission occurs, the counter may remain at that value until a new counter value is received from the reader. In some embodiments, after the counter is reduced to the default value (e.g., zero) and a transmission occurs, the counter value resets to the last value received from the reader if no new counter value is received.

[0042] FIG. 4 illustrates a signal flow diagram 402 for an ambient loT device 404 using timer-based access to a reader 406 in accordance with some embodiments. The reader406 may be a base station, UE, or other device configured to communicate with the ambient loT device 404. The ambient loT device 404 may use timer-based access to reduce collisions with other devices communicating with the reader 406. The time value for the timer may be in terms of milliseconds, seconds, frames, slots, symbols, or other time-based units.

[0043] In some embodiments, the ambient loT device 404, in order to determine whether it should initiate an access to the reader 406 (e.g., base station), may be configured with a time-value by the reader (e.g., base station) and as long as the time value is greater than zero, the device is not expected to access the channel. In one implementation, if an ambient loT device receives SSB from the network, then the ambient loT device checks its time value and if it is zero, then the ambient loT device may respond on the RO corresponding to the received SSB. Upon successful completion of the access to the reader, the reader may initialize / configure a timer value to the ambient loT device.

[0044] For example, in some embodiments, if the ambient loT device 404 receives an SSB 412 from the network (e.g., reader 406), then the ambient loT device 404 checks 408 its current timer value. If the timer value is zero, then the ambient loT device 404 may respond on the random-access channel (RACH) occasion (RO) corresponding to the received SSB 412 (e.g., RO transmission 414). For example, the ambient loT device 404 may send a RO transmission 414 and perform the rest of the access procedure 416. If the value of the timer is not zero, then the ambient loT device 404 is not expected to respond to the received SSB 412. In some embodiments, the timer may be initialized with a number greater than zero. In some embodiments, the timer may be initialized as zero.

[0045] Upon successful completion of access to the reader 406 (e.g.. base station), the reader 406 may set a value for the timer. The reader 406 may provide a timer value 418 to the ambient loT device 404. The timer value 418 may be used to determine when the ambient loT device 404 can send a next RO transmission 422. The ambient loT device 404 may check 410 the value of the timer after each SSB (e.g., SSB 420). Once the timer reaches zero, the ambient loT device 404 may transmit the RO transmission 422 on the next RO.

[0046] In some embodiments, the reader 406 may select the timer value to prioritize or deprioritize different devices. For example, the reader 406 may provide a timer value based on the device type of the ambient loT device 404, the information provided by theambient loT device 404, the device type of the reader 406, the density of the ambient loT devices, or other factors. The timer-based access may reduce collisions between devices.

[0047] FIG. 5 illustrates a transmission timeline 502 for an ambient loT device using timer-based access for communication with a reader in accordance with some embodiments. In the illustrated embodiment, the ambient loT device is referred to in the illustration as a UE, and the reader is a base station. As shown, the ambient loT device receives a first SSB 504. The ambient loT device may check the timer value, and since the tuner value equals zero, the ambient loT device transmits in the first RO 506. The base station receives the RO transmission, and the rest of the access procedure is performed. The timer value may be preconfigured default value. In the illustrated embodiment, the timer value is set to zero before it receives a different value from the base station. In other embodiments, the pre-configured timer value may be greater than zero.[004S] Upon completion of the access procedure, the base station may set the timer value to a target value. In the illustrated embodiment, the base station sets the timer value to a number greater than zero. The ambient loT device sets its timer to the timer value, and does not attempt to access the base station for the time duration 516 when the timer value is greater than zero. For instance, in the illustrated embodiment, the ambient loT device receives the second SSB 508. The second SSB 508 triggers the ambient loT device to check the current value of the timer. As the current timer value is greater than zero, the ambient loT device does not transmit in the second RO 510.

[0049] The ambient loT device receives a third SSB 512. The third SSB 512 causes the ambient loT device to check the timer value. As the current timer value is still greater than zero, the ambient loT device does not transmit in the third RO 514. After the timer becomes zero, then the ambient loT device may respond on the next RO corresponding to the next received SSB.

[0050] FIG. 6 illustrates a method 600 for an ambient IOT device in accordance with some embodiments. The illustrated method 600 includes maintaining 602 an event meter, wherein the event meter indicates when the ambient loT device is allowed to respond to a reader. The method 600 further includes receiving 604 a value for the event meter from the reader. The method 600 further includes receiving 606, from the reader, a downlink signal. The method 600 further includes checking 608 the value of the event meter when the downlink signal is received. The method 600 further includes sending 610, when theevent meter is depleted, a response to the received downlink signal on a corresponding transmission occasion associated with the downlink signal. The method 600 further includes delaying 612, when the event meter is not depleted, the response until a future downlink signal is received when the event meter is depleted.

[0051] In some embodiments of the method 600, the event meter comprises a counter, and whenever the counter reaches a default pre-configured value the ambient loT device is allowed to access the reader. In some embodiments, the default pre-configured value is zero.

[0052] In some embodiments, the method 600 further comprises reducing the counter by one after each downlink signal is received from the reader.

[0053] In some embodiments, the method 600 further comprises monitoring multiple counters associated with different transmission types corresponding to a reader identifier.

[0054] In some embodiments, the method 600 further comprises monitoring multiple counters where each of the multiple counters is associated with a specific reader identifier, and wherein counter values of the multiple counters are updated independently.

[0055] In some embodiments of the method 600, the event meter comprises a timer, and whenever the timer reaches zero the ambient loT device is allowed to access the reader.

[0056] In some embodiments, the method 600 further comprises monitoring multiple timers associated with different transmission types corresponding to a reader identifier.

[0057] In some embodiments, the method 600 further comprises monitoring multiple timers associated with different transmission types corresponding to a reader identifier.

[0058] In some embodiments of the method 600, the downlink signal is an SSB, and wherein the response is a RO transmission sent to the reader on a RO corresponding to the SSB.

[0059] In some embodiments of the method 600, the value of the event meter is set by a network, based on energy harvesting at the ambient loT device, or a category of device type.

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

[0061] 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 600. This non-transitory computer-readable media may be, for example, a memory of a UE (such as a memory 806 of a wireless device 802 that is a UE, as described herein).

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

[0063] 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 600. This apparatus may be, for example, an apparatus of a UE (such as a wireless device 802 that is a UE, as described herein).

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

[0065] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor causes the processor to carry out one or more elements of the method 600. The processor may be a processor of a UE (such as a processor(s) 804 of a wireless device 802 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 806 of a wireless device 802 that is a UE, as described herein).

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

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

[0068] The UE 702 and UE 704 may be configured to communicatively couple with a RAN 706. In embodiments, the RAN 706 may be NG-RAN, E-UTRAN, etc. The UE 702 and UE 704 utilize connections (or channels) (shown as connection 708 and connection 710, respectively) with the RAN 706, each of which comprises a physical communications interface. The RAN 706 can include one or more base stations (such as base station 712 and base station 714) that enable the connection 708 and connection 710.

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

[0070] In some embodiments, the UE 702 and UE 704 may also directly exchange communication data via a sidelink interface 716. The UE 704 is shown to be configured to access an access point (shown as AP 718) via connection 720. By way of example, the connection 720 can comprise a local wireless connection, such as a connection consistent with any IEEE 802. 11 protocol, wherein the AP 718 may comprise a Wi-Fi® router. In this example, the AP 718 may be connected to another network (for example, the Internet) without going through a CN 724.

[0071] In embodiments, the UE 702 and UE 704 can be configured to communicate using orthogonal frequency division multiplexing (OFDM) communication signals with each other or with the base station 712 and / or the base station 714 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.

[0072] In some embodiments, all or parts of the base station 712 or base station 714 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 712 or base station 714 may be configured to communicate with one another via interface 722.In embodiments where the wireless communication system 700 is an LTE system (e.g., when the CN 724 is an EPC), the interface 722 may be an X2 interface. The X2 interface 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 700 is an NR system (e.g., when CN 724 is a 5GC), the interface 722 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 712 (e g., a gNB) connecting to 5GC and an eNB, and / or between two eNBs connecting to 5GC (e.g., CN 724).

[0073] The RAN 706 is shown to be communicatively coupled to the CN 724. The CN 724 may comprise one or more network elements 726, which are configured to offer various data and telecommunications services to customers / subscribers (e.g., users of UE 702 and UE 704) who are connected to the CN 724 via the RAN 706. The components of the CN 724 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).

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

[0075] In embodiments, the CN 724 may be a 5GC, and the RAN 706 may be connected with the CN 724 via an NG interface 728. In embodiments, the NG interface 728 may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the base station 712 or base station 714 and a user plane function (UPF), and the SI control plane (NG-C) interface, which is a signaling interface between the base station 712 or base station 714 and access and mobility management functions (AMFs).

[0076] Generally, an application server 730 may be an element offering applications that use internet protocol (IP) bearer resources with the CN 724 (e.g., packet switched data services). The application server 730 can also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) forthe UE 702 and UE 704 via the CN 724. The application server 730 may communicate with the CN 724 through an IP communications interface 732.

[0077] FIG. 8 illustrates a system 800 for performing signaling 834 between a wireless device 802 and a network device 818, according to embodiments disclosed herein. The system 800 may be a portion of a wireless communications system as herein described. The wireless device 802 may be, for example, a UE of a wireless communication system. The network device 818 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.

[0078] The wireless device 802 may include one or more processor(s) 804. The processor(s) 804 may execute instructions such that various operations of the wireless device 802 are performed, as described herein. The processor(s) 804 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.

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

[0080] The wireless device 802 may include one or more transceiver(s) 810 that may include radio frequency (RF) transmitter circuitry and / or receiver circuitry that use the antenna(s) 812 of the wireless device 802 to facilitate signaling (e.g., the signaling 834) to and / or from the wireless device 802 with other devices (e.g., the network device 818) according to corresponding RATs.

[0081] The wireless device 802 may include one or more antenna(s) 812 (e.g., one, two, four, or more). For embodiments with multiple antenna(s) 812, the wireless device 802 may leverage the spatial diversity of such multiple antenna(s) 812 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 a receiving device that enable this aspect). MIMO transmissions by the wireless device 802 may beaccomplished according to precoding (or digital beamforming) that is applied at the wireless device 802 that multiplexes the data streams across the antenna(s) 812 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).

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

[0083] The wireless device 802 may include one or more interface(s) 814. The interface(s) 814 may be used to provide input to or output from the wireless device 802. For example, a wireless device 802 that is a UE may include interface(s) 814 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) 810 / antenna(s) 812 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).

[0084] The wireless device 802 may include a counter / timer module 816. The counter / timer module 816 may be implemented via hardware, software, or combinations thereof. For example, the counter / timer module 816 may be implemented as a processor, circuit, and / or instructions 808 stored in the memory 806 and executed by the processor(s) 804. In some examples, the counter / timer module 816 may be integrated within the processor(s) 804 and / or the transceiver(s) 810. For example, the counter / timer module 816 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) 804 or the transceiver(s) 810.

[0085] The counter / timer module 816 may be used for various aspects of the present disclosure, for example, aspects of FIGS. 1-7. The counter / timer module 816 isconfigured to maintain and monitor a counter or timer for accessing the network device 818.

[0086] The network device 818 may include one or more processor(s) 820. The processor(s) 820 may execute instructions such that various operations of the network device 818 are performed, as described herein. The processor(s) 820 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.

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

[0088] The network device 818 may include one or more transceiver(s) 826 that may include RF transmitter circuitry’ and / or receiver circuitry that use the antenna(s) 828 of the network device 818 to facilitate signaling (e.g.. the signaling 834) to and / or from the network device 818 with other devices (e.g., the wireless device 802) according to corresponding RATs.

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

[0090] The network device 818 may include one or more interface(s) 830. The interface(s) 830 may be used to provide input to or output from the network device 818. For example, a network device 818 that is a base station may include interface(s) 830 made up of transmitters, receivers, and other circuitry (e.g., other than the transceiver(s) 826 / antenna(s) 828 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 for purposes of operations, administration, and maintenance of the base station or other equipment operably connected thereto.

[0091] The network device 818 may include a counter / timer value module 832. The counter / timer value module 832 may be implemented via hardware, software, orcombinations thereof. For example, the counter / timer value module 832 may be implemented as a processor, circuit, and / or instructions 824 stored in the memory 822 and executed by the processor(s) 820. In some examples, the counter / timer value module 832 may be integrated within the processor(s) 820 and / or the transceiver(s) 826. For example, the counter / timer value module 832 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) 820 or the transceiver(s) 826.

[0092] The counter / timer value module 832 may be used for various aspects of the present disclosure, for example, aspects of FIGS. 1-7. The counter / timer value module 832 is configured to set a counter or timer value for the wireless device 802.

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

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

[0095] Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions 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.

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

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

[0098] 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: maintaining an event meter, wherein the event meter indicates when the ambient loT device is allowed to respond to a reader; receiving a value of the event meter from the reader; receiving, from the reader, a downlink signal; checking the value of the event meter when the downlink signal is received; when the event meter is depleted, sending a response to the received downlink signal on a corresponding transmission occasion associated with the downlink signal; and when the event meter is not depleted, delaying the response until a future downlink signal is received when the event meter is depleted.

2. The method of claim 1, wherein the event meter comprises a counter, and whenever the counter reaches a default pre-configured value the ambient loT device is allowed to respond to the reader.

3. The method of claim 2, wherein the default pre-configured value is zero.

4. The method of claim 2, further comprising reducing the counter by one after each downlink signal is received from the reader.

5. The method of claim 2, further comprising monitoring multiple counters associated with different transmission types corresponding to a reader identifier.

6. The method of claim 2, further comprising monitoring multiple counters where each of the multiple counters is associated with a specific reader identifier, and wherein counter values of the multiple counters are updated independently.

7. The method of claim 1, wherein the event meter comprises a timer, and whenever the timer reaches zero the ambient loT device is allowed to respond to the reader.

8. The method of claim 7, further comprising monitoring multiple timers associated with different transmission types corresponding to a reader identifier.

9. The method of claim 7, further comprising monitoring multiple timers associated with different transmission types corresponding to a reader identifier.

10. The method of claim 1, wherein the downlink signal is a synchronization signal block (SSB), and wherein the response is a random-access channel (RACH) occasion (RO) transmission sent to the reader on a RO corresponding to the SSB.

11. The method of claim 1, wherein the value of the event meter is set by a network, based on energy harvesting at the ambient loT device, or a category of device type.

12. An apparatus for an ambient Internet of Things (loT) device comprising: a processor; and a memory storing instructions that, when executed by the processor, configure the apparatus to: maintain an event meter, wherein the event meter indicates when the ambient loT device is allowed to respond to a reader: receive a value of the event meter from the reader; receive, from the reader, a downlink signal; check the value of the event meter when the downlink signal is received; when the event meter is depleted, send a response to the received downlink signal on a corresponding transmission occasion associated with the downlink signal; and when the event meter is not depleted, delay the response until a future downlink signal is received when the event meter is depleted.

13. The apparatus of claim 12, wherein the event meter comprises a counter, and whenever the counter reaches zero the ambient loT device is allowed to respond to the reader.

14. The apparatus of claim 13, wherein the instructions further configure the apparatus to reduce the counter by one after each downlink signal is received from the reader.

15. The apparatus of claim 13, wherein the instructions further configure the apparatus to monitor multiple counters associated with different transmission types corresponding to a reader identifier.

16. The apparatus of claim 13, wherein the instructions further configure the apparatus to monitor multiple counters where each of the multiple counters is associated with a specific reader identifier, and wherein counter values of the multiple counters are updated independently.

17. The apparatus of claim 12, wherein the event meter comprises a timer, and whenever the timer reaches zero the ambient loT device is allowed to respond to the reader.

18. The apparatus of claim 17, wherein the instructions further configure the apparatus to monitor multiple timers associated with different transmission types corresponding to a reader identifier.

19. The apparatus of claim 17, wherein the instructions further configure the apparatus to monitor multiple timers associated with different transmission types corresponding to a reader identifier.

20. A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by an ambient Internet of Things (loT) device, cause the ambient loT device to: maintain an event meter, wherein the event meter indicates when the ambient loT device is allowed to respond to a reader; receive a value of the event meter from the reader; receive, from the reader, a downlink signal; check the value of the event meter when the downlink signal is received; when the event meter is depleted, send a response to the received downlink signal on a corresponding transmission occasion associated with the downlink signal; and when the event meter is not depleted, delay the response until a future downlink signal is received when the event meter is depleted.

21. The computer-readable storage medium of claim 20, wherein the event meter comprises a counter, and whenever the counter reaches a default pre-configured value the ambient loT device is allowed to respond to the reader.

22. The computer-readable storage medium of claim 21, wherein the instructions further configure the ambient loT device to reduce the counter by one after each downlink signal is received from the reader.

23. The computer-readable storage medium of claim 21, wherein the instructions further configure the ambient loT device to monitor multiple counters associated with different transmission types corresponding to a reader identifier.

24. The computer-readable storage medium of claim 21, wherein the instructions further configure the ambient loT device to monitor multiple counters where each of the multiple counters is associated with a specific reader identifier, and wherein counter values of the multiple counters are updated independently.

25. The computer-readable storage medium of claim 20, wherein the event meter comprises a timer, and whenever the timer reaches zero the ambient loT device is allowed to respond to the reader.

26. The computer-readable storage medium of claim 25, wherein the instructions further configure the ambient loT device to monitor multiple timers associated with different transmission types corresponding to a reader identifier.

27. The computer-readable storage medium of claim 25, wherein the instructions further configure the ambient loT device to monitor multiple timers associated with different transmission types corresponding to a reader identifier.

28. An apparatus comprising means to perform the method of any of claim 1 to claim 11.

29. 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.

Images