Method and device for decreasing power consumption of terminal having wake-up receiver in wireless communication system
By implementing PDCCH monitoring skipping and using a low power wake-up receiver, the method addresses the high power consumption of terminals in wireless communication systems, enhancing battery life and supporting low-latency applications.
Patent Information
- Application Number
- PCT/KR2024/006370
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-12
- Filing Date
- 2024-05-10
- Publication Date
- 2024-11-21
AI Technical Summary
The high power consumption of terminals in wireless communication systems, particularly in 5G and beyond, due to continuous monitoring of PDCCH channels, leads to increased energy expenditure and reduced battery life, especially in devices requiring low latency and extended operation.
Implementing a method where a terminal sets specific time intervals for PDCCH monitoring skipping through higher layer signaling and using a low power wake-up receiver to receive wake-up signals, allowing the main radio to transmit only when necessary, thereby reducing unnecessary power usage.
This approach significantly reduces power consumption by minimizing unnecessary PDCCH monitoring and extends battery life in devices, making it suitable for applications requiring low latency and extended operation.
Smart Images

Figure KR2024006370_21112024_PF_FP_ABST
Abstract
Description
Method and device for reducing power consumption of a terminal having a wake-up receiver in a wireless communication system
[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for reducing power consumption of a terminal having a wake-up receiver.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.
[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.
[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.
[0005] In addition, standardization of wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.
[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.
[0008] As described above and with the development of mobile communication systems, various services have become available, and methods for effectively providing these services are required.
[0009] Based on the discussion described above, the present disclosure can provide a method and device for reducing power consumption of a terminal having a wake-up receiver in a wireless communication system.
[0010] The technical problems to be achieved in the present disclosure are not limited to those mentioned above, and other technical problems not mentioned can be considered by a person having ordinary skill in the art from the various embodiments of the present disclosure described below.
[0011] A method performed by a terminal in a communication system according to one embodiment of the present disclosure comprises the steps of: receiving, through higher layer signaling, a configuration for a plurality of time intervals for skipping physical downlink control channel (PDCCH) monitoring and a configuration related to skipping PDCCH monitoring through a main radio (MR) of the terminal; receiving downlink control information (DCI) including information related to a time interval among the plurality of time intervals; skipping PDCCH monitoring through the MR in the time interval; and performing PDCCH monitoring through the MR in at least a part of the time interval after the WUS is received in the time interval when a WUS (wake up signal) is received through a low power wake up receiver (LR) of the terminal within the time interval.
[0012] According to one embodiment of the present disclosure, PDCCH monitoring through the MR is skipped for a plurality of PDCCH search space types, wherein the plurality of PDCCH search space types include a user equipment specific search space (USS) and a Type3-PDCCH CSS (common search space), and further include one or more of a Type0-PDCCH CSS, a Type0A-PDCCH CSS, a Type0B-PDCCH CSS, a Type1A-PDCCH CSS, a Type2-PDCCH CSS, or a Type2A-PDCCH CSS.
[0013] According to one embodiment of the present disclosure, PDCCH monitoring through the MR is performed for the plurality of PDCCH search space types after the WUS is received, or for a specific PDCCH search space type indicated by the WUS among the plurality of PDCCH search space types after the WUS is received.
[0014] According to one embodiment of the present disclosure, when a DRX (discontinuous reception) configuration is received through the upper layer signaling and a WUS is received through the LR, whether or not drx-onDurationTimer included in the DRX configuration is triggered is indicated by the WUS, and the WUS is different from the DCI format 2_6 for the MR.
[0015] According to one embodiment of the present disclosure, when WUS is set to be monitored through the LR, the DCI format 2_6 is not monitored through the MR or the DCI format 2_6 received through the MR is ignored.
[0016] According to one embodiment of the present disclosure, the terminal further comprises a step of transmitting a terminal capability report related to including the LR.
[0017] According to one embodiment of the present disclosure, a terminal of a communication system includes a transceiver; and a processor connected to the transceiver, wherein the processor is configured to: receive, through higher layer signaling, a configuration for a plurality of time intervals for skipping physical downlink control channel (PDCCH) monitoring and a configuration related to skipping PDCCH monitoring through a main radio (MR) of the terminal; receive downlink control information (DCI) including information related to a time interval among the plurality of time intervals; skip PDCCH monitoring through the MR in the time interval; and perform PDCCH monitoring through the MR in at least a part of the time interval after the WUS is received in the time interval when a WUS (wake up signal) is received through a low power wake up receiver (LR) of the terminal within the time interval.
[0018] According to one embodiment of the present disclosure, PDCCH monitoring through the MR is skipped for a plurality of PDCCH search space types, wherein the plurality of PDCCH search space types include a user equipment specific search space (USS) and a Type3-PDCCH CSS (common search space), and further include one or more of a Type0-PDCCH CSS, a Type0A-PDCCH CSS, a Type0B-PDCCH CSS, a Type1A-PDCCH CSS, a Type2-PDCCH CSS, or a Type2A-PDCCH CSS.
[0019] According to one embodiment of the present disclosure, PDCCH monitoring through the MR is performed for the plurality of PDCCH search space types after the WUS is received, or for a specific PDCCH search space type indicated by the WUS among the plurality of PDCCH search space types after the WUS is received.
[0020] According to one embodiment of the present disclosure, when a DRX (discontinuous reception) configuration is received through the upper layer signaling and a WUS is received through the LR, whether or not drx-onDurationTimer included in the DRX configuration is triggered is indicated by the WUS, and the WUS is different from the DCI format 2_6 for the MR.
[0021] According to one embodiment of the present disclosure, when WUS is set to be monitored through the LR, the DCI format 2_6 is not monitored through the MR or the DCI format 2_6 received through the MR is ignored.
[0022] In a communication system according to one embodiment of the present disclosure, a method performed by a base station includes the steps of transmitting, to a terminal through upper layer signaling, a configuration for a plurality of time intervals for skipping physical downlink control channel (PDCCH) monitoring and a configuration related to skipping of PDCCH monitoring through a main radio (MR) of the terminal; and transmitting, to the terminal, downlink control information (DCI) including information related to a time interval among the plurality of time intervals, wherein transmission of the PDCCH for the MR to the terminal in the time interval is skipped, and when a wake up signal (WUS) for a low power wake up receiver (LR) of the terminal is transmitted to the terminal within the time interval, transmission of the PDCCH for the MR to the terminal is performed in at least a part of the time interval after the WUS is transmitted in the time interval.
[0023] According to one embodiment of the present disclosure, when a DRX (discontinuous reception) configuration is received through the upper layer signaling and a WUS for the LR is transmitted, whether or not drx-onDurationTimer included in the DRX configuration is triggered is indicated by the WUS, and the WUS is different from the DCI format 2_6 for the MR.
[0024] According to one embodiment of the present disclosure, a base station of a communication system includes a transceiver; and a processor connected to the transceiver, wherein the processor is configured to: transmit, to the terminal through upper layer signaling, a configuration for a plurality of time intervals for skipping of physical downlink control channel (PDCCH) monitoring and a configuration related to skipping of PDCCH monitoring through a main radio (MR) of the terminal; and transmit, to the terminal, downlink control information (DCI) including information related to a time interval among the plurality of time intervals, wherein transmission of the PDCCH for the MR to the terminal in the time interval is skipped, and when a wake up signal (WUS) for a low power wake up receiver (LR) of the terminal is transmitted to the terminal within the time interval, transmission of the PDCCH for the MR to the terminal is performed in at least a part of the time interval after the WUS is transmitted in the time interval.
[0025] According to one embodiment of the present disclosure, when a DRX (discontinuous reception) configuration is received through the upper layer signaling and a WUS for the LR is transmitted, whether or not drx-onDurationTimer included in the DRX configuration is triggered is indicated by the WUS, and the WUS is different from the DCI format 2_6 for the MR.
[0026] The above-described embodiment of the present disclosure is only a part of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description to be described below.
[0027] According to one embodiment of the present disclosure, by defining a signal transmission method of a base station in a wireless communication system, low power consumption can be provided to a terminal.
[0028] According to one embodiment of the present disclosure, excessive power consumption of a terminal can be eliminated.
[0029] The effects that can be obtained from one embodiment of the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly derived and understood by a person having ordinary skill in the art based on the detailed description below.
[0030] FIG. 1 is a diagram illustrating an example of a basic structure of a time-frequency resource domain of a 5G system according to one embodiment of the present disclosure.
[0031] FIG. 2 is a diagram showing an example of a time domain mapping structure and beam sweeping operation of a synchronization signal according to one embodiment of the present disclosure.
[0032] FIG. 3 is a diagram illustrating an example of a random access procedure according to one embodiment of the present disclosure.
[0033] FIG. 4 is a diagram illustrating an example of a procedure in which a terminal reports terminal capability information to a base station according to one embodiment of the present disclosure.
[0034] FIG. 5 is a diagram illustrating an example of DRX operation according to one embodiment of the present disclosure.
[0035] FIG. 6 is a diagram illustrating an example of a base station instructing a terminal with a WUR to switch to a main radio state through a WUS according to an embodiment of the present disclosure.
[0036] FIG. 7 is a diagram showing an example of an operation in which an RRC_CONNECTED terminal with WUR according to one embodiment of the present disclosure dynamically activates DRX when a WUS arrives regardless of the concept of a DRX cycle.
[0037] FIG. 8 is a diagram illustrating DCI format 2_6, which indicates whether an existing terminal should wake up for PDCCH monitoring in the next DRX cycle.
[0038] FIG. 9 is a diagram illustrating an example of an operation for a terminal procedure in which an RRC_CONNECTED terminal with WUR receives a WUS and is informed whether or not it should wake up in the configured DRX according to one embodiment of the present disclosure.
[0039] Figure 10 is a diagram of the PDCCH skipping operation of an existing terminal.
[0040] FIG. 11 is a diagram illustrating an example of a PDCCH skipping operation of an RRC_CONNECTED terminal with WUR according to one embodiment of the present disclosure.
[0041] FIG. 12 is a diagram showing an example of the operation of a terminal and a base station according to one embodiment of the present disclosure.
[0042] FIG. 13 is a diagram showing an example of a terminal transmitting and receiving device in a wireless communication system according to one embodiment of the present disclosure.
[0043] FIG. 14 is a block diagram showing an example of a configuration of a terminal according to one embodiment of the present disclosure.
[0044] FIG. 15 is a block diagram showing an example of a configuration of a base station according to one embodiment of the present disclosure.
[0045] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Furthermore, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on their functions in the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the overall content of this specification.
[0046] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the present disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals refer to like elements throughout the specification.
[0047] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).
[0048] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.
[0049] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.
[0050] In the following description of the present disclosure, detailed descriptions of related known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Hereinafter, embodiments of the present disclosure will be described with reference to the attached drawings.
[0051] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.
[0052] In the following description, the terms "physical channel" and "signal" may be used interchangeably with data or control signals. For example, while PDSCH (physical downlink shared channel) refers to a physical channel through which data is transmitted, PDSCH can also be used to refer to data. That is, in the present disclosure, the expression "transmitting a physical channel" can be interpreted equivalently to the expression "transmitting data or a signal through a physical channel."
[0053] Hereinafter, in the present disclosure, upper signaling refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of the physical layer, or a terminal transmits a signal to a base station using an uplink data channel of the physical layer. Upper signaling can be understood as radio resource control (RRC) signaling or a media access control (MAC) control element (CE).
[0054] For convenience of explanation, this disclosure uses terms and names defined in the 3GPP NR (New Radio: 5th generation mobile communications standard) standards. However, this disclosure is not limited to these terms and names and can be equally applied to systems conforming to other standards. Furthermore, the term "terminal" can refer to not only mobile phones, smartphones, IoT devices, and sensors, but also other wireless communication devices.
[0055] Hereinafter, a base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, a gNB, an eNode B, an eNB, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Of course, the present invention is not limited to the above examples.
[0056] To handle the explosive growth in mobile data traffic, 5G (5G), the next-generation communication system after LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)) and LTE-A (LTE-Advanced or E-UTRA Evolution), is being developed. thThe initial standards for the 5G (New Radio Access Technology Generation) system or New Radio access technology (NR) have been completed. While existing mobile communication systems have focused on conventional voice / data communications, the 5G system aims to satisfy various services and requirements, such as enhanced Mobile Broadband (eMBB) services to improve existing voice / data communications, Ultra-Reliable and Low Latency Communication (URLLC) services to support high-reliability / ultra-low latency communications, and massive Machine Type Communication (MTC) services to support massive machine-to-machine communications.
[0057] While the transmission bandwidth of existing LTE and LTE-A systems per single carrier is limited to a maximum of 20MHz, the 5G system aims to provide ultra-high-speed data services of up to several Gbps by utilizing a much wider ultra-wide bandwidth. Accordingly, the 5G system is considering ultra-high frequency bands from several GHz up to 100 GHz as candidate frequencies, where securing ultra-wide bandwidth frequencies is relatively easy. Additionally, it is possible to secure wide bandwidth frequencies for the 5G system through frequency reallocation or allocation among frequency bands included in the hundreds of MHz to several GHz used in existing mobile communication systems.
[0058] Radio waves in the ultra-high frequency band are sometimes called millimeter waves (mmWave) because their wavelengths are on the order of millimeters. However, in the ultra-high frequency band, the path loss of radio waves increases in proportion to the frequency band, reducing the coverage of mobile communication systems.
[0059] In order to overcome the disadvantage of reduced coverage in the above ultra-high frequency band, beamforming technology is applied, which uses multiple antennas to concentrate the radiated energy of radio waves to a predetermined target point and increase the transmission distance of radio waves. That is, a signal to which the beamforming technology is applied has a relatively narrow beam width of the signal, and the radiated energy is concentrated within the narrowed beam width, thereby increasing the transmission distance. The beamforming technology can be applied to both the transmitter and the receiver. In addition to the effect of increasing coverage, the beamforming technology has the effect of reducing interference in areas other than the beamforming direction. In order for the beamforming technology to operate properly, accurate measurement and feedback methods of the transmission / reception beams are required. The beamforming technology can be applied to a control channel or data channel that corresponds one-to-one between a predetermined terminal and a base station. Additionally, beamforming technology can be applied to common signals transmitted by a base station to multiple terminals within a system, such as synchronization signals, physical broadcast channels (PBCH), control channels for transmitting system information, and data channels, to increase coverage. When beamforming technology is applied to common signals, beam sweeping technology, which transmits signals by changing the beam direction, is additionally applied so that the common signal can reach terminals located at any location within the cell.
[0060] Another requirement for 5G systems is ultra-low latency services, with transmission delays of approximately 1 ms between transmitters and receivers. One way to reduce transmission delay is to design a frame structure based on a short TTI (Transmission Time Interval), which is shorter than that of LTE and LTE-A. A TTI is the basic time unit used for scheduling, and the TTI of existing LTE and LTE-A systems is 1 ms, which corresponds to the length of one subframe. For example, to meet the requirements for ultra-low latency services in the 5G system, possible short TTIs are 0.5 ms, 0.25 ms, and 0.125 ms, which are shorter than those of existing LTE and LTE-A systems.
[0061] According to one embodiment of the present disclosure, a method for transmitting a signal by a terminal having a wake-up receiver in a mobile communication system is defined, thereby resolving the problem of excessive terminal power consumption and achieving high energy efficiency.
[0062] FIG. 1 is a diagram illustrating an example of the basic structure of a time-frequency resource domain of a 5G system according to one embodiment of the present disclosure. That is, FIG. 1 is a diagram illustrating the basic structure of a time-frequency resource domain, which is a radio resource domain through which data or control channels of a 5G system are transmitted.
[0063] Referring to Figure 1, the horizontal axis in Figure 1 represents the time domain and the vertical axis represents the frequency domain. The minimum transmission unit in the time domain of the 5G system is an OFDM (Orthogonal Frequency Division Multiplexing) symbol. (102) symbols are grouped together to form one slot (106), A plurality of slots can be combined to form a subframe (105). The length of the subframe is 1.0 ms, and 10 subframes can be combined to form a 10 ms frame (114). The minimum transmission unit in the frequency domain is a subcarrier, and the bandwidth of the entire system transmission bandwidth is a total of N BW It can be composed of (104) subcarriers.
[0064] The basic unit of resources in the time-frequency domain is a Resource Element (RE) (112), which can be represented by an OFDM symbol index and a subcarrier index. A Resource Block (RB or Physical Resource Block, PRB) is a resource block in the frequency domain. It can be defined as (110) consecutive subcarriers. In 5G systems, , and the data rate can increase in proportion to the number of RBs scheduled to the terminal.
[0065] In a 5G system, a base station can map data in RB units and perform scheduling on RBs, which typically constitute a slot for a given terminal. That is, in a 5G system, the basic time unit for scheduling may be a slot, and the basic frequency unit for scheduling may be an RB.
[0066] Number of OFDM symbols It is determined by the length of the cyclic prefix (CP) added to each symbol to prevent interference between symbols. For example, if the normal CP is applied, , when Extended CP is applied It can be. Extended CP is applied to a system with a relatively long transmission distance than the general CP, and it can maintain orthogonality between symbols. In the case of the general CP, since the ratio of the CP length to the symbol length is maintained at a constant value, the overhead due to the CP can be maintained constant regardless of the subcarrier spacing. That is, if the subcarrier spacing is small, the symbol length becomes longer, and thus the CP length can also become longer. Conversely, if the subcarrier spacing is large, the symbol length becomes shorter, and thus the CP length can be reduced. The symbol length and CP length can be inversely proportional to the subcarrier spacing.
[0067] In 5G systems, various frame structures can be supported by adjusting the subcarrier spacing to meet diverse services and requirements. For example,
[0068] - From the perspective of the operating frequency band, the larger the subcarrier spacing, the more advantageous it is for recovering phase noise in the high-frequency band.
[0069] - From a transmission time perspective, if the subcarrier spacing is large, the symbol length in the time domain becomes shorter, and consequently, the slot length becomes shorter, which is advantageous for supporting ultra-low delay services such as URLLC.
[0070] - From a cell size perspective, a longer CP length allows for larger cells to be supported, so a smaller subcarrier spacing allows for relatively larger cells to be supported. In mobile communications, a cell is a concept that refers to the area covered by a single base station.
[0071] The above subcarrier spacing, CP length, etc. are essential information for OFDM transmission and reception. For smooth transmission and reception, the base station and terminal must recognize the subcarrier spacing, CP length, etc. as common values. [Table 1] shows the relationship between the subcarrier spacing configuration (μ), subcarrier spacing (Δf), and CP length supported by the 5G system.
[0072] [Table 1]
[0073]
[0074] [Table 2] shows the number of symbols per slot for each subcarrier spacing setting (μ) in the case of the general CP. ), number of slots per frame ( ), number of slots per subframe ( ) is indicated.
[0075] [Table 2]
[0076]
[0077] [Table 3] shows the number of symbols per slot (μ) for each subcarrier spacing setting for the extended CP. ), number of slots per frame ( ), number of slots per subframe ( ) is indicated.
[0078] [Table 3]
[0079]
[0080] In the early stages of 5G system deployment, coexistence or dual-mode operation with existing LTE and / or LTE-A (hereinafter referred to as LTE / LTE-A) systems is expected. This allows existing LTE / LTE-A systems to provide stable system operation to terminals, while the 5G system can provide enhanced services to terminals. Therefore, the 5G system's frame structure must at least include the LTE / LTE-A frame structure or essential parameter set (subcarrier spacing = 15 kHz).
[0081] For example, comparing a frame structure with a subcarrier spacing setting μ=0 (hereinafter referred to as frame structure A) and a frame structure with a subcarrier spacing setting μ=1 (hereinafter referred to as frame structure B), compared to frame structure A, frame structure B shows that the subcarrier spacing and RB size are twice as large, and the slot length and symbol length are twice as small. In the case of frame structure B, two slots can constitute one subframe, and 20 subframes can constitute one frame.
[0082] Generalizing the frame structure of the 5G system allows for high scalability by ensuring that essential parameters—subcarrier spacing, CP length, and slot length—have integer multiple relationships for each frame structure. Furthermore, a fixed-length subframe of 1 ms can be defined to represent a reference time unit independent of the frame structure.
[0083] The frame structure can be applied to correspond to various scenarios. From the perspective of cell size, since a longer CP length can support a larger cell, frame structure A can support a relatively larger cell than frame structure B. From the perspective of operating frequency band, a larger subcarrier spacing is advantageous for phase noise recovery in a high-frequency band, so frame structure B can support a relatively higher operating frequency than frame structure A. From the perspective of service, since a shorter slot length, which is the basic time unit of scheduling, is advantageous for supporting ultra-low-latency services such as URLLC, frame structure B can be relatively more suitable for URLLC services than frame structure A.
[0084] In the following description of the present disclosure, uplink (UL) may refer to a wireless link through which a terminal transmits data or a control signal to a base station, and downlink (DL) may refer to a wireless link through which a base station transmits data or a control signal to a terminal.
[0085] In the initial access phase when a terminal first accesses the system, the terminal can synchronize downlink time and frequency from a synchronization signal transmitted by a base station through cell search, and obtain a cell identifier (cell ID). Then, the terminal can receive a Physical Broadcast Channel (PBCH) using the obtained cell ID, and obtain a Master Information Block (MIB), which is essential system information, from the PBCH. Additionally, the terminal can obtain cell-common transmission and reception-related control information by receiving system information (System Information Block, SIB) transmitted by the base station. The cell-common transmission and reception-related control information may include random access-related control information, paging-related control information, and common control information for various physical channels.
[0086] A synchronization signal is a signal that serves as a reference for cell search, and subcarrier spacing can be applied to suit channel environments such as phase noise for each frequency band. In the case of a data channel or control channel, as described above, different subcarrier spacings can be applied depending on the service type in order to support various services.
[0087] FIG. 2 is a diagram showing an example of a time domain mapping structure and beam sweeping operation of a synchronization signal according to one embodiment of the present disclosure.
[0088] For the purpose of explanation, the following components can be defined:
[0089] - PSS (Primary Synchronization Signal): This signal serves as the basis for DL time / frequency synchronization and provides some cell ID information.
[0090] - SSS (Secondary Synchronization Signal): Serves as a reference for DL time / frequency synchronization and provides some remaining information, including the cell ID. Additionally, it can serve as a reference signal for PBCH demodulation.
[0091] - PBCH (Physical Broadcast Channel): Provides MIB (Master Information Block), essential system information required for transmission and reception of data and control channels of the terminal. Essential system information may include search space-related control information indicating radio resource mapping information of the control channel, scheduling control information for a separate data channel that transmits system information, and SFN (System Frame Number), which is a frame-unit index that serves as a timing reference.
[0092] - SS / PBCH Block (Synchronization Signal / PBCH Block or SSB): An SS / PBCH block consists of N OFDM symbols and is a combination of PSS, SSS, PBCH, etc. In a system where beam sweeping technology is applied, the SS / PBCH block is the minimum unit to which beam sweeping is applied. In a 5G system, N can be 4. The base station can transmit up to L SS / PBCH blocks, and the L SS / PBCH blocks are mapped within a half frame (0.5 ms). The L SS / PBCH blocks are periodically repeated in units of a predetermined period P. The period P can be notified to the terminal through signaling by the base station. If there is no separate signaling for the period P, the terminal applies a pre-agreed default value.
[0093] Referring to FIG. 2, FIG. 2 illustrates an example in which beam sweeping is applied to SS / PBCH block units over time. In the example of FIG. 2, terminal 1 (205) receives an SS / PBCH block using a beam radiated in the direction of #d0 (203) by beamforming applied to SS / PBCH block #0 at time t1 (201). Terminal 2 (206) receives an SS / PBCH block using a beam radiated in the direction of #d4 (204) by beamforming applied to SS / PBCH block #4 at time t2 (202). The terminal can obtain an optimal synchronization signal through a beam radiated from the base station in the direction where the terminal is located. For example, terminal 1 (205) may have difficulty in obtaining time / frequency synchronization and essential system information from an SS / PBCH block through a beam radiated in the direction of #d4, which is far from the location of terminal 1.
[0094] In addition to the initial connection procedure, the UE may also receive SS / PBCH blocks to determine whether the radio link quality of the current cell is maintained at a certain level. Furthermore, during a handover procedure, in which the UE moves from the current cell to a neighboring cell, the UE may receive SS / PBCH blocks from the neighboring cell to determine the radio link quality of the neighboring cell and obtain time / frequency synchronization with the neighboring cell.
[0095] After the terminal acquires MIB and system information from the base station through the initial access procedure, the terminal can perform a random access procedure to transition the link with the base station to a connected state (or RRC_CONNECTED state). Upon completion of the random access procedure, the terminal transitions to a connected state, enabling one-to-one communication between the base station and the terminal. The random access procedure will be described in detail below with reference to FIG. 3.
[0096] FIG. 3 is a diagram illustrating an example of a random access procedure according to one embodiment of the present disclosure.
[0097] Referring to FIG. 3, as a first step (310) of the random access procedure, a terminal may transmit a random access preamble to a base station. The random access preamble, which is the first transmission message of the terminal in the random access procedure, may be referred to as message 1. The base station may measure a transmission delay value between the terminal and the base station from the random access preamble and synchronize uplink. At this time, the terminal may arbitrarily select which random access preamble to use within a random access preamble set given in advance by system information. In addition, the initial transmission power of the random access preamble may be determined according to the path loss between the terminal and the base station measured by the terminal. In addition, the terminal may determine the transmission beam direction of the random access preamble from the synchronization signal received from the base station and transmit the random access preamble.
[0098] In the second step (320), the base station transmits an uplink transmission timing adjustment command to the terminal based on the transmission delay value measured from the random access preamble received in the first step (310). In addition, the base station may transmit uplink resources and power control commands to be used by the terminal as scheduling information. The scheduling information may include control information regarding the terminal's uplink transmission beam.
[0099] If the terminal does not receive the Random Access Response (RAR) (or message 2), which is scheduling information for message 3, from the base station within a predetermined time in the second step (320), the first step (310) can be performed again. If the first step (310) is performed again, the terminal can increase the probability of the base station receiving the random access preamble by transmitting the random access preamble with the transmission power increased by a predetermined step (power ramping).
[0100] In the third step (330), the terminal transmits uplink data (message 3) including its terminal ID to the base station through an uplink data channel (Physical Uplink Shared Channel, PUSCH) using the uplink resources allocated in the second step (320). The transmission timing of the uplink data channel for transmitting Message 3 may follow the timing control command received from the base station in the second step (320). In addition, the transmission power of the uplink data channel for transmitting Message 3 may be determined in consideration of the power control command received from the base station in the second step (320) and the power ramping value of the random access preamble. The uplink data channel for transmitting Message 3 may mean the first uplink data signal that the terminal transmits to the base station after transmitting the random access preamble.
[0101] In the fourth step (340), if the base station determines that the terminal has performed random access without collision with other terminals, the base station can transmit data (message 4) including the ID of the terminal that transmitted uplink data in the third step (330) to the terminal. If the terminal receives the signal transmitted by the base station in the fourth step (340) from the base station, the terminal can determine that the random access has been successful. In addition, the terminal can transmit HARQ-ACK information indicating whether message 4 has been successfully received to the base station through an uplink control channel (Physical Uplink Control Channel, PUCCH).
[0102] If the data transmitted by the terminal in step 3 (330) collides with data from another terminal, causing the base station to fail to receive a data signal from the terminal, the base station may not transmit any more data to the terminal. Accordingly, if the terminal fails to receive the data transmitted from the base station in step 4 (340) within a certain period of time, it may determine that the random access procedure has failed and may restart from step 1 (310).
[0103] Upon successful completion of the random access procedure, the terminal transitions to the connected state, enabling one-to-one communication between the base station and the terminal. The base station receives UE capability information from the connected terminal and can adjust scheduling by referencing the UE capability information of the terminal. Through the UE capability information, the terminal can inform the base station whether it supports a certain function, the maximum allowable value of the function supported by the terminal, etc. Accordingly, the UE capability information reported by each terminal to the base station may have different values for each terminal.
[0104] For example, the terminal may report UE capability information including at least a portion of the following control information as the UE capability information to the base station.
[0105] - Control information related to frequency bands supported by the terminal
[0106] - Control information related to channel bandwidth supported by the terminal
[0107] - Control information related to the maximum modulation method supported by the terminal
[0108] - Control information related to the maximum number of beams supported by the terminal
[0109] - Control information related to the maximum number of layers supported by the terminal
[0110] - Control information related to CSI reporting supported by the terminal
[0111] - Control information on whether the terminal supports frequency hopping
[0112] - Bandwidth-related control information when supporting carrier aggregation (CA)
[0113] - Control information on whether cross carrier scheduling is supported when carrier aggregation is supported.
[0114] FIG. 4 is a diagram illustrating an example of a procedure in which a terminal reports terminal capability information to a base station according to one embodiment of the present disclosure.
[0115] Referring to FIG. 4, at step 410, the base station (402) can transmit a UE capability information request message to the terminal (401). In response to the base station's request for UE capability information, the terminal transmits UE capability information to the base station at step 420.
[0116] Through the aforementioned process, a terminal connected to a base station is in the RRC_CONNECTED state and can perform one-to-one communication. Conversely, a terminal that is not connected is in the RRC_IDLE state. The operation of a terminal in the RRC_IDLE state can be distinguished as follows. Of course, the following examples are not limited.
[0117] - Operates terminal-specific DRX (Discontinuous Reception) cycle set by upper layer
[0118] - Action to receive paging messages from the core network
[0119] - Obtain system information
[0120] - Measurement operations related to surrounding cells and cell reselection
[0121] In 5G systems, a new terminal state called RRC_INACTIVE has been defined to reduce the energy and time consumed during initial access. In addition to the actions performed by RRC_IDLE terminals, RRC_INACTIVE terminals can perform the following actions. Of course, these actions are not limited to the examples below.
[0122] - Storage of AS (Access stratum) information required for cell access
[0123] - Terminal-specific DRX cycle operation set by the RRC layer
[0124] - Setting up and periodically updating an RNA (RAN-based notification area) that can be used during handover by the RRC layer.
[0125] - Monitoring RAN-based paging messages transmitted via I-RNTI
[0126] Below, a scheduling method for a base station to transmit downlink data to a terminal or instruct the terminal to transmit uplink data is described.
[0127] Downlink Control Information (DCI) is control information transmitted from a base station to a terminal via the downlink. It may include downlink data scheduling information or uplink data scheduling information for a given terminal. Typically, the base station independently channel-codes DCI for each terminal and then transmits it to each terminal via the Physical Downlink Control Channel (PDCCH).
[0128] The base station can operate by applying a predetermined DCI format according to the purpose, such as whether it is scheduling information for downlink data (downlink assignment), scheduling information for uplink data (uplink grant), or DCI for power control, for the terminal to be scheduled.
[0129] The base station can transmit downlink data to the terminal via the Physical Downlink Shared Channel (PDSCH), a physical channel for downlink data transmission. Scheduling information, such as the specific mapping location in the time and frequency domains of the PDSCH, modulation scheme, HARQ-related control information, and power control information, can be provided by the base station to the terminal via DCI related to downlink data scheduling information among the DCIs transmitted via the PDCCH.
[0130] A terminal can transmit uplink data to a base station via the Physical Uplink Shared Channel (PUSCH), a physical channel for uplink data transmission. Scheduling information, such as specific mapping locations in the time and frequency domains of the PUSCH, modulation schemes, HARQ-related control information, and power control information, can be provided to the terminal by the base station via DCI related to uplink data scheduling information, among the DCIs transmitted via the PDCCH.
[0131] The time-frequency resources to which the PDCCH is mapped are called a Control Resource Set (CORESET). A CORESET can be configured for all or part of the frequency resources of the bandwidth supported by the UE in the frequency domain. In the time domain, it can be configured with one or more OFDM symbols, which can be defined as the CORESET length (Control Resource Set Duration). The base station can configure one or more CORESETs to the UE through higher layer signaling (e.g., System Information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Configuring a CORESET to the UE may mean providing information such as a CORESET identifier (Identity), the frequency location of the CORESET, and the symbol length of the CORESET. The information that the base station provides to the UE to configure the CORESET may include at least some of the information included in .
[0132] [Table 4]
[0133]
[0134]
[0135] CORESET is in the frequency domain It can be composed of RBs and in the time domain It can be composed of symbols. The NR PDCCH can be composed of one or more CCEs (Control Channel Elements). One CCE can be composed of six REGs (Resource Element Groups), and a REG can be defined as one RB during one OFDM symbol. Within one CORESET, REGs can be indexed in time-first order, starting with REG index 0 from the first OFDM symbol of the CORESET, the lowest RB.
[0136] Interleaved and non-interleaved transmission methods for PDCCH can be supported. The base station can configure whether to use interleaved or non-interleaved transmission for each CORESET to the terminal through upper layer signaling. Interleaving can be performed in units of REG bundles. A REG bundle can be defined as a set of one or more REGs. The terminal can determine the CCE-to-REG mapping method in the corresponding CORESET based on whether to use interleaved or non-interleaved transmission as configured by the base station, as shown in below.
[0137] [Table 5]
[0138]
[0139] The base station can inform the terminal of configuration information such as which symbol within the slot the PDCCH is mapped to and the transmission cycle through signaling.
[0140] The search space of the PDCCH is described as follows. The number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8, or 16 depending on the aggregation level (AL), and different numbers of CCEs can be used for link adaptation of the downlink control channel. For example, when AL=L, a single downlink control channel can be transmitted through L CCEs. The UE performs blind decoding, which detects a signal without knowing information about the downlink control channel, and for this purpose, a search space representing a set of CCEs can be defined. The search space is a set of downlink control channel candidates consisting of CCEs that the UE should attempt to decode at a given aggregation level. Since there are various aggregation levels that create a single group with 1, 2, 4, 8, or 16 CCEs, the UE can have multiple search spaces. A search space set can be defined as the set of search spaces at all established aggregation levels.
[0141] Search spaces can be classified into a common search space (CSS) and a UE-specific search space (USS). A certain group of UEs or all UEs can scan the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling for the System Information Block (SIB) or paging messages. For example, a UE can receive scheduling allocation information for the PDSCH for system information reception by scanning the common search space of the PDCCH. In the case of the common search space, since a certain group of UEs or all UEs must receive the PDCCH, it can be defined as a set of pre-arranged CCEs. UEs can receive scheduling allocation information for the PDSCH or PUSCH by scanning the UE-specific search space of the PDCCH. The UE-specific search space can be defined UE-specifically as a function of the UE's ID and various system parameters.
[0142] The base station can set the search space configuration information of the PDCCH to the terminal through higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can set the number of PDCCH candidates in each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol in the slot for the search space, the search space type (common search space or terminal-specific search space), the combination of the DCI format and RNTI to be monitored in the corresponding search space, the CORESET index to be monitored for the search space, etc. to the terminal. For example, the parameters for the search space for the PDCCH may include information such as the following .
[0143] [Table 6]
[0144]
[0145]
[0146]
[0147] Depending on the configuration information, the base station may configure one or more search space sets for the terminal. According to one embodiment of the present disclosure, the base station may configure search space set 1 and search space set 2 for the terminal. In search space set 1, the terminal may be configured to monitor DCI format A scrambled with X-RNTI in a common search space, and in search space set 2, the terminal may be configured to monitor DCI format B scrambled with Y-RNTI in a terminal-specific search space.
[0148] According to the configuration information, one or more search space sets may exist in a common search space or a terminal-specific search space. For example, search space set #1 and search space set #2 may be configured as a common search space, and search space set #3 and search space set #4 may be configured as terminal-specific search spaces.
[0149] In a common search space, a terminal can monitor the following combinations of DCI formats and RNTIs, although these are not limited to the following examples.
[0150] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI
[0151] - DCI format 2_0 with CRC scrambled by SFI-RNTI
[0152] - DCI format 2_1 with CRC scrambled by INT-RNTI
[0153] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI
[0154] - DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI
[0155] In a terminal-specific search space, a terminal can monitor the following combinations of DCI formats and RNTIs, although these are not limited to the following examples.
[0156] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI
[0157] - DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI
[0158] The above-mentioned RNTIs may follow the following definitions and uses:
[0159] - C-RNTI (Cell RNTI): For terminal-specific PDSCH or PUSCH scheduling purposes.
[0160] - TC-RNTI (Temporary Cell RNTI): For terminal-specific PDSCH scheduling purposes.
[0161] - CS-RNTI (Configured Scheduling RNTI): Used for terminal-specific PDSCH scheduling that is set semi-statically.
[0162] - RA-RNTI (Random Access RNTI): Used for PDSCH scheduling in the random access phase.
[0163] - P-RNTI (Paging RNTI): Used for scheduling PDSCH where paging is transmitted.
[0164] - SI-RNTI (System Information RNTI): Used for scheduling PDSCH where system information is transmitted.
[0165] - INT-RNTI (Interruption RNTI): Used to indicate whether pucturing is in progress for PDSCH.
[0166] - TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to indicate power control commands for PUSCH.
[0167] - TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to indicate power control commands for PUCCH.
[0168] - TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to indicate power control commands for SRS.
[0169] The DCI formats described above can follow the definitions shown in below.
[0170] [Table 7]
[0171]
[0172] CORESET p, the search space of aggregation level L in the search space set s can be expressed as the following mathematical formula.
[0173] [Mathematical Formula 1]
[0174]
[0175] - : Integration level
[0176] - : Carrier Index
[0177] - : Total number of CCEs existing within the control region p
[0178] - : slot index
[0179] - : Number of PDCCH candidates for aggregation level L
[0180] - : PDCCH candidate index of aggregation level L
[0181] -
[0182] - , , , , ,
[0183] - : Terminal identifier
[0184] The value can be 0 for a common search space.
[0185] In the case of a terminal-specific search space, the value may correspond to a value that changes according to the terminal's ID (C-RNTI or ID set to the terminal by the base station) and time index.
[0186] Next, we will specifically explain downlink control information (DCI) in the 5G system.
[0187] In a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) can be transmitted from a base station to a terminal via DCI. The terminal can monitor a DCI format for fallback and a DCI format for non-fallback for the PUSCH or PDSCH. The fallback DCI format can be composed of fixed fields defined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.
[0188] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after going through the channel coding and modulation process. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the UE. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly, but is included in the CRC calculation process. When the UE receives a DCI message transmitted on the PDCCH, it verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the UE can determine that the message was transmitted to the UE.
[0189] For example, a DCI scheduling a PDSCH for System Information (SI) may be scrambled with SI-RNTI. A DCI scheduling a PDSCH for a Random Access Response (RAR) message may be scrambled with RA-RNTI. A DCI scheduling a PDSCH for a Paging message may be scrambled with P-RNTI. A DCI notifying a Slot Format Indicator (SFI) may be scrambled with SFI-RNTI. A DCI notifying a Transmit Power Control (TPC) may be scrambled with TPC-RNTI. A DCI scheduling a UE-specific PDSCH or PUSCH may be scrambled with C-RNTI (Cell RNTI).
[0190] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI can include the following information, for example, as shown in Table 8.
[0191] [Table 8]
[0192]
[0193] DCI format 0_1 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 with the CRC scrambled with C-RNTI can include the following information, for example, as shown in Table 9.
[0194] [Table 9]
[0195]
[0196]
[0197]
[0198]
[0199] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI can include the following information, for example, as shown in Table 10.
[0200] [Table 10]
[0201]
[0202] DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include the following information, for example, as shown in Table 11.
[0203] [Table 11]
[0204]
[0205]
[0206]
[0207] FIG. 5 is a diagram illustrating an example of DRX operation according to one embodiment of the present disclosure.
[0208] DRX (Discontinuous Reception) is an operation in which a terminal using a service discontinuously receives data while in an RRC Connected state, where a radio link is established between the base station and the terminal. When DRX is applied, the terminal turns on the receiver at a specific time to monitor the control channel, and if no data is received for a certain period of time, the receiver is turned off, thereby reducing the terminal's power consumption. DRX operation can be controlled by the MAC layer device based on various parameters and timers.
[0209] Referring to FIG. 5, the active time (505) is the time during which the terminal wakes up every DRX cycle and monitors the PDCCH. The active time (505) can be defined as follows.
[0210] - drx-onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimerDL or drx-RetransmissionTimerUL or ra-ContentionResolutionTimer is running; or
[0211] - a Scheduling Request is sent on PUCCH and is pending; or
[0212] - a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the Random Access Preamble not selected by the MAC entity among the contention-based Random Access Preamble
[0213] drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, ra-ContentionResolutionTimer, etc. are timers whose values are set by the base station, and have the function of setting the terminal to monitor the PDCCH when a certain condition is met.
[0214] drx-onDurationTimer (515) is a parameter for setting the minimum time for which the terminal stays awake in the DRX cycle. drx-InactivityTimer (520) is a parameter for setting the additional time for which the terminal stays awake when receiving (530) a PDCCH indicating a new uplink transmission or downlink transmission. drx-RetransmissionTimerDL is a parameter for setting the maximum time for which the terminal stays awake to receive a downlink retransmission in the downlink HARQ procedure. drx-RetransmissionTimerUL is a parameter for setting the maximum time for which the terminal stays awake to receive an uplink retransmission grant in the uplink HARQ procedure. drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, and drx-RetransmissionTimerUL can be set to, for example, time, the number of subframes, the number of slots, etc. ra-ContentionResolutionTimer is a parameter for monitoring PDCCH in random access procedure.
[0215] The inActive time (510) is a time set not to monitor PDCCH during DRX operation and / or a time set not to receive PDCCH. The remaining time excluding the Active time (505) from the entire time of performing the DRX operation can be the inActive time (510). If the terminal does not monitor the PDCCH during the Active time (505), it can enter a sleep or inActive state to reduce power consumption.
[0216] DRX cycle refers to the period during which the terminal wakes up and monitors the PDCCH. In other words, it refers to the time interval or on duration that occurs after the terminal monitors the PDCCH until it monitors the next PDCCH. DRX cycles are divided into two types: short DRX cycle and long DRX cycle. The short DRX cycle can be applied optionally.
[0217] Long DRX cycle (525) is the longer cycle among the two DRX cycles set in the terminal. While operating in Long DRX, the terminal starts drx-onDurationTimer (515) again at a point in time when Long DRX cycle (525) has elapsed from the starting point (e.g., start symbol) of drx-onDurationTimer (515). When operating in Long DRX cycle (525), the terminal can start drx-onDurationTimer (515) in a slot after drx-SlotOffset in a subframe satisfying Mathematical Formula 2 below. Here, drx-SlotOffset means a delay before starting drx-onDurationTimer (515). drx-SlotOffset can be set to, for example, time, the number of slots, etc.
[0218] [Equation 2]
[0219]
[0220] At this time, drx-LongCycleStartOffset can be used to define a Long DRX cycle (525) and drx-StartOffset can be used to define a subframe at which to start the Long DRX cycle (525). drx-LongCycleStartOffset can be set to, for example, a time, a number of subframes, a number of slots, etc.
[0221] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Hereinafter, a base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, a gNB, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a wireless access point, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Although embodiments of the present disclosure are described below using a 5G system as an example, embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, this may include LTE or LTE-A mobile communication and mobile communication technologies developed after 5G. Therefore, embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure as determined by a person skilled in the art. The contents of this disclosure can be applied to FDD (frequency division duplex), TDD (time division duplex), XDD (cross division duplex) systems, etc.
[0222] Additionally, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents of this specification.
[0223] In the following description of the present disclosure, upper layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.
[0224] - MIB (Master Information Block)
[0225] - SIB (System Information Block) or SIB
[0226] - RRC (Radio Resource Control)
[0227] - MAC (Medium Access Control) CE (Control Element)
[0228] In addition, L1 signaling may be signaling corresponding to at least one or a combination of one or more signaling methods using the following physical layer channels or signaling.
[0229] - PDCCH (Physical Downlink Control Channel)
[0230] - DCI (Downlink Control Information)
[0231] - UE-specific DCI
[0232] - Group common DCI
[0233] - Common DCI
[0234] - Scheduling DCI (e.g. DCI used for scheduling downlink or uplink data)
[0235] - Non-scheduled DCI (e.g. DCI not intended for scheduling downlink or uplink data)
[0236] - PUCCH (Physical Uplink Control Channel)
[0237] - UCI (Uplink Control Information)
[0238] In the present disclosure, the fact that a specific signal includes a specific sequence, or that a specific signal is a specific sequence, or that a specific signal corresponds to a specific sequence may also be interpreted as the specific signal being generated based on a specific sequence.
[0239] In the present disclosure below, the above examples are described through a number of embodiments, but they are not independent and one or more embodiments may be applied simultaneously or in combination.
[0240] As described above, to achieve ultra-high-speed data services reaching several Gbps in 5G systems, ultra-wide bandwidth signal transmission and reception of tens to hundreds of MHz or even several GHz may be supported. Ultra-wide bandwidth signal transmission and reception may be supported through a single component carrier (CC) or through carrier aggregation (CA) technology that combines multiple component carriers. When a mobile communication service provider is unable to secure a frequency with sufficient bandwidth for ultra-high-speed data services through a single component carrier, carrier aggregation technology can increase the total frequency bandwidth by combining individual component carriers with relatively small bandwidths, thereby enabling ultra-high-speed data services.
[0241] 5G systems are designed and developed to address a wide range of use cases. In addition to standby time, reliability, and availability, device energy efficiency is crucial in 5G systems. 5G devices typically require weekly or daily charging, depending on individual usage, consuming tens of mW in RRC_IDLE / RRC_INACTIVE states and hundreds of mW in RRC_CONNECTED states. Designing for extended battery life is essential not only for a better user experience but also for improving energy efficiency. Energy efficiency is even more critical for devices without a continuous energy source, such as those using small rechargeable and / or single coin cell batteries. Sensors and actuators are widely deployed in 5G use cases for monitoring, measurement, and charging. Typically, their batteries are non-rechargeable and expected to last at least several years. Wearables, including smartwatches, rings, eHealth devices, and medical monitoring devices, typically struggle to maintain a battery life of more than one to two weeks, depending on usage.
[0242] The power consumption of 5G terminals depends on the configured length of wake-up periods, such as paging cycles. To meet battery life requirements, extended discontinuous reception (eDRX) cycles with large values are expected to be used. However, eDRX methods are not suitable for low-latency services because they maintain long battery life based on high latency. For example, in fire detection and extinguishing use cases, fire shutters must be closed and sprinklers must be turned on by actuators within 1-2 seconds of a fire being detected by a sensor. In other words, since latency is a critical use case, long eDRX cycles as in the past cannot meet the latency requirements, making eDRX unsuitable for such cases.
[0243] In one embodiment, a 5G terminal may require a periodic wake-up once per eDRX cycle, which may impact power consumption during periods of no signaling or data traffic. If the terminal could wake up only when triggered, such as by paging, power consumption could be drastically reduced. This can be achieved by triggering the main radio (NR radio) using a wake-up signal (WUS), as shown in FIG. 6, and using a separate receiver, a wake-up receiver (WUR), that can monitor the WUS at ultra-low power to turn on the main radio only when data transmission and reception are required (and / or when transmission and reception of non-WUS signals are required). In the present disclosure, the main radio may be a transceiver used to transmit and receive signals other than WUS, such as configuration information / control information / data, etc.
[0244] FIG. 6 is a diagram illustrating a base station instructing a terminal with a WUR to switch to a main radio state through a WUS according to one embodiment of the present disclosure.
[0245] Referring to FIG. 6, for example, when a base station transmits a WUS (601) corresponding to ON or OFF to a terminal (UE), the terminal receives the WUS using a WUR (602). The terminal triggers (603) the main radio (604) in the OFF or ON state according to the ON or OFF information included in the received signal, thereby waking it up or turning it off, respectively. In some cases, the terminal may not completely turn the main radio (504) off, but may also set it to a deep sleep state. If data traffic (605) to be sent from the base station to the terminal is generated and a signal corresponding to WUS ON is transmitted (i.e., if the WUS includes ON information), the main radio of the terminal becomes ON (606), and the terminal receives the data transmitted by the base station through the main radio, not the WUR. Since the power consumption for monitoring WUS depends on the WUS design and the hardware modules of WUR used for signal detection and processing, the gains can be maximized, particularly for power-sensitive and small form factor devices including IoT (internet of things) use cases (e.g., industrial sensors, controllers, etc.) and wearables, according to one embodiment.
[0246] Terminals in the RRC_IDLE / INACTIVE state with WUR and terminals in the RRC_CONNECTED state can perform different operations. That is, terminals with WUR can perform different operations depending on the RRC state. The following embodiments describe the operations of terminals in the RRC_CONNECTED state. However, at least some of the following embodiments can also be applied to terminals in the RRC_IDLE / INACTIVE state.
[0247] <Example 1>
[0248] The first embodiment is about a terminal procedure for an RRC_CONNECTED terminal in power saving state with WUR to wake up the main radio after receiving WUS regardless of DRX settings.
[0249] In the case of existing terminals, a technology called C-DRX (connected mode DRX) was introduced to save terminal power, so that PDCCH can be monitored or data can be transmitted / received in a specific section for each cycle. Therefore, long DRX cycles and short DRX cycles can be set according to the traffic situation of RRC_CONNECTED terminals to allow the terminal to stay in the sleep state for as long as possible. However, in the case of a long DRX cycle, a long delay time may occur from traffic generation to reception, and in the case of a short DRX cycle, the terminal must wake up and perform PDCCH monitoring regardless of traffic presence, resulting in high power consumption. Furthermore, since the DRX cycle changes semi-statically at the MAC-CE (medium access control-control element) level, it could not flexibly respond to various traffic situations.
[0250] FIG. 7 is a diagram showing an example of an operation in which an RRC_CONNECTED terminal with WUR according to one embodiment of the present disclosure dynamically activates DRX when a WUS arrives regardless of the concept of a DRX cycle.
[0251] According to one embodiment, triggering of DRX can be indicated via WUS. That is, DRX can be triggered aperiodically via WUS. For example, WUS can indicate on / off of DRX with 1 bit. For example, if the value of 1 bit is 0, it can correspond to off, if the value of 1 bit is 1, it can correspond to on, and vice versa. As another example, WUS can include information on a starting point of DRX (e.g., start time) and / or a time period during which DRX should be on (on duration time). This will be described in more detail below.
[0252] Referring to FIG. 7, a terminal having a WUR can operate an MR (main radio / main receiver) (701) and an LR (low power wake up receiver / low power wake up radio) (702) within the terminal. A terminal having a WUR can include an MR (701) and an LR (702). In the present disclosure, the operation of the MR can be understood as an operation of the terminal using the MR and / or an operation of the terminal through the MR and / or a control operation of the terminal with respect to the MR, and the operation of the LR can be understood as an operation of the terminal using the LR and / or an operation of the terminal through the LR and / or a control operation of the terminal with respect to the LR.
[0253] Among MR (701) and LR (702), MR (701) consumes a lot of power even when C-DRX is applied. Therefore, in order to reduce power consumption of the terminal, when there is no change in traffic or system information, MR (701) can be maintained in deep sleep (710) or ultra deep sleep state.
[0254] Both the Deep sleep state and the Ultra Deep Sleep state are states where the power of the terminal is minimized, and the Ultra Deep Sleep state can be said to be a higher power saving state that turns off even the memory of the terminal. Unlike the RRC_IDLE / INACTIVE terminal, the RRC_CONNECTED terminal requires a lot of transition time and power / energy to switch from the Ultra Deep Sleep state to the Active state. Therefore, it may be more efficient for the terminal to maintain the Deep Sleep state even if it consumes more power than the Ultra Deep Sleep state. Accordingly, the MR (701) can be maintained in the Deep Sleep (710) state while the WUS (720) comes through the LR (702). The WUS (720) may simply be the ID of the terminal, or the group ID or cell ID to which the terminal belongs. Alternatively, the maintenance time and start time for the DRX cycle to be activated may be specified and transmitted. That is, WUS (720) may include the ID of the terminal and / or the group ID and / or the cell ID that the terminal is included in and / or information about the DRX cycle to be activated (e.g., onDurationTimer for the on duration of the DRX cycle, start time, etc.).
[0255] The LR (702) receiving the WUS (720) triggers the MR (701) to wake up immediately or after a specific application time. The MR (701) can become active (715) after a specific transition time and start the on duration for the DRX cycle. The terminal in the active (715) state can perform PDCCH monitoring or data transmission and reception according to the DRX operation in the on duration time within the C-DRX cycle of the terminal. After completing all transmission and reception, the terminal transitions back to the Deep sleep (710) state and enters a power saving state. That is, after the terminal finishes transmission and reception, the MR (701) transitions to the Deep sleep (710) state.
[0256] <Example 2>
[0257] A second embodiment relates to a terminal procedure in which an RRC_CONNECTED terminal in a power-saving state with a WUR receives a WUS to indicate whether it should wake up from a configured DRX state. At least a portion of the second embodiment may be combined with at least a portion of the first embodiment.
[0258] FIG. 8 is a description of DCI format 2_6 that indicates whether an existing terminal should wake up for PDCCH monitoring in the next DRX cycle. DCI format 2_6 may be DCP (DCI with CRC (cyclic redundancy check) scrambled with PS-RNTI (power saving radio network temporary identifier)) and may be understood as an example of WUS. In the present disclosure, DCI format 2_6 may be used as WUS and / or a signal different from DCI format 2_6 may be used as WUS. The name WUS is an example and a signal with a different name may be used.
[0259] Referring to Fig. 8, for existing terminals, a long drx-Cycle (820) is set for each cycle. At the start of each cycle, drx-onDurationTimer (821) is set, and if a PDCCH for the terminal is found within the drx-onDurationTimer (821) period (825), drx-inactivityTimer (826) is started to prepare for the arrival of a subsequent PDCCH. However, since the terminal must wake up and monitor the PDCCH every long drx-Cycle (820) even if there is no traffic, large power consumption is expected.
[0260] To reduce this power consumption, the terminal can check whether to start drx-onDurationTimer (821) by receiving DCI format 2_6 (810) before starting a DRX cycle. DCI format 2_6 (810) is a 1-bit indicator, which indicates not to start drx-onDurationTimer (821) when it is 0, and indicates to start drx-onDurationTimer (821) when it is 1. This allows the terminal to maintain a power saving state for a longer period of time, but in order to receive DCI format 2_6, the terminal must synchronize by receiving terminal SSB burst for each DRX cycle and perform AGC (Automatic Gain Control) settling, which is inefficient.
[0261] FIG. 9 is a diagram illustrating an example of an operation for a terminal procedure in which an RRC_CONNECTED terminal with WUR receives a WUS and is informed whether or not the configured DRX should occur according to one embodiment of the present disclosure.
[0262] Referring to FIG. 9, a terminal having WUR may set drx-onDurationTimer (915 or 916) for each DRX cycle in the MR (901). However, since traffic or system information changes may not occur, the terminal may receive a WUS (920) from the base station indicating that drx-onDurationTimer (915) does not need to be started from the LR (902). Therefore, the WUS (920) may need to be received earlier than drx-onDurationTimer (915). This may be determined based on the UE capability considering the state transition time of the terminal. That is, the time at which the WUS (920) should be received is determined by the UE capability, and the time may be determined as a certain time interval based on the start time of drx-onDurationTimer (915) or the start time of the DRX cycle. The WUS (920) may need to be received at least before or up to the time. For example, a terminal may decide whether to skip drx-onDurationTimer (915) only after receiving WUS (920) before X slots. WUS (920) may include 1-bit information indicating 0, similar to DCI format 2_6, and / or may be based on a sequence that plays a similar role to 1-bit information indicating 0. A terminal that receives WUS (920) does not start drx-onDurationTimer (915) and remains in deep sleep (910).
[0263] Similarly, just before the next DRX cycle, the UE may receive WUS (925) before X slots. In this case, WUS (925) may include 1-bit information indicating 1 and / or may be based on a sequence that plays a similar role to 1-bit information indicating 1. The UE may start drx-onDurationTimer (916) to monitor the PDCCH during this period. In the example of FIG. 9, there may be a case where WUS (920) is not received and only WUS (925) is received, in which case the UE / base station may operate similarly to the first embodiment. In this embodiment, since WUS replaces DCI format 2_6, it is necessary to consider the operation of the UE when WUS is not received. For example, when the UE does not receive WUS, the UE may determine that WUS was transmitted but not received and may receive DCI format 2_6. And / or if WUS is not received, the terminal may recognize that the base station did not instruct the terminal to wake up and may not wake up in the next C-DRX.
[0264] <Example 3>
[0265] The third embodiment is about a terminal procedure in which an RRC_CONNECTED terminal with WUR receives WUS and performs PDCCH skipping.
[0266] Figure 10 is a diagram of the PDCCH skipping operation of an existing terminal.
[0267] If the first and second embodiments were methods for reducing power consumption of a terminal at the DRX cycle level of the terminal, PDCCH skipping is a method for reducing power consumption within the DRX onDuration cycle (1000). An existing terminal receives a PDCCH monitoring occasion (1010) at a specific cycle. In the PDCCH monitoring occasion (1010), various search space types of PDCCHs (1020 or 1025) with different cycles can be monitored. Table 12 summarizes various types of PDCCH search space types. Table 12 is an example of a PDCCH search space type, and the present disclosure is not limited thereto.
[0268] [Table 12]
[0269]
[0270] To reduce the number of PDCCH monitoring times during DRX active time in Active BWP, a PDCCH monitoring adaptation indication of {0, 1, 2} bits may be transmitted in DCI format 0_1 / 0_2 / 1_1 / 1_2. Two methods for reducing the number of PDCCH monitoring times include PDCCH skipping, which skips PDCCH monitoring during a specific period, and search space set group (SSSG) switching, which adjusts the number of PDCCH monitoring times. Both of these techniques (PDCCH skipping and SSSG switching) may be indicated in one indication, and / or only one of them may be indicated. For SSSG switching and PDCCH skipping, candidate skipping durations are indicated via PDCCH-Config in RRC, as shown in Table 13.
[0271] [Table 13]
[0272]
[0273] In both technologies, three values from 1 to 800 are first selected / identified through RRC, and specific values can be specified through PDCCH monitoring adaptation indication of DCI 1_X and 2_X.
[0274] In a situation where only one of PDCCHSkippingDurationList and searchSpaceGroupIdList-r17 is defined in RRC, a PDCCH monitoring adaptation indication of {1, 2} bits can be sent down. In the case of 1 bit, the first of the three values set in RRC can be selected, and in the case of 2 bits, one of the three can be selected.
[0275] On the other hand, if both PDCCHSkippingDurationList and searchSpaceGroupIdList-r17 are set in RRC, 2 bits of PDCCH monitoring adaptation indication can be sent, and 1 bit each can be dedicated / corresponded, and the first values set in RRC can be applied.
[0276] Therefore, referring to FIG. 10, assuming that the DCI format is 1_X or 2_X in PDCCH (1025) and only PDCCHSkippingDurationList is set, the skipping duration (1045) can be indicated through the skipping indication (1040) in PDCCH (1025). At this time, PDCCH skipping can be applied 1 slot after receiving PDCCH (925). At this time, only Type3-PDCCH and USS in Table 12 can be skipped. PDSCH (1030) or Type0 / 0A / 0B / 1 / 1A / 2 / 2A-PDCCH (e.g., 1020) cannot be skipped. This may be because Type 0 / 0A / 0B / 1 / 1A / 2 / 2A-PDCCHs contain important information, such as system information, Msg2, 4, or paging, and thus the terminal must monitor these PDCCHs during the skipping period. Due to this behavior, skipping operations, which reduce terminal power consumption, are inevitably limited.
[0277] FIG. 11 is a diagram illustrating an example of a PDCCH skipping operation of an RRC_CONNECTED terminal with WUR according to an embodiment of the present disclosure. FIG. 11 illustrates an operation within a DRX onDuration cycle (1100), but the present disclosure is not limited thereto.
[0278] Referring to FIG. 11, an RRC_CONNECTED terminal with WUR can skip not only Type3-PDCCH and USS but also Type0 / 0A / 0B / 1 / 1A / 2 / 2A-PDCCH to minimize power consumption in the PDCCH skipping section, unlike existing terminals.
[0279] When PDCCH monitoring adaptation indication (1140) is indicated on PDCCH (1125) transmitting Type 1_X and 2_X in MR (1160), all types of PDCCHs are skipped during the PDCCH skipping duration one slot later. And / or, configured grants, semi-persistent scheduling, etc. scheduled during the period may also be skipped to further reduce power consumption.
[0280] While all types of PDCCHs are being skipped, that is, while Type0 / 0A / 0B / 1 / 1A / 2 / 2A-PDCCH as well as Type3-PDCCH and USS are being skipped, if Type0-PDCCH needs to be monitored by the corresponding terminal for (important) system information change, etc., the base station may transmit a WUS (1170) containing information to monitor the corresponding type of PDCCH (Type0-PDCCH) to LR (1150). Type0-PDCCH is exemplary, and the present disclosure may be applied to Type0 / 0A / 0B / 1 / 1A / 2 / 2A-PDCCH as well as Type3-PDCCH and USS. That is, the WUS may indicate at least some of the types of PDCCHs being skipped, which are different from Type0-PDCCH.
[0281] The LR (1150) that receives the corresponding WUS can trigger the MR (1160) to wake up, so that the terminal can monitor the corresponding PDCCH in the MR (1160) during a specific period. After the required PDCCH monitoring is completed, the terminal can skip the PDCCH for the remaining skipping period, or assume that the PDCCH skipping has already expired and monitor various types of PDCCH as before the PDCCH monitoring adaptation indication.
[0282] To enable the operation illustrated in FIG. 11 to be performed, a terminal with WUR may have a specification change as in the example in Table 14 to enable skipping of all types of PDCCHs during the PDCCH skipping period.
[0283] [Table 14]
[0284]
[0285] That is, if an RRC configuration called PDCCHTypeIndicationforWUS is set in a terminal with WUR, the terminal can skip all PDCCHs. The present disclosure is not limited to an IE (information element) with a specific name, and an IE with a name other than the name used in the present disclosure may be used. For example, PDCCHTypeIndicationforWUS is an example, and an IE with a different name may be used.
[0286] Additionally, the operation of the terminal may vary depending on what content / information is contained / included in the WUS that can instruct this (i.e., the WUS that instructs the PDCCH of the specific type mentioned above).
[0287] First, when a terminal simply receives a WUS, there are cases where MR occurs depending on the terminal's capability or after a fixed specific time to view / monitor all types of PDCCHs. In this case, the content / information included in the WUS may be the terminal's ID, the group ID to which the terminal belongs, or the cell ID. Or, it may be 1 bit of 0 or 1, or a sequence equivalent thereto. That is, in this case, the terminal's ID and / or the group ID to which the terminal belongs and / or the cell ID and / or 1 bit (which may correspond to the WUS indication) may be transmitted and received through the WUS, and / or the WUS may be based on a sequence equivalent to 1 bit.
[0288] A UE that receives a corresponding WUS in LR can trigger the MR to wake up. The MR that wakes up after a certain time (e.g., from the trigger time) will monitor both PDCCH and USS of Type 0 / 0A / 0B / 1 / 1A / 2 / 2A / 3. Alternatively, the WUS can indicate the PDCCH search space type to be monitored by the UE. For this purpose, the WUS can be composed of multiple bits and / or various sequences can be supported for indication. For example, the PDCCH search space type can be set / indicated based on multiple bits included in the WUS. Each bit can correspond to a different PDCCH search space type. That is, the PDCCH search space type can be set / indicated using a bitmap. As another example, the PDCCH search space type can be set / indicated based on a sequence based on the WUS, in which case each sequence of the multiple sequences that the WUS can be based on can correspond to a different PDCCH search space type. The terminal receiving the WUS (and / or the MR of the terminal) wakes up and monitors the PDCCH of the specified type, depending on the terminal's capability or after a fixed specific time.
[0289] In addition, according to one embodiment, the time for which the terminal performs monitoring may also be defined. For example, since it may take a long time for the terminal to monitor all types of PDCCHs, a value for this may be determined based on the capability of the terminal. The maximum value of the capability of the terminal may be a time interval from the time of WUS reception to the time of PDCCH skipping termination or a time interval corresponding thereto. For example, it may be considered that PDCCH monitoring is instructed to be performed with the maximum value of the capability of the terminal, and after the PDCCH is detected, the MR is switched back to deep sleep. And / or, the monitoring period may be set according to the number of PDCCH search spaces to be monitored. For example, a relatively long time may be required for monitoring all types of PDCCHs, and a relatively short time may be required for monitoring a specific type of PDCCH.
[0290] FIG. 12 is a diagram illustrating an example of the operation of a terminal and a base station according to one embodiment of the present disclosure. Various modifications may be made to the method illustrated in the flowchart of FIG. 12 . For example, although illustrated as a series of steps, the various steps in each diagram may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.
[0291] Referring to FIG. 12, in operation 1201 according to one embodiment, a terminal may receive a WUS. The terminal may receive the WUS using an LR. Information included in the WUS may be based on at least some of the contents described in the first to third embodiments. For example, the WUS may include an ID of the terminal and / or a group ID and / or a cell ID to which the terminal is included and / or information about a DRX cycle to be active. The terminal may also receive configuration information related to the WUS and perform a WUS reception operation based on the configuration information.
[0292] In operation 1203 according to one embodiment, the terminal may activate the MR (or wake up the MR) based on the WUS. That is, whether the MR is activated may be determined based on the WUS. More specific conditions for activating the MR may be based on at least some of the contents described in the first to third embodiments.
[0293] In operation 1205 according to one embodiment, the terminal may perform operations related to PDCCH monitoring. For example, the terminal may perform PDCCH monitoring through an activated MR and receive a PDCCH transmitted from a base station. PDCCH monitoring may be performed based on a DRX operation.
[0294] The base station can transmit WUS-related configuration information and / or WUS to the terminal. For example, if the base station has data to transmit to the terminal, it can transmit WUS related to activating the MR of the terminal. Afterwards, the base station can transmit a PDCCH to the terminal.
[0295] FIG. 13 is a diagram illustrating an example of a terminal transceiver in a wireless communication system according to one embodiment of the present disclosure. FIG. 13 illustrates an example of a terminal transceiver, and the terminal transceiver may further include other configuration blocks in addition to the illustrated configuration blocks.
[0296] Referring to FIG. 13, the terminal may be configured with a transmitter (1304) including an uplink transmission processing block (1301), a multiplexer (1302), and a transmission RF block (1303), a receiver (1308) including a downlink reception processing block (1305), a demultiplexer (1306), and a reception RF block (1307), and a control unit (1309). As described above, the control unit (1309) may control each of the configuration blocks of the receiver (1308) for receiving a data channel or control channel transmitted by the base station and each of the configuration blocks of the transmitter (1104) for transmitting an uplink signal.
[0297] In the transmitter (1304) of the terminal, the uplink transmission processing block (1301) can generate a signal to be transmitted by performing processes such as channel coding and modulation. The signal generated in the uplink transmission processing block (1301) can be multiplexed with another uplink signal by a multiplexer (1302), and then transmitted to the base station after signal processing in the transmission RF block (1303).
[0298] The terminal's receiving unit (1308) demultiplexes the signal received from the base station and distributes it to each downlink receiving processing block. The downlink receiving processing block (1305) can perform processes such as demodulation and channel decoding on the downlink signal of the base station to obtain control information or data transmitted by the base station. The terminal receiving unit (1308) can support the operation of the control unit (1309) by applying the output result of the downlink receiving processing block to the control unit (1309).
[0299] FIG. 14 is a block diagram showing an example of a configuration of a terminal according to one embodiment of the present disclosure.
[0300] As illustrated in FIG. 14, the terminal of the present disclosure may include a processor (1430), a transceiver (1410), and a memory (1420). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the processor (1430), the transceiver (1410), and the memory (1420) may be implemented in the form of a single chip. According to one embodiment, the transceiver (1410) of FIG. 14 may include the transmitter (1304) and receiver (1308) of FIG. 13. In addition, the processor (1430) of FIG. 14 may include the control unit (1309) of FIG. 13.
[0301] According to one embodiment, the processor (1430) may control a series of processes that enable the terminal to operate according to the embodiments of the present disclosure described above. For example, according to an embodiment of the present disclosure, the processor may control components of the terminal to perform a transmission and reception method of the terminal depending on whether the base station mode is the base station energy saving mode or the base station normal mode. There may be one or more processors (1430), and the processors (1430) may perform operations of the terminal according to the embodiments of the present disclosure described above by executing a program stored in the memory (1420).
[0302] The transceiver (1410) can transmit and receive signals with a base station. The signals transmitted and received with the base station can include control information and data. The transceiver (1410) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and frequency-converts a received signal. However, the transceiver (1410) is only one embodiment, and the components of the transceiver (1410) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1410) can receive a signal through a wireless channel, output it to the processor (1430), and transmit a signal output from the processor (1430) through the wireless channel.
[0303] According to one embodiment, the memory (1420) can store programs and data necessary for the operation of the terminal. In addition, the memory (1420) can store control information or data included in signals transmitted and received by the terminal. The memory (1420) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (1420). According to one embodiment, the memory (1420) can store a program for performing transmission and reception operations of the terminal depending on whether the base station mode of the embodiments of the present disclosure described above is a base station energy saving mode or a base station normal mode.
[0304] FIG. 15 is a block diagram showing an example of a configuration of a base station according to one embodiment of the present disclosure.
[0305] As illustrated in FIG. 15, the base station of the present disclosure may include a processor (1530), a transceiver (1510), and a memory (1520). However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. Furthermore, the processor (1530), the transceiver (1510), and the memory (1520) may be implemented in the form of a single chip.
[0306] The processor (1530) can control a series of processes so that the base station can operate according to the above-described embodiment of the present disclosure. The processor (1530) can control components of the base station to perform a method according to an embodiment of the present disclosure. There may be one or more processors (1530), and the processors (1530) can perform the method according to the above-described embodiment of the present disclosure by executing a program stored in the memory (1520).
[0307] The transceiver (1510) can transmit and receive signals with the terminal. The signals transmitted and received with the terminal can include control information and data. The transceiver (1510) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, an RF receiver that low-noise amplifies the received signal and down-converts the frequency, etc. However, the transceiver (1510) is only one embodiment, and the components of the transceiver (1510) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1510) can receive a signal through a wireless channel and output it to the processor (1530), and transmit a signal output from the processor (1530) through the wireless channel.
[0308] According to one embodiment, the memory (1520) may store programs and data necessary for the operation of the base station. In addition, the memory (1520) may store control information or data included in signals transmitted and received by the base station. The memory (1520) may be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there may be a plurality of memories (1520). According to one embodiment, the memory (1520) may store a program for performing a method according to the embodiments of the present disclosure described above.
[0309]
[0310] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0311] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present disclosure.
[0312] These programs (software modules, software) may be stored in a non-volatile memory including random access memory, flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage devices, compact disc ROMs (CD-ROMs), digital versatile discs (DVDs) or other forms of optical storage devices, magnetic cassettes, or may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.
[0313] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present disclosure.
[0314] In the specific embodiments of the present disclosure described above, components included in the present disclosure are expressed singularly or plurally, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.
[0315] Meanwhile, the present specification and drawings disclose preferred embodiments of the present disclosure, and although specific terms are used, they are used in a general sense only to easily explain the technical contents of the present disclosure and to aid in the understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. It will be apparent to those skilled in the art to which the present disclosure pertains that other modified examples based on the technical idea of the present disclosure are possible in addition to the embodiments disclosed herein. In addition, each of the above embodiments can be combined and operated as needed.
[0316] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.
Claims
1. In a method performed by a terminal in a communication system, A step of receiving, through upper layer signaling, a configuration for a plurality of time intervals for skipping PDCCH (physical downlink control channel) monitoring and a configuration related to skipping of PDCCH monitoring through MR (main radio) of the terminal; A step of receiving DCI (downlink control information) including information related to a time period among the plurality of time periods; A step of skipping PDCCH monitoring through the MR in the above time interval; and A method comprising: performing PDCCH monitoring through the MR during at least a portion of a time period after the WUS is received in the time period, when a WUS (wake up signal) is received through the LR (low power wake up receiver) of the terminal within the time period.
2. In paragraph 1, A method wherein PDCCH monitoring through the above MR is skipped for a plurality of PDCCH search space types, wherein the plurality of PDCCH search space types include a user equipment specific search space (USS) and a Type3-PDCCH CSS (common search space), and further include one or more of Type0-PDCCH CSS, Type0A-PDCCH CSS, Type0B-PDCCH CSS, Type1A-PDCCH CSS, Type2-PDCCH CSS, or Type2A-PDCCH CSS.
3. In paragraph 2, A method wherein PDCCH monitoring through the MR is performed for the plurality of PDCCH search space types after the WUS is received, or for a specific PDCCH search space type indicated by the WUS among the plurality of PDCCH search space types after the WUS is received.
4. In paragraph 1, A method in which, when a DRX (discontinuous reception) configuration is received through the upper layer signaling and a WUS is received through the LR, whether or not drx-onDurationTimer included in the DRX configuration is triggered is indicated by the WUS, and the WUS is different from the DCI format 2_6 for the MR.
5. In paragraph 4, A method wherein, when WUS is set to be monitored via the above LR, the DCI format 2_6 is not monitored via the MR or the DCI format 2_6 received via the MR is ignored.
6. In paragraph 1, A method further comprising the step of transmitting a terminal capability report related to the terminal including the LR.
7. At the terminal of the communication system, Transmitter and receiver; and A processor coupled to the transceiver, the processor comprising: Receive, through upper layer signaling, settings for multiple time intervals for skipping PDCCH (physical downlink control channel) monitoring and settings related to skipping of PDCCH monitoring through MR (main radio) of the terminal; Receiving DCI (downlink control information) including information related to a time interval among the above multiple time intervals; Skipping PDCCH monitoring through the MR during the above time interval; and A terminal configured to perform PDCCH monitoring through the MR during at least a portion of a time period after the WUS is received in the time period, when a WUS (wake up signal) is received through the LR (low power wake up receiver) of the terminal within the time period.
8. In paragraph 7, A terminal, wherein PDCCH monitoring through the above MR is skipped for a plurality of PDCCH search space types, wherein the plurality of PDCCH search space types include a user equipment specific search space (USS) and a Type3-PDCCH CSS (common search space), and further includes at least one of Type0-PDCCH CSS, Type0A-PDCCH CSS, Type0B-PDCCH CSS, Type1A-PDCCH CSS, Type2-PDCCH CSS, or Type2A-PDCCH CSS.
9. In paragraph 8, A terminal in which PDCCH monitoring through the above MR is performed for the plurality of PDCCH search space types after the WUS is received, or for a specific PDCCH search space type indicated by the WUS among the plurality of PDCCH search space types after the WUS is received.
10. In paragraph 7, A terminal in which, when a DRX (discontinuous reception) configuration is received through the upper layer signaling and a WUS is received through the LR, whether or not drx-onDurationTimer included in the DRX configuration is triggered is indicated by the WUS, and the WUS is different from the DCI format 2_6 for the MR.
11. In Article 10, A terminal, wherein when WUS is set to be monitored through the above LR, the DCI format 2_6 is not monitored through the MR or the DCI format 2_6 received through the MR is ignored.
12. In a method performed by a base station in a communication system, A step of transmitting, to the terminal, through upper layer signaling, a setting for a plurality of time intervals for skipping PDCCH (physical downlink control channel) monitoring and a setting related to skipping of PDCCH monitoring through MR (main radio) of the terminal; and Comprising a step of transmitting DCI (downlink control information) including information related to a time section among the plurality of time sections to the terminal, A method wherein, in the time interval, transmission of a PDCCH for the MR to the terminal is skipped, and when a wake up signal (WUS) for a LR (low power wake up receiver) of the terminal is transmitted to the terminal within the time interval, transmission of the PDCCH for the MR to the terminal is performed in at least a part of the time interval after the WUS is transmitted in the time interval.
13. In paragraph 12, A method wherein, when a DRX (discontinuous reception) configuration is received through the upper layer signaling and a WUS for the LR is transmitted, whether or not drx-onDurationTimer included in the DRX configuration is triggered is indicated by the WUS, and the WUS is different from the DCI format 2_6 for the MR.
14. In the base station of the communication system, Transmitter and receiver; and A processor coupled to the transceiver, the processor comprising: Transmitting to the terminal, through upper layer signaling, a configuration for a plurality of time intervals for skipping PDCCH (physical downlink control channel) monitoring and a configuration related to skipping PDCCH monitoring through the terminal's MR (main radio); and It is set to transmit DCI (downlink control information) including information related to a time section among the above multiple time sections to the terminal, A base station, wherein transmission of a PDCCH for the MR to the terminal is skipped during the time interval, and when a wake up signal (WUS) for a LR (low power wake up receiver) of the terminal is transmitted to the terminal within the time interval, transmission of the PDCCH for the MR to the terminal is performed during at least a part of the time interval after the WUS is transmitted during the time interval.
15. In paragraph 14, A base station, wherein, when a DRX (discontinuous reception) configuration is received through the upper layer signaling and a WUS for the LR is transmitted, whether drx-onDurationTimer included in the DRX configuration is triggered is indicated by the WUS, and the WUS is different from the DCI format 2_6 for the MR.
Citation Information
Patent Citations
Physical downlink control channel (PDCCH) monitoring method and apparatus
EP4156760A1
Method and apparatus for activating a cell group without a random access procedure in next-generation wireless communication systems
KR1020230053471A
A Camping house structure for unloading from vehicles
KR1020230148958A
Dynamic physical downlink control channel skipping indication
US20210058304A1
