Environmental IoT signaling procedure
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- NOKIA TECHNOLOGIES OY
- Filing Date
- 2026-02-03
- Publication Date
- 2026-08-07
Smart Images
Figure CN122534597A_ABST
Abstract
Description
Cross-references to related applications
[0001] This application claims priority and benefit to EP application No. 25156496.9, filed on February 7, 2025, the contents of which are incorporated herein by reference in their entirety. Technical Field
[0002] Various exemplary embodiments of this disclosure generally relate to the telecommunications field, and more specifically to methods, apparatuses, devices, and computer-readable storage media for environmental Internet of Things (IoT) signaling processes. Background Technology
[0003] In recent years, IoT technology has been proposed to support battery-free devices without energy storage capabilities or devices with energy storage that do not require manual replacement or recharging. AIoT devices, also known as Ambient IoT (AIoT) devices, can capture and collect energy by collecting radio waves to perform data collection, transmission, and distributed computing. Summary of the Invention
[0004] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to at least: receive from a second apparatus a first message associated with paging the first apparatus; and determine association information based on at least one of the following: whether a second message following the first message is associated with the first message; association data included in the second message; or the length of time associated with the reception of the second message.
[0005] In a second aspect of this disclosure, a second apparatus is provided. The second apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to at least: send a first message to a first apparatus associated with paging the first apparatus; and send a second message to the first apparatus following the first message, the second message including association data for determining association information regarding whether the second message is associated with the first message.
[0006] In a third aspect of this disclosure, a method is provided. The method includes: receiving from a second device a first message associated with paging a first device; and determining association information based on at least one of the following: association data included in the second message, or the length of time associated with the reception of the second message.
[0007] In a fourth aspect of this disclosure, a method is provided. The method includes: sending a first message associated with paging the first device to a first device; and sending a second message following the first message to the first device, the second message including association data for determining association information regarding whether the second message is associated with the first message.
[0008] In a fifth aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components for receiving from a second apparatus a first message associated with paging the first apparatus; and components for determining association information based on at least one of the following: whether a second message following the first message is associated with the first message: association data included in the second message, or the length of time associated with the reception of the second message.
[0009] In a sixth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components for sending a first message associated with paging the first apparatus to a first apparatus; and components for sending a second message following the first message to the first apparatus, the second message including association data for determining association information regarding whether the second message is associated with the first message.
[0010] In a seventh aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to a third aspect.
[0011] In an eighth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to the fourth aspect.
[0012] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description
[0013] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which example embodiments of the present disclosure may be implemented is shown; Figure 2 An example signaling flow for the process between an AIoT device and a reader is shown; Figure 3 Example signaling flows for AIoT signaling procedures according to some example embodiments of this disclosure are shown; Figure 4 Example signaling flows for AIoT signaling procedures according to some example embodiments of this disclosure are shown; Figure 5 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 6 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 7 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 8 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.
[0014] Throughout the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation
[0015] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to help those skilled in the art to understand and implement this disclosure, without implying any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.
[0016] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.
[0017] References to "an embodiment," "an embodiment," "an exemplary embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment needs to include that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is to be noted that those skilled in the art will recognize, whether explicitly described or not, that such features, structures, or characteristics apply in conjunction with other embodiments.
[0018] It should be understood that although the terms “first,” “second,” etc., may be used before nouns (or similar terms) to describe various elements herein, these elements should not be limited to these terms. These terms are used only to distinguish one element from another, and they do not restrict the order of the nouns (or similar terms). For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0019] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where a list of two or more elements is connected by “and” or “or”, means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.
[0020] As used herein, unless explicitly stated otherwise, “in response to A” performing a step does not indicate that the step is performed immediately after “A” occurs and may include one or more intermediate steps.
[0021] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. 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 the terms “comprising,” “including,” “having,” “possessing,” “containing,” and / or “covering,” as used herein, specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.
[0022] As used in this application, the term "circuit" may refer to one or more or all of the following: (a) Hardware circuit implementation only (e.g., implemented with purely analog and / or digital circuits) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor(s) having software (including (multiple) digital signal processors, software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions) and (c) The operation requires software (e.g., firmware) for the operation of (multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or parts thereof, but the software may be absent when the operation does not require the software.
[0023] This definition of "circuit" 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" also covers only hardware circuitry or processors (or processors in general) or a portion thereof and its accompanying software and / or firmware implementations. For example, where applicable to a particular claim element, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or network devices.
[0024] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, sixth-generation (6G) communication protocols and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development in communications, there will naturally be future types of communication technologies and systems that can implement this disclosure. The scope of this disclosure should not be limited to the aforementioned systems only.
[0025] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Head (RH), a Remote Radio Head (RRH), a repeater, an Integrated Access and Backhaul (IAB) node, a low-power node (such as a femtosecond or picosecond), a Non-Terrestrial Network (NTN) or Non-Terrestrial Network Equipment (such as satellite network equipment, Low Earth Orbit (LEO) satellites, and Geostationary Earth Orbit (GEO) satellites), an aircraft network equipment, etc. In some example embodiments, the Radio Access Network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB donor node. An IAB node includes: a mobile terminal (IAB-MT) portion that behaves similarly to a UE when facing a parent node; and a DU portion of the IAB node that behaves similarly to a base station when facing a next-hop IAB node.
[0026] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback facilities, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.
[0027] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication (e.g., communication between a terminal device and a network device), such as resources in the time domain, resources in the frequency domain, resources in the spatial domain, resources in the code domain, or any other combination of time-domain, frequency-domain, spatial-domain, and / or code-domain resources capable of communication. In the following, unless explicitly stated otherwise, resources in both the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.
[0028] Figure 1 An example communication environment 100 in which exemplary embodiments of the present disclosure may be implemented is shown. In the communication environment 100, a plurality of communication devices, including a first device 110 and a second device 120, can communicate with each other.
[0029] exist Figure 1 In this example, the second device 120 has a coverage area, which may be referred to as a service area or source cell. The first device 110 is located in a cell managed by the second device 120. In the communication environment 100, the second device 120 can communicate with the first device 110.
[0030] In some example embodiments, if the first device 110 is a terminal device and the second device 120 is a network device, the link from the second device 120 to the first device 110 is referred to as a downlink (DL), and the link from the first device 110 to the second device 120 is referred to as an uplink (UL). In the DL, the second device 120 is a transmitting (TX) device (or transmitter), and the first device 110 is a receiving (RX) device (or receiver). In the UL, the first device 110 is a TX device (or transmitter), and the second device 120 is an RX device (or receiver).
[0031] It should be understood that Figure 1 The number of devices and their connections shown is for illustrative purposes only and does not imply any limitation. The communication environment 100 may include any suitable number of devices configured to implement the exemplary embodiments of this disclosure.
[0032] In the following description, for illustrative purposes, some example embodiments are described in which the first device 110 operates as a terminal device (e.g., an AIoT device) and the second device 120 operates as a network device (e.g., an AIoT reader, also referred to as a reader for the purposes of discussion). However, in some example embodiments, the operations described in connection with the terminal device can be implemented at the network device or other devices, and vice versa.
[0033] Communication in communication environment 100 can be implemented according to any suitable communication protocol, including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), and sixth-generation (6G), wireless local area network communication protocols such as IEEE 802.11, and / or any other currently known or future-developed protocols. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.
[0034] Figure 2 Example AIoT signaling 200 is shown for the process between AIoT device (sometimes referred to as "device") 210 and reader 220.
[0035] AIoT device 210 can be a much smaller and cheaper IoT device compared to previous generations of IoT. In some cases, AIoT device 210 can be an end device (e.g., UE) or implemented within an end device. The ultimate power source for ambient IoT comes from radio waves. Both ambient IoT and ambient computing rely on energy harvesting as one of the key mechanisms for powering and enabling the technology. When energy harvesting is applied to ambient IoT and ambient computing, it utilizes the power in ambient radio waves to power a microcomputer.
[0036] Environmental IoT devices can have a new radio / air interface to readers / nodes. This new radio interface can be frame-based or non-frame-based. Deploying environmental IoT services on existing systems can reduce operating costs and rapidly commercialize new services.
[0037] Reader 220 can be a device that reads and interprets data collected from AIoT device 210. For example, reader 220 can extract meaningful information from large amounts of data generated by the surrounding environment, making it usable for various applications. Communication between reader 220 and AIoT device 210 can be via a new radio / air interface, as discussed above.
[0038] The necessary functions and processes for implementing DO-DTT and DT data transmission have now been investigated for a compact protocol stack and lightweight signaling procedures for Ambient IoT (AIoT): IoT paging, including subsequent paging for the same service. The following options are supported: the paging message includes an identifier / the paging message does not contain an identifier. Temporary identifiers may not be supported unless required by the SA working group.
[0039] IoT random access, including re-access for failure handling. Supports both contention-based and contention-free scenarios.
[0040] IoT data transmission, including data (re)transmission for fault handling. Segmentation is supported at least in device-to-reader (D2R) communication.
[0041] Only the MAC layer is included.
[0042] AIoT signaling at the MAC layer is limited to both Topology 1 and Topology 2. For example... Figure 2 As shown, step A is related to A-IoT paging. In step A, reader 220 sends an AIoT paging message to AIoT device 110. Based on the service request, the reader sends an A-IoT paging message indicating which of the multiple devices needs to respond.
[0043] Step B involves D2R data transmission (using device ID). The triggered A-IoT device(s) (such as AIoT device 210) performs device ID transmission via or without the A-IoT random access procedure. Step B includes a B2 step (also known as a B2 message) in which AIoT device 120 performs D2R data transmission.
[0044] Step C, comprising steps C1 and C2 (also referred to as messages C1 and C2 in some examples), relates to data transmission. Specifically, in step C1, reader 220 performs possible reader-to-device (R2D) data transmission to AIoT device 210 (e.g., for sending commands). At step C2, AIoT device 210 may perform possible device-to-receive (D2R) data transmission to reader 220 (e.g., a corresponding response to a command).
[0045] The aforementioned Access Layer (AS) process can then support indoor inventory and indoor command use cases in the following manner. For the detailed use case of "inventory only," it is supported with a process having steps A and B as a baseline.
[0046] For the detailed use case of "inventory and commands," it is supported with a process having steps A, B, C1, and C2 as a baseline. It should be understood that for the use case of "inventory and commands," this does not mean that the A-IoT paging message includes both inventory and commands, nor does it imply that the reader receives both inventory and commands from a higher layer simultaneously.
[0047] The following provides a more detailed discussion of the use case for "command only". It can also be supported by a baseline procedure with steps A, B, C1, and C2. Additionally, another candidate supporting this use case is as follows: Step A': A-IoT Paging. Based on the service request, the reader sends an A-IoT paging message including a command, instructing (multiple) devices to process / respond to the command.
[0048] Step C2: Possible D2R data transmission (e.g., device ID and / or corresponding response to a command) via or without the A-IoT random access procedure.
[0049] In some conventional solutions, a process with steps A, B, C1, and C2 can be supported as a baseline for the "inventory and command" use case. However, A-IoT paging messages do not necessarily include inventory and commands, nor do they necessarily require the reader to receive inventory and commands simultaneously from a higher layer.
[0050] In other words, while an inventory request is being issued (meaning signaling steps A and B are being used), it is unclear whether a command request (additional step C) will be followed. There may be a relatively long delay between inventory and command (e.g., the access function (AF) issues a command with a relatively long delay based on the result of the inventory request). Similarly, since reader 220 only acts as an intermediary between the AF and AIoT device 210, reader 220 may typically be unaware of the inventory and the command sequence.
[0051] This may be as follows Figure 2 The AIoT data transmission shown presents a double problem. First, the service type may not be clearly signaled as part of the initial message (e.g., paging) to indicate whether step C will be necessary. Furthermore, after a relatively long delay following step B, step C may be required to execute subsequent commands without prior notification.
[0052] According to some example embodiments of this disclosure, a solution for an AIoT signaling process is provided. In this solution, a first device receives a first message associated with paging the first device from a second device. The first device then determines association information regarding whether a second message following the first message is associated with the first message. This determination is based on association data included in the second message and / or the time length associated with the reception of the second message.
[0053] In this way, (multiple) additional signaling can be avoided. For example, neither new paging requests with associated resource usage nor any possible random access resolution are required. Additionally, if subsequent commands are delivered in conjunction with previous inventory requests, a security context may not be necessary.
[0054] The exemplary embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.
[0055] Figure 3 An example signaling flow 300 for an AIoT signaling process according to some example embodiments of this disclosure is shown. Reference will be made to this document for discussion purposes. Figure 1 For example, signaling flow 300 is discussed by using the first device 110 and the second device 120.
[0056] In some example embodiments, the first device 110 can be discussed as an AIoT device. The AIoT device can be a terminal device, such as a UE or other suitable device. The second device 120 can be discussed as a reader associated with the AIoT device. The reader can be, for example, a reader capable of reading and interpreting data collected from the AIoT device. In some example implementations, the second device can be implemented as a network device, such as a BS or gNB.
[0057] In signaling flow 300, the second device 120 sends (305) a first message associated with paging the first device to the first device 110. The first device 110 receives (310) the first message from the second device. Then, the first device 110 determines (330) association information regarding whether a second message following the first message is associated with the first message. This determination (330) is made based on association data included in the second message, the duration of time associated with the reception of the second message, and / or other information.
[0058] After sending (305) the first message, the second device 120 sends (315) the second message to the first device 110. In some example embodiments, the first device 110 may receive (320) the second message from the second device 120 and may obtain associated data from the second message for determining (330) associated information. The associated data may include various data or information, such as, but not limited to, the identifier (ID) of the first device (e.g., device ID), the identifier of the first message (e.g., paging request ID), the identifier of the second device (e.g., reader ID), the paging identifier associated with the first message, security context, contention resolution identifier, data segments associated with the payload of another message, etc.
[0059] In some example embodiments, another message may be sent from the first device 110 to the second device 120 (312). This other message may be associated with a random access procedure involving the first device 110 and the second device 120. In some example embodiments, this other message may include an identifier of the first device 110 (e.g., an AIoT device ID) via a random access procedure. This other message may be, for example, in… Figure 2 The message sent in step B2. Upon receiving (313) this other message, the second device 120 can know the identifier of the first device 110, for example, the AIoT device ID.
[0060] Some associated data may be indicated by the first message. For example, the first message may indicate, for instance, the identifier of the first device 110, the identifier of the first message, the identifier of the second device 120, a paging identifier associated with the first message, etc. Some other associated data may be indicated by another message, such as a contention resolution identifier, a data segment associated with the payload of another message, etc.
[0061] To determine (330) associated information, in some example embodiments, the first device 110 may determine (325) reference data from at least one of the following: a first message, another message sent to the second device, or a security context. For example, reference data determined from the first message may include, for example, an identifier of the first device, an identifier of the first message, an identifier of the second device, a paging identifier associated with the first message, etc. Reference data determined from another message may include, for example, a contention resolution identifier and / or a data segment associated with the payload of the other message.
[0062] Based on the associated data received (320) via the second message and the determined (325) reference data, the first device 110 can determine (330) the association information. For example, the first device 110 can compare the reference data with the associated data, and if the reference data matches the corresponding associated data, it determines that the second message is associated with the first message. Otherwise, the first device 110 can determine that the second message is not associated with the first message.
[0063] In some example implementations, the determination of the associated information is performed based on several factors, such as the service type of the second message. The service type of the second message can be one of inventory, command, or unknown. For example, if the first message indicates that the service type of the second message is command or unknown, the first device 110 can determine the associated information. Conversely, if the first message indicates that the service type of the second message is only inventory, the first device 110 can stop waiting for the second message to be received.
[0064] Alternatively, in some example embodiments, the second message may not necessarily be received by the first device 110. In this case, the first device 110 may determine (330) association information based on the length of time associated with the reception of the second message. For example, the first device 110 may start a timer of a certain length to monitor the second message after sending another message. If the second message is received before the timer expires, the first device 110 may determine that the second message is associated with the first message. Conversely, if the first device 110 fails to receive the second message before the timer expires, it may stop waiting for the second message. That is, if the first device 110 waits for the second message for too long, it may stop waiting and may enter a power-saving mode.
[0065] The duration can be determined in various ways. In some example embodiments, the duration can be predefined or configured by the second device 120. Alternatively, the duration can be determined based on: the identifier of the first device, the identifier of the first message, the identifier of the second device, etc. As another alternative, the duration can be determined based on: information about the maximum timer, the end time information of the resources allocated for the second message, etc.
[0066] More details will be discussed below. In the following discussion, the first device 110 may be discussed as an AIoT device, and the second device 120 may be discussed as a reader. Figure 2 Steps A, B, and C also involve discussion for illustrative purposes. It should be understood that these examples are discussed for the purpose of discussion only and do not imply any limitations.
[0067] In some example embodiments, association information is presented to allow for linking for each specific device and paging timing. Figure 2 The steps A and C, or link steps B and C, discussed herein. More specifically, message C1 is suggested to include association information to link inventory step B with subsequent command steps for correct device and paging requests.
[0068] As shown in the following examples, association information can be (uniquely) derived from, for example, the parameters of step A (e.g., device ID, reader ID, and paging sequence number) and / or the parameters of step B (e.g., 16-bit contention resolution ID, payload segments (such as CRC)). This association can be created using pre-configured rules. Due to the unique nature of the association information, multiple devices expecting commands can correctly associate incoming C1 messages from the reader.
[0069] In some cases, the associated information can be derived from similar parameters as above, but the reader's security context is established and / or maintained. This can prevent command spoofing even when the message content is in plaintext.
[0070] It can also be assumed that the associated information has a finite time validity determined by a timer, which may be newly proposed to receive message C1 after message B2, which is given by the minimum of the maximum timer, resource end, or session end, etc.
[0071] Once the timer expires, post-disk commands can be stopped being received, and the device can even continue exiting the process, such as deleting buffer data and page state transitions (e.g., to the "complete" state) and "releasing" the security context (clearing the buffer). Such operations allow the device to more effectively stop consuming power.
[0072] The two examples will be discussed in detail below. (Regarding...) Figure 4 Let's discuss the first example. Figure 4 An example signaling flow 400 for an AIoT signaling process according to some example embodiments of the present disclosure is shown. The signaling flow 400 relates to an AIoT device 410, which is an example of a first device 110, and a reader 420, which is an example of a second device 120.
[0073] exist Figure 4In step A (401), reader 420 sends a first message, such as an AIoT paging message, to AIoT device 410. At step 402, AIoT device 410 sends message B (B2 message) to reader 420, including D2R data transmission. At step 403, reader 420 sends message C1 to AIoT device 410, which includes R2D data transmission with associated data. At step 404, AIoT device 410 sends message C2 to reader 420, including D2R data transmission.
[0074] In some example embodiments, the service type of the AIoT service can be inventory, command, or unknown. It should be understood that the examples of service types described above are for illustrative purposes only and do not imply any limitation. In other embodiments of this disclosure, the service type may have other suitable values.
[0075] In some cases, the service type may not be explicitly indicated to the AIoT device 410 by the reader 420. Alternatively, the service type indicator may be included in the paging, including inventory, command, and / or unknown.
[0076] After completing the inventory request, including message B, and after a certain delay, if the received service type is inventory, AIoT device 410 can be allowed to shut down. If the received service type is command or unknown, AIoT device 410 can start a timer that defines the deadline at which subsequent commands can be received by the same device as part of an ongoing paging event (including transfers on resources as defined herein).
[0077] Once the AF issues a subsequent command, the reader relays the request by sending a second message (e.g., a C1 message) containing the proposed associated data. For contention-free random access (CFRA) scenarios, the associated data included in the C1 message can be any of the device ID, paging request ID, or reader ID. In some cases, if each reader has only one session, there may be no need for the paging request ID information. In other cases, where multiple parallel readers cannot send paging requests simultaneously, the reader ID is not required.
[0078] For contention-based random access (CBRA) scenarios, the associated data can be in the form of a partial / complete device ID or a 16-bit RA_ID (each device uniquely generates its 16-bit RA_ID relative to previous paging requests). In the unlikely event that two devices accidentally share the same RA_ID, command decoding and device-specific execution will only succeed on the target device.
[0079] For both CFRA and CBRA scenarios, the associated data can be in the form of a data segment associated with the payload of another message sent (312) to the second device 120 (e.g., the payload of the B2 message or the B2 segment (e.g., N bits of the CRC)).
[0080] Then, the associated data allows the AIoT device 410 to be corrected in a wait-for-possible-command mode to link the incoming C1 message with its past step B.
[0081] If needed, the AIoT device 410 can respond using the C2 message. Preferably, this is done within the valid timeframe for receiving the C1 message (assuming the CBRA is parsed) and on the resources defined in the initial paging in step 401 (step A).
[0082] In an additional embodiment, where the manifest and commands are broadcast, the gNB can request the establishment of a security context before data transmission.
[0083] In the second example, during payload transmission in step B, the device proactively sets and reports its own (random) timer, within which the device is willing to accept subsequent commands (subject to the end of a resource / paging request). This timer can have a unique / random value so that it can be used as association data for B-C1 association purposes.
[0084] Alternatively, the associated data can be explicitly defined by the device in the form of an auxiliary "re-access" code and indicated to the reader. The reader can forward the command timing constraints to the AF. The "re-access" code can be generated similarly to 16b RA_ID to be unique to the device and paging request, and its validity will be determined by the aforementioned timer.
[0085] In specific embodiments of this disclosure, standardized conventions regarding how to generate "re-access" codes and associated validity timers based on device ID, paging request ID, reader ID, etc., are known. This allows the reader to send incoming follow-up commands directly to the device in C1, without requiring prior pre-configuration of the proposed associated data by the device and its messaging to the reader.
[0086] Advantageously, this avoids new paging requests with associated resource usage and potential random access resolution. Security context is also not required if subsequent commands are delivered in conjunction with previous inventory requests.
[0087] Figure 5 A flowchart of an example method 500 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 500 is described by the angle of the first device 110 in the middle.
[0088] In frame 510, the first device 110 receives a first message associated with paging the first device from the second device.
[0089] In block 520, the first device 110 determines association information based on at least one of the following, the association information being about whether a second message following the first message is associated with the first message: associated data included in the second message, or the length of time associated with the receipt of the second message.
[0090] In some example embodiments, the associated data includes at least one of the following: an identifier of the first device, an identifier of the first message, an identifier of the second device, a paging identifier associated with the first message, a security context, a contention resolution identifier, or a data segment associated with the payload of another message sent to the second device, wherein the other message is associated with a random access procedure involving the first and second devices.
[0091] In some example embodiments, method 500 further includes: determining reference data from at least one of the following: a first message, another message sent to the second device, or a security context, wherein the other message is associated with a random access procedure involving the first device and the second device; and determining association information by comparing the reference data with associated data.
[0092] In some example embodiments, method 500 further includes: if it is determined that the reference data matches the corresponding associated data, determining that the second message is associated with the first message.
[0093] In some example embodiments, the reference data determined from the first message includes at least one of the following: an identifier of the first device, an identifier of the first message, an identifier of the second device, or a paging identifier associated with the first message; and / or wherein the reference data determined from another message includes at least one of the following: a contention resolution identifier, or a data segment associated with the payload of the other message.
[0094] In some example embodiments, method 500 further includes: determining associated information if it is determined that the service type of the first message indicating the second message is command or unknown.
[0095] In some example embodiments, method 500 further includes: if it is determined that the service type of the first message indicating the second message is only inventory, stopping waiting for the reception of the second message.
[0096] In some example embodiments, method 500 further includes: after sending another message, starting a timer of a duration to monitor for a second message; determining that the second message is associated with the first message in response to receiving the second message before the timer expires; and stopping waiting for the second message in response to not receiving the second message before the timer expires.
[0097] In some example embodiments, the duration is predefined or configured by the second device; or the duration is determined based on at least one of the following: the identifier of the first device, the identifier of the first message, or the identifier of the second device; or the duration is determined based on at least one of the following: information of the maximum timer, or the end time information of the resources allocated for the second message.
[0098] In some example embodiments, method 500 further includes sending another message, including the identifier of the first device, to the second device via a random access procedure.
[0099] In some example embodiments, the first device includes an Ambient Internet of Things (AIoT) device, while the second device includes a reader device.
[0100] Figure 6 A flowchart of an example method 600 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 600 is described by the angle of the second device 120 in the middle.
[0101] At frame 610, the second device 120 sends a first message associated with paging the first device to the first device.
[0102] In box 620, the second device 120 sends a second message to the first device following the first message. The second message includes association data for determining whether the second message is associated with the first message.
[0103] In some example embodiments, the associated data includes at least one of the following: an identifier of the first device, an identifier of the first message, an identifier of the second device, a paging identifier associated with the first message, a security context, a contention resolution identifier, or a data segment associated with the payload of another message received from the first device, wherein the other message is associated with a random access procedure involving the first and second devices.
[0104] In some example embodiments, the first message indicates at least one of the following: an identifier of a first device, an identifier of the first message, an identifier of a second device, or a paging identifier associated with the first message; and / or another message indicates at least one of the following: a contention resolution identifier, or a data segment associated with the payload of another message.
[0105] In some example embodiments, the service type of the second message is one of inventory, command, or unknown.
[0106] In some example embodiments, method 600 further includes sending a second message based on the time length following the preamble message.
[0107] In some example embodiments, the duration is predefined or configured by the second device.
[0108] In some example embodiments, the duration is determined based on at least one of the following: the identifier of the first device, the identifier of the first message, or the identifier of the second device.
[0109] In some example embodiments, the duration is determined based on at least one of the following: information about the maximum timer, or information about the end time of the resources allocated for the second message.
[0110] In some example embodiments, method 600 further includes receiving, via a random access procedure, another message including an identifier of the first device from the first device.
[0111] In some example embodiments, the first device includes an Ambient Internet of Things (AIoT) device, while the second device includes a reader device.
[0112] In some example embodiments, a first device capable of performing any method 500 (e.g., Figure 1 The first device 110 may include a component for performing a corresponding operation of method 500. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module. The first device may be implemented as or included in... Figure 1 In the first device 110.
[0113] In some example embodiments, the first device includes: a component for receiving a first message associated with paging the first device from a second device; and a component for determining association information based on at least one of the following: whether a second message following the first message is associated with the first message: associated data included in the second message, or the length of time associated with the reception of the second message.
[0114] In some example embodiments, the associated data includes at least one of the following: an identifier of the first device, an identifier of the first message, an identifier of the second device, a paging identifier associated with the first message, a security context, a contention resolution identifier, or a data segment associated with the payload of another message sent to the second device, wherein the other message is associated with a random access procedure involving the first and second devices.
[0115] In some example embodiments, the first device further includes: components for determining reference data from at least one of: a first message, another message sent to the second device, or a security context, wherein the other message is associated with a random access procedure involving the first device and the second device; and components for determining association information by comparing the reference data with associated data.
[0116] In some example embodiments, the first device further includes a component for determining that the second message is associated with the first message if it is determined that the reference data matches the corresponding associated data.
[0117] In some example embodiments, the reference data determined from the first message includes at least one of the following: an identifier of the first device, an identifier of the first message, an identifier of the second device, or a paging identifier associated with the first message; and / or wherein the reference data determined from another message includes at least one of the following: a contention resolution identifier, or a data segment associated with the payload of the other message.
[0118] In some example embodiments, the first apparatus further includes a component for determining associated information if it is determined that the service type of the first message indicating the second message is command or unknown.
[0119] In some example embodiments, the first device further includes a component for stopping waiting for the reception of the second message if it is determined that the first message indicates that the service type of the second message is only inventory.
[0120] In some example embodiments, the first device further includes: a component for starting a timer of a duration to monitor for a second message after sending another message; a component for determining that the second message is associated with the first message in response to receiving the second message before the timer expires; and a component for stopping waiting for the second message in response to failing to receive the second message before the timer expires.
[0121] In some example embodiments, the duration is predefined or configured by the second device; or the duration is determined based on at least one of the following: the identifier of the first device, the identifier of the first message, or the identifier of the second device; or the duration is determined based on at least one of the following: information of the maximum timer, or the end time information of the resources allocated for the second message.
[0122] In some example embodiments, the first device further includes a component for sending another message, including the identifier of the first device, to the second device via a random access procedure.
[0123] In some example embodiments, the first device includes an Ambient Internet of Things (AIoT) device, while the second device includes a reader device.
[0124] In some example embodiments, a second means capable of performing any of the methods in method 600 (e.g., Figure 1 The second device 120 may include a component for performing the corresponding operation of method 600. This component may be implemented in any suitable form. For example, the component may be implemented in a circuit or software module. The second device may be implemented as or included in... Figure 1 The second device 120 in the middle.
[0125] In some example embodiments, the second device includes: a component for sending a first message associated with paging the first device to the first device; and a component for sending a second message following the first message to the first device, the second message including association data for determining whether the association information is associated with the first message.
[0126] In some example embodiments, the associated data includes at least one of the following: an identifier of the first device, an identifier of the first message, an identifier of the second device, a paging identifier associated with the first message, a security context, a contention resolution identifier, or a data segment associated with the payload of another message received from the first device, wherein the other message is associated with a random access procedure involving the first and second devices.
[0127] In some example embodiments, the first message indicates at least one of the following: an identifier of a first device, an identifier of the first message, an identifier of a second device, or a paging identifier associated with the first message; and / or another message indicates at least one of the following: a contention resolution identifier, or a data segment associated with the payload of another message.
[0128] In some example embodiments, the service type of the second message is one of inventory, command, or unknown.
[0129] In some example embodiments, the second device further includes a component for sending a second message based on the time length following the preamble message.
[0130] In some example embodiments, the duration is predefined or configured by the second device.
[0131] In some example embodiments, the duration is determined based on at least one of the following: the identifier of the first device, the identifier of the first message, or the identifier of the second device.
[0132] In some example embodiments, the duration is determined based on at least one of the following: information about the maximum timer, or information about the end time of the resources allocated for the second message.
[0133] In some example embodiments, the second device further includes a component for receiving, via a random access procedure, another message including the identifier of the first device from the first device.
[0134] In some example embodiments, the first device includes an Ambient Internet of Things (AIoT) device, and the second device includes a reader device.
[0135] Figure 7 This is a simplified block diagram of a device 700 suitable for implementing an example embodiment of the present disclosure. Device 700 can be used to implement a communication device, for example, as... Figure 1 The first device 110 or the second device 120 shown. As shown, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processors 710, and one or more communication modules 740 coupled to the processors 710.
[0136] Communication module 740 is used for bidirectional communication. Communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface necessary for communication with other network elements. In some example embodiments, communication module 740 may include at least one antenna.
[0137] As a non-limiting example, processor 710 can be any type suitable for a local technology network and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 700 can have multiple processors, such as application-specific integrated circuit chips, which are time-subordinate to a clock that synchronizes the main processor.
[0138] Memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that will not be retained during power outages.
[0139] Computer program 730 includes computer-executable instructions that are executed by an associated processor 710. The instructions of program 730 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 730 may be stored in memory (e.g., ROM 724). Processor 710 can perform any suitable actions and processes by loading program 730 into RAM 722.
[0140] The exemplary embodiments of this disclosure can be implemented by program 730, enabling device 700 to perform as described in the reference. Figures 3 to 6 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or a combination of software and hardware.
[0141] In some example embodiments, program 730 may be tangibly contained in a computer-readable medium, which may be included in device 700 (such as in memory 720) or in other storage devices accessible by device 700. Device 700 may load program 730 from the computer-readable medium into RAM 722 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation of the medium itself (i.e., tangible, not tactile), rather than a limitation of the persistence of data storage (e.g., RAM versus ROM).
[0142] Figure 8 An example of a computer-readable medium 800 is shown, which may be in the form of a CD, DVD, or other optical storage disc. The computer-readable medium 800 has a program 730 stored thereon.
[0143] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, and others can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.
[0144] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions, such as those included in a program module, which execute in a device on a target physical or virtual processor to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, the program module can reside on both local and remote storage media.
[0145] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0146] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.
[0147] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0148] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure, but rather as a description of features that may be specific to particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.
[0149] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms for implementing the claims.
[0150] Further examples of embodiments according to this disclosure are shown below.
[0151] Example 1. A first device for communication, comprising: At least one processor; and At least one memory, the at least one memory storing instructions, which, when executed by at least one processor, cause the first device to at least: Receive from the second device a first message associated with paging the first device; and The association information is determined based on at least one of the following, wherein the association information pertains to whether a second message following the first message is associated with the first message: Related data included in the second message, or The length of time associated with the receipt of the second message.
[0152] Example 2. According to the first device of Example 1, the associated data includes at least one of the following: The identifier of the first device, The identifier of the first message, The identification of the second device, The paging identifier associated with the first message. Security context, Competition resolution identifier, or A data segment associated with the payload of another message sent to the second device, wherein the other message is associated with a random access procedure involving the first and second devices.
[0153] Example 3. According to the first device of Example 1 or Example 2, wherein the first device is made such that: The reference data is determined from at least one of the following: a first message, another message sent to the second device, or a security context, wherein the other message is associated with a random access procedure involving the first and second devices; and By comparing reference data with related data, the relevant information is determined.
[0154] Example 4. According to the first device of Example 3, wherein the first device is made such that: If the reference data is determined to match the corresponding associated data, then the second message is determined to be associated with the first message.
[0155] Example 5. The first apparatus according to Example 3 or Example 4, wherein the reference data determined from the first message includes at least one of the following: The identifier of the first device, The identifier of the first message, The identifier of the second device, or The paging identifier associated with the first message; and / or The reference data determined from another message includes at least one of the following: Competition resolution identifier, or The data segment associated with the payload of another message.
[0156] Example 6. A first device according to any one of Examples 1 to 5, wherein the first device is such that: If it is determined that the service type of the first message instructing the second message is command or unknown, determine the associated information.
[0157] Example 7. A first device according to any one of Examples 1 to 6, wherein the first device is such that: If it is determined that the service type of the first message indicating the second message is only inventory, stop waiting for the second message to be received.
[0158] Example 8. A first device according to any one of Examples 1 to 7, wherein the first device is such that: After sending another message, start a timer with a duration to monitor for the second message; In response to receiving a second message before the timer expires, it is determined that the second message is associated with the first message; and If the second message is not received before the timer expires, stop waiting for the second message.
[0159] Example 9. A first device according to any one of Examples 1 to 8, wherein the duration is predefined or configured by a second device; or The duration is determined based on at least one of the following: The identifier of the first device, The identifier of the first message, or The identifier of the second device; or The duration is determined based on at least one of the following: Information about the maximum timer, or Information on the end time of the resources allocated in response to the second message.
[0160] Example 10. A second means for communication, comprising: At least one processor; and At least one memory, the at least one memory storing instructions, which, when executed by at least one processor, cause the second device to at least: Send a first message associated with paging the first device to the first device; and A second message following the first message is sent to the first device. The second message includes association data for determining whether the second message is associated with the first message.
[0161] Example 11. A second apparatus according to Example 10, wherein the associated data includes at least one of the following: The identifier of the first device, The identifier of the first message, The identification of the second device, The paging identifier associated with the first message. Security context, Competition resolution identifier, or A data segment associated with the payload of another message received from the first device, wherein the other message is associated with a random access procedure involving the first and second devices.
[0162] Example 12. A second device according to Example 10, wherein the first message indicates at least one of the following: The identifier of the first device, The identifier of the first message, The identifier of the second device, or The paging identifier associated with the first message; and / or Another message indicates at least one of the following: Competition resolution identifier, or The data segment associated with the payload of another message.
[0163] Example 13. The second device according to Example 10, wherein the service type of the second message is one of inventory, command, or unknown.
[0164] Example 14. A method for communication, comprising: Receive from the second device a first message associated with paging the first device; and The association information is determined based on at least one of the following, wherein the association information pertains to whether a second message following the first message is associated with the first message: Related data included in the second message, or The length of time associated with the receipt of the second message.
[0165] Example 15. A method for communication, comprising: Send a first message associated with paging the first device to the first device; and A second message following the first message is sent to the first device. The second message includes association data for determining whether the second message is associated with the first message.
Claims
1. A first device for communication, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions, when executed by the at least one processor, cause the first device to at least: Receive a first message associated with paging the first device from the second device; as well as The association information is determined based on at least one of the following, wherein the association information pertains to whether a second message following the first message is associated with the first message: The associated data included in the second message, or The length of time associated with receiving the second message.
2. The first apparatus according to claim 1, wherein the associated data includes at least one of the following: The identifier of the first device, The identifier of the first message, The identifier of the second device, The paging identifier associated with the first message, Security context, Competition resolution identifier, or A data segment associated with the payload of another message sent to the second device, wherein the other message is associated with a random access procedure involving the first device and the second device.
3. The first device according to claim 1 or claim 2, wherein the first device is configured to: The reference data is determined from at least one of the following: the first message, another message sent to the second device, or a security context, wherein the other message is associated with a random access procedure involving the first device and the second device; and The association information is determined by comparing the reference data with the associated data.
4. The first device according to claim 3, wherein the first device is configured to: If it is determined that the reference data matches the corresponding associated data, then the second message is associated with the first message.
5. The first apparatus of claim 3, wherein the reference data determined from the first message includes at least one of the following: The identifier of the first device, The identifier of the first message, The identifier of the second device, or The paging identifier associated with the first message; and / or The reference data determined from the other message includes at least one of the following: Competition resolution identifier, or The data segment associated with the payload of the other message.
6. The first device according to claim 1 or claim 2, wherein the first device is configured to: If it is determined that the service type of the first message indicating the second message is command or unknown, the associated information is determined.
7. The first device according to claim 1 or claim 2, wherein the first device is configured to: If it is determined that the first message indicates that the service type of the second message is only inventory, stop waiting for the receipt of the second message.
8. The first device according to claim 1 or claim 2, wherein the first device is configured to: After sending the other message, a timer with the specified duration is started to monitor the second message; In response to receiving the second message before the timer expires, determining that the second message is associated with the first message; and In response to the failure to receive the second message before the timer expires, the waiting for the second message is stopped.
9. The first device according to claim 1 or claim 2, wherein the time length is predefined or configured by the second device; or The duration of said time is determined based on at least one of the following: The identifier of the first device, The identifier of the first message, or The identifier of the second device; or The duration of said time is determined based on at least one of the following: Information about the maximum timer, or The end time information for the resources allocated in response to the second message.
10. A second means for communication, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions, when executed by the at least one processor, cause the second device to at least: Send a first message associated with paging the first device to the first device; as well as A second message following the first message is sent to the first device. The second message includes association data for determining whether the second message is associated with the first message.