COMMUNICATION CONTROL METHOD, COMMUNICATION NODE, WIRELESS COMMUNICATION SYSTEM, PROGRAM, AND CHIPSET

Abstract

This communication control method according to one embodiment of the present invention is used in a wireless communication system. The communication control method includes a step in which a first communication node included in a network sends a prescribed message to a second communication node. In addition, the communication control method includes a step in which the second communication node sends, to the first communication node and in response to the receipt of a prescribed message, tag information read from a wireless tag.

Description

[Technical Field]

[0001] The present disclosure relates to a communication control method in a wireless communication system. [Background technology]

[0002] BACKGROUND ART Passive IoT is being discussed in the Third Generation Partnership Project (3GPP), a standardization project for mobile communication systems (see, for example, Non-Patent Documents 1 to 3).

[0003] Passive IoT, for example, is a technology that supports ultra-low cost and ultra-low power devices. [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] 3GPP contribution RP-212688 [Non-patent document 2] 3GPP contribution RP-213368 [Non-patent document 3] 3GPP contribution RP-213369 Summary of the Invention

[0005] A communication control method according to a first aspect is a communication control method in a wireless communication system. The communication control method includes a step in which a first communication node included in a network transmits a predetermined message to a second communication node. The communication control method also includes a step in which the second communication node transmits tag information read from a wireless tag to the first communication node in response to receiving the predetermined message.

[0006] A communication control method according to a second aspect is a communication control method in a wireless communication system. The communication control method includes a step in which a first communication node included in a network sets a second communication node to monitor a wireless tag. The communication control method also includes a step in which the second communication node periodically reads tag information from the wireless tag in accordance with the setting. The communication control method further includes a step in which the second communication node transmits predetermined tag information to the first communication node when tag information read from the wireless tag at a first timing differs from tag information read from the wireless tag at a second timing following the first timing. Here, the predetermined tag information is either difference information indicating a difference between the tag information read at the first timing and the tag information read at the second timing, or tag information read at the second timing.

[0007] A communication control method according to a third aspect is a communication control method in a wireless communication system. The communication control method includes a step of reading tag information from a wireless tag by a user equipment in response to detection of a predetermined event. The communication control method also includes a step of transmitting the tag information to a communication node included in a network by the user equipment. Here, the predetermined event is any one of a Registration Area Update, a Tracking Area Update, a RAN-based Notification Area Update, a handover, an RRC connection reestablishment, an RRC connection resume, and an RRC setup.

[0008] A communication control method according to a fourth aspect is a communication control method in a wireless communication system. The communication control method includes a step in which a first communication node included in a network instructs a second communication node to process a wireless tag. The communication control method also includes a step in which the second communication node processes the wireless tag in accordance with the instruction. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a wireless communication system according to the first embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of a UE (user equipment) according to the first embodiment. [Figure 3] FIG. 3 is a diagram illustrating an example configuration of a gNB (base station) according to the first embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of the configuration of the wireless tag according to the first embodiment. [Figure 5] FIG. 5 is a diagram illustrating an example of the configuration of a protocol stack related to a user plane according to the first embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of the configuration of a protocol stack related to the control plane according to the first embodiment. [Figure 7] FIG. 7 is a diagram for explaining a problem of the passive IoT according to the first embodiment. [Figure 8] 8(A) and 8(B) are diagrams for explaining scenario a according to the first embodiment. [Figure 9] 9(A) to 9(C) are diagrams for explaining scenario b according to the first embodiment. [Figure 10] FIG. 10 is a diagram for explaining scenario c according to the first embodiment. [Figure 11] FIG. 11 is a diagram illustrating an example of operation according to the first embodiment. [Figure 12] FIG. 12 is a diagram illustrating an example of operation according to the second embodiment. [Figure 13] FIG. 13 is a diagram illustrating an example of operation according to the third embodiment. [Figure 14] FIG. 14 is a diagram illustrating an example of operation according to the fourth embodiment. [Figure 15] FIG. 15 is a diagram illustrating an example of operation according to the fifth embodiment. [Figure 16] FIG. 16 shows an example of operation according to the sixth embodiment. [Figure 17]FIG. 17 is a diagram illustrating an example of operation according to the seventh embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of operation according to the eighth embodiment. [Figure 19] FIG. 19 is a diagram illustrating an example of operation according to the ninth embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] One aspect aims to enable a network or a communication node to appropriately communicate with a wireless tag in a wireless communication system.

[0011] A wireless communication system according to an embodiment will be described with reference to the drawings. In the description of the drawings, the same or similar parts are denoted by the same or similar reference numerals.

[0012] [First embodiment]

[0013] (Example of wireless communication system configuration) FIG. 1 is a diagram illustrating an example of the configuration of a wireless communication system according to the first embodiment. The wireless communication system 1 includes a mobile communication system that is a 3GPP standard 5th Generation System (5GS). In the following, the mobile communication system will be described using 5GS as an example, but an LTE (Long Term Evolution) system may also be applied at least partially. Furthermore, a sixth generation (6G) system or later system may also be applied at least partially as the mobile communication system. Note that the wireless communication system 1 may be a mobile communication system.

[0014] The wireless communication system 1 includes a user equipment (UE) 100, a 5G radio access network (NG-RAN: Next Generation Radio Access Network) 10, a 5G core network (5GC: 5G Core Network) 20, and an RF (Radio Frequency) tag 300. Hereinafter, the 5GC 20 may be simply referred to as the core network (CN) 20.

[0015] The UE 100 is a mobile wireless communication device. The UE 100 may be any device that is used by a user. The UE 100 may be, for example, a mobile phone terminal (including a smartphone), a tablet terminal, a laptop PC, a communication module (including a communication card or a chipset), a sensor or a device provided in a sensor, a vehicle or a device provided in a vehicle (Vehicle UE), or an aircraft or a device provided in an aircraft (Aerial UE).

[0016] The NG-RAN 10 includes a base station (called "gNB" in the 5G system) 200. The gNBs 200 are connected to each other via an Xn interface, which is an interface between base stations. The gNB 200 manages one or more cells. The gNB 200 performs wireless communication with a UE 100 that has established a connection with its own cell. The gNB 200 has a radio resource management (RRM) function, a routing function for user data (hereinafter simply referred to as "data"), and a measurement control function for mobility control and scheduling. The term "cell" is used to indicate the smallest unit of a wireless communication area. The term "cell" is also used to indicate a function or resource for wireless communication with a UE 100. One cell belongs to one carrier frequency (hereinafter simply referred to as "frequency").

[0017] In addition, gNBs can also connect to the Evolved Packet Core (EPC), which is the LTE core network. LTE base stations can also connect to 5GC. LTE base stations and gNBs can also be connected via a base station-to-base station interface.

[0018] The 5GC20 includes an Access and Mobility Management Function (AMF) 30 and a User Plane Function (UPF). The AMF 30 performs various mobility controls for the UE 100. The AMF 30 manages the mobility of the UE 100 by communicating with the UE 100 using NAS (Non-Access Stratum) signaling. The UPF controls data forwarding. The AMF 30 and the UPF are connected to the gNB 200 via an NG interface, which is an interface between a base station and a core network.

[0019] The RF tag (or wireless tag; hereinafter, sometimes referred to as "wireless tag") 300 is a wireless communication device capable of wireless communication with the UE 100 or the gNB 200. The wireless tag 300 is also an information medium that uses radio waves or electromagnetic fields to write data to an internal memory and read data from the memory. The wireless tag 300 is, for example, an extremely small, thin, lightweight, and low-complexity IoT (Internet of Things) device.

[0020] (Example of UE configuration) 2 is a diagram illustrating an example of the configuration of a UE 100 (user equipment) according to the first embodiment. The UE 100 includes a receiving unit 110, a transmitting unit 120, and a control unit 130. The UE 100 may include a reader / writer 140. The receiving unit 110 and the transmitting unit 120 configure a wireless communication unit that performs wireless communication with the gNB 200.

[0021] The receiving unit 110 performs various types of reception under the control of the control unit 130. The receiving unit 110 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 130.

[0022] The transmitting unit 120 performs various transmissions under the control of the control unit 130. The transmitting unit 120 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 130 into a radio signal and transmits it from the antenna.

[0023] The control unit 130 performs various controls and processes in the UE 100. Such processes include processes in each layer, which will be described later. The control unit 130 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processes by the processor. The processor may include a baseband processor and a CPU (Central Processing Unit). The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals. The CPU executes programs stored in the memory to perform various processes. In the example shown below, the operations or processes in the UE 100 may be performed by the control unit 130.

[0024] The reader / writer 140 includes an RFID (Radio Frequency Identifier) ​​antenna 141. The reader / writer 140 communicates with the wireless tag 300 via the RFID antenna 141 under the control of the control unit 130. The reader / writer 140 communicates with the wireless tag 300 using RFID technology. RFID technology is a technology for writing data to the wireless tag 300 and reading data from the wireless tag 300 in a contactless manner using radio waves or an electromagnetic field. The reader / writer 140 can also generate power for the wireless tag 300 using the radio waves or electromagnetic field transmitted from the RFID antenna 141. The UE 100 can wirelessly communicate with the wireless tag 300 via the reader / writer 140. Note that the reader / writer 140 may have only a reader function and not a writer function.

[0025] The reader / writer 140 can also perform wireless communication with the wireless tag 300 using a communication protocol conforming to 3GPP. In this case, instead of the RFID antenna 141, the reader / writer 140 may include an antenna capable of transmitting and receiving wireless signals at frequencies used in 3GPP. The reader / writer 140 can also perform wireless communication with the wireless tag 300 using backscattering (or backward scattering). In this case, the reader / writer 140 may include an antenna capable of transmitting and receiving frequency signals used in backscattering. Details of backscattering will be described later.

[0026] (Example of gNB configuration) 3 is a diagram illustrating an example of the configuration of a gNB200 (base station) according to the first embodiment. The gNB200 includes a transmitter 210, a receiver 220, a controller 230, and a backhaul communication unit 240. The gNB200 may include a reader / writer 250. The transmitter 210 and the receiver 220 constitute a wireless communication unit that performs wireless communication with the UE100. The backhaul communication unit 240 constitutes a network communication unit that performs communication with the CN20.

[0027] The transmission unit 210 performs various transmissions under the control of the control unit 230. The transmission unit 210 includes an antenna and a transmitter. The transmitter converts a baseband signal (transmission signal) output by the control unit 230 into a radio signal and transmits it from the antenna.

[0028] The receiving unit 220 performs various types of reception under the control of the control unit 230. The receiving unit 220 includes an antenna and a receiver. The receiver converts a radio signal received by the antenna into a baseband signal (received signal) and outputs the baseband signal to the control unit 230.

[0029] The control unit 230 performs various controls and processes in the gNB 200. Such processes include processes for each layer, which will be described later. The control unit 230 includes at least one processor and at least one memory. The memory stores programs executed by the processor and information used in the processes by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation / demodulation and encoding / decoding of baseband signals, etc. The CPU executes programs stored in the memory to perform various processes. In the example shown below, the operations or processes in the gNB 200 may be performed by the control unit 230.

[0030] The backhaul communication unit 240 is connected to neighboring base stations via an Xn interface, which is an interface between base stations. The backhaul communication unit 240 is connected to the AMF 30 / UPF via an NG interface, which is an interface between a base station and a core network. Note that the gNB 200 may be configured (i.e., functionally divided) with a CU (Central Unit) and a DU (Distributed Unit), and both units may be connected via an F1 interface, which is a fronthaul interface.

[0031] The reader / writer 250 includes an RFID antenna 251. Under the control of the control unit 230, the reader / writer 250 communicates with the wireless tag 300 via the RFID antenna 251. The reader / writer 250 writes data to the wireless tag 300 or reads data from the wireless tag 300 in a contactless manner using radio waves or an electromagnetic field transmitted from the RFID antenna 251. The reader / writer 250 can also generate power in the wireless tag 300 using the radio waves or an electromagnetic field transmitted from the RFID antenna 251. The gNB 200 can wirelessly communicate with the wireless tag 300 via the reader / writer 250. Note that the reader / writer 250 may have only a reader function and no writer function.

[0032] The reader / writer 250 can also perform wireless communication with the wireless tag 300 using a communication protocol conforming to 3GPP. In this case, instead of the RFID antenna 251, the reader / writer 250 may include an antenna capable of transmitting and receiving wireless signals at frequencies used in 3GPP. The reader / writer 250 can also perform wireless communication with the wireless tag 300 using backscattering. In this case, the reader / writer 250 may include an antenna capable of transmitting and receiving frequency signals used in backscattering.

[0033] (Example of wireless tag configuration) 4 is a diagram illustrating an example of the configuration of a wireless tag 300 according to the first embodiment. The wireless tag 300 includes an RFID antenna 310, a control unit 320, and a memory 330. The wireless tag 300 may also include a power source 340.

[0034] The RFID antenna 310 uses RFID technology to perform wireless communication with the UE 100 or the gNB 200. As described above, RFID technology includes a radio wave method and an electromagnetic induction method.

[0035] The radio wave method is a method of transmitting energy and signals using radio waves. In this case, the RFID antenna 310 receives radio waves transmitted from the UE 100 or the gNB 200, and outputs a portion of the radio waves to the control unit 320 as DC power using a rectifier circuit provided in the RFID antenna 310. This causes the control unit 320 to operate. The RFID antenna 310 also converts the received radio waves into a received signal using a demodulation circuit or the like provided in the RFID antenna 310, and outputs the received signal to the control unit 320. The RFID antenna 310 also converts the transmission signal received from the control unit 320 into a radio signal in a radio band using a modulation circuit or the like provided in the RFID antenna 310, and transmits the radio signal to the UE 100 or the gNB 200. In this case, the RFID antenna 310 may transmit the radio signal using a reflected wave of the received radio waves received from the UE 100 or the gNB 200.

[0036] The electromagnetic induction method is a method of transmitting energy and signals by generating an electromagnetic field in an antenna coil through electromagnetic induction. In the case of the electromagnetic induction method, the RFID antenna 310 is a loop coil antenna. Both the RFID antenna 141 of the UE 100 and the RFID antenna 251 of the gNB 200 are loop coil antennas. Even in the electromagnetic induction method, as in the radio wave method, power to the control unit 320 can be obtained by a rectifier circuit, a received signal can be obtained by a demodulation circuit, and reflected waves can be used.

[0037] The control unit 320 receives a received signal from the RFID antenna 310. The control unit 320 writes data included in the received signal to the memory 330, for example, in accordance with instruction information included in the received signal. The control unit 320 also reads data from the memory 330, for example, in accordance with instruction information included in the received signal. The control unit 320 outputs a transmission signal including the read data to the RFID antenna 310. In the following example, the operation or processing in the wireless tag 300 may be performed by the control unit 320.

[0038] The memory 330 stores the identifier of the wireless tag 300 (or identification information of the wireless tag 300; hereinafter, the terms "identifier" and "identification information" may be used interchangeably), data, etc. The memory 330 of the wireless tag 300 may be based on the EPC GEN2 (EPC (Electronic Product Code) Class 1 Generation 2) standard conforming to ISO / IEC 18000-63. The memory 330 based on the EPC GEN2 standard has four memory areas: a USER memory, a TID (Tag ID) memory, an EPC memory, and a RESERVED memory. The USER memory is an area that can be freely written to and read by a user of the wireless tag 300. The TID memory is an area where information such as the manufacturer and model of the wireless tag 300 is written. The TID memory is a readable but unwritable area. The EPC memory is an area where the identifier of the wireless tag 300 is written. The RESERVED memory is an area where password information of the wireless tag 300 is written. The password information includes password information used to lock writing to the wireless tag 300 and password information used to disable (kill) the wireless tag 300.

[0039] The power supply 340 is, for example, a power supply that uses energy harvesting. The environment can be heat, vibration, motion, light, wind, radio waves, biotechnology, etc. Energy harvesting is a power generation method that obtains electromotive force from the surrounding environment. Energy harvesting is different from power generation methods that use batteries such as secondary batteries. However, the wireless tag 300 may be equipped with a battery and generate its own power like an active tag. Therefore, the power supply 340 may be a battery-based power supply.

[0040] The wireless tag 300 may not have a writer function for writing data to the memory 330, but may have only a reader function for reading data from the memory 330.

[0041] The wireless tag 300 can also use a communication protocol based on 3GPP to perform wireless communication with the UE 100 or the gNB 200. In this case, instead of the RFID antenna 310, the wireless tag 300 may include an antenna capable of transmitting and receiving wireless signals at frequencies used in 3GPP.

[0042] In the following description, the wireless tag 300 is described as using RFID technology as a communication method, but this is not limiting. For example, the wireless tag 300 may use a 3GPP-compliant communication protocol as a communication method. The wireless tag 300 may also perform communication using backscattering.

[0043] (protocol stack) Next, an example of the configuration of a protocol stack will be described. Here, an example of the configuration of a protocol stack in the UE 100, the gNB 200, and the AMF 30, excluding the wireless tag 300, will be described.

[0044] FIG. 5 is a diagram showing an example of the configuration of a protocol stack of a radio interface of a user plane that handles data.

[0045] The user plane radio interface protocol includes a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer.

[0046] The PHY layer performs encoding / decoding, modulation / demodulation, antenna mapping / demapping, and resource mapping / demapping. Data and control information are transmitted between the PHY layer of UE100 and the PHY layer of gNB200 via a physical channel. The PHY layer of UE100 receives downlink control information (DCI) transmitted from gNB200 on a physical downlink control channel (PDCCH). Specifically, UE100 performs blind decoding of the PDCCH using a radio network temporary identifier (RNTI) and acquires successfully decoded DCI as DCI addressed to the UE. The DCI transmitted from gNB200 has CRC parity bits scrambled by the RNTI added.

[0047] The MAC layer performs data priority control, retransmission processing using Hybrid Automatic Repeat reQuest (HARQ), random access procedures, etc. Data and control information are transmitted between the MAC layer of UE100 and the MAC layer of gNB200 via transport channels. The MAC layer of gNB200 includes a scheduler, which determines the uplink and downlink transport format (transport block size, modulation and coding scheme (MCS)) and the resource blocks to be allocated to UE100.

[0048] The RLC layer transmits data to the RLC layer on the receiving side using the functions of the MAC layer and PHY layer. Data and control information are transmitted between the RLC layer of the UE 100 and the RLC layer of the gNB 200 via logical channels.

[0049] The PDCP layer performs header compression / decompression, encryption / decryption, etc.

[0050] The SDAP layer maps IP flows, which are the units for Quality of Service (QoS) control by the core network, to radio bearers, which are the units for QoS control by the Access Stratum (AS). Note that if the RAN is connected to the EPC, SDAP is not necessary.

[0051] FIG. 6 is a diagram illustrating an example of the configuration of a protocol stack of a radio interface of a control plane that handles signaling (control signals).

[0052] The protocol stack for the control plane radio interface is shown in Fig. 5 Instead of the SDAP layer shown in Figure 1, the RRC (Radio Resource Control) layer and NAS (Non-Access Stratum) layer It has.

[0053] RRC signaling for various settings is transmitted between the RRC layer of UE100 and the RRC layer of gNB200. The RRC layer controls logical channels, transport channels, and physical channels according to the establishment, re-establishment, and release of radio bearers. When there is a connection (RRC connection) between the RRC of UE100 and the RRC of gNB200, UE100 is in an RRC connected state. When there is no connection (RRC connection) between the RRC of UE100 and the RRC of gNB200, UE100 is in an RRC idle state. When the connection between the RRC of UE100 and the RRC of gNB200 is suspended, UE100 is in an RRC inactive state.

[0054] The NAS, which is located above the RRC layer, performs session management, mobility management, etc. NAS signaling is transmitted between the NAS of the UE 100 and the NAS of the AMF 30. Note that the UE 100 has an application layer and the like in addition to the radio interface protocol. The layer below the NAS is called an AS (Access Stratum).

[0055] (Passive IoT) Passive IoT is a technology that supports, for example, ultra-low cost and ultra-low power devices. Hereinafter, devices that support passive IoT may be referred to as "passive IoT devices." The wireless tag 300 is an example of a passive IoT device.

[0056] Passive IoT devices support ultra-low power devices. Due to the low power consumption of passive IoT, passive IoT devices may not require a battery or may use energy harvesting.

[0057] Even passive IoT devices may have built-in power sources, but even in such cases, they can be powered by small-capacity batteries and / or energy harvesting, assuming low power consumption, and therefore can be less expensive than devices that use large-capacity batteries.

[0058] On the other hand, passive IoT devices communicate with lower power than the UE 100 in a 5G system, resulting in a narrower coverage area. Furthermore, communication time is limited, and the amount of data that can be sent and received at one time is small. Furthermore, with passive IoT, interference can occur when multiple passive IoT devices communicate simultaneously. Therefore, with passive IoT, communication can be unstable and irregular.

[0059] An example of a target of passive IoT is RFID. There are three types of RFID: passive tags, active tags, and semi-passive tags (or semi-active tags). Passive tags are wireless tags that use radio waves from a reader as their power source. Passive IoT is expected to mainly use passive tags. Active tags are wireless tags that use a battery built into the wireless tag as their power source. Semi-passive tags are wireless tags that normally operate as passive tags and operate as active tags in response to a request from a reader. Passive IoT may target, for example, semi-passive tags or active tags.

[0060] Another example of a target of passive IoT is backscattering. Backscattering refers to the reflection of radio waves, particles, or signals back in the direction from which they came. As described above, backscattering in passive IoT is used in communication methods that use reflected waves. The wireless tag 300 can transmit data using the reflected waves by modulating the reflected waves.

[0061] Another target of passive IoT is, for example, energy harvesting. As mentioned above, energy harvesting is a power generation method that obtains power from the environment. For example, energy harvesting generates power by converting energy such as vibration or heat into electrical energy. Energy harvesting may include solar panels or windmills. The low power consumption of passive IoT makes it possible to use energy harvesting as a power source. Unlike batteries, energy harvesting does not require charging or replacement, allowing for long-term operation without maintenance.

[0062] (Passive IoT Challenges) If passive IoT can be accommodated in a 3GPP-compliant mobile communication system, for example, passive IoT devices can be managed by the NG-RAN 10 or CN 20.

[0063] However, there are some challenges to be overcome when incorporating passive IoT into a mobile communication system.

[0064] FIG. 7 is a diagram for explaining the problem of the passive IoT according to the first embodiment. In FIG. 7, a network 500 and a communication node 400 are included in a mobile communication system conforming to 3GPP. The communication node 400 has a reader / writer function and is a node that communicates with a wireless tag 300. The communication node 400 is a UE 100 or a gNB 200. Meanwhile, the network 500 includes a device that communicates with the communication node 400. The network 500 is a CN20 or a gNB 200.

[0065] From the perspective of the network 500 (CN20 or gNB200), there is a problem of whether to manage the wireless tag 300 as a wireless tag or as a UE 100. If the wireless tag 300 can be managed as a UE 100 in the network 500, it becomes possible to handle the wireless tag 300 in the same way as the UE 100.

[0066] There is also the issue of whether the reader function (and / or writer function) is performed by the UE 100 or the gNB 200. Not only the UE 100 but also the gNB 200 can communicate directly with the wireless tag 300.

[0067] Furthermore, there is also the issue of whether the link between the communication node 400 and the wireless tag 300 will use existing specifications such as RFID or a 3GPP-compliant communication protocol, or whether the link will use a 3GPP-compliant communication band or an RFID communication band (such as the 13.56 MHz band or the 900 MHz band).

[0068] As described above, there are several challenges to accommodating passive IoT in a mobile communication system. It will be understood that the following embodiments can solve all or part of the above-mentioned challenges.

[0069] (Passive IoT scenario) The following three scenarios (scenario a, scenario b, and scenario c) are assumed as scenarios in which passive IoT is used. Note that in the three scenarios, a communication node 400 exists, and the communication node 400 may be, for example, either a UE 100 having a reader / writer 140 or a gNB 200 having a reader / writer 250.

[0070] 8(A) and 8(B) are diagrams for explaining scenario a according to the first embodiment. Scenario a is, for example, a scenario in which passive IoT is used locally.

[0071] As shown in FIG. 8(A), the communication node 400 detects the wireless tag 300 loaded on a moving object such as a truck T (or a pallet) when the wireless tag 300 passes through a gate. A wireless tag 300 may be attached to each product. Alternatively, a wireless tag 300 may be attached to each pallet containing products. For example, if the communication node 400 is installed at the main gate of a factory and the communication node 400 detects the wireless tag 300, it becomes possible to manage products shipped from the factory or parts entering the factory.

[0072] The example in FIG. 8(B) is an example in which a moving object (e.g., a person H or a moving vehicle) moves through the communication node 400 to detect the wireless tag 300 loaded on a fixed object (e.g., a pallet). The wireless tag 300 may be attached to each product. Alternatively, the wireless tag 300 may be attached to each pallet. By detecting the wireless tag 300, it is possible to manage, for example, the products loaded on the pallet.

[0073] 9(A) to 9(C) are diagrams for explaining scenario b according to the first embodiment. Scenario b is a scenario for managing wireless tags 300 present at a certain location. The location may be a factory (or warehouse) (FIG. 9(A)), a specific area (FIG. 9(B)), or the cargo of a truck T (FIG. 9(C)). By managing the wireless tags 300 present at the location, the communication node 400 can perform inventory management of products or parts within the factory, management of products or parts loaded on a truck T, and the like.

[0074] FIG. 10 is a diagram illustrating scenario c according to the first embodiment. Scenario c is a scenario in which measurement values ​​are continuously or periodically read from a wireless tag 300 placed or present at a certain location. For example, a thermometer and a wireless tag 300 connected to the thermometer are placed on a site or a ranch. The wireless tag 300 can obtain measurement values ​​(temperature information) from the thermometer. Then, the communication node 400 continuously or periodically reads the measurement values ​​from the wireless tag 300, thereby enabling temperature management on the site or the ranch.

[0075] (Communication control method according to the first embodiment) Next, a communication control method according to the first embodiment will be described.

[0076] In the first embodiment, a protocol for managing the wireless tag 300 on the network 500 will be described.

[0077] In the first embodiment, the configuration shown in Fig. 7 is also basically applicable. That is, the network 500 and the communication node 400 are accommodated in a mobile communication system, and the wireless tag 300 is managed by the mobile communication system. In this case, the network 500 is the AMF 30 or the gNB 200. Furthermore, the communication node 400 is the gNB 200 or the UE 100. Specifically, the following combinations are available.

[0078] That is, there is a case where the network 500 is the AMF 30 and the communication node 400 is the gNB 200. In this case, the gNB 200 has a reader / writer function (i.e., the reader / writer 250), and communicates with the wireless tag 300. For example, an NG-AP message according to the NG-AP protocol is transmitted and received between the AMF 30 (network 500) and the gNB 200 (communication node 400).

[0079] There is also a case where the network 500 is the AMF 30 and the communication node 400 is the UE 100. In this case, the UE 100 has a reader / writer function (i.e., the reader / writer 140), and communicates with the wireless tag 300. For example, a NAS message according to the NAS protocol is transmitted and received between the AMF 30 (network 500) and the UE 100 (communication node 400).

[0080] Furthermore, there is a case where the network 500 is the gNB 200 and the communication node 400 is the UE 100. In this case as well, the UE 100 has a reader / writer function and communicates with the wireless tag 300. For example, an RRC message according to the RRC protocol is transmitted and received between the gNB 200 (network 500) and the UE 100 (communication node 400).

[0081] Under such a premise, in the first embodiment, first, a first communication node (e.g., AMF30 or gNB200) included in a network (e.g., network 500) transmits a predetermined message (e.g., a paging message) to a second communication node (e.g., communication node 400, gNB200 or UE100). Second, in response to receiving the predetermined message, the second communication node transmits tag information read from a wireless tag (e.g., wireless tag 300) to the first communication node.

[0082] As described above, in the first embodiment, the second communication node reads tag information from the wireless tag in response to receiving a predetermined message, and transmits the tag information to the first communication node.

[0083] As a result, for example, as shown in scenario b (FIGS. 9(A) to 9(C)), the communication node 400 can be triggered by receiving a paging message to read tag information from a wireless tag 300 placed or present at a certain location and transmit the tag information to the network 500. Therefore, the wireless communication system 1 according to the first embodiment can appropriately communicate with the wireless tag 300.

[0084] (Operation example according to the first embodiment) Fig. 11 is a diagram illustrating an example of operation according to the first embodiment. In the example of operation illustrated in Fig. 11, a paging message will be used as an example of the predetermined message. Furthermore, before the operation illustrated in Fig. 11 is performed, if the communication node 400 is the UE 100, it is assumed that the UE 100 is in an RRC idle state or an RRC inactive state.

[0085] As shown in FIG. 11, in step S10, the network 500 transmits a paging message to the communication node 400.

[0086] When the network 500 is the AMF 30 and the communication node 400 is the UE 100, the paging message is transmitted as a NAS message. In this case, the paging is initiated by the core network (CN-initiated). When the network 500 is the AMF 30 and the communication node 400 is the gNB 200, the paging message is transmitted as an NG-AP message. When the network 500 is the gNB 200 and the communication node 400 is the UE 100, the paging message is transmitted as an RRC message. In this case, the paging is initiated by the access network (AN-initiated).

[0087] First, the paging message may include an identifier of the wireless tag 300 to be called (Case A). The identifier may be an identification code used in the EPC (Electronic Product Code). The EPC is an identification code standardized by GS1, a standards organization. The EPC is a general term for identification codes written to the wireless tag 300. Examples of EPC identification codes include the SGTIN (Serialized Global Trade Item Number) used to manage objects or products, the SGLN (Serialized Global Location Number) used to manage locations, and the GRAI (Global Returnable Asset Identifier) ​​used to manage assets such as pallets. Such EPC-compliant identification codes may be used as the identifier of the wireless tag 300.

[0088] Furthermore, a group of identifiers may be used as the identifier of the wireless tag 300. For example, the identifier of the wireless tag 300 may be a list of EPC identification codes. RFID has an anti-collision function that reads multiple wireless tags 300 at once. The anti-collision function is a function that reads tag information from each wireless tag 300 in a time-division manner. By using a group of tag identifiers as the identifier of the wireless tag 300, the wireless tags 300 can be processed at once, which can be efficient in some cases.

[0089] Second, the paging message may include an indicator instructing that the wireless tag 300 be called (Case B). The indicator may be an indicator instructing that tag information be read.

[0090] However, the identifier of the wireless tag 300 in case A may be used to instruct the wireless tag 300 having the identifier to "call" the wireless tag 300. Also, the identifier of the wireless tag 300 in case A may be used to instruct the wireless tag 300 having the identifier to "read tag information."

[0091] The identifier of the call target (Case A) and the indicator instructing to call the tag (Case B) may be linked to a UE ID. In this case, the network 500 performs paging on the UE 100 that manages the call target wireless tag 300 and has the UE ID. In addition, when the communication node 400 is a gNB, the identifier of the call target (Case A) and the indicator instructing to call the tag (Case B) may be linked to a gNB ID and / or a cell ID.

[0092] In step S11, the communication node 400 performs a tag information read process in response to receiving a paging message. The communication node 400 may perform the read process in response to receiving a paging message including an identifier of the target to be called (Case A) or an indicator instructing to call the tag (Case B). The read process itself may utilize RFID. The tag information read from the wireless tag 300 may be information stored in the EPC memory. That is, the tag information may be the identifier of the wireless tag 300. Alternatively, the tag information may be information stored in the TID memory (e.g., the manufacturer of the wireless tag 300). Alternatively, the tag information may be information stored in the USER memory. For example, the tag information may be a measurement value (e.g., temperature information) stored in the USER memory. Alternatively, the tag information may be the remaining battery charge when the wireless tag 300 is an active tag. Alternatively, the tag information may be password information stored in the RESERVED memory.

[0093] In step S12, the communication node 400 determines whether or not a predetermined condition is satisfied. If the communication node 400 determines that the predetermined condition is satisfied (YES in step S12), the process proceeds to step S13. On the other hand, if the communication node 400 determines that the predetermined condition is not satisfied (NO in step S12), the process proceeds to step S14.

[0094] The predetermined condition is a condition for determining whether or not to transmit the tag information read in the tag information reading process to the network 500.

[0095] The predetermined condition is, first, whether or not the identifier of the wireless tag 300 included in the tag information read from the wireless tag 300 (for example, the tag identifier read from the EPC memory) matches the identifier of the wireless tag 300 to be called included in the paging message (Case A). If the identifier of the wireless tag read from the wireless tag 300 matches the identifier of the wireless tag 300 to be called included in the paging message (YES in step S12), the process proceeds to step S13. On the other hand, if the tag information and the identifier do not match (NO in step S12), the process proceeds to step S14.

[0096] The second predetermined condition is whether or not the tag information has been successfully read when the paging message contains an indicator instructing to call the wireless tag 300 (case B). If the tag information has been successfully read (YES in step S12), the process proceeds to step S13. On the other hand, if the tag information has not been successfully read (NO in step S12), the process proceeds to step S14.

[0097] In step S13, the communication node 400 transmits the tag information to the network 500. When the communication node 400 is the UE 100 and the network 500 is the gNB 200, the UE 100 (communication node 400) may transmit an RRC message including the tag information to the gNB 200 (network 500), thereby performing step S13. When the communication node 400 is the UE and the network 500 is the AMF 30, the UE 100 (communication node 400) may transmit a NAS message including the tag information to the AMF 30, thereby performing step S13. When the communication node 400 is the gNB 200 and the network 500 is the AMF 30, the gNB 200 (communication node 400) may transmit an NG-AP message including the tag information to the AMF 30 (network 500), thereby performing step S13.

[0098] In step S14, the communication node 400 does not respond to the paging message. Note that in step S14, the communication node 400 may transmit to the network 500 a message (for example, an RRC message, a NAS message, or an NG-AP message) including at least one of information indicating that reading of the wireless tag 300 has failed, information indicating that no information has been read from the wireless tag 300, and information indicating that the information read from the wireless tag 300 does not satisfy a predetermined condition.

[0099] (Modification 1 of the first embodiment) In the first embodiment, a paging message has been described as an example of the predetermined message, but the predetermined message may be a message other than a paging message.

[0100] For example, if the network 500 is a gNB 200 and the communication node 400 is a UE 100, the following applies.

[0101] First, an RRC reconfiguration message may be transmitted instead of a paging message (step S10). The RRC reconfiguration message includes the information included in the paging message (step S10) described in the first embodiment. The UE 100 (communication node 400) performs a process of reading tag information triggered by reception of the RRC reconfiguration message (step S11). If a predetermined condition is satisfied (YES in step S12), the UE 100 transmits an RRC reconfiguration complete message including the tag information to the gNB 200 (network 500) (step S13). The UE 100 may transmit UE assistance information (UE assistance information) (UAI) including the tag information to the gNB 200.

[0102] Second, instead of the paging message, an RRC reconfiguration message including a measurement configuration may be transmitted (step S10). The measurement configuration includes the radio tag 300 as a measurement object. The measurement configuration may also include reporting conditions (whether to perform the measurement periodically or when an event is triggered) as reporting configurations. For example, the UE 100 periodically reads tag information and reports when a predetermined condition is satisfied. The predetermined event may be, for example, a change in the read tag information (for example, an increase or decrease in the number of radio tags). The measurement configuration may also include the predetermined condition described in the first embodiment. The measurement configuration may also include conditions for communication with the radio tag 300. For example, it may specify whether to perform tag information reading periodically or when an event occurs. The RRC reconfiguration message includes information included in the paging message (step S10) described in the first embodiment. When the predetermined condition is satisfied (YES in step S12) and the reporting condition is satisfied, the UE 100 may transmit a measurement report including tag information (step S13). Alternatively, the UE 100 may transmit a measurement report including tag information when the reporting condition is satisfied without considering the predetermined condition (step S13).

[0103] Third, a new message may be transmitted from the gNB 200 to the UE 100 (step S10). The new message may be a message such as "Passive IoT read indication" that instructs the UE 100 to read the wireless tag 300. The new message may include information included in the paging message (step S10) described in the first embodiment.

[0104] The above is an example of an RRC message. Note that a system information block (SIB) may be used as an example of an RRC message. A specific radio tag group can also be specified by the system information block (SIB). However, if the network 500 is the AMF 30 and the communication node 400 is the UE 100, a NAS message (step S10) other than a paging message may be used.

[0105] Furthermore, when the network 500 is the AMF 30 and the communication node 400 is the gNB 200, an NG-AP message other than a paging message (step S10) may be used. In this case, the gNB 200 (communication node 400) may transmit a new message (such as TAG RESPONSE) including tag information to the AMF 30 (network 500) (step S13).

[0106] (Modification 2 of the first embodiment) In the first embodiment, when the communication node 400 is the UE 100, the description is given on the assumption that the UE 100 is in an RRC idle state or an RRC inactive state before performing the operation example shown in Fig. 11. The UE 100 may be assumed to be in an RRC connected state. Even in this case, the UE 100 may monitor a paging message (step S10). Alternatively, when the network 500 (AMF 30 or gNB 200) is aware that the UE 100 has a radio tag 300 under its control, the network 500 may transmit a NAS message or an RRC message (RRC dedicated signaling) equivalent to a paging message to the UE 100 in the RRC connected state (step S10).

[0107] [Second embodiment] Next, a second embodiment will be described.

[0108] In the first embodiment, the communication node 400 reads the wireless tag 300 when it receives a paging message. In the second embodiment, the communication node 400 transmits tag information when it receives a paging message. In the second embodiment, the communication node 400 manages the wireless tag 300 under its control more actively than in the first embodiment.

[0109] Specifically, first, the second communication node (e.g., communication node 400) reads tag information from a wireless tag (e.g., wireless tag 300). Second, after reading the tag information, the second communication node transmits the tag information to the first communication node (e.g., network 500) in response to receiving a predetermined message (e.g., a paging message).

[0110] As a result, for example, the communication node 400 can be triggered by receiving a paging message to transmit tag information of the wireless tag 300 placed or present at a certain location to the network 500 (for example, scenario b). Therefore, the wireless communication system 1 according to the second embodiment can appropriately communicate with the wireless tag 300 and appropriately acquire tag information.

[0111] (Operation example according to the second embodiment) Fig. 12 is a diagram illustrating an example of operation according to the second embodiment. When the communication node 400 is the UE 100, the UE 100 is in the RRC idle state or the RRC inactive state, as in the first embodiment, before the example of operation illustrated in Fig. 12 is started.

[0112] 12, in step S20, the communication node 400 periodically reads tag information from the wireless tag 300. The communication node 400 stores the read tag information in a memory.

[0113] In step S21, the network 500 transmits a paging message to the communication node 400. The paging message includes the information included in the paging message described in the first embodiment.

[0114] In step S22, the communication node 400 determines whether a predetermined condition is satisfied. The predetermined condition can be case A (the paging message includes the identifier of the wireless tag 300 to be called) or case B (the paging message includes an indicator instructing the wireless tag 300 to be called).

[0115] In the case of case A, for example, the following is true: That is, the predetermined condition is whether or not the identifier of the wireless tag 300 included in the paging message (step S21) exists among the identifiers of the wireless tag 300 read from the wireless tag 300 (or stored in the memory of the communication node 400). If the identifier of the wireless tag 300 included in the paging message exists among the identifiers of the wireless tag 300 read from the wireless tag 300 (YES in step S22), the process proceeds to step S23. If not (NO in step S22), the process proceeds to step S24.

[0116] In case B, for example, the predetermined condition is as follows: That is, the predetermined condition is whether or not the identifier of the wireless tag 300 is present in the tag information read from the wireless tag 300. If the identifier of the wireless tag 300 is present in the tag information read from the wireless tag 300 (YES in step S22), the process proceeds to step S23. If the identifier is not present (NO in step S22), the process proceeds to step S24.

[0117] In step S23, the communication node 400 responds to the paging message (step S21). That is, the communication node 400 transmits a response message including tag information. The response message may be transmitted as any one of an RRC message, a NAS message, and an NG-AP message.

[0118] In step S24, the communication node 400 does not respond to the paging message (step S21). In this case, similar to the first embodiment, the communication node 400 may transmit to the network 500 a message including any of information indicating that the wireless tag 300 could not be read, information indicating that no tag information was read from the wireless tag 300, and information indicating that a predetermined condition was not satisfied. This message may also be transmitted as any of an RRC message, a NAS message, and an NG-AP message.

[0119] 12, a paging message (step S21) has been taken as an example. However, a message other than a paging message may be used, as in the first modification of the first embodiment.

[0120] 12, when the communication node 400 is the UE 100, the UE 100 may be in a connected state, similarly to the second modification of the first embodiment. For example, the UE 100 may be brought into an RRC connected state by a paging message, and then may be triggered by an NAS message or an RRC message (step S21) to transmit tag information to the network 500 (step S23). The NAS message or the RRC message includes information included in the paging message (step S10 of FIG. 11), such as (a list of) identifiers of the wireless tags 300, similarly to the first embodiment.

[0121] [Third embodiment] Next, a third embodiment will be described.

[0122] In the third embodiment, the communication node 400 periodically reads tag information from the wireless tag 300, and transmits the tag information if there is a change between the tag information before and after reading.

[0123] Specifically, first, a first communication node (e.g., AMF30 or gNB200) included in a network (e.g., network 500) configures a second communication node (e.g., communication node 400, gNB200 or UE100) to monitor a wireless tag (e.g., wireless tag 300). Second, the second communication node periodically reads tag information from the wireless tag in accordance with the configuration. Third, if the tag information read from the wireless tag at the first timing differs from the tag information read from the wireless tag at a second timing following the first timing, the second communication node transmits predetermined tag information to the first communication node. Here, the predetermined tag information is either difference information indicating the difference between the tag information read at the first timing and the tag information read at the second timing, or the tag information read at the second timing.

[0124] This allows, for example, the communication node 400 to properly communicate with the wireless tag 300 and properly transmit any changed tag information read from the wireless tag 300 to the network 500. This also allows the network 500 to properly manage the tag information.

[0125] For example, in scenario a (FIG. 8(B)), if there are multiple wireless tags 300 on a pallet, the communication node 400 periodically reads the tag information, and if there is no change in the tag information, it does not transmit the tag information, but if there is a change in the tag information, it transmits the tag information. This makes it possible to read the tag information from the wireless tag 300 attached to the part, for example, if a new part is present on the pallet, and therefore makes it possible to manage the new part appropriately.

[0126] Note that "when there is a change in tag information" means, for example, when the tag information read at a first timing differs from the tag information read at a second timing following the first timing (or a timing later than the first timing).

[0127] (Operation example of the third embodiment) FIG. 13 is a diagram illustrating an example of operation according to the third embodiment.

[0128] 13, in step S30, the network 500 transmits a configuration message to the communication node 400. This allows the network 500 to configure the communication node 400 for periodic tag monitoring. The configuration message is transmitted by any one of an RRC message, a NAS message, and an NG-AP message. The configuration message includes at least one of the following information:

[0129] First, the setting message may include a read interval (or read time). The read interval may be a timer value. For example, the communication node 400 starts counting a timer upon receiving the setting message, and when the timer reaches the timer value and expires, it performs a read process on the wireless tag 300 and restarts the timer.

[0130] Second, the setting message may include information instructing the communication node 400 to periodically monitor the wireless tag 300. For example, the communication node 400 reads tag information (at implementation-dependent timing) in accordance with the instruction.

[0131] Thirdly, the setting message may include the identifier of the wireless tag 300 to be regularly monitored. The communication node 400 determines that the wireless tag 300 having the identifier is a wireless tag to be regularly monitored.

[0132] Fourth, the configuration message may include information regarding the reporting conditions. The reporting conditions are whether to report every time tag information is read (periodic) or whether to report only when there is a change in the tag information (event-trigger). In the case of periodic, information indicating the reporting interval (which may be a timer value) is included. In the case of event-trigger, the reporting is triggered when there is a change in the tag information. It may also be triggered when there is a change in the measurement value acquired as tag information. In the case of event-trigger, the reporting may be triggered when the number of wireless tags 300 increases (or when the identifiers of the wireless tags 300 included in the read tag information increase compared to the identifiers of the wireless tags 300 read previously). Alternatively, in the case of event-trigger, the reporting may be triggered when the number of wireless tags 300 decreases (or when the identifiers of the wireless tags 300 included in the read tag information decrease compared to the identifiers of the wireless tags 300 read previously).

[0133] Fifth, the setting message may include information indicating the report content. For example, the setting message may include information indicating that all read tag information is to be reported. Or, the setting message may include information indicating that tag information that has changed is to be reported. In this case, the setting message may include information indicating which event the report is based on. For example, the communication node 400 can report to the network 500, according to the information, information indicating that "wireless tag #2 has entered the communication node 400's control, and therefore has transmitted tag information."

[0134] In step S31, the communication node 400 monitors the wireless tag 300 in accordance with the settings included in the setting message, and reads tag information from the wireless tag 300 in accordance with the settings.

[0135] In step S32, the communication node 400 determines whether the reporting condition is met. If the reporting condition is met (YES in step S32), the process proceeds to step S33. On the other hand, if the reporting condition is not met (NO in step S32), step S32 is repeated until the reporting condition is met.

[0136] The reporting condition may be a condition that the tag information is reported every time it is read (periodic) or that the tag information is reported only when there is a change (event-trigger), as included in the setting message (step S30). If the setting message does not include the reporting condition, the reporting condition may be pre-configured, for example. Note that if there is no change in the tag information, the communication node 400 may report information indicating that there is no change in the tag information, rather than the tag information itself.

[0137] In step S33, the communication node 400 transmits the tag information to the network 500. The transmitted tag information is predetermined tag information. The predetermined tag information may be differential information between tag information read at a first timing and tag information read at a second timing following the first timing (or later than the first timing). The predetermined tag information may also be tag information read at the second timing. The tag information may be transmitted in an RRC message, as in the first embodiment. Alternatively, the tag information may be transmitted in an NAS message. Alternatively, the tag information may be transmitted in an NG-AP message.

[0138] [Fourth embodiment] Next, a fourth embodiment will be described.

[0139] The fourth embodiment is an embodiment in which the communication node 400 is the UE 100. In the fourth embodiment, an example will be described in which, when the UE 100 detects a predetermined event, the UE 100 reads tag information from the wireless tag 300 and transmits the tag information to the network 500 (AMF 30 or gNB 200).

[0140] Specifically, first, the user equipment (e.g., UE 100) reads tag information from a radio tag (e.g., radio tag 300) in response to detecting a predetermined event. Second, the user equipment transmits the tag information to a communication node (e.g., AMF 30 or gNB 200) included in a network (e.g., network 500). Here, the predetermined event is any one of a Registration Area Update, a Tracking Area Update, a RAN-based Notification Area Update, a handover, an RRC connection reestablishment, an RRC connection resume, and an RRC setup.

[0141] As a result, as shown in scenario b (FIG. 9(C)), for example, when the UE 100 (communication node 400) moves to a new registration area (RA) as the truck T moves, the UE 100 can read tag information from the wireless tag 300 and transmit the tag information to the network 500. Therefore, the wireless communication system 1 can read tag information from the wireless tag 300 at an appropriate timing.

[0142] (Operation example according to the fourth embodiment) FIG. 14 is a diagram illustrating an example of operation according to the fourth embodiment.

[0143] As shown in Fig. 14, in step S40, the network 500 may transmit a configuration message to the UE 100. The configuration message may be a message including information indicating permission (or request) to transmit tag information. The configuration message is transmitted as an RRC message or an NAS message. In the case of an RRC message, the configuration message may be broadcast by system information (SIB: System Information Block). Furthermore, the configuration message may be transmitted by the paging message described in the first embodiment.

[0144] In step S41, the UE 100 detects a predetermined event. Examples of the predetermined event include the following.

[0145] (1) First, the predetermined event is at least one of a Registration Area Update (RAU), a Tracking Area Update (TAU), and a RAN-based Notification Area Update (RNAU). The Tracking Area (TA) is, for example, an area including one or more cells, into which the UE 100 in an RRC idle state can move without performing an update to the MME. The RAN Notification Area (RNA) is, for example, an area including one or more cells, into which the UE 100 in an RRC inactive state can move without performing a notification to the NG-RAN 10. The Registration Area (RA) is, for example, an area including multiple tracking areas, into which the UE 100 can move without performing a registration procedure to the network. An update process performed when the UE 100 moves into such an area can be the predetermined event. Note that the TAU is performed between the UE 100 and the MME, but may also be performed between the UE 100 and the AMF 30. A specific description will be given below.

[0146] (1-1) When network 500 is gNB200 Specifically, the predetermined event may be at least one of when the UE 100 transmits an RRC Resume Request (RRCResumeRequest) message in association with any of an RAU, a TAU, and an RNAU, when the UE 100 receives an RRC Resume (RRCResume) message, and when the UE 100 transmits an RRC Resume Complete (RRCResumeComplete) message. The time when the UE 100 transmits or receives such a message may be the time when the predetermined event is detected.

[0147] (1-2) When network 500 is AMF30 Specifically, the predetermined event may be at least one of when the UE 100 transmits a registration request (REGISTRATION REQUEST) message associated with an RAU and when the UE 100 receives a registration accept (REGISTRATION ACCEPT) message associated with an RAU. The time when the UE 100 transmits or receives such a message may be the time when the predetermined event is detected.

[0148] (2) Second, the predetermined event may be a handover. Specifically, when the network 500 is the gNB 200, the predetermined event may be one of the following: when the UE 100 receives an RRC reconfiguration message associated with handover, when the UE 100 starts access to the target cell, and when the UE 100 transmits an RRC reconfiguration complete message associated with handover. The time when the UE 100 starts access to the target cell may be at least one of when the UE 100 starts a Random Access Channel (RACH) procedure and when the RACH procedure is completed.

[0149] (3) Third, the predetermined event may be when UE 100 reestablishes an RRC connection. Specifically, when network 500 is gNB 200, the predetermined event may be at least one of when UE 100 transmits an RRC reestablishment request (RRCReestablishmentRequest) message, when UE 100 receives an RRC reestablishment (RRCReestablishment) message, and when UE 100 transmits an RRC reestablishment complete (RRCReestablishmentComplete) message.

[0150] (4) Fourth, the predetermined event may be when UE 100 resumes the RRC connection. Specifically, when network 500 is gNB 200, the predetermined event may be at least one of when UE 100 transmits an RRC resume request (RRCResumeRequest) message, when UE 100 receives an RRC resume (RRCResume) message, and when UE 100 transmits an RRC resume complete (RRCResumeComplete) message.

[0151] (5) Fifth, the predetermined event may be when the UE 100 sets up an RRC connection. Specifically, when the network 500 is the gNB 200, the UE 100 may send an RRC setup request (RRCSetupRequest) message, when the UE 100 receives an RRC setup (RRCSetup) message, and when the UE 100 sets up an RRC connection. C This may be at least one of the times when an RRCSetupComplete message is sent.

[0152] In step S42, the UE 100 performs a process of reading tag information from the wireless tag 300 in response to the detection of the predetermined event.

[0153] If the UE 100 has successfully read the tag information, the UE 100 transmits, to the network 500, information indicating that the UE 100 has the tag information, in step S43.

[0154] For example, when the network 500 is the gNB 200, the UE 100 transmits the information by including it in either message 3 (MSG3) or message 5 (MGS5) in the RACH procedure. The information may be, for example, "tag available."

[0155] For example, if the network 500 is the AMF 30, the UE 100 transmits a NAS message including information indicating that it has tag information.

[0156] Then, if UE100 has successfully read the tag information, UE100 transmits the tag information (or a list of tag information) in step S44. For example, if network 500 is gNB200, UE100 may include the tag information in message 5 in the RACH procedure and transmit it. UE100 may also include the tag information in UE assistance information (UEAssistanceInformation) and transmit it. Note that, if there is a difference in the tag information in step S44 (i.e., there is a difference between the tag information acquired in the previous tag information read process and the tag information acquired in the current tag information read process), UE100 may transmit the tag information (i.e., the tag information acquired in the current tag information read process). UE100 may also transmit information on the difference.

[0157] If UE 100 fails to read tag information in the tag information reading process (step S42), UE 100 may not perform steps S43 and S44. Alternatively, if UE 100 fails to read tag information, UE 100 may transmit a message (RRC message or NAS message) including information indicating that tag information reading has failed to network 500. Alternatively, UE 100 may transmit a message (RRC message or NAS message) including information indicating that there was no tag information in wireless tag 300 to network 500.

[0158] [Fifth embodiment] Next, a fifth embodiment will be described.

[0159] The fifth embodiment is an example in which the UE 100 adds additional information to tag information to be transmitted to the network 500 and transmits the tag information.

[0160] Specifically, a second communication node (for example, a UE 100 or a gNB 200 which is a communication node 400) transmits tag information to which additional information has been added to a first communication node (for example, an AMF 30 or a gNB 200 included in a network 500).

[0161] This allows the network 500 to appropriately manage products to which the wireless tag 300 is attached, for example, by using the additional information.

[0162] (Operation example according to the fifth embodiment) Fig. 15 is a diagram illustrating an example of operation according to the fifth embodiment. Fig. 15 shows processing that is mainly performed in the communication node 400 (the UE 100 or the gNB 200).

[0163] As shown in FIG. 15, in step S50, the communication node 400 starts the process.

[0164] In step S51, the communication node 400 performs a process of reading tag information.

[0165] In step S52, the communication node 400 adds additional information to the read tag information. The additional information may be, for example, at least one of the following pieces of information:

[0166] First, the additional information may be time information. The time information may be information that indicates the time when the communication node 400 reads the tag information. For example, the time information may be the date and time (date or hour) when the communication node 400 reads the tag information. The time information may also be the frame number of the radio frame when the communication node 400 reads the tag information. If the communication node 400 is a gNB200, the radio frame may be the radio frame when the gNB200 performs radio communication with the UE100. If the communication node 400 is a UE100, the radio frame may be the radio frame when the UE100 performs radio communication with the gNB200.

[0167] Second, the additional information may be location information. The location information may be information that indicates the location where the communication node 400 reads the tag information. For example, the location information may be represented by latitude and longitude. The location information may also include altitude in addition to latitude and longitude. For example, the location information may be represented by an RF fingerprint. The location information may also be location information obtained from beacon information of surrounding Wi-Fi (registered trademark) or Bluetooth (registered trademark).

[0168] Third, the additional information may be received signal information regarding a received signal. The received signal information may be the received power (e.g., RSRP (Reference Signal Received Power)) and / or the received quality (e.g., RSRQ (Reference Signal Received Quality)) of a signal received from the wireless tag 300. Alternatively, the received signal information may be the propagation loss (path loss) of the signal received from the wireless tag 300. In this case, if the transmission power of the wireless tag 300 is known, the communication node 400 measures the received power of the signal received from the wireless tag 300 and obtains the propagation loss by subtracting the transmission power of the wireless tag 300 from the received power at the communication node 400. Furthermore, if the reception power of the wireless tag 300 can be fed back, the communication node 400 obtains the propagation loss by subtracting the transmission power of the communication node 400 to the wireless tag 300 from the received power at the wireless tag 300. In this case, for example, the wireless tag 300 stores the received power value in a USER memory, and the communication node 400 can obtain the received power value by reading the information in the USER memory. When the wireless tag 300 transmits a transmission wave (reflected wave) using backscattering, the communication node 400 can obtain the propagation loss by subtracting the transmission power of the communication node 400 from the reception power of the communication node 400.

[0169] The additional information is set by a configuration message (any of an RRC message, a NAS message, or an NG-AP message) transmitted from the network 500, and the communication node 400 may add the additional information to the tag information according to the setting. The configuration message may include information indicating the target to be added as additional information. If the information is, for example, location information, the communication node 400 adds the location information to the tag information as additional information.

[0170] In step S53, in response to detecting a predetermined event, the communication node 400 transmits tag information to which additional information has been added to the network 500. The predetermined event may be the same as the predetermined event described in the fourth embodiment.

[0171] Then, in step S54, the communication node 400 ends the series of processes.

[0172] [Sixth embodiment] Next, a sixth embodiment will be described.

[0173] In the sixth embodiment, the network 500 manages the acquired tag information by linking it to the communication node 400. In addition, in the sixth embodiment, the network 500 stores the tag information linked to the communication node 400 as a part of the context of the communication node 400.

[0174] Specifically, a first communication node (for example, a gNB200 or an AMF30 included in the network 500) manages tag information by linking it to a second communication node (for example, a UE100 or a gNB200 which is a communication node 400).

[0175] This enables, for example, the network 500 to appropriately manage the tag information because the tag information is associated with the communication node 400. Furthermore, for example, the network 500 manages the tag information as part of the context information (UE Context) of the UE 100, and thereby becomes able to transmit the tag information to another network 500 as part of the context information of the UE 100.

[0176] The UE context information includes, for example, information that can uniquely identify the UE 100 in the gNB 200, such as a cell ID (PCI (Physical Cell ID)), and / or a UE identifier (C-RNTI (Cell-Radio Network Temporary Identifier)).

[0177] (Operation example according to the sixth embodiment) FIG. 16 shows an example of operation according to the sixth embodiment.

[0178] 16, in step S60, the communication node 400 transmits the tag information to the network 500. As in the first embodiment, the communication node 400 transmits the tag information using any one of an RRC message, a NAS message, and an NG-AP message as a message including the tag information.

[0179] In step S61, the network 500 associates the tag information received from the communication node 400 with the communication node 400. For example, the network 500 may associate the tag information with identification information of the communication node 400. The network 500 may store the tag information in memory as (part of) context information of the communication node 400. The context information of the communication node 400 includes, for example, identification information of the communication node 400.

[0180] In step S62, the network 500 may read the tag information upon a predetermined read event. The predetermined read event may be paging. This is because the tag information is used to identify the communication node 400 that manages the wireless tag 300 that is the target of a network call when paging is performed in the network 500. The predetermined read event may also be communication with the wireless tag 300. This is because the tag information is used to identify the communication node 400 that manages the wireless tag 300 when communication is performed in the network 500.

[0181] In step S63, the network 500 may transmit the tag information to the other network 510 as context information of the communication node 400 upon a predetermined transmission event. The predetermined transmission event may be a case where the other network 510 requests context information of the communication node 400. For example, the network 500 may transmit the tag information when requested by the other network 510 in an RAU, a TAU, an RNAU, an RRC connection re-establishment, or an RRC connection resumption. The predetermined transmission event may also be a case where the other network 510 is requested to take over the context information of the communication node 400. For example, the network 500 may transmit the tag information when the other network 510 requests to take over the context information in connection with handover. Note that the network 500 may transmit the tag information (step S63) by transmitting to the other network 510 either an Xn message including tag information or an NG message including tag information.

[0182] [Seventh embodiment] Next, a seventh embodiment will be described.

[0183] The seventh embodiment is an embodiment in which the network 500 instructs a specific communication node 400 to execute processing on a specific wireless tag 300. In the first embodiment, the reading processing on the wireless tag 300 has been mainly described, but in the seventh embodiment, processing other than the reading processing will be described.

[0184] Specifically, first, a first communication node (e.g., gNB200 or AMF30) included in a network (e.g., network 500) instructs a second communication node (e.g., UE100 or gNB200, which is communication node 400) to perform processing on a wireless tag (e.g., wireless tag 300). Second, the second communication node performs the processing on the wireless tag in accordance with the instruction.

[0185] As a result, for example, the network 500 can perform processing on a specific wireless tag 300, such as writing to the wireless tag 300, locking the wireless tag 300, or invalidating (killing) the wireless tag 300, via a specific communication node 400. Therefore, the wireless communication system 1 can appropriately perform specific processing on a specific wireless tag 300.

[0186] (Operation example according to the seventh embodiment) FIG. 17 is a diagram illustrating an example of operation according to the seventh embodiment.

[0187] 17, in step S70, the network 500 instructs the communication node 400 to perform processing on the wireless tag 300. The network 500 may issue the instruction by transmitting any one of an RRC message, a NAS message, and an NG-AP message as a message including information indicating the instruction. The RRC message may be an RRCReconfiguration message, system information (SIB), or a paging message as in the first embodiment.

[0188] The instructions may include at least one of the following pieces of information:

[0189] First, the instruction may include an identifier of the wireless tag 300. The identifier may be represented by an identification code by EPC, as in the first embodiment. Alternatively, the identifier may be a list including a plurality of identifiers.

[0190] Second, the instruction may include processing details for the wireless tag 300. The processing details may be information instructing reading of information stored in the wireless tag 300, as in the first embodiment. Alternatively, the processing details may be information instructing writing to the wireless tag 300. When the processing details are writing to the wireless tag 300, the instruction may include data to be written. In this case, information instructing writing for each piece of data may be included in the instruction. When the processing details are writing to the wireless tag 300, the instruction may include information indicating a memory area to which the data is to be written. For example, the instruction may include information indicating which memory is the EPC memory, the TID memory, the USER memory, or the RESERVED memory. When the processing details are writing to the wireless tag 300, information indicating attributes of the data to be written may be included. The attributes of the data to be written may be, for example, information indicating data, locking the wireless tag 300, or disabling (killing) the wireless tag 300.

[0191] In step S71, the communication node 400 receives the instruction and performs the instructed process on the wireless tag 300. When receiving the instruction, the communication node 400 may read tag information from the wireless tag 300 again and check whether the wireless tag 300 that is the target of the instruction exists based on the read tag information. Alternatively, the communication node 400 may check whether the wireless tag 300 that is the target of the instruction exists based on tag information that has already been read from the wireless tag 300 at the time of receiving the instruction. After checking whether the wireless tag 300 that is the target of the instruction exists, the communication node 400 may perform the process indicated by the instruction on the wireless tag 300.

[0192] The process instructed by the instruction may be, for example, writing to the wireless tag 300, locking the wireless tag 300, or disabling (killing) the wireless tag 300. In this way, the process instructed by the instruction may be a process indicating control over the wireless tag 300. The process indicating control also includes the read instruction to the wireless tag 300 described in the first embodiment. This enables the network 500 to execute control over the wireless tag 300, for example. In other words, the first and seventh embodiments enable the establishment of a control plane (signaling) between the network 500 and the wireless tag 300.

[0193] In step S72, if the communication node 400 has successfully completed the instructed process for the wireless tag 300, it transmits an acknowledgment indicating that the instructed process has ended successfully to the network 500. The acknowledgment may include the identifier of the wireless tag 300 that the communication node 400 has processed. The acknowledgment may also include tag information that the communication node 400 has read in accordance with the instruction.

[0194] On the other hand, in step S72, if the communication node 400 is unable to normally complete the instructed process for the wireless tag 300, it transmits a negative response to the network 500 indicating that the instructed process did not end normally. The negative response may include, like the positive response, the identifier of the wireless tag 300 on which the communication node 400 performed the process. The negative response may also include cause information on why the process did not end normally. The cause information may be one or more of the following: the wireless tag 300 does not exist under its control; communication with the wireless tag 300 was not established; tag information from the wireless tag 300 could not be read; and tag information from the wireless tag 300 could not be written.

[0195] Note that the communication node 400 may transmit a message including the positive response and negative response to the network 500 using any of an RRC message, a NAS message, and an NG-AP message.

[0196] [Eighth embodiment] Next, an eighth embodiment will be described.

[0197] In the seventh embodiment, an example has been described in which the network 500 instructs a specific communication node 400 to execute processing on a specific wireless tag 300. The eighth embodiment is an embodiment regarding data exchange (user plane) with the wireless tag 300.

[0198] Specifically, first, the first communication node (e.g., gNB200 or AMF30 in network 500) sets up a communication path to the second communication node (e.g., UE100 or gNB200, which is communication node 400) that is linked to the identifier of a wireless tag (e.g., wireless tag 300) under the second communication node. Second, the second communication node exchanges data with the wireless tag via the communication path.

[0199] This allows, for example, the network 500 to exchange data with the wireless tag 300 via a communication path linked to the identifier of the wireless tag 300. Therefore, the wireless communication system 1 can perform appropriate communication with the wireless tag 300.

[0200] (Operation example according to the eighth embodiment) FIG. 18 is a diagram illustrating an example of operation according to the eighth embodiment.

[0201] 18, in step S80, the communication node 400 may transmit the identifier of the wireless tag 300 under its control to the network 500. The communication node 400 may transmit the message including the identifier of the wireless tag 300 using any of an RRC message, an NAS message, and an NG-AP message.

[0202] In step S81, the network 500 sets up a communication path. The communication path may be a PDU session (between the UPF and the UE 100). The network 500 may also set up a QoS flow (between the UPF and the gNB 200, or between the gNB 200 and the UE 100). The communication path may also be a radio access bearer (between the UPF and the gNB 200). The communication path may also be a radio bearer (between the gNB 200 and the UE 100). The linking setting for linking the identifier of the wireless tag 300 to the communication path is performed, for example, as follows.

[0203] First, when the network 500 is the AMF 30, the AMF 30 may associate a PDU session ID with the identifier of the wireless tag 300 for the PDU session. Also, the AMF 30 may associate a QFI (QoS flow ID) with the identifier of the wireless tag 300 for the QoS flow included in the PDU session.

[0204] Second, if the network 500 is a gNB200, the gNB200 may link the radio bearer ID with the identifier of the radio tag 300.

[0205] The communication path may also be a network slice (a single network slice, a group of network slices, or a network slice type that reads tag information may be defined and used). A network slice is a virtual network constructed by logically dividing a physical network built by a telecommunications carrier. In this case, AMF30 may perform the linking setting by linking the slice identifier of the network slice (S-NSSAI (Single Network Slicing Selection Assistance Information)) with the identifier of the radio tag 300.

[0206] The network 500 may use any one of an RRC message, a NAS message, and an NG-AP message as a message including information on the binding setting to transmit the message to the communication node 400. This allows the communication node 400 to acquire information on the binding setting of the communication path.

[0207] In step S82, the communication node 400 receives the DL data from the network 500 via the communication path.

[0208] In step S83, the communication node 400 transmits the received DL data to the wireless tag 300 linked to the communication path.

[0209] In step S84, the communication node 400 receives the UL data from the wireless tag 300. For example, the communication node 400 may read tag information from the wireless tag 300.

[0210] In step S85, the communication node 400 transmits the UL data to the network 500 via the communication path associated with the wireless tag 300.

[0211] Note that steps S84 and S85 may be performed before step S82.

[0212] [Ninth embodiment] Next, a ninth embodiment will be described. In the ninth embodiment, a communication node 400 notifies the network 500 that it has a wireless tag 300 under its control.

[0213] Specifically, the second communication node (for example, the UE 100 or the gNB 200 which is the communication node 400) transmits passive link information regarding the passive link between the second communication node and a wireless tag (for example, the wireless tag 300) to the first communication node (for example, the gNB 200 or the AMF 30 of the network 500). Here, the passive link information includes at least one of information indicating that the second communication node has a wireless tag under its control, information indicating that the passive link is supported, and information indicating the protocol of the passive link.

[0214] This allows the network 500 to know, for example, that the wireless tag 300 is under the control of the communication node 400, and enables appropriate processing of the wireless tag 300.

[0215] (Operation example according to the ninth embodiment) FIG. 19 is a diagram illustrating an example of operation according to the ninth embodiment.

[0216] As shown in FIG. 19 , in step S90, the communication node 400 transmits passive link information regarding the passive link between the communication node 400 and the wireless tag 300 under its control to the network 500. The passive link information may be information indicating that the communication node 400 has a wireless tag 300 under its control. In this case, the passive link information may be, for example, an identifier of the wireless tag 300. By receiving the passive link information including the identifier from the communication node 400, the network 500 can determine that the wireless tag 300 is under its control. The passive link information may also be information indicating that a passive link is supported between the communication node 400 and the wireless tag 300. In this case, if the communication node 400 can support a passive link, regardless of whether it has a wireless tag 300 under its control, the communication node 400 may transmit information indicating that it supports the passive link as the passive link information. Furthermore, the passive link information may be information indicating the protocol of the supported passive link. The information may be, for example, information indicating that it is RFID, information indicating that it is NFC (Near Field Communication), a standard name indicating a protocol, etc. Note that the communication node 400 may transmit the message including the information about the passive link to the network 500 using any of an RRC message, a NAS message, and an NG-AP message.

[0217] In step S91, the network 500 performs either setting for the communication node 400 or communication with the wireless tag 300 via the communication node 400, taking into account the passive link information.

[0218] [Other embodiments] A program may be provided that causes a computer to execute each process performed by the UE 100, the gNB 200, or the AMF 30. The program may be recorded on a computer-readable medium. Using the computer-readable medium, the program can be installed on a computer. Here, the computer-readable medium on which the program is recorded may be a non-transitory recording medium. The non-transitory recording medium is not particularly limited, and may be, for example, a recording medium such as a CD-ROM or a DVD-ROM.

[0219] In addition, circuits that execute each process performed by UE100, gNB200, or AMF30 may be integrated, and at least a portion of UE100, gNB200, or AMF30 may be configured as a semiconductor integrated circuit (chip set, SoC: System on a chip).

[0220] As used in this disclosure, the terms "based on" and "depending on" do not mean "based only on" or "depending only on," unless expressly stated otherwise. The term "based on" means both "based only on" and "based at least in part on." Similarly, the term "depending on" means both "depending only on" and "depending at least in part on." Furthermore, the terms "include," "comprise," and variations thereof do not mean including only the listed items, but may mean including only the listed items or may include additional items in addition to the listed items. Furthermore, the term "or," as used in this disclosure, is not intended to mean an exclusive or. Furthermore, any reference to elements using designations such as "first," "second," etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used herein as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way. In this disclosure, where articles are added by translation, such as a, an, and the in English, these articles shall include the plural unless the context clearly indicates otherwise.

[0221] Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to the above, and various design changes can be made within the scope of the gist. Furthermore, it is also possible to combine all or part of each embodiment, each operation, each process, and each step within the scope of consistent combinations.

[0222] This application claims priority from Japanese Patent Application No. 2022-032193 (filed March 2, 2022), the entire contents of which are incorporated herein by reference.

[0223] (Addendum) The following additional notes are about the features of the above-described embodiment.

[0224] (1) A communication control method in a wireless communication system, comprising: a first communication node included in the network transmitting a predetermined message to a second communication node; and transmitting tag information read from the wireless tag by the second communication node to the first communication node in response to receiving the predetermined message. Communication control method.

[0225] (2) the step of transmitting to the first communication node includes a step of the second communication node reading the tag information from the wireless tag in response to receiving the predetermined message, and a step of the second communication node transmitting the tag information to the first communication node. The communication control method according to (1) above.

[0226] (3) The method further includes a step of the second communication node reading the tag information from the wireless tag, the step of transmitting to the first communication node includes a step of the second communication node reading the tag information and then transmitting the tag information to the first communication node in response to receiving the predetermined message; The communication control method according to (1) or (2) above.

[0227] (4) the step of transmitting to the first communication node includes a step of transmitting the tag information to the first communication node when the second communication node satisfies a predetermined condition; The predetermined condition is either that the identification information of the wireless tag included in the predetermined message matches the identification information of the wireless tag included in the tag information, or that the tag information is successfully read. A communication control method according to any one of (1) to (3) above.

[0228] (5) The step of transmitting to the first communication node includes a step of the second communication node transmitting the tag information to which additional information has been added to the first communication node. A communication control method according to any one of (1) to (4) above.

[0229] (6) The method further comprises a step in which the first communication node manages the tag information by linking it to the second communication node. A communication control method according to any one of (1) to (5) above.

[0230] (7) further comprising a step of the second communication node transmitting passive link information regarding the passive link between the second communication node and the wireless tag to the first communication node. A communication control method according to any one of (1) to (6) above.

[0231] (8) the passive link information includes at least one of information indicating that the wireless tag is under the control of the second communication node, information indicating that the passive link is supported, and information indicating a protocol of the passive link. A communication control method according to any one of (1) to (7) above.

[0232] (9) A communication control method in a wireless communication system, comprising: A step in which a first communication node included in the network sets a second communication node to monitor a wireless tag; the second communication node periodically reading tag information from the wireless tag in accordance with the setting; the second communication node transmitting predetermined tag information to the first communication node when tag information read from the wireless tag at a first timing differs from tag information read from the wireless tag at a second timing following the first timing, the predetermined tag information is either difference information indicating a difference between the tag information read at the first timing and the tag information read at the second timing, or the tag information read at the second timing. Communication control method.

[0233] (10) A communication control method in a wireless communication system, comprising: a step of reading tag information from the wireless tag by the user device in response to detecting a predetermined event; the user device transmitting the tag information to a communication node included in a network; The predetermined event is any one of a Registration Area Update, a Tracking Area Update, a RAN-based Notification Area Update, a handover, an RRC connection reestablishment, an RRC connection resume, and an RRC connection setup. Communication control method.

[0234] (11) A communication control method in a wireless communication system, comprising: a step in which a first communication node included in the network instructs a second communication node to perform processing on a wireless tag; the second communication node performing the process on the wireless tag in accordance with the instruction. Communication control method.

[0235] (12) The method further comprises a step in which the second communication node transmits to the first communication node either a positive response indicating that the processing has been completed successfully or a negative response indicating that the processing has not been completed successfully. The communication control method according to (11) above.

[0236] (13) Furthermore, the first communication node sets up a communication path associated with the identifier of the wireless tag under the second communication node to the second communication node; and a step of exchanging data between the second communication node and the wireless tag via the communication path. The communication control method according to (11) or (12) above.

[0237] (14) the exchanging step includes a step in which the second communication node receives the data from the first communication node via the communication path, and a step in which the second communication node transmits the data to the wireless tag linked to the communication path. A communication control method according to any one of (11) to (13) above.

[0238] (15) the exchanging step includes a step of the second communication node receiving the data from the wireless tag, and a step of the second communication node transmitting the data to the first communication node via the communication path. A communication control method according to any one of (11) to (14) above. [Explanation of symbols]

[0239] 1: Wireless communication system 10:NG-RAN 20:5GC(CN) 30:AMF 100:UE 110: Receiving unit 120: Transmitter 130: Control unit 140: Reader / writer 141: RFID antenna 200 :gNB 210: Transmission unit 220: Receiving unit 230: Control unit 250: Reader / writer 251: RFID antenna 300: Wireless tag 310: RFID antenna 320: Control unit 330: Memory 340 :Power supply 400: Communication node 500: Network

Claims

1. A communication control method in a wireless communication system, comprising: A first communication node included in the network instructs a second communication node to perform processing on a wireless tag; the second communication node performs the process on the wireless tag in accordance with the instruction; The operation is one of read, write, invalidate, and call. Communication control method.

2. The second communication node may further transmit to the first communication node either a positive response indicating that the process has been completed successfully or a negative response indicating that the process has not been completed successfully. The communication control method according to claim 1.

3. The method further comprises: the second communication node transmitting a message including information indicating a result of the processing to the first communication node. The communication control method according to claim 1.

4. The information indicating the result of the processing includes an identifier of the wireless tag, The first communication node further associates an identifier of the wireless tag with an identifier of the second communication node. The communication control method according to claim 3.

5. A communication node in a wireless communication system, a control unit that instructs other communication nodes to process the wireless tag; the other communication node performs the process on the wireless tag in accordance with the instruction; The operation is one of read, write, invalidate, and call. Communication node.

6. A wireless communication system having a first communication node and a second communication node included in a network, the first communication node instructs the second communication node to perform processing on the wireless tag; the second communication node performs the process on the wireless tag in accordance with the instruction; The operation is one of read, write, invalidate, and call. Wireless communication system.

7. A computer of a communication node in a wireless communication system, causing other communication nodes to execute a process to instruct the wireless tag to perform a predetermined process; the other communication node performs the predetermined process on the wireless tag in accordance with the instruction; The predetermined process is one of read, write, invalidate, and call. program.

8. A chipset for a communication node in a wireless communication system, comprising: instructing other communication nodes to perform processing on the wireless tag; the other communication node performs the process on the wireless tag in accordance with the instruction; The operation is one of read, write, invalidate, and call. Chipset.

Images