[go: up one dir, main page]

WO2023211171A1 - Procédé et appareil d'optimisation de c-drx - Google Patents

Procédé et appareil d'optimisation de c-drx Download PDF

Info

Publication number
WO2023211171A1
WO2023211171A1 PCT/KR2023/005735 KR2023005735W WO2023211171A1 WO 2023211171 A1 WO2023211171 A1 WO 2023211171A1 KR 2023005735 W KR2023005735 W KR 2023005735W WO 2023211171 A1 WO2023211171 A1 WO 2023211171A1
Authority
WO
WIPO (PCT)
Prior art keywords
drx
starting
ondurationtimer
location
candidate locations
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/KR2023/005735
Other languages
English (en)
Inventor
Min Wu
Sa ZHANG
Feifei SUN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Publication of WO2023211171A1 publication Critical patent/WO2023211171A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0248—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • H04L27/26—Systems using multi-frequency codes
    • H04L27/2601—Multicarrier modulation systems
    • H04L27/2602—Signal structure
    • H04L27/26025—Numerology, i.e. varying one or more of symbol duration, subcarrier spacing, Fourier transform size, sampling rate or down-clocking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] 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 leader and terminal is follower
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is leader and terminal is follower using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal where the received signal is a power saving command
    • 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

  • the present disclosure relates generally to wireless communication systems and, more specifically, the present disclosure relates to discontinuous reception (DRX) mechanism optimization in a wireless communication system.
  • DRX discontinuous reception
  • 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz.
  • 6G mobile communication technologies referred to as Beyond 5G systems
  • terahertz bands for example, 95GHz to 3THz bands
  • IIoT Industrial Internet of Things
  • IAB Integrated Access and Backhaul
  • DAPS Dual Active Protocol Stack
  • 5G baseline architecture for example, service based architecture or service based interface
  • NFV Network Functions Virtualization
  • SDN Software-Defined Networking
  • MEC Mobile Edge Computing
  • multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
  • FD-MIMO Full Dimensional MIMO
  • OAM Organic Angular Momentum
  • RIS Reconfigurable Intelligent Surface
  • an aspect of the present invention provides a method and apparatus for C-DRX optimization.
  • the present disclosure relates to wireless communication systems and, more specifically, the present disclosure relates to solve the problem that the discontinuous reception (DRX) mechanism is not matched with the arrival time of service data.
  • DRX discontinuous reception
  • a method executed by a UE in a communication system including steps of: acquiring related information of a plurality of candidate locations within a DRX cycle, the candidate locations being used for starting a drx-onDurationTimer; and starting or not starting the drx-onDurationTimer based on the related information.
  • the related information of the plurality of candidate locations includes at least one of the following: related information of a starting window of the drx-onDurationTimer where the plurality of candidate locations are located, and/or location related information of the plurality of candidate locations within the starting window; a gap between any two adjacent candidate locations among the plurality of candidate locations, and/or a number of candidate locations within the DRX cycle; and an offset of each of the plurality of candidate locations relative to a starting location of the DRX cycle.
  • the starting location of the starting window is the starting location of the DRX cycle; and/or, the length of the starting window is predefined or configured by a base station through a high-layer signaling.
  • each time unit within the starting window is a candidate location; or, some of time units within the starting window are candidate locations.
  • the plurality of candidate locations are configured by a bit map, the length of the bit map corresponds to the length of the starting window, and each bit in the bit map is used for indicating whether the corresponding time unit is a candidate location or not; or, any two adjacent candidate locations among the plurality of candidate locations are equally spaced, and the first candidate location among the plurality of candidate locations is the starting location of the DRX cycle.
  • the length of the starting window is not greater than that of the DRX cycle.
  • the gap between any two adjacent candidate locations is configured by the base station through a high-layer signaling
  • the number of candidate locations within the DRX cycle is configured by the base station through a high-layer signaling
  • the first candidate location among the plurality of candidate locations is the starting location of the DRX cycle.
  • the number of times of starting the drx-onDurationTimer within the DRX cycle is predefined or preconfigured; and/or, the drx-onDurationTimer is started at most once within the DRX cycle.
  • the gap between two adjacent startings of the drx-onDurationTimer is not less than a first gap.
  • the method further includes: monitoring a wakeup indication transmitted by the base station in a DRX inactive time; and the starting or not starting the drx-onDurationTimer based on the related information includes: based on the wakeup indication and the related information, starting or not starting the drx-onDurationTimer at the first candidate location after the wakeup indication is received.
  • the method further includes: monitoring a wakeup indication transmitted by the base station in a DRX inactive time; and the starting or not starting the drx-onDurationTimer based on the related information includes: based on the wakeup indication and the related information, not starting the drx-onDurationTimer at each of the remaining candidate locations within the DRX cycle after the wakeup indication is received.
  • the wakeup indication is carried by downlink control information (DCI) and/or a physical signal sequence.
  • DCI downlink control information
  • the method further includes: monitoring the wakeup indication in a first time window corresponding to the DRX cycle; and/or, monitoring the wakeup indication in second time windows respectively corresponding to the plurality of candidate locations.
  • the starting location of the first time window is determined based on a first offset before the starting location of the DRX cycle; and/or, an ending location of the first time window is determined based on the starting location of the first time window and the length of the first time window, or the ending location of the first time window is determined based on a second gap before the last candidate location within the DRX cycle.
  • the starting location of each of the second time windows is determined based on a second offset before the corresponding candidate location; and/or, the ending location of each of the second time windows is determined based on the starting location of the second time window and the length of the second time window, or the ending location of each of the second time windows is determined based on a third gap before the corresponding candidate location.
  • At least one of the first offset, the second offset and the length of the time window is predefined or configured by the base station through a high-layer signaling.
  • the second gap or the third gap includes at least one of the following situations: it is a gap reported by the UE; its granularity is a time unit; and the size of the gap is determined based on a subcarrier spacing of a downlink active bandwidth part (BWP) of the UE.
  • BWP downlink active bandwidth part
  • the DCI carrying the wakeup indication is of a specific DCI format
  • the wakeup indication field of the specific DCI format is used for indicating to start or not start the drx-onDurationTimer at the first candidate location after the specific DCI format is received.
  • the DCI carrying the wakeup indication is of a specific DCI format
  • the specific DCI format is configured to include at least one of the following indication fields: a field for indicating a downlink active BWP used firstly after a drx-onDurationTimer is started; a field for indicating a search space set group (SSSG) monitored firstly after the drx-onDurationTimer is started; a field for indicating the size of the drx-onDurationTimer; and a field for jointly indicating the wakeup indication and at least one of the downlink active BWP used firstly and the SSSG monitored firstly after the drx-onDurationTimer is started, and the size of the drx-onDurationTimer.
  • SSSG search space set group
  • the downlink active BWP used firstly after the drx-onDurationTimer is started includes at least one of the following: a downlink active BWP used firstly configured by a high-layer parameter; a downlink default BWP configured by a high-layer parameter; a downlink initial BWP configured by a high-layer parameter; and a dedicated BWP preconfigured by the base station.
  • the SSSG monitored firstly includes at least one of the following: a predefined SSSG; and a dedicated SSSG preconfigured by the base station.
  • a method executed by a base station in a communication system including steps of: transmitting, to a UE, related information of a plurality of candidate locations within a DRX cycle, so that the UE starts a drx-onDurationTimer based on the related information.
  • a user equipment including: a transceiver, which is configured to transmit and receive signals; and a controller, which is coupled to the transceiver and configured to control to execute the steps of the method executed by a UE provided in the embodiments of the present application.
  • a base station including: a transceiver, which is configured to transmit and receive signals; and a controller, which is coupled to the transceiver and configured to control to execute the steps of the method executed by a base station provided in the embodiments of the present application.
  • a computer-readable storage medium having computer programs stored thereon that, when executed by a processor, implement the steps of the method executed by a UE provided in the embodiments of the present application.
  • a computer-readable storage medium having computer programs stored thereon that, when executed by a processor, implement the steps of the method executed by a base station provided in the embodiments of the present application.
  • a computer program product including computer programs that, when executed by a processor, implement the steps of the method executed by a UE provided in the embodiments of the present application.
  • a computer program product including computer programs that, when executed by a processor, implement the steps of the method executed by a base station provided in the embodiments of the present application.
  • Couple and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another.
  • transmit and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication.
  • the term “or” is inclusive, meaning and/or.
  • controller means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and/or firmware. The functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.
  • phrases "at least one of,” when used with a list of items, means that different combinations of one or more of the listed items may be used, and only one item in the list may be needed.
  • “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.
  • various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium.
  • application and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code.
  • computer readable program code includes any type of computer code, including source code, object code, and executable code.
  • computer readable medium includes any type of medium capable of being accessed by a computer, such as read only memory (ROM), random access memory (RAM), a hard disk drive, a compact disc (CD), a digital video disc (DVD), or any other type of memory.
  • ROM read only memory
  • RAM random access memory
  • CD compact disc
  • DVD digital video disc
  • a "non-transitory” computer readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals.
  • a non-transitory computer readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.
  • a UE can dynamically adjust time points of starting the drx-onDurationTimer in different DRX cycles, thereby achieving the purpose of matching with the actual arrival time of an XR service, and minimizing the power consumption of the UE while ensuring the transmission delay.
  • FIG. 1 is a schematic diagram of an overall structure of a wireless network according to an embodiment of the present application
  • FIG. 2a is a schematic diagram of a transmission path according to an embodiment of the present application.
  • FIG. 2b is a schematic diagram of a reception path according to an embodiment of the present application.
  • FIG. 3a is a schematic structure diagram of a UE according to an embodiment of the present application.
  • FIG. 3b is a schematic structure diagram of a base station according to an embodiment of the present application.
  • FIG. 4 is a flowchart of a method executed by a UE according to an embodiment of the present application
  • FIG. 5 is a schematic diagram of candidate locations where the drx-onDurationTimer may be started according to an embodiment of the present application
  • FIG. 6 is a schematic diagram of a starting window where the drx-onDurationTimer is started according to an embodiment of the present application
  • FIG. 7 is a schematic diagram of a starting window where the drx-onDurationTimer may be started and a time window where the DCI format 2-6 is monitored according to an embodiment of the present application.
  • FIG. 8 is a schematic structure diagram of an electronic device according to an embodiment of the present application.
  • the term “include” or “may include” refers to the existence of a corresponding disclosed function, operation or component which can be used in various embodiments of the present application and does not limit one or more additional functions, operations, or components.
  • the terms such as “include” and/or “have” may be construed to denote a certain characteristic, number, step, operation, constituent element, component or a combination thereof, but may not be construed to exclude the existence of or a possibility of addition of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.
  • a or B may include A, may include B, or may include both A and B.
  • FIG. 1 illustrates an example wireless network 100 according to various embodiments of the present application.
  • the embodiment of the wireless network 100 shown in FIG. 1 is for illustration only. Other embodiments of the wireless network 100 can be used without departing from the scope of the present application.
  • the wireless network 100 includes a gNodeB (gNB) 101, a gNB 102, and a gNB 103.
  • gNB 101 communicates with gNB 102 and gNB 103.
  • gNB 101 also communicates with at least one Internet Protocol (IP) network 130, such as the Internet, a private IP network, or other data networks.
  • IP Internet Protocol
  • gNodeB base station
  • access point can be used instead of “gNodeB” or “gNB”.
  • gNodeB and gNB are used in this patent document to refer to network infrastructure components that provide wireless access for remote terminals.
  • other well-known terms such as “mobile station”, “user station”, “remote terminal”, “wireless terminal” or “user apparatus” can be used instead of “user equipment” or “UE”.
  • the terms "user equipment” and "UE” are used in this patent document to refer to remote wireless devices that wirelessly access the gNB, no matter whether the UE is a mobile device (such as a mobile phone or a smart phone) or a fixed device (such as a desktop computer or a vending machine).
  • the GNB 102 provides wireless broadband access to the network 130 for a first plurality of User Equipments (UEs) within a coverage area 120 of gNB 102.
  • the first plurality of UEs include a UE 111, which may be located in a Small Business (SB); a UE 112, which may be located in an enterprise (E); a UE 113, which may be located in a WiFi Hotspot (HS); a UE 114, which may be located in a first residence (R); a UE 115, which may be located in a second residence (R); a UE 116, which may be a mobile device (M), such as a cellular phone, a wireless laptop computer, a wireless PDA, etc.
  • M mobile device
  • GNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within a coverage area 125 of gNB 103.
  • the second plurality of UEs include a UE 115 and a UE 116.
  • one or more of gNBs 101-103 can communicate with each other and with UEs 111-116 using 5G, Long Term Evolution (LTE), LTE-A, WiMAX or other advanced wireless communication technologies.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-A
  • WiMAX Worldwide Interoperability for Microwave Access
  • the dashed lines show approximate ranges of the coverage areas 120 and 125, and the ranges are shown as approximate circles merely for illustration and explanation purposes. It should be clearly understood that the coverage areas associated with the gNBs, such as the coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on configurations of the gNBs and changes in the radio environment associated with natural obstacles and man-made obstacles.
  • one or more of gNB 101, gNB 102, and gNB 103 include a 2D antenna array as described in embodiments of the present application.
  • one or more of gNB 101, gNB 102, and gNB 103 support codebook designs and structures for systems with 2D antenna arrays.
  • the wireless network 100 can include any number of gNBs and any number of UEs in any suitable arrangement, for example.
  • gNB 101 can directly communicate with any number of UEs and provide wireless broadband access to the network 130 for those UEs.
  • each gNB 102-103 can directly communicate with the network 130 and provide direct wireless broadband access to the network 130 for the UEs.
  • gNB 101, 102 and/or 103 can provide access to other or additional external networks, such as external telephone networks or other types of data networks.
  • FIGs. 2a and 2b illustrate example wireless transmission and reception paths according to the present application.
  • the transmission path 200 can be described as being implemented in a gNB, such as gNB 102
  • the reception path 250 can be described as being implemented in a UE, such as UE 116.
  • the reception path 250 can be implemented in a gNB and the transmission path 200 can be implemented in a UE.
  • the reception path 250 is configured to support codebook designs and structures for systems with 2D antenna arrays as described in embodiments of the present application.
  • the transmission path 200 includes a channel coding and modulation block 205, a Serial-to-Parallel (S-to-P) block 210, a size N Inverse Fast Fourier Transform (IFFT) block 215, a Parallel-to-Serial (P-to-S) block 220, a cyclic prefix addition block 225, and an up-converter (UC) 230.
  • S-to-P Serial-to-Parallel
  • IFFT Inverse Fast Fourier Transform
  • P-to-S Parallel-to-Serial
  • UC up-converter
  • the reception path 250 includes a down-converter (DC) 255, a cyclic prefix removal block 260, a Serial-to-Parallel (S-to-P) block 265, a size N Fast Fourier Transform (FFT) block 270, a Parallel-to-Serial (P-to-S) block 275, and a channel decoding and demodulation block 280.
  • DC down-converter
  • S-to-P Serial-to-Parallel
  • FFT Fast Fourier Transform
  • P-to-S Parallel-to-Serial
  • the channel coding and modulation block 205 receives a set of information bits, applies coding (such as Low Density Parity Check (LDPC) coding), and modulates the input bits (such as using Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) to generate a sequence of frequency-domain modulated symbols.
  • coding such as Low Density Parity Check (LDPC) coding
  • QPSK Quadrature Phase Shift Keying
  • QAM Quadrature Amplitude Modulation
  • the Serial-to-P) block 210 converts (such as demultiplexes) serial modulated symbols into parallel data to generate N parallel symbol streams, where N is a size of the IFFT/FFT used in gNB 102 and UE 116.
  • the size N IFFT block 215 performs IFFT operations on the N parallel symbol streams to generate a time-domain output signal.
  • the Parallel-to-Serial block 220 converts (such as multiplexes) parallel time-domain output symbols from the Size N IFFT block 215 to generate a serial time-domain signal.
  • the cyclic prefix addition block 225 inserts a cyclic prefix into the time-domain signal.
  • the up-converter 230 modulates (such as up-converts) the output of the cyclic prefix addition block 225 to an RF frequency for transmission via a wireless channel.
  • the signal can also be filtered at a baseband before converting to the RF frequency.
  • the RF signal transmitted from gNB 102 arrives at UE 116 after passing through the wireless channel, and operations in reverse to those at gNB 102 are performed at UE 116.
  • the down-converter 255 down-converts the received signal to a baseband frequency
  • the cyclic prefix removal block 260 removes the cyclic prefix to generate a serial time-domain baseband signal.
  • the Serial-to-Parallel block 265 converts the time-domain baseband signal into a parallel time-domain signal.
  • the Size N FFT block 270 performs an FFT algorithm to generate N parallel frequency-domain signals.
  • the Parallel-to-Serial block 275 converts the parallel frequency-domain signal into a sequence of modulated data symbols.
  • the channel decoding and demodulation block 280 demodulates and decodes the modulated symbols to recover the original input data stream.
  • Each of gNBs 101-103 may implement a transmission path 200 similar to that for transmitting to UEs 111-116 in the downlink, and may implement a reception path 250 similar to that for receiving from UEs 111-116 in the uplink.
  • each of UEs 111-116 may implement a transmission path 200 for transmitting to gNBs 101-103 in the uplink, and may implement a reception path 250 for receiving from gNBs 101-103 in the downlink.
  • Each of the components in FIGs. 2a and 2b can be implemented using only hardware, or using a combination of hardware and software/firmware.
  • at least some of the components in FIGs. 2a and 2b may be implemented in software, while other components may be implemented in configurable hardware or a combination of software and configurable hardware.
  • the FFT block 270 and IFFT block 215 may be implemented as configurable software algorithms, in which the value of the size N may be modified according to the implementation.
  • variable N may be any integer (such as 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of variable N may be any integer which is a power of 2 (such as 1, 2, 4, 8, 16, etc.).
  • FIGs. 2a and 2b illustrate examples of wireless transmission and reception paths
  • various changes may be made to FIGs. 2a and 2b.
  • various components in FIGs. 2a and 2b can be combined, further subdivided or omitted, and additional components can be added according to specific requirements.
  • FIGs. 2a and 2b are intended to illustrate examples of types of transmission and reception paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.
  • FIG. 3a illustrates an example UE 116 according to the present application.
  • the embodiment of UE 116 shown in FIG. 3a is for illustration only, and UEs 111-115 of FIG. 1 can have the same or similar configuration.
  • a UE has various configurations, and FIG. 3a does not limit the scope of the present application to any specific implementation of the UE.
  • UE 116 includes an antenna 305, a radio frequency (RF) transceiver 310, a transmission (TX) processing circuit 315, a microphone 320, and a reception (RX) processing circuit 325.
  • UE 116 also includes a speaker 330, a processor/controller 340, an input/output (I/O) interface 345, an input device(s) 350, a display 355, and a memory 360.
  • the memory 360 includes an operating system (OS) 361 and one or more applications 362.
  • OS operating system
  • applications 362 one or more applications
  • the RF transceiver 310 receives an incoming RF signal transmitted by a gNB of the wireless network 100 from the antenna 305.
  • the RF transceiver 310 down-converts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal.
  • the IF or baseband signal is transmitted to the RX processing circuit 325, where the RX processing circuit 325 generates a processed baseband signal by filtering, decoding and/or digitizing the baseband or IF signal.
  • the RX processing circuit 325 transmits the processed baseband signal to speaker 330 (such as for voice data) or to processor/controller 340 for further processing (such as for web browsing data).
  • the TX processing circuit 315 receives analog or digital voice data from microphone 320 or other outgoing baseband data (such as network data, email or interactive video game data) from processor/controller 340.
  • the TX processing circuit 315 encodes, multiplexes, and/or digitizes the outgoing baseband data to generate a processed baseband or IF signal.
  • the RF transceiver 310 receives the outgoing processed baseband or IF signal from the TX processing circuit 315 and up-converts the baseband or IF signal into an RF signal transmitted via the antenna 305.
  • the processor/controller 340 can include one or more processors or other processing devices and execute an OS 361 stored in the memory 360 in order to control the overall operation of UE 116.
  • the processor/controller 340 can control the reception of forward channel signals and the transmission of backward channel signals through the RF transceiver 310, the RX processing circuit 325 and the TX processing circuit 315 according to well-known principles.
  • the processor/controller 340 includes at least one microprocessor or microcontroller.
  • the processor/controller 340 is also capable of executing other processes and programs residing in the memory 360, such as operations for channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the present application.
  • the processor/controller 340 can move data into or out of the memory 360 as required by an execution process.
  • the processor/controller 340 is configured to execute the application 362 based on the OS 361 or in response to signals received from the gNB or the operator.
  • the processor/controller 340 is also coupled to an I/O interface 345, where the I/O interface 345 provides UE 116 with the ability to connect to other devices such as laptop computers and handheld computers. I/O interface 345 is a communication path between these accessories and the processor/controller 340.
  • the processor/controller 340 is also coupled to the input device(s) 350 and the display 355. An operator of UE 116 can input data into UE 116 using the input device(s) 350.
  • the display 355 may be a liquid crystal display or other display capable of presenting text and/or at least limited graphics (such as from a website).
  • the memory 360 is coupled to the processor/controller 340. A part of the memory 360 can include a random access memory (RAM), while another part of the memory 360 can include a flash memory or other read-only memory (ROM).
  • FIG. 3a illustrates an example of UE 116
  • various changes can be made to FIG. 3a.
  • various components in FIG. 3a can be combined, further subdivided or omitted, and additional components can be added according to specific requirements.
  • the processor/controller 340 can be divided into a plurality of processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs).
  • FIG. 3a illustrates that the UE 116 is configured as a mobile phone or a smart phone, UEs can be configured to operate as other types of mobile or fixed devices.
  • FIG. 3b illustrates an example gNB 102 according to the present application.
  • the embodiment of gNB 102 shown in FIG. 3b is for illustration only, and other gNBs of FIG. 1 can have the same or similar configuration.
  • a gNB has various configurations, and FIG. 3b does not limit the scope of the present application to any specific implementation of a gNB.
  • gNB 101 and gNB 103 can include the same or similar structures as gNB 102.
  • gNB 102 includes a plurality of antennas 370a-370n, a plurality of RF transceivers 372a-372n, a transmission (TX) processing circuit 374, and a reception (RX) processing circuit 376.
  • one or more of the plurality of antennas 370a-370n include a 2D antenna array.
  • gNB 102 also includes a controller/processor 378, a memory 380, and a backhaul or network interface 382.
  • RF transceivers 372a-372n receive an incoming RF signal from antennas 370a-370n, such as a signal transmitted by UEs or other gNBs. RF transceivers 372a-372n down-convert the incoming RF signal to generate an IF or baseband signal. The IF or baseband signal is transmitted to the RX processing circuit 376, where the RX processing circuit 376 generates a processed baseband signal by filtering, decoding and/or digitizing the baseband or IF signal. RX processing circuit 376 transmits the processed baseband signal to controller/processor 378 for further processing.
  • the TX processing circuit 374 receives analog or digital data (such as voice data, network data, email or interactive video game data) from the controller/processor 378.
  • TX processing circuit 374 encodes, multiplexes and/or digitizes outgoing baseband data to generate a processed baseband or IF signal.
  • RF transceivers 372a-372n receive the outgoing processed baseband or IF signal from TX processing circuit 374 and up-convert the baseband or IF signal into an RF signal transmitted via antennas 370a-370n.
  • the controller/processor 378 can include one or more processors or other processing devices that control the overall operation of gNB 102.
  • the controller/processor 378 can control the reception of forward channel signals and the transmission of backward channel signals through the RF transceivers 372a-372n, the RX processing circuit 376 and the TX processing circuit 374 according to well-known principles.
  • the controller/processor 378 can also support additional functions, such as higher-level wireless communication functions.
  • the controller/processor 378 can perform a Blind Interference Sensing (BIS) process such as that performed through a BIS algorithm, and decode a received signal from which an interference signal is subtracted.
  • a controller/processor 378 may support any of a variety of other functions in gNB 102.
  • the controller/processor 378 includes at least one microprocessor or microcontroller.
  • the controller/processor 378 is also capable of executing programs and other processes residing in the memory 380, such as a basic OS.
  • the controller/processor 378 can also support channel quality measurement and reporting for systems with 2D antenna arrays as described in embodiments of the present application.
  • the controller/processor 378 supports communication between entities such as web RTCs.
  • the controller/processor 378 can move data into or out of the memory 380 as required by an execution process.
  • the controller/processor 378 is also coupled to the backhaul or network interface 382.
  • the backhaul or network interface 382 allows gNB 102 to communicate with other devices or systems through a backhaul connection or through a network.
  • the backhaul or network interface 382 can support communication over any suitable wired or wireless connection(s).
  • gNB 102 is implemented as a part of a cellular communication system, such as a cellular communication system supporting 5G or new radio access technology or NR, LTE or LTE-A
  • the backhaul or network interface 382 can allow gNB 102 to communicate with other gNBs through wired or wireless backhaul connections.
  • the backhaul or network interface 382 can allow gNB 102 to communicate with a larger network, such as the Internet, through a wired or wireless local area network or through a wired or wireless connection.
  • the backhaul or network interface 382 includes any suitable structure that supports communication through a wired or wireless connection, such as an Ethernet or an RF transceiver.
  • the memory 380 is coupled to the controller/processor 378.
  • a part of the memory 380 can include an RAM, while another part of the memory 380 can include a flash memory or other ROMs.
  • a plurality of instructions, such as the BIS algorithm are stored in the memory. The plurality of instructions are configured to cause the controller/processor 378 to execute the BIS process and decode the received signal after subtracting at least one interference signal determined by the BIS algorithm.
  • the transmission and reception paths of gNB 102 (implemented using RF transceivers 372a-372n, TX processing circuit 374 and/or RX processing circuit 376) support aggregated communication with FDD cells and TDD cells.
  • FIG. 3b illustrates an example of gNB 102
  • gNB 102 can include any number of each component shown in FIG. 3a.
  • the access point can include many backhaul or network interfaces 382, and the controller/processor 378 can support routing functions to route data between different network addresses.
  • gNB 102 can include multiple instances of each (such as one for each RF transceiver).
  • the UE in a radio resource control (RRC) connected state may be configured with DRX, the UE starts the drx-onDurationTimer (drx-onDurationTimer) at the starting location of each DRX cycle, and the size of the drx-onDurationTimer may be less than that of the DRX cycle.
  • RRC radio resource control
  • the UE can maintain a period of active time and a period of inactive time in each DRX cycle.
  • the UE needs to monitor physical downlink control channels (PDCCHs) in the active time, but does not need to monitor PDCCHs in the inactive time.
  • PDCCHs physical downlink control channels
  • Continuous PDCCH monitoring is the main reason for the power consumption of the terminal, and the DRX technology can achieve of the purpose of saving power of the terminal by discontinuous PDCCH monitoring.
  • the duration of the active time is the duration of the drx-onDurationTimer
  • the inactive time is the time other than the active time within the DRX cycle.
  • the base station may configure the size of the DRX cycle and the starting location of the DRX cycle according to the cycle and arrival time of data service of the UE, so that the DRX is matched with the service of the UE, thereby achieving the purpose of saving power. That is, the data that arrives periodically can be transmitted in the active time of each DRX cycle, and the UE enters the inactive time of the DRX at the end of transmission to realize power saving.
  • the active time is prolonged through a DRX inactive timer (drx-inactivityTimer) and a DRX retransmission timer (drx-retransmissionTimer).
  • drx-inactivityTimer a DRX inactive timer
  • drx-retransmissionTimer a DRX retransmission timer
  • the UE receives new data scheduling, the UE starts the drx-inactivityTimer and DRX-HARQ (Hybrid Automatic Repeat Request) timer, and the UE may start the drx-retransmissionTimer after the expirationof the drx-HARQTimer.
  • the UE needs to monitor a PDCCH, i.e., the UE maintains the active time of continuous DRX; or, the base station may issue a DRX control instruction to instruct the UE to end the active time of the DRX in advance, that is, the UE enters the inactive time of the DRX from the active time of the RX without waiting for the expiration of the drx-onDurationTimer.
  • a PDCCH i.e., the UE maintains the active time of continuous DRX
  • the base station may issue a DRX control instruction to instruct the UE to end the active time of the DRX in advance, that is, the UE enters the inactive time of the DRX from the active time of the RX without waiting for the expiration of the drx-onDurationTimer.
  • a signaling for indicating whether the UE starts the drx-onDurationTimer at the starting location of one DRX cycle is introduced. This signaling is indicated by a 1-bit wakeup indication field contained in a downlink control information (DCI) format 2-6.
  • DCI downlink control information
  • the UE If the indication value is "1", the UE starts the drx-onDurationTimer at the starting location of a next long DRX cycle; and, if the indication value is "0", the UE does not starts the drx-onDurationTimer at the starting location of a next long DRX cycle, that is, the whole DRX cycle is kept as the inactive time, so that the purpose of further saving power is achieved.
  • the UE only monitors the DCI format 2-6 in the inactive time of the DRX.
  • the DCI format 2-6 is a UE group common signaling for carrying a power saving instruction.
  • the DCI format 2-6 includes a plurality of indication blocks, and each indication block contains a 1-bit wakeup indication field a 0-5 bit(s) SCell dormancy indication field.
  • the plurality of indication blocks may belong to different UEs or UE groups.
  • the UE may determine the starting location of the corresponding indication block in the DCI format 2-6 by a high-layer parameter ps (power saving)-LocationDCI-2-6.
  • the UE is also configured with a high-layer parameter ps-RNTI (power saving-radio network temporary identity) for scrambling the cyclic redundancy check (CRC) of the DCI format 2-6.
  • the total number of bits (the size of load) contained in the DCI format 2-6 is also configured to the UE through a high-layer parameter size-DCI-2-6.
  • the UE does not monitor the DCI format 2-6 in the whole inactive time of the DRX, but the UE can monitor the DCI format 2-6 in a time window.
  • the starting location of the time window is determined by a high-layer parameter ps-Offset (power saving offset).
  • the parameter ps-Offset is used for indicating the relative offset before the slot where the starting location of a next DRX cycle (i.e. the location of starting the drx-onDurationTimer) is located, and the UE begins to monitor the DCI format 2-6 at the location determined according to the parameter ps-Offset.
  • the UE On each configured search space for monitoring the DCI format 2-6, the UE only monitors PDCCH transmission occasions on first Ts PDCCH slots, where the value of Ts is determined by the duration in the configuration parameters for the corresponding search space. If the duration is not provided, only the PDCCH transmission occasion on the first PDCCH slot is monitored. In other words, from the determined starting location of monitoring, the at least one cycle of PDCCH monitoring should be completed on the corresponding search space.
  • the UE stops monitoring the DCI format 2-6 at a location of a preset gap before the starting location of the next DRX cycle (i.e., the location of starting the drx-onDurationTimer), wherein the preset gap is determined by the parameter MinTimeGap reported by the UE for the downlink active bandwidth part (BWP).
  • the optional values of MinTimeGap reported by the UE are specified in Table 1. That is, the UE reports value1 or value2.
  • the UE does not expect to monitor a PDCCH carrying the DCI format 2-6, where the X is related to the subcarrier spacing.
  • extended reality (XR) services include, but not limited to, augmented services of various realities, such as augmented reality (AR), virtual reality (VR), mixed reality (MR) and cinematic reality (CR).
  • AR augmented reality
  • VR virtual reality
  • MR mixed reality
  • CR cinematic reality
  • the data packets of the XR services do not arrive on a strictly periodical basis, and the arrival time in each cycle fluctuates within a certain range. That is, the arrival time is uncertain. Since the existing DRX mechanisms are difficult to match the XR services, related enhancements are made to the DRX mechanisms in the embodiments of the present application.
  • An embodiment of the present application provides a method executed by a UE. As shown in FIG. 4, the method includes the following steps.
  • the embodiment of the present application is different from the existing method for starting the drx-onDurationTimer at the starting location of each DRX cycle.
  • there may be a plurality of candidate locations where the drx-onDurationTimer can be started in one DRX cycle that is, there may be a plurality of candidate time points of starting the drx-onDurationTimer in one DRX cycle.
  • candidate locations For example, with reference to FIG. 5, by taking the number of candidate locations being four as an example, four locations where the drx-onDurationTimer may be started are shown.
  • the drx-onDurationTimer is started or not started based on the related information.
  • the UE can adaptively adjust the locations where the drx-onDurationTimer is started in each DRX cycle. For example, in a DRX cycle, the UE may start the drx-onDurationTimer in a slot (i.e., the first slot) where the starting location of this cycle is located; while in another DRX cycle, the UE may start the drx-onDurationTimer in a certain slot (e.g., the second slot or the N1th slot, where N1 is a positive integer greater than 2) after the starting location of this cycle.
  • a slot i.e., the first slot
  • N1 is a positive integer greater than 2
  • the UE starts the drx-onDurationTimer at different locations of different DRX cycles to match the fluctuation of the arrival time of the XR service, that is, the UE can dynamically adjust the time point of starting the drx-onDurationTimer in each DRX cycle, thereby achieving the purpose of matching with the actual arrival time of the XR service, and minimizing the power consumption of the UE while ensuring the transmission delay.
  • the embodiment of the present application provides an optional implementation.
  • the plurality of candidate locations are located in a starting window of the drx-onDurationTimer, as shown in FIG. 6.
  • the starting window is a time window where the drx-onDurationTimer can be started, and is also called a time window.
  • the related information of the plurality of candidate locations may include: related information of a starting window of the drx-onDurationTimer where the plurality of candidate locations are located, and/or location related information of the plurality of candidate locations within the starting window.
  • the starting location of the starting window may be predefined or preconfigured.
  • the starting location of the starting window may be predefined to be the starting location of the DRX cycle, wherein the starting location of the DRX cycle may also be the first candidate location within the starting window where the drx-onDurationTimer can be started.
  • the starting location of the starting window may also be defined or configured in other ways.
  • the length of the starting window may be predefined or preconfigured.
  • the length of the starting window is configured by the base station through a high-layer signaling.
  • a high-layer parameter duration may be newly introduced to indicate the length of the starting window.
  • the high-layer parameter is not limited to this name and may be called other names.
  • the indication granularity of the length of the starting window may be, but not limited to, a time unit, e.g., a slot. In other embodiments, the length of the starting window may also be defined or configured in other ways.
  • all candidate locations where the drx-onDurationTimer is started within the DRX cycle may be determined by the starting window, and the starting window may be determined according to the starting location of the starting window and the length of the starting window. That is, all candidate locations where the drx-onDurationTimer may be started within the DRX cycle may be determined according to the starting location of the starting window and the length of the starting window.
  • the candidate locations where the drx-onDurationTimer can be started within the starting window may be determined by predefined rules and/or preconfigured parameters.
  • the locations of each time unit or some of time units within the starting window are candidate locations where the drx-onDurationTimer is started.
  • each time unit within the starting window is a candidate location, or some of time units within the starting window are candidate locations.
  • the candidate locations where the drx-onDurationTimer can be stared within the starting window are determined by predefined rules. For example, each slot in the time window is a candidate location where the drx-onDurationTimer is started, or one slot of every N 2 slots in the time window is a candidate location where the drx-onDurationTimer can be started, where the value of N2 is predefined, and N 2 is a positive integer not less than 2. That is, any two adjacent candidate locations among the plurality of candidate locations are equally spaced.
  • the first candidate location in the plurality of candidate locations is the starting location of the DRX cycle, and the gap (N2) between any two adjacent candidate locations is predefined. It should be understood that, in the embodiment of the present application, all candidate locations can be determined by acquiring the related information of the starting window.
  • the candidate locations where the drx-onDurationTimer can be started within the starting window are determined by preconfigured parameters. For example, by indicating by a bit map whether each slot in the time window is a candidate location where the drx-onDurationTimer can be started, some of time units within the starting window can be configured as candidate locations. That is, the plurality of candidate locations are configured by a bit map.
  • the length of the bit map corresponds to the length of the starting window and each bit in the bit map is used for indicating whether the corresponding time unit is a candidate location, but it is not limited thereto.
  • one slot in every N3 slots in the time window is a candidate location where the drx-onDurationTimer can be started, where the value of N3 is preconfigured, and N3 is a positive integer not less than 2. It is also possible to configure some of time units within the starting window as candidate locations. That is, any two adjacent candidate locations among the plurality of candidate locations are equally spaced.
  • the first candidate location in the plurality of candidate locations is the starting location of the DRX cycle and the gap (N3) between any two adjacent candidate locations is configured by the base station through a high-layer signaling, but it is not limited thereto.
  • the length of the starting window is not greater than that of the DRX cycle. That is, the length of the starting window where the drx-onDurationTimer can be started may at most reach the length of the DRX cycle. In other words, any location in the whole DRX cycle may be a candidate location where the drx-onDurationTimer is started. As an example, if it is defined or configured that each time unit within the starting window is a candidate location, the UE can start the drx-onDurationTimer at any location in the whole DRX cycle.
  • the ratio of the length of the starting window where the drx-onDurationTimer can be started to the length of the DRX cycle does not exceed a predefined or preconfigured ratio, and this ratio is not greater than 1.
  • any two adjacent candidate locations among the plurality of candidate locations are equally spaced, and all candidate locations where the drx-onDurationTimer can be started in a DRX cycle may be determined by the gap between two adjacent candidate locations (which can also be interpreted as the offset between two adjacent candidate locations).
  • the related information of the plurality of candidate locations may include: the gap between any two adjacent candidate locations among the plurality of candidate locations, and/or the number of candidate locations within the DRX cycle.
  • the first candidate location among the plurality of candidate locations may be predefined or preconfigured.
  • the first candidate location among the plurality of candidate locations is the starting location of the DRX cycle.
  • the second candidate location where the drx-onDurationTimer can be started may be determined according to the first candidate location and the gap (or offset) between two adjacent candidate locations, and other candidate locations are determined by that analogy.
  • the size of the gap (or offset) between any two adjacent candidate locations may be predefined or preconfigured.
  • the gap (or offset) between any two adjacent candidate locations is configured by the base station through a high-layer signaling.
  • a high-layer parameter offsetBetweenPoints offset between candidate points
  • this high-layer parameter is not limited to this name and may also be called other names.
  • the indication granularity of the gap (or offset) may be, but not limited to, a time unit, e.g., a slot.
  • the number of candidate locations where the drx-onDurationTimer can be started in one DRX cycle is predefined or preconfigured.
  • the number of candidate locations in one DRX cycle is configured by the base station through a high-layer signaling.
  • a high-layer parameter numPoints (number of candidate points) may be introduced to indicate the total number of candidate locations where the drx-onDurationTimer can be started in one DRX cycle. It is to be noted that, this high-layer parameter is not limited to this name and may also be called other names.
  • the embodiment of the present application provides still another optional implementation.
  • the plurality of candidate locations are determined based on the respective offset relative to the starting location of the DRX cycle.
  • the related information of the plurality of candidate locations includes: the gap between any two adjacent candidate locations among the plurality of candidate locations, and/or the number of candidate locations within the DRX cycle.
  • each offset of each candidate location relative to the starting location of the DRX cycle may be predefined or preconfigured.
  • each offset is configured by the base station through a high-layer signaling.
  • the indication granularity of each offset may be, but not limited to, a time unit, e.g., a slot.
  • the first offset relative to the starting location of the DRX cycle is 0, the starting location of the DRX cycle is the first candidate location in the plurality of candidate locations; if the second offset relative to the starting location of the DRX cycle is 2, the location of 2 slots after the starting location of the DRX cycle is the second candidate location in the plurality of candidate locations; and, other candidate locations are reasoned by that analogy.
  • the method may further include: monitoring a wakeup indication transmitted by the base station in a DRX inactive time.
  • the step S102 may specifically include: based on the wakeup indication and the related information, starting or not starting the Drx-onDurationTimer at the first candidate location after the wakeup indication is received.
  • the drx-onDurationTimer is started or not at the first candidate location after the predetermined gap indicated by the wakeup indication is received.
  • the predetermined gap is a gap reported by the UE, the granularity of the predetermined gap is a time unit, and the size of the predetermined gap is determined based on a subcarrier spacing of a downlink active BWP of the UE.
  • the number of times of starting the drx-onDurationTimer in one DRX cycle is predefined or preconfigured.
  • the UE will not always monitor the wakeup indication from the base station.
  • the UE stops monitoring the wakeup indication for starting the drx-onDurationTimer.
  • the drx-onDurationTimer is started at most once within the DRX cycle.
  • the UE starts the drx-onDurationTimer at most once. For example, the UE monitors the wakeup indication from the base station in the DRX inactive time, and the UE starts the drx-onDurationTimer at a certain candidate location in the plurality of candidate locations based on the wakeup indication from the base station. The location where the drx-onDurationTimer is started is determined by the location of the wakeup indication. For example, the drx-onDurationTimer is started at the first candidate location after the wakeup indication.
  • the UE will not monitor the wakeup indication even if the UE enters the DRX inactive time again; or, the UE does not start the drx-onDurationTimer at the plurality of candidate locations based on the wakeup indication from the base station, that is, the whole DRX cycle is the inactive time. For example, the UE has not monitored the wakeup indication in the monitoring window of the wakeup indication. For another example, the UE monitors the wakeup indication from the base station in the DRX inactive time, and the UE does not start the drx-onDurationTimer at the first candidate location after the wakeup indication. In this DRX cycle, the UE will not monitor the wakeup indication.
  • the method may further include: monitoring a wakeup indication transmitted by the base station in a DRX inactive time.
  • the step S102 may specifically include: based on the wakeup indication and the related information, not starting the drx-onDurationTimer at each of the remaining candidate locations within the DRX cycle after the wakeup indication is received.
  • the UE may start the drx-onDurationTimer for two or more times at most. For example, the UE monitors the wakeup indication from the base station in the DRX inactive time, and the UE starts the drx-onDurationTimer at a certain candidate location in the plurality of candidate locations based on the wakeup indication from the base station. For example, the drx-onDurationTimer is started at the first candidate location after the wakeup indication.
  • the UE may also always monitor the wakeup indication from the base station and start the drx-onDurationTimer at another candidate location based on the last received wakeup indication; or, the UE does not start the drx-onDurationTimer at the plurality of candidate locations based on the wakeup indication from the base station, that is, the whole DRX cycle is the inactive time. For example, the UE has not monitored the wakeup indication in the monitoring window of the wakeup indication.
  • the gap between two adjacent startings of the drx-onDurationTimer is not less than a first gap.
  • the size of the first gap is predefined or preconfigured. In other words, in one DRX cycle, if the drx-onDurationTimer is started, the UE will not start the drx-onDurationTimer in a period of time with a preset length. Thus, in this period of time, the UE does not need to monitor the wakeup indication from the base station even if the UE enters the DRX inactive time again.
  • the wakeup indication is carried by DCI and/or a physical signal sequence.
  • the wakeup indication used for indicating whether the UE starts the drx-onDurationTimer at a certain candidate location within the DRX cycle may be carried by DCI.
  • the 1-bit wakeup indication field contained in the existing DCI format 2-6 may be reused by a method similar to that used in the existing Rel-16 system to indicate whether the UE starts the drx-onDurationTimer at the starting location of the DRX cycle.
  • the method is simple and direct.
  • the method for determining the time window (also referred to as DCI format 2-6 monitoring window) for monitoring the DCI format 2-6 by the UE and the meaning of the 1-bit wakeup indication field are different those in the existing DCI format 2-6.
  • the DCI used in the embodiment of the present application is not limited to this format or name and may have other specific formats or names.
  • one DRX cycle may correspond to one time window used for monitoring the wakeup indication, that is, the wakeup indication may be monitored in the first time window corresponding to the DRX cycle; and/or, the plurality of candidate locations correspond to respective time windows used for monitoring the wakeup indication, respectively, that is, the wakeup indication may be monitored in second time windows respectively corresponding to the plurality of candidate locations.
  • the methods of determining the time window for monitoring DCI by the UE corresponding to the two situations may be different.
  • the starting location of the first time window is determined based on the first offset before the starting location of the DRX cycle.
  • the UE needs to monitor the DCI format 2-6 in the DRX inactive time.
  • the starting time of monitoring the DCI format 2-6 by the UE may be determined by the first offset.
  • the location of the first offset relative to the starting location of the DRX cycle or the first candidate location where the drx-onDurationTimer can be started (which may be a location the same as or different from the starting location of the DRX cycle) is the location where the DCI format 2-6 starts to be monitored.
  • the first offset is predefined or configured by the base station through a high-layer signaling.
  • the first offset may be configured by the method in the Rel-16 system by using the existing parameter ps-Offset, or may be configured by other methods.
  • the ending location of the first time window is determined based on the starting location of the first time window and the length of the first time window.
  • the wakeup indication being configured as a DCI format 2-6 as an example
  • the latest ending time of monitoring the DCI format 2-6 by the UE may be determined by the length of the first time window.
  • the length of the first time window is predefined or configured by the base station through a high-layer signaling.
  • a high-layer parameter durationMonitoringPS power saving monitoring duration
  • the location determined based on the durationMonitoringPS may be used as the last location where the monitoring of the DCI format 2-6 is ended. It is to be noted that this high-layer parameter is not limited this name and may also be called other names.
  • the ending location of the first time window is determined based on the second gap before the last candidate location within the DRX cycle.
  • the ending location of monitoring the first time window of the DCI format 2-6 by the UE of the new release may be determined by the last candidate location where the drx-onDurationTimer can be started within the DRX cycle.
  • the latest ending time for the UE to monitor the DCI format 2-6 should not exceed (i.e., should not be later than) the location of the second gap before the last candidate location where the drx-onDurationTimer can be started within the DRX cycle.
  • the second gap may be the minimum gap reported by the UE.
  • the second gap may be determined by the existing parameter MinTimeGap, but it is not limited thereto.
  • the granularity of the second gap may be, but not limited to, a time unit, e.g., a slot.
  • the UE does not expect to monitor a PDCCH carrying the DCI format 2-6 on X slots before the last candidate location where the drx-onDurationTimer can be started within the DRX cycle.
  • the value of X i.e., the size of the second gap
  • MinTimeGap reported by the UE and the subcarrier spacing of the current downlink active BWP of the UE.
  • the starting location of each of the second time windows is determined based on the second offset before the corresponding candidate location.
  • the UE of the new release is configured with a plurality of candidate locations where the drx-onDurationTimer can be started in a DRX cycle
  • the wakeup indication being configured as a DCI format 2-6 as an example
  • the UE determines the respective second time window for monitoring the DCI format 2-6.
  • the starting time of each second time window may be determined by the second offset relative to the corresponding candidate location where the drx-onDurationTimer can be started. That is, the location of the second offset relative to any candidate location is the location where the DCI format 2-6 corresponding to this candidate location starts to be monitored.
  • the second offset is predefined or configured by the base station through a high-layer signaling.
  • the starting location of each second time window is determined by the existing high-layer parameter ps-Offset, or may be determined by other methods.
  • the ending location of each of the second time windows is determined based on the starting location of the second time window and the length of the second time window.
  • the specific implementation may be similar to the above description of one second time window corresponding to one DRX cycle, and will not be repeated here.
  • the determination is performed based on a third gap before the corresponding candidate location.
  • the wakeup indication being configured as a DCI format 2-6 as an example
  • the latest ending time of monitoring the DCI format 2-6 should not exceed (i.e., should not be later than) the location of the third gap before the corresponding candidate location where the drx-onDurationTimer can be started, wherein the third gap may be the minimum gap reported by the UE.
  • the third gap may be determined by the existing parameter MinTimeGap, but it is not limited thereto.
  • the granularity of the third gap may be, but not limited to, a time unit, e.g., a slot.
  • the size of the third gap is determined based on the subcarrier spacing of the downlink active BWP of the UE.
  • the specific undetailed implementation of the third gap may be similar to the description of the second gap and will not be repeated here.
  • the relationship between the starting window where the drx-onDurationTimer may be started and the time window for monitoring the DCI format 2-6 may be shown in FIG. 7.
  • the UE for each search space for monitoring a specific DCI format (e.g., the DCI format 2-6), the UE only monitors PDCCH monitoring occasions on first Ts PDCCH slots, where Ts is determined based on the configuration parameter duration of this search space.
  • DCI format 2-6 the DCI format 2-6
  • the wakeup indication field of the specific DCI format is used for indicating to start or not start the drx-onDurationTimer at the first candidate location after the specific DCI format is received.
  • the UE monitors a PDCCH carrying the DCI format 2-6 in the time window determined by at least one of the above embodiments. If the UE has monitored the DCI format 2-6 and the bit value of the wakeup indication field in the DCI format 2-6 is "1", the UE starts the drx-onDurationTimer at the first candidate location after a predetermined gap, where the predetermined gap is determined by the existing parameter MinTimeGap. That is, the UE starts the drx-onDurationTimer at the first candidate location satisfying the gap of X slots after the DCI format 2-6 is received. As described above, the value of X is determined by the MinTimeGap reported by the UE and the subcarrier spacing of the current active BWP. Once the UE has entered the DRX active time, the UE does not need to monitor the DCI format 2-6, that is, the UE only monitors the DCI format 2-6 in the DRX inactive time.
  • the UE does not starts the drx-onDurationTimer at the first candidate location after a predetermined gap, where the predetermined gap is determined by the existing parameter MinTimeGap. If the time window for the DCI format 2-6 does not end, the UE may always monitor a PDCCH carrying the DCI format 2-6; or, the UE does not start the drx-onDurationTimer at all candidate locations belonging to the same DRX cycle, and the UE stops monitoring the DCI format 2-6.
  • the wakeup indication for indicating whether the UE starts the drx-onDurationTimer or not at a certain candidate location within the DRX cycle may be carried by a physical signal sequence.
  • the UE starts the drx-onDurationTimer at the corresponding candidate location; and, if the UE has not monitored the physical signal sequence, the UE does not start the drx-onDurationTimer at the corresponding candidate location.
  • the physical signal sequence carrying the wakeup indication is called a wakeup signal (WUS).
  • WUS wakeup signal
  • the UE may monitor the WUS in the first time window corresponding to one DRX cycle, or the UE may monitor the WUS in the second time window corresponding to each candidate location where the drx-onDurationTimer can be started.
  • the UE monitors the WUS in the first time window corresponding to one DRX cycle.
  • the method for determining a WUS monitoring window may adopt the above-described method for determining the monitoring window of a specific DCI format (e.g., the DCI format 2-6).
  • the starting location of the first time window is determined based on the first offset before the starting location of the DRX cycle or the first candidate location where the drx-onDurationTimer can be started
  • the ending location of the first time window is determined based on the starting location of the first time window and the length of the first time window or based on the second gap relative to the last candidate location in the DRX period. That is, the latest ending location of monitoring the WUS by the UE should not exceed (i.e., should not be later than) the location of the second gap before the last candidate location where the drx-onDurationTimer can be started.
  • the UE If the UE has monitored the WUS, the UE starts the drx-onDurationTimer at the first candidate location satisfying the predetermined gap after the WUS is monitored, and stops subsequent WUS monitoring.
  • Other undetailed contents may refer to the above description of carrying the wakeup indication by DCI, and will not be repeated here.
  • the UE monitors the WUS in the second time window corresponding to each candidate location where the drx-onDurationTimer can be started.
  • the method for determining the WUS monitoring window may also adopt the above-described method for determining the monitoring window of the DCI format 2-6.
  • the starting location of each second time window for the WUS is determined based on the second offset before the corresponding candidate location. That is, the UE starts to monitor the respective WUS at the location of the second offset before each candidate location where the drx-onDurationTimer can be started.
  • each second time window for the WUS is determined based on the starting location of the second time window and the length of the second time window, or the ending location of each second time window is determined based on a third gap before the corresponding candidate location. If the UE has monitored the WUS, the UE starts the drx-onDurationTimer at the corresponding candidate location; and, if the UE has not monitored the WUS, the UE does not need to start the drx-onDurationTimer at the corresponding candidate location. Other undetailed contents may refer to the above description of carrying the wakeup indication by DCI, and will not be repeated here.
  • the base station indicates through a signaling that the UE does not start the drx-onDurationTimer at each of the remaining candidate locations in one DRX cycle, and the UE stops monitoring the wakeup indication for indicating the UE to start the drx-onDurationTimer, thereby achieving the purpose of saving power.
  • the signaling may be carried by a DCI format 2-6 or a physical layer signal sequence.
  • the UE does not start the drx-onDurationTimer at each of the remaining candidate locations in this DRX cycle, and the UE stops monitoring the DCI format 2-6 and does not need to monitor the DCI format 2-6 in other monitoring windows of the DCI format 2-6 in this DRX cycle. In other words, within the remaining time of this DRX cycle, UE may be in a dormant state.
  • each offset as described above refers to the distance between the starting location of one time unit and the starting time of another time unit and each gap as described above refers to the distance between the ending location of one time unit and the starting location of another time unit.
  • the time unit is a radio subframe, slot or symbol.
  • the purpose of matching with the actual arrival time of the service is achieved by dynamically adjusting a time point of starting the drx-onDurationTimer in each DRX cycle.
  • the XR service has a fluctuation in the amount of data arrived in each cycle, that is, the data packet arrived in each cycle may be very different in size. Consequently, the required transmission bandwidth and the total transmission time may also be different. For example, it is possible to dynamically adjust the size of the drx-onDurationTimer, the active system BWP and/or the search space set group (SSSG), etc. in each DRX cycle.
  • the DCI carrying the wakeup indication is of a specific DCI format (e.g., DCI format 2-6), and the specific DCI format may be configured to include at least one of the following indication fields.
  • this indication may be a field for indicating an active BWP used firstly in a next long DRX cycle. For example, 2 bits are used to indicate an active BWP used firstly in the next long DRX cycle from among 4 preconfigured BWPs.
  • this indication may be a field for indicating an SSSG used firstly in a next long DRX cycle. For example, 2 bits are used to indicate an SSSG used firstly in the next long DRX cycle from among 3 preconfigured SSSGs.
  • this indication may be used for indicating the size of the drx-onDurationTimer used in a next long DRX cycle.
  • this indication may be used for jointly indicating whether to start the drx-onDurationTimer in a next long DRX cycle and at least one of the downlink active BWP used firstly, the SSSG monitored firstly and the size of the drx-onDurationTimer in the next long DRX cycle.
  • Table 2 One example shown in Table 2:
  • an active BWP or SSSG used firstly in one DRX cycle may be preset from the perspective of saving power.
  • the active BWP used firstly may be of a smaller bandwidth, and the SSSG used firstly may have sparse PDCCH monitoring.
  • the active BWP or SSSG may be dynamically adjusted through a signaling.
  • the downlink active BWP used firstly by the UE in each DRX cycle is predefined or preconfigured.
  • the downlink active BWP used firstly after the drx-onDurationTimer is started includes at least one of the following:
  • a downlink active BWP used firstly configured by a high-layer parameter firstActiveDLBWP first active downlink BWP
  • first active downlink BWP i.e., a downlink active BWP used firstly by the UE after the BWP is configured through a high-layer signaling
  • a downlink initial BWP configured by a high-layer parameter initialDLBWP (initial downlink BWP), i.e., a downlink initial BWP configured in a system information block;
  • a dedicated BWP preconfigured by the base station e.g., a BWP indicated by the newly introduced parameter firstActiveDLBWPforDRX (first active downlink BWP for the DRX).
  • the SSSG used firstly by the UE in each DRX cycle is predefined or preconfigured.
  • the SSSG monitored firstly includes at least one of the following:
  • a predefined SSSG e.g., an SSSG with an index number of 0;
  • a dedicated SSSG preconfigured by the base station e.g., an SSSG indicated by the newly introduced parameter firstSSSGforDRX (first SSSG for the DRX).
  • a UE can dynamically adjust time points of starting the drx-onDurationTimer in different DRX cycles based on the wakeup indication, thereby achieving the purpose of matching with the actual arrival time of an XR service, and minimizing the power consumption of the UE while ensuring the transmission delay.
  • An embodiment of the present application further provides a method executed by a base station in a communication system.
  • the method includes a step of: transmitting, to a UE, related information of a plurality of candidate locations within a DRX cycle, so that the UE starts a drx-onDurationTimer based on the related information.
  • the method provided in the embodiment of the present application corresponds to the method in the embodiments on the UE side, and the detailed functional descriptions and the achieved beneficial effects can specifically refer to the above description of the corresponding method in the embodiments on the UE side and will not be repeated here.
  • the user equipment may specifically include an acquisition module and a startup module, wherein,
  • the acquisition module is configured to acquire related information of a plurality of candidate locations within a DRX cycle, the candidate locations being drx-onDurationTimerused for starting a drx-onDurationTimer;
  • the startup module is configured to start or not start the drx-onDurationTimer based on the related information.
  • the related information of the plurality of candidate locations includes at least one of the following:
  • the starting location of the starting window is the starting location of the DRX cycle; and/or,
  • the length of the starting window is predefined or configured by a base station through a high-layer signaling.
  • each time unit within the starting window is a candidate location
  • the plurality of candidate locations are configured by a bit map, the length of the bit map corresponds to the length of the starting window, and each bit in the bit map is used for indicating whether the corresponding time unit is a candidate location or not; or,
  • any two adjacent candidate locations among the plurality of candidate locations are equally spaced, and the first candidate location among the plurality of candidate locations is the starting location of the DRX cycle.
  • the gap between any two adjacent candidate locations is configured by the base station through a high-layer signaling.
  • the length of the starting window is not greater than that of the DRX cycle.
  • the gap between any two adjacent candidate locations is configured by the base station through a high-layer signaling
  • the number of candidate locations within the DRX cycle is configured by the base station through a high-layer signaling
  • the first candidate location among the plurality of candidate locations is the starting location of the DRX cycle.
  • the number of times of starting the drx-onDurationTimer within the DRX cycle is predefined or preconfigured.
  • the drx-onDurationTimer is started at most once within the DRX cycle.
  • the gap between two adjacent startings of the drx-onDurationTimer is not less than a first gap.
  • the user equipment may further include a monitoring module configured to monitor a wakeup indication transmitted by the base station in a DRX inactive time; and
  • the startup module is specifically configured to: based on the wakeup indication and the related information, start or not start the drx-onDurationTimer at the first candidate location after the wakeup indication is received.
  • the monitoring module is further configured to monitor a wakeup indication transmitted by the base station in a DRX inactive time
  • the startup module is further specifically configured to: based on the wakeup indication and the related information, not start the drx-onDurationTimer at each of the remaining candidate locations within the DRX cycle after the wakeup indication is received.
  • the wakeup indication is carried by downlink control information (DCI) and/or a physical signal sequence.
  • DCI downlink control information
  • the monitoring module is further configured to: monitor the wakeup indication in a first time window corresponding to the DRX cycle; and/or,
  • the starting location of the first time window is determined based on a first offset before the starting location of the DRX cycle
  • the ending location of the first time window is determined based on the starting location of the first time window and the length of the first time window, or based on a second gap before the last candidate location within the DRX cycle.
  • the starting location of each of the second time windows is determined based on a second offset before the corresponding candidate location
  • the ending location of each of the second time windows is determined based on the starting location of the second time window and the length of the second time window, or the ending location of each of the second time windows is determined based on a third gap before the corresponding candidate location.
  • At least one of the first offset, the second offset and the length of the time window is predefined or configured by the base station through a high-layer signaling.
  • the second gap or the third gap includes at least one of the following situations:
  • the size of the gap is determined based on a subcarrier spacing of a downlink active BWP of the UE.
  • the DCI carrying the wakeup indication is of a specific DCI format
  • the wakeup indication field of the specific DCI format is used for indicating to start or not start the drx-onDurationTimer at the first candidate location after the specific DCI format is received.
  • the DCI carrying the wakeup indication is of a specific DCI format
  • the specific DCI format is configured to include at least one of the following indication fields:
  • the downlink active BWP used firstly after the drx-onDurationTimer is started includes at least one of the following:
  • a downlink active BWP used firstly configured by a high-layer parameter
  • the SSSG monitored firstly includes at least one of the following:
  • An embodiment of the present application further provides a base station.
  • the base station may include a transmission module configured to: transmit, to a UE, related information of a plurality of candidate locations within a DRX cycle, so that the UE starts a drx-onDurationTimer based on the related information.
  • the user equipment and base station of the embodiments of the present application may execute the methods provided by the embodiments of the present application, and the implementation principles thereof are similar.
  • the actions performed by the modules in the user equipment and base station in the embodiment of the present application correspond to the steps in the methods in the embodiments of the present application.
  • the detailed functional description of the modules in the user equipment and base station and the achieved beneficial effects can refer to the description of the corresponding methods described above and will not be repeated here.
  • an electronic device which includes: a transceiver configured to transmit and receive signals; and a processor coupled with the transceiver and configured to implement steps of the forgoing embodiments of various methods.
  • the electronic device may be a UE, and the processor in the electronic device is configured to control to implement the steps of the method executed by a UE provided in the above method embodiments.
  • the electronic device may be a base station, and the processor in the electronic device is configured to control to implement the steps of the method executed by a base station provided in the above method embodiments.
  • an electronic device as shown in FIG. 8.
  • the electronic device 800 as shown in FIG. 8 includes a processor 801 and a memory 803. Wherein, the processor 801 is connected with the memory 803, for example, through the bus 802.
  • the electronic device 800 may further include a transceiver 804, and the transceiver 804 may be used for data interaction between the electronic device and other electronic devices, such as data transmission and/or data reception and so on. It is to be noted that, in practical applications, the number of the transceiver 804 is not limited to 1, and the structure of the electronic device 800 does not constitute any limitations to the embodiments of the present application.
  • the processor 801 may be a central processing unit (CPU), 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 devices, transistor logic devices, hardware components or any combination thereof.
  • the processor can implement or execute various exemplary logic blocks, modules and circuits described in the disclosure of the present application.
  • the processor 801 may also be a combination of functions for implementing computing, for example, a combination of one or more microprocessors, a combination of DSPs and microprocessors, etc.
  • the bus 802 may include a passageway for transferring information between the above components.
  • the bus 802 may be a peripheral component interconnect (PCI) bus, an extended industry standard architecture (EISA) bus, etc.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus 802 may be classified into address bus, data bus, control bus, etc.
  • the bus is represented by only one bold line in FIG. 8, but it does not mean that there is only one bus or one type of buses.
  • the memory 803 may be a read only memory (ROM) or other types of static storage devices that may store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that may store information and instructions, it may also be electrically erasable and programmable read only memory (EEPROM), compact disc read only memory (CD-ROM) or other optical disk storage, optical disk storage (including compressed compact disc, laser disc, compact disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media, other magnetic storage devices, or any other medium capable of carrying or storing computer programs and capable of being read by a computer, without limitation therein.
  • ROM read only memory
  • RAM random access memory
  • EEPROM electrically erasable and programmable read only memory
  • CD-ROM compact disc read only memory
  • optical disk storage including compressed compact disc, laser disc, compact disc, digital versatile disc, blu-ray disc, etc.
  • magnetic disk storage media other magnetic storage devices, or any other medium capable of carrying or storing computer programs and capable of being read by a computer
  • the memory 803 is configured to store computer programs for executing the embodiments of the present application, and is controlled and executed by the processor 801.
  • the processor 801 is configured to execute the computer programs stored in the memory 803 to implement the steps in the above method embodiments.
  • An embodiment of the present application provides a computer-readable storage medium having computer programs stored thereon that, when executed by a processor, can implement the steps and corresponding contents in the above method embodiments.
  • An embodiment of the present application further provides a computer program product, comprising computer programs that, when executed by a processor, can implement the steps and corresponding contents in the above method embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un système de communication 5G ou 6G pour prendre en charge un débit supérieur de transmission de données. La présente invention concerne un procédé et un appareil d'optimisation de C-DRX. Le procédé comprend les étapes consistant à : acquérir des informations associées d'une pluralité d'emplacements candidats dans un cycle DRX, l'emplacement candidat étant utilisé pour démarrer un drx-onDurationTimer ; et démarrer ou ne pas démarrer un drx-onDurationTimer sur la base des informations associées. Étant donné qu'une pluralité d'emplacements candidats sont dans un cycle DRX, un équipement utilisateur (UE) peut ajuster dynamiquement des points temporels de démarrage du drx-onDurationTimer dans différents cycles DRX, ce qui permet d'atteindre l'objectif de mise en correspondance avec le temps d'arrivée réel d'un service XR, et de réduire au minimum la consommation d'énergie de l'UE tout en garantissant le retard de transmission.
PCT/KR2023/005735 2022-04-27 2023-04-27 Procédé et appareil d'optimisation de c-drx Ceased WO2023211171A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210458182.1A CN117015079A (zh) 2022-04-27 2022-04-27 通信方法和用户设备
CN202210458182.1 2022-04-27

Publications (1)

Publication Number Publication Date
WO2023211171A1 true WO2023211171A1 (fr) 2023-11-02

Family

ID=88519194

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2023/005735 Ceased WO2023211171A1 (fr) 2022-04-27 2023-04-27 Procédé et appareil d'optimisation de c-drx

Country Status (2)

Country Link
CN (1) CN117015079A (fr)
WO (1) WO2023211171A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025111887A1 (fr) * 2023-11-29 2025-06-05 Zte Corporation Procédé, dispositif et produit-programme informatique pour communication sans fil

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150305083A1 (en) * 2012-09-28 2015-10-22 Intel Corporation Discontinuous reception (drx) enhancements in lte systems
US20200120596A1 (en) * 2017-06-16 2020-04-16 Huawei Technologies Co., Ltd. Drx configuration method, terminal device, network device, and communications system
WO2020091422A1 (fr) * 2018-11-02 2020-05-07 엘지전자 주식회사 Procédé de surveillance de pdcch effectué par un terminal dans un système de communication sans fil, et terminal mettant en œuvre ce procédé
WO2021248450A1 (fr) * 2020-06-12 2021-12-16 Lenovo (Beijing) Limited Procédés et appareil pour opération de réception discontinue (drx) en liaison latérale

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150305083A1 (en) * 2012-09-28 2015-10-22 Intel Corporation Discontinuous reception (drx) enhancements in lte systems
US20200120596A1 (en) * 2017-06-16 2020-04-16 Huawei Technologies Co., Ltd. Drx configuration method, terminal device, network device, and communications system
WO2020091422A1 (fr) * 2018-11-02 2020-05-07 엘지전자 주식회사 Procédé de surveillance de pdcch effectué par un terminal dans un système de communication sans fil, et terminal mettant en œuvre ce procédé
WO2021248450A1 (fr) * 2020-06-12 2021-12-16 Lenovo (Beijing) Limited Procédés et appareil pour opération de réception discontinue (drx) en liaison latérale

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Medium Access Control (MAC) protocol specification (Release 17)", 3GPP TS 38.321, no. V17.0.0, 14 April 2022 (2022-04-14), pages 1 - 221, XP052145972 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025111887A1 (fr) * 2023-11-29 2025-06-05 Zte Corporation Procédé, dispositif et produit-programme informatique pour communication sans fil

Also Published As

Publication number Publication date
CN117015079A (zh) 2023-11-07

Similar Documents

Publication Publication Date Title
WO2023191367A1 (fr) Procédé de communication dans un système de communication et appareil associé
WO2023191560A1 (fr) Procédé de communication, équipement utilisateur, et station de base
WO2022211479A1 (fr) Procédé de communication, appareil, dispositif électronique et support d'enregistrement lisible par ordinateur
WO2022211533A1 (fr) Procédé et appareil pour émettre et recevoir des données de liaison montante et des informations de commande
WO2024071739A1 (fr) Procédé de communication et équipement électronique
WO2022255679A1 (fr) Procédé réalisé par un équipement utilisateur et équipement utilisateur
WO2023080593A1 (fr) Procédé de transmission/réception d'un ensemble de signaux et appareil associé
WO2023121356A1 (fr) Procédé de détermination de paramètres de cellule par terminal
WO2023211171A1 (fr) Procédé et appareil d'optimisation de c-drx
WO2022203282A1 (fr) Procédé de réception d'un canal de commande de liaison descendante physique et équipement correspondant
WO2025037896A1 (fr) Bloc ss/pbch à la demande
WO2023167570A1 (fr) Procédé et appareil de surveillance de canal de commande de liaison descendante dans un système de communication sans fil
WO2023191373A1 (fr) Procédé et appareil pour émettre et recevoir des données et des informations de commande dans un système de communication sans fil
WO2023008962A1 (fr) Procédé et appareil de communication en liaison latérale dans un système de communication sans fil
WO2022255849A1 (fr) Terminal, station de base et procédé exécuté par ceux-ci dans un système de communication sans fil
WO2023211150A1 (fr) Procédé et appareil permettant de transmettre une information dans un système de communication sans fil
WO2024071850A1 (fr) Procédé de communication, terminal, dispositif de nœud de réseau et support d'enregistrement
WO2024096561A1 (fr) Procédé de transmission et de réception de données et d'informations de commande [commutation inter-cellules]
WO2023146261A1 (fr) Procédé de détection d'un canal de commande de liaison descendante
WO2024210432A2 (fr) Procédé exécuté par un équipement d'utilisateur, procédé exécuté par une station de base, équipement d'utilisateur et station de base
WO2023158245A1 (fr) Procédé et dispositif pour recevoir un canal physique de contrôle descendant
WO2024237607A1 (fr) Équipement utilisateur et procédés exécutés par celui-ci
WO2023211209A1 (fr) Procédé réalisé par un équipement utilisateur, procédé réalisé par une station de base, et dispositifs correspondants associés
WO2025121867A1 (fr) Format de créneau avec signaux de faible puissance
WO2024232577A1 (fr) Procédé et dispositif de réception et de transmission d'informations

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: 23796814

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23796814

Country of ref document: EP

Kind code of ref document: A1