Event exposure for AIOT services
The AloT reader device addresses communication challenges in battery-less IoT devices by monitoring and notifying on events like overload, latency, and coverage issues, ensuring efficient and reliable AloT system operation.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-09-19
- Publication Date
- 2026-04-09
AI Technical Summary
Existing wireless communication networks face challenges in facilitating efficient communication between ambient Internet of Things (IoT) devices and application servers, particularly in scenarios where battery-less IoT devices lack power for continuous communication, and there is a need for effective event monitoring and notification mechanisms to manage device overload, latency, positioning, and out-of-coverage issues.
Implementing an AloT reader device that monitors for specific events such as reader overload, device-reader latency, positioning capability, and out-of-coverage events, and transmits notifications to designated entities when these events occur, using a wireless communication network that supports 5G technology to manage these events effectively.
Enables efficient communication and event management for battery-less AloT devices by providing timely notifications and managing network load, reducing latency, and ensuring reliable positioning and coverage, thereby enhancing the functionality of AloT systems.
Smart Images
Figure EP2025076832_09042026_PF_FP_ABST
Abstract
Description
EVENT EXPOSURE FOR AIOT SERVICESRELATED APPLICATIONS
[0001] This patent application claims the benefit of priority of Indian Patent Application No. 202441075108 filed October 4, 2024, which is hereby incorporated by reference as if reproduced in their entirety.
[0002] FIELD OF TECHNOLOGY
[0003] The present disclosure relates to providing notifications for ambient internet of things (AloT) events over a wireless communication network to external application functions.
[0004] BACKGROUND
[0005] Internet of things (loT) device refers to an everyday object embedded with sensors, software and a network interface which enables these objects to collect data and send data to and receive data from other devices via a communication network. Ambient loT (AloT) devices refers to loT devices that are powered by a component that harvests energy, for example, a capacitor, that is provided by another device and used to power the AloT device for communication. Thus, an AloT device does not have a battery and can store only a limited amount of energy that is used to power the AloT device for communications.
[0006] AloT devices complement existing loT devices by providing loT-like devices in contexts in which, for example, power, charging, or regularly replacing batteries of loT devices would be impractical. Some use cases leveraging Ambient loT devices include, for example, ID tags, similar to RFID but with a wider range, sensors such as, for example, temperature and humidity sensors, healthcare devices used, for example, for monitoring personal medical information, tracking objects in logistics contexts.
[0007] A system of AloT devices may include one or more AloT devices, an activator or illuminator that sends an activation signal to wake up the one or more AloT devices by providing energy that allows each of the one or more AloT devices to transmit messages and / or data, a reader, or receiver, that listens and detects messages and / or data sent by the one or more AloT devices, an AloT controller, and a AloT application server. The reader may be collocated with the activator, such as, for example, within the same device that is configured as both the activator and reader, or may be located at a location that differs from the location of the activator.
[0008] It is desirable to enable a wireless communication network, for example, a wireless communication network that operates in accordance with the 5th generation radio access technology described in the 3rdGeneration Partnership Project (3GPP) standard for new radio, to facilitate communication between application servers and AloT devices.
[0009] Developments in AloT communication between AloT devices and an application server via a wireless communication network is desirable.SUMMARY
[0010] According to one aspect of an embodiment, the present disclosure provides A method of an ambient internet of things (AloT) reader device, the method includes receiving, from an AloT function (AloTF) of a communication network, an AloT event subscription, the AloT event subscription comprising an AloT event identifier that identifies an AloT event that the AloT reader device is to monitor and information identifying a destination entity to notify, monitoring for occurrences of the AloT event, in response to monitoring an occurrence of the AloT event, transmitting an AloT event notification to the destination entity to indicate the occurrence of the AloT event, the AloT event notification including the AloT event identifier, and an identifier of the AloT reader device, where the AloT event consists of one of: an AloT reader overload event, wherein the AloT reader overload event occurs when a load measurement at the AloT reader device is greater than or equal to a load measurement threshold for the AloT reader device, a device-reader latency event, wherein the device-reader latency event occurs when a latency of responses received at the AloT reader device from a particular AloT device is equal to or greater than a threshold latency for receiving response at the AloT device, wherein the AloT event notification includes an identifier of the particular AloT device for which the devicereader latency event occurred, a positioning capability event, wherein the positioning capability event occurs when the AloT reader device is capable of performing positioning according to a positioning criteria, or an out- of-coverage event, wherein the out-of-coverage event occurs when a response from a particular AloT device associated with the AloT reader device is not received at the AloT reader device within a predetermined time period or after a predetermined number of messages sent by the AloT reader device to the particular AloT device, wherein the AloT event subscription includes identifiers for one or more AloT devices including the particular AloT device.
[0011] In an example, when the AloT event comprises the AloT reader overload event, and the AloT event subscription received at the AloT reader device includes the load measurement threshold, when the AloT event comprises the device-reader latency event, the AloT event subscription message includes the threshold latency, when the AloT event comprises the positioning capability event, the AloT event subscription includes the positioning criteria, and when the AloT event comprises the out-of-coverage event, he AloT event subscription includes the predetermined time period or the predetermined number of messages.
[0012] In an example, the AloT event comprises the AloT reader overload event, and the load measurement threshold is one of: a utilization amount of a central processing unit (CPU) of the AloT reader device, wherein the load measurement is an amount of processing capacity of the CPU that is utilized, a storage space utilization amount of a memory of the AloT reader device, wherein the load measurement is an amount of storage space of the memory that is utilized, an average processing time for the CPU of the AloT reader device to process responses from AloT devices, wherein the load measurement is an average processing time for the CPU of the AloT reader device to process responses from AloT devices, or a charge remaining amount for a battery of the AloT reader device, wherein the load measurement is an amount of charge remaining in the battery.
[0013]
[0014] In an example, the AloT event comprises the positioning capability event, and the positioning criteria comprises one or more of: the AloT reader device being enabled by a location management function (LMF) of the wireless communication system to perform positioning, the AloT reader device being enabled by an end user of the AloT reader device to perform positioning, or subscription an available processing capacity of a central processing unit (CPU) of the AloT reader device meets or exceeds a processing threshold to support the positioning capability.
[0015] In an example, the AloT event subscription is included in an AloT service request.
[0016] In an example, the AloT event subscription includes aperiodicity time, and in response to monitoring an occurrence of the AloT event, periodically transmitting to the destination entity, with a periodicity of the periodicity time: a current value of the load measurement when the AloT event is the AloT reader overload event, and a current value of the latency of responses received at the AloT reader device from the AloT device when the AloT event is the device-reader latency event.
[0017] According to another aspect of an embodiment, the present disclosure provides An AloT reader device including at least one processor, and at least one memory storing instructions which, when executed by the at least one processor, cause the AloT reader device to receive, from an AloT function (AloTF) of a communication network, an AloT event subscription, the AloT event subscription comprising an AloT event identifier that identifies an AloT event that the AloT reader device is to monitor and information identifying a destination entity to notify, monitor for occurrences of the AloT event, and in response to monitoring an occurrence of the AloT event, transmit an AloT event notification to the destination entity to indicate the occurrence of the AloT event, the AloT event notification including the AloT event identifier, and an identifier of the AloT reader device, where the AloT event consists of one of: an AloT reader overload event, wherein the AloT reader overload event occurs when a load measurement at the AloT reader device is greater than or equal to a load measurement threshold for the AloT reader device, a device-reader latency event, wherein the device-reader latency event occurs when a latency of responses received at the AloT reader device from a particular AloT device is equal to or greater than a threshold latency for receiving response at the AloT device, wherein the AloT event notification includes an identifier of the particular AloT device for which the devicereader latency event occurred, a positioning capability event, wherein the positioning capability event occurs when the AloT reader device is capable of performing positioning according to a positioning criteria, or an out- of-coverage event, wherein the out-of-coverage event occurs when a response from a particular AloT device associated with the AloT reader device is not received at the AloT reader device within a predetermined time period or after a predetermined number of messages sent by the AloT reader device to the particular AloT device, wherein the AloT event subscription includes identifiers for one or more AloT devices including the particular AloT device.
[0018] In an example, when the AloT event comprises the AloT reader overload event, and the AloT event subscription received at the AloT reader device includes the load measurement threshold, when the AloT event comprises the device-reader latency event, the AloT event subscription message includes the threshold latency, when the AloT event comprises the positioning capability event, the AloT event subscriptionincludes the positioning criteria, and when the AloT event comprises the out-of-coverage event, he AloT event subscription includes the predetermined time period or the predetermined number of messages.
[0019] In an example, the AloT event comprises the AloT reader overload event, and the load measurement threshold is one of: a utilization amount of a central processing unit (CPU) of the AloT reader device, wherein the load measurement is an amount of processing capacity of the CPU that is utilized, a storage space utilization amount of a memory of the AloT reader device, wherein the load measurement is an amount of storage space of the memory that is utilized, an average processing time for the CPU of the AloT reader device to process responses from AloT devices, wherein the load measurement is an average processing time for the CPU of the AloT reader device to process responses from AloT devices, or a charge remaining amount for a battery of the AloT reader device, wherein the load measurement is an amount of charge remaining in the battery.
[0020] In an example, the AloT event comprises the positioning capability event, and the positioning criteria comprises one or more of: the AloT reader device being enabled by a location management function (LMF) of the wireless communication system to perform positioning, the AloT reader device being enabled by an end user of the AloT reader device to perform positioning, or subscription an available processing capacity of a central processing unit (CPU) of the AloT reader device meets or exceeds a processing threshold to support the positioning capability.
[0021] In an example, the AloT event subscription is included in an AloT service request.
[0022] In an example, the AloT event subscription includes a periodicity time, and in response to monitoring an occurrence of the AloT event, and the instructions, when executed by a processor of the AloT device cause the processor to periodically transmit to the destination entity, with a periodicity of the periodicity time: a current value of the load measurement when the AloT event is the AloT reader overload event, and a current value of the latency of responses received at the AloT reader device from the AloT device when the AloT event is the device-reader latency event.
[0023] In an example, the AloT reader device comprises a user equipment.
[0024] According to another aspect of an embodiment, the present disclosure provides a computer-readable medium storing instructions, wherein when the instructions are executed by at least one processor of an ambient internet of things (AloT) reader device, cause the AloT reader device to receive, from an AloT function (AloTF) of a communication network, an AloT event subscription, the AloT event subscription comprising an AloT event identifier that identifies an AloT event that the AloT reader device is to monitor and information identifying a destination entity to notify, monitor for occurrences of the AloT event, and in response to monitoring an occurrence of the AloT event, transmit an AloT event notification to the destination entity to indicate the occurrence of the AloT event, the AloT event notification including the AloT event identifier, and an identifier of the AloT reader device, where the AloT event consists of one of: an AloT reader overload event, wherein the AloT reader overload event occurs when a load measurement at the AloT reader device is greater than or equal to a load measurement threshold for the AloT reader device, a device-reader latency event, wherein the device-reader latency event occurs when a latency of responses received at the AloTreader device from a particular AloT device is equal to or greater than a threshold latency for receiving response at the AloT device, wherein the AloT event notification includes an identifier of the particular AloT device for which the device-reader latency event occurred, a positioning capability event, wherein the positioning capability event occurs when the AloT reader device is capable of performing positioning according to a positioning criteria, or an out-of-coverage event, wherein the out-of-coverage event occurs when a response from a particular AloT device associated with the AloT reader device is not received at the AloT reader device within a predetermined time period or after a predetermined number of messages sent by the AloT reader device to the particular AloT device, wherein the AloT event subscription includes identifiers for one or more AloT devices including the particular AloT device.
[0025] In an example, when the AloT event comprises the AloT reader overload event, and the AloT event subscription received at the AloT reader device includes the load measurement threshold, when the AloT event comprises the device-reader latency event, the AloT event subscription message includes the threshold latency, when the AloT event comprises the positioning capability event, the AloT event subscription includes the positioning criteria, and when the AloT event comprises the out-of-coverage event, he AloT event subscription includes the predetermined time period or the predetermined number of messages.
[0026] In an example, the AloT event comprises the AloT reader overload event, and the load measurement threshold is one of: a utilization amount of a central processing unit (CPU) of the AloT reader device, wherein the load measurement is an amount of processing capacity of the CPU that is utilized, a storage space utilization amount of a memory of the AloT reader device, wherein the load measurement is an amount of storage space of the memory that is utilized, an average processing time for the CPU of the AloT reader device to process responses from AloT devices, wherein the load measurement is an average processing time for the CPU of the AloT reader device to process responses from AloT devices, or a charge remaining amount for a battery of the AloT reader device, wherein the load measurement is an amount of charge remaining in the battery.
[0027] In an example, the AloT event comprises the positioning capability event, and the positioning criteria comprises one or more of: the AloT reader device being enabled by a location management function (LMF) of the wireless communication system to perform positioning, the AloT reader device being enabled by an end user of the AloT reader device to perform positioning, or subscription an available processing capacity of a central processing unit (CPU) of the AloT reader device meets or exceeds a processing threshold to support the positioning capability.
[0028] In an example, the AloT event subscription is included in an AloT service request.
[0029] In an example, the AloT event subscription includes a periodicity time, and in response to monitoring an occurrence of the AloT event, and the instructions, when executed by a processor of the AloT device cause the processor to periodically transmit to the destination entity, with a periodicity of the periodicity time: a current value of the load measurement when the AloT event is the AloT reader overload event, and a current value of the latency of responses received at the AloT reader device from the AloT device when the AloT event is the device-reader latency event.
[0030] According to another aspect of an embodiment, the present disclosure provides a computer program comprising instructions, wherein the instructions when the executed by at least one processor of an ambient internet of things (AloT) reader device, cause the AloT reader device to receive, from an AloT function (AloTF) of a communication network, an AloT event subscription, the AloT event subscription comprising an AloT event identifier that identifies an AloT event that the AloT reader device is to monitor and information identifying a destination entity to notify, monitor for occurrences of the AloT event, and in response to monitoring an occurrence of the AloT event, transmit an AloT event notification to the destination entity to indicate the occurrence of the AloT event, the AloT event notification including the AloT event identifier, and an identifier of the AloT reader device, where the AloT event consists of one of: an AloT reader overload event, wherein the AloT reader overload event occurs when a load measurement at the AloT reader device is greater than or equal to a load measurement threshold for the AloT reader device, a device-reader latency event, wherein the device-reader latency event occurs when a latency of responses received at the AloT reader device from a particular AloT device is equal to or greater than a threshold latency for receiving response at the AloT device, wherein the AloT event notification includes an identifier of the particular AloT device for which the device-reader latency event occurred, a positioning capability event, wherein the positioning capability event occurs when the AloT reader device is capable of performing positioning according to a positioning criteria, or an out-of-coverage event, wherein the out-of-coverage event occurs when a response from a particular AloT device associated with the AloT reader device is not received at the AloT reader device within a predetermined time period or after a predetermined number of messages sent by the AloT reader device to the particular AloT device, wherein the AloT event subscription includes identifiers for one or more AloT devices including the particular AloT device.
[0031] In an example, when the AloT event comprises the AloT reader overload event, and the AloT event subscription received at the AloT reader device includes the load measurement threshold, when the AloT event comprises the device-reader latency event, the AloT event subscription message includes the threshold latency, when the AloT event comprises the positioning capability event, the AloT event subscription includes the positioning criteria, and when the AloT event comprises the out-of-coverage event, he AloT event subscription includes the predetermined time period or the predetermined number of messages.
[0032] In an example, the AloT event comprises the AloT reader overload event, and the load measurement threshold is one of: a utilization amount of a central processing unit (CPU) of the AloT reader device, wherein the load measurement is an amount of processing capacity of the CPU that is utilized, a storage space utilization amount of a memory of the AloT reader device, wherein the load measurement is an amount of storage space of the memory that is utilized, an average processing time for the CPU of the AloT reader device to process responses from AloT devices, wherein the load measurement is an average processing time for the CPU of the AloT reader device to process responses from AloT devices, or a charge remaining amount for a battery of the AloT reader device, wherein the load measurement is an amount of charge remaining in the battery.
[0033] In an example, the AloT event comprises the positioning capability event, and the positioning criteriacomprises one or more of: the AloT reader device being enabled by a location management function (LMF) of the wireless communication system to perform positioning, the AloT reader device being enabled by an end user of the AloT reader device to perform positioning, or subscription an available processing capacity of a central processing unit (CPU) of the AloT reader device meets or exceeds a processing threshold to support the positioning capability.
[0034] In an example, the AloT event subscription is included in an AloT service request.
[0035] In an example, the AloT event subscription includes a periodicity time, and in response to monitoring an occurrence of the AloT event, and the instructions, when executed by a processor of the AloT device cause the processor to periodically transmit to the destination entity, with a periodicity of the periodicity time: a current value of the load measurement when the AloT event is the AloT reader overload event, and a current value of the latency of responses received at the AloT reader device from the AloT device when the AloT event is the device-reader latency event.
[0036] According to another aspect of an embodiment, the present disclosure provides a method of a core network of a communication network, the method includes receiving at a network exposure function (NEF) of the core network, from an application function (AF), an ambient internet of things (AloT) event subscription request, the AloT event subscription request includes an AloT event identifier that identifies an AloT event to monitor for, and information that identifies one or more of a area to monitor for the AloT event, one or more AloT device identifiers, or one or more AloT reader device identifiers, determining by the NEF, based on the information that identifies one or more of the area, the one or more AloT device identifiers, or the one or more AloT reader device identifiers included in the AloT event subscription request, an AloT function (AloTF) of the core network and transmitting the AloT event subscription request to the AloTF, determining by the AloTF at least one target AloT reader device based on the information that identifies one or more of the area, the one or more AloT device identifiers, or the one or more AloT reader device identifiers included in the AloT event subscription request, transmitting, by the AloTF to the at least one target AloT reader device, an AloT event subscription, the AloT event subscription includes the AloT event identifier that identifies the AloT event for the AloT reader device to monitor for and information identifying the AF to notify; subscription receiving at the AloTF from one of the at least one target AloT reader device an AloT event notification directed to the AF and indicating the occurrence of the AloT event, the AloT event notification including the AloT event identifier , and an identifier of the one of the at least one target AloT reader device, transmitting, by the AloTF to the AF, the AloT event notification, where the AloT event consists of one of: an AloT reader overload event, wherein the AloT reader overload event occurs when a load measurement at the AloT reader device is greater than or equal to a load measurement threshold, a device-reader latency event, wherein the device— reader latency of response event occurs when a latency of responses received at the AloT reader device from a particular AloT device is equal to or greater than a threshold latency, wherein the AloT event notification includes an identifier of the particular AloT device for which the device-reader latency event occurred, a positioning capability event, wherein the positioning capability event occurs when the AloT reader device is capable of performing positioning according to a positioning criteria, or an out-of-coverage event, wherein the out-of-coverage eventoccurs when a response from a particular AloT device is not received at the AloT reader device within a predetermined time period or after a predetermined number of messages sent by the AloT reader device to the particular AloT device, wherein the AloT event subscription includes identifiers for one or more Alot devices including the particular AloT device.
[0037] In an example, when the AloT event comprises the AloT reader overload event, and the AloT event subscription includes the load measurement threshold, when the AloT event comprises the device-reader latency , the AloT event subscription includes the threshold latency, when the AloT event comprises the positioning capability event, the AloT event subscription includes the positioning criteria, and when the AloT event comprises the out-of-coverage event, the AloT event subscription includes the predetermined time period or the predetermined number of messages.
[0038] In an example, the AloT event comprises the AloT reader overload event, and the load measurement threshold is one of: a utilization amount of a central processing unit (CPU) of the AloT reader device, wherein the load measurement is an amount of processing capacity of the CPU that is utilized, a storage space utilization amount of a memory of the AloT reader device, wherein the load measurement is an amount of storage space of the memory that is utilized, an average processing time for the CPU of the AloT reader device to process responses from AloT devices, wherein the load measurement is an average processing time for the CPU of the AloT reader device to process responses from AloT devices, or a charge remaining amount for a battery of the AloT reader device, wherein the load measurement is an amount of charge remaining in the battery.
[0039] In an example, the AloT event comprises the positioning capability event, and the positioning criteria comprises one or more of: the AloT reader device being enabled by a location management function (LMF) of the wireless communication system to perform positioning, the AloT reader device being enabled by an end user of the AloT reader device to perform positioning, or subscription an available processing capacity of a central processing unit (CPU) of the AloT reader device meets or exceeds a processing threshold to support the positioning capability.
[0040] In an example, the AloT event subscription request is included in an AloT service request.
[0041] In an example, the AloT event subscription request includes information identifying one or more AloT device identifiers, and determining, by the AloTF, the least one target AloT reader device comprises determining, for each of the one or more AloT device identifiers, an AloT reader device identifier associated with that AloT device identifier utilizing binding information stored in a memory associated with the AloTF, the binding information including pairings of AloT device identifiers and their corresponding AloT reader device identifiers.
[0042] In an example, the AloT event comprises the out-of-coverage event, the method further includes in response to the AloTF receiving the AloT event notification indicating that the particular AloT device is out-of- coverage from the at least one target AloT reader device, updating the stored binding information to remove the binding information for the particular AloT device identifier.
[0043] In an example, the method further includes, in response to receiving the AloT event notification fromthe one of the at least one target AloT reader devices, updating context information associated with the one of the at least one AloT reader devices stored at a memory associated with the AloTF to include information related to the one of the at least one AloT devices and associated with the occurrence of the AloT event.
[0044] According to another aspect of an embodiment, the present disclosure provides a system of a communication network, the system including a network exposure function (NEF) comprising a means for receiving from an application function (AF), an ambient internet of things (AloT) event subscription request, the AloT event subscription request includes an AloT event identifier that identifies an AloT event to monitor for, and information that identifies one or more of an area to monitor for the AloT event, one or more AloT device identifiers, or one or more AloT reader device identifiers, a means for determining, based on the information that identifies one or more of the area, the one or more AloT device identifiers, or the one or more AloT reader device identifiers included in the AloT event subscription request, an AloT function (AloTF) of the core network and transmitting the AloT event subscription request to the AloTF, and an AloTF comprising a means for determining at least one target AloT reader device based on the information that identifies one or more of the area, the one or more AloT device identifiers, or the one or more AloT reader device identifiers included in the AloT event subscription request, a means for transmitting to the at least one target AloT reader device, an AloT event subscription, the AloT event subscription includes the AloT event identifier that identifies the AloT event for the AloT reader device to monitor for and information identifying the AF to notify, a means for receiving at the AloTF from one of the at least one target AloT reader device an AloT event notification directed to the AF and indicating the occurrence of the AloT event, the AloT event notification including the AloT event identifier , and an identifier of the one of the at least one target AloT reader device, a means for transmitting, by the AloTF to the AF, the AloT event notification, where the AloT event consists of one of: an AloT reader overload event, wherein the AloT reader overload event occurs when a load measurement at the AloT reader device is greater than or equal to a load measurement threshold, a device-reader latency event, wherein the device— reader latency of response event occurs when a latency of responses received at the AloT reader device from a particular AloT device is equal to or greater than a threshold latency, wherein the AloT event notification includes an identifier of the particular AloT device for which the device-reader latency event occurred, a positioning capability event, wherein the positioning capability event occurs when the AloT reader device is capable of performing positioning according to a positioning criteria, or an out-of-coverage event, wherein the out-of-coverage event occurs when a response from a particular AloT device is not received at the AloT reader device within a predetermined time period or after a predetermined number of messages sent by the AloT reader device to the particular AloT device, wherein the AloT event subscription includes identifiers for one or more AloT devices including the particular AloT device.
[0045] In an example, when the AloT event comprises the AloT reader overload event, and the AloT event subscription includes the load measurement threshold, when the AloT event comprises the device-reader latency , the AloT event subscription includes the threshold latency, when the AloT event comprises the positioning capability event, the AloT event subscription includes the positioning criteria, and when the AloT event comprises the out-of-coverage event, the AloT event subscription includes the predetermined timeperiod or the predetermined number of messages.
[0046] In an example, the AloT event comprises the AloT reader overload event, and the load measurement threshold is one of: a utilization amount of a central processing unit (CPU) of the AloT reader device, wherein the load measurement is an amount of processing capacity of the CPU that is utilized, a storage space utilization amount of a memory of the AloT reader device, wherein the load measurement is an amount of storage space of the memory that is utilized, an average processing time for the CPU of the AloT reader device to process responses from AloT devices, wherein the load measurement is an average processing time for the CPU of the AloT reader device to process responses from AloT devices, or a charge remaining amount for a battery of the AloT reader device, wherein the load measurement is an amount of charge remaining in the battery.
[0047] In an example, the AloT event comprises the positioning capability event, and the positioning criteria comprises one or more of: the AloT reader device being enabled by a location management function (LMF) of the wireless communication system to perform positioning, the AloT reader device being enabled by an end user of the AloT reader device to perform positioning, or an available processing capacity of a central processing unit (CPU) of the AloT reader device meets or exceeds a processing threshold to support the positioning capability.
[0048] In an example, the AloT event subscription request is included in an AloT service request.
[0049] In an example, the AloT event subscription request includes information identifying one or more AloT device identifiers, and the AloTF comprising the means determining the least one target AloT reader device comprises the AloTF comprising a means for determining, for each of the one or more AloT device identifiers, an AloT reader device identifier associated with that AloT device identifier utilizing binding information stored in a memory associated with the AloTF, the binding information including pairings of AloT device identifiers and their corresponding AloT reader device identifiers.
[0050] In an example, the AloT event comprises the out-of-coverage event, the AloTF further including a means for, in response to the AloTF receiving the AloT event notification indicating that the particular AloT device is out-of-coverage from the at least one target AloT reader device, updating the stored binding information to remove the binding information for the particular AloT device identifier.
[0051] In an example, the AloTF further including a means for, in response to receiving the AloT event notification from the one of the at least one target AloT reader devices, updating context information associated with the one of the at least one AloT reader devices stored at a memory associated with the AloTF to include information related to the one of the at least one AloT devices and associated with the occurrence of the AloT event.
[0052] According to another aspect of an embodiment, the present disclosure provides a method for a core network of a communication network, the method includes receiving at a network exposure function (NEF) of the core network from application function (AF), an ambient internet of things (AloT) event subscription request, the AloT event subscription request includes an AloT event identifier that identifies an AloT event to monitor for, and one or more AloT device identifiers associated with the AloT event, determining by the NEF,based on the one or more AloT device identifiers included in the AloT event subscription request, an AloT function (AloTF) of the core network and transmitting the AloT event subscription request to the AloTF, determining by the AloTF at least one target AloT reader device based on the information that identifies one or more AloT device identifiers included in the AloT event subscription request by determining, for each of the one or more AloT device identifiers, an AloT reader device identifier associated with that AloT device identifier utilizing binding information stored in a memory associated with the AloTF, the binding information including pairings of AloT device identifiers and their corresponding AloT reader device identifiers, determining by the AloTF, at least one access management function (AMF) of the core network based on the determined at least one target AloT reader device, transmitting by the AloTF to the at least one AMF an AloT event subscription, the AloT event subscription includes the AloT event identifier that identifies the AloT event for the AMF to monitor, information identifying the AF to notify and an identifier for each of the at least one target AloT reader devices, monitoring, by the at least one AMF, for occurrences of the AloT event, wherein the AloT event consists of one or more of: one of the at least one target AloT reader devices moves out of an area associated with the one or more AloT device identifiers that the one of the at least one target AloT reader devices is associated with based on the binding information, a response to a message sent by the AMF to one of the at least one target AloT reader devices is not received by the AMF from the one of the at least one target AloT reader devices within a predetermined time period or after the AMF has sent a predetermine number of messages, or a message from one of the at least one target AloT reader devices is received at the AMF, the message indicating that the one of the at least one target AloT reader devices did not receive a response from one or more AloT devices that the one of the at least one target AloT reader devices is associated with based on the binding information, in response to determining that the AloT event has occurred, transmitting by the AMF to the AloTF an AloT event notification directed to the AF and indicating the occurrence of the AloT event, the AloT event notification including the AloT event identifier, a cause of the AloT event occurrence, and one or both of the identifier of the one of the at least one AloT reader device and the identifiers of the at least one AloT device for which the AloT event occurred in association with, transmitting, by the AloTF to the AF, the AloT event notification.
[0053] In an example, when the cause included in the event notification indicates that the AloT event occurred when one of the at least one target AloT reader devices moved out of the location or that one of the at least one target AloT reader devices did not respond to the AMF, the method further comprises removing by the AloTF binding information associated with the one of the at least one target AloT reading device, and when the cause included in the event notification indicates that the AloT event occurred when one of the at least one target AloT reader devices did not receive a response from one of the one or more AloT devices, the method further comprises removing by the AloTF binding information associated with the one of the AloT devices.
[0054] In an example, in response to the AloTF receiving the AloT event notification from the AMF, the method further includes determining, by the AloTF, one or more affected AloT devices for which binding information is no longer valid based on the cause and the one or both of the identifier of the one of the at leastone AloT reader device and the identifiers of the at least one AloT device for which the AloT even occurred in association with, initiating by the AloTF an AloT reader device re-selection process for the one or more affected AloT devices to select an AloT reader device for each of the one or more affected AloT devices, and updating by the AloTF binding information for each of the one or more affected AloT devices to include the selected AloT reader device, and wherein the AloT event notification transmitted by the AloTF to the AF further includes the updated binding information for the one or more affected AloT devices.
[0055] According to another aspect of an embodiment, the present disclosure provides a method for a system for a communication network, the system including a network exposure function (NEF) comprising: a means for receiving from application function (AF), an ambient internet of things (AloT) event subscription request, the AloT event subscription request includes an AloT event identifier that identifies an AloT event to monitor for, and one or more AloT device identifiers associated with the AloT event, a means for determining, based on the one or more AloT device identifiers included in the AloT event subscription request, an AloT function (AloTF), and a means for transmitting the AloT event subscription request to the AloTF, an AloTF comprising: a means for determining at least one target AloT reader device based on the information that identifies one or more AloT device identifiers included in the AloT event subscription request by determining, for each of the one or more AloT device identifiers, an AloT reader device identifier associated with that AloT device identifier utilizing binding information stored in a memory associated with the AloTF, the binding information including pairings of AloT device identifiers and their corresponding AloT reader device identifiers, a means for determining by the AloTF, at least one access management function (AMF) based on the determined at least one target AloT reader device, a means for transmitting to the at least one AMF an AloT event subscription, the AloT event subscription includes the AloT event identifier that identifies the AloT event for the AMF to monitor, information identifying the AF to notify, and an identifier for each of the at least one target AloT reader devices, at least one AMF comprising: a means for monitoring for occurrences of the AloT event, wherein the AloT event consists of one or more of: one of the at least one target AloT reader devices moves out of an area associated with the one or more AloT device identifiers that the one of the at least one target AloT reader devices is associated with based on the binding information, a response to a message sent by the AMF to one of the at least one target AloT reader devices is not received by the AMF from the one of the at least one target AloT reader devices within a predetermined time period or after the AMF has sent a predetermined number of messages, or a message from one of the at least one target AloT reader devices is received at the AMF, the message indicating that the one of the at least one target AloT reader devices did not receive a response from one or more AloT devices that the one of the at least one target AloT reader devices is associated with based on the binding information, a means for, in response to determining that the AloT event has occurred, transmitting to the AloTF an AloT event notification directed to the AF and indicating the occurrence of the AloT event, the AloT event notification including the AloT event identifier, a cause of the AloT event occurrence, and one or both of the identifier of the one of the at least one AloT reader device and the identifiers of the at least one AloT device for which the AloT event occurred in association with, the AloTF further comprising a means for transmitting to the AF the AloT event notification received from one of the atleast one AMR
[0056] In an example, the AloTF further comprises a means for when the cause included in the event notification indicates that the AloT event occurred when one of the at least one target AloT reader devices moved out of the location or that one of the at least one target AloT reader devices did not respond to the AMF, removing by the AloTF binding information associated with the one of the at least one target AloT reading device, and when the cause included in the event notification indicates that the AloT event occurred when one of the at least one target AloT reader devices did not receive a response from one of the one or more AloT devices, removing by the AloTF binding information associated with the one of the AloT devices.
[0057] In an example, the AloTF further comprises: a means for, in response to the AloTF receiving the event notification from the AMF, determining one or more affected AloT devices for which binding information is no longer valid based on the cause and the one or both of the identifier of the one of the at least one AloT reader device and the identifiers of the at least one AloT device for which the AloT even occurred in association with, a means for initiating an AloT reader device re-selection process for the one or more affected AloT devices to select an AloT reader device for each of the one or more affected AloT devices, and a means for updating binding information for each of the one or more affected AloT devices to include the selected AloT reader device, and wherein the means for transmitting the AloT event notification to the AF further comprises a means for including the updated binding information for the one or more affected AloT devices in the AloT event notification.
[0058] The term "non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).BRIEF DESCRIPTION OF THE DRAWINGS
[0059] Embodiments of the present disclosure will now be described, by way of example only, with reference to the attached figures.
[0060] FIGS. 1Aand 1B are schematic diagrams showing communication between an ambient internet of things (AloT) device and a base station;
[0061] FIG. 2 is a schematic diagram showing a communication network in accordance with an aspect of an embodiment.
[0062] FIG. 3 is a flowchart showing a method for a system in accordance with an example embodiment.
[0063] FIG. 4 is a flowchart showing a method for an AloT reader device in accordance with an example embodiment.
[0064] FIGS. 5 and 6 are diagrams showing operations in procedures in accordance with some example embodiments.
[0065] FIGs. 7A and 7B are a flowchart showing a method for a system in accordance with an example embodiment.
[0066] FIG. 8 is a diagram showing operations in a procedure in accordance with some example embodiments.
[0067] FIG. 9 is a schematic diagram showing components of one or more of the example embodiments.DETAILED DESCRIPTION
[0068] For simplicity and clarity of illustration, reference numerals may be repeated among the figures to indicate corresponding or analogous elements. Numerous details are set forth to provide an understanding of the examples described herein. The examples may be practiced without these details. In other instances, well-known methods, procedures, and components are not described in detail to avoid obscuring the examples described. The description is not to be considered as limited to the scope of the examples described herein.
[0069] In general, communications between an AloT device and a base station of a wireless communication network can be implemented as, either, direct AloT communication in which the AloT device communicates directly with the base station, or indirect AloT communication in which the AloT device communicates with the base station via an intermediate node. FIG. 1 A shows a AloT device that communicates directly with the base station (BS) that is configured as a reader, referred to herein as the "AloT reader device”, for the AloT device. FIG. 1 B shows communication between an AloT device and a base station (BS) of the wireless communication network is via an intermediate node. The intermediate node transfers AloT signaling and / or data received from the base station to the AloT device or transfers AloT signaling and / or data received from the AloT device to the base station. The intermediate node may be referred to as the "AloT reader device” for indirect AloT communication.
[0070] In the present disclosure, "AloT communication” refers to signaling and / or data transmission to or from an AloT enabled device such as, for example, an AloT device or an AloT reader device, or that is related to transmission of signaling and / or data transmission to or from an AloT enabled device.
[0071] AloT services are provided by a wireless communication network to external application functions hosted on external application services. AloT communication is one example of an AloT service that is provided to an external application function to enable AloT communications with AloT devices via a base station of a wireless communication network that operates in accordance with the 5th generation radio access technology described in the 3rdGeneration Partnership Project (3GPP) standard for new radio, a base station that operates in accordance with the 3GPP standard for new radio may be configured to be an AloT reader device for direct AloT communication or a user equipment (UE) may be configured to be an intermediate node (e.g., an AloT reader device) for indirect AloT communication.
[0072] Reference is first made to FIG. 2, which shows a schematic representation of an example wireless communication network 200 that an AloT device 202 has access to in order to enable AloT communication with an external third party application functions (AF) 206 that may be hosted on an third party application server. The communication network 200 comprises a radio access network 208 (e.g., a NG-RAN) and a core network 210 (e.g., a 5G core network (5GC)) that operate based on the 5th generation radio access technology described in the 3GPP standard for new radio.
[0073] The radio access network (RAN) 208 comprises one or more radio access network (RAN) nodes (otherwise referred to as base stations), such as a gNodeB (gNB). A radio access network node may comprise a central unit (e.g., gNB-CU) and one or more distributed units (e.g., one or more gNB-DUs) linkedto the central unit (e.g., gNB-CU).
[0074] In examples in which AloT communication with the AloT device 202 is direct AloT communication, as described previously with reference to FIG. 1 A, the RAN 208 may be configured to function as the AloT reader device to facilitate communication between the AloT device 202 and the application function 206 via the core network 210. In other examples in which AloT communication with the AloT device 202 is indirect AloT communication, as described previously with reference to FIG. 1 B, wireless communication network 200 includes a UE 204 that is configured to function as the AloT reader device to facilitate communication between the AloT device 202 with the application function 206 via the RAN 208 and the core network 210.
[0075] The core network 210 has a service-based architecture and comprises a plurality of network functions (NFs), including, inter alia, an access and mobility function (AMF) 212, a trusted application function (AF) 214, a network exposure function (NEF) 216, a user data management system (UDM) 218, and a location management function 224 (LMF). Other network functions of the core network 208 are not illustrated but would be understood by a person skilled in the art. The functionalities of the network functions of the core network 210 are known to a person skilled in the art and hence are not described in detail.
[0076] Each network function (NF) of the core network 210 provides one or more services to other network functions of the core network via Application Programming Interfaces (APIs). Any NF is operable to consume (e.g., use) the services provided and exposed by another NF. A NF that consumes a service of another network function is generally referred to as a network function service consumer. A network function that provides and exposes one or more of its services is referred to as a network function service producer. In addition to the network functions referred to above, the core network 210 also includes a AloT function (AloTF) 222 that provides and exposes AloT services to an NF service consumer of the AloT services provided and exposed by the AloTF. "AloT services” as utilized in the present disclosure relates to any service that relates to an AloT enable device such as, for example, the AloT device 202 and an AloT reader device, which may be a gNB of the RAN 208 in direct AloT communication or a UE 204 in indirect AloT communication that is configured as an AloT reader device. The NEF 216 exposes services, including the AloT services provided and exposed by the AloTF 222, to the external AF 206.
[0077] In some examples the AloTF 222 and the NEF 216 may be combined into a single network function that performs the functionality of both an NEF and a AloTF, or the AloTF 222 and the NEF 216 may be implemented as separate network functions. The NEF 216 may act as an intermediatory and enables secure communication between the AloTF 222 and any external AFs, such as AF 206, that are located outside of the core network 210, whereas trusted AFs, such as AF 214, which are part of the core network 210, may communicate directly with the AloTF 222.
[0078] The network functions of the core network 210 described herein, including the AMF 112, the NEF 212, and the AloTF 222, or any network function that incorporates some or all of the functionality of the AMF, the NEF, and / or the AloTF, may be implemented as a combination of hardware processing circuit and software and / or firmware comprising machine-readable instructions that are executable by the hardware processing circuit, or software comprising machine-readable instructions that are executable by a hardware processingcircuit of an apparatus. A hardware processing circuit includes at least one processor comprising machine- readable instructions that are executable by the at least one processor of the hardware processing circuit and at least one memory storing the machine-readable instructions. A processor includes any or some combination of an accelerator, microprocessor, a core of a multi-core microprocessor, a microcontroller, a programmable integrated circuit, a programmable gate array, a digital signal processor, a central processing unit, a graphic processing unit, a tensor processing unit. Memory includes any or some combination of volatile or non-volatile memory (e.g., a flash memory, cache, a random-access memory (RAM), and / or a read-only memory (ROM)). The memory stores the machine-executable instructions of the software and / or firmware for execution by the at least one processor of the hardware processing circuit. The machine-executable instructions are executable by the hardware processing circuit to perform the actions or operations of the methods of the network functions core network 210 described herein, including the AMF 112, the NEF 212, and the AloTF 222 and / or the network function that incorporates any of the functionalities of the AMF 112, the NEF 212, and the AloTF 222 described herein.
[0079] In general, any network function of the core network 210, which may also be referred to as a network entity, may be implemented as: dedicated hardware comprising software; as a software instance running on a dedicated hardware; or as a virtualised function instantiated on dedicated hardware (e.g., a computing system) such as, for example, on a cloud computing system.
[0080] In accordance with the present disclosure, it is desirable to provide and expose to an external AF, such as the AF 206, AloT events such that an external AF may request to be notified of an occurrence of a specific event related to an AloT configured device, such as an AloT device 202 or an AloT reader device, such as a gNB of the RAN 208 or a UE 204 that is configured as AloT reader devices.
[0081] In general, a NF consumer may request to be notified of the occurrence of a specific event, which is referred to as "subscribing” to the event, and configuring a network function service producer to have a certain event available for other network entities or functions to subscribe to be notified of is referred to as "event exposure”. Conventional event exposure that may be consumed by external AFs, such as AF 206 described previously, is provided by the NEF, such as NEF 216, and is described in the clause 4.15.3 of V19.1 3GPP TS 23.502. Current event exposure to external AFs via the NEF does not contemplate providing event exposure in the context of events related to AloT enabled devices, such as for example, events related to AloT devices and AloT reader devices, i.e., AloT events. "AloT event” as used herein generally refers an event related to an AloT device and / or an AloT reader device that may be monitored by an element or an entity, such as a UE or a RAN node, or any network function of the wireless communication network, such as any NF of the core network. When the particular event occurs, a notification is provided to the entity that has subscribed to receive notifications of occurrences of the event.
[0082] The present disclosure describes methods, devices, and systems for providing AloT event exposure to external AFs, such as the example AF 206 described previously. The AloT event exposure to external AFs may provide useful information related to AloT devices and / or information related to AloT reader devices to the external AF, which may, for example, be used by the external AF to optimize the external AF's internallogic, for selecting appropriate AloT reader devices for particular AloT devices, or for charging the external AFs in relation to AloT communication.
[0083] The present disclosure describes the following new AloT events:
[0084] Referring to FIG. 3, a flowchart showing a method or process in accordance with one example is shown. The method or process is performed by system of a wireless communication network such as, for example, a system comprising the NEF 216, the AloTF 222, and the AMF 212 of the wireless communication system 200, or another system comprising network functions that incorporates the functionality of an NEF, an AMF, and an AloTF as described herein. As described in more detail below, the method or process illustrated in FIG. 3 enables an external AF, such as the example AF 206, to "subscribe” to be notified of occurrences of the example AloT events listed at No. 1-4 in the above table that are monitored by an AloT reader device, which include: an AloT reader overload event, related to no. 1 in the above table; a device-reader latency event, related to no. 2 in the above table; a positioning capability event, related to no. 3 in the above table; and an out-of-coverage event, related to no. 4 in the above table.
[0085] At 302, an AloT event subscription request is received at an NEF from an AF. The AloT event subscription request includes an AloT event identifier that identifies the AloT event that the AF is subscribing to, i.e., the AloT event that the AF is requesting to receive a notification upon the occurrence of. The AloT event identifier may be, for example, an alpha-numeric identifier that has previously been associated with, or assigned to, a particular AloT event.
[0086] The AloT event subscription request may includes additional information depending on the AloT event that is identified by the AloT event identifier. For example, the information may include one or more identifiers that identify one or more AloT devices, such as AloT devices 202 in the example communication network 200, for which the AF is subscribing to AloT event notifications in relation to. Alternatively or additionally, the AloT event subscription request may include one or more identifiers that identify one or more AloT reader devices, such as a UE 204 and / or a RAN 208, for which the AF is subscribing to event notifications in relation to. Alternatively or additionally, the AloT event subscription request may include information identifying one or more areas or locations, such as for example a geographical area or location, ora particular cell of the wireless communication network, for which the AF is subscribing to event notifications in relation to.
[0087] Alternatively or additionally, the AloT event subscription request may include information related to the reporting of the notifications that are sent upon the occurrence of the AloT event. Such information may include, for example, a time duration over which the AF is subscribing to the AloT event, a maximum number of occurrences of the AloT event that the AF wants to receive notifications of, a number of occurrences of the AloT event that must occur before a notification is sent, and a periodicity of reporting the AloT event or information related to the AloT event.
[0088] Alternatively or additionally, the AloT event subscription request may include information related to the monitoring of the particular AloT event that is being subscribed to. For example, if the occurrence of the AloT event depends on a particular threshold, or condition, or criteria to be met, then AloT event subscription request may optionally include information related to the particular threshold, or condition, or criteria to be met.
[0089] For example, an AloT reader overload event, related to no. 1 in the above table, may occur when a load measurement at the AloT reader device is greater than or equal to a load measurement threshold for the AloT reader device, and this load measurement threshold may be included in the AloT event subscription request for an AloT reader overload event.
[0090] In another example, a device-reader latency event, related to no. 2 in the table, may occur when a latency of responses received at the AloT reader device from a particular AloT device is equal to or greater than a threshold latency for receiving response at the AloT device, and this threshold latency may be included in the AloT event subscription request for a device-reader latency event.
[0091] In another example, a positioning capability event, related to no. 3 in the table, may occur when a AloT reader device is capable of performing a positioning according to a positioning criteria, and this positioning criteria may be included in the AloT event subscription request for a positioning capability event.
[0092] In another example, an out-of-coverage event, related to no. 3 in the above table, may occur when a response from a particular AloT device associated with the AoT reader device is not received at the AloT reader device within a predetermined time period or after a predetermined number of messages sent by the AloT reader device to the particular AloT device, and the predetermined time period or the predetermined number of messages may be included in the AloT event subscription request for an out-of-coverage event.
[0093] In some examples, the AloT event subscription request received at 302 is included in an AloT service request that is transmitted by the AF to request an AloT service such as, for example, an inventory of the AloT devices that are an identified area or location. An example of an AloT event subscription request included in an AloT service request is described in more detail with reference to FIG. 6.
[0094] The NEF, upon receiving the AloT event subscription request may determine whether the AF from which the AloT event subscription request was received from is authorized to subscribe to the AloT event identified by the AloT event identifier, either in general, or for any of the area, the AloT reader devices, or the AloT devices identified by any additional information included in the AloT event subscription request.
[0095] If the NEF determines that the AF is authorized to subscribe to the AloT event identified in the AloT event subscription request, the NEF, at 304, determines an AloTF to send the AloT event subscription request to. The determination of the AloTF may be based on determining an AloTF that is responsible for the AloT devices and / or AloT reader devices identified in the AloT event subscription request, or that are located at the area or location identified in the AloT event subscription request. The NEF then forwards the AloT event subscription request to the determined AloTF.
[0096] At 306, the AloTF determines at least one target AloT reader device based on the information included in the AloT event subscription request that is transmitted by the NEF at 304. As described previously, the AloT reader devices may be gNBs of a RAN, such as the example RAN 208 for direct AloT communication described with reference to FIG. 1 A, or may be a UE, such as UE 204, for indirect AloT communication described with reference to FIG. 1 B.
[0097] The determination of the at least one target AloT reader device may include determining the AloT reader devices located at an area or location identified in the AloT event subscription request utilizing location data that is stored in association with the AloT reader devices such as, for example, location information stored in association with gNBs that are utilized as AloT reader devices for direct AloT communication, and stored, such as in context information as described in more detail below, in association with UEs that are utilized as AloT reader devices in indirect AloT communication.
[0098] In examples in which the AloT event subscription request includes AloT device identifiers, then the AloTF may determine the one or more target AloT reader devices using a database of "binding information” that is maintained by the AloTF and stored, for example, at a memory associated with the AloTF.
[0099] Binding information is a mapping between an AloT device identifier and an identifier of an AloT reader device that is assigned to as the reader device for the AloT device associated with the AloT device identifier. Binding information may be utilized to, for example, determine which AloT reader device to utilize for communication with an AloT device. Binding information may be generated utilizing an AloT reader selection process in a discovery signal is sent to the AloT devices, then AloT reader devices that receive a response transmit to the AloTF a response that includes the AloT device identifiers of the AloT devices that they received response from. Based on the responses from the AloT reader devices, the AloTF may then select an AloT reader device for each of the AloT devices, and store this mapping as binding information. Generating the binding information may include selecting one of the UEs as a responsible UE when responses were received from multiple UEs for a given AloT device.
[0100] In examples in which the AloT event subscription request includes identifiers of AloT reader devices, then the AloTF may determine that these AloT reader devices identified in the AloT event subscription request as the at least one target AloT reader devices.
[0101] At 308, the AloTF transmits an AloT event subscription to the at least one target AloT reader device. The AloT event subscription includes the AloT event identifier, and includes information that identifies a destination entity to notify of the occurrence of the AloT event, i.e., the entity that the AloT event subscription request was received from, which is the AF.
[0102] The AloT event subscription may include additional information, depending on the AloT event identified by the AloT event identifier. For example, when the AloT event and out-of-coverage event, described previously and related to no. 4 of the above table, the AloT event subscription may include identifiers for one or more AloT devices for which the at least one AloT reader device is to monitor for the occurrence of the out-of-coverage event.
[0103] The AloT event subscription may also optionally include, for example, any thresholds, or conditions, or criteria to be met that are related to the particular AloT event identified by the AloT event identifier as described previously. These thresholds, or conditions, or criteria that may be optionally included may be thresholds, or conditions, or criteria that were optionally included in the AloT event subscription request that was received from the AF, or may be determined by the AloTF based on the AloT event identifier. These thresholds, or conditions, or criteria may then be utilized by the one or more AloT reader device for monitoring for an occurrence of the AloT event.
[0104] Alternatively, any thresholds, or conditions, or criteria that are related to the monitoring of the AloT event identified by the AloT event identifier may be pre-configured at the AloT reader device, or otherwise available such that the AloT reader device can determine the related thresholds, or conditions, or criteria based on the AloT event identifier.
[0105] The AloT event subscription may optionally include information related to the reporting of the notifications as previously described, which information may include, for example, a time duration over which the AF is subscribing to the AloT event, a maximum number of occurrences of the AloT event that the AF wants to receive notifications of, a number of occurrences of the AloT event that must occur before a notification is sent, and a periodicity of reporting the AloT event or information related to the AloT event.
[0106] The AloT event subscription may also include other information that identifies information or results that the at least one target AloT reader device is to include when reporting the occurrence of the AloT event. For example, in the case of the AloT reader overload event, the information may indicate that the AloT reader device is to report the load measurement that resulted in the AloT reader overload event. In the example of a device-reader latency event, the information may indicate that the AloT reader device is to report the latency of responses received at the AloT reader device. In the example of the out-of-coverage event, the information may indicate that the AloT reader device is to report the identifier of the particular AloT device(s) for which no response was received.
[0107] The at least one target AloT reader devices, upon receiving the AloT event subscription transmitted at 308, monitors for an occurrence of the AloT event identified by the AloT event identifier included in the AloT event subscription, as described in more detail below with reference to FIG. 4.
[0108] Upon an occurrence of the AloT event identified by the AloT event identified included in the AloT event subscription, an AloT event notification is received at the AloTF from one of the at least one target AloT reader devices that indicates the occurrence of the AloT event. The AloT event notification is directed to the destination entity identified in the AloT event subscription, i.e., the AF. The AloT event notification includes the AloT event identifier, and identifier of the one of the at least one AloT reader devices from which the AloTevent notification is received from.
[0109] The AloT event notification may include any results that are to be included the particular AloT event which as described previously may include, for example, the load measurement for the AloT reader overload event, a latency of responses for the device-reader latency event, or an identifier of the particular AloT device(s) for which no response was received for an out-of-coverage event.
[0110] Optionally at 312, the AloTF may update binding information stored at the AloTF, or may update context information associated with the AloT reader device from which the AloT event notification was received, or both, based on the AloT event notification.
[0111] For example, for a AloT event notification for an AloT reader overload event, the binding information associated with the AloT reader device from which the AloT event notification is received may be deleted and, optionally an AloT reader device re-selection process may be initiated for the AloT devices that were previously mapped to that AloT reader device to select new AloT reader devices for those AloT devices, and the binding information for those AloT devices updated based on the re-selection. Similarly, for an event notification for an out-of-context event, the binding information for the particular AloT device identified in the AloT event notification may be updated, which may include an AloT reader device re-selection process for the particular AloT device.
[0112] Alternatively or additionally, for UE that is configured as a AloT reader device (generally referred to as a UE AloT reader device), context information related to the UE AloT reader device from which the AloT event notification was received may be updated based on the AloT event notification. Context information related to the UE AloT reader device may be stored at, for example, in a UDM of the core network, such as the UDM 218 of the example wireless communication network 200 described previously, as part of the subscription information of the AloT reader device that is stored for UE AloT reader devices, and / or may be stored at an AMF, such as the AMF 212 of the example wireless communication network 200 described previously.
[0113] Generally, context information for a UE AloT reader device may include a subscriber identifier, an access type, and a security context of the UE. The present disclosure optionally adds one or more new information types to the context information that may indicate whether the UE is configured to, and / or is currently available to, act as an AloT reader device. Which context information may be useful to, for example, when the AloTF is assigning AloT reader devices to particular AloT devices. For example, for an AloT reader overload event, the context information related to the UE AloT reader device may be updated to include an indication (e.g., a flag or a bit value) that the AloT reader device is in an overloaded state and, optionally, to include the load measurement is the load measurement is included in the AloT event notification. In an example of a device-reader latency event, the context information related to a UE AloT reader device may be updated to indicate the latency condition is present for the AloT reader device. In an example of a positioning capability event, the context information related to the UE AloT reader device may be updated to indicate that positioning is enabled, or disabled, at the UE AloT reader device as the case may be.
[0114] At 314, the AloTF transmits the AloT event notification to the AF, which is the destination entity thatthe AloT event notification was directed to by the AloT reader device.
[0115] Referring to FIG. 4, a flowchart showing a method or process in accordance with one example is shown. The method or process is performed by an AloT reader device, which may be a base station (e.g., gNB) of a RAN, such as the RAN 208 of the example wireless communication system 200 described previously when an AloT device communicates directly with a base station communication as shown in FIG. 1 A, or may be intermediate node , such as the UE 204 of the example wireless communication network 200 described previously when the AloT device communicates with the base station (e.g., gNB) via the intermediate node as shown in FIG. 1 B. As described in more detail below, the method or process illustrated in FIG. 4 provides for the monitoring by an AloT reader device of the example AloT events listed at No. 1-4 in the above table, which include: an AloT reader overload event, related to no. 1 in the above table; a devicereader latency event, related to no. 2 in the above table; a positioning capability event, related to no. 3 in the above table; and an out-of-coverage event, related to no. 4 in the above table.
[0116] At 402, an AloT event subscription is received at the AloT reader device from an AloTF. The AloT event subscription that is received at 402 may be substantially similar to the AloT event subscription that is described previously with reference to 308 of FIG. 3, including all information that is included, or may optionally be included, in the AloT event subscription for different example AloT events.
[0117] At 404, the AloT reader device monitors for the occurrence of the AloT event identified by the AloT event identifier included in the AloT event subscription.
[0118] In the example of an AloT reader overload event, the AloT reader device monitors a load measurement of the AloT reader device and monitors that the event has occurred when the load measurement is greater than or equal to a load measurement threshold. In an example, the load measurement threshold includes one or more of a utilization amount of a central processing unit (CPU) of the AloT reader device, wherein the load measurement is an amount of processing capacity of the CPU that is utilized, a storage space utilization amount of a memory of the AloT reader device, wherein the load measurement is an amount of storage space of the memory that is utilized, an average processing time for the CPU of the AloT reader device to process responses from AloT devices, wherein the load measurement is an average processing time for the CPU of the AloT reader device to process responses from AloT devices, or a charge remaining amount for a battery of the AloT reader device, wherein the load measurement is an amount of charge remaining in the battery. As described previously, the load measurement threshold may be included in the AloT subscription, may be pre-configured at the AloT reader device, or may be determined by the AloT reader device based on the AloT event identifier.
[0119] In an example of a device-reader latency event, the AloT reader device monitors a latency of responses received at the AloT reader device from a particular AloT device and monitors that the event has occurred when the latency of the responses is equal to or greater than a threshold latency. As described previously, the threshold latency may be included in the AloT subscription, may be pre-configured at the AloT reader device, or may be determined by the AloT reader device based on the AloT event identifier.
[0120] In an example of a positioning capability event, the AloT reader device monitors whether it is capableof performing positioning according to a positioning criteria. In example, the positioning criteria comprises one or more of the AloT reader device being enabled by an LMF, such as the LMF 224 of the example wireless communication system 200 described previously, to perform positioning, the AloT reader device being enabled by an end user of the AloT reader device to perform positioning, or an available processing capacity of a central processing unit (CPU) of the AloT reader device meets or exceeds a processing threshold to support the positioning capability. As described previously, the positioning criteria may be included in the AloT subscription, may be pre-configured at the AloT reader device, or may be determined by the AloT reader device based on the AloT event identifier.
[0121] In an example of an out-of-coverage event, the AloT reader device monitors an occurrence of the out-of-coverage event when a response from a particular AloT device is not received within a predetermined time period or after a predetermined number of messages sent by the AloT reader device to the particular AloT device. As described previously, the AloT subscription may include identifiers of one or more AloT devices including the particular AloT device. Further, as previously described, predetermined time period and / or the predetermined number of messages may be included in the AloT subscription, may be preconfigured at the AloT reader device, or may be determined by the AloT reader device based on the AloT event identifier.
[0122] In response to monitoring an occurrence of the AloT event, an AloT event notification message is transmitted at 406. The AloT event notification message is directed to the destination entity identified in the AloT event subscription. The AloT event notification message includes the AloT event identifier and the identifier of the AloT reader device. The AloT event notification message may be transmitted at 406 in accordance with any information related to the reporting of AloT events that may optionally have been included in the AloT event subscription such as, for example, reporting only after a predetermine number occurrences of the AloT event have occurred.
[0123] The AloT event notification transmitted at 406 may optionally include additional information or results such as additional information that is requested to be reported in the AloT event subscription and / or that is required for the AloT event identified by the AloT event identifier, as previously described. For example, the AloT event notification may include, for example, the load measurement for the AloT reader overload event, a latency of responses for the device-reader latency event, or an identifier of the particular AloT device(s) for which no response was received for an out-of-coverage event.
[0124] In the event that the AloT event subscription contained information requesting periodic reporting of information related to the AloT event, then the information related to the AloT event is periodically reported. For example, the AloT event subscription may include a periodicity for such reporting, and the AloT reader device will report the information related to the AloT event with a periodicity of the periodicity time. The information related to the AloT event may include, for example, a current value of the load measurement when the AloT event is the AloT reader overload event, or a current value of the latency of responses received at the AloT reader device from the AloT device when the AloT event is the device-reader latency event. The reporting at 408 may be transmitted to the AloTF or the AF depending on the information that is included inthe AloT event subscription, and may be transmitted as a further AloT event notification message, or in some other form of reporting message.
[0125] Referring to FIG. 5, operations of an example procedure in accordance with an example embodiment is shown for providing AloT event notification to an AF for any of the example AloT events listed at No. 1-4 in the above table, which include: an AloT reader overload event, related to no. 1 in the above table; a devicereader latency event, related to no. 2 in the above table; a positioning capability event, related to no. 3 in the above table; and an out-of-coverage event, related to no. 4 in the above table. The operations described relate to messaging between an AloT device 502, an AloT reader device 504, an AMF 506, an AloTF 508, an NEF 510, and an external AF 512, which may be similar to the AloT device 202, where the AloT reader device 502 is either a base station of the RAN 208 or the UE 204 depending on whether the AloT device communicates directly or indirectly with the base station, the AMF 212, the AloTF 122, the NEF 216, and the AF 106, respectively, as described previously with reference to FIG. 2.
[0126] An AloT event subscription request 514 is transmitted by the AF 512 to the NEF 510. The AloT event subscription request 514 includes an AloT event identifier (ID) and identifiers of AloT reader devices or AloT devices that are related to the AloT event being subscribed to. The AloT event subscription request 514 may optionally include additional information related to reporting any AloT event notifications and / or threshold, condition, or criteria to be met related to the AloT event as described previously.
[0127] The NEF 510 may determine that the AF 512 is authorized to subscribe the requested AloT event, and if authorized forwards the AloT event subscription request 516 to the AloTF 508. At 518, the AloTF 508 determines at least one target AloT reader device as described previously with reference to 306. In the example shown, the AloTF 508 determines a target AloT reader device based on the information included in the AloT event subscription request 516. For example, the AloT event subscription request 514 may include, for example, a global public subscriber identifier (GPSI), or any other public identifier, for the AloT reader devices identified in the AloT event subscription request 514 and the AloTF 510 converts the public AloT reader device identifiers into, or otherwise determines, a non-public identifier, such as, for example, a subscription permanent identifier (SUPI) of the UE or gNB AloT reader devices that corresponds to the AloT reader device identifier. Based on the determined target AloT reader device, an AMF 506 for forwarding an AloT event subscription 520 is determined.
[0128] The AloT event subscription 520 is transmitted to the determined AMF 506, which forwards the AloT event subscription 520 to the target AloT reader device 504. The AloT event subscription 520 may be as described previously with reference to 308. The AloT event subscription 520 includes the AloT event identifier, and in the example shown, includes reporting information that may be utilized by the AloT reader device for reporting notifications of the occurrence of the AloT event as previously described.
[0129] At 522, the AloT reader device monitors the AloT event as described previously with reference to 404 and 406, and when the AloT event occurs, the AloT reader device 504 transmits an AloT event notification 524, which is forwarded by the AMF 506 to the AloTF 508. As described previously, the AloT event notification 524 is addressed, or directed to, by the AloT reader device to the destination entity, which in thiscase is the AF 512. The AloT event notification 524 includes the event identifier and, in the example AloT event notification 524 shown in FIG. 5, includes results information related to the AloT event as previously described.
[0130] Optionally at 526, the AloTF 508 updates the binding information and / or context information based on the results information included in the AloT event notification 524. The AloTF 508 then forwards the AloT event notification 528 to the AF 512 via the NEF 510.
[0131] Referring to FIG. 6, operations of another example procedure in accordance with an example embodiment is shown for providing AloT event notification to an AF for any of the example AloT events listed at No. 1-4 in the above table, which include: an AloT reader overload event, related to no. 1 in the above table; a device-reader latency event, related to no. 2 in the above table; a positioning capability event, related to no. 3 in the above table; and an out-of-coverage event, related to no. 4 in the above table. The operations described relate to messaging between an AloT device 602, an AloT reader device 604, an AMF 606, an AloTF 608, an NEF 610, and an external AF 612, which may be similar to the AloT device 202, the UE 204 or the RAN 208 depending on the topology utilized for AloT communication, the AMF 212, the AloTF 122, the NEF 216, and the AF 106, respectively, as described previously with reference to FIG. 2.
[0132] In the operations illustrated in FIG. 6, the AloT event subscription request is included in an AloT service request 614 that is sent by the AF. The AloT service request 614 requests an AloT service such as, for example, an inventory of the AloT devices at a particular area or location. The AloT event subscription request included in the AloT service request 614 in the example shown in FIG. 6 is the same as the AloT event subscription request 514 described previously. The NEF 610, after, for example, confirming that the AF 612 is authorized to request the services and event subscription requested by the AloT service request 614, forwards a AloT service request 616 to the AloTF 608.
[0133] At 618, the AloTF 608 determines a target AloT reader device associated with the AloT event subscription request included in the AloT service request 616 substantially similar the determination at 518 described previously. The AloTF 608 may additionally determine target AloT reader devices associated with the AloT service request included in the AloT service request 616.
[0134] The AloTF 608 transmits an AloT service message 620 to the AloT reader device 604 via the AMF 606, which includes a AloT event subscription similar to the AloT event subscription 520 described previously.
[0135] The AloT reader device 604 communicates with the AloT device at 622 to perform the AloT service, then transmits an AloT response message 624 that includes an identifier of the AloT device 602 as well as any data that is related to the AloT service that is requested. The AloT response 624 is transmitted to the AF 612 via the AMF 606, the AloTF 608, and the NEF 610.
[0136] The AloT reader device then monitors for the AloT event at 626, similar to the monitoring performed at 522, transmits an event notification 628 similar the event notification 524, optionally the AloTF 608 updates the binding information and / or context information at 630 similar the updating performed at 526, and the event notification 632 is transmitted by the AloTF 608 to the AF 612 via the NEF 610 similar the event notification 528.
[0137] Referring to FIGS. 7A and 7B, a flowchart showing a method or process in accordance with one example is shown. The method or process is performed by system of a wireless communication network such as, for example, a system comprising the NEF 216, the AloTF 222, and the AMF 212 of the wireless communication system 200, or another system comprising network functions that incorporates the functionality of an NEF, an AMF, and an AloTF as described herein. As described in more detail below, the method or process illustrated in FIGs. 7Aand 7B enables an external AF, such as the example AF 206, to "subscribe” to the example AloT events listed at No. 5 and 6 in the above table, which include: a readerdevice association failure, related to no. 5 of the above table; and reader-device reassignment, related to no. 6 of the above table.
[0138] At 702, an AloT event subscription request is received at an NEF from an AF. The AloT event subscription request includes an AloT event identifier that identifies an AloT event to monitor and one or more AloT device identifiers that identify one or more AloT devices that the AloT event is monitored in relation to.
[0139] The NEF, upon receiving the AloT event subscription request may optionally determine whether the AF from which the AloT event subscription request was received from is authorized to subscribe to the AloT event identified by the AloT event identifier, either in general, or for the AloT devices identifiers included in the AloT event subscription request.
[0140] If the NEF determines that the AF is authorized to subscribe to the AloT event identified in the AloT event subscription request, the NEF, at 704, determines an AloTF to send the AloT event subscription request to. The determination of the AloTF may be based on determining an AloTF that is responsible for the AloT devices identified in the AloT event subscription request. The NEF then forwards the AloT event subscription request to the determined AloTF.
[0141] At 706, the AloTF determines at least one target AloT reader device based on the one or more AloT device identifiers included in the AloT event subscription request that is transmitted by the NEF at 704. As described previously, depending on the topology utilized, the AloT reader devices may be gNBs of a RAN, such as the example RAN 208, in a first topology described with reference to FIG. 1 A, or may be a UE, such as UE 204, in a second topology described with reference to FIG. 1 B.
[0142] As described previously, the at least one AloT reader device may be determined based on binding information for the one or more AloT device identifiers included in the AloT event subscription request. The at least one target AloT reader devices are determined as the AloT reader devices that are mapped to the AloT devices associated with the one or more AloT device identifiers included in the AloT event subscription request.
[0143] Based on the at least one target AloT reader devices, an AMF is determined that is associated with the at least one target AloT reader devices.
[0144] At 708, the AloTF transmits an AloT event subscription to the AMF. The AloT event subscription includes the AloT event identifier, and includes information that identifies a destination entity to notify of the occurrence of the AloT event, i.e., the entity that the AloT event subscription request was received from, which is the AF. The AloT event subscription also includes identifiers for the at least one target AloT reader devicesto monitor the AloT event in relation to.
[0145] The AloT event identified by the AloT event identifier included in the AloT event subscription is reader-device association failure, related to no. 5 in the table above. The reader-device association failure may occur when one or more of one of the following occur: one of the at least one target AloT reader devices moves out of an area associated with the one or more AloT device identifiers that is associated with the one of the at least one target AloT reader devices based on the binding information; a response to a message sent by the AMF to one of the at least one target AloT reader devices is not received by the AMF within a predetermined time period or after the AMF has sent a predetermine number of messages; or a message from one of the at least one target AloT reader devices is received at the AMF, the message indicating that the one of the at least one target AloT reader devices did not receive a response from one or more AloT devices that the one of the at least one target AloT reader devices is associated with based on the binding information.
[0146] The AloT event subscription may also optionally include, for example, any thresholds, or conditions, or criteria to be met that are related to the particular AloT event identified by the AloT event identifier. For example, the AloT event subscription may include the predetermined time period and / or the predetermine number of messages utilized to determine that a response from a target AloT reader device is not received by the AMF.
[0147] These thresholds, or conditions, or criteria may be thresholds, or conditions, or criteria that were optionally included in the AloT event subscription request that was received from the AF at 702, or may be determined by the AloTF based on the AloT event identifier. These thresholds, or conditions, or criteria may then be utilized by the AMF for monitoring for an occurrence of the AloT event.
[0148] The AloT event subscription request may optionally include information related to the reporting of the notifications that are sent upon the occurrence of the AloT event. Such information may include, for example, a time duration over which the AF is subscribing to the AloT event, a maximum number of occurrences of the AloT event that the AF wants to receive notifications of, a number of occurrences of the AloT event that must occur before a notification is sent, and a periodicity of reporting the AloT event or information related to the AloT event.
[0149] At 710, the AMF monitors for occurrences of the AloT event. For example, the AMF monitors for whether one of the at least one target AloT reader devices moves out of an area associated with the one or more AloT device identifiers that is associated with the one of the at least one target AloT reader devices based on the binding information; a response to a message sent by the AMF to one of the at least one target AloT reader devices is not received by the AMF within a predetermined time period or after the AMF has sent a predetermine number of messages; or a message from one of the at least one target AloT reader devices is received at the AMF, the message indicating that the one of the at least one target AloT reader devices did not receive a response from one or more AloT devices that the one of the at least one target AloT reader devices is associated with based on the binding information.
[0150] At 712, in response to determining an occurrence of the AloT event, the AMF transmits an AloT event notification message to the AloTF. The AloT event notification message is directed to the AF, which is thedestination entity identified in the AloT subscription. The AloT event notification includes a cause of the AloT event occurrence, which may be an indication of whether the AloT even occurred because the target AloT reader device moved out of the area, because no response was received from the AloT device, or because a message was received from the target AloT device indicating no response was received at the AloT reader device from the associated AloT device.
[0151] The AloT event notification message also includes one or both of the identifier of the one of the at least one AloT reader device and the identifiers of the at least one AloT device for which the AloT event occurred in association with. For example, if the cause of the AloT event was that one of the target AloT reader devices moved out of the area or that no response was received from one of the target AloT devices, then an identifier for the one of the target AloT reader devices is included in the AloT event notification. If the cause of the AloT event was that a response from a target AloT reader device indicates that no response was received from an AloT device, then the AloT event notification includes an identifier of the AloT device for which no response was received.
[0152] Optionally, at 714, the AloTF deletes the binding information associated with the AloT reader device(s) or AloT device(s) that are identified in the AloT event notification. For example, if the cause of the AloT event was that one of the target AloT reader devices moved out of the area or that no response was received from one of the target AloT devices, then binding information associated with an identifier for the one of the target AloT reader devices may optionally be deleted from the binding information, which may include deleting binding information for all AloT devices mapped to the one of the target AloT reader devices. If the cause of the AloT event was that a response from a target AloT reader device indicates that no response was received from an AloT device, then binding information for the identifier of the AloT device is optionally deleted.
[0153] Optionally, at 716, an AloT reader device re-selection process may be initiated by the AloTF for the AloT device identifiers associated with the AloT event notification. For example, AloT reader re-selection may be performed all of the AloT device identifiers for which binding information was deleted at 714. The AloTF may update the binding information based on the re-selection process to include binding information for the AloT device identifiers and the AloT reader device identifiers that are selected for the AloT device identifiers.
[0154] At 718, the AloT event notification is transmitted to the AF. The AloT event notification may be the AloT event notification that is received at the AloTF from the AM F at 712.
[0155] In examples in which the AloT event subscription request sent by the AF includes an AloT event identifier that identifies a reader reassignment event, related to no. 6 of the above table, and in which the optional AloT reader device re-selection process is performed at 716, then the AloT event notification transmitted at 718 includes sending an AloT event notification including the AloT event identifier related to the reader reassignment event, and including the updated binding information mapping the AloT device identifiers to the newly assigned AloT reader device. The AloT event notification for the reader assignment event may be included together with the AloT event notification received from the AMF, such that a single AloT event notification is transmitted, or may be transmitted separately from the AloT event notification that received fromthe AMF and is transmitted by the AloTF to the AF.
[0156] Referring to FIG. 8, operations of another example procedure in accordance with an example embodiment is shown for providing AloT event notification to an AF for any of the example AloT events listed at No. 5 and 6 in the above table, which include: a reader-device association failure, related to no. 5 of the above table; and reader-device reassignment, related to no. 6 of the above table. The operations described relate to messaging between an AloT reader device 802, an AMF 804, an AloTF 806, an NEF 808, and an external AF 810, which may be similar to the UE 204 or the RAN 208 depending on the topology utilized for AloT communication, the AMF 212, the AloTF 122, the NEF 216, and the AF 106, respectively, as described previously with reference to FIG. 2.
[0157] At 811, an AloT reader device selection process is performed to select AloT reader devices for particular AloT devices. The selected AloT reader devices for the particular AloT devices are utilized to generate binding information for the particular AloT devices.
[0158] The AF 810 transmits an AloT event subscription request 812 to the NEF 808. The AloT event subscription request 812 includes an event identifier, and one or more target AloT device identifiers. The NEF 808 determines if the AF 810 is authorized to subscribe to the AloT event for the target AloT devices, and once confirming authorization, transmits the AloT event subscription request 814 to the AloTF 806.
[0159] At 816, the AloTF 806 determines at least one target AloT reader device identifiers based on the AloT device identifiers included in the AloT event subscription request 814. As described previously, the at least one target AloT reader device identifier are determined utilizing binding information for the target AloT device identifiers included in the AloT event subscription request 814. Based on the at least one AloT reader device identifiers, an AMF 804 is determined by the AloTF 806.
[0160] The AloTF 806 transmits an AloT event subscription 818 to the determined AMF 804, which includes the AloT event identifier and the identifier of the at least one target AloT reader device.
[0161] At 820, an event occurs at the AloT reader device 802, such as the AloT reader device moves out the area, or something occurs, for example the AloT reader device shuts down, that results in the AloT reader device to fail to respond to the AMF 804, or an AloT device (not shown) fails to respond to a message from the AloT reader device.
[0162] At 822, the AMF 804 which is monitoring for the AloT event, determines the AloT event that occurs at 822, which includes determining the cause of the AloT event.
[0163] In response to the determining the occurrence of the event at 822, the AMF 804 transmits an AloT event notification message 824 to the AloTF 806. The AloT event notification message 824 is directed to the AF and includes the AloT event identifier and the cause, as described previously with reference to 712.
[0164] At 826, the AloTF 806 optionally deletes the binding information for the AloT device identifiers or the AloT reader device identifiers related to the cause of the AloT event as described previously with reference to 714.
[0165] At 830, the AloTF 806 transmits AloT event notification message 830 to the AF 810 via the NEF 808.
[0166] At 832, an AloT reader device reselection process is optionally initiated by the AloTF 806 to selectnew AloT reader devices for the AloT devices for which binding information was deleted at 826.
[0167] At 834, binding information stored in a memory associated with the AloTF 806 is optionally updated by the AloTF 806 to include new AloT reader device identifier selected for the AloT device identifiers in the reselection process performed at 832.
[0168] At 836, the AloTF 806 transmits an AloT event notification message 836 to the AF 810 via the NEF 808. The AloT event notification message 836 includes an AloT event identifier and includes the updated binding information.
[0169] Referring to FIG. 9, a schematic diagram illustrating various physical and logical components of an exemplary an AloT reader device. The AloT reader device may be either a UE or a RAN node (e.g., a gNB), as previously described herein in accordance with an embodiment is shown. Although an example embodiment of the apparatus 900 is shown and discussed below, other embodiments may be used to implement examples disclosed herein, which may include components different from those shown. Although FIG. 9 shows a single instance of each component of the apparatus 900, there may be multiple instances of each component shown.
[0170] The apparatus 900 includes one or more processors 902, such as a central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a dedicated logic circuitry, a graphics processing unit (GPU), a tensor processing unit, a neural processing unit, a dedicated artificial intelligence processing unit, a hardware accelerator, or any other suitable hardware processing circuitry, or combinations thereof. The one or more processors 902 may collectively be referred to as a processor 902.
[0171] The apparatus 900 also includes one or more memories 904 (collectively referred to as "memory 904"), which may include a volatile or non-volatile memory (e.g., a flash memory, a random-access memory (RAM), and / or a read-only memory (ROM)). The non-transitory memory 904 may store instructions for execution by the processor 902. The instructions 906, when executed by the processor 902 causes the apparatus 900 to perform the actions or operations of the methods or processes of FIG. 4 described herein. The apparatus 900 may also include one or more network interfaces 908 for connecting, when the apparatus 900 is configured as a UE, to the RAN node and to the AloT device, and when the apparatus 900 is configured as a RAN node, to the AloT device, or to an AloT reader device in indirect AloT communication, and to the core network.
[0172] The apparatus 900 may optionally include a user input 910 for receiving input from a user of the apparatus 900 and a display 912.
[0173] In some examples, the apparatus 900 may also include one or more electronic storage units (not shown) for storing data, such as a solid-state drive, a hard disk drive, a magnetic disk drive and / or an optical disk drive. In some examples, one or more data and / or software modules may be provided by an external memory (e.g., an external drive in wired or wireless communication with the apparatus 900) or may be provided by a transitory or non-transitory computer-readable medium. Examples of non-transitory computer readable media include a RAM, a ROM, an erasable programmable ROM (EPROM), an electrically erasableprogrammable ROM (EEPROM), a flash memory, a CD-ROM, or other portable memory storage. The electronic storage units and / or external memory may be used in conjunction with memory 904 to store data, retrieve stored data, and cache data.
[0174] The components of the apparatus 900 may communicate with each other via a bus.
[0175] Embodiments of the present disclosure including methods, processes, and operations, may be implemented in software, and stored as executable instructions on a computer-readable medium that when executed by a processor cause the disclosed methods, processes, and operations to be performed by the processor. In the context of this application, a "memory” or "computer-readable medium” may be any non- transitory media or means that contains, stores, communicates, propagates or transports the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.
[0176] Reference to, where relevant, "computer-readable medium”, "computer program product”, "tangibly embodied computer program” etc., or a "processor” or "processing circuitry” etc. should be understood to encompass not only computers having differing architectures such as single / multi-processor architectures and sequencers / parallel architectures, but also specialized circuits such as field programmable gate arrays FPGA, application specify circuits ASIC, signal processing devices / apparatus and other devices / apparatus. References to computer program, instructions, code etc. should be understood to express software for a programmable processor firmware such as the programmable content of a hardware device / apparatus as instructions for a processor or configured or configuration settings for a fixed function device / apparatus, gate array, programmable logic device / apparatus, etc.
[0177] As used in the present disclosure, the term "circuitry”, for example in the hardware processing circuitry that may be used to implement the IVE or the CHF in accordance with certain embodiments of the present disclosure, may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / fi rmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and (iii) hardware ci rcuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in the present disclosure, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0178] The present disclosure provides methods and apparatuses for providing AloT event exposure in a wireless communication network. The present disclosure provides for subscribing to AloT events related toAloT devices, monitoring for occurrences of AloT events and providing notification of the occurrences of such AloT events.
[0179] The functions, processes, and operations described herein may be performed in a different order, or may be performed concurrently with each other, or a combination thereof. Furthermore, one or more of the functions, processes, and operations may be optional or may be combined. It will be appreciated that the flow diagrams shown in FIG. 3, FIG. 4, and FIGS. 7A and 7B and the procedures illustrated in FIG. 5, FIG. 6, and FIG. 8 are examples only. Various operations and processes depicted therein may be omitted, may be reordered, may be combined, or a combination of reordered and combined.
[0180] Advantageously, the present disclosure enables providing AloT event notification in wireless communication systems.
[0181] The scope of the claims should not be limited by the preferred embodiments set forth in the examples but should be given the broadest interpretation consistent with the description as a whole.
Claims
35Claims1 . A method of an ambient internet of things (AloT) reader device, the method comprising: receiving, from an AloT function (AloTF) of a communication network, an AloT event subscription, the AloT event subscription comprising an AloT event identifier that identifies an AloT event that the AloT reader device is to monitor and information identifying a destination entity to notify; monitoring for occurrences of the AloT event; and in response to monitoring an occurrence of the AloT event, transmitting an AloT event notification to the destination entity to indicate the occurrence of the AloT event, the AloT event notification including the AloT event identifier, and an identifier of the AloT reader device; wherein the AloT event consists of one of: an AloT reader overload event, wherein the AloT reader overload event occurs when a load measurement at the AloT reader device is greater than or equal to a load measurement threshold for the AloT reader device; a device-reader latency event, wherein the device-reader latency event occurs when a latency of responses received at the AloT reader device from a particular AloT device is equal to or greater than a threshold latency for receiving response at the AloT device, wherein the AloT event notification includes an identifier of the particular AloT device for which the device-reader latency event occurred; a positioning capability event, wherein the positioning capability event occurs when the AloT reader device is capable of performing positioning according to a positioning criteria; or an out-of-coverage event, wherein the out-of-coverage event occurs when a response from a particular AloT device associated with the AloT reader device is not received at the AloT reader device within a predetermined time period or after a predetermined number of messages sent by the AloT reader device to the particular AloT device, wherein the AloT event subscription includes identifiers for one or more AloT devices including the particular AloT device.
2. The method of claim 1 , wherein: when the AloT event comprises the AloT reader overload event, and the AloT event subscription received at the AloT reader device includes the load measurement threshold; when the AloT event comprises the device-reader latency event, the AloT event subscription message includes the threshold latency; when the AloT event comprises the positioning capability event, the AloT event subscription includes the positioning criteria; and when the AloT event comprises the out-of-coverage event, he AloT event subscription includes the predetermined time period or the predetermined number of messages.
363. The method of claim 1, wherein the AloT event comprises the AloT reader overload event, and the load measurement threshold is one of: a utilization amount of a central processing unit (CPU) of the AloT reader device, wherein the load measurement is an amount of processing capacity of the CPU that is utilized; a storage space utilization amount of a memory of the AloT reader device, wherein the load measurement is an amount of storage space of the memory that is utilized; an average processing time for the CPU of the AloT reader device to process responses from AloT devices, wherein the load measurement is an average processing time for the CPU of the AloT reader device to process responses from AloT devices; or a charge remaining amount for a battery of the AloT reader device, wherein the load measurement is an amount of charge remaining in the battery.
4. The method of claim 1, wherein the AloT event comprises the positioning capability event, and the positioning criteria comprises one or more of: the AloT reader device being enabled by a location management function (LMF) of the wireless communication system to perform positioning; the AloT reader device being enabled by an end user of the AloT reader device to perform positioning; or subscription an available processing capacity of a central processing unit (CPU) of the AloT reader device meets or exceeds a processing threshold to support the positioning capability.
5. The method of claim 1, wherein the AloT event subscription is included in an AloT service request.
6. The method of claim 1 , wherein: the AloT event subscription includes a periodicity time; and the method further comprises in response to monitoring an occurrence of the AloT event, periodically transmitting to the destination entity, with a periodicity of the periodicity time: a current value of the load measurement when the AloT event is the AloT reader overload event, and a current value of the latency of responses received at the AloT reader device from the AloT device when the AloT event is the device-reader latency event.
7. An AloT reader device comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, cause the AloT reader device to perform the method of any of claims 1-6.
8. The apparatus of claim 6, wherein the AloT reader device comprises a user equipment.
9. A computer-readable medium storing instructions, wherein when the instructions are executed by at least one processor of an ambient internet of things (AloT) reader device, cause the AloT reader device to perform the method of any of claims 1-6.
10. A computer program comprising instructions, wherein the instructions when the executed by at least one processor of an ambient internet of things (AloT) reader device, cause the AloT reader device to perform the method of any of claims 1-611. A method of a core network of a communication network, the method comprising: receiving at a network exposure function (NEF) of the core network, from an application function (AF), an ambient internet of things (AloT) event subscription request, the AloT event subscription request includes an AloT event identifier that identifies an AloT event to monitor for, and information that identifies one or more of a area to monitor for the AloT event, one or more AloT device identifiers, or one or more AloT reader device identifiers; determining by the NEF, based on the information that identifies one or more of the area, the one or more AloT device identifiers, or the one or more AloT reader device identifiers included in the AloT event subscription request, an AloT function (AloTF) of the core network and transmitting the AloT event subscription request to the AloTF; determining by the AloTF at least one target AloT reader device based on the information that identifies one or more of the area, the one or more AloT device identifiers, or the one or more AloT reader device identifiers included in the AloT event subscription request; transmitting, by the AloTF to the at least one target AloT reader device, an AloT event subscription, the AloT event subscription includes the AloT event identifier that identifies the AloT event for the AloT reader device to monitor for and information identifying the AF to notify; subscription receiving at the AloTF from one of the at least one target AloT reader device an AloT event notification directed to the AF and indicating the occurrence of the AloT event, the AloT event notification including the AloT event identifier , and an identifier of the one of the at least one target AloT reader device; transmitting, by the AloTF to the AF, the AloT event notification; wherein the AloT event consists of one of: an AloT reader overload event, wherein the AloT reader overload event occurs when a load measurement at the AloT reader device is greater than or equal to a load measurement threshold; a device-reader latency event, wherein the device— reader latency of response event occurs when a latency of responses received at the AloT reader device from a particular AloT device is equal to or greater than a threshold latency, wherein the AloT event notification includes an identifier of the particular AloT device for which the device-reader latency event occurred;a positioning capability event, wherein the positioning capability event occurs when the AloT reader device is capable of performing positioning according to a positioning criteria; or an out-of-coverage event, wherein the out-of-coverage event occurs when a response from a particular AloT device is not received at the AloT reader device within a predetermined time period or after a predetermined number of messages sent by the AloT reader device to the particular AloT device, wherein the AloT event subscription includes identifiers for one or more Alot devices including the particular AloT device.
12. The method of claim 11, wherein: when the AloT event comprises the AloT reader overload event, and the AloT event subscription includes the load measurement threshold; when the AloT event comprises the device-reader latency , the AloT event subscription includes the threshold latency; when the AloT event comprises the positioning capability event, the AloT event subscription includes the positioning criteria; and when the AloT event comprises the out-of-coverage event, the AloT event subscription includes the predetermined time period or the predetermined number of messages.
13. The method of claim 11, wherein the AloT event comprises the AloT reader overload event, and the load measurement threshold is one of: a utilization amount of a central processing unit (CPU) of the AloT reader device, wherein the load measurement is an amount of processing capacity of the CPU that is utilized; a storage space utilization amount of a memory of the AloT reader device, wherein the load measurement is an amount of storage space of the memory that is utilized; an average processing time for the CPU of the AloT reader device to process responses from AloT devices, wherein the load measurement is an average processing time for the CPU of the AloT reader device to process responses from AloT devices; or a charge remaining amount for a battery of the AloT reader device, wherein the load measurement is an amount of charge remaining in the battery.
14. The method of claim 11, wherein the AloT event comprises the positioning capability event, and the positioning criteria comprises one or more of: the AloT reader device being enabled by a location management function (LMF) of the wireless communication system to perform positioning; the AloT reader device being enabled by an end user of the AloT reader device to perform positioning; or39 subscription an available processing capacity of a central processing unit (CPU) of the AloT reader device meets or exceeds a processing threshold to support the positioning capability.
15. The method of claim 11, wherein the AloT event subscription request is included in an AloT service request.
16. The method of claim 11, wherein the AloT event subscription request includes information identifying one or more AloT device identifiers, and determining, by the AloTF, the least one target AloT reader device comprises determining, for each of the one or more AloT device identifiers, an AloT reader device identifier associated with that AloT device identifier utilizing binding information stored in a memory associated with the AloTF, the binding information including pairings of AloT device identifiers and their corresponding AloT reader device identifiers.
17. The method of claim 16, wherein the AloT event comprises the out-of-coverage event, the method further comprising: in response to the AloTF receiving the AloT event notification indicating that the particular AloT device is out-of-coverage from the at least one target AloT reader device, updating the stored binding information to remove the binding information for the particular AloT device identifier.
18. The method of claim 11, further comprising, in response to receiving the AloT event notification from the one of the at least one target AloT reader devices, updating context information associated with the one of the at least one AloT reader devices stored at a memory associated with the AloTF to include information related to the one of the at least one AloT devices and associated with the occurrence of the AloT event.
19. A system of a communication network, the system comprising: a network exposure function (NEF) comprising: a means for receiving from an application function (AF), an ambient internet of things (AloT) event subscription request, the AloT event subscription request includes an AloT event identifier that identifies an AloT event to monitor for, and information that identifies one or more of an area to monitor for the AloT event, one or more AloT device identifiers, or one or more AloT reader device identifiers; a means for determining, based on the information that identifies one or more of the area, the one or more AloT device identifiers, or the one or more AloT reader device identifiers included in the AloT event subscription request, an AloT function (AloTF) of the core network and transmitting the AloT event subscription request to the AloTF; an AloTF comprising:40 a means for determining at least one target AloT reader device based on the information that identifies one or more of the area, the one or more AloT device identifiers, or the one or more AloT reader device identifiers included in the AloT event subscription request; a means for transmitting to the at least one target AloT reader device, an AloT event subscription, the AloT event subscription includes the AloT event identifier that identifies the AloT event for the AloT reader device to monitor for and information identifying the AF to notify; a means for receiving at the AloTF from one of the at least one target AloT reader device an AloT event notification directed to the AF and indicating the occurrence of the AloT event, the AloT event notification including the AloT event identifier , and an identifier of the one of the at least one target AloT reader device; a means for transmitting, by the AloTF to the AF, the AloT event notification; wherein the AloT event consists of one of: an AloT reader overload event, wherein the AloT reader overload event occurs when a load measurement at the AloT reader device is greater than or equal to a load measurement threshold; a device-reader latency event, wherein the device— reader latency of response event occurs when a latency of responses received at the AloT reader device from a particular AloT device is equal to or greater than a threshold latency, wherein the AloT event notification includes an identifier of the particular AloT device for which the device-reader latency event occurred; a positioning capability event, wherein the positioning capability event occurs when the AloT reader device is capable of performing positioning according to a positioning criteria; or an out-of-coverage event, wherein the out-of-coverage event occurs when a response from a particular AloT device is not received at the AloT reader device within a predetermined time period or after a predetermined number of messages sent by the AloT reader device to the particular AloT device, wherein the AloT event subscription includes identifiers for one or more AloT devices including the particular AloT device.
20. The system of claim 19, wherein: when the AloT event comprises the AloT reader overload event, and the AloT event subscription includes the load measurement threshold; when the AloT event comprises the device-reader latency , the AloT event subscription includes the threshold latency; when the AloT event comprises the positioning capability event, the AloT event subscription includes the positioning criteria; and when the AloT event comprises the out-of-coverage event, the AloT event subscription includes the predetermined time period or the predetermined number of messages.4121 . The system of claim 19, wherein the AloT event comprises the AloT reader overload event, and the load measurement threshold is one of: a utilization amount of a central processing unit (CPU) of the AloT reader device, wherein the load measurement is an amount of processing capacity of the CPU that is utilized; a storage space utilization amount of a memory of the AloT reader device, wherein the load measurement is an amount of storage space of the memory that is utilized; an average processing time for the CPU of the AloT reader device to process responses from AloT devices, wherein the load measurement is an average processing time for the CPU of the AloT reader device to process responses from AloT devices; or a charge remaining amount for a battery of the AloT reader device, wherein the load measurement is an amount of charge remaining in the battery.
22. The system of claim 19, the AloT event comprises the positioning capability event, and the positioning criteria comprises one or more of: the AloT reader device being enabled by a location management function (LMF) of the wireless communication system to perform positioning; the AloT reader device being enabled by an end user of the AloT reader device to perform positioning; or an available processing capacity of a central processing unit (CPU) of the AloT reader device meets or exceeds a processing threshold to support the positioning capability.
23. The system of claim 19, wherein the AloT event subscription request is included in an AloT service request.
24. The system of claim 19, wherein the AloT event subscription request includes information identifying one or more AloT device identifiers, and wherein the AloTF comprising the means determining the least one target AloT reader device comprises the AloTF comprising a means for determining, for each of the one or more AloT device identifiers, an AloT reader device identifier associated with that AloT device identifier utilizing binding information stored in a memory associated with the AloTF, the binding information including pairings of AloT device identifiers and their corresponding AloT reader device identifiers.
25. The system of claim 24, wherein the AloT event comprises the out-of-coverage event, the AloTF further comprising: a means for, in response to the AloTF receiving the AloT event notification indicating that the particular AloT device is out-of-coverage from the at least one target AloT reader device, updating the stored binding information to remove the binding information for the particular AloT device identifier.4226. The system of claim 19, the AloTF further comprising a means for, in response to receiving the AloT event notification from the one of the at least one target AloT reader devices, updating context information associated with the one of the at least one AloT reader devices stored at a memory associated with the AloTF to include information related to the one of the at least one AloT devices and associated with the occurrence of the AloT event.
27. A method for a core network of a communication network, the method comprising: receiving at a network exposure function (NEF) of the core network from application function (AF), an ambient internet of things (AloT) event subscription request, the AloT event subscription request includes an AloT event identifier that identifies an AloT event to monitor for, and one or more AloT device identifiers associated with the AloT event; determining by the NEF, based on the one or more AloT device identifiers included in the AloT event subscription request, an AloT function (AloTF) of the core network and transmitting the AloT event subscription request to the AloTF; determining by the AloTF at least one target AloT reader device based on the information that identifies one or more AloT device identifiers included in the AloT event subscription request by determining, for each of the one or more AloT device identifiers, an AloT reader device identifier associated with that AloT device identifier utilizing binding information stored in a memory associated with the AloTF, the binding information including pairings of AloT device identifiers and their corresponding AloT reader device identifiers; determining by the AloTF, at least one access management function (AMF) of the core network based on the determined at least one target AloT reader device; transmitting by the AloTF to the at least one AMF an AloT event subscription, the AloT event subscription includes the AloT event identifier that identifies the AloT event for the AMF to monitor, information identifying the AF to notify and an identifier for each of the at least one target AloT reader devices; monitoring, by the at least one AMF, for occurrences of the AloT event, wherein the AloT event consists of one or more of: one of the at least one target AloT reader devices moves out of an area associated with the one or more AloT device identifiers that the one of the at least one target AloT reader devices is associated with based on the binding information; a response to a message sent by the AMF to one of the at least one target AloT reader devices is not received by the AMF from the one of the at least one target AloT reader devices within a predetermined time period or after the AMF has sent a predetermine number of messages; or a message from one of the at least one target AloT reader devices is received at the AMF, the message indicating that the one of the at least one target AloT reader devices did not receive a response from one or more AloT devices that the one of the at least one target AloT reader devices is associated with based on the binding information;43 in response to determining that the AloT event has occurred, transmitting by the AMF to the AloTF an AloT event notification directed to the AF and indicating the occurrence of the AloT event, the AloT event notification including the AloT event identifier, a cause of the AloT event occurrence, and one or both of the identifier of the one of the at least one AloT reader device and the identifiers of the at least one AloT device for which the AloT event occurred in association with; transmitting, by the AloTF to the AF, the AloT event notification.
28. The method of claim 27, wherein: when the cause included in the event notification indicates that the AloT event occurred when one of the at least one target AloT reader devices moved out of the location or that one of the at least one target AloT reader devices did not respond to the AMF, the method further comprises removing by the AloTF binding information associated with the one of the at least one target AloT reading device; and when the cause included in the event notification indicates that the AloT event occurred when one of the at least one target AloT reader devices did not receive a response from one of the one or more AloT devices, the method further comprises removing by the AloTF binding information associated with the one of the AloT devices.
29. The method of claim 27, in response to the AloTF receiving the AloT event notification from the AMF, the method further comprising: determining, by the AloTF, one or more affected AloT devices for which binding information is no longer valid based on the cause and the one or both of the identifier of the one of the at least one AloT reader device and the identifiers of the at least one AloT device for which the AloT even occurred in association with; initiating by the AloTF an AloT reader device re-selection process for the one or more affected AloT devices to select an AloT reader device for each of the one or more affected AloT devices; and updating by the AloTF binding information for each of the one or more affected AloT devices to include the selected AloT reader device; and wherein the AloT event notification transmitted by the AloTF to the AF further includes the updated binding information for the one or more affected AloT devices.
30. A system for a communication network, the system comprising: a network exposure function (NEF) comprising: a means for receiving from application function (AF), an ambient internet of things (AloT) event subscription request, the AloT event subscription request includes an AloT event identifier that identifies an AloT event to monitor for, and one or more AloT device identifiers associated with the AloT event; a means for determining, based on the one or more AloT device identifiers included in the AloT event subscription request, an AloT function (AloTF); and44 a means for transmitting the AloT event subscription request to the AloTF; an AloTF comprising: a means for determining at least one target AloT reader device based on the information that identifies one or more AloT device identifiers included in the AloT event subscription request by determining, for each of the one or more AloT device identifiers, an AloT reader device identifier associated with that AloT device identifier utilizing binding information stored in a memory associated with the AloTF, the binding information including pairings of AloT device identifiers and their corresponding AloT reader device identifiers; a means for determining by the AloTF, at least one access management function (AMF) based on the determined at least one target AloT reader device; a means for transmitting to the at least one AMF an AloT event subscription, the AloT event subscription includes the AloT event identifier that identifies the AloT event for the AMF to monitor, information identifying the AF to notify, and an identifier for each of the at least one target AloT reader devices; at least one AMF comprising: a means for monitoring for occurrences of the AloT event, wherein the AloT event consists of one or more of: one of the at least one target AloT reader devices moves out of an area associated with the one or more AloT device identifiers that the one of the at least one target AloT reader devices is associated with based on the binding information; a response to a message sent by the AMF to one of the at least one target AloT reader devices is not received by the AMF from the one of the at least one target AloT reader devices within a predetermined time period or after the AMF has sent a predetermined number of messages; or a message from one of the at least one target AloT reader devices is received at the AMF, the message indicating that the one of the at least one target AloT reader devices did not receive a response from one or more AloT devices that the one of the at least one target AloT reader devices is associated with based on the binding information; a means for, in response to determining that the AloT event has occurred, transmitting to the AloTF an AloT event notification directed to the AF and indicating the occurrence of the AloT event, the AloT event notification including the AloT event identifier, a cause of the AloT event occurrence, and one or both of the identifier of the one of the at least one AloT reader device and the identifiers of the at least one AloT device for which the AloT event occurred in association with; the AloTF further comprising a means for transmitting to the AF the AloT event notification received from one of the at least one AMF.4531 . The system of claim 30, wherein the AloTF further comprises a means for: when the cause included in the event notification indicates that the AloT event occurred when one of the at least one target AloT reader devices moved out of the location or that one of the at least one target AloT reader devices did not respond to the AMF, removing by the AloTF binding information associated with the one of the at least one target AloT reading device; and when the cause included in the event notification indicates that the AloT event occurred when one of the at least one target AloT reader devices did not receive a response from one of the one or more AloT devices, removing by the AloTF binding information associated with the one of the AloT devices.
32. The system of claim 30, the AloTF further comprises: a means for, in response to the AloTF receiving the event notification from the AMF, determining one or more affected AloT devices for which binding information is no longer valid based on the cause and the one or both of the identifier of the one of the at least one AloT reader device and the identifiers of the at least one AloT device for which the AloT even occurred in association with; a means for initiating an AloT reader device re-selection process for the one or more affected AloT devices to select an AloT reader device for each of the one or more affected AloT devices; and a means for updating binding information for each of the one or more affected AloT devices to include the selected AloT reader device; and wherein the means for transmitting the AloT event notification to the AF further comprises a means for including the updated binding information for the one or more affected AloT devices in the AloT event notification.