Device, reader, data processing method, communication method, and program

Abstract

The purpose of the present disclosure is to provide: a device capable of being operated in an efficient processing sequence; a reader; a data processing method; a communication method; and a program. The device according to the present disclosure comprises: an execution unit that executes a random access procedure together with a reader; and a decision unit that decides on an access stratum (AS) identifier (ID) for identifying the device after the random access procedure is completed. The AS ID is a random ID for identifying the device generated for random access procedure contention resolution and / or identification information allocated by the reader.

Description

Device, Reader, Data Processing Method, Communication Method, and Program

[0001] The present disclosure relates to a device, a reader, a data processing method, a communication method, and a program.

[0002] In 3GPP (Registered Trademark) (3rd Generation Partnership Project), the application of AIoT (Ambient Internet of Things) within the 3GPP system has been under consideration. The number of devices related to AIoT is expected to increase exponentially in the future. Furthermore, for devices related to AIoT, power consumption reduction is desired compared to existing IoT-related devices. An AIoT device is an ambient power-enabled IoT device. An AIoT device is an IoT device powered by energy harvesting (environmental power generation) and is either battery-less or has limited energy storage capabilities (e.g., using a capacitor). The energy for an AIoT device is supplied by harvesting radio waves, light, motion, heat, or other suitable power sources.

[0003] Non-Patent Document 1 shows various considerations regarding AIoT. For example, it shows considerations regarding the introduction of an AS (Access Stratum) ID (Identifier) used for scheduling when transmitting AIoT data between a device and a reader. Furthermore, Non-Patent Document 1 shows considerations regarding the processing when data transmission related to AIoT fails.

[0004] R2-2407984, TP for TR 38.769 update, Huawei, CMCC, T-Mobile USA, 3GPP TSG-RAN WG2 Meeting #127-bis, Hefei, China, 14th - 18th October, 2024

[0005] In the future, the number of AIoT devices deployed within 3GPP systems is expected to increase dramatically, and further reductions in power consumption are desired. Therefore, improving the processing sequences for AIoT devices will be a key challenge going forward.

[0006] One of the purposes of this disclosure is to provide devices, readers, data processing methods, communication methods, and programs that can operate in an efficient processing sequence.

[0007] The device relating to this disclosure comprises an execution unit that performs a random access procedure with a reader, and a determination unit that determines an Access Stratum (AS) ID (Identifier) ​​to identify the device after the random access procedure is completed, wherein the AS ID is at least one of the identification information assigned to the random ID that identifies the device generated for Contention Resolution in the random access procedure.

[0008] The reader relating to this disclosure includes an execution unit that performs a random access procedure with a device, and a communication unit that sends an R2D message to the device containing instruction information instructing that the random ID used to identify the device be the AS ID used to identify the device if the random ID used to identify the device generated for Contention Resolution in the random access procedure does not overlap with that of other devices, and sends an R2D message to the device containing instruction information instructing that the random ID used to identify the device be the AS ID used to identify the device if the random ID used to identify the device does overlap with that of other devices.

[0009] The data processing method relating to this disclosure involves performing a random access procedure with a reader, determining an Access Stratum (AS) ID (Identifier) ​​to identify a device after the random access procedure is completed, wherein the AS ID is at least one of a random ID that identifies the device for Contention Resolution generated in the random access procedure and identification information assigned by the reader.

[0010] The communication method relating to this disclosure performs a random access procedure with a device, and if the random ID used to identify the device generated for Contention Resolution in the random access procedure does not overlap with that of other devices, it sends an R2D message to the device containing instruction information that instructs the random ID to be used as the AS ID that identifies the device, and if the random ID used to identify the device generated for Contention Resolution in the random access procedure overlaps with that of other devices, it sends an R2D message to the device containing instruction information that instructs the random ID and the assigned identification information to be used as the AS ID that identifies the device.

[0011] The program relating to this disclosure causes a computer to perform a random access procedure with a reader, and after the random access procedure is completed, to determine an Access Stratum (AS) ID (Identifier) ​​to identify the device, wherein the AS ID is at least one of a random ID that identifies the device in the random access procedure and identification information assigned by the reader.

[0012] This disclosure provides devices, readers, data processing methods, communication methods, and programs that can operate in an efficient processing sequence.

[0013] Figure 1 shows an example of a device configuration. Figure 2 shows the flow of data processing methods performed in the device. Figure 3 shows an example of a reader configuration. Figure 4 shows the processing flow of communication methods performed in the reader. Figure 5 shows an example of an AIoT device configuration. Figure 6 shows the processing flow that triggers the reader to start communication with the AIoT device. Figure 7 shows the random access procedure for CBRA. Figure 8 shows the case where message 1 sent by the AIoT device did not reach the reader. Figure 9 shows the case where message 2 sent by the reader did not reach the AIoT device. Figure 10 shows the random access procedure for CFRA. Figure 11 shows the random access procedure for CBRA. Figure 12 shows the random access procedure for CBRA. Figure 13 shows the random access procedure for CFRA. Figure 14 shows the random access procedure for CFRA. Figure 15 shows the random access procedure for CBRA. Figure 16 shows the random access procedure for CBRA. Figure 17 shows the flow of communication processing according to the re-access status when random access fails. Figure 18 is a block diagram showing an example configuration of a reader. Figure 19 is a block diagram showing an example configuration of a device and an AIoT controller.

[0014] Embodiment 1 Figure 1 shows an example of the configuration of device 10. Device 10 may be an AIIoT device (hereinafter referred to as an AIIoT device). Device 10 may, for example, function as a tag, allowing for contactless reading or rewriting of information from a reader. The tag may be, for example, an RFID (Radio Frequency Identification) tag or an IC (Integrated Circuit) tag. Device 10 may, for example, function as a sensor. Device 10 may hold information detected by the sensor. Device 10 may include, for example, a sensor and a tag.

[0015] Device 10 has an execution unit 11 and a decision unit 12. Device 10 may be a computer device that operates by a processor executing a program stored in memory. The execution unit 11 and the decision unit 12 may be software or modules whose processing is performed by a processor executing a program stored in memory. Alternatively, the execution unit 11 and the decision unit 12 may be hardware such as a circuit or chip.

[0016] The execution unit 11 may be used as a means to execute a process or procedure. The decision unit 12 may be used as a means to determine data, a process, or a procedure.

[0017] The execution unit 11 executes a random access procedure in relation to the reader. The random access procedure may be, for example, a two-step random access procedure or a three-step random access procedure. Alternatively, the random access procedure may be CBRA (Contention Based Random Access) or CFRA (Contention Free Random Access).

[0018] In a three-step random access procedure, for example, device 10 sends message 1 containing a random ID to the reader. Next, the reader sends message 2 containing the random ID included in message 1 to device 10. Next, device 10 sends message 3 containing the device ID of device 10 to the reader. Alternatively, the three-step random access procedure may be a four-step random access procedure that includes a step in which the reader sends the contention resolution to device 10.

[0019] In a two-step random access procedure, for example, device 10 performs a step that serves the same purpose as messages 1 and 3 in a three-step random access procedure (i.e., sends message 1 containing a random ID and a device ID to the reader). Next, the reader performs a step that serves the same purpose as message 2 in a three-step random access procedure (i.e., sends message 2 containing the random ID included in message 1 to device 10).

[0020] CBRA is a procedure in which the access timing sent from device 10 to the reader may overlap with the access timing sent from other devices. Overlapping access timings sent from devices can also be described as an access contention occurring. CFRA may be a procedure in which, for example, the timing of access from device 10 to the reader is controlled by the reader. By controlling the procedure in which device 10 accesses the reader, collisions can be avoided. On the other hand, in CBRA, the random ID sent from device 10 to the reader may overlap with the random ID sent from other devices. Overlapping random IDs sent from devices can also be described as a random ID collision or collision occurring.

[0021] The success of the random access procedure establishes a connection between device 10 and the reader. The establishment of a connection between device 10 and the reader may also be referred to as establishing a channel or setting up a channel.

[0022] The determination unit 12 determines an Access Stratum (AS) ID (Identifier) ​​to identify the device 10 after the random access procedure is completed. The AS ID is used as identification information to identify the device 10 in communication between the device 10 and the reader after the connection between the device 10 and the reader is established. For example, the AS ID may be used as information to identify the device 10 when the reader notifies the device 10 of the scheduling result of a Device to Reader (D2R) message sent from the device 10 to the reader. The AS ID may also be used by the device 10 to determine whether or not a Reader to Device (R2D) message sent from the reader is destined for the device 10.

[0023] Figure 2 shows the flow of the data processing method performed in device 10. First, the execution unit 11 performs a random access procedure with the reader (S11). Next, the determination unit 12 determines an AS ID to identify the device after the random access procedure is completed (S12).

[0024] Figure 3 shows an example configuration of the reader 20. The reader 20 may be a computer device that operates by having a processor execute a program stored in memory. The reader 20 writes data to the device 10 and reads data stored in the device 10. The reader 20 may be used in conjunction with other devices. For example, the reader 20 may be used in conjunction with a device that performs wireless communication with the device 10. The device that performs wireless communication may be, for example, a base station or an access point that runs a wireless LAN (Local Area Network). The base station may be, for example, a gNB (g NodeB) that supports the so-called 5G wireless communication method specified in the 3GPP standard.

[0025] The leader 20 has an execution unit 21 and a communication unit 22. The execution unit 21 and the communication unit 22 may be software or modules whose processing is performed by the processor executing a program stored in memory. Alternatively, the execution unit 21 and the communication unit 22 may be hardware such as a circuit or chip.

[0026] The execution unit 21 may be used as a means to execute processing or procedures. The communication unit 22 may be used as a means to transmit or receive data.

[0027] The execution unit 21 executes a random access procedure in relation to the device 10.

[0028] The communication unit 22 performs the following processing depending on whether the random ID used to identify device 10 in the random access procedure overlaps with that of other devices. If the random ID does not overlap with that of other devices, the communication unit 22 sends an R2D message to device 10 containing instruction information that instructs the random ID to be used as the AS ID to identify device 10. The communication unit 22 sends the instruction information to device 10 after the random access procedure is completed.

[0029] If the random ID overlaps with that of another device, the communication unit 22 sends instruction information to device 10 instructing it to use the random ID and the access occasion ID indicating the timing of access from device 10 to reader 20 as the AS ID. The communication unit 22 may also send an R2D message containing the instruction information to device 10. Using the random ID and access occasion ID as the AS ID means using information that combines the random ID and the access occasion ID as the AS ID.

[0030] The reader 20 communicates with multiple devices, including device 10. A random ID is generated at each device. Therefore, a random ID generated at one device may overlap with a random ID generated at another device.

[0031] The access occasion ID is identification information that identifies the timing of access. For example, an access occasion ID may be associated with each value from 0 to N (where N is a positive integer). For example, the device that selects an access occasion ID of value 0 may communicate with the reader 20 first. Next, the device that selects an access occasion ID of value 1 may communicate with the reader 20. In other words, devices may communicate with the reader 20 in order, starting with the device that selects an access occasion ID with the smallest value.

[0032] Even if a random ID generated on device 10 overlaps with a random ID generated on another device, including a different access occasion ID in the AS ID makes the AS ID uniquely identify each device.

[0033] Figure 4 shows the processing flow of the communication method executed in the reader 20. First, the execution unit 21 performs a random access procedure with the device 10 (S21). Next, the communication unit 22 determines whether the random ID that identifies the device 10 overlaps with the random ID that identifies another device (S22). The communication unit 22 may receive the determination result regarding whether the random ID that identifies the device 10 overlaps with the random ID that identifies another device from other functional blocks, etc.

[0034] If the random ID used to identify device 10 does not overlap with any other random ID used to identify other devices, the communication unit 22 sends an R2D message to device 10 containing instruction information that instructs the random ID to be used as the AS ID used to identify device 10 (S23).

[0035] If the random ID used to identify device 10 overlaps with a random ID used to identify another device, the communication unit 22 sends an R2D message to device 10 containing instruction information that instructs the random ID and access occasion ID to be set as the AS ID (S24).

[0036] As explained above, after the random access procedure is completed, device 10 can determine an AS ID different from the random ID as information to identify device 10. For example, after the random access procedure is completed, in communication between device 10 and reader 20, device 10 and reader 20 can use a uniquely identified AS ID as information to identify device 10.

[0037] Embodiment 2 Figure 5 shows an example configuration of the AIoT device 30. The AIoT device 30 corresponds to device 10 in Figure 1. The execution unit 31 and the determination unit 33 correspond to the execution unit 11 and the determination unit 12 in Figure 1, so a detailed explanation is omitted. The identification information management unit 32 may be software or a module that performs processing by executing a program. Alternatively, the identification information management unit 32 may be hardware such as a circuit or chip. The identification information management unit 32 may be used as a means for managing identification information.

[0038] The identification information management unit 32 manages random IDs and access occasion IDs. Managing may include processes such as saving, storing, storing, updating, and discarding.

[0039] Next, the communication processing flow in the reader 20, AF (Application Function) entity 40, and AIoT controller 50 will be explained using Figure 6. Figure 6 shows the processing flow that triggers the reader 20 to start communication with the AIoT device 30. The AF entity 40 and AIoT controller 50 may be computer devices that operate by having a processor execute a program stored in memory.

[0040] AF entity 40 is an entity that provides application services. AF entity 40 may, for example, provide application services using data generated by AIoT device 30. Using data generated by AIoT device 30 may involve processing, analyzing, calculating, displaying, or providing the data generated by AIoT device 30 to other devices.

[0041] The AIoT controller 50 may be a device that controls the reader 20 and the AIoT device 30. Controlling the reader 20 and the AIoT device 30 may mean controlling the communication between the reader 20 and the AIoT device 30.

[0042] First, the AF entity 40 sends an Inventory Request message or an AIoT service request to the AIoT controller 50 (S31). The Inventory Request message may be used, for example, to request confirmation of the location of an AIoT device, and the AIoT service request may be used to collect data held by the AIoT device. Alternatively, the AIoT service request message may be used to write data to the AIoT device. The Inventory Request message and the AIoT service request may include, for example, identification information of the AIoT device as filter information. The filter information may be, for example, information for extracting the AIoT device to be accessed. The filter information may also be called filter criteria information. Furthermore, the Inventory Request message and the AIoT service request may include identification information of the reader. Furthermore, the Inventory Request message and the AIoT service request may include information indicating the frequency of access to the AIoT device. The frequency of access to the AIoT device may be the frequency of collecting data from the AIoT device, or the frequency of writing data to the AIoT device. The frequency of access to AIoT devices may, for example, be information indicating periodicity.

[0043] Next, the AIoT controller 50 executes an authentication process for an Inventory Request message and an AIoT service request (S32). The authentication process for the Inventory Request message and the AIoT service request may be a process performed to determine whether to send the Inventory Request message and the AIoT service request to the reader 20. For example, the process for the Inventory Request message and the AIoT service request may be a process of authenticating the AF entity 40. Specifically, the process for the Inventory Request message and the AIoT service request may be a process related to whether to accept the Inventory Request message and the AIoT service request sent from the AF entity 40.

[0044] When the AIoT controller 50 determines to send an Inventory Request message and an AIoT service request to the reader 20, it sends the Inventory Request message and the AIoT service request to the reader 20 (S33). The AIoT controller 50 may send the Inventory Request message and the AIoT service request to the reader indicated by the reader identification information included in the Inventory Request message and the AIoT service request.

[0045] Upon receiving the Inventory Request message and the AIoT service request, the reader 20 starts communication with at least one AIoT device indicated by the filter criteria information.

[0046] Next, the communication process flow between the reader 20 and the AIoT device 30 will be described using FIG. 7. FIG. 7 shows a random access procedure for CBRA. First, the reader 20 transmits an AIoT paging message to the AIoT device 30 (S41). For example, the reader 20 may transmit an AIoT paging message to start communication with the AIoT device 30. When transmitting the AIoT paging message, for example, the resources between the reader 20 and the AIoT device 30 may be in a released state. Also, the reader 20 may not hold information about the AIoT device 30. The reader 20 may transmit an AIoT paging message契机として when receiving an Inventory Request message or an AIoT service request. Or, the reader 20 may transmit an AIoT paging message契机として when receiving a message from a core network different from the Inventory Request message or the AIoT service request.

[0047] The AIoT paging message may be used to call one AIoT device or may be used to call a plurality of AIoT devices. The AIoT paging message may include filter information.

[0048] Next, the AIoT device 30 generates a random ID and selects an access occasion ID indicating the timing of communicating with the reader 20 (S42). The AIoT device 30 may generate a random ID and select an access occasion ID when the AIoT device 30 satisfies the filter information. Satisfying the filter information may mean that the filter information includes identification information for identifying the AIoT device 30. That is, satisfying the filter information may mean that the communication target of the reader 20 is the AIoT device 30.

[0049] It should be noted that there are some inaccuracies in the original Chinese text, such as "契机として" which is an incorrect usage in this context. I have tried my best to translate it as accurately as possible while maintaining the overall meaning.Furthermore, the AIoT paging message may also indicate a range of access occasion IDs. The range of access occasion IDs may be indicated, for example, from 0 to N (where N is a positive integer).

[0050] Next, the AIoT device 30 stores the selected access occasion ID and the generated random ID in the identification information management unit 32 (S43). Alternatively, if the random ID and access occasion ID are stored in the identification information management unit 32, the AIoT device 30 may update the information stored in the identification information management unit 32 with the selected access occasion ID and the generated random ID. Alternatively, if the random ID and access occasion ID are stored in the identification information management unit 32, the AIoT device 30 may replace the information stored in the identification information management unit 32 with the selected access occasion ID and the generated random ID.

[0051] Next, the AIoT device 30 performs a random access procedure with respect to the reader 20 (S44). The AIoT device 30 may, for example, perform a three-step random access procedure.

[0052] For example, in a three-step random access procedure, the reader 20 may determine that the random access to the AIoT device 30 has been successful when it receives message 3 containing the device ID of the AIoT device 30. Successful random access to the AIoT device 30 may mean, for example, that the random ID generated by the AIoT device 30 does not overlap with the random ID generated by other AIoT devices. Alternatively, the random ID generated by the AIoT device 30 may overlap with the random ID generated by other devices, but the reader 20 sends message 2 to the AIoT device 30 and does not send message 2 to the other devices.

[0053] Next, if the reader 20 determines that the random access to the AIoT device 30 was successful, it sends a success indication message to the AIoT device 30 (S45). The success indication message may include information indicating the definition of the AS ID. The success indication message may also be instruction information indicating the definition of the AS ID. For example, the definition of the AS ID may be that the random ID is the AS ID, or that the random ID and the access occasion ID are the AS ID.

[0054] For example, suppose reader 20 receives message 1 from AIoT device 30, which contains a random ID that does not overlap with a random ID received from another AIoT device. In this case, reader 20 may include definition information in the success notification message indicating that the random ID generated by AIoT device 30 is the AS ID. Also suppose reader 20 receives message 1 from AIoT device 30, which contains a random ID that overlaps with a random ID received from another AIoT device. Furthermore, suppose reader 20 sends message 2 to AIoT device 30. In this case, reader 20 may include definition information in the success notification message indicating that the random ID generated by AIoT device 30 and the access occasion ID selected by AIoT device 30 are the AS IDs.

[0055] Next, the reader 20 sends an R2D message to the AIoT device 30 indicating the scheduling result of the D2R message (S46). The reader 20 may include the AS ID defined in the success notification message in the R2D message as information to identify the AIoT device 30.

[0056] In Figure 7, the success notification message in step S45 includes information indicating the definition of the AS ID, but the R2D message in step S46 may also include information indicating the definition of the AS ID. If the R2D message in step S46 includes information indicating the definition of the AS ID, the reader 20 does not need to send the success notification message in step S45.

[0057] Next, we will explain the operation when random access fails using Figures 8 and 9. Figure 8 shows the case in which message 1, sent by the AIoT device 30 in step S51, does not reach the reader 20. The case in which message 1 does not reach the reader 20 may include cases in which the reader 20 does not receive message 1 and cases in which the receiving process of message 1 fails. In the case of Figure 8, the AIoT device 30 does not receive message 2, which is a response message to message 1, from the reader 20.

[0058] Figure 9 shows a case where message 2 sent by reader 20 did not reach AIoT device 30. In the case of Figure 9, reader 20 received message 1 in step S61, but message 2 sent from reader 20 in step S62 did not reach AIoT device 30.

[0059] As shown in Figures 8 and 9, if the AIoT device 30 does not receive message 2, it may discard the access occasion ID and random ID stored in the identification information management unit 32 in step S43 of Figure 7. For example, if the AIoT device 30 does not receive message 2 within a predetermined period after sending message 1, it may discard the access occasion ID and random ID.

[0060] In addition to the cases shown in Figures 8 and 9, another case in which random access fails is when the reader 20 does not receive message 3 sent from the AIoT device 30. In this case, the reader 20 recognizes the random ID and access occasion ID of the AIoT device 30, but does not recognize the device ID of the AIoT device 30.

[0061] Normally, when the reader 20 receives a request from the AF entity 40 and communicates with the AIoT device 30, it identifies the AIoT device 30 based on the device ID specified by the AF entity 40 or the AIoT controller 50. Therefore, if the reader 20 does not know the device ID of the AIoT device 30, it cannot communicate with the AIoT device 30 based on the request from the AF entity 40. For this reason, even if the AIoT device 30 keeps the access occasion ID and random ID stored, there is no problem because it does not expect to be accessed by the reader 20 after the random access procedure. Alternatively, if the AIoT device 30 does not receive a message (e.g., a success notification message) from the reader 20 within a predetermined period after sending message 3, it may discard the stored access occasion ID and random ID.

[0062] Alternatively, if the reader 20 does not receive message 3 from the AIoT device 30 within a predetermined period after sending message 2, it may send a failure indication message to the AIoT device 30 indicating a failure of random access. If the AIoT device 30 receives a failure indication message, it may discard the stored access occasion ID and random ID.

[0063] Next, the communication process flow between the reader 20 and the AIoT device 30 will be explained using Figure 10. Figure 10 shows the random access procedure for CFRA. First, the reader 20 sends an AIoT paging message to the AIoT device 30 (S71). For example, the reader 20 may send an AIoT paging message to initiate communication with the AIoT device 30. When sending an AIoT paging message, for example, resources between the reader 20 and the AIoT device 30 may be released. The reader 20 may send an AIoT paging message triggered by receiving an Inventory Request message or an AIoT service request. Alternatively, the reader 20 may send an AIoT paging message triggered by receiving a message from a core network different from an Inventory Request message or an AIoT service request.

[0064] Furthermore, the AIoT paging message may include an access occasion ID indicating the timing at which the AIoT device 30 transmits its identification information to the reader 20. For example, if the AIoT paging message targets only the AIoT device 30 for communication, it may include the device ID of the AIoT device 30. Alternatively, if the AIoT paging message targets multiple AIoT devices, including the AIoT device 30, it may include information combining each device ID with a different access occasion ID. In other words, the reader 20 may control or adjust the timing at which each AIoT device accesses the reader 20.

[0065] Next, the AIoT paging message may include a request to generate a random ID. If the AIoT paging message includes a request to generate a random ID, the AIoT device 30 generates a random ID (S72). The AIoT device 30 may generate a random ID if the AIoT device 30 satisfies the filter information. Satisfying the filter information means that the filter information includes identification information that identifies the AIoT device 30.

[0066] Next, the AIoT device 30 stores the access occasion ID instructed by the reader 20 and the generated random ID in the identification information management unit 32 (S73).

[0067] Next, the AIoT device 30 sends an identification information notification message to the reader 20 (S74). The identification information notification message includes a random ID and a device ID.

[0068] Next, when the reader 20 receives an identification information notification message, it sends a success notification message to the AIoT device 30 that includes information indicating the definition of the AS ID (S75). If the AIoT paging message sent by the reader 20 in step S71 contains only the device ID of the AIoT device 30 (i.e., does not include a request to generate a random ID), the AIoT device 30 will not generate a random ID. In this case, the reader 20 may include in the AIoT paging message sent in step S71 information that combines multiple device IDs and different access occasion IDs for each device ID. In this case, the reader 20 may include definition information in the success notification message indicating that only the access occasion ID is the AS ID.

[0069] Step S76 is the same as step S46 in Figure 7, so a detailed explanation is omitted.

[0070] As explained above, the AIoT device 30 can identify an AS ID in CBRA or CFRA that uniquely identifies the AIoT device 30. This allows the AIoT device 30 and the reader 20 to transmit R2D messages and D2R messages using the AS ID as information to identify the AIoT device 30 after the random access procedure has been executed.

[0071] Embodiment 3: An example of the process by which the reader 20 assigns an AS ID to the AIoT device 30 will be described using Figure 11. Figure 11 shows a random access procedure for CBRA. Steps S81 and S82 are the same as steps S41 and S42 in Figure 7, so a detailed explanation will be omitted.

[0072] Next, the AIoT device 30 performs a random access procedure with respect to the reader 20 (S83). The AIoT device 30 may, for example, perform a three-step random access procedure.

[0073] Here, when the reader 20 receives message 1 containing a random ID, it may include the AS ID assigned to the AIoT device 30 in message 2, which it sends to the AIoT device 30 as a response to message 1. Specifically, message 2 may include the random ID contained in message 1 and the AS ID assigned by the reader 20.

[0074] If the random ID contained in message 1 received from AIoT device 30 does not overlap with a random ID received from another device, the reader 20 may set the random ID contained in message 1 as the AS ID of AIoT device 30.

[0075] Assume that the random ID contained in message 1 received from AIoT device 30 is the same as a random ID received from another device. In this case, reader 20 may assign a new ID to AIoT device 30 as its AS ID that does not overlap with that of another device.

[0076] In other words, the reader 20 may set identification information that can uniquely identify the AIoT device 30 as the AS ID without using a random ID.

[0077] Next, the AIoT device 30 stores the AS ID specified by the reader 20 in the identification information management unit 32 (S84).

[0078] Steps S85 and S86 are the same as steps S45 and S46 in Figure 7, so a detailed explanation is omitted.

[0079] Furthermore, if the AIoT device 30 receives a message from the reader 20 instructing it to discard the AS ID, it may discard the AS ID stored in the identification information management unit 32.

[0080] Next, using Figure 12, we will explain an example of the process by which the reader 20 assigns an AS ID to the AIoT device 30, which differs from that shown in Figure 11. Figure 12 shows a random access procedure for CBRA. Steps S91 to S93 are the same as steps S41, S42, and S44 in Figure 7, so a detailed explanation will be omitted.

[0081] If the random access in step S93 is successful, the reader 20 sends a success notification message to the AIoT device 30 (S94). The reader 20 may include the AS ID assigned to the AIoT device 30 in the success notification message. The AS ID included in the success notification message is the same as the AS ID included in message 2 in Figure 11, so a detailed explanation is omitted.

[0082] Steps S95 and S96 are the same as steps S84 and S86 in Figure 11, so a detailed explanation is omitted.

[0083] Next, using Figure 13, we will explain an example of the process by which the reader 20 assigns an AS ID to the AIoT device 30, which differs from the example in Figure 11. Figure 13 shows the random access procedure for CFRA.

[0084] First, the reader 20 sends an AIoT paging message to the AIoT device 30 (S101). The AIoT paging message may include an access occasion ID indicating when the AIoT device 30 sends its identification information to the reader 20. For example, if the AIoT paging message targets only the AIoT device 30 for communication, it may include the device ID of the AIoT device 30. Alternatively, if the AIoT paging message targets multiple AIoT devices, including the AIoT device 30, it may include information combining each device ID with an occasion ID of a different value. In other words, the reader 20 may control or adjust the timing at which each AIoT device accesses the reader 20.

[0085] Furthermore, the AIoT paging message may include the AS ID assigned by the reader 20 to the AIoT device 30. The AS ID is identification information that can uniquely identify the AIoT device 30.

[0086] Next, the AIoT device 30 sends an identification information notification message containing the device ID of the AIoT device 30 to the reader 20 (S102). Next, the AIoT device 30 stores the AS ID in the identification information management unit 32 (S103).

[0087] Steps S104 and S105 are the same as steps S75 and S76 in Figure 10, so a detailed explanation is omitted.

[0088] Next, using Figure 14, we will explain an example of the process by which the reader 20 assigns an AS ID to the AIoT device 30, which differs from the example in Figure 13. Figure 14 shows the random access procedure for CFRA.

[0089] Step S111 is the same as step S71 in Figure 10, so a detailed explanation is omitted. Also, the AIoT device 30 sends an identification information notification message including the device ID at the timing indicated by the access occasion ID included in the AIoT paging message (S112).

[0090] Next, when the reader 20 receives the identification information notification message, it sends a success notification message to the AIoT device 30 (S113). The success notification message may include the AS ID that the reader 20 has assigned to the AIoT device 30. For example, the AS ID may be an access occasion ID, or it may be any other identification information that can uniquely identify the AIoT device 30.

[0091] Step S115 is the same as step S76 in Figure 10, so a detailed explanation is omitted.

[0092] As explained above, the AIoT device 30 can obtain its identification information by receiving the AS ID specified by the reader 20. This allows the AIoT device 30 and the reader 20 to transmit R2D messages and D2R messages using the AS ID as information to identify the AIoT device 30.

[0093] Embodiment 4 The communication process flow between the reader 20 and the AIoT device 30 will be explained using Figure 15. Figure 15 shows a random access procedure related to CBRA. Steps S121 to S123 are the same as steps S41 to S43 in Figure 7, so a detailed explanation will be omitted.

[0094] Next, the AIoT device 30 performs a random access procedure with respect to the reader 20 (S124). The AIoT device 30 may, for example, perform a three-step random access procedure.

[0095] Suppose that in the random access procedure, the reader 20 determines that the random ID of the AIoT device 30 included in message 1 is the same as the random ID included in message 1 received from another device. In this case, the reader 20 may include the AS ID that the reader 20 has assigned to the AIoT device 30 in message 2, which is the response to message 1. The AS ID that the reader 20 assigns to the AIoT device 30 may be a combination of a random ID and an access occasion ID, or it may be identification information that can uniquely identify other AIoT devices 30.

[0096] When the random access procedure is completed, the AIoT device 30 updates the stored access occasion ID and random ID with the AS ID notified by the reader 20 (S125). Specifically, the AIoT device 30 may replace the stored access occasion ID and random ID with the AS ID notified by the reader 20, or it may store the AS ID together with the access occasion ID and random ID.

[0097] Steps S126 and S127 are the same as steps S45 and S46 in Figure 7, so a detailed explanation is omitted.

[0098] As explained above, the reader 20 may assign an AS ID to the AIoT device 30 if the random ID generated by the AIoT device 30 overlaps with a random ID generated by another AIoT device. This allows the AIoT device 30 and the reader 20 to transmit R2D messages and D2R messages using the AS ID as information to identify the AIoT device 30.

[0099] Embodiment 5 The reader 20 may communicate with multiple AIoT devices. For example, when the reader 20 receives an Inventory Request message or an AIoT service request specifying multiple device IDs, it communicates with multiple AIoT devices. When the reader 20 communicates with AIoT devices, it sends an AIoT paging message. The AIoT paging message may target multiple AIoT devices.

[0100] Even when the reader 20 sends an AIoT paging message targeting multiple AIoT devices, it may not be able to establish a connection with all AIoT devices with a single AIoT paging message. Specifically, if a collision occurs because multiple AIoT devices access the reader 20 substantially simultaneously (same access occasion), there will be AIoT devices that cannot establish a connection with the reader 20. In such cases, the reader 20 sends a re-access paging message to give the AIoT devices that could not establish a connection with the reader 20 another opportunity to access them. The re-access paging message may target multiple AIoT devices, similar to AIoT paging.

[0101] In such cases, the transmission of duplicate messages 1 from an AIoT device that has successfully performed random access will interfere with the access opportunity of an AIoT device that requires re-access. Therefore, it is necessary to clarify the re-access procedure so that the AIoT device requiring re-access can establish a connection with the reader 20.

[0102] Therefore, using Figure 16, we will explain a re-access procedure that can increase the likelihood that an AIoT device requiring a re-access procedure can establish a connection with the reader 20. Figure 16 shows a random access procedure related to CBRA.

[0103] In Figure 16, the AIoT device 30 manages the re-access status. For example, if the re-access status is "enable," the AIoT device 30 is able to respond to re-access paging messages. If the re-access status is "disable," the AIoT device 30 is unable to respond to re-access paging messages.

[0104] Figure 16 shows the flow of communication processing according to the re-access status when random access is successful. In Figure 16, it is assumed that the initial value of the re-access status of the AIoT device (for example, the initial value immediately after power-on or the default value) is "enable". Steps S131 to S135 are the same as steps S41 to S45 in Figure 7, so a detailed explanation is omitted.

[0105] Next, if the AIoT device 30 successfully obtains random access to the reader 20, it updates the re-access status from "enable" to "disable" (S136).

[0106] Next, the AIoT device 30 receives a reaccess paging message from the reader 20 (S137). At this time, the AIoT device 30 decides not to respond to the reaccess paging message because the reaccess status is "disable" (S138). The response to the reaccess paging message may be, for example, not to perform the random access procedure even if the AIoT device 30 has terminated communication with the reader 20.

[0107] Next, the AIoT device 30 updates the re-access status from "disable" to "enable" (S139). For example, suppose the reader 20 is limited to sending only one re-access paging message between the time it sends an AIoT paging message indicating the initial access (not a re-access) and the time it sends an AIoT paging message indicating the next initial access. In this case, the AIoT device 30 may update the re-access status from "disable" to "enable" after receiving the first re-access paging message. Alternatively, suppose the reader 20 is limited to sending multiple re-access paging messages between the time it sends an AIoT paging message indicating the initial access and the time it sends an AIoT paging message indicating the next initial access. In this case, the final indication may be included in the re-access paging message. The AIoT device 30 may update the re-access status from "disable" to "enable" after receiving the re-access paging message containing the final indication.

[0108] Figure 17 shows the flow of communication processing according to the re-access status when random access fails. Steps S141 to S144 are the same as steps S41 to S44 in Figure 7, so a detailed explanation is omitted.

[0109] Next, the AIoT device 30 performs a random access procedure with the reader 20 (S144). Now, let's assume that the random access procedure in step S144 fails. For example, let's assume that the reader 20 did not receive message 3 from the AIoT device 30.

[0110] In such cases, the reader 20 does not send a success notification message to the AIoT device 30. Alternatively, if the reader 20 determines that the random access procedure has failed, it may send a failure notification message to the AIoT device 30.

[0111] Next, the AIoT device 30 receives a re-access paging message from the reader 20 (S145). Since the AIoT device 30 has not received a success notification message since step S144, the re-access status remains "enable". Therefore, upon receiving the re-access paging message from the reader 20, the AIoT device 30 decides to respond to the re-access paging message (S146). If the AIoT device 30 decides to respond to the re-access paging message, it executes the processes from step S142 onwards. In other words, the AIoT device 30 performs a random access procedure with the reader 20.

[0112] Assume that in the reader 20, the sending of a re-access paging message is limited to one between the time an AIoT paging message indicating the initial access is sent and the time an AIoT paging message indicating the next initial access is sent. In this case, the AIoT device 30 may leave the re-access status as "enable" after responding to the first re-access paging message. Assume that in the reader 20, the sending of a re-access paging message is limited to multiple times between the time an AIoT paging message indicating the initial access is sent and the time an AIoT paging message indicating the next initial access is sent. In this case, the final (second) indication may be included in the re-access paging message. After the AIoT device 30 receives the re-access paging message containing the final re-access indication, it may decide not to respond to the re-access paging message and then update the re-access status from "disable" to "enable".

[0113] As explained above, the AIoT device 30 decides whether or not to respond to a reaccess paging message depending on the reaccess status. This prevents, for example, the AIoT device 30, which has communicated with the reader 20, from interfering with the access opportunities of other AIoT devices by accessing the reader 20 again after receiving a reaccess paging message.

[0114] Furthermore, an AIoT device that has already established a connection with the reader 20 will not respond to a re-access paging message. This reduces the number of AIoT devices that respond to re-access paging messages. As a result, an AIoT device that missed receiving the AIoT paging message indicating its initial access and was unable to access the reader 20 will respond to the reader 20's re-access paging message and make a random access. This increases the likelihood that it can establish a connection with the reader 20. An AIoT device that was unable to access the reader 20 is an AIoT device that missed receiving the AIoT paging message indicating its initial access.

[0115] Figure 18 is a block diagram showing an example configuration of the leader 20. Referring to Figure 18, the leader 20 includes an RF transceiver 1001, a network interface 1003, a processor 1004, and a memory 1005. The RF transceiver 1001 performs analog RF signal processing to communicate with UEs. The RF transceiver 1001 may include multiple transceivers. The RF transceiver 1001 is coupled with an antenna 1002 and a processor 1004. The RF transceiver 1001 receives modulated symbol data (or OFDM symbol data) from the processor 1004, generates a transmit RF signal, and supplies the transmit RF signal to the antenna 1002. The RF transceiver 1001 also generates a baseband receive signal based on the received RF signal received by the antenna 1002 and supplies this to the processor 1004.

[0116] The network interface 1003 is used to communicate with network nodes (e.g., other core network nodes). The network interface 1003 may include, for example, a network interface card (NIC) compliant with the IEEE 802.3 series.

[0117] The processor 1004 performs data plane processing and control plane processing, including digital baseband signal processing for wireless communication.

[0118] The processor 1004 may include multiple processors. For example, the processor 1004 may include a modem processor (e.g., DSP) that performs digital baseband signal processing and a protocol stack processor (e.g., CPU or MPU) that performs control plane processing.

[0119] Memory 1005 is composed of a combination of volatile memory and non-volatile memory. Memory 1005 may include a plurality of physically independent memory devices. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof. Non-volatile memory is Mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. Memory 1005 may include storage located away from the processor 1004. In this case, the processor 1004 may access memory 1005 via the network interface 1003 or an I / O interface not shown.

[0120] The memory 1005 may store a software module (computer program) containing a set of instructions and data for performing the processing by the reader 20 as described in the above-described embodiments. In some implementations, the processor 1004 may be configured to read the software module from the memory 1005 and execute it to perform the processing of the reader 20 as described in the above-described embodiments.

[0121] Figure 19 is a block diagram showing an example configuration of device 10 and AIoT controller 50 (hereinafter referred to as device 10, etc.). The Radio Frequency (RF) transceiver 1101 performs analog RF signal processing to communicate with the leader 20. The analog RF signal processing performed by the RF transceiver 1101 includes frequency upconversion, frequency downconversion, and amplification. The RF transceiver 1101 is coupled with the antenna 1102 and the baseband processor 1103. Specifically, the RF transceiver 1101 receives modulation symbol data (or OFDM symbol data) from the baseband processor 1103, generates a transmit RF signal, and supplies the transmit RF signal to the antenna 1102. The RF transceiver 1101 also generates a baseband receive signal based on the received RF signal received by the antenna 1102 and supplies this to the baseband processor 1103.

[0122] The baseband processor 1103 performs digital baseband signal processing (data plane processing) and control plane processing for wireless communication. Digital baseband signal processing includes (a) data compression / decompression, (b) data segmentation / concatenation, (c) generation / decomposition of transmission format (transmission frame), (d) transmission path coding / decoding, (e) modulation (symbol mapping) / demodulation, and (f) generation of OFDM symbol data (baseband OFDM signal) by Inverse Fast Fourier Transform (IFFT). Meanwhile, control plane processing includes communication management at Layer 1, Layer 2, and Layer 3.

[0123] The baseband processor 1103 may include a modem processor (e.g., Digital Signal Processor (DSP)) for performing digital baseband signal processing and a protocol stack processor (e.g., Central Processing Unit (CPU) or Micro Processing Unit (MPU)) for performing control plane processing. In this case, the protocol stack processor for performing control plane processing may be shared with the application processor 1104 described later.

[0124] The application processor 1104 is also called a CPU, MPU, microprocessor, or processor core. The application processor 1104 may include multiple processors (multiple processor cores). The application processor 1104 implements various functions of the device 10, etc., by executing system software programs (Operating System (OS)) and various application programs (e.g., calling applications, web browsers, mail clients, camera operation applications, music playback applications) read from memory 1106 or memory not shown.

[0125] In some implementations, the baseband processor 1103 and the application processor 1104 may be integrated on a single chip, as shown by the dashed line (1105) in Figure 19. In other words, the baseband processor 1103 and the application processor 1104 may be implemented as a single System on Chip (SoC) device 1105. An SoC device is sometimes called a System Large Scale Integration (LSI) or chipset.

[0126] Memory 1106 is volatile memory, non-volatile memory, or a combination thereof. Memory 1106 may include multiple physically independent memory devices. Volatile memory is, for example, Static Random Access Memory (SRAM) or Dynamic RAM (DRAM), or a combination thereof. Non-volatile memory is Mask Read Only Memory (MROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, or hard disk drive, or any combination thereof. For example, memory 1106 may include an external memory device accessible from the baseband processor 1103, the application processor 1104, and the SoC 1105. Memory 1106 may also include an internal memory device integrated within the baseband processor 1103, the application processor 1104, or the SoC 1105. Furthermore, memory 1106 may include memory within a Universal Integrated Circuit Card (UICC).

[0127] The memory 1106 may store a software module (computer program) containing instruction sets and data for processing by the device 10, etc., as described in the above-described embodiments. In some implementations, the baseband processor 1103 or application processor 1104 may be configured to read the software module from the memory 1106 and execute it to perform the processing of the device 10, etc., as described in the above-described embodiments.

[0128] In the examples described above, the program includes a set of instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more of the functions described in the embodiments. The program may be stored on a non-temporary computer-readable medium or a physical storage medium. Examples, but not limited to, include random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technologies, CD-ROM, digital versatile disc (DVD), Blu-ray® disc or other optical disc storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage devices. The program may be transmitted over a temporary computer-readable medium or a communication medium. Examples, but not limited to, include temporary computer-readable medium or a communication medium that includes electrical, optical, acoustic or other forms of propagating signals.

[0129] Although the present disclosure has been described above with reference to embodiments, the present disclosure is not limited to the embodiments described above. Various modifications to the structure and details of the present disclosure can be made as can be understood by those skilled in the art within the scope of the present disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0130] Each drawing is merely illustrative to illustrate one or more embodiments. Each drawing may be associated with one or more other embodiments, rather than being associated with only one specific embodiment. As those skilled in the art will understand, various features or steps described with reference to any one drawing can be combined with features or steps shown in one or more other drawings, for example, to create embodiments not explicitly shown or described. Not all features or steps shown in any one drawing to illustrate an exemplary embodiment are necessarily required, and some features or steps may be omitted. The order of steps described in any of the drawings may be changed as appropriate.

[0131] Some or all of the above embodiments may also be described as follows, but are not limited to the following: (Note 1) A device comprising: an execution unit that performs a random access procedure with a reader; and a determination unit that determines an AS (Access Stratum) ID (Identifier) ​​to identify the device after the random access procedure is completed, wherein the AS ID is at least one of a random ID that identifies the device in the random access procedure and an access occasion ID that identifies the timing of access to the reader. (Note 2) The device according to Note 1, wherein the determination unit determines the AS ID based on instruction information contained in a first R2D message received from the reader after the random access procedure is completed. (Note 3) The device according to Note 2, wherein the instruction information indicates that if the random ID does not overlap with other devices, the random ID is to be the AS ID, and if the random ID overlaps with other devices, the random ID and the access occasion ID are to be the AS ID. (Note 4) The device according to Note 2 or 3, wherein the instruction information indicates that if the second R2D message received from the reader as a trigger for executing the random access procedure includes the access occasion ID, the access occasion ID is set to the AS ID. (Note 5) The device according to any one of Notes 2 to 4, further comprising a communication unit that receives the first R2D message when the random access procedure is successful. (Note 6) The device according to any one of Notes 2 to 5, wherein the first R2D message indicates that the random access procedure was successful. (Note 7) The device according to any one of Notes 2 to 5, wherein the first R2D message indicates the scheduling result of the D2R (Device to Reader) message to be sent to the reader.(Note 8) The device according to any one of Notes 1 to 7, further comprising an identification information management unit that generates the random ID and selects the access occasion ID when it receives a second R2D message from the reader as a trigger for executing the random access procedure, the execution unit sends a first random access message including the random ID to the reader at the access timing indicated by the access occasion ID, and the identification information management unit discards the random ID and the access occasion ID if it does not receive a second random access message from the reader in response to the first random access message. (Note 9) The device according to Note 1, wherein the determination unit receives a message including the AS ID determined by the reader. (Note 10) The device according to Note 9, wherein the message including the AS ID is a second random access message received from the reader in the random access procedure, or a first R2D message indicating that the random access procedure was successful. (Note 11) The device as described in Note 1, wherein the determination unit receives a message containing the AS ID determined by the reader when the random ID overlaps with that of another device, and determines the AS ID based on instruction information indicating that the random ID is the AS ID, which is included in the first R2D message received from the reader after the random access procedure is completed, when the random ID does not overlap with that of another device.(Note 12) A reader comprising: an execution unit that performs a random access procedure between itself and a device; and a communication unit that, if the random ID used to identify the device in the random access procedure does not overlap with that of another device, sends an R2D message to the device containing instruction information that instructs the random ID to be used as the AS ID that identifies the device after the random access procedure is completed; and if the random ID used to identify the device in the random access procedure overlaps with that of another device, sends the R2D message to the device containing instruction information that instructs the random ID and an access occasion ID indicating the timing of access from the device to be used as the AS ID that identifies the device after the random access procedure is completed. (Note 13) The reader according to Note 12, wherein the communication unit sends the R2D message to the device when the random access procedure is successful. (Note 14) The reader according to Note 12 or 13, wherein the R2D message indicates that the random access procedure was successful. (Note 15) The reader described in Note 12 or 13, wherein the R2D message indicates the scheduling result of the D2R (Device to Reader) message transmitted from the device to the reader. (Note 16) A data processing method comprising: performing a random access procedure with the reader; determining an AS (Access Stratum) ID (Identifier) ​​to identify the device after the random access procedure is completed; wherein the AS ID is at least one of a random ID to identify the device in the random access procedure and an access occasion ID to identify the timing of access to the reader.(Note 17) A communication method comprising: executing a random access procedure between a device and a computer; sending an R2D message to the computer containing instruction information instructing that the random ID used to identify the device in the random access procedure be set as the AS ID used to identify the device after the random access procedure is completed, if the random ID used to identify the device in the random access procedure is not duplicated with that of another device; and sending an R2D message to the computer containing instruction information instructing that the random ID and the access occasion ID indicating the timing of access from the device be set as the AS ID used to identify the device after the random access procedure is completed. (Note 18) A program comprising: executing a random access procedure between a computer and a reader; causing a computer to determine an AS (Access Stratum) ID (Identifier) ​​to identify the device after the random access procedure is completed, wherein the AS ID is at least one of the random ID used to identify the device in the random access procedure and the access occasion ID indicating the timing of access to the reader. (Note 19) A program that causes a computer to perform a random access procedure with a device, and if the random ID used to identify the device in the random access procedure does not overlap with that of another device, sends an R2D message to the device containing instruction information that instructs the random ID to be used as the AS ID to identify the device after the random access procedure is completed, and if the random ID used to identify the device in the random access procedure overlaps with that of another device, sends an R2D message to the device containing instruction information that instructs the random ID and the access occasion ID indicating the access timing from the device to be used as the AS ID to identify the device after the random access procedure is completed.

[0132] Some or all of the elements (e.g., configuration and function) described in Appendices 2 to 11 that are dependent on Appendice 1 may also be dependent on Appendices 16 and 18 in the same way as those described in Appendices 2 to 11. Some or all of the elements (e.g., configuration and function) described in Appendices 13 to 15 that are dependent on Appendice 12 may also be dependent on Appendices 17 and 19 in the same way as those described in Appendices 13 to 15. Some or all of the elements described in any appendice may be applied to various hardware, software, recording means, systems, and methods for recording software.

[0133] This application claims priority based on Japanese Patent Application No. 2024-194427, filed on November 6, 2024, and incorporates all of its disclosures herein.

[0134] 10 Device 11 Execution Unit 12 Decision Unit 20 Reader 21 Execution Unit 22 Communication Unit 30 AIoT Device 31 Execution Unit 32 Identification Information Management Unit 33 Decision Unit 40 AF Entity 50 AIoT Controller

Claims

1. A device comprising: execution means for executing a random access procedure between itself and a reader; and determination means for determining an Access Stratum (AS) ID (Identifier) ​​for identifying a device after the random access procedure is completed, wherein the AS ID is at least one of a random ID for identifying the device generated for Contention Resolution in the random access procedure and identification information assigned by the reader.

2. The device according to claim 1, wherein the determination means determines the AS ID based on instruction information contained in the first R2D message received from the reader.

3. The device according to claim 2, wherein the instruction information indicates that if the random ID does not overlap with that of another device, the random ID will be the AS ID, and if the random ID overlaps with that of another device, the identification information assigned by the reader will be the AS ID.

4. The device according to claim 2 or 3, wherein the instruction information indicates that the access occasion ID is the AS ID if the second R2D message received from the reader as a trigger for executing the random access procedure includes an access occasion ID.

5. The device according to claim 2 or 3, further comprising communication means for receiving the first R2D message if the random access procedure is successful.

6. The device according to claim 2 or 3, wherein the first R2D message indicates that the random access procedure was successful.

7. The device according to claim 2 or 3, wherein the first R2D message indicates the scheduling result of a D2R (Device to Reader) message to be sent to the reader.

8. The device according to any one of claims 1 to 3, further comprising identification information management means for generating a random ID and selecting an access occasion ID when a second R2D message is received from the reader as a trigger for executing the random access procedure, wherein the execution means transmits a first random access message including the random ID to the reader at the access timing indicated by the access occasion ID, and the identification information management means discards the random ID and the access occasion ID if it does not receive a second random access message from the reader in response to the first random access message.

9. The device according to claim 1, wherein the determination means receives a message including the AS ID determined by the reader.

10. The device according to claim 9, wherein the message containing the AS ID is a second random access message received from the reader in the random access procedure, or a first R2D message indicating that the random access procedure was successful.

11. The device according to claim 1, wherein the determination means receives a message containing the AS ID determined by the reader when the random ID overlaps with that of another device, and determines the AS ID based on instruction information contained in a first R2D message received from the reader indicating that the random ID is the AS ID when the random ID does not overlap with that of another device.

12. The device according to claim 2, wherein the first R2D message includes an access occasion ID.

13. A reader comprising: execution means for performing a random access procedure between itself and a device; and communication means for sending an R2D message to the device containing instruction information instructing that the random ID used to identify the device be the AS ID used to identify the device if the random ID used to identify the device generated for Contention Resolution in the random access procedure does not overlap with that of other devices; and for sending an R2D message to the device containing instruction information instructing that the random ID used to identify the device be the AS ID used to identify the device if the random ID used to identify the device does overlap with that of other devices.

14. The reader according to claim 13, wherein the communication means transmits the R2D message to the device when the random access procedure is successful.

15. The reader according to claim 13 or 14, wherein the R2D message indicates that the random access procedure was successful.

16. The reader according to claim 13 or 14, wherein the R2D message indicates the scheduling result of a D2R (Device to Reader) message to be sent from the device to the reader.

17. The reader according to claim 13, wherein the R2D message includes an access occasion ID.

18. A data processing method comprising: performing a random access procedure with a reader; determining an Access Stratum (AS) ID (Identifier) ​​to identify a device after the random access procedure is completed; wherein the AS ID is at least one of a random ID that identifies the device generated for Contention Resolution in the random access procedure and identification information assigned by the reader.

19. A communication method comprising: performing a random access procedure between the device and the communication method; sending an R2D message to the device containing instruction information that instructs the random ID to be used as the AS ID to identify the device if the random ID generated for Contention Resolution in the random access procedure does not overlap with that of other devices; and sending an R2D message to the device containing instruction information that instructs the random ID and the assigned identification information to be used as the AS ID to identify the device if the random ID generated for Contention Resolution in the random access procedure overlaps with that of other devices.

20. A program that causes a computer to perform a random access procedure with a reader, and after the random access procedure is completed, to determine an Access Stratum (AS) ID (Identifier) ​​to identify a device, wherein the AS ID is at least one of a random ID that identifies the device generated for Contention Resolution in the random access procedure and identification information assigned by the reader.

21. A program that causes a computer to perform a random access procedure with a device, and if the random ID used to identify the device generated for Contention Resolution in the random access procedure does not overlap with that of other devices, it sends an R2D message to the device containing instruction information that instructs the random ID to be used as the AS ID to identify the device, and if the random ID used to identify the device generated for Contention Resolution in the random access procedure overlaps with that of other devices, it sends an R2D message to the device containing instruction information that instructs the random ID and the assigned identification information to be used as the AS ID to identify the device.

Images