Reader-based attachment process for passive terminal devices

Abstract

Various techniques are provided for a method that may include receiving, by a terminal device, configuration information from a network device, the configuration information for the terminal device to transmit a signal to, or to receive a signal from, at least one passive terminal device, wherein the configuration information configures the terminal device to perform at least one of: according to the configuration information, transmitting a signal to the at least one passive terminal device, and receiving at least one signal from the at least one passive terminal device, each signal responsive to reception of the transmitted signal received at the at least one passive terminal device; and determining an association between the at least one passive terminal device and the terminal device based on received signal strength information of the at least one signal received at the terminal device.

Description

Technical Field

[0001] This specification relates to wireless communications. Background Art

[0002] A communication system may be a facility that enables communication between two or more nodes or devices (such as fixed or mobile communication devices). Signals may be carried on wired or wireless carriers.

[0003] An example of a cellular communication system is the architecture standardized by the Third Generation Partnership Project (3GPP). The latest development in this area is generally referred to as the Long Term Evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio access technology. E-UTRA (Evolved UMTS Terrestrial Radio Access) is the air interface of the 3GPP Long Term Evolution (LTE) upgrade path for mobile networks. In LTE, base stations or access points (APs), called enhanced nodes AP (eNBs), provide wireless access within a coverage area or cell. In LTE, mobile devices or mobile stations are called user equipment (UEs). LTE includes many improvements or developments. Various aspects of LTE are constantly being improved.

[0004] 5G New Radio (NR) development is part of the ongoing mobile broadband evolution process to meet the requirements of 5G, similar to the earlier evolution of 3G and 4G wireless networks. In addition to mobile broadband, 5G also targets emerging use cases. The goal of 5G is to significantly improve wireless performance, which can include new levels of data rate, latency, reliability and security. 5G NR can also be extended to efficiently connect large-scale Internet of Things (IoT) and can provide new types of mission-critical services. For example, ultra-reliable low latency communication (URLLC) equipment may require high reliability and very low latency. Summary of the Invention

[0005] According to an example embodiment, a method may include: receiving, by a terminal device, configuration information from a network device, the configuration information being used for the terminal device to send a signal to, or receive a signal from, at least one passive terminal device, wherein the configuration information configures the terminal device to perform at least one of the following: sending a signal to, and receiving at least one signal from, the at least one passive terminal device in accordance with the configuration information, each signal being in response to reception of a transmitted signal received at the at least one passive terminal device; and determining an association between the at least one passive terminal device and the terminal device based on received signal strength information of the at least one signal received at the terminal device.

[0006] According to an example embodiment, a method may include: sending configuration information from a network device to at least one terminal device, the configuration information being used to configure the at least one terminal device to send or receive a signal to at least one passive terminal device; and receiving, by the network device from the at least one terminal device, corresponding association information between the at least one passive terminal device and the at least one terminal device, wherein the corresponding association information is based on corresponding received signal strength information of at least one received signal received at the at least one terminal device, and each of the at least one received signal is reflected or backscattered by the at least one corresponding passive terminal device in response to receiving a signal sent from the at least one terminal device.

[0007] The details of one or more examples of embodiments are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 is a block diagram of a wireless network according to an example embodiment.

[0009] Figure 2A is a diagram illustrating a network according to an example embodiment.

[0010] Figure 2B is a diagram illustrating another network according to example embodiments.

[0011] Figure 2C is a diagram illustrating yet another network according to an example embodiment.

[0012] Figure 2D is a diagram illustrating yet another network according to an example embodiment.

[0013] Figure 3 A signal flow diagram according to an example embodiment is illustrated.

[0014] Figure 4 Another signal flow diagram according to an example embodiment is illustrated.

[0015] Figure 5 A further signal flow diagram according to an example embodiment is illustrated.

[0016] Figure 6 is a block diagram illustrating a synchronous excitation method for a reader edge passive terminal device according to an example embodiment.

[0017] Figure 7 is a block diagram of a method of operating a terminal device according to an example embodiment.

[0018] Figure 8 is a block diagram of a method of operating a network device according to an example embodiment.

[0019] Figure 9 is a block diagram of a wireless station or wireless node (e.g., AP, BS, gNB, RAN node, relay node, UE or user equipment, network node, network entity, DU, CU-CP, CU-CP, etc. or other node) according to an example embodiment. DETAILED DESCRIPTION

[0020] Figure 1 is a block diagram of a wireless network 130 according to an example embodiment. Figure 1 In a wireless network 130, user equipment 131, 132, 133, and 135 (which may also be referred to as mobile stations (MSs) or user equipment (UEs)) may be connected to (and communicate with) a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB), a BS, a next-generation Node B (gNB), a next-generation enhanced Node B (ng-eNB), or a network node. The terms user equipment and user equipment (UE) may be used interchangeably. The BS may also include or may be referred to as a RAN (Radio Access Network) node, and may include a portion of a BS or a portion of a RAN node, such as (for example, a centralized unit (CU) and / or a distributed unit (DU) in the case of a split BS). At least a portion of the functionality of a BS (e.g., an access point (AP), a base station (BS), or an (e)Node B (eNB), a BS, a RAN node) may also be performed by any node, server, or host that may be operably coupled to a transceiver (such as a remote radio head). BS (or AP) 134 provides wireless coverage within cell 136, including to user equipment (or UE) 131, 132, 133, and 135. Although only four user equipment (or UE) are shown as connected or attached to BS 134, any number of user equipment may be provided. BS 134 is also connected to core network 150 via an S1 interface or NG interface 151. This is just one simple example of a wireless network, and other wireless networks may be used.

[0021] A base station (e.g., such as BS 134) is an example of a radio access network (RAN) node within a wireless network. A BS (or RAN node) may be, or may include (or may alternatively be referred to as), for example, an access point (AP), a gNB, an eNB, or portions thereof (such as a centralized unit (CU) and / or distributed unit (DU) in the case of a split BS or split gNB), or other network nodes. For example, a BS (or gNB) may include: a distributed unit (DU) network entity, such as a gNB distributed unit (gNB-DU); and a centralized unit (CU) that can control multiple DUs. For example, in some cases, the centralized unit (CU) may be split or divided into: a control plane entity, such as a gNB centralized (or central) unit control plane (gNB-CU-CP); and a user plane entity, such as a gNB centralized (or central) unit user plane (gNB-CU-UP). For example, the CU sub-entities (gNB-CU-CP, gNB-CU-UP) may be provided as different logical entities or different software entities (e.g., as separate or different software entities that communicate with each other), which may run or be provided on the same hardware or server, in the cloud, etc., or may be provided on different hardware, systems, or servers, e.g., physically separated or running in different systems, hardware, or servers.

[0022] As previously mentioned, in a split gNB / BS configuration, gNB functionality can be split between the DU and CU. A distributed unit (DU) can provide or establish wireless communications with one or more UEs. Thus, a DU can provide one or more cells and can allow UEs to communicate with and / or establish connections with the DU to receive wireless services, such as allowing the UE to send or receive data. A centralized (or central) unit (CU) can provide control and / or data plane functions for one or more connected DUs, including, for example, control functions such as gNB control of user data transmission, mobility control, radio access network sharing, positioning, session management, etc., except for functions specifically assigned to the DU. The CU can control the operation of the DU (e.g., the CU communicates with one or more DUs) via the fronthaul (Fs) interface.

[0023] According to an illustrative example, in general, a BS node (e.g., BS, eNB, gNB, CU / DU, etc.) or a radio access network (RAN) may be part of a mobile telecommunications system. The RAN (radio access network) may include one or more BSs or RAN nodes that implement a radio access technology, for example, to allow one or more UEs to access a network or core network. Thus, for example, a RAN (RAN node, such as a BS or gNB) may reside between one or more user equipment (UEs) and a core network. According to an example embodiment, each RAN node (e.g., BS, eNB, gNB, CU / DU, etc.) or BS may provide one or more wireless communication services to one or more UEs or user equipment, for example, to allow the UE to wirelessly access the network via the RAN node. Each RAN node or BS may perform or provide wireless communication services, for example, such as allowing a UE or user equipment to establish a wireless connection to a RAN node and to send data to and / or receive data from one or more UEs. For example, after establishing a connection to a UE, a RAN node (e.g., a base station (BS), eNB, gNB, CU / DU, etc.) may forward data received from the network or core network to the UE, and / or forward data received from the UE to the network or core network. A RAN node (e.g., a BS, eNB, gNB, CU / DU, etc.) may perform various other wireless functions or services, such as broadcasting control information (e.g., such as system information) to the UE, paging the UE when data is available for delivery, assisting the UE in handovers between cells, scheduling resources for uplink data transmission from (multiple) UEs and downlink data transmission to (multiple) UEs, and issuing control information for configuring one or more UEs. These are just a few examples of one or more functions that a RAN node or BS may perform. A base station may also be the DU (distributed unit) portion of an IAB (integrated access and backhaul) node (also known as a relay node). The DU facilitates access link connectivity for the IAB node.

[0024] A user device (user terminal, user equipment (UE), mobile terminal, handheld wireless device, etc.) may refer to a portable computing device including a wireless mobile communication device operating with or without a subscriber identity module (SIM) (which may be referred to as a universal SIM), including, for example, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and / or touch screen computer, a tablet, a tablet phone, a game console, a notebook computer, a vehicle, a sensor, a multimedia device, or any other wireless device. It should be understood that a user device may also be (or may include) an almost exclusively uplink-only device, an example of which is a camera or camcorder that uploads images or video clips to a network. A user device may also be the MT (mobile terminal) portion of an IAB (integrated access and backhaul) node (also known as a relay node). The MT facilitates the backhaul connection of the IAB node.

[0025] In LTE (as an illustrative example), the core network 150 may be referred to as an evolved packet core (EPC), which may include a mobility management entity (MME), one or more gateways, and other control functions or blocks. The MME may handle or assist in the movement / handover of user equipment between base stations (BSs), and the one or more gateways may forward data and control signals between the BSs and a packet data network or the Internet. Other types of wireless networks, such as 5G (which may be referred to as new radio (NR)), 5G advanced, 6G, etc., may also include a core network (e.g., in 5G / NR, it may be referred to as 5GC).

[0026] Furthermore, as illustrative examples, the various example embodiments or techniques described herein may be applied to various types of user devices or data service types, or may be applied to user devices on which multiple applications may be running, each of which may be of different data service types. New radio (5G) and 6G developments may support many different applications or many different data service types, such as, for example: machine type communication (MTC), enhanced machine type communication (eMTC), massive MTC (mMTC), Internet of Things (IoT) and / or narrowband IoT user devices, enhanced mobile broadband (eMBB), and ultra-reliable low latency communication (URLLC). Many of these new 5G (NR) and 6G-related applications may require higher performance than previous wireless networks.

[0027] The IoT can refer to the growing group of objects that can have internet or network connectivity, allowing them to send and receive information to other network devices. For example, many sensor-type applications or devices can monitor physical conditions or states and can report to servers or other network devices, such as when events occur. For example, machine-type communications (MTC or machine-to-machine communications) can be characterized as fully automated data generation, exchange, processing, and actuation between intelligent machines, with or without human intervention. Enhanced mobile broadband (eMBB) can support higher data rates than currently available in LTE.

[0028] Ultra-Reliable Low Latency Communication (URLLC) is a new data service type or new use case that New Radio (5G) and 6G systems can support. This enables emerging new applications and services such as industrial automation, autonomous driving, vehicle safety, e-health services, etc. As an illustrative example, 3GPP aims to provide a 10-GHz LTE-M-based system with the same -5 Connectivity with reliability corresponding to a block error rate (BLER) of up to 1 ms and a U-plane (user / data plane) latency of up to 1 ms. Therefore, for example, a URLLC user equipment / UE may require a significantly lower block error rate and low latency than other types of user equipment / UE (with or without simultaneous high reliability requirements). Therefore, for example, a URLLC UE (or a URLLC application on a UE) may require shorter latency than an eMBB UE (or an eMBB application running on a UE).

[0029] Various example embodiments may be applied to various wireless technologies or wireless networks, such as LTE, LTE-A, 5G (New Radio (NR)), 6G, cmWave and / or mmWave frequency band networks, IoT, MTC, eMTC, mMTC, eMBB, URLLC, etc., or any other wireless network or wireless technology. These example networks, technologies, or data service types are provided as illustrative examples only.

[0030] Energy harvesting-enabled communication services can be used in a variety of vertical industries, including logistics, manufacturing, transportation, and the energy industry. Passive end devices (sometimes referred to as passive IoT devices and / or tags) can include end devices without batteries and / or end devices with limited energy storage capabilities (e.g., using capacitors). Enabling passive end devices in both public and private networks can benefit the 5G ecosystem.

[0031] Some areas of consideration associated with passive terminal devices may include operation under extreme environmental conditions (e.g., high voltage, extreme high / low temperatures, humid environments, vibrations, etc.), ultra-low complexity (cost), very small terminal size / form factor (e.g., mm thickness), maintenance-free, and longer life cycle, which are all very necessary.

[0032] Compared to existing 3GPP terminal (e.g., IoT) technologies, the passive terminal device segment can provide significantly lower power consumption and lower complexity. Battery-free passive terminal devices can have advantages in reducing power consumption, equipment cost, and maintenance cost.

[0033] However, passive terminal devices will have different use cases, and KPIs such as data rate and coverage will vary in different use cases. In some use cases, greater coverage or higher data rates may be required, which means higher device power consumption. For example, a reflection amplifier may be required in a passive terminal device to achieve better coverage. This may result in higher power consumption (for example, hundreds of microwatts). Although the energy collected from the environment may not be enough for a certain collection method, from the perspective of reducing maintenance costs, it would be very useful if a button battery could be used to support such a passive terminal device for several years. Therefore, implementations can include both battery-free devices and devices with energy storage capabilities.

[0034] Energy harvesting-enabled communication services can be configured to use backscatter technology. Radio frequency identification (RFID) solutions can be used in conjunction with backscatter technology. Passive end devices can use 3GPP technologies to enhance the coverage of backscatter RFID solutions and introduce new solutions with advanced features, such as harvesting energy from dedicated sources or ambient energy and efficiently using that energy for passive end device data transmission.

[0035] One problem with existing energy harvesting enabled communication services may be that the BS (e.g., BS 134) may not always be used as an illuminator for backscatter due to the limited link budget of the BS. Furthermore, the BS may not be used during the initial attach process because the BS may not be the most efficient source for providing power to the passive terminal device(s). Furthermore, using the BS during the initial attach process may cause interference to the UEs served by the BS. For example, if the backscattered signal associated with a passive terminal device at the cell edge is to be received and correctly decoded by the BS, the power sent by the BS to illuminate the passive terminal device must be very high. Therefore, the power sent by the BS to illuminate the passive terminal device may interfere with all other communications (e.g., UEs) operating on the same frequency.

[0036] Depending on the density of (multiple) passive terminal devices, existing solutions can deploy multiple excitation sources and receivers (or readers). These excitation sources and receivers can be 5G terminals that have all the characteristics of 5G UE and can communicate with the BS. The excitation sources and receivers deployed nearby can minimize the power required for excitation (illumination). For example, the excitation source will only cover nearby (multiple) passive terminal devices (for example, due to the limited maximum transmission power of the UE, the range is small). The 5G terminal can transmit at a power with less interference impact on the UE and (multiple) passive terminal devices within a smaller range.

[0037] The excitation sources and / or receivers may be fixed and powered by an AC / DC power supply, or may be powered by a mobile battery based on the use case and / or system requirements. In some cases, when the passive terminal device(s) are no longer present around some excitation sources and / or are no longer acting as receivers, the passive terminal device(s) may be deactivated by the system, or opportunistically excited and / or received by the mobile 5G terminal. When backscatter passive terminal devices are allowed, multiple excitation sources and / or receivers may be used based on the density of the passive terminal devices(s). In order to achieve the goals associated with energy harvesting enabled communication services using 3GPP technologies, several issues should be addressed. For example, these issues may include how to ensure reduced signaling overhead, efficient resource usage, and minimized interference levels at the network for each association that may be short in duration and / or repeated in time.

[0038] Example implementations may address these and other issues caused by passive terminal device association through 5G NR mechanisms. Example implementations may describe new signaling between the base station (BS), excitation source, receiver, and (multiple) passive terminal devices. Example implementations may avoid direct signaling between the UE and the BS by using distributed readers to complete the attachment process.

[0039] Figure 2A is a diagram illustrating a network according to an example embodiment. Figure 2AAs shown, a network (e.g., a cellular network) includes a BS 134 and a passive end device 205 (e.g., a passive IoT device, a tag, etc.). BS 134 can be configured to transmit a carrier wave (CW) 210, and the passive end device 205 can be configured to reflect CW 210 as a backscattered signal 215. To deploy the passive end device 205 in the cellular network, BS 134 can function as a reader similar to, for example, an RFID reader. BS 134 can be configured to provide CW 210 to the passive end device 205 via CW 210 as an RF energy source and control signaling. The passive end device 205 can be configured to transmit information to BS 134 via the reflected or backscattered signal 215. In this example implementation, the passive end device 205 can be supported without UE assistance. In this example implementation, BS 134 can be configured to support full-duplex operation (e.g., simultaneously transmitting CW 210 and receiving reflected or backscattered signal 215).

[0040] Figure 2B is a diagram illustrating another network according to an example embodiment. Figure 2B As shown, a network (e.g., a cellular network) includes a BS 134, a passive end device 205 (e.g., a passive IoT device, a tag, etc.), and a UE 131. The UE 131 can be configured to transmit a CW 210, and the passive end device 205 can be configured to reflect the CW 210 as a reflected or backscattered signal 215. The BS 134 can serve the UE 131 via a cellular signal 225. In addition, the passive end device 205 can be configured to transmit data to the BS 134 via the UE 131 using data stream signals 220-1, 220-2.

[0041] In some cases, passive terminal device coverage may not always be available via the BS (e.g., smart home devices). Therefore, in an example implementation, UE 131 can act as a reader. In other words, UE 131 can be configured to provide CW 210 and receive reflected or backscattered signals 215 from passive terminal device 205. In this implementation, passive terminal device 205 may not be directly connected to the network. Therefore, UE 131 can be configured to relay data via data stream signals 220-1, 220-2. Data can be obtained from passive terminal device 205. In addition, passive terminal device 205 can register with the network via UE 131. In other words, UE 131 can be a relay node between BS 134 (and the network) and passive terminal device 205. In this example implementation, UE 131 can be configured to support full-duplex operation (e.g., transmitting CW 210 and receiving reflected or backscattered signals 215 substantially simultaneously).

[0042] Figure 2Cis a diagram illustrating yet another network according to an example embodiment. Figure 2C As shown, a network (e.g., a cellular network) includes a BS 134, a passive terminal device 205 (e.g., a passive IoT device, a tag, etc.), and a UE 131. The BS 134 can be configured to transmit a CW 210, and the passive terminal device 205 can be configured to reflect the CW 210 as a reflected or backscattered signal 215. The UE 131 can be configured to receive the reflected or backscattered signal 215. The BS 134 can serve the UE 131 via a cellular signal 225. In addition, the passive terminal device 205 can be configured to transmit data to the BS 134 via the UE 131 using data stream signals 220-1 and 220-2. In addition, the BS 134 can generate an interference signal 230 that interferes with the UE 131.

[0043] Figure 2D is a diagram illustrating yet another network according to an example embodiment. Figure 2D As shown, a network (e.g., a cellular network) includes a BS 134, a passive terminal device 205 (e.g., a passive IoT device, a tag, etc.), and a UE 131. The UE 131 can be configured to transmit a CW 210, and the passive terminal device 205 can be configured to reflect the CW 210 as a reflected or backscattered signal 215. The BS 134 can be configured to receive the reflected or backscattered signal 215. The BS 134 can serve the UE 131 via a cellular signal 225. In addition, the passive terminal device 205 can be configured to transmit data to the BS 134 using a data stream signal 220. In addition, the BS 134 can generate an interference signal 230 that interferes with the UE 131.

[0044] Figure 2C and Figure 2D The UE-assisted passive terminal device usage scenario can be illustrated. As shown in the figure, in this example implementation, the UE 131 can be configured to assist the communication between the passive IoT device and the BS. Figure 2C In , UE 131 may be configured to acquire data from passive terminal device 205, and the data may be relayed to BS 134 (eg, network). Figure 2D In the embodiment of the present invention, BS 134 may be configured to acquire data from passive terminal device 205, and UE 131 may be configured as a nearby RF energy source.

[0045] exist Figure 2C and Figure 2DIn the example implementation shown, UE 131 and / or BS 134 may be configured as a transmitter for CW and / or commands, and / or BS 134 may be configured as a receiver of reflected or backscattered signals from passive terminal device 205. However, in the example implementation, UE 131 and / or BS 134 may not be both a transmitter and a receiver at the same time. Therefore, BS 134 and / or UE 131 may not require full-duplex operation. Therefore, Figure 2C and Figure 2D The example implementation shown may be of reduced complexity.

[0046] In addition to reducing implementation complexity, UE-assisted passive terminal device communication can also provide coverage advantages. The distance from the UE to the passive terminal device can be shorter than the distance from the passive terminal device to the base station. Therefore, the round-trip path loss (e.g., from the carrier transmitter to the reflected signal receiver) can be reduced. Some data / signaling exchange between the base station and the UE can be achieved, and the link between the UE and the base station can be more robust compared to the passive terminal device to base station link. Therefore, with the help of the UE, better coverage can be expected.

[0047] An example implementation may include data transmission between a passive terminal device and a passive terminal application. The passive terminal application may be configured to record the reader (e.g., UE or RAN) that can transmit data for the passive terminal device. When the reader is changed (e.g., when the passive terminal device is moving), the passive terminal application can be updated with the new reader. In this implementation, in order to minimize processing complexity, the passive terminal device may not be connected to the 5G core network during the update operation.

[0048] An example implementation may include the UE or RAN helping the passive terminal device access the 5G core network (e.g., registering with the AMF). The passive terminal device may not need to support the NAS protocol stack, which can help support ultra-low cost and ultra-low power passive terminal devices. In addition, the AMF can be configured to manage the corresponding reader of the passive terminal device and may not need to support a NAS connection separate from each passive terminal device. In this implementation, the 5G core network can support passive terminal services. For example, the 5G core network can help authenticate the passive terminal device, perform mobility management on the passive terminal device (e.g., provide location information of the passive IoT device), manage readers within the operator network, and select readers to help establish communication with the passive terminal device to avoid interference between readers.

[0049] An example implementation describes reader-based association of passive terminal devices. Reader-based association can use BS assistance as needed. The association decision can be made by the reader. In an example implementation, the decision can be made based on perceived link quality by comparing the RSRP of the backscattered received signal with an RSRP threshold pre-configured by the BS. If the RSRP of the backscattered received signal is greater than a threshold (e.g., RSRP_threshold), the passive terminal device can be associated with the reader. Otherwise, the passive terminal device may not be associated with the reader (e.g., associated with a more suitable reader later). If the BS does not configure the RSRP threshold, the reader can be configured to rely on its device sensitivity. If each reader performs autonomous association with a passive terminal device, it is possible for a passive terminal device to be associated with several readers.

[0050] In an example implementation, the reader may be configured to report association decisions to the BS in order to refine the reader association decision. For example, the reporting may be triggered periodically after a preconfigured timer for reporting. For example, the reporting may be triggered in response to a BS request (e.g., the BS may schedule a common signal to request the reader to report its association decision). For example, the reporting may be triggered based on a list of passive end devices being associated. For example, the reporting may be triggered in response to an event at the reader (e.g., the load exceeds a certain level, requiring BS involvement to efficiently distribute the load between readers).

[0051] Objectives associated with the BS refinement process may include coordinating between excitation sources / readers in the case of synchronization signal broadcasts and thereby strengthening the received signal at specific passive end devices at the edge, ensuring efficient load balancing between readers based on the passive end device ID decoded from the backscattered signal of the allocated query opportunity to avoid high levels of interference and collisions of reader passive end device queries, determining the validity of attachments, etc.

[0052] In an example implementation, the BS may be configured to provide an association update message to all readers, which may also contain an updated configuration. The readers may be configured to apply the new association decision refined by the BS, and the new configuration (if received).

[0053] According to an example implementation, a passive end device (e.g., a passive IoT device, a tag, etc.) may be configured to communicate with a reader via backscatter. In some cases, the processing capabilities of the passive end device may be limited. For example, the passive end device may include a microprocessor and may have the ability to synchronize based on a given signal. The passive end device may not have a full 3GPP protocol stack. In other words, the passive end device may support a limited portion of the L1 stack. The passive end device may not have the ability to perform RSRP measurements.

[0054] According to an example implementation, the reader can be a 5G UE enhanced with the ability to excite passive terminal devices and decode backscattered signals received from passive terminal devices. The reader and exciter can be two different 3GPP devices to coordinate the excitation signal and backscattered signal reception. The reader and / or exciter can be turned on / off based on a duty cycle (e.g., configured by the BS as active transmission and reception opportunities and sleep periods). The exciter can be excited according to the maximum Tx power configured by the BS. The BS can be configured as the default reader and / or excitation source. The reader can be configured to derive an approximate location of the passive terminal device.

[0055] The BS can be configured to configure a dedicated 3GPP stimulus source or sources and / or readers to broadcast energy. This configuration can include one or more of the following parameters: the maximum transmit power to be used for stimulus, which can be a common parameter for all stimulus sources or specific to each stimulus source, with the general purpose of reducing overall interference in the system; the RSRP threshold (if configured) to be taken into account for passive end device association; the duty cycle at which the reader / stimulator is activated to receive backscattered signals and / or transmit stimulus signals and deactivated (i.e., enters a sleep mode with no Tx / Rx) for efficient energy consumption; and, for scenarios where multiple stimulus sources are broadcasting energy simultaneously, a time offset as to when transmissions should be initiated. One use case for passive end devices is to obtain their location. If the location is known, synchronized stimulus can be further fine-tuned by providing offsets for different stimulus sources.

[0056] Figure 3 FIGURE 1 illustrates a signal flow diagram according to an example embodiment. Figure 3 As shown, the network may include a passive terminal device (PTD) 305, a PTD 310, a reader / activator 315, a reader / activator 320, and a BS 134. In an example implementation, BS 134 may communicate with reader / activator 315 and reader / activator 320 using a cellular standard. BS 134 may be a combination of devices. For example, BS 134 may represent a BS and a core network device (or entity), BS 134 may represent a BS and a control device (or entity), BS 134 may represent a base station on a satellite, a satellite acting as a relay and a ground base station, and any other similar combination of network devices. Individual devices and / or combinations of devices may sometimes be referred to as devices, systems, etc. Reader / activator 315 and reader / activator 320 may be user equipment, terminal devices, user terminals, mobile devices, fixed devices, Internet of Things (IoT) devices, any wireless (or cellular) connected device, etc.

[0057] BS 134 may transmit (e.g., wirelessly) a message received by reader / activator 320 (block 322A). BS 134 may transmit (e.g., wirelessly) a message received by reader / activator 315 (block 322B). In this implementation, the message is generated by BS 134 and transmitted to reader / activator 315 and reader / activator 320. In an example implementation, one message is transmitted (e.g., broadcast) by BS 134 and received by both reader / activator 315 and reader / activator 320. The message may include a reader-based passive terminal device configuration. A reader-based passive terminal device configuration may be associated with a single-station deployment. For example, the reader-based passive end device configuration may include at least one of the following: a maximum transmit power to be used for stimulation, which is common to all stimulation sources or specific to each stimulation source, with the general purpose of reducing overall interference in the system; an RSRP threshold (if configured) to be considered for passive end device association; a duty cycle at which the reader / stimulator is activated to receive backscattered signals and / or transmit stimulation signals and deactivated (i.e., enters a sleep mode with no Tx / Rx) for efficient energy consumption; a time offset as to when transmission should be initiated for scenarios where multiple stimulation sources are broadcasting energy simultaneously, etc. In response to receiving the message, the reader / stimulator 315 and the reader / stimulator 320 may be configured to perform reader-based passive end device association according to the reader-based passive end device configuration.

[0058] Reader / activator 320 may generate and transmit (block 324A) an excitation signal that is received by PTD 310. Reader / activator 320 may generate and transmit (block 324B) an excitation signal that is received by PTD 305. In an example implementation, one excitation signal is transmitted (e.g., broadcast) by reader / activator 320 and received by both PTD 305 and PTD 310. In response to receiving the excitation signal, PTD 305 may generate and transmit (block 326A) a backscatter signal. The backscatter signal may be received by reader / activator 315. The backscatter signal may include an identification (ID) (sometimes referred to as a tag ID) associated with PTD 305. In response to receiving the excitation signal, PTD 305 may generate and transmit (block 326B) a backscatter signal. The backscatter signal may be received by reader / activator 320. In an example implementation, one backscatter signal is generated and transmitted or reflected by PTD 305 and received by both reader / activator 315 and reader / activator 320 .

[0059] In response to receiving the excitation signal, the PTD 310 may generate and transmit or reflect (block 328A) a backscatter signal. The backscatter signal may be received by the reader / activator 315. The backscatter signal may include an identification (ID) associated with the PTD 310 (sometimes referred to as a tag ID). In response to receiving the excitation signal, the PTD 310 may generate and transmit (block 328B) a backscatter signal. The backscatter signal may be received by the reader / activator 320. The backscatter signal may include an identification (ID) associated with the PTD 310 (sometimes referred to as a tag ID). In an exemplary implementation, one backscatter signal is generated and transmitted or reflected by the PTD 310 and received by both the reader / activator 315 and the reader / activator 320.

[0060] In response to receiving backscatter signals from PTD 305 and / or PTD 310, reader / activator 315 may perform passive end device association (block 330). For example, PTD 305 may associate with reader / activator 315. In response to receiving backscatter signals from PTD 305 and / or PTD 310, reader / activator 320 may perform passive end device association (block 332). For example, PTD 310 may associate with reader / activator 320. Each reader / activator may be configured to make a decision to associate with a PTD based on the received RSRP. In an example implementation, the RSRP threshold (if configured) may be lowered to ensure passive end device association with at least one reader. In another example, the RSRP threshold (if configured) may be increased to reduce simultaneous associations. In another example, if the RSRP threshold is not configured, the association decision may be made based on the device sensitivity of the detection signal reception.

[0061] After performing passive end device association (block 330), reader / activator 315 may transmit (e.g., wirelessly transmit) a message that is received by reader / activator 320 (block 334A). Reader / activator 315 may transmit (e.g., wirelessly transmit) a message that is received by BS 134 (block 334B). Figure 3In an example implementation, reader / activator 315 reports to reader / activator 320 and BS134. However, although not shown, reader / activator 320 may report to reader / activator 315 and BS134. In addition, reader / activator 315 may report to reader / activator 320, and then reader / activator 320 may report to BS134, or reader / activator 320 may report to reader / activator 315, and then reader / activator 315 may report to BS134. The message may include passive terminal device association information. For example, the passive terminal device association information may include an identification (ID) (sometimes referred to as a tag ID) associated with PTD 305 and / or PTD 310. In an example implementation, the passive terminal device association information may be transmitted periodically and / or in response to a trigger. For example, reader / activator 320 may be configured to report an association decision to the BS in order to refine the reader / activator association decision. For example, the report may be triggered periodically after a preconfigured timer for reporting. For example, the report may be triggered in response to a BS request (e.g., the BS may schedule a common signal to request the reader to report its association decision). For example, the report may be triggered based on a list of passive end devices that are associating. For example, the report may be triggered in response to an event at the reader (e.g., the load exceeds a certain level, requiring BS involvement to efficiently distribute the load among readers).

[0062] In response to receiving the passive terminal device association information, BS 134 may perform an attach refinement operation (block 336). After performing the attach refinement operation (block 336), BS 134 may transmit (e.g., wirelessly transmit) a message that is received by reader / activator 320 (block 338A). BS 134 may transmit (e.g., wirelessly transmit) a message that is received by reader / activator 315 (block 338B). In this implementation, the message is generated by BS 134 and transmitted to reader / activator 315 and reader / activator 320. In an example implementation, a single message is transmitted (e.g., broadcast) by BS 134 and received by both reader / activator 315 and reader / activator 320. The message may include the updated association and reader / activator configuration information generated in block 336. In an example implementation, the association update information may include an identification (ID) (sometimes referred to as a tag ID) associated with the PTD 305 and / or PTD 310 to be associated. In an example implementation, the new configuration may include an updated duty cycle configuration to ensure better coordination between available readers / activators. Reader / activator 315 and reader / activator 320 may employ the duty cycle to ensure there are no conflicts when performing queries on the PTD.

[0063] Figure 4Another signal flow diagram according to an example embodiment is shown. Figure 4 As shown, the network may include passive terminal devices (PTDs) 405, PTDs 410, activators 415, activators 420, readers 425, readers 430, and BS 134. In an example implementation, BS 134 may communicate with activators 415, activators 420, readers 425, and readers 430 using cellular standards. BS 134 may be a combination of devices. For example, BS 134 may represent a BS and a core network device (or entity), BS 134 may represent a BS and a control device (or entity), BS 134 may represent a base station on a satellite, a satellite acting as a relay and a ground base station, and any other similar combination of network devices. Individual devices and / or combinations of devices may sometimes be referred to as devices, systems, and the like. Activators 415, activators 420, readers 425, and / or readers 430 may be user equipment, terminal devices, user terminals, mobile devices, fixed devices, Internet of Things (IoT) devices, any wireless (or cellular) connected device, and the like.

[0064] BS 134 may transmit (e.g., wirelessly transmit) a message received by reader 430 (block 432A). BS 134 may transmit (e.g., wirelessly transmit) a message received by reader 425 (block 432B). BS 134 may transmit (e.g., wirelessly transmit) a message received by activator 420 (block 432C). BS 134 may transmit (e.g., wirelessly transmit) a message received by activator 415 (block 432C). In this implementation, the message is generated by BS 134 and transmitted to activator 415, activator 420, reader 425, and / or reader 430. In an example implementation, a message is transmitted (e.g., broadcast) by BS 134 and received by activator 415, activator 420, reader 425, and / or reader 430. The message may include a reader-based passive end device configuration. The reader-based passive end device configuration may be associated with a reader-based bistatic deployment. For example, the reader-based passive end device configuration may include at least one of the following: a maximum transmit power to be used for excitation, which may be common to all excitation sources or specific to each excitation source, with the general purpose of reducing overall interference in the system; an RSRP threshold (if configured) to be considered for passive end device association; a duty cycle at which the reader / excitation source is activated to receive backscattered signals and / or transmit excitation signals and deactivated (i.e., enters a sleep mode with no Tx / Rx) for efficient energy consumption; a time offset as to when transmissions should be initiated for scenarios where multiple excitation sources are broadcasting energy simultaneously, etc. In response to receiving the message, the excitation source 415, the excitation source 420, the reader 425, and / or the reader 430 may be configured to perform reader-based passive end device association according to the reader-based passive end device configuration.

[0065] The exciter 420 may generate and transmit (block 434A) an excitation signal that is received by the PTD 410. The exciter 420 may generate and transmit (block 434B) an excitation signal that is received by the PTD 405. In an example implementation, one excitation signal is transmitted (e.g., broadcast) by the exciter 420 and received by both the PTD 405 and the PTD 410. The exciter 415 may generate and transmit (block 436A) an excitation signal that is received by the PTD 410. The exciter 415 may generate and transmit (block 434B) an excitation signal that is received by the PTD 405. In an example implementation, one excitation signal is transmitted (e.g., broadcast) by the exciter 415 and received by both the PTD 405 and the PTD 410.

[0066] In response to receiving the excitation signal, PTD 405 may generate and transmit (block 438A) a backscatter signal. The backscatter signal may be received by reader 425. The backscatter signal may include an identification (ID) associated with PTD 405 (sometimes referred to as a tag ID). In response to receiving the excitation signal, PTD 405 may generate and transmit (block 438B) a backscatter signal. The backscatter signal may be received by reader 430. The backscatter signal may include an identification (ID) associated with PTD 405 (sometimes referred to as a tag ID). In an example implementation, one backscatter signal is generated and transmitted or reflected by PTD 405 and received by both reader 425 and reader 430.

[0067] In response to receiving the excitation signal, PTD 410 may generate and transmit (block 440A) a backscatter signal. The backscatter signal may be received by reader 425. The backscatter signal may include an identification (ID) associated with PTD 410 (sometimes referred to as a tag ID). In response to receiving the excitation signal, PTD 410 may generate and transmit or reflect (block 440B) a backscatter signal. The backscatter signal may be received by reader 430. The backscatter signal may include an identification (ID) associated with PTD 410 (sometimes referred to as a tag ID). In an example implementation, one backscatter signal is generated and transmitted by PTD 410 and received by both reader 425 and reader 430.

[0068] In response to receiving backscatter signals from PTD 405 and / or PTD 410, reader 425 may perform passive end device association (block 442). For example, PTD 405 may associate with reader 425. In response to receiving backscatter signals from PTD 405 and / or PTD 410, reader 430 may perform passive end device association (block 444). For example, PTD 410 may associate with reader 430. Reader 425 and reader 430 may each be configured to make a decision to associate with a PTD based on received RSRP. In an example implementation, the RSRP threshold (if configured) may be low to ensure passive end device association with at least one reader. In another example, the RSRP threshold (if configured) may be high to reduce simultaneous associations. In another example, if the RSRP threshold is not configured, the association decision may be made based on device sensitivity.

[0069] After performing passive end device association (block 442), reader 425 may transmit (e.g., wirelessly transmit) a message received by BS 134 (block 446). Reader 430 may transmit (e.g., wirelessly transmit) a message received by BS 134 (block 448). Figure 4In an example implementation, reader 425 and reader 430 report to BS 134. However, although not shown, reader 425 may report to reader 430, and reader 430 may report to BS 134. Alternatively (or additionally), reader 430 may report to reader 425, and reader 425 may report to BS 134. The message may include passive terminal device association information. For example, the passive terminal device association information may include an identifier (ID) (sometimes referred to as a tag ID) associated with PTD 405 and / or PTD 410. In an example implementation, the passive terminal device association information may be transmitted periodically and / or in response to a trigger. For example, reader 425 and / or reader 430 may be configured to report the association decision to BS 134 in order to refine the reader association decision. For example, the report may be triggered periodically after a preconfigured timer for reporting. For example, the reporting may be triggered in response to a request from BS 134 (e.g., BS 134 may dispatch a common signal to request the reader to report its association decision). For example, the reporting may be triggered based on a list of passive end devices that are associating. For example, the reporting may be triggered in response to an event at the reader (e.g., the load exceeds a certain level, requiring BS 134 involvement to efficiently distribute the load among the readers).

[0070] In response to receiving the passive end device association information, BS 134 may perform an attach refinement operation (block 450). After performing the attach refinement operation (block 450), BS 134 may transmit (e.g., wirelessly transmit) a message received by reader 430 (block 452A). BS 134 may transmit (e.g., wirelessly transmit) a message received by reader 425 (block 452B). BS 134 may transmit (e.g., wirelessly transmit) a message received by energizer 420 (block 452C). BS 134 may transmit (e.g., wirelessly transmit) a message received by energizer 415 (block 452D).

[0071] In this implementation, the message is generated by BS 134 and transmitted to activator 415, activator 420, reader 425, and / or reader 430. In an example implementation, a message is transmitted (e.g., broadcast) by BS 134 and received by activator 415, activator 420, reader 425, and / or reader 430. The message may include the updated association and reader / activator configuration information generated in block 450. In an example implementation, the association update information may include an identification (ID) (sometimes referred to as a tag ID) associated with the PTD 405 and / or PTD 410 to be associated. In an example implementation, the new configuration may include an updated duty cycle configuration to ensure better coordination between available readers / activators. Reader 425 and reader 430 may employ this duty cycle to ensure that there are no conflicts when performing queries on the PTDs.

[0072] Figure 5 1 illustrates another signal flow diagram according to an example embodiment. Figure 5 As shown, the network may include passive terminal devices (PTDs) 505, PTDs 510, activators 515, activators 520, readers 525, readers 530, and BS 134. In an exemplary implementation, BS 134 may communicate with activators 515, activators 520, readers 525, and readers 530 using cellular standards. BS 134 may be a combination of devices. For example, BS 134 may represent a BS and a core network device (or entity), BS 134 may represent a BS and a control device (or entity), BS 134 may represent a base station on a satellite, a satellite acting as a relay and a ground base station, and any other similar combination of network devices. Individual devices and / or combinations of devices may sometimes be referred to as devices, systems, and the like. Activators 515, activators 520, readers 525, and / or readers 530 may be user equipment, terminal devices, user terminals, mobile devices, fixed devices, Internet of Things (IoT) devices, any wireless (or cellular) connected device, and the like.

[0073] BS 134 may transmit (e.g., wirelessly transmit) a message received by reader 530 (block 532A). BS 134 may transmit (e.g., wirelessly transmit) a message received by reader 525 (block 532B). BS 134 may transmit (e.g., wirelessly transmit) a message received by activator 520 (block 532C). BS 134 may transmit (e.g., wirelessly transmit) a message received by activator 515 (block 532C). In this implementation, the message is generated by BS 134 and transmitted to activator 515, activator 520, reader 525, and / or reader 530. In an example implementation, a message is transmitted (e.g., broadcast) by BS 134 and received by activator 515, activator 520, reader 525, and / or reader 530. The message may include a reader-based passive terminal device configuration. The reader-based passive terminal device configuration may be associated with a reader-based bistatic deployment. For example, the reader-based passive end device configuration may include at least one of the following: a maximum transmit power to be used for excitation, which is common to all excitation sources or specific to each excitation source, with the general purpose of reducing overall interference in the system; an RSRP threshold (if configured) to be considered for passive end device association; a duty cycle at which the reader / excitation source is activated to receive backscattered signals and / or transmit excitation signals and deactivated (i.e., enters a sleep mode with no Tx / Rx) for efficient energy consumption; a time offset as to when transmission should be initiated for scenarios where multiple excitation sources are broadcasting energy simultaneously, etc. In response to receiving the message, the excitation source 515, the excitation source 520, the reader 525, and / or the reader 530 may be configured to perform reader-based passive end device association based on the reader-based passive end device configuration.

[0074] The exciter 520 may generate and transmit (block 534A) an excitation signal that is received by the PTD 510. The exciter 520 may generate and transmit (block 534B) an excitation signal that is received by the PTD 505. In an example implementation, one excitation signal is transmitted (e.g., broadcast) by the exciter 520 and received by both the PTD 505 and the PTD 510. The exciter 515 may generate and transmit (block 536A) an excitation signal that is received by the PTD 510. The exciter 515 may generate and transmit (block 534B) an excitation signal that is received by the PTD 505. In an example implementation, one excitation signal is transmitted (e.g., broadcast) by the exciter 515 and received by both the PTD 505 and the PTD 510.

[0075] In response to receiving the excitation signal, the PTD 505 may generate and transmit (block 538A) a backscatter signal. The backscatter signal may be received by the reader 525. The backscatter signal may include an identification (ID) associated with the PTD 505 (sometimes referred to as a tag ID). In response to receiving the excitation signal, the PTD 505 may generate and transmit (block 538B) a backscatter signal. The backscatter signal may be received by the reader 530. The backscatter signal may include an identification (ID) associated with the PTD 505 (sometimes referred to as a tag ID). In an example implementation, one backscatter signal is generated and transmitted by the PTD 505 and received by both the reader 525 and the reader 530.

[0076] In response to receiving the excitation signal, PTD 510 may generate and transmit (block 540A) a backscatter signal. The backscatter signal may be received by reader 525. The backscatter signal may include an identification (ID) associated with PTD 510 (sometimes referred to as a tag ID). In response to receiving the excitation signal, PTD 510 may generate and transmit (block 540B) a backscatter signal. The backscatter signal may be received by reader 530. The backscatter signal may include an identification (ID) associated with PTD 510 (sometimes referred to as a tag ID). In an example implementation, one backscatter signal is generated and transmitted by PTD 510 and received by both reader 525 and reader 530.

[0077] In response to receiving backscatter signals from PTD 505 and / or PTD 510, reader 525 may perform passive end device association (block 542). For example, PTD 505 may associate with reader 525. In response to receiving backscatter signals from PTD 505 and / or PTD 510, reader 530 may perform passive end device association (block 544). For example, PTD 510 may associate with reader 530. Reader 525 and reader 530 may each be configured to make a decision to associate with a PTD based on received RSRP. In an example implementation, the RSRP threshold (if configured) may be lowered to ensure passive end device association with at least one reader. In another example, the RSRP threshold (if configured) may be increased to reduce simultaneous associations. In another example, if the RSRP threshold is not configured, the association decision may be made based on device sensitivity.

[0078] After performing passive end device association (block 542), reader 525 may transmit (e.g., wirelessly transmit) the message received by BS 134 (block 546). Reader 530 may transmit (e.g., wirelessly transmit) the message received by BS 134 (block 548). Figure 5In an example implementation, reader 525 and reader 530 report to BS 134. However, although not shown, reader 525 may report to reader 530, and reader 530 may report to BS 134. Alternatively (or additionally), reader 530 may report to reader 525, and reader 525 may report to BS 134. The message may include passive terminal device association information. For example, the passive terminal device association information may include an identifier (ID) (sometimes referred to as a tag ID) associated with PTD 505 and / or PTD 510. In an example implementation, the passive terminal device association information may be transmitted periodically and / or in response to a trigger. For example, reader 525 and / or reader 530 may be configured to report the association decision to BS 134 in order to refine the reader association decision. For example, the report may be triggered periodically after a preconfigured timer for reporting. For example, the reporting may be triggered in response to a request from BS 134 (e.g., BS 134 may dispatch a common signal to request the reader to report its association decision). For example, the reporting may be triggered based on a list of passive end devices that are associating. For example, the reporting may be triggered in response to an event at the reader (e.g., the load exceeds a certain level, requiring BS 134 involvement to efficiently distribute the load among the readers).

[0079] In response to receiving the passive terminal device association information, BS134 can perform an attachment refinement operation (block 550). In an example implementation, the attachment refinement operation can be configured to increase the connectivity of a PTD that cannot backscatter signals to any available reader with a good (e.g., greater than a threshold) RSRP and therefore cannot associate with any reader. However, the backscattered signal can be higher than the reader sensitivity. To help these PTDs (sometimes referred to as edge PTDs or edge tags), in addition to the excitation source ID, the reader also provides the perceived SINR to all relevant PTDs. BS134 can then identify PTDs that are potentially in poor radio conditions (e.g., experiencing low SINR) and send association information to the corresponding exciter to achieve synchronous excitation. As a result, the overall received signal at the PTD can be improved. The PTD can collect more energy from more than one excitation source to send a backscattered signal with a higher SINR to its associated reader.

[0080] After performing the attach refinement operation (block 550), BS 134 may transmit (e.g., wirelessly transmit) a message received by reader 530 (block 552A). BS 134 may transmit (e.g., wirelessly transmit) a message received by reader 525 (block 552B). BS 134 may transmit (e.g., wirelessly transmit) a message received by activator 520 (block 552C). BS 134 may transmit (e.g., wirelessly transmit) a message received by activator 515 (block 552D).

[0081] In this implementation, the message is generated by BS 134 and transmitted to activator 515, activator 520, reader 525, and / or reader 530. In an exemplary implementation, a message is transmitted (e.g., broadcast) by BS 134 and received by activator 515, activator 520, reader 525, and / or reader 530. The message may include the updated association and reader / activator configuration information generated in block 550. In an exemplary implementation, the association update information may include an identification (ID) (sometimes referred to as a tag ID) associated with the PTD 505 and / or PTD 510 to be associated. In an exemplary implementation, the new configuration may include an updated duty cycle configuration to ensure better coordination between available readers / activators. Reader 525 and reader 530 may employ this duty cycle to ensure that there are no conflicts when performing queries on the PTDs.

[0082] In addition, synchronous excitation can be enabled on exciter 515 and / or exciter 520 (block 554). Synchronous excitation can include substantially simultaneous excitation of two or more exciters to increase the energy at the PTD (e.g., for backscatter). Synchronous excitation can be performed on selected exciters only when required by marginal PTD. Blindly enabling synchronous excitation for all exciters may increase overall system interference. After enabling synchronous excitation, attachment is performed as described above, and the reader reports its attached tag ID to BS 134 substantially immediately or by following a reporting period configured by BS 134 to ensure that the tag is associated with only one reader (and multiple exciters) as required by the design goals.

[0083] Figure 6 is a block diagram illustrating a synchronous excitation method for reader edge PTD according to an example embodiment. Figure 6 As shown, in block S605, one or more devices may transmit a PTD ID, SINR at the reader, exciter ID, etc. to a network device (e.g., a BS). For example, the PTD may generate a backscatter signal received by the reader. The backscatter signal may include the PTD ID, exciter ID, etc. The reader may measure the SINR associated with the backscatter signal. The reader may transmit the PTD ID, SINR, exciter ID, etc. to the network device.

[0084] In block S610, a network device (eg, a BS) may receive information from all PTDs. The information may be received via a reader. The information may include PTD ID, SINR, exciter ID, etc.

[0085] In block S615, the network device may determine whether the SINR is greater than a threshold value for at least one reader. For example, the network device may receive information from multiple readers, and this information may be associated with multiple PTDs. The network device may determine whether the SINR is greater than a threshold value for at least one of the multiple readers. If the SINR is greater than the threshold value for at least one of the multiple readers, processing continues to step S625. Otherwise, processing continues to step S620.

[0086] In block S620, the network device may determine whether more than one reader reports PTD. If more than one reader reports PTD, processing continues to step S635. Otherwise, processing continues to step S630.

[0087] In block S625, the network device generates a configuration to attach the PTD(s) to the reader with the largest SINR and saves the corresponding activator ID. The network device may transmit the configuration to the activator, thereby implementing the new configuration.

[0088] In block S630, the network determines that there is no available attachment for the PTD.Then, the network waits for the next attachment cycle.

[0089] In block S610, if the reporting readers report different excitation sources, all readers are attached (eg, in a reader list).The stimulators are time synchronized for excitation signal generation.

[0090] Example 1. Figure 7 is a block diagram of a method for operating a terminal device according to an exemplary embodiment. Figure 7 As shown, in step S705, the terminal device receives configuration information from the network device, the configuration information being used for the terminal device to send a signal to or receive a signal from at least one passive terminal device, wherein the configuration information configures the terminal device to perform at least one of the following: (1) in step S710, send a signal to the at least one passive terminal device according to the configuration information, and (2) in step S715, receive at least one signal from the at least one passive terminal device, each signal being in response to reception of a transmitted signal received at the at least one passive terminal device. In step S720, an association between the at least one passive terminal device and the terminal device is determined based on received signal strength information of the at least one signal received at the terminal device.

[0091] Example 2. The method of Example 1, wherein the received signal strength information may include: a received signal power level.

[0092] Example 3. The method of Example 1, wherein the terminal device may include one of an activator, a reader, or a co-located activator and reader.

[0093] Example 4. The method of Example 1, wherein the determination of the association between the at least one passive terminal device and the terminal device may be based on a forwarded signal based on a received passive terminal device signal.

[0094] Example 5. The method of Example 4, wherein the forwarded signal can be received from another terminal device.

[0095] Example 6. The method of Example 4, wherein the forwarded signal can be received via a network node.

[0096] Example 7. The method of Example 1, wherein the configuration information may include one or more of: a maximum transmission power level, a duty cycle configuration, and a threshold value for the at least one received signal.

[0097] Example 8. The method of Example 7, wherein the terminal device is further caused to determine the association between the at least one passive terminal device and the terminal device based on the threshold value.

[0098] Example 9. The method of Example 7 or 8, wherein the terminal device may be further caused to associate the terminal device with the at least one passive terminal device by comparing the received signal strength information with the threshold.

[0099] Example 10. A method according to any one of Examples 1 to 9, wherein the terminal device can also be enabled to report or update the association between the at least one passive terminal device and the terminal device to the network device based on the received signal strength information exceeding a threshold.

[0100] Example 11. A method according to Example 10, wherein reporting the association information between the at least one passive terminal device and the terminal device can be triggered based on at least one of the following: a preconfigured timer for reporting; in response to a network request; and a predefined event for reporting at the terminal device.

[0101] Example 12. The method of Example 10, wherein the terminal device is further caused to receive an association update message between the at least one passive terminal device and the terminal device from the network device.

[0102] Example 13. The method of Example 12, wherein the terminal device is further caused to associate the terminal device with the at least one passive terminal device based on the association update message content.

[0103] Example 14. The method of Example 13, wherein the update message content may be part of or associated with a configuration information update.

[0104] Example 15. The method according to Example 13, wherein the terminal device can also be enabled to enable synchronous stimulation with another terminal device, wherein the synchronous stimulation includes: synchronizing the transmission time of the signal to the at least one passive terminal device with the other terminal device.

[0105] Example 16. The method of Example 4, wherein the terminal device is further caused to determine the association between the at least one passive terminal device and the terminal device based on a device sensitivity of the terminal device.

[0106] Example 17. Figure 8 is a block diagram of a method of operating a network device according to an example embodiment. Figure 8 As shown, in step S805, configuration information is sent to at least one terminal device, where the configuration information is used to configure the at least one terminal device to send or receive a signal to at least one passive terminal device. In step S810, corresponding association information between the at least one passive terminal device and the at least one terminal device is received from the at least one terminal device, where the corresponding association information is based on corresponding received signal strength information of at least one received signal received at the at least one terminal device, and each of the at least one received signal is reflected or backscattered by at least one corresponding passive terminal device in response to receiving a signal sent from the at least one terminal device.

[0107] Example 18. The method of Example 17, wherein the network device is further caused to: in response to a change in the association between the specific one terminal device and the specific one passive terminal device, send an update of the association information to the specific one terminal device.

[0108] Example 19. The method of Example 17, wherein the received reflected or backscattered signal strength information may include: received signal power level.

[0109] Example 20. The method of Example 17, wherein the at least one terminal device may include one of an activator, a reader, or a co-located activator and reader.

[0110] Example 21. A method according to Example 18, wherein the configuration information may include: the at least one passive terminal device identifier, time offset, duty cycle configuration, a threshold for received reflected or backscattered signals, a synchronization excitation enable indicator, and a maximum transmit power value of the at least one user terminal device.

[0111] Example 22. The method of Example 21, wherein the synchronous excitation enable indicator may indicate enabling synchronous excitation of the at least one passive terminal device based on a received power associated with the at least one passive terminal device being less than the threshold.

[0112] Example 23. A method according to Example 17, wherein the network device can also be enabled to receive association information of one or more passive terminal devices from one or more terminal devices, wherein the association information includes: one or more passive terminal device identifiers, and corresponding reflected signal receiving power.

[0113] Example 24. A method according to Example 23, wherein the network device can also be caused to: determine whether one of the reflected signal received powers is greater than a received power threshold; and in response to determining that one of the reflected signal received powers is greater than the received power threshold, generate an association update message including an updated configuration to be applied by a specific terminal device.

[0114] Example 25. A method according to Example 23, wherein the network device can also be caused to: determine whether two or more terminal device identifiers are received; and in response to determining that the two or more terminal device identifiers are received, generate the association update message to enable synchronous excitation of each of the two or more terminal devices, wherein the synchronous excitation is based on the association information, and the received signal power of one or more passive terminal devices.

[0115] Example 26. A method that may include any combination of one or more of Examples 1 to 25.

[0116] Example 27. A non-transitory computer-readable storage medium comprising instructions stored thereon, which, when executed by at least one processor, are configured to cause a computing system to perform the method according to any one of Examples 1 to 26.

[0117] Example 28. An apparatus comprising components for performing the method according to any one of Examples 1 to 26.

[0118] Example 29. An apparatus comprising at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least perform a method according to any one of Examples 1 to 26.

[0119] Figure 9 is a block diagram of a wireless station 900 or a wireless node or a network node 900 according to an example embodiment. According to an example embodiment, the wireless node or wireless station or network node 900 may include, for example, one or more of an AP, a BS, a gNB, a RAN node, a relay node, a UE or user equipment, a network node, a network entity, a DU, a CU-CP, a CU-UP, etc., or other nodes.

[0120] The wireless station 900 may include, for example, one or more (e.g., Figure 9 1 and 2. The wireless station also includes two (2) radio frequency (RF) or wireless transceivers 902A, 902B, each of which includes a transmitter for sending signals and a receiver for receiving signals. The wireless station also includes a processor or control unit / entity (controller) 904 for executing instructions or software and controlling the transmission and reception of signals, and a memory 906 for storing data and / or instructions.

[0121] The processor 904 may also make decisions or determinations, generate frames, packets, or messages for transmission, decode received frames or messages for further processing, and perform other tasks or functions described herein. For example, the processor 904, which may be a baseband processor, may generate messages, packets, frames, or other signals for transmission via the wireless transceiver 902 (902A or 902B). The processor 904 may control the transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., over a wireless network (e.g., after being down-converted by the wireless transceiver 902). The processor 904 may be programmable and capable of executing software or other instructions stored in a memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. For example, the processor 904 may be (or may include) hardware, programmable logic, a programmable processor that executes software or firmware, and / or any combination thereof. For example, using other terminology, the processor 904 and the transceiver 902 may be considered together as a wireless transmitter / receiver system.

[0122] In addition, reference Figure 9 , the controller (or processor) 908 can execute software and instructions and can provide overall control for the station 900 and can Figure 9Other systems not shown provide controls, such as controlling input / output devices (e.g., display, keypad), and / or software that can execute one or more applications that can be provided on wireless station 900, such as, for example, an email program, audio / video applications, a word processor, a voice over IP application, or other applications or software.

[0123] Additionally, a storage medium may be provided that includes stored instructions that, when executed by a controller or processor, may cause the processor 904 or other controllers or processors to perform one or more of the functions or tasks described above.

[0124] According to another example embodiment, the RF or wireless transceiver(s) 902A / 902B may receive signals or data, and / or transmit or send signals or data. The processor 904 (and possibly the transceiver 902A / 902B) may control the RF or wireless transceiver 902A or 902B to receive, send, broadcast or send signals or data.

[0125] However, the example embodiments are not limited to the systems given as examples, and those skilled in the art may apply the solutions to other communication systems. Another example of a suitable communication system is a 5G system. It is assumed that the network architecture of 5G will be very similar to that of advanced LTE. 5G may use multiple-input multiple-output (MIMO) antennas, more base stations or nodes than LTE (the so-called small cell concept), including macro sites operating in cooperation with smaller base stations, and may also adopt various radio technologies to achieve better coverage and higher data rates. Another example of a suitable communication system is a 6G system. It is assumed that the network architecture of 6G will be similar to that of 5G.

[0126] It should be appreciated that future networks are likely to utilize network function virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions into "building blocks" or entities that can be operationally connected or linked together to provide services. A virtualized network function (VNF) may include one or more virtual machines that run computer program code using standard or general-purpose type servers (rather than custom hardware). Cloud computing or data storage may also be utilized. In radio communications, this may mean that node operations may be performed at least in part in a server, host or node that is operatively coupled to a remote radio head. Node operations may also be distributed among multiple servers, nodes or hosts. It should also be understood that the workload distribution between core network operations and base station operations may be different from that of LTE, or even non-existent.

[0127] Example embodiments of the various technologies described herein may be implemented in a digital electronic circuit system, or in computer hardware, firmware, software, or a combination thereof. Example embodiments may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, for example, in a machine-readable storage device or in a propagated signal, for execution by a data processing apparatus or for controlling the operation of a data processing apparatus, for example, a programmable processor, a computer, or multiple computers. The embodiments may also be provided on a computer-readable medium or a computer-readable storage medium, which may be a non-transitory medium. Embodiments of the various technologies may also include embodiments provided via transient signals or media, and / or downloadable programs and / or software embodiments via the Internet or (multiple) other networks (wired networks and / or wireless networks). In addition, embodiments may be provided via machine type communications (MTC) or via the Internet of Things (IOT).

[0128] A computer program may be in source code form, object code form, or some intermediate form, and may be stored on some carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. Examples of such carriers include recording media, computer memory, read-only memory, optical and / or electrical carrier signals, telecommunications signals, and software distribution packages. Depending on the required processing power, a computer program may be executed on a single electronic digital computer or distributed among multiple computers.

[0129] Furthermore, example embodiments of the various techniques described herein may utilize cyber-physical systems (CPS) (systems that enable computing elements that control physical entities to collaborate). CPS may enable the implementation and utilization of a large number of interconnected ICT devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects at different locations. Mobile cyber-physical systems (where the physical system in question has inherent mobility) are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robots and electronic devices that are transported by humans or animals. The popularity of smartphones has increased interest in the field of mobile cyber-physical systems. Therefore, various embodiments of the techniques described herein may be provided by one or more of these techniques.

[0130] Computer programs such as the above-mentioned computer program(s) may be written in any form of programming language, including compiled or interpreted languages, and may be deployed in any form, including as stand-alone programs, or as modules, components, subroutines, or other units or portions thereof suitable for a computing environment. A computer program may be deployed to execute on one computer, or on multiple computers at one site, or on multiple computers distributed across multiple sites and interconnected by a communication network.

[0131] The method steps may be performed by one or more programmable processors executing a computer program or portion of a computer program to perform functions by operating on input data and generating output. The method steps may also be performed by, and apparatus may be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

[0132] For example, processors suitable for executing a computer program include both general-purpose and special-purpose microprocessors, and any one or more processors of any kind of digital computer, chip, or chipset. Typically, the processor will receive instructions and data from a read-only memory or a random access memory, or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer may also include, or be operatively coupled to, receive data from or transfer data to, or both, one or more mass storage devices (e.g., magnetic, magneto-optical, or optical disks) for storing data. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including, for example, semiconductor memory devices such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated in, special-purpose logic circuitry.

[0133] To provide interaction with a user, embodiments may be implemented on a computer having a display device (e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) display) for displaying information to the user, and a user interface (e.g., a keyboard and a pointing device, e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices may also be used to provide interaction with the user; for example, feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including sound, voice, or tactile input.

[0134] Example embodiments may be implemented in a computing system that includes a back-end component, such as a data server, or a middleware component, such as an application server, or a front-end component, such as a client computer having a graphical user interface or a web browser through which a user can interact with the embodiment, or any combination of such back-end, middleware, or front-end components. The components may be interconnected by any form or medium of digital data communication, such as a communication network. Examples of communication networks include local area networks (LANs) and wide area networks (WANs), such as the Internet.

[0135] While certain features of the described embodiments have been illustrated as described herein, those skilled in the art will now be able to devise numerous modifications, substitutions, changes, and equivalents. It should therefore be understood that the appended claims are intended to cover all such modifications and variations that fall within the true spirit of the various embodiments.

Claims

1. A terminal device, comprising: at least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the terminal device to at least: Receive configuration information from a network device, the configuration information being used by the terminal device to send a signal to at least one passive terminal device, or to receive a signal from at least one passive terminal device, wherein the configuration information configures the terminal device to perform at least one of the following: sending a signal to the at least one passive terminal device according to the configuration information, and receiving at least one signal from the at least one passive terminal device, each signal being responsive to receipt of a transmit signal received at the at least one passive terminal device; as well as An association between the at least one passive terminal device and the terminal device is determined based on received signal strength information of the at least one signal received at the terminal device.

2. The terminal device according to claim 1, wherein the received signal strength information comprises: Received signal power level.

3. The terminal device according to claim 1, wherein the terminal device comprises one of the following: exciter; reader; or Co-located activator and reader.

4. The terminal device of claim 1, wherein the determination of the association between the at least one passive terminal device and the terminal device is based on a forwarded signal, the forwarded signal being based on a received passive terminal device signal. The terminal device according to claim 4 , wherein the forwarded signal is received from another terminal device. The terminal device according to claim 4 , wherein the forwarded signal is received via a network node.

7. The terminal device of claim 1, wherein the configuration information comprises one or more of: a maximum transmission power level, a duty cycle configuration, and a threshold value of the at least one received signal.

8. The terminal device according to claim 7, wherein the terminal device is configured to: The association between the at least one passive terminal device and the terminal device is determined based on the threshold value.

9. The terminal device according to claim 7 or 8, wherein the terminal device is configured to: The terminal device is associated with the at least one passive terminal device by comparing the received signal strength information with the threshold.

10. The terminal device according to any one of claims 3 to 9, wherein the terminal device is configured to: Based on the received signal strength information exceeding a threshold, the association between the at least one passive terminal device and the terminal device is reported or updated to the network device.

11. The terminal device according to claim 10, wherein reporting the association information between the at least one passive terminal device and the terminal device is triggered based on at least one of the following: Preconfigured timers for reporting; responding to network requests; and Predefined events at the terminal device for reporting.

12. The terminal device according to claim 10, wherein the terminal device is configured to: An association update message between the at least one passive terminal device and the terminal device is received from the network device.

13. The terminal device according to claim 12, wherein the terminal device is configured to: Based on the association update message content, the terminal device is associated with the at least one passive terminal device.

14. The terminal device according to claim 13, wherein the update message content is part of a configuration information update or is associated with a configuration information update.

15. The terminal device according to claim 13, wherein the terminal device is configured to: Enabling synchronous stimulation with another terminal device, wherein the synchronous stimulation includes: A transmission time of the signal to the at least one passive terminal device is synchronized with the other terminal device.

16. The terminal device according to claim 4, wherein the terminal device is configured to: The association between the at least one passive terminal device and the terminal device is determined based on a device sensitivity of the terminal device.

17. A network device comprising: at least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the network device to at least: Sending configuration information to at least one terminal device, where the configuration information is used to configure the at least one terminal device to send or receive signals to at least one passive terminal device; as well as Receiving corresponding association information between the at least one passive terminal device and the at least one terminal device from the at least one terminal device, wherein the corresponding association information is based on corresponding received signal strength information of at least one received signal received at the at least one terminal device, and each of the at least one received signal is reflected or backscattered by at least one corresponding passive terminal device in response to receiving a signal transmitted from the at least one terminal device.

18. The network device of claim 17, wherein the network device is caused to: In response to a change in the association between the specific one terminal device and the specific one passive terminal device, an update of the association information is sent to the specific one terminal device.

19. The network device according to claim 17, wherein the received reflected or backscattered signal strength information comprises: Received signal power level.

20. The network device according to claim 17, wherein the at least one terminal device comprises one of the following: exciter; reader; or Co-located activator and reader.

21. The network device according to claim 18, wherein the configuration information comprises: The at least one passive terminal device identification, time offset, duty cycle configuration, threshold of received reflection or backscatter signal, synchronization excitation enable indicator, and maximum transmit power value of the at least one user terminal device.

22. The network device of claim 21, wherein the synchronization excitation enable indicator indicates that synchronization excitation of the at least one passive terminal device is enabled based on a received power associated with the at least one passive terminal device being less than the threshold.

23. The network device of claim 17, wherein the network device is caused to: Receiving association information of one or more passive terminal devices from one or more terminal devices, wherein the association information includes: One or more passive terminal device identifiers and the corresponding reflected signal received power.

24. The network device of claim 23, wherein the network device is caused to: Determine whether one of the reflected signal received powers is greater than a received power threshold; and In response to determining that one of the reflected signal received powers is greater than a received power threshold, an association update message including an updated configuration to be applied by the specific terminal device is generated.

25. The network device of claim 23, wherein the network device is caused to: determining whether two or more terminal device identifications are received; and In response to determining that the two or more terminal device identifications are received, the association update message is generated to enable synchronous stimulation of each of the two or more terminal devices, wherein the synchronous stimulation is based on the association information and the received signal power of one or more passive terminal devices.

26. An apparatus comprising means for performing the steps of the terminal device according to any one of claims 1 to 16.

27. An apparatus comprising means for performing the steps of the network device according to any one of claims 17 to 25.

28. An apparatus comprising at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least perform the steps of the terminal device according to any one of claims 1 to 16.

29. An apparatus comprising at least one processor and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to at least perform the steps of the network device according to any one of claims 17 to 25.

Images