Communication control method, communication node, wireless communication system, program and chipset

Abstract

The wireless communication system communicates appropriately with the wireless tag. [Solution] One embodiment of the communication control method is a communication control method in a wireless communication system. The communication control method includes the step of a first communication node included in the network transmitting a predetermined message to a second communication node. The communication control method also includes the step of the second communication node transmitting tag information read from a wireless tag to the first communication node in response to receiving the predetermined message.

Description

Technical Field

[0006] , ,

[0005] , ,

[0001] The present disclosure relates to a communication control method, a communication node, a wireless communication system, a program, and a chipset.

Background Art

[0002] In 3GPP (The Third Generation Partnership Project), which is a standardization project for mobile communication systems, discussions are being held on Passive IoT (for example, refer to Non-Patent Document 1 to Non-Patent Document 3).

[0003] Passive IoT is a technology that supports, for example, ultra-low cost and ultra-low power devices.

Prior Art Documents

Non-Patent Documents

[0004]

Non-Patent Document 1

Non-Patent Document 2

Non-Patent Document 3

Summary of the Invention

[0005] The communication control method according to the 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. Further, the communication control method 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] The second aspect of the communication control method is a communication control method in a wireless communication system. The communication control method includes the step of a first communication node included in the network setting a second communication node to monitor a wireless tag. The communication control method also includes the step of the second communication node periodically reading tag information from the wireless tag according to the setting. Furthermore, the communication control method includes the step of transmitting predetermined tag information to the first communication node if the tag information read by the second communication node at a first timing differs from the tag information read by the wireless tag at a second timing following the first timing. 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.

[0007] The third aspect of the communication control method is a communication control method in a wireless communication system. The communication control method includes the step of a user device reading tag information from a wireless tag in response to detecting a predetermined event. The communication control method also includes the step of the user device transmitting the tag information to a communication node included in the network. Here, the predetermined event is any of the following: Registration Area Update, Tracking Area Update, RAN-based Notification Area Update, handover, RRC Reestablishment, RRC Resume, and RRC Setup.

[0008] The fourth aspect of the communication control method is a communication control method in a wireless communication system. The communication control method includes the step of a first communication node included in the network instructing a second communication node to process a wireless tag. The communication control method also includes the step of the second communication node processing the wireless tag in accordance with the instruction. [Brief explanation of the drawing]

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

Embodiments for Carrying Out the Invention

[0010] One aspect aims at enabling 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 while referring 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] (Configuration Example of Wireless Communication System) FIG. 1 is a diagram showing a configuration example of a wireless communication system according to the first embodiment. The wireless communication system 1 includes a mobile communication system which is a 5th generation system (5GS: 5th Generation System) conforming to the 3GPP standard. In the following, the 5GS will be taken as an example to describe the mobile communication system, but an LTE (Long Term Evolution) system may be at least partially applied. Also, a system after the 6th generation (6G) system may be at least partially applied as the mobile communication system. Note that the wireless communication system 1 may be a mobile communication system.

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

[0015] UE100 is a mobile wireless communication device. UE100 can be any device used by a user. Examples of UE100 include mobile phone terminals (including smartphones), tablet terminals, notebook PCs, communication modules (including communication cards or chipsets), sensors or devices attached to sensors, vehicles or devices attached to vehicles (Vehicle UE), and aircraft or devices attached to aircraft (Aerial UE).

[0016] NG-RAN10 includes base stations (referred to as "gNBs" in 5G systems) 200. The gNBs 200 are interconnected via the Xn interface, which is an inter-base station interface. Each gNB 200 manages one or more cells. The gNB 200 performs wireless communication with UEs 100 that have established a connection with its own cell. The gNB 200 has radio resource management (RRM) functions, user data routing functions (hereinafter simply referred to as "data"), and measurement and control functions for mobility control and scheduling. Note that "cell" is used as a term indicating the smallest unit of a wireless communication area. "Cell" is also used as a term indicating a function or resource that performs wireless communication with the UE 100. One cell belongs to one carrier frequency (hereinafter simply referred to as "frequency").

[0017] Furthermore, gNBs can also connect to the EPC (Evolved Packet Core), which is the core network of LTE. LTE base stations can also connect to 5GCs. LTE base stations and gNBs can also be connected via an inter-base station interface.

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

[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 UE100 or gNB200. The wireless tag 300 is also an information medium that uses radio waves or electromagnetic fields to write data to its built-in memory and read data from that 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) Figure 2 shows an example configuration of UE100 (user device) according to the first embodiment. UE100 comprises a receiving unit 110, a transmitting unit 120, and a control unit 130. UE100 may also include a reader / writer 140. The receiving unit 110 and the transmitting unit 120 constitute a wireless communication unit that performs wireless communication with gNB200.

[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 the radio signal received by the antenna into a baseband signal (received signal) and outputs it to the control unit 130.

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

[0023] The control unit 130 performs various control and processing in the UE100. Such processing includes processing in each layer 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 for processing by the processor. The processor may include a baseband processor and a CPU (Central Processing Unit). The baseband processor performs modulation, demodulation, encoding, and decoding of baseband signals. The CPU executes programs stored in memory and performs various processing. In the example shown below, the operation or processing in the UE100 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 unit 130. The reader / writer 140 communicates with the wireless tag 300 using RFID technology. RFID technology is a technology that uses radio waves or electromagnetic fields to write data to or read data from the wireless tag 300 contactlessly. The reader / writer 140 can also generate power for the wireless tag 300 using the radio waves or electromagnetic fields transmitted from the RFID antenna 141. The UE 100 can communicate wirelessly with the wireless tag 300 via the reader / writer 140. Note that the reader / writer 140 may have only a reader function and no writer function.

[0025] Furthermore, the reader / writer 140 can also communicate wirelessly with the wireless tag 300 using the 3GPP communication protocol. 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 by 3GPP. In addition, the reader / writer 140 can also communicate wirelessly with the wireless tag 300 using backscattering. In this case, the reader / writer 140 may include an antenna capable of transmitting and receiving frequency signals used for backscattering. Details of backscattering will be described later.

[0026] (Example of gNB configuration) Figure 3 is a diagram showing an example configuration of a gNB200 (base station) according to the first embodiment. The gNB200 comprises a transmitter 210, a receiver 220, a control unit 230, and a backhaul communication unit 240. The gNB200 may also include a reader / writer 250. The transmitter 210 and 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 communicates with the CN20.

[0027] The transmitting unit 210 performs various types of transmissions under the control of the control unit 230. The transmitting unit 210 includes an antenna and a transmitter. The transmitter converts the 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 the radio signal received by the antenna into a baseband signal (received signal) and outputs it to the control unit 230.

[0029] The control unit 230 performs various control and processing in the gNB200. Such processing includes processing in each layer 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 for processing by the processor. The processor may include a baseband processor and a CPU. The baseband processor performs modulation, demodulation, encoding, and decoding of baseband signals. The CPU executes programs stored in memory and performs various processing. In the example shown below, the operation or processing in the gNB200 may be performed by the control unit 230.

[0030] The backhaul communication unit 240 is connected to an adjacent base station via the Xn interface, which is an inter-base station interface. The backhaul communication unit 240 is connected to the AMF30 / UPF via the NG interface, which is an inter-base station-core network interface. The gNB200 may consist of a CU (Central Unit) and a DU (Distributed Unit) (i.e., functionally separated), and the two units may be connected by the F1 interface, which is a fronthaul interface.

[0031] The reader / writer 250 includes an RFID antenna 251. Under the control unit 230, the reader / writer 250 communicates with the wireless tag 300 via the RFID antenna 251. The reader / writer 250 uses radio waves or electromagnetic fields transmitted from the RFID antenna 251 to write data to and read data from the wireless tag 300 contactlessly. The reader / writer 250 can also generate power for the wireless tag 300 using radio waves or electromagnetic fields transmitted from the RFID antenna 251. The gNB200 can communicate wirelessly 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] Furthermore, the reader / writer 250 can also communicate wirelessly with the wireless tag 300 using the 3GPP communication protocol. 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 by 3GPP. Additionally, the reader / writer 250 can communicate wirelessly with the wireless tag 300 using backscattering. In this case, the reader / writer 250 may include an antenna capable of transmitting and receiving frequencies used in backscattering.

[0033] (Example of wireless tag configuration) Figure 4 is a diagram showing an example 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 supply 340.

[0034] The RFID antenna 310 uses RFID technology to communicate wirelessly with the UE100 or gNB200. As mentioned above, RFID technology includes both radio wave and electromagnetic induction methods.

[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 UE100 or gNB200, and a rectifier circuit provided in the RFID antenna 310 outputs a portion of the radio waves as a DC power supply to the control unit 320. 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, 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 the radio band using a modulation circuit or the like, and transmits the radio signal to the UE100 or gNB200. At this time, the RFID antenna 310 may also transmit the radio signal using the reflected waves of the received radio waves received from the UE100 or gNB200.

[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 UE100 and the RFID antenna 251 of the gNB200 are loop coil antennas. Even in the electromagnetic induction method, power to the control unit 320 can be obtained by a rectifier circuit, the received signal can be obtained by a demodulation circuit, and reflected waves may be used, just as in the radio wave method.

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

[0038] Memory 330 stores the identifier of the wireless tag 300 (or identification information of the wireless tag 300; hereinafter, "identifier" and "identification information" may be used interchangeably), and data. The memory 330 of the wireless tag 300 may adopt the EPC GEN2 (EPC (Electronic Product Code) Class 1 Generation 2) standard compliant with ISO / IEC 18000-63. Memory 330 conforming to the EPC GEN2 standard has four memory areas: USER memory, TID (Tag ID) memory, EPC memory, and RESERVED memory. USER memory is an area that users of the wireless tag 300 can freely write to and read from. TID memory is an area where the manufacturer and model information of the wireless tag 300 is written. TID memory is a read-only, non-write area. EPC memory is an area where the identifier of the wireless tag 300 is written. RESERVED memory is an area where the 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] Power source 340 is, for example, a power source that utilizes energy harvesting. The environment includes heat, vibration, motion, light, wind power, 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, power source 340 may use a battery power source.

[0040] Furthermore, the wireless tag 300 may not have a writer function to write data to the memory 330, but only a reader function to read data from the memory 330.

[0041] Furthermore, the wireless tag 300 can also communicate wirelessly with the UE100 or gNB200 using the 3GPP communication protocol. 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 by 3GPP.

[0042] In the following description, the communication method of the wireless tag 300 will be explained as utilizing RFID technology, but it is not limited to this. For example, the communication method of the wireless tag 300 may utilize a 3GPP-compliant communication protocol. Furthermore, the wireless tag 300 may communicate using backscattering.

[0043] (Protocol stack) Next, we will describe an example of a protocol stack configuration. Here, we will describe an example of a protocol stack configuration for the UE100, gNB200, and AMF30, excluding the wireless tag 300.

[0044] Figure 5 shows an example of the protocol stack configuration for a user-plane wireless interface that handles data.

[0045] The user plane radio interface protocol consists of a physical (PHY) layer, a MAC (Medium Access Control) layer, an RLC (Radio Link Control) layer, a PDCP (Packet Data Convergence Protocol) layer, and an SDAP (Service Data Adaptation Protocol) 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 UE100's PHY layer and the gNB200's PHY layer via a physical channel. The UE100's PHY layer receives downlink control information (DCI) transmitted from the gNB200 over the physical downlink control channel (PDCCH). Specifically, the UE100 performs blind decoding of the PDCCH using a Radio Network Temporary Identifier (RNTI) and acquires the successfully decoded DCI as the DCI addressed to its own UE. The DCI transmitted from the gNB200 has a CRC parity bit added, which is scrambled by the RNTI.

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

[0048] The RLC layer transmits data to the receiving RLC layer using the functions of the MAC layer and PHY layer. Data and control information are transmitted between the UE100's RLC layer and the gNB200's RLC layer via a logical channel.

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

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

[0051] Figure 6 shows an example of the protocol stack configuration for a wireless interface of a control plane that handles signaling (control signals).

[0052] The control plane's wireless interface protocol stack includes an RRC (Radio Resource Control) layer and a NAS (Non-Access Stratum) layer, instead of the SDAP layer shown in Figure 6.

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

[0054] The NAS, located above the RRC layer, handles session management and mobility management, among other things. NAS signaling is transmitted between the UE100's NAS and the AMF30's NAS. The UE100 also has application layers in addition to its wireless interface protocol. Furthermore, layers below the NAS are called AS (Access Stratum).

[0055] (Passive IoT) Passive IoT is a technology that supports devices that are, for example, ultra-low cost and ultra-low power. Hereafter, 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. The low power consumption of passive IoT devices means that they may not need batteries, or they may even be able to utilize energy harvesting.

[0057] Even passive IoT devices may have a built-in power supply. However, even in such cases, they can be powered by small-capacity batteries and / or energy harvesting, assuming low power consumption, thus achieving lower costs compared to devices that use large-capacity batteries.

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

[0059] One example of a target for passive IoT is RFID. RFID tags are classified into 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 primarily utilizes passive tags. Active tags are wireless tags that use a battery built into the tag as their power source. Semi-passive tags operate as passive tags under normal circumstances and become active tags upon request from a reader. Passive IoT may target, for example, semi-passive tags or active tags.

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

[0061] Furthermore, energy harvesting is one example of a target for passive IoT. As mentioned above, energy harvesting is a method of generating electricity from the environment. For example, energy harvesting generates electricity by converting energy such as vibration or heat into electrical energy. Energy harvesting may include solar panels or wind turbines. The low power consumption of passive IoT makes it possible to use energy harvesting as a power source. Since energy harvesting does not require charging or replacement like batteries, it can operate for long periods without maintenance.

[0062] (Challenges of Passive IoT) If passive IoT can be integrated into a 3GPP-compliant mobile communication system, then, for example, passive IoT devices can be managed using NG-RAN10 or CN20.

[0063] However, there are several challenges to consider when integrating passive IoT into mobile communication systems.

[0064] Figure 7 is a diagram illustrating the challenges of the passive IoT according to the first embodiment. In Figure 7, the network 500 and the communication node 400 are included in a mobile communication system compliant with 3GPP. The communication node 400 is a node that has a reader / writer function and communicates with the wireless tag 300. The communication node 400 is either UE100 or gNB200. On the other hand, the network 500 includes a device that communicates with the communication node 400. The network 500 is either CN20 or gNB200.

[0065] From the perspective of network 500 (CN20 or gNB200), there is an issue of whether to manage the wireless tag 300 as a wireless tag or as a UE100. If the wireless tag 300 can be managed as a UE100 in network 500, it will also be possible to treat the wireless tag 300 in the same way as a UE100.

[0066] Another issue is whether the reader function (and / or writer function) will be handled by the UE100 or the gNB200. Both the UE100 and the gNB200 can communicate directly with the wireless tag 300.

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

[0068] Thus, several challenges exist in integrating passive IoT into mobile communication systems. It will be understood that all or part of the above-mentioned challenges can be solved in the embodiments shown below.

[0069] (Passive IoT scenario) Three scenarios (scenario a, scenario b, and scenario c) are assumed to be scenarios in which passive IoT is used. In all three scenarios, a communication node 400 exists, but the communication node 400 may be, for example, a UE100 with a reader / writer 140, or a gNB200 with a reader / writer 250.

[0070] Figures 8(A) and 8(B) illustrate 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 Figure 8(A), the communication node 400 detects the wireless tag 300 when it passes through the gate, which is loaded onto a moving object such as a truck T (or pallet). The wireless tag 300 may be attached to each product. Alternatively, the 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 being shipped out of the factory or parts entering the factory.

[0072] The example in Figure 8(B) shows how a moving object (e.g., a person H or a moving vehicle) moves over a communication node 400 to detect a 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, for example, products loaded on a pallet can be managed.

[0073] Figures 9(A) to 9(C) illustrate scenario b according to the first embodiment. Scenario b is a scenario for managing wireless tags 300 located in a certain location. This location may be a factory (or warehouse) (Figure 9(A)), a specific area (Figure 9(B)), or the cargo on a truck T (Figure 9(C)). By managing the wireless tags 300 located in this location, the communication node 400 can perform tasks such as inventory management of products or parts within a factory, or management of products or parts loaded on a truck T.

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

[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 Figure 7 is basically applicable. That is, the network 500 and the communication node 400 are connected to a mobile communication system, and the wireless tag 300 is managed by the mobile communication system. In this case, the network 500 is either an AMF30 or a gNB200. The communication node 400 is either a gNB200 or a UE100. Specifically, the following combinations are possible.

[0078] In other words, network 500 may be AMF30 and communication node 400 may be gNB200. In this case, gNB200 has a reader / writer function (i.e., reader / writer 250) and communicates with the wireless tag 300. Between AMF30 (network 500) and gNB200 (communication node 400), for example, NG-AP messages using the NG-AP protocol are sent and received.

[0079] In another case, network 500 may be AMF30 and communication node 400 may be UE100. In this case, UE100 has a reader / writer function (i.e., reader / writer 140) and communicates with the wireless tag 300. Between AMF30 (network 500) and UE100 (communication node 400), for example, NAS messages using the NAS protocol are sent and received.

[0080] Furthermore, there are cases where network 500 is gNB200 and communication node 400 is UE100. In this case as well, UE100 has reader / writer functionality and communicates with the wireless tag 300. Between gNB200 (network 500) and UE100 (communication node 400), for example, RRC messages using the RRC protocol are sent and received.

[0081] Under these premises, in the first embodiment, firstly, a first communication node (e.g., AMF30 or gNB200) located within the network (e.g., network 500) transmits a predetermined message (e.g., a paging message) to a second communication node (e.g., communication node 400, which is gNB200 or UE100). Secondly, upon 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] Thus, 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 (Figures 9(A) to 9(C)), the communication node 400 can, triggered by the reception of a paging message, read tag information from a wireless tag 300 located or present in a certain location and transmit the tag information to the network 500. Thus, the wireless communication system 1 according to the first embodiment can communicate appropriately with the wireless tag 300.

[0084] (Example of operation according to the first embodiment) Figure 11 is a diagram illustrating an example of operation according to the first embodiment. In the example of operation shown in Figure 11, a paging message is used as an example of a predetermined message. Furthermore, before the operation shown in Figure 11 is performed, if the communication node 400 is UE100, it is assumed that UE100 is in an RRC idle state or an RRC inactive state.

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

[0086] If network 500 is AMF30 and communication node 400 is UE100, paging messages are sent as NAS messages. In this case, paging is core network-initiated (CN-initiated). Also, if network 500 is AMF30 and communication node 400 is gNB200, paging messages are sent as NG-AP messages. Furthermore, if network 500 is gNB200 and communication node 400 is UE100, paging messages are sent as RRC messages. In this case, paging is access network-initiated (AN-initiated).

[0087] Firstly, the paging message may include an identifier for the wireless tag 300 being called (Case A). This identifier may be an identification code used in Electronic Product Codes (EPCs). EPCs are identification codes standardized by the standardization body GS1. EPCs are a general term for identification codes written to wireless tags 300. Examples of EPC identification codes include SGTINs (Serialized Global Trade Item Numbers) used to manage things or products, SGLNs (Serialized Global Location Numbers) used to manage locations, and GRAIs (Global Returnable Asset Identifiers) used to manage assets such as pallets. Such EPC-compliant identification codes may be used as identifiers for wireless tags 300.

[0088] Furthermore, a group of identifiers may be used as the identifier for the wireless tag 300. For example, the identifier for the wireless tag 300 may be a list of identification codes provided by the EPC. 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. Using a group of tag identifiers as the identifier for the wireless tag 300 allows for batch processing of the wireless tags 300, which can be efficient in some cases.

[0089] Secondly, the paging message may include an indicator that instructs the wireless tag 300 to be invoked (Case B). This indicator may also be an indicator that instructs the tag information to be read.

[0090] However, the identifier of the wireless tag 300 in Case A may instruct a "call" to the wireless tag 300 having said identifier. Alternatively, the identifier of the wireless tag 300 in Case A may instruct a "read tag information" to the wireless tag 300 having said identifier.

[0091] Furthermore, the identifier of the device to be called (Case A) and the indicator that instructs the tag to be called (Case B) may be associated with a UEID. In this case, network 500 will perform paging to the UE100 that has the UEID and manages the wireless tag 300 to be called, for example. Also, if the communication node 400 is a gNB, the identifier of the device to be called (Case A) and the indicator that instructs the tag to be called (Case B) may be associated with a gNB ID and / or a cell ID.

[0092] In step S11, the communication node 400 performs a tag information reading process in response to receiving a paging message. The communication node 400 may perform the reading process in response to receiving a paging message containing an identifier to be called (Case A) or an indicator that instructs the tag to be called (Case B). RFID may be used for the reading process itself. 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 measured values ​​(e.g., temperature information) stored in the USER memory. Also, the tag information may be the battery level 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 met. If the communication node 400 determines that the predetermined condition is met (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 met (NO in step S12), the process proceeds to step S14.

[0094] The predetermined conditions are used to determine whether or not to transmit the tag information read during the tag information reading process to the network 500.

[0095] The predetermined conditions are, firstly, whether the identifier of the wireless tag 300 contained in the tag information read from the wireless tag 300 (for example, the identifier of the tag read from the EPC memory) matches the identifier of the wireless tag 300 to be called contained 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 contained 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 the tag information was successfully read if the paging message contains an indicator that instructs the wireless tag 300 to be called (case B). If the tag information was successfully read (YES in step S12), the process proceeds to step S13. On the other hand, if the tag information was not read (NO in step S12), the process proceeds to step S14.

[0097] In step S13, the communication node 400 sends tag information to the network 500. If the communication node 400 is UE100 and the network 500 is gNB200, step S13 may be performed by UE100 (communication node 400) sending an RRC message containing tag information to gNB200 (network 500). Also, if the communication node 400 is UE and the network 500 is AMF30, step S13 may be performed by UE100 (communication node 400) sending a NAS message containing tag information to AMF30. Furthermore, if the communication node 400 is gNB200 and the network 500 is AMF30, step S13 may be performed by gNB200 (communication node 400) sending an NG-AP message containing tag information to AMF30 (network 500).

[0098] In step S14, the communication node 400 does not respond to the paging message. However, in step S14, the communication node 400 may send a message (for example, an RRC message, a NAS message, or an NG-AP message) to the network 500 that includes at least one of the following: information indicating that reading the wireless tag 300 failed, information indicating that no information was read from the wireless tag 300, and information indicating that the information read from the wireless tag 300 does not meet predetermined conditions.

[0099] (Modification 1 of the first embodiment) In the first embodiment, a paging message was used as an example of a predetermined message. However, the predetermined message may be a message other than a paging message.

[0100] For example, if network 500 is gNB200 and communication node 400 is UE100, then the following applies:

[0101] Firstly, instead of a paging message, an RRC Reconfiguration message may be sent (step S10). The RRC Reconfiguration message includes the information contained in the paging message (step S10) as described in the first embodiment. The UE100 (communication node 400) triggers the reading of tag information upon receiving the RRC Reconfiguration message (step S11). If the UE100 meets predetermined conditions (YES in step S12), it sends an RRC Reconfiguration Complete message containing the tag information to the gNB200 (network 500) (step S13). The UE100 may also send UE Assistance Information (UAI) containing the tag information to the gNB200.

[0102] Secondly, instead of a paging message, an RRC reset message including measurement configuration may be sent (step S10). The measurement configuration includes the wireless tag 300 as the Measurement Object. The measurement configuration may also include reporting configurations, such as reporting conditions (whether reporting is performed periodically or when an event occurs). For example, the UE 100 periodically reads tag information and reports when predetermined conditions are met. Such predetermined events include, for example, changes in the read tag information (e.g., an increase or decrease in the number of wireless tags). The measurement configuration may also include predetermined conditions as described in the first embodiment. Furthermore, the measurement configuration may include communication conditions with the wireless tag 300. For example, it may specify whether tag information is read periodically or when an event occurs. The RRC reset message includes the information contained in the paging message (step S10) as described in the first embodiment. UE100 may send a Measurement Report including tag information if it meets the predetermined conditions (YES in step S12) and the reporting conditions (step S13). Alternatively, UE100 may send a Measurement Report including tag information if it meets the reporting conditions without considering the predetermined conditions (step S13).

[0103] Thirdly, a new message may be sent from gNB200 to UE100 (step S10). The new message may be a message instructing the wireless tag 300 to be read, such as "Passive IoT read indication". The new message may include the information contained in the paging message (step S10) described in the first embodiment.

[0104] The above is an example of an RRC message. A System Information Block (SIB) may also be used as an example of an RRC message. A System Information Block (SIB) can also be used to specify a particular wireless tag group. However, if network 500 is AMF30 and communication node 400 is UE100, a NAS message other than a paging message (step S10) may be used.

[0105] Furthermore, if network 500 is AMF30 and communication node 400 is gNB200, NG-AP messages other than paging messages (step S10) may be used. In this case, gNB200 (communication node 400) may send a new message containing tag information (such as TAG RESPONSE) to AMF30 (network 500) (step S13).

[0106] (Modification 2 of the first embodiment) In the first embodiment, when the communication node 400 is UE100, the description was based on the assumption that UE100 is in an RRC idle state or an RRC inactive state before performing the operation example shown in Figure 11. It may also be assumed that UE100 is in an RRC connected state. Even in this case, UE100 may monitor paging messages (step S10). Alternatively, if network 500 (AMF30 or gNB200) is aware that UE100 has a wireless tag 300 under its control, network 500 may send a NAS message or RRC message (RRC individual signaling) equivalent to a paging message to UE100 in an RRC connected state (step S10).

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

[0108] In the first embodiment, the communication node 400 read out the wireless tag 300 when it received 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 tags 300 under its control more actively than in the first embodiment.

[0109] Specifically, firstly, the second communication node (e.g., communication node 400) reads tag information from the wireless tag (e.g., wireless tag 300). Secondly, after the second communication node has read the tag information, it 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, triggered by the reception of a paging message, transmit tag information of a wireless tag 300 located or present in a certain location to the network 500 (for example, scenario b). Thus, the wireless communication system 1 according to the second embodiment can communicate appropriately with the wireless tag 300 and appropriately acquire tag information.

[0111] (Example of operation according to the second embodiment) Figure 12 is a diagram showing an example of operation according to the second embodiment. Note that when the communication node 400 is UE100, before the example of operation shown in Figure 12 is started, UE100 is in an RRC idle state or RRC inactive state, similar to the first embodiment.

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

[0113] In step S21, the network 500 sends a paging message to the communication node 400. The paging message contains 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 met. The predetermined condition can be either case A (the paging message contains the identifier of the wireless tag 300 to be called) or case B (the paging message contains an indicator that instructs the wireless tag 300 to be called).

[0115] In the case of Case A, for example, it would be as follows: 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 it does not exist (NO in step S22), the process proceeds to step S24.

[0116] In the case of Case B, for example, it would be as follows: The predetermined condition is whether or not the identifier of the wireless tag 300 exists in the tag information read from the wireless tag 300. If the identifier of the wireless tag 300 exists in the tag information read from the wireless tag 300 (YES in step S22), the process proceeds to step S23. If it does not exist (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 sends a response message containing tag information. The response message may be sent as an RRC message, a NAS message, or an NG-AP message.

[0118] In step S24, the communication node 400 does not respond to the paging message (step S21). In this case, the communication node 400 may send a message to the network 500 that includes any of the following: 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 met. This message may also be sent as an RRC message, a NAS message, or an NG-AP message.

[0119] In the example shown in Figure 12, a paging message (step S21) was used as an example. As with the first embodiment, other messages may also be used.

[0120] Furthermore, in the example of operation shown in Figure 12, similar to the modification 2 of the first embodiment, if the communication node 400 is UE100, UE100 may be in a connected state. For example, UE100 may enter an RRC connected state due to a paging message, and then a NAS message or RRC message (step S21) may trigger the transmission of tag information to the network 500 (step S23). The NAS message or RRC message may contain information included in the paging message (step S10 in Figure 11), such as the identifier (list) of the wireless tag 300, similar to the first embodiment.

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

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

[0123] Specifically, firstly, a first communication node (e.g., AMF30 or gNB200) located within the network (e.g., network 500) configures a second communication node (e.g., communication node 400, which is gNB200 or UE100) to monitor a wireless tag (e.g., wireless tag 300). Secondly, the second communication node periodically reads tag information from the wireless tag according to the configuration. Thirdly, if the tag information read by the second communication node at the first timing differs from the tag information read at the second timing following the first timing, it 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 communicate appropriately with the wireless tag 300 and appropriately transmit any changed tag information read from the wireless tag 300 to the network 500. Therefore, the network 500 can also properly manage the tag information.

[0125] For example, in scenario a (Figure 8(B)), if there are multiple wireless tags 300 on the pallet, the communication node 400 periodically reads the tag information. 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 a new part if a new part is found on the pallet, thereby enabling proper management of the new part.

[0126] "A change in tag information" refers, for example, to a situation where the tag information read at the first timing point differs from the tag information read at the second timing point (which follows the first timing point or occurs at a later timing point than the first timing point).

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

[0128] As shown in Figure 13, in step S30, the network 500 sends a configuration message to the communication node 400. This allows the network 500 to configure periodic tag monitoring for the communication node 400. The configuration message is sent as either an RRC message, a NAS message, or an NG-AP message. The configuration message includes at least one of the following pieces of information.

[0129] Firstly, the configuration message may include a reading interval (or reading time). The reading interval may be a timer value. For example, the communication node 400 starts counting the timer from the time it receives the configuration message, and when the timer reaches the timer value and the timer expires, it performs the reading process of the wireless tag 300 and restarts the timer.

[0130] Secondly, the configuration message may include information instructing the wireless tag 300 to be monitored periodically. For example, the communication node 400 may read the tag information (at an implementation-dependent timing) in accordance with the instruction.

[0131] Thirdly, the configuration message may include an identifier for the wireless tag 300 to be periodically monitored. The communication node 400 designates the wireless tag 300 having this identifier as the wireless tag to be periodically monitored.

[0132] Fourth, the configuration message may include information regarding reporting conditions. Reporting conditions include reporting each time tag information is read (periodic) or reporting only when there is a change in the tag information (event-trigger). In the case of periodic, information representing the reporting interval (which may be a timer value) is included. In the case of event-trigger, the trigger for reporting is when there is a change in the tag information. It may also be when there is a change in the measured value obtained as tag information. In the case of event-trigger, the trigger for reporting may also be when the number of wireless tags 300 increases (or when the identifiers of wireless tags 300 included in the read tag information increase compared to the identifiers of wireless tags 300 read previously). Alternatively, in the case of event-trigger, the trigger for reporting may be when the number of wireless tags 300 decreases (or when the identifiers of wireless tags 300 included in the read tag information decrease compared to the identifiers of wireless tags 300 read previously).

[0133] Fifth, the configuration message may include information indicating the content of the report. For example, it may include information indicating that all of the read tag information will be reported. Or, it may include information indicating that tag information that has changed will be reported. In this case, it may include information indicating which event caused the report. For example, communication node 400 can report to network 500, according to this information, that "wireless tag #2 has entered the network of communication node 400, so tag information has been sent."

[0134] In step S31, the communication node 400 monitors the wireless tag 300 according to the settings included in the configuration message. The communication node 400 reads the tag information from the wireless tag 300 according to the settings.

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

[0136] The reporting conditions may include reporting for each tag information reading process (periodic) or reporting only when there is a change in the tag information (event-trigger), as specified in the configuration message (step S30). If the configuration message does not include reporting conditions, they may be pre-configured, for example. 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 tag information to the network 500. The transmitted tag information is predetermined tag information. The predetermined tag information may be the difference between the tag information read at the first timing and the tag information read at the second timing following (or at a timing later than the first timing). Alternatively, the predetermined tag information may be the tag information read at the second timing. The tag information may be transmitted in the RRC message, as in the first embodiment. Alternatively, the tag information may be transmitted in the NAS message. Alternatively, the tag information may be transmitted in the 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 UE100. In the fourth embodiment, an example is described in which UE100 reads tag information from the wireless tag 300 when it detects a predetermined event and transmits it to the network 500 (AMF30 or gNB200).

[0140] Specifically, firstly, the user device (e.g., UE100) reads tag information from the wireless tag (e.g., wireless tag 300) in response to detecting a predetermined event. Secondly, the user device transmits the tag information to a communication node (e.g., AMF30 or gNB200) included in the network (e.g., network 500). Here, the predetermined event is one of the following: Registration Area Update, Tracking Area Update, RAN-based Notification Area Update, handover, RRC Reestablishment, RRC Resume, or RRC Setup.

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

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

[0143] As shown in Figure 14, in step S40, the network 500 may send a configuration message to the UE 100. The configuration message may include information indicating permission (or request) for the transmission of tag information. The configuration message is sent as an RRC message or a NAS message. In the case of an RRC message, the configuration message may be announced by a System Information Block (SIB). Alternatively, the configuration message may be sent by a paging message as described in the first embodiment.

[0144] In step S41, the UE100 detects a predetermined event. Examples of predetermined events include the following:

[0145] (1) Firstly, the predetermined events include at least one of the following: Registration Area Update (RAU), Tracking Area Update (TAU), and RAN-based Notification Area Update (RNAU). The Tracking Area (TA) is, for example, an area containing one or more cells that a UE100 in an RRC idle state can move to without performing an update to the MME. The RAN Notification Area (RNA) is, for example, an area containing one or more cells that a UE100 in an RRC inactive state can move to without performing a notification to the NG-RAN10. The Registration Area (RA) is, for example, an area containing multiple tracking areas that a UE100 can move to without performing a registration procedure to the network. The update process performed when a UE100 moves to such an area may be the predetermined event. Note that the TAU is performed between the UE100 and the MME, but it may also be performed between the UE100 and the AMF30. The following provides a detailed explanation.

[0146] (1-1) When network 500 is gNB200 Specifically, the predetermined event may be at least one of the following: when UE100 sends an RRC Restart Request (RRCResumeRequest) message in response to an RAU, TAU, or RNAU; when UE100 receives an RRC Restart (RRCResume) message; or when UE100 sends an RRC Restart Complete (RRCResumeComplete) message. The time when UE100 sends or receives such a message may be considered the detection of the predetermined event.

[0147] (1-2) When Network 500 is AMF30 Specifically, the predetermined event may be at least one of the following: when UE100 sends a registration request message associated with the RAU, or when UE100 receives a registration accept message associated with the RAU. The moment UE100 sends or receives such a message may be considered the detection of the predetermined event.

[0148] (2) Secondly, the specified event may be a handover. Specifically, if network 500 is gNB200, the event may be any of the following: when UE100 receives an RRCReconfiguration message associated with a handover, when it initiates access to the target cell, or when it sends an RRCReconfigurationComplete message associated with a handover. When it initiates access to the target cell, it may be at least either when it initiates the RACH (Random Access Channel) procedure or when it completes the RACH procedure.

[0149] (3) Thirdly, a predetermined event may be when the UE100 re-establishes the RRC connection. Specifically, this may be at least one of the following: when the network 500 is gNB200 and the UE100 sends an RRCReestablishmentRequest message, when the UE100 receives an RRCReestablishment message, or when the UE100 sends an RRCReestablishmentComplete message.

[0150] (4) Fourthly, a predetermined event may be when the UE100 resumes the RRC connection. Specifically, this may be at least one of the following: when the network 500 is gNB200 and the UE100 sends an RRC resumption request message, when the UE100 receives an RRC resumption message, and when the UE100 sends an RRC resumption complete message.

[0151] (5) Fifth, a predetermined event may be when the UE100 sets up the RRC connection. Specifically, the network 500 is the gNB200 and the UE100 sends an RRC setup request message, the UE100 receives an RRC setup message, and the UE100 sends an RRC setup complete message, at least one of these.

[0152] In step S42, the UE100 performs a tag information reading process for the wireless tag 300 in response to detecting a predetermined event.

[0153] If UE100 successfully reads the tag information, in step S43 it sends information to the network 500 indicating that it has tag information.

[0154] For example, if network 500 is gNB200, UE100 will include this information in either message 3 (MSG3) or message 5 (MGS5) in the RACH procedure. This information could be, for example, "tag available".

[0155] For example, if network 500 is AMF30, UE100 will send a NAS message containing information indicating that it has tag information.

[0156] Then, if UE100 successfully reads the tag information, it sends 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 of the RACH procedure and send it. Alternatively, UE100 may include the tag information in UEAssistanceInformation and send it. Furthermore, if there is a difference in the tag information in step S44 (i.e., there is a difference between the tag information obtained in a previous tag information reading process and the tag information obtained in the current tag information reading process), UE100 may send the tag information (i.e., the tag information obtained in the current tag information reading process). Alternatively, UE100 may send information about the difference.

[0157] If UE100 fails to read the tag information in the tag information reading process (step S42), it does not need to perform steps S43 and S44. Alternatively, if UE100 fails to read the tag information, it may send a message (RRC message or NAS message) to the network 500 that indicates that it failed to read the tag information. Alternatively, UE100 may send a message (RRC message or NAS message) to the network 500 that indicates that there was no tag information in the wireless tag 300.

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

[0159] In the fifth embodiment, the UE100 adds additional information to the tag information transmitted to the network 500 before sending it.

[0160] Specifically, the second communication node (for example, UE100 or gNB200, which is communication node 400) transmits tag information with additional information attached to it to the first communication node (for example, AMF30 or gNB200, which is included in network 500).

[0161] This allows, for example, network 500 to properly manage products to which wireless tags 300 are attached by utilizing additional information.

[0162] (Example of operation according to the fifth embodiment) Figure 15 is a diagram illustrating an example of operation according to the fifth embodiment. Figure 15 mainly shows the processing performed at the communication node 400 (UE100 or gNB200).

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

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

[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 types of information.

[0166] Firstly, the additional information may be time information. The time information may be information that represents the time when the communication node 400 read the tag information. For example, the time information may be the date and time (day or time) when the communication node 400 read the tag information. Alternatively, the time information may be the frame number of the wireless frame at the time the communication node 400 read the tag information. If the communication node 400 is gNB200, the wireless frame may be the wireless frame when gNB200 communicates wirelessly with UE100. Alternatively, if the communication node 400 is UE100, the wireless frame may be the wireless frame when UE100 communicates wirelessly with gNB200.

[0167] Secondly, the additional information may be location information. The location information may be any information that represents the location where the communication node 400 read the tag information. For example, the location information may be represented by latitude and longitude. In addition, the location information may include altitude in addition to latitude and longitude. Also, for example, the location information may be represented by an RF fingerprint. Furthermore, the location information may be location information obtained from beacon information such as surrounding Wi-Fi® or Bluetooth®.

[0168] Thirdly, the additional information may also be received signal information relating to the received signal. The received signal information may be the received power (e.g., RSRP (Reference Signal Received Power)) and / or received quality (e.g., RSRQ (Reference Signal Received Quality)) of the 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 [transmission power of wireless tag 300] - [received power at communication node 400]. Also, if the received power of the wireless tag 300 is feedbackable, the communication node 400 obtains the propagation loss by [transmission power of communication node 400 to wireless tag 300] - [received power at wireless tag 300]. In this case, for example, the wireless tag 300 stores the received power value in USER memory, and the communication node 400 can obtain the received power value by reading the information from USER memory. When the wireless tag 300 transmits a transmitted wave (reflected wave) using backscattering, the communication node 400 can obtain the propagation loss by subtracting the received power of the communication node 400 from the transmitted power of the communication node 400.

[0169] These additional pieces of information are configured by a configuration message (either an RRC message, a NAS message, or an NG-AP message) sent from network 500, and communication node 400 may add the additional information to the tag information according to that configuration. The configuration message may include information indicating what to add as additional information. If that information is, for example, location information, communication node 400 will add the location information to the tag information as additional information.

[0170] In step S53, the communication node 400 transmits tag information with additional information to the network 500 in response to detecting a predetermined event. 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 terminates 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 associating it with the communication node 400. In the sixth embodiment, the network 500 stores the tag information associated with the communication node 400 as part of the context of the communication node 400.

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

[0175] This allows, for example, network 500 to link tag information with communication node 400, enabling proper management of tag information. Furthermore, network 500 can manage tag information as part of UE100's context information (UE Context), making it possible to transmit tag information to other networks 500 as part of UE100's context information.

[0176] Furthermore, UE context information includes, for example, information that uniquely identifies UE100 in gNB200, such as the cell ID (PCI (Physical Cell ID), etc.) and / or the UE identifier (C-RNTI (Cell-Radio Network Temporary Identifier), etc.).

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

[0178] As shown in Figure 16, in step S60, the communication node 400 transmits tag information to the network 500. The communication node 400 transmits the tag information as a message, for example, using one of the following: an RRC message, a NAS message, or an NG-AP message, similar to the first embodiment.

[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 the identification information of the communication node 400. The network 500 may store the tag information in memory as (part of) the context information of the communication node 400. The context information of the communication node 400 may include, for example, the identification information of the communication node 400.

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

[0181] In step S63, network 500 may transmit the tag information to another network 510 as context information for communication node 400 in the event of a predetermined transmission event. The predetermined transmission event may also occur when another network 510 requests the context information for communication node 400. For example, network 500 may transmit the tag information when requested by another network 510 in the event of RAU, TAU, RNAU, RRC connection re-establishment, or RRC connection resumption. Alternatively, the predetermined transmission event may occur when another network 510 requests the transfer of context information for communication node 400. For example, network 500 may transmit the tag information when another network 510 requests the transfer of context information in connection with a handover. Network 500 may also transmit the tag information (step S63) by sending either an Xn message containing the tag information or an NG message containing the tag information to the other network 510.

[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 perform processing on a specific wireless tag 300. In the first embodiment, the reading process for the wireless tag 300 was mainly described, but in the seventh embodiment, processing other than the reading process will be described.

[0184] Specifically, firstly, a first communication node (e.g., gNB200 or AMF30) located within the 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). Secondly, the second communication node performs the processing on the wireless tag in accordance with the instruction.

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

[0186] (Example of operation according to the 7th embodiment) Figure 17 is a diagram illustrating an example of operation according to the seventh embodiment.

[0187] As shown in Figure 17, in step S70, the network 500 instructs the communication node 400 to process the wireless tag 300. The network 500 may give this instruction by sending one of the following as a message containing information indicating the instruction: an RRC message, a NAS message, or an NG-AP message. The RRC message may be an RRC Reconfiguration message, a System Information Board (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] Firstly, the instruction may include an identifier for the wireless tag 300. This identifier may be represented by an identification code by EPC, as in the first embodiment. Alternatively, the identifier may be a list containing multiple identifiers.

[0190] Secondly, the instruction may include processing details for the wireless tag 300. The processing details may be information instructing the reading of information stored in the wireless tag 300, similar to the first embodiment. Alternatively, the processing details may be information indicating writing to the wireless tag 300. If the processing details are writing to the wireless tag 300, the instruction may include the data to be written. In this case, the instruction may include information instructing writing for each piece of data. If the processing details are writing to the wireless tag 300, the instruction may include information indicating the memory area to which the data is to be written. For example, the instruction may include information indicating which of the EPC memory, TID memory, USER memory, and RESERVED memory it is. If the processing details are writing to the wireless tag 300, the instruction may include information indicating the attributes of the data to be written. The attributes of the data to be written may include, for example, information indicating data, a lock on the wireless tag 300, or the invalidation (kill) of the wireless tag 300.

[0191] In step S71, the communication node 400 receives the instruction and performs the instructed processing on the wireless tag 300. When the communication node 400 receives the instruction, it may read the tag information from the wireless tag 300 again and check whether the wireless tag 300 to be instructed exists based on the read tag information. Alternatively, the communication node 400 may check whether the wireless tag 300 to be instructed exists based on the tag information already read from the wireless tag 300 at the time the instruction is received. After confirming that the wireless tag 300 to be instructed exists, the communication node 400 may perform the processing 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. Thus, the process instructed by the instruction may also be a process that indicates control over the wireless tag 300. As a process that indicates control, a read instruction for the wireless tag 300 described in the first embodiment is also included. This makes it possible for the network 500 to perform control over the wireless tag 300. In other words, the first and seventh embodiments make it possible to establish a control plane (signaling) between the network 500 and the wireless tag 300.

[0193] In step S72, if the communication node 400 successfully completes the instructed processing for the radio tag 300, it sends an acknowledgment to the network 500 indicating that the instructed processing was successfully completed. The acknowledgment may include the identifier of the radio tag 300 that the communication node 400 processed. The acknowledgment may also include the tag information that the communication node 400 read in accordance with the instructions.

[0194] On the other hand, in step S72, if the communication node 400 is unable to successfully complete the instructed processing for the radio tag 300, it sends a negative response to the network 500 indicating that the instructed processing did not complete successfully. The negative response may include, like the positive response, the identifier of the radio tag 300 that the communication node 400 processed. The negative response may also include information about the cause of the failure to complete successfully. This cause information may be one or more of the following: the radio tag 300 is not located under its control; communication with the radio tag 300 could not be established; the tag information of the radio tag 300 could not be read; or the tag information could not be written to the radio tag 300.

[0195] Furthermore, the communication node 400 may send a message containing acknowledgments and denials to the network 500 using either an RRC message, a NAS message, or an NG-AP message.

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

[0197] The seventh embodiment describes an example in which the network 500 instructs a specific communication node 400 to perform processing on a specific wireless tag 300. The eighth embodiment is an embodiment of data exchange (user plane) with respect to the wireless tag 300.

[0198] Specifically, firstly, the first communication node (for example, gNB200 or AMF30 in network 500) configures a communication path for the second communication node (for example, UE100 or gNB200, which is communication node 400) that associates the identifier of the wireless tag (for example, wireless tag 300) under the second communication node. Secondly, the second communication node exchanges data with the wireless tag via the communication path.

[0199] This allows, for example, network 500 to exchange data with wireless tag 300 via a communication channel associated with the identifier of wireless tag 300. Consequently, wireless communication system 1 can communicate appropriately with wireless tag 300.

[0200] (Example of operation according to the 8th embodiment) Figure 18 is a diagram illustrating an example of operation according to the eighth embodiment.

[0201] As shown in Figure 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 identifier of the wireless tag 300 as a message using one of the following: an RRC message, a NAS message, or an NG-AP message.

[0202] In step S81, network 500 configures a communication path. The communication path may be a PDU session (between UPF and UE100). Network 500 may also be a QoS flow (between UPF and gNB200, or between gNB200 and UE100). The communication path may also be a wireless access bearer (between UPF and gNB200). The communication path may also be a wireless bearer (between gNB200 and UE100). The association setting to link the identifier of the wireless tag 300 to the communication path is performed, for example, as follows.

[0203] Firstly, if network 500 is AMF30, AMF30 may associate the PDU session ID with the identifier of the wireless tag 300 for each PDU session. Furthermore, AMF30 may associate the QFI (QoS flow ID) with the identifier of the wireless tag 300 for each QoS flow included in the PDU session.

[0204] Secondly, if network 500 is gNB200, gNB200 may associate the wireless bearer ID with the identifier of the wireless tag 300.

[0205] The communication channel may also be a network slice (a single network slice, a grouped network slice, 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 the physical network built by the telecommunications carrier. In this case, the 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 wireless tag 300.

[0206] Network 500 may send a message containing the linking settings information to communication node 400 using either an RRC message, a NAS message, or an NG-AP message. This allows communication node 400 to obtain the linking settings information for the communication path.

[0207] In step S82, the communication node 400 receives 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 associated with the communication channel.

[0209] In step S84, the communication node 400 receives 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 channel associated with the wireless tag 300.

[0211] Steps S84 and S85 may be performed before step S82.

[0212] [Ninth Embodiment] Next, the ninth embodiment will be described. The ninth embodiment is an embodiment in which 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, UE100 or gNB200, which is communication node 400) transmits passive link information regarding the passive link between the second communication node and the wireless tag (for example, wireless tag 300) to the first communication node (for example, gNB200 or AMF30 in network 500). Here, the passive link information includes at least one of the following: information indicating that the second communication node has a wireless tag under its control; information indicating that it supports the passive link; and information indicating the protocol of the passive link.

[0214] This allows, for example, network 500 to recognize the presence of a wireless tag 300 under the communication node 400, and to process the wireless tag 300 appropriately.

[0215] (Example of operation according to the 9th embodiment) Figure 19 is a diagram illustrating an example of operation according to the ninth embodiment.

[0216] As shown in Figure 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 also 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, the identifier of the wireless tag 300. By receiving the passive link information containing the identifier from the communication node 400, the network 500 can determine that a wireless tag 300 exists under the communication node 400. The passive link information may also be information indicating that the communication node 400 supports a passive link between the communication node 400 and the wireless tag 300. In this case, the communication node 400 may transmit information indicating that it supports a passive link as passive link information, regardless of whether it has a wireless tag 300 under its control, as long as it can support a passive link. Furthermore, the passive link information may also be information indicating the supported passive link protocol. This information may include, for example, information indicating that it is RFID, information indicating that it is NFC (Near Field Communication), or a standard name indicating the protocol. The communication node 400 may also send a message containing information about the passive link to the network 500 using one of the following: an RRC message, a NAS message, or an NG-AP message.

[0217] In step S91, the network 500 takes passive link information into consideration and either configures the communication node 400 or communicates with the wireless tag 300 via the communication node 400.

[0218] [Other embodiments] A program may be provided that causes a computer to perform each of the processes performed by UE100, gNB200, or AMF30. The program may be recorded on a computer-readable medium. Using a computer-readable medium, it is possible to install the program on a computer. Here, the computer-readable medium on which the program is recorded may be a non-transient recording medium. The non-transient recording medium is not particularly limited, but may be a recording medium such as a CD-ROM or DVD-ROM.

[0219] Alternatively, the circuits that perform each of the processes carried out 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 (chipset, SoC: System on a chip).

[0220] The terms “based on” and “depending on” used in this disclosure do not mean “based solely on” or “depending solely on” unless otherwise specified. “Based on” means both “based solely on” and “at least partially on.” Similarly, “depending on” means both “at least partially on” and “at least partially on.” Furthermore, the terms “include,” “comprise,” and variations thereof do not mean that only the listed items are included; they may include only the listed items, or they may include additional items in addition to the listed items. Also, the term “or” used in this disclosure is not intended to mean exclusive OR. Moreover, any reference to elements using designations such as “first,” “second,” etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used herein as a convenient way to distinguish between two or more elements. Therefore, references to the first and second elements do not imply that only two elements may be adopted therein, or that the first element must precede the second element in any way. In this disclosure, where articles are added by translation, such as a, an, and the in English, these articles shall be plural unless it is clearly indicated by the context that they are not.

[0221] Although one embodiment has been described in detail above with reference to the drawings, the specific configuration is not limited to that described above, and various design changes can be made without departing from the gist of the work. Furthermore, it is possible to combine all or part of each embodiment, each operation, each process, and each step, as long as they do not contradict each other.

[0222] This application claims priority to Japanese Patent Application No. 2022-032193 (filed on March 2, 2022), and all of its contents are incorporated into the specification of this application.

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

[0224] (1) A communication control method in a wireless communication system, The first communication node included in the network sends a predetermined message to the second communication node, The second communication node, upon receiving the predetermined message, transmits the tag information read from the wireless tag to the first communication node. Communication control method.

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

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

[0227] (4) The step of transmitting to the first communication node includes the step of the second communication node transmitting the tag information to the first communication node if predetermined conditions are met. The predetermined conditions are either when 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 when the tag information is successfully read. A communication control method as described in any of (1) to (3) above.

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

[0229] (6) Furthermore, the first communication node has the step of associating the tag information with the second communication node and managing it. A communication control method as described in any of (1) to (5) above.

[0230] (7) Furthermore, the second communication node includes the step of transmitting passive link information relating to the passive link between the second communication node and the wireless tag to the first communication node. A communication control method as described in any of (1) to (6) above.

[0231] (8) The passive link information includes at least one of the following: information indicating that the second communication node has the wireless tag under its control; information indicating that it supports the passive link; and information indicating the protocol of the passive link. A communication control method as described in any of (1) to (7) above.

[0232] (9) A communication control method in a wireless communication system, The first communication node included in the network configures the second communication node to monitor wireless tags, The second communication node periodically reads tag information from the wireless tag according to the settings, The second communication node includes the step of transmitting predetermined tag information to the first communication node if the tag information read from the wireless tag at a first timing differs from the tag information read from the wireless tag at a second timing following the first timing. 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. Communication control method.

[0233] (10) A communication control method in a wireless communication system, The user device reads tag information from a wireless tag in response to detecting a predetermined event, The user device has the step of transmitting the tag information to a communication node included in the network, The aforementioned predetermined event is one of the following: Registration Area Update, Tracking Area Update, RAN-based Notification Area Update, Handover, RRC Reestablishment, RRC Resume, and RRC Setup. Communication control method.

[0234] (11) A communication control method in a wireless communication system, The first communication node included in the network instructs the second communication node to process the wireless tag, The second communication node performs the processing on the wireless tag in accordance with the instructions. Communication control method.

[0235] (12) Furthermore, the second communication node sends to the first communication node either an affirmative response indicating that the process was completed successfully, or a negative response indicating that the process was not completed successfully. The communication control method described in (11) above.

[0236] (13) Furthermore, the first communication node performs the step of setting up a communication path for the second communication node, which is associated with the identifier of the wireless tag under the second communication node. The second communication node has the step of exchanging data with the wireless tag via the communication path. The communication control method described in (11) or (12) above.

[0237] (14) The exchange step includes the step of the second communication node receiving the data from the first communication node via the communication path, and the step of the second communication node transmitting the data to the wireless tag associated with the communication path. A communication control method as described in any of (11) to (13) above.

[0238] (15) The exchange step includes the step of the second communication node receiving the data from the wireless tag, and the step of the second communication node transmitting the data to the first communication node via the communication path. A communication control method as described in any of (11) to (14) above. [Explanation of Symbols]

[0239] 1: Wireless communication system 10: NG-RAN 20:5GC(CN) 30: AMF 100 :UE 110: Receiver 120: Transmitter 130: Control Unit 140: Reader / Writer 141: RFID antenna 200 :gNB 210: Transmitter 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, A communication node receives a first message from another communication node containing instructions regarding the processing of a radio tag, The communication node performs the processing on the wireless tag in accordance with the instructions, The communication node transmits a second message containing information indicating the result of the processing to the other communication node, The aforementioned process is one of the following: reading, writing, invalidating, or calling. Communication control method.

2. The information indicating the result of the processing includes either an affirmative response indicating that the processing was completed successfully, or a negative response indicating that the processing was not completed successfully. Communication control method according to claim 1

3. The information indicating the result of the processing includes the identifier of the wireless tag, The identifier of the wireless tag is associated with the identifier of the other communication node. The communication control method according to claim 1.

4. A communication node in a wireless communication system, A receiving unit that receives a first message from another communication node containing instructions regarding the processing of a wireless tag, A control unit that performs the processing on the wireless tag in accordance with the instructions, The system includes a transmitting unit that transmits a second message containing information indicating the result of the processing to the other communication node, The aforementioned process is one of the following: reading, writing, invalidating, or calling. Communication node.

5. A wireless communication system having a communication node and other communication nodes, The communication node receives a first message from the other communication node, which includes instructions regarding the processing of the wireless tag. The communication node performs the processing on the wireless tag in accordance with the instructions. The communication node transmits a second message containing information indicating the result of the processing to the other communication node. The aforementioned process is one of the following: reading, writing, invalidating, or calling. Wireless communication system.

6. In the computer of the communication node in the wireless communication system, The process involves receiving a first message from another communication node that includes instructions regarding predetermined processing for a wireless tag, The process of performing the predetermined processing on the wireless tag in accordance with the above instructions, The process involves sending a second message containing information indicating the result of the predetermined process to the other communication node, The predetermined process is one of the following: reading, writing, invalidating, or calling. program.

7. A chipset for a communication node in a wireless communication system, Receiving a first message from another communication node containing instructions on how to process the wireless tag, Perform the above processing on the wireless tag in accordance with the above instructions, The process includes sending a second message containing information indicating the result of the process to the other communication node, The aforementioned process is one of the following: reading, writing, invalidating, or calling. Chipset.

Images