WO2022082647A1 - Sidelink drx optimizations for rrc_connected user equipment (ue) - Google Patents
Sidelink drx optimizations for rrc_connected user equipment (ue) Download PDFInfo
- Publication number
- WO2022082647A1 WO2022082647A1 PCT/CN2020/122962 CN2020122962W WO2022082647A1 WO 2022082647 A1 WO2022082647 A1 WO 2022082647A1 CN 2020122962 W CN2020122962 W CN 2020122962W WO 2022082647 A1 WO2022082647 A1 WO 2022082647A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- drx
- gnb
- computer
- readable storage
- storage medium
- Prior art date
Links
- 238000005457 optimization Methods 0.000 title 1
- 238000000034 method Methods 0.000 claims description 79
- 230000011664 signaling Effects 0.000 claims description 17
- 230000008569 process Effects 0.000 claims description 11
- 238000012545 processing Methods 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 4
- 238000004891 communication Methods 0.000 description 41
- 238000010586 diagram Methods 0.000 description 14
- 230000005540 biological transmission Effects 0.000 description 11
- 230000007246 mechanism Effects 0.000 description 11
- 238000001228 spectrum Methods 0.000 description 11
- 230000000694 effects Effects 0.000 description 10
- 238000007726 management method Methods 0.000 description 8
- 230000006870 function Effects 0.000 description 7
- 230000003139 buffering effect Effects 0.000 description 5
- 230000001413 cellular effect Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 5
- 238000013459 approach Methods 0.000 description 4
- 230000008901 benefit Effects 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- 238000013468 resource allocation Methods 0.000 description 4
- 238000012384 transportation and delivery Methods 0.000 description 4
- 239000000969 carrier Substances 0.000 description 3
- 230000010267 cellular communication Effects 0.000 description 3
- 230000002093 peripheral effect Effects 0.000 description 3
- 101001056707 Homo sapiens Proepiregulin Proteins 0.000 description 2
- 101100172132 Mus musculus Eif3a gene Proteins 0.000 description 2
- 102100025498 Proepiregulin Human genes 0.000 description 2
- 101150014328 RAN2 gene Proteins 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000005641 tunneling Effects 0.000 description 2
- 101100411667 Arabidopsis thaliana RAN4 gene Proteins 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 208000028626 extracranial carotid artery aneurysm Diseases 0.000 description 1
- 238000005755 formation reaction Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000010363 phase shift Effects 0.000 description 1
- 229920000915 polyvinyl chloride Polymers 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/28—Discontinuous transmission [DTX]; Discontinuous reception [DRX]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
- H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/04—Interfaces between hierarchically different network devices
- H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/18—Interfaces between hierarchically similar devices between terminal devices
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks
Definitions
- This application relates generally to wireless communication systems, including sidelink for user equipment (UE) to UE communication.
- UE user equipment
- Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device.
- Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G) or new radio (NR) (e.g., 5G) ; the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly known to industry groups as worldwide interoperability for microwave access (WiMAX) ; and the IEEE 802.11 standard for wireless local area networks (WLAN) , which is commonly known to industry groups as Wi-Fi.
- 3GPP 3rd Generation Partnership Project
- LTE long term evolution
- NR new radio
- WiMAX Institute of Electrical and Electronics Engineers
- WiMAX IEEE 802.11 standard for wireless local area networks (WLAN) , which is commonly known to industry groups as Wi-Fi.
- the base station can include a RAN Node such as a Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE) .
- E-UTRAN Evolved Universal Terrestrial Radio Access Network
- eNodeB also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB
- RNC Radio Network Controller
- RAN Nodes can include a 5G Node, NR node (also referred to as a next generation Node B or g Node B (gNB) ) .
- RANs use a radio access technology (RAT) to communicate between the RAN Node and UE.
- RANs can include global system for mobile communications (GSM) , enhanced data rates for GSM evolution (EDGE) RAN (GERAN) , Universal Terrestrial Radio Access Network (UTRAN) , and/or E-UTRAN, which provide access to communication services through a core network.
- GSM global system for mobile communications
- EDGE enhanced data rates for GSM evolution
- GERAN enhanced data rates for GSM evolution
- UTRAN Universal Terrestrial Radio Access Network
- E-UTRAN which provide access to communication services through a core network.
- Each of the RANs operates according to a specific 3GPP RAT.
- the GERAN implements GSM and/or EDGE RAT
- the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT
- the E-UTRAN implements LTE RAT
- NG-RAN implements 5G RAT.
- Frequency bands for 5G NR may be separated into two different frequency ranges.
- Frequency Range 1 may include frequency bands operating in sub-6 GHz frequencies, some of which are bands that may be used by previous standards, and may potentially be extended to cover new spectrum offerings from 410 MHz to 7125 MHz.
- Frequency Range 2 may include frequency bands from 24.25 GHz to 52.6 GHz. Bands in the millimeter wave (mmWave) range of FR2 may have smaller coverage but potentially higher available bandwidth than bands in the FR1. Skilled persons will recognize these frequency ranges, which are provided by way of example, may change from time to time or from region to region.
- mmWave millimeter wave
- FIG. 1 is a block diagram of a system for wireless communications, in accordance with one embodiment.
- FIG. 2 is an annotated block diagram of a system for wireless communications, in accordance with one embodiment.
- FIG. 3 is an annotated block diagram of a system for wireless communications, in accordance with one embodiment.
- FIG. 4A is an annotated block diagram of a system for wireless communications, in accordance with one embodiment.
- FIG. 4B is an annotated timing diagram showing non-overlapping and overlapping onDurations, in accordance with one embodiment.
- FIG. 5A is an annotated timing diagram showing DRX alignment, in accordance with one embodiment.
- FIG. 5B is an annotated timing diagram showing two versions of adjacent DRX cycles, in accordance with one embodiment.
- FIG. 6 is a table showing full and partial alignment, in accordance with one embodiment.
- FIG. 7 is an annotated timing diagram showing another example of DRX alignment, in accordance with one embodiment.
- FIG. 8 is a table showing drx-LongCycleStartOffset, in accordance with one embodiment.
- FIG. 9 is a message flow diagram, in accordance with one embodiment.
- FIG. 10A is a message flow diagram, in accordance with one embodiment.
- FIG. 10B is a message flow diagram, in accordance with one embodiment.
- FIG. 11 is a block diagram, according to one embodiment.
- FIG. 1 illustrates an example architecture of a system 100 of a network, in accordance with various embodiments.
- the following description is provided for an example system 100 that operates in conjunction with the LTE system standards and 5G or NR system standards as provided by 3GPP technical specifications.
- the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., Sixth Generation (6G) ) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc. ) , or the like.
- 6G Sixth Generation
- IEEE 802.16 protocols e.g., WMAN, WiMAX, etc.
- the system 100 includes UE 122 and UE 120.
- the UE 122 and the UE 120 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) , but may also comprise any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs) , pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI) , in-car entertainment (ICE) devices, an Instrument Cluster (IC) , head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME) , mobile data terminals (MDTs) , Electronic Engine Management System (EEMS) , electronic/engine control units (ECUs) , electronic/engine control modules (ECMs) , embedded systems, microcontrollers, control modules, engine management systems (EMS) , networked or "s
- EEMS Electronic Engine Management
- the UE 122 and/or the UE 120 may be IoT UEs, which may comprise a network access layer designed for low power IoT applications utilizing short-lived UE connections.
- An IoT UE can utilize technologies such as M2M or MTC for exchanging data with an MTC server or device via a PLMN, ProSe or D2D communication, sensor networks, or IoT networks.
- the M2M or MTC exchange of data may be a machine-initiated exchange of data.
- An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) , with short-lived connections.
- the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc. ) to facilitate the connections of the IoT network.
- the UE 122 and UE 120 may be configured to connect, for example, communicatively couple, with an access node or radio access node (shown as (R) AN 108) .
- the (R) AN 108 may be an NG RAN or a SG RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN.
- the term "NG RAN” or the like may refer to a (R) AN 108 that operates in an NR or SG system
- the term "E-UTRAN” or the like may refer to a (R) AN 108 that operates in an LTE or 4G system.
- the UE 122 and UE 120 utilize connections (or channels) (shown as connection 104 and connection 102, respectively) , each of which comprises a physical communications interface or layer (discussed in further detail below) .
- connection 104 and connection 102 are air interfaces to enable communicative coupling, and can be consistent with cellular communications protocols, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a SG protocol, a NR protocol, and/or any of the other communications protocols discussed herein.
- the UE 122 and UE 120 may directly exchange communication data via a ProSe interface 110.
- the ProSe interface 110 may alternatively be referred to as a sidelink (SL) interface 110 and may comprise one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.
- SL sidelink
- the UE 120 is shown to be configured to access an AP 112 (also referred to as "WLAN node, " “WLAN, “ “WLAN Termination, “ “WT” or the like) via connection 124.
- the connection 124 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 112 would comprise a wireless fidelity router.
- the AP 112 may be connected to the Internet without connecting to the core network of the wireless system (described in further detail below) .
- the UE 120, (R) AN 108, and AP 112 may be configured to utilize LWA operation and/or LWIP operation.
- the LWA operation may involve the UE 120 in RRC_CONNECTED being configured by the RAN node 114 or the RAN node 116 to utilize radio resources of LTE and WLAN.
- LWIP operation may involve the UE 120 using WLAN radio resources (e.g., connection 124) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection 124.
- IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.
- the (R) AN 108 can include one or more AN nodes, such as RAN node 114 and RAN node 116, that enable the connection 104 and connection 102.
- AN nodes such as RAN node 114 and RAN node 116, that enable the connection 104 and connection 102.
- access node such as RAN node 114 and RAN node 116
- access point such as RAN node 114 and RAN node 116
- access node access point, or the like may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users.
- These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell) .
- ground stations e.g.,
- the term "NG RAN node” or the like may refer to a RAN node that operates in an NR or SG system (for example, a gNB)
- the term "E-UTRAN node” or the like may refer to a RAN node that operates in an LTE or 4G system 100 (e.g., an eNB)
- the RAN node 114 or RAN node 116 may be implemented as one or more of a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
- LP low power
- all or parts of the RAN node 114 or RAN node 116 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and/or a virtual baseband unit pool (vBBUP) .
- a virtual network which may be referred to as a CRAN and/or a virtual baseband unit pool (vBBUP) .
- vBBUP virtual baseband unit pool
- the CRAN or vBBUP may implement a RAN function split, such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN nodes (e.g., RAN node 114 or RAN node 116) ; a MAC/PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUP and the PHY layer is operated by individual RAN nodes (e.g., RAN node 114 or RAN node 116) ; or a "lower PHY" split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer are operated by the CRAN/vBBUP and lower portions of the PHY layer are operated by individual RAN nodes.
- a RAN function split such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN
- an individual RAN node may represent individual gNB-DUs that are connected to a gNB-CU via individual F1 interfaces (not shown by FIG. 1) .
- the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CU may be operated by a server that is located in the (R) AN 108 (not shown) or by a server pool in a similar manner as the CRAN/vBBUP.
- one or more of the RAN node 114 or RAN node 116 may be next generation eNBs (ng-eNBs) , which are RAN nodes that provide E-UTRA user plane and control plane protocol terminations toward the UE 122 and UE 120, and are connected to an SGC via an NG interface (discussed infra) .
- ng-eNBs next generation eNBs
- NG interface discussed infra
- RSU may refer to any transportation infrastructure entity used for V2X communications.
- An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a "UE-type RSU, " an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU, " an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU, " and the like.
- an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs (vUEs) .
- the RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
- the RSU may operate on the 5.9 GHz Direct Short Range Communications (DSRC) band to provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally, or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications, as well as other cellular communications services. Additionally, or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and/or provide connectivity to one or more cellular networks to provide uplink and downlink communication.
- DSRC Direct Short Range Communications
- the computing device (s) and some or all of the radio frequency circuitry of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and/or a backhaul network.
- a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and/or a backhaul network.
- the RAN node 114 and/or the RAN node 116 can terminate the air interface protocol and can be the first point of contact for the UE 122 and UE 120.
- the RAN node 114 and/or the RAN node 116 can fulfill various logical functions for the (R) AN 108 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
- RNC radio network controller
- the UE 122 and UE 120 can be configured to communicate using OFDM communication signals with each other or with the RAN node 114 and/or the RAN node 116 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a SC-FDMA communication technique (e.g., for uplink and ProSe or sidelink communications) , although the scope of the embodiments is not limited in this respect.
- the OFDM signals can comprise a plurality of orthogonal subcarriers.
- a downlink resource grid can be used for downlink transmissions from the RAN node 114 and/or the RAN node 116 to the UE 122 and UE 120, while uplink transmissions can utilize similar techniques.
- the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
- a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
- Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
- the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
- the smallest time-frequency unit in a resource grid is denoted as a resource element.
- Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
- Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
- the licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band.
- the UE 122 and UE 120 and the RAN node 114 or RAN node 116 may operate using LAA, eLAA, and/or feLAA mechanisms.
- the UE 122 and UE 120 and the RAN node 114 or RAN node 116 may perform one or more known medium-sensing operations and/or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum.
- the medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.
- LBT listen-before-talk
- LBT is a mechanism whereby equipment (for example, UE 122 and UE 120, RAN node 114 or RAN node 116, etc. ) senses a medium (for example, a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied) .
- the medium sensing operation may include CCA, which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear.
- CCA which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear.
- This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks.
- ED may include sensing RF energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.
- WLAN employs a contention-based channel access mechanism, called CSMA/CA
- CSMA/CA contention-based channel access mechanism
- a WLAN node e.g., a mobile station (MS) such as UE 122, AP 112, or the like
- MS mobile station
- AP 112 AP 112
- a backoff mechanism is used to avoid collisions in situations where more than one WLAN node senses the channel as idle and transmits at the same time.
- the backoff mechanism may be a counter that is drawn randomly within the CWS, which is increased exponentially upon the occurrence of collision and reset to a minimum value when the transmission succeeds.
- the LBT mechanism designed for LAA is somewhat similar to the CSMA/CA of WLAN.
- the LBT procedure for DL or UL transmission bursts including PDSCH or PUSCH transmissions, respectively may have an LAA contention window that is variable in length between X and Y ECCA slots, where X and Y are minimum and maximum values for the CWSs for LAA.
- the minimum CWS for an LAA transmission may be 9 microseconds ( ⁇ s) ; however, the size of the CWS and a MCOT (for example, a transmission burst) may be based on governmental regulatory requirements.
- each aggregated carrier is referred to as a CC.
- a CC may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is 100 MHz.
- the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers.
- individual CCs can have a different bandwidth than other CCs.
- the number of CCs as well as the bandwidths of each CC is usually the same for DL and UL.
- CA also comprises individual serving cells to provide individual CCs.
- the coverage of the serving cells may differ, for example, because CCs on different frequency bands will experience different pathloss.
- a primary service cell or PCell may provide a PCC for both UL and DL, and may handle RRC and NAS related activities.
- the other serving cells are referred to as SCells, and each SCell may provide an individual SCC for both UL and DL.
- the SCCs may be added and removed as required, while changing the PCC may require the UE 122 to undergo a handover.
- LAA SCells In LAA, eLAA, and feLAA, some or all of the SCells may operate in the unlicensed spectrum (referred to as "LAA SCells" ) , and the LAA SCells are assisted by a PCell operating in the licensed spectrum.
- LAA SCells When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within a same subframe.
- the PDSCH carries user data and higher-layer signaling to the UE 122 and UE 120.
- the PDCCH carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UE 122 and UE 120 about the transport format, resource allocation, and HARQ information related to the uplink shared channel.
- downlink scheduling (assigning control and shared channel resource blocks to the UE 120 within a cell) may be performed at any of the RAN node 114 or RAN node 116 based on channel quality information fed back from any of the UE 122 and UE 120.
- the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UE 122 and UE 120.
- the PDCCH uses CCEs to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as REGs. Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG.
- QPSK Quadrature Phase Shift Keying
- Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an EPDCCH that uses PDSCH resources for control information transmission.
- the EPDCCH may be transmitted using one or more ECCEs. Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an EREGs. An ECCE may have other numbers of EREGs in some situations.
- the RAN node 114 or RAN node 116 may be configured to communicate with one another via interface 130.
- the interface 130 may be an X2 interface.
- the X2 interface may be defined between two or more RAN nodes (e.g., two or more eNBs and the like) that connect to an EPC, and/or between two eNBs connecting to the EPC.
- the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C) .
- the X2-U may provide flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs.
- the X2-U may provide specific sequence number information for user data transferred from a MeNB to an SeNB; information about successful in sequence delivery of PDCP PDUs to a UE 122 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 122; information about a current minimum desired buffer size at the Se NB for transmitting to the UE user data; and the like.
- the X2-C may provide intra-LTE access mobility functionality, including context transfers from source to target eNBs, user plane transport control, etc.; load management functionality; as well as inter-cell interference coordination functionality.
- the interface 130 may be an Xn interface.
- the Xn interface is defined between two or more RAN nodes (e.g., two or more gNBs and the like) that connect to SGC, between a RAN node 114 (e.g., a gNB) connecting to SGC and an eNB, and/or between two eNBs connecting to 5GC (e.g., CN 106) .
- the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface.
- the Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality.
- the Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 122 in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN node 114 or RAN node 116.
- the mobility support may include context transfer from an old (source) serving RAN node 114 to new (target) serving RAN node 116; and control of user plane tunnels between old (source) serving RAN node 114 to new (target) serving RAN node 116.
- a protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer (s) to carry user plane PDUs.
- the Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP) ) and a transport network layer that is built on SCTP.
- the SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages.
- point-to-point transmission is used to deliver the signaling PDUs.
- the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack (s) shown and described herein.
- the (R) AN 108 is shown to be communicatively coupled to a core network-in this embodiment, CN 106.
- the CN 106 may comprise one or more network elements 132, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UE 122 and UE 120) who are connected to the CN 106 via the (R) AN 108.
- the components of the CN 106 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) .
- NFV may be utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below) .
- a logical instantiation of the CN 106 may be referred to as a network slice, and a logical instantiation of a portion of the CN 106 may be referred to as a network sub-slice.
- NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.
- an application server 118 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc. ) .
- the application server 118 can also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc. ) for the UE 122 and UE 120 via the EPC.
- the application server 118 may communicate with the CN 106 through an IP communications interface 136.
- the CN 106 may be an SGC, and the (R) AN 116 may be connected with the CN 106 via an NG interface 134.
- the NG interface 134 may be split into two parts, an NG user plane (NG-U) interface 126, which carries traffic data between the RAN node 114 or RAN node 116 and a UPF, and the S1 control plane (NG-C) interface 128, which is a signaling interface between the RAN node 114 or RAN node 116 and Access and Mobility Management Functions (AMFs) .
- NG-U NG user plane
- N-C S1 control plane
- the CN 106 may be a SG CN, while in other embodiments, the CN 106 may be an EPC) .
- the (R) AN 116 may be connected with the CN 106 via an S1 interface 134.
- the S1 interface 134 may be split into two parts, an S1 user plane (S1-U) interface 126, which carries traffic data between the RAN node 114 or RAN node 116 and the S-GW, and the S1-MME interface 128, which is a signaling interface between the RAN node 114 or RAN node 116 and MMEs.
- S1-U S1 user plane
- FIG. 2 shows an example of a wireless communications system 200 for SL operation.
- Wireless communications system 200 includes a gNB 202 communicatively coupled with a first UE 204 and a second UE 206.
- First UE 204 is communicatively coupled to a fourth UE 208.
- Second UE 206 is communicatively coupled to a third UE 210 and a fifth UE 212.
- the UEs are shown as vehicles because SL is commonly employed for Vehicle-to-Vehicle (V2V) , which is a type of Vehicle-to-Everything (V2X) communication.
- V2V Vehicle-to-Vehicle
- V2X Vehicle-to-Everything
- SL-DRX involves both Uu and PC5 interfaces.
- RRC_CONNECTED UE also referred to as a connected mode UE, or simply connected UE
- SL-DRX enhancements are described in this disclosure.
- a first enhancement entails a gNB capable of triggering SL-DRX based on enhanced Uu MAC control element (CE) signaling to trigger UE to enter DRX.
- an index may be used to point to one of the predefined (i.e., Uu or SL) DRX configurations.
- this index is a pointer to a DRX configuration, such as a look-up table. To perform the look-up, the table is predefined. And which index value corresponds to which DRX configuration is also predefined. This table can be part of RRC configuration via Uu RRC.
- a Uu DRX command to trigger SL DRX 214 is provided between gNB 202 and first UE 204 via MAC CE layer-2 signaling.
- An SL DRX command 216 (also layer-2 signaling) is made between first UE 204 and fourth UE 208.
- Tthe Uu DRX MAC CE layer-2 command includes a flag (or 2-bits) to point out to be used in Uu, in SL, or in both.
- a second enhancement entails a UE including its desired SL-DRX configuration or choices into a UEAssistanceInformation (UAI) message to a gNB.
- UAI UEAssistanceInformation
- This can include all UE engaged DRX operations (common DRX, link-specific DRX) . It can also establish how much traffic that is expected to be generated (e.g., how busy the link will be) , so the DRX schedule (e.g., how frequently the UE will wake up) can be established.
- Uu 218 which can be designated to be used in Uu interface, or PC5 interface or both interfaces
- RRC layer-3 signaling is provided from gNB 202 to second UE 206.
- Second UE 206 provides a UAI for SL operation 220 to gNB 202.
- a DRX configuration via PC5 222 (also layer-3 signaling) is provided from second UE 206 to third UE 210.
- a DRX configuration via PC5 224 is established between fifth UE 212 and second UE 206 by layer-3 signaling.
- a SidelinkUEInformation (SUI) message may be used.
- Uu/SL DRX alignment or simply alignment Alignment of SL-DRX alignment with Uu-DRX is also described, as an optional feature (since not all schedules can temporally align) .
- FIG. 3 is an annotated block diagram 300 showing an overview of RRC configuration of a sidelink.
- a first gNB 302 providing a first coverage area 304 is in wireless communication with a first UE 306 to form a Uu interface 308 between first UE 306 and first gNB 302. Accordingly, first UE 306 is in RRC connected mode and may be configured for a sidelink through RRCReconfigure messages.
- a second gNB 310 provides a second coverage area 312.
- a second UE 314 is located in second coverage area 312, but is in Idle/Inactive mode. Nevertheless, it receives a common DRX configuration in in a system information block (SIB) .
- SIB system information block
- PC5-link specific configuration is also provided between first UE 306 and second UE 314, which have already had a PC5-RRC connection 316.
- a third UE 318 is preconfigured.
- a common configuration can be configured to all sidelink UEs in-coverage or out of coverage. This provides a baseline to ensure a sidelink UE works even as the transmitters in SL carriers are not always connected.
- PC5-link specific configuration is between the two UEs that have a PC5-RRC connection.
- a gNB makes a decision for UE for power-savings, based on information provided by UE regarding its SL engagements. If possible, the gNB will align Uu- DRX, with common and/or link-specific SL-DRX. If alignment is not feasible, gNB can still keep the DRX configurations separate. SL-DRX alignment with Uu-DRX is an optional feature. Skipping monitoring of PDCCH and skipping monitoring of PSCCH can be independently configured. A gNB is able to enable/disable the support of this feature.
- FIG. 4A shows an example SL DRX alignment with Uu DRX use case in an SL relay system 400 to explain the potential benefits of SL/Uu DRX alignment for sidelink relay.
- a gNB 402 has a Uu DRX link 404 with a relay UE 406.
- Relay UE 406 has a PC5 link 408 with a remote UE 410. Aside from power saving, alignment could reduce unnecessary buffering in sidelink relay and reduce overall end-to-end latency.
- the traffic may be buffered twice: a first buffering 412 occurs at gNB 402, as relay UE 406 is in DRX inactive mode; a second buffering 414 occurs at relay UE 406, as remote UE 410 is in DRX inactive for PC5 link.
- FIG. 4B shows two examples in which Uu-DRX and SL-DRX cycles, respectively, are temporally spaced apart 416 and overlap 418 in terms of the wake up time “onDuration. ” When they overlap 418, e.g., due to alignment, second buffering 414 can be mitigated.
- a RAN2 objective is to specify a mechanism aiming to align sidelink DRX wake-up time with Uu DRX wake-up time in an in-coverage UE. But fully overlapping alignment may not be always be desirable in every scenario.
- LTE ProSe if a UE uses a single RX chain for WAN and D2D Communication, a discovery gap is configured for UE to switching to monitor D2D signals. LTE ProSe supports commercial discovery, which may not justify a dedicated RX chain for D2D.
- SL and Uu may operate in the same band.
- n38 and n79 are added in Rel-16 by RAN4, and SL communication is not restricted to n47 ITS bands.
- UE shares the single RX chain in licensed band for both V2X SL and NR DL reception it is not suitable for alignment of Uu-DRX and SL-DRX.
- a UE may be able to do DL reception and SL reception at the same time (similar to intra-band CA) , but TX in SL (as triggered in onDuration) would cause problem for PDCCH monitoring for Uu-DRX. Instead of full alignment, a TDM gap is implemented.
- FIG. 5A shows Uu and SL are overlapping in a aligned common wake up period (e.g., dedicated RX chain for SL) .
- FIG. 5B shows two examples in which Uu and SL are non-overlapping TDM-ed in a shared/common wake up period (e.g., single Rx chain, shared carrier) .
- a shared/common wake up period e.g., single Rx chain, shared carrier.
- the buffering time can be minimized for DL traffic. Even when DRX cycle is not overlapping, it may be desired to make them adjacent to each other so that the traffic forwarding latency can be reduced.
- SL-DRX for CONNECTED mode, coordination with Uu DRX is described.
- a UE can be configured with connected mode DRX (C-DRX) in Uu (short and long DRX cycle) . It may be advantageous to halt SL activity when Uu is in DRX mode, for the following reasons: First, mode 1 UE operation will be impacted by Uu C-DRX. In NR-V2X Rel-16, RAN2 agrees that UE does not expect DRX configuration if SL mode 1 is configured in Rel-16. Second, power savings cannot be fully achieved if SL operation is still ongoing, Uu RRC procedures for sidelink are used even for CONNECTED mode 2 UE, and SL operation may trigger some “activity” in Uu.
- FIG. 6 summarizes the impact to SL RX and TX, if aligned with Uu-DRX. Note that the table includes SL-DRX partial alignment. The following two paragraphs describe examples for implementing such behavior.
- the UE avoids mode 1 operation when Uu DRX is configured.
- UE switches to mode 2 TX (autonomous resource selection) .
- Sidelink RX is not disabled (so no power-saving in SL) .
- the network will enable/disable this “mode-switch” with a flag.
- UE no longer initiates any RRC message (e.g., SidelinkUEInformation) .
- UE delays any report of new/modified QoS flow to network, and employs default SL radio bearer SLRB mapping for any QoS flow which does not have a configuration.
- SL RX is shut off as long as Uu DRX is inactive, but limited TX activity is allowed without sensing.
- This approach achieves improved power savings.
- Mode 2 UE can transmit with use of random TX resource selection in configured pools.
- Mode 1 UE TX relies on Configured Grant Type 2.
- HARQ feedback can be either enabled or disabled, depending on whether a DRX INACTIVE UE can still receive Physical Sidelink Feedback Channel (PSFCH) or not.
- PSFCH Physical Sidelink Feedback Channel
- FIG. 7 shows an example of alignment of DRX cycles in the SL-DRX for CONNECTED mode.
- alignment for Uu DRX and SL DRX means fully-aligned and Partial Alignment Option 2 (FIG. 6) .
- the same DRX cycle applies to both downlink and sidelink. Cycle lengths are identical and UE may skip both PDCCH and PSCCH monitoring.
- SL DRX may also use a short and long cycle.
- OnDurations are aligned, although they need not necessarily be of identical length, and SL-DRX can have shorter onDuration. Inactivity timer configurations may be different as well.
- Uu DRX configuration is UE-specific configuration and not known by other UEs, and not compatible with the common DRX configuration explained previously with reference to FIG. 3.
- C-DRX is arbitrary with plenty of choices because DRX can be started with arbitrary offset and cycle (see e.g., FIG. 8 drx-LongCycleStartOffset) .
- the gNB is aware of the DRX configuration, so it can delay its DL traffic accordingly, but SL traffic is not controlled by the gNB.
- any potential SL TX UE may not be aware of this because it may not know if RX UE is in RRC_CONNECTED and it does not know the coordinated Uu/SL-DRX configuration is used in RX UE. If SL traffic is destined to this UE during the DRX inactivity and the UE cannot be properly delayed, then that traffic will not be properly received by the UE which aligns its SL DRX cycle to a configured Uu C-DRX cycle. Packet loss will mount for SL-DRX UE which deviates from the commonly known SL DRX cycle.
- FIG. 9 shows an example of restricting Uu DRX configuration to that of SL-DRX (match or alight Uu-DRX towards SL-DRX) .
- the gNB will decide what is the best alignment that can be provided, and then gNB shares this aligned configuration (common for both Uu and SL) to UE 1. More specifically, the gNB (and neighboring gNBs) will broadcast supported DRX cycle and offset (limited number of choices) to all UEs in the cell.
- SL UE reports its SL engagements and DRX configurations (received via Uu and via PC5) to the gNB.
- the gNB determines which SL DRX cycle based on SL service (QoS profile, PSID) or SL address. If possible, Uu DRX cycle is then aligned with SL DRX. Any SL TX sender, if it knows the RX UE may support SL DRX, assumes DRX is enabled and only transmit in onDuration. The gNB can enable/disable this alignment with a flag. If not aligned, the gNB can configure Uu-DRX with separate parameters.
- SL service QoS profile, PSID
- the DRX configuration is conveyed to other RRC_CONNECTED UEs via dedicated RRC signaling. If any CONNECTED UE B indicates it tries to transmit to a SL destination address which involves UE A’s RX, it shares the UE’A DRX configuration in the RRCReconfig message to UE B.
- the approach works for CONNECTED UE in the same cell.
- a list of each UE and its DRX configuration is announced.
- the gNB (and neighboring gNBs) broadcast the list of SL destinations and its corresponding DRX cycles in broadcast RRC signaling (SIB) .
- SIB broadcast RRC signaling
- the approach contemplates inter-gNB signaling.
- SL announcements on the start of DRX.
- the UE as inactivity timer is going to expire, sends a PC5-RRC broadcast message to the neighboring UEs about its own “aligned” DRX configuration.
- This approach contemplates additional reliability enhancements, as broadcast may not reach all UEs, especially when other UEs may also in SL-DRX.
- FIG. 9 also shows the UE can use PC5-RRC unicast messages to deliver its DRX configurations to UEs which it has PC5-RRC connections.
- the UE 1 can notify the peer UE 2 to also align its SL-DRX with this DRX configuration. This is suitable for a UE which has SL unicast traffic to serve.
- the PC5 interface can align the DRX.
- FIG. 10A shows how Uu activity and SL activity are not in-sync (different applications, different traffic profile) .
- Uu traffic pauses, SL traffic may still ongoing, or vice versa.
- the gNB may not be aware of SL traffic. The gNB may unnecessarily delay the DL traffic when it falsely assumes UE1 is in DRX state. This may not be a material issue as UE still benefits from skipping PDCCH decoding. Nevertheless, to address the issue, there are several embodiments.
- a single inactivity timer is re-defined to take account of both Uu and SL activities. Accordingly, UE the enters DRX when there is inactivity in both interfaces and does not enter DRX when either interface has activity. In case of a lack of Uu traffic, sidelink UE keeps Uu busy so that the gNB will not misunderstand the DRX status. For instance, it may send some dummy traffic in Uu when SL traffic is ongoing.
- FIG. 10B shows another embodiment. Separate inactivity timers in Uu and SL are maintained.
- the gNB cannot track the SL inactivity timer, so the UE sends UL signaling to keep the gNB updated on SL activities.
- a new UL MAC CE is designed for this purpose, and it indicates the “predicted” starting time of DRX based on SL traffic activities. Timings received from MAC CE overrides the default drx-inactivityTimer mechanism.
- FIG. 11 is a block diagram illustrating components 1100, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
- FIG. 11 shows a diagrammatic representation of hardware resources 1102 including one or more processors 1106 (or processor cores) , one or more memory/storage devices 1114, and one or more communication resources 1124, each of which may be communicatively coupled via a bus 1116.
- a hypervisor 1122 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1102.
- the processors 1106 may include, for example, a processor 1108 and a processor 1110.
- the memory/storage devices 1114 may include main memory, disk storage, or any suitable combination thereof.
- the memory/storage devices 1114 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM) , static random-access memory (SRAM) , erasable programmable read-only memory (EPROM) , electrically erasable programmable read-only memory (EEPROM) , Flash memory, solid-state storage, etc.
- DRAM dynamic random access memory
- SRAM static random-access memory
- EPROM erasable programmable read-only memory
- EEPROM electrically erasable programmable read-only memory
- Flash memory solid-state storage, etc.
- the communication resources 1124 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1104 or one or more databases 1120 via a network 1118.
- the communication resources 1124 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB) ) , cellular communication components, NFC components, components (e.g., Low Energy) , components, and other communication components.
- wired communication components e.g., for coupling via a Universal Serial Bus (USB)
- USB Universal Serial Bus
- NFC components e.g., Low Energy
- components e.g., Low Energy
- Instructions 1112 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1106 to perform any one or more of the methodologies discussed herein.
- the instructions 1112 may reside, completely or partially, within at least one of the processors 1106 (e.g., within the processor’s cache memory) , the memory/storage devices 1114, or any suitable combination thereof.
- any portion of the instructions 1112 may be transferred to the hardware resources 1102 from any combination of the peripheral devices 1104 or the databases 1120.
- the memory of the processors 1106, the memory/storage devices 1114, the peripheral devices 1104, and the databases 1120 are examples of computer-readable and machine-readable media.
- At least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the Example Section below.
- the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
- circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
- Example 1 A method, performed by a first user equipment (UE) in connected mode with a gNB, of entering sidelink (SL) discontinuous reception (DRX) , the method comprising: receiving from the gNB a Uu DRX MAC control element (CE) layer-2 command to trigger the first UE to enter either Uu or SL DRX indicated in the Uu DRX MAC CE layer-2 command; and processing the Uu DRX MAC CE layer-2 command to determine whether to enter Uu DRX or SL DRX with a second UE.
- UE user equipment
- DRX sidelink
- CE Uu DRX MAC control element
- Example 2 The method of Example 1, in which the Uu DRX MAC CE layer-2 command includes an index representing one of a predefined Uu DRX configuration or SL DRX configuration.
- Example 3 The method of Example 1, further comprising RRC signaling to configure a look up table so that the Uu DRX MAC CE layer-2 command indicates a DRX configuration.
- Example 4 The method of Example 3, in which the Uu DRX MAC CE layer-2 command includes a flag to indicate whether the look up table is be used in Uu, in SL, or in both.
- Example 5 The method of Example 3, in which the look up table is a concatenated table for both Uu and SL DRX.
- Example 6 The method of Example 3, in which the look up table includes two different tables and the Uu DRX MAC CE layer-2 command includes a flag to indicate which table is used.
- Example 7 A method, performed by a first user equipment (UE) in connected mode with a gNB, of configuring sidelink (SL) discontinuous reception (DRX) , the method comprising: generating for the gNB a first RRC message including a desired SL-DRX configuration; and in response to the first RRC message, receiving via Uu from the gNB a second RRC message specifying a DRX configuration for one or both of Uu and PC5 interfaces.
- UE user equipment
- DRX sidelink
- Example 8 The method of Example 7, in which the first RRC message comprises a UEAssistance Information (UAI) message including the desired SL-DRX configuration.
- UAI UEAssistance Information
- Example 9 The method of Example 7, in which the first RRC message comprises a SidelinkUEInformation (SUI) message including the desired SL-DRX configuration.
- SAI SidelinkUEInformation
- Example 10 The method of Example 9, in which SUI or RRC message contain the DRX configurations used by peer UEs.
- Example 11 The method of Example 7, in which the first RRC message includes parameters for common DRX operations.
- Example 12 The method of Example 7, in which the first RRC message includes parameters for link-specific DRX operations.
- Example 13 A method, performed by a first user equipment (UE) , of aligning discontinuous reception (DRX) over Uu and sidelink (SL) by restriction of Uu-DRX configuration to those aligned with SL-DRX, the method comprising: providing a Uu RRC message to a gNB to report SL engagements and DRX configurations; and receiving from the gNB an RRCReconfigure message to align DRX cycles.
- UE user equipment
- DRX discontinuous reception
- SL sidelink
- Example 14 The method of Example 13, in which the Uu RRC message comprises a UEAssistance Information (UAI) message.
- UAI UEAssistance Information
- Example 15 The method of Example 13, in which the Uu RRC message comprises a SidelinkUEInformation (SUI) message.
- Uu RRC message comprises a SidelinkUEInformation (SUI) message.
- SUPI SidelinkUEInformation
- Example 16 The method of Example 13, further comprising receiving an initial SidelinkReconfig layer-3 message from a second UE to cause the first UE to provide the Uu RRC message to the gNB.
- Example 17 The method of Example 13, further comprising receiving a message from the gNB to disable alignment.
- Example 18 The method of Example 13, further comprising providing a SidelinkReconfig layer-3 message to a second UE having a PC5 interface with the first UE.
- Example 19 A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a first user equipment (UE) connected mode with a gNB, of entering sidelink (SL) discontinuous reception (DRX) , cause the first UE to: receive from the gNB a Uu DRX MAC control element (CE) layer-2 command to trigger the first UE to enter either Uu or SL DRX indicated in the Uu DRX MAC CE layer-2 command; and process the Uu DRX MAC CE layer-2 command to determine whether to enter Uu DRX or SL DRX with a second UE.
- UE user equipment
- a gNB of entering sidelink (SL) discontinuous reception
- CE Uu DRX MAC control element
- Example 20 The computer-readable storage medium of Example 19, in which the Uu DRX MAC CE layer-2 command includes an index representing one of a predefined Uu DRX configuration or SL DRX configuration.
- Example 21 The computer-readable storage medium of Example 19, wherein the instructions further configure the first UE to RRC signal to configure a look up table so that the Uu DRX MAC CE layer-2 command indicates a DRX configuration.
- Example 22 The computer-readable storage medium of Example 21, in which the Uu DRX MAC CE layer-2 command includes a flag to indicate whether the look up table is be used in Uu, in SL, or in both.
- Example 23 The computer-readable storage medium of Example 21, in which the look up table is a concatenated table for both Uu and SL DRX.
- Example 24 The computer-readable storage medium of Example 21, in which the look up table includes two different tables and the Uu DRX MAC CE layer-2 command includes a flag to indicate which table is used.
- Example 25 A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a user equipment (UE) , cause the UE to: generate for the gNB a first RRC message including a desired SL-DRX configuration; and in response to the first RRC message, receive via Uu from the gNB a second RRC message specifying a DRX configuration for one or both of Uu and PC5 interfaces.
- UE user equipment
- Example 26 The computer-readable storage medium of Example 25, in which the first RRC message comprises a UEAssistance Information (UAI) message include the desired SL-DRX configuration.
- UAI UEAssistance Information
- Example 27 The computer-readable storage medium of Example 25, in which the first RRC message comprises a SidelinkUEInformation (SUI) message include the desired SL-DRX configuration.
- SAI SidelinkUEInformation
- Example 28 The computer-readable storage medium of Example 27, in which SUI or RRC message contain the DRX configurations used by peer UEs.
- Example 29 The computer-readable storage medium of Example 25, in which the first RRC message includes parameters for common DRX operations.
- Example 30 The computer-readable storage medium of Example 25, in which the first RRC message includes parameters for link-specific DRX operations.
- Example 31 A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a first user equipment (UE) , cause the computer to: provide a Uu RRC message to a gNB to report SL engagements and DRX configurations; and receive from the gNB an RRCReconfigure message to align DRX cycles.
- UE user equipment
- Example 32 The computer-readable storage medium of Example 31, in which the Uu RRC message comprises a UEAssistance Information (UAI) message.
- UAI UEAssistance Information
- Example 33 The computer-readable storage medium of Example 31, in which the Uu RRC message comprises a SidelinkUEInformation (SUI) message.
- Uu RRC message comprises a SidelinkUEInformation (SUI) message.
- SUPI SidelinkUEInformation
- Example 34 The computer-readable storage medium of Example 31, wherein the instructions further configure the UE to receive an initial SidelinkReconfig layer-3 message from a second UE to cause the first UE to provide the Uu RRC message to the gNB.
- Example 35 The computer-readable storage medium of Example 31, wherein the instructions further configure the first UE to receive a message from the gNB to disable alignment.
- Example 36 The computer-readable storage medium of Example 31, wherein the instructions further configure the first UE to provide a SidelinkReconfig layer-3 message to a second UE having a PC5 interface with the first UE.
- Example 37 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of the above Examples, or any other method or process described herein.
- Example 38 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of the above Examples, or any other method or process described herein.
- Example 39 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of the above Examples, or any other method or process described herein.
- Example 40 may include a method, technique, or process as described in or related to any of the above Examples, or portions or parts thereof.
- Example 41 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of the above Examples, or portions thereof.
- Example 42 may include a signal as described in or related to any of the above Examples, or portions or parts thereof.
- Example 43 may include a datagram, packet, frame, segment, protocol data unit (PDU) , or message as described in or related to any of the above Examples, or portions or parts thereof, or otherwise described in the present disclosure.
- PDU protocol data unit
- Example 44 may include a signal encoded with data as described in or related to any of the above Examples, or portions or parts thereof, or otherwise described in the present disclosure.
- Example 45 may include a signal encoded with a datagram, packet, frame, segment, PDU, or message as described in or related to any of the above Examples, or portions or parts thereof, or otherwise described in the present disclosure.
- Example 46 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of the above Examples, or portions thereof.
- Example 47 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of the above Examples, or portions thereof.
- Example 48 may include a signal in a wireless network as shown and described herein.
- Example 49 may include a method of communicating in a wireless network as shown and described herein.
- Example 50 may include a system for providing wireless communication as shown and described herein.
- Example 51 may include a device for providing wireless communication as shown and described herein.
- Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system.
- a computer system may include one or more general-purpose or special-purpose computers (or other electronic devices) .
- the computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.
- personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users.
- personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (36)
- A method, performed by a first user equipment (UE) in connected mode with a gNB, of entering sidelink (SL) discontinuous reception (DRX) , the method comprising:receiving from the gNB a Uu DRX MAC control element (CE) layer-2 command to trigger the first UE to enter either Uu or SL DRX indicated in the Uu DRX MAC CE layer-2 command; andprocessing the Uu DRX MAC CE layer-2 command to determine whether to enter Uu DRX or SL DRX with a second UE.
- The method of claim 1, in which the Uu DRX MAC CE layer-2 command includes an index representing one of a predefined Uu DRX configuration or SL DRX configuration.
- The method of claim 1, further comprising RRC signaling to configure a look up table so that the Uu DRX MAC CE layer-2 command indicates a DRX configuration in this configured table.
- The method of claim 3, in which the Uu DRX MAC CE layer-2 command includes a flag to indicate whether the DRX configuration is to be used in Uu, in SL, or in both.
- The method of claim 3, in which the look up table is a concatenated table for both Uu and SL DRX.
- The method of claim 3, in which the look up table includes two different tables and the Uu DRX MAC CE layer-2 command includes a flag to indicate which table is used.
- A method, performed by a first user equipment (UE) in connected mode with a gNB, of configuring sidelink (SL) discontinuous reception (DRX) , the method comprising:generating for the gNB a first RRC message including parameters related to one or more potential SL-DRX configurations; andin response to the first RRC message, receiving via Uu from the gNB a second RRC message specifying a DRX configuration for one or both of Uu and PC5 interfaces.
- The method of claim 7, in which the first RRC message comprises a UEAssistance Information (UAI) message including the parameters related to potential SL-DRX configurations.
- The method of claim 7, in which the first RRC message comprises a SidelinkUEInformation (SUI) message including the parameters related to potential SL-DRX configurations.
- The method of claim 9, in which SUI or RRC message contain the DRX configurations used by peer UEs.
- The method of claim 7, in which the first RRC message includes parameters for common DRX operations.
- The method of claim 7, in which the first RRC message includes parameters for link-specific DRX operations.
- A method, performed by a first user equipment (UE) , of aligning discontinuous reception (DRX) over Uu and sidelink (SL) by restriction of Uu-DRX configuration to those aligned with SL-DRX, the method comprising:providing a Uu RRC message to a gNB to report SL engagements and DRX configurations; andreceiving from the gNB an RRCReconfigure message to align DRX cycles.
- The method of claim 13, in which the Uu RRC message comprises a UEAssistance Information (UAI) message.
- The method of claim 13, in which the Uu RRC message comprises a SidelinkUEInformation (SUI) message.
- The method of claim 13, further comprising receiving an initial SidelinkReconfig layer-3 message from a second UE to cause the first UE to provide the Uu RRC message to the gNB.
- The method of claim 13, further comprising receiving a message from the gNB to disable alignment.
- The method of claim 13, further comprising providing a SidelinkReconfig layer-3 message to a second UE having a PC5 interface with the first UE.
- A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a first user equipment (UE) connected mode with a gNB, of entering sidelink (SL) discontinuous reception (DRX) , cause the first UE to:receive from the gNB a Uu DRX MAC control element (CE) layer-2 command to trigger the first UE to enter either Uu or SL DRX indicated in the Uu DRX MAC CE layer-2 command; andprocess the Uu DRX MAC CE layer-2 command to determine whether to enter Uu DRX or SL DRX with a second UE.
- The computer-readable storage medium of claim 19, in which the Uu DRX MAC CE layer-2 command includes an index representing one of a predefined Uu DRX configuration or SL DRX configuration.
- The computer-readable storage medium of claim 19, wherein the instructions further configure the first UE to RRC signal to configure a look up table so that the Uu DRX MAC CE layer-2 command indicates a DRX configuration.
- The computer-readable storage medium of claim 21, in which the Uu DRX MAC CE layer-2 command includes a flag to indicate whether the look up table is be used in Uu, in SL, or in both.
- The computer-readable storage medium of claim 21, in which the look up table is a concatenated table for both Uu and SL DRX.
- The computer-readable storage medium of claim 21, in which the look up table includes two different tables and the Uu DRX MAC CE layer-2 command includes a flag to indicate which table is used.
- A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a user equipment (UE) , cause the UE to:generate for the gNB a first RRC message including parameters related to one or more potential SL-DRX configurations; andin response to the first RRC message, receive via Uu from the gNB a second RRC message specifying a DRX configuration for one or both of Uu and PC5 interfaces.
- The computer-readable storage medium of claim 25, in which the first RRC message comprises a UEAssistance Information (UAI) message include the parameters related to one or more potential SL-DRX configurations.
- The computer-readable storage medium of claim 25, in which the first RRC message comprises a SidelinkUEInformation (SUI) message include the parameters related to one or more potential SL-DRX configurations.
- The computer-readable storage medium of claim 27, in which SUI or RRC message contain the DRX configurations used by peer UEs.
- The computer-readable storage medium of claim 25, in which the first RRC message includes parameters for common DRX operations.
- The computer-readable storage medium of claim 25, in which the first RRC message includes parameters for link-specific DRX operations.
- A non-transitory computer-readable storage medium, the computer-readable storage medium including instructions that when executed by a first user equipment (UE) , cause the computer to:provide a Uu RRC message to a gNB to report SL engagements and DRX configurations; andreceive from the gNB an RRCReconfigure message to align DRX cycles.
- The computer-readable storage medium of claim 31, in which the Uu RRC message comprises a UEAssistance Information (UAI) message.
- The computer-readable storage medium of claim 31, in which the Uu RRC message comprises a SidelinkUEInformation (SUI) message.
- The computer-readable storage medium of claim 31, wherein the instructions further configure the UE to receive an initial SidelinkReconfig layer-3 message from a second UE to cause the first UE to provide the Uu RRC message to the gNB.
- The computer-readable storage medium of claim 31, wherein the instructions further configure the first UE to receive a message from the gNB to disable alignment.
- The computer-readable storage medium of claim 31, wherein the instructions further configure the first UE to provide a SidelinkReconfig layer-3 message to a second UE having a PC5 interface with the first UE.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US17/593,552 US20220312543A1 (en) | 2020-10-22 | 2020-10-22 | Sidelink drx optimizations for rrc_connected user equipment (ue) |
PCT/CN2020/122962 WO2022082647A1 (en) | 2020-10-22 | 2020-10-22 | Sidelink drx optimizations for rrc_connected user equipment (ue) |
EP20958229.5A EP4229922A4 (en) | 2020-10-22 | 2020-10-22 | Sidelink drx optimizations for rrc_connected user equipment (ue) |
CN202080107166.7A CN116458214A (en) | 2020-10-22 | 2020-10-22 | Side link DRX optimization for RRC_CONNECTED User Equipment (UE) |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2020/122962 WO2022082647A1 (en) | 2020-10-22 | 2020-10-22 | Sidelink drx optimizations for rrc_connected user equipment (ue) |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022082647A1 true WO2022082647A1 (en) | 2022-04-28 |
Family
ID=81291439
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2020/122962 WO2022082647A1 (en) | 2020-10-22 | 2020-10-22 | Sidelink drx optimizations for rrc_connected user equipment (ue) |
Country Status (4)
Country | Link |
---|---|
US (1) | US20220312543A1 (en) |
EP (1) | EP4229922A4 (en) |
CN (1) | CN116458214A (en) |
WO (1) | WO2022082647A1 (en) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN114080066B (en) * | 2020-08-20 | 2024-02-27 | 维沃移动通信有限公司 | Discontinuous Reception (DRX) processing method and device, terminal and network side equipment |
US20220264376A1 (en) * | 2021-02-12 | 2022-08-18 | Qualcomm Incorporated | Techniques for sidelink resource reservations |
US11956849B2 (en) * | 2021-09-23 | 2024-04-09 | Qualcomm Incorporated | Discontinuous reception (DRX) configuration for a user equipment (UE) |
US11963256B2 (en) * | 2021-10-27 | 2024-04-16 | Qualcomm Incorporated | Signaling of joint alignment of Uu DRX and SL DRX |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018016882A1 (en) * | 2016-07-21 | 2018-01-25 | Samsung Electronics Co., Ltd. | A system and method for discovering user equipment (ue) over side link in device to device (d2d) communication |
WO2018082541A1 (en) * | 2016-11-04 | 2018-05-11 | Huizhou Tcl Mobile Communication Co., Ltd | Paging and connection establishment via relay devices in a wireless communication system |
US20190174411A1 (en) * | 2016-08-11 | 2019-06-06 | Sony Corporation | Electronic device and method used for network control terminal and network node |
-
2020
- 2020-10-22 EP EP20958229.5A patent/EP4229922A4/en active Pending
- 2020-10-22 US US17/593,552 patent/US20220312543A1/en active Pending
- 2020-10-22 WO PCT/CN2020/122962 patent/WO2022082647A1/en active Application Filing
- 2020-10-22 CN CN202080107166.7A patent/CN116458214A/en active Pending
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018016882A1 (en) * | 2016-07-21 | 2018-01-25 | Samsung Electronics Co., Ltd. | A system and method for discovering user equipment (ue) over side link in device to device (d2d) communication |
US20190174411A1 (en) * | 2016-08-11 | 2019-06-06 | Sony Corporation | Electronic device and method used for network control terminal and network node |
WO2018082541A1 (en) * | 2016-11-04 | 2018-05-11 | Huizhou Tcl Mobile Communication Co., Ltd | Paging and connection establishment via relay devices in a wireless communication system |
Non-Patent Citations (3)
Title |
---|
HUAWEI, HISILICON: "Alignment between Uu DRX and SL DRX", 3GPP DRAFT; R2-2101764, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200125 - 20200205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051974629 * |
QUALCOMM INCORPORATED, LG ELECTRONICS: "New Solution: QoS aware power efficient PC5 communication", 3GPP DRAFT; S2-2004714, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. E (e-meeting); 20200601 - 20200612, 13 June 2020 (2020-06-13), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051899010 * |
See also references of EP4229922A4 * |
Also Published As
Publication number | Publication date |
---|---|
EP4229922A1 (en) | 2023-08-23 |
EP4229922A4 (en) | 2023-12-20 |
US20220312543A1 (en) | 2022-09-29 |
CN116458214A (en) | 2023-07-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2022082647A1 (en) | Sidelink drx optimizations for rrc_connected user equipment (ue) | |
WO2022082639A1 (en) | Sidelink (sl) discontinuous reception (drx) for unicast, connection-specific drx | |
US20220302989A1 (en) | Systems and methods for beam failure recovery for multi-dci mode | |
US20230239955A1 (en) | Cross-mode coordination and mode 1 support for inter-ue coordination | |
US20240080790A1 (en) | Service access restriction enhancements for 5g new radio (nr) | |
US20220312248A1 (en) | Measurement objects merging for nr unlicensed spectrums | |
US20220360311A1 (en) | Full power transmission mode 2 tpmi list signaling enhancement | |
US20220312393A1 (en) | Physical downlink control channel (pdcch) reliability enhancement | |
US20230199718A1 (en) | Inter-ue coordination for on-demand sensing | |
US20240073988A1 (en) | Proactive grant allocation during a radio resource control (rrc) reestablishment procedure | |
US11490306B2 (en) | Reducing RNA update procedures and improving RACH efficiency | |
US11902937B2 (en) | Wake-up signal (WUS) design and configuration for paging | |
WO2022205710A1 (en) | Method and apparatus for handover procedures | |
WO2024031249A1 (en) | Method and apparatus for pdu set based scheduling | |
WO2023029012A1 (en) | Method and apparatus for up enhancement |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20958229 Country of ref document: EP Kind code of ref document: A1 |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112023007319 Country of ref document: BR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202080107166.7 Country of ref document: CN |
|
ENP | Entry into the national phase |
Ref document number: 2020958229 Country of ref document: EP Effective date: 20230518 |
|
ENP | Entry into the national phase |
Ref document number: 112023007319 Country of ref document: BR Kind code of ref document: A2 Effective date: 20230419 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |