Id allocation for unified paging

Abstract

Various example embodiments described herein relate to devices and methods for ID allocation 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') to at least: generate a trigger message, the trigger message comprising an address portion, the address portion identifying one or more second devices (500'), wherein the address portion comprises: a type field indicating an identifier type; a length field indicating a length of one or more identifiers; and a list of one or more identifiers based on the type field; and send the trigger message to the one or more second devices (500').

Description

Technical Field

[0001] The various example embodiments described herein relate to devices and methods for ID allocation for unified paging. abbreviation

[0002] IoT (Internet of Things)

[0003] A-IoT Environment IoT

[0004] PDU Protocol Data Unit

[0005] TB Transport Block

[0006] MCS modulation and coding scheme

[0007] NR New Radio

[0008] ID identifier Background Technology

[0009] A-IoT refers to a class of IoT devices that autonomously power themselves using energy from the environment, such as radio waves, light, motion, and heat. These devices provide low-maintenance or even maintenance-free operation by incorporating the typical functions of traditional IoT devices, such as sensing, positioning, identification, and control, while utilizing ambient energy. Summary of the Invention

[0010] Various exemplary embodiments of this disclosure are intended to address at least part of the problems and / or difficulties explicitly described herein or otherwise apparent to those skilled in the art, in order to provide methods, apparatus, and computer program products by which individual devices or groups of devices can be addressed using a uniform triggering format.

[0011] Various aspects of the various exemplary embodiments will be described in conjunction with certain aspects. These aspects are not intended to indicate key or essential features of the various exemplary embodiments, nor are they intended to be used to otherwise limit the scope of this disclosure. Other features, aspects, and elements of the various exemplary embodiments will be apparent to those skilled in the art in light of this disclosure.

[0012] According to a first aspect, a first device is provided, the first device comprising: At least one processor; and At least one memory storing instructions that, when executed by at least one processor, cause the first device to at least: A trigger message is generated, the trigger message including an address portion identifying one or more second devices, wherein the address portion includes: a type field indicating an identifier type; a length field indicating the length of one or more identifiers; and a list of the one or more identifiers based on the type field; and Send the trigger message to one or more second devices.

[0013] According to a second aspect, a second device is provided, the second device comprising: At least one processor; and At least one memory storing instructions that, when executed by at least one processor, cause the second device to at least: A trigger message is received from a first device, the trigger message including an address portion identifying one or more devices, wherein the address portion includes: a type field indicating a common identifier portion indicating a portion of a complete device identifier common to at least two devices, followed by a list of short identifiers; a length field indicating the length of the common identifier portion; and a common identifier portion preceding the list of short identifiers; and... Based on the trigger message, the following operations are performed to determine whether the second device is addressed by the trigger message: The length of the short device identifier is calculated by subtracting the length indicated in the length field of the trigger message from the length of the configured device identifier of the second device. The received list of short device identifiers is divided into multiple segments according to the calculated length of the short device identifiers; Combine the common identifier portion with each of the multiple segmented portions to obtain multiple complete device identifiers; and The configured device identifier of the second device is compared with each of the obtained complete device identifiers.

[0014] According to the third aspect, a method is provided, comprising: A trigger message is generated by a first device, the trigger message including an address portion that identifies one or more second devices, wherein the address portion includes: a type field that indicates an identifier type; a length field that indicates the length of one or more identifiers; and a list of one or more identifiers based on the type field; Send the trigger message to one or more second devices.

[0015] According to the fourth aspect, a method is provided, comprising: A trigger message is received from a first device, the trigger message including an address portion identifying one or more second devices, wherein the address portion includes: a type field indicating a common identifier portion, the common identifier portion indicating a portion of a complete device identifier common to at least two devices, the common identifier portion followed by a list of short identifiers; a length field indicating the length of the common identifier portion; and the common identifier portion preceding the list of short identifiers; and... Based on the trigger message, the following operations are performed to determine whether the second device is addressed by the trigger message: The length of the short device identifier is calculated by subtracting the length indicated in the length field of the trigger message from the length of the configured device identifier of the second device. The received list of short device identifiers is divided into multiple segments according to the calculated length of the short device identifiers; Combine the common identifier portion with each of the multiple segmented portions to obtain multiple complete device identifiers; and The configured device identifier of the second device is compared with each of the obtained complete device identifiers.

[0016] According to a fifth aspect, a computer program product is provided, the computer program product including a code component for executing the method according to the third or fourth aspect when running on a processing component or module.

[0017] According to a sixth aspect, a first device is provided, the first device comprising: A component for generating a trigger message, the trigger message including an address portion that identifies one or more second devices, wherein the address portion includes: a type field that indicates an identifier type; a length field that indicates the length of one or more identifiers; and a list of one or more identifiers based on the type field; A component used to send the trigger message to one or more second devices.

[0018] According to the seventh aspect, a second device is provided, comprising: Components for receiving a trigger message from a first device, the trigger message including an address portion identifying one or more devices, wherein the address portion includes: a type field indicating a common identifier portion indicating a portion of a complete device identifier common to at least two devices, followed by a list of short identifiers; a length field indicating the length of the common identifier portion; and a common identifier portion preceding the list of short identifiers; and The component used to determine whether the second device is addressed by the trigger message by performing the following operations based on the trigger message: The length of the short device identifier is calculated by subtracting the length indicated in the length field of the trigger message from the length of the configured device identifier of the second device. The received list of short device identifiers is divided into multiple segments according to the calculated length of the short device identifiers; Combine the common identifier portion with each of the multiple segmented portions to obtain multiple complete device identifiers; and The configured device identifier of the second device is compared with each of the obtained complete device identifiers.

[0019] According to some example embodiments, at least one of the following advantages can be achieved: • Reduce power consumption in A-IoT devices; • Reduce signaling overhead; • Coordinated identifier / trigger structure; • Reduce complexity; • Improve resource efficiency. Attached Figure Description

[0020] Further details, features, objects, and advantages will become apparent from the following detailed description of preferred exemplary embodiments, which should be taken in conjunction with the accompanying drawings, in which:

[0021] Figure 1 This is a block diagram illustrating a device according to an example embodiment;

[0022] Figure 2 This is a schematic diagram of a method according to an example embodiment;

[0023] Figure 3 This is a block diagram illustrating a device according to an example embodiment;

[0024] Figure 4 This is a schematic diagram of a method according to an example embodiment;

[0025] Figure 5 This is a block diagram illustrating a device according to an example embodiment;

[0026] Figure 6 This is a schematic diagram of a method according to an example embodiment;

[0027] Figure 7 It is a schematic diagram illustrating a method according to an example embodiment;

[0028] Figure 8 It is a schematic diagram illustrating a method according to an example embodiment;

[0029] Figure 9 This is a schematic diagram illustrating a trigger message according to an example embodiment;

[0030] Figure 10 This is a schematic diagram illustrating a trigger message according to an example embodiment;

[0031] Figure 11 This is a schematic diagram illustrating a trigger message according to an example embodiment;

[0032] Figure 12 This is a schematic diagram illustrating a trigger message according to an example embodiment;

[0033] Figure 13A This is a schematic diagram illustrating a portion of a trigger message according to an example embodiment;

[0034] Figure 13B This is a schematic diagram illustrating an exemplary combined complete device identifier according to an example embodiment;

[0035] Figure 14A This is a schematic diagram illustrating a portion of a trigger message according to an example embodiment;

[0036] Figure 14B This is a schematic diagram illustrating an exemplary combined complete device identifier according to an example embodiment;

[0037] Figure 15 The diagram alternatively illustrates a block diagram of a device according to an example embodiment;

[0038] Figure 16 The alternative diagram illustrates a block diagram of a device according to an example embodiment; and

[0039] Figure 17 The diagram alternatively illustrates a block diagram of a device according to an example embodiment. Detailed Implementation

[0040] A-IoT provides a low-power and cost-efficient device architecture comprising passive terminals and readers. Readers utilize wireless radio frequencies to facilitate contactless, two-way data communication, allowing them to read device identification sets and / or payloads. This process is initiated using A-IoT paging.

[0041] An open question is how to address both individual devices and groups of devices while using a uniform format.

[0042] In A-IoT paging, adding a complete list of device identifiers to the trigger message presents problems. If the address list has a variable length, this can excessively increase the size of the trigger message; or if the address list has a fixed length, it limits the number of devices that can be addressed using a single trigger message. Furthermore, if the trigger message has a flexible size, decoding the trigger message can be more energy-intensive and complex.

[0043] In A-IoT paging, the following issues may arise: • Overhead proportional to the length of the list, and negative impact on the format / organization of A-IoT trigger messages. • Even with short IDs, variable-length address lists will require the device to conditionally read a minimum amount of message data (e.g., total field length). • If not fully utilized, a fixed list size is resource inefficient (or may prove too short), and conditionally including such a list may again increase complexity.

[0044] A unified format for addressing both individual devices and groups of devices needs to be developed to overcome at least one of the aforementioned problems.

[0045] In the following description, certain exemplary embodiments are described in detail with reference to the accompanying drawings. Unless otherwise stated, the features of these exemplary embodiments can be freely combined with each other. However, it should be clearly understood that the description of certain exemplary embodiments is provided by way of non-limiting and illustrative example only and is absolutely not intended to be construed as limiting.

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

[0047] References to “one example embodiment,” “some example embodiments,” “certain example embodiments,” “various example embodiments,” etc., in this disclosure indicate that the referenced embodiments may include specific features, structures, or characteristics, but not every example embodiment described herein necessarily includes specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same example embodiment. Moreover, when specific features, structures, or characteristics are described in conjunction with example embodiments, those skilled in the art will consider that combining such features, structures, or characteristics in conjunction with any other example embodiments described herein (whether such combinations are explicitly described or not) to be within the knowledge of those skilled in the art.

[0048] As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that, when used herein, the terms “comprising,” “including,” “having,” “having,” “including,” and / or “containing” specify the presence of the stated feature, element, and / or component, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0049] As used herein, the terms “at least one” and “one or more” respectively mean “any one of at least one” and “any one of one or more”.

[0050] Furthermore, it will be understood that the device is configured to execute the corresponding method, although in some cases only the device or only the method is described.

[0051] In addition, a computer program comprising instructions which, when executed by a device, cause the device to perform each method step. The instructions may also be stored on a non-transitory computer-readable medium. As used herein, the term “non-transitory” refers to a limitation of the medium itself (i.e., tangible, not tactile), rather than a limitation of the persistence of data storage (e.g., random access memory (RAM) and read-only memory (ROM)).

[0052] As used in this article, a trigger message is a message that enables one or more devices to participate in data transmission.

[0053] Figure 1 This is a block diagram illustrating a device according to an example embodiment. Figure 1 Device 100 can be the first device. Figure 1 The device 100 can be a reader device. The reader device can be a 5G or 6G user equipment. Figure 2This is a schematic diagram of a method according to an example embodiment. According to Figure 1 Device 100 can perform Figure 2 This method is applicable, but not limited to this method. Figure 2 The method can be derived from Figure 1 The execution is performed by device 100, but is not limited to execution by device 100. Figure 1 and Figure 2 In the diagram, optional features are indicated by dashed lines.

[0054] like Figure 1 As indicated in the example embodiment, device 100 includes a component 120 for generating and a component 130 for transmitting. Device 100 may also include a component 110 for determining and a component 140 for receiving.

[0055] In some example embodiments, the component 110 used for determination may determine a common identifier portion that indicates a portion of a complete device identifier common to at least two devices (S210). This common identifier portion may be determined using, for example, comparison logic circuitry.

[0056] A component generation trigger message (S220) is used to generate component 120. This trigger message includes an address portion that identifies one or more devices 300, 500. The address portion includes a type field indicating the identifier type; a length field indicating the length of one or more identifiers; and a list of one or more identifiers based on the type field.

[0057] In some example embodiments, the type field may enable an indication of at least one (preferably at least two) of the following: a complete device identifier, at least one device group identifier (sometimes referred to as a “group ID” or “group identifier”), at least one short device identifier (sometimes referred to as a “short ID”), or a public identifier portion followed by a list of short identifiers. In some example embodiments, the type field may enable an indication of at least one of the following: a complete device identifier, at least one device group identifier, or at least one short device identifier. In some example embodiments, the type field may enable an indication of at least a public identifier portion followed by a list of short identifiers.

[0058] In some example embodiments, the address portion may also include a common identifier portion preceding the short device identifier list, and the length field may indicate the length of the common identifier portion.

[0059] In some example embodiments, the address portion may also include one or more reserved bits R, for example, indications of release version, format type, encoding, etc. One or more reserved bits R may include a binary flag field B indicating whether one or more identifiers listed in the trigger message are required to respond to device 100 (i.e., included in the trigger message) or are prohibited from responding to device 100 (i.e., excluded from the trigger message). The type field T and binary field B may indicate only some of the excluded devices 300, 500. One or more reserved bits R may include an offset field indicating which portion of the complete device identifier will be used as the short device identifier.

[0060] In some example embodiments, the short device identifier may be an identifier specifically assigned to devices 300 and 500. In some example embodiments, the short device identifier may be a part of the complete device identifier of devices 300 and 500, for example, the lowest 16 bits. In some example embodiments, the short device identifier may be derived from the complete device identifier of devices 300 and 500, for example, by truncating the complete device identifier.

[0061] In some example embodiments, device 100 may hash / protect one or more short identifiers when generating a trigger message to ensure privacy. One or more reserved bits R may include a hash indicator field indicating that one or more short identifiers are hashed / protected. One or more reserved bits R may include a hash instruction field containing key information such as a specific hash key, an index of a set of (pre)configured keys, etc.

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

[0063] In some example embodiments, the length of the list of one or more identifiers may correspond to the length of the complete device identifier, such as 96 bits.

[0064] In some example embodiments, device 100 may base its request on an incoming request from a higher layer (as will be discussed later). Figure 7 The description determines whether to include a complete device identifier, at least one device group identifier, or at least one short device identifier. Considering the required reliability / link budget for transmission .

[0065] 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 IoT devices, more preferably, one or more A-IoT devices. The address portion may be a MAC header or a portion thereof, more preferably, an A-IoT MAC header or a portion thereof. The trigger message may be a paging message.

[0066] The component 130, used for sending, sends a trigger message to one or more devices 300, 500.

[0067] In some example embodiments, the receiving component 140 may receive access or response messages from one or more devices 300, 500 (S240).

[0068] Figure 3 This is a block diagram illustrating a device according to an example embodiment. Figure 3 Device 300 can be a second device. Figure 3 The device 300 can be an IoT device, more preferably an A-IoT device. Figure 4 This is a schematic diagram of a method according to an example embodiment. According to Figure 3 Device 300 can perform Figure 4 This method, but not limited to this method. Figure 4 The method can be derived from Figure 3 The execution is performed by device 300, but is not limited to execution by device 300. Figure 3 and Figure 4 In the diagram, optional features are indicated by dashed lines.

[0069] like Figure 3 As shown, according to an example embodiment, device 300 includes a receiving component 310 and a determining component 320. Device 300 may also include a transmitting component 330.

[0070] The receiving component 310 receives a trigger message from the device 100. The trigger message includes an address portion that identifies one or more second devices. The address portion includes a type field that indicates 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 that indicates the length of one or more identifiers; and a list of one or more identifiers based on the type field (S410).

[0071] The component used to determine 320 determines whether device 300 is addressed by the trigger message by dividing a list of one or more received identifiers into multiple segments according to the length indicated in the length field, and comparing at least a portion of the configured device identifier of the second device with each of the multiple segments (S420).

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

[0073] In some example embodiments, the short device identifier may be an identifier specifically assigned to device 300. In some example embodiments, the short device identifier may be a portion of the complete device identifier of device 300. In some example embodiments, the short device identifier may be derived from the complete device identifier of device 300, for example, by truncating the complete device identifier. In some example embodiments, a triggering message may indicate which portion of the complete device identifier forms the short device identifier.

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

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

[0076] In some example embodiments, the address portion may also include one or more reserved bits as described above. One or more reserved bits R may include 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. One or more reserved bits R may indicate which part of the complete device identifier will be used as the short device identifier. One or more reserved bits R may include the hash indicator field as described above. One or more reserved bits R may indicate the offset field as described above.

[0077] If the trigger message indicates in the hash indication field that one or more short identifiers are hashed / protected and the hash instruction field contains key information, the determination component 320 of device 300 may use the key information to decode one or more hashed short identifiers when determining whether device 300 is addressed by the trigger message.

[0078] In some example embodiments, when it is determined that device 100 is addressed by a trigger message, the sending component 320 sends an access or response message to device 100 (S430).

[0079] If a reserved bit (e.g., using a binary flag) indicates that device 300 is excluded (i.e., its response is disabled), device 300 may not send an access or response message.

[0080] Figure 5 This is a block diagram illustrating a device according to an example embodiment. Figure 5 Device 500 can be a second device. Figure 5 The device 500 can be an IoT device, more preferably an A-IoT device. Figure 6 This is a schematic diagram of a method according to an example embodiment. Figure 5 Device 500 can perform Figure 6 This method is applicable, but not limited to this method. Figure 6 The method can be derived from Figure 5 The device 500 executes the commands, but it is not limited to execution by that device 500. Figure 5 and Figure 6 In the diagram, optional features are indicated by dashed lines.

[0081] like Figure 5 As indicated in the example embodiment, device 500 includes a receiving component 510 and a determining component 520. Device 500 may also include a transmitting component 530.

[0082] The receiving component 510 receives a trigger message from device 100. The trigger message includes an address portion that identifies one or more devices 500. The address portion includes a type field that indicates a common identifier portion that indicates a portion of a complete device identifier common to at least two devices, followed by a list of short identifiers; a length field that indicates the length of the common identifier portion; and a common identifier portion preceding the list of short identifiers (S610).

[0083] The component 520 used for determination determines whether device 500 is addressed by trigger message based on the trigger message by: calculating the length of the short device identifier by subtracting the length indicated in the length field from the length of the configured device identifier of the second device; dividing the received list of short device identifiers into multiple segments according to the calculated length; combining the common identifier portion with each of the multiple segments to obtain multiple complete device identifiers; and comparing the configured device identifier of the second device with each of the obtained complete device identifiers (S620).

[0084] In some example embodiments, device 100 may be a first device. 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 portion may be a MAC header or a portion thereof, more preferably, an A-IoT MAC header or a portion thereof.

[0085] In some example embodiments, the short device identifier may be an identifier specifically assigned to device 500. In some example embodiments, the short device identifier may be a portion of the complete device identifier of device 500. In some example embodiments, the short device identifier may be derived from the complete device identifier of device 500, for example, by truncating the complete device identifier. In some example embodiments, a triggering message may indicate which portion of the complete device identifier forms the short device identifier.

[0086] In some example embodiments, the address portion may also include one or more reserved bits as described above. One or more reserved bits R may include 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 500. One or more reserved bits R may indicate which part of the complete device identifier will be used as the short device identifier. One or more reserved bits R may include the hash indicator field as described above. One or more reserved bits R may indicate the offset field as described above.

[0087] If the trigger message indicates in the hash indication field that one or more short identifiers are hashed / protected and the hash instruction field contains key information, the determination component 320 of device 300 may use the key information to decode one or more hashed short identifiers when determining whether device 500 is addressed by the trigger message.

[0088] If it is determined that the device is addressed by the trigger message, the sending component 530 can send an access or response message to the device that sent the trigger message (e.g., device 100) (S630).

[0089] If a reserved bit (e.g., using a binary flag) indicates that device 500 is excluded (i.e., its response is disabled), device 500 may not send an access or response message.

[0090] Figure 7 This is a schematic diagram of a method according to an example embodiment. Figure 7 The method can be executed by device 100.

[0091] In step 701, the device receives a request from a higher layer. In step 702, the device determines whether the request addresses multiple specific devices or groups of devices. If the request does not address multiple devices / groups ("No" in step 702), step 703 is performed. In step 703, the device generates a trigger message that includes the ID of the single device / group to be addressed. If only one device will be addressed using the short ID in the trigger message, a mask, left truncation, and / or right truncation of the full device identifier may be performed.

[0092] If the answer in step 702 is "yes", then step 704 is executed. In step S704, the device determines whether the length of the multiple device / group IDs is suitable for a trigger message with a fixed length (such as the length of a single complete device identifier), also considering the reliability / link budget required for transmission. If the length of the trigger message is fixed to a predetermined length, it is possible that not all device / group IDs are suitable for a single trigger message. If the length of the multiple device / group IDs is suitable for a single trigger message ("yes" in step S704), then step S705 is executed. In step S705, the device generates a trigger message containing the multiple device / group IDs.

[0093] If the answer in step S704 is "No", then step S706 is executed. In step S706, the device tests multiple device / group IDs for the common part. In step S707, the device determines whether the common part is shared among multiple devices / device groups, i.e., whether the common part identifier is found. If the answer in step S707 is "No", then step S708 is executed. In step S708, the device generates a trigger message that includes multiple device / group IDs and has a length longer than a fixed length.

[0094] If the common part is found (yes in step S707), step S709 is executed. In step S709, the device splits multiple device / group IDs into a common ID and multiple unique IDs. Next, in step S710, the device determines whether the complete set of the common part and unique IDs is suitable for a trigger message with a fixed length. If the answer in step S710 is "yes," then step S711 is executed. In step S711, the device generates a trigger message that includes the common part and a list of (unique) IDs with a fixed length.

[0095] If the answer in step S710 is "no", step S712 is executed. In step S712, the device generates a trigger message that includes a common part and a subset of the (unique) ID list. In this case, the device can generate and send multiple trigger messages, each addressing a subset of the unique ID list, until all devices / groups of devices indicated in the request have been addressed.

[0096] The generated trigger message can have the combination described above. Figure 1 The configuration in the example implementation depends on factors such as how many devices / groups need to be addressed, the length of the trigger message, and privacy requirements. This means that the generated trigger message may include reserved bits, hashed short IDs, etc.

[0097] Figure 8 This is a schematic diagram illustrating a method according to an example embodiment. The method can be performed by devices 300 and 500.

[0098] In step S801, the device determines whether it has received a trigger message. If the device has not received a trigger message, step S801 is executed again.

[0099] If the answer in step S801 is "yes", step S802 is executed. 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. If the answer in step S802 is "no", step S803 is executed. 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 executed.

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

[0101] If the trigger message indicates a complete list of device / group identifiers ("Yes" in step S804), step S805 is executed. In step S805, the device uses the length indicated in the length field of the trigger message (e.g., regarding...). Figure 4 The process involves segmenting the complete list of device / group identifiers (as described) and comparing each of the complete device / group identifiers with its own configured device ID. Next, step S812 is performed.

[0102] If the answer in step S804 is "no", then step S806 is executed. In step S806, the device determines whether the trigger message indicates a short device identifier list.

[0103] If the trigger message indicates a short device identifier list ("Yes" in step S806), then step S807 is executed. In step S807, the device determines whether the trigger message indicates a hashing process.

[0104] If the answer in step S807 is "yes", step S808 is executed. In step S808, the device dehazes the short device identifier list and compares each short device identifier with the device's configured short device identifiers. The segmentation of the short device identifier list is performed in step S809 as described below. Next, step S812 is executed.

[0105] If the answer in step S807 is "no", then step S809 is executed. In step S809, the device uses the length indicated in the length field of the trigger message to segment the short device identifier list (e.g., regarding...). Figure 4 (as described), and compares each short device ID in the short device identifier list with the device's configured short device identifier. Next, step S812 is performed.

[0106] If the answer in step S806 is "no", then step S810 is executed. In step S810, the device determines whether the trigger message indicates the use of a common component.

[0107] If the answer in step S810 is "yes", step S811 is executed. In step S811, the device calculates the length of the short device identifier and uses the calculated length (e.g., regarding...) Figure 6 The received list is segmented using the method described above, and the common part ID is combined with each unique (short) ID listed in the trigger message, and each combination is compared with its own configured device ID. Next, step S812 is performed.

[0108] If the answer in step S810 is "no", the process is terminated / the device determines that the device was not addressed by the trigger message.

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

[0110] If it is determined that the device is addressed by a trigger message ("Yes" in step S812), step S813 is executed.

[0111] In step S813, the device initiates a response process.

[0112] If the answer in step S812 is "no", then step S814 is executed. In step S814, the device does nothing or returns to sleep.

[0113] Figure 9 This is a schematic diagram illustrating a trigger message according to an example embodiment.

[0114] Figure 9 The trigger message includes an address portion that identifies one or more devices. The trigger message may also include trigger content such as service type, session / paging identifier, reader identifier, resource configuration, access type, etc. The address portion includes a type field T, which indicates the identifier type; a length field L, which indicates the length of one or more identifiers; and a list of one or more identifier IDs based on the type field. As used herein, a field including one or more identifiers may be referred to as an ID field. Figure 9 The trigger message can be generated by device 100.

[0115] Figure 10 This is a schematic diagram illustrating a trigger message according to an example embodiment.

[0116] According to the example embodiment, Figure 10 The trigger message can correspond to Figure 9 The trigger message includes a reserved bit R in the address portion, as described above. Figure 10 The trigger message indicates three reserved bits R; however, the number of reserved bits R is not limited to three. Figure 10 The trigger message can be generated by device 100.

[0117] Figure 11 This is a schematic diagram illustrating a trigger message according to an example embodiment.

[0118] According to the example embodiment, Figure 11 The trigger message can correspond to Figure 10 The trigger message contains a reserved bit R including a binary flag B that indicates whether the listed ID is required to respond to the device that sent the trigger message, or whether its response is prohibited. Figure 11 The trigger message can be generated by device 100.

[0119] Figure 12 This is a schematic diagram illustrating a trigger message according to an example embodiment. Figure 12 The trigger message shown can be generated by device 100.

[0120] In the example embodiment, Figure 12In the trigger message shown, the following are assumed: the length of the list of one or more identifier IDs is fixed at 96 bits (as an example), corresponding to the length of the full device identifier; the type field T indicates the list of short device identifiers (as an example); and the length field L indicates that the length of the short device identifier is 16 bits (as an example).

[0121] In the example embodiment, device 300 receives the aforementioned trigger message.

[0122] The determining component 320 divides the received list of short identifiers into six segments, each segment being the length indicated in the length field (i.e., 16 bits). The determining component 320 then compares its own configured short device identifier with each of the six segments. If the configured short identifier of device 300 matches one of the segments, the determining component 320 determines that device 300 is addressed by the trigger message. Accordingly, the sending component 330 sends an access or response message to the device that sent the trigger message (e.g., device 100).

[0123] If a reserved bit (e.g., using a binary flag) indicates that device 300 is excluded (i.e., its response is disabled), the component 330 for sending will not send an access or response message.

[0124] In the example embodiment described above, the trigger message addresses six devices. Therefore, it is possible to address multiple devices using a trigger message with an address portion of a fixed length (such as the length of a single complete device identifier).

[0125] In the example embodiment, as... Figure 12 In the trigger message shown, the following are assumed: the length of the list of one or more identifier IDs is fixed at 96 bits (as an example), corresponding to the length of the complete device identifier; the type field T indicates the complete device identifier (as an example); and the length field L indicates that the length of the complete device identifier is 96 bits (as an example).

[0126] In the example embodiment, device 300 receives the aforementioned trigger message.

[0127] The determining component 320 divides the received list of complete device identifiers into segments according to the length indicated in the length field (i.e., 96 bits) and obtains one segment. The determining component 320 then compares its own configured complete device identifier with this segment. If the configured complete device identifier of device 300 matches the segment, the determining component 320 determines that device 300 is addressed by the trigger message. Therefore, the sending component 330 sends an access or response message to the device that sent the trigger message (e.g., device 100).

[0128] If a reserved bit (e.g., using a binary flag) indicates that device 300 is excluded (i.e., its response is disabled), the component 330 for sending will not send an access or response message.

[0129] In the example embodiment described above, a message is triggered to address a single device.

[0130] As a result of the above example embodiments, it is possible to address a single device or multiple devices using trigger messages with a coordinated structure.

[0131] Figure 13A This is a schematic diagram illustrating a portion of a trigger message according to an example embodiment. This portion of the trigger message may be a part of a trigger message generated by device 100.

[0132] Figure 13A The trigger message shown includes a length field L indicating that the length of the public identifier portion is 80 bits, and a public identifier portion preceding a list of four short identifiers.

[0133] In an example embodiment, the determining component 110 of device 100 determines that the common identifier portion of the four devices to be addressed by the trigger message is 80 bits.

[0134] The component 120 of device 100 then generates a trigger message that indicates the length of the common part identifier (i.e., 80 bits) in the length field and includes a common identifier portion preceding the list of short device identifiers to be addressed (in this case, short device identifiers for four devices). In this case, the type field may indicate that the list of short identifiers follows the common identifier portion.

[0135] Figure 13B This is a schematic diagram illustrating an exemplary combined complete device identifier according to an example embodiment. The combined complete device identifier may be obtained by device 500.

[0136] In an example embodiment, the receiving component 510 of device 500 receives a trigger message, the trigger message including... Figure 13A This part of the trigger message shown includes a length field L indicating the length (i.e., 80 bits) of the public identifier portion, and a public identifier portion preceding the short device identifier list.

[0137] The component 520 used for determination calculates the length of the short device identifier by subtracting the length indicated in the length field of the trigger message from the length of the complete device identifier of the device. It is assumed that the length of the configured device identifier of device 500 is known. Here, the configured complete device identifier of device 500 is assumed to be 96 bits.

[0138] Therefore, in this example, the length of the short device identifier is 96 bits - 80 bits = 16 bits.

[0139] Next, the component 520 used for determination divides the received list of short device identifiers into multiple segments (i.e., four segments in this case) according to the calculated length of the short device identifier (i.e., 16 bits).

[0140] Then, component 520, used for determination, combines the common identifier portion with each of the multiple segmented portions to obtain multiple complete device identifiers. In this case, four complete device identifiers are obtained, such as... Figure 13B As shown in the image.

[0141] Subsequently, the component 520 used for determination can compare the configured complete device identifier of the device with each of the acquired complete device identifiers (i.e., four complete device identifiers).

[0142] If the configured complete device identifier of the device is the same as one of the acquired complete device identifiers, the determining component 120 can determine that the device is addressed by a trigger message. If neither the configured complete device identifier of the device nor any of the acquired complete device identifiers is the same, the determining component 120 can determine that the device is not addressed by a trigger message.

[0143] If it is determined that device 500 is addressed by a trigger message, the sending component 530 can send an access or response message to device 100.

[0144] If the trigger message indicates that device 500 is excluded (i.e., its response is disabled), device 500 may not send access or response messages to device 100.

[0145] Figure 14AThis is a schematic diagram illustrating a portion of a trigger message according to an example embodiment. This portion of the trigger message may be a part of a trigger message generated by device 100. (The last sentence appears to be incomplete and possibly refers to something similar to the previous one.) Figure 13A The same process described above is performed in this case, so its description is omitted.

[0146] for Figure 14B In the example embodiment shown, the common identifier portion of the three devices to be addressed is determined to be 90 bits.

[0147] Figure 14B This is a schematic diagram illustrating an exemplary combined complete device identifier according to an example embodiment. The combined complete device identifier can be obtained by device 500. As described above for... Figure 13B The same process described above is performed in this case, so its description is omitted.

[0148] for Figure 14B In the example embodiment shown, the length of the short device identifier is calculated to be 6 bits (96 bits - 80 bits). After segmentation and recombination, three complete device identifiers are obtained, which can then be used to determine whether device 500 is addressed by a trigger message.

[0149] As is evident from the examples above, if multiple devices (i.e., at least two devices) share a portion of the device identifier (the common identifier portion), it is not necessary to send the complete device identifiers of all devices. In this case, it is possible to send the common identifier portion along with portions of the device identifiers of all devices that allow identification of each device within the device. Therefore, reducing the length of the trigger message is possible, which can reduce power consumption in A-IoT devices and decrease the complexity of decoding the trigger message.

[0150] Figure 15 The diagram alternatively illustrates a block diagram of a device according to an example embodiment. For example... Figure 15 As indicated in the example embodiment, device 100' (corresponding to device 100) includes a processor 1510, a memory 1520, and an I / O unit 1530 capable of sending to and / or receiving from other network elements.

[0151] Figure 16 The diagram alternatively illustrates a block diagram of a device according to an example embodiment. For example... Figure 16 As indicated in the example embodiment, device 300' (corresponding to device 300) includes a processor 1610, a memory 1620, and an I / O unit 1630 capable of sending to and / or receiving from other network elements.

[0152] Figure 17A block diagram of a device according to an example embodiment is shown alternatively. Figure 17 As indicated in the example embodiment, device 500' (corresponding to device 500) includes a processor 1710, a memory 1720, and an I / O unit 1730 capable of sending to and / or receiving from other network elements.

[0153] Memory 1520, 1620, 1720 may store a corresponding program, which is assumed to include program instructions or computer program code, which, when executed by the corresponding processor 1510, 1610, 1710, enable the corresponding electronic device 100', 300', 500' to operate according to the example embodiment.

[0154] Generally speaking, the corresponding device (and / or part thereof) may refer to a component for performing the corresponding operation and / or exhibiting the corresponding function, and / or the corresponding device (and / or part thereof) may have the function for performing the corresponding operation and / or exhibiting the corresponding function.

[0155] When a specification states that a processor (or some other component) is configured to perform certain functions, this should be interpreted as equivalent to stating that at least one processor (potentially cooperating with computer program code stored in the memory of the respective device) is configured to cause the device to perform at least the mentioned functions, and vice versa. Furthermore, such functions will be interpreted as being equivalently implemented by components specifically configured to perform the corresponding functions (i.e., the statement "a processor configured [to cause the device] to perform xxx" is interpreted as equivalent to a statement such as "a component for xxx"), and vice versa.

[0156] For further details regarding the operability / functionality of individual devices, please refer to the above combination. Figures 1 to 14A Description of any of / B.

[0157] Typically, the example embodiments can be implemented by computer software stored in the memories (memory resources, memory circuitry) 1520, 1620, 1720 and executable by the processors (processing resources, processing circuitry) 1510, 1610, 1710, or by hardware, or by a combination of software and / or firmware and hardware.

[0158] The memory (memory resources, memory circuitry) 1520, 1620, and 1720 can be of any type suitable for the local technical environment and can 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 and removable memory, and non-transitory computer-readable media. The processor (processing resources, processing circuitry) 1510, 1610, and 1710 can be of any type suitable for the local technical environment and, by way of non-limiting example, can include one or more of the following: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures.

[0159] Furthermore, as used in this application, the term "circuit system" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuit systems) and (b) A combination of (multiple) hardware circuits and software, such as (if applicable): (i) A combination of (multiple) analog, digital, and / or quantum hardware circuits and software / firmware, and (ii) Any or all portions of (multiple) hardware processors (including (multiple) digital and / or quantum processors) having software, and (multiple) memories, working together to enable a device (such as a mobile device, computing device, or server) to perform various functions, and (c) Any or all parts of (multiple) hardware circuits, such as (multiple) microprocessors, (multiple) processors and / or (multiple) quantum processors, which require software (e.g., firmware) to operate, but do not require operation, and the software may not exist.

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

[0161] For the purposes of this disclosure as described above, it should be noted that: - Method steps that may be implemented as part of software code and run on a processor at a network server or network entity (as an example of a device, apparatus and / or its modules, or as an example of an entity including an apparatus and / or its modules), independent of software code, and may be specified using any known or future-developed programming language, provided that the functionality defined by the method steps is preserved; - Generally, any method steps are suitable to be implemented as software or by hardware without changing the idea of ​​the embodiment and its modifications in terms of the implemented functionality; - The method steps and / or devices, units or components (e.g., devices that perform the functions of the apparatus according to the embodiments described above) that may be implemented as hardware components at any of the above-defined devices or modules thereof are hardware-independent and may be implemented using any known or future-developed hardware technology or any hybrid of these technologies, such as MOS (Metal-Oxide-Semiconductor), CMOS (Complementary MOS), BiMOS (Bipolar MOS), BiCMOS (Bipolar CMOS), ECL (Emitter-Coupled Logic), TTL (Transistor-Transistor Logic), etc., for example using ASIC (Application-Specific Integrated Circuit) components, FPGA (Field-Programmable Gate Array) components, CPLD (Complex Programmable Logic Device) components or DSP (Digital Signal Processor) components; - Devices, units, or components (e.g., any of the devices defined above or their corresponding units / components) may be implemented as individual devices, units, or components, but this does not preclude them from being deployed in a distributed manner throughout the system, as long as the functionality of the devices, units, or components is preserved; - A device (e.g., a device as defined above) may be represented by a semiconductor chip, a chipset, or a (hardware) module including such a chip or chipset; however, this does not preclude the possibility that the function of the device or module is not implemented in hardware but is implemented as software in a (software) module, such as a computer program or a computer program product including executable software code portions for execution / running on a processor. - For example, a device can be considered as a unit or as a component of more than one unit, whether they are functionally cooperative or functionally independent but within the same device housing.

[0162] Generally, it should be noted that the corresponding functional blocks or components according to the foregoing aspects can be implemented by any known components (in hardware and / or software), provided that they are only applicable to performing the functions described in the corresponding parts. The mentioned method steps can be implemented in individual functional blocks or by individual devices, or one or more method steps in the method steps can be implemented in a single functional block or by a single device.

[0163] Generally, any method or procedure is applicable whether implemented as software or in hardware, without altering the spirit of this disclosure. Devices and components may be implemented as independent devices, but this does not preclude them from being implemented in a distributed manner throughout the system, provided that the functionality of the devices is preserved. Such and similar principles should be considered known to those skilled in the art.

[0164] Software in the sense of this specification includes software code, including code components or portions for performing corresponding functions, or computer programs or computer program products; and software (or computer programs or computer program products) embodied on tangible media (such as computer-readable (storage) media) having corresponding data structures or code components / portions stored thereon, or embodied in signals or in chips, potentially during their processing.

[0165] This disclosure also covers any conceivable combination of the above-described method steps and operations, as well as any conceivable combination of the above-described nodes, devices, apparatuses, modules, or elements, provided that the concepts of the above-described method and structural arrangement apply.

[0166] It will be understood that the various exemplary embodiments of this disclosure are merely illustrative and not restrictive, and are not intended to be construed as limiting. Various modifications and applications will be apparent to those skilled in the art without departing from the spirit and scope of the various exemplary embodiments of this disclosure.

[0167] The following items are covered by the above disclosure:

[0168] Item 1. A first device, comprising: At least one processor; and At least one memory storing instructions that, when executed by at least one processor, cause the first device to at least: A trigger message is generated, comprising an address portion identifying one or more second devices, wherein the address portion includes: a type field indicating an identifier type; a length field indicating the length of one or more identifiers; and a list of one or more identifiers based on the type field; and Send a trigger message to one or more second devices.

[0169] Item 2. The first device according to Item 1, wherein The type field implements an instruction for at least one of the following: Complete device identifier, At least one device group identifier, or At least one short device identifier.

[0170] Item 3. The first device according to item 1 or 2, wherein The length field indicates the length of one or more identifiers by indicating the number of identifiers.

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

[0172] Item 5. The first device according to any one of items 1 to 4, wherein When executed by at least one processor, the instruction also causes the first device to: Receive access or response messages from one or more second devices.

[0173] Item 6. The first device according to any one of items 1 to 5, wherein The first device is a reader device, and One or more second devices are one or more Internet of Things (IoT) devices.

[0174] Item 7. The first device according to any one of items 1 to 6, wherein The address portion is either part of the MAC header or a section of the MAC header.

[0175] Item 8. A second device, comprising: At least one processor; and At least one memory storing instructions that, when executed by at least one processor, cause the second device to at least: A trigger message is received from a first device, the trigger message including an address portion identifying one or more second devices, wherein the address portion includes: 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 the length of one or more identifiers; and a list of one or more identifiers based on the type field; and Based on the trigger message, the following operations are used to determine whether the second device is addressed by the trigger message: The received list of one or more identifiers is divided into multiple segments according to the length indicated in the length field; and At least a portion of the configured device identifier of the second device is compared with each of the plurality of segments.

[0176] Item 9. The second device according to Item 8, wherein The length field indicates the length of one or more identifiers by indicating the number of identifiers.

[0177] Item 10. The second device according to item 8 or 9, wherein The length of the list of one or more identifiers corresponds to the length of the complete device identifier.

[0178] Item 11. The second device according to any one of items 8 to 10, wherein If it is determined that the second device is addressed by a trigger message, the instruction, when executed by at least one processor, also causes the second device to: Send an access or response message to the first device.

[0179] Item 12. The second device according to any one of items 8 to 11, wherein The first device is a reader device, and One or more second devices are one or more Internet of Things (IoT) devices.

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

[0181] Item 14. A method comprising: A trigger message is generated by a first device, the trigger message including an address portion identifying one or more second devices, wherein the address portion includes: a type field indicating an identifier type; a length field indicating the length of one or more second identifiers; and a list of one or more identifiers based on the type field; and Send a trigger message to one or more second devices.

[0182] Item 15. A method comprising: A trigger message is received from a first device. The trigger message includes an address portion that identifies one or more second devices, wherein the address portion includes: 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 the length of one or more identifiers; and a list of one or more identifiers based on the type field; and Based on the trigger message, the following steps are used to determine whether the device is addressed by the trigger message: The received list of one or more identifiers is divided into multiple segments according to the length indicated in the length field; and At least a portion of the configured device identifier of the second device is compared with each of the plurality of segments.

[0183] Item 16. A computer program product comprising code components for performing the method described in accordance with Item 14 or 15 when executed on a processing component or module.

[0184] 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 can be directly loaded into the computer's internal memory, and / or can be sent via a network by means of at least one of the processes of uploading, downloading, and pushing.

[0185] Item 18. A first device, comprising: A component for generating a trigger message, the trigger message including an address portion identifying one or more second devices, wherein the address portion includes a type field indicating an identifier type; a length field indicating the length of one or more identifiers; and a list of one or more identifiers based on the type field; and A component used to send trigger messages to one or more second devices.

[0186] Item 19. The first device according to Item 18, wherein The type field enables an indication of at least one of the following: Complete device identifier, At least one device group identifier, or At least one short device identifier.

[0187] Item 20. The first device according to item 18 or 19, wherein The length field indicates the length of one or more identifiers by indicating the number of identifiers.

[0188] Item 21. The first device according to Item 19 or 20, wherein The length of the list of one or more identifiers corresponds to the length of the complete device identifier.

[0189] Item 22. The first device according to any one of items 18 to 21, wherein the first device further comprises: A component used to receive access or response messages from one or more second devices.

[0190] Item 23. The first device according to any one of items 18 to 22, wherein The first device is a reader device, and One or more second devices are one or more Internet of Things (IoT) devices.

[0191] Item 24. The first device according to any one of items 18 to 23, wherein The address portion is either part of the MAC header or a section of the MAC header.

[0192] Item 25. A second device, comprising: A component for receiving a trigger message from a first device, the trigger message including an address portion identifying one or more second devices, wherein the address portion includes 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 the length of one or more identifiers; and a list of one or more identifiers based on the type field; and A component used to determine whether a second device is addressed by a trigger message based on the trigger message by performing the following operations: The received list of one or more identifiers is divided into multiple segments according to the length indicated in the length field; and At least a portion of the configured device identifier of the second device is compared with each of the plurality of segments.

[0193] Item 26. The second device according to Item 25, wherein The length field indicates the length of one or more identifiers by indicating the number of identifiers.

[0194] Item 27. The second device according to Item 25 or 26, wherein The length of the list of one or more identifiers corresponds to the length of the complete device identifier.

[0195] Item 28. The second device according to any one of items 25 to 27, wherein the second device further comprises: A component used to send access or response messages to a first device.

[0196] Item 29. The second device according to any one of items 25 to 28, wherein The first device is a reader device, and One or more second devices are one or more Internet of Things (IoT) devices.

[0197] Item 30. The second device according to any one of items 25 to 29, wherein The address portion is either part of the MAC header or a section of the MAC header.

[0198] Item 31. A first device, comprising: At least one processor; and At least one memory storing instructions that, when executed by at least one processor, cause the first device to at least: Generate a trigger message, the trigger message including an address portion that identifies one or more second devices, wherein the address portion includes a type field that indicates an identifier type; a length field that indicates the length of one or more identifiers; and a list of one or more identifiers based on the type field; Send a trigger message to one or more second devices.

[0199] Item 32. The first device according to item 31, wherein The type field enables an indication of at least a public identifier portion, which indicates a portion of a complete device identifier that is public to at least two devices, followed by a list of short identifiers.

[0200] Item 33. The first device according to item 32, wherein The short device identifier is part of the complete device identifier.

[0201] Item 34. The first device according to item 33, wherein The trigger message indicates which part of the complete device identifier forms the short device identifier.

[0202] Item 35. The first device according to any one of items 31 to 34, wherein When executed by at least one processor, the instruction also causes the first device to: Determine the public identifier portion.

[0203] Item 36. The first device according to any one of items 32 to 35, wherein The address portion also includes the public identifier portion preceding the short device identifier list, and The length field indicates the length of the public identifier portion.

[0204] Item 37. The first device according to item 35 or 36, wherein The type field indicates that the public identifier section is followed by a list of short device identifiers.

[0205] Item 38. The first device according to any one of items 31 to 37, wherein When executed by at least one processor, the instruction also causes the first device to: Receive access or response messages from one or more second devices.

[0206] Item 39. The first device according to any one of items 31 to 38, wherein The first device is a reader device, and One or more second devices are one or more Internet of Things (IoT) devices.

[0207] Item 40. The first device according to any one of items 31 to 39, wherein The address portion is either part of the MAC header or a section of the MAC header.

[0208] Item 41. A second device, comprising: At least one processor; and At least one memory storing instructions that, when executed by at least one processor, cause the second device to at least: A trigger message is received from a first device, the trigger message including an address portion identifying one or more devices, wherein the address portion includes: a type field indicating a common identifier portion, the common identifier portion indicating a portion of a complete device identifier common to at least two devices, the common identifier portion followed by a list of short identifiers; a length field indicating the length of the common identifier portion; and a common identifier portion preceding the list of short identifiers; and... Based on the trigger message, the following operations are used to determine whether the second device is addressed by the trigger message: The length of the short device identifier is calculated by subtracting the length indicated in the length field of the trigger message from the length of the configured device identifier of the second device. The received list of short device identifiers is divided into multiple segments according to the calculated length of the short device identifiers; The common identifier portion is combined with each of the multiple segmented portions to obtain multiple complete device identifiers; and The configured device identifier of the second device is compared with each of the complete device identifiers obtained from the complete device identifiers.

[0209] Item 42. The second device according to Item 41, wherein The short device identifier is part of the complete device identifier.

[0210] Item 43. The second device according to item 42, wherein The trigger message indicates which part of the complete device identifier forms the short device identifier.

[0211] Item 44. The second device according to any one of 41 to 43, wherein If it is determined that the second device is addressed by a trigger message, the instruction, when executed by at least one processor, also causes the second device to: Send an access or response message to the first device.

[0212] Item 45. The second device according to any one of items 41 to 44, wherein The first device is a reader device, and One or more second devices are one or more Internet of Things (IoT) devices.

[0213] Item 46. The second device according to any one of items 41 to 45, wherein The address portion is either part of the MAC header or a section of the MAC header.

[0214] Item 47. A method comprising: A trigger message is generated by a first device, the trigger message including an address portion that identifies one or more second devices, wherein the address portion includes: a type field that indicates the type of identifier; a length field that indicates the length of one or more identifiers; and a list of one or more identifiers based on the type field; Send a trigger message to one or more second devices.

[0215] Item 48. A method comprising: A trigger message is received from a first device, the trigger message including an address portion identifying one or more second devices, wherein the address portion includes: a type field indicating a common identifier portion, the common identifier portion indicating a portion of a complete device identifier common to at least two devices, the common identifier portion followed by a list of short identifiers; a length field indicating the length of the common identifier portion; and a common identifier portion preceding the list of short identifiers; and... Based on the trigger message, the following operations are used to determine whether the second device is addressed by the trigger message: The length of the short device identifier is calculated by subtracting the length indicated in the length field of the trigger message from the length of the configured device identifier of the second device. The received list of short device identifiers is divided into multiple segments according to the calculated length of the short device identifiers; The common identifier portion is combined with each of the multiple segmented portions to obtain multiple complete device identifiers; and The configured device identifier of the second device is compared with each of the complete device identifiers obtained from the complete device identifiers.

[0216] Item 49. A computer program product comprising code components for performing the method described in accordance with item 47 or 48 when executed on a processing component or module.

[0217] 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 can be directly loaded into the internal memory of a computer, and / or can be transmitted via a network by means of at least one of the processes of uploading, downloading, and pushing.

[0218] Item 51. A first device, comprising: A component for generating a trigger message, the trigger message including an address portion that identifies one or more second devices, wherein the address portion includes a type field that indicates an identifier type; a length field that indicates the length of one or more identifiers; and a list of one or more identifiers based on the type field; A component used to send trigger messages to one or more second devices.

[0219] Item 52. The first device according to item 51, wherein The type field enables an indication of at least a public identifier portion, which indicates a portion of a complete device identifier that is public to at least two devices, followed by a list of short identifiers.

[0220] Item 53. The first device according to item 52, wherein The short device identifier is part of the complete device identifier.

[0221] Item 54. The first device according to item 33, wherein, The trigger message indicates which part of the complete device identifier forms the short device identifier.

[0222] Item 55. The first device according to any one of items 51 to 54, wherein the first device further comprises: Components used to determine the public identifier portion.

[0223] Item 56. The first device according to any one of items 52 to 55, wherein, The address portion also includes the public identifier portion preceding the short device identifier list, and The length field indicates the length of the public identifier portion.

[0224] Item 57. The first device according to item 55 or 56, wherein, The type field indicates that the public identifier section is followed by a list of short device identifiers.

[0225] Item 58. The first device according to any one of items 51 to 57, wherein the first device further comprises: A component used to receive access or response messages from one or more second devices.

[0226] Item 59. The first device according to any one of items 51 to 58, wherein, The first device is a reader device, and One or more second devices are one or more Internet of Things (IoT) devices.

[0227] Item 60. The first device according to any one of items 51 to 59, wherein The address portion is either part of the MAC header or a section of the MAC header.

[0228] Item 61. A second device, comprising: Components for receiving a trigger message from a first device, the trigger message including an address portion identifying one or more devices, wherein the address portion includes a type field indicating a common identifier portion indicating a portion of a complete device identifier common to at least two devices, followed by a list of short identifiers; a length field indicating the length of the common identifier portion; and a common identifier portion preceding the list of short identifiers; and... A component used to determine whether a second device is addressed by a trigger message based on the trigger message by performing the following operations: The length of the short device identifier is calculated by subtracting the length indicated in the length field of the trigger message from the length of the configured device identifier of the second device. The received list of short device identifiers is divided into multiple segments according to the calculated length of the short device identifiers; The common identifier portion is combined with each of the multiple segmented portions to obtain multiple complete device identifiers; and The configured device identifier of the second device is compared with each of the complete device identifiers obtained from the complete device identifiers.

[0229] Item 62. The second device according to Item 61, wherein The short device identifier is part of the complete device identifier.

[0230] Item 63. The second device according to item 62, wherein The trigger message indicates which part of the complete device identifier forms the short device identifier.

[0231] Item 64. The second device according to any one of 61 to 63, wherein the second device further comprises: A component used to send access or response messages to a first device.

[0232] Item 65. The second device according to any one of items 61 to 64, wherein The first device is a reader device, and One or more second devices are one or more Internet of Things (IoT) devices.

[0233] Item 66. The second device according to any one of items 61 to 65, wherein The address portion is either part of the MAC header or a section of the MAC header.

Claims

1. A first device (100') for communication, comprising: At least one processor (1510); as well as At least one memory (1520) stores instructions that, when executed by the at least one processor (1510), cause the first device (100') to at least: A trigger message is generated, the trigger message including an address portion identifying one or more second devices (500'), wherein the address portion includes: a type field indicating an identifier type; a length field indicating the length of one or more identifiers; and a list of the one or more identifiers based on the type field; and The trigger message is sent to one or more second devices (500').

2. The first device (100') according to claim 1, wherein The type field enables an indication of at least a public identifier portion, which indicates a portion of a complete device identifier that is common to at least two devices, followed by a list of short identifiers.

3. The first device (100') according to claim 2, wherein, The short device identifier is part of the complete device identifier.

4. The first device (100') according to claim 3, wherein The trigger message indicates which part of the complete device identifier forms the short device identifier.

5. The first device (100') according to any one of claims 1 to 4, wherein When the instruction is executed by the at least one processor (1510), it also causes the first device (100'): Determine the public identifier portion.

6. The first device (100') according to any one of claims 2 to 5, wherein The address portion also includes the public identifier portion preceding the short device identifier list, and The length field indicates the length of the public identifier portion.

7. The first device (100') according to claim 5 or 6, wherein The type field indicates that the public identifier portion is followed by the list of short device identifiers.

8. The first device (100') according to any one of claims 1 to 7, wherein When the instruction is executed by the at least one processor (1510), it also causes the first device (100'): Receive access or response messages from the one or more second devices (500').

9. The first device (100') according to any one of claims 1 to 8, wherein The first device (100') is a reader device, and The one or more second devices (500') are one or more Internet of Things (IoT) devices.

10. The first device (100') according to any one of claims 1 to 9, wherein The address portion is either the MAC header or a part of the MAC header.

11. A second device (500') for communication, comprising: At least one processor (1710); as well as At least one memory (1720) stores instructions that, when executed by the at least one processor (1710), cause the second device (500') to at least: A trigger message is received from a first device (100'), the trigger message including an address portion identifying one or more devices, wherein the address portion includes: a type field indicating a common identifier portion indicating a portion of a complete device identifier common to at least two devices, the common identifier followed by a list of short identifiers; a length field indicating the length of the common identifier portion; and the common identifier portion preceding the list of short identifiers; and Based on the trigger message, the following operations are performed to determine whether the second device (500') is addressed by the trigger message: The length of the short device identifier is calculated by subtracting the length indicated in the length field of the trigger message from the length of the configured device identifier of the second device (500'). The received list of short device identifiers is divided into multiple segments according to the calculated length of the short device identifier; Combining the public identifier portion with each of the plurality of segmented portions to obtain a plurality of complete device identifiers; and The configured device identifier of the second device (500') is compared with each of the acquired complete device identifiers.

12. The second device (500') according to claim 11, wherein The short device identifier is part of the complete device identifier.

13. The second device (500') according to claim 12, wherein The trigger message indicates which part of the complete device identifier forms the short device identifier.

14. The second device (500') according to any one of claims 11 to 13, wherein If it is determined that the second device (500') is addressed by the trigger message, the instruction, when executed by the at least one processor (1710), also causes the second device to: Send an access or response message to the first device (100').

15. The second device (500') according to any one of claims 11 to 14, wherein The first device (100') is a reader device, and The one or more second devices (500') are one or more Internet of Things (IoT) devices.

16. The second device (500') according to any one of claims 11 to 15, wherein The address portion is either the MAC header or a part of the MAC header.

17. A method for communication, comprising: A trigger message is generated by a first device (100'), the trigger message including an address portion identifying one or more second devices (500'), wherein the address portion includes: a type field indicating an identifier type; a length field indicating the length of one or more identifiers; and a list of the one or more identifiers based on the type field; and The trigger message is sent to one or more second devices (500').

18. A method for communication, comprising: A trigger message is received from a first device (100'), the trigger message including an address portion identifying one or more second devices 500', wherein the address portion includes: a type field indicating a common identifier portion indicating a portion of a complete device identifier common to at least two devices, the common identifier followed by a list of short identifiers; a length field indicating the length of the common identifier portion; and the common identifier portion preceding the list of short identifiers; and Based on the trigger message, the following operations are performed to determine whether the second device (500') is addressed by the trigger message: The length of the short device identifier is calculated by subtracting the length indicated in the length field of the trigger message from the length of the configured device identifier of the second device (500'). The received list of short device identifiers is divided into multiple segments according to the calculated length of the short device identifier; Combining the public identifier portion with each of the plurality of segmented portions to obtain a plurality of complete device identifiers; and The configured device identifier of the second device (500') is compared with each of the acquired complete device identifiers.

19. A computer program product comprising code components for performing the method according to claim 17 or 18 when executed on a processing component or module.

20. The computer program product of claim 19, wherein the computer program product is embodied on a computer-readable medium, and / or the computer program product is directly loaded into the internal memory of the computer, and / or can be transmitted via a network by means of at least one of the processes of uploading, downloading, and pushing.

Images