Transfer mode loop alignment

Abstract

Methods, systems, and apparatus for wireless communications are described. A user equipment (UE) may receive, at a processing layer of the UE, a discontinuous reception (DRX) cycle parameter set from a corresponding application set at an application layer of the UE. The UE may determine a common DRX cycle to satisfy each application in the application set based on the DRX parameter set. The UE may transmit the common DRX cycle to one or more layers in a user plane protocol stack of the UE. A base station may also receive, from the UE, a request for the DRX cycle parameter set that satisfies the common DRX cycle of the UE. The base station may transmit an indication of the DRX parameter set and receive, from the UE, an acknowledgment of the DRX cycle associated with the DRX cycle parameter set.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 147,738, filed by BALASUBRAMANIAN et al. on January 13, 2021, entitled “TRANSMISSION MODE CYCLE ALIGNMENT,” which claims priority to U.S. provisional patent application No. 62 / 962,861, filed by BALASUBRAMANIAN et al. on January 17, 2020, entitled “TRANSMISSION MODE CYCLE ALIGNMENT,” each of which is assigned to its assignee. Technical Field

[0003] The following relates generally to wireless communications, and more particularly to transmission pattern cycle alignment.

[0004] background

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, broadcast, and the like. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems (such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems), and fifth generation (5G) systems, which may be referred to as new radio (NR) systems. These systems may employ various technologies, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting communication with multiple communication devices, which may be further referred to as user equipment (UE).

[0006] The UE may utilize a wake-up cycle, such as a discontinuous reception (DRX) cycle, to periodically monitor a communication channel. In some cases, the UE may communicate on one or more radio access technologies (RATs) (e.g., NR or LTE), or using one or more communication types (such as unicast or broadcast). Each communication in each RAT or each different application type may include operation on a different wake-up cycle. This may cause the UE to operate in an always-on or similar mode, which may reduce the power and efficiency of the UE.

[0007] Overview

[0008] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting transmission mode cycle alignment. Generally, the described techniques are provided for use by a user equipment (UE), for example, in a vehicle-to-everything (V2X) communication system, to determine a common discontinuous reception (DRX) cycle. The UE may receive, at a processing layer of the UE, a set of DRX cycle parameters from a corresponding application set at an application layer of the UE. The processing layer may be below the application layer and above a user plane protocol stack of the UE. The UE may determine, based on the set of DRX cycle parameters, a common DRX cycle to satisfy each of the application sets. The UE may communicate the common DRX cycle to one or more layers in the user plane protocol stack of the UE.

[0009] In addition, a base station in communication with the UE may receive a request from the UE for a DRX cycle parameter set that satisfies the common DRX cycle of the UE. The base station may transmit a confirmation of the DRX cycle associated with the DRX cycle parameter set to the UE. The base station may receive a confirmation of the DRX cycle associated with the DRX parameter set from the UE.

[0010] A method for wireless communication at a UE is described. The method may include: receiving, at a processing layer of the UE, a set of DRX cycle parameter sets from a corresponding application set at an application layer of the UE, wherein the processing layer is below the application layer and above a user plane protocol stack of the UE; determining a common DRX cycle based on the set of DRX cycle parameter sets to satisfy each of the application sets; and transmitting the common DRX cycle to one or more layers in the user plane protocol stack of the UE.

[0011] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive, at a processing layer of the UE, a set of DRX cycle parameter sets from a corresponding application set at an application layer of the UE, wherein the processing layer is below the application layer and above a user plane protocol stack of the UE; determine, based on the set of DRX cycle parameter sets, a common DRX cycle to satisfy each of the application sets; and transmit the common DRX cycle to one or more layers in the user plane protocol stack of the UE.

[0012] Another apparatus for wireless communication at a UE is described. The apparatus may include means for: receiving, at a processing layer of the UE, a set of DRX cycle parameter sets from a corresponding application set at an application layer of the UE, wherein the processing layer is below the application layer and above a user plane protocol stack of the UE; determining a common DRX cycle based on the set of DRX cycle parameter sets to satisfy each of the application sets; and transmitting the common DRX cycle to one or more layers in the user plane protocol stack of the UE.

[0013] A non-transitory computer-readable medium storing code for wireless communication at a UE is described. The code may include instructions executable by a processor to: receive, at a processing layer of the UE, a set of DRX cycle parameter sets from corresponding application sets at an application layer of the UE, wherein the processing layer is below the application layer and above a user plane protocol stack of the UE; determine, based on the set of DRX cycle parameter sets, a common DRX cycle to satisfy each of the application sets; and transmit the common DRX cycle to one or more layers in the user plane protocol stack of the UE.

[0014] A method of wireless communication at a base station is described. The method may include: receiving a request from a UE for a DRX cycle parameter set that satisfies a common DRX cycle of the UE; transmitting an indication of the DRX cycle parameter set to the UE in response to the request; and receiving an acknowledgement of a DRX cycle associated with the DRX cycle parameter set from the UE.

[0015] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive a request from a UE for a DRX cycle parameter set that satisfies a common DRX cycle of the UE; transmit an indication of the DRX cycle parameter set to the UE in response to the request; and receive an acknowledgment of a DRX cycle associated with the DRX cycle parameter set from the UE.

[0016] Another apparatus for wireless communication at a base station is described. The apparatus may include means for: receiving a request from a UE for a DRX cycle parameter set that satisfies a common DRX cycle for the UE; transmitting an indication of the DRX cycle parameter set to the UE in response to the request; and receiving an acknowledgment of a DRX cycle associated with the DRX cycle parameter set from the UE.

[0017] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code may include instructions executable by a processor to: receive a request from a UE for a DRX cycle parameter set that satisfies a common DRX cycle for the UE; transmit an indication of the DRX cycle parameter set to the UE in response to the request; and receive an acknowledgement of a DRX cycle associated with the DRX cycle parameter set from the UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 An example of a wireless communication system supporting transmission pattern cycle alignment according to aspects of the present disclosure is illustrated.

[0020] Figure 2 An example of a wireless communication system supporting transmission pattern cycle alignment according to aspects of the present disclosure is illustrated.

[0021] Figure 3 and 4 An example of a protocol stack supporting transmission mode cycle alignment according to aspects of the present disclosure is illustrated.

[0022] Figure 5 and 6 An example of a process flow supporting transmission mode cycle alignment according to aspects of the present disclosure is illustrated.

[0023] Figure 7 and 8 A block diagram of a device supporting transmission mode cycle alignment according to aspects of the present disclosure is shown.

[0024] Figure 9 A block diagram of a communication manager supporting transmission mode cycle alignment according to aspects of the present disclosure is shown.

[0025] Figure 10 A diagram of a system including devices supporting transmission pattern cycle alignment is shown in accordance with aspects of the present disclosure.

[0026] Figure 11 and 12 A block diagram of a device supporting transmission mode cycle alignment according to aspects of the present disclosure is shown.

[0027] Figure 13 A block diagram of a communication manager supporting transmission mode cycle alignment according to aspects of the present disclosure is shown.

[0028] Figure 14 A diagram of a system including devices supporting transmission pattern cycle alignment is shown in accordance with aspects of the present disclosure.

[0029] Figures 15 to 18A flow chart illustrating a method of supporting transmission mode cycle alignment according to aspects of the present disclosure is shown.

[0030] Detailed description

[0031] User equipment (UE) can use a wake-up cycle, such as a discontinuous reception (DRX) cycle, to periodically monitor a channel during an awake period. Monitoring of the channel can include transmitting and receiving signals during the awake period. During other periods, the UE can be in a low-power or sleep mode. The UE can thus save power by periodically monitoring communications rather than operating in an always-on mode.

[0032] A UE may communicate in a vehicle-to-everything (V2X) communication system (which may be an example of sidelink communication) or directly with a base station. The UE may further communicate according to different radio access technologies (RATs) or according to different schemes, such as unicast, groupcast, multicast, or broadcast. The UE may configure different DRX cycles for communications on different RATs, and may also have different DRX cycles between unicast and broadcast communications. The UE may also have a configured DRX scheme for V2X communication, as well as configured DRX schemes for uplink and downlink communications with a base station.

[0033] In this way, the UE may monitor the communication channel according to each configured DRX cycle, and in some cases, each DRX cycle may have a different periodicity or wake-up length. As a result, the UE may be continuously in on mode due to the misaligned DRX cycles that the UE attempts to meet. Even if the UE is able to enter sleep or low-power mode, the UE's total on duration may result in an extended monitoring period. Therefore, this extended monitoring due to the DRX cycle configuration may reduce the UE's power and efficiency because the UE no longer operates to take advantage of the power savings of the DRX cycle.

[0034] Furthermore, if multiple UEs in the system have aligned DRX cycles, congestion may occur because each UE may access the communication channel simultaneously, and there may be periods where few or no UEs access the channel. This may lead to further inefficiencies.

[0035] Thus, the UE can individually determine a common DRX cycle for different applications of the UE (such as sidelink or V2X communication, and sidelink communication on different RATs). The common DRX cycle can allow all applications of the UE to wake up in the same or overlapping time periods, which can save power at the UE and use resources more efficiently. In addition, the UE can also align the common DRX cycle used for sidelink communication with the DRX cycle used for communicating with the base station. Therefore, the base station can have information about the common DRX cycle for each UE in the system for the sidelink, and align the base station and UE DRX cycles (e.g., UuDRX cycle) for each UE to efficiently use the uplink, downlink, and sidelink resources in the system to further reduce congestion.

[0036] Aspects of the present disclosure are initially described in the context of wireless communication systems. Aspects of the present disclosure are subsequently described in the context of protocol stacks and process flows. Aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flow diagrams related to transmission mode cycle alignment.

[0037] Figure 1 An example of a wireless communication system 100 supporting transmission mode cycle alignment according to aspects of the present disclosure is illustrated. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, communication with low-cost and low-complexity devices, or any combination thereof.

[0038] Base stations 105 may be dispersed throughout a geographic area to form wireless communication system 100 and may be different forms of devices or devices with different capabilities. Base stations 105 and UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which UEs 115 and base stations 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographic area over which base stations 105 and UEs 115 may support signal communication according to one or more radio access technologies.

[0039] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. The UEs 115 may be different forms of devices or devices with different capabilities. Figure 11. The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network equipment (e.g., core network nodes, relays, integrated access and backhaul (IAB) nodes, or other network equipment), such as Figure 1 As shown in .

[0040] Each base station 105 can communicate with the core network 130, with each other, or both. For example, the base stations 105 can interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 can communicate with each other directly (e.g., directly between the base stations 105), indirectly (e.g., via the core network 130), or both directly and indirectly on the backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some examples, the backhaul links 120 can be or include one or more wireless links.

[0041] One or more of the base stations 105 described herein may include or may be referred to by one of ordinary skill in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next generation Node B, or a Gigabit Node B (any of which may be referred to as a gNB), a Home Node B, a Home Evolved Node B, or other suitable terminology.

[0042] UE 115 may include or be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where "device" may also be referred to as a unit, a station, a terminal, or a client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a machine type communication (MTC) device, etc., which may be implemented in various objects, such as appliances or vehicles, meters, etc.

[0043] The UE 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, which may sometimes act as relays, as well as base stations 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. Figure 1 As shown in .

[0044] The UE 115 and the base station 105 may communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer (PHY) structure for supporting the communication link 125. For example, a carrier for the communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating carrier operation, user data, or other signaling. The wireless communication system 100 may support communication with the UE 115 using carrier aggregation or multi-carrier operation. The UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0045] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel grid for discovery by a UE 115. A carrier may operate in a standalone mode in which initial acquisition and connection may be performed by a UE 115 via the carrier, or a carrier may operate in a non-standalone mode in which the connection is anchored using a different carrier (e.g., a different carrier of the same or different radio access technology).

[0046] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. A carrier may carry downlink or uplink communications (e.g., in FDD mode) or may be configured to carry both downlink and uplink communications (e.g., in TDD mode).

[0047] A carrier may be associated with a particular bandwidth of radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or wireless communication system 100. For example, the carrier bandwidth may be one of several determined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)) of a carrier of a particular radio access technology. Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) may have a hardware configuration that supports communication on a particular carrier bandwidth, or may be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of the carrier bandwidth.

[0048] The signal waveform transmitted on the carrier may include multiple subcarriers (e.g., using a multicarrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may include one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Thus, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate of UE 115 can be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may further improve the data rate or data integrity of communications with UE 115.

[0049] One or more parameter sets for a carrier may be supported, where the parameter set may include a subcarrier spacing (Δf) and a cyclic prefix. A carrier may be divided into one or more BWPs with the same or different parameter designs. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications for the UE 115 may be limited to the one or more active BWPs.

[0050] The time interval of the base station 105 or the UE 115 can be expressed as a multiple of a basic time unit, which can be, for example, a sampling period T s =1 / (Δf max ·N f ) seconds, where Δf max It can represent the maximum supported subcarrier spacing, and N fThe maximum supported discrete Fourier transform (DFT) size may be indicated. Time intervals of communication resources may be organized according to radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0051] Each frame may include a plurality of consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of code element periods (e.g., depending on the length of the cyclic prefix added before each code element period). In some wireless communication systems 100, a time slot may be further divided into a plurality of mini-time slots containing one or more code elements. Excluding the cyclic prefix, each code element period may contain one or more (e.g., N f The duration of a symbol period may depend on the subcarrier spacing or the operating band.

[0052] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0053] Physical channels may be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels may be multiplexed on a downlink carrier, for example, using one or more of time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for physical control channels may be defined by a number of symbol periods and may extend across the system bandwidth or a subset of the system bandwidth of a carrier. One or more control regions (e.g., CORESETs) may be configured for a set of UEs 115. For example, one or more of UEs 115 may monitor or search the control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. The search space sets may include a common search space set configured for transmitting control information to multiple UEs 115 and a UE-specific search space set for transmitting control information to a specific UE 115 .

[0054] Each base station 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with a base station 105 (e.g., on a carrier) and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other) used to distinguish between adjacent cells. In some examples, a cell may also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which the logical communication entity operates. The scope of such a cell may range from a smaller area (e.g., a structure, a subset of structures) to a larger area depending on various factors (such as the capabilities of the base station 105). For example, a cell may be or include a building, a subset of buildings, or an external space between or overlapping geographic coverage areas 110, among other examples.

[0055] A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access to UEs 115 that have a service subscription with a network provider that supports the macro cell. A small cell may be associated with a lower power base station 105 (compared to a macro cell), and the small cell may operate in the same or different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 that have a service subscription with the network provider, or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). A base station 105 may support one or more cells and may also support communications over one or more cells using one or more component carriers.

[0056] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

[0057] In some examples, base stations 105 can be mobile and, therefore, provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies can overlap, but the different geographic coverage areas 110 can be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies can be supported by different base stations 105. The wireless communication system 100 can include, for example, a heterogeneous network in which different types of base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.

[0058] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations 105 may have similar frame timing, and transmissions from different base stations 105 may be approximately aligned in time. For asynchronous operation, the base stations 105 may have different frame timing, and transmissions from different base stations 105 may not be aligned in time in some examples. The techniques described herein may be used for either synchronous or asynchronous operation.

[0059] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a base station 105 without human intervention. In some examples, M2M communication or MTC may include communications from devices that incorporate sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents it to a person interacting with the application. Some UEs 115 may be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wilderness survival monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0060] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communication, operating over a limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0061] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. The UE 115 can be designed to support ultra-reliable, low-latency or critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private communication or group communication and can be supported by one or more mission-critical services such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions can include prioritization of services, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency can be used interchangeably herein.

[0062] In some examples, UE 115 may also be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within the geographic coverage area 110 of base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of base station 105 or otherwise unable to receive transmissions from base station 105. In some examples, groups of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system, in which each UE 115 transmits to every other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving base station 105.

[0063] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. The vehicles can signal information related to traffic conditions, signal scheduling, weather, safety, emergency situations, or any other information related to the V2X system. In some examples, the vehicles in the V2X system can use vehicle-to-network (V2N) communication to communicate with roadside infrastructure (such as roadside units), with the network, or with both via one or more network nodes (e.g., base station 105).

[0064] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and the EPC or 5GC may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnects to external networks. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the core network 130. User IP packets may be delivered through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the network operator IP service 150. Operator IP services 150 may include access to the Internet, an intranet, an IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0065] Some network devices (such as base stations 105) may include subcomponents, such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with each UE 115 through one or more other access network transport entities 145, which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., base station 105).

[0066] The wireless communication system 100 can operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally speaking, the 300 MHz to 3 GHz region is referred to as the ultra-high frequency (UHF) region or the decimeter band because the wavelengths range from approximately 1 decimeter to 1 meter long. UHF waves can be blocked or redirected by buildings and environmental features, but these waves can penetrate various structures sufficiently for macrocells to provide service to UEs 115 located indoors. Transmissions using UHF waves can be associated with smaller antennas and a shorter range (e.g., less than 100 kilometers) compared to transmissions using the lower frequencies and longer wavelengths in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0067] The wireless communication system 100 may also operate in the super high frequency (SHF) region of the frequency band from 3 GHz to 30 GHz (also known as the centimeter band) or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the base station 105, and the EHF antennas of the corresponding devices may be smaller and more closely spaced than the UHF antennas. In some examples, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be subject to even greater atmospheric attenuation and a shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

[0068] The wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 may employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band, such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices (such as base stations 105 and UEs 115) may employ carrier sensing for conflict detection and avoidance. In some examples, operations in the unlicensed band may be based on a carrier aggregation configuration (e.g., LAA) in coordination with component carriers operating in the licensed band. Operations in the unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among others.

[0069] The base station 105 or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels that can support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with the base station 105 may be located at different geographical locations. The base station 105 may have an antenna array having several rows and columns of antenna ports that the base station 105 can use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0070] The base station 105 or the UE 115 can use MIMO communication to exploit multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such a technique may be referred to as spatial multiplexing. For example, a transmitting device may transmit multiple signals via different antennas or different antenna combinations. Similarly, a receiving device may receive multiple signals via different antennas or different antenna combinations. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), in which multiple spatial layers are transmitted to the same receiving device, and multi-user MIMO (MU-MIMO), in which multiple spatial layers are transmitted to multiple devices.

[0071] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., base station 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with that device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0072] The base station 105 or the UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, the base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by the base station 105 in different directions. For example, the base station 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. The transmissions in different beam directions may be used (e.g., by a transmitting device (such as the base station 105) or a receiving device (such as the UE 115)) to identify a beam direction for later transmission or reception by the base station 105.

[0073] Some signals, such as data signals associated with a particular recipient device, may be transmitted by base station 105 in a single beam direction, e.g., a direction associated with a recipient device, such as UE 115. In some examples, a beam direction associated with transmissions along a single beam direction may be determined based on signals transmitted in one or more beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions and may report to base station 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0074] In some examples, transmission by a device (e.g., by a base station 105 or a UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from the base station 105 to the UE 115). The UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. The base station 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may be precoded or uncoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may use similar techniques to transmit signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0075] A receiving device (e.g., UE 115) may attempt multiple receive configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105. For example, the receiving device may attempt multiple receive directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array (e.g., different directional listening weight sets), or processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receive configurations or receive directions. In some examples, the receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving data signals). The single receive configuration may be aligned on a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0076] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication of the bearer or packet data convergence protocol (PDCP) layer can be IP-based. The radio link control (RLC) layer can perform packet segmentation and reassembly to communicate on the logical channel. The media access control (MAC) layer can perform priority handling and multiplex the logical channel into the transport channel. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission of the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer can provide the establishment, configuration and maintenance of the RRC connection of the radio bearer that supports user plane data between the UE 115 and the base station 105 or the core network 130. At the physical layer, the transport channel can be mapped to the physical channel.

[0077] UE 115 and base station 105 may support retransmission of data to increase the likelihood that the data is successfully received. Hybrid Automatic Repeat Request (HARQ) feedback is a technique for increasing the likelihood that data is correctly received on communication link 125. HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve MAC layer throughput in poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support simultaneous slot HARQ feedback, wherein the device may provide HARQ feedback in a particular time slot for data received in a previous symbol in that time slot. In other cases, the device may provide HARQ feedback in a subsequent time slot or based on some other time interval.

[0078] For example, a UE 115 in a V2X communication system may determine a common DRX cycle. The UE 115 may receive a DRX cycle parameter set from a corresponding application set at an application layer of the UE 115 at a processing layer of the UE 115. The processing layer may be below the application layer and above the user plane protocol stack of the UE. The UE 115 may determine a common DRX cycle based on the DRX cycle parameter set to satisfy each of the applications in the application set. The UE 115 may communicate the common DRX cycle to one or more layers in the user plane protocol stack of the UE.

[0079] In addition, the base station 105 in communication with the UE 115 may receive a request from the UE 115 for a DRX cycle parameter set that satisfies the common DRX cycle of the UE 115. The base station 105 may transmit an acknowledgment of the DRX cycle associated with the DRX cycle parameter set to the UE 115. The base station 105 may receive an acknowledgment of the DRX cycle associated with the DRX cycle parameter set from the UE 115.

[0080] Figure 2An example of a wireless communication system 200 that supports transmission mode cycle alignment according to aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 can implement aspects of the wireless communication system 100. The base station 105-a can be as described with reference to Figure 1 Examples of base stations 105 are described. UEs 115-a and 115-b may be reference Figure 1 An example of a UE 115 is depicted. Base station 105-a can serve one or more UEs 115, including UEs 115-a and 115-b within coverage area 110-a. Base station 105-a can communicate with UE 115-a over communication link 205-a, and base station 105-a can also communicate with UE 115-b over communication link 205-b. Furthermore, UEs 115-a and 115-b can communicate over sidelink 210. For example, UE 115-a and UE 115-b can be vehicles within a V2X wireless communication system.

[0081] The UE 115-a may monitor both the communication link 205-a and the side link 210 based on one or more DRX cycles. For example, the UE 115-a may operate on a first DRX cycle to monitor the communication link 205-a and on a second DRX cycle to monitor the side link 210. The UE 115-a may also operate based on other DRX cycles to operate according to different RATs (e.g., LTE or NR), or may communicate on the communication link 205-a or the side link 210 based on different RATs using different DRX cycles.

[0082] UE 115-a may determine a common DRX cycle based on its monitoring (e.g., transmitting and receiving) on ​​the side link 210 with UE 115-b. UE 115-a may determine the common DRX cycle based on a negotiation within UE 115-a. For example, a processing layer of UE 115-a may negotiate with other layers of UE 115-a (such as an application in an application layer) to determine the common DRX cycle. UE 115-a may use the common DRX cycle to monitor the side link 210. UE 115-a may use the common DRX cycle to monitor communications of different RATs, as well as to transmit and receive unicast and broadcast communications. The common DRX cycle may allow UE 115-a to operate more efficiently during wake-up time, rather than in an always-on mode.

[0083] Additionally, the UE 115-a may communicate with the base station 105-a over the communication link 205-a to determine a Uu DRX cycle. The Uu DRX cycle may be a DRX cycle used for communications between the base station 105 and the UE 115. For example, the UE 115-a may use the Uu DRX cycle to determine when to monitor the communication link 205-a, including transmitting and receiving messages to and from the base station 105-a. In some cases, the base station 105-a may configure the UE 115-a with the Uu DRX cycle. In some cases, the base station 105-a may not configure the UE 115-a with the Uu DRX cycle.

[0084] In the event that the base station 105-a configures the UE 115-a with a Uu DRX cycle, the UE 115-a may use the Uu DRX cycle to determine the common DRX cycle, or the UE 115-a may determine the common DRX cycle and may require that the Uu DRX cycle configured by the base station 105-a match the common DRX cycle.

[0085] For example, UE 115-a may determine a common DRX cycle. UE 115-a may transmit an indication of the common DRX cycle or an indication of a parameter of the common DRX cycle to base station 105-a. Base station 105-a may determine a Uu DRX cycle based on the indication or the parameter and may transmit an indication of the Uu DRX cycle to UE 115-a over communication link 205-a. UE 115-a may accept the Uu DRX cycle and may transmit an indication acknowledging the Uu DRX cycle to base station 105-a. UE 115-a may communicate with base station 105-a over communication link 205-a using the Uu DRX cycle.

[0086] Furthermore, base station 105-a may determine a Uu DRX cycle so that communications with other UEs 115 are not interrupted or so that interference between UEs 115 can be reduced. For example, UE 115-b may also be configured with a Uu DRX cycle or may request an updated Uu DRX cycle. Base station 105-a may be configured to determine a Uu DRX cycle for UE 115-a and a Uu DRX cycle for UE 115-b so that each UE 115 has a different Uu DRX cycle and is therefore less likely to transmit and receive communications at similar times, thereby reducing interference and improving communication reliability at UEs 115-a and 115-b.

[0087] Figure 3An example of a protocol stack 300 that supports transmission mode cycle alignment according to aspects of the present disclosure is illustrated. In some examples, the protocol stack 300 can implement aspects of wireless communication systems 100 and 200. The protocol stack 300 can include the following: Figure 1 and Figure 2 Components within the UE 115 are depicted. The protocol stack 300 may include a V2X layer 305, a plurality of V2X applications 310 (each including a V2X service 315). The V2X layer 305 may communicate with the V2X applications 310. The protocol stack may also include a service data adaptation protocol (SDAP) 320, a PDCP 325, an RLC 330, and a MAC / PHY 335. Each of the SDAP 320, the PDCP 325, the RLC 330, and the MAC / PHY 335 may be included in a user plane protocol stack of the UE 115. In some cases, the MAC / PHY 335 may be separated into different layers.

[0088] To determine a common DRX cycle for sidelink communications, the V2X layer 305 (e.g., a processing layer) of the UE 115 may negotiate the common DRX cycle with one or more V2X applications 310 (e.g., an application layer) of the UE 115. In scenarios where each V2X service of the application 310 operates on a different RAT or according to a different communication configuration, each V2X service 315 may operate according to a different DRX cycle.

[0089] For example, V2X service 315-a may communicate on a first RAT (e.g., LTE), while V2X service 315-b may communicate on a second RAT (e.g., NR). Thus, V2X service 315-a and V2X service 315-b may have different service requirements for their corresponding DRX cycles. In another example, V2X service 315-c may communicate in a unicast configuration, and V2X service 315-d may communicate in a multicast configuration. V2X service 315-c and V2X service 315-d may also have different service requirements resulting in different DRX cycles, which may also be different from the DRX cycles of V2X services 315-a, 315-b, 315-e, and 315-f.

[0090] The UE 115 can thus determine a common DRX cycle across all application services to save battery and avoid large "on" periods caused by unsynchronized DRX cycles. The common DRX cycle can be determined to align with the different communication parameters of each V2X application 310 of the UE 115. The common DRX cycle can maximize power saving efficiency and fairly distribute channel load across each V2X application 310 of the UE 115.

[0091] Each V2X application 310 may be aware of its service requirements. Service requirements may include packet delay budget (PDB), reliability requirements, and other parameters. Each V2X application 310 may transmit a request to the V2X layer 305 for a DRX cycle that meets the service requirements of each V2X application 310. This request may be transmitted in a message 340. For example, V2X application 310-a may transmit a message 340-a that includes an indication of service requirements and a request for a DRX cycle in accordance with the service requirements. V2X applications 310-b and 310-c may transmit messages 340-b and 340-c, respectively, indicating the service requirements.

[0092] The V2X layer 305 may combine the service requirements and DRX cycle requests from each of the V2X applications 310-a, 310-b, and 310-c (or more) and may determine a common DRX cycle that is subject to each of the V2X applications 310. The V2X layer 305 may then request the V2X applications 310 to update the corresponding DRX cycles in a message 345. For example, the V2X application 310-b may already be using the determined common DRX cycle, but the V2X applications 310-a and 310-c may use different DRX cycles. Therefore, the V2X layer 305 may request the V2X applications 310-a and 310-c to update their DRX cycles. The V2X layer 305 may transmit requests to change the DRX cycles of the applications 310-a and 310-b in messages 345-a and 345-b, respectively. In an example where the V2X application 310 - b is already using a common DRX cycle, the V2X layer 305 may transmit an acknowledgement of the common DRX cycle in a message 345 - b .

[0093] Each V2X application 310 that receives a request from the V2X layer 305 to update its DRX cycle in message 345 may respond to the availability of the request by transmitting a response to the V2X layer 305 in message 350. For example, V2X applications 310-a and 310-c may transmit availability response messages 350-a and 350-b, respectively, to the V2X layer 305. The V2X layer 305 may then confirm the common DRX cycle to be followed by each of the V2X applications 310-a and 310-c by transmitting confirmation messages 355-a and 355-b, respectively. This confirmation may enable each V2X application 310-a and 310-c to determine the rate and periodicity at which to generate V2X data packets for sidelink transmission to other UEs 115. The V2X application 310-b may also determine the rate and periodicity of the generated V2X packets based on the confirmation message 345-b. The V2X layer 305 may also communicate an indication of the common DRX cycle to the lower layers SDAP 320, PDCP 325, RLC 330, and MAC / PHY 335. The UE 115 may then communicate with other UEs 115 on the sidelink using the common DRX cycle.

[0094] Figure 4 An example of a protocol stack 400 supporting transmission mode cycle alignment according to aspects of the present disclosure is illustrated. In some examples, the protocol stack 400 can implement aspects of wireless communication systems 100 and 200. The protocol stack 400 can include reference to Figure 1 and Figure 2 Components within the UE 115 are depicted. The protocol stack 400 may include a V2X layer 405, a plurality of V2X applications 410 (each including a V2X service 415). The V2X layer 405 may communicate with the V2X applications 410 via a middleware layer 440. The protocol stack may also include an SDAP 420, a PDCP 425, an RLC 430, and a MAC / PHY 435. Each of the SDAP 420, PDCP 425, RLC 430, and MAC / PHY 435 may be included in a user plane protocol stack of the UE 115. In some cases, the MAC / PHY 435 may be divided into different layers.

[0095] To determine a common DRX cycle for sidelink communications, in some cases, each V2X application 410 may negotiate among themselves rather than through the V2X layer 405. Each V2X application 410 is aware of its own service requirements, as well as the service requirements of each V2X service 415.

[0096] In scenarios where each V2X service of the application 410 operates on a different RAT or according to a different communication configuration, each V2X service 415 may operate according to a different DRX cycle.

[0097] For example, V2X service 415-a may communicate on a first RAT (e.g., LTE), while V2X service 415-b may communicate on a second RAT (e.g., NR). Thus, V2X service 415-a and V2X service 415-b may have different service requirements for their corresponding DRX cycles. In another example, V2X service 415-c may communicate in a unicast configuration, and V2X service 415-d may communicate in a multicast configuration. V2X service 415-c and V2X service 415-d may also have different service requirements resulting in different DRX cycles, which may also be different from the DRX cycles of V2X services 415-a, 415-b, 415-e, and 415-f.

[0098] Each V2X application 410 can therefore negotiate with all other V2X applications 410 to arrive at a common DRX cycle by aligning the DRX cycles of each V2X service 415 while also fairly distributing channel load to maximize power saving efficiency. Each V2X application 415 can then provide the determined common DRX cycle to the V2X layer 405. The V2X layer 405 can confirm the common DRX cycle. The V2X layer 405 can also pass the determined common DRX cycle down to the lower layers SDAP 420, PDCP 425, RLC 430, and MAC / PHY 435.

[0099] In some cases, negotiation of a common DRX cycle between V2X applications 410 may occur using a middleware layer 440. In this case, each middleware layer may receive service requirements from the corresponding V2X application 410 in signaling 445. Middleware layer 440-a may receive the service requirements from V2X application 410-a in signaling 445-a, middleware layer 440-b may receive the service requirements from V2X application 410-b in signaling 445-b, and middleware layer 440-c may receive the service requirements from V2X application 410-c in signaling 445-c. Middleware layer 440 may negotiate with other middleware layers 440 to determine a common DRX cycle. Middleware layer 440 may communicate with each other middleware layer 440 using signaling 450. Middleware layer 440 may transmit an indication of the common DRX cycle to V2X layer 405 in signaling 455. The V2X layer 405 may then pass the common DRX cycle down to the lower layers SDAP 420 , PDCP 425 , RLC 430 , and MAC / PHY 435 .

[0100] The UE 115 may thus determine a common DRX cycle between all application services to save battery and avoid large "on" periods caused by unsynchronized DRX cycles. The UE 115 may then communicate with other UEs 115 on the sidelink using the common DRX cycle.

[0101] Figure 5 An example of a process flow 500 for supporting transmission mode cycle alignment according to aspects of the present disclosure is illustrated. In some examples, the process flow 500 may implement aspects of wireless communication systems 100 and 200. The process flow 500 may include a UE 115-c, which may be as described with reference to FIG. Figures 1 to 4 The process flow 500 may also include a base station 105-b, which may be as described with reference to Figure 1 and 2 An example of a base station 105 is described. UE 115-c and base station 105-b can communicate on uplink and downlink communication links. UE 115-c can also communicate with other UEs 115 and other wireless devices on sidelinks (such as in a V2X communication system).

[0102] UE 115-c may determine to align a common DRX cycle with a DRX cycle used for communications with base station 105-b. The DRX cycle for communications between UE 115-c and base station 105-b may be an example of a Uu DRX cycle, a DRX cycle used for communications between a UE and a base station. In some cases, base station 105-b may configure the Uu DRX cycle. For example, UE 115-c may receive an indication of an additional set of DRX cycle parameters from base station 105-b, wherein the additional set of DRX cycle parameters is relevant to communications between UE 115-c and base station 105-b. UE 115-c may determine the common DRX cycle based on the indication.

[0103] In other cases, the base station 105-b may not configure the Uu DRX cycle for the UE 115-c. The UE 115-c may be configured with a common DRX cycle. The common DRX cycle may be based on the Uu DRX cycle as described herein. Figures 2 to 4 UE 115-c may transmit a request for a Uu DRX cycle to base station 105-b at 505. At 505, base station 105-b may receive a request for a DRX parameter set that satisfies the common DRX cycle of UE 115-c. The request for the Uu DRX cycle may be based on the common DRX cycle used for the sidelink and parameters associated with the common DRX cycle. The request for the Uu DRX cycle may be transmitted in an RRC connection request.

[0104] For example, UE 115-c may include a parameter set in the request. The parameters may include a sidelink traffic pattern for a particular DRX cycle or an explicit request for a particular DRX cycle. The parameters may also include an alignment indicator. The alignment indicator may indicate whether UE 115-c requests that the Uu DRX cycle be aligned with the common DRX cycle used for sidelink communication. In the event that UE 115-c sets the alignment indicator to true, base station 105-b may attempt to align the Uu DRX cycle with the indicated common DRX cycle of UE 115-c used for sidelink communication.

[0105] The parameters in the request may also include a flexibility indicator. The flexibility indicator may indicate whether the UE 115-c is flexible in modifying the common DRX cycle of the UE 115-c. In a scenario where the UE 115-c sets the flexibility indicator to "true", the UE 115-c may indicate to the base station 105-b that the base station 105-b does not have to strictly synchronize the Uu DRX cycle based on the common DRX cycle indicated by the UE 115-c. In addition, the flexibility indicator set to "true" may indicate that the common DRX cycle and the Uu DRX cycle determined by the base station 105-b do not have to completely overlap. If the UE 115-c sets the flexibility indicator to "false", the base station 105-b may provide the Uu DRX cycle to the UE 115-c so that the Uu DRX cycle partially overlaps or completely overlaps with the common DRX cycle.

[0106] For example, UE 115-c may also transmit a request to base station 105-b for an additional uplink DRX parameter set to be satisfied by the common DRX cycle. The request may be transmitted in an RRC configuration request. The request may include an alignment indicator that indicates whether the additional DRX cycle associated with the additional DRX parameter set is to be aligned with the common DRX cycle. The request may also include a flexibility indicator that indicates whether the UE 115-c is flexible in modifying the common DRX cycle. The request may also include an indication of a sidelink traffic pattern, an explicit indication of a common DRX cycle, or a combination thereof.

[0107] The base station 105-c may then transmit an acknowledgement of the Uu DRX cycle at 510. The base station 105-b may transmit an indication of the DRX cycle parameter set to the UE 115-c in response to the request from the UE 115-c at 505. The acknowledgement of the Uu DRX cycle may be transmitted in an RRC connection setup message.

[0108] In some cases, base station 105-b may have previously been provided with a Uu DRX cycle. In some cases, UE 115-c may take Uu DRX into account when determining the common DRX cycle to be used for the sidelink. UE 115-c may determine the common DRX cycle so that it partially overlaps or completely overlaps with the Uu DRX cycle. In other cases, UE 115-c may determine the common DRX cycle and may transmit a request for an updated Uu DRX cycle to base station 105-b. The request may include an indication of the common DRX cycle determined by UE 115-c.

[0109] For example, UE 115-c may determine that the common DRX cycle does not satisfy an additional DRX parameter set (e.g., defining a Uu DRX cycle). UE 115-c may then transmit a request to base station 105-b for an updated DRX cycle parameter set that is satisfied by the common DRX cycle. The request may be transmitted in an RRC reconfiguration message.

[0110] At 515, UE 115-c may transmit an acknowledgment of the determined Uu DRX cycle. Base station 105-b may receive an acknowledgment of the DRX cycle associated with the DRX parameter set (e.g., the Uu DRX cycle) from UE 115-c. UE 115-c may then monitor the communication channel between UE 115-c and base station 105-b using the Uu DRX cycle. UE 115-c may transmit communications to and receive communications from base station 105-b based on the Uu DRX cycle.

[0111] Figure 6 An example of a process flow 600 for supporting transmission mode cycle alignment according to aspects of the present disclosure is illustrated. In some examples, the process flow 600 may implement aspects of wireless communication systems 100 and 200, and protocol stacks 300 and 400. The UE 115-c may be as described with reference to FIG. Figures 1 to 5 An example of a UE 115 is depicted. The UE 115-d may include a processing layer 605 and applications 610. The processing layer 605 may be an example of a V2X layer 305 or 405. The applications 610 may be one or more applications, such as one or more V2X applications 310 or one or more V2X applications 410.

[0112] At 615, the UE 115-d may receive several DRX cycle parameter sets from a corresponding application (610) set at the application layer of the UE 115-d at a processing layer 605. The processing layer may be below the application layer and above the user plane protocol stack of the UE 115-d.

[0113] In some cases, the processing layer 605 may be a sidelink layer. The sidelink layer may include a V2X layer. In this case, at 615, the processing layer may receive each of the DRX cycle parameter sets via a corresponding DRX cycle request from the corresponding application 610. The request may include an indication of the service requirements of the corresponding application 610.

[0114] At 620, the UE 115-d may determine a common DRX cycle based on the plurality of DRX cycle parameter sets to satisfy each of the set of applications 610. The UE 15-d may determine a common DRX cycle parameter set that satisfies the individual DRX cycles associated with the plurality of DRX cycle parameter sets or satisfies the adjusted DRX cycle associated with the adjusted DRX cycle parameter set. In the case where the processing layer 605 is a sidelink layer, the processing layer 605 may determine an initial common DRX cycle based on the plurality of DRX cycle parameter sets.

[0115] In some cases, the processing layer 605 may determine that the initial common DRX cycle cannot satisfy at least one application in the set of applications 610. The processing layer 605 may transmit a request to the at least one application in the set of applications to update a corresponding DRX cycle parameter set so that the initial common DRX cycle satisfies the at least one application in the set of applications 610.

[0116] The processing layer 605 may receive a confirmation from at least one application in the application set 610 that the corresponding DRX parameter set has been updated so that the initial common DRX cycle satisfies the at least one application in the application set 610. The processing layer 605 may determine, based on the confirmation, that the common DRX cycle includes the initial common DRX cycle.

[0117] In addition, the processing layer 605 may receive a response from the at least one application in the application set (610) that the corresponding DRX cycle parameter set may not be updated. The processing layer 605 may adjust the initial common DRX cycle to the adjusted common DRX cycle based on the response. The processing layer 605 may transmit a request to the at least one application in the application set (610) to update the corresponding DRX cycle parameter set so that the adjusted common DRX cycle satisfies the at least one application in the application set (610). The processing layer 605 may receive a confirmation from the at least one application in the application set that the corresponding DRX cycle parameter set has been updated so that the adjusted common DRX cycle satisfies the at least one application in the application set. The processing layer 605 may determine, based on the confirmation, that the common DRX cycle includes the adjusted common DRX cycle.

[0118] In other cases, the processing layer 605 may be a set of middleware layers. The set of middleware layers may include one or more of the following: a V2X application enablement (VAE) layer, a service enabling architecture layer (SEAL), or both. The processing layer 605 may receive individual DRX parameter sets from corresponding applications 610 in the set of applications (610) at corresponding middleware layers in the set of middleware layers. At 620, the processing layer 605 may determine the common DRX cycle by negotiating a common DRX cycle between the set of applications (610) via corresponding middleware layers in the set of middleware layers. The common DRX cycle may be determined based on the negotiation. Negotiating the common DRX cycle may further include determining the common DRX cycle to improve power saving efficiency of the UE 115-d and to distribute channel load among the set of applications (610).

[0119] At 625, UE 115-d may communicate the common DRX cycle to one or more layers in the user plane protocol stack of UE 115-d. At 625, in the case where processing layer 605 is a V2X layer, processing layer 605 may communicate an acknowledgement of the common DRX cycle to one or more applications in the application set. At 625, in the case where processing layer 605 is a set of middleware layers, processing layer 605 may communicate the common DRX cycle to a sidelink layer for communication to one or more layers in the user plane protocol stack of UE 115-d.

[0120] UE 115-d may communicate with one or more other wireless communication devices based on the common DRX cycle. For example, UE 115-d may be a vehicle in a V2X communication system and may communicate with other vehicles on a sidelink channel based on the common DRX cycle. UE 115-d may also communicate using the common DRX cycle on different RATs or using unicast or broadcast transmissions, or a combination of these transmissions.

[0121] Figure 7 A block diagram 700 of a device 705 supporting transmission mode cycle alignment according to aspects of the present disclosure is shown. The device 705 can be an example of aspects of the UE 115 as described herein. The device 705 may include a receiver 710, a communication manager 715, and a transmitter 720. The device 705 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0122] The receiver 710 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmission mode cycle alignment, etc.). The information may be passed to other components of the device 705. The receiver 710 may be a reference Figure 10Examples of aspects of the transceiver 1020 are described. The receiver 710 may utilize a single antenna or a collection of antennas.

[0123] The communication manager 715 may receive a set of DRX cycle parameter sets from a corresponding application set at an application layer of the UE at a processing layer of the UE, wherein the processing layer is below the application layer and above the user plane protocol stack of the UE; determine a common DRX cycle based on the set of DRX cycle parameter sets to satisfy each of the application sets; and transmit the common DRX cycle to one or more layers in the user plane protocol stack of the UE. The communication manager 715 may be an example of various aspects of the communication manager 1010 described herein.

[0124] The communication manager 715 or its subcomponents may be implemented in hardware, in code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 715 or its subcomponents may be performed by 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 designed to perform the functions described in this disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0125] The communication manager 715 or its subcomponents can be physically located at various locations, including being distributed such that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 715 or its subcomponents can be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 715 or its subcomponents can be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0126] The transmitter 720 may transmit signals generated by other components of the device 705. In some examples, the transmitter 720 may be co-located with the receiver 710 in a transceiver. For example, the transmitter 720 may be a reference Figure 10 Examples of aspects of the described transceiver 1020. The transmitter 720 may utilize a single antenna or a collection of antennas.

[0127] In some examples, the communication manager 715 described herein can be implemented as a chipset for a wireless modem, while the receiver 710 and transmitter 720 can be implemented as a collection of analog components (e.g., amplifiers, filters, phase shifters, antennas, etc.). The wireless modem can obtain and decode a signal from the receiver 710 on a receive interface and can output a signal on a transmit interface for transmission to the transmitter 720.

[0128] The actions performed by the communication manager 715 as described herein may be implemented to achieve one or more potential advantages. One implementation may allow the UE 115 to save power and increase battery life by aligning the DRX cycles of different systems of the UE 115. This may therefore reduce the amount of time the UE 115 spends monitoring a channel for different applications, which may therefore save power.

[0129] Figure 8 A block diagram 800 is shown of a device 805 that supports transmission mode cycle alignment according to aspects of the present disclosure. The device 805 can be an example of aspects of the device 705 or UE 115 as described herein. The device 805 may include a receiver 810, a communication manager 815, and a transmitter 835. The device 805 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0130] The receiver 810 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmission mode cycle alignment, etc.). The information may be passed to other components of the device 805. The receiver 810 may be a reference Figure 10 Examples of aspects of the transceiver 1020 are described. The receiver 810 may utilize a single antenna or a collection of antennas.

[0131] Communications manager 815 can be an example of aspects of communications manager 715 as described herein. Communications manager 815 can include parameter component 820, loop determination component 825, and loop transmission component 830. Communications manager 815 can be an example of aspects of communications manager 1010 as described herein.

[0132] The parameter component 820 can receive a set of DRX cycle parameters from a corresponding application set at an application layer of the UE, wherein the processing layer is below the application layer and above the user plane protocol stack of the UE.

[0133] Cycle determination component 825 can determine a common DRX cycle based on the set of DRX cycle parameter sets to satisfy each of the set of applications.

[0134] Cyclic transmission component 830 can transmit the common DRX cycle to one or more layers in the user plane protocol stack of the UE.

[0135] The transmitter 835 can transmit signals generated by other components of the device 805. In some examples, the transmitter 835 can be co-located with the receiver 810 in a transceiver. For example, the transmitter 835 can be a reference Figure 10 Examples of aspects of the described transceiver 1020. The transmitter 835 may utilize a single antenna or a collection of antennas.

[0136] The processor of the UE 115 (eg, controlling the receiver 810, the transmitter 835 or as described in reference Figure 10 The described transceiver 1020 can save power by aligning the DRX cycles used by different applications and services of the UE 115. This can improve the efficiency of the UE 115 because the processor of the UE 115 reduces the amount of unnecessary "always on" time of the UE 115, thereby saving power while maintaining the reliability and service capabilities of the UE 115.

[0137] Figure 9 A block diagram 900 is shown of a communication manager 905 that supports transmission mode cycle alignment according to aspects of the present disclosure. The communication manager 905 can be an example of aspects of the communication manager 715, the communication manager 815, or the communication manager 1010 described herein. The communication manager 905 can include a parameter component 910, a cycle determination component 915, a cycle transmission component 920, a communication component 925, a request component 930, an acknowledgement component 935, and a cycle adjustment component 940. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0138] The parameter component 910 can receive a set of DRX cycle parameter sets from a corresponding application set at an application layer of the UE, wherein the processing layer is below the application layer and above the user plane protocol stack of the UE.

[0139] In some examples, parameter component 910 can receive a response from the at least one application in the application set that the corresponding DRX cycle parameter set will not be updated.

[0140] In some examples, parameter component 910 can receive individual DRX cycle parameter sets from corresponding applications in the set of applications at corresponding middleware layers in the set of middleware layers.

[0141] In some examples, parameter component 910 may receive an indication of an additional DRX cycle parameter set from a base station, wherein the additional DRX cycle parameter set is related to communication between the UE and the base station; and wherein determining the common DRX cycle is further based on the indication.

[0142] In some examples, parameter component 910 can receive an indication of an additional set of DRX cycle parameters from a base station, where the additional set of DRX cycle parameters is related to communications between the UE and the base station.

[0143] In some examples, parameter component 910 can transmit a request to the base station for an updated set of additional DRX cycle parameters satisfied by the common DRX cycle.

[0144] In some examples, parameter component 910 can transmit the request in an RRC reconfiguration message.

[0145] In some examples, parameter component 910 can transmit a request to the base station for an additional uplink DRX cycle parameter set to be satisfied by the common DRX cycle.

[0146] In some examples, parameter component 910 can transmit the request in an RRC configuration request.

[0147] In some cases, the set of middleware layers includes one or more of the following: an Internet of Vehicles application enabling layer, or a vertical service enabling architecture layer, or both.

[0148] In some cases, the request includes an alignment indicator that indicates whether the additional DRX cycle associated with the additional DRX cycle parameter set is to be aligned with the common DRX cycle.

[0149] In some cases, the request includes a flexibility indicator that indicates whether the UE is flexible in modifying the common DRX cycle.

[0150] In some cases, the request includes an indication of a sidelink traffic pattern, an explicit indication of the common DRX cycle, or a combination thereof.

[0151] Cycle determination component 915 can determine a common DRX cycle based on the set of DRX cycle parameter sets to satisfy each of the set of applications.

[0152] In some examples, cycle determining component 915 can determine a set of common DRX cycle parameters that satisfy individual DRX cycles associated with the group of DRX cycle parameter sets or satisfy an adjusted DRX cycle associated with an adjusted DRX cycle parameter set.

[0153] In some examples, cycle determining component 915 can determine an initial common DRX cycle based on the set of DRX cycle parameter sets.

[0154] In some examples, cycle determining component 915 can determine that the initial common DRX cycle cannot satisfy at least one application in the application set.

[0155] In some examples, determining the common DRX cycle based on the confirmation includes the initial common DRX cycle.

[0156] In some examples, determining the common DRX cycle based on the confirmation includes an adjusted common DRX cycle.

[0157] In some examples, cycle determining component 915 can negotiate a common DRX cycle between the set of applications via corresponding middleware layers in the set of middleware layers.

[0158] In some examples, cycle determining component 915 can determine the common DRX cycle based on the negotiation.

[0159] In some examples, cycle determining component 915 can determine the common DRX cycle to facilitate improving power saving efficiency of the UE and to facilitate distributing channel load among the application set.

[0160] In some examples, cycle determining component 915 can determine that the common DRX cycle does not satisfy the additional DRX cycle parameter set.

[0161] Cyclic transmission component 920 can transmit the common DRX cycle to one or more layers in the user plane protocol stack of the UE.

[0162] In some examples, cyclic transmission component 920 can transmit the common DRX cycle to the sidelink layer for transmission to one or more layers in the user plane protocol stack of the UE.

[0163] The communication component 925 can be used by the UE to communicate with one or more other wireless communication devices according to the common DRX cycle.

[0164] Requesting component 930 can receive each DRX cycle parameter set in the set of DRX cycle parameter sets via a respective DRX cycle request from a corresponding application.

[0165] In some examples, request component 930 can transmit a request to the at least one application in the application set to update a corresponding DRX cycle parameter set so that the initial common DRX cycle satisfies the at least one application in the application set.

[0166] In some examples, request component 930 can transmit a request to the at least one application in the application set to update a corresponding DRX cycle parameter set so that the adjusted common DRX cycle satisfies the at least one application in the application set.

[0167] In some cases, the respective DRX cycle request includes an indication of the service requirements of the corresponding application.

[0168] In some cases, the sidelink layer includes a vehicle networking layer.

[0169] Confirmation component 935 can receive a confirmation from the at least one application in the application set that the corresponding DRX cycle parameter set has been updated so that the initial common DRX cycle satisfies the at least one application in the application set.

[0170] In some examples, confirmation component 935 can receive confirmation from the at least one application in the application set that the corresponding DRX cycle parameter set has been updated so that the adjusted common DRX cycle satisfies the at least one application in the application set.

[0171] In some examples, confirmation component 935 can transmit confirmation of the common DRX cycle to one or more applications in the application set.

[0172] Cycle adjustment component 940 can adjust the initial common DRX cycle to an adjusted common DRX cycle based on the response.

[0173] Figure 10 A diagram of a system 1000 including a device 1005 that supports transmission mode cycle alignment according to aspects of the present disclosure is shown. The device 1005 can be an example of, or include a component of, a device 705, a device 805, or a UE 115 as described herein. The device 1005 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a communication manager 1010, an I / O controller 1015, a transceiver 1020, an antenna 1025, a memory 1030, and a processor 1040. These components can be in electronic communication via one or more buses (e.g., bus 1045).

[0174] The communication manager 1010 may receive, at a processing layer of the UE, a set of DRX cycle parameter sets from a corresponding application set at an application layer of the UE, wherein the processing layer is below the application layer and above the user plane protocol stack of the UE; determine a common DRX cycle based on the set of DRX cycle parameter sets to satisfy each of the application sets; and transmit the common DRX cycle to one or more layers in the user plane protocol stack of the UE.

[0175] I / O controller 1015 can manage input and output signals for device 1005. I / O controller 1015 can also manage peripheral devices that are not integrated into device 1005. In some cases, I / O controller 1015 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1015 can utilize an operating system, such as or another known operating system. In other cases, I / O controller 1015 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 1015 may be implemented as part of a processor. In some cases, a user may interact with device 1005 via I / O controller 1015 or via hardware components controlled by I / O controller 1015.

[0176] The transceiver 1020 can communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, the transceiver 1020 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1020 can also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and demodulate packets received from the antenna.

[0177] In some cases, a wireless device may include a single antenna 1025. However, in some cases, the device may have more than one antenna 1025, which may be capable of transmitting or receiving multiple wireless transmissions concurrently.

[0178] Memory 1030 may include random access memory (RAM) and read-only memory (ROM). Memory 1030 may store computer-readable, computer-executable code 1035 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, memory 1030 may include, among other things, a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0179] The processor 1040 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, the processor 1040 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into the processor 1040. The processor 1040 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1030) to cause the device 1005 to perform various functions (e.g., functions or tasks that support transfer mode cycle alignment).

[0180] The code 1035 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1035 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, the code 1035 may not be directly executed by the processor 1040, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0181] Figure 11 A block diagram 1100 is shown of a device 1105 that supports transmission mode cycle alignment according to aspects of the present disclosure. The device 1105 can be an example of aspects of the base station 105 as described herein. The device 1105 can include a receiver 1110, a communication manager 1115, and a transmitter 1120. The device 1105 can also include a processor. Each of these components can be in communication with each other (e.g., via one or more buses).

[0182] The receiver 1110 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmission mode cycle alignment, etc.). The information may be passed to other components of the device 1105. The receiver 1110 may be a reference Figure 14 Examples of various aspects of the transceiver 1420 are described. The receiver 1110 may utilize a single antenna or a collection of antennas.

[0183] The communication manager 1115 may receive a request from a UE for a DRX cycle parameter set that satisfies a common DRX cycle for the UE; transmit an indication of the DRX cycle parameter set to the UE in response to the request; and receive a confirmation of the DRX cycle associated with the DRX cycle parameter set from the UE. The communication manager 1115 may be an example of aspects of the communication manager 1410 described herein.

[0184] The communication manager 1115 or its subcomponents may be implemented in hardware, in code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 1115 or its subcomponents may be performed by a general-purpose processor, a DSP, an application-specific integrated circuit (ASIC), an FPGA or other programmable logic device designed to perform the functions described in this disclosure, discrete gate or transistor logic, discrete hardware components, or any combination thereof.

[0185] The communication manager 1115 or its subcomponents can be physically located at various locations, including being distributed such that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 1115 or its subcomponents can be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 1115 or its subcomponents can be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0186] The transmitter 1120 may transmit signals generated by other components of the device 1105. In some examples, the transmitter 1120 may be co-located with the receiver 1110 in a transceiver. For example, the transmitter 1120 may be a reference Figure 14 Examples of aspects of the described transceiver 1420. The transmitter 1120 may utilize a single antenna or a collection of antennas.

[0187] Figure 12 A block diagram 1200 is shown of a device 1205 that supports transmission mode cycle alignment according to aspects of the present disclosure. The device 1205 can be an example of aspects of the device 1105 or base station 105 as described herein. The device 1205 may include a receiver 1210, a communication manager 1215, and a transmitter 1235. The device 1205 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0188] The receiver 1210 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to transmission mode cycle alignment, etc.). The information may be passed to other components of the device 1205. The receiver 1210 may be a reference Figure 14 Examples of various aspects of the transceiver 1420 are described. The receiver 1210 may utilize a single antenna or a collection of antennas.

[0189] Communications manager 1215 can be an example of aspects of communications manager 1115 as described herein. Communications manager 1215 can include parameter requesting component 1220, parameter indicating component 1225, and confirmation receiving component 1230. Communications manager 1215 can be an example of aspects of communications manager 1410 as described herein.

[0190] Parameter requesting component 1220 can receive a request from a UE for a set of DRX cycle parameters that satisfies a common DRX cycle for the UE.

[0191] Parameter indicating component 1225 can transmit an indication of the DRX cycle parameter set to the UE in response to the request.

[0192] Acknowledgement receiving component 1230 can receive, from the UE, an acknowledgement of the DRX cycle associated with the DRX cycle parameter set.

[0193] The transmitter 1235 may transmit signals generated by other components of the device 1205. In some examples, the transmitter 1235 may be co-located with the receiver 1210 in a transceiver. For example, the transmitter 1235 may be a reference Figure 14 Examples of various aspects of the described transceiver 1420. The transmitter 1235 may utilize a single antenna or a collection of antennas.

[0194] Figure 13 A block diagram 1300 is shown of a communication manager 1305 that supports transmission mode cycle alignment according to aspects of the present disclosure. The communication manager 1305 can be an example of aspects of the communication manager 1115, the communication manager 1215, or the communication manager 1410 described herein. The communication manager 1305 can include a transmission request component 1310, a parameter indication component 1315, and an acknowledgment reception component 1320. Each of these components can communicate with each other directly or indirectly (e.g., via one or more buses).

[0195] Parameter requesting component 1310 can receive a request from a UE for a set of DRX cycle parameters that satisfies a common DRX cycle for the UE.

[0196] In some examples, parameter requesting component 1310 can receive the request in an RRC configuration request.

[0197] In some examples, parameter requesting component 1310 may receive a request from the UE for an updated set of additional DRX cycle parameters satisfied by the common DRX cycle.

[0198] In some examples, parameter requesting component 1310 may receive a request from the UE for an additional uplink DRX cycle parameter set to be satisfied by the common DRX cycle.

[0199] In some cases, the request includes an alignment indicator that indicates whether the additional DRX cycle associated with the additional DRX cycle parameter set is to be aligned with the common DRX cycle.

[0200] In some cases, the request includes a flexibility indicator that indicates whether the UE is flexible in modifying the common DRX cycle.

[0201] In some cases, the request includes an indication of a sidelink traffic pattern, an explicit indication of the common DRX cycle, or a combination thereof.

[0202] Parameter indicating component 1315 can transmit an indication of the DRX cycle parameter set to the UE in response to the request.

[0203] In some examples, parameter indicating component 1315 may transmit an indication of an additional set of DRX cycle parameters to the UE, where the additional set of DRX cycle parameters is related to communication between the UE and the base station.

[0204] In some examples, parameter indicating component 1315 can transmit to the UE an updated set of additional DRX cycle parameters satisfied by the common DRX cycle.

[0205] Acknowledgement receiving component 1320 can receive, from the UE, an acknowledgement of the DRX cycle associated with the DRX cycle parameter set.

[0206] Figure 14 A diagram of a system 1400 including a device 1405 that supports transmission mode cycle alignment according to aspects of the present disclosure is shown. Device 1405 can be an example of, or include components of, device 1105, device 1205, or base station 105 as described herein. Device 1405 may include components for two-way voice and data communications, including components for transmitting and receiving communications, including a communication manager 1410, a network communication manager 1415, a transceiver 1420, an antenna 1425, a memory 1430, a processor 1440, and an inter-station communication manager 1445. These components can be in electronic communication via one or more buses (e.g., bus 1450).

[0207] The communication manager 1410 may receive a request from a UE for a DRX cycle parameter set that satisfies a common DRX cycle of the UE; transmit an indication of the DRX cycle parameter set to the UE in response to the request; and receive confirmation of a DRX cycle associated with the DRX cycle parameter set from the UE.

[0208] The network communications manager 1415 may manage communications with the core network (eg, via one or more wired backhaul links). For example, the network communications manager 1415 may manage the delivery of data communications for client devices, such as one or more UEs 115.

[0209] The transceiver 1420 can communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, the transceiver 1420 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 1420 can also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and demodulate packets received from the antenna.

[0210] In some cases, a wireless device may include a single antenna 1425. However, in some cases, the device may have more than one antenna 1425, which may be capable of transmitting or receiving multiple wireless transmissions concurrently.

[0211] Memory 1430 may include RAM, ROM, or a combination thereof. Memory 1430 may store computer-readable code 1435 including instructions that, when executed by a processor (e.g., processor 1440), cause the device to perform the various functions described herein. In some cases, memory 1430 may include, among other things, a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0212] Processor 1440 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1440 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1440. Processor 1440 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1430) to cause device 1405 to perform various functions (e.g., functions or tasks that support transfer mode cycle alignment).

[0213] The inter-site communication manager 1445 can manage communications with other base stations 105 and can include a controller or scheduler for controlling communications with the UE 115 in cooperation with the other base stations 105. For example, the inter-site communication manager 1445 can coordinate the scheduling of transmissions to the UE 115 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, the inter-site communication manager 1445 can provide an X2 interface within an LTE / LTE-A wireless communication network technology to provide communications between the base stations 105.

[0214] The code 1435 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 1435 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, the code 1435 may not be directly executed by the processor 1440, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0215] Figure 15 1500 according to various aspects of the present disclosure. The operations of the method 1500 may be implemented by the UE 115 or its components as described herein. For example, the operations of the method 1500 may be implemented by the UE 115 or its components as described herein. Figures 7 to 10 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.

[0216] At 1505, the UE may receive a set of DRX cycle parameter sets from a corresponding application set at an application layer of the UE, wherein the processing layer is below the application layer and above the user plane protocol stack of the UE. The operations of 1505 may be performed according to the methods described herein. In some examples, aspects of the operations of 1505 may be as described with reference to Figures 7 to 10Describes the parameters component to execute.

[0217] At 1510, the UE may determine a common DRX cycle to satisfy each of the application sets based on the set of DRX cycle parameters. The operations of 1510 may be performed according to the methods described herein. In some examples, aspects of the operations of 1510 may be as described with reference to Figures 7 to 10 The described loop determines the components to execute.

[0218] At 1515, the UE may transmit the common DRX cycle to one or more layers in the user plane protocol stack of the UE. The operations of 1515 may be performed according to the methods described herein. In some examples, aspects of the operations of 1515 may be as described with reference to Figures 7 to 10 The described cyclic transmission component is executed.

[0219] Figure 16 16. A flow chart of a method 1600 for supporting transmission mode cycle alignment according to aspects of the present disclosure is shown. The operations of the method 1600 may be implemented by the UE 115 or components thereof as described herein. For example, the operations of the method 1600 may be implemented by the UE 115 or components thereof as described herein. Figures 7 to 10 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.

[0220] At 1605, the UE may receive a set of DRX cycle parameter sets from a corresponding application set at an application layer of the UE, wherein the processing layer is below the application layer and above the user plane protocol stack of the UE. The operations of 1605 may be performed according to the methods described herein. In some examples, aspects of the operations of 1605 may be performed as described with reference to Figures 7 to 10 Describes the parameters component to execute.

[0221] At 1610, the UE may receive each DRX cycle parameter set in the set of DRX cycle parameter sets via a corresponding DRX cycle request from a corresponding application. The operations of 1610 may be performed according to the methods described herein. In some examples, aspects of the operations of 1610 may be as described with reference to Figures 7 to 10 Describes the request component to execute.

[0222] At 1615, the UE may determine a common DRX cycle to satisfy each of the application sets based on the set of DRX cycle parameters. The operations of 1615 may be performed according to the methods described herein. In some examples, aspects of the operations of 1615 may be as described with reference to Figures 7 to 10 The described loop determines the components to execute.

[0223] At 1620, the UE may transmit the common DRX cycle to one or more layers in the user plane protocol stack of the UE. The operations of 1620 may be performed according to the methods described herein. In some examples, aspects of the operations of 1620 may be as described with reference to Figures 7 to 10 The described cyclic transmission component is executed.

[0224] Figure 17 1700 according to various aspects of the present disclosure. The operations of the method 1700 may be implemented by the UE 115 or its components as described herein. For example, the operations of the method 1600 may be implemented by the UE 115 or its components as described herein. Figures 7 to 10 In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described herein. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described herein.

[0225] At 1705, the UE may receive a set of DRX cycle parameter sets from a corresponding application set at an application layer of the UE, wherein the processing layer is below the application layer and above the user plane protocol stack of the UE. The operations of 1705 may be performed according to the methods described herein. In some examples, aspects of the operations of 1705 may be performed as described with reference to Figures 7 to 10 Describes the parameters component to execute.

[0226] At 1710, the UE may receive an individual DRX cycle parameter set from a corresponding application in the application set at a corresponding middleware layer in the middleware layer set. The operations of 1710 may be performed according to the methods described herein. In some examples, aspects of the operations of 1710 may be as described with reference to Figures 7 to 10 Describes the parameters component to execute.

[0227] At 1715, the UE may determine a common DRX cycle to satisfy each of the application sets based on the set of DRX cycle parameters. The operations of 1715 may be performed according to the methods described herein. In some examples, aspects of the operations of 1715 may be as described with reference to Figures 7 to 10 The described loop determines the components to execute.

[0228] At 1720, the UE may transmit the common DRX cycle to one or more layers in the user plane protocol stack of the UE. The operations of 1720 may be performed according to the methods described herein. In some examples, aspects of the operations of 1720 may be as described with reference to Figures 7 to 10 The described cyclic transmission component is executed.

[0229] Figure 181800 according to various aspects of the present disclosure. The operations of the method 1800 may be implemented by the base station 105 or its components as described herein. For example, the operations of the method 1600 may be implemented by the base station 105 or its components as described herein. Figures 11 to 14 In some examples, a base station may execute an instruction set to control functional elements of the base station to perform the functions described herein. Additionally or alternatively, a base station may use dedicated hardware to perform various aspects of the functions described herein.

[0230] At 1805, the base station may receive a request from a UE for a set of DRX cycle parameters that satisfies a common DRX cycle for the UE. The operations of 1805 may be performed according to the methods described herein. In some examples, aspects of the operations of 1805 may be as described with reference to Figures 11 to 14 Describes the parameters that request the component to execute.

[0231] At 1810, the base station may transmit an indication of the DRX cycle parameter set to the UE in response to the request. The operations of 1810 may be performed according to the methods described herein. In some examples, aspects of the operations of 1810 may be as described with reference to Figures 11 to 14 The parameters described instruct the component to execute.

[0232] At 1815, the base station may receive a confirmation of the DRX cycle associated with the DRX cycle parameter set from the UE. The operations of 1815 may be performed according to the methods described herein. In some examples, aspects of the operations of 1815 may be as described with reference to Figures 11 to 14 Described confirmation receiving component to perform.

[0233] The following provides an overview of various aspects of the disclosure:

[0234] Aspect 1: A method for wireless communication at a UE, comprising: receiving, at a processing layer of the UE, multiple DRX cycle parameter sets from corresponding multiple applications at an application layer of the UE, wherein the processing layer is below the application layer and above the user plane protocol stack of the UE; determining a common DRX cycle based at least in part on the multiple DRX cycle parameter sets to satisfy each application in the multiple applications; and transmitting the common DRX cycle to one or more layers in the user plane protocol stack of the UE.

[0235] Aspect 2: A method as in Aspect 1, wherein determining the common DRX cycle includes: determining a common DRX cycle parameter set, wherein these common DRX cycle parameters satisfy individual DRX cycles associated with multiple DRX cycle parameter sets or satisfy an adjusted DRX cycle associated with an adjusted DRX cycle parameter set.

[0236] Aspect 3: The method according to any one of aspects 1 to 2 further comprises: communicating, by the UE, with one or more other wireless communication devices according to the common DRX cycle.

[0237] Aspect 4: A method as in any one of Aspects 1 to 3, wherein: the processing layer is a side link layer, wherein receiving the multiple DRX cycle parameter sets from the corresponding multiple applications includes: receiving each DRX cycle parameter set in the multiple DRX cycle parameter sets via a corresponding DRX cycle request from the corresponding application.

[0238] Aspect 5: The method of aspect 4, wherein determining the common DRX cycle further comprises: determining an initial common DRX cycle based at least in part on the multiple DRX cycle parameter sets.

[0239] Aspect 6: The method of Aspect 5 further includes: determining that the initial common DRX cycle cannot satisfy at least one application among the multiple applications; and transmitting a request to the at least one application among the multiple applications to update the corresponding DRX cycle parameter set so that the initial common DRX cycle satisfies the at least one application among the multiple applications.

[0240] Aspect 7: The method of Aspect 6 further includes: receiving a confirmation from at least one application among the multiple applications that the corresponding DRX cycle parameter set has been updated so that the initial common DRX cycle satisfies the at least one application among the multiple applications; and determining, at least in part based on the confirmation, that the common DRX cycle includes the initial common DRX cycle.

[0241] Aspect 8: The method of any one of Aspects 6 to 7 further includes: receiving a response from the at least one application among the multiple applications that the corresponding DRX cycle parameter set will not be updated; adjusting the initial common DRX cycle to an adjusted common DRX cycle based at least in part on the response; transmitting to the at least one application among the multiple applications a request to update the corresponding DRX cycle parameter set so that the adjusted common DRX cycle satisfies the at least one application among the multiple applications; receiving from the at least one application among the multiple applications a confirmation that the corresponding DRX cycle parameter set has been updated so that the adjusted common DRX cycle satisfies the at least one application among the multiple applications; and determining, based at least in part on the confirmation, that the common DRX cycle includes the adjusted common DRX cycle.

[0242] Aspect 9: The method according to any one of aspects 5 to 8, further comprising: transmitting a confirmation of the common DRX cycle to one or more applications of the plurality of applications.

[0243] Aspect 10: The method according to any one of aspects 4 to 9, wherein: the corresponding DRX cycle request includes an indication of a service requirement of the corresponding application.

[0244] Aspect 11: The method according to any one of Aspects 4 to 10, wherein: the side link layer includes a vehicle network layer.

[0245] Aspect 12: A method as described in any one of Aspects 1 to 11, wherein: the processing layer is a plurality of middleware layers, wherein receiving the plurality of DRX cycle parameter sets from the corresponding plurality of applications includes: a corresponding middleware layer in the plurality of middleware layers receiving an individual DRX cycle parameter set from a corresponding application in the plurality of applications.

[0246] Aspect 13: The method of aspect 12, wherein determining the common DRX cycle further comprises: negotiating a common DRX cycle between the plurality of applications via corresponding middleware layers among the plurality of middleware layers; and determining the common DRX cycle based at least in part on the negotiation.

[0247] Aspect 14: The method of aspect 13 further comprises: transmitting the common DRX cycle to a side link layer for transmission to one or more layers in a user plane protocol stack of the UE.

[0248] Aspect 15: The method according to any one of aspects 13 to 14, wherein: negotiating the common DRX cycle comprises: determining the common DRX cycle so as to improve the power saving efficiency of the UE and to distribute the channel load among the multiple applications.

[0249] Aspect 16: The method according to any one of Aspects 12 to 15, wherein: the plurality of middleware layers include one or more of the following: an Internet of Vehicles application enabling layer, or a vertical service enabling architecture layer, or both.

[0250] Aspect 17: The method of any one of Aspects 1 to 16 further includes: receiving an indication of an additional DRX cycle parameter set from a base station, wherein the additional DRX cycle parameter set is related to the communication between the UE and the base station; and wherein determining the common DRX cycle is further based at least in part on the indication.

[0251] Aspect 18: The method of any one of Aspects 1 to 17 further includes: receiving an indication of an additional DRX cycle parameter set from a base station, wherein the additional DRX cycle parameter set is related to the communication between the UE and the base station; determining that the common DRX cycle does not satisfy the additional DRX cycle parameter set; and transmitting a request to the base station for an updated additional DRX cycle parameter set satisfied by the common DRX cycle.

[0252] Aspect 19: The method of Aspect 18, wherein transmitting the request comprises: transmitting the request in an RRC reconfiguration message.

[0253] Aspect 20: The method of any one of aspects 1 to 19, further comprising: transmitting a request to the base station for an additional uplink DRX cycle parameter set to be satisfied by the common DRX cycle.

[0254] Aspect 21: The method of Aspect 20, wherein transmitting the request comprises: transmitting the request in an RRC configuration request.

[0255] Aspect 22: The method of any one of aspects 20 to 21, wherein: the request includes an alignment indicator, the alignment indicator indicating whether the additional DRX cycle associated with the additional uplink DRX cycle parameter set is to be aligned with the common DRX cycle.

[0256] Aspect 23: The method of any one of aspects 20 to 22, wherein: the request includes a flexibility indicator, the flexibility indicator indicating whether the UE is flexible in modifying the common DRX cycle.

[0257] Aspect 24: The method of any one of aspects 20 to 23, wherein: the request comprises an indication of a sidelink traffic pattern, an explicit indication of the common DRX cycle, or a combination thereof.

[0258] Aspect 25: A method for wireless communication at a base station, comprising: receiving a request from a UE for a DRX cycle parameter set that satisfies a common DRX cycle of the UE; transmitting an indication of the DRX cycle parameter set to the UE in response to the request; and receiving a confirmation of the DRX cycle associated with the DRX cycle parameter set from the UE.

[0259] Aspect 26: The method of Aspect 25, wherein receiving the request comprises: receiving the request in an RRC configuration request.

[0260] Aspect 27: The method of any one of Aspects 25 to 26 further includes: transmitting an indication of an additional DRX cycle parameter set to the UE, wherein the additional DRX cycle parameter set is related to the communication between the UE and the base station; receiving a request for an updated additional DRX cycle parameter set satisfied by the common DRX cycle from the UE; and transmitting the updated additional DRX cycle parameter set satisfied by the common DRX cycle to the UE.

[0261] Aspect 28: The method of any one of aspects 25 to 27, further comprising: receiving a request from the UE for an additional uplink DRX cycle parameter set to be satisfied by the common DRX cycle.

[0262] Aspect 29: The method of aspect 28, wherein the request includes an alignment indicator, the alignment indicator indicating whether the additional DRX cycle associated with the additional uplink DRX cycle parameter set is to be aligned with the common DRX cycle.

[0263] Aspect 30: The method according to any one of aspects 28 to 29, wherein: the request includes a flexibility indicator, the flexibility indicator indicating whether the UE is flexible in modifying the common DRX cycle.

[0264] Aspect 31: The method of any one of Aspects 28 to 30, wherein: the request comprises an indication of a sidelink traffic pattern, an explicit indication of the common DRX cycle, or a combination thereof.

[0265] Aspect 32: An apparatus for wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of any one of aspects 1 to 24.

[0266] Aspect 33: An apparatus for wireless communication at a UE, comprising at least one means for performing the method of any one of aspects 1 to 24.

[0267] Aspect 34: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method of any one of aspects 1 to 24.

[0268] Aspect 35: An apparatus for performing wireless communication at a base station, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method as in any one of Aspects 25 to 31.

[0269] Aspect 36: An apparatus for wireless communication at a base station, comprising at least one means for performing the method of any one of Aspects 25 to 31.

[0270] Aspect 37: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform the method of any one of aspects 25 to 31.

[0271] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0272] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used throughout much of the description, the techniques described herein may also be applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0273] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout this description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0274] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0275] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Other examples and implementations fall within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including being distributed so that parts of the functions are implemented at different physical locations.

[0276] Computer readable medium includes both non-transient computer storage medium and communication medium, and it includes any medium that facilitates a computer program to be transferred from one place to another.Non-transient storage medium can be any available medium that can be accessed by a general or special-purpose computer.As an example and not limitation, non-transient computer readable medium may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, magnetic disc storage or other magnetic storage device, or can be used to carry or store the desired program code means of instruction or data structure form and can be accessed by a general or special-purpose computer, or any other non-transient medium of a general or special-purpose processor. As used herein, disk (disk) and dish (disc) include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and blue-ray disc, wherein the dish often reproduces data magnetically and the dish reproduces data optically with laser. The combination of the above media is also included in the scope of computer readable medium.

[0277] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Likewise, as used herein, the phrase "based on" should not be read as referencing a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be read in the same manner as the phrase "based at least in part on."

[0278] In the accompanying drawings, similar components or features may have the same reference number. In addition, components of the same type may be distinguished by following the reference number with a dash and a second reference number that distinguishes between the similar components. If only the first reference number is used in the specification, the description applies to any of the similar components having the same first reference number, regardless of the second reference number or other subsequent reference numbers.

[0279] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that can be implemented or fall within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and does not mean "better than" or "better than other examples." This detailed description includes specific details to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0280] The description herein is provided to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: receiving, at a processing layer of the UE, a plurality of discontinuous reception cycle parameter sets from corresponding plurality of applications at an application layer of the UE, wherein the processing layer is below the application layer and above a user plane protocol stack of the UE; determining a common discontinuous reception cycle to satisfy each of the plurality of applications based at least in part on the plurality of discontinuous reception cycle parameter sets; transmitting a request for an additional uplink discontinuous reception cycle parameter set to be satisfied by the common discontinuous reception cycle; as well as The common discontinuous reception cycle is transmitted to one or more layers in the user plane protocol stack of the UE.

2. The method of claim 1 , wherein determining the common DRX cycle comprises: A common set of DRX cycle parameters is determined that satisfies the individual DRX cycles associated with the plurality of DRX cycle parameter sets or satisfies the adjusted DRX cycle associated with the adjusted DRX cycle parameter set.

3. The method of claim 1, further comprising: The UE communicates with one or more other wireless communication devices according to the common discontinuous reception cycle.

4. The method of claim 1 , wherein the processing layer is a side link layer, wherein receiving the plurality of DRX cycle parameter sets from the corresponding plurality of applications comprises: Each discontinuous reception cycle parameter set of the plurality of discontinuous reception cycle parameter sets is received via a respective discontinuous reception cycle request from a corresponding application.

5. The method of claim 4 , wherein determining the common DRX cycle further comprises: An initial common discontinuous reception cycle is determined based at least in part on the plurality of discontinuous reception cycle parameter sets.

6. The method of claim 5, further comprising: determining that the initial common discontinuous reception cycle cannot satisfy at least one application among the plurality of applications; as well as A request is transmitted to the at least one application of the plurality of applications to update a corresponding DRX cycle parameter set so that the initial common DRX cycle satisfies the at least one application of the plurality of applications.

7. The method of claim 6, further comprising: receiving a confirmation from the at least one application of the plurality of applications that the corresponding DRX cycle parameter set has been updated so that the initial common DRX cycle satisfies the at least one application of the plurality of applications; as well as The common discontinuous reception cycle is determined to include the initial common discontinuous reception cycle based at least in part on the confirmation.

8. The method of claim 6, further comprising: receiving a response from the at least one application of the plurality of applications that the corresponding DRX cycle parameter set will not be updated; Based at least in part on the response, adjusting the initial common discontinuous reception cycle to an adjusted common discontinuous reception cycle; transmitting, to the at least one application of the plurality of applications, a request to update a corresponding DRX cycle parameter set so that the adjusted common DRX cycle satisfies the at least one application of the plurality of applications; receiving a confirmation from the at least one application of the plurality of applications that the corresponding DRX cycle parameter set has been updated so that the adjusted common DRX cycle satisfies the at least one application of the plurality of applications; as well as Determining the common discontinuous reception cycle based at least in part on the confirmation includes the adjusted common discontinuous reception cycle.

9. The method of claim 5, further comprising: An acknowledgement of the common discontinuous reception cycle is transmitted to one or more applications of the plurality of applications.

10. The method of claim 4, wherein the corresponding DRX cycle request includes an indication of a service requirement of a corresponding application. The method of claim 4 , wherein the side link layer comprises a vehicle networking layer.

12. The method of claim 1 , wherein the processing layers are a plurality of middleware layers, wherein receiving the plurality of DRX cycle parameter sets from the corresponding plurality of applications comprises: A corresponding middleware layer among the plurality of middleware layers receives an individual discontinuous reception cycle parameter set from a corresponding application among the plurality of applications.

13. The method of claim 12, wherein determining the common DRX cycle further comprises: negotiating the common discontinuous reception cycle between the plurality of applications via corresponding middleware layers among the plurality of middleware layers; as well as The common discontinuous reception cycle is determined based at least in part on the negotiation.

14. The method of claim 13, further comprising: The common discontinuous reception cycle is transmitted to a sidelink layer for transmission to the one or more layers in the user plane protocol stack of the UE.

15. The method of claim 13 , wherein negotiating the common DRX cycle comprises: The common discontinuous reception cycle is determined so as to improve power saving efficiency of the UE and to distribute channel load among the multiple applications. 16 . The method of claim 12 , wherein the plurality of middleware layers comprise one or more of the following: an IoV application enabling layer, or a vertical service enabling architecture layer, or both.

17. The method of claim 1, further comprising: An indication of an additional set of discontinuous reception cycle parameters is received, wherein the additional set of discontinuous reception cycle parameters is related to communications between the UE and a network node, and wherein determining the common discontinuous reception cycle is further based at least in part on the indication.

18. The method of claim 1, further comprising: receiving an indication of an additional set of discontinuous reception cycle parameters, wherein the additional set of discontinuous reception cycle parameters is related to communication between the UE and a network node; determining that the common DRX cycle does not satisfy the additional DRX cycle parameter set; as well as A request is transmitted for an updated set of additional DRX cycle parameters satisfied by the common DRX cycle.

19. The method of claim 18, wherein transmitting the request comprises: The request is transmitted in a radio resource control reconfiguration message.

20. The method of claim 1, wherein transmitting the request comprises: The request is transmitted in a radio resource control configuration request.

21. The method of claim 1, wherein the request includes an alignment indicator indicating whether an additional DRX cycle associated with the additional uplink DRX cycle parameter set is to be aligned with the common DRX cycle.

22. The method of claim 1, wherein the request includes a flexibility indicator indicating whether the UE is flexible in modifying the common discontinuous reception cycle.

23. The method of claim 1, wherein the request comprises an indication of a sidelink traffic pattern, an explicit indication of the common discontinuous reception cycle, or a combination thereof.

24. A method for wireless communication at a network node, comprising: receiving a request for a set of discontinuous reception cycle parameters that satisfies a common discontinuous reception cycle for a user equipment (UE); transmitting an indication of the discontinuous reception cycle parameter set in response to the request; receiving a request for an additional uplink discontinuous reception cycle parameter set satisfied by the common discontinuous reception cycle; as well as An acknowledgement of a discontinuous reception cycle associated with the discontinuous reception cycle parameter set is received.

25. The method of claim 24, wherein receiving the request comprises: The request is received in a radio resource control configuration request.

26. The method of claim 24, further comprising: transmitting an indication of an additional set of discontinuous reception cycle parameters, wherein the additional set of discontinuous reception cycle parameters is related to communication between the UE and a network node; receiving a request for an updated set of additional DRX cycle parameters satisfied by the common DRX cycle; as well as The updated set of additional DRX cycle parameters satisfied by the common DRX cycle is transmitted.

27. The method of claim 24, further comprising: A request is received for an additional uplink DRX cycle parameter set to be satisfied by the common DRX cycle.

28. An apparatus for wireless communication at a user equipment (UE), comprising: means for receiving, at a processing layer of the UE, a plurality of discontinuous reception cycle parameter sets from corresponding plurality of applications at an application layer of the UE, wherein the processing layer is below the application layer and above a user plane protocol stack of the UE; means for determining a common discontinuous reception cycle to satisfy each of the plurality of applications based at least in part on the plurality of discontinuous reception cycle parameter sets; means for transmitting a request for an additional uplink discontinuous reception cycle parameter set to be satisfied by the common discontinuous reception cycle; as well as Means for transmitting the common discontinuous reception cycle to one or more layers in the user plane protocol stack of the UE.

29. An apparatus for wireless communication at a network node, comprising: means for receiving a request for a set of discontinuous reception cycle parameters that satisfies a common discontinuous reception cycle for a user equipment (UE); means for transmitting an indication of the discontinuous reception cycle parameter set in response to the request; means for receiving a request for an additional uplink discontinuous reception cycle parameter set to be satisfied by the common discontinuous reception cycle; as well as Means for receiving an acknowledgement of a discontinuous reception cycle associated with the discontinuous reception cycle parameter set.

30. An apparatus for wireless communication at a user equipment (UE), comprising: processor, a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: receiving, at a processing layer of the UE, a plurality of discontinuous reception cycle parameter sets from corresponding plurality of applications at an application layer of the UE, wherein the processing layer is below the application layer and above a user plane protocol stack of the UE; determining a common discontinuous reception cycle to satisfy each of the plurality of applications based at least in part on the plurality of discontinuous reception cycle parameter sets; transmitting a request for an additional uplink discontinuous reception cycle parameter set to be satisfied by the common discontinuous reception cycle; as well as The common discontinuous reception cycle is transmitted to one or more layers in the user plane protocol stack of the UE.

31. The apparatus of claim 30, wherein the instructions executable by the processor to cause the apparatus to determine the common discontinuous receive cycle are further executable by the processor to cause the apparatus to: A common set of DRX cycle parameters is determined that satisfies the individual DRX cycles associated with the plurality of DRX cycle parameter sets or satisfies the adjusted DRX cycle associated with the adjusted DRX cycle parameter set.

32. The apparatus of claim 30, wherein the instructions are further executable by the processor to cause the apparatus to: The UE communicates with one or more other wireless communication devices according to the common discontinuous reception cycle.

33. The apparatus of claim 30, wherein the processing layer is a side link layer, wherein receiving the plurality of DRX cycle parameter sets from the corresponding plurality of applications comprises: Each discontinuous reception cycle parameter set of the plurality of discontinuous reception cycle parameter sets is received via a respective discontinuous reception cycle request from a corresponding application.

34. The apparatus of claim 33, wherein the instructions executable by the processor to cause the apparatus to determine the common discontinuous receive cycle are further executable by the processor to cause the apparatus to: An initial common discontinuous reception cycle is determined based at least in part on the plurality of discontinuous reception cycle parameter sets.

35. The apparatus of claim 34, wherein the instructions are further executable by the processor to cause the apparatus to: determining that the initial common DRX cycle cannot satisfy at least one application among the plurality of applications; and A request is transmitted to the at least one application of the plurality of applications to update a corresponding DRX cycle parameter set so that the initial common DRX cycle satisfies the at least one application of the plurality of applications.

36. The apparatus of claim 35, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a confirmation from the at least one application of the plurality of applications that the corresponding DRX cycle parameter set has been updated so that the initial common DRX cycle satisfies the at least one application of the plurality of applications; and The common discontinuous reception cycle is determined to include the initial common discontinuous reception cycle based at least in part on the confirmation.

37. The apparatus of claim 35, wherein the instructions are further executable by the processor to cause the apparatus to: receiving a response from the at least one application of the plurality of applications that the corresponding DRX cycle parameter set will not be updated; Based at least in part on the response, adjusting the initial common discontinuous reception cycle to an adjusted common discontinuous reception cycle; transmitting, to the at least one application of the plurality of applications, a request to update a corresponding DRX cycle parameter set so that the adjusted common DRX cycle satisfies the at least one application of the plurality of applications; receiving a confirmation from the at least one application of the plurality of applications that the corresponding DRX cycle parameter set has been updated so that the adjusted common DRX cycle satisfies the at least one application of the plurality of applications; as well as Determining the common discontinuous reception cycle based at least in part on the confirmation includes the adjusted common discontinuous reception cycle.

38. The apparatus of claim 34, wherein the instructions are further executable by the processor to cause the apparatus to: An acknowledgement of the common discontinuous reception cycle is transmitted to one or more applications of the plurality of applications.

39. The apparatus of claim 33, wherein the corresponding DRX cycle request comprises an indication of a service requirement of a corresponding application.

40. The apparatus of claim 33, wherein the sidelink layer comprises a vehicle networking layer.

41. The apparatus of claim 30, wherein the processing layers are a plurality of middleware layers, wherein receiving the plurality of DRX cycle parameter sets from the corresponding plurality of applications comprises: A corresponding middleware layer among the plurality of middleware layers receives an individual discontinuous reception cycle parameter set from a corresponding application among the plurality of applications.

42. The apparatus of claim 41 , wherein the instructions executable by the processor to cause the apparatus to determine the common discontinuous receive cycle are further executable by the processor to cause the apparatus to: negotiating the common discontinuous reception cycle between the plurality of applications via corresponding middleware layers among the plurality of middleware layers; and The common discontinuous reception cycle is determined based at least in part on the negotiation.

43. The apparatus of claim 42, wherein the instructions are further executable by the processor to cause the apparatus to: The common discontinuous reception cycle is transmitted to a sidelink layer for transmission to the one or more layers in the user plane protocol stack of the UE.

44. The apparatus of claim 42, wherein the instructions executable by the processor to cause the apparatus to negotiate the common DRX cycle are further executable by the processor to cause the apparatus to: The common discontinuous reception cycle is determined so as to improve power saving efficiency of the UE and to distribute channel load among the multiple applications.

45. The apparatus of claim 41, wherein the plurality of middleware layers comprise one or more of: an Internet of Vehicles application enabling layer, or a vertical service enabling architecture layer, or both.

46. ​​The apparatus of claim 30, wherein the instructions are further executable by the processor to cause the apparatus to: An indication of an additional set of discontinuous reception cycle parameters is received, wherein the additional set of discontinuous reception cycle parameters is related to communications between the UE and a network node, and wherein determining the common discontinuous reception cycle is further based at least in part on the indication.

47. The apparatus of claim 30, wherein the instructions are further executable by the processor to cause the apparatus to: receiving an indication of an additional set of discontinuous reception cycle parameters, wherein the additional set of discontinuous reception cycle parameters is related to communication between the UE and a network node; determining that the common DRX cycle does not satisfy the additional DRX cycle parameter set; as well as A request is transmitted for an updated set of additional DRX cycle parameters satisfied by the common DRX cycle.

48. The apparatus of claim 47, wherein the instructions executable by the processor to cause the apparatus to transmit the request are further executable by the processor to cause the apparatus to: The request is transmitted in a radio resource control reconfiguration message.

49. The apparatus of claim 30, wherein the instructions executable by the processor to cause the apparatus to transmit the request are further executable by the processor to cause the apparatus to: The request is transmitted in a radio resource control configuration request.

50. The apparatus of claim 30, wherein the request comprises an alignment indicator indicating whether an additional DRX cycle associated with the additional uplink DRX cycle parameter set is to be aligned with the common DRX cycle.

51. The apparatus of claim 30, wherein the request includes a flexibility indicator indicating whether the UE is flexible in modifying the common discontinuous reception cycle.

52. The apparatus of claim 30, wherein the request comprises an indication of a sidelink traffic pattern, an explicit indication of the common discontinuous reception cycle, or a combination thereof.

53. An apparatus for wireless communication at a network node, comprising: processor, a memory coupled to the processor; as well as instructions stored in the memory and executable by the processor to cause the apparatus to: receiving a request for a set of discontinuous reception cycle parameters that satisfies a common discontinuous reception cycle for a user equipment (UE); transmitting an indication of the discontinuous reception cycle parameter set in response to the request; receiving a request for an additional uplink discontinuous reception cycle parameter set satisfied by the common discontinuous reception cycle; as well as An acknowledgement of a discontinuous reception cycle associated with the discontinuous reception cycle parameter set is received.

54. The apparatus of claim 53, wherein the instructions executable by the processor to cause the apparatus to receive the request are further executable by the processor to cause the apparatus to: The request is received in a radio resource control configuration request.

55. The apparatus of claim 53, wherein the instructions are further executable by the processor to cause the apparatus to: transmitting an indication of an additional set of discontinuous reception cycle parameters, wherein the additional set of discontinuous reception cycle parameters is related to communication between the UE and a network node; receiving a request for an updated set of additional DRX cycle parameters satisfied by the common DRX cycle; as well as The updated set of additional DRX cycle parameters satisfied by the common DRX cycle is transmitted.

56. The apparatus of claim 53, wherein the instructions are further executable by the processor to cause the apparatus to: A request is received for an additional uplink DRX cycle parameter set to be satisfied by the common DRX cycle.

Images