Terminals, communication devices, and communication methods

Abstract

This enables advanced paging in IoT technology. [Solution] The terminal has a storage unit that stores a first group identifier indicating the owner to which the terminal belongs or the owner to which the article to which the terminal is attached belongs, and a transmitting / receiving unit that performs wireless communication with a reader device, the transmitting / receiving unit including a receiving unit that receives a paging message including a second group identifier from the reader device, and a transmitting unit that transmits a paging response to the reader device in response to the second group identifier matching the first group identifier.

Description

Technical Field

[0001] This disclosure relates to a terminal, a communication device, and a communication method used in a wireless communication system.

Background Art

[0002] In 3GPP (registered trademark; the same shall apply hereinafter) (3rd Generation Partnership Project), which is a standardization project for wireless communication systems, the realization of services using ambient power-enabled terminals has been studied (see, for example, Non-Patent Document 1). Such technology is referred to as AIoT (Ambient Internet of Things), and such terminals are referred to as AIoT devices or AIoT terminals.

[0003] The AIoT terminal may be a terminal powered by energy harvesting. The AIoT terminal may be battery-less or have limited energy storage capabilities (e.g., a capacitor), and energy may be supplied by harvesting radio waves, light, motion, heat, or any other suitable power source.

[0004] Compared with IoT technologies already introduced in 3GPP standards, such as NB-IoT (Narrow Band Internet of Things) and eMTC (enhanced Machine-Type Communication), etc., AIoT technology can realize terminals with low complexity, small size, low capabilities, and low power consumption. The AIoT terminal may be maintenance-free and may have a long lifespan.

Prior Art Documents

Non-Patent Documents

[0005]

Non-Patent Document 1

[0006] In IoT technologies such as AIoT, there are plans to use persistent identifiers, which are unique identifiers (i.e., fixed identifiers) to each device, to call (paging) devices from the network side.

[0007] On the other hand, the ownership of a device or an item to which such a device is attached may change. However, because persistent identifiers are fixed identifiers, it is difficult to reflect the current owner in the persistent identifier. Therefore, there is a challenge in that advanced paging that can be performed by specifying the owner cannot be implemented.

[0008] Therefore, this disclosure provides a terminal, a communication device, and a communication method that enable advanced paging in IoT technology. [Means for solving the problem]

[0009] The technology of this disclosure provides a terminal having a storage unit that stores a first group identifier indicating the owner to which the terminal belongs or the owner to which an article to which the terminal is attached belongs, and a transmitting / receiving unit that performs wireless communication with a reader device, wherein the transmitting / receiving unit includes a receiving unit that receives a paging message including a second group identifier from the reader device, and a transmitting unit that transmits a paging response to the reader device in response to the second group identifier matching the first group identifier.

[0010] Furthermore, the technology of this disclosure provides a communication device comprising: a receiving unit that receives a paging request from an external device that includes a group identifier indicating the owner to which the terminal belongs or the owner to which the article to which the terminal is attached belongs; and a transmitting unit that, in response to the receipt of the paging request, transmits a paging message including the group identifier to the terminal or a reader device that performs wireless communication with the terminal.

[0011] Furthermore, the present disclosure provides a communication method performed by a terminal, comprising the steps of: storing a first group identifier indicating the owner to which the terminal belongs or the owner to which an article to which the terminal is attached belongs; receiving a paging message from a reader device including a second group identifier; and transmitting a paging response to the reader device in response to the second group identifier matching the first group identifier. [Effects of the Invention]

[0012] According to the disclosed technology, it is possible to provide terminals, communication devices, and communication methods that enable advanced paging in IoT technology. [Brief explanation of the drawing]

[0013] [Figure 1] This figure shows an example configuration of a wireless communication system according to the first embodiment. [Figure 2] This diagram illustrates problems in inventory operations. [Figure 3] This is a diagram illustrating the overview of the inventory operation according to the first embodiment. [Figure 4] This is a diagram illustrating the operation of the comparative example. [Figure 5] This figure shows an example of the functional configuration of an AIoT device according to the first embodiment. [Figure 6] This figure shows an example of the functional configuration of a communication device that performs paging according to the first embodiment. [Figure 7] This figure shows an example of the operation sequence according to the first embodiment. [Figure 8] It is a diagram showing an example of information stored by the UDM according to the first embodiment. [Figure 9] It is a diagram showing an example of a paging message according to the first embodiment. [Figure 10] It is a diagram showing an example of the operation flow of the AIoT device according to the first embodiment. [Figure 11] It is a diagram showing a configuration example of a wireless communication system according to the second embodiment. [Figure 12] It is a diagram for explaining problems in the group ID according to the first embodiment. [Figure 13] It is a diagram for explaining an overview of the group ID allocation operation according to the second embodiment. [Figure 14] It is a diagram showing an example of the functional configuration of the AIoT device according to the second embodiment. [Figure 15] It is a diagram showing an example of the functional configuration of a communication device that performs group ID allocation according to the second embodiment. [Figure 16] It is a diagram showing an example of the operation sequence according to the second embodiment (part 1). [Figure 17] It is a diagram showing an example of the operation sequence according to the second embodiment (part 2). [Figure 18] It is a diagram showing an example of information stored by the UDM according to the second embodiment. [Figure 19] It is a diagram showing an example of information stored by the UDR according to the second embodiment. [Figure 20] It is a diagram showing an example of the hardware configuration of each communication entity according to each embodiment. [Figure 21] It is a diagram showing an example of the configuration of a vehicle according to each embodiment.

Modes for Carrying Out the Invention

[0014] The wireless communication system according to the first embodiment will be described below with reference to the drawings. Existing technologies will be used as appropriate in the operation of the wireless communication system. Existing technologies include, for example, existing communication methods based on 3GPP standards such as 5G / NR (New Radio). Existing technologies are not limited to 5G / NR, but may also include methods such as 4G / LTE (Long Term Evolution) and LTE-Advanced, or wireless LAN (Local Area Network).

[0015] The embodiments described below are examples and are not limited to those embodiments. For example, the following embodiments mainly describe a wireless communication system having an AIoT device (also referred to as the "AIoT system"), but the wireless communication system may have other IoT devices (e.g., NB-IoT devices and / or eMTC devices, etc.) in place of, or in addition to, the AIoT device. In other words, the wireless communication system of this disclosure is applicable not only to AIoT devices but also to other IoT devices. In the following description of embodiments, the term "AIoT device" may be used interchangeably with the term "IoT device" or the term "terminal".

[0016] (1) First Embodiment The first embodiment will be described.

[0017] (1.1) Example of system configuration Figure 1 shows an example of the configuration of a wireless communication system according to the first embodiment.

[0018] The wireless communication system according to the first embodiment comprises a network (NW) 1, a UE (User Equipment) 2, and an AIoT device 3. The wireless communication system according to the first embodiment may be a 5GS (5G System) or may be referred to as an AIoT system. NW1 may be a 5G network or a 6G network, but in the following description of the embodiments, the case where NW1 is a 5G network will be mainly assumed.

[0019] The elements that make up NW1 are called network nodes. Network nodes may be logically configured entities or physically configured entities. Hereafter, one network node will be assigned to each function, but one network node may implement multiple functions, or multiple network nodes may implement one function. Network nodes may also be called NFs (Network Functions). Note that the "connections" described below may be logical connections or physical connections.

[0020] NW1 comprises AF (Application Function) 11, CN (Core Network) 12, RAN (Radio Access Network) 13, and OAM (Operations, Administration and Maintenance) 14.

[0021] AF11 is a network node with the functionality to control applications. AF11 is connected to CN12. AF11 may also be an external node located outside of CN12, such as an external application server. AF11 utilizes the AIoT services provided by CN12.

[0022] CN12 is the network portion that provides functions such as connectivity between subscribers and external networks, management of network resources, mobility management, security, and billing. CN12 may also be a 5GC (5G Core Network). Network nodes included in CN12 may be referred to as CN nodes.

[0023] In the first embodiment, CN12 includes NEF (Network Exposure Function) 12a, AIoT function (AIoTF) 12b, UDM (Unified Data Management) 12c, UDR (User Data Repository) 12d, and AMF (Access and Mobility Management Function) 12e.

[0024] NEF12a is a network node that provides authorized AF11s with a means to access CN12. NEF12a mediates communication between AF11s and CN nodes (e.g., AIoTF12b). However, CN12 does not necessarily have to have an NEF12a. For example, if AIoTF12b also performs authentication for AF11s, communication between AF11s and AIoTF12b may occur without going through NEF12a.

[0025] AIoTF12b is a network node that provides functions for managing and controlling AIoT services using AIoT device 3. AIoTF12b may be integrated with AMF12e. Such AMF12e may be an AMF dedicated to AIoT services. Alternatively, AIoTF12b may be a separate network node from AMF12e and communicate with RAN13 via AMF12e. AIoTF12b communicates regarding AIoT services with a reader device, which is a device that performs wireless communication with AIoT device 3. The reader device is either base station 13a or UE2.

[0026] UDM12c is a network node that provides the functionality to manage the data stored by UDR12d. UDM12c provides data stored by UDR12d, and adds, updates, or deletes data stored by UDR12d in response to requests from other network nodes.

[0027] UDR12d is a network node that provides the function of storing subscriber data related to UE2. UDR12d stores subscriber data, such as subscriber profiles and subscriber status. UDR12d provides, updates, or deletes stored data in response to requests from other network nodes. In the first embodiment, UDR12d may also have the function of storing data related to AIoT device 3. UDR12d may be an existing UDR with the function of storing data related to AIoT device 3 added. Alternatively, UDR12d may be an AIoT-dedicated UDR that specializes in storing data related to AIoT device 3.

[0028] The AMF12e is a network node that has functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and terminal mobility management.

[0029] RAN13 is the network component that provides wireless communication to UE2 and AIoT device 3. RAN13 manages and allocates wireless resources and communicates wirelessly with UE2 and AIoT device 3 via a wireless interface. RAN13 may also be an NG-RAN (Next Generation-Radio Access Network). Network nodes included in RAN13 may be referred to as RAN nodes.

[0030] RAN13 has multiple base stations 13a and 13b. In the example in Figure 1, RAN13 has a base station 13a that operates as a reader device and a base station 13b that performs wireless communication with a UE2 that also operates as a reader device. A reader device is a device capable of performing wireless communication with an AIoT device 3. Base station 13a performs wireless communication with AIoT device 3a. UE2 performs wireless communication with AIoT device 3b. Base station 13a that operates as a reader device is referred to as a RAN reader, and UE2 that operates as a reader device is referred to as a UE reader. The air interface between the reader device and the AIoT device 3 is referred to as an AIoT air interface. In the first embodiment, RAN13 may be an AIoT-dedicated RAN specialized for AIoT services.

[0031] OAM14 is a network node that has the functions of operating, managing, and maintaining NW1. For example, CN12 and RAN13 are networks belonging to a certain telecommunications carrier (also referred to as the "operator"), and OAM14 is also a network node belonging to that telecommunications carrier.

[0032] UE2 is a terminal such as a smartphone, mobile phone, tablet, wearable device, or communication module. The UE2, which is a reader device, may be a terminal dedicated to being a reader device. In the first embodiment, UE2 performs wireless communication with the base station 13b and wireless communication with the AIoT device 3b.

[0033] AIoT device 3 is an energy harvesting-enabled device. AIoT device 3 may be powered by energy harvesting. AIoT device 3 may be battery-less or have limited energy storage capacity (e.g., a capacitor) and may be powered by harvesting radio waves, light, motion, heat, or any other suitable power source. AIoT device 3 may be less complex, smaller, less powerful, and consume less power compared to IoT devices already introduced in 3GPP standards, such as NB-IoT devices and eMTC devices. AIoT device 3 may be maintenance-free and may have a long lifespan (e.g., more than 10 years). AIoT device 3 may be installed to blend into the surrounding environment.

[0034] For example, one use case for AIoT device 3 is inventory management. In this use case, it is expected that the status of goods and materials will be understood in real time based on identification information (also called "device ID"), status information (which may include location information), and / or measured values ​​(sensor information) transmitted by AIoT device 3 in the warehouse. The "inventory" function in the AIoT service is used for such inventory management. Inventory is a function that manages AIoT device 3.

[0035] Furthermore, while the following three categories ("A" to "C") have been considered for the AIoT device 3, the AIoT device 3 according to the first embodiment may belong to any of these categories.

[0036] Device "A": It lacks energy storage capabilities and independent signal generation / amplification functions. In other words, it uses backscatter RF (Radio Frequency) transmission. In backscatter transmission, AIoT device 3 transmits information to the reader device by reflecting the radio waves received from the reader device and changing the reflection pattern of the radio waves.

[0037] Device "B": It has an energy storage function, but no independent signal generation function. In other words, it is RF transmission using backscatter. The stored energy can be used to amplify the reflected signal.

[0038] Device "C": It has energy storage capabilities and independent signal generation capabilities. In other words, it has an active RF component for transmission, enabling active transmission rather than RF reflection.

[0039] Furthermore, the operation of communicating with AIoT device 3 is referred to as "AIoT operation." Examples of AIoT operations include the following "inventory" and "command."

[0040] Inventory: The inventory allows for the extraction and / or discovery of one or more AIoT devices 3. Furthermore, the inventory can detect AIoT devices 3 present around the reader device and collect their information. Unlike UE2, AIoT devices 3 are not always connected to NW1. Using the inventory function, NW1 can acquire information about AIoT devices 3 (device ID, status, measured values, etc.) at the necessary time.

[0041] Inventory is performed using the following steps, for example: 1) to 4).

[0042] 1) Trigger: CN12 instructs the reader device to start the inventory.

[0043] 2) Broadcasting of paging messages by the reader device: The reader device broadcasts a paging message containing information (device ID) to identify the AIoT device 3 to be inventoryed. Such a paging message may be referred to as a broadcast message, inventory request, or inventory message.

[0044] 3) Response from AIoT device 3: AIoT device 3 that matches the broadcasted identification information (device ID) responds to the reader device, for example, through random access.

[0045] 4) Information gathering: The reader device collects the necessary information from the responding AIoT device 3 and provides the collected information to CN12.

[0046] Such an inventory can enable the detection and identification of devices. For example, it can determine what devices are present in an area and identify each device. Furthermore, the inventory can enable monitoring of device status (e.g., operating status, battery level, etc.) and collection of data (e.g., sensing data, etc.).

[0047] ·command: Commands can be used to read, write to, control, disable, and / or enable one or more AIoT devices 3. Examples of commands include the Read command for reading and the Write command for writing.

[0048] Furthermore, in addition to "inventory" and "commands," AIoT operations may also include "device selection." Device selection allows for the selection of the appropriate AIoT device 3 to perform a specific task when a large number of AIoT devices 3 exist. The aforementioned paging messages may also be used in device selection.

[0049] The identifier (device ID) of AIoT device 3 can be any information that uniquely identifies AIoT device 3, such as an EPC (Electronic Product Code), MAC address, or serial number. Such a device ID is a unique identifier (i.e., a fixed identifier) ​​for AIoT device 3 and is called a permanent identifier. If AIoT device 3 can implement a SIM (Subscriber Identity Module) card or eSIM, the device ID of AIoT device 3 may be a SUCI (Subscriber Concealed Identifier) / SUPI (Subscription Permanent Identifier).

[0050] Furthermore, as mentioned above, there are two topologies (Topology 1 and Topology 2) for the connection between AIoT device 3 and NW1.

[0051] In the Topology 1 architecture, the AIoT device 3a is connected to CN12 via a base station 13a, which is a RAN node. The base station 13a is an AIoT-enabled base station that supports the AIoT air interface, and may be, for example, an AIoT-specific base station (AIoT-specific gNB). In other words, in Topology 1, the base station 13a functions as a leader device.

[0052] In the Topology 2 architecture, the AIoT device 3b is connected to CN12 via UE2 and base station 13b. UE2 is an AIoT-enabled UE that supports the AIoT air interface. In other words, in Topology 2, UE2 functions as a leader device.

[0053] In architectures 1 and 2, the interface of AIoT device 3 is the same. AIoT device 3 is a small device, such as an IC tag in RFID (Radio Frequency Identification), and does not necessarily have to be able to accommodate a UICC (Universal Integrated Circuit Card), such as a USIM (Universal Subscriber Identity Module) and / or a SIM (Subscriber Identity Module). Furthermore, AIoT device 3 may be a simple device that does not implement an eSIM.

[0054] In the following description of the embodiments, we primarily assume the architecture of Topology 1, but the architecture of Topology 2 may also be used.

[0055] (1.2) System operation example Figure 2 is a diagram illustrating the problems in inventory operation.

[0056] Considering the outdoor use of AIoT device 3, extending the communication range of the AIoT air interface is being considered. For example, if outdoor use of AIoT device 3 is anticipated, the communication range of the AIoT air interface needs to be wider compared to when only indoor use of AIoT device 3 is anticipated.

[0057] In the example shown in Figure 2, AIoT device 3#1 is located at facility #1, and AIoT device 3#2 is located at facility #2. Facility #1 and facility #2 are facilities owned by different owners (different operators). For example, facility #1 may be a store or its warehouse. Facility #2 may be another store or its warehouse. Facility #1 and facility #2 may be located in close proximity to each other. Facility #1 and facility #2 may be located within the communication range of a single reader device (base station 13a or UE2).

[0058] AIoT device 3#1 is attached to product Z#1, and AIoT device 3#2 is attached to product Z#2. Products Z#1 and Z#2 are assumed to be the same type of product Z. The term "product" may be used interchangeably with the term "item."

[0059] Here, "the AIoT device is attached to the product" means that the AIoT device 3 is attached to the product directly or indirectly. Direct attachment of the AIoT device 3 to the product means that the AIoT device 3 may be incorporated into the product or attached to the product. Indirect attachment of the AIoT device 3 to the product means that the AIoT device 3 may be attached to the product via a string or the like, or attached to the product's packaging.

[0060] Furthermore, each of AIoT device 3#1 and AIoT device 3#2 stores a persistent identifier as its own device ID. In other words, a persistent identifier is predefined for each of AIoT device 3#1 and AIoT device 3#2. In the example in Figure 2, the persistent identifier is the EPC (Electronic Product Code) or a similar identifier. Note that the term "identifier" can be used interchangeably with the terms "ID," "code," or "number."

[0061] A persistent identifier may include, for example, a producer ID, a product ID, and a serial number. Here, we show an example where a persistent identifier includes three parts (three fields), but it is not limited to this. For example, a persistent identifier may also include additional information such as a check digit. The producer ID is an identifier used to identify the business that produced the goods, and is also called the business code. The product ID is an identifier used to identify the type of goods, and is also called the product item code. The serial number is an identifier used to identify individual goods within a given type of goods.

[0062] In the example in Figure 2, the persistent identifier stored by AIoT device 3#1 is producer ID=X, product ID=Z, and serial number=1, which means it is the first product Z produced by producer X. On the other hand, the persistent identifier stored by AIoT device 3#2 is producer ID=X, product ID=Z, and serial number=2, which means it is the second product Z produced by producer X.

[0063] Under these circumstances, we assume a scenario in which the owner of facility #1 performs inventory management of product Z within facility #1 using AF11.

[0064] In this case, firstly, AF11 sends an inventory request message to CN12 that includes "Producer ID=X and Product ID=Z" as a mask. Here, "mask" refers to the conditions (i.e., filtering conditions) that the AIoT device 3 must satisfy to respond to the inventory request (paging).

[0065] Secondly, CN12 selects a reader device (base station 13a or UE2) in response to an inventory request message from AF11, and sends an inventory request message to the selected reader device that includes "Producer ID=X and Product ID=Z" as a mask. The inventory request message is an example of a paging message.

[0066] Thirdly, the reader device (base station 13a or UE2) broadcasts an inventory request message (paging message) that includes "producer ID=X and product ID=Z" as a mask, in response to the inventory request message from CN12.

[0067] Fourth, AIoT device 3#1 located at facility #1 receives an inventory request message from the reader device and determines that the mask of persistent identifiers (producer ID=X and product ID=Z) contained in the received inventory request message matches the persistent identifiers it has stored (in this case, producer ID and product ID). In this case, AIoT device 3#1 responds to the inventory request message. Specifically, AIoT device 3#1 sends an inventory response message (paging response message) to the reader device.

[0068] Additionally, AIoT device 3#2, located in facility #2, also receives an inventory request message from the reader device. AIoT device 3#2 determines that the mask of persistent identifiers included in the received inventory request (producer ID=X and product ID=Z) matches the persistent identifiers it has stored (in this case, producer ID and product ID), and sends an inventory response message to the reader device.

[0069] As a result, in a scenario where inventory management of product Z within facility #1 is desired, not only AIoT device 3#1 attached to product Z#1 within facility #1, but also AIoT device 3#2 attached to product Z#2 within facility #2 will respond to the inventory request message. Therefore, inventory management of product Z within facility #1 becomes inaccurate. Consequently, the owner of facility #1 will have an inaccurate understanding of the remaining stock of product Z in facility #1. This problem can be particularly noticeable when facility #1 and facility #2 are within the communication range (specifically, within the paging range) of the reader device.

[0070] As described above, in the AIoT technology currently under consideration, the AIoT device 3 is called (paging) from the NW1 side using a persistent identifier (i.e., a fixed identifier) ​​that is unique to the AIoT device 3. However, paging using persistent identifiers leads to the problems described above. In particular, because the persistent identifier is a fixed identifier, it is difficult to reflect the current owner (facility #1 or facility #2 in the example in Figure 2) in the persistent identifier. Therefore, it is not possible to perform advanced paging that specifies the owner. If it were possible to paging that specifies the owner, in the example in Figure 2, it would be possible to call only the AIoT device 3 within facility #1.

[0071] Figure 3 is a diagram illustrating the overview of the inventory operation according to the first embodiment.

[0072] In the first embodiment, advanced paging is enabled, such as by specifying the owner. Note that the operation according to the first embodiment is not limited to inventory and may be applied to device selection. The term "owner" may be used interchangeably with the terms "facility," "operator," or "third party." Here, "third party" may mean an operator other than a telecommunications carrier (operator).

[0073] In the first embodiment, a new group ID is introduced that indicates the owner to which the product to which the AIoT device 3 is attached belongs. The group ID may be an identifier that indicates the owner to which the AIoT device 3 belongs, for example, the current owner of the AIoT device 3. In addition to owner information (owner ID), the group ID may include optional information. Any information can be set as optional information, but optional information may be, for example, information on the arrival date of the product. Here, an example is shown in which the group ID includes two parts (two fields), but it is not limited to this. In the following embodiments, an example in which the owner ID of the group ID is used as a mask will be mainly described, but optional information may also be used as a mask.

[0074] Each AIoT device 3 stores a group ID in addition to a persistent identifier similar to that in Figure 2. In the example in Figure 2, AIoT device 3#1 stores a group ID that includes "Owner ID=1" corresponding to facility #1. On the other hand, AIoT device 3#2 stores a group ID that includes "Owner ID=2" corresponding to facility #2. Thus, each AIoT device 3 is set with a group ID in addition to a persistent identifier as information to identify the owner. The group ID may be a non-persistent identifier, i.e., an updatable (mutable) identifier or a temporary identifier.

[0075] While a persistent identifier is an identifier set at the time of manufacture or shipment of AIoT device 3 (or product), a group ID may be an identifier set after shipment of AIoT device 3 (or product). In other words, a group ID may be an identifier set on AIoT device 3 at a later time than when a persistent identifier is set on AIoT device 3. In this case, the group ID may be a fixed identifier rather than an updatable (variable) identifier. A group ID may be set on AIoT device 3 by a business operator (third party) using AIoT device 3. Here, the expression "a group ID is set on AIoT device 3" can be used interchangeably with the expression "a group ID is written to AIoT device 3".

[0076] In addition to paging AIoT devices 3 using persistent identifiers, or as an alternative to paging AIoT devices 3 using persistent identifiers, NW1 can also paging AIoT devices 3 using group IDs. For example, by masking paging with group IDs, NW1 can ensure that only AIoT devices 3 belonging to a specific group ID respond to paging.

[0077] Each AIoT device 3 can receive a paging message containing a group ID from a reader device (base station 13a or UE2). Each AIoT device 3 determines whether the group ID contained in the received paging message matches its own group ID that it has stored in advance. If the group ID contained in the received paging message matches its own group ID that it has stored in advance, each AIoT device 3 sends a paging response to the reader device.

[0078] Therefore, according to the first embodiment, by enabling paging using group IDs, advanced paging such as specifying the owner can be realized.

[0079] Referring to Figure 3, the inventory operation according to the first embodiment will be described. Here, we assume a scenario similar to that in Figure 2, specifically, a scenario in which the owner of facility #1 performs inventory of product Z using AF11 in order to manage the inventory of product Z within facility #1.

[0080] In this case, firstly, AF11 sends an inventory request message to CN12 that includes "Producer ID=X and Product ID=Z" as a mask for persistent identifiers, and "Owner ID=1" as a mask for group IDs.

[0081] Secondly, in response to the inventory request message from AF11, CN12 selects a reader device (base station 13a or UE2) and sends an inventory request message (paging message) to the selected reader device that includes "Producer ID=X and Product ID=Z" as a persistent identifier mask and "Owner ID=1" as a group ID mask.

[0082] Thirdly, the reader device (base station 13a or UE2) broadcasts an inventory request message (paging message) in response to an inventory request message from CN12, which includes "Producer ID=X and Product ID=Z" as a persistent identifier mask and "Owner ID=1" as a group ID mask.

[0083] Fourth, AIoT device 3#1 located at facility #1 receives an inventory request message from the reader device and determines that the mask of persistent identifiers (producer ID=X and product ID=Z) included in the received inventory request message matches the persistent identifiers it has stored (in this case, producer ID and product ID). AIoT device 3#1 also determines that the mask of group IDs (owner ID=1) included in the received inventory request message matches the group ID it has stored (in this case, owner ID). In this case, AIoT device 3#1 responds to the inventory request message. Specifically, AIoT device 3#1 sends an inventory response message (paging response message) to the reader device.

[0084] Additionally, AIoT device 3#2, located in facility #2, also receives an inventory request message from the reader device. AIoT device 3#2 determines that the persistent identifier mask (producer ID=X and product ID=Z) included in the received inventory request matches the persistent identifiers it stores (in this case, producer ID and product ID). However, AIoT device 3#2 determines that the group ID mask (owner ID=1) included in the received inventory request message does not match the group ID it stores (in this case, owner ID). In this case, AIoT device 3#2 does not respond to the inventory request message. Specifically, AIoT device 3#2 does not send an inventory response message (paging response message) to the reader device.

[0085] As a result, in a scenario where inventory management of product Z within facility #1 is desired, only AIoT device 3#1 attached to product Z#1 within facility #1 will respond to inventory request messages, while AIoT device 3#2 attached to product Z#2 within facility #2 will not respond to inventory request messages. Therefore, inventory management of product Z within facility #1 becomes accurate. Consequently, the owner of facility #1 can accurately know the number of product Z remaining in facility #1.

[0086] In the example shown in Figure 3, paging using both a persistent identifier and a group ID was explained, but paging can also be performed using only a group ID without a persistent identifier.

[0087] Figure 4 is a diagram illustrating the operation of the comparative example. In the comparative example, the owner ID is included in the persistent identifier, and the group ID is not used. When the owner ID is included in the persistent identifier, the following problems may arise.

[0088] In the example in Figure 4, firstly, producer (X) produces products Z#1 and Z#2, attaching AIoT device 3#1 to product Z#1 and AIoT device 3#2 to product Z#2. Then, producer (X) transfers (sells) product Z with AIoT devices 3 attached to wholesaler (A). Here, the persistent identifiers of AIoT device 3#1 and AIoT device 3#2 are set to "Owner ID=A". In other words, wholesaler (A) is set as the owner.

[0089] Secondly, wholesaler (A) transfers (sells) product Z#1, which is attached to AIoT device 3#1, to facility (seller) #1, and transfers (sells) product Z#2, which is attached to AIoT device 3#2, to facility (seller) #2. At this point, the owner of product Z#1 changes to facility (seller) #1, and the owner of product Z#2 changes to facility (seller) #2. However, since persistent identifiers are non-updatable identifiers, the persistent identifiers of AIoT device 3#1 and AIoT device 3#2 remain set to "Owner ID=A".

[0090] As a result, the owner ID stored in each AIoT device 3 no longer matches the current owner. Therefore, including the owner ID in the persistent identifier leads to the same problem as in Figure 2. Thus, the comparative example in which the owner ID is included in the persistent identifier has the problem of not being able to handle changes in ownership during the distribution process of the product. In contrast, the first embodiment solves this problem by newly introducing the group ID as described above as an independent identifier separate from the persistent identifier.

[0091] (1.3) Example of device configuration An example of the apparatus configuration according to the first embodiment will be described.

[0092] (1.3.1) Example of AIoT device configuration Figure 5 shows an example of the functional configuration of the AIoT device 3 according to the first embodiment. However, the configuration shown in Figure 5 may be just one example of the hardware configuration of the AIoT device 3.

[0093] The AIoT device 3 includes a transmitting / receiving unit 31, a storage unit 32, and a control unit 33. This functional configuration (functional block) is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operation according to the first embodiment. The AIoT device 3 may further include a battery for realizing an energy storage function.

[0094] The transceiver 31 performs wireless communication with the reader device (base station 13a or UE2). The transceiver 31 may perform RF transmission by backscatter, or it may be capable of active transmission instead of RF reflection. The transceiver 31 has a transmitting unit 31a and a receiving unit 31b. The transmitting unit 31a includes the function of generating a signal to be transmitted to the reader device and transmitting the signal wirelessly. The receiving unit 31b includes the function of receiving various signals transmitted from the reader device and obtaining information from the received signal, for example, from a higher layer. The signal transmitted from the reader device to the AIoT device 3 may be called an "R2D signal". The signal transmitted from the AIoT device 3 to the reader device may be called a "D2R signal".

[0095] The storage unit 32 includes a memory device, which stores pre-configured setting information and the like in the memory device and reads it from the memory device as needed. The storage unit 32 has a persistent identifier storage area 32a for storing persistent identifiers and a group ID storage area 32b for storing group IDs (first group IDs). The persistent identifier storage area 32a and the group ID storage area 32b may be provided in the same memory or in different memories. The memory is preferably a non-volatile memory. The group ID storage area 32b is provided in a writable (rewritable) memory.

[0096] The control unit 33 performs processing to control the above-mentioned operations and the operations described later in the AIoT device 3. The signal transmission function of the control unit 33 may be included in the transmission unit 31a, and the signal reception function of the control unit 33 may be included in the reception unit 31b.

[0097] In the AIoT device 3 configured in this way, the storage unit 32 (group ID storage area 32b) stores a first group ID that indicates the owner to which the AIoT device 3 belongs or the owner to which the item to which the AIoT device 3 is attached belongs. The receiving unit 31b receives a paging message containing a second group ID from the reader device (base station 13a or UE2). The paging message is an example of an R2D signal and may be, for example, an inventory request message. The control unit 33 determines whether the second group ID matches the first group ID. For example, the control unit 33 determines whether the mask of the second group ID included in the received paging message (e.g., owner ID) matches the first group ID (e.g., owner ID) that it stores. The transmitting unit 31a, in response to the determination that the second group ID matches the first group ID, transmits a paging response to the reader device (base station 13a or UE2). The paging response is an example of a D2R signal and may be, for example, an inventory response message. This enables paging using group IDs, allowing for advanced paging that can specify the owner.

[0098] In the first embodiment, the storage unit 32 (persistent identifier storage area 32a) stores a first persistent identifier, which is an identifier unique to the AIoT device 3. The receiving unit 31b may receive a paging message containing a second persistent identifier and a second group ID from a reader device (base station 13a or UE2). The control unit 33 may determine whether the second persistent identifier matches the first persistent identifier. For example, the control unit 33 determines whether the mask of the second persistent identifier contained in the received paging message matches the first persistent identifier it stores. The transmitting unit 31a may transmit a paging response to the reader device (base station 13a or UE2) depending on whether the second persistent identifier matches the first persistent identifier and the second group ID matches the first group ID. This enables paging using both the group ID and the persistent identifier, making advanced paging possible.

[0099] (1.3.2) Example of a communication device configuration for paging Figure 6 shows an example of the functional configuration of a communication device that performs paging according to the first embodiment. However, the configuration shown in Figure 6 may be just one example of the hardware configuration of the communication device.

[0100] In topology 1, the communication device that directly performs paging to AIoT device 3 may be base station 13a. In topology 2, the communication device that directly performs paging to AIoT device 3 may be UE2. Regardless of topology 1 and 2, the communication device that indirectly performs paging to AIoT device 3 may be AIoTF12b. Other network nodes (e.g., UDM12c and UDR12d) have a configuration similar to that shown in Figure 6.

[0101] The communication device shown in Figure 6 (base station 13a, UE2, AIoTF12b) has a transmitting / receiving unit 41, a storage unit 42, and a control unit 43. Such a functional configuration (functional block) is merely an example. Any functional classification and functional unit name is acceptable as long as it enables the operation according to the first embodiment.

[0102] The transmitting / receiving unit 41 performs wireless communication with other communication devices. The transmitting / receiving unit 41 has a transmitting unit 41a and a receiving unit 41b. The transmitting unit 41a includes the function of generating a signal to be transmitted to other communication devices and transmitting the signal wirelessly or via wire. The receiving unit 41b includes the function of receiving various signals transmitted from other communication devices and obtaining information from the received signals, for example, information of a higher layer.

[0103] The memory unit 42 includes a storage device, which stores pre-configured setting information and the like in the storage device, and reads it from the storage device as needed.

[0104] The control unit 43 performs processing to control the above-mentioned operations and the operations described later in the communication device. The signal transmission function unit of the control unit 43 may be included in the transmission unit 41a, and the signal reception function unit of the control unit 43 may be included in the reception unit 41b.

[0105] In the communication device configured in this way, the receiving unit 41b receives a paging request from an external device (another communication device) that includes a group ID indicating the owner to which the AIoT device 3 belongs or the owner to which the item to which the AIoT device 3 is attached belongs. The paging request may be, for example, an inventory request message from the external device. In response to receiving the paging request, the transmitting unit 31a transmits a paging message including the group ID to the AIoT device 3 or the reader device.

[0106] The receiving unit 41b may receive a paging request from an external device (another communication device) that includes the persistent identifier and group ID of the AIoT device 3. In response to receiving the paging request, the transmitting unit 31a may transmit a paging message containing the persistent identifier and group ID to the AIoT device 3 or the reader device.

[0107] (1.4) Examples Based on the system configuration example and system operation example of the first embodiment described above, an embodiment of the first embodiment will be described.

[0108] (1.4.1) Operation Sequence Figure 7 shows an example of the operation sequence according to the first embodiment. This operation sequence corresponds to an example of the inventory operation according to the embodiment described above.

[0109] In step S101, NF11 sends an AIoT service request message to NEF12a requesting AIoT services. NEF12a receives the AIoT service request message.

[0110] The AIoT service request message includes the following parameters: an Ambient IoT device mask indicating the field to be used as the mask for the persistent identifier; an Ambient IoT device identifier containing the field to be used as the mask; a group ID mask indicating the field to be used as the mask for the group ID; a group ID containing the field to be used as the mask; a service operation indicating that it is an inventory item; and an AF identifier identifying AF11. Note that the AF identifier does not necessarily have to be assigned at this point.

[0111] The Ambient IoT device mask indicates which fields (parts) within the persistent identifier need to be matched. The group ID mask also indicates which fields (parts) within the persistent identifier need to be matched. Note that if the group ID consists only of the owner ID, the group ID mask may not be necessary.

[0112] In step S102, NEF12a verifies (i.e., authenticates) the legitimacy of AF11 and then forwards the AIoT service request message received in step S101 to AIoTF12b. AIoTF12b receives the AIoT service request message. Such an AIoT service request message is an example of a paging request. NEF12a may also add an AF identifier (AF ID) to the AIoT service request message before forwarding it to AIoTF12b.

[0113] In step S103, AIoTF12b begins verifying (authentication) whether AF11 is authorized to use the group ID in the AIoT service request message received in step S102.

[0114] Specifically, AIoTF12b sends a Nudm_SDM_GET Request message to UDM12c. UDM12c receives the Nudm_SDM_GET Request message. Nudm_SDM_GET Request is one of the SDM (Subscriber Data Management) services provided by UDM12c. In this embodiment, the Nudm_SDM_GET Request message includes the group ID and AF ID from the AIoT service request message received in step S102.

[0115] UDM12c determines (authenticates) whether AF11, indicated by the AF ID in the Nudm_SDM_GET Request message, is authorized to use the group ID in the Nudm_SDM_GET Request message. This prevents AF11 from accessing (in this case, inventory) groups it is not authorized to access.

[0116] In step S104, UDM12c sends a Nudm_SDM_GET Response message to AIoTF12b. AIoTF12b receives the Nudm_SDM_GET Response message. The Nudm_SDM_GET Response message contains information indicating the authentication result in UDM12c, such as authorized (yes / no). Here, we will proceed assuming that the authentication was successful (yes).

[0117] In step S105, AIoTF12b selects a reader device (base station 13a or UE2). For example, AIoTF12b may select a reader device that covers the call range primarily based on its location.

[0118] In step S106, AIoTF12b sends an inventory request message to the reader device selected in step S105. The reader device receives the inventory request message. The inventory request message is an example of a paging message. The inventory request message is an example of a paging request for the reader device.

[0119] If the reader device is base station 13a, the inventory request message may be a message on the NG interface, which is the interface between RAN13 and CN12. On the other hand, if the reader device is UE2, the inventory request message may be a message on NAS (Non-Access Stratum).

[0120] The inventory request message includes the following parameters: an Ambient IoT device mask, which indicates the field to be used as the mask for the persistent identifier; an Ambient IoT device identifier, which contains the field to be used as the mask; a group ID mask, which indicates the field to be used as the mask for the group ID; and a group ID, which contains the field to be used as the mask.

[0121] In step S107, the reader device broadcasts an AIoT paging message. AIoT device 3 receives the AIoT paging message.

[0122] An AIoT paging message includes the following parameters: an Ambient IoT device mask, which indicates the field to be used as a mask for the persistent identifier; an Ambient IoT device identifier, which contains the field to be used as a mask; a group ID mask, which indicates the field to be used as a mask for the group ID; and a group ID, which contains the field to be used as a mask.

[0123] The AIoT paging message may include information indicating that the AIoT device 3 must consider the group ID mask before responding. This information may be a single-bit flag. This information may be referred to as the group ID matching bit.

[0124] Here, we will proceed with the assumption that the persistent identifier mask field matches the persistent identifier field of AIoT device 3, and the group ID mask field matches the group ID field of AIoT device 3.

[0125] In step S108, AIoT device 3 sends an AIoT inventory response message to the reader device. The reader device receives the AIoT inventory response message. The AIoT inventory response message is an example of a paging response. The AIoT inventory response message may also be referred to as an AIoT NAS Inventory Response message. The AIoT inventory response message includes the persistent identifier of AIoT device 3.

[0126] In step S109, the reader device forwards the AIoT inventory response message received in step S108 to AIoTF12b. AIoTF12b receives the AIoT inventory response message.

[0127] In step S110, AIoTF12b sends an AIoT service response message to NEF12a. NEF12a receives the AIoT service response message. The AIoT service response message includes the persistent identifier of AIoT device 3.

[0128] In step S111, NEF12a forwards the AIoT service response message received in step S110 to AF11. AF11 receives the AIoT service response message.

[0129] (1.4.2) Information stored by UDM Figure 8 shows an example of the information stored by the UDM12c according to the first embodiment.

[0130] As described above, UDM12c determines (authenticates) whether the group that AF11 attempts to access (specifically, the inventory) is authorized to do so. To perform such authentication, UDM12c may store and manage an AF profile for each AF11, as shown in Figure 8. The AF profile may be called an AF subscription. The AF profile may be stored in UDM12 by, for example, OAM14.

[0131] An AF profile includes a set of AF IDs that identify the corresponding AF11 and group IDs that identify the group. Multiple group IDs may be associated with a single AF profile. Each group ID is associated with "Authorization true / false," which indicates whether the AF11 is allowed to access the group.

[0132] In the example sequence shown in Figure 7, in step S103, UDM12c receives a Nudm_SDM_GET Request message from AIoTF12b. UDM12c identifies an AF profile that matches the group ID and AF ID in the Nudm_SDM_GET Request message, and verifies whether the group ID in the identified AF profile is "Authorization true / false".

[0133] If Authorization is true, in step S104, UDM12c sends a Nudm_SDM_GET Response message to AIoTF12b containing authorized (yes) as the authentication result. On the other hand, if Authorization is false, in step S104, UDM12c sends a Nudm_SDM_GET Response message to AIoTF12b containing authorized (no) as the authentication result.

[0134] Although Figure 8 describes a configuration in which the AF profile is stored and managed by the UDM12c, a configuration in which the AF profile is stored and managed by the UDR12d or AIoTF12b is also possible.

[0135] (1.4.3) Paging Messages Figure 9 shows an example of a paging message according to the first embodiment. The paging message shown in Figure 9 corresponds to the AIoT paging message sent from the reader device to the AIoT device 3 in step S107 of Figure 7.

[0136] In this embodiment, the paging message includes a Group ID matching bit 51, a Permanent Ambient IoT device identifier mask 52, a Permanent Ambient IoT device identifier 53, a Group ID mask 54, and a Group ID 55.

[0137] The group ID matching bit 51 is information indicating that the AIoT device 3 must consider the group ID mask 54 before responding. When the AIoT device 3 receives a paging message, if the received paging message contains the group ID matching bit 51, it will consider (verify) the group ID mask 54. On the other hand, if the received paging message does not contain the group ID matching bit 51, the AIoT device 3 does not need to consider (verify) the group ID mask 54.

[0138] The persistent identifier mask 52 is information indicating the fields to be used as a mask for the persistent identifier 53. In this embodiment, the persistent identifier 53 may include four fields 531 to 534. Field 534 may be further divided into multiple fields. The persistent identifier mask 52 indicates the fields among these fields that the AIoT device 3 should match with its own persistent identifier.

[0139] The persistent identifier 53 is a persistent identifier that includes fields used as a mask. The persistent identifier 53 may be a partial persistent identifier containing only the fields used as a mask, or it may be a full persistent identifier. In this embodiment, the persistent identifier 53 may include a field 531 indicating the assignor of the persistent identifier, a field 532 for the network identifier, a field 533 for the third-party identifier, and a field 534 for EPC and other information. The network identifier may be a combination of MCC (Mobile Country Code) and MNC (Mobile Network Code), and / or NID (Network Identifier).

[0140] The group ID mask 54 is information that indicates the field to be used as the mask for the group ID.

[0141] Group ID 55 is a group ID that includes the field used as a mask. Group ID 55 may be a partial group ID containing only the field used as a mask, or it may be a complete group ID.

[0142] (1.4.4) Operation flow of AIoT devices Figure 10 shows an example of the operation flow of the AIoT device 3 according to the first embodiment.

[0143] In step S151, the AIoT device 3 receives a paging message from the reader device.

[0144] In step S152, the AIoT device 3 checks whether the received paging message contains a group ID mask. For example, the AIoT device 3 may perform this check using the group ID matching bit 51 shown in Figure 9. If there is no group ID mask (step S152: NO), the AIoT device 3 proceeds to step S154.

[0145] On the other hand, if there is a mask for the group ID (step S152: YES), in step S153, AIoT device 3 checks whether the group ID specified in the paging message matches the group ID of its own device. For example, AIoT device 3 checks whether the field of the group ID specified as the group ID mask in the paging message matches the corresponding field of the group ID of its own device.

[0146] If the group ID specified in the paging message does not match the group ID of the local device (step S153: NO), in step S155, AIoT device 3 decides not to respond to the paging message. On the other hand, if the group ID specified in the paging message matches the group ID of the local device (step S153: YES), AIoT device 3 proceeds to step S154.

[0147] In step S154, AIoT device 3 checks whether the persistent identifier specified in the paging message matches the persistent identifier of its own device. For example, AIoT device 3 checks whether the field of the persistent identifier specified as the persistent identifier mask in the paging message matches the corresponding field of the persistent identifier of its own device.

[0148] If the persistent identifier specified in the paging message does not match the persistent identifier of the local device (step S154: NO), in step S155, AIoT device 3 decides not to respond to the paging message. On the other hand, if the persistent identifier specified in the paging message matches the persistent identifier of the local device (step S154: YES), in step S156, AIoT device 3 decides to respond to the paging message and sends a paging response to the reader device.

[0149] In this embodiment, an example was described in which the AIoT device 3 performs a persistent identifier match check after performing a group ID match check. However, the AIoT device 3 may also reverse these steps, performing a persistent identifier match check first and then a group ID match check.

[0150] (2) Second Embodiment The second embodiment will be described primarily in terms of its differences from the first embodiment. The second embodiment may be an embodiment based on the first embodiment. In the second embodiment, the configuration and operation that enable NW1 to assign a group ID to AIoT device 3 will be described.

[0151] (2.1) Example System Configuration Figure 11 shows an example of the configuration of a wireless communication system according to the second embodiment.

[0152] In the second embodiment, the UDR12d stores and manages the group ID of each AIoT device 3 as an AIoT device profile. Such storage and management of group IDs by the UDR12d may also be performed in the first embodiment.

[0153] CN12 further includes AIoT Data Management (AIoTDM) 12f. AIoTDM 12f is a network node that acts as a front-end for UDR 12d and provides an interface with other network nodes. AIoTDM 12c mediates communication between AIoTF 12b and UDR 12d. AIoTDM 12c may be a network node with similar functionality to UDR 12c.

[0154] However, CN12 does not necessarily have to have AIoTDM12c. For example, if UDR12d is a network node dedicated to AIoT services, communication between AIoTF12b and UDR12d may occur without going through AIoTDM12c.

[0155] (2.2) System operation example Figure 12 is a diagram illustrating the problems in the group ID according to the first embodiment.

[0156] As mentioned above, the group ID is an identifier that indicates the owner to which the product with AIoT device 3 attached belongs. However, after the group ID is set on AIoT device 3, the owner may change during the product's lifecycle.

[0157] In the example in Figure 12, AIoT device 3, which is attached to product Z#1, is located in the store. AIoT device 3 stores a persistent identifier as its own device ID, as well as a group ID that includes "Owner ID=1" corresponding to the store. For example, let's assume that product Z#1 is a food product.

[0158] Here, we consider a scenario where a customer purchases product Z#1 at a store and stores product Z#1 in their refrigerator at home. In this scenario, the customer becomes the owner of product Z#1 at the time of purchase, but AIoT device 3 holds a group ID that includes "Owner ID=1" corresponding to the store. In this case, it is difficult to use the inventory to, for example, check the refrigerator's stock. Therefore, it is desirable to be able to change the group ID stored in AIoT device 3 to the customer's ID.

[0159] Figure 13 is a diagram illustrating the overview of the group ID assignment operation according to the second embodiment.

[0160] In the second embodiment, a new command (also referred to as the "assignment command" or "group ID assignment command") is introduced that enables NEF12a to assign a group ID to AIoT device 3. AF11 can use this new command to assign a group ID to AIoT device 3. Furthermore, the profile information of AIoT device 3 stored in UDR12d is extended to include the group ID currently assigned to AIoT device 3.

[0161] In the example in Figure 13, firstly, AF11 sends a group ID assignment command to CN12 that includes the persistent identifier of AIoT device 3 and the group ID to be assigned to AIoT device 3 (in this case, owner ID=3 corresponding to the customer who purchased product Z#1).

[0162] Secondly, CN12 selects a leader device (base station 13a or UE2) in response to a group ID assignment command from AF11, and sends a group ID assignment command to the selected leader device, which includes the persistent identifier of the AIoT device 3 and the group ID (owner ID=3) to be assigned to the AIoT device 3.

[0163] Thirdly, the leader device (base station 13a or UE2) sends a group ID assignment command to the AIoT device 3 in response to the group ID assignment command from CN12, which includes the persistent identifier of the AIoT device 3 and the group ID to be assigned to the AIoT device 3 (owner ID=3).

[0164] Fourth, the AIoT device 3 located in the customer's refrigerator receives a group ID assignment command from the reader device and stores the group ID (owner ID=3) included in the received group ID assignment command. In the example in Figure 13, the group ID (owner ID=1) stored by the AIoT device 3 is overwritten, and the AIoT device 3 stores the new group ID (owner ID=3).

[0165] In this way, NW1 uses a group ID assignment command to change the group ID stored in AIoT device 3. As a result, even if the owner changes during the product lifecycle, the group ID can be updated to indicate the current owner.

[0166] Figure 13 illustrates the process by which the group ID stored in AIoT device 3 is changed. However, the group ID assignment command can also be used when assigning the first group ID to AIoT device 3, even if AIoT device 3 does not currently have a group ID stored in it.

[0167] Furthermore, Figure 13 illustrates a scenario in which the ownership of a product changes from a store to a customer. However, the scenario is not limited to this. For example, in the scenario of Figure 4, when the ownership of product Z#1 changes from wholesaler (A) to facility #1, NW1 may use a group ID assignment command to assign a group ID containing the owner ID corresponding to facility #1 to AIoT device 3#1. Similarly, in the scenario of Figure 4, when the ownership of product Z#2 changes from wholesaler (A) to facility #2, NW1 may use a group ID assignment command to assign a group ID containing the owner ID corresponding to facility #2 to AIoT device 3#2.

[0168] (2.3) Example of device configuration The following will primarily describe the differences between the apparatus configuration example of the second embodiment and the apparatus configuration example of the first embodiment.

[0169] (2.3.1) Example of AIoT device configuration Figure 14 shows an example of the functional configuration of the AIoT device 3 according to the second embodiment. However, the configuration shown in Figure 14 may be just one example of the hardware configuration of the AIoT device 3.

[0170] In the second embodiment, the group ID storage area 32b of the storage unit 32 is provided in writable (rewritable) memory. The address of the memory area constituting the group ID storage area 32b may be specified by a group ID assignment command.

[0171] In the second embodiment, the receiving unit 31b receives a group ID assignment command from the reader device (base station 13a or UE2) to assign a group ID to the AIoT device 3. The control unit 33 stores the group ID assigned by the group ID assignment command in the group ID storage area 32b of the storage unit 32. Specifically, if the group ID assignment command received by the receiving unit 31b contains the persistent identifier of its own device, the control unit 33 may determine that it is a group ID assignment command addressed to its own device and store the group ID included in the received group ID assignment command in the group ID storage area 32b of the storage unit 32.

[0172] If the group ID storage area 32b already stores a group ID, the control unit 33 updates (i.e., overwrites) the group ID storage area 32b with the group ID assigned by the group ID assignment command. As a result, it is prevented that multiple group IDs are stored in the group ID storage area 32b.

[0173] Alternatively, in a scenario where the AIoT device 3 may belong to multiple owners, multiple group IDs may be stored in the group ID storage area 32b. In this case, two types of group ID assignment commands may be defined: a command for "updating (changing)" a group ID and a command for "adding" a group ID. When the receiver 31b receives a command for "updating (changing)" a group ID, the control unit 33 may update (change) the group ID already stored in the group ID storage area 32b to the new group ID specified in the command. On the other hand, when the receiver 31b receives a command for "adding" a group ID, the control unit 33 may store the new group ID specified in the command in the group ID storage area 32b while retaining the group ID already stored in the group ID storage area 32b.

[0174] (2.3.2) Example of a communication device configuration for assigning group IDs Figure 15 shows an example of the functional configuration of a communication device that performs group ID assignment according to the second embodiment. However, the configuration shown in Figure 15 may be just one example of the hardware configuration of the communication device.

[0175] In topology 1, the communication device that directly assigns a group ID to the AIoT device 3 may be the base station 13a. In topology 2, the communication device that directly assigns a group ID to the AIoT device 3 may be the UE2. Regardless of topology 1 and 2, the communication device that indirectly assigns a group ID to the AIoT device 3 may be the AIoTF12b.

[0176] In the second embodiment, the receiving unit 31b receives a group ID assignment request (group ID assignment command) from an external device indicating a group ID to be assigned to the AIoT device 3. If the communication device is a base station 13a or UE2, the external device may be an AIoTF12b. Alternatively, if the communication device is an AIoTF12b, the external device may be an AF11 or NEF12a.

[0177] Upon receiving a group ID assignment request (group ID assignment command) from the receiving unit 31b, the transmitting unit 41a transmits a group ID assignment command, which includes the group ID indicated in the group ID assignment request, to the AIoT device 3 or the reader device.

[0178] (2.4) Examples Based on the system configuration example and system operation example of the second embodiment described above, an embodiment of the second embodiment will be described.

[0179] (2.4.1) Operation Sequence Figures 16 and 17 show an example of the operation sequence according to the second embodiment. This operation sequence corresponds to an example of the system operation according to the second embodiment described above.

[0180] As shown in Figure 16, in step S201, AF11 sends an AIoT service request message to NEF12a that includes a new command type, assignGroup. NEF12a receives the AIoT service request message. The AIoT service request message including assignGroup corresponds to a group ID assignment command (assignment request). Note that assignGroup can be considered a special type of "write" operation. For example, the AIoT service request message may include the persistent identifier (Ambient IoT device ID) of the AIoT device 3 to which the group ID is to be assigned, a Command (assignGroup, group ID) that includes the group ID to be assigned, and an AF ID that identifies AF11.

[0181] In step S202, NEF12a verifies (i.e., authenticates) the legitimacy of AF11 and then forwards the AIoT service request message received in step S201 to AIoTF12b. AIoTF12b receives the AIoT service request message.

[0182] In step S203, AIoTF12b begins verifying (authentication) whether or not group ID assignment (assignGroup) by AF11 is permitted. Specifically, AIoTF12b sends a Nudm_SDM_GET Request message containing assignGroup and AF ID to UDM12c. UDM12c receives the Nudm_SDM_GET Request message. The Nudm_SDM_GET Request message may also include the group ID to be assigned.

[0183] UDM12c verifies (authenticates) whether AF11 is permitted to assign a group ID (assignGroup) based on the Nudm_SDM_GET Request message. UDM12c may also verify (authenticate) whether to permit the assignment of the group ID to be assigned.

[0184] In step S204, UDM12c sends a Nudm_SDM_GET Response message to AIoTF12b that includes authorized (yes / no) as the result of the verification (authentication). AIoTF12b receives the Nudm_SDM_GET Response message. Here, we will proceed assuming that the result is authorized (yes).

[0185] In step S205, AIoTF12b initiates the process of updating the AIoT device profile stored in UDR12d. Specifically, AIoTF12b sends a Nadm_Update_AIoTProfile Request message to AIoTDM12f containing the persistent identifier (Ambient IoT device ID) and the group ID to be assigned to AIoT device 3. AIoTDM12f receives the Nadm_Update_AIoTProfile Request message.

[0186] In step S206, AIoTDM12f sends a Nudr_DM_Update Request message to UDR12d containing the persistent identifier (Ambient IoT device ID) and group ID received in step S205. UDR12d receives the Nudr_DM_Update Request message and updates the AIoT device profile of AIoT device 3 based on the Nudr_DM_Update Request message.

[0187] In step S207, UDR12d sends a Nudr_DM_Update Response message to AIoTDM12f containing the AIoT device profile update result (Result). AIoTDM12f receives the Nudr_DM_Update Response message.

[0188] In step S208, AIoTDM12f sends a Nadm_Update_AIoTProfile Response message containing the AIoT device profile update result (Result) to AIoTF12b. AIoTF12b receives the Nadm_Update_AIoTProfile Response message. In this way, the update of the AIoT device profile stored in UDR12d is completed.

[0189] In step S209, AIoTF12b selects a reader device (base station 13a or UE2).

[0190] In step S210, AIoTF12b starts an inventory to search for AIoT device 3 to which a group ID is to be assigned. However, such inventory operations (steps S210 to S213) are not mandatory and may be omitted.

[0191] Specifically, AIoTF12b sends an inventory request message to the reader device containing the persistent identifier (Ambient IoT device ID) of the AIoT device 3 to which the group ID is to be assigned. The reader device receives the inventory request message.

[0192] In step S211, the reader device broadcasts an AIoT paging message containing the persistent identifier (Ambient IoT device ID) of the AIoT device 3 to which the group ID is to be assigned. The AIoT device 3 receives the AIoT paging message.

[0193] As shown in Figure 17, in step S212, the AIoT device 3 sends an AIoT paging response message containing its persistent identifier (Ambient IoT device ID) to the reader device. The reader device receives the AIoT paging response message.

[0194] In step S213, the reader device sends an Ambient IoT NAS Inventory Response message containing the persistent identifier (Ambient IoT device ID) of AIoT device 3 to AIoTF12b. AIoTF12b receives the AIoT Inventory Response message.

[0195] In step S214, AIoTF12b sends a group ID assignment command (assignment request) to the reader device. The reader device receives the group ID assignment command. This assignment command may be an Ambient IoT NAS command request message containing assignGroup(group ID). This assignment command may also contain the persistent identifier (Ambient IoT device ID) of AIoT device 3.

[0196] In step S215, the reader device sends a group ID assignment command to the AIoT device 3. The AIoT device 3 receives the assignment command. The assignment command includes assignGroup(group ID). The assignment command may also include the persistent identifier (Ambient IoT device ID) of the AIoT device 3.

[0197] In step S216, the AIoT device 3 stores the group ID specified in the assignment command upon receiving the assignment command.

[0198] In step S217, the AIoT device 3 sends a command response message to the reader device. The reader device receives the command response message. The command response message may be an Ambient IoT NAS command response message. The command response message may include assignGroup and result. The command response message may also include the persistent identifier (Ambient IoT device ID) of the AIoT device 3.

[0199] In step S218, the reader device forwards the command response message to AIoTF12b. AIoTF12b receives the command response message.

[0200] In step S218, AIoTF12b sends an AIoTF service response message to NEF12a. NEF12a receives the AIoTF service response message. The AIoTF service response message may include the persistent identifier (Ambient IoT device ID) of the AIoT device 3, assignGroup, and result.

[0201] In step S218, NEF12a forwards the AIoTF service response message to AF11. AF11 receives the AIoTF service response message.

[0202] (2.4.2) Information stored by the UDM Figure 18 shows an example of the information stored by the UDM12c according to the second embodiment.

[0203] In the second embodiment, the UDM12c may store and manage an AF profile (AF subscription) for each AF11, as shown in Figure 18. The AF profile may be stored in the UDM12 by, for example, the OAM14.

[0204] An AF profile includes a set of an AF ID that identifies the corresponding AF11 and an assignGroup. The assignGroup is associated with "Group ID X: Authorization true / false," which indicates for each group whether the AF11 is authorized to assign new groups (group IDs). This information may also include information indicating the range (value range) of group IDs that the AF11 can assign. This information may also include information indicating whether the AF11 is authorized to assign group IDs.

[0205] In the example sequence shown in Figure 16, in step S203, UDM12c receives a Nudm_SDM_GET Request message from AIoTF12b that includes assignGroup and AF ID. The Nudm_SDM_GET Request message may also include the group ID to be assigned.

[0206] Upon receiving a Nudm_SDM_GET Request message, UDM12c may refer to the AF profile and verify (authenticate) whether the assignment of the group ID by AF11 indicated by the AF ID is permitted. Alternatively, UDM12c may refer to the AF profile and verify (authenticate) whether the AF11 is permitted to assign the group ID to be assigned. Then, in step S204, UDM12c sends a Nudm_SDM_GET Response message containing the result of the authentication to AIoTF12b.

[0207] (2.4.3) Information stored by the UDR Figure 19 shows an example of the information stored by the UDR12d according to the second embodiment.

[0208] In the second embodiment, the UDM12c may store and manage an AIoT device profile for each AIoT device 3, as shown in Figure 19. The AIoT device profile includes a set of data, consisting of the Ambient IoT Device identifier of the corresponding AIoT device 3 and a "group" as a data key. The current group ID of the AIoT device 3 is associated with the "group". In this way, the UDM12c stores and manages the current group ID for each AIoT device 3.

[0209] In the sequence example in Figure 16, in step S206, UDR12d receives a Nudr_DM_Update Request message from AIoTDM12f containing the persistent identifier of AIoT device 3 and the group ID to be assigned. UDR12d identifies the AIoT device profile corresponding to the persistent identifier in the Nudr_DM_Update Request message and updates the group ID in the identified AIoT device profile to match the group ID in the Nudr_DM_Update Request message.

[0210] Then, in step S207, UDR12d sends a Nudr_DM_Update Response message to AIoTDM12f containing information about the update result of the group ID.

[0211] (3) Hardware configuration The block diagrams of each communication entity (network node, UE2, AIoT device 3) used in the description of the above embodiment show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired, wireless, etc.). A functional block may be realized by combining the above one device or the above multiple devices with software.

[0212] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. As mentioned above, the method of implementation is not particularly limited.

[0213] For example, each communication entity (each communication device) in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 18 is a diagram showing an example of the hardware configuration of each communication entity according to the embodiment. Each of the above-described communication entities may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.

[0214] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station and AIoT device 3 may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

[0215] Each of the functions in the aforementioned communication entities is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and the storage device 1002, which then causes the processor 1001 to perform calculations and control communication by the communication device 1004, or to control at least one of the reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

[0216] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, etc. For example, the control unit and the like described above may be implemented by the processor 1001.

[0217] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit of each of the above-mentioned communication entities may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-mentioned various processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

[0218] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of this disclosure.

[0219] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0220] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may include high-frequency switches, duplexers, filters, frequency synthesizers, etc., to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmit / receive antenna, amplifier section, transmit / receive section, transmission path interface, etc., may be implemented by the communication device 1004. The transmit / receive section may be implemented with physically or logically separated transmitting and receiving sections.

[0221] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0222] Furthermore, each device, such as the processor 1001 and the storage device 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.

[0223] Furthermore, each communication entity may be composed of hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), or an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, processor 1001 may be implemented using at least one of these hardware components.

[0224] Figure 19 shows an example of the configuration of a vehicle according to this embodiment.

[0225] The vehicle 2001 comprises a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021-2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described herein may be applied to a communication device mounted on the vehicle 2001, for example, to the communication module 2013.

[0226] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0227] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (I / O (Input / Output) ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0228] Signals from various sensors 2021-2029 include current signals from current sensor 2021 which senses motor current, front or rear wheel rotation speed signals obtained by rotation speed sensor 2022, front or rear wheel air pressure signals obtained by air pressure sensor 2023, vehicle speed signals obtained by vehicle speed sensor 2024, acceleration signals obtained by acceleration sensor 2025, accelerator pedal depression signals obtained by accelerator pedal sensor 2029, brake pedal depression signals obtained by brake pedal sensor 2026, shift lever operation signals obtained by shift lever sensor 2027, and detection signals obtained by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0229] The Information Services Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Services Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0230] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS (Global Navigation Satellite System)), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0231] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-2029 provided in the vehicle 2001.

[0232] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0233] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021 to 2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021 to 2028, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above input.

[0234] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0235] (4) Supplementary information on embodiments While embodiments have been described above, the present invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. Although specific numerical examples have been used in the explanation, unless otherwise specified, these numbers are merely examples, and any appropriate values ​​may be used. The division of items in the above explanation is not essential to this disclosure, and the items described above may be used in combination as necessary, and items described in one item may be applied to items described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, each communication entity has been described using a functional block diagram, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the base station according to the embodiment and the software operated by the processor of the terminal according to the embodiment may be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0236] Furthermore, notification of information is not limited to the embodiments / models described herein and may be performed by other methods. For example, notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Information notified by higher layer signaling may be called configuration information. Information notified by physical layer signaling may be called control information. Also, RRC signaling may be called RRC messages, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0237] Each aspect / embodiment described in this disclosure may be applied to at least one of the following systems: LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), Beyond-5G, 6G, FRA (Future Radio Access), NR, W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0238] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements using exemplary order and are not limited to the specific order presented.

[0239] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by the base station and at least one other network node (for example, an MME (Mobility Management Entity) or an S-GW (Serving Gateway), but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0240] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0241] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0242] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0243] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0244] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0245] The information, signals, etc. described in this disclosure may be represented using any of the various different techniques. For example, the data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0246] In addition, terms used in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0247] The terms “system” and “network” as used in this disclosure are interchangeable.

[0248] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0249] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0250] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "Transmission / Reception Point (TRP)", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0251] A base station can house one or more (e.g., three) cells. If a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into several smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0252] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform information-based control or operation.

[0253] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0254] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0255] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademarks), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0256] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminal may have the functions that the base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0257] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal.

[0258] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0259] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0260] The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot depending on the applicable standard.

[0261] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0262] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0263] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0264] In the present disclosure, when the terms "include", "including" and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in the present disclosure is not intended to be an exclusive disjunction.

[0265] A wireless frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. The subframe may further be composed of one or more slots in the time domain. The subframe may have a fixed time length (e.g., 1 ms) independent of numerology.

[0266] Numerology may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. Numerology may indicate at least one of, for example, subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, wireless frame configuration, specific filtering processing performed by a transceiver in the frequency domain, specific windowing processing performed by a transceiver in the time domain, etc.

[0267] A slot may be composed of one or more symbols (OFDM symbol, DC - FDMA (Single Carrier Frequency Division Multiple Access) symbol, etc.) in the time domain. The slot may be a time unit based on numerology.

[0268] A slot may include a plurality of mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. Also, a mini-slot may be called a sub-slot. A mini-slot may be composed of a smaller number of symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a mini-slot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a mini-slot may be called a PDSCH (or PUSCH) mapping type B.

[0269] A radio frame, a sub-frame, a slot, a mini-slot, and a symbol all represent time units when transmitting a signal. Different names corresponding to each of them may be used.

[0270] For example, one sub-frame may be called a transmission time interval (TTI), a plurality of consecutive sub-frames may be called a TTI, or one slot or one mini-slot may be called a TTI. That is, at least one of the sub-frame and the TTI may be a sub-frame (1 ms) in the existing LTE, a period shorter than 1 ms (for example, 1 - 13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, a mini-slot, etc. instead of a sub-frame.

[0271] Here, the TTI refers to, for example, the minimum time unit of scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used in each terminal) to each terminal in units of TTI. Note that the definition of the TTI is not limited to this.

[0272] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0273] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0274] A TTI with a time length of 1 ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0275] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

[0276] A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and in the frequency domain, it may contain one or more consecutive subcarriers. The number of subcarriers in an RB may be the same regardless of the neurology, for example, 12. The number of subcarriers in an RB may be determined based on the neurology.

[0277] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0278] One or more RBs may also be called a Physical RB (PRB), Subcarrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0279] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0280] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common RBs (Routing Bands) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of RBs relative to a common reference point of the carrier. PRBs may be defined and numbered within a given BWP.

[0281] A BWP may include both a BWP for UL (Ultraviolet Link) and a BWP for DL ​​(Downloadable Link). One or more BWPs may be configured for a terminal within a single carrier.

[0282] At least one of the configured BWPs may be active, and the terminal does not need to be expected to send or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0283] The above-described structures of wireless frames, subframes, slots, minislots, and symbols are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0284] "Configuring" wireless parameters means that predetermined values ​​are pre-configured, or that wireless parameters notified by a network node or terminal are configured.

[0285] In this disclosure, if articles are added by translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0286] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0287] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0288] As described above in detail, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented in modified and changed forms without departing from the spirit and scope of the present disclosure defined by the claims. Therefore, the description of the present disclosure is for illustrative purposes and has no restrictive meaning for the present disclosure.

[0289] (5) Supplementary Note The features related to the above-described embodiments are appended.

[0290] · Supplementary Note 1 A terminal, a storage unit that stores a first group identifier indicating the owner to whom the terminal belongs or the owner to whom the article to which the terminal is attached belongs; a transceiver that performs wireless communication with a reader device, where the transceiver includes a receiver that receives a paging message including a second group identifier from the reader device, and a transmitter that transmits a paging response to the reader device in response to the second group identifier matching the first group identifier, a terminal.

[0291] · Supplementary Note 2 The terminal according to Supplementary Note 1, wherein the first group identifier is an updatable identifier.

[0292] · Supplementary Note 3 further having a control unit, where the receiver receives an assignment command for assigning the first group identifier to the terminal from the reader device, and the control unit stores the first group identifier assigned by the assignment command in the storage unit, the terminal according to Supplementary Note 1 or 2.

[0293] · Supplementary Note 4 where the storage unit further stores a first persistent identifier that is an identifier unique to the terminal, The receiving unit receives the paging message including the second persistent identifier and the second group identifier, The terminal according to either Appendix 1 or 2, wherein the transmitting unit transmits the paging response in response to the second persistent identifier matching the first persistent identifier and the second group identifier matching the first group identifier.

[0294] • Appendix 5 A receiving unit that receives paging requests from an external device, including a group identifier indicating the owner to which the terminal belongs or the owner to which the article to which the terminal belongs, A communication device comprising: a transmitting unit that, in response to receiving the aforementioned paging request, transmits a paging message including the group identifier to the terminal or a reader device that performs wireless communication with the terminal.

[0295] • Appendix 6 A communication method performed by a terminal, A step of storing a first group identifier that indicates the owner to which the terminal belongs or the owner to which the article to which the terminal is attached belongs, The steps include receiving a paging message containing a second group identifier from the reader device, A communication method comprising the step of transmitting a paging response to the reader device in response to the second group identifier matching the first group identifier. [Explanation of Symbols]

[0296] 1: NW 2: UE (Reader device) 3: AIoT devices 12:CN 12a :NEF 12b: AIoTF 12c :UDM 12d :UDR 12e :AMF 12f : AIoTDM 13: RAN 13a: Base station (reader device) 13b:Base station 14: OAM 31: Transmitter / Receiver 31a: Transmitter 31b: Receiver 32: Storage section 32a: Persistent identifier storage area 32b: Group ID storage area 33: Control Unit 41: Transmitter / Receiver 41a: Transmitter 41b: Receiver 42: Storage section 43: Control Unit 1001: Processor 1002: Storage device 1003 :Auxiliary storage device 1004: Communication device 1005: Input device 1006: Output device 1007: Bus 2001: Vehicle 2002: Drive unit 2003: Steering Department 2004: Accelerator pedal 2005: Brake pedal 2006: Shift lever 2007: Front wheel 2008: Rear wheel 2009: Axle 2010: Electronic Control Unit 2012: Information Services Department 2013: Communication module 2021-2029: Sensors 2030: Driver Support Systems Department 2031: Microprocessor 2032: Memory 2033: Communication port

Claims

1. It is a terminal, A storage unit that stores a first group identifier indicating the owner to which the terminal belongs or the owner to which the article to which the terminal is attached belongs, It has a transmitting and receiving unit that performs wireless communication with a reader device, The aforementioned transmitting and receiving unit is A receiving unit that receives a paging message containing a second group identifier from the reader device, A terminal comprising: a transmitting unit that transmits a paging response to the reader device in response to the second group identifier matching the first group identifier.

2. The terminal according to claim 1, wherein the first group identifier is an updatable identifier.

3. It further has a control unit, The receiving unit receives an assignment command from the reader device to assign the first group identifier to the terminal, The terminal according to claim 1 or 2, wherein the control unit stores the first group identifier assigned by the assignment command in the storage unit.

4. The storage unit further stores a first persistent identifier, which is an identifier unique to the terminal. The receiving unit receives the paging message including the second persistent identifier and the second group identifier, The terminal according to claim 1 or 2, wherein the transmitting unit transmits the paging response in response to the second persistent identifier matching the first persistent identifier and the second group identifier matching the first group identifier.

5. A receiving unit that receives paging requests from an external device, including a group identifier indicating the owner to which the terminal belongs or the owner to which the article to which the terminal belongs, A communication device comprising: a transmitting unit that, in response to receiving the aforementioned paging request, transmits a paging message including the group identifier to the terminal or a reader device that performs wireless communication with the terminal.

6. A communication method performed by a terminal, A step of storing a first group identifier that indicates the owner to which the terminal belongs or the owner to which the article to which the terminal is attached belongs, The steps include receiving a paging message containing a second group identifier from the reader device, A communication method comprising the step of transmitting a paging response to the reader device in response to the second group identifier matching the first group identifier.

Images