Id assignment for unified paging

Abstract

Various example embodiments described herein relate to devices and methods for ID assignment for unified paging. One such example embodiment relates to a first device (100'), comprising: at least one processor (1510); and at least one memory (1520) storing instructions that, when executed by the at least one processor (1510), cause the first device (100') at least to: generate a trigger message, said trigger message comprising an address part identifying one or more second devices (300'), wherein the address part comprises a type field indicating an identifier type, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and transmit the trigger message to the one or more second devices (300').

Description

[0001] ID assignment for unified paging

[0002] Technical Field

[0003] Various examples embodiments described herein relate to devices and methods for ID assignment for unified paging.

[0004] Abbreviations

[0005] loT Internet of Things

[0006] A-IoT Ambient loT

[0007] PDU Protocol Data Unit

[0008] TB Transport Block

[0009] MCS Modulation and Coding Scheme

[0010] NR. New Radio

[0011] ID Identifier

[0012] Background

[0013] A-IoT refers to a category of loT devices that harness energy from the environment, such as radio waves, light, motion, and heat, to power themselves autonomously. These devices offer low maintenance or even maintenance-free operation by utilizing environmental energy while incorporating the typical functions of traditional loT devices - such as sensing, positioning, identification, and control.

[0014] Summary

[0015] Various example embodiments of the subject disclosure aim at addressing at least part of the issue and / or problems and drawbacks either explicitly described herein or otherwise apparent to a person skilled in the relevant arts to provide methods, devices and computer program products by whichindividual devices or device groups can be addressed using a unified trigger format.

[0016] Several aspects of the various example embodiments will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the various example embodiments, nor are they intended to be used to otherwise limit the scope of the subject disclosure. Other features, aspects and elements of the various example embodiments will be readily apparent to a person skilled in the art in view of the subject disclosure.

[0017] According to a first aspect, there is provided a first device, comprising:

[0018] at least one processor; and

[0019] at least one memory storing instructions that, when executed by the at least one processor, cause the first device at least to:

[0020] generate a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating an identifier type, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and

[0021] transmit the trigger message to the one or more second devices.

[0022] According to a second aspect, there is provided a second device, comprising:

[0023] at least one processor; and

[0024] at least one memory storing instructions that, when executed by the at least one processor, cause the second device at least to:

[0025] receive, from a first device, a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating at least one of the following: a full device identifier, at least one device group identifier, or at least one short device identifier, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; anddetermine, based on the trigger message, whether the second device is addressed by the trigger message or not, by:

[0026] splitting the received list of the one or more identifiers by the length indicated in the length field into a plurality of split parts; and comparing at least a part of a configured device identifier of the second device with each one of the plurality of split parts.

[0027] According to a third aspect, there is provided a method, comprising:

[0028] generating a trigger message by a first device, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating an identifier type, a length field indicating a length of one or more second identifiers, and a list of the one or more identifiers based on the type field; and

[0029] transmitting the trigger message to the one or more second devices.

[0030] According to a fourth aspect, there is provided a method, comprising:

[0031] receiving, from a first device, a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating at least one of the following : a full device identifier, at least one device group identifier, or at least one short device identifier, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and

[0032] determining, based on the trigger message, whether the device is addressed by the trigger message or not, by:

[0033] splitting the received list of the one or more identifiers by the length indicated in the length field into a plurality of split parts; and comparing at least a part of a configured device identifier of the second device with each one of the plurality of split parts.

[0034] According to a fifth aspect, there is provided a computer program product comprising code means for performing a method according to the third or fourth aspect when run on a processing means or module.According to a sixth aspect, there is provided a first device, comprising: means for generating a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating an identifier type, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and

[0035] means for transmitting the trigger message to the one or more second devices.

[0036] According to a seventh aspect, there is provided a second device, comprising:

[0037] means for receiving, from a first device, a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating at least one of the following: a full device identifier, at least one device group identifier, or at least one short device identifier, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and

[0038] means for determining, based on the trigger message, whether the second device is addressed by the trigger message or not, by:

[0039] splitting the received list of the one or more identifiers by the length indicated in the length field into a plurality of split parts; and comparing at least a part of a configured device identifier of the second device with each one of the plurality of split parts.

[0040] According to some example embodiments, at least one of the following advantages may be achieved:

[0041] • reduced power consumption in A-IoT devices;

[0042] • reduced signaling overhead;

[0043] • harmonized identification / trigger structure;

[0044] • decreased complexity;

[0045] • increased resource efficiency.Brief

[0046]

[0047] of the

[0048]

[0049] Further details, features, objects, and advantages are apparent from the following detailed description of the preferred example embodiments, which is to be taken in conjunction with the appended drawings, wherein:

[0050] Fig. 1 is a block diagram illustrating a device according to example embodiments;

[0051] Fig. 2 is a schematic diagram of a method according to example embodiments;

[0052] Fig. 3 is a block diagram illustrating a device according to example embodiments;

[0053] Fig. 4 is a schematic diagram of a method according to example embodiments;

[0054] Fig. 5 is a block diagram illustrating a device according to example embodiments;

[0055] Fig. 6 is a schematic diagram of a method according to example embodiments;

[0056] Fig. 7 is a schematic diagram illustrating a method according to example embodiments;

[0057] Fig. 8 is a schematic diagram illustrating a method according to example embodiments;

[0058] Fig. 9 is a schematic diagram illustrating a trigger message according to example embodiments;

[0059] Fig. 10 is a schematic diagram illustrating a trigger message according to example embodiments;

[0060] Fig. 11 is a schematic diagram illustrating a trigger message according to example embodiments;

[0061] Fig. 12 is a schematic diagram illustrating a trigger message according to example embodiments;

[0062] Fig. 13A is a schematic diagram illustrating a part of a trigger message according to example embodiments;Fig. 13B is a schematic diagram illustrating exemplary combined full device identifiers according to example embodiments;

[0063] Fig. 14A is a schematic diagram illustrating a part of a trigger message according to example embodiments;

[0064] Fig. 14B is a schematic diagram illustrating exemplary combined full device identifiers according to example embodiments;

[0065] Fig. 15 is a block diagram alternatively illustrating a device according to example embodiments;

[0066] Fig. 16 is a block diagram alternatively illustrating a device according to example embodiments; and

[0067] Fig. 17 is a block diagram alternatively illustrating a device according to example embodiments.

[0068] Detailed description

[0069] A-IoT provides a low power and cost effective device architecture including passive terminals and readers. The readers utilize wireless radio frequencies to facilitate non-contact, two-way data communication, allowing them to read a set of device identities and / or payload. Such a procedure is initialized using A-IoT paging.

[0070] An open problem is how to address both individual devices and device groups while using a unified format.

[0071] In A-IoT paging, adding a list of full device identifiers in the trigger message is problematic, since that could increase the size of the trigger message too much, if the address list has a variable length, or limit the number of devices that can be addressed using a single trigger message, if the address list has a fixed length. Further, if the trigger message has a flexible size, decoding of the trigger message may be more energy consuming / complex.

[0072] In A-IoT paging, the following issues may occur:• Overhead proportional to the length of the list, as well as negative impact on the A-IoT trigger message format / organization.

[0073] • Even with short IDs, address lists of variable length will require the device to conditionally read a certain minimum amount of message data (e.g. the total field length).

[0074] • A fixed list size is resource-inefficient if not fully utilized (or may prove to be too short), and conditionally including such list may again increase complexity.

[0075] There is a need for a unified format for addressing both individual devices and device groups that overcomes at least one of the above problems.

[0076] In the following, certain example embodiments are described in detail with reference to the accompanying drawings, where the features of the example embodiments can be freely combined with each other unless otherwise described. However, it is to be expressly understood that the description of certain example embodiments is provided by way of non-limiting and illustrative example only, and that it is by no way intended to be understood as limiting.

[0077] The terminology used herein is generally provided for the purpose of describing certain example embodiments only and is not intended to be limiting. In the following, all technical and scientific terms used herein may have the same meaning as commonly understood by one of ordinary skill in the art to which this subject disclosure pertains, unless otherwise defined.

[0078] References in the subject disclosure to "an example embodiment," "some example embodiments," "certain example embodiments," "various example embodiments," and the like indicate that the referenced embodiment(s) described may include particular feature(s), structure(s), or characteristic(s), but it is not necessary that every example embodiment described herein includes the particular feature(s), structure(s), or characteristic(s). Moreover, such phrases are not necessarily referring to the same example embodiment.Further, when particular feature(s), structure(s), or characteristic(s) are described in connection with an example embodiment, it is submitted that it is within the knowledge of one skilled in the art to combine such feature(s), structure(s), or characteristic(s) in connection with any other example embodiments described herein, whether or not such combination is explicitly described.

[0079] As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises", "comprising", "has", "having", "includes" and / or "including", when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0080] As used herein, the terms "the at least one" and "the one or more" mean "any one of the at least one" and "any one of the one or more", respectively.

[0081] Moreover, it is to be understood that the devices are configured to perform the corresponding methods, although in some cases only the devices or only the methods are described.

[0082] Furthermore, a computer program comprising instructions may be provided, which when executed by a device, cause the device to perform each method step. Said instructions may also be stored on a non-transitory computer readable medium. The term "non-transitory," as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., Random Access Memory (RAM) vs. Read Only Memory (ROM)).

[0083] As used herein, the trigger message may be a message to engage one or more devices in data transfer.Fig. 1 is a block diagram illustrating a device according to example embodiments. The device 100 of Fig. 1 may be a first device. The device 100 of Fig. 1 may be a reader device. The reader device may be a 5G or 6G user equipment. Fig. 2 is a schematic diagram of a method according to example embodiments. The device 100 according to Fig. 1 may perform the method of Fig. 2, but is not limited to this method. The method of Fig. 2 may be performed by the device 100 of Fig. 1, but is not limited to being performed by this device 100. In Figs. 1 and 2, optional features are shown by dashed lines.

[0084] As indicated in Fig. 1, according to example embodiments, the device 100 comprises means for generating 120 and means for transmitting 130. The device 100 may further comprise means for determining 110 and means for receiving 140.

[0085] In some example embodiments, the means for determining 110 may determine a common identifier part indicating a part of a full device identifier common to at least two devices (S210). The common identifier part may be determined using e.g. a comparison logic circuit.

[0086] The means for generating 120 generates a trigger message (S220). The trigger message comprises an address part identifying one or more devices 300, 500. The address part comprises a type field indicating an identifier type, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field.

[0087] In some example embodiments, the type field may enable indication of at least one, preferably at least two, of the following: a full device identifier, at least one device group identifier (sometimes referred to as "group ID" or "group identifier"), at least one short device identifier (sometimes referred to as "short ID") or a common identifier part followed by a list of short identifiers. In some example embodiments, the type field may enable indication of at least one of the following: a full device identifier, at least onedevice group identifier, or at least one short device identifiers. In some example embodiments, the type field may enable indication of at least the common identifier part followed by the list of short identifiers.

[0088] In some example embodiments, the address part may further comprise the common identifier part preceding the list of short device identifiers and the length field may indicate the length of the common identifier part.

[0089] In some example embodiments, the address part may further comprise one or more reserved bits R for e.g., indication of release version, format type, encoding, etc. The one or more reserved bits R may comprise a binary flag field B indicating whether the one or more identifiers listed in the trigger message are required to respond to the device 100, i.e. included in the trigger message, or prohibited from responding to the device 100, i.e. excluded in the trigger message. The type field T and the binary field B may indicate only some of the excluded devices 300, 500. The one or more reserved bits R may comprise an offset field indicating which part of the full device identifier is to be used as the short device identifier.

[0090] In some example embodiments, the short device identifier may be an identifier specifically assigned to the device 300, 500. In some example embodiments, the short device identifier may be a part of the full device identifier of the device 300, 500, e.g. lowest 16 bits. In some example embodiments, the short device identifier may be derived from the full device identifier of the device 300, 500 by e.g. truncating the full device identifier.

[0091] In some example embodiments, the device 100 may hash / protect the one or more short identifiers when generating the trigger message to ensure privacy. The one or more reserved bits R may comprise a hashing indication field indicating that the one or more short identifiers are hashed / protected. The one or more reserved bits R may comprise a hashing instruction field containing key information, such as a specific hash key, an index to a set of (pre)configured keys, etc.In some example embodiments, the length field may indicate the length of the one or more identifiers by indicating a number of the one or more identifiers.

[0092] In some example embodiments, the length of the list of the one or more identifiers may correspond to the length of the full device identifier, e.g. 96 bits.

[0093] In some example embodiments, the device 100 may determine whether to include a full device identifier, at least one device group identifier or at least one short device identifiers based on an incoming request from a higher layer, as described later with respect to Fig. 7, taking into consideration the desired reliabi litv / li nk budget of the transmission.

[0094] In some example embodiments, the one or more devices 300, 500 may be one or more second devices. The one or more devices 300, 500 may be one or more loT devices, more preferably one or more A-IoT devices. The address part may be a MAC header or a part of the MAC header, more preferably an A-IoT MAC header or a part of an A-IoT MAC header. The, the trigger message may be a paging message.

[0095] The means for transmitting 130 transmits the trigger message to the one or more devices 300, 500.

[0096] In some example embodiments, the means for receiving 140 may receive an access or response message from one or more devices 300, 500 (S240).

[0097] Fig. 3 is a block diagram illustrating a device according to example embodiments. The device 300 of Fig. 3 may be a second device. The device 300 of Fig. 3 may be an loT device, more preferably an A-IoT device. Fig. 4 is a schematic diagram of a method according to example embodiments. The device 300 according to Fig. 3 may perform the method of Fig. 4, but is notlimited to this method. The method of Fig. 4 may be performed by the device 300 of Fig. 3, but is not limited to being performed by this device 300. In Figs. 3 and 4, optional features are shown by dashed lines.

[0098] As indicated in Fig. 3, according to example embodiments, the device 300 comprises means for receiving 310 and means for determining 320. The device 300 may further comprise means for transmitting 330.

[0099] The means for receiving 310 receives, from a device 100, a trigger message. The trigger message comprises an address part identifying one or more second devices. The address part comprises a type field indicating at least one of the following: a full device identifier, at least one device group identifier, or at least on short device identifiers, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field (S410).

[0100] The means for determining 320 determines, based on the trigger message, whether the device 300 is addressed by the trigger message or not by splitting the received list of the one or more identifiers by the length indicated in the length field into a plurality of split parts, and comparing at least a part of a configured device identifier of the second device with each one of the plurality of split parts (S420).

[0101] In some example embodiments, the device 100 may be a first device. The device 100 may be a reader device. The reader device may be a 5G or 6G user equipment. The address part may be a MAC header or a part of the MAC header, more preferably an A-IoT MAC header or a part of an A-IoT MAC header. The trigger message may be a paging message.

[0102] In some example embodiments, the short device identifier may be an identifier specifically assigned to the device 300. In some example embodiments, the short device identifier may be a part of the full device identifier of the device 300. In some example embodiments, the short deviceidentifier may be derived from the full device identifier of the device 300 by e.g. truncating the full device identifier. In some example embodiments, the trigger message may indicate which part of the full device identifier forms the short device identifier.

[0103] In some example embodiments, the length field may indicate the length of the one or more identifiers by indicating the number of the one or more identifiers.

[0104] In some example embodiments, the length of the list of the one or more identifiers may correspond to the length of the full device identifier.

[0105] In some example embodiments, the address part may further comprise the one or more reserved as described above. The one or more reserved bits R may comprise the binary flag field B as described above. The type field T and the binary flag field B may indicate only some of the excluded devices 300. The one or more reserved bits R may indicate which part of the full device identifier is to be used as the short device identifier. The one or more reserved bits R may comprise the hash indication field as described above. The one or more reserved bits R may indicate the offset field as described above.

[0106] In case the trigger message indicates in the hashing indication field that the one or more short identifiers are hashed / protected and the hashing instruction field contains the key information, the means for determining 320 of device 300 may decode the one or more hashed short identifiers using the key information when determining whether the device 300 is addressed by the trigger message.

[0107] In some example embodiments, the means for transmitting 330 transmits an access or response message to the device 100 in case it is determined that the device is addressed by the trigger message (S430).In case the reserved bits indicate, e.g. using the binary flag, that the device 300 is excluded, i.e. its response is prohibited, the device 300 may not transmit the access or response message.

[0108] Fig. 5 is a block diagram illustrating a device according to example embodiments. The device 500 of Fig. 5 may be a second device. The device 500 of Fig. 5 may be an loT device, more preferably an A-IoT device. Fig. 6 is a schematic diagram of a method according to example embodiments. The device 500 according to Fig. 5 may perform the method of Fig. 6, but is not limited to this method. The method of Fig. 6 may be performed by the device 500 of Fig. 5, but is not limited to being performed by this device 500. In Figs. 5 and 6, optional features are shown by dashed lines.

[0109] As indicated in Fig. 5, according to example embodiments, the device 500 comprises means for receiving 510 and means for determining 520. The device 500 may further comprise means for transmitting 530.

[0110] The means for receiving 510 receives, from a device 100, a trigger message. The trigger message comprises an address part identifying one or more devices 500. The address part comprises a type field indicating a common identifier part indicating a part of a full device identifier common to at least two devices followed by a list of short identifiers, a length field indicating a length of the common identifier part, and the common identifier part preceding a list of short identifiers (S610).

[0111] The means for determining 520 determines, based on the trigger message, whether the device 500 is addressed by the trigger message or not by calculating a length of the short device identifiers by subtracting the length indicated in the length field from a length of a configured device identifier of the second device, splitting the received list of short device identifiers by the calculated length of short device identifiers into a plurality of split parts, combining the common identifier part with each of the plurality of split parts to obtain a plurality of full device identifiers, and comparing the configureddevice identifier of the second device with each of the obtained full device identifiers (S620).

[0112] In some example embodiments, the device 100 may be a first device. The device 100 may be a reader device. The reader device may be a 5G or 6G user equipment. The trigger message may be a paging message. The address part may be a MAC header or a part of the MAC header, more preferably an A-IoT MAC header or a part of an A-IoT MAC header.

[0113] In some example embodiments, the short device identifier may be an identifier specifically assigned to the device 500. In some example embodiments, the short device identifier may be a part of the full device identifier of the device 500. In some example embodiments, the short device identifier may be derived from the full device identifier of the device 500 by e.g. truncating the full device identifier. In some example embodiments, the trigger message may indicate which part of the full device identifier forms the short device identifier.

[0114] In some example embodiments, the address part may further comprise the one or more reserved as described above. The one or more reserved bits R may comprise the binary flag field B as described above. In some example embodiments, the type field T and the binary flag field B may indicate only some of the excluded devices 500. The one or more reserved bits R may indicate which part of the full device identifier is to be used as the short device identifier. The one or more reserved bits R may comprise the hash indication field as described above. The one or more reserved bits R may indicate the offset field as described above.

[0115] In some example embodiments, in case the trigger message indicates in the hashing indication field that the one or more short identifiers are hashed / protected and the hashing instruction field contains the key information, the means for determining 320 of device 300 may decode theone or more hashed short identifiers using the key information when determining whether the device 500 is addressed by the trigger message.

[0116] The means for transmitting 530 may transmit an access or response message to the device transmitting the trigger message, e.g. device 100, in case it is determined that the device is addressed by the trigger message (S630).

[0117] In case the reserved bits indicate, e.g. using the binary flag, that the device 500 is excluded, i.e. its response is prohibited, the device 500 may not transmit the access or response message.

[0118] Fig. 7 is a schematic diagram illustrating a method according to example embodiments. The method of Fig. 7 may be performed by the device 100.

[0119] In step 701, the device receives a request from a higher layer. In step 702, the device determines whether the request is addressing multiple specific devices or device groups. In case the request does not address multiple devices / device groups ("No" in S702), step S703 is performed. In step S703, the device generates a trigger message including the single device / group ID to be addressed. In case only one device is to be addressed using a short ID in the trigger message, masking, left and or right truncating of a full device identifier may be performed.

[0120] If the answer in step S702 is "Yes", step S704 is performed. In step S704, the device determines whether the length of the multiple device / group IDs fits within a trigger message having a fixed length, such as the length of a single full device identifier, also taking into consideration the desired reliability / link budget of the transmission. In case the length of the trigger message is fixed to a predetermined length, it may occur that not all of the multiple / group IDs fit into a single trigger message. In case the length of the multiple device / group IDs fits into a single trigger message ("Yes" in step S704), step S705 is performed. In step S705, the device generates a trigger message including the multiple device / group IDs.If the answer in step S704 is "No", step S706 is performed. In step S706, the device tests the multiple device / group IDs for a common part. In step S707, the device determines whether a common part is shared between the multiple devices / device groups, i.e. whether a common part identifier was found. If the answer in step S707 is "no", step S708 is performed. In step S708, the device generates a trigger message including the multiple device / group IDs with a length longer than the fixed length.

[0121] In case a common part is found ("Yes" in step S707), step S709 is performed. In step S709, the device splits the multiple device / group IDs into the common and multiple unique IDs. Next, in step S710, the device determines whether the common part and the full set of unique IDs fit within a trigger message having the fixed length. If the answer in step S710 is "Yes", step S711 is performed. In step S711, the device generates a trigger message including the common part and the list of (unique) IDs, having the fixed length.

[0122] In case the answer in step S710 is "No", step S712 is performed. In step S712, the device generates a trigger message including the common part and a subset of the list of (unique) IDs. In such a case, the device may generate and transmit multiple trigger messages each addressing a subset of the list of unique IDs until all devices / device groups indicated in the request are addressed.

[0123] The generated trigger messages may have the configuration as described above in example embodiments with respect to Fig. 1, depending on e.g., how many devices / groups are to be addressed, the length of the trigger message, privacy requirements, etc. That means, the generated trigger message may include reserved bits, hashed short IDs, etc.

[0124] Fig. 8 is a schematic diagram illustrating a method according to example embodiments. The method may be performed by device 300, 500.In step S801, the device determines whether it received a trigger message. In case the device did not receive a trigger message, step S801 is performed again.

[0125] In case the answer in step S801 is "Yes", step S802 is performed. In step S802, the device determines whether the trigger message addresses multiple specific devices / groups. This determination may be based on the type field and / or length field of the trigger message. In case the answer in step S802 is "No", step S803 is performed. In step S803, the device compares the device / group ID indicated in the ID field of the trigger message with its own configured device ID. Next, step S812 is performed.

[0126] If multiple specific devices / groups are addressed by the trigger message ("Yes" in step S802), step S804 is performed. In step S804, the device determines whether the trigger message indicates a list of full device / group identifiers.

[0127] In case the trigger messages indicates the list of full device / group identifiers ("Yes" in step S804), step S805 is performed. In step S805, the device splits the list of full device / group identifiers using the length indicated in the length field of the trigger message as e.g. described with respect to Fig. 4 and compares each one of the full device / group identifiers with its own configured device ID. Next, step S812 is performed.

[0128] If the answer in step S804 is "No", step S806 is performed. In step S806, the device determines whether the trigger message indicates a list of short device identifiers.

[0129] If the trigger message indicates the list of short device identifiers ("Yes" in step S806), step S807 is performed. In step S807, the device determines whether the trigger message indicates a hashing procedure.In case the answer in step S807 is "Yes", step S808 is performed. In step S808, the device unhashes the list of short device identifiers and compares each short device identifier with the configured short device identifier of the device. Splitting of the list of short device identifiers is performed as described below in step S809. Next, step S812 is performed.

[0130] If the answer in step S807 is "No", step S809 is performed. In step S809, the device splits the list of short device identifiers using the length indicated in the length field of the trigger message as e.g. described with respect to Fig.

[0131] 4 and compares each short device ID in the list of short device IDs with the configured short device ID of the device. Next, step S812 is performed.

[0132] If the answer in step S806 is "No", step S810 is performed. In step S810, the device determines whether the trigger message indicates the use of a common part.

[0133] In case the answer is "Yes" in step S810, step S811 is performed. In step S811, the device calculates the length of short device identifiers and splits the received list using the calculated length as e.g. described with respect to Fig. 6, and combines the common part ID with each unique (short) ID listed in the trigger message and compares each one of the combinations with its own configured device ID. Next, step S812 is performed.

[0134] If the answer in step S810 is "No", the procedure is ended / the device determines that the device is not addressed by the trigger message.

[0135] In step S812, the device determines whether the device is addressed by the trigger message based on the result of the comparison in step S803, S805, S809 or S811.

[0136] In case it is determined that the device is addressed by the trigger message ("Yes" in step S812), step S813 is performed.In step S813, the device initiates a reply procedure.

[0137] If the answer in step S812 is "No", step S814 is performed. In step S814, the device does nothing or goes back to sleep.

[0138] Fig. 9 is a schematic diagram illustrating a trigger message according to example embodiments.

[0139] The trigger message of Fig. 9 comprises an address part identifying one or more devices. The trigger message may further comprise trigger content, such as service type, session / paging identifier, reader identifier, resource configuration, access type, etc. The address part comprises a type field T indicating the identifier type, the length field L indicating the length of one or more identifiers, and the list of one or more identifiers ID based on the type field. As used herein, the field including the one or more identifiers may be referred to as ID field. The trigger message of Fig. 9 may be generated by device 100.

[0140] Fig. 10 is a schematic diagram illustrating a trigger message according to example embodiments.

[0141] The trigger message of Fig. 10, according to example embodiments, may correspond to the trigger message of Fig. 9, wherein the address part further comprises reserved bits R, as described above. The trigger message of Fig.

[0142] 10 shows three reserved bits R, however, the number of reserved bits R is not limited to three. The trigger message of Fig. 10 may be generated by device 100.

[0143] Fig. 11 is a schematic diagram illustrating a trigger message according to example embodiments.

[0144] The trigger message of Fig. 11, according to example embodiments, may correspond to the trigger message of Fig. 10, wherein the reserved bits Rcomprise the binary flag B indicating whether the listed IDs are required to response to the device that transmitted the trigger message or whether their response is prohibited. The trigger message of Fig. 11 may be generated by device 100.

[0145] Fig. 12 is a schematic diagram illustrating a trigger message according to example embodiments. The trigger message shown in Fig. 12 may be generated by the device 100.

[0146] In example embodiments, in the trigger message shown in Fig. 12, the following is assumed: the length of the list of one or more identifiers ID is fixed to 96 bits, as example, corresponding to the length of a full device identifier, the type field T indicates a list of short device identifiers, as example, and the length field L indicates the length of a short device identifiers to be 16 bits, as example.

[0147] In example embodiments, the device 300 receives the above trigger message.

[0148] The means for determining 320 splits the received lists of the short identifiers by the length indicated in the length field, i.e. 16 bits, and obtains six split parts. Subsequently, the means for determining 320 compares its own configured short device identifier with each one of the six splits parts. In case the configured short identifier of the device 300 matches one of the split part, the means for determining 320 determines that the device 300 is addressed by the trigger message. Accordingly, the means for transmitting 330 transmits an access or response message to the device that transmitted the trigger message, e.g. device 100.

[0149] In case the reserved bits indicate, e.g. using the binary flag, that the device 300 is excluded, i.e. its response is prohibited, the means for transmitting 330 does not transmit the access or response message.In the example embodiments above, the trigger message addressed six devices. Accordingly, it is possible to address a plurality of devices using a trigger message having an address part with a fixed length, such as the length of a single full device identifier.

[0150] In example embodiments, in the trigger message shown in Fig. 12, the following is assumed: the length of the list of one or more identifiers ID is fixed to 96 bits, as example, corresponding to the length of a full device identifier, the type field T indicates a full device identifier, as example, and the length field L indicates the length of the full device identifiers to be 96 bits, as example.

[0151] In example embodiments, the device 300 receives the above trigger message.

[0152] The means for determining 320 splits the received lists of the one full device identifier by the length indicated in the length field, i.e. 96 bits, and obtains one split part. Subsequently, the means for determining 320 compares its own configured full device identifier with the one split part. In case the configured full device identifier of the device 300 matches the one split part, the means for determining 320 determines that the device 300 is addressed by the trigger message. Accordingly, the means for transmitting 330 transmits an access or response message to the device that transmitted the trigger message, e.g. device 100.

[0153] In case the reserved bits indicate, e.g. using the binary flag, that the device 300 is excluded, i.e. its response is prohibited, the means for transmitting 330 does not transmit the access or response message.

[0154] In the example embodiments above, the trigger message addressed one single device.As a result of the above example embodiments, it is possible to address one single device or a plurality of devices using trigger messages having a harmonized structure.

[0155] Fig. 13A is a schematic diagram illustrating a part of a trigger message according to example embodiments. The part of the trigger message may be a part of a trigger message generated by the device 100.

[0156] The part of the trigger message shown in Fig. 13A, comprises the length field L indicating that the length of the common identifier part is 80 bits, and the common identifier part preceding a list of four short identifiers.

[0157] In example embodiments, the means for determining 110 of the device 100 determined the common identifier part of four devices to be addressed by the trigger message to be 80 bits.

[0158] The means for generating 120 of device 100 subsequently generated a trigger message, which indicates in the length field the length of the common part identifier, i.e. 80 bits, and comprises the common identifier part preceding the list of short device identifiers, in this case the short device identifiers of four devices, to be addressed. The type field in this case may indicate the common identifier part followed by the list of short identifiers.

[0159] Fig. 13B is a schematic diagram illustrating exemplary combined full device identifiers according to example embodiments. The combined full device identifiers may be obtained by the device 500.

[0160] In example embodiments, the means for receiving 510 of the device 500 received a trigger message including the part of the trigger message shown in Fig. 13A, in which the address part comprised the length field L indicating the length of the common identifier part, i.e. 80 bits, and the common identifier part preceding the list of short device identifiers.The means for determining 520 calculated the length of the short device identifiers by subtracting the length indicated in the length field of the trigger message from the length of the full device identifier of the device. It is assumed that the length of the configured device identifier of the device 500 is known. Here, the configured full device identifier of the device 500 is assumed to be 96 bits.

[0161] Accordingly, in this example, the length of the short device identifiers is 96 bits - 80 bits = 16 bits.

[0162] Next, the means for determining 520 split the received list of short device identifiers by the calculated length of short device identifiers, i.e. 16 bits, into a plurality of split parts, i.e. four split parts in this case.

[0163] Then, the means for determining 520 combined the common identifier part with each of the plurality of split parts to obtain a plurality of full device identifiers. In this case, four full device identifiers are obtained, as shown in Fig. 13B.

[0164] Subsequently, the means for determining 520 may compare the configured full device identifier of the device with each of the obtained full device identifiers, i.e. four full device identifiers.

[0165] In case the configured full device identifier of the device is the same as one of the obtained full device identifiers, the means for determining 120 may determine that the device is addressed by the trigger message. In case the configured full device identifier of the device is not the same as any one of the obtained full device identifiers, the means for determining 120 may determine that the device is not addressed by the trigger message.The means for transmitting 530 may transmit an access or response message to the device 100 in case it is determined that the device 500 is addressed by the trigger message.

[0166] In case it is indicated in the trigger message, using e.g. binary flag B, that the device 500 is excluded, i.e. its response is prohibited, the device 500 may not transmit an access or response message to the device 100.

[0167] Fig. 14A is a schematic diagram illustrating a part of a trigger message according to example embodiments. The part of the trigger message may be a part of a trigger message generated by the device 100. The same procedure as stated above for Fig. 13A is performed in this case, so that the description thereof is omitted.

[0168] As for the example embodiments shown in Fig. 14B, the common identifier part of three devices to be addressed is determined to be 90 bits.

[0169] Fig. 14B is a schematic diagram illustrating exemplary combined full device identifiers according to example embodiments. The combined full device identifiers may be obtained by the device 500. The same procedure as stated above for Fig. 13B is performed in this case, so that the description thereof is omitted.

[0170] As for the example embodiments shown in Fig. 14B, the length of the short device identifiers is calculated to be 6 bits (96 bits - 80 bits). After the splitting and combining, three full device identifiers are obtained, which may subsequently be used to determine whether the device 500 is addressed by the trigger message or not.

[0171] As is apparent from the above examples, if a plurality of devices, i.e., at least two devices, share a part of a device identifier (a common identifier part), it is not necessary to transmit the full device identifier of the plurality of devices. In such a case, it is possible to transmit the common identifier part and theparts of the device identifiers of the plurality of devices which allow an identification of each of the devices. As a result, it is possible to reduce the length of the trigger message, which may reduce power consumption in A-loT devices and decrease complexity with respect to decoding the trigger message.

[0172] Fig. 15 is a block diagram alternatively illustrating a device according to example embodiments. As indicated in Fig. 15, according to example embodiments, the device 100' (corresponding to the device 100) comprises a processor 1510, a memory 1520 and I / O unit 1530 capable of transmitting to and / or receiving from other network elements.

[0173] Fig. 16 is a block diagram alternatively illustrating a device according to example embodiments. As indicated in Fig. 16, according to example embodiments, the device 300' (corresponding to the device 300) comprises a processor 1610, a memory 1620 and I / O unit 1630 capable of transmitting to and / or receiving from other network elements.

[0174] Fig. 17 is a block diagram alternatively illustrating a device according to example embodiments. As indicated in Fig. 17, according to example embodiments, the device 500' (corresponding to the device 500) comprises a processor 1710, a memory 1720 and I / O unit 1730 capable of transmitting to and / or receiving from other network elements.

[0175] The memory 1520, 1620, 1720 may store respective programs assumed to include program instructions or computer program code that, when executed by the respective processor 1510, 1610, 1710, enables the respective electronic device 100', 300', 500' to operate in accordance with the example embodiments.

[0176] In general terms, the respective devices (and / or parts thereof) may represent means for performing respective operations and / or exhibiting respective functionalities, and / or the respective devices (and / or parts thereof) may havefunctions for performing respective operations and / or exhibiting respective functionalities.

[0177] When in the description it is stated that the processor (or some other means) is configured to perform some function, this is to be construed to be equivalent to a description stating that at least one processor, potentially in cooperation with computer program code stored in the memory of the respective device, is configured to cause the device to perform at least the thus mentioned function, and vice versa. Also, such function is to be construed to be equivalently implementable by specifically configured means for performing the respective function (i.e. the expression "processor configured to [cause the device to] perform xxx-ing" is construed to be equivalent to an expression such as "means for xxx-ing"), and vice versa.

[0178] For further details regarding the operability / functionality of the individual devices, reference is made to the above description in connection with any one of Figs. 1 to 14A / B, respectively.

[0179] In general, example embodiments may be implemented by computer software stored in the memory (memory resources, memory circuitry) 1520, 1620, 1720 and executable by the processor (processing resources, processing circuitry) 1510, 1610, 1710 or by hardware, or by a combination of software and / or firmware and hardware.

[0180] The memory (memory resources, memory circuitry) 1520, 1620, 1720 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, and non-transitory computer-readable media. The processor (processing resources, processing circuitry) 1510, 1610, 1710 may be of any type suitable to the local technical environment, and may include one or more of general purpose computers, special purpose computers, microprocessors,digital signal processors (DSPs) and processors based on a multi core processor architecture, as non-limiting examples.

[0181] Further, as used in this application, the term "circuitry" may refer to one or more or all of the following:

[0182] (a) hardware-only circuit implementations (such as implementations in analog, digital and / or quantum circuitry) and

[0183] (b) combinations of hardware circuit(s) and software, such as (as applicable):

[0184] (i) a combination of analog, digital and / or quantum hardware circuit(s) with software / firmware and

[0185] (ii) any or all portions of hardware processor(s) (including digital and / or quantum processor(s)) with software, and memory(ies) that work together to cause an apparatus, such as a mobile device, computing device or server, to perform various functions) and

[0186] (c) any or all portions of hardware circuit(s), such as microprocessor(s), processor(s) and / or quantum processor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

[0187] This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device.

[0188] For the purpose of the present disclosure as described herein above, it should be noted that

[0189] - method steps likely to be implemented as software code portions and being run using a processor at a network server or network entity (as examples ofdevices, apparatuses and / or modules thereof, or as examples of entities including apparatuses and / or modules therefore), are software code independent and can be specified using any known or future developed programming language as long as the functionality defined by the method steps is preserved;

[0190] - generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the embodiments and its modification in terms of the functionality implemented;

[0191] - method steps and / or devices, units or means likely to be implemented as hardware components at the above-defined apparatuses, or any module(s) thereof, (e.g., devices carrying out the functions of the apparatuses according to the embodiments as described above) are hardware independent and can be implemented using any known or future developed hardware technology or any hybrids of these, such as MOS (Metal Oxide Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter Coupled Logic), TTL (Transistor-Transistor Logic), etc., using for example ASIC (Application Specific IC (Integrated Circuit)) components, FPGA (Field-programmable Gate Arrays) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components;

[0192] - devices, units or means (e.g. the above-defined devices, or any one of their respective units / means) can be implemented as individual devices, units or means, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device, unit or means is preserved;

[0193] - a device (e.g. the above-defined devices) may be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of an apparatus or module, instead of being hardware implemented, be implemented as software in a (software) module such as a computer program or a computer program product comprising executable software code portions for execution / being run on a processor;- a device may be regarded as an apparatus or as an assembly of more than one apparatus, whether functionally in cooperation with each other or functionally independently of each other but in a same device housing, for example.

[0194] In general, it is to be noted that respective functional blocks or elements according to above-described aspects can be implemented by any known means, either in hardware and / or software, respectively, if it is only adapted to perform the described functions of the respective parts. The mentioned method steps can be realized in individual functional blocks or by individual devices, or one or more of the method steps can be realized in a single functional block or by a single device.

[0195] Generally, any method step is suitable to be implemented as software or by hardware without changing the idea of the present disclosure. Devices and means can be implemented as individual devices, but this does not exclude that they are implemented in a distributed fashion throughout the system, as long as the functionality of the device is preserved. Such and similar principles are to be considered as known to a skilled person.

[0196] Software in the sense of the present description comprises software code as such comprising code means or portions or a computer program or a computer program product for performing the respective functions, as well as software (or a computer program or a computer program product) embodied on a tangible medium such as a computer-readable (storage) medium having stored thereon a respective data structure or code means / portions or embodied in a signal or in a chip, potentially during processing thereof.

[0197] The present disclosure also covers any conceivable combination of method steps and operations described above, and any conceivable combination of nodes, devices, apparatuses, modules or elements described above, as longas the above-described concepts of methodology and structural arrangement are applicable.

[0198] It is to be understood that the various example embodiments of the subject disclosure are illustrative and non-limiting and are not intended to be construed as limiting. Various modifications and applications may be apparent to those skilled in the art without departing from the spirit and scope of the various example embodiments of the subject disclosure.

[0199] Among others, the following Items are covered by the above disclosure:

[0200] Item 1. A first device, comprising:

[0201] at least one processor; and

[0202] at least one memory storing instructions that, when executed by the at least one processor, cause the first device at least to:

[0203] generate a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating an identifier type, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and

[0204] transmit the trigger message to the one or more second devices.

[0205] Item 2. The first device according to item 1, wherein

[0206] the type field enables indication of at least one of the following:

[0207] a full device identifier,

[0208] at least one device group identifier, or

[0209] at least one short device identifier.

[0210] Item 3. The first device according to item 1 or 2, wherein

[0211] the length field indicates the length of the one or more identifiers by indicating a number of the one or more identifiers.

[0212] Item 4. The first device according to item 2 or 3, whereinthe length of the list of the one or more identifiers corresponds to the length of the full device identifier.

[0213] Item 5. The first device according to anyone of items 1 to 4, wherein the instructions, when executed by the at least one processor, further cause the first device to:

[0214] receive an access or response message from the one or more second devices.

[0215] Item 6. The first device according to anyone of items 1 to 5, wherein the first device is a reader device, and

[0216] the one or more second device are one or more internet of things, loT, devices.

[0217] Item 7. The first device according to anyone of items 1 to 6, wherein the address part is a MAC header or a part of the MAC header.

[0218] Item 8. A second device, comprising:

[0219] at least one processor; and

[0220] at least one memory storing instructions that, when executed by the at least one processor, cause the second device at least to:

[0221] receive, from a first device, a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating at least one of the following: a full device identifier, at least one device group identifier, or at least one short device identifier, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and

[0222] determine, based on the trigger message, whether the second device is addressed by the trigger message or not, by:

[0223] splitting the received list of the one or more identifiers by the length indicated in the length field into a plurality of split parts; andcomparing at least a part of a configured device identifier of the second device with each one of the plurality of split parts.

[0224] Item 9. The second device according to item 8, wherein

[0225] the length field indicates the length of the one or more identifiers by indicating a number of the one or more identifiers.

[0226] Item 10. The second device according to item 8 or 9, wherein

[0227] the length of the list of the one or more identifiers corresponds to the length of the full device identifier.

[0228] Item 11. The second device according to anyone of items 8 to 10, wherein in case it is determined that the second device is addressed by the trigger message, the instructions, when executed by the at least one processor, further cause the second device to:

[0229] transmit an access or response message to the first device.

[0230] Item 12. The second device according to anyone of items 8 to 11, wherein the first device is a reader device, and

[0231] the one or more second devices are one or more internet of things, loT, devices.

[0232] Item 13. The second device according to any one of items 8 to 12, wherein the address part is a MAC header or a part of the MAC header.

[0233] Item 14. A method, comprising:

[0234] generating a trigger message by a first device, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating an identifier type, a length field indicating a length of one or more second identifiers, and a list of the one or more identifiers based on the type field; and

[0235] transmitting the trigger message to the one or more second devices.Item 15. A method, comprising:

[0236] receiving, from a first device, a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating at least one of the following : a full device identifier, at least one device group identifier, or at least one short device identifier, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and

[0237] determining, based on the trigger message, whether the device is addressed by the trigger message or not, by:

[0238] splitting the received list of the one or more identifiers by the length indicated in the length field into a plurality of split parts; and comparing at least a part of a configured device identifier of the second device with each one of the plurality of split parts.

[0239] Item 16. A computer program product comprising code means for performing a method according to item 14 or 15 when run on a processing means or module.

[0240] Item 17. The computer program product according to item 16, wherein the computer program product is embodied on a computer-readable medium, and / or the computer program product is directly loadable into the internal memory of the computer and / or transmittable via a network by means of at least one of upload, download and push procedures.

[0241] Item 18. A first device, comprising:

[0242] means for generating a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating an identifier type, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and

[0243] means for transmitting the trigger message to the one or more second devices.Item 19. The first device according to item 18, wherein

[0244] the type field enables indication of at least one of the following:

[0245] a full device identifier,

[0246] at least one device group identifier, or

[0247] at least one short device identifier.

[0248] Item 20. The first device according to item 18 or 19, wherein

[0249] the length field indicates the length of the one or more identifiers by indicating a number of the one or more identifiers.

[0250] Item 21. The first device according to item 19 or 20, wherein

[0251] the length of the list of the one or more identifiers corresponds to the length of the full device identifier.

[0252] Item 22. The first device according to anyone of items 18 to 21, wherein the first device further comprises:

[0253] means for receiving an access or response message from the one or more second devices.

[0254] Item 23. The first device according to anyone of items 18 to 22, wherein the first device is a reader device, and

[0255] the one or more second device are one or more internet of things, loT, devices.

[0256] Item 24. The first device according to anyone of items 18 to 23, wherein the address part is a MAC header or a part of the MAC header.

[0257] Item 25. A second device, comprising:

[0258] means for receiving, from a first device, a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating at least one of the following: a full device identifier, at least one device group identifier, or atleast one short device identifier, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and

[0259] means for determining, based on the trigger message, whether the second device is addressed by the trigger message or not, by:

[0260] splitting the received list of the one or more identifiers by the length indicated in the length field into a plurality of split parts; and comparing at least a part of a configured device identifier of the second device with each one of the plurality of split parts.

[0261] Item 26. The second device according to item 25, wherein

[0262] the length field indicates the length of the one or more identifiers by indicating a number of the one or more identifiers.

[0263] Item 27. The second device according to item 25 or 26, wherein

[0264] the length of the list of the one or more identifiers corresponds to the length of the full device identifier.

[0265] Item 28. The second device according to anyone of items 25 to 27, wherein the second device further comprises:

[0266] means for transmitting transmit an access or response message to the first device.

[0267] Item 29. The second device according to anyone of items 25 to 28, wherein

[0268] the first device is a reader device, and

[0269] the one or more second devices are one or more internet of things, loT, devices.

[0270] Item 30. The second device according to any one of items 25 to 29, wherein

[0271] the address part is a MAC header or a part of the MAC header.

[0272] Item 31. A first device, comprising:at least one processor; and

[0273] at least one memory storing instructions that, when executed by the at least one processor, cause the first device at least to:

[0274] generate a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating an identifier type, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and

[0275] transmit the trigger message to the one or more second devices.

[0276] Item 32. The first device according to item 31, wherein

[0277] the type field enables indication of at least a common identifier part indicating a part of a full device identifier common to at least two devices followed by a list of short identifiers.

[0278] Item 33. The first device according to item 32, wherein

[0279] the short device identifier is a part of the full device identifier.

[0280] Item 34. The first device according to item 33, wherein

[0281] the trigger message indicates which part of the full device identifier forms the short device identifier.

[0282] Item 35. The first device according to any one of items 31 to 34, wherein the instructions, when executed by the at least one processor, further cause the first device to:

[0283] determine the common identifier part.

[0284] Item 36. The first device according to any one of items 32 to 35, wherein the address part further comprises the common identifier part preceding the list of short device identifiers, and

[0285] the length field indicates the length of the common identifier part.

[0286] Item 37. The first device according to item 35 or 36, whereinthe type field indicates the common identifier part followed by the list of short device identifiers.

[0287] Item 38. The first device according to anyone of items 31 to 37, wherein the instructions, when executed by the at least one processor, further cause the first device to:

[0288] receive an access or response message from the one or more second devices.

[0289] Item 39. The first device according to anyone of items 31 to 38, wherein the first device is a reader device, and

[0290] the one or more second devices are one or more internet of things, loT, devices.

[0291] Item 40. The first device according to anyone of items 31 to 39, wherein the address part is a MAC header or a part of the MAC header.

[0292] Item 41. A second device, comprising:

[0293] at least one processor; and

[0294] at least one memory storing instructions that, when executed by the at least one processor, cause the second device at least to:

[0295] receive, from a first device, a trigger message, said trigger message comprising an address part identifying one or more devices, wherein the address part comprises a type field indicating a common identifier part indicating a part of a full device identifier common to at least two devices followed by a list of short identifiers, a length field indicating a length of the common identifier part, and the common identifier part preceding a list of short identifiers, and

[0296] determine, based on the trigger message, whether the second device is addressed by the trigger message or not, by:

[0297] calculating a length of the short device identifiers by subtracting the length indicated in the length field of the trigger message from a length of a configured device identifier of the second device;splitting the received list of short device identifiers by the calculated length of short device identifiers into a plurality of split parts;

[0298] combining the common identifier part with each of the plurality of split parts to obtain a plurality of full device identifiers; and comparing the configured device identifier of the second device with each of the obtained full device identifiers.

[0299] Item 42. The second device according to item 41, wherein

[0300] the short device identifier is a part of the full device identifier.

[0301] Item 43. The second device according to item 42, wherein

[0302] the trigger message indicates which part of the full device identifier forms the short device identifier.

[0303] Item 44. The second device according to anyone of items 41 to 43, wherein

[0304] in case it is determined that the second device is addressed by the trigger message, the instructions, when executed by the at least one processor, further cause the second device to:

[0305] transmit an access or response message to the first device.

[0306] Item 45. The second device according to anyone of items 41 to 44, wherein

[0307] the first device is a reader device, and

[0308] the one or more second devices are one or more an internet of things, loT, devices.

[0309] Item 46. The second device according to any one of items 41 to 45, wherein

[0310] the address part is a MAC header or a part of the MAC header.

[0311] Item 47. A method, comprising:generating a trigger message by a first device, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating an identifier type, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and

[0312] transmitting the trigger message to the one or more second devices.

[0313] Item 48. A method, comprising:

[0314] receiving, from a first device, a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating a common identifier part indicating a part of a full device identifier common to at least two devices followed by a list of short identifiers, a length field indicating a length of the common identifier part, and the common identifier part preceding a list of short identifiers, and

[0315] determining, based on the trigger message, whether the second device is addressed by the trigger message or not, by:

[0316] calculating a length of the short device identifiers by subtracting the length indicated in the length field of the trigger message from a length of a configured device identifier of the second device;

[0317] splitting the received list of short device identifiers by the calculated length of short device identifiers into a plurality of split parts;

[0318] combining the common identifier part with each of the plurality of split parts to obtain a plurality of full device identifiers; and comparing the configured device identifier of the second device with each of the obtained full device identifiers.

[0319] Item 49. A computer program product comprising code means for performing a method according to item 47 or 48 when run on a processing means or module.

[0320] Item 50. The computer program product according to item 49, wherein the computer program product is embodied on a computer-readable medium,and / or the computer program product is directly loadable into the internal memory of the computer and / or transmittable via a network by means of at least one of upload, download and push procedures.

[0321] Item 51. A first device, comprising:

[0322] means for generating a trigger message, said trigger message comprising an address part identifying one or more second devices, wherein the address part comprises a type field indicating an identifier type, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; and

[0323] means for transmitting the trigger message to the one or more second devices.

[0324] Item 52. The first device according to item 51, wherein

[0325] the type field enables indication of at least a common identifier part indicating a part of a full device identifier common to at least two devices followed by a list of short identifiers.

[0326] Item 53. The first device according to item 52, wherein

[0327] the short device identifier is a part of the full device identifier.

[0328] Item 54. The first device according to item 53, wherein

[0329] the trigger message indicates which part of the full device identifier forms the short device identifier.

[0330] Item 55. The first device according to any one of items 51 to 54, wherein the first device further comprises:

[0331] means for determining the common identifier part.

[0332] Item 56. The first device according to any one of items 52 to 55, wherein the address part further comprises the common identifier part preceding the list of short device identifiers, and

[0333] the length field indicates the length of the common identifier part.Item 57. The first device according to item 55 or 56, wherein

[0334] the type field indicates the common identifier part followed by the list of short device identifiers.

[0335] Item 58. The first device according to anyone of items 51 to 57, wherein the first device further comprises:

[0336] means for receiving an access or response message from the one or more second devices.

[0337] Item 59. The first device according to anyone of items 51 to 58, wherein the first device is a reader device, and

[0338] the one or more second devices are one or more internet of things, loT, devices.

[0339] Item 60. The first device according to anyone of items 51 to 59, wherein the address part is a MAC header or a part of the MAC header.

[0340] Item 61. A second device, comprising:

[0341] means for receiving, from a first device, a trigger message, said trigger message comprising an address part identifying one or more devices, wherein the address part comprises a type field indicating a common identifier part indicating a part of a full device identifier common to at least two devices followed by a list of short identifiers, a length field indicating a length of the common identifier part, and the common identifier part preceding a list of short identifiers, and

[0342] means for determining, based on the trigger message, whether the second device is addressed by the trigger message or not, by:

[0343] calculating a length of the short device identifiers by subtracting the length indicated in the length field of the trigger message from a length of a configured device identifier of the second device;

[0344] splitting the received list of short device identifiers by the calculated length of short device identifiers into a plurality of split parts;combining the common identifier part with each of the plurality of split parts to obtain a plurality of full device identifiers; and comparing the configured device identifier of the second device with each of the obtained full device identifiers.

[0345] Item 62. The second device according to item 46, wherein

[0346] the short device identifier is a part of the full device identifier.

[0347] Item 63. The second device according to item 62, wherein

[0348] the trigger message indicates which part of the full device identifier forms the short device identifier.

[0349] Item 64. The second device according to anyone of items 61 to 63, wherein the second device further comprises:

[0350] means for transmitting an access or response message to the first device.

[0351] Item 65. The second device according to anyone of items 61 to 64, wherein

[0352] the first device is a reader device, and

[0353] the one or more second devices are one or more an internet of things, loT, devices.

[0354] Item 66. The second device according to any one of items 61 to 65, wherein

[0355] the address part is a MAC header or a part of the MAC header.

Claims

44CLAIMS1. A first device (100'), comprising:at least one processor (1510); andat least one memory (1520) storing instructions that, when executed by the at least one processor (1510), cause the first device (100') at least to:generate a trigger message, said trigger message comprising an address part identifying one or more second devices (300'), wherein the address part comprises a type field indicating an identifier type, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; andtransmit the trigger message to the one or more second devices (300').

2. The first device (100') according to claim 1, whereinthe type field enables indication of at least one of the following:a full device identifier,at least one device group identifier, orat least one short device identifier.

3. The first device (100') according to claim 1 or 2, whereinthe length field indicates the length of the one or more identifiers by indicating a number of the one or more identifiers.

4. The first device (100') according to claim 2 or 3, whereinthe length of the list of the one or more identifiers corresponds to the length of the full device identifier.

5. The first device (100') according to anyone of claims 1 to 4, wherein the instructions, when executed by the at least one processor (1510), further cause the first device (100') to:receive an access or response message from the one or more second devices (300').

456. The first device (100') according to anyone of claims 1 to 5, wherein the first device (100') is a reader device, andthe one or more second device (300') are one or more internet of things, loT, devices.

7. The first device (100') according to anyone of claims 1 to 6, wherein the address part is a MAC header or a part of the MAC header.

8. A second device (300'), comprising:at least one processor (1610); andat least one memory (1620) storing instructions that, when executed by the at least one processor (1610), cause the second device (300') at least to:receive, from a first device (100'), a trigger message, said trigger message comprising an address part identifying one or more second devices (300'), wherein the address part comprises a type field indicating at least one of the following: a full device identifier, at least one device group identifier, or at least one short device identifier, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; anddetermine, based on the trigger message, whether the second device (300') is addressed by the trigger message or not, by:splitting the received list of the one or more identifiers by the length indicated in the length field into a plurality of split parts; and comparing at least a part of a configured device identifier of the second device (300') with each one of the plurality of split parts.

9. The second device (300') according to claim 8, whereinthe length field indicates the length of the one or more identifiers by indicating a number of the one or more identifiers.

10. The second device (300') according to claim 8 or 9, wherein46the length of the list of the one or more identifiers corresponds to the length of the full device identifier.

11. The second device (300') according to anyone of claims 8 to 10, whereinin case it is determined that the second device (300') is addressed by the trigger message, the instructions, when executed by the at least one processor (1610), further cause the second device (300') to:transmit an access or response message to the first device (100').

12. The second device according to anyone of claims 8 to 11, wherein the first device (100') is a reader device, andthe one or more second devices (300') are one or more internet of things, loT, devices.

13. The second device (300') according to any one of claims 8 to 12, whereinthe address part is a MAC header or a part of the MAC header.

14. A method, comprising:generating a trigger message by a first device (100'), said trigger message comprising an address part identifying one or more second devices (300'), wherein the address part comprises a type field indicating an identifier type, a length field indicating a length of one or more second identifiers, and a list of the one or more identifiers based on the type field; and transmitting the trigger message to the one or more second devices (300').

15. A method, comprising:receiving, from a first device (100'), a trigger message, said trigger message comprising an address part identifying one or more second devices (300'), wherein the address part comprises a type field indicating at least oneof the following: a full device identifier, at least one device group identifier, or at least one short device identifier, a length field indicating a length of one or more identifiers, and a list of the one or more identifiers based on the type field; anddetermining, based on the trigger message, whether the device is addressed by the trigger message or not, by:splitting the received list of the one or more identifiers by the length indicated in the length field into a plurality of split parts; and comparing at least a part of a configured device identifier of the second device (300') with each one of the plurality of split parts.

16. A computer program product comprising code means for performing a method according to claim 14 or 15 when run on a processing means or module.

17. The computer program product according to claim 16, wherein the computer program product is embodied on a computer-readable medium, and / or the computer program product is directly loadable into the internal memory of the computer and / or transmittable via a network by means of at least one of upload, download and push procedures.

Images