Terminal, communication apparatus, and communication method

Abstract

This terminal comprises: a reception unit that receives, from a reader device, a first message belonging to either service of an inventory for managing the terminal or a command for controlling the terminal; and a transmission unit that transmits, to the reader device, a second message including information indicating a capability of the terminal related to at least one of the inventory and the command, as a response to the first message.

Description

Terminal, Communication Apparatus, and Communication Method

[0001] The present disclosure relates to a terminal, a communication apparatus, and a communication method for use in a wireless communication system.

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

[0003] An AIoT terminal may be a terminal supplied with power via energy harvesting. An AIoT terminal is batteryless or has limited energy storage capacity (e.g., a capacitor), and can be supplied with energy via harvesting of 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), AIoT technology can realize terminals with low complexity, small size, low capability, and low power consumption. AIoT terminals may be maintenance-free and have a long service life.

[0005] 3GPP Contribution "S2-2500927", 3GPP Contribution "S2-2500928"

[0006] A plurality of service types are under consideration as AIoT service types. Such service types include, for example, "inventory" for managing AIoT terminals, and "commands" for controlling AIoT terminals.

[0007] However, not all AIoT devices support all service types. Therefore, some AIoT devices may only support certain service types. For example, an AIoT device may support inventory but not commands.

[0008] Therefore, this disclosure provides a technology that can appropriately address scenarios in which AIoT devices exist that support only certain service types.

[0009] The technology of this disclosure provides a terminal having: a receiving unit that receives a first message from a reader device that belongs to either an inventory service for managing the terminal or a command service for controlling the terminal; and a transmitting unit that, in response to the first message, transmits a second message to the reader device that includes information indicating the terminal's capability with respect to at least one of the inventory and the command service.

[0010] Furthermore, the present invention provides a communication method performed by a terminal, comprising the steps of: receiving a first message from a reader device that belongs to either an inventory service for managing the terminal or a command service for controlling the terminal; and transmitting a second message to the reader device in response to the first message, which includes information indicating the terminal's capability with respect to at least one of the inventory and the command service.

[0011] This figure shows an example configuration of a wireless communication system according to an embodiment. This figure illustrates inventory operation in the wireless communication system according to an embodiment. This figure shows an overview of the command procedure. This figure illustrates the first operation pattern of the embodiment. This figure illustrates the second operation pattern of the embodiment. This figure shows an example of the functional configuration of an AIoT device according to an embodiment. This figure shows an example of the functional configuration of a communication device according to an embodiment. This figure shows the operation of the wireless communication system according to the first embodiment. This figure shows the operation of the wireless communication system according to the second embodiment. This figure shows the operation of the wireless communication system according to the third embodiment. This figure illustrates the command procedure according to the first modification example. This figure shows the operation of the wireless communication system according to the second modification example. This figure shows the operation of the wireless communication system according to the third modification example. This figure shows the operation of the wireless communication system according to the fourth modification example. This figure shows an example of the hardware configuration of each communication entity according to an embodiment. This figure shows an example of the configuration of a vehicle according to an embodiment.

[0012] The wireless communication system according to an embodiment will be described below with reference to the drawings.

[0013] 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 the 3GPP standard, 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, as well as wireless LAN (Local Area Network).

[0014] 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.

[0015] 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) System Configuration First, the configuration of the wireless communication system according to this embodiment will be described. Figure 1 is a diagram showing an example of the configuration of the wireless communication system according to this embodiment.

[0017] As shown in Figure 1, the wireless communication system according to this embodiment includes a network (NW) 1, a UE (User Equipment) 2, and an AIoT device 3. The wireless communication system according to this embodiment may be a 5GS (5G System) or may be called an AIoT system. NW1 may be a 5G network or a 6G network, but in the following description of the embodiments, we will mainly assume that NW1 is a 5G network.

[0018] The elements that constitute NW1 are called network nodes. The term "network node" can be used interchangeably with the term "NF (Network Function)". Network nodes may be logically configured entities or physically configured entities. Hereinafter, 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 be composed of one or more computers. Note that the "connection" described below may be a logical connection or a physical connection.

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

[0020] AF11 is a network node that has the function of controlling applications. AF11 is connected to CN12. AF11 may also be an external node located outside CN12, for example, an external application server. In this embodiment, AF11 uses an AIoT service provided by CN12, which involves wireless communication with one or more AIoT devices 3. In the illustrated example, there is one AF11, but there may be multiple AF11s. Multiple AF11s may correspond one-to-one with multiple operators (multiple users, multiple customers).

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

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

[0023] NEF12a is a network node that has the function of providing authorized AF11s with a means to access CN12. NEF12a mediates communication between AF11 and CN nodes (e.g., AIOTF12b). However, CN12 does not necessarily have to have NEF12a. For example, if AIOTF12b also performs authentication of AF11, communication between AF11 and AIOTF12b may occur without going through NEF12a.

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

[0025] UDM12c is a network node that provides the function of managing the data stored by UDR12d. UDM12c provides the data stored by UDR12d, or adds, updates, or deletes the data stored by UDR12d, in response to requests from other network nodes. In addition, AIoT Data Management (AIoTTDM) may be provided on CN12 for AIoT. AIoTTDM is a network node that provides the function of managing data related to AIoT services. For example, AIoTTDM may function as a front-end for UDR and provide an interface with other network nodes.

[0026] 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. 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 specialized in storing data related to AIoT device 3.

[0027] 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.

[0028] RAN13 is the network portion 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 (Next Generation)-RAN in 5G. Network nodes included in RAN13 may be referred to as RAN nodes.

[0029] RAN13 has multiple base stations 13. In the illustrated example, RAN13 has a base station 13a that operates as a reader device and a base station 13b that performs wireless communication with UE2 which also operates as a reader device. The reader device is a device capable of performing wireless communication with the AIoT device 3.

[0030] Base station 13a performs wireless communication with AIoT device 3a. UE2 performs wireless communication with AIoT device 3b. Base station 13a, which operates as a reader device, may be referred to as a RAN reader, and UE2, which operates as a reader device, may be referred to as a UE reader. The air interface between the reader device and AIoT device 3 is referred to as an AIoT air interface. In this embodiment, RAN 13 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 "operator"), and OAM14 may also be 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 this embodiment, UE2 performs wireless communication with the base station 13b and wireless communication with the AIoT device 3b.

[0033] The AIoT device 3 is an energy harvesting-enabled device. The AIoT device 3 may be a device that is powered by energy harvesting. The AIoT device 3 is battery-less or has 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.

[0034] The AIoT device 3 may be less complex, smaller, less powerful, and consume less power compared to IoT devices already introduced under the 3GPP standard, such as NB-IoT devices and eMTC devices. The AIoT device 3 may be maintenance-free and may have a long lifespan (e.g., 10 years or more). The AIoT device 3 may be installed to blend into its surrounding environment.

[0035] The AIoT device 3 has a protocol stack consisting of lower-layer protocols such as the physical layer and the MAC (Medium Access Control) layer. These lower-layer protocols may be dedicated protocols defined for AIoT. On the other hand, the AIoT device 3 does not have existing higher-layer protocols such as RRC (Radio Resource Control). Furthermore, unlike UE2, the AIoT device 3 is not expected to perform registration with NW1. Therefore, it is difficult for NW1 to grasp the status and capabilities of each AIoT device 3.

[0036] Furthermore, the following three categories ("A" to "C") are being considered for the AIoT device 3. The AIoT device 3 according to this embodiment may belong to any of these categories.

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

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

[0039] 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.

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

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

[0042] As shown in FIG. 1, in the architecture of topology 1, the AIoT device 3a is connected to the CN 12 via a base station 13a which is a RAN node. The base station 13a is an AIoT-compatible base station compatible with the AIoT air interface, and may be, for example, an AIoT-specific gNB. That is, in topology 1, the base station 13a functions as a reader device.

[0043] In the architecture of topology 2, the AIoT device 3b is connected to the CN 12 via the UE 2 and a base station 13b. The UE 2 is an AIoT-compatible UE compatible with the AIoT air interface. That is, in topology 2, the UE 2 functions as a reader device.

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

[0045] (2) AIoT Service Next, the AIoT service according to the present embodiment will be described. As service types of AIoT, a plurality of service types have been studied, for example, "inventory" for managing the AIoT device 3 and "command" for controlling the AIoT device 3. In the following, inventory and commands will be mainly described.

[0046] Furthermore, in addition to inventory and command, the AIoT service type, which is a type of AIoT service, may include "device selection". When there are a large number of AIoT devices 3, device selection allows an appropriate AIoT device 3 to be selected for executing a specific task. "Device selection" may be performed prior to inventory and / or command.

[0047] (2.1) Inventory One or more AIoT devices 3 can be extracted and / or discovered by inventory. In addition, inventory enables detection of AIoT devices 3 existing around a reader device and collection of information thereof. Unlike UE 2, AIoT devices 3 are not always connected to NW 1. By using the inventory function, the NW 1 side can acquire information (device ID, status, measurement values, etc.) of AIoT devices 3 at required timing.

[0048] Figure 2 is a diagram for explaining inventory operation in the wireless communication system according to the present embodiment. As shown in Figure 2, inventory is performed, for example, in accordance with the following procedures 1) to 4).

[0049] 1) Trigger: CN 12 instructs the reader device to start inventory. For example, CN 12 transmits an inventory request message to the reader device (in the illustrated example, base stations 13#1 to 13#3 selected as the reader device). CN 12 may start inventory in response to an AIoT service request message from AF 11.

[0050] Each of the AIoT service request message and the inventory request message may include a device ID of each AIoT device 3 to be inventoried, and / or a device mask (also referred to as "mask" or "bit mask") indicating conditions (filtering conditions) to be satisfied by the AIoT device 3 that should respond to an inventory request (paging). Use of a device mask allows multiple AIoT devices 3 to respond. The AIoT service request message may include information used for selecting a reader device, for example, a reader set ID.

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

[0052] 3) Response of AIoT device 3: Each AIoT device 3 that matches the broadcasted identification information (device ID) responds to the reader device, for example, by random access.

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

[0054] Such an inventory may enable the detection and identification of AIoT devices 3. For example, it may be possible to understand what devices are present in an area and identify each AIoT device 3. Furthermore, the inventory may enable monitoring of the device status (e.g., operating status, battery level, etc.) and collection of data (e.g., sensing data, etc.).

[0055] Furthermore, inventory management becomes easier. In inventory management use cases, for example, it is expected that the status of goods and materials can be grasped in real time based on identification information (device ID), status information (which may include location information), and / or measured values ​​(sensor information) transmitted by an AIoT device 3 in a warehouse or store.

[0056] In the inventory management use case, the AIoT device 3 may be attached to an item, in particular a product. Here, "the AIoT device is attached to a product" means that the AIoT device 3 is attached to the product directly or indirectly. Direct attachment of the AIoT device 3 to a 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 a 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.

[0057] (2.2) Commands Commands can be used to read, write, control, disable, and / or enable one or more AIoT devices 3. Several types of commands are defined. For example, commands include the Read command, the Write command, and the Permanent Disable command. Commands may also include Temporary Disable and Enable commands.

[0058] In the currently envisioned command procedure, inventory is executed prior to the command execution. Figure 3 shows an overview of the command procedure.

[0059] As shown in Figure 3(a), AF11 sends an AIoT service request message to CN12 containing command-related information for one of the command types. The command-related information may include information about the command type (also referred to as the "service operation"). For example, if the service operation is Read, the information related to the read command may include address information of the data to be read (e.g., the starting address and the length of the data). If the service operation is Write, the information related to the write command may include the data to be written and the corresponding address information where the data will be stored (e.g., the starting address and the length of the data). If the service operation is Permanent Disable, the information related to the Permanent Disable command may include security parameters.

[0060] When the AIoTF 12b of CN12 receives an AIoT service request message via NEF 12a, it sends an inventory request message to the reader device (in the illustrated example, base stations 13#1 to 13#3 selected as reader devices). In response to receiving the inventory request message, the reader device broadcasts a paging message for inventory. In response to receiving the paging message, the AIoT device 3 responds to the reader device, for example, by random access. The reader device sends an inventory response message to the AIoTF 12b. The AIoTF 12b discovers and identifies the AIoT device 3 based on the inventory response message.

[0061] Next, as shown in Figure 3(b), the AIoTF 12b sends a command request message containing the command of the specified type from AF 11 to the reader device. Upon receiving the command request message, the reader device sends a command message to the AIoT device 3. Upon receiving the command message, the AIoT device 3 performs the action instructed by the command and sends a response message (command response message) containing command-related response information to the reader device. The reader device sends the command response message to the AIoTF 12b. Upon receiving the command response message, the AIoTF 12b sends an AIoT service response (or notification) message containing command-related response information to AF 11.

[0062] For example, if the command is a read command, the command-related response information may include the data read by the read command. If the command is a write command, the command-related response information may include information indicating that the write was successful (e.g., ACK). If the command is a permanent disable command, the command-related response information may include information indicating that the permanent disable was successful (e.g., ACK).

[0063] (3) System Operation Next, the operation of the wireless communication system according to this embodiment will be described.

[0064] As mentioned above, the service types for AIoT include inventory for managing AIoT device 3 and commands for controlling AIoT device 3. However, not all AIoT device 3 support all service types. Therefore, there may be AIoT device 3 that supports only some service types. For example, there may be an AIoT device 3 that supports inventory but does not support commands. Here, "does not support commands" means that the AIoT device 3 is not compatible with commands. Such an AIoT device 3 may be designed or pre-configured not to handle commands.

[0065] Note that inventory is a fundamental AIoT service and is expected to be supported by all AIoT devices 3. On the other hand, commands may only be used in specific use cases. Therefore, there may be AIoT devices 3 that do not support commands (i.e., AIoT devices 3 that only support inventory).

[0066] Thus, differences may arise in the capabilities of each AIoT device 3 regarding AIoT services. However, unlike UE2, AIoT device 3 is not expected to perform registration with NW1, and NW1 cannot ascertain the capabilities of each AIoT device 3 during its registration process. As a result, it is difficult for CN12 to determine which AIoT services are supported by each AIoT device 3. Furthermore, CN12 cannot know in advance which AIoT device 3 will respond to paging.

[0067] Therefore, even though AIoT device 3 does not support commands, it may still receive command messages, but the behavior of AIoT device 3 in that case is unclear. In such cases, there is a concern that unexpected errors may occur.

[0068] The following embodiments describe a technique that can appropriately address scenarios in which an AIoT device 3 exists that supports only certain service types.

[0069] In this embodiment, the AIoT device 3 receives a first message from the reader device belonging to either an inventory service for managing the AIoT device 3 or a command service for controlling the AIoT device 3. In response to the received first message, the AIoT device 3 sends a second message to the reader device that includes information indicating the capabilities of the AIoT device 3 with respect to at least one of the inventory and commands (hereinafter also referred to as "capability information"). The second message may include the capability information and the device ID of the AIoT device 3. The transmission and reception of the first and second messages may be performed in a specific layer or a specific protocol. The specific layer or specific protocol may be an AIoT-dedicated layer or AIoT-dedicated protocol that is different from the existing layers or protocols for UE2. The AIoT-dedicated layer or AIoT-dedicated protocol may be an AIoT-dedicated NAS (Non-access stratum) and / or an AIoT-dedicated AS (Access stratum).

[0070] Thus, in this embodiment, the AIoT device 3 transmits a second message to the reader device containing capability information relating to at least one of inventory and commands. This allows the NW1 to understand the capabilities of the AIoT device 3 relating to at least one of inventory and commands based on the information contained in the second message. Furthermore, the AIoT device 3 transmits a second message containing capability information to the reader device as a response to the first message it receives. This allows the AIoT device 3, which does not undergo registration with the NW1, to efficiently provide capability information to the NW1 at an appropriate time.

[0071] In the first operation pattern of this embodiment, the first message is a paging message used for inventorying performed before the command. The second message is a response message to the paging message. The AIoT device 3 sends the response message, which includes capability information, to the reader device.

[0072] Figure 4 is a diagram illustrating the first operation pattern of this embodiment.

[0073] As shown in Figure 4(a), when the AIoTF 12b of CN12 receives an AIoT service request message via NEF 12a, it sends an inventory request message to the reader device (in the illustrated example, base stations 13#1 to 13#3 selected as reader devices). In response to receiving the inventory request message, the reader device broadcasts a paging message for inventory. In response to receiving the paging message, the AIoT device 3 sends a response message to the reader device, for example, by random access. Here, the response message includes capability information of the AIoT device 3. The reader device sends an inventory response message containing capability information to the AIoTF 12b. Based on the inventory response message, the AIoTF 12b discovers and identifies the AIoT device 3 and understands the capabilities of the AIoT device 3 based on the capability information.

[0074] Here, we assume that the AIoT device 3 supports inventory but does not support commands. In this case, the capability information may be information indicating that the AIoT device 3 supports inventory but does not support commands. In this case, as shown in Figure 4(b), the AIoTTF 12b recognizes that the AIoT device 3 does not support commands and does not send a command request message to the reader device. That is, the AIoTTF 12b stops sending commands to the AIoT device 3. As a result, no command messages are sent to the AIoT device 3, and the resource consumption and processing load due to command transmission can be reduced. The AIoTTF 12b then sends an AIoT service response (or notification) message containing error information to the AF 11. The error information may be information indicating that the AIoT device 3 does not support commands. As a result, the AF 11 can recognize that the command was not completed (i.e., the command failed) because the AIoT device 3 does not support commands.

[0075] In the second operation pattern of this embodiment, the first message is a command message used for the command. The second message is a response message to the command message. If the AIoT device 3 does not support the command, the AIoT device 3 sends a response message to the reader device as a response to the command message, which includes information indicating that the AIoT device 3 does not support the command.

[0076] Figure 5 is a diagram illustrating the second operation pattern of this embodiment. In the second operation pattern, inventory does not necessarily have to be performed before the command. The first and second operation patterns may be performed separately and independently, or they may be performed in combination.

[0077] As shown in Figure 5, the AIoTF 12b sends a command request message to the reader device containing a command of the type specified by AF 11. Upon receiving the command request message, the reader device sends a command message to the AIoT device 3. Here, we assume that the AIoT device 3 does not support the command. In this case, the AIoT device 3, upon receiving the command message, sends a response message to the reader device containing error information indicating that it does not support the command. Such error information can be considered a type of capability information. The error information may also be cause information that specifically indicates the cause of the error. The reader device sends a command response message containing the error information to the AIoTF 12b. The AIoTF 12b sends an AIoT service response (or notification) message containing the error information to AF 11. This allows AF 11 to understand that the command could not be completed (i.e., the command failed) because the AIoT device 3 did not support the command.

[0078] (4) Device Configuration Next, the configurations of the AIoT device 3 and the communication device according to this embodiment will be described. The communication device is an AIoTTF 12b or a reader device. The reader device is a base station 13a or a UE2.

[0079] (4.1) Example of AIoT device configuration Figure 6 is a diagram showing an example of the functional configuration of the AIoT device 3 according to this embodiment. However, the configuration shown in Figure 6 may be an example of the hardware configuration of the AIoT device 3.

[0080] 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 operations according to this embodiment. The AIoT device 3 may further include a battery for realizing an energy storage function.

[0081] The transmitting / receiving unit 31 performs wireless communication with the reader device (base station 13a or UE2). The transmitting / receiving unit 31 may perform RF transmission by backscatter, or it may be capable of active transmission instead of RF reflection. The transmitting / receiving unit 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, information of 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".

[0082] The storage unit 32 includes a memory device, stores pre-configured settings and other information in the memory device, and reads it from the memory device as needed. The storage unit 32 stores the device ID (persistent identifier) ​​of its own device. The storage unit 32 may also store data according to the use case.

[0083] 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 unit of the control unit 33 may be included in the transmission unit 31a, and the signal reception function unit of the control unit 33 may be included in the reception unit 31b.

[0084] In the AIoT device 3 configured in this way, the receiving unit 31b receives a first message from the reader device that belongs to either the inventory service for managing the AIoT device 3 or the command service for controlling the AIoT device 3. In response to the first message, the transmitting unit 31a sends a second message to the reader device that includes information indicating the capabilities of the AIoT device 3 with respect to at least one of the inventory and the command service.

[0085] In the first operation pattern of this embodiment, the receiving unit 31b receives a paging message used for inventorying before a command from the reader device as a first message. The transmitting unit 31a sends a response message to the reader device as a second message. Here, the transmitting unit 31a sends a response message to the reader device that includes capability information relating to at least one of the inventory and the command.

[0086] Such capability information may be any of the following a) to c):

[0087] a) Information indicating that only inventory is supported among inventory and commands. This information may be a 1-bit piece of information that is set to "1" (True) if only inventory is supported, and "0" (False) otherwise.

[0088] b) Information indicating that the command is not supported. This information may be a single bit that is set to "1" (True) if the command is not supported, and "0" (False) otherwise.

[0089] c) Information indicating support for a command This information may be a single bit that is set to "1" (True) if the command is supported, and "0" (False) otherwise.

[0090] Capability information may be specified as an optional field in the response message. For example, if inventory and commands are supported, the absence of capability information in the response message may implicitly indicate that inventory and commands are supported.

[0091] As described above, in the first operation pattern of this embodiment, the receiving unit 31b receives a paging message used for inventorying performed before a command from the reader device, and the transmitting unit 31a sends a response message to the reader device that includes capability information. As a result, NW1 can determine whether or not the AIoT device 3 supports the command based on the capability information in the response message. NW1 may stop sending command messages to AIoT devices 3 that do not support the command.

[0092] In the second operation pattern of this embodiment, the receiving unit 31b receives a command message from the reader device as the first message. The transmitting unit 31a sends a response message to the reader device as the second message. If the AIoT device 3 does not support the command, the transmitting unit 31a sends a response message to the reader device that includes error information indicating that the command is not supported. Such error information may be information indicating that only inventory is supported among inventory and commands, similar to a) above.

[0093] As a result, NW1 can determine, based on the error information in the response message, that the AIoT device 3 does not support the command. NW1 can also determine that the command was not completed because the AIoT device 3 did not support the command.

[0094] (4.2) Example of Communication Device Configuration Figure 7 is a diagram showing an example of the functional configuration of the communication device according to this embodiment. However, the configuration shown in Figure 7 may be an example of the hardware configuration of the communication device.

[0095] In topology 1, the communication device may be a base station 13a that directly transmits and receives the first and second messages with the AIoT device 3. In topology 2, the communication device may be a UE2 that directly transmits and receives the first and second messages with the AIoT device 3. Regardless of topology 1 and 2, the communication device may be an AIoTTF 12b that indirectly transmits and receives the first and second messages with the AIoT device 3.

[0096] The communication device shown in Figure 7 (base station 13a, UE2, AIoTF 12b) 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 the operation according to this embodiment can be performed.

[0097] The transmitting / receiving unit 41 communicates 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.

[0098] 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.

[0099] 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.

[0100] In the communication device configured in this way, the transmitting unit 41a transmits a first message to the AIoT device 3 that belongs to either an inventory service for managing the AIoT device 3 or a command service for controlling the AIoT device 3. The receiving unit 41b receives a second message from the AIoT device 3 in response to the first message, which includes information indicating the AIoT device 3's capability with respect to at least one of the inventory and the command service.

[0101] In the first operation pattern of this embodiment, the transmitting unit 41a transmits a paging message used for inventorying performed before a command to the AIoT device 3 as a first message. The receiving unit 41b receives a response message to the paging message from the AIoT device 3 as a second message. Here, the receiving unit 41b receives a response message from the AIoT device 3 that includes capability information relating to at least one of the inventory and the command.

[0102] As a result, NW1 (e.g., AIoTF12b) can determine whether or not the AIoT device 3 supports the command based on the capability information in the response message. NW1 (e.g., AIoTF12b) may stop sending command messages to the AIoT device 3 that does not support the command.

[0103] In the second operation pattern of this embodiment, the receiving unit 31b receives a command message from the reader device as the first message. The transmitting unit 31a sends a response message to the reader device as the second message. If the AIoT device 3 does not support the command, the transmitting unit 31a sends a response message to the reader device that includes error information indicating that the command is not supported. Such error information may be information indicating that only inventory is supported among inventory and commands, similar to a) above.

[0104] As a result, NW1 can determine, based on the error information in the response message, that the AIoT device 3 does not support the command. NW1 can also determine that the command was not completed because the AIoT device 3 did not support the command.

[0105] (5) Examples Next, based on the configuration and operation of the above-described embodiments, the first to third embodiments will be described. In the first to third embodiments, the AMF 12e may be intervened in the communication between the AIoTF 12b and the reader device.

[0106] (5.1) Figure 8 of the first embodiment shows the operation of the wireless communication system according to the first embodiment. The first embodiment is an example corresponding to the first operation pattern.

[0107] As shown in Figure 8, in step S101, AF11 sends an AIoT service request message to NEF12a. NEF12a receives the AIoT service request message. The AIoT service request message includes the command-related information described above. The command-related information may include the device ID and / or device mask of the AIoT device 3 that is the target of the command. The command-related information may also include the AF ID, which is the identifier of AF11 that requested the command.

[0108] In step S102, NEF12a authenticates AF11 and / or selects AIoTF12b, and sends an AIoT service request message containing command-related information to AIoTF12b. AIoTF12b receives the AIoT service request message.

[0109] In step S103, AIoTF12b verifies (authenticates) whether AF11 is authorized to trigger the command. Here, we will proceed assuming that AF11 is authorized to trigger the command. If AF11 is not authorized to trigger the command, AIoTF12b may reject the AIoT service request and skip the subsequent steps.

[0110] In step S104, the AIoTF12b selects a reader device based on information provided, for example, by AF11.

[0111] In step S105, the AIoTF12b sends an inventory request message to the selected reader device, which includes the device ID and / or device mask. The reader device receives the inventory request message. The inventory request message may include information indicating that it is for the service operation of the command.

[0112] In step S106, the reader device sends a paging message (AIoT paging) including the device ID and / or device mask to the AIoT device 3. The AIoT device 3 receives the paging message.

[0113] In step S107, the AIoT device 3 determines that the identifier (device ID and / or device mask) in the paging message matches its own identifier and sends a response message (inventory response) to the reader device via a random access procedure. The reader device receives the response message.

[0114] The response message includes the device ID of AIoT device 3 and the capability information described above. Here, we will proceed with the assumption that AIoT device 3 does not support the command, and that the capability information indicates this. Note that the response message may also be an AIoT NAS message handled by a dedicated AIoT NAS.

[0115] In step S108, the reader device sends an inventory response message to the AIoTF12b, which includes the device ID and capability information in the response message. The AIoTF12b receives the inventory response message. The reader device may also send an inventory response message to the AIoTF12b, which includes an AIoT NAS message from the AIoT device 3. The inventory response message may be referred to as an inventory report message.

[0116] In step S109, the AIoTF 12b determines, based on the capability information in the inventory response message, that the AIoT device 3 indicated by the device ID in the inventory response message does not support the command. In this case, the AIoTF 12b stops generating a command for the AIoT device 3. This prevents the transmission of a command to the AIoT device 3 that does not support the command.

[0117] In step S110, the AIoTF 12b sends an AIoT service response message to the NEF 12a, which includes the device ID in the inventory response message and error information. The NEF 12a receives the AIoT service response message. The error information may indicate that the AIoT device 3 indicated by the device ID does not support the command, as this is the cause of the error.

[0118] In step S111, NEF12a sends an AIoT service response message to AF11 that includes the device ID from the AIoT service response message from AIoTTF12b and error information. AF11 receives the AIoT service response message. This allows AF11 to understand that the command could not be completed because the AIoT device 3 indicated by the device ID does not support the command.

[0119] (5.2) Second Embodiment Figure 9 is a diagram showing the operation of the wireless communication system according to the second embodiment. The second embodiment is an embodiment that modifies the first embodiment shown in Figure 8. Specifically, because the execution of the operation may take a long time, in the second embodiment, the AIoTF12b first sends an AIoT service response message, and then sends an AIoT service notification message.

[0120] As shown in Figure 9, the operation of steps S201 to S203 is the same as the operation of steps S101 to S103 in Figure 8. In step S203, AIoTF12b verifies (authenticates) whether AF11 is authorized to trigger a command. Here, we will proceed with the assumption that AF11 is authorized to trigger a command.

[0121] In step S204, the AIoTF 12b sends an AIoT service response message to the NEF 12a indicating that it accepts the AIoT command service operation request. The NEF 12a receives the AIoT service response message.

[0122] In step S205, NEF12a sends an AIoT service response message to AF11 indicating that it accepts the AIoT command service operation request. AF11 receives the AIoT service response message. This allows AF11 to understand that the AIoT command service operation request has been accepted.

[0123] The operation in steps S206 to S211 is the same as the operation in steps S104 to S109 in Figure 8. In step S211, the AIoTF 12b determines, based on the capability information in the inventory response message, that the AIoT device 3 indicated by the device ID in the inventory response message does not support the command.

[0124] In step S212, the AIoTF 12b sends an AIoT service notification message to the NEF 12a, which includes the device ID in the inventory response message and error information. The NEF 12a receives the AIoT service notification message. The error information may indicate that the AIoT device 3 indicated by the device ID does not support the command, as this is the cause of the error.

[0125] In step S213, NEF12a sends an AIoT service response message to AF11 that includes the device ID from the AIoT service response message from AIoTTF12b and error information. AF11 receives the AIoT service notification message. This allows AF11 to understand that the command could not be completed because the AIoT device 3 indicated by the device ID does not support the command.

[0126] (5.3) Figure 10 of the third embodiment shows the operation of the wireless communication system according to the third embodiment. The third embodiment is an embodiment that corresponds to an example of the second operation pattern.

[0127] As shown in Figure 10, the operations in steps S301 to S308 are the same as those in steps S101 to S108 in Figure 8. However, in this embodiment, the AIoT device 3 does not need to include capability information in the inventory response in step S307. As a result, in step S308, the AIoTF 12b receives an inventory response message that does not include capability information.

[0128] In step S309, the AIoTF12b generates a command based on the command-related information from the AF11.

[0129] In step S310, the AIoTF 12b sends a command request message containing the generated command to the reader device. The reader device receives the command request message. The command request message may be an AIoT NAS message handled by an AIoT-dedicated NAS.

[0130] In step S311, the AIoTF 12b sends a command message based on the command request message to the AIoT device 3. The AIoT device 3 receives the command message. The command message may include an AIoT NAS message from the AIoTF 12b. Here, we assume that the AIoT device 3 does not support commands.

[0131] In step S312, the AIoT device 3 sends a command response message to the reader device, which includes the device ID and error information indicating that the command is not supported. Such error information can be considered a type of capability information. The reader device receives the command response message. The command response message may also be an AIoT NAS message handled by a NAS dedicated to AIoT.

[0132] In step S313, the reader device sends a command response message to the AIoTF 12b, which includes the device ID and error information from the command response message from the AIoT device 3. The AIoTF 12b receives the command response message.

[0133] In step S314, the AIoTF 12b determines, based on the error information in the command response message, that the AIoT device 3 indicated by the device ID in the command response message does not support the command. The AIoTF 12b may also determine that the command was not completed because the AIoT device 3 does not support the command.

[0134] In step S315, the AIoTF 12b sends an AIoT service response message to the NEF 12a, which includes the device ID in the command response message and error information. The NEF 12a receives the AIoT service response message. The error information may indicate that the AIoT device 3, indicated by the device ID, does not support the command, as this is the cause of the error.

[0135] In step S316, NEF12a sends an AIoT service response message to AF11 that includes the device ID from the AIoT service response message from AIoTTF12b and error information. AF11 receives the AIoT service response message. This allows AF11 to understand that the command could not be completed because the AIoT device 3 indicated by the device ID does not support the command.

[0136] In addition, this embodiment may be modified, similar to the second embodiment, so that the AIoTF12b first sends an AIoT service response message and then sends an AIoT service notification message.

[0137] (6) Examples of modifications Next, examples of modifications to the above-described embodiments and examples will be explained.

[0138] (6.1) First Modification Example In the above embodiment, an example in which there is one AIoT device 3 that is the target of the command has been mainly described. However, there may be multiple AIoT devices 3 that are the target of the command.

[0139] Figure 11 is a diagram illustrating the command procedure related to this modification example. Here, we assume that in the first operation pattern of the embodiment described above, there are multiple AIoT devices 3 that are the target of the command (AIoT devices 3#1 to 3#4).

[0140] As shown in Figure 11(a), AF11 sends an AIoT service request message to CN12 containing command-related information for any type of command. When CN12's AIoTTF12b receives the AIoT service request message via NEF12a, it sends an inventory request message to the reader device (in the illustrated example, base stations 13#1 to 13#3 selected as the reader device). In response to receiving the inventory request message, the reader device broadcasts a paging message for inventory. In response to receiving the paging message, AIoT devices 3#1 to 3#4 respond to the reader device, for example, by random access.

[0141] Here, each of the AIoT devices 3#1 to 3#4 sends a response message to the reader device containing capability information indicating whether or not it supports commands (i.e., whether or not it only supports inventory) and its own device ID. In the illustrated example, we will proceed with the assumption that AIoT devices 3#1 and 3#2 support commands, and AIoT devices 3#3 and 3#4 do not support commands.

[0142] The reader device sends an inventory response message to the AIoTF 12b for each of the AIoT devices 3#1 to 3#4. Each inventory response message includes capability information indicating whether the corresponding AIoT device 3 supports commands (i.e., whether it only supports inventory) and the device ID of the corresponding AIoT device 3. The AIoTF 12b discovers and identifies the AIoT devices 3#1 to 3#4 based on the device ID in each inventory response message. The AIoTF 12b also determines whether each of the AIoT devices 3#1 to 3#4 supports commands based on the capability information in each inventory response message.

[0143] In this modified example, as shown in Figure 11(b), the AIoTF 12b generates a command request message for each of the AIoT devices 3#1 and 3#2 that support commands, and sends each generated command request message to the reader device. On the other hand, the AIoTF 12b does not generate a command request message for each of the AIoT devices 3#3 and 3#4 that do not support commands. As a result, AIoT devices 3#1 and 3#2 receive command messages from the reader device and perform command operations. AIoT devices 3#3 and 3#4, however, do not receive command messages from the reader device.

[0144] Alternatively, the AIoTF 12b generates a command request message for each of the AIoT devices 3#1 to 3#4 and sends each generated command request message to the reader device. The AIoTF 12b may also instruct the reader device not to prepare uplink resources for responses from AIoT devices 3#3 and 3#4, which do not support commands. As a result, the reader device does not need to prepare uplink resources for command responses from AIoT devices 3#3 and 3#4, thus saving radio resources.

[0145] In this modified example, AIoT devices 3#1 and 3#2, upon receiving a command message, perform the action instructed by the command and send a response message (command response message) containing command-related response information to the reader device. The reader device sends the command response message to the AIoTTF 12b. Upon receiving the command response message, the AIoTTF 12b sends an AIoT service response (or notification) message containing command-related response information to the AF 11.

[0146] (6.2) Second Modification Example In the first operation pattern of the embodiment described above, the AIoT 12b sent a response message including the device ID and capability information to the reader device in response to receiving an inventory paging message from the reader device. However, in the case of inventory not caused by a command, the AIoT device 3 may send a response message to the reader device that does not include capability information.

[0147] In this modified example, the reader device sends a paging message to the AIoT device 3 that includes an identifier (device ID and / or device mask) and information indicating that the command is for service operation. The AIoT device 3 sends a response message to the reader device that includes its device ID and capability information if the identifier in the paging message matches its own identifier and the paging message includes information indicating that the command is for service operation.

[0148] On the other hand, if the AIoT device 3 finds that the identifier in the paging message matches its own identifier, but the paging message does not contain information indicating that it is for the service operation of a command, it sends a response message to the reader device that includes the device ID but does not include capability information. This reduces the overhead associated with sending and receiving capability information.

[0149] Figure 12 shows the operation of the wireless communication system according to this modified example. Here, the operation based on the first embodiment described above will be explained. However, redundant explanations of operations similar to those of the first embodiment described above will be omitted.

[0150] As shown in Figure 12, in step S105a, the AIoTF 12b sends an inventory request message to the selected reader device, which includes the device ID and / or device mask and information indicating that it is for the service operation of a command (also referred to as the "command indicator"). The reader device receives the inventory request message.

[0151] In step S106a, the reader device sends a paging message (AIoT paging) to the AIoT device 3, which includes the device ID and / or device mask and a command indicator. The AIoT device 3 receives the paging message. The AIoT device 3 may determine, based on the command indicator, that the paging is inventory caused by a command.

[0152] In step S107a, the AIoT device 3 determines that the identifier (device ID and / or device mask) in the paging message matches its own identifier and sends a response message (inventory response) to the reader device via a random access procedure to the reader device. The reader device receives the response message. Here, the AIoT device 3 includes capability information in the response message, depending on whether the paging message contained a command directive.

[0153] (6.3) Third Modification Example The above embodiment described a case in which multiple types of commands are defined. For example, the commands may include a Read command, a Write command, and a Permanent Disable command. The commands may also include a Temporary Disable command and an Enable command.

[0154] It is possible that AIoT device 3 supports only some of the command types among several types. For example, there may be an AIoT device 3 that supports read commands but not write commands. Also, there may be an AIoT device 3 that supports temporary disable and enable commands but not permanent disable commands.

[0155] Therefore, in the above embodiment, the capability information (or error information) transmitted by the AIoT device 3 may be information indicating the AIoT device 3's capability with respect to a specific type of command among several types. In this case, the capability information may be multi-bit information rather than single-bit information. This allows the AIoTF 12b to understand which types of commands the AIoT device 3 supports or does not support. As a result, the AIoTF 12b can control the transmission of commands of types that the AIoT device 3 does not support to the AIoT device 3.

[0156] For example, in the first operation pattern of the embodiment described above, when the AIoT device 3 sends an inventory response message to the reader device, it may include capability information in the response message indicating each type of command it supports or does not support. For example, assuming that three types of commands are defined—read commands, write commands, and permanent disable commands—the capability information may be a bit sequence in which each type is associated with one bit. In such a bit sequence, the first bit may be associated with the read command, the second bit with the write command, and the third bit with the permanent disable command. Then, "1" (True) is set if supported, and "0" (False) is set if not supported. To give a specific example, an AIoT device 3 that supports read commands but does not support write commands and permanent disable commands may send a bit sequence of "100" as capability information. Note that this format of capability information can also be applied to error information.

[0157] Alternatively, instead of providing support or non-support information (or error information) for each individual command type, support or non-support information may be provided for groups of command types. For example, a set of temporarily disabled commands and enabled commands may be defined as a group, and support or non-support information (or error information) may be provided for that group.

[0158] Figure 13 shows the operation of the wireless communication system according to this modified example. Here, the operation based on the first embodiment described above will be explained. However, redundant explanations of operations similar to those of the first embodiment described above will be omitted.

[0159] As shown in Figure 13, in step S107b, the AIoT device 3 sends a response message (inventory response) to the reader device, which includes the device ID and capability information for each command type. The reader device receives the response message.

[0160] In step S108b, the reader device sends an inventory response message to the AIoTF12b, which includes the device ID and capability information for each command type in the response message. The AIoTF12b receives the inventory response message.

[0161] In step S109b, the AIoTF 12b determines whether the AIoT device 3 supports the type of command (specific command) requested by the AF 11, based on the capability information for each command type in the inventory response message. Here, we will proceed with the assumption that the AIoT device 3 does not support the type of command (specific command) requested by the AF 11. In this case, the AIoTF 12b stops generating commands for the AIoT device 3.

[0162] In step S110b, the AIoTF 12b sends an AIoT service response message to the NEF 12a, which includes the device ID in the inventory response message and error information. The NEF 12a receives the AIoT service response message. The error information may indicate that the AIoT device 3 does not support the type of command (specific command) requested by the AF 11 as the cause of the error.

[0163] In step S111b, NEF12a sends an AIoT service response message to AF11 that includes the device ID from the AIoTTF12b and error information. AF11 receives the AIoT service response message. This allows AF11 to understand that the command could not be completed because the AIoT device 3 does not support the type of command requested by AF11 (a specific command).

[0164] (6.4) Fourth Modification Example In this modification example, the reader device may send a paging message to the AIoT device 3 in the inventory resulting from a command, which includes an identifier (device ID and / or device mask) and information indicating the type of the command.

[0165] If the AIoT device 3 finds that the identifier in the received paging message matches its own identifier, it may send a response message to the reader device that includes capability information indicating whether or not it supports the type of command shown in the received paging message.

[0166] For example, consider a scenario where a write command is used, but the AIoT device 3 does not support the write command. In this case, the AIoTTF 12b sends an inventory request message to the reader device indicating that it is for the service operation of the write command. Based on the inventory request message, the reader device sends a paging message to the AIoT device 3 indicating that it is for the service operation of the write command.

[0167] The AIIoT device 3 then determines whether or not it supports the write command indicated in the received paging message. The AIIoT device 3 sends a response message to the reader device that includes capability information indicating whether or not it supports the write command. The reader device includes the capability information from the response message in an inventory response message and sends it to the AIIoTTF 12b. This allows the AIIoTTF 12b to send a write command if the AIIoT device 3 supports the write command, and not send a write command if the AIIoT device 3 does not support the write command.

[0168] Figure 14 shows the operation of the wireless communication system according to this modified example. Here, the operation based on the first embodiment described above will be explained. However, redundant explanations of operations similar to those of the first embodiment described above will be omitted.

[0169] As shown in Figure 14, in step S105c, the AIoTF 12b sends an inventory request message to the selected reader device, which includes the device ID and / or device mask and information indicating the type of command requested from AF 11 (also referred to as the "command type indicator"). The reader device receives the inventory request message.

[0170] In step S106c, the reader device sends a paging message (AIoT paging) to the AIoT device 3, which includes the device ID and / or device mask and a command type indicator. The AIoT device 3 receives the paging message.

[0171] In step S107c, the AIoT device 3 determines that the identifier (device ID and / or device mask) in the paging message matches its own identifier and sends a response message (inventory response) to the reader device via a random access procedure. The reader device receives the response message.

[0172] In this modified example, AIoT device 3 determines whether it supports the type of command indicated by the command type indicator in the paging message. If it supports the command of that type, AIoT device 3 includes information indicating that it supports the command of that type as capability information in the response message. On the other hand, if it does not support the command of that type, AIoT device 3 includes information indicating that it does not support the command of that type as capability information in the response message.

[0173] In step S108c, the reader device sends an inventory response message to the AIoTF12b, which includes the device ID and capability information in the response message. The AIoTF12b receives the inventory response message.

[0174] In step S109c, the AIoTF 12b determines, based on the capability information in the inventory response message, whether the AIoT device 3 supports the type of command requested by AF 11. Here, we proceed with the assumption that the AIoTF 12b does not support the type of command in question. In this case, the AIoTF 12b stops generating a command for the AIoT device 3.

[0175] (6.5) Fifth Modification Example In this modification example, when the AIoTF 12b receives capability information and device ID from the AIoT device 3, it temporarily stores (caches) the capability information in association with the device ID. The AIoTF 12b may also temporarily store (caches) the capability information in association with the device ID in the UDM 12c and / or UDR 12d.

[0176] If AIoTF12b subsequently receives a command request from AF11, it determines whether AIoT device 3 supports the command corresponding to the command request based on the stored capability information and device ID. This allows AIoTF12b to determine whether AIoT device 3 supports the command based on the stored information before performing paging caused by the command. If it determines that AIoT device 3 does not support the command, it can send an AIoT service response message containing error information to that effect to AF11 via NEF12a.

[0177] (7) Hardware Configuration The block diagrams of each communication entity (network node, UE2, AIoT device3) used in the description of the above embodiments 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 one device or the multiple devices with software.

[0178] Functions include, but are not limited to, judgment, decision, determination, 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. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0179] 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 15 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.

[0180] In the following explanation, the term "device" can be read as "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 figure, or it may be configured without some of the devices.

[0181] 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, control communication by the communication device 1004, and control at least one of the reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

[0182] 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 devices, arithmetic units, registers, etc. For example, the control unit and the like described above may be implemented by the processor 1001.

[0183] 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 a computer to execute at least a part of the operations described in the above embodiment. For example, the control unit of each communication entity described above may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above 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.

[0184] 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 the present disclosure.

[0185] 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 disk, a digital multipurpose disk, a Blu-ray® disk), 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.

[0186] The communication device 1004 is hardware (transmitting / receiving 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 be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

[0187] 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).

[0188] 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.

[0189] 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, the processor 1001 may be implemented using at least one of these hardware components.

[0190] Figure 16 shows an example of the configuration of a vehicle according to the embodiment.

[0191] The vehicle 2001 includes 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 to 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.

[0192] 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.

[0193] 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).

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

[0195] The Information Service 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 Service 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 Service 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.).

[0196] 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 transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0197] 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 the 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 to 2029 provided in the vehicle 2001.

[0198] 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 with 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.

[0199] 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.

[0200] 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 a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the 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.

[0201] (8) Supplementary Information on Embodiments The embodiments have been described above, but the present invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used in the explanation, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to this disclosure, and the matters described in the above items may be used in combination as necessary, and matters described in one item may be applied to matters 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.

[0202] 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, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0203] Each aspect / embodiment described herein may be applied to at least one of systems utilizing 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®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, 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 and 5G).

[0204] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be rearranged in order, 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.

[0205] 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).

[0206] 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.

[0207] 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.

[0208] 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).

[0209] 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.

[0210] 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.

[0211] 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.

[0212] 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.

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

[0214] 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.

[0215] 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.

[0216] 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.

[0217] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple 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.

[0218] 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 control or operation based on the information.

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

[0220] 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.

[0221] 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 trademark), 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.

[0222] 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.

[0223] 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.

[0224] The terms “determining” and “decision” as used in this disclosure 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 tables, databases or other data structures), and ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, “determining” may include resolving, selecting, choosing, establishing, and comparing. In other words, "judgment" and "decision" can include considering that some action has been "judged" or "decided." Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0225] The terms “connected,” “coupled,” and any variations 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 read 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.

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

[0227] 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."

[0228] 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.

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

[0230] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

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

[0232] Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0233] A slot may consist of one or more symbols in the time domain (such as OFDM symbols or DC-FDMA (Single Carrier Frequency Division Multiple Access) symbols). A slot may also be a time unit based on neurology.

[0234] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called a PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called a PDSCH (or PUSCH) mapping type B.

[0235] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0236] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0237] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal) in TTI units. However, the definition of TTI is not limited to this.

[0238] 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. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

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

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

[0241] 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.

[0242] 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.

[0243] Furthermore, the time domain of the 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.

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

[0245] 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.

[0246] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common RBs (RBs) 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.

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

[0248] 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".

[0249] 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.

[0250] When wireless parameters are "configured," this may mean that predetermined values ​​are pre-configured, or that wireless parameters notified by a network node or terminal are configured.

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

[0252] 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."

[0253] Each aspect / embodiment described in this disclosure 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).

[0254] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0255] (9) Additional notes: Features of the above-described embodiments are noted below.

[0256] - Appendix 1 A terminal comprising: a receiving unit that receives a first message from a reader device belonging to either an inventory service for managing the terminal or a command service for controlling the terminal; and a transmitting unit that, as a response to the first message, transmits a second message to the reader device that includes information indicating the terminal's capability with respect to at least one of the inventory and the command.

[0257] - Appendix 2 The terminal as described in Appendix 1, wherein the first message is a paging message used for the inventory that is performed before the command, and the transmitting unit transmits the second message as a response to the paging message, the second message containing information indicating whether the terminal supports only the inventory among the inventory and the command.

[0258] - Appendix 3 The terminal as described in Appendix 1, wherein the first message is a command message used in the command, and if the terminal does not support the command, the transmitting unit transmits the second message, which includes the information indicating that the terminal does not support the command, as a response to the command message.

[0259] - Appendix 4: In cases where multiple types are defined in the command, the transmitting unit transmits a second message containing the information indicating the terminal's capability with respect to a specific type of command among the multiple types, as described in any of Appendix 1 to 3.

[0260] - Appendix 5 A communication device comprising: a transmitting unit that transmits a first message to a terminal belonging to either an inventory service for managing a terminal or a command service for controlling the terminal; and a receiving unit that receives a second message from the terminal as a response to the first message, which includes information indicating the terminal's capability with respect to at least one of the inventory and the command service.

[0261] - Appendix 6 A communication method performed by a terminal, comprising the steps of: receiving a first message from a reader device that belongs to either an inventory service for managing the terminal or a command service for controlling the terminal; and transmitting a second message to the reader device in response to the first message, which includes information indicating the terminal's capability with respect to at least one of the inventory and the command.

[0262] This application is based on Japanese Patent Application No. 2025-049118, filed on March 24, 2025. All of its contents are included herein.

[0263] 1: NW 2: UE (Reader device) 3: AIoT device 11: AF 12: CN 12a: NEF 12b: AIoTF 12c: UDM 12d: UDR 12e: AMF 13: RAN 13a, 13b: Base station 31: Transmitting / receiving unit 31a: Transmitting unit 31b: Receiving unit 32: Storage unit 33: Control unit 41: Transmitting / receiving unit 41a: Transmitting unit 41b: Receiving unit 42: Storage unit 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 unit 2004 : Accelerator pedal 2005 : Brake pedal 2006 : Shift lever 2007 : Front wheel 2008 : Rear wheel 2009 : Axle 2010 : Electronic control unit 2012 : Information service unit 2013 : Communication module 2021-2029 : Sensor 2030 : Driving support system unit 2031 : Microprocessor 2032 : Memory 2033 : Communication port

Claims

1. A terminal comprising: a receiving unit that receives a first message from a reader device belonging to either an inventory service for managing the terminal or a command service for controlling the terminal; and a transmitting unit that, as a response to the first message, transmits a second message to the reader device that includes information indicating the terminal's capabilities with respect to at least one of the inventory and the command service.

2. The terminal according to claim 1, wherein the first message is a paging message used for the inventory which is performed before the command, and the transmitting unit transmits the second message as a response to the paging message, the second message containing information indicating whether the terminal supports only the inventory among the inventory and the command.

3. The terminal according to claim 1, wherein the first message is a command message used in the command, and if the terminal does not support the command, the transmitting unit transmits the second message, which includes the information indicating that the terminal does not support the command, as a response to the command message.

4. In cases where the command has multiple types defined, the transmitting unit transmits a second message containing information indicating the terminal's capability with respect to a specific type of command among the multiple types, according to any one of claims 1 to 3.

5. A communication device comprising: a transmitting unit that transmits a first message to a terminal belonging to either an inventory service for managing a terminal or a command service for controlling the terminal; and a receiving unit that receives a second message from the terminal as a response to the first message, the second message containing information indicating the terminal's capability with respect to at least one of the inventory and the command service.

6. A communication method performed by a terminal, comprising: receiving a first message from a reader device that belongs to either an inventory service for managing the terminal or a command service for controlling the terminal; and transmitting a second message to the reader device in response to the first message, which includes information indicating the terminal's capability with respect to at least one of the inventory and the command services.

Images