Network node and communication method

Abstract

This allows for the temporary disabling of IoT devices. [Solution] The network node includes a transmission unit that sends a first message to another network node, which is a message requesting communication with an IoT (Internet of Things) device and is addressed to one or more IoT devices; and a control unit that, before sending the first message, determines, based on a management database, which IoT devices among the one or more IoT devices are in a first state in which communication is disabled, and excludes the IoT devices in the first state from being the destination of the first message.

Description

Technical Field

[0001] The present disclosure relates to a network node and a communication method used in a wireless communication system.

Background Art

[0002] In 3GPP (Registered Trademark. The same applies hereinafter) (3rd Generation Partnership Project), which is a standardization project for wireless communication systems, the realization of services using ambient power-enabled devices has been studied (for example, see Non-Patent Document 1). Such devices are referred to as AIoT (Ambient Internet of Things) devices.

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

[0004] Compared with IoT devices already introduced in the 3GPP standard, such as NB-IoT (Narrow Band Internet of Things) devices and eMTC (enhanced Machine-Type Communication) devices, the AIoT device may have low complexity, small size, low capabilities, and low power consumption. The AIoT device may be maintenance-free and may have a long lifespan.

Prior Art Documents

Non-Patent Documents

[0005]

Non-Patent Document 1

[0006] When a large number of AIoT devices are connected to a network, there is a concern that the sheer volume of AIoT devices responding to messages from the network may cause excessive signaling. This issue can also arise with IoT devices other than AIoT devices (e.g., NB-IoT devices and eMTC devices).

[0007] Therefore, this disclosure provides a network node and a communication method that can temporarily disable IoT devices. [Means for solving the problem]

[0008] The technology of this disclosure provides a network node having: a transmission unit that sends a first message to another network node, which is a message requesting communication with an IoT (Internet of Things) device and is addressed to one or more IoT devices; and a control unit that, before sending the first message, determines, based on a management database, which of the one or more IoT devices is in a first state in which communication is disabled, and excludes the IoT devices in the first state from being the destination of the first message.

[0009] Furthermore, the technology of this disclosure provides a network node having: a storage unit that stores information for each IoT (Internet of Things) device indicating whether or not it is in a first state in which communication is temporarily disabled; a receiving unit that receives a message from another network node to inquire about the IoT device in the first state; and a transmitting unit that sends a message to the other network node to notify about the IoT device in the first state based on the stored information.

[0010] Furthermore, the present disclosure provides a communication method performed by a network node, comprising the steps of: determining, based on a management database, which IoT devices among the one or more IoT devices are in a first state in which communication will be disabled, before sending a request message to one or more IoT devices to another network node, requesting communication with IoT devices; and excluding the IoT devices in the first state from the destination of the request message. [Effects of the Invention]

[0011] According to the disclosed technology, it is possible to provide a network node and communication method that can temporarily disable IoT devices. [Brief explanation of the drawing]

[0012] [Figure 1] This figure shows an example configuration of a wireless communication system according to the embodiment. [Figure 2] This is a diagram illustrating the operation of the comparative example. [Figure 3] This is a diagram illustrating the management operations related to temporary deactivation according to the embodiment. [Figure 4] This figure shows an example of information stored and managed by the UDR according to this embodiment. [Figure 5] This diagram shows the inventory operation according to the embodiment. [Figure 6] This figure shows an example of the functional configuration of AIoTF according to the embodiment. [Figure 7] This figure shows an example of the functional configuration of a UDR according to the embodiment. [Figure 8] This figure shows an example of the temporary deactivation operation according to the embodiment. [Figure 9] This figure shows an example of the operation of the inventory according to the present invention. [Figure 10] This figure shows an example of the activation process according to the embodiment. [Figure 11]This is a diagram for explaining Modification Example 1 of the embodiment. [Figure 12] This is a diagram for explaining Modification Example 2 of the embodiment. [Figure 13] This is a diagram for explaining Modification Example 3 of the embodiment. [Figure 14] This is a diagram showing an example of the hardware configuration of each communication entity according to the embodiment. [Figure 15] This is a diagram showing an example of the configuration of a vehicle according to the embodiment.

Mode for Carrying Out the Invention

[0013] Hereinafter, a wireless communication system according to the present embodiment will be described with reference to the drawings. In the operation of the wireless communication system, existing technologies are used as appropriate. The existing technology is, for example, a communication method based on a 3GPP standard such as existing 5G / NR (New Radio). The existing technology is not limited to 5G / NR, and may include methods such as 4G / LTE (Long Term Evolution) and LTE-Advanced, or may include a wireless LAN (Local Area Network).

[0014] The embodiments described below are examples and are not limited to the following embodiments. For example, in the following embodiments, a wireless communication system having an AIoT device (also referred to as an "AIoT system") will be mainly described. However, the wireless communication system may have other IoT devices (for example, NB-IoT devices, eMTC devices, etc.) instead of or in addition to the AIoT device. That is, the wireless communication system of the present disclosure is applicable not only to AIoT devices but also to other IoT devices. In the description of the following embodiments, the term "AIoT device" may be used interchangeably with the term "IoT device".

[0015] (1) Configuration of the wireless communication system FIG. 1 is a diagram showing a configuration example of the wireless communication system according to the present embodiment.

[0016] The wireless communication system according to this embodiment comprises 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 referred to as an AIoT system. NW1 may be a 5G network or a 6G network, but in the following description of the embodiments, the case where NW1 is a 5G network will be mainly assumed.

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

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

[0019] AF11 is a network node that has the functionality to control applications. AF11 is connected to CN12. AF11 may also be an external node located outside of CN12, such as an external application server.

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

[0021] In this embodiment, CN12 includes a Network Exposure Function (NEF) 12a, an AIoT Function (AIoTF) 12b, an AIoT Data Management (AIoTDM) 12c, a User Data Repository (UDR) 12d, and an Access and Mobility Management Function (AMF) 12e.

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

[0023] AIoTF12b is a network node that provides functions for managing and controlling AIoT services (also referred to as "AIoT operations") using AIoT device 3. AIoTF12b may be integrated with AMF12e. Such an AMF12e may be an AMF dedicated to AIoT services. Alternatively, AIoTF12b may be a separate network node from AMF12e and communicate with RAN13 via AMF12e. Details of AIoTF12b will be described later.

[0024] AIoTDM12c is a network node that functions as a front-end for UDR12d and provides an interface with other network nodes. AIoTDM12c mediates communication between AIoTF12b and UDR12d. AIoTDM12c may be a network node with similar functionality to an existing UDM (Unified Data Management). However, CN12 does not necessarily have to have AIoTDM12c. For example, if UDR12d is a network node dedicated to AIoT services, communication between AIoTF12b and UDR12d may occur without going through AIoTDM12c.

[0025] UDR12d is a network node that provides the functionality to store and manage subscriber data related to UE2. UDR12d stores and manages subscriber data, such as subscriber profiles and subscriber status. UDR12d provides, updates, or deletes stored data in response to requests from other network nodes.

[0026] In this embodiment, UDR12d has the function of storing and managing data related to AIoT device 3. UDR12d may be an existing UDR with the added function of storing and managing data related to AIoT device 3. Alternatively, UDR12d may be an AIoT-dedicated UDR specifically for storing and managing data related to AIoT device 3.

[0027] In this embodiment, AIoTDM12c and UDR12d constitute a management database 12A for storing and managing data related to the AIoT device 3. If AIoTDM12c is not present, UDR12d alone may constitute the management database 12A.

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

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

[0030] RAN13 has multiple base stations 13a and 13b. In the illustrated example, RAN13 has base station 13a which operates as a Reader and base station 13b which performs wireless communication with UE2 which operates as a Reader. A Reader is a device that supports communication with AIoT device 3. Base station 13a performs wireless communication with AIoT device 3a. UE2 performs wireless communication with AIoT device 3b. Base station 13b which operates as a Reader is referred to as RAN Reader, and UE2 which operates as a Reader is referred to as UE Reader. The air interface between the Reader and AIoT device 3 is referred to as AIoT air interface.

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

[0032] UE2 can be a device such as a smartphone, mobile phone, tablet, wearable device, or communication module. A UE2 that is a UE Reader may also be a device dedicated solely to reading.

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

[0034] For example, one use case for AIoT device 3 is inventory management. In this use case, it is expected that the status of goods and materials can be grasped in real time based on location information and sensor information transmitted by AIoT device 3 within the warehouse.

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

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

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

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

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

[0040] Inventory: The objective is to extract and / or discover one or more AIoT devices 3. The inventory allows the Reader to detect AIoT devices 3 present in its vicinity and collect information about them. Unlike UE2, AIoT devices 3 are not always connected to NW1. By using the inventory function, NW1 can obtain information about AIoT devices 3 (device ID, status, measured values, etc.) at the time needed.

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

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

[0043] 2) Broadcast by Reader: The Reader broadcasts an inventory message containing information (such as the device ID) to identify the AIoT device 3 to be inventoryed.

[0044] 3) Response of AIoT device 3: AIoT device 3 that matches the broadcasted identification information responds to the Reader, for example, by random access.

[0045] 4) Information gathering: The Reader collects the necessary information from the responding AIoT device 3.

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

[0047] ·command: For example, this involves reading, writing to, controlling, disabling, or enabling one or more AIoT devices 3. Details on disabling and enabling AIoT devices 3 will be described later.

[0048] The identifier (device ID) of AIoT device 3 can be any information that uniquely identifies AIoT device 3, such as EPC (Electronic Product Code), MAC address, or serial number. If AIoT device 3 can implement a SIM (Subscriber Identity Module) card or eSIM, the identifier of AIoT device 3 may be SUCI (Subscriber Concealed Identifier) / SUPI (Subscription Permanent Identifier).

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

[0050] In the Topology 1 architecture, the AIoT device 3 is connected to the CN 12 via the base station 13b, which is a RAN node. The base station 13b is an AIoT-compatible base station, and may be, for example, an AIoT-specific base station (AIoT-specific gNB). In other words, in Topology 1, the base station 13b functions as a Reader.

[0051] In the Topology 2 architecture, the AIoT device 3 is connected to CN12 via UE2. In other words, in Topology 1, UE2 functions as a Reader.

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

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

[0054] (2) Operation of the wireless communication system The operation of the wireless communication system according to this embodiment will be described.

[0055] AIoT devices 3 may be deployed at high density, and NW1 may accommodate a large number of AIoT devices. For example, an operator may deploy a large number of AIoT devices 3 on behalf of a customer using AIoT services. As a result, there is a concern that a large number of AIoT devices will respond to messages from NW1 (e.g., triggers in inventory), causing excessive signaling.

[0056] To address these challenges, it is conceivable to disable some of the AIoT devices 3. For example, a customer could request CN12 via AF11 to temporarily disable several AIoT devices 3.

[0057] Here, disabling AIoT device 3 may mean disabling communication of AIoT device 3. For example, disabling communication of AIoT device 3 may mean disabling RF transmission of AIoT device 3. Here, RF transmission of AIoT device 3 may be backscatter transmission or active transmission. Note that the term "disable" may be used interchangeably with the term "deactivate". Similarly, the term "enable" may be used interchangeably with the term "activate".

[0058] For example, disabling AIoT device 3 may mean disabling the ability of one or more AIoT devices 3 that are currently capable of transmitting RF signals to transmit RF signals. On the other hand, enabling AIoT device 3 may mean enabling the ability of one or more AIoT devices 3 that are currently unable to transmit RF signals to transmit RF signals.

[0059] There are two ways to disable AIoT device 3: permanent disable and temporary disable. Permanent disable permanently disables AIoT device 3, preventing it from ever functioning again. Temporary disable, on the other hand, temporarily disables AIoT device 3, allowing it to be re-enabled.

[0060] The following description of the embodiments primarily assumes temporary disabling and explains the operation for temporarily disabling the AIoT device 3. However, it is not limited to temporary disabling, and the operation according to the following embodiments may also be applied to permanent disabling.

[0061] Furthermore, the state of AIoT device 3 that is permanently or temporarily disabled will be referred to as the "disabled state" or "first state," the state of AIoT device 3 that is permanently disabled will be referred to as the "permanently disabled state," and the state of AIoT device 3 that is temporarily disabled will be referred to as the "temporarily disabled state." On the other hand, the state of AIoT device 3 that is enabled will be referred to as the "enabled state" or "second state."

[0062] (2.1) Comparative Examples Prior to describing the operation according to this embodiment, an example of an operation in which the AIoT device 3 is temporarily disabled will be explained.

[0063] Figure 2 is a diagram illustrating the operation of the comparative example. In the comparative example, in order to temporarily disable AIoT device 3, a disablement message (also called a "disable command") is sent from NW1 to AIoT device 3.

[0064] In the comparative example, firstly, AIoTF12b sends a disabling request to RAN13 to disable multiple AIoT devices 3 in response to a disabling request from AF11. In the illustrated example, the AIoT devices 3 to be disabled are AIoT devices 3#1 to 3#3. Note that the illustration shows an example where RAN13 has base stations 13#1 to 13#3.

[0065] Secondly, RAN13 sends a disable command to AIoT devices 3#1 to 3#3. However, because AIoT device 3 does not have advanced communication capabilities, or because AIoT device 3 is in a poor communication environment, the disable command may not reach some AIoT devices 3. In the illustrated example, the disable command reaches AIoT devices 3#1 and 3#2, but not AIoT device 3#3. As a result, AIoT device 3#3 remains enabled.

[0066] Thus, in the operation of the comparative example, the reachability of the disable command is not guaranteed, raising concerns that NW1 may not be able to disable at least some of the multiple AIoT devices 3 that it intends to disable.

[0067] Furthermore, if both permanent and temporary disabling are supported, the behavior of the example device requires the use of different disabling commands for permanent and temporary disabling. However, because AIoT device 3 is low complexity, it may not be able to distinguish between permanent and temporary disabling. Also, adding logic to distinguish between permanent and temporary disabling to AIoT device 3 would increase its complexity. This raises concerns about supporting both temporary and permanent disabling.

[0068] Furthermore, in the comparative example's operation, enabling AIoT device 3, which has been temporarily disabled, requires sending an enable command from NW1 to AIoT device 3. Here, since the reachability of the enable command is not guaranteed, there is a concern that NW1 may not be able to enable AIoT device 3 as intended. Also, even if an AIoT device is already disabled, modifications to the air interface may be necessary to know when it will be enabled again. Moreover, if AIoT device 3 supports logic for being enabled again after temporary disabling, the complexity of AIoT device 3 will increase.

[0069] (2.2) Operation according to the embodiment The operation according to this embodiment is capable of solving the problems in the operation of the comparative example described above.

[0070] In this embodiment, instead of NW1 sending disable and / or enable commands to AIoT devices 3, NW1 manages information on whether each AIoT device 3 is in a disabled state (e.g., temporarily disabled). NW1 then controls not to send messages to AIoT devices 3 that are managed as disabled. For example, NW1 does not trigger AIoT devices 3 that are managed as disabled in the inventory. As a result, AIoT devices 3 that are managed as disabled will not initiate communication in response to a trigger.

[0071] Thus, the temporary disabling of AIoT device 3 is handled on the NW1 side, and this process is transparent to AIoT device 3. Therefore, it is not necessary to implement additional logic in AIoT device 3 to support temporary disabling.

[0072] This type of temporary disabling via network management eliminates the need to send disabling and / or enabling commands to AIoT device 3, thus solving the problem of not being able to guarantee the reachability of disabling and / or enabling commands.

[0073] Furthermore, since there is no need to use different disable commands for permanent disabling and temporary disabling, it is not necessary to add logic to AIoT device 3 to distinguish between permanent and temporary disabling, thus suppressing the increase in complexity of AIoT device 3.

[0074] Furthermore, since it is not necessary to add logic to AIoT device 3 to support the activation command, the increase in complexity of AIoT device 3 can be suppressed.

[0075] Therefore, it becomes possible to temporarily disable AIoT device 3 without adding any further complexity to AIoT device 3.

[0076] Figure 3 is a diagram illustrating the management operations related to temporary disabling according to this embodiment.

[0077] In this embodiment, firstly, in response to a temporary deactivation request from AF11, AIoTF12b sends a device status update request to AIoTDM12c to register AIoT device 3 as temporarily deactivated. Here, both the temporary deactivation request and the device status update request include the device ID of AIoT device 3 to be temporarily deactivated.

[0078] Secondly, in response to a device status update request from AIoTF12b, AIoTDM12c sends a device profile update request to UDR12d that includes the device ID of the AIoT device 3 to be temporarily disabled.

[0079] Thirdly, UDR12d manages AIoT device 3, specified in the device profile update request, as a temporarily disabled state.

[0080] Figure 4 shows an example of the information stored and managed by the UDR12d according to this embodiment.

[0081] In the illustrated example, UDR12d stores and manages the set of "Device ID" and "Temporarily Disabled State = True" for AIoT device 3. For example, the "Device ID" is the Permanent Ambient IoT Device identifier. The Permanent Ambient IoT Device ID is an ID unique to AIoT device 3.

[0082] Furthermore, in the illustrated example, the AIoT device profile managed by UDR12d for each AIoT device 3 is extended to indicate whether the AIoT device 3 associated with the AIoT device ID is temporarily disabled. UDR12d maintains an AIoT device profile for each AIoT device 3, and this profile is configured to include a "temporarily disabled state," which is an information element (also called a "Data key") that can be True or False.

[0083] In this way, NW1 manages information on whether each AIoT device 3 is in a temporarily disabled state, specifically the Data key "Temporarily Disabled State" in the AIoT device profile. This eliminates the need for NW1 to send disable commands and / or enable commands to each AIoT device 3 regarding the temporarily disabled state.

[0084] In this embodiment, NW1 (UDR12d) manages information on whether each AIoT device 3 is in a temporarily disabled state, but NW1 (UDR12d) does not need to manage information on whether each AIoT device 3 is in a permanently disabled state. When permanently disabling an AIoT device 3, NW1 may send a disabling command to the AIoT device 3. The AIoT device 3 only needs to support a disabling command for permanent disabling, and does not need to support a disabling command for temporary disabling. In this case, permanent disabling is the only type of disabling that the AIoT device 3 needs to implement.

[0085] Alternatively, NW1 (UDR12d) may store and manage information regarding whether each AIoT device 3 is temporarily disabled or not, and information regarding whether it is permanently disabled or not. In the following description of the embodiment, an example will be described in which NW1 (UDR12d) stores and manages information regarding whether each AIoT device 3 is temporarily disabled or not, but does not store and manage information regarding whether it is permanently disabled or not.

[0086] Figure 5 is a diagram illustrating the inventory operation according to this embodiment.

[0087] In this embodiment, firstly, in response to an inventory request from AF11, AIoTF12b queries AIoTDM12c for the temporary disabled state of one or more AIoT devices 3 to be inventoryed (device status query). Here, each of the inventory request and the device status query includes the device ID of each AIoT device 3 to be inventoryed. In the illustrated example, each of the inventory request and the device status query includes the respective device IDs of AIoT devices 3#1 to 3#3.

[0088] Secondly, in response to a device status query from AIoTF12b, AIoTDM12c sends a device status query to UDR12d that includes the device ID of each AIoT device 3 to be included in the inventory.

[0089] Thirdly, UDR12d sends information about the temporary disabled state of each AIoT device 3 specified in the device status query to AIoTDM12c as a response to the query, based on the AIoT device profile it manages. In the illustrated example, the response includes "Temporarily disabled state = False" for AIoT devices 3#1 and 3#2, and "Temporarily disabled state = True" for AIoT device 3#3. In other words, of AIoT devices 3#1 to 3#3, AIoT devices 3#1 and 3#2 are in an enabled state, and AIoT device 3#3 is in a temporarily disabled state.

[0090] Fourth, AIoTDM12c notifies (transfers) the temporary disabled state information received from UDR12d to AIoTF12b.

[0091] Fifth, AIoTF12b determines (identifies) which of the one or more AIoT devices 3 to be inventoryed is managed as being in a temporarily disabled state, based on the temporary disabled state information notified by AIoTDM12c. For example, AIoTF12b determines that AIoT device 3#3 is in a temporarily disabled state based on the fact that "temporarily disabled state = True" for AIoT device 3#3.

[0092] Sixth, AIoTF12b sends an inventory request to RAN13 excluding AIoT device 3, which is managed as temporarily disabled, from the destination. As a result, RAN13 sends an inventory message to AIoT device 3, excluding AIoT device 3, which is managed as temporarily disabled, from the destination. In the illustrated example, the inventory message is sent to AIoT devices 3#1 and 3#2, which are managed as enabled, but not to AIoT device 3#3, which is managed as disabled. As a result, AIoT devices 3#1 and 3#2 respond to RAN13, which is the Reader, but AIoT device 3#3 does not respond.

[0093] Thus, in this embodiment, NW1(AIoTF12b) verifies that AIoT device 3 is not temporarily disabled before triggering a request for an AIoT service (in this case, inventory). For example, NW1(AIoTF12b) decides whether to allow AIoT device 3 to be the destination for inventory based on the temporary disable status managed by UDR12d.

[0094] Therefore, NW1 (AIoTF12b) controls the system so as not to send messages (triggers) to AIoT device 3, which is managed as being in a temporarily disabled state. As a result, AIoT device 3, which is managed as being in a disabled state, will not initiate communication in response to triggers. Thus, the temporary disabling of AIoT device 3 is handled on the NW1 side, and this process is transparent to AIoT device 3.

[0095] (3) Equipment configuration The respective device configurations of AIoTF12b and UDR12d according to this embodiment will be described below.

[0096] (3.1) Configuration of AIoTF Figure 6 shows an example of the functional configuration of AIoTF12b according to this embodiment. However, the configuration shown in Figure 6 may be just one example of the hardware configuration of AIoTF12b. Each network node is assumed to have a configuration similar to that shown in Figure 6.

[0097] The AIoTF12b includes a transmitter 121b, a receiver 122b, a storage unit 123b, and a control unit 124b. This functional configuration (functional block) is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operation according to this embodiment.

[0098] The transmitting unit 121b includes the function of generating a signal to be transmitted to other network nodes and transmitting the signal by wire or wireless. The receiving unit 122b includes the function of receiving various signals transmitted from other network nodes and obtaining information from the received signals, for example, information from a higher layer. A transmitting and receiving unit (communication unit) including the transmitting unit 121b and the receiving unit 122b may be configured.

[0099] The memory unit 123b includes a storage device, which stores pre-configured setting information and other data in the storage device and reads it from the storage device as needed.

[0100] The control unit 124b performs processing to control the above-mentioned operations and the operations described later in AIoTF12b. The signal transmission function of the control unit 124b may be included in the transmission unit 121b, and the signal reception function of the control unit 124b may be included in the reception unit 122b.

[0101] In the AIoTF12b configured in this way, the transmitting unit 121b sends a first message to one or more AIoT devices 3 to another network node, which is a message requesting communication with the AIoT devices 3. Here, the "first message" may be the inventory request described above. The inventory request may be an AIoT Service Request message containing information indicating the inventory. Alternatively, the "first message" may be a read command (read message) or a write command (read message). The "other network node" may be a RAN node. The transmitting unit 121b may send the first message to the RAN node via the AMF12e, or it may send it to the RAN node without going through the AMF12e. The transmitting unit 121b may also send the first message to the Reader via one or more network nodes.

[0102] Before sending the first message, the control unit 124b determines, based on the management database 12A, which is in a first state (temporarily disabled state) where communication is temporarily disabled, and excludes AIoT devices 3 in the first state (temporarily disabled state) from being the destination of the first message. In other words, the control unit 124b designates only AIoT devices 3 in the second state (enabled state) as the destination of the first message.

[0103] In this embodiment, the management database 12A consists of AIoTDM 12c and UDR 12d (see Figure 1). However, assuming that AIoTDM 12c does not exist, the management database 12A consists of UDR 12d. As will be described in detail later, the management database 12A may be integrated with AIoTF 12b. Assuming that the management database 12A is integrated with AIoTF 12b, the management database 12A may be included in the storage unit 123b.

[0104] In this embodiment, the AIoTF 12b and the management database 12A are separate network nodes. Under these conditions, the transmitting unit 121b sends the above-mentioned device status query to the management database 12A, and the receiving unit 122b receives the response to the query from the management database 12A (see Figure 5).

[0105] Prior to this operation, the receiving unit 122b receives a second message from an external node indicating the AIoT device 3 that is required to be set to a first state (temporarily disabled state). Here, the second message is the temporary disable request mentioned above, and may be a message sent from AF11 (see Figure 3). The temporary disable request may be an AIoT Service Request message containing information indicating temporary disablement. The receiving unit 122b may receive the second message from AF11 via NEF12a. Alternatively, assuming that NEF12a does not exist, the receiving unit 122b may receive the second message from AF11 without going through NEF12a. The control unit 124b registers the AIoT device 3 indicated by the second message as the AIoT device 3 in the first state (temporarily disabled state) in the management database 12A.

[0106] Furthermore, the receiving unit 122b may receive a third message from an external node indicating an AIoT device 3 that is required to be set to a second state (enabled state) for enabling communication. Here, the third message is an enablement request and may be a message sent from AF11. The enablement request may be an AIoT Service Request message containing information indicating enablement. The receiving unit 122b may receive the third message from AF11 via NEF12a. Alternatively, assuming that NEF12a does not exist, the receiving unit 122b may receive the third message from AF11 without going through NEF12a. The control unit 124b registers the AIoT device 3 indicated by the third message as an AIoT device 3 in the second state (enabled state) in the management database 12A.

[0107] (3.2) UDR configuration Figure 7 shows an example of the functional configuration of UDR12d according to this embodiment. However, the configuration shown in Figure 7 may be just one example of the hardware configuration of UDR12d.

[0108] The UDR12d includes a transmitter 121d, a receiver 122d, a storage unit 123d, and a control unit 124d. This functional configuration (functional block) is merely an example. The names of the functional categories and functional units can be anything as long as they can perform the operation according to this embodiment.

[0109] The transmitting unit 121d includes the function of generating a signal to be transmitted to other network nodes and transmitting the signal by wire or wireless. The receiving unit 122d includes the function of receiving various signals transmitted from other network nodes and obtaining information from the received signals, for example, information from a higher layer. A transmitting and receiving unit (communication unit) including the transmitting unit 121d and the receiving unit 122d may be configured.

[0110] The memory unit 123d includes a storage device, which stores pre-configured setting information and other data in the storage device and reads it from the storage device as needed.

[0111] The control unit 124d performs processing to control the above-mentioned operations and the operations described later in the UDR 12d. The signal transmission function unit of the control unit 124d may be included in the transmission unit 121d, and the signal reception function unit of the control unit 124d may be included in the reception unit 122d.

[0112] In the UDR12d configured in this way, the storage unit 123d stores information for each AIoT device 3 indicating whether or not it is in the first state (temporarily disabled state). For example, the storage unit 123d stores the above-mentioned AIoT device profile for each AIoT device 3 (see Figure 4).

[0113] The receiving unit 122d receives a message from another network node inquiring about a device in a first state (temporarily disabled state). This message may be the device status query described above. In this embodiment, the receiving unit 122d receives the message from AIoTF 12b via AIoTDM 12c. However, assuming that AIoTDM 12c does not exist, the receiving unit 122d may receive the message from AIoTF 12b without going through AIoTDM 12c.

[0114] Then, based on the information (AIoT device profile) stored in the storage unit 123d, the transmission unit 121d sends a message to the other network node in response to the inquiry, notifying it about a device in the first state (temporarily disabled state). In this embodiment, the transmission unit 121d sends the message to the AIoTF 12b via the AIoTDM 12c. However, assuming that the AIoTDM 12c does not exist, the transmission unit 121d may send the message to the AIoTF 12b without going through the AIoTDM 12c.

[0115] (4) Examples Based on the above-described embodiment, an example of the operation of the wireless communication system will be explained.

[0116] (4.1) Example of temporary disabling operation Figure 8 shows an example of the temporary disabling operation according to this embodiment.

[0117] 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 device ID of each AIoT device 3 to be temporarily disabled, and the temporary disabled state = True.

[0118] In step S102, NEF12a forwards the AIoT Service Request message to AIoTF12b. AIoTF12b receives the AIoT Service Request message.

[0119] In step S103, AIoTF12b determines that it is performing a temporary disable operation based on the temporary disable status = True in the AIoT Service Request message received from NEF12a.

[0120] In step S104, AIoTF12b performs a service operation on AIoTDM12c to update the profile of each AIoT device 3 to be temporarily disabled. The service operation between AIoTF12b and AIoTDM12c may be performed by a new process such as Nadm_AIoT_ModifyProfile. In this embodiment, AIoTF12b sends an AIoT device profile update request message to AIoTDM12c. AIoTDM12c receives the AIoT device profile update request message. The AIoT device profile update request message includes the device ID of each AIoT device 3 to be temporarily disabled and the temporary disabled state = True.

[0121] In step S105, AIoTDM12c sends a Nudr_DM_Update Request message to UDR12d. UDR12d receives the Nudr_DM_Update Request message. Note that the Nudr_DM_Update Request message is an existing message. In this embodiment, the Nudr_DM_Update Request message includes the device ID of each AIoT device 3 to be temporarily disabled and the temporary disabled state = True. UDR12d updates the AIoT device profile to set the temporary disabled state corresponding to each device ID in the Nudr_DM_Update Request message to True.

[0122] In step S106, UDR12d sends a Nudr_DM_Update Response message to AIoTDM12c. AIoTDM12c receives the Nudr_DM_Update Response message. The Nudr_DM_Update Response message is an existing message. In this embodiment, the Nudr_DM_Update Response message includes information indicating the result of the processing in response to the Nudr_DM_Update Request message in step S105 (e.g., success or failure). For example, the Nudr_DM_Update Response message may include the device ID of each AIoT device 3 to be temporarily disabled and information indicating the processing result for each AIoT device 3 (e.g., success or failure).

[0123] In step S107, AIoTDM12c sends a service operation response message to AIoTF12b. AIoTF12b receives the service operation response message. In this embodiment, the service operation response message includes information indicating the result of the processing in response to the AIoT device profile update request in step S104 (e.g., success or failure). For example, the service operation response message may include the device ID of each AIoT device 3 to be temporarily disabled and information indicating the processing result for each AIoT device 3 (e.g., success or failure).

[0124] In step S108, AIoTF12b sends an AIoT Service Response message to NEF12a. NEF12a receives the AIoT Service Response message. In this embodiment, the AIoT Service Response message includes information indicating the result of the processing in response to the AIoT Service Request message in step S102 (e.g., success or failure). For example, the AIoT Service Response message may include the device ID of each AIoT device 3 to be temporarily disabled and information indicating the processing result for each AIoT device 3 (e.g., success or failure).

[0125] In step S109, NEF12a forwards the AIoT Service Response message to AF11. AF11 receives the AIoT Service Response message.

[0126] (4.2) Example of inventory operation Figure 9 shows an example of the operation of the inventory according to this embodiment.

[0127] In step S201, AF11 sends an AIoT Service Request message to NEF12a. NEF12a receives the AIoT Service Request message. The AIoT Service Request message includes the device ID of each AIoT device 3 to be inventoryed and "Inventory" as the AIoT operation. In this embodiment, the AIoT devices 3 to be inventoryed are assumed to be AIoT devices 3#1 and 3#2. Therefore, the AIoT Service Request message includes "AIoT device ID=#1" and "AIoT device ID=#2" as the device IDs of each AIoT device 3 to be inventoryed.

[0128] In step S202, NEF12a forwards the AIoT Service Request message to AIoTF12b. AIoTF12b receives the AIoT Service Request message. AIoTF12b decides to determine (verify) the temporary disabled state based on the "inventory" in the AIoT Service Request message.

[0129] In step S203, AIoTF12b performs a service operation on AIoTDM12c to derive (obtain, query) the temporary disabled status of each AIoT device 3 to be inventoryed. The service operation between AIoTF12b and AIoTDM12c may be performed by a new process such as Nadm_AIoT_GET(TemporaryDisableStatus). In this embodiment, AIoTF12b sends a temporary disabled status derivation request message to AIoTDM12c. AIoTDM12c receives the temporary disabled status derivation request message. The temporary disabled status derivation request message includes the device ID of each AIoT device 3 to be inventoryed and the temporary disabled status as a data key.

[0130] In step S204, AIoTDM12c sends a Nudr_DM_Query Request message to UDR12d to obtain (query) the temporary disabled status of each AIoT device 3 to be inventoryed. UDR12d receives the Nudr_DM_Query Request message. The Nudr_DM_Query Request message includes the device ID of each AIoT device 3 to be inventoryed and the temporary disabled status as a Data key. UDR12d obtains the temporary disabled status of each AIoT device 3 to be inventoryed based on the AIoT device profile it manages.

[0131] In step S205, UDR12d sends a Nudr_DM_Query Response message to AIoTDM12c to notify it of the temporary disabled state of each AIoT device 3 to be inventoryed. AIoTDM12c receives the Nudr_DM_Query Response message. The Nudr_DM_Query Response message includes the device ID of each AIoT device 3 to be inventoryed and the temporary disabled state associated with that device ID. In this embodiment, it is assumed that among the AIoT devices 3 to be inventoryed, AIoT device 3#1 is managed as a temporary disabled state and AIoT device 3#2 is managed as an enabled state. Therefore, the Nudr_DM_Query Response message includes the set "AIoT device ID=#1" and "temporarily disabled state #1=True" and the set "AIoT device ID=#2" and "temporarily disabled state #2=False".

[0132] In step S206, AIoTDM12c sends a service operation response message containing the contents of the Nudr_DM_Query Response message to AIoTF12b as a response to the request in step S203. AIoTF12b receives the service operation response message.

[0133] In step S207, AIoTF12b determines which AIoT device 3 among the AIoT devices 3 to be inventoryed is temporarily disabled, based on the content of the service operation response message. In this embodiment, AIoTF12b determines that of the AIoT devices 3#1 and 3#2 to be inventoryed, AIoTF12b determines that AIoT device 3#2 among the AIoT devices 3#1 and 3#2 to be inventoryed is enabled.

[0134] In step S208, AIoTF12b excludes AIoT device 3#1, which is temporarily disabled, from the list of AIoT devices 3 to be included in the inventory, from the destination of the AIoT Service Request message to RAN13. On the other hand, AIoTF12b designates AIoT device 3#2, which is enabled, from the list of AIoT devices 3 to be included in the inventory, as the destination of the AIoT Service Request message to RAN13.

[0135] In step S209, AIoTF12b sends an AIoT Service Request message to RAN13 to trigger the inventory. RAN13 receives the AIoT Service Request message. The AIoT Service Request message includes the device ID #2 of the destination (inventory target) AIoT device 3#2 and the word "inventory".

[0136] In this embodiment, the RAN node is the Reader, and the Reader is instructed to start the inventory. The RAN node may broadcast an inventory message containing the device ID #2 of the AIoT device 3#2 to be inventoryed. AIoT device 3#2 may respond to the inventory message. The RAN node may collect the necessary information from the responding AIoT device 3 and send the collected information to AIoTF12b. AIoTF12b may provide the collected information to AF11 via NEF12a.

[0137] Thus, in this embodiment, AIoTF12b verifies that AIoT device 3 is not temporarily disabled before triggering an AIoT service request to RAN13. Based on the temporary disabled state, AIoTF12b decides whether to allow or disallow AIoT device 3 as the target (destination).

[0138] In this embodiment, the operation when the AIoT Service Request message includes "inventory" (i.e., inventory operation) has been described. However, the operation described in this embodiment may also be applied to the operation when the AIoT Service Request message includes a "write" command (i.e., write operation), or to the operation when the AIoT Service Request message includes a "read" command (i.e., read operation).

[0139] (4.3) Example of activation operation Figure 10 shows an example of the activation operation according to this embodiment.

[0140] In step S301, AF11 sends an AIoT Service Request message to NEF12a. NEF12a receives the AIoT Service Request message. The AIoT Service Request message includes the device ID of each AIoT device 3 to be enabled, and the temporary disabled state = False.

[0141] In step S302, NEF12a forwards the AIoT Service Request message to AIoTF12b. AIoTF12b receives the AIoT Service Request message.

[0142] In step S303, AIoTF12b determines that it is in an enabled state based on the temporary disabled state = False in the AIoT Service Request message received from NEF12a.

[0143] In step S304, AIoTF12b performs a service operation on AIoTDM12c to update the profile of each AIoT device 3 to be enabled. The service operation between AIoTF12b and AIoTDM12c may be performed by a new process such as Nadm_AIoT_ModifyProfile. In this embodiment, AIoTF12b sends an AIoT device profile update request message to AIoTDM12c. AIoTDM12c receives the AIoT device profile update request message. The AIoT device profile update request message includes the device ID of each AIoT device 3 to be enabled and the temporary disabled state = False.

[0144] In step S305, AIoTDM12c sends a Nudr_DM_Update Request message to UDR12d. UDR12d receives the Nudr_DM_Update Request message. Note that the Nudr_DM_Update Request message is an existing message. In this embodiment, the Nudr_DM_Update Request message includes the device ID of each AIoT device 3 to be activated and the temporary disabled state = False. UDR12d updates the AIoT device profile to set the temporary disabled state corresponding to each device ID in the Nudr_DM_Update Request message to False.

[0145] In step S306, UDR12d sends a Nudr_DM_Update Response message to AIoTDM12c. AIoTDM12c receives the Nudr_DM_Update Response message. The Nudr_DM_Update Response message is an existing message. In this embodiment, the Nudr_DM_Update Response message includes information indicating the result of the processing in response to the Nudr_DM_Update Request message in step S305 (e.g., success or failure). For example, the Nudr_DM_Update Response message may include the device ID of each AIoT device 3 to be activated and information indicating the processing result for each AIoT device 3 (e.g., success or failure).

[0146] In step S307, AIoTDM12c sends a service operation response message to AIoTF12b. AIoTF12b receives the service operation response message. In this embodiment, the service operation response message includes information indicating the result of the processing in response to the AIoT device profile update request in step S304 (e.g., success or failure). For example, the service operation response message may include the device ID of each AIoT device 3 to be activated and information indicating the processing result for each AIoT device 3 (e.g., success or failure).

[0147] In step S308, AIoTF12b sends an AIoT Service Response message to NEF12a. NEF12a receives the AIoT Service Response message. In this embodiment, the AIoT Service Response message includes information indicating the result of the processing in response to the AIoT Service Request message in step S302 (e.g., success or failure). For example, the AIoT Service Response message may include the device ID of each AIoT device 3 to be activated and information indicating the processing result for each AIoT device 3 (e.g., success or failure).

[0148] In step S309, NEF12a forwards the AIoT Service Response message to AF11. AF11 receives the AIoT Service Response message.

[0149] (5) Example of change 1 Example 1 of the above embodiment will now be described.

[0150] The above embodiment described an example of temporarily disabling and enabling the AIoT device 3 from AF11. AF11 is typically operated by a customer, for example, rather than a network node operated by an operator. However, the use case is not limited to this example.

[0151] Figure 11 is a diagram illustrating a modified example of the embodiment 1.

[0152] In this example of modification, OAM14 updates the AIoT device profile in UDR12d to allow temporary disabling and enabling of AIoT device 3. This makes it possible to accommodate use cases where the operator needs to temporarily disable and enable AIoT device 3.

[0153] (6) Example of change 2 A second example of a modification of the above embodiment will now be described. Figure 12 is a diagram illustrating the second example of a modification of the embodiment.

[0154] In the above embodiment, an example was described in which CN12 has an AIoTDM12c, but CN12 does not necessarily have to have an AIoTDM12c. In this case, AIoTF12b communicates directly with UDR12d. Also, under the assumption that AIoTDM12c does not exist, the management database 12A consists of UDR12d.

[0155] (7) Example of change 3 A third modification example of the above embodiment will now be described. Figure 13 is a diagram illustrating the third modification example of the embodiment.

[0156] In this modified example, AIoTF12b and the management database 12A are configured as a single unit. That is, AIoTF12b stores and manages AIoT device profiles. In this configuration, AIoTDM12c can be omitted. Furthermore, the dedicated UDR12d for AIoT services may also be omitted.

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

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

[0159] For example, each communication entity in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 14 shows 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0214] 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 PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

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

[0216] 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 (1 ms) in existing LTE, 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.

[0217] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each terminal to allocate radio 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0235] (10) Note The features of the above-described embodiment are noted below.

[0236] • Note 1 A transmission unit that sends a first message to another network node, which is a message requesting communication with an IoT (Internet of Things) device and is addressed to one or more IoT devices, The system includes a control unit that, before sending the first message, determines, based on a management database, which of the one or more IoT devices is in a first state in which communication is disabled, and excludes the IoT device in the first state from being the destination of the first message. Network node.

[0237] • Appendix 2 The system further includes a receiving unit that receives a second message from an external node indicating an IoT device that is required to be in the first state, The control unit registers the IoT device indicated by the second message as an IoT device in the first state in the management database. The network node described in Appendix 1.

[0238] • Appendix 3 It further includes a receiving unit that receives a third message from an external node indicating an IoT device that is required to be put into a second state to enable communication, The control unit registers the IoT device indicated by the third message as the IoT device in the second state in the management database. The network node described in Appendix 2.

[0239] • Appendix 4 The aforementioned IoT device is an ambient IoT device, The first message is an inventory message addressed to multiple ambient IoT devices. A network node listed in any of the appendices 1-3.

[0240] • Appendix 5 A memory unit that stores information for each IoT (Internet of Things) device indicating whether or not it is in the first state where communication is temporarily disabled, A receiving unit that receives a message from another network node to inquire about the IoT device in the first state, The system includes a transmission unit that transmits a message to another network node to notify about the IoT device in the first state based on the stored information. Network node.

[0241] • Appendix 6 A communication method performed by a network node, Before sending a request message to another network node for communication with an IoT (Internet of Things) device, which is a request message addressed to one or more IoT devices, the process involves determining, based on a management database, which of the one or more IoT devices is in a first state where communication is disabled. The step of excluding the IoT device in the first state from the destination of the request message. Communication method. [Explanation of symbols]

[0242] 1: NW 2:UE 3: AIoT devices 12:CN 12a :NEF 12b: AIoTF 12c: AIoTDM 12d :UDR 12e :AMF 12A: Management Database 13: RAN 13a: Base station 13b:Base station 14: OAM 121b: Transmitter 121d: Transmitter 122b: Receiver 122d: Receiver 123b: Storage section 123d: Storage section 124b: Control Unit 124d: Control Unit 1001: Processor 1002: Storage device 1003 :Auxiliary storage device 1004: Communication device 1005: Input device 1006: Output device 1007: Bus 2001: Vehicle 2002: Drive unit 2003: Steering Department 2004: Accelerator pedal 2005: Brake pedal 2006: Shift lever 2007: Front wheel 2008: Rear wheel 2009: Axle 2010: Electronic Control Unit 2012: Information Services Department 2013: Communication module 2021-2029: Sensors 2030: Driver Support Systems Department 2031: Microprocessor 2032: Memory 2033: Communication port

Claims

1. A transmitting unit that sends a first message to another network node, which is a message requesting communication with an IoT (Internet of Things) device and is addressed to one or more IoT devices, The system includes a control unit that, before sending the first message, determines, based on a management database, which IoT devices among the one or more IoT devices are in a first state in which communication is disabled, and excludes the IoT devices in the first state from being the destination of the first message. Network node.

2. The system further includes a receiving unit that receives a second message from an external node indicating an IoT device that is required to be in the first state, The control unit registers the IoT device indicated by the second message as the IoT device in the first state in the management database. The network node according to claim 1.

3. The system further includes a receiving unit that receives a third message from an external node indicating an IoT device that is required to be put into a second state to enable communication, The control unit registers the IoT device indicated by the third message as the IoT device in the second state in the management database. The network node according to claim 2.

4. The IoT device is an ambient IoT device, The first message is an inventory message addressed to multiple ambient IoT devices. A network node according to any one of claims 1 to 3.

5. A storage unit that stores information for each IoT (Internet of Things) device indicating whether or not it is in the first state where communication is temporarily disabled, A receiving unit that receives a message from another network node to inquire about the IoT device in the first state, The system includes a transmission unit that transmits a message to another network node to notify about the IoT device in the first state based on the stored information. Network node.

6. A communication method performed by a network node, Before sending a request message to another network node for communication with an IoT (Internet of Things) device, which is addressed to one or more IoT devices, the process involves determining, based on a management database, which of the one or more IoT devices is in a first state where communication is disabled. The process includes the step of excluding the IoT device in the first state from the destination of the request message. Communication method.

Images