Environmental communication system conflict resolution
By receiving and configuring parameters to schedule the UE's communication sessions, scheduling conflicts between the UE and the surrounding communication system and network entities in the wireless communication system are resolved, communication efficiency and reliability are improved, and the UE's multi-tasking capabilities are ensured.
Patent Information
- Application Number
- CN202380096197.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-03-27
- Publication Date
- 2025-11-04
AI Technical Summary
In wireless communication systems, scheduling conflicts between user equipment (UE) and environmental communication systems and network entities can cause communication interference, affecting communication efficiency and reliability.
The UE schedules communication sessions with the environment's communication systems and network entities by receiving and configuring parameters, and sends continuous waves or commands during the session to resolve scheduling conflicts.
It effectively resolves communication conflicts between the UE and the environmental communication system and network entities, improves communication efficiency and reliability, and ensures that the UE can simultaneously participate in RFID tag processing operations and other network communications.
Smart Images

Figure CN120898463A_ABST
Abstract
Description
TECHNICAL FIELD
[0001] Aspects of the disclosure relate generally to wireless communication and to techniques and apparatuses for resolving communication conflicts involving a user equipment, a network entity, and an environmental communication system. BACKGROUND
[0002] Wireless communications systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communications systems can employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple-access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and other similar technologies.
[0003] Despite the tremendous technological advancements in wireless communications systems over the years, challenges remain. For example, complex and dynamic environments can still attenuate or block signals between a wireless transmitter and a wireless receiver. Accordingly, there is a continuing desire to improve the technical performance of wireless communications systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of use of shared communications media, reducing the power used by transmitters and receivers in performing communications, improving the reliability of wireless communications, avoiding redundant transmissions and / or receptions and related processing, improving the coverage area of wireless communications, increasing the number and types of devices that can access a wireless communications system, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communications media that are available for use, and so forth. Thus, there is a need to further improve wireless communications systems to overcome the aforementioned technical challenges and others. SUMMARY
[0004] One aspect provides a method for wireless communications by a user equipment (UE). The method includes receiving a parameter for resolving a scheduling conflict that occurs during communications with an environmental communication system and a network entity; scheduling, in accordance with the parameter, a first session for communications with the environmental communication system and a second session for communications with the network entity; and transmitting one or more of a continuous wave or a command to the environmental communication system during the first session.
[0005] Another aspect provides a method for wireless communications by a network entity. The method includes outputting or configuring a parameter for resolving a scheduling conflict that occurs during communications with a UE; configuring the UE to schedule, in accordance with the parameter, one or more of a first session for communications between the UE and an environmental communication system or a second session for communications between the UE and the network entity; and configuring the UE to transmit one or more of a continuous wave or a command to the environmental communication system during the first session.
[0006] Other aspects provide for an apparatus operable to, configured to, or otherwise adapted to perform any one or more of the preceding methods and / or those described herein with reference to and as illustrated by the accompanying drawings and specification; a non-transitory computer-readable medium comprising computer-executable instructions for causing a processor of an apparatus to perform the preceding methods and / or those described herein with reference to and as illustrated by the accompanying drawings and specification; a computer program product, embodied on a computer-readable storage medium, comprising code for performing the preceding methods and / or those described herein with reference to and as illustrated by the accompanying drawings and specification; and / or an apparatus comprising means for performing the preceding methods and / or those described herein with reference to and as illustrated by the accompanying drawings and specification. By way of example, an apparatus can comprise a processing system, a device having a processing system, or a processing system in cooperation with one or more networks.
[0007] The foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows can be better understood. Additional features and advantages will be described hereinafter. The disclosed concepts and specific examples can be readily utilized as bases for modifying or designing other for carrying the same purposes thereof. Such equivalent constructions not only follow from the scope of the claims but are intended to be encompassed thereby. The characteristics of the concepts disclosed herein both their organization and method of operation together with associated advantages will be better understood from the following description when considered in connection with the accompanying drawings. Each of the figures is provided for the purpose of illustration and description and is not intended as a definition of the limits of the claims.
[0008] While aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects can be implemented in many different arrangements and scenarios. Techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence devices). Aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating described aspects and features can include additional components and features for implementation and practice of claimed and described aspects. For example, transmission and reception of wireless signals can include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is intended that aspects described herein can be practiced in a wide variety of devices, components, systems, distributed arrangements, and / or end-user devices of varying sizes, shapes, and constitution. BRIEF DESCRIPTION OF DRAWINGS
[0009] To more fully understand the aspects of the present disclosure, a more
[0010] Figure 1 An example of a wireless communication network in accordance with the present disclosure is depicted.
[0011] Figure 2 Aspects of an example base station and user equipment (UE) in accordance with the present disclosure are depicted.
[0012] Figure 3 An example disaggregated base station architecture is depicted.
[0013] Figure 4A , Figure 4B , Figure 4C and Figure 4D Aspects of data structures for a wireless communication network, such as the wireless communication network of Figure 1 are depicted in accordance with the present disclosure.
[0014] Figure 5 A diagram illustrating an example of backscatter communication in accordance with the present disclosure is depicted.
[0015] Figure 6 FIG. 1 is a diagram illustrating an example of signals transmitted during backscatter communication between a radio frequency identifier (RFID) reader and an environmental Internet of Things (IoT) device, in accordance with the present disclosure.
[0016] Figures 7A to 7B FIG. 2 is a diagram illustrating an example associated with resolving scheduling conflicts between a UE and an environmental communication system and a BS, in accordance with the present disclosure.
[0017] Figure 8 FIG. 3 is a diagram illustrating an example associated with resolving scheduling conflicts between a UE and an environmental communication system and a network entity via a minimum time interval, in accordance with the present disclosure.
[0018] Figures 9A to 9D FIG. 4 is a diagram illustrating an example associated with resolving conflicts between tag processing and downlink or uplink communication via a deferral procedure, in accordance with the present disclosure.
[0019] Figure 10 FIG. 5 is a diagram illustrating an example associated with transmission of a continuous wave during downlink communication, in accordance with the present disclosure.
[0020] Figure 11 FIG. 6 is a diagram illustrating an example of scheduling downlink control information for multiple cells, in accordance with the present disclosure.
[0021] Figure 12 A method for wireless communication by a UE, in accordance with the present disclosure, is shown.
[0022] Figure 13 A method for wireless communication by a network entity, in accordance with the present disclosure, is shown.
[0023] Figure 14 FIG. 7 is a diagram illustrating an example of an implementation of code and circuitry for a communication device, in accordance with the present disclosure.
[0024] Figure 15 FIG. 8 is a diagram illustrating an example of an implementation of code and circuitry for a communication device, in accordance with the present disclosure. DETAILED DESCRIPTION
[0025] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer readable media for resolving communication conflicts between a user equipment (UE) and an environmental communication system (also referred to as an environmental Internet of Things (IoT) device), such as a passive radio frequency identification (RFID) tag, and a network entity.
[0026] Communications between a UE and an environmental communication system can occur at unexpected times. Processing of communications with the environmental communication system can interfere with other network communications involving the UE. Without a way to resolve communication conflicts and / or prioritize communications with the environmental communication system and other network communications, the UE can miss messages sent by the environmental communication system, network entities, other UEs, or other network components.
[0027] As described herein, one way to resolve such conflicts is to configure the UE with rules that handle communications between the UE and the environmental communication system, particularly when those communications can conflict with communications between the UE and a network entity. With a configuration that allows the UE to resolve these communication conflicts, the UE can participate in RFID tag processing operations while continuing to maintain communications with, for example, a network entity or another UE.
[0028] Various aspects of the disclosure are more fully described below with reference to the figures. However, the disclosure can be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout this disclosure. Rather, these aspects are provided as illustrative examples so that the disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. The scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to encompass other apparatuses or methods having other structures, functionalities, or structures and functionalities in addition to or different from those explicitly presented throughout this disclosure. It should be understood that any aspect of the disclosure disclosed herein can be embodied by one or more elements of a claim.
[0029] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms, among other examples (collectively referred to as “elements”). These elements can be implemented using hardware, software, or combinations thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.
[0030] While aspects can be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and / or a RAT subsequent to 5G (e.g., 6G).
[0031] Figure 1An example of a wireless communication network 100 according to the present disclosure is depicted.
[0032] Generally, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is generally a communication device and / or a communication function performed by a communication device (e.g., a UE, a base station (BS), a component of a BS, a server, etc.). For example, various functions of a network and various devices associated with and interacting with a network can be considered network entities. Further, the wireless communication network 100 includes ground-based aspects, such as ground-based network entities (e.g., BSs 110), and non-ground-based aspects, such as satellites 140 and aircraft 145, which can include onboard network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., ground-based BSs) and UEs.
[0033] In the depicted example, the wireless communication network 100 includes BSs 110, UEs 120, and one or more core networks, such as an Evolved Packet Core (EPC) 160 and a 5G Core (5GC) 190, which interoperate to provide communication services via various communication links, including wired and wireless links.
[0034] Figure 1 Various example UEs 120 can include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system (GPS), a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an always-on (AON) device, an edge processing device, or another similar device. A UE 120 can also be referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a remote unit, a remote device, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, or a handset, among other possibilities.
[0035] The BS 110 can wirelessly communicate with the UE 120 via communication link 170 (e.g., transmit signals to or receive signals from the UE). The communication link 170 between the BS 110 and the UE 120 can carry uplink (UL) (also referred to as reverse link) transmissions from the UE 120 to the BS 110 and / or downlink (DL) (also referred to as forward link) transmissions from the BS 110 to the UE 120. In various aspects, the communication link 170 can utilize multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.
[0036] The BSs 110 can include, for example, a NodeB, an enhanced NodeB (eNB), a next-generation enhanced NodeB (ng-eNB), a next-generation NodeB (gNB or gNode B), an access point, a transceiver base station, a radio base station, a radio transceiver, a transceiver function, a transmit receive point (TRP), etc. The BSs 110 can provide communication coverage for respective geographic coverage areas 112, which can be referred to as a cell, and which can overlap in some scenarios (e.g., small cells provided by BS 110a can have coverage areas 112' that overlap with a coverage area 112 of a macro cell). For example, a BS 110 can be a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (covering a relatively small geographic area, such as a home), and / or other types of cells.
[0037] While the BS 110 is depicted as a single, self-contained unit in various aspects, the BS 110 can be implemented in various configurations. For example, one or more components of the base station can be split into central units (CUs), one or more distributed units (DUs), one or more radio units (RUs), near real-time (near-RT) RAN intelligent controllers (RICs), or non-RT RICs, to name a few examples. In another example, various aspects of the base station can be virtualized. More generally, a BS (e.g., the BS 110) can include components located at a single physical location or components located at various physical locations. In examples where the BS includes components located at various physical locations, the various components can each perform various functions such that the various components collectively implement similar functionality as a BS located at a single physical location. In some aspects, a BS that includes components located at various physical locations can be referred to as having a disaggregated radio access network architecture, such as an Open RAN (O-RAN) architecture or a virtualized RAN (VRAN) architecture. Figure 3 An example disaggregated BS architecture is depicted and described.
[0038] Different BSs 110 within the wireless communication network 100 can also be configured to support different radio access technologies, such as 3G, 4G, and / or 5G, among others. For example, BSs 110 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with the EPC 160 through first backhaul links 132 (e.g., S I interface). BSs 110 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) can interface with the 5GC 190 through second backhaul links 184. The BSs 110 can communicate with one another directly or indirectly (e.g., through the EPC 160 or 5GC 190) through third backhaul links 134 (e.g., X2 interface), which can be wired or wireless.
[0039] The wireless communication network 100 can subdivide the electromagnetic spectrum into various classes, bands, channels, or other characteristics. In some aspects, the subdivision is based on wavelength and frequency, where frequency can also be referred to as a carrier, subcarrier, frequency channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) to include 410-7125 MHz, which is often (interchangeably) referred to as “sub-6 GHz.” Similarly, 3GPP currently defines frequency range 2 (FR2) to include 24,250-52,600 MHz, which is sometimes (interchangeably) referred to as “millimeter wave” (“mmW” or “mmWave”). Base stations configured to communicate using mmWave or near-mmWave radio frequencies (e.g., mmWave base stations such as BS 110b) can utilize beamforming (e.g., as illustrated by 182) with UEs (e.g., 120) to improve path loss and range.
[0040] The communication links 170 between the BSs 110 and, for example, the UEs 120 can be through one or more carriers, which can be portions of frequency bands that are scheduled, allocated, or used (e.g., by a scheduler, such as a scheduler in a base station) for a communication link. The carriers can be on different frequencies and / or different frequency bands. A single flat frequency band can be split into multiple carriers for different services, different technologies, or different bandwidths. The frequency spectrum for each carrier can be divided into multiple channels, where each channel is a resource for a communication link at a specific frequency or range of frequencies. For example, a channel can be a resource for a communication link between a transmitter and a receiver, where the transmitter and receiver schedule and communicate on the resource. In some aspects, a BS can communicate with a UE using multiple carriers, where each carrier can be on a different frequency, be in a different frequency band, or be associated with a different service. Carrier can also pertain to a portion of a frequency spectrum that is scheduled, allocated, or used by a scheduler, where the frequency spectrum can be partitioned into multiple carriers.
[0041] Communication using higher frequency bands can have higher path loss and a shorter range than lower frequency communication. Accordingly, certain base stations (e.g., macro BSs 110) can operate in a lower frequency band (e.g., 1-3.8 GHz), while smaller BSs 110 (e.g., a small cell, a femto cell, a home BS, a pico BS, and / or the like) can operate in a higher frequency band (e.g., 24.25-52.6 GHz). Figure 1The base stations 110b in the communications cells 184 can utilize beamforming with the UEs 120 to improve the path loss and range, as shown at 182. For example, the BSs 110b and UEs 120 can each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming. In some cases, the BSs 110b can transmit beamformed signals to the UEs 120 in one or more transmit directions 182'. The UEs 120 can receive the beamformed signals from the BSs 110b in one or more receive directions 182". The UEs 120 can also transmit beamformed signals to the BSs 110b in one or more transmit directions 182". The BSs 110b can also receive beamformed signals from the UEs 120 in one or more receive directions 182'. The BSs 110b and UEs 120 can then perform beam training to determine the best receive and transmit directions for each of the BSs 110b and UEs 120. Notably, the transmit and receive directions of the BSs 110b can or can not be the same. Similarly, the transmit and receive directions of the UEs 120 can or can not be the same.
[0042] The wireless communications network 100 also includes a Wi-Fi AP 150 in communication with Wi-Fi stations (STAs) 152 via communication links 154, e.g., in 2.4 GHz and / or 5 GHz unlicensed spectrum.
[0043] Certain UEs 120 can communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 can use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).
[0044] The EPC 160 can include various functionality, including a mobility management entity (MME) 161, other MMEs 162, a serving gateway 163, a multimedia broadcast multicast service (MBMS) gateway 164, a broadcast multicast service center (BM-SC) 165, and / or a packet data network (PDN) gateway 166, such as in the depicted example. The MME 161 can be in communication with a home subscriber server (HSS) 167. The MME 161 is the control node that processes the signaling between the UEs 120 and the EPC 160. Generally, the MME 161 provides bearer and connection management.
[0045] Generally, user Internet Protocol (IP) packets are conveyed through the serving gateway 163, which is connected to the PDN gateway 166. The PDN gateway 166 provides UE IP address allocation as well as other functions. The PDN gateway 166 and the BM-SC 165 are connected to the IP services 168, which can include, for example, the Internet, an intranet, an IP multimedia subsystem (IMS), a packet switched (PS) streaming service, and / or other IP services.
[0046] The BM-SC 165 can provide functions for MBMS user service provisioning and delivery. The BM-SC 165 can serve as an entry point for content provider MBMS transmission, can be used to authorize and initiate MBMS Bearer Services within a public land mobile network (PLMN), and / or can be used to schedule MBMS transmissions. The MBMS Gateway 164 can distribute MBMS traffic to the BSs 110 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service, and / or can be responsible for session management (start / stop) and for collecting eMBMS related charging information.
[0047] The 5GC 190 can include various function components including an Access and Mobility Management Function (AMF) 191, other AMFs 192, a Session Management Function (SMF) 193, and a User Plane Function (UPF) 194. The AMF 191 can be in communication with a Unified Data Management (UDM) 195.
[0048] The AMF 191 is the control node that processes the signaling between the UEs 120 and the 5GC 190. The AMF 191 provides, for example, Quality of Service (QoS) flow and session management.
[0049] IP packets are conveyed through the UPF 194, which connects to the IP Services 196 and provides UE IP address allocation as well as other functions for the 5GC 190. The IP Services 196 can include, for example, the Internet, an intranet, an IMS, a PS streaming service, and / or other IP services.
[0050] In various aspects, a network entity or network node can be implemented as an aggregated base station, disaggregated base station, component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a transmission reception point (TRP), or a combination thereof, to name a few examples.
[0051] As indicated above, Figure 1 are provided as examples. Other examples can differ from what is described with respect to the Figure 1 examples described.
[0052] Figure 2 Aspects of example BSs 110 and UEs 120 according to this disclosure are depicted.
[0053] Generally, the BS 110 includes various processors (e.g., 220, 230, 238, and 240), antennas 234a-234t, collectively 234, transceivers 232a-232t, collectively 232, including modulators and demodulators, and other aspects that implement wireless transmission of data (e.g., data source 212) and wireless reception of data (e.g., data sink 239). For example, the BS 110 can transmit and receive data between the BS 110 and the UE 120. The BS 110 includes a controller / processor 240 that can be configured to implement various functions described herein related to wireless communication.
[0054] Generally, the UE 120 includes various processors (e.g., 258, 264, 266, and 280), antennas 252a-252r, collectively 252, transceivers 254a-254r, collectively 254, including modulators and demodulators, and other aspects that implement wireless transmission of data (e.g., retrieved from data source 262) and wireless reception of data (e.g., provided to data sink 260). The UE 120 includes a controller / processor 280 that can be configured to implement various functions described herein related to wireless communication.
[0055] For an example downlink transmission, the BS 110 includes a transmit processor 220 that can receive data from a data source 212 and control information from a controller / processor 240. The control information can be for the physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid automatic repeat request (HARQ) indicator channel (PHICH), physical downlink control channel (PDCCH), group common PDCCH (GC PDCCH), and / or other channel. In some examples, the data can be for the physical downlink shared channel (PDSCH).
[0056] The transmit processor 220 can process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 220 can also generate reference symbols, such as for the primary synchronization signal (PSS), secondary synchronization signal (SSS), PBCH demodulation reference signal (DMRS), or channel state information reference signal (CSI-RS).
[0057] A transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., precoding) on data symbols, control symbols, and / or reference symbols, if applicable, and can provide output symbol streams to the modulators (MODs) in transceivers 232a-232t. Each modulator in transceivers 232a-232t can process a respective output symbol stream to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. Downlink signals from the modulators in transceivers 232a-232t can be transmitted via the antennas 234a-234t, respectively.
[0058] The UE 120 includes antennas 252a-252r, which can receive downlink signals from the BS 110 and can provide received signals to the demodulators (DEMODs) in transceivers 254a-254r, respectively. Each demodulator in transceivers 254a-254r can condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.
[0059] A MIMO detector 256 can obtain received symbols from all the demodulators in transceivers 254a-254r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 258 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, providing decoded data for the UE 120 to a data sink 260, and provide decoded control information to a controller / processor 280.
[0060] For example uplink transmission, the UE 120 also includes a transmit processor 264, which can receive and process data (e.g., for the physical uplink shared channel (PUSCH)) from a data source 262 and control information (e.g., for the physical uplink control channel (PUCCH)) from the controller / processor 280. The transmit processor 264 can also generate reference symbols for a reference signal (e.g., for the sounding reference signal (SRS)). The symbols from the transmit processor 264 can be precoded by a TX MIMO processor 266 if applicable, further processed by the modulators in transceivers 254a-254r (e.g., for SC-FDM), and transmitted to the BS 110.
[0061] At the BS 110, the uplink signals from the UEs 120 can be received by antennas 234a-234t, processed by demodulators in transceivers 232a-232t, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information transmitted by the UEs 120. The receive processor 238 can provide the decoded data to a data sink 239 and to the controller / processor 240 for the decoded control information. The memory 242 and the memory 282 can store data and program codes (e.g., processor- executable instructions, computer-executable instructions) for the BS 110 and the UE 120, respectively. A scheduler 244 can schedule UEs for data transmission on the downlink and / or uplink.
[0062] In various aspects, the BS 110 can be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms of outputting data, such as from the data source 212, the scheduler 244, the memory 242, the transmit processor 220, the controller / processor 240, the TX MIMO processor 230, the transceivers 232a-232t, the antennas 234a-234t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms of obtaining data, such as from the antennas 234a-234t, the transceivers 232a-232t, the RX MIMO detector 236, the controller / processor 240, the receive processor 238, the scheduler 244, the memory 242, a network interface, and / or other aspects described herein.
[0063] In various aspects, the UE 120 can likewise be described as transmitting and receiving various types of data associated with the methods described herein. In these contexts, “transmitting” can refer to various mechanisms of outputting data, such as from the data source 262, the memory 282, the transmit processor 264, the controller / processor 280, the TX MIMO processor 266, the transceivers 254a-254t, the antennas 252a-252t, and / or other aspects described herein. Similarly, “receiving” can refer to various mechanisms of obtaining data, such as from the antennas 252a-252t, the transceivers 254a-254t, the RX MIMO detector 256, the controller / processor 280, the receive processor 258, the memory 282, and / or other aspects described herein.
[0064] In some aspects, a processor can be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.
[0065] Although Figure 2 The blocks in FIG. 16 are illustrated as distinct components, but the functionality described above with respect to these blocks can be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 can be performed by controller / processor 280 or under the control of the controller / processor.
[0066] As indicated above, Figure 2 are provided as examples. Other examples can differ from what is described with respect to the examples described herein. Figure 2 described with respect to the examples described herein.
[0067] Deployment of communication systems, such as 5G NR systems, can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, network entity, mobility element of a network, RAN node, core network node, network element, base station, or network equipment can be implemented in an aggregated architecture or a disaggregated architecture. For example, a base station, such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP, or a cell, or one or more units (or one or more components) performing base station functions, can be implemented as an aggregated base station (also referred to as a standalone base station or a monolithic base station) or a disaggregated base station. A “network entity” or “network node” can refer to a disaggregated base station or one or more units of a disaggregated base station, such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof.
[0068] An aggregated base station (e.g., an aggregated network node) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A disaggregated base station (e.g., a disaggregated network node) can be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more CUs, one or more DUs, or one or more RUs. In some examples, a CU can be implemented within a network node, and one or more DUs can be co-located with the CU or, alternatively, can be geographically or virtually spread out over one or more other network nodes. The DUs can be implemented to communicate with one or more RUs. Each of the CUs, DUs, and RUs can also be implemented as virtual units, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples.
[0069] Base station type operations or network designs can take into account the aggregate nature of base station functionality. For example, disaggregated base stations can be utilized in an IAB network, an open radio access network (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also referred to as a cloud radio access network (C-RAN)) to facilitate scaling of a communication system by separating base station functionality into one or more units that can be deployed individually. A disaggregated base station can include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which can enable flexibility in network design. Various units of a disaggregated base station can be configured for wired or wireless communication with at least one other unit of the disaggregated base station.
[0070] Figure 3 An example disaggregated base station 300 architecture is depicted. The disaggregated base station 300 architecture can include one or more central units (CUs) 310 that can communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CUs 310 can communicate with one or more distributed units (DUs) 330 via respective fronthaul links, such as Fl interfaces. The DUs 330 can communicate with one or more radio units (RUs) 340 via respective front-haul links. The RUs 340 can communicate with respective UEs 120 via one or more radio frequency (RF) access links. In some implementations, a UE 120 can be simultaneously served by multiple RUs 340.
[0071] Each of the units (e.g., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) can include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. The associated processor or controller of each unit or the communication interface providing instructions to the unit can be configured to communicate with one or more of the other units via the transmission media. For example, the units can include wired interfaces configured to receive or transmit signals to one or more of the other units over a wired transmission medium. Additionally or alternatively, the units can include wireless interfaces, which can include receivers, transmitters, or transceivers (such as RF transceivers), configured to receive or transmit signals to one or more of the other units over a wireless transmission medium, or both.
[0072] In some aspects, the CU 310 can host one or more higher layer control functions. Such control functions can include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function can utilize an interface configured to communicate signals with other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bi-directionally with the CU-CP units via an interface, such as an El interface. As needed, the CU 310 can be implemented to communicate with the DU 330 for network control and signaling.
[0073] The DU 330 can correspond to a logical unit that includes one or more base station functions for controlling operation of one or more RUs 340. In some aspects, the DU 330 can host, at least in part depending on a functional split, such as a functional split defined by the 3rd Generation Partnership Project (3GPP), one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers, such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 can further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.
[0074] Lower layer functionality can be implemented by one or more RUs 340. In some deployments, an RU 340 controlled by the DU 330 can correspond to a logical node that hosts RF processing functions or low PHY layer functions, such as performing fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, or physical random access channel (PRACH) extraction and filtering, etc., or both, based at least in part on a functional split, such as a lower layer functional split. In such an architecture, the RU 340 can be implemented to handle over-the-air (OTA) communications with one or more UEs 120. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration can enable the DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
[0075] The SMO framework 305 can be configured to support RAN deployment and orchestration of non-virtualized network elements and virtualized network elements. For non- virtualized network elements, the SMO framework 305 can be configured to support deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface, such as an Ol interface. For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform, such as Open Cloud (O-Cloud) 390, to perform network element lifecycle management, such as to instantiate virtualized network elements, via a cloud computing platform interface, such as an 02 interface. Such virtualized network elements can include, but are not limited to, CUs 310, DUs 330, RUs 340, and near-RT RICs 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of a 4G RAN, such as Open eNB (O-eNB) 311, via an Ol interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via an Ol interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support functionality of the SMO framework 305.
[0076] The non-RT RIC 315 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updates, or policy-based direction of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to, or in communication with, the near-RT RIC 325, such as via an Al interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources through interfaces, such as via an E2 interface, that connect one or more CUs 310, one or more DUs 330, or both, and an O-eNB with the near-RT RIC 325 via data collection and actions.
[0077] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 can receive parameters or external enrichment information from an external server. Such information can be utilized by the near-RT RIC 325 and can be received at the SMO framework 305 or the non-RT RIC 315 from non-network data sources or from network functions. In some examples, the non-RT RIC 315 or the near-RT RIC 325 can be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 can monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305, such as via reconfiguration of Ol, or via creation of RAN management policies, such as Al policies.
[0078] As indicated above, Figure 3 are provided as examples. Other examples can differ from what is described Figure 3 with respect to the examples described.
[0079] Figure 4A , Figure 4B , Figure 4C and Figure 4D depict aspects of data structures for a wireless communication network, such as the wireless communication network 100, in accordance with the present disclosure. Figure 1 is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., a 5G NR) frame structure, Figure 4A is a diagram 430 illustrating an example of DL channels within a 5G subframe, Figure 4B is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4C is a diagram 480 illustrating an example of UL channels within a 5G subframe. Figure 4D
[0080] A wireless communication system can utilize orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) on the uplink and downlink. Such a system can also support half-duplex Figure 4B and Figure 4D operation using time division duplex (TDD). OFDM and single-carrier frequency division multiplexing (SC-FDM) partition the (e.g., system) bandwidth into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted on the frequency domain with OFDM and / or on the time domain with SC-FDM.
[0081] A wireless communication frame structure can be frequency division duplex (FDD) in which a set of particular subcarriers are dedicated for either DL or UL within that set of subcarriers. A wireless communication frame structure can also be time division duplex (TDD) in which a set of particular subcarriers are dedicated for both DL and UL within that set of subcarriers.
[0082] In Figure 4A and Figure 4C , the wireless communication frame structure is TDD, where D is DL, U is UL, and F is flexibly used between DL / UL. A UE can be configured with a slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by RRC signaling) through a received slot format indicator (SFI). In the depicted example, a 10 ms frame is divided into 10 equal-sized 1 ms subframes. Each subframe can include one or more slots. In some examples, each slot can include 7 or 14 symbols, depending on the slot format. A subframe can also include mini-slots, which generally have fewer symbols than a whole slot. Other wireless communication technologies can have different frame structures and / or different channels.
[0083] In certain aspects, the number of slots within a subframe is based on a slot configuration and a numerology. For example, for slot configuration 0, different numerologies (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 slots per subframe, respectively. For slot configuration 1, different numerologies 0 to 2 allow for 2, 4, and 8 slots per subframe, respectively. Accordingly, for slot configuration 0 and numerology μ, there are 14 symbols per slot and 2 µ slots per subframe. The subcarrier spacing and symbol length / duration are a function of the numerology. The subcarrier spacing can equal 2 μ x 15 kHz, where μ is a numerology index, which can be selected from values 0 to 5. Thus, the subcarrier spacing for numerology μ = 0 is 15 kHz, and the subcarrier spacing for numerology μ = 5 is 480 kHz. Other numerologies and subcarrier spacings can be used. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D An example is provided with slot configuration 0 having 14 symbols per slot and numerology μ = 2 having 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.
[0084] As Figure 4A 、 Figure 4B 、 Figure 4C and Figure 4D depicted, a resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as a physical RB (PRB)) that extends, for example, 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
[0085] As Figure 4ASome of the REs carry reference (pilot) signals (RS) for the UE (e.g., UE 120). An RS can include demodulation RS (DM-RS) and / or channel state information RS (CSI-RS) for channel estimation at the UE. The RS can also include beam measurement RS (BRS), beam refinement RS (BRRS), and / or phase tracking RS (PT-RS).
[0086] Figure 4B An example of various DL channels is illustrated. The physical downlink control channel (PDCCH) carries DCI within one or multiple control channel elements (CCEs), each CCE including, for example, nine RE groups (REGs), each REG including, for example, four consecutive REs in an OFDM symbol.
[0087] A primary synchronization signal (PSS) can be within symbol 2 of particular subframes of a frame. The PSS is used by a UE (e.g., UE 120) to determine subframe / symbol timing and physical layer identity.
[0088] A secondary synchronization signal (SSS) can be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a physical layer cell identity group number and radio frame timing.
[0089] Based on the physical layer identity and the physical layer cell identity group number, the UE can determine a physical cell identifier (PCI). Based on the PCI, the UE can determine the locations of the aforementioned DM-RS. The physical broadcast channel (PBCH), which carries a master information block (MIB), can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (SSB). The MIB provides system bandwidth configuration information and a scheduling of remaining minimum system information (RMSI). The physical downlink shared channel (PDSCH) carries RMSI, system information block type 2 (SIB2), and other system information (SI). The PDSCH also carries user data.
[0090] As Figure 4CSome of the REs carry DMRS (indicated as R for one particular configuration, but other DMRS configurations are possible) for channel estimation at the base station. The UE can transmit DMRS for PUCCH and DMRS for PUSCH. The PUSCH DMRS can be transmitted, for example, in the first or first two symbols of the PUSCH. The PUCCH DMRS can be transmitted in different configurations depending on whether a short PUCCH or long PUCCH is transmitted and depending on the particular PUCCH format used. The UE 120 can transmit sounding reference signals (SRS). The SRS can be transmitted, for example, in the last symbol of a subframe. The SRS can have a comb structure, and a UE can transmit SRS on one of the combs. The SRS can be used by a base station for channel quality estimation to enable frequency-dependent scheduling for the UL.
[0091] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH can be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data, and can additionally be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.
[0092] Figure 5 is a diagram illustrating an example 500 of backscatter communication according to the present disclosure. In the example 500, the backscatter communication is between an RFID reader 505 and an ambient communication system, which is shown as an ambient Internet of Things (IoT) device 510, such as an RFID tag, and is sometimes also referred to as a “passive tag.” The RFID reader 505 can be a UE 120. The ambient communication system can be a batteryless system that uses ambient radio frequency signals to communicate.
[0093] The RFID reader 505 can transmit, and the ambient IoT device 510 can receive, a continuous wave (CW) that charges the ambient IoT device 510. The CW can be a radio frequency signal. The RFID reader 505 can transmit the CW when the RFID reader 505 is in the vicinity of the ambient IoT device 510. The RFID reader 505 can transmit the CW for a period of time sufficient to charge the ambient IoT device 510. For example, the RFID reader 505 can transmit the CW for a period of time on the order of 400 microseconds to 1500 microseconds. The RFID reader 505 can transmit a command (shown in Figure 5 as a packet transmitted via a modulated wave) after the period of time has elapsed.
[0094] The environmental IoT device 510 can receive the CW and store energy from the CW in a power source, such as a capacitor. When the CW provides enough energy to the power source to communicate with the RFID reader 505, the environmental IoT device 510 can receive the command and transmit a response (at Figure 5 is shown as a packet transmitted as a modulated wave).
[0095] The RFID reader 505 can be configured for full-duplex or half-duplex communication with the environmental IoT device 510. During full-duplex communication, the RFID reader 505 can transmit the CW and / or the command while the environmental IoT device 510 transmits the response. During half-duplex communication, the RFID reader 505 can briefly stop transmitting the CW and / or the command while the environmental IoT device 510 transmits the response. In implementations involving half-duplex communication, another network device, such as another UE 120 or BS 110, can transmit the CW to the environmental IoT device 510 while the environmental IoT device 510 communicates the response. Alternatively, another network device can transmit the CW to the environmental IoT device 510 instead of the RFID reader 505 transmitting the CW to the environmental IoT device 510.
[0096] As indicated above, Figure 5 is provided as an example. Other examples can differ from what is described with Figure 5 respect to the examples described in this regard.
[0097] Figure 6 is a diagram illustrating an example 600 of signals transmitted during backscatter communication between the RFID reader 505 and the environmental IoT device 510 in accordance with the present disclosure.
[0098] As shown in example 600, the RFID reader 505 transmits a CW to the environmental IoT device 510 for a power-up duration, which can be an amount of time sufficient to charge the environmental IoT device 510 to at least a turn-on voltage. The power-up duration can be on the order of at least 400 microseconds.
[0099] After the power-up duration has elapsed, the RFID reader 505 can transmit a command to the environmental IoT device 510. As discussed above, the command can be transmitted via a modulated signal. After communicating the command, the RFID reader 505 can transmit a CW to keep the environmental IoT device 510 charged (e.g., at a voltage level above the turn-on voltage). Alternatively, a different network device, such as a UE 120 or BS 110, can transmit the CW instead of the RFID reader 505, such as when the RFID reader 505 is configured for half-duplex communication.
[0100] After receiving the command, the environmental IoT device 510 can send a response. As discussed above, the response can be sent to the RFID reader 505 via the modulated signal. The RFID reader 505 can receive the response and stop transmitting the CW.
[0101] In some implementations, the RFID reader 505 can be configured to periodically retransmit the command until a response is received. Doing so can increase the likelihood that the command will be received, especially in cases where the CW did not sufficiently charge the environmental IoT device 510 to receive one or more previous transmissions of the command. In some implementations, the RFID reader 505 can send a final command to the environmental IoT device 510 confirming receipt of the response. After the RFID reader 505 has received the response, the RFID reader 505 (or another network device) can stop transmitting the CW, which can cause the voltage of the environmental IoT device 510 to drop below the turn-on voltage.
[0102] In some instances, the UE 120 (acting as the RFID reader 505) can receive the reflected signal through a backscatter device, such as another UE 120 or a BS 110. For example, when the UE 120 is configured for full-duplex communication, the BS 110 can transmit the CW during a DL slot and the UE 120 can transmit the CW during a UL slot, and the UE 120 can receive the reflected signal from the BS 110 via the environmental IoT device 510. In another example, such as when a first UE 120 (acting as the RFID reader 505) is configured for half-duplex communication, the BS 110 can configure a second UE 120 to transmit the CW during a UL slot. In this example, the first UE 120 can receive the reflected signal of the second UE 120 via the environmental IoT device 510. The UE 120 can use the transmitted and / or reflected signal from the environmental IoT device 510 to determine a response from the environmental IoT device 510.
[0103] As indicated above, Figure 6 are provided as examples. Other examples can differ from what is described with respect to Figure 6 the examples described.
[0104] Communications between the UE 120 and environmental communication systems, such as RFID tags, can span multiple UL, DL, or SL slots, and the amount of time needed to process such communications can increase with the number of environmental communication devices in communication with the UE 120. Thus, processing of communications with environmental communication systems can interfere with other network communications involving the UE 120. Without a way to resolve communication conflicts and / or prioritize communications with environmental communication systems and other network communications, the UE 120 can miss messages transmitted by environmental communication systems, network nodes 110, other UEs 120, or other network components.
[0105] Some techniques and apparatuses described herein enable a UE 120 to receive a parameter for resolving a scheduling conflict occurring during communication with an environmental communication system and a network entity; schedule, in accordance with the parameter, a first session for communication with the environmental communication system and a second session for communication with the network entity; and transmit, to the environmental communication system, one or more of a continuous wave or a command during the first session. Thus, the UE 120 can engage in periodic and / or aperiodic RFID tag processing while continuing to maintain communication with, for example, a BS 110 or another UE 120.
[0106] Some techniques and apparatuses described herein enable a network entity, such as a BS 110, to output or configure a parameter for resolving a scheduling conflict occurring during communication with a UE; configure the UE to schedule, in accordance with the parameter, one or more of a first session for communication between the UE and an environmental communication system or a second session for communication between the UE and the network entity; and configure the UE to transmit, to the environmental communication system, one or more of a continuous wave or a command during the first session. Thus, the BS 110 can configure the UE 120 to perform RFID tag processing operations while continuing to receive DL signals and transmit UL signals between the UE 120 and other network devices.
[0107] In some examples discussed herein, DL and / or UL communications can occur over an over-the-air (Uu) interface. In some examples discussed herein, sidelink (SL) communications can occur over a PC5 / SL interface. In some examples discussed herein, DL, UL, and / or SL communications can occur over different interfaces that allow for communication between, for example, an RFID reader (such as the RFID reader 505) and an environmental IoT device (such as the environmental IoT device 510). Thus, the UE 120, the environmental IoT device 510, and / or a combination thereof, among other examples, can be configured to communicate via a Uu interface, a SL interface, and / or another interface. The BS 110 can be configured to communicate with the UE 120 via a Uu interface and configure one or more UEs 120 and / or environmental IoT devices for communication via a Uu interface or a PC5 interface (or another SL interface), among other examples.
[0108] Figures 7A to 7B FIGS. 700A-700B are diagrams illustrating examples 700A-700B associated with resolving scheduling conflicts between a UE 120 and an environmental communication system (such as the environmental IoT device 510) and a BS 110, in accordance with the present disclosure. For example, a scheduling conflict can occur if the UE 120 attempts to communicate with the environmental IoT device 510 (hereinafter referred to as “environmental IoT device processing”) during a time slot allocated for DL, UL, or SL communication.
[0109] With respect to periodic tag processing, the BS 110 can configure two or more devices, such as two or more UEs 120, or at least one UE 120 and at least one BS 110, among other examples, to jointly and periodically process communications with the environmental communication system. In some aspects, the configuration can include dynamic DL, UL, or SL resource grants.
[0110] As shown in example 700A, the UE 120 can be configured to prioritize tag processing (i.e., the “first session”) over certain DL and / or UL communications (i.e., the “second session”), but not over other communications. For example, the UE 120 can be configured to prioritize tag processing over DL communications, such as serving cell dynamic PDSCH communications and CSI-RS signaling, but not, for example, PDCCH communications. With respect to the periodic processing session and the semi-periodic DL grant, in some aspects, the UE 120 can be configured to prioritize serving cell non-dynamic DL channels and / or signals over tag processing. In some aspects, such as when the UE 120 measures an RFID tag signal during an UL slot, the UE 120 can be configured to prioritize serving cell UL transmissions over tag processing. For example, the UE 120 can be configured to prioritize tag processing over UL communications, such as serving cell dynamic PUSCH communications and SRS signaling, but not, for example, PUCCH communications. Alternatively, with respect to the periodic processing session and the configured UL grant, in some aspects, the UE 120 can be configured to prioritize tag processing over all UL transmissions.
[0111] In some aspects, the UE 120 can be configured to prioritize tag processing when it conflicts with dynamic serving cell DL channels and / or signals. For example, the UE 120 can be configured to semi-statically determine the signals to receive (i.e., semi-statically determine the tag processing resources). In a “semi-static” slot configuration, whether a flexible slot is for DL, UL, or SL communications can be indicated by, for example, a transmission of DCI. Thus, in one example, the tag processing resources can be scheduled during a flexible slot in a semi-static slot configuration. The UE 120 can be further or alternatively configured to receive dynamically scheduled DL communications (such as PDSCH and / or CSI-RS signaling) when the tag processing conflicts with the dynamic serving cell DL channels and / or signals. In a “dynamic” slot configuration, time domain resources can be modified from UL to DL, and vice versa. Thus, in one example, one or more UL slots can be dynamically reassigned to DL slots to accommodate the tag processing resources. With respect to periodic processing sessions and semi-periodic DL grants, in some aspects, the UE 120 can be configured to prioritize serving cell DL channels and / or signals that are not dynamically scheduled or triggered over the tag processing resources. The DL channels or signals that are prioritized over the tag processing can include PDCCH, semi-periodic PDSCH, and / or periodic and semi-periodic CSI-RS, among other examples. Similarly, after receiving the DL serving cell channels and / or signals, N symbols can be reserved to account for the maximum timing difference between the tag processing resources and the serving cell DL channels and / or signals.
[0112] As shown in example 700B, the priority of tag processing relative to DL, UL, or SL communications can be based on layer 1 (LI), layer 2 (L2), or layer 3 (L3) signaling. For DL and UL communications, LI signaling can include scheduled or unscheduled DCI signaling. L2 can include MAC control element (MAC-CE) signaling. L3 can include RRC signaling. For periodic processing sessions and dynamic downlink grants, in some aspects, UE 120 can be configured to switch between prioritizing serving cell dynamic DL communications over tag processing and prioritizing tag processing over dynamic serving cell DL communications based on, for example, L2 or LI indication. For example, the indication can be provided to UE 120 via radio network temporary identifier (RNTI), UE-specific or common search space, or bits in DCI. In some aspects, such as in the context of periodic tag processing and dynamic or semi-periodic DL grants, one or more parameters, such as a priority parameter, a QoS parameter, a latency parameter, and / or a combination thereof, among other examples, can be defined for ambient IoT device 510, and UE 120 can be configured to prioritize tag processing based on one or more of these parameters. In some aspects, UE 120 can be configured to prioritize tag processing over DL communications based at least in part on an adjacent channel leakage ratio (ACLR) level measured by UE 120. In some aspects, UE 120 can be configured to prioritize tag processing over DL communications based at least in part on a type of full duplex (e.g., based on whether UE is configured for half duplex, in-band full duplex (IBFD), and / or sub-band full duplex (SBFD) communications). In some aspects, UE 120 can be configured with a table and / or a function, one or both of which can define how UE 120 prioritizes tag processing relative to DL, UL, or SL communications. In some aspects, the table and / or function can be defined according to LI, L2, and / or L3 signaling.
[0113] In some aspects, such as during SL communication between two UEs 120 or between a UE 120 and a power line communication (PLC) network element via, for example, a PC5 interface, a priority of the SL communication can be based on L1 signaling (such as sidelink control information (SCI) or communication on PSSCH or PSFCH), L2 signaling (such as PC5-MAC-CE), L3 signaling (such as PC5-RRC), and / or a combination thereof, among other examples. In some aspects, the L1, L2, and / or L3 signaling can be used to determine the priority of the SL communication. In some aspects, the L1, L2, and / or L3 signaling can be multiplexed, which can include multiplexing one or more of the L1, L2, and / or L3 signaling with a buffer status report (BFR), a delay status report (DSR) (which can include a packet remaining delay budget or a latency of a transmitted packet), a scheduling request (SR), a HARQ ACK, a channel state information (CSI) report, a sidelink reference signal (SL-RS) transmitted by the UE 120, and / or a power headroom report (PHR), among other examples.
[0114] With respect to periodic tag processing sessions and configured UL grants, in some aspects, UE 120 can be configured to switch between prioritizing serving cell dynamic UL communications over tag processing and prioritizing tag processing over dynamic serving cell UL communications based on, for example, L2 or LI indications. For example, the indications can be provided to UE 120 via RNTI, UE-specific or common search space, or bits in DCI. In some aspects, the indications can be provided to UE 120 via PUSCH or semi-periodic SRS signaling. In aspects where UE 120 can be configured for full-duplex communications, UE 120 can be configured to perform tag processing and transmit UL communications on, for example, SBFD or IBFD time slots or symbols and based at least in part on ACLR as measured at UE 120. In some aspects, such as in the context of periodic tag processing and configured UL grants, one or more parameters can be defined for ambient IoT device 510, such as a priority parameter, a QoS parameter, a latency parameter, and / or combinations thereof, among other examples, and UE 120 can be configured to prioritize tag processing based on one or more of these parameters. In some aspects, UE 120 can be configured with tables and / or functions, one or both of which can define how UE 120 prioritizes tag processing over DL, UL, or SL communications. In some aspects, the tables and / or functions can be defined according to LI, L2, and / or L3 signaling. In some aspects, UE 120 can be configured to switch between prioritizing serving cell dynamic UL communications over tag processing and prioritizing tag processing over dynamic serving cell UL communications based on, for example, LI, L2, or L3 indications. In some aspects, such as in the case of L3 indications, BS 110 can transmit, and UE 120 can receive, the indications via initial access messages, such as master information block (MIB) or system information block (SIB) messages, among other examples.
[0115] In some aspects, UE 120 can be configured to refrain from transmitting certain UL communications, such as PUCCH, PUSCH, and / or SRS communications, on OFDM symbols for which the UE performs tag processing. In some aspects, UE 120 can be configured to refrain from transmitting within X data symbols prior to, for example, OFDM symbols for tag processing. The value of X can be as low as 1 and can be based at least in part on subcarrier spacing (SCS), bandwidth, and / or combinations thereof, among other examples.
[0116] As indicated above, Figures 7A to 7B are provided by way of example. Other examples can differ from those described. Figures 7A to 7B without departing from the spirit and scope of the disclosure.
[0117] Figure 8is a diagram illustrating an example 800 associated with resolving scheduling conflicts between UE 120 and an environmental communication system, such as environmental IoT device 510, and BS 110 via a minimum time interval, in accordance with the present disclosure.
[0118] In some aspects, such as aspects involving periodic processing sessions and dynamic DL grants, UE 120 can be configured with a minimum time interval between a scheduled PDCCH and a next tagged processing resource or scheduled PDSCH or CSI-RS. The minimum time interval can allow UE 120 sufficient time to switch Fast Fourier Transform (FFT) domain window timing between capturing samples of a tagged processing or DL signaling. UE 120 can be configured to drop or postpone a tagged processing occasion that starts before the minimum time interval expires. In example 800, UE 120 can be configured to drop or postpone the tagged processing occasion because it starts within the minimum time interval.
[0119] In some aspects, the tagged processing can overlap with CSI-RS measurements. In such instances, the CSI-RS measurements can be RRC configured, with no dynamic prioritization over the tagged processing. Instead, in this instance, the tagged processing can be prioritized according to a pre-defined configuration or based on L1, L2, or L3 indications. For UE 120, the L1, L2, or L3 indications can include RRC, MAC-CE, uplink control information (UCI), user assistance information, and / or combinations thereof, among other examples. In some aspects, the prioritization can be indicated during a random access control channel (RACH) occasion or via RACH signaling. For BS 110, such as a gNB, the L1, L2, or L3 indications can include scheduled or unscheduled DCI, MAC-CE, RRC, and / or combinations thereof, among other examples. In some aspects, UE 120 can be configured to resolve scheduling conflicts between CSI-RS measurements and tagged processing based at least in part on whether UE is capable of simultaneous processing. For example, if capable, UE 120 can be configured to simultaneously process communications with environmental IoT device 510 and BS 110. In some aspects, UE 120 can be configured for flexible prioritization between tagged processing and CSI-RS measurements. For example, the tagged processing and / or CSI-RS communications can be assigned a priority, and UE 120 can be configured to process the signals according to their assigned priority. In some aspects, UE 120 can be configured to switch between prioritizing CSI-RS measurements over tagged processing and prioritizing tagged processing over CSI-RS measurements based on, for example, L1, L2, or L3 indications. In some aspects, such as in the case of L3 indications, BS 110 can transmit, and UE 120 can receive, an indication via an initial access message, such as a MIB or SIB message, among other examples.
[0120] In some aspects, such as flexible symbols or UL symbols with scheduled, configured, or triggered UL transmissions (e.g., PUCCH, PUSCH, or SRS transmissions) from the UE 120 to the serving BS 110 and scheduled, configured, or triggered tag processing, if the UL transmissions are configured at a higher layer (e.g., L2 or L3) or semi-statically configured (e.g., PUCCH, configured grant UL communications, PUSCH, semi-periodically scheduled SRS, and / or combinations thereof, among other examples), the UE 120 can be configured to transmit the configured UL transmissions to the BS 110 without performing tag processing. Alternatively, the UE 120 can be configured to transmit dynamically scheduled PUSCH and SRS communications without performing tag processing. Alternatively, in aspects where the UE 120 is a full duplex device, the UE 120 can be configured to perform tag processing and transmit UL communications based on a capability (e.g., SBFD or IBFD) and ACLR measured at the UE 120. Alternatively, the UE 120 can be configured to perform periodic tag processing and transmit UL communications according to one or more parameters defined for the environmental IoT device 510, such as a priority parameter, a QoS parameter, a latency parameter, and / or combinations thereof, among other examples, and the UE 120 can be configured to prioritize tag processing based on one or more of the parameters. In some aspects, the UE 120 can be configured with a table and / or a function, one or both of which can define how the UE 120 prioritizes tag processing with respect to DL, UL, or SL communications. In some aspects, the table and / or function can be defined according to L1, L2, and / or L3 signaling. In some aspects, such as where L3 indicates, the BS 110 can transmit, and the UE 120 can receive, the indication via an initial access message, such as a MIB or SIB message, among other examples.
[0121] In some aspects, the example 800 discussed with respect to DL and / or UL communications can further or alternatively apply to SL communications on PSSCH. For example, the UE 120 can be configured with a minimum time interval between a scheduled PSCCH and a next tag processing resource or scheduled PSSCH. The minimum time interval can allow the UE 120 sufficient time to switch a fast Fourier transform (FFT) domain window timing between capturing samples of tag processing or SL signaling. The UE 120 can be configured to drop or postpone a tag processing occasion that starts before the minimum time interval expires. In the example 800, the UE 120 can be configured to drop or postpone the tag processing occasion as it starts within the minimum time interval.
[0122] As indicated above, Figure 8 are provided as examples. Other examples can differ from what is described with respect to Figure 8 the examples described with respect to the examples described with respect to
[0123] Figures 9A to 9D are respective illustrations of examples 900A-900D illustrating an example 900A-900D associated with resolving a conflict between tag processing and a DL, UL, or SL communication via a deferral procedure in accordance with the present disclosure. Each of the examples 900A-900D illustrates an instance where a conflict (“conflict”) occurs due to tag processing and a DL, UL, or SL communication at least partially overlapping, and how the conflict can be resolved (“resolution”) via a deferral procedure. For example, when a conflict occurs, the UE 120 can be configured to split the tag processing into different occasions around the DL, UL, or SL communication (900A), shorten the tag processing occasion (900B), delay the tag processing to after the DL, UL, or SL communication (900C), or delay the DL, UL, or SL communication to after the tag processing (900D) rather than dropping the tag processing or the DL, UL, or SL communication. The deferral procedure can be indicated by a semi-persistent activation DCI received by the UE 120 before the tag processing time, a configured grant activation DCI, a UL / DL dynamic grant DCI, MAC-CE signaling, RRC signaling, and / or a combination thereof, among other examples. If two or more UEs 120 are involved in the tag processing occasion, one UE can signal to another UE via deferral time signaling that the tag processing can be deferred. The deferral time signaling between the UEs 120 can occur via L1, L2, or L3 signaling or via sidelink communication, among other examples.
[0124] As shown in example 900A, the tag processing can be divided into multiple tag processing sessions around the DL, UL, or SL communication, including a first tag processing session and a second tag processing session. For example, as shown in example 900A, the DL, UL, or SL communication can occur between the first tag processing session and the second tag processing session. For example, the DL, UL, or SL communication can be deferred after the first tag processing session ends, and the second tag processing session can be deferred after the DL, UL, or SL communication ends. In some aspects, a first time offset can be configured between the first tag processing session and the DL, UL, or SL communication. In some aspects, a second time offset can be configured between the DL, UL, or SL communication and the second tag processing session. In some aspects, the first time offset and the second time offset can be the same length. The first time offset and the second time offset can each represent a time gap to account for, for example, a switching interface or RF tuning, particularly to a different bandwidth, frequency range, or frequency.
[0125] As shown in example 900B, the tag processing occasion can be shortened to accommodate the DL, UL, or SL communication. For example, the UE 120 can be configured to end the tag processing occasion before the DL, UL, or SL communication is scheduled to begin. In some aspects, a time gap can be configured between the end of the shortened tag processing occasion and the DL, UL, or SL communication.
[0126] Referring to example 900C, the timing of the tag processing occasion can be postponed to occur after the DL, UL, or SL communication has ended. The postponement of the tag processing occasion can be configured, preconfigured, designated, or agreed upon via L1, L2, or L3 communication, or provided in a configured grant DCI. In some aspects, a timing offset can occur between the end of the DL, UL, or SL communication and the beginning of the tag processing occasion.
[0127] Referring to example 900D, the timing of the DL, UL, or SL communication can be postponed to occur after the tag reading occasion has ended. The postponement of the DL, UL, or SL communication can be configured, preconfigured, designated, or agreed upon via L1, L2, or L3 communication, or provided in a configured grant DCI. In some aspects, a timing offset can occur between the end of the tag processing occasion and the beginning of the DL, UL, or SL communication.
[0128] In some aspects, the UE 120 is configured with a default configuration for handling conflicts between tag processing and DL, UL, and / or SL communications. The default configuration can apply one of the configurations shown in examples 900A-900D. Based on a priority or condition, the UE 120 can be configured to apply a different configuration than the default condition to handle a particular conflict occasion. When coordinating tag processing with other network devices, such as the BS 110 or another UE 120, the UE 120 can send an indication to the other network device indicating a change in tag processing behavior. The indication from the UE 120 can be sent before the conflict occurs. The UE 120 can send the indication via, for example, L1, L2, or L3 signaling, or the indication can be multiplexed with L1, L2, or L3 signaling. For an over-the-air (Uu) interface, L1 can include UCI carried on PUCCH or PUSCH, L2 can include a MAC-CE carried on PUSCH, and L3 can include RRC carried on PUSCH, which can include user assistance information (UAI). In some aspects, the UE can multiplex L1, L2, and / or L3 signals (e.g., CG-UCI, HARQ-ACK, SR, CSI report, SRS signal, PHR, BSR, DSR, RACH message, UAI, etc.). In some aspects, the indication can be sent after the conflict occurs and for the duration of using the same indication (e.g., L1, L2, or L3 signaling) and associated resources. The indication from the UE 120 to the network 100 can occur before or after the conflict is resolved.
[0129] For the SL interface, L1 can include SCI carried on a PSCCH communication on the PSSCH or PSFCH, L2 can include a PC5-MAC-CE, and L3 can include a PC5-RRC (which can include user assistance information (UAI)) carried on the PSSCH or PSFCH. In some aspects, UE 120 can multiplex L1, L2, and / or L3 signaling. In some aspects, the indication can be transmitted after a collision occurs and for a duration of time using the same indication (e.g., L1, L2, or L3 signaling) and associated resources. The indication from UE 120 to network 100 can occur before or after the collision is resolved.
[0130] As indicated above, Figures 9A to 9D are provided as examples. Other examples can differ from what is described with respect to Figures 9A to 9D the examples described with respect to the examples described with respect to
[0131] Figure 10 is a diagram illustrating an example 1000 associated with transmission of a CW during UL communication in accordance with the present disclosure. In example 1000, UE 120 can transmit a CW and a UL communication (such as a PUSCH communication) at the same time. Alternatively, UE 120 can transmit a CW while a different UE transmits a UL communication, which can occur, for example, when UE 120 acts as a CW source to another UE acting as an RFID reader 505.
[0132] In some aspects, UE 120 can be configured to transmit a CW during a DL and / or UL slot depending on a capability of UE 120. For example, during a DL slot, if UE 120 is configured for full duplex communication and is under ACLR conditions, UE 120 can be able to transmit and / or receive a DL communication at the same time as transmitting a CW. If UE 120 is not configured for full duplex communication, UE 120 can prioritize and / or perform tag processing over the DL communication, as discussed above.
[0133] In some aspects, such as for transmitting a CW during a UL slot based on a UE 120 capability, and if no RF tuning is needed to perform both the transmission of the CW and the transmission of the UL communication, the UE 120 can be configured to transmit both signals via multiplexing, as long as the UE 120 has sufficient power to transmit both types of signals. The power allocation can be based on a priority associated with each communication. The priority can be based on, for example, whether the communication is associated with L2 (MAC), LI (PHY), or both, QoS, and a delay parameter (e.g., a remaining packet delay budget) associated with each communication. In some aspects, the UE 120 can be configured with a table and / or a function, one or both of which can define how the UE 120 prioritizes the tag handling over the UL communication. In some aspects, the table and / or function can be defined according to LI, L2, and / or L3 signaling. In some aspects, such as in the case of L3 indication, the BS 110 can transmit, and the UE 120 can receive, an indication via an initial access message (such as a MIB or SIB message), among other examples. Thus, the priority can be indicated to prioritize one type of communication over another type of communication (e.g., to prioritize the CW over the UL communication). Alternatively, in some aspects, the priority can be determined based on a PHY priority or an upper layer priority. In some aspects, the priority can be based on physical parameters and / or upper layer parameters, such as a delay, a remaining packet delay budget, a latency of packets in a buffer, an explicit delay, a packet delay budget signaling, and / or combinations thereof, among other examples.
[0134] To perform the tag handling, a given priority of the PHY or upper layer can be based on the importance of the underlying data to be read from one or more environmental IoT devices 510 in performing the tag handling. The performance of the tag handling can be collectively assigned a priority based on the PHY and upper layer priorities, and, for example, a delay requirement or a remaining delay of a command to be communicated to one or more of the environmental IoT devices in the session or data carried by one or more of the environmental IoT devices in the session and to be communicated or backscattered by them.
[0135] In some aspects, Figure 10 Example 1000 can apply to a tag reading occasion that conflicts with a SL communication between, for example, two UEs 120 or a UE 120 and a PLC network element.
[0136] As indicated above, Figure 10 is provided as an example. Other examples can differ from what is described with Figure 10 respect to the examples described in this regard.
[0137] Figure 11 is a diagram illustrating an example 1100 of DCI scheduling multiple cells according to the present disclosure. As Figure 11As shown, BS 110 and UE 120 can communicate with one another (e.g., directly or via one or more network nodes).
[0138] BS 110 can transmit, to UE 120 (e.g., directly or via one or more network nodes), DCI 1105 scheduling multiple communications for UE 120. The multiple communications can be scheduled for at least two different cells. In some cases, a cell can be referred to as a component carrier (CC). In some cases, a DCI scheduling communications for a cell via which the DCI is transmitted can be referred to as a self-carrier (or self-cell) scheduling DCI. In some cases, a DCI scheduling communications for a cell via which the DCI is transmitted can be referred to as a cross-carrier (or cross-cell) scheduling DCI. In some aspects, DCI 1105 can be a cross-carrier scheduling DCI and can or can not be a self-carrier scheduling DCI. In some aspects, DCI 1105 carrying communications in at least two cells can be referred to as a combined DCI.
[0139] In example 1100, DCI 1105 schedules communications for a first cell 1110 (shown as CC0) carrying DCI 1105, schedules communications for a second cell 1115 (shown as CC1) not carrying DCI 1105, and schedules communications for a third cell 1120 (shown as CC2) not carrying DCI 1105. In some aspects, DCI 1105 can schedule communications on a different number of cells (e.g., two cells, four cells, five cells, etc.) than shown in 1100. The number of cells can be greater than or equal to two. Figure 11 In example 1100, DCI 1105 schedules communications for a first cell 1110 (shown as CC0) carrying DCI 1105, schedules communications for a second cell 1115 (shown as CC1) not carrying DCI 1105, and schedules communications for a third cell 1120 (shown as CC2) not carrying DCI 1105. In some aspects, DCI 1105 can schedule communications on a different number of cells (e.g., two cells, four cells, five cells, etc.) than shown in 1100. The number of cells can be greater than or equal to two.
[0140] The communications scheduled by DCI 1105 can include data communications, such as physical downlink shared channel (PDSCH) communications or physical uplink shared channel (PUSCH) communications. For data communications, DCI 1105 can schedule a single transport block (TB) across multiple cells, or can separately schedule multiple TBs in multiple cells. Additionally or alternatively, the communications scheduled by DCI 1105 can include reference signals, such as channel state information reference signals (CSI-RSs) or sounding reference signals (SRSs). For reference signals, DCI 1105 can trigger a single resource for reference signal transmission across multiple cells, or can separately schedule multiple resources for reference signal transmission in multiple cells. In some cases, scheduling information in DCI 1105 can be indicated once and reused for multiple communications (e.g., on different cells), such as a modulation and coding scheme (MCS), resources to use for acknowledgement (ACK) or negative acknowledgement (NACK) of the communications scheduled by DCI 1105, and / or resource allocation for the scheduled communications, to save signaling overhead.
[0141] The concepts discussed above with respect to FIGs. 7 through Figure 10 The concepts discussed can be further applied to instances where a DCI from a different CC configures, triggers, or schedules a DL and / or UL grant. For example, in addition to the DL and / or UL grant, the DCI 1105 for the first cell 1110 can also configure, trigger, or schedule a tag processing. As shown, the DCI 1105 can configure, trigger, or schedule the tag processing to occur during a DL and / or UL communication on the third cell 1120. The UE 120 can be configured to resolve a conflict between the DL and / or UL communication on the third cell 1120 and performing the tag processing, as discussed above with respect to FIGs. 7 through Figure 11 Figure 10
[0142] As indicated above, Figure 11 are provided as examples. Other examples can differ from what is described with respect to Figure 11 the examples described with respect to FIGs. 7 through
[0143] Certain concepts discussed above relate to periodic and / or semi-periodic tag processing sessions. For aperiodic tag processing, prioritization can occur as discussed above with respect to periodic tag processing. Additionally, a DCI triggering a tag processing occasion can identify a priority, QoS, latency parameter, and / or indicate how to resolve a conflict, if any.
[0144] In some aspects, semi-persistent tag processing can be activated by RRC or DCI signaling. When initiating and / or prioritizing semi-persistent tag processing, data and reference signals can also be considered. For example, semi-periodic tag processing can be based on a semi-persistent scheduling (SPS) PDSCH for DL data, a configured grant PUSCH for UL data, a semi-periodic CSI-RS for DL CSI measurement, a semi-periodic SRS for UL CSI measurement, and / or a combination thereof, among other examples.
[0145] In some aspects, periodic tag processing can be enabled during a time period. When initiating and / or prioritizing periodic tag processing, data and reference signals can also be considered. Examples of data or reference signals used to initiate and / or prioritize periodic tag processing can include a type 1 configured grant for UL communication, a periodic CSI-RS, a periodic SRS, a periodic SSB, other periodic reference signals and / or data, and / or a combination thereof, among other examples.
[0146] In some aspects, the aperiodic tag processing can be scheduled or triggered by DCI. In some aspects, the aperiodic tag processing can be configured to occur a predetermined number of times, where the predetermined number of times is indicated by RRC, MAC-CE, or DCI configuration. Data and reference signals can also be considered when initiating and / or prioritizing aperiodic tag processing. Examples of data or reference signals for initiating and / or prioritizing aperiodic tag processing can include aperiodic CSI-RS, aperiodic SRS, dynamic grant for UL data, dynamic grant for DL data, and / or combinations thereof, among other examples.
[0147] Figure 12 A method 1200 for wireless communication by a UE, such as the UE 120, is shown.
[0148] The method 1200 begins, at 1210, by receiving a parameter for resolving a scheduling conflict that occurs during communication with an environmental communication system and a network entity.
[0149] The method 1200 then proceeds to step 1220, where a first session for communication with the environmental communication system and a second session for communication with the network entity are scheduled in accordance with the parameter.
[0150] The method 1200 then proceeds to step 1230, where one or more of a continuous wave or a command is transmitted to the environmental communication system during the first session.
[0151] In one aspect, scheduling the first session and the second session includes scheduling the first session and the second session to occur at different times.
[0152] In one aspect, scheduling the first session and the second session includes scheduling the first session and the second session to partially overlap in time.
[0153] In one aspect, scheduling the first session and the second session includes scheduling the first session to end before the second session begins.
[0154] In one aspect, scheduling the first session and the second session includes scheduling the first session to begin after the second session ends.
[0155] In one aspect, scheduling the first session and the second session includes shortening a configured duration of the first session and scheduling the second session to begin after the first session ends.
[0156] In one aspect, scheduling the first session and the second session includes dividing the first session into a first portion and a second portion, scheduling the first portion to end before the second session begins, and scheduling the second portion to begin after the second session ends.
[0157] In one aspect, the method 1200 further includes receiving a response to the continuous wave or the command from the environmental communication system during the first session.
[0158] In one aspect, scheduling the first session and the second session includes scheduling the first session as a result of an L1 priority indicator, an L2 priority indicator, or an L3 priority indicator.
[0159] In one aspect, the method 1200 further includes detecting the scheduling conflict after receiving the parameter for resolving the scheduling conflict.
[0160] In one aspect, scheduling one or more of the first session or the second session occurs after detecting the scheduling conflict.
[0161] In one aspect, scheduling one or more of the first session or the second session occurs before detecting the scheduling conflict.
[0162] In one aspect, the method 1200 further includes receiving a configuration for full-duplex communication, wherein the parameter is based at least in part on the configuration for full-duplex communication.
[0163] In one aspect, the parameter based at least in part on the configuration for full-duplex communication includes a parameter for simultaneously transmitting the continuous wave or the command and receiving the response to the continuous wave or the command from the environmental communication system.
[0164] In one aspect, the method 1200 further includes receiving a configuration for half-duplex communication, wherein the parameter is based at least in part on the configuration for half-duplex communication.
[0165] In one aspect, the parameter based at least in part on the configuration for half-duplex communication includes a parameter for transmitting the continuous wave or the command and receiving the response to the continuous wave or the command from the environmental communication system at different times.
[0166] In one aspect, the method 1200 further includes receiving a priority indication indicating a priority assigned to one or more of the first session or the second session, wherein scheduling one or more of the first session or the second session includes scheduling one or more of the first session or the second session based at least in part on the priority indication.
[0167] In one aspect, the method 1200 or any aspect related thereto can be performed by an apparatus, such as the communication device 1400 of FIG. 14, that includes various components, which can operate, be configured to operate, or be adapted to operate, to perform the method 1200. The communication device 1400 is described in more detail below. Figure 14
[0168] Note that Figure 12 This is merely one example of a method, and other methods including fewer, additional, or alternative steps are possible in accordance with the present disclosure.
[0169] Figure 13 A method 1300 for wireless communication by a network entity, such as a BS 110, or a disaggregated base station as discussed with respect to FIG. 1 is shown. Figure 3
[0170] The method 1300 begins, at 1310, by outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE.
[0171] The method 1300 then proceeds to step 1320, where the UE is configured to schedule one or more of a first session for communications between the UE and an environmental communication system or a second session for communications between the UE and the network entity in accordance with the parameters.
[0172] The method 1300 then proceeds to step 1330, where the UE is configured to transmit one or more of a continuous wave or a command to the environmental communication system during the first session.
[0173] In one aspect, configuring the UE includes configuring the UE to schedule the first session and the second session to occur at different times.
[0174] In one aspect, configuring the UE includes configuring the UE to schedule the first session and the second session to at least partially overlap in time.
[0175] In one aspect, configuring the UE includes configuring the UE to schedule the first session to end before the second session begins.
[0176] In one aspect, configuring the UE includes configuring the UE to schedule the first session to begin after the second session ends.
[0177] In one aspect, configuring the UE includes configuring the UE to shorten a configured duration of the first session and schedule the second session to begin after the first session ends.
[0178] In one aspect, configuring the UE includes configuring the UE to split the first session into a first portion and a second portion and schedule the first portion to end before the second session begins and schedule the second portion to begin after the second session ends.
[0179] In one aspect, the method 1300 further includes configuring the UE to receive a response to the continuous wave or the command from the environmental communication system during the first session.
[0180] In one aspect, configuring the UE includes configuring the UE to schedule the first session according to the L1 priority indicator, the L2 priority indicator, or the L3 priority indicator.
[0181] In one aspect, the method 1300 further includes outputting or configuring a priority indication indicating a priority assigned to one or more of the first session and the second session, wherein configuring the UE includes configuring the UE to schedule one or more of the first session and the second session based at least in part on the priority indication.
[0182] In one aspect, the parameter is outputted or configured based at least in part on the UE being configured for full-duplex communication.
[0183] In one aspect, the parameter configures the UE to simultaneously transmit a continuous wave or a command and receive a response to the continuous wave or the command from the environmental communication system.
[0184] In one aspect, the parameter is outputted or configured based at least in part on the UE being configured for half-duplex communication.
[0185] In one aspect, the method 1300, or any aspect related thereto, can be performed by an apparatus, such as the Figure 15 communication device 1500 of FIG. 15, that includes various components
[0186] Note that Figure 13 The method of FIG. 13 is just one example of a method, and other methods including fewer, additional, or alternative steps are possible according to the present disclosure.
[0187] Figure 14 is a diagram that illustrates an example of a specific implementation of code and circuitry for a communication device 1400 according to the present disclosure. The communication device 1400 can be a UE, or a UE can include the communication device 1400.
[0188] The communication device 1400 includes a processing system 1402 coupled to a transceiver 1408 (e.g., a transmitter and / or a receiver). The transceiver 1408 is configured to transmit and receive signals for the communication device 1400 via an antenna 1410, such as the various signals as described herein. The processing system 1402 can be configured to perform the processing functions of the communication device 1400, including processing signals received by and / or to be transmitted by the communication device 1400.
[0189] Processing system 1402 includes one or more processors 1420. In various aspects, the one or more processors 1420 may represent one or more of a receive processor 258, a transmit processor 264, a TX MIMO processor 266, and / or a controller / processor 280, as per [reference to...]. Figure 2 As described. One or more processors 1420 are coupled to computer-readable medium / memory 1430 via bus 1406. In various respects, computer-readable medium / memory 1430 may represent memory 282, as described above. Figure 2 As described. In some aspects, the computer-readable medium / memory 1430 is configured to store instructions (e.g., computer-executable code, processor-executable code) that, when executed by one or more processors 1420, cause one or more processors 1420 to perform actions related to... Figure 12 The described method 1200 or any aspect thereof. It should be noted that references to processors performing the functions of communication device 1400 may include one or more processors performing those functions of communication device 1400.
[0190] like Figure 14 As shown, the communication device 1400 may include circuitry (circuit 1435) for receiving parameters for resolving scheduling conflicts that occur during communication with environmental communication systems and network entities.
[0191] like Figure 14 As shown, the communication device 1400 may include code (code 1440) stored in a computer-readable medium / memory 1430 for receiving parameters for resolving scheduling conflicts that occur during communication with environmental communication systems and network entities.
[0192] like Figure 14 As shown, the communication device 1400 may include circuitry (circuit 1445) for scheduling a first session of communication with an environmental communication system and a second session of communication with a network entity based on parameters.
[0193] like Figure 14 As shown, the communication device 1400 may include code (code 1450) stored in a computer-readable medium / memory 1430 for scheduling a first session for communication with an environmental communication system and a second session for communication with a network entity, based on parameters.
[0194] like Figure 14 As shown, the communication device 1400 may include circuitry (circuit 1455) for transmitting one or more of a continuous wave or a command to an environmental communication system during a first session.
[0195] like Figure 14As shown, the communication device 1400 can include code (code 1460) stored in the computer-readable medium / memory 1430 for transmitting one or more of a continuous wave or a command to an environmental communication system during a first session.
[0196] The various components of the communication device 1400 can provide functionality to enable the performance of the methods described herein for Figure 12 any aspects related thereto. For example, means for transmitting, communicating, or outputting for transmission can comprise the transceiver 254 and / or the antennas 252 of the UE 120, and / or the transceiver 1408 and the antennas 1410 of the communication device 1400 in Figure 14 For example, means for receiving or obtaining can comprise the transceiver 254 and / or the antennas 252 of the UE 120, and / or the transceiver 1408 and the antennas 1410 of the communication device 1400 in Figure 14 For example, means for receiving or obtaining can comprise the transceiver 254 and / or the antennas 252 of the UE 120, and / or the transceiver 1408 and the antennas 1410 of the communication device 1400 in
[0197] Figure 14 are provided as examples. Other examples can differ from what is described in connection with Figure 14 the examples described herein.
[0198] Figure 15 is a diagram illustrating an example of a specific implementation of code and circuitry for a communication device 1500 in accordance with the present disclosure. The communication device 1500 can be a network entity such as a BS 110 or a disaggregated base station as described with respect to Figure 3 The network entity can include the communication device 1500.
[0199] The communication device 1500 includes a processing system 1502 coupled to a transceiver 1508 (e.g., a transmitter and / or a receiver). The transceiver 1508 is configured to transmit and receive signals for the communication device 1500 via an antenna 1510, such as the various signals as described herein. A network interface 1512 is configured to obtain and transmit signals for the communication device 1500 via a communication link, such as a backhaul link, an intermediate link, and / or a fronthaul link as described herein, such as with respect to Figure 3 The processing system 1502 can be configured to perform processing functions of the communication device 1500, including processing signals received by and / or to be transmitted by the communication device 1500.
[0200] The processing system 1502 includes one or more processors 1520. In various aspects, the one or more processors 1520 can represent one or more of the reception processor 238, the transmit processor 220, the TX MIMO processor 230, and / or the controller / processor 240, as described with respect to Figure 2The one or more processors 1520 are coupled to the computer-readable medium / memory 1530 via bus 1506. In various aspects, the computer-readable medium / memory 1530 can represent a memory 242 as described with respect to FIG. 2, and the one or more processors 1520 can represent a processor 240 as described with respect to FIG. 2. Figure 2 In certain aspects, the computer-readable medium / memory 1530 is configured to store instructions (e.g., computer-executable code, processor-executable code) that, when executed by the one or more processors 1520, cause the one or more processors 1520 to perform the methods 1300 described herein or any aspect related thereto. Figure 13 The one or more processors 1520 are coupled to the computer-readable medium / memory 1530 via bus 1506. In various aspects, the computer-readable medium / memory 1530 can represent a memory 242 as described with respect to FIG. 2, and the one or more processors 1520 can represent a processor 240 as described with respect to FIG. 2.
[0201] As described above, the communication device 1500 can include circuitry for outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE (circuitry 1535). Figure 15 As described above, the communication device 1500 can include circuitry for outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE (circuitry 1535).
[0202] As described above, the communication device 1500 can include circuitry for outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE (circuitry 1535). Figure 15 As described above, the communication device 1500 can include circuitry for outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE (circuitry 1535).
[0203] As described above, the communication device 1500 can include circuitry for outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE (circuitry 1535). Figure 15 As described above, the communication device 1500 can include circuitry for outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE (circuitry 1535).
[0204] As described above, the communication device 1500 can include circuitry for outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE (circuitry 1535). Figure 15 As described above, the communication device 1500 can include circuitry for outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE (circuitry 1535).
[0205] As described above, the communication device 1500 can include circuitry for outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE (circuitry 1535). Figure 15 As described above, the communication device 1500 can include circuitry for outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE (circuitry 1535).
[0206] As described above, the communication device 1500 can include circuitry for outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE (circuitry 1535). Figure 15 As described above, the communication device 1500 can include circuitry for outputting or configuring parameters for resolving scheduling conflicts that occur during communications with a UE (circuitry 1535).
[0207] The various components of the communication device 1500 can provide functionality for performing the steps of the methods 1300 described with respect to FIG. 13. Figure 13 The components of the described method 1300 or any aspect related thereto. For example, means for transmitting, communicating, or outputting for transmission can include the transceiver 232 and / or the antenna 234 of the BS 110, and / or the transceiver 1508 and the antenna 1510 of the communication device 1500 in Figure 15 The components of the described method 1300 or any aspect related thereto. For example, means for transmitting, communicating, or outputting for transmission can include the transceiver 232 and / or the antenna 234 of the BS 110, and / or the transceiver 1508 and the antenna 1510 of the communication device 1500 in Figure 15 The components of the described method 1300 or any aspect related thereto. For example, means for transmitting, communicating, or outputting for transmission can include the transceiver 232 and / or the antenna 234 of the BS 110, and / or the transceiver 1508 and the antenna 1510 of the communication device 1500 in
[0208] Figure 15 are provided as examples. Other examples can differ from what is described in connection with Figure 15 the examples described in connection with the
[0209] SUMMARY
[0210] Aspect 1 : A method of wireless communication performed by a UE, the method comprising: receiving a parameter for resolving a scheduling conflict occurring during communication with an environmental communication system and a network entity; scheduling, in accordance with the parameter, a first session for communication with the environmental communication system and a second session for communication with the network entity; and transmitting, to the environmental communication system, one or more of a continuous wave or a command during the first session.
[0211] Aspect 2: The method of aspect 1, wherein scheduling the first session and the second session comprises scheduling the first session and the second session to occur at different times.
[0212] Aspect 3: The method of any one of aspects 1 through 2, wherein scheduling the first session and the second session comprises scheduling the first session and the second session to partially overlap in time.
[0213] Aspect 4: The method of any one of aspects 1 through 3, wherein scheduling the first session and the second session comprises scheduling the first session to terminate prior to the second session beginning.
[0214] Aspect 5: The method of any one of aspects 1 through 4, wherein scheduling the first session and the second session comprises scheduling the first session to begin after the second session ends.
[0215] Aspect 6: The method of any one of aspects 1 through 5, wherein scheduling the first session and the second session comprises shortening a configured duration of the first session, and scheduling the second session to begin after the first session ends.
[0216] Aspect 7: The method of any one of aspects 1 through 6, wherein scheduling the first session and the second session comprises splitting the first session into a first portion and a second portion, scheduling the first portion to end before the second session begins, and scheduling the second portion to begin after the second session ends.
[0217] Aspect 8: The method of any one of aspects 1 through 7, further comprising receiving a response to the continuous wave or the command from the environmental communication system during the first session.
[0218] Aspect 9: The method of any one of aspects 1 through 8, wherein scheduling the first session and the second session comprises scheduling the first session as a result of an Ll priority indicator, an L2 priority indicator, or an L3 priority indicator.
[0219] Aspect 10: The method of any one of aspects 1 through 9, further comprising detecting the scheduling conflict after receiving the parameter for resolving the scheduling conflict.
[0220] Aspect 11: The method of aspect 10, wherein scheduling one or more of the first session or the second session occurs after detecting the scheduling conflict.
[0221] Aspect 12: The method of aspect 10, wherein scheduling one or more of the first session or the second session occurs before detecting the scheduling conflict.
[0222] Aspect 13: The method of any one of aspects 1 through 12, further comprising receiving a configuration for full-duplex communication, wherein the parameter is based at least in part on the configuration for full-duplex communication.
[0223] Aspect 14: The method of aspect 13, wherein the parameter based at least in part on the configuration for full-duplex communication comprises a parameter for simultaneously transmitting the continuous wave or command and receiving a response to the continuous wave or command from the environmental communication system.
[0224] Aspect 15: The method of any one of aspects 1 through 14, further comprising receiving a configuration for half-duplex communication, wherein the parameter is based at least in part on the configuration for half-duplex communication.
[0225] Aspect 16: The method of aspect 15, wherein the parameter based at least in part on the configuration for half-duplex communication comprises a parameter for transmitting the continuous wave or command and receiving a response to the continuous wave or command from the environmental communication system at different times.
[0226] Aspect 17: The method of any of aspects 1 through 16, further comprising: receiving a priority indication indicating a priority assigned to one or more of the first session or the second session, wherein scheduling one or more of the first session or the second session comprises scheduling one or more of the first session or the second session based at least in part on the priority indication.
[0227] Aspect 18: A method of wireless communication performed by a network entity, comprising: outputting or configuring a parameter for resolving a scheduling conflict that occurs during communication with a UE; configuring the UE to schedule, in accordance with the parameter, one or more of a first session for communication between the UE and an environmental communication system or a second session for communication between the UE and the network entity; and configuring the UE to transmit, to the environmental communication system, one or more of a continuous wave or a command during the first session.
[0228] Aspect 19: The method of aspect 18, wherein configuring the UE comprises configuring the UE to schedule the first session and the second session to occur at different times.
[0229] Aspect 20: The method of aspect 19, wherein configuring the UE comprises configuring the UE to schedule the first session and the second session to at least partially overlap in time.
[0230] Aspect 21: The method of aspect 19, wherein configuring the UE comprises configuring the UE to schedule the first session to end before the second session begins.
[0231] Aspect 22: The method of aspect 19, wherein configuring the UE comprises configuring the UE to schedule the first session to begin after the second session ends.
[0232] Aspect 23: The method of aspect 19, wherein configuring the UE comprises configuring the UE to shorten a configured duration of the first session and to schedule the second session to begin after the first session ends.
[0233] Aspect 24: The method of aspect 19, wherein configuring the UE comprises configuring the UE to divide the first session into a first portion and a second portion and to schedule the first portion to end before the second session begins and to schedule the second portion to begin after the second session ends.
[0234] Aspect 25: The method of aspect 19, further comprising configuring the UE to receive, from the environmental communication system during the first session, a response to the continuous wave or the command.
[0235] Aspect 26: The method of aspect 19, wherein configuring the UE comprises configuring the UE to schedule the first session according to an L1 priority indicator, an L2 priority indicator, or an L3 priority indicator.
[0236] Aspect 27: The method of aspect 19, further comprising: outputting or configuring a priority indication that indicates a priority assigned to one or more of the first session and the second session, wherein configuring the UE comprises configuring the UE to schedule one or more of the first session and the second session based at least in part on the priority indication.
[0237] Aspect 28: The method of aspect 19, wherein the parameter is outputted or configured based at least in part on the UE being configured for full-duplex communication.
[0238] Aspect 29: The method of aspect 30, wherein the parameter configures the UE to simultaneously transmit the continuous wave or command and receive, from the environmental communication system, a response to the continuous wave or command.
[0239] Aspect 30: The method of aspect 19, wherein the parameter is outputted or configured based at least in part on the UE being configured for half-duplex communication.
[0240] Aspect 31: The method of aspect 32, wherein the parameter configures the UE to transmit the continuous wave or command and receive, from the environmental communication system, a response to the continuous wave or command at different times.
[0241] Aspect 32: An apparatus for wireless communication at a device, the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of aspects 1 through 31.
[0242] Aspect 33: A device for wireless communication, the device comprising memory and one or more processors coupled to the memory, the one or more processors configured to perform the method of one or more of aspects 1 through 31.
[0243] Aspect 34: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of aspects 1 through 31.
[0244] Aspect 35: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-31.
[0245] Aspect 36: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-31.
[0246] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or from practicing the aspects.
[0247] As used herein, the term “component” is intended to be broadly interpreted to include hardware and / or a combination of hardware and software. “Software” shall be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware and / or a combination of hardware and software. It will be apparent that systems and / or methods described herein can be implemented in different forms of hardware and / or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — because software and hardware can be designed to implement the systems and / or methods based on the description herein, with the software and hardware being at least partially non- transitory.
[0248] As used herein, depending on the context, “satisfy a threshold” can refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, and / or the like.
[0249] Although specific combinations of features are set out in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of the features described herein can be combined in ways not specifically recited in the claims and / or described in the specification. The disclosure of various aspects includes each and every combination of the features described herein (and / or in the claims). As used herein, the phrase “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination of items from among a, b, and c (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c, or duplicates of a, b, and c).
[0250] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items, and can be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items unless otherwise indicated by context. Also, as used herein, the terms “has,” “have,” “having,” or “has” are intended to be open-ended terms that do not limit any element, or item, to a single instance, but rather, to one or more instances, and are intended to cover any and all possible instances. Furthermore, as used herein, expressions such as “based on” can mean “based, at least in part, on” unless expressly specified otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series of items (e.g., “a, b, or c” or “a, b, and c”) unless otherwise indicated by context.
[0251] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein are not limiting in terms of the scope, applicability, or configurations set forth in the claims. Various modifications can be made by those skilled in the art to the examples discussed herein, and the generic principles defined herein can be applied to other aspects. For example, changes can be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples can omit, substitute, or add various procedures or components as appropriate. For instance, the methods described can be performed in an order different than that described, and various actions can be added, omitted, or combined. Also, features described with respect to some examples can be combined in other examples. For example, an apparatus can be implemented or a method can be practiced using any number of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover devices, methods, and articles of manufacture, as set forth in the claims, that are found to be
[0252] The various illustrative logical blocks, modules, and circuits described in connection with the disclosure herein can be implemented or performed with a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device (PLD), 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 the alternative, the processor can be any commercially available processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a
[0253] As used herein, the term “determining” encompasses a wide variety of actions. For example, “determining” can include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database, or another data structure), ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, “determining” can include resolving, selecting, choosing, establishing, and the like.
[0254] The methods disclosed herein comprise one or more actions for implementing each method. The method actions can be interchanged with one another without departing from the scope of the claims. In other words, the order of certain actions can be modified, and / or used, without departing from the scope of the claims unless specified otherwise by the specified order of actions. Moreover, various operations of the methods described above can be performed by any suitable means capable of performing the corresponding functions. These means can include various hardware and / or software component(s) and / or module(s), including, but not limited to, circuitry, an application specific integrated circuit (ASIC), or processor.
[0255] The following claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims. Within the claims, the singular forms are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "some" refers to one or more. Unless specifically stated otherwise, the term "about" as used herein is intended to accommodate some imprecision in amounts. Any claim element not specifically recited in a claim is not intended to be a disavowed element important for the practice of the disclosure, unless specifically recited in the claim. All structural and functional equivalents to aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.
Claims
1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and One or more processors coupled to the memory, the one or more processors being configured to: Receive parameters used to resolve scheduling conflicts that occur during communication with environmental communication systems and network entities; The parameters are used to schedule a first session for communication with the environment communication system and a second session for communication with the network entity. as well as During the first session, one or more of a continuous wave or a command are sent to the environmental communication system.
2. The UE of claim 1, wherein, in order to schedule the first session and the second session, the one or more processors are configured to schedule the first session and the second session to occur at different times.
3. The UE of claim 1, wherein, in order to schedule the first session and the second session, the one or more processors are configured to schedule the first session to terminate before the second session begins.
4. The UE of claim 1, wherein, in order to schedule the first session and the second session, the one or more processors are configured to schedule the first session to begin after the second session has ended.
5. The UE of claim 1, wherein, in order to schedule the first session and the second session, the one or more processors are configured to shorten the configuration duration of the first session and schedule the second session to begin after the first session ends.
6. The UE of claim 1, wherein, in order to schedule the first session and the second session, the one or more processors are configured to divide the first session into a first part and a second part, schedule the first part to end before the second session begins, and schedule the second part to begin after the second session ends.
7. The UE of claim 1, wherein the one or more processors are further configured to receive a response to the continuous wave or the command from the environmental communication system during the first session.
8. The UE of claim 1, wherein, in order to schedule the first session and the second session, the one or more processors are configured to schedule the first session as a result of a Layer 1 priority indicator, a Layer 2 priority indicator, or a Layer 3 priority indicator.
9. The UE of claim 1, wherein the one or more processors are further configured to detect the scheduling conflict after receiving the parameters for resolving the scheduling conflict.
10. The UE of claim 9, wherein scheduling one or more of the first session or the second session occurs after the scheduling conflict is detected.
11. The UE of claim 9, wherein scheduling one or more of the first session or the second session occurs before the scheduling conflict is detected.
12. The UE of claim 1, wherein the one or more processors are further configured to receive configuration for full-duplex communication, wherein the parameters are at least in part based on the configuration for full-duplex communication.
13. The UE of claim 12, wherein the parameters based at least in part on the configuration for full-duplex communication include parameters for simultaneously transmitting the continuous wave or command and receiving a response to the continuous wave or command from the environmental communication system.
14. The UE of claim 1, wherein the one or more processors are further configured to receive configuration for half-duplex communication, wherein the parameters are at least in part based on the configuration for half-duplex communication.
15. The UE of claim 14, wherein the parameters based at least in part on the configuration for half-duplex communication include parameters for transmitting the continuous wave or command at different times and receiving a response to the continuous wave or command from the environmental communication system.
16. The UE of claim 1, wherein the one or more processors are further configured to: Receive a priority indication that assigns a priority to one or more of the first session or the second session. In order to schedule one or more of the first session or the second session, the one or more processors are configured to schedule one or more of the first session or the second session at least in part based on the priority indication.
17. A network entity for wireless communication, the network entity comprising: Memory; and One or more processors coupled to the memory, the one or more processors being configured to: Output or configure parameters used to resolve scheduling conflicts that occur during communication with user equipment (UE); The UE is configured to schedule one or more of a first session for communication between the UE and the environmental communication system or a second session for communication between the UE and the network entity, according to the parameters; and The UE is configured to send one or more of a continuous wave or a command to the environmental communication system during the first session.
18. The network entity of claim 17, wherein the one or more processors are configured to configure the UE to schedule the first session and the second session to occur at different times.
19. The network entity of claim 18, wherein the one or more processors are configured to configure the UE to schedule the first session to end before the second session begins.
20. The network entity of claim 18, wherein the one or more processors are configured to configure the UE to schedule the first session to begin after the second session ends.
21. The network entity of claim 18, wherein the one or more processors are configured to configure the UE to shorten the configuration duration of the first session and schedule the second session to begin after the first session ends.
22. The network entity of claim 18, wherein the one or more processors are configured to configure the UE to divide the first session into a first part and a second part, and to schedule the first part to end before the second session begins and to schedule the second part to begin after the second session ends.
23. The network entity of claim 18, wherein the one or more processors are further configured to configure the UE to receive a response to the continuous wave or the command from the environmental communication system during the first session.
24. The network entity of claim 18, wherein the one or more processors are configured to configure the UE to schedule the first session according to a Layer 1 priority indicator, a Layer 2 priority indicator, or a Layer 3 priority indicator.
25. The network entity of claim 18, wherein the one or more processors are further configured to: The output or configuration indication is a priority indication that assigns priority to one or more of the first session and the second session. The one or more processors are configured to configure the UE to schedule one or more of the first session and the second session at least in part based on the priority indication.
26. The network entity of claim 18, wherein the parameters are output or configured at least in part based on the UE being configured for full-duplex communication.
27. The network entity of claim 26, wherein the parameters configure the UE to simultaneously transmit the continuous wave or command and receive a response to the continuous wave or command from the environmental communication system.
28. The network entity of claim 18, wherein the parameters are output or configured at least in part based on the UE being configured for half-duplex communication.
29. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive parameters used to resolve scheduling conflicts that occur during communication with environmental communication systems and network entities; The parameters are used to schedule a first session for communication with the environment communication system and a second session for communication with the network entity. as well as During the first session, one or more of a continuous wave or a command are sent to the environmental communication system.
30. A method for wireless communication performed by a network entity, the method comprising: Output or configure parameters used to resolve scheduling conflicts that occur during communication with user equipment (UE); The UE is configured to schedule one or more of a first session for communication between the UE and the environmental communication system or a second session for communication between the UE and the network entity, according to the parameters; and The UE is configured to send one or more of a continuous wave or a command to the environmental communication system during the first session.