Ambient internet of things reader device configuration

Abstract

A method, apparatus, and computer program are described comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; sending, from the AIoT reader device, to the mobile communication system, a resource release request, the resource release request being a message responsive to which the mobile communication system sends a resource release indication; and receiving, at the AIoT reader device, from the mobile communication system, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

Description

[0001] AMBIENT INTERNET OF THINGS READER DEVICE CONFIGURATION

[0002] Field

[0003] Example embodiments may relate to Ambient Internet of Things reader devices, network nodes, and methods for configuring Ambient Internet of Things reader devices.

[0004] Background

[0005] Ambient Internet of Things reader devices use resources (e.g., frequency and / or time resources) to communicate with Ambient Internet of Things devices (e.g., tag devices). There remains an interest in providing for control over the behavior of an Ambient Internet of Things reader device by a mobile communication system by configuring the Ambient Internet of Things reader devices.

[0006] Summary

[0007] The scope of protection sought for various embodiments of the invention is set out by the independent claims. The embodiments and features, if any, described in this specification that do not fall under the scope of the independent claims are to be interpreted as examples useful for understanding various embodiments of the invention.

[0008] A first aspect provides an Ambient Internet of Things, AIoT, reader device comprising : means for receiving, from a mobile communication system, first configuration information, the first configuration information comprising information defining at least part of a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform AIoT communication operations with AIoT devices; means for receiving, from the mobile communication system, a first AIoT request; and means for receiving, from the mobile communication system, second configuration information, the second configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0009] In some example embodiments the second configuration information defines, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request by at least indicating at least one of: a selection from information of the first configuration information; an addition to information of the first configuration information; and a change to information of the first configuration information.

[0010] In some example embodiments, the first configuration information comprises a plurality of information elements, and the second configuration information defines at least a part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request by indicating at least one selection of at least one information element of the plurality of information elements of the first configuration information.

[0011] In some example embodiments, the first configuration information defines a plurality of resource pools, and the second configuration information defines at least a part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request by indicating at least one of the plurality of resource pools for use in fulfilling the first AIoT request.

[0012] In some example embodiments, the means for receiving the first configuration information is configured to receive, in a system information broadcast from a network node of the mobile communication system, at least a part of the first configuration information from which the second configuration information indicates a selection.

[0013] In some example embodiments the second configuration information indicates information elements that are additional to information elements included in the first configuration information to define at least part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0014] In some example embodiments the second configuration information indicates modifications to or replacements for information elements of the first configuration information to define at least part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0015] In some example embodiments the means for receiving the first configuration information is configured to receive, as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests, at least a part of the first configuration information to which the second configuration information indicates an addition and / or change.

[0016] In some example embodiments, the AIoT reader device further comprises means for fulfilling the first AIoT request using the configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0017] In some example embodiments the means for receiving the second configuration information is configured to receive the second configuration information via a small data transmission, SDT, procedure. In some example embodiments the means for receiving the second configuration information is configured to receive the second configuration information with or as part of the AIoT request.

[0018] In some example embodiments, the AIoT device further comprises means for sending information associated with the first AIoT request to the mobile communication system, and the means for receiving second configuration information is configured to receive second configuration information sent by the mobile communication system in response to the information associated with an AIoT request.

[0019] In some example embodiments, the AIoT device further comprises means for receiving, from the mobile communication system, a second AIoT request; and means for receiving, from the mobile communication system, third configuration information, the third configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the second AIoT request.

[0020] A second aspect provides a method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, first configuration information, the first configuration information comprising information defining at least part of a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform AIoT communication operations with AIoT devices; receiving, at the AIoT reader device, from the mobile communication system, a first AIoT request; and receiving, at the AIoT reader device, from the mobile communication system, second configuration information, the second configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0021] In some example embodiments the second configuration information defines, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request by at least indicating at least one of: a selection from information of the first configuration information; an addition to information of the first configuration information; and a change to information of the first configuration information.

[0022] In some example embodiments, the first configuration information comprises a plurality of information elements, and the second configuration information defines at least a part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request by indicating at least one selection of at least one information element of the plurality of information elements of the first configuration information.

[0023] In some example embodiments, the first configuration information defines a plurality of resource pools, and the second configuration information defines at least a part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request by indicating at least one of the plurality of resource pools for use in fulfilling the first AIoT request.

[0024] In some example embodiments, receiving the first configuration information comprises receiving at least a part of the first configuration information from which the second configuration information indicates a selection in a system information broadcast from a network node of the mobile communication system.

[0025] In some example embodiments the second configuration information indicates information elements that are additional to information elements included in the first configuration information to define at least part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0026] In some example embodiments the second configuration information indicates modifications to or replacements for information elements of the first configuration information to define at least part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0027] In some example embodiments receiving the first configuration information comprises receiving, as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests, at least a part of the first configuration information to which the second configuration information indicates an addition and / or change.

[0028] In some example embodiments, the method further comprises fulfilling the first AIoT request using the configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0029] In some example embodiments receiving the second configuration information comprises receiving the second configuration information via a small data transmission, SDT, procedure.

[0030] In some example embodiments receiving the second configuration comprises receiving the second configuration information with or as part of the AIoT request.

[0031] In some example embodiments, the method further comprises sending information associated with the first AIoT request to the mobile communication system, and receiving second configuration information comprises receiving second configuration information sent by the mobile communication system in response to the information associated with an AIoT request.

[0032] In some example embodiments, the method further comprises: receiving, from the mobile communication system, a second AIoT request; and receiving, from the mobile communication system, third configuration information, the third configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the second AIoT request.

[0033] A third aspect provides a computer program comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out a method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, first configuration information, the first configuration information comprising information defining at least part of a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform AIoT communication operations with AIoT devices; receiving, at the AIoT reader device, from the mobile communication system, a first AIoT request; and receiving, at the AIoT reader device, from the mobile communication system, second configuration information, the second configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0034] In some example embodiments, the third aspect may include any other feature mentioned with respect to the method of the second aspect.

[0035] A fourth aspect provides a non-transitory computer-readable medium having stored thereon computer-readable code, which, when executed by at least one processor, causes the at least one processor to perform a method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, first configuration information, the first configuration information comprising information defining at least part of a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform AIoT communication operations with AIoT devices; receiving, at the AIoT reader device, from the mobile communication system, a first AIoT request; and receiving, at the AIoT reader device, from the mobile communication system, second configuration information, the second configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0036] The fourth aspect may include any other feature mentioned with respect to the method of the second aspect.

[0037] A fifth aspect provides an apparatus, the apparatus having at least one processor and at least one memory having computer-readable code stored thereon which when executed controls the at least one processor to perform a method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, first configuration information, the first configuration information comprising information defining at least part of a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform AIoT communication operations with AIoT devices; receiving, at the AIoT reader device, from the mobile communication system, a first AIoT request; and receiving, at the AIoT reader device, from the mobile communication system, second configuration information, the second configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0038] The fifth aspect may include any other feature mentioned with respect to the method of the second aspect.

[0039] A sixth aspect provides a network node comprising: means for sending, to an ambient internet of things, AIoT, reader device, first configuration information, the first configuration information comprising information defining at least part of a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform AIoT communication operations with AIoT devices; means for sending, to the AIoT reader device, a first AIoT request; and means for sending, to the AIoT reader device, second configuration information, the second configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0040] In some example embodiments the second configuration information defines, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request by at least indicating at least one of: a selection from information of the first configuration information; an addition to information of the first configuration information; and a change to information of the first configuration information. In some example embodiments, the first configuration information comprises a plurality of information elements, and the second configuration information defines at least a part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request by indicating at least one selection of at least one information element of the plurality of information elements of the first configuration information.

[0041] In some example embodiments, the first configuration information defines a plurality of resource pools, and the second configuration information defines at least a part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request by indicating at least one of the plurality of resource pools for use in fulfilling the first AIoT request.

[0042] In some example embodiments, the means for sending the first configuration information is configured to send to the AIoT reader device, in a system information broadcast, at least a part of the first configuration information from which the second configuration information indicates a selection.

[0043] In some example embodiments the second configuration information indicates information elements that are additional to information elements included in the first configuration information to define at least part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0044] In some example embodiments the second configuration information indicates modifications to or replacements for information elements of the first configuration information to define at least part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0045] In some example embodiments the means for sending the first configuration information is configured to send to the AIoT reader device, as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests, at least a part of the first configuration information to which the second configuration information indicates an addition and / or change.

[0046] In some example embodiments the means for sending the second configuration information is configured to send the second configuration information via a small data transmission, SDT, procedure.

[0047] In some example embodiments the means for sending the second configuration information is configured to send the second configuration information with or as part of the AIoT request.

[0048] In some example embodiments, the network node further comprises means for receiving information associated with the first AIoT request from the AIoT reader device, and the means for sending second configuration information is configured to send second configuration information in response to the information associated with an AIoT request.

[0049] In some example embodiments, the network node further comprises means for sending, to the AIoT reader device, a second AIoT request; and means for sending, to the AIoT reader device, third configuration information, the third configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the second AIoT request.

[0050] A seventh aspect provides a method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, first configuration information, the first configuration information comprising information defining at least part of a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform AIoT communication operations with AIoT devices; sending, from the network node, to the AIoT reader device, a first AIoT request; and sending, from the network node, to the AIoT reader device, second configuration information, the second configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0051] In some example embodiments the second configuration information defines, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request by at least indicating at least one of: a selection from information of the first configuration information; an addition to information of the first configuration information; and a change to information of the first configuration information.

[0052] In some example embodiments, the first configuration information comprises a plurality of information elements, and the second configuration information defines at least a part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request by indicating at least one selection of at least one information element of the plurality of information elements of the first configuration information.

[0053] In some example embodiments, the first configuration information defines a plurality of resource pools, and the second configuration information defines at least a part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request by indicating at least one of the plurality of resource pools for use in fulfilling the first AIoT request.

[0054] In some example embodiments, sending the first configuration information comprises sending to the AIoT reader device, in a system information broadcast, at least a part of the first configuration information from which the second configuration information indicates a selection.

[0055] In some example embodiments the second configuration information indicates information elements that are additional to information elements included in the first configuration information to define at least part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0056] In some example embodiments the second configuration information indicates modifications to or replacements for information elements of the first configuration information to define at least part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0057] In some example embodiments sending the first configuration information comprises sending to the AIoT reader device, as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests, at least a part of the first configuration information to which the second configuration information indicates an addition and / or change.

[0058] In some example embodiments sending the second configuration information comprises sending the second configuration information via a small data transmission, SDT, procedure.

[0059] In some example embodiments sending the second configuration information comprises sending the second configuration information with or as part of the AIoT request.

[0060] In some example embodiments, the method further comprises receiving information associated with the first AIoT request from the AIoT reader device, and sending second configuration information comprises sending second configuration information in response to the information associated with an AIoT request.

[0061] In some example embodiments, the method further comprises sending, to the AIoT reader device, a second AIoT request; and sending, to the AIoT reader device, third configuration information, the third configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the second AIoT request.

[0062] An eighth aspect provides a computer program comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out a method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, first configuration information, the first configuration information comprising information defining at least part of a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform AIoT communication operations with AIoT devices; sending, from the network node, to the AIoT reader device, a first AIoT request; and sending, from the network node, to the AIoT reader device, second configuration information, the second configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0063] In some example embodiments, the eighth aspect may include any other feature mentioned with respect to the method of the seventh aspect.

[0064] A ninth aspect provides a non-transitory computer-readable medium having stored thereon computer-readable code, which, when executed by at least one processor, causes the at least one processor to perform a method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, first configuration information, the first configuration information comprising information defining at least part of a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform AIoT communication operations with AIoT devices; sending, from the network node, to the AIoT reader device, a first AIoT request; and sending, from the network node, to the AIoT reader device, second configuration information, the second configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0065] The ninth aspect may include any other feature mentioned with respect to the method of the seventh aspect.

[0066] A tenth aspect provides an apparatus, the apparatus having at least one processor and at least one memory having computer-readable code stored thereon which when executed controls the at least one processor to perform a method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, first configuration information, the first configuration information comprising information defining at least part of a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform AIoT communication operations with AIoT devices; sending, from the network node, to the AIoT reader device, a first AIoT request; and sending, from the network node, to the AIoT reader device, second configuration information, the second configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0067] The tenth aspect may include any other feature mentioned with respect to the method of the seventh aspect.

[0068] An eleventh aspect provides an Ambient Internet of Things, AIoT, reader device comprising : means for receiving, from a mobile communication system, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; means for sending, to the mobile communication system, a resource release request, the resource release request being a message responsive to which the mobile communication system sends a resource release indication; and means for receiving, from the mobile communication system, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

[0069] In some example embodiments, the AIoT reader device further comprises means for determining that one or more AIoT communication operations using a set of resources allocated to the reader have ended, and the means for sending, to the mobile communication system, the resource release request is configured to send the resource release request at least partially responsive to the AIoT reader device determining that the one or more AIoT communication operations have ended.

[0070] In some example embodiments, the AIoT reader device further comprises: means for receiving, from the mobile communication system, an indication of a reference signal received power, RSRP, threshold; and means for determining that an RSRP of a signal received from an AIoT device is below the RSRP threshold, and the means for sending, to the mobile communication system, the resource release request is configured to send the resource release request at least partially responsive to the reader determining that the RSRP is below the RSRP threshold. In some example embodiments, the means for receiving the indication of the RSRP threshold is configured to receive the indication of the RSRP threshold with or as part of the indication of a resource allocation. In some example embodiments, the means for receiving the indication of the RSRP threshold is configured to receive the indication of the RSRP threshold in configuration information received as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests.

[0071] In some example embodiments the AIoT reader device further comprises: means for receiving, from the mobile communication system, an indication of a radio link failure, RLF, duration threshold; and means for determining that a duration of a radio link failure between the AIoT reader device and the mobile communication system exceeds the RLF duration threshold, and the means for sending, to the mobile communication system, the resource release request is configured to send the release resource request at least partially responsive to the AIoT reader device determining that the radio link failure duration exceeds the RLF duration threshold. In some example embodiments, the means for receiving the indication of the RLF duration threshold is configured to receive the indication of the RLF duration threshold with or as part of the indication of a resource allocation. In some example embodiments the means for receiving the indication of the RLF duration threshold is configured to receive the indication of the RLF duration threshold in configuration information received as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests.

[0072] A twelfth aspect provides a method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; sending, from the AIoT reader device, to the mobile communication system, a resource release request, the resource release request being a message responsive to which the mobile communication system sends a resource release indication; and receiving, at the AIoT reader device, from the mobile communication system, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

[0073] In some example embodiments, the method further comprises determining, by the AIoT reader device, that one or more AIoT communication operations using a set of resources allocated to the reader have ended, wherein sending, to the mobile communication system, the resource release request comprises sending the resource release request at least partially responsive to the AIoT reader device determining that the one or more AIoT communication operations have ended.

[0074] In some example embodiments, the method further comprises receiving, at the AIoT reader device, from the mobile communication system, an indication of a reference signal received power, RSRP, threshold; and determining by the AIoT reader device that an RSRP of a signal received from an AIoT device is below the RSRP threshold, wherein sending, to the mobile communication system, the resource release request comprises sending the resource release request at least partially responsive to the AIoT reader device determining that the RSRP is below the RSRP threshold. In some example embodiments, receiving the indication of the RSRP threshold comprises receiving the indication of the RSRP threshold with or as part of the indication of a resource allocation. In some example embodiments, receiving the indication of the RSRP threshold comprises receiving the indication of the RSRP threshold in configuration information received as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests.

[0075] In some example embodiments, the method further comprises: receiving, at the AIoT reader device, from the mobile communication system, an indication of a radio link failure, RLF, duration threshold; and determining by the AIoT reader device that a duration of a radio link failure between the AIoT reader device and the mobile communication system exceeds the RLF duration threshold, wherein sending, to the mobile communication system, the resource release request comprises sending the release resource request at least partially responsive to the AIoT reader device determining that radio link failure duration exceeds the RLF duration threshold. In some example embodiments receiving the indication of the RLF duration threshold comprises receiving the indication of the RLF duration threshold with or as part of the indication of a resource allocation. In some example embodiments receiving the indication of the RLF duration threshold comprises receiving the indication of the RLF duration threshold in configuration information received as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests.

[0076] A thirteenth aspect provides a computer program comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out a method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; sending, from the AIoT reader device, to the mobile communication system, a resource release request, the resource release request being a message responsive to which the mobile communication system sends a resource release indication; and receiving, at the AIoT reader device, from the mobile communication system, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

[0077] In some example embodiments, the thirteenth aspect may include any other feature mentioned with respect to the method of the twelfth aspect.

[0078] A fourteenth aspect provides a non-transitory computer-readable medium having stored thereon computer-readable code, which, when executed by at least one processor, causes the at least one processor to perform a method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; sending, from the AIoT reader device, to the mobile communication system, a resource release request, the resource release request being a message responsive to which the mobile communication system sends a resource release indication; and receiving, at the AIoT reader device, from the mobile communication system, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

[0079] The fourteenth aspect may include any other feature mentioned with respect to the method of the twelfth aspect.

[0080] A fifteenth aspect provides an apparatus, the apparatus having at least one processor and at least one memory having computer-readable code stored thereon which when executed controls the at least one processor to perform a method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; sending, from the AIoT reader device, to the mobile communication system, a resource release request, the resource release request being a message responsive to which the mobile communication system sends a resource release indication; and receiving, at the AIoT reader device, from the mobile communication system, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

[0081] The fifteenth aspect may include any other feature mentioned with respect to the method of the twelfth aspect.

[0082] A sixteenth aspect provides a network node comprising: means for sending, to an ambient internet of things, AIoT, reader device, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; means for receiving, from the AIoT reader device, a resource release request; and means for sending, to the AIoT reader device, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

[0083] In some example embodiments, the network node further comprises: means for sending, to the AIoT reader device, an indication of a reference signal received power, RSRP, threshold. In some example embodiments, the means for sending the indication of the RSRP threshold is configured to send the indication of the RSRP threshold with or as part of the indication of a resource allocation. In some example embodiments, the means for sending the indication of the RSRP threshold is configured to send the indication of the RSRP threshold in configuration information sent as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests.

[0084] In some example embodiments the network node further comprises: means for sending, to the AIoT reader device, an indication of a radio link failure, RLF, duration threshold. In some example embodiments, the means for sending the indication of the RLF duration threshold is configured to send the indication of the RLF duration threshold with or as part of the indication of a resource allocation. In some example embodiments the means for sending the indication of the RLF duration threshold is configured to send the indication of the RLF duration threshold in configuration information sent as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests.

[0085] A seventeenth aspect provides a method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; receiving, at the network node, from the AIoT reader device, a resource release request; and sending, from the network node, to the AIoT reader device, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

[0086] In some example embodiments, the method further comprises sending, from the network node, to the AIoT reader device, an indication of an AIoT device reference signal received power, RSRP, threshold below which the AIoT reader device is to send the resource release request. In some example embodiments sending the indication of the RSRP threshold comprises sending the indication of the RSRP threshold with or as part of the indication of a resource allocation. In some example embodiments sending the indication of the RSRP threshold comprises sending the indication of the RSRP threshold in configuration information sent as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests.

[0087] In some example embodiments, the method further comprises sending, from the network node, to the AIoT reader device, an indication of a radio link failure, RLF, duration threshold above which the AIoT reader device is to send the resource release request. In some example embodiments, sending the indication of the RLF duration threshold comprises sending the indication of the RLF duration threshold with or as part of the indication of a resource allocation. In some example embodiments sending the indication of the RLF duration threshold comprises sending the indication of the RLF duration threshold in configuration information sent as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests.

[0088] An eighteenth aspect provides a computer program comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out a method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; receiving, at the network node, from the AIoT reader device, a resource release request; and sending, from the network node, to the AIoT reader device, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

[0089] In some example embodiments, the eighteenth aspect may include any other feature mentioned with respect to the method of the seventeenth aspect.

[0090] A nineteenth aspect provides a non-transitory computer-readable medium having stored thereon computer-readable code, which, when executed by at least one processor, causes the at least one processor to perform a method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; receiving, at the network node, from the AIoT reader device, a resource release request; and sending, from the network node, to the AIoT reader device, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

[0091] The nineteenth aspect may include any other feature mentioned with respect to the method of the seventeenth aspect.

[0092] A twentieth aspect provides an apparatus, the apparatus having at least one processor and at least one memory having computer-readable code stored thereon which when executed controls the at least one processor to perform a method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; receiving, at the network node, from the AIoT reader device, a resource release request; and sending, from the network node, to the AIoT reader device, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

[0093] The twentieth aspect may include any other feature mentioned with respect to the method of the seventeenth aspect.

[0094] A twenty-first aspect provides an Ambient Internet of Things, AIoT, reader device comprising: means for receiving, from a mobile communication system, a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices, and the configuration indicating a duration for which the configuration is validly usable; means for receiving, from the mobile communication system, a validity duration extension message, the validity duration extension message indicating an extension to the duration for which the configuration is validly usable; and means for using the configuration for at least part of the extended duration.

[0095] In some examples the AIoT reader device further comprises means for sending, to the mobile communication system, a validity duration extension request. In some examples, the configuration indicates that the AIoT reader device is allowed to send a validity duration extension request, and the means for sending the validity duration extension request are configured to send the validity extension request based at least in part on this indication.

[0096] In some examples, the AIoT reader device further comprises means for receiving, from the mobile communication system, at least one AIoT request; means for determining that the AIoT reader device will not fulfil the at least one AIoT request within the indicated duration for which the configuration is validly usable, wherein the means for sending the validity duration extension request is configured to send the validity duration extension request at least partly responsive to the determining that the AIoT reader device will not fulfil the at least one AIoT request within the indicated duration for which the configuration is validly usable.

[0097] A twenty-second aspect provides a method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices, and the configuration indicating a duration for which the configuration is validly usable; receiving, at the AIoT reader device, from the mobile communication system, a validity duration extension message, the validity duration extension message indicating an extension to the duration for which the configuration is validly usable; and using, by the AIoT reader device, the configuration for at least part of the extended duration.

[0098] In some examples the method further comprises sending, from the AIoT reader device, to the mobile communication system, a validity duration extension request. In some examples, the configuration indicates that the AIoT reader device is allowed to send a validity duration extension request, and sending the validity duration extension request is performed based at least in part on this indication.

[0099] In some examples, the method further comprises receiving, at the AIoT reader device, from the mobile communication system, at least one AIoT request; determining that the AIoT reader device will not fulfil the at least one AIoT request within the indicated duration for which the configuration is validly usable, wherein sending the validity duration extension request is performed at least partly responsive to the determining that the AIoT reader device will not fulfil the at least one AIoT request within the indicated duration for which the configuration is validly usable. A twenty-third aspect provides a computer program comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out a method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices, and the configuration indicating a duration for which the configuration is validly usable; receiving, at the AIoT reader device, from the mobile communication system, a validity duration extension message, the validity duration extension message indicating an extension to the duration for which the configuration is validly usable; and using, by the AIoT reader device, the configuration for at least part of the extended duration.

[0100] In some example embodiments, the twenty-third aspect may include any other feature mentioned with respect to the method of the twenty-second aspect.

[0101] A twenty-fourth aspect provides a non-transitory computer-readable medium having stored thereon computer-readable code, which, when executed by at least one processor, causes the at least one processor to perform a method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices, and the configuration indicating a duration for which the configuration is validly usable; receiving, at the AIoT reader device, from the mobile communication system, a validity duration extension message, the validity duration extension message indicating an extension to the duration for which the configuration is validly usable; and using, by the AIoT reader device, the configuration for at least part of the extended duration.

[0102] The twenty-fourth aspect may include any other feature mentioned with respect to the method of the twenty-second aspect.

[0103] A twenty-fifth aspect provides an apparatus, the apparatus having at least one processor and at least one memory having computer-readable code stored thereon which when executed controls the at least one processor to perform a method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices, and the configuration indicating a duration for which the configuration is validly usable; receiving, at the AIoT reader device, from the mobile communication system, a validity duration extension message, the validity duration extension message indicating an extension to the duration for which the configuration is validly usable; and using, by the AIoT reader device, the configuration for at least part of the extended duration.

[0104] The twenty-fifth aspect may include any other feature mentioned with respect to the method of the twenty-second aspect.

[0105] A twenty-sixth aspect provides a network node comprising : means for sending, to an ambient internet of things, AIoT, reader device, a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices, and the configuration indicating a duration for which the configuration is validly usable; and means for sending, to the AIoT reader device, a validity duration extension message, the validity duration extension message indicating an extension to the duration for which the configuration is validly usable.

[0106] In some example embodiments, the network node further comprises means for receiving, from the AIoT reader device, a validity duration extension request, wherein the means for sending the validity duration extension message is configured to send the validity duration extension message responsive to receiving the validity duration extension request. In some example embodiments the configuration indicates that the AIoT reader device is allowed to send a validity duration extension request.

[0107] In some example embodiments, the network node further comprises means for sending to the AIoT reader device at least one AIoT request, wherein the means for sending the validity duration extension message is configured to send the validity duration extension message at least partly responsive to the sending of at least one AIoT request.

[0108] A twenty-seventh aspect provides a method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices, and the configuration indicating a duration for which the configuration is validly usable; and sending, from the network node, to the AIoT reader device, a validity duration extension message, the validity duration extension message indicating an extension to the duration for which the configuration is validly usable. In some example embodiments, the method further comprises receiving, at the network node, from the AIoT reader device, a validity duration extension request, wherein sending the validity duration extension message is responsive to receiving the validity duration extension request. In some example embodiments the configuration indicates that the AIoT reader device is allowed to send a validity duration extension request.

[0109] In some example embodiments, the method further comprises sending to the AIoT reader device at least one AIoT request, wherein sending the validity duration extension message comprises sending the validity duration extension message at least partly responsive to sending of at least one AIoT request.

[0110] A twenty-eighth aspect provides a computer program comprising a set of instructions which, when executed on an apparatus, is configured to cause the apparatus to carry out a method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices, and the configuration indicating a duration for which the configuration is validly usable; and sending, from the network node, to the AIoT reader device, a validity duration extension message, the validity duration extension message indicating an extension to the duration for which the configuration is validly usable.

[0111] In some example embodiments, the twenty-eighth aspect may include any other feature mentioned with respect to the method of the twenty-seventh aspect.

[0112] A twenty-ninth aspect provides a non-transitory computer-readable medium having stored thereon computer-readable code, which, when executed by at least one processor, causes the at least one processor to perform a method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices, and the configuration indicating a duration for which the configuration is validly usable; and sending, from the network node, to the AIoT reader device, a validity duration extension message, the validity duration extension message indicating an extension to the duration for which the configuration is validly usable.

[0113] The twenty-ninth aspect may include any other feature mentioned with respect to the method of the twenty-seventh aspect.

[0114] A thirtieth aspect provides an apparatus, the apparatus having at least one processor and at least one memory having computer-readable code stored thereon which when executed controls the at least one processor to perform a method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices, and the configuration indicating a duration for which the configuration is validly usable; and sending, from the network node, to the AIoT reader device, a validity duration extension message, the validity duration extension message indicating an extension to the duration for which the configuration is validly usable.

[0115] The thirtieth aspect may include any other feature mentioned with respect to the method of the twenty-seventh aspect.

[0116] Brief Description of the Drawings

[0117] Example embodiments will now be described by way of non-limiting example, with reference to the accompanying drawings, in which:

[0118] Fig. 1 illustrates an example of a communication system to which examples disclosed herein may be applied;

[0119] Fig. 2 illustrates AIoT topology 1 schematically;

[0120] Fig. 3 illustrates AIoT topology 2 schematically;

[0121] Fig. 4 illustrates a method of allocating resources to an AIoT reader device in a first scenario;

[0122] Fig. 5 illustrates a method of allocating resources to an AIoT reader device in a second scenario;

[0123] Figs. 6 - 12 illustrate methods in accordance with example embodiments;

[0124] Fig. 13 is a schematic diagram of a system that may be used to implement one or more of the example embodiments; and

[0125] Fig. 14 shows tangible media for storing computer-readable code which when run by a computer may perform methods according to example embodiments described herein.

[0126] Detailed Description

[0127] The following embodiments are exemplary. Although the specification may refer to "an", "one", or "some" embodiment(s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodiment(s), or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. Further, when a particular feature, structure, or characteristic is described in connection of an embodiment, it is within the knowledge of one skilled in the art to apply such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. It shall be understood that although the terms "first," "second" and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0128] For the purposes of the present disclosure, the phrases "at least one of A or B", "at least one of A and B", and "A and / or B" means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase "A, B, and / or C" means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0129] Embodiments described may be implemented in a communication system, such as any of the following radio access technologies (RATs) : World-wide Interoperability for Micro-wave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), highspeed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, and enhanced LTE (eLTE), 5G (also called NR), or any future RAT such as 6G. Moreover, communication within the communication system may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), and / or Discrete Fourier Transform spread OFDM (DFT- s-OFDM).

[0130] As used herein, the term "network device" or "network node" refers to a node in a communication system via which user equipment may access the network and / or which is capable of controlling radio communication and managing radio resources within a cell. The network node or network device may be referred to as a base station (BS), an access point (AP) or an access node. The network device may be, depending on the applied technology, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node, a nonterrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, or an aircraft network device.

[0131] Moreover, in connection of split radio access network (RAN), the network device may refer to a centralised unit (CU) of a base station and / or a distributed unit (DU) of a base station. An interface between CU and DU may be referred to as an Fl interface in NR. In the split RAN architecture, node operations may be carried out, at least partly, in the central / centralized unit, CU, (e.g. server, host or node) operationally coupled to the DU, (e.g. a radio head / node). One CU may control one or more DUs, acting at least as transmit / receive (Tx / Rx) nodes. In some embodiments, the DUs may comprise e.g. a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the CU may comprise the layers above RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) and an internet protocol (IP) layers. Other functional splits are possible too. In practice, any processing task may be performed in either the CU or the DU and the boundary where the responsibility is shifted between the CU and the DU may depend on the applied implementation.

[0132] The term "terminal device" refers to any end device that may be capable of wireless communication. By way of example, a terminal device may be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), or a Mobile Station (MS). The terminal device may include a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and play-back appliances, vehicle-mounted wireless terminal devices, USB dongles, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like.

[0133] A term "resource", as used herein, may refer to radio resources in time domain, in frequency domain, in space domain, and / or in code domain. Some examples of resources include e.g. a physical resource block (PRB), a radio frame, a subframe, a time slot, a subband, a frequency region, a sub-carrier, a beam, etc. The term "transmission" and / or "reception" may refer to wirelessly transmitting and / or receiving via a wireless propagation channel on radio resources.

[0134] Fig. 1 illustrates an example of a communication system to which examples disclosed herein may be applied. The communication system or a cellular communication system may comprise a network node 110 providing one or more cells, such as cell 100, and a network node 112 providing one or more other cells, such as cell 102. Each cell may be, e.g., a macro cell, a micro cell, femto, or a pico cell, for example. The cell may define a coverage area or a service area of the corresponding access node.

[0135] The network node 110 may provide a user equipment (UE) 120 (one or more UEs) with wireless access to the communication system. The wireless access may comprise downlink (DL) communication from the network node to the UE 120 and uplink (UL) communication from the UE 120 to the network node. Examples of uplink channels comprise physical uplink control channel (PUCCH) for transmitting control information and physical uplink shared channel (PUSCH) for transmitting data towards the network. Examples of downlink channels comprise physical downlink control channel (PDCCH) for transmitting control information and physical downlink shared channel (PDSCH) for transmitting data towards the user equipment.

[0136] There may be a plurality of UEs 120, 122 in the system. Each of them may be served by the same or by different network nodes 110, 112. UE may be configured with dual connectivity (DC), wherein the UE, e.g. UE 120, may be connected to multiple network nodes 110, 112. The UEs 120, 122 may communicate with each other, in case device-to-device (D2D) communication interface is established between them via a so-called sidelink (SL). Such D2D communications may be referred to as machine-to-machine, peer-to-peer (P2P) communications, or vehicle-to-vehicle (V2V), for example.

[0137] In the case of multiple network nodes in the communication system, the network nodes may be connected to each other via an interface. LTE specifications call such an interface as X2 interface. An interface between an LTE node and a 5G node, or between two 5G nodes may be called Xn interface.

[0138] The network nodes 110 and 112 may be further connected via another interface to a core network 116 of the communication system. The LTE specifications specify the core network as an evolved packet core (EPC), and the core network may comprise e.g. a mobility management entity (MME) and a gateway node. The MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signalling connections between the terminal devices and the core network. The gateway node may handle data routing in the core network and to / from the terminal devices. The 5G specifications specify the core network as a 5G core (5GC). The 5G core may comprise e.g. an access and mobility management function (AMF) and a user plane function / gateway (UPF) and other functions. The AMF may handle termination of non-access stratum (NAS) signalling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The UPF node may support packet routing and forwarding, packet inspection and quality of service (QoS) handling, for example.

[0139] An Ambient Internet of Things (AIoT) device, (which may in some cases be referred to as a "tag"), may be a device that is capable of wireless communications. AIoT devices are typically less capable than UEs, and typically have lower power consumption. In some cases AIoT devices may transmit information by modulating a backscattered signal.

[0140] In a communication system comprising an AIoT device, different topologies are possible. Release 19 of the 3GPP specifications considers "topology 1" and "topology 2".

[0141] Fig. 2 illustrates topology 1 schematically. In topology 1, the AIoT device directly and bidirectionally communicates with a network node (e.g., a base station) as shown in Figure 1. The communication between the network node and the ambient loT device may include Ambient loT data and / or signaling.

[0142] Fig. 3 illustrates topology 2 schematically. In topology 2, the AIoT device communicates bidirectionally with an intermediate node between the device and base station. In this topology, the intermediate node can be a relay, IAB node, UE, repeater, etc. capable of communicating with the AIoT device. The intermediate node transfers Ambient loT data and / or signaling between BS and the Ambient loT device.

[0143] In Ambient loT topology 2 the "reader" may be an intermediate UE between the gNB and AIoT device.

[0144] In examples, a UE may be in the RRC_CONNECTED state when communicating with an AIoT device. In other examples, the UE can be in a different RRC state (such as the RRC_INACTIVE or RRC_IDLE state) when communicating with an AIoT device.

[0145] While a UE may use resources to communicate with an AIoT device, it may be advantageous to providing the mobile communication system, or a particular network node of the mobile communication system, with at least some control over which resources are used and how those resources are used in communications between a UE (acting as an AIoT reader device) and an AIoT device.

[0146] Further, it may be advantageous to provide this control in a low-latency and / or resource efficient manner.

[0147] Examples described herein therefore provide mechanisms for allocating a UE resources for transmission on the AIoT reader device / AIoT device interface (i.e., reader to device, or R2D) and / or reception on the AIoT reader device / AIoT device interface (i.e., device to reader, or D2R). Further, in some examples said mechanisms account for the UE acting as the AIoT reader device being in an RRC state other than RRC_CONNECTED.

[0148] Fig. 4 illustrates a message flow sequence 200 showing a method of allocating resources to an AIoT reader device 210 in a first scenario, to fulfil an AIoT request. The AIoT request is received from the core network 212 via network node 214. For example, core network 212 may have an AIoT function for managing AIoT devices 216, and may communicate with AIoT devices 216 via network node 214 and intermediate UE / AIoT reader device 210. Core network 212 may therefore make a decision to communicate with at least one AIoT reader devices 216, network node 214 may manage radio resources used in communicating with AIoT device(s) 216, and AIoT reader device 210 may be responsible for communicating with AIoT device(s) 216.

[0149] Message flow sequence 200 shows AIoT devices 216 1, 2, and N, however, it will be appreciated that the examples herein are applicable to scenarios in which a different number of AIoT devices are present and / or communicated with (e.g., there may be at least one AIoT device 216).

[0150] At step 220, core network 212 sends an AIoT request to network node 214. The AIoT request may generally be a request to perform communication operations with AIoT devices. The request may be addressed to a particular AIoT reader device (e.g., by the core network). The request may comprise an indication of a read and / or write operation to be performed on at least one AIoT device by the AIoT reader device.

[0151] At step 222, network node 214 sends the AIoT request to AIoT reader device 210. In the first scenario, the network node may be unable to include an indication of resources allocated for fulfilling the request when sending the request to the reader device. This could be for at least one of several reasons.

[0152] In some examples, reader 210 may be in the RRC_IN ACTIVE state. The small data transfer (SDT) procedure may be used for uplink and downlink communications below a threshold size without transitioning to an RRC_CONNECTED state, but this threshold size may be too small to include both the AIoT request and a resource allocation. The resource allocation may therefore be performed in a separate message. The resource allocation itself may be too large for the SDT procedure, so reader 210 may transition to the RRC_CONNECTED state at step 224 so that "normal" RRC_CONNECTED communication procedures may be used to transmit the resource allocation. In some embodiments the transition to the RRC_CONNECTED state may occur before the AIoT request is communicated to reader 210.

[0153] In some examples, the AIoT request, or parts of the AIoT request may be transparent to network node 214. Information present in the AIoT request but inaccessible to network node 214 may be useful determining a suitable resource allocation to reader 210, so network node 214 may send the AIoT request to reader 210 at step 222 without a resource allocation.

[0154] In some examples, reader 210 may be in an RRC_IDLE state. Network node 214 may be unable to allocate resources to an RRC_IDLE reader device, or network node 214 may be unaware of the capabilities of the reader, so may not have the information needed to determine which resources to allocate.

[0155] At step 224, reader 210 in some examples performs a state transition. For example, if the SDT procedure is insufficient to send a resource allocation message to the reader, the reader may undergo a transition from the RRC_INACTIVE to RRC_CONNECTED state. In other examples, a reader may undergo a transition from the RRC_IDLE to RRC_CONNECTED state. In some embodiments the state transition of step 224 may occur before the AIoT request is sent to the reader at step 210.

[0156] At step 226, the reader 210, having received the AIoT request, sends a resource request to network node 214. The reader may base this resource request on the AIoT request. For example, the reader may derive properties of the required resources from the AIoT request, and send these to network node 214, upon which network node 214 may determine resources to allocate. In other examples, reader 210 may send some or all of the content of the AIoT request (e.g., unmodified) to network node 214, for network node 214 to base the resource allocation on. At step 228, network node 214 sends a resource allocation message to reader 210, indicating a set of resources to use in fulfilling the AIoT request.

[0157] At step 230, the reader device 210 communicates with, or attempts to communicate with, AIoT device(s) 216 in accordance with the request, using the allocated resources.

[0158] At step 232, reader device 210 sends an AIoT report to the network node, which may be forwarded to the core network 212. The AIoT report may indicate whether reader device 210 was successful in fulfilling the request or unsuccessful (or partially successful). If the AIoT request comprised a request to retrieve data from an AIoT device, the AIoT report may comprise the retrieved data (if successfully retrieved).

[0159] Fig. 5 illustrates a message flow sequence 300 showing a method of allocating resources to an AIoT reader device 210 in a second scenario, to fulfil an AIoT request. This scenario is similar to the first scenario, except that network node 214 is able to include a resource allocation / configuration when sending the AIoT request to reader device 210. For example, relevant parts of the AIoT request from core network 212 may be readable by network node 214, allowing network node 214 to determine a resource allocation before sending the AIoT request to reader device 210. For example, reader device 210 may be in RRC_CONNECTED mode, or the reader device may be in RRC_INACTIVE mode, and the resource allocation message may be small enough to send using the SDT procedure (without transitioning to the RRC_CONNECTED mode).

[0160] Regardless of whether the first or second scenario applies, network node 214 sends a message to allocate resources to reader device 210.

[0161] Resource configuration signaling

[0162] The allocated resources may be indicated in a resource configuration. The resource configuration may comprise at least one or more of the following.

[0163] • A carrier wave (CW) frequency. This is the frequency of an activation / illumination signal received and backscattered by AIoT devices to communicate with the reader. In some examples an AIoT reader device generates this signal.

[0164] • CW Transmission power. This may be a fixed value or a range to allow the AIoT reader some power control. • Frequency Division Multiple Access (FDMA) resource blocks.

[0165] • Resource Validity Information. The resources allocated may remain valid under conditions defined in the configuration. For example, the resource validity information may include one or more of the following. o Resource validity duration. This is a duration in which the allocated resources may be validly used (e.g., the network node may allocate the same resources to another reader after the expiry of the duration). o Coverage area scope. The allocation may be valid in a defined area. This limitation on the validity of the resources may for example allow the same frequency and time resources to be allocated to an AIoT reader in a different location. This coverage area scope may be expressed in terms of the following.

[0166] ■ A geographical area. For example, if the reader is GNSS capable or other position estimation functions are available, a geographical area may suitably define a coverage area in which the allocation is valid.

[0167] ■ A list of cells. An AIoT reader may determine whether it is served by or camped on one of these cells to determine whether it is in a coverage area scope expressed in terms of a list of cells. o RSRP threshold, or cell-specific RSRP threshold. The validity of the resources may depend on the RSRP of a signal from an AIoT device received by an AIoT reader device (e.g., a D2R RSRP). By invalidating resource allocations based on a low RSRP, those resources may be made available to reader devices that are better able to use them. o A Radio Link Failure (RLF) threshold duration. Allocated resources may be considered invalid if an RLF duration exceeds the RLF threshold duration. This may allow a network node to reallocate resources in the event of an RLF.

[0168] Additionally or alternatively, the configuration may comprise the at least one of the following additional parameters.

[0169] • An access slot length (i.e., duration). This may be expressed in terms of a number of access slots between R2D cycles. Configuration of this parameter by the network node may facilitate multiple access. Configuring this parameter may also permit configuration of discontinuous transmission (DTX) and / or discontinuous reception (DRX) cycles.

[0170] • A DRX Window within access slots of R2D cycle.

[0171] • Whether the UE is allowed to request extension of the validity duration. If the network node expects that the allocated resources will not be available after expiry of the validity duration (e.g., because the resources are also allocated after the expiry of the validity duration), then disallowing extension requests may prevent unnecessary signaling where a refusal of the extension request is foreseeable at the time of resource allocation.

[0172] • Whether the UE is allowed to transition from RRC_CONNECTED to any other state (e.g., the RRC_INACTIVE STATE). Remaining in the RRC_CONNECTED state may consume more power at the AIoT reader device, but allows for higher data rates than the SDT procedure of the RRC_INACTIVE state.

[0173] The resources can be indicated with a validity time or without it. In case no validity time is indicated, the reader UE may be free to use those resources until those resources are released by the network node via a "Resource Release Indication" message, cell switch, handover, RLF and / or any other event that can be defined in the configuration configured.

[0174] In the case that the reader UE is convinced that the resources are not needed, the UE may indicate this to the network node via a "Resource Release Request" message, which may be followed by a "Resource Release Indication" from the network node.

[0175] Validity extension

[0176] Fig. 6 is a flow diagram showing example method 600.

[0177] Example method 600 may be carried out an AIoT reader device.

[0178] The method comprises step 610, which comprises receiving, from a mobile communication system, a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices, and the configuration indicating a duration for which the configuration is validly usable. Receiving from a mobile communication system may comprise receiving from a network node such as a gNB, or a radio access network access node more generally. The configuration may comprise or indicate an allocation of resources (e.g., radio resources, such as time or frequency resources, and / or conditions under which those resources are useable, such as geographical or cell limitations) for fulfilling requests, and the validity duration may allow the reuse of those resources upon the expiry of the duration. By setting the validity duration, the communication system may expect that those resources will be available upon expiry of the duration (e.g., even without further communication with the AIoT reader device). An AIoT communication operation may comprise an inventory, read, and / or write operation to be performed on at least one AIoT device by the AIoT reader device.

[0179] The method comprises step 620, which comprises receiving at the AIoT device, from the mobile communication system, a validity duration extension message, the validity duration extension message indicating an extension to the duration for which the configuration is validly usable.

[0180] Control over extension of the validity of the configuration by the communication system allows the communication system to allocate resources to avoid or reduce interference between AIoT reader devices / AIoT devices involved in different AIoT operations, while providing the flexibility to extend the validity of the configuration.

[0181] At step 630, the AIoT reader device uses the configuration for at least part of the extended duration.

[0182] In some embodiments, the method further comprises the AIoT reader device sending to the mobile communication system a validity duration extension request. This provides the AIoT reader device with the ability to indicate to the mobile communication system that an extension is desired. The mobile communication system, or a network node thereof, may send the validity duration extension responsive to receiving this message. The sending of the validity duration extension may depend on further factors, such as the resource requirements of other AIoT reader devices or user equipment.

[0183] The AIoT reader device may send the validity duration extension request based on determining that it will not fulfil an AIoT request within the validity duration of the configuration.

[0184] In some embodiments, the method comprises receiving from the mobile communication system, at least one AIoT request; determining that the AIoT reader device will not fulfil the at least one AIoT request within the indicated duration for which the configuration is validly usable, and the sending of the validity duration extension request may be at least partly responsive determining that the AIoT reader device will not fulfil the at least one AIoT request within the indicated duration for which the configuration is validly usable.

[0185] For example, if an AIoT operation of the AIoT reader device will not conclude before the expiry of the validity duration, the AIoT reader device may send a validity extension request. Sending a validity extension message may be more efficient in terms of signaling overhead than sending a new configuration.

[0186] In some examples, the mobile communication system, or a network node of said mobile communication system, may send to the AIoT reader device at least one AIoT request, and the validity duration extension message may be sent at least partly responsive to the sending of at least one AIoT request. Sending a validity duration extension message may avoid the need to send a new configuration to fulfil the AIoT request, if the AIoT reader already has a configuration with a validity duration that may be extended.

[0187] In some examples, the configuration may comprise an indication of whether the AIoT reader device is permitted to send a validity extension request. At the time of sending the configuration to the AIoT device, it may be known or predicted that a validity extension will not be possible (for example, because it may be known or expected that the resources of that configuration will be allocated to other devices upon expiry of the validity duration). Controlling permission to send a validity extension request may reduce the signaling overhead of validity extension requests where it can be foreseen that a validity extension will not be granted.

[0188] Fig. 7 is a message flow diagram showing example method 700.

[0189] At step 710 of method 700, a network node (e.g., of the mobile communication system of method 500) sends an AIoT request to an AIoT reader device.

[0190] At step 712, the network node sends an AIoT configuration to the AIoT reader device. The AIoT configuration may be sent before, after, or in the same message as the AIoT request. The AIoT configuration includes a validity duration, during which a resource allocation of the configuration is valid.

[0191] Steps 714 and 716 correspond to a first set of steps that may trigger the sending of a validity duration extension message from the network node to the AIoT reader device.

[0192] At step 714, the AIoT reader device attempts to fulfil the AIoT request using the AIoT configuration, but determines that the validity duration is insufficient to fulfil the AIoT request (e.g., not all required AIoT communication operations can be completed within the validity duration).

[0193] At step 716, the AIoT reader device sends a validity duration extension request to the network node.

[0194] Step 718 represents a second set of steps that may trigger the sending of a validity duration extension message from the network node to the AIoT reader device.

[0195] At step 718, the network node sends a further AIoT request to the AIoT reader device (the AIoT request may for example originate from the core network).

[0196] In steps 714 and 716, the AIoT reader device has an AIoT configuration that it can use, but determines that the duration will be insufficient, and indicates this to the network node.

[0197] In step 718, the network node is aware that the AIoT reader device has a configuration that it can use, but becomes aware, from the AIoT request, that the validity duration may not be sufficient in view of the new AIoT request. In both cases (step 714 and 716, and step 718) the network node may determine or receive an indication that the validity duration of a configuration at the AIoT reader is insufficient.

[0198] At step 720, the network node (in response) sends a validity duration extension message to the AIoT reader.

[0199] At step 722, the AIoT reader uses the configuration for at least a part of the extended duration (e.g., to fulfil the request of step 710, or the request of step 718).

[0200] Resource release

[0201] Fig. 8 is a flow diagram showing example method 800.

[0202] Example method 800 may be carried out an AIoT reader device.

[0203] The method comprises step 810, which comprises receiving, by an AIoT reader device, from a mobile communication system (e.g., from a network node of a mobile communication system), an indication of resources allocated (e.g., as part of an AIoT configuration) for use by the AIoT reader device in fulfilling AIoT requests. The AIoT requests may be requests to the AIoT reader device to perform communication operations with AIoT devices.

[0204] The method comprises step 820, which comprises sending, from the AIoT reader device, to the mobile communication system, a resource release request, the resource release request being a message responsive to which the mobile communication system sends a resource release indication.

[0205] The method comprises step 830, which comprises receiving, from the mobile communication system, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

[0206] This resource release procedure may allow allocated resources to be reallocated when appropriate.

[0207] The method may further comprise determining, by the AIoT reader device, that one or more AIoT communication operations using a set of resources allocated to the reader have ended, and the sending of the resource release request may be at least partially responsive to the AIoT reader device determining that the one or more AIoT communication operations have ended.

[0208] Sending a resource release request when AIoT communication operations have ended may improve resource efficiency by allowing unneeded resources to be reused (e.g., in other AIoT communication operations).

[0209] The method may further comprise receiving, at the AIoT reader device, from the mobile communication system, an indication of a reference signal received power, RSRP, threshold (which may in some examples be part of the resource allocation or AIoT configuration), and determining that an RSRP of a signal received from an AIoT device is below the RSRP threshold. The sending of the resource release request may be at least partially responsive to the AIoT reader device determining that the RSRP is below the RSRP threshold.

[0210] Sending a resource release request when the RSRP of a signal received from an AIoT device is below the RSRP threshold may allow those resources to be used more effectively by a different AIoT reader device.

[0211] In some examples the indication of the RSRP threshold is received in configuration information received as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests.

[0212] The method may further comprise receiving, at the AIoT reader device, from the mobile communication system, an indication of a radio link failure, RLF, duration threshold; and determining that a duration of a radio link failure between the AIoT reader device and the mobile communication system exceeds the RLF duration threshold. Sending the resource release request may be at least partially responsive to the AIoT reader device determining that the radio link failure duration exceeds the RLF duration threshold.

[0213] Sending a resource release request when an RLF duration exceeds a threshold may allow resources to be reallocated when RLF prevents their use in fulfilling the request.

[0214] In some examples the indication of the RLF duration threshold may be received with or as part of the indication of a resource allocation.

[0215] In some examples the indication of the RLF duration threshold is received in configuration information received as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests.

[0216] Fig. 9 is a message flow diagram showing example method 900.

[0217] At step 910 of method 900, a network node (e.g., of the mobile communication system of method 500) sends an AIoT request to an AIoT reader device.

[0218] At step 912, the network node sends an AIoT configuration to the AIoT reader device. The AIoT configuration may be sent before, after, or in the same message as the AIoT request.

[0219] Each of steps 914 - 918 corresponds to AIoT reader device activity that may motivate an AIoT reader device to send a resource release request. An AIoT reader device may be configured to send the resource release request as a result of any one of these activities, or as a result of any one of a subset of these activities.

[0220] At step 914, the AIoT reader device performs communication operations in accordance with the AIoT request. The communication operations end, and in response the method proceeds to step 920.

[0221] At step 916, the AIoT reader device performs AIoT communication operations, and determines that an RSRP from an AIoT device is below a threshold (which may be indicated in the AIoT configuration). In response the method proceeds to step 920.

[0222] At step 918, the AIoT reader device determines that an RLF duration exceeds an RLF duration threshold (which may be indicated in the AIoT configuration). In response the method proceeds to step 920.

[0223] At step 920, the AIoT reader device sends a resource release request to the network node (e.g., in response to determinations made in any one of steps 914 - 918).

[0224] At step 922, the network node sends a resource release indication to the AIoT reader device, indicating that the resources are no longer available to the AIoT reader device.

[0225] Resource allocation procedure: Static resource allocation

[0226] Resource allocation can be performed according to a "static" procedure. In static resource allocation network node 214 generates a configuration for use by AIoT reader 210 in fulfilling the AIoT request (e.g., in response to step 226 of method 200, or in response to step 220 of method 300) and provides the configuration to the AIoT reader (e.g., at step 228 of method 200, or at step 222 of method 300). As discussed in preceding portions of the description, the configuration may indicate a set of resources, validity conditions, etc.

[0227] Resource allocation procedure: Hybrid resource allocation

[0228] Resource allocation can additionally or alternatively be performed according to a "hybrid" procedure. In hybrid resource allocation, the resources are allocated in a hybrid manner.

[0229] In the hybrid procedure, the AIoT reader device obtains a "minimum" configuration, which may be considered a preliminary or baseline configuration. This minimum configuration may be configured at the time of reader registration, although this is not essential. The minimum configuration may be available at the AIoT reader and at the communication system before the AIoT request is sent to the AIoT reader device (e.g., the minimum configuration may be available at the network node and at the AIoT reader device in advance of the AIoT reader device receiving the AIoT request from the network node, or in advance of the network node receiving the AIoT request from the core network).

[0230] The minimum configuration may comprise information such as a (carrier wave) frequency of operation and FDMA resource ranges. In some examples, the minimum configuration can contain different validity durations for different operations. A validity duration for an Inventory procedure and a validity duration for a standalone read / write operation can also be included in the minimum configuration. Other potential information elements of the configuration, such as those discussed in preceding portions of the description, can be part of the minimum configuration, and the minimum configuration may configure different elements for different AIoT operations. For example, an RSRP threshold or RLF duration threshold may be different for an Inventory procedure and a standalone read / write operation.

[0231] Upon the reception of an AIoT request from the core network (e.g. step 220 and 222 of method 300) or "Resource Allocation Request" (step 226 and 228 of method 200), the network node indicates a further configuration to the reader UE. The network node can indicate this further configuration by defining it with respect to the minimum (or preliminary) configuration. For example upon triggering the AIoT request to the AIoT reader device, the network node can provide the values for the minimum configuration parameters that are different from the previously configured minimum configuration values, or otherwise indicate a change in the values (e.g., as a difference).

[0232] Further, the further configuration may include values that are not defined in the minimum configuration, and the AIoT reader device may be expected to use these values in the configuration for fulfilling the AIoT request.

[0233] If the parameters from minimum configuration are present in the "Resource Allocation Request" along with the AIoT request, the reader UE is expected to use the recently shared values, otherwise, the reader UE is expected to use the resource parameter values indicated in the minimum configuration values.

[0234] The further configuration may therefore define a configuration for use by defining additions and / or modifications to the "minimum" configuration. The further configuration may therefore be referred to as a "delta" configuration. Some, most, or all of the minimum configuration may be unaltered by the "delta" configuration, so by defining the configuration for use in fulfilling the AIoT request with respect to configuration information already present at the AIoT reader device, the size of the communication needed to indicate the configuration may be smaller than the full size of the defined configuration. This may reduce the size of the message that the network node sends to allocate resources. This may reduce latency, and / or permit the use of the SDT procedure.

[0235] Further, the AIoT request itself, or the delta configuration, may indicate a selection from the minimum configuration. Therefore, while the minimum configuration may in some examples act as a "baseline" that the delta configuration indicates additions and / or modifications to, the minimum configuration may additionally or alternatively act as a "pool" comprising configuration information, or sets of configuration information, from which a selection may be indicated. For example, the AIoT request type may indicate that a particular configuration of the minimum configuration should form the baseline. Additionally or alternatively, a resource allocation or an AIoT request (comprising a resource allocation) could indicate a resource pool.

[0236] In some embodiments, the minimum configuration may act as the "baseline" for multiple configurations (e.g., for multiple sequential AIoT requests), with a delta configuration being indicated for each.

[0237] In some embodiments, the preliminary configuration may be updated upon explicit instruction by a network node.

[0238] In some embodiments, the preliminary configuration may be updated based on the delta configuration each time a delta configuration is received (e.g., so that each subsequent delta configuration defines a configuration with respect to the previous configuration), or on explicit indication from the network node (e.g., so that indicated configurations form a new baseline that a subsequent delta configuration may be defined with respect to).

[0239] Fig. 10 is a flow diagram illustrating method 1000. Method 1000 comprises aspects of hybrid resource allocation, and may be carried out by an AIoT reader device.

[0240] The method comprises steps 1010, 1020, and 1030.

[0241] Step 1010 comprises receiving, at an AIoT reader device, from a mobile communication system, first configuration information, the first configuration information comprising information defining at least part of a configuration for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform AIoT communication operations with AIoT devices.

[0242] Step 1020 comprises receiving, at the AIoT reader device, from the mobile communication system, a first AIoT request.

[0243] Step 1030 comprises receiving, at the AIoT reader device, from the mobile communication system, second configuration information, the second configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request. By defining a configuration for use in fulfilling the received AIoT request with respect to first configuration information, the second configuration information can be smaller than the full configuration that it defines with respect to the first configuration. Latency in communicating the configuration to the AIoT reader device may therefore be reduced.

[0244] In some examples, the second configuration information defines, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the first AIoT request by at least indicating at least one of: a selection from information of the first configuration information; an addition to information of the first configuration information; and a change to information of the first configuration information.

[0245] In some examples, the first configuration information comprises a plurality of information elements, and the second configuration information defines at least a part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request by indicating at least one selection of at least one information element of the plurality of information elements of the first configuration information. By defining the configuration by reference (e.g., pointer) to first configuration information, the size of the second configuration information may be reduced without reducing the size of the defined configuration.

[0246] In some examples the first configuration information defines a plurality of resource pools, and the second configuration information defines at least a part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request by indicating at least one of the plurality of resource pools for use in fulfilling the first AIoT request.

[0247] In some examples at least a part of the first configuration information from which the second configuration information indicates a selection is received in a system information broadcast from a network node of the mobile communication system. By including at least a portion of the first configuration information (e.g., resource pools) in a system information broadcast, first configuration information can be indicated to AIoT reader devices without redundant dedicated signalling.

[0248] In some examples the second configuration information indicates information elements that are additional to information elements included in the first configuration information to define at least part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request. By indicating in the second configuration information additions to the first configuration information, elements that are not likely to be applicable to many AIoT requests (e.g., that are likely to be specific to one request) can be excluded from the first configuration information.

[0249] In some examples the second configuration information indicates modifications to or replacements for information elements of the first configuration information to define at least part of the configuration for use by the AIoT reader device in fulfilling the first AIoT request. By indicating modifications or replacements in the second configuration information, the first configuration information can include information elements that are likely to be applicable to many AIoT requests, while retaining the flexibility to replace or modify these in an AIoT request specific second configuration information if the information element is not appropriate.

[0250] In some examples at least a part of the first configuration information to which the second configuration information indicates an addition and / or change is indicated as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests. By providing the first configuration information at the reader registration stage, the first configuration information will be available to define configurations with respect to from the registration stage.

[0251] In some examples, the method further comprises fulfilling the first AIoT request using the configuration for use by the AIoT reader device in fulfilling the first AIoT request.

[0252] In some examples the second configuration information is received via the small data transmission, SDT, procedure. The SDT procedure may comprises receiving and / or transmitting data below a threshold size within a random-access procedure, without transitioning to an RRC connected state. Using the above methods may allow use of the SDT procedure, as the second configuration information may be smaller than the SDT size limit, while the configuration itself may be larger. Transitioning to the RRC connected state to transmit information would typically increase power consumption compared to using the SDT procedure.

[0253] In some examples the second configuration information is received with or as part of the AIoT request.

[0254] In some examples, the method further comprises the AIoT reader device sending information associated with the first AIoT request to the mobile communication system, and the second configuration information is sent by the mobile communication system in response to the information associated with an AIoT request. This may allow the mobile communication system to determine a suitable configuration in cases in which the AIoT request or parts of the AIoT request are transparent to all or part of the mobile communication system.

[0255] In some examples, the method further comprises receiving, at the AIoT reader device, from the mobile communication system, a second AIoT request; and receiving, at the AIoT reader device, from the mobile communication system, third configuration information, the third configuration information defining, with respect to the first configuration information, a configuration for use by the AIoT reader device in fulfilling the second AIoT request. The first configuration information may be reused so that multiple configurations may be defined with respect to it. These multiple configurations may be configurations for multiple different AIoT requests.

[0256] Resource indication

[0257] An AIoT configuration may indicate a resource allocation through dedicated resource signaling within the entire band by time / frequency resources through one or more of:

[0258] • a bitmap;

[0259] • an explicit subframe number; and

[0260] • a repetition pattern or number of repetitions.

[0261] Additionally, or alternatively, an AIoT configuration may indicate a resource allocation through mapped signaling pointing to a (pre)configured pool(s) of resources.

[0262] The resources from these (pre)configured pool(s) can be indicated using, e.g., a bit map, time allocation, a pattern, or other means.

[0263] A (pre)configured resource pool can be beneficial, as this may simplify signaling for each 'grant' from the network node to the AIoT reader device, as the resource allocation or 'grant' would not need to contain an explicit reference to all allocated resources, and could simply include a pointer towards a subset of resources.

[0264] The same resources could be negotiated across cells and each network node could be aware of these resource 'pools'.

[0265] In other examples, the (pre)configured resource pools could comprise an indication of whether they are supported by multiple cells. In some examples, in which the reader UE is in RRC_IN ACTIVE state, the AIoT resource configuration along with the AIoT request can be delivered as an SDT message. Using the above discussed approaches to reducing the size of the AIoT resource configuration message (e.g., using the hybrid approach) may enable the use of SDT.

[0266] In some examples the network node can provide an extension to the current resource allocation to an AIoT reader if a new AIoT request is triggered before the completion of the current AIoT request.

[0267] In some examples, an AIoT reader device may request early termination of resource allocation if it can complete the AIoT procedure within the validity duration. This can be indicated via a "Resource Release Request" message or via including a 'Final' indication when responding to the request (e.g., in the AIoT report). For example, this can be included in a medium access control (MAC) control element (CE) when it delivers the AIoT device response.

[0268] In response to the resource release request, the network node may send a resource release indication, indicating that the resources are no longer allocated. Additionally, or alternatively, the AIoT reader device may assume the termination of the resource allocation when the AIoT report is received (e.g., based on sending the AIoT report, or based on receiving an acknowledgement that the AIoT report was received at the network node).

[0269] In some examples, the AIoT reader may provide (e.g., at reader registration, or prior to the allocation of the resources) an indication of whether a cell change is expected or not. Based on this indication, the network node may select and indicate resources across cells (e.g., the configuration selected may be valid across multiple cells).

[0270] In some examples, the AIoT reader may, when performing an Inventory AIoT operation, provide to the network node an indication of whether the inventory replies received are from different devices from the ones expected (which may for example, occur if some other UEs are using resources provided by the network node in parallel).

[0271] Fig. 12 illustrates message flow diagram of example static resource allocation procedure 400. UE 210 is acting as an AIoT reader device. The dashed lines of the diagram indicate options (4.1, 4.1.1, 4.1.2, 4.2).

[0272] In option 4.1, at step 420, the core network 212, or a function thereof, sends an AIoT request to AIoT reader device 210 via network node 214 (which in this example is a gNB). The AIoT request passes through network node 214 and terminates at AIoT reader device 210 (i.e., without information on which network node 214 would base the resource allocation being readable by network node 214). The method may then proceed according to option 4.1.1 or 4.1.2.

[0273] In option 4.1.1, at step 422, AIoT reader device 210 determines a resource allocation needed for fulfilling the AIoT request received at step 420 (e.g., comprising resource parameters), or otherwise performs some processing of the AIoT request to determine the content of a resource allocation request. In some examples AIoT reader device 210 may determine a resource allocation needed based on information relating to at least one previous request and corresponding resource allocation.

[0274] At step 424, AIoT reader device 210 sends a resource allocation request comprising the determined resource allocation, and / or other information derived from the AIoT request at step 422.

[0275] In option 4.1.2, at step 426, AIoT reader device 210 sends some or all of the information from the AIoT request received at step 420 to network node 214.

[0276] In both of options 4.1.1 and 4.1.2, AIoT reader device 210 may send information to the network node 214 enabling it to determine a resource allocation.

[0277] At step 428, network node 214 determines resource requirements for fulfilling the AIoT request and determines a resource allocation for the AIoT reader device, based on the information received in step 424 of option 4.1.1, or step 426 of option 4.1.2. For example, the validity duration of the resource allocation / configuration could be based at least in part on a number of read / write and / or inventory operations associated with the AIoT request.

[0278] At step 430, network node 214 sends a "Resource Allocation Indication" message to the AIoT reader device 210, indicating the determined resource allocation (i.e., in a configuration for use by the AIoT reader device 210).

[0279] In option 4.2, at step 432, the AIoT request terminates at network node 214 (e.g., so that network node 214 may read portions of the AIoT request relevant to determining the resource requirements for fulfilling the request). At step 434, after receiving the AIoT request, network node 214 determines resource requirements for fulfilling the request, based on the AIoT request.

[0280] At step 436, network node 214 sends the AIoT request to AIoT reader device 210, and sends a resource allocation / configuration for use by the AIoT reader device in fulfilling the request (e.g., with or in the same message as the AIoT request).

[0281] At step 438, AIoT reader device 210 performs AIoT communication operations with the AIoT device(s) 216 associated with the request, using the configuration / allocated resources indicated at step 430 or 436 (of options 4.1 and 4.2 respectively), to fulfil the AIoT request.

[0282] Fig. 12 illustrates message flow diagram of example hybrid resource allocation procedure 500. UE 210 is acting as an AIoT reader device. The dashed lines of the diagram indicate example options (5.1, 5.2, 5.X.1, 5.X.2, 5.X.Y.1, 5.X.Y.2). These options may be combined (e.g., 5.1, 5.X.1, and 5.X.Y.2 could be combined, and referred to as example option 5.1.1.2).

[0283] At step 520, preconfigured resource pools are indicated to AIoT reader device 210. For example, these resource pools could be indicated in a system information block (SIB). These resource pools may map pools or sets of resources to references or pointers, and the SIB may indicate that these resource pools are for use in AIoT communication by AIoT reader devices. In some examples, the SIB may indicate that these resource pools are specifically for AIoT reader devices in topology 2.

[0284] At step 522, core network 212 and network node 214 perform reader selection. AIoT reader device 210 is selected as a reader.

[0285] In option 5.1, at step 524, network node 214 performs a reader registration procedure with the selected AIoT reader device(s) 210. A preliminary resource allocation (e.g., a preliminary or minimum configuration) is sent to AIoT reader device 210. In this case, the reader is provided with resource parameters.

[0286] In option 5.2, at step 526, network node 210 also performs a reader registration procedure with the selected AIoT reader device(s) 210. A preliminary resource allocation (e.g., a preliminary or minimum configuration) is indicated to AIoT reader device 210. In this case, the resource allocation is indicated by reference to the preconfigured pools indicated at step 520. For example, the preliminary resource allocation may include a bitmap, with bits of the bitmap mapping to allocated or unallocated resources or sets of resources of the resource pools.

[0287] Both step 524 of option 5.1 and step 526 or option 5.2 provide AIoT reader device with information that forms at least a part of a resource allocation / configuration for fulfilling AIoT requests.

[0288] In option 5.X.1, at step 528, network node 214 receives an AIoT request, similar to step 432 of method 400.

[0289] At step 530, network node 214 sends the AIoT request to AIoT reader device 210 along with a determined "delta" resource allocation / configuration, defining a resource allocation / configuration with respect to the information received at step 524 or 526. Network node 214 may determine the "delta" resource allocation in a similar manner to step 434 of method 400.

[0290] In option 5.X.2, at step 532, the AIoT reader device 210 receives the AIoT request, similar to step 420 of method 400.

[0291] At step 534, AIoT reader device 210 sends information to the network node 214 enabling it to determine a resource allocation. This may include some or all of the AIoT request itself (similar to step 426), or a message similar to that of step 424. In some examples, this may further include the preliminary configuration received during reader registration, or an indication of the received configuration. In some examples network node 214 may be aware of the preliminary configuration (e.g., through tracking this at the network side) without this indication from the AIoT reader device 210.

[0292] At step 536, network node 214 sends a determined "delta" resource allocation / configuration to the AIoT reader device 210, defining a resource allocation / configuration with respect to the information received at step 524 or 526. Network node 214 may determine the "delta" resource allocation in a similar manner to step 434 of method 400.

[0293] The "delta" resource allocation may include additional information not defined in the preliminary configuration. Additionally or alternatively, the "delta" resource configuration may include information or parameters that overwrite or modify the preliminary resource configuration. For example, some parameters may be undefined in the preliminary configuration, and defined in the delta configuration, while other parameters may not be suitable in view of information obtained in the AIoT request, or obtained between reader registration and receipt of the AIoT request, and the delta resource configuration may indicate replacements or updates.

[0294] At step 538, AIoT reader device 210 performs an AIoT communication operation with AIoT device(s) 216 in accordance with the AIoT request (received at step 530 or 532), using the configuration that the delta configuration (received at step 530 or 536) defines with respect to the preliminary configuration (received at step 524 or 526).

[0295] In option 5.X.Y.1, at step 540, AIoT reader device 210 may have completed the AIoT procedure, the allocated resources may no longer be needed. AIoT reader device 210 may send an explicit resource release request to network node 214 (for example, because it has determined that the resources are no longer needed, e.g., because the AIoT procedure has concluded).

[0296] In option 5.X.Y.2, at step 542, AIoT reader device 210 may send an AIoT report to network node 214, indicating that the AIoT procedure is completed. The AIoT report may explicitly indicate that the resources are no longer needed, or it may be assumed (i.e., implicit) that the resources are no longer needed by the AIoT reader 210 when it sends an AIoT report to network node 214. The AIoT report may in some examples include further information regarding the results of the AIoT procedure.

[0297] At step 544, based on the AIoT report of step 542 or resource release request of step 540, network node 215 may send a resource release indication to AIoT reader device 210, indicating that the configured resources are no longer allocated to AIoT reader device 210.

[0298] For completeness, FIG. 13 is a schematic diagram of components of one or more of the example embodiments described previously, which hereafter are referred to generically as a processing system 1800. The processing system 1800 may, for example, be comprised by the device referred to in the claims below.

[0299] The processing system 1800 may have a processor 1802, a memory 1804 closely coupled to the processor and comprised of a Random Access Memory (RAM) 1814 and a Read Only Memory (ROM) 1812, and, optionally, a user input 1810 and a display 1818. The processing system 1800 may comprise one or more network / apparatus interfaces 1808 for connection to a network / apparatus, e.g., a modem which may be wired or wireless. The network / apparatus interface 1808 may also operate as a connection to other apparatus such as device / apparatus which is not network side apparatus. Thus, direct connection between devices / apparatus without network participation is possible.

[0300] The processor 1802 is connected to each of the other components in order to control operation thereof.

[0301] The memory 1804 may comprise a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD). The ROM 1812 of the memory 1804 stores, amongst other things, an operating system 1815 and may store software applications 1816. The RAM 1814 of the memory 1804 is used by the processor 1802 for the temporary storage of data. The operating system 1815 may contain code which, when executed by the processor implements aspects of the methods 200, 300, 400, 500, 600, 700, 800, 900, and 100 described above. Note that in the case of small device / apparatus the memory can be most suitable for small size usage i.e., not always a hard disk drive (HDD) or a solid state drive (SSD) is used.

[0302] The processor 1802 may take any suitable form. For instance, it may be a microcontroller, a plurality of microcontrollers, a processor, or a plurality of processors.

[0303] The processing system 1800 may be a standalone computer, a server, a console, or a network thereof. The processing system 1800 and needed structural parts may be all inside device / apparatus such as loT device / apparatus i.e., embedded to very small size.

[0304] In some example embodiments, the processing system 1800 may also be associated with external software applications. These may be applications stored on a remote server device / apparatus and may run partly or exclusively on the remote server device / apparatus. These applications may be termed cloud-hosted applications. The processing system 1800 may be in communication with the remote server device / apparatus in order to utilize the software application stored there.

[0305] FIG. 14 shows a tangible media, in the form of a removable memory unit 1910, storing computer-readable code which when run by a computer may perform methods according to example embodiments described above. The removable memory unit 1910 may be a memory stick, e.g., a Universal Serial Bus (USB) memory stick, having internal memory 1930 storing the computer-readable code. The internal memory 1930 may be accessed by a computer system via a connector 1920. Of course, other forms of tangible storage media may be used, as will be readily apparent to those of ordinary skilled in the art. Tangible media can be any device / apparatus capable of storing data / information which data / information can be exchanged between devices / apparatus / network.

[0306] Embodiments of the present invention may be implemented in software, hardware, application logic or a combination of software, hardware and application logic. The software, application logic and / or hardware may reside on memory, or any computer media. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media. In the context of this document, a "memory" or "computer-readable medium" may be any non-transitory media or means that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer.

[0307] 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 specialised circuits such as field programmable gate arrays (FPGA), application specific integrated 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.

[0308] If desired, the different functions discussed herein may be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the abovedescribed functions may be optional or may be combined. Similarly, it will also be appreciated that the flow and signalling diagrams of Figures 4 - 12 are examples only and that various operations depicted therein may be omitted, reordered and / or combined.

[0309] It will be appreciated that the above-described example embodiments are purely illustrative and are not limiting on the scope of the invention. Other variations and modifications will be apparent to persons skilled in the art upon reading the present specification.

[0310] Moreover, the disclosure of the present application should be understood to include any novel features or any novel combination of features either explicitly or implicitly disclosed herein or any generalization thereof and during the prosecution of the present application or of any application derived therefrom, new claims may be formulated to cover any such features and / or combination of such features.

[0311] Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described example embodiments and / or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims.

[0312] It is also noted herein that while the above describes various examples, these descriptions should not be viewed in a limiting sense. Rather, there are several variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.

[0313] List of abbreviations

[0314] 5GC 5G Core

[0315] AF Application Function

[0316] AIOT Ambient Internet of Things

[0317] CN / AIoTF AIoT Function

[0318] IWCP Independent Wace Carrier Provider gNB gNodeB

[0319] UE User Equipment

[0320] SDT Small Data Transfer

[0321] RRC Radio Resource Control

[0322] RACH Random Access

[0323] MT-SDT Mobile Terminated SDT

[0324] SIB System Information Broadcast

Claims

ClaimsWhat is claimed is:

1. An ambient internet of things, AIoT, reader device comprising: means for receiving, from a mobile communication system, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; means for sending, to the mobile communication system, a resource release request, the resource release request being a message responsive to which the mobile communication system sends a resource release indication; and means for receiving, from the mobile communication system, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

2. The AIoT reader device of claim 1, further comprising means for determining that one or more AIoT communication operations using a set of resources allocated to the reader have ended, and wherein the means for sending, to the mobile communication system, the resource release request is configured to send the resource release request at least partially responsive to the AIoT reader device determining that the one or more AIoT communication operations have ended.

3. The AIoT reader device of claim 1 or claim 2, further comprising: means for receiving, from the mobile communication system, an indication of a reference signal received power, RSRP, threshold; and means for determining that an RSRP of a signal received from an AIoT device is below the RSRP threshold, and wherein the means for sending, to the mobile communication system, the resource release request is configured to send the resource release request at least partially responsive to the reader determining that the RSRP is below the RSRP threshold.

4. The AIoT reader device of claim 3, wherein the means for receiving the indication of the RSRP threshold is configured to receive the indication of the RSRP threshold with or as part of the indication of a resource allocation.

5. The AIoT reader device of claim 3, wherein the means for receiving the indication ofthe RSRP threshold is configured to receive the indication of the RSRP threshold in configuration information received as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests.

6. The AIoT reader device of any preceding claim, further comprising: means for receiving, from the mobile communication system, an indication of a radio link failure, RLF, duration threshold; and means for determining that a duration of a radio link failure between the AIoT reader device and the mobile communication system exceeds the RLF duration threshold, and wherein the means for sending, to the mobile communication system, the resource release request is configured to send the release resource request at least partially responsive to the AIoT reader device determining that the radio link failure duration exceeds the RLF duration threshold.

7. The AIoT reader device of claim 6, wherein the means for receiving the indication of the RLF duration threshold is configured to receive the indication of the RLF duration threshold with or as part of the indication of a resource allocation.

8. The AIoT reader device of claim 6, wherein the means for receiving the indication of the RLF duration threshold is configured to receive the indication of the RLF duration threshold in configuration information received as part of a registration procedure for registering the AIoT reader device as a reader for fulfilling AIoT requests.

9. A network node comprising: means for sending, to an ambient internet of things, AIoT, reader device, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; means for receiving, from the AIoT reader device, a resource release request; and means for sending, to the AIoT reader device, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

10. The network node of claim 9, further comprising means for sending, to the AIoT reader device, an indication of an AIoT device reference signal received power, RSRP, threshold below which the AIoT reader device is to send the resource release request.

11. The network node of claim 9 or 10, further comprising means for sending, to the AIoT reader device, an indication of a radio link failure, RLF, duration threshold above which the AIoT reader device is to send the resource release request.

12. A method comprising: receiving, at an ambient internet of things, AIoT, reader device, from a mobile communication system, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; sending, from the AIoT reader device, to the mobile communication system, a resource release request, the resource release request being a message responsive to which the mobile communication system sends a resource release indication; and receiving, at the AIoT reader device, from the mobile communication system, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

13. The method of claim 12, further comprising determining, by the AIoT reader device, that one or more AIoT communication operations using a set of resources allocated to the reader have ended, and wherein sending, to the mobile communication system, the resource release request comprises sending the resource release request at least partially responsive to the AIoT reader device determining that the one or more AIoT communication operations have ended.

14. The method of claim 12 or claim 13 further comprising: receiving, at the AIoT reader device, from the mobile communication system, an indication of a reference signal received power, RSRP, threshold; and determining by the AIoT reader device that an RSRP of a signal received from an AIoT device is below the RSRP threshold, and wherein sending, to the mobile communication system, the resource release request comprises sending the resource release request at least partially responsive to the AIoT reader device determining that the RSRP is below the RSRP threshold.

15. The method of any of claims 12 - 14, further comprising: receiving, at the AIoT reader device, from the mobile communication system, an indication of a radio link failure, RLF, duration threshold; and determining by the AIoT reader device that a duration of a radio link failure betweenthe AIoT reader device and the mobile communication system exceeds the RLF duration threshold, and wherein sending, to the mobile communication system, the resource release request comprises sending the release resource request at least partially responsive to the AIoT reader device determining that radio link failure duration exceeds the RLF duration threshold.

16. A method comprising: sending, from a network node, to an ambient internet of things, AIoT, reader device, an indication of resources allocated for use by the AIoT reader device in fulfilling AIoT requests, the AIoT requests being requests to the AIoT reader device to perform communication operations with AIoT devices; receiving, at the network node, from the AIoT reader device, a resource release request; and sending, from the network node, to the AIoT reader device, a resource release indication, the resource release indication indicating that a set of allocated resources is no longer allocated to the AIoT reader device.

17. The method of claim 16, further comprising sending, from the network node, to the AIoT reader device, an indication of an AIoT device reference signal received power, RSRP, threshold below which the AIoT reader device is to send the resource release request.

18. The method of claim 16 or 17, further comprising sending, from the network node, to the AIoT reader device, an indication of a radio link failure, RLF, duration threshold above which the AIoT reader device is to send the resource release request.

Images