Dynamic base station control for wireless controllers
By introducing semi-static segmentation and dynamic gNB control in the wireless communication system, frequency resource allocation is optimized, and the problem of low latency and high reliability in IIoT systems is solved, and the delay performance and reliability of the system are improved.
Patent Information
- Application Number
- CN202180010175.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-01-27
- Filing Date
- 2021-01-29
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2041-01-29
AI Technical Summary
Existing wireless communication systems are difficult to meet strict low latency and high reliability requirements in industrial Internet of Things (IIoT) applications, especially in multi-hop communication configurations, and delays may be difficult to meet the goal of 1-2ms.
By introducing a semi-static segmentation communication mode between the controller and the base station, using interrupt resource configuration information to manage handover time and priority, reducing the number of air transmissions, and using integrated access backhaul (IAB) framework and dynamic gNB control, optimized Frequency resource allocation, reduce transmission hop count to improve delay performance.
It realizes lower latency and higher reliability communication in IIoT system, reduces the delay problems caused by multi-hop communication, improves the overall performance and reliability of the system, and meets levels 10-5 to 10-6. reliability goals.
Smart Images

Figure CN115004832B_ABST
Abstract
Description
[0001] Claiming priority under 35 USC § 119
[0002] This patent application claims priority to and the benefit of U.S. Patent Application No. 17 / 160,126, filed on January 27, 2021, and claims the benefit of U.S. Provisional Patent Application No. 62 / 976,506, filed on February 14, 2020, the entire contents of which are hereby incorporated by reference as if fully set forth below and for all applicable purposes. Technical Field
[0003] The following generally relates to wireless communications, and more specifically, the following relates to wireless control low latency use cases. Background Art
[0004] Wireless communication systems are widely deployed to provide various types of communication services such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems, such as long term evolution (LTE) systems, improved LTE (LTE-A) systems or LTE-APro systems, and fifth generation (5G) systems that may be referred to as new radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each of which simultaneously supports communication for multiple communication devices, which may also be referred to as user equipment (UE).
[0005] 5G NR is part of the continued mobile broadband evolution, which is being released by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., along with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard.
[0006] Emerging wireless communication technologies such as URLLC can provide a reliable framework for Industrial Internet of Things (IIoT) applications that require high reliability and low latency. IIoT applications include factory automation applications, laboratory applications, and other commercial, academic, or government applications that use complex automation. Summary of the invention
[0007] Methods, systems, and devices for wireless communications are described. In summary, in one aspect, a controller such as a programmable logic controller includes memory circuits and processor circuits configured to store information such as data and instructions to perform the actions of the disclosed methods. The controller also includes transceiver circuits to send and receive signals according to the disclosed methods.
[0008] In summary, in one aspect, a method for wireless communication of a controller includes: receiving configuration information for interruption resources from a base station. The interruption resources include time resources included in a time interval for communication between the controller and one or more associated sensors / actuators (S / As). In some aspects, the controller processes the interruption information received using the interruption resources to determine a switching time, wherein the switching time is a time for switching from communication between the controller and the one or more S / As to communication between the controller and the base station.
[0009] In some aspects, the interruption information includes priority information indicating a priority for switching to communications between the controller and the base station. The method may include processing the interruption information to determine the priority information, and determining whether to switch to communications between the controller and the base station at the switching time or to continue communicating with the one or more associated S / As. In some cases, the method may include sending an acknowledgment to the base station in response to processing the interruption information and determining to switch to communications between the controller and the base station at the switching time; or sending a negative acknowledgment (NACK) to the base station in response to processing the interruption information and determining not to switch to communications between the controller and the base station at the switching time.
[0010] In some aspects, the method may include processing the interrupt information to determine an offset, the offset indicating a wait time before the switching time. The controller may process the interrupt information to determine an implicitly indicated offset or an explicitly indicated offset. The offset may indicate a particular time slot, mini-time slot, symbol, or subframe in which the switching time is included.
[0011] In some aspects, receiving configuration information for interruption resources from a base station may include: receiving an indication of one or more physical downlink control channel (PDCCH) monitoring opportunities. In some aspects, receiving configuration information for interruption resources from a base station may include: receiving physical uplink control channel (PUCCH) signaling from the base station, receiving physical uplink shared channel (PUSCH) signaling from the base station, or both operations. In some aspects, receiving configuration information for interruption resources from a base station includes: receiving broadcast signaling from the base station including at least some configuration for interruption resources. In some aspects, the interruption resources may be periodic.
[0012] In some aspects, in the absence of interruption information from the base station indicating a switching time, the controller can be configured to switch between communication with the base station and communication with the one or more S / As using semi-static segmentation. The semi-static segmentation can include a recurring set of time resources, the recurring set of time resources including a first duration during which the controller communicates with the base station and a second duration during which the controller communicates with the one or more S / As, wherein the second duration is greater than the first duration. The time resources included in the time interval for communication between the controller and one or more associated S / As can include time resources included in the second duration.
[0013] The second duration may include a plurality of cyclic communications between the controller and the one or more associated S / As. The plurality of cyclic communications between the controller and the one or more associated S / As each include a downlink-centric portion and an uplink-centric portion. In some cases, the downlink-centric portion includes a first semi-statically configured set of transmissions from the controller to the one or more associated S / As, wherein the transmissions from the controller to each of the one or more associated S / As use different frequency resources.
[0014] The downlink-centric portion may also include at least one ACK / NACK symbol, wherein the controller receives an ACK or NACK from each of the one or more associated S / As during the at least one ACK / NACK symbol. In response to receiving at least one NACK in the at least one ACK / NACK symbol, the controller may transmit a PDCCH including scheduling information for retransmission of each of the one or more associated S / As that transmitted a NACK.
[0015] In summary, in another aspect, a base station and associated methods are disclosed. The base station includes memory circuits and processor circuits configured to store information such as data and instructions to perform the actions of the disclosed methods. The base station also includes transceiver circuits to send and receive signals according to the disclosed methods.
[0016] In summary, in one aspect, a method for wireless communication at a base station includes sending configuration information for interruption resources to a controller. The interruption resources may include time resources included in a time interval for communication between the controller and one or more associated sensors / actuators (S / As). The method may also include sending interruption information using the interruption resources. The interruption information may include information indicating a switching time, wherein the switching time is a time to switch from communication between the controller and the one or more S / As to communication between the controller and the base station.
[0017] In some cases, the interruption information may include priority information indicating a priority for switching to communication between the controller and the base station. The method may also include: receiving an acknowledgement from the controller indicating that the controller will switch to communication between the controller and the base station at the switching time; or receiving a negative acknowledgement (NACK) from the controller indicating that the controller will not switch to communication between the controller and the base station at the switching time.
[0018] In some aspects, the interruption information includes an offset indicating a wait time before the switching time. The offset may indicate a specific time slot, mini-time slot, symbol, or subframe in which the switching time is included.
[0019] In some aspects, the configuration information for interrupting resources includes an indication of one or more physical downlink control channels (PDCCH) monitoring opportunities for the controller to monitor the interruption information. In some aspects, sending the configuration information for interrupting resources includes sending the configuration information using physical uplink control channel (PUCCH) signaling, physical uplink shared channel (PUSCH) signaling, or both. In some aspects, sending the configuration information for interrupting resources includes sending broadcast signaling, and the broadcast signaling includes at least some configurations for interrupting resources. The interruption resources can be periodic. In some aspects, the base station is configured to communicate with the controller using semi-static switching in the absence of an interruption.
[0020] In general, in another aspect, a sensor / actuator and associated methods are disclosed. The sensor / actuator includes memory circuitry and processor circuitry configured to store information such as data and instructions to perform the actions of the disclosed methods. The sensor / actuator also includes transceiver circuitry to send and receive signals according to the disclosed methods.
[0021] In summary, in one aspect, the sensor / actuator performs a method comprising: communicating with a controller according to a semi-static partitioning, the semi-static partitioning comprising a set of recurring time resources, the set of recurring time resources comprising a first duration and a second duration greater than the first duration. In some aspects, the second duration comprises a plurality of cyclic communications between the controller and the sensor / actuator. Communicating with the controller according to the semi-static partitioning comprises communicating with the controller during the second duration and not communicating with the controller during the first duration. The method may also comprise: receiving an indication from the controller that an interrupt is scheduled during a second duration of a particular set in the set of recurring time resources; and avoiding communicating with the controller during the scheduled interrupt. In some aspects, communicating with the controller comprises communicating with the controller using a Uu interface. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] Figure 1 An example of a wireless communication system according to the prior art is shown;
[0023] Figure 2A An example of a communication cycle between a controller and a sensor / actuator is shown;
[0024] Figure 2B An example of a communication cycle including two downlink-centric time slots and two uplink-centric time slots is shown;
[0025] Figure 3A An example of a wireless communication system according to some embodiments is shown;
[0026] Figure 3B An example of a wireless communication system using an integrated access backhaul (IAB) framework according to some embodiments is shown;
[0027] Figure 4 shows an example of a communication interval for semi-static segmentation according to some embodiments;
[0028] Figure 5 shows an example of a communication interval (including an interruption resource) for semi-static segmentation according to some embodiments;
[0029] Figure 6 An example of a controller for communicating with a base station and one or more sensors / actuators according to some embodiments is shown;
[0030] Figure 7 shows a flow chart for a controller to communicate with a base station and one or more sensors / actuators according to some embodiments;
[0031] Figure 8 An example of a base station for communicating with one or more controllers and optionally one or more sensors / actuators according to some embodiments is shown;
[0032] Fig. 9 shows a flow chart for a base station to communicate with one or more controllers and optionally one or more sensors / actuators according to some embodiments;
[0033] Fig.10 shows an example of a sensor / actuator in communication with a controller and optionally a base station according to some embodiments; and
[0034] Fig.11 A flow chart is shown for sensors / actuators communicating with a controller and an optional base station according to some embodiments. DETAILED DESCRIPTION
[0035] Emerging wireless communication systems and technologies, such as 5G (NR) URLLC (Ultra-Reliable Low Latency Communication) technology, can enable applications with stringent latency and reliability requirements. In some examples of IIoT systems, maximum latency targets on the order of 1-2 ms and reliability targets on the order of 10 -5 to 10 -6 Reliability targets of the order of 10000 are common, with some systems targeting even lower latency and / or higher reliability. In current IIoT systems, both control and data channels typically have stringent reliability targets.
[0036] The traffic for some factory automation and other IIoT systems is deterministic and periodic. A controller (such as a programmable logic controller (PLC)) and one or more associated devices (such as sensors / actuators (S / A)) use cyclic communication to perform system actions (such as executing commands to make measurements and executing measurement-related algorithms), execute movement algorithms, execute state-related algorithms, execute calibration-related algorithms, change temperature or other environmental factors (e.g., turn on heating elements, perform pressure adjustments, or adjust filtration), perform quality measurements on semi-finished products (WIP), and so on. A base station (such as an eNB, gNB, or other base station device) communicates with the PLC and S / A to provide overall system control and connects to other network devices (such as core network devices). In an IIoT environment, the S / A includes communication circuits for receiving and executing commands and receiving and sending data and also connecting to factory or laboratory equipment, measurement equipment, etc. The S / A can be integrated with the equipment, or can be a separate device to control the interface with one or more pieces of equipment.
[0037] In some previous IIoT systems, the base station functionality and controller functionality were combined into a single device, or the base station and one or more PLCs were co-located devices using a wired connection. However, locating the PLC closer to its associated S / A can allow for more reliable PLC-S / A communications, while locating the base station somewhere with relatively unobstructed transmission paths to the controller and external network devices (in the case of wireless connections to the network) enhances the reliability of those communications.
[0038] Therefore, the controller and the base station are sometimes located in different locations and are configured to communicate wirelessly. Figure 1An example communication system 100 according to the prior art is shown, which includes a PLC 102 and two associated S / As 106-1 and 106-2. The PLC 102 communicates wirelessly with the S / As 106-1 and 106-2 and with a base station (gNB) 103, while the S / As 106-1 and 106-2 communicate wirelessly with their particular PLC 102 and with the gNB 103. In this system, the gNB 103 provides control, so (for example) if the PLC 102 wants to send control information to the S / A 106-1, it first sends it to the gNB 103, and the gNB 103 sends the control information to the S / A 106-1. In another example, if S / A 160 does not successfully receive a transmission from its associated PLC 102, information about the failure needs to be sent to gNB 103, which determines whether and how to reallocate resources between PLCs 102, and then sends configuration information to PLCs 102 and S / A 106. Because multiple hops are used to transmit control information, latency requirements for each of these transmissions may be difficult to meet.
[0039] As described above, communications between a PLC and its associated S / A may be deterministic and periodic. Figure 2A For example, in Figure 1 A timing diagram of example cyclic communications in a system such as system 100 . Figure 2A Communication between one PLC 102 and one S / A 106-1 is shown, and communication between a base station such as gNB 103 and PLC 102 or communication between gNB 103 and S / A 106 is not shown.
[0040] Figure 2A The first communication cycle 200 of a plurality of communication cycles between the controller PLC 102 and its associated UE (S / A 106-1) is shown, wherein the cycle 200 has a plurality of communication cycles represented by T cycle The cycle time is 212. Figure 2A , the x-axis represents time, and the y-axis represents transmissions between the PLC 102 and the S / A 106-1. Other S / As 106 may also communicate with the same associated PLC 102 (or with other PLCs) using different frequency resources during the cycle time 212 shown.
[0041] exist Figure 2A In the example shown, the first portion of the cycle is referred to as the downlink portion 211 and the second portion is referred to as the uplink portion 215; however, some uplink communications may occur during the downlink portion, and some downlink communications may occur during the uplink portion. Figure 2B As shown in and described below, S / A 106-1 can send uplink acknowledgement and negative acknowledgement transmissions (ACK, NACK) during both the uplink portion and the downlink portion, and downlink control channel transmissions such as PDCCH (Physical Downlink Control Channel) transmissions can be sent during both the downlink portion and the uplink portion.
[0042] exist Figure 2A At the beginning of the cycle shown in , PLC 102 sends information 208 on the downlink to S / A 106-1. The information may include, for example, information associated with a command for S / A 106-1 to execute, data for S / A 106-1, update information for S / A 106-1, etc.
[0043] The downlink portion 211 of cycle 212 is denoted as T D-DL As explained in more detail below, the downlink portion 211 of the cycle time 212 may include time for initial transmission of information and time for retransmission to one or more of the S / As that did not successfully receive the initial transmission. After the downlink portion of the cycle, T cycle Including the first processing time T AP1 213, to process (at least) the newly received information. AP1 After 213, the uplink portion 215 of loop 212 is designated for uplink communication 210 from S / A 106-1 to PLC 102, Figure 2A In the D-UP As with the downlink portion 211 of the cycle, the uplink portion 215 of the cycle may include a first portion for initial transmission of information from the S / A 106-1 to the PLC 102, and a second portion for retransmission when necessary, as outlined below. The uplink information may include instructions regarding execution of commands (for commands sent on the downlink portion of the current cycle or during a previous communication cycle), data related to equipment controlled / monitored by the S / A (e.g., measurements or status information), etc.
[0044] As in Figure 2A T shown in cycle Also included is a processing portion T after the uplink portion 215 of the loop 212 AP2214. The processing portion 214 at the end of the cycle 212 may have the same or different duration as the processing time 213 in the middle of the cycle. In one example, if the end-of-cycle processing portion 214 includes processing information to be sent up to the application layer, the duration of the processing portion 214 at the end of the cycle may be greater than the processing portion 213 between the downlink portion 211 and the uplink portion 215 of the cycle 212.
[0045] Figure 2B Shown for use such as Figure 2A 106 (as shown in FIG. Figure 2A The communication resources of the communication cycle of the communication loop (as shown in FIG. 1 ) are controlled by the gNB 103, and the gNB 103 provides some control. Figure 2B In , time is shown along the x-axis and frequency is shown along the y-axis. Figure 2B The communication cycle shown in includes a downlink-centric portion and an uplink-centric portion. In the example shown, N S / As communicate using at least N frequency portions (e.g., subcarriers or subcarrier groups) 140-1 to 140-N, wherein the downlink portion of the cycle includes two downlink-centric time slots 120-a and 120-b, and the uplink portion includes two uplink-centric time slots 130-a and 130-b.
[0046] For initial downlink transmissions in slot 120-a, semi-persistent scheduling (SPS) is used.At the end of slot 120-a (eg, the last symbol of slot 120-1), each S / A 106-1 to 106-N sends an acknowledgement (ACK) or negative acknowledgement (NACK). Figure 2B A system is shown in which a NACK indicates that a transmission was partially or completely unsuccessful. If a retransmission is required (at least one NACK is received), the retransmission is scheduled in time slot 120-b using PDCCH (Physical Downlink Control Channel) scheduling. Figure 2B In the example shown, the initial transmission to S / A 106-1 is partially unsuccessful, so it is retransmitted using the same frequency resources in time slot 120-b, while the initial transmission to S / A 106-2 fails more completely, so the retransmission uses more frequency resources (in the example shown, N-1 frequency resources out of the available N frequency resources).
[0047] Similarly, semi-persistent scheduling is used for the initial uplink transmission in time slot 130-a. The uplink transmission is followed by an uplink common burst (ULCB), and any required retransmissions are then scheduled using PDCCH scheduling and sent during time slot 130-b, which is also followed by an uplink common burst. Figure 2B In the example of , the uplink transmission from S / A 106-N was partially unsuccessful, so its retransmission is scheduled for the same frequency resource 140-N, while the transmission from S / A 160-1 failed more completely, so its retransmission is scheduled for frequency resources 140-1 through 140-(N-1).
[0048] Although existing wireless system configurations can provide reliability gains compared to systems using co-located base stations and controller functions, the additional communication hops can increase latency. The systems and techniques described herein can provide reliable communications with lower latency by reducing the number of over-the-air transmissions in the control and monitoring S / A.
[0049] Figure 3A An example system 300 is shown in accordance with some embodiments. The gNB 303 is in wireless communication with one or more controllers, such as PLCs 302-1 through 302-M, each of which is in wireless communication with one or more associated S / As 306-1 through 306-N. Figure 3A In the example of FIG. 3 , PLC 302 - 1 wirelessly communicates with S / As 306 - 1 , 306 - 2 , and 306 - 3 , while PLC 302 -M wirelessly communicates with S / As 306 -(N- 1 ) and 306 -N .
[0050] System 300 locates gNB 303 separately from PLCs 302-1 through 302-M, which are located near the S / As 306 they control. By managing communications as outlined below, direct communications between gNB 303 and S / As 306 are not required, thereby reducing latency associated with multi-hop communications.
[0051] In this configuration, PLCs 302-1 to 302-M each act as a small cell or relay node with a wireless backhaul to gNB 303. During operation of the IIoT system (after acquisition and authentication), S / As 306-1 to 306-N communicate with PLCs 302-1 to 302-M and not directly with gNB 303. In examples where PLC 302-1 acts as a small cell, its associated S / As 306-1 to 306-3 may communicate exclusively with PLC 302-1, while in examples where PLC 302-1 acts as a relay node, S / As 306-1 to 306-3 may communicate with gNB 303 for operations such as system access and authentication, and then communicate exclusively with PLC 302-1. In some examples, all of the PLCs 302-1 through 302-M have the same capabilities, and in some examples, at least some of the PLCs 302-1 through 302-M have different capabilities.
[0052] In some implementations, an integrated access backhaul (IAB) framework is used to manage communications between the gNB 303, one or more PLCs 302, and one or more S / As 306. Figure 3B An example system 301 is shown in the context of an IAB framework, where a gNB 303 acts as an IAB donor and shares a central unit / distributed unit (CU / DU) functional split with a PLC 302. The gNB 303 may also manage core network functions.
[0053] exist Figure 3B In the example shown in FIG. 1 , gNB 303 acts as a distributed unit (DU) 313 for communicating with PLCs 302-1 and 302-2 over a wireless backhaul link. The DU functionality uses memory circuits at gNB 303 to store instructions and data, processor circuits for executing instructions, and processor circuits for sending instructions to the appropriate IAB node (in the Figure 3B In the example of FIG. 5 , PLCs 302 - 1 and 302 - 2 are implemented by transceiver circuits that send signals to and receive signals from.
[0054] Within the IAB framework, the gNB 303 may act as a central unit (CU) for both the control plane (CU-CP) 323 and the user plane (CU-UP) 333, and may perform other functions 343. The gNB 303 may also communicate with the core network 307 over a wired or wireless interface for system control, backhaul to human-machine interface (HMI) communications, etc.
[0055] PLCs 302-1 and 302-2 act as IAB nodes with a dual role. In communication with gNB 303, PLCs 302-1 and 302-2 implement mobile terminal (MT) functionality 312 and communicate on a wireless backhaul link. PLCs 302-1 and 302-2 communicate with gNB 303 for purposes such as inter-PLC coordination, backhaul to system control, etc. When communicating with their associated S / As (S / As 306-1 to 306-4), PLCs 302-1 and 302-2 implement DU functionality 322 and communicate on a wireless access link. PLC 302-1 and 302-2 implement DU and MT functions using memory circuits for storing instructions and data, processor circuits for executing instructions, and transceiver circuits for sending and receiving signals to and from gNB 303 (PLC implements MT function) and S / A 306 (PLC implements DU function).
[0056] exist Figure 3B In the example of , S / A plays the role of UE in its communication with PLC. By implementing the IAB framework, S / A 306-1 to 306-4 can use the standard Uu interface. In contrast, some previous systems will use the PC5 or sidelink communication interface with PLC, which requires a separate interface.
[0057] In some embodiments, PLCs 302-1 and 302-2 perform local PHY / MAC (physical / medium access control layer) functions (such as CSI-RS (channel state information resource signal), scheduling, HARQ (hybrid automatic repeat request) functions, etc.), while gNB303 performs resource management across PLCs 302-1 to 302-4. According to the IAB technology for CU / DU splitting, an example of CU / DU splitting between gNB 303 and PLCs 302-1 and 302-2 is to use option 1 for data between PLCs 302-1 and 302-2 and their associated S / As 306-1 to 306-4, and to use option 5 for data between S / As 306-1 to 306-4 and gNB 303. The above technology can provide multiple advantages in an IAB-based configuration. Since the S / As only need to support the Uu interface, the equipment complexity can be limited to the PLC. In addition, latency can be improved by reducing the number of transmission hops.
[0058] Implementations of the present disclosure may provide further latency reduction using techniques that reduce the frequency of transmissions between the PLC and the gNB compared to local traffic between the PLC and its associated S / A. One technique for managing communications is to use resource sharing across access links (communications between the PLC and its associated S / A) and across backhaul links (communications between the gNB and the PLC).
[0059] For example, a semi-static split between the backhaul link and the access link may be used. Figure 4 An example of semi-statically partitioned time and frequency resources is shown, with time along the x-axis and frequency along the y-axis. Figure 4 As shown in FIG. 1 , recurring time resource sets 450-1 and 450-2 (partially shown) each include a first duration 460 assigned to the backhaul link (during which PLC 302 communicates with gNB 303) and a second duration 470 assigned to the access link (during which PLC 302 communicates with its S / A 306). To reduce latency for operation of the IIoT system, the second duration 470 is greater than the first duration 460. Note that throughout the description, the terms "first" and "second" do not mean that the first element necessarily precedes the second element in time.
[0060] For PLC / gNB communication during the first duration 460, PLC 302 assumes the role of MT and gNB 303 assumes the role of DU. The first duration 460 may include transmission of PDCCH from gNB 303 to PLCs 302-1 and 302-2. During the uplink portion of the first duration 460, PLCs 302-1 and 302-2 transmit to gNB 303 on the assigned resources and schedule common uplink bursts at the end of the first duration 460. Figure 4 As shown in FIG. 4 , the first duration 460 is shown as having only an uplink portion; however, the first duration 460 may include a single uplink portion, a single downlink portion, or a combination of an uplink portion and a downlink portion, depending on the implementation. The first duration 460 includes a plurality of symbols; for example, one or more time slots, mini-slots, or other durations. The frequency resources during the first duration 460 may include one or more subcarriers assigned to different PLCs and / or frequency resources common to multiple PLCs.
[0061] The PLC assumes the role of the DU and the S / A assumes the role of the MT during the second duration 470. For example, the PLC 302-1 uses some or all of the frequency resources 440 to send PDCCH transmissions to the S / As 306-1 and 306-2 during the first (downlink-centric) time slot 420-1, sends downlink traffic to the S / As 306-1 and 306-2 during different portions of the frequency resources 440 in subsequent symbols of the first time slot 420-1, and receives information from the S / As 306-1 and 306-2 during an uplink common burst at the end of the first time slot 420-1. At the end of the second duration 470, PLC 302-1 sends a PDCCH to S / As 306-1 and 306-2 during the Nth (uplink-centric) time slot 430-N, receives uplink traffic from S / As 306-1 and 306-2, and then receives uplink common bursts from S / As 306-1 and 306-2. After the end of the second duration 470, another time resource in the recurring set of time resources 450-2 begins. The second duration 470 includes at least one transmission cycle having a downlink portion for transmission from the PLC to the S / As and at least one uplink portion from the S / As to the PLC. The second duration 470 may be referred to as a gNB "gap out" period during which the gNB generates communication resources to the PLC and the S / As.
[0062] In some implementations, similar to Figure 2A and 2B The cyclic transmissions shown in the cyclic transmissions may be used for the first duration 460 and / or the second duration 470. For example, a first time slot of the second duration 470 may be semi-persistently scheduled (with a PDCCH zero symbol or a small number of symbols to schedule a non-resource allocation transmission), and may be followed by a second time slot that includes a PDCCH schedule for retransmissions of those S / As that sent a NACK in response to the first transmission, wherein each S / A 306 that needs a retransmission is assigned one or more frequency portions of the frequency resources 440. Although Figure 2A and 2B Control transmissions (such as PDCCH) are provided by gNB 103, but control transmissions in the current embodiment are provided by PLC 302.
[0063] Figure 4 Embodiments provide reduced latency for traffic between PLC and S / A, with regular intervals during which the gNB can perform control functions (such as resource allocation between PLCs).
[0064] One challenge with this implementation is determining the relative lengths of the first duration 460 and the second duration 470. Increasing the second duration 470 allows more resources to be dedicated to traffic between the PLC and its associated S / A, but may make it difficult for the gNB to effectively manage resource allocation or other issues. On the other hand, dedicating more resources to gNB control makes it more difficult to meet latency requirements.
[0065] In some implementations, outage resources may be used for dynamic gNB control. Figure 5 An embodiment is shown in which interruption is used to dynamically schedule gNB control. Figure 5 In the example, gNB 303 configures interruption resource (IR) 580, which is used by gNB 303 to indicate the interruption resource used by gNB in addition to Figure 4 4. The IR 580 is a time and frequency resource for switching time 590 for communicating with PLC 302 at a time outside of the scheduled first duration 460 of the semi-statically partitioned recurring time resources 450 shown in FIG. That is, IR 580 is used to give control to gNB 303 during the time resources originally used for traffic between PLC 302 and S / A 306.
[0066] There are multiple different ways that the gNB can configure the interruption resources. In a first example, the gNB can act as another UE for the PLC in the UL timeslot of the PLC. That is, the interruption resources can be configured so that the gNB is allocated resources within the uplink portion of the communication cycle between the PLC and the S / A, and uses Physical Uplink Control Channel (PUCCH) / Physical Uplink Shared Channel (PUSCH) signaling to use IR 580 to schedule a switching time that indicates when the gNB communicates with the PLC at a time other than the first duration 460 (the time allocated for gNB / PLC communication in semi-static switching). In another example, the gNB 303 can configure the PDCCH monitoring opportunity for the PLC as IR 580.
[0067] In either example, the IR 580 may include information indicating an offset 595 indicating the amount of time between the IR and the switching time 590 to the gNB / PLC communication. Figure 5In the example shown in , during IR 580-2, the gNB indicates a request or command for resources for communicating with one or more of the PLCs, and indicates an offset 595 between IR 580-1 and the time during which the gNB will begin communicating with some or all of the PLCs. One or more communication cycle portions may occur during the offset 595. At the switching time, a new set of time resources 550-2 (starting from the first duration 560) may begin, or the set of time resources 550-1 will resume, depending on the implementation.
[0068] In some embodiments, the IR 580 may include priority information, and the interruption may be a request for gNB control that may be rejected by one or more of the PLCs. For example, the IR 580 may include an indication of the priority of information regarding the gNB's desire to communicate with one or more of the PLCs. The PLCs then send an acknowledgment (ACK) or a negative acknowledgment (NACK) to indicate whether the PLC will communicate with the gNB during the requested interval.
[0069] In some cases, IR 580 can be shared between PLCs so that the interruption can be broadcast based. When a change in resource allocation is required, the gNB usually has to communicate with more than one PLC, because when one PLC needs more resources to improve its reliability of communication with the S / A, it is usually necessary to reduce the resource allocation to one or more other PLCs.
[0070] Compared to a semi-static split between backhaul and access links alone, the example of using dynamic gNB control can provide more flexible and better performing communications between the PLC and its associated S / A. Figure 4 The second duration 470 will be chosen to be small enough so that the gNB can manage resources efficiently; however, this reduces resources available for communication between the PLC and its S / A. Where dynamic gNB control is utilized, the second duration can be extended, and if the gNB needs to reclaim control before the next instance of the first duration, it has a mechanism to do so.
[0071] The following Figures 6 to 11 An example structure and flow chart for implementing the above-described techniques are shown.
[0072] Figure 6A simplified diagram of an example controller PLC 602 is shown. In operation, the PLC 602 communicates with a base station gNB 603 and one or more S / As 606 associated with equipment 604. The PLC 602 includes antenna circuitry 630, transceiver circuitry 625, processor circuitry 620, and memory circuitry 640 including data and instructions 645. The transceiver circuitry 625 includes one or more receive (Rx) chains 627 having RF components (such as amplifiers, analog-to-digital converters, mixers, oscillators, filters, etc.) for processing received downlink signals and one or more transmit (TX) chains 628 (which include RF components for generating signals to be sent on the uplink). The PLC 602 includes processor circuitry 620 and memory circuitry 640. The processor circuitry 620 and memory circuitry 640 are shown as separate blocks, but may be implemented in a variety of ways; for example, the processor circuitry may be implemented in one or more dedicated areas of a chip or in a different chip, and at least some of the memory circuitry in the memory circuitry 640 may be integrated with the processor circuitry. Similarly, memory circuit 640 can be implemented as a main memory, with or without other portions of the memory circuit added on the same or different chip, and at least some of the processor circuits in processor circuit 620 can be integrated with memory circuit 640. Note that "processor circuit," "memory circuit," and similar language are used herein to refer to structures. Instructions stored in memory circuit 640 and executed by processor circuit 620 cause PLC 602 to perform operations described more fully below.
[0073] Figure 7 A flow chart of a method 700 that may be performed by a controller, such as a PLC 302 or 602, is shown. At 710, the controller receives configuration information for interruption resources. The interruption resources include time resources included in a time interval for communication between the controller and one or more associated S / As. The interruption resources may be configured based on receiving PUCCH and / or PUSCH signaling from the gNB 603 (as described above in an implementation in which the gNB 303 acts as a UE), based on receiving an indication of one or more PDCCH monitoring opportunities, or in a different manner. In some embodiments, at least some of the configuration information for the interruption resources may be received as broadcast signaling from the gNB 603. The gNB 603 may send a common interruption request across multiple PLCs, so that the PLCs may stop transmitting during the interruption resources, and so that the multiple PLCs may reallocate resources as needed. As Figure 5 As shown in , the interruption resources can be periodic, where the period is chosen to balance the need for the gNB 603 to quickly alleviate communication issues with the need to allocate sufficient PLC / SA communication resources for latency targets.
[0074] At 720, the PLC 602 processes the interruption information received using the interruption resources to determine a switching time, wherein the switching time is a time for switching from communications between the PLC 602 and one or more associated S / As to communications between the PLC 602 and a base station (such as a gNB 603). The switching time can be indicated explicitly or implicitly. An example of an implicit indication is a case where the switching time is the same for all interruptions (e.g., the start of a next slot, a mini slot, a subframe, the start of a second next slot, etc.), wherein the switching time is priority-based (e.g., an indication of a high priority implicitly indicates a switching time at the start of the next slot, etc.), the switching time is control information type-based (e.g., a switching time for resource allocation is implicitly the start of the next slot, etc.), or based on another parameter (a mode, state, device type, emergency or critical indication, etc. is associated with a particular switching time or calculation for the switching time).
[0075] An example of an explicit indication is an indicated offset. The offset is used to indicate a waiting time before the switching time and can be provided in a variety of ways. For example, the offset can indicate a symbol index of the switching time, a subframe index of the switching time, a waiting time (expressed as an offset symbol or number of slots relative to the current symbol, relative to the start symbol of the current slot, relative to the end symbol of the current slot, or some other expression of the waiting time). Failure to indicate an offset or indicating an offset value equal to a certain value (such as zero) can indicate that the switching time is the beginning of the next slot, mini slot, subframe, or other time position.
[0076] In some embodiments, the interruption information includes priority information indicating a priority for switching to communication between the controller and the base station. For example, if the gNB 603 wants to send or update advanced information, it may indicate a relatively low priority, and if the gNB 603 wants to change resource allocation due to interference and / or blocking, it may indicate a relatively high priority. At 730, the PLC 602 optionally processes the interruption information to determine the priority information, and determines whether to switch to communication between the controller and the base station at the switching time or to continue communicating with one or more S / A 606. In some embodiments, the PLC 602 optionally sends an ACK to the gNB 303 in response to determining to switch to communication between the controller and the base station at the switching time, or sends a NACK to the gNB 303 in response to determining not to switch to communication between the controller and the base station at the switching time.
[0077] At 740, if PLC 602 does not have the option to determine whether to switch to communication with gNB 603 at the switch time, or if it has the option and determines to switch, PLC 602 switches to communication with the gNB at the switch time. At the switch time, a new set of time resources may be started, or the current set of time resources may be resumed after an interruption, depending on the implementation.
[0078] Alternatively, at 750, if the PLC 602 does not receive the interruption information indicating the switching time, or if the interruption information includes priority information and the PLC 602 determines not to switch, the PLC 602 continues to communicate with one or more S / As 606 associated with it until it is next scheduled to switch to communication with the gNB 603. Figure 4 and 5 In an example of a semi-static segmentation, the PLC 602 maintains communication with its S / A 606 until the end of the second duration of the current set of time resources and changes at the beginning of the first duration of the next recurring set of time resources (the next scheduled time for switching). According to some embodiments, when the PLC 602 is communicating with its S / A 606, it can use cyclic communication. The multiple cyclic communications in these embodiments include a downlink-centric portion (where the PLC 602 sends data, commands, etc. to the S / A 606), and an uplink-centric portion (where the PLC 602 receives data from the S / A 606 (such as measurement data, health or status information, etc. based on commands in the downlink-centric portion of the previous cycle)). The downlink-centric portion may include a first semi-statically configured set of transmissions from the controller to one or more associated S / As 606, which uses different frequency resources for each of the one or more S / As. The downlink-centric portion may include at least one ACK / NACK symbol, and the PLC 602 receives ACKs and NACKs sent on the at least one ACK / NACK symbol from its S / A 606. In response to the at least one NACK, the PLC 602 sends a PDCCH including scheduling information for retransmission of each of the associated S / A 606 that sent the NACK.
[0079] refer to Figure 6 and 7 , PLC 602 uses antenna circuit 630 and transceiver circuit 625, according to Figure 7 6 to receive and send information using the techniques outlined in , and uses processor circuit 620 to process information and make determinations and memory circuit 640 to store data and instructions 645 .
[0080] Figure 8A simplified diagram of an example base station gNB 803 is shown in accordance with some embodiments. In operation, the gNB 803 communicates with one or more controllers, such as PLCs 802-1 and 802-2. In some embodiments, the gNB 803 communicates exclusively with the PLC 802 and not with the S / A 806. Optionally, for some systems or in some circumstances, the gNB 803 may communicate with the S / A 806; for example, when its associated PLC 802 is a relay node that does not have the capability to perform actions such as acquisition and authentication. In such a system, the gNB 803 communicates exclusively with the PLC 802 during the time that the PLC is controlling the S / A 806. The gNB 803 includes antenna circuitry 835, transceiver circuitry 827, processor circuitry 825, and memory circuitry 845 including data and instructions 847. The transceiver circuitry 827 includes one or more receive (Rx) chains having RF components (such as amplifiers, analog-to-digital converters, mixers, oscillators, filters, etc.) for processing received downlink signals, and one or more transmit (TX) chains including RF components for generating signals to be sent on the uplink. The processor circuitry 825 and the memory circuitry 845 are shown as separate blocks, but may be implemented in a variety of ways; for example, the processor circuitry may be implemented in one or more dedicated areas of a chip or in a different chip, and in some implementations, at least some of the memory circuitry 845 may be integrated with the processor circuitry 825. Similarly, the memory circuitry 845 may be implemented as a main memory with or without other portions of the memory circuitry added on the same or different chip, and in some implementations, at least some of the processor circuitry 825 may be integrated with the memory circuitry 845. The instructions stored in the memory circuitry 845 and executed by the processor circuitry 825 cause the gNB 803 to perform operations described more fully below.
[0081] Fig. 9 A flow chart of a method 900 that may be performed by a base station such as a gNB 303 or 803 is shown. At 910, the gNB generates configuration information for blackout resources and sends it to a controller such as a PLC 302 or 802. The blackout resources include time intervals (e.g., intervals between the controller and one or more associated S / As 306 or 806) for communication. Figure 5gNB 803 may configure the blackout resources using PUCCH and / or PUSCH (e.g., as described above, gNB 803 acts as a UE), may configure one or more PDCCH monitoring opportunities, or may configure the resources in a different manner. In some embodiments, at least some configuration information for the blackout resources may be broadcast from gNB 803. Figure 5 As shown in , the interruption resources can be periodic, where the period is chosen to balance the need for the gNB 803 to quickly alleviate communication issues with the need to allocate sufficient PLC / SA communication resources for latency targets.
[0082] At 920, the gNB 803 generates interruption information and sends the interruption information using interruption resources. The interruption information includes information indicating a switching time, wherein the switching time is a time for a controller to switch from communication between the controller and one or more of its associated UEs to communication between the controller and the gNB 803. As described above, the switching time can be indicated explicitly or implicitly. An example of an implicit indication is a case where the switching time is the same for all interruptions (e.g., the beginning of the next time slot, mini-time slot, subframe, etc.), where the switching time is priority-based (e.g., an indication of a high priority implicitly indicates a switching time at the beginning of the next time slot, etc.), the switching time is based on the type of control information (e.g., the switching time for resource allocation is implicitly the beginning of the next time slot, etc.), or is based on another parameter (mode, state, device type, emergency or critical indication, etc.).
[0083] An example of an explicit indication is an offset. The offset indicates a waiting time before the switching time and can be provided in a variety of ways. For example, the offset can indicate a symbol index of the switching time, a subframe index of the switching time, a waiting time (expressed as an offset symbol or number of slots relative to the current symbol, relative to the start symbol of the current slot, relative to the end symbol of the current slot, or some other expression of the waiting time). Failure to indicate an offset or indicating an offset value equal to a certain value (such as zero) can indicate that the switching time is the beginning of the next slot, mini slot, subframe, or other time resource.
[0084] The interruption information may optionally include priority information. If the gNB 803 indicates a priority, at 930, the gNB 803 may then (also optionally) receive an indication from the PLC that they will switch at the switch time or that they will not switch at the switch time. In some embodiments, the gNB 803 may receive an ACK from the first PLC 802-1 as an indication that it will switch from communication with one or more of its associated S / As to communication with the gNB 803 at the switch time, or may receive a NACK as an indication that the PLC 802-1 will not switch.
[0085] At 940, if PLC 802 does not have the option to determine whether to switch to communication with gNB 803 at the switch time, or if PLC 802 has the option and determines to switch, the gNB communicates with PLC 802 at the switch time. At the switch time, a new set of recurring time resources may begin, or the current set of time resources may be resumed after an interruption, depending on the implementation.
[0086] Alternatively, at 950, if gNB 803 does not determine to initiate an outage, or if PLC 802 has the option to switch and determines not to switch, gNB 803 waits until the next scheduled duration for communication with the PLC. Figure 4 and 5 In an example of semi-static segmentation, gNB 803 waits until the end of the second duration of the current time resource set and starts communication with PLC 802 at the beginning of the first duration of the next recurring time resource set (the next scheduled time for switching).
[0087] refer to Figure 8 and 9 , gNB 803 uses antenna circuit 835 and transceiver circuit 827, according to Fig. 9 to receive and send information using the techniques outlined in , and uses processor circuit 825 to process the information, generate information for transmission and make determinations, and uses memory circuit 845 to store data and instructions 847.
[0088] Fig.10A simplified diagram of an example S / A 1006 is shown in accordance with some embodiments. In operation, the S / A 1006 communicates with a specific controller, such as the PLC 1002. As described above, for some systems or in some situations, the S / A 1006 may communicate exclusively with the PLC 1102, or alternatively with the gNB 1003; for example, when the PLC 1002 is a relay node that does not have the ability to perform actions such as acquisition and authentication with the S / A 1006. The S / A 1006 manages the equipment 1004 using a wired or wireless interface. The S / A 1006 includes antenna circuitry 1035, transceiver circuitry 1030, processor circuitry 1026, and memory circuitry 1046 including data and instructions 1048. The transceiver circuit 1030 includes one or more receive (Rx) chains 1039 having RF components (such as amplifiers, analog-to-digital converters, mixers, oscillators, filters, etc.) for processing received downlink signals, and one or more transmit (TX) chains 1038 including RF components for generating signals to be sent on the uplink. The processor circuit 1026 and the memory circuit 1046 are shown as separate blocks, but can be implemented in a variety of ways; for example, the processor circuit can be implemented in one or more dedicated areas of the chip or in a different chip, and in some implementations, at least some of the memory circuits in the memory circuit 1046 can be integrated with the processor circuit. Similarly, the memory circuit 1046 can be implemented as a main memory, with or without other parts of the memory circuit added on the same or different chip, and in some implementations, at least some of the processor circuits in the processor circuit 1026 can be integrated with the memory circuit 1046. Note that "processor circuit", "memory circuit" and similar language are used herein to refer to structures. The instructions stored in memory circuit 1046 and executed by processor circuit 1026 cause S / A 1006 to perform operations described more fully below.
[0089] Fig.11A flow chart of a method 1100 that can be performed by the S / A 306 or 1006 is shown. At 1110, the S / A 1106 communicates with a controller such as a PLC 1102 according to a semi-static partitioning that includes a set of recurring time resources, the set of recurring time resources including a first duration and a second duration greater than the first duration. The S / A 1106 communicates with the PLC 1102 according to the semi-static partitioning by communicating with the PLC 1102 during the second duration and not communicating with the controller during the first duration. In some embodiments, the S / A 1106 communicates with the PLC 1102 using a Uu interface. At 1120, the S / A 1106 receives an indication from the controller that an interruption is scheduled for one or more frequency resources within the second duration of a particular set of recurring time resources. At 1130, the S / A 1106 does not communicate with the PLC 1102 during the interruption using the one or more frequency resources.
[0090] During the second duration, without interruption, at 1140, the S / A 1106 communicates with the PLC 1102 using cyclic communication. The cyclic communication between the controller and the S / A 1106 each includes a downlink-centric portion and an uplink-centric portion, wherein the downlink-centric portion includes a semi-statically configured first transmission from the PLC 1102 to the S / A 1106 on one or more assigned frequency resources. At 1150, the S / A 1106 sends an ACK or a NACK after the first transmission. At 1160, in response to sending the NACK, the S / A 1106 receives a physical downlink control channel (PDCCH) transmission from the PLC 1102 scheduling one or more frequency resources for retransmission, wherein the one or more frequency resources for retransmission may be the same or different from the one or more frequency resources for the first transmission.
[0091] refer to Fig.10 and 11 , S / A 1106 uses antenna circuit 1035 and transceiver circuit 1030, according to Fig.11 1048 and uses memory circuits 1046 to store data and instructions 1048.
[0092] It should be noted that these methods describe possible implementations, and operations and steps can be rearranged or otherwise modified so that other implementations are also possible. In some examples, various aspects from two or more methods can be combined. For example, various aspects of each method in the method can include other aspects described herein, or steps or aspects of other steps or technologies.
[0093] The description herein is provided to enable one of ordinary skill in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is given the widest scope consistent with the principles and novel features disclosed herein.
[0094] The functions described herein can be implemented with hardware, software executed by a processor, firmware, or any combination thereof. If implemented with software executed by a processor, the functions can be stored on a computer-readable medium as one or more instructions or codes or sent by it. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software, hardware, firmware, hard wiring, or any combination of these items executed by a processor. The features of implementing the functions can also be physically located at various locations, including being distributed so that the functions of each part of the functions are implemented at different locations (physical). In addition, as used herein (including in the claims), the "or" used in the list of items (e.g., a list of items ending with phrases such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).
[0095] Computer readable medium includes both computer storage medium and communication medium, and communication medium includes any medium that promotes the transmission of computer program from one place to another place.Computer storage medium can be any available medium that can be accessed by general-purpose computer or special-purpose computer, but phrase "computer storage medium" does not refer to temporary propagation signal.By way of example and not limitation, computer storage medium can include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage device, or can be used for storing desired program code unit and can be accessed by general-purpose or special-purpose computer or general-purpose or special-purpose processor in the form of instruction or data structure.In addition, the connection of sending information is called communication medium.For example, if software is to send from website, server or other remote source using coaxial cable, optical fiber cable, twisted pair, digital subscriber line (DSL) or wireless technology such as infrared, radio and microwave, then coaxial cable, optical fiber cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of communication medium.
[0096] The technology of this article is described with reference to systems using broadband, such as 5G or new radio (NR) systems and future systems using spectrum in the mmW range of the electromagnetic spectrum. If applicable, the technology described herein can be used in various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, single carrier frequency division multiple access (SC-FDMA), and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000 versions 0 and A are commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, high speed packet data (HRPD), etc. UTRA includes broadband CDMA (WCDMA) and other variants of CDMA. A TDMA system can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA systems can implement radio technologies such as ultra mobile broadband (UMB), evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16 (WiMAX), IEEE 802.20, flash-OFDM, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (Universal Mobile Telecommunications System (UMTS)). 3GPP LTE and improved LTE (LTE-A) are new versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-a, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The technology described herein can be used for the systems and radio technologies mentioned above as well as other systems and radio technologies. However, for the purpose of example, the description herein describes a 5G system, and 5G terms are used in most of the descriptions above, but the scope of application of the technology exceeds 5G applications.
[0097] A base station may include or may be referred to by those skilled in the art as a base station transceiver, a wireless base station, an access point (AP), a wireless transceiver, a node B, an evolved node B (eNB), a home node B, a home evolved node B, a gNodeB or some other appropriate term. The geographic coverage area of a base station may be divided into sectors, which constitute only a portion of the coverage area. One or more wireless communication systems described herein may include different types of base stations (e.g., macro cell base stations or small cell base stations). The UE described herein is capable of communicating with various types of base stations and network devices (including macro eNBs, small cell eNBs, relay base stations, etc.). For different technologies, there may be overlapping geographic coverage areas. In some cases, different coverage areas may be associated with different communication technologies. In some cases, the coverage area for one communication technology may overlap with the coverage area associated with another technology. Different technologies may be associated with the same base station, or with different base stations.
[0098] A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE through a service subscription with a network provider. Small cells may be lower power base stations compared to macro cells, and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. According to various examples, small cells may include pico cells, femto cells, and micro cells. For example, a pico cell may cover a small geographic area and may allow unrestricted access by a service subscription with a network provider. A femto cell may also cover a small geographic area (e.g., a residence), and may provide restricted access to UEs associated with a femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in a residence, etc.). An eNB for a macro cell may be referred to as a macro eNB. An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB may support one or more (e.g., two, three, four, etc.) cells (e.g., component carriers (CCs)). A UE may be able to communicate with various types of base stations and network devices including macro eNBs, small cell eNBs, relay base stations, and the like.
[0099] One or more wireless communication systems described herein may support synchronous or asynchronous operation. For synchronous operation, base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.
[0100] The DL transmission described herein may also be referred to as a forward link transmission, and the UL transmission may also be referred to as a reverse link transmission. Each communication link described herein may include one or more carriers, wherein each carrier may be a signal consisting of multiple subcarriers (e.g., waveform signals of different frequencies). Each modulated signal may be sent on a different subcarrier and may carry control information (e.g., reference signals, control channels, etc.), overhead information, user data, etc. The communication link described herein may use frequency division duplex (FDD) operation (e.g., using paired spectrum resources) or time division duplex (TDD) operation (e.g., using unpaired spectrum resources) to send bidirectional communications. A frame structure for FDD (e.g., frame structure type 1) and a frame structure for TDD (e.g., frame structure type 2) may be defined.
[0101] It should be noted that these methods describe possible implementations, and that the operations and steps may be rearranged or otherwise modified so that other implementations are possible. In some examples, aspects from two or more methods may be combined.
[0102] The various illustrative blocks and modules described in conjunction with the disclosure herein can be implemented or executed using a general-purpose processor, digital signal processor (DSP), ASIC, field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in an alternative manner, the processor can be any conventional processor, controller, microcontroller or state machine. The processor can also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration). Therefore, the functions described herein can be performed by one or more other processing units (or cores) on at least one integrated circuit (IC). In various examples, different types of ICs (e.g., structured / platform ASICs, FPGAs or other semi-custom ICs) that can be programmed in any manner known in the art can be used. The functions of each unit can also be implemented in whole or in part using instructions embodied in a memory and formatted to be executed by one or more general or special processors.
[0103] In the drawings, similar components or features may have the same or similar reference numerals. In addition, various components of the same type may be distinguished by following the reference numeral with a dash and a second reference numeral, the second reference numeral being used to distinguish between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, without regard to the second reference numeral or other subsequent reference numerals.
Claims
1. A method for wireless communication at a controller, include: receiving, from a base station, configuration information for interruption resources, the interruption resources comprising time resources included in a time interval for communication between the controller and one or more associated sensors / actuators (S / As); as well as processing interruption information received using the interruption resource to determine a switching time, wherein the switching time is a time for switching from communication between the controller and the one or more S / As to communication between the controller and the base station, The interruption information includes priority information associated with information to be sent by the base station, and the priority information indicates a priority for switching from communication between the controller and the one or more S / As to communication between the controller and the base station.
2. The method according to claim 1, further comprising: include: processing the interrupt information to determine the priority information; as well as A determination is made as to whether to switch to communication between the controller and the base station at the switching time or to continue communicating with the one or more associated S / As.
3. The method according to claim 2, further comprising: include: sending an acknowledgement to the base station in response to processing the interruption information; as well as Switching to communication between the controller and the base station at the switching time.
4. The method according to claim 2, further comprising: include: In response to processing the interruption information, sending a negative acknowledgement (NACK) to the base station; as well as Communication between the controller and the base station is maintained at the switching time.
5. The method according to claim 1, in, Processing the interruption information received using the interruption resource to determine the switching time further includes processing the interruption information to determine an offset, the offset indicating a wait time before the switching time.
6. The method according to claim 5, in, Processing the interruption information to determine the offset also includes: processing the interruption information to determine an implicitly indicated offset or an explicitly indicated offset, wherein the offset indicates a specific time slot, mini time slot, symbol or subframe, and wherein the switching time is included in the specific time slot, mini time slot, symbol or subframe.
7. The method according to claim 1, in, Receiving configuration information for outage resources from the base station also includes receiving an indication of one or more physical downlink control channel (PDCCH) monitoring opportunities from the base station.
8. The method according to claim 1, in, Receiving configuration information for interruption resources from the base station further includes: receiving physical uplink control channel (PUCCH) signaling from the base station, receiving physical uplink shared channel (PUSCH) signaling from the base station, or performing both operations.
9. The method according to claim 1, in, Receiving configuration information for blackout resources from the base station also includes receiving broadcast signaling from the base station including at least some configuration for blackout resources.
10. The method according to claim 1, in, The interruption resource is periodic.
11. The method according to claim 1, in, In the absence of interruption information from the base station indicating the switching time, the method further includes switching between communication with the base station and communication with the one or more S / As using semi-static segmentation.
12. The method according to claim 11, in, The semi-static segmentation includes a set of recurring time resources, which includes a first duration during which the controller communicates with the base station and a second duration during which the controller communicates with the one or more S / As, and wherein the second duration is greater than the first duration.
13. The method according to claim 12, in, The time resources included in the time interval for communication between the controller and one or more associated S / As also include time resources included in the second time duration.
14. The method according to claim 12, in, The second duration includes a plurality of cycles of communication between the controller and the one or more associated S / As.
15. The method according to claim 14, in, The plurality of cyclic communications between the controller and the one or more associated S / As each include a downlink-centric portion and an uplink-centric portion.
16. The method according to claim 15, in, The downlink-centric portion includes a first set of semi-statically configured transmissions from the controller to the one or more associated S / As, wherein the transmissions from the controller to each of the one or more associated S / As use different frequency resources.
17. The method according to claim 16, in, The downlink-centric portion also includes at least one acknowledgement / negative acknowledgement (ACK / NACK) symbol, wherein the controller receives an ACK or a NACK from each of the one or more associated S / As during the at least one ACK / NACK symbol.
18. The method according to claim 17, in, Also includes: In response to receiving at least one NACK in the at least one ACK / NACK symbol, a PDCCH is transmitted, the PDCCH including scheduling information for retransmission of each of the one or more associated S / As for which the NACK was transmitted.
19. A controller, include: Memory circuit; as well as The processor circuit, the memory circuit and the processor circuit are configured to perform the following operations: receiving, from a base station, configuration information for interruption resources, the interruption resources comprising time resources included in a time interval for communication between the controller and one or more associated sensors / actuators (S / As); as well as processing interruption information received using the interruption resource to determine a switching time, wherein the switching time is a time for switching from communication between the controller and the one or more S / As to communication between the controller and the base station, The interruption information includes priority information associated with information to be sent by the base station, and the priority information indicates a priority for switching from communication between the controller and the one or more S / As to communication between the controller and the base station.
20. The controller according to claim 19, in, The memory circuit and the processor circuit are further configured to: processing the interrupt information to determine the priority information; as well as A determination is made as to whether to switch to communication between the controller and the base station at the switching time or to continue communicating with the one or more associated S / As.
21. The controller according to claim 20, in, The memory circuit and the processor circuit are further configured to process the interrupt information and determine to switch to communication between the controller and the base station at the switching time, and to generate an acknowledgement, wherein the controller further comprises a transceiver circuit configured to send the acknowledgement to the base station.
22. The controller according to claim 20, in, The memory circuit and the processor circuit are further configured to process the interruption information and maintain communication between the controller and the base station at the switching time, and generate a negative acknowledgement, wherein the controller further comprises a transceiver circuit for sending the negative acknowledgement (NACK) to the base station.
23. The controller according to claim 19, in, The memory circuit and the processor circuit are further configured to process the interrupt information to determine an offset, the offset indicating a wait time before the switch time.
24. The controller according to claim 19, in, The memory circuit and the processor circuit are further configured to receive an indication of one or more physical downlink control channel (PDCCH) monitoring opportunities from the base station, receive physical uplink control channel (PUCCH) signaling from the base station, or receive physical uplink shared channel (PUSCH) signaling from the base station.
25. The controller according to claim 19, in, The memory circuit and the processor circuit are further configured to receive broadcast signaling from the base station including at least some configuration for blackout resources.
26. The controller according to claim 19, in, The memory circuit and the processor circuit are further configured to switch between communicating with the base station and communicating with the one or more S / As using semi-static segmentation in the absence of interrupt information from the base station indicating the switching time.
27. An apparatus for wireless communication, include: means for receiving, from a base station, configuration information for interruption resources including time resources included in a time interval for communication between the controller and one or more associated sensors / actuators (S / As); and means for processing interruption information received using the interruption resources to determine a switching time, wherein the switching time is a time for switching from communication between the controller and the one or more S / As to communication between the controller and the base station, The interruption information includes priority information associated with information to be sent by the base station, and the priority information indicates a priority for switching from communication between the controller and the one or more S / As to communication between the controller and the base station.
28. A non-transitory computer readable medium storing code for wireless communication, the code comprising instructions executable by a processor to: receiving, from a base station, configuration information for interruption resources including time resources included in a time interval for communication between the controller and one or more associated sensors / actuators (S / As); and processing interrupt information received using the interrupt resource to determine a switching time, in, The switching time is the time for switching from the communication between the controller and the one or more S / As to the communication between the controller and the base station, The interruption information includes priority information associated with information to be sent by the base station, and the priority information indicates a priority for switching from communication between the controller and the one or more S / As to communication between the controller and the base station.
