Limiting device responses in an inventory procedure

Abstract

The described system, device and method provide a procedure where a reader, or base station, broadcasts information that indicates what group of devices it needs to collect inventory information from and how many devices it needs to respond. In a RACH procedure, the devices use the information about how many devices need to respond to determine to detect that a sufficient number of devices have responded. Once the device determines that a sufficient number of devices have responded, the device can stop performing the RACH procedure and determine that a response is not necessary. Thus, each device that receives an AS request message may attempt a RACH procedure at least once, but some devices may be able to detect that the RACH procedure does not need to be attempted again if the RACH attempt fails.

Description

LIMITING DEVICE RESPONSES IN AN INVENTORY PROCEDURECROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 574,712, entitled Limiting Device Responses In An Inventory Procedure and filed April 4, 2024, the contents of which are incorporated herein by reference.BACKGROUND

[0002] Ambient loT (AloT) devices may be assigned an AloT device ID. The Ambient loT Device ID may consist of three parts The first part may be a Home Network Identifier that identifies the operator that manages the AloT device The second part may be an Owner Identifier that identifies a 3rd party that owns the AloT device, sends requests to perform operations on the AloT device, receives information about the AloT device, and receives information from the AloT device. The third part may be an Instance Identifier that identifies the specific AloT device.

[0003] An application function (AF) may send a request to the 5GC to inventory one or more devices. Inventory means send a request and receive responses from one or more AloT devices The responses include the identifying information of each AloT device. The 5GC then sends a list of devices to the AF. The list of devices represents the devices that responded and may also include information about the location where the devices responded. The information about the location where the devices responded may be the identity of the reader or the identity of the base station. For example, the information about the location where a device responded may be a reader identity or a base station identity.

[0004] In order to trigger the AloT devices to respond, a reader or base station may transmit a full or partial AloT device ID. Any AloT device whose configured AloT device ID matches the received full or partial AloT device ID may respond to the inventory request.SUMMARY

[0005] The described system, device and method provide a procedure where a reader, or base station, broadcasts information that indicates what group of devices it needs to collect inventory information from and how many devices it needs to respond. In a random-access channel (RACH) procedure, the devices use the information about how many devices need to respond to determine to detect that a sufficient number of devices have responded. Once the device determines that a sufficient number of devices have responded, the device can stop performing the RACH procedure and determine that a response is not necessary. Thus, each devicethat receives an access stratum (AS) request message may attempt a RACH procedure at least once, but some devices may be able to detect that the RACH procedure does not need to be attempted again if the RACH attempt fails.

[0006] A system, device and method are disclosed. The method may be performed in an Ambient loT device (AloT device). The method includes receiving a first message including a group identifier and a response number, determining that the group identifier in the received first message matches a group identifier configured in the AloT device, and performing a first random-access channel (RACH) procedure. The method further includes on a condition that the performed first RACH procedure fails to successfully complete and the response number is below a first threshold relative to a number of times a RACH procedure for a device configured with the group identifier fails to successfully complete, waiting for a second message. The method further includes on a condition that the performed first RACH procedure fails to successfully complete and the response number is above a second threshold relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete, performing a second RACH procedure. The method further includes on a condition that the performed first RACH procedure or the second RACH procedure successfully completed, sending a response message. The received first message may further include a throttle indication and based on the throttle indication, the performed first RACH procedure if unsuccessful is repeated until successful. The group identifier may include a network operator Identifier configured to enable the AloT device to determine if the AloT device is configured with the identifier. The group identifier may include an owner identifier configured to enable the AloT device to determine if the AloT device is configured with the owner identifier. The response message may include an identifier of the AloT device. Being below a first threshold comprises the response number being sufficiently small relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete. For example, the AloT device may count the number of times that a RACH procedure fails (i.e. count the number of times that RACH failure is detected) The AoT device may compare the number of times that a RACH procedure failed to the response number. The comparison may involve multiplying a scale factor value by the response number. The scale factor value may be pre-configured in the AloT device or received by the AloT device in a configuration message. The scale factor value may be based on the type of AloT device and / or how quickly other AloT devices in the group are likely to respond to an inventory request. For example, the response number may be 100 and the scale factor value may be 0.2. A scale factor 0.2 may be used if it is likely that 20 devices can respond to the inventory request in the time that it takes for 1 RACH procedure to fail. In this example, after each RACH failure event, the AloT device may compare the number of times that a RACH failure was detected to the multiplication of the scale factor and the response number. The AloT device may determine to reattempt the RACH procedure if the number of times that a RACH failure was detected is equal to or below the result of the multiplication. In other words, the AloT device may determine that the response number is sufficiently small relative to the number of times a RACH procedure failed because the number of times that RACH failure was detected is greater than 20. Based on determining that the response number is sufficiently small relative to the number of times a RACH procedure failed, the AloT device may determine to wait for a second message. Beingabove a second threshold comprises the response number being sufficiently large relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete. In this example, if the AloT device determines that the threshold is 20 the AloT device may reattempt the RACH procedure if the number of times that RACH failure was detected is greater than 20. In other words, the AloT device may determine that the response number is sufficiently large relative to the number of times a RACH procedure failed because the number of times that RACH failure was detected is less than or equal to 20. Based on determining that the response number is sufficiently large relative to the number of times a RACH procedure failed, the AloT device may determine to perform a second RACH procedure. The first threshold and the second threshold may be equal. The response number may be configured to enable the AloT device to detect when a response is no longer necessary. The response number may be received from a base station (BS). The first message may further include a time-out value indicating a time period for collecting responses before acting. The response number may include a number that indicates a limit on a number of times a RACH procedure fails to successfully complete before stopping the performance of a RACH procedure, and waiting for a second message.

[0007] The device may be an Ambient loT device (AloT device). The AloT device may include a processor and associated memory, and a transceiver operably coupled to the processor. The processor and transceiver configured to receive a first message including a group identifier and a response number, determine that the group identifier in the received first message matches a group identifier configured in the AloT device, and perform a first random-access channel (RACH) procedure The device, on a condition that the performed first RACH procedure fails to successfully complete and the response number is below a first threshold relative to a number of times a RACH procedure for a device configured with the group identifier fails to successfully complete, may wait for a second message. The device, on a condition that the performed first RACH procedure fails to successfully complete and the response number is above a second threshold relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete, may perform a second RACH procedure. The device, on a condition that the performed first RACH procedure or the second RACH procedure successfully completed, may send a response message. The received first message may further include a throttle indication and based on the throttle indication, the performed first RACH procedure if unsuccessful is repeated until successful. The group identifier may include a network operator Identifier configured to enable the AloT device to determine if the AloT device is configured with the identifier. The group identifier may include an owner identifier configured to enable the AloT device to determine if the AloT device is configured with the owner identifier The response message may include an identifier of the AloT device. Being below a first threshold comprises the response number being sufficiently small relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete. Being above a second threshold comprises the response number being sufficiently large relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete. The first threshold and the second threshold may be equal. The response number may be configured to enable the AloT device to detect when a response is no longer necessary The response numbermay be received from a base station (BS) The first message may further include a time-out value indicating a time period for collecting responses before acting. The response number may include a number that indicates a limit on a number of times a RACH procedure fails to successfully complete before stopping the performance of a RACH procedure, and waiting for a second message.BRIEF DESCRIPTION OF THE DRAWINGS

[0008] A more detailed understanding may be had from the following description, given by way of example in conjunction with the accompanying drawings, wherein like reference numerals in the figures indicate like elements, and wherein:

[0009] FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented;

[0010] FIG. 1 B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG 1A according to an embodiment;

[0011] FIG. 1C is a system diagram illustrating an example radio access network (RAN) and an example core network (CN) that may be used within the communications system illustrated in FIG. 1A according to an embodiment;

[0012] FIG. 1D is a system diagram illustrating a further example RAN and a further example CN that may be used within the communications system illustrated in FIG 1A according to an embodiment;

[0013] FIG. 2 illustrates an example procedure for how an AF can initiate an inventory operation;

[0014] FIG. 3 illustrates an example of how an Ambient loT Device may use the desired response number to detect when it is no longer necessary to respond;

[0015] FIG. 4 illustrates a method of WTRU Actions that may be performed by an Ambient loT Device; and

[0016] FIG. 5 includes a method of BS / Reader Actions that may be performed by a Base Station, or reader.DETAILED DESCRIPTION

[0017] The described system, device and method provide a procedure where a reader, or base station, broadcasts information that indicates what group of devices it needs to collect inventory information from and how many devices it needs to respond. In a random-access channel (RACH) procedure, the devices use the information about how many devices need to respond to determine to detect that a sufficient number of devices have responded. Once the device determines that a sufficient number of devices have responded, the device can stop performing the RACH procedure and determine that a response is not necessary. Thus, each device that receives an AS request message may attempt a RACH procedure at least once, but some devices may be able to detect that the RACH procedure does not need to be attempted again if the RACH attempt fails.

[0018] The terms base station and reader are used interchangeably herein.

[0019] Generally, the Ambient loT (AloT) device initiates a RACH procedure when it detects that it might need send information to the network. A RACH is a procedure that is used by a device to gain initial access to a network after the device has had a period of inactivity. As described herein, the concepts can be applied to any procedure that is used to a device to gain initial access to a network.

[0020] The terms AloT device, device, and WTRU are used interchangeably herein.

[0021] The AloT device may perform a RACH procedure. Performing a RACH procedure may mean that the Ambient loT Device transmits a message to attempt to access the network and the Ambient loT Device determines if the RACH procedure is a success if the AloT device has gained access to the network. The Ambient loT Device may determine that RACH is successful, or is not successful, based on receiving a message from the network.

[0022] A broadcast message from a base station or reader is an example of an AS message.

[0023] Reference to a first RACH procedure and second RACH procedure and / or to a RACH procedure includes the same procedure being performed again by the same or different device as would be understood by those possessing an ordinary skill in the art

[0024] A system, device and method are disclosed. The method may be performed in an Ambient loT device (AloT device). The method includes receiving a first message including a group identifier and a response number, determining that the group identifier in the received first message matches a group identifier configured in the AloT device, and performing a first random-access channel (RACH) procedure. The method further includes on a condition that the performed first RACH procedure fails to successfully complete and the response number is below a first threshold relative to a number of times a RACH procedure for a device configured with the group identifier fails to successfully complete, waiting for a second message. The method further includes on a condition that the performed first RACH procedure fails to successfully complete and the response number is above a second threshold relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete, performing a second RACH procedure. The method further includes on a condition that the performed first RACH procedure or the second RACH procedure successfully completed, sending a response message. The received first message may further include a throttle indication and based on the throttle indication, the performed first RACH procedure if unsuccessful is repeated until successful. The group identifier may include a network operator Identifier configured to enable the AloT device to determine if the AloT device is configured with the identifier. The group identifier may include an owner identifier configured to enable the AloT device to determine if the AloT device is configured with the owner identifier. The response message may include an identifier of the AloT device. Being below a first threshold comprises the response number being sufficiently small relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete. For example, the AloT device may count the number of times that a RACH procedure fails (i.e. count the number of times that RACH failure is detected). The AloT device may compare the number of times that a RACH procedure failedto the response number. The comparison may involve multiplying a scale factor value by the response number. The scale factor value may be pre-configured in the AloT device or received by the AloT device in a configuration message. The scale factor value may be based on the type of AloT device and / or how quickly other AloT devices in the group are likely to respond to an inventory request. For example, the response number may be 100 and the scale factor value may be 0.2. A scale factor 0.2 may be used if it is likely that 20 devices can respond to the inventory request in the time that it takes for 1 RACH procedure to fail. In this example, after each RACH failure event, the AloT device may compare the number of times that a RACH failure was detected to the multiplication of the scale factor and the response number. The AloT device may determine to reattempt the RACH procedure if the number of times that a RACH failure was detected is equal to or below the result of the multiplication. In other words, the AloT device may determine that the response number is sufficiently small relative to the number of times a RACH procedure failed because the number of times that RACH failure was detected is greater than 20. Based on determining that the response number is sufficiently small relative to the number of times a RACH procedure failed, the AloT device may determine to wait for a second message. Being above a second threshold comprises the response number being sufficiently large relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete. In this example, if the AloT device determines that the threshold is 20 the AloT device may reattempt the RACH procedure if the number of times that RACH failure was detected is greater than 20. In other words, the AloT device may determine that the response number is sufficiently large relative to the number of times a RACH procedure failed because the number of times that RACH failure was detected is less than or equal to 20. Based on determining that the response number is sufficiently large relative to the number of times a RACH procedure failed, the AloT device may determine to perform a second RACH procedure. The first threshold and the second threshold may be equal. The response number may be configured to enable the AloT device to detect when a response is no longer necessary. The response number may be received from a base station (BS). The first message may further include a time-out value indicating a time period for collecting responses before acting. The response number may include a number that indicates a limit on a number of times a RACH procedure fails to successfully complete before stopping the performance of a RACH procedure, and waiting for a second message.

[0025] The device may be an Ambient loT device (AloT device). The AloT device may include a processor and associated memory, and a transceiver operably coupled to the processor. The processor and transceiver configured to receive a first message including a group identifier and a response number, determine that the group identifier in the received first message matches a group identifier configured in the AloT device, and perform a first random-access channel (RACH) procedure The device, on a condition that the performed first RACH procedure fails to successfully complete and the response number is below a first threshold relative to a number of times a RACH procedure for a device configured with the group identifier fails to successfully complete, may wait for a second message. The device, on a condition that the performed first RACH procedure fails to successfully complete and the response number is above a second threshold relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete, mayperform a second RACH procedure. The device, on a condition that the performed first RACH procedure or the second RACH procedure successfully completed, may send a response message. The received first message may further include a throttle indication and based on the throttle indication, the performed first RACH procedure if unsuccessful is repeated until successful. The group identifier may include a network operator Identifier configured to enable the AloT device to determine if the AloT device is configured with the identifier. The group identifier may include an owner identifier configured to enable the AloT device to determine if the AloT device is configured with the owner identifier The response message may include an identifier of the AloT device. Being below a first threshold comprises the response number being sufficiently small relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete. Being above a second threshold comprises the response number being sufficiently large relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete. The first threshold and the second threshold may be equal. The response number may be configured to enable the AloT device to detect when a response is no longer necessary The response number may be received from a base station (BS) The first message may further include a time-out value indicating a time period for collecting responses before acting. The response number may include a number that indicates a limit on a number of times a RACH procedure fails to successfully complete before stopping the performance of a RACH procedure, and waiting for a second message.

[0026] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), singlecarrier FDMA (SC-FDMA), zero-tail unique-word discrete Fourier transform Spread OFDM (ZT-UW-DFT-S- OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0027] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN) 104, a core network (ON) 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though itwill be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a station (STA), may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fl device, an Internet of Things (loT) device, a watch or otherwearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0028] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a NodeB, an eNode B (eNB), a Home Node B, a Home eNode B, a next generation NodeB, such as a gNode B (gNB), a new radio (NR) NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0029] The base station 114a may be part of the RAN 104, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, and the like. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to as a cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0030] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0031] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+).HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed Uplink (UL) Packet Access (HSUPA).

[0032] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0033] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access , which may establish the air interface 116 using NR.

[0034] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g , an eNB and a gNB).

[0035] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e , Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0036] The base station 114b in FIG 1A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106.

[0037] The RAN 104 may be in communication with the CN 106, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shownin FIG. 1A, it will be appreciated that the RAN 104 and / or the CN 106 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 or a different RAT. For example, in addition to being connected to the RAN 104, which may be utilizing a NR radio technology, the CN 106 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0038] The CN 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and / or the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

[0039] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1 A may be configured to communicate with the base station 114a, which may employ a cellularbased radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0040] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1 B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0041] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0042] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, thetransmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0043] Although the transmit / receive element 122 is depicted in FIG. 1 B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0044] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11 , for example.

[0045] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit) The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0046] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li- ion), etc.), solar cells, fuel cells, and the like.

[0047] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated thatthe WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment

[0048] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a handsfree headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors. The sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor, an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, a humidity sensor and the like.

[0049] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e g., associated with particular subframes for both the UL (e.g., for transmission) and DL (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e g., for transmission) or the DL (e g., for reception)).

[0050] FIG. 1C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0051] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

[0052] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0053] The CN 106 shown in FIG. 1C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (PGW) 166. While the foregoing elements aredepicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0054] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA

[0055] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0056] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0057] The CN 106 may facilitate communications with other networks For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

[0058] Although the WTRU is described in FIGS. 1A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily or permanently) wired communication interfaces with the communication network.

[0059] In representative embodiments, the other network 112 may be a WLAN.

[0060] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA The traffic between STAs within a BSS may be considered and / or referred to as peer-to-peer traffic. The peer-to- peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct linksetup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad-hoc” mode of communication.

[0061] When using the 802.11ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example in 802.11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0062] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0063] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two noncontiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately The streams may be mapped on to the two 80 MHz channels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0064] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11ah relative to those used in 802.11n, and 802.11ac. 802.11 af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11 ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non-TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control / Machine- Type Communications (MTC), such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g , only support for) certain and / or limited bandwidths The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0065] WLAN systems, which may support multiple channels, and channel bandwidths, such as 802 11 n, 802.11ac, 802.11 at, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs in operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode) transmitting to the AP, all available frequency bands may be considered busy even though a majority of the available frequency bands remains idle.

[0066] In the United States, the available frequency bands, which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for 802.11 ah is 6 MHz to 26 MHz depending on the country code.

[0067] FIG. 1 D is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0068] The RAN 104 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 104 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0069] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing a varying number of OFDM symbols and / or lasting varying lengths of absolute time).

[0070] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non- standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, 102c.

[0071] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, DC, interworking between NR and E-UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0072] The CN 106 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0073] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different protocol data unit (PDU) sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of non-access stratum (NAS) signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for MTC access, and the like The AMF 182a, 182b may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0074] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 106 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 106 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing DL data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernet-based, and the like.

[0075] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 104 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering DL packets, providing mobility anchoring, and the like.

[0076] The CN 106 may facilitate communications with other networks For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local DN 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0077] In view of FIGs. 1A-1 D, and the corresponding description of FIGs. 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0078] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network The emulation device may be directly coupled to another device for purposes of testing and / or performing testing using over-the-air wireless communications.

[0079] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, theemulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be test equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0080] In some scenarios it may be desirable to only inventory a few Ambient loT Devices. For example, an AF may need check the location of a pallet of Ambient loT Devices In such a scenario, it is only necessary for a few devices to respond to the inventory request before the AF has sufficient information to infer the location of the pallet. The network could broadcast a combination of the Home Network Identifier and Owner Identifier in order to solicit a response from all devices that share the same Home Network Identifier and Owner Identifier. However, this approach may result in responses from many more devices than what is required

[0081] Mechanisms are desired to allow the network to limit the number of devices that respond to an inventory request and for devices to detect when it is necessary to respond to an inventory request.

[0082] A reader, or base station, may broadcast information that indicates what group of devices it needs to collect inventory information from and how many devices it needs to respond. In a RACH procedure, the devices use the information about how many devices need to respond to determine to detect that a sufficient number of devices have responded. Once the device determines that a sufficient number of devices have responded, the device can stop performing the RACH procedure and determine that a response is not necessary. Thus, each device that receives an AS request message may attempt a RACH procedure at least once, but some devices may be able to detect that the RACH procedure does not need to be attempted again if the RACH attempt fails.

[0083] Optimization of inventory procedures are described. An inventory procedure is a procedure where an Ambient loT Device responds to the network with an identifier of the Ambient loT Device in order to indicate the Ambient loT Device’s presence. The procedures deal with how devices can detect if they need to respond (i.e., if other devices have provided a sufficient number of responses to the network).

[0084] Optimized read procedures are described. For example, a read procedure may be a procedure where an Ambient loT Device responds to the network with an Ambient loT Device identifier and application layer information such as a sensor reading. The procedure may apply where the network only needs to collect sensor readings from a percentage, such as 10%, of a group of Ambient loT Devices.

[0085] FIG. 2 illustrates an example procedure 200 illustrating AF initiating an inventory operation. A desired response number is used by devices in the procedure to detect when a response is no longer necessary. FIG. 3, in conjunction with FIG. 2, illustrates an example 300 of how an Ambient loT Device may use the desired response number to detect when a response is no longer necessary When an Ambient loT Device determines that a response is no longer necessary, the Ambient loT Device may stop attempting to perform a RACH procedure and / or stop attempting to send an AS response. The Ambient loT Device may determine that a response is no longer necessary because the Ambient loT Device detects that enough otherAmbient loT Devices have responded to the request from the network and that the network therefore no longer needs to obtain information from the Ambient loT Device.

[0086] FIG. 2 illustrates an example inventory procedure 200. Procedure 200 includes an AloT device 210 in communication with a BS 220, including a BS or a reader, an AloTF 230, including an AMF or a AloTF, a NEF 240 and an AF 250. As will be provided in greater detail below, procedure 200 at 205 includes AF 250 sending an NEF inventory request to NEF 240. NEF 240, at 215, sends an AMF inventory request to AloTF 230. AloTF 230, at 225 sends a N2 inventory request to BS 220. At 235, BS 220 sends an access stratum request to AloT device 210. AloT device 210, at 245, performs a RACH and determines whether AloT device 210 needs to respond to the reader. At 255, AloT device 210 sends an access stratum response to BS 220. BS 220, at 265, aggregates the access stratum responses from a plurality of AloT devices. At 275, BS 220 sends an N2 inventory response to AloTF 230. At 285, AMF / AloTF 230 sends an AMF inventory response to NEF 2540. At 295, NEF 240 sends an NEF inventory response to AF 250.

[0087] As a precondition to procedure 200, AloT device 210 may be pre-configured with an identifier. The identifier may include a Network Operator Identifier, an Owner Identifier, and an Instance Identifier As a precondition to procedure 200, AloT device may be configured with information that can be used to determine what RACH resources are allocated to other Ambient loT Devices that are part of the same Ambient loT Device Group as AloT device 210. For example, the RACH resources may be allocated to devices that share the same Network Operator Identifier and Owner Identifier.

[0088] At 205, AF 250 invokes an NEF API to request that certain Ambient loT Devices be inventoried The request may include the identity of a group of devices that need to be inventoried. For example, the group ID may be a combination of a Home Network identifier and an Owner Identifier. Thus, the request may indicate that Ambient loT Devices that are associated with the Home Network identifier and an Owner Identifier be inventoried. The request may also include a desired response number. The desired response number indicates the number of Ambient loT Devices that AF 250 desires responses from. For example, it may be the case that 10,000 devices share the same Home Network identifier and an Owner Identifier but AF 250 desires response from any 50 of the 10,000 devices. In this sense and in this example, the word desire refers to the fact that AF 250 requires a response from at least 50 devices for AF 250 to consider the responses to provide useful information. For example, if AF 250 is collecting environmental reading, AF 250 may require at least 50 readings before AF 250 considers the collected information to be a sufficiently large sample size. The request may also indicate a time out value that represents how long the network should collect responses before providing a response For example, the time out value may be used to indicate that the network should respond within the time value even if the desired number of responses have not been received.

[0089] At 215, N EF 240 may invoke an API of a network function to request that the network function initiate the inventory command. The network function that the request is sent to may be AMF 230 or network function that is tasked with interfacing with Ambient loT Devices. Such a network function may be called an Ambient loT Function (AloTF 230). NEF 240 may determine to send the request to multiple network functions. Forexample, it may be that more than one network serves the Ambient loT Devices. In such a scenario, NEF 240 may indicate a different desired response number to each network function. For example, if the desired response number that was received from AF 250 was 50, then NEF 240 may indicate a desired response number of 30 to one network function and a desired response number of 20 to a second network function. The time out value may also be provided to the network function.

[0090] At 225, the network function (e.g., AloTF 230) sends an inventory request to BS 220, or reader, device. The request includes the group ID and a desired response number and the time out value.

[0091] At 235, BS 220 sends an access stratum message. The message may be a broadcast message. The message may include one or more of the following information. The message may include a Home Network Identifier. The message may include an Owner Identifier. The message may include a throttle indication. The throttle indication is an indication that responses are not needed from all devices that share the same Home Network Identifier and Owner Identifier. The message may include a desired response number. The presence of the desired response number may be the throttle indication Alternatively, the desired response number can be a number that indicates a limit on the number of RACH failures that the AloT Device may detect before stopping the RACH procedure and waiting for a new access stratum message.

[0092] At 245, AloT device 210 receives a AS message and determines whether AloT device 210 needs to respond to the BS 220. FIG. 3 illustrates an example procedure 300 for an AloT device to determine whether to respond to the AS message at 245 of FIG 2. FIG. 3 shows an example of the steps that may be performed by AloT device 210 when receiving the AS message at 235. At 310, AloT device 210 may wait to receive a new AS message. At 320, AloT device 210 may receive the AS message. At 330, AloT device 210 may check if the Home Network Identifier and Owner Identifier in the broadcast message matches a Home Network Identifier and Owner Identifier that is provisioned in AloT device 210 If the Home Network Identifier and Owner Identifier in the broadcast message does not match a Home Network Identifier and Owner Identifier that is provisioned in AloT device 210, then AloT device 210 may determine that it does not need to respond to the message and may return to 310 to wait for a new AS message. If the Home Network Identifier and Owner Identifier in the broadcast message does match a Home Network Identifier and Owner Identifier that is provisioned in AloT device 210, then AloT device 210 may determine that a response to the message may be necessary. For example, when AloT device 210 detects that the Home Network Identifier and Owner Identifier in the broadcast messages does not match the match a Home Network Identifier and Owner Identifier values that are provisioned in AloT device 210 , then AloT device 210 may determine that the message was not broadcasted by a network that AloT device 210 is associated with and determine that AloT device 210 should therefore not respond. If AloT device 210 determines that it may need to respond to the message, then AloT device 210 proceeds at 340 to check the rest of the information in the AS message to determine whether or not AloT device 210 may attempt to respond to the message.

[0093] Additionally, the Owner Identifier may be partitioned into two fields. One field may identity the owner and the second field may identity a group of devices that the owner is permitted to control In such aconfiguration, AloT device 210 may determine that a response is needed when the broadcasted identifier matches owner identifier and group identifier that is provisioned in AloT device 210.

[0094] Additionally, the Instance Identifier may be partitioned into two fields. One field may identify a group of devices that the owner is permitted to control, and the second field may indicate the device. In such a configuration, AloT device 210 may determine that a response is needed when the broadcasted identifier matches a group identifier that is provisioned in AloT device 210.

[0095] At 340, AloT device 210 may check if the AS Message includes a throttle indication. If the AS message does not include a throttle indication, then AloT device 210 may determine that it needs to respond regardless of how many other devices respond to the request. AloT device 210 may then proceed to perform a RACH procedure, at 350, until the AloT successfully gains access to the channel. Once AloT device 210 gains access to the channel (i.e., the RACH procedure is successful), AloT device 210 may proceed to send the AS Response at 360.

[0096] If the AS message does include a throttle indication, then AloT device 210 may perform a RACH procedure. However, if the RACH procedure is not successful, AloT device 210 may proceed to 370. An example why the RACH procedure might not have been successful is that the RACH procedure was simultaneously being performed by a second AloT Device and the second AloT device was granted access to channel. In other words, the RACH procedure may have not been successful because a second AloT device was already using the channel to respond to the AS message or a second AloT device was already given access to the channel to respond to the AS message.

[0097] At 380, AloT device 210 may check the desired response number that was received at 235 in the access stratum message. In other words, AloT device 210 may compare the number of RACH failures to the desired response number that was received at 235. Alternatively, AloT device 210 may have been configured with a re-try factor. The re-try factor may be pre-configured in AloT device 210 with AloT device 210 identity or the re-try factor may be received from the network in a configuration message. This configuration message may be provided separate from the procedures discussed herein as would be understood in the art. AloT device 210 may perform a mathematical calculation where the re-try factor and the desired response number are inputs to the calculation and the result of the calculation may be compared to the number of RACH failures.

[0098] If the desired response number is not sufficiently high compared the number of RACH failures at 380, then AloT device 210 may determine that a sufficient response number of AloT Devices have likely already responded and return to 310 to wait for another AS Message to be received. For example, if the desired response number was 1, AloT device 210 may determine that another AloT Device has already responded (i.e., whatever device was given access to the channel at 370).

[0099] If the desired response number is sufficiently high compared the number of RACH failures at 380, then AloT device 210 may determine that a sufficient response number of AloT Devices have not likely already responded to and return to 370 to perform a RACH procedure again to attempt to obtain access to the channel so that a response may be sent by AloT device 210.

[0100] For example, AloT device 210 may count the number of times that a RACH procedure fails (i.e., count the number of times that RACH failure is detected). AloT device 210 may compare the number of times that a RACH procedure failed to the response number. The comparison may involve multiplying a scale factor value by the response number. The scale factor value may be pre-configured in AloT device 210 or received by AloT device 210 in a configuration message The scale factor value may be based on the type of AloT device and / or how quickly other AloT devices in the group are likely to respond to an inventory request. For example, the response number may be 100 and the scale factor value may be 0.2. A scale factor 0.2 may be used if it is likely that 20 devices can respond to the inventory request in the time that it takes for 1 RACH procedure to fail. In this example, after each RACH failure event, AloT device 210 may compare the number of times that a RACH failure was detected to the multiplication of the scale factor and the response number. AloT device 210 may determine to reattempt the RACH procedure if the number of times that a RACH failure was detected is equal to or below the result of the multiplication. In other words, AloT device 210 may determine that the response number is sufficiently small relative to the number of times a RACH procedure failed because the number of times that RACH failure was detected is greater than 20. Based on determining that the response number is sufficiently small relative to the number of times a RACH procedure failed, AloT device 210 may determine to wait for a second message.

[0101] While the scale factor of 0.2 is provided in the example, based on 20 devices responding to the inventory request in the time for a RACH procedure to fail, this scale factor may, in other examples, be 1, 10, 30, 40, 50, 100, 1000, and 10,000, for example. This variation would be understood by those possessing an ordinary skill in the art, and may be based on the number of devices responding to the inventory request in the rime for the RACH procedure to fail. Multiples of the number of device responding may be used, such as 0.1, 0.5, 2, 4, 8, 16 times for example, to set the scale factor

[0102] In an example, if AloT device 210 determines that the threshold is 20, AloT device 210 may reattempt the RACH procedure if the number of times that RACH failure was detected is greater than 20. In other words, AloT device 210 may determine that the response number is sufficiently large relative to the number of times a RACH procedure failed because the number of times that RACH failure was detected is less than or equal to 20. Based on determining that the response number is sufficiently large relative to the number of times a RACH procedure failed, AloT device 210 may determine to perform a second RACH procedure.

[0103] Returning again also to FIG. 2, at 255, AloT device 210 sends an AS Message in response to the access stratum request of 235 The message includes an identity of AloT device 210. For example, the identity of AloT device 210 may include the Home Network Identifier, the Owner Identifier, and the Instance Identifier. In an example, 255 may be included within or as part of the RACH procedure For example, the purpose of the inventory command may be to check for the presence of devices. AloT device 210 may transmit a message during the RACH procedure that identifies AloT device 210.

[0104] At 265, BS 220 may aggregate responses from multiple devices. For example, stations 220 may wait until it receives a number of responses that is equal to the desired response number that was received at225 or stations 220 may aggregate responses until the time out value is reached. Alternatively, reception of a response from an AloT device may trigger BS 220 to broadcast a new AS Request message. The new AS Request message may be different than the message at 235 because it may include a different desired response number. For example, if the base station has received responses from 4 different AloT devices, then stations 220 may send a new AS Request message that includes a desired response value that is 4 less than the desired response value that was sent at 225.

[0105] At 275, stations 220 may send an N2 Inventory Response to the network function, i.e., AMF or AloTF 230. The N2 Inventory Response may include a list of the identifiers of the AloT Devices that responded.

[0106] At 285 and 295, the list that was sent from stations 285 is forwarded to NEF 240 and to AF 250.

[0107] In the procedure 200 of FIG. 2 and procedure 300 of FIG. 3, AloT device 210 may check if the desired response number is sufficiently high in order to determine whether or not to attempt the RACH procedure again. Before the procedure 200 of FIG. 2 and procedure 300 of FIG. 3 are performed, AloT device 210 may be configured with a number, or policy, that is used to determine if the desired response number is sufficiently high. For example, AloT device 210 may be configured with a policy that indicates that the RACH procedure may be re-attempted a given number of times, such as up to 5 times, if the desired response number is less than 10 and may be re-attempted a higher number of times, such as up to 12 times, if the desired response number is 100. In other words, the policy may configure the AloT device to stop attempting to the to gain access to the channel after 5 failures if the desired response number is less than 10. AloT device 210 may be configured with the policy during the manufacturing process, or AloT device 210 may receive the policy from the network.

[0108] The desired response number may be a value that AloT device 210 converts to a number that represents the number of times that AloT device 210 may attempt the RACH procedure before determining that it is not necessary for AloT device 210 to respond to the network.

[0109] Alternatively, AloT device 210 may be provisioned with the RACH or response determination function which may take the desired response number as an input parameter along with AloT device 210 Home Network Identifier, Owner Identifier and Instance identifier, contextual information (e.g., time of the day, battery information), AloT command type to determine the number of times that AloT device 210 needs to attempt the RACH / Response procedure it needs to carry out before giving up. For example, this function may be an operation wherein AloT device 210 may exclusive OR (xOR) the desire response number with the device instance identifier and positive outcomes may be assigned different RACH values as compared to negative outcomes. In an example, this function may be used to create a delay in the response from AloT device 210, to ensure the resources are not overloaded via simultaneous attempts from all the devices.

[0110] FIG. 4 illustrates a method 400 of WTRU Actions that may be performed by AloT device 210. Illustrated in 235 of FIG. 2 and 320 of FIG. 3, method 400 may include receiving an access stratum message at 410. The message may include a group identifier, a throttle indication, and a desired response number The group identifier includes a Network Operator Identifier and an Owner Identifier.

[0111] In an example, illustrated in 330 and 340 of FIG. 3, method 400 may include determining that the group identifier in the access stratum message matches a group identifier that is configured in AloT device 210 and determining that the access stratum message includes a throttle indication at 420.

[0112] In an example, illustrated in 370 of FIG. 3, method 400 may include determining that a RACH procedure has failed at 430.

[0113] In an example illustrated in 380 and 310 of FIG. 3, method 400 may include, based on the RACH procedure failing and based on the desired response number being sufficiently small, determining to not send an AS Message and wait for a new AS message at 440.

[0114] As set forth above as an example, at 380, AloT device 210 may check the desired response number that was received at 235 in the access stratum message. In other words, AloT device 210 may compare the number of RACH failures to the desired response number that was received at 235. Alternatively, AloT device 210 may have been configured with a re-try factor. The re-try factor may be pre-configured in AloT device 210 with AloT device 210 identity or the re-try factor may be received from the network in a configuration message. This configuration message may be provided separate from the procedures discussed herein as would be understood in the art. AloT device 210 may perform a mathematical calculation where the re-try factor and the desired response number are inputs to the calculation and the result of the calculation may be compared to the number of RACH failures.

[0115] If the desired response number is not sufficiently high compared the number of RACH failures at 380, then AloT device 210 may determine that a sufficient response number of AloT Devices have likely already responded and return to 310 to wait for another AS Message to be received. For example, if the desired response number was 1 , AloT device 210 may determine that another AloT Device has already responded based on detecting a RACH failure (i.e., whatever device was given access to the channel at 370).

[0116] If the desired response number is sufficiently high compared the number of RACH failures at 380, then AloT device 210 may determine that a sufficient response number of AloT Devices have not likely already responded and return to 370 to perform a RACH procedure again to attempt to obtain access to the channel so that a response may be sent by AloT device 210.

[0117] For example, AloT device 210 may count the number of times that a RACH procedure fails (i.e., count the number of times that RACH failure is detected). AloT device 210 may compare the number of times that a RACH procedure failed to the response number. The comparison may involve multiplying a scale factor value by the response number. The scale factor value may be pre-configured in AloT device 210 or received by AloT device 210 in a configuration message The scale factor value may be based on the type of AloT device and / or how quickly other AloT devices in the group are likely to respond to an inventory request. For example, the response number may be 100 and the scale factor value may be 0.2. A scale factor 0.2 may be used if it is likely that 20 devices can respond to the inventory request in the time that it takes for 1 RACH procedure to fail. In this example, after each RACH failure event, AloT device 210 may compare the number of times that a RACH failure was detected to the multiplication of the scale factor and the response number.AloT device 210 may determine to reattempt the RACH procedure if the number of times that a RACH failure was detected is equal to or below the result of the multiplication. In other words, AloT device 210 may determine that the response number is sufficiently small relative to the number of times a RACH procedure failed because the number of times that RACH failure was detected is greater than 20. Based on determining that the response number is sufficiently small relative to the number of times a RACH procedure failed, AloT device 210 may determine to wait for a second message.

[0118] In an example, if AloT device 210 determines that the threshold is 20, AloT device 210 may reattempt the RACH procedure if the number of times that RACH failure was detected is greater than 20. In other words, AloT device 210 may determine that the response number is sufficiently large relative to the number of times a RACH procedure failed because the number of times that RACH failure was detected is less than or equal to 20. Based on determining that the response number is sufficiently large relative to the number of times a RACH procedure failed, AloT device 210 may determine to perform a second RACH procedure.

[0119] In an example illustrated in 380 and 370 of FIG. 3, method 400 may include, based on the RACH procedure failing based on the desired response number being sufficiently large, determining to perform the RACH procedure again at 450.

[0120] In an example, illustrated in 370 and 360 of FIG. 3 , method 400 may include, based on the RACH procedure succeeding, sending an AS response message at 460. The AS response message include an identifier of AloT device 210. The identifier includes an instance identifier.

[0121] FIG. 5 includes a method 500 of BS / Reader Actions that may be performed by BS such as BS 220. Illustrated at 225 of FIG. 2, method 500 may include receiving an inventory request message from a network function at 510. The message may include a group identifier, a throttle indication, and a desired response number. The inventory request may also indicate a time out value that represents how long the network should collect responses before providing a response. As set forth above as an example, at 225, the network function (e g., AloTF 230) sends an inventory request to BS 220, or reader, device. The request includes the group ID and a desired response number and the time out value.

[0122] In an example, illustrated at 235 of FIG. 2 and 320 of FIG. 3, method 500 may include sending an access stratum message at 520. The message may include a group identifier, a throttle indication, and a desired response number. The group identifier may include a Network Operator Identifier and an Owner Identifier. As set forth above as an example, at 235, BS 220 sends an access stratum message. The message may be a broadcast message. The message may include one or more of the following information. The message may include a Home Network Identifier. The message may include an Owner Identifier. The message may include a throttle indication. The throttle indication is an indication that responses are not needed from all devices that share the same Home Network Identifier and Owner Identifier. The message may include a desired response number. The presence of the desired response number may be the throttle indication. Alternatively, the desired response number can be a number that indicates a limit on the number of RACHfailures that the AloT Device may detect before stopping the RACH procedure and waiting for a new access stratum message.

[0123] In an example, illustrated at 255 of FIG. 2, method 500 may include receiving an AS response message at 530 The AS response message may include an identifier of the Ambient loT Device. As set forth above as an example, at 255, AloT device 210 sends an AS Message in response to the access stratum request of 235. The message includes an identity of AloT device 210. For example, the identity of AloT device 210 may include the Home Network Identifier, the Owner Identifier, and the Instance Identifier. In an example, 255 may be included within or as part of the RACH procedure. For example, the purpose of the inventory command may be to check for the presence of devices. AloT device 210 may transmit a message during the RACH procedure that identifies AloT device 210. As set forth above as an example, at 265, BS 220 may aggregate responses from multiple devices. For example, stations 220 may wait until it receives a number of responses that is equal to the desired response number that was received at 225 or stations 220 may aggregate responses until the time out value is reached. Alternatively, reception of a response from an AloT device may trigger BS 220 to broadcast a new AS Request message. The new AS Request message may be different than the message at 235 because it may include a different desired response number. For example, if the base station has received responses from 4 different AloT devices, then stations 220 may send a new AS Request message that includes a desired response value that is 4 less than the desired response value that was sent at 225.

[0124] In an example, illustrated at 265 in FIG 2, method 500 may include aggregating responses from multiple Ambient loT Devices until it has received a number of responses that is equal to the desired response number at 540.

[0125] In an example, illustrated at 275 of FIG. 2, method 500 may include sending the aggregated responses to the network function at 550. As set forth above as an example, at 275, stations 220 may send an N2 Inventory Response to the network function, i.e., AMF or AloTF 230. The N2 Inventory Response may include a list of the identifiers of the AloT Devices that responded.

[0126] Although features and elements are described above in particular combinations, one of ordinary skill in the art will appreciate that each feature or element can be used alone or in any combination with the other features and elements. In addition, the methods described herein may be implemented in a computer program, software, or firmware incorporated in a computer-readable medium for execution by a computer or processor. Examples of computer-readable media include electronic signals (transmitted over wired or wireless connections) and computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magnetooptical media, and optical media such as CD-ROM disks, and digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims

CLAIMSWhat is Claimed:

1. A method performed in an Ambient loT device (AloT device), the method comprising: receiving a first message including a group identifier and a response number; determining that the group identifier in the received first message matches a group identifier configured in the AloT device; performing a first random-access channel (RACH) procedure; and on a condition that the performed first RACH procedure fails to successfully complete and: the response number is below a first threshold relative to a number of times a RACH procedure for a plurality of devices configured with the group identifier fails to successfully complete, waiting for a second message; or the response number is above a second threshold relative to the number of times a RACH procedure for the plurality of devices configured with the group identifier fails to successfully complete, performing a second RACH procedure; and on a condition that the performed first RACH procedure or the second RACH procedure successfully completed, sending a response message.

2. The method of claim 1 , wherein the received first message further includes a throttle indication and based on the throttle indication, the performed first RACH procedure if unsuccessful is repeated until successful.

3. The method of claim 1 or 2, wherein the group identifier includes a network operator Identifier configured to enable the AloT device to determine if the AloT device is configured with the identifier.

4. The method of any of claims 1 to 3, wherein the group identifier includes an owner identifier configured to enable the AloT device to determine if the AloT device is configured with the identifier.

5. The method of any of claims 1 to 4, wherein the response message includes an identifier of the AloT device.

6. The method of any of claims 1 to 5, wherein being below a first threshold comprises the response number being sufficiently small relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete.

7. The method of any of claims 1 to 6, wherein being above a second threshold comprises the response number being sufficiently large relative to the number of times a RACH procedure for a device configured with the group identifier fails to successfully complete.

8. The method of any of claims 1 to 7, wherein the first threshold and the second threshold are equal.

9. The method of any of claims 1 to 8, wherein the response number is configured to enable the AloT device to detect when a response is no longer necessary.

10. The method of any of claims 1 to 9, wherein the response number is received from a base station (BS).

11. The method of any of claims 1 to 10, wherein the first message further includes a time-out value indicating a time period for collecting responses before acting.

12. The method of any of claims 1 to 11 , wherein the response number includes a number that indicates a limit on a number of times a RACH procedure fails to successfully complete before stopping the performance of a RACH procedure, and waiting for a second message.

13. An Ambient loT device (AloT device) comprising: a processor and associated memory; and a transceiver operably coupled to the processor, the processor and transceiver configured to: receive a first message including a group identifier and a response number; determine that the group identifier in the received first message matches a group identifier configured in the AloT device; perform a first random-access channel (RACH) procedure; and on a condition that the performed first RACH procedure fails to successfully complete and:the response number is below a first threshold relative to a number of times a RACH procedure for a plurality of devices configured with the group identifier fails to successfully complete, wait for a second message; or the response number is above a second threshold relative to the number of times a RACH procedure for the plurality of devices configured with the group identifier fails to successfully complete, perform a second RACH procedure; and on a condition that the performed first RACH procedure or the second RACH procedure successfully completed, send a response message.

14. The device of claim 13, wherein the received first message further includes a throttle indication and based on the throttle indication, the performed first RACH procedure if unsuccessful is repeated until successful.

15. The device of claim 13 or 14, wherein the group identifier includes at least one of network operator identifier or an owner identifier configured to enable the AloT device to determine if the AloT device is configured with the identifier.

16. The device of any of claims 13 to 15, wherein the response message includes an identifier of the AloT device.

17. The device of any of claims 13 to 16, wherein the first threshold and the second threshold are equal.

18. The device of any of claims 13 to 17, wherein the response number is configured to enable the AloT device to detect when a response is no longer necessary.

19. The device of any of claims 13 to 18, wherein the received first message further includes a time-out value indicating a time period for collecting responses before acting.

20. The device of any of claims 13 to 19, wherein the response number includes a number that indicates a limit on a number of a RACH procedure fails to successfully complete before stopping the performance of a RACH procedure, and waiting for a new message.

Images