Discontinuous reception operation method
By introducing BWP-based sleep state management in the NR system, the problem of high UE battery consumption is solved, more efficient power use and fast cell activation/deactivation is achieved, and system efficiency and reliability are improved.
Patent Information
- Application Number
- CN202080072476.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-11-08
- Filing Date
- 2020-09-01
- Publication Date
- 2025-07-15
- Estimated Expiration
- 2040-09-01
AI Technical Summary
When the existing wireless communication system handles the sleep state management of multiple cells, especially in the new radio access technology (NR), there is a problem of high UE battery consumption, especially when switching BWP frequently, resulting in unnecessary PDCCH monitoring and signal reception, affecting battery life.
Bandwidth Part (BWP)-based sleep state management is introduced. By defining sleep BWP and normal BWP, limiting PDCCH monitoring and signal reception, combining BWP inactivity timer and DCI signaling, the UE's sleep and activation state switching is optimized to reduce unnecessary power consumption.
By optimizing the sleep state management of BWP, the power consumption of the UE is reduced, the battery life is improved, and the auxiliary cells are quickly activated/deactivated, improving system efficiency and reliability.
Smart Images

Figure CN114600538B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to wireless communication. Background Art
[0002] As more and more communication devices require more communication capacity, improved mobile broadband communication compared to existing radio access technologies (RATs) is needed. Massive machine type communication (MTC), which provides various services anytime and anywhere by connecting multiple devices and multiple objects, is one of the main issues to be considered in next-generation communication. In addition, the design of a communication system considering services or user equipment (UE) that are sensitive to reliability and latency is being discussed. The introduction of a next-generation RAT considering enhanced mobile broadband communication, massive MTC, and ultra-reliable low-latency communication (URLLC) has been discussed. In the present disclosure, for ease of description, this technology may be referred to as a new RAT or new radio (NR).
[0003] In the LTE system, a dormant state is defined to quickly perform activation / deactivation of a secondary cell (SCell), and when a specific SCell is set to the dormant state, the UE may not monitor the PDCCH for the cell. Thereafter, to quickly activate the corresponding SCell, measurements and reports are defined to be performed in the dormant state to monitor the channel condition and link state of the corresponding cell. For example, when a specific SCell is set to the dormant state, the UE does not perform PDCCH monitoring, but may perform measurements and reports for channel state information (CSI) / radio resource management (RRM). In the NR system, the above-mentioned dormant state or dormant behavior may be defined in units of BWP. Summary of the Invention
[0004] Technical Solution
[0005] The present disclosure provides a method for discontinuous reception operation.
[0006] Advantageous Effects
[0007] According to the present disclosure, considering power saving of the UE, discontinuous reception operation based on BWP activation is provided.
[0008] The effects obtained through the specific examples of this specification are not limited to the foregoing effects. For example, those of ordinary skill in the relevant art can understand or derive various technical effects from this specification. Therefore, the specific effects of the present disclosure are not limited to those clearly indicated herein, but may include various effects that can be understood or derived from the technical features of the present disclosure. Brief Description of the Drawings
[0009] Figure 1 Communication system 1 applied to the present disclosure is illustrated.
[0010] Figure 2Illustrates a wireless device applicable to the present disclosure.
[0011] Figure 3 Illustrates a signal processing circuit for transmitting signals.
[0012] Figure 4 Illustrates another example of a wireless device applicable to the present disclosure.
[0013] Figure 5 Illustrates a handheld device applicable to the present disclosure.
[0014] Figure 6 Illustrates a vehicle or autonomous driving vehicle applicable to the present disclosure.
[0015] Figure 7 Illustrates a vehicle applicable to the present disclosure.
[0016] Figure 8 Illustrates an XR device applicable to the present disclosure.
[0017] Figure 9 Illustrates a robot applicable to the present disclosure.
[0018] Figure 10 Illustrates an AI device applicable to the present disclosure.
[0019] Figure 11 Shows a wireless communication system to which the present disclosure can be applied.
[0020] Figure 12 Is a diagram showing the wireless protocol architecture for the user plane.
[0021] Figure 13 Is a diagram showing the wireless protocol architecture for the control plane.
[0022] Figure 14 Shows another wireless communication system to which the present disclosure can be applied.
[0023] Figure 15 Illustrates the functional division between NG-RAN and 5GC.
[0024] Figure 16 Illustrates an example of a frame structure applicable in NR.
[0025] Figure 17 Illustrates a time slot structure.
[0026] Figure 18 Shows an example of the sleep behavior.
[0027] Figure 19 Shows an example of the BWP operation.
[0028] Figure 20Shows another example of the BWP operation of the UE.
[0029] Figure 21 Is a flowchart of an example of the discontinuous reception method of the UE.
[0030] Figure 22 Is a flowchart illustrating an example of performing the idle mode DRX operation.
[0031] Figure 23 Illustrates an example of the idle mode DRX operation.
[0032] Figure 24 Illustrates an example of the DRX cycle.
[0033] Figure 25 Is a flowchart of the C-DRX operation.
[0034] Figure 26 Illustrates an example of the C-DRX operation.
[0035] Figure 27 Illustrates the power consumption depending on the state of the UE. Detailed implementation
[0036] As used herein, "A or B" may mean "only A", "only B", or "both A and B". That is, "A or B" may be interpreted herein as "A and / or B". For example, "A, B, or C" may mean "only A", "only B", "only C", or "any combination of A, B, and C".
[0037] As used herein, the slash ( / ) or comma (,) may mean "and / or". For example, "A / B" may mean "A and / or B". Thus, "A / B" may include "only A", "only B", or "both A and B". For example, "A, B, C" may mean "A, B, or C".
[0038] As used herein, "at least one of A and B" may mean "only A", "only B", or "both A and B". In addition, as used herein, "at least one of A or B" or "at least one of A and / or B" may be equivalently interpreted as "at least one of A and B".
[0039] As used herein, "at least one of A, B, and C" may mean "only A", "only B", "only C", or "any combination of A, B, and C". In addition, "at least one of A, B, or C" or "at least one of A, B, and / or C" may mean "at least one of A, B, and C".
[0040] As used herein, parentheses can mean "for example". For example, the expression "control information (PDCCH)" can mean that the PDCCH is presented as an example of control information. That is, the control information is not limited to the PDCCH, but the PDCCH is presented as an example of control information. In addition, the expression "control information (i.e., PDCCH)" can also mean that the PDCCH is presented as an example of control information.
[0041] Technical features described separately in one drawing can be implemented separately or can be implemented simultaneously.
[0042] Hereinafter, examples of a communication system to which the present disclosure is applied will be described.
[0043] The various descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein can be applied to, but are not limited to, various fields that require wireless communication / connection (e.g., 5G) between devices.
[0044] Hereinafter, specific examples will be illustrated with reference to the drawings. In the following drawings / descriptions, unless otherwise specified, the same reference numerals may refer to the same or corresponding hardware blocks, software blocks, or functional blocks.
[0045] Figure 1 A communication system 1 to which the present disclosure is applied is illustrated.
[0046] Refer to Figure 1, the communication system 1 applied to the present disclosure includes a wireless device, a base station (BS), and a network. Here, the wireless device refers to a device that performs communication using radio access technology (e.g., 5G new radio access technology (NR) or long-term evolution (LTE)) and can be referred to as a communication / wireless / 5G device. The wireless device may include, but is not limited to, a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a household appliance 100e, an Internet of Things (IoT) device 100f, and an AI device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous vehicle, a vehicle capable of vehicle-to-vehicle communication, etc. Here, the vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). The XR device may include an augmented reality (AR) / virtual reality (VR) / mixed reality (MR) device and may be configured as a head-mounted device (HMD), an in-vehicle head-up display (HUD), a TV, a smart phone, a computer, a wearable device, a household appliance, a digital sign, a vehicle, a robot, etc. The handheld device may include a smart phone, a smart tablet, a wearable device (e.g., a smart watch or smart glasses), and a computer (e.g., a laptop). The household appliance may include a TV, a refrigerator, a washing machine, etc. The IoT device may include a sensor, a smart meter, etc. For example, the base station and the network may be configured as a wireless device, and a specific wireless device 200a may operate as a base station / network node for other wireless devices.
[0047] Here, the wireless communication technologies implemented in the wireless devices of the present disclosure may include Narrowband Internet of Things (NB-IoT) for low-power communication, as well as LTE, NR, and 6G. At this time, for example, the NB-IoT technology may be an example of a low-power wide area network (LPWAN) technology, and may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above names. Additionally or alternatively, the wireless communication technologies implemented in the wireless devices of the present disclosure may perform communication based on the LTE-M technology. In this case, as an example, the LTE-M technology may be an example of an LPWAN technology, and may be referred to by various names such as enhanced machine type communication (eMTC). For example, the LTE-M technology may be implemented by at least any one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-bandwidth-limited), 5) LTE-MTC, 6) LTE machine type communication, and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, the wireless communication technologies implemented in the wireless devices of the present disclosure may include at least one of ZigBee, Bluetooth, and LPWAN considering low-power communication, and is not limited to the above names. For example, the ZigBee technology may create a personal area network (PAN) related to small / low-power digital communication based on various standards such as IEEE802.15.4, and may be referred to by various names.
[0048] Wireless devices 100a to 100f may be connected to network 300 through base station 200. Artificial intelligence (AI) technology may be applied to wireless devices 100a to 100f, and wireless devices 100a to 100f may be connected to AI server 400 through network 300. Network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Wireless devices 100a to 100f may communicate with each other via base station 200 / network 300, and may also perform direct communication (e.g., sidelink communication) with each other without going through the base station / network. For example, vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). In addition, IoT devices (e.g., sensors) may communicate directly with another IoT device (e.g., sensor) or another wireless device 100a to 100f.
[0049] Wireless communications / connections 150a, 150b, and 150c can be established between wireless devices 100a to 100f and a base station 200, as well as between base stations. Here, the wireless communications / connections can be established by various radio access technologies (e.g., 5G NR), such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication), and inter-base station communication 150c (e.g., relay or integrated access backhaul (IAB)). The wireless devices and the base station / wireless devices, as well as the base station and the base station, can send / receive radio signals to / from each other via the wireless communications / connections 150a, 150b, and 150c. For example, the wireless communications / connections 150a, 150b, and 150c can send / receive signals via various physical channels. To this end, at least some of various configuration information setting processes, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and resource allocation processes can be performed based on various proposals of the present disclosure.
[0050] Figure 2 Illustrates a wireless device applicable to the present disclosure.
[0051] Referring to Figure 2 , the first wireless device 100 and the second wireless device 200 can send and receive wireless signals via various radio access technologies (e.g., LTE and NR). Here, the first wireless device 100 and the second wireless device 200 can correspond to wireless device 100x and base station 200 of Figure 1 respectively and / or can correspond to wireless device 100x and wireless device 100x of Figure 1 respectively.
[0052] The first wireless device 100 includes at least one processor 102 and at least one memory 104, and may further include at least one transceiver 106 and / or at least one antenna 108. The processor 102 may be configured to control the memory 104 and / or the transceiver 106, and implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then may transmit radio signals including the first information / signals through the transceiver 106. Additionally, the processor 102 may receive radio signals including second information / signals through the transceiver 106, and may store the information obtained from the signal processing of the second information / signals in the memory 104. The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions to execute some or all of the processes controlled by the processor 102 or to execute the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement radio communication technologies (such as LTE or NR). The transceiver 106 may be connected to the processor 102 and may transmit and / or receive radio signals via at least one antenna 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be replaced by a radio frequency (RF) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.
[0053] The second wireless device 200 includes at least one processor 202 and at least one memory 204, and may also include at least one transceiver 206 and / or at least one antenna 208. The processor 202 may be configured to control the memory 204 and / or the transceiver 206, and implement the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then may transmit radio signals including the third information / signals through the transceiver 206. Additionally, the processor 202 may receive radio signals including fourth information / signals through the transceiver 206, and may store the information obtained from the signal processing of the fourth information / signals in the memory 204. The memory 204 may be connected to the processor 202, and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions to execute some or all of the processes controlled by the processor 202 or to execute the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement radio communication technologies (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202, and may transmit and / or receive radio signals via at least one antenna 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be replaced by an RF unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.
[0054] In the following, the hardware components of wireless devices 100 and 200 are described in detail. At least one protocol layer can be, but is not limited to, implemented by at least one processor 102 and 202. For example, at least one processor 102 and 202 can implement at least one layer (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP layers). At least one processor 102 and 202 can generate at least one protocol data unit (PDU) and / or at least one service data unit (SDU) according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. At least one processor 102 and 202 can generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein. At least one processor 102 and 202 can generate signals (e.g., baseband signals) including PDU, SDU, messages, control information, data, or information according to the functions, processes, proposals, and / or methods disclosed herein, and can provide the signals to at least one transceiver 106 and 206. At least one processor 102 and 202 can receive signals (e.g., baseband signals) from at least one transceiver 106 and 206, and can obtain PDU, SDU, messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein.
[0055] At least one processor 102 and 202 can be referred to as a controller, microcontroller, microprocessor, or microcomputer. At least one processor 102 and 202 can be implemented by hardware, firmware, software, or a combination thereof. For example, at least one application specific integrated circuit (ASIC), at least one digital signal processor (DSP), at least one digital signal processing device (DSPD), at least one programmable logic device (PLD), or at least one field programmable gate array (FPGA) can be included in at least one processor 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein can be implemented using firmware or software, and the firmware or software can be configured to include modules, programs, functions, etc. The firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein can be included in at least one processor 102 and 202, or can be stored in at least one memory 104 and 204 and can be executed by at least one processor 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operation flowcharts disclosed herein can be implemented using firmware or software in the form of code, instructions, and / or instruction sets.
[0056] At least one of memories 104 and 204 may be connected to at least one of processors 102 and 202, and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. At least one of memories 104 and 204 may be configured as ROM, RAM, EPROM, flash memory, hard disk drive, register, cache memory, computer-readable storage medium, and / or a combination thereof. At least one of memories 104 and 204 may be provided inside and / or outside at least one of processors 102 and 202. Additionally, at least one of memories 104 and 204 may be connected to at least one of processors 102 and 202 by various techniques such as wired or wireless connections.
[0057] At least one of transceivers 106 and 206 may transmit user data, control information, radio signals / channels, etc. mentioned in the methods and / or flowcharts of operations disclosed herein to at least one different device. At least one of transceivers 106 and 206 may receive user data, control information, radio signals / channels, etc. mentioned in the descriptions, functions, processes, proposals, methods, and / or flowcharts of operations disclosed herein from at least one different device. For example, at least one of transceivers 106 and 206 may be connected to at least one of processors 102 and 202, and may transmit and receive radio signals. For example, at least one of processors 102 and 202 may control at least one of transceivers 106 and 206 to transmit user data, control information, or radio signals to at least one different device. Additionally, at least one of processors 102 and 202 may control at least one of transceivers 106 and 206 to receive user data, control information, or radio signals from at least one different device. At least one of transceivers 106 and 206 may be connected to at least one of antennas 108 and 208, and may be configured to transmit or receive user data, control information, radio signals / channels, etc. mentioned in the descriptions, functions, processes, proposals, methods, and / or flowcharts of operations disclosed herein through at least one of antennas 108 and 208. In this document, at least one antenna may be multiple physical antennas or may be multiple logical antennas (e.g., antenna ports). At least one of transceivers 106 and 206 may convert the received radio signals / channels from RF band signals into baseband signals to facilitate the use of at least one of processors 102 and 202 to process the received user data, control information, radio signals / channels, etc. At least one of transceivers 106 and 206 may convert the user data, control information, radio signals / channels, etc. processed using at least one of processors 102 and 202 from baseband signals into RF band signals. To this end, at least one of transceivers 106 and 206 may include (analog) oscillators and / or filters.
[0058] Figure 3 A signal processing circuit for transmitting signals is illustrated.
[0059] Referring to Figure 3 , the signal processing circuit 1000 may include a scrambler 1010, a modulator 1020, a layer mapper 1030, a precoder 1040, a resource mapper 1050, and a signal generator 1060. Referring to Figure 3 The illustrated operations / functions may be performed by, but are not limited to Figure 2 processors 102 and 202 and / or transceivers 106 and 206. Figure 3 The illustrated hardware elements may be configured in Figure 2 processors 102 and 202 and / or transceivers 106 and 206. For example, blocks 1010 to 1060 may be configured in Figure 2 processors 102 and 202. Alternatively, blocks 1010 to 1050 may be configured in Figure 2 processors 102 and 202, and block 1060 may be configured in Figure 2 transceivers 106 and 206.
[0060] A codeword may be converted into a radio signal via Figure 3 the signal processing circuit 1000. Here, a codeword is a coded bit sequence of an information block. The information block may include a transport block (e.g., a UL-SCH transport block or a DL-SCH transport block). The radio signal may be transmitted through various physical channels (e.g., PUSCH or PDSCH).
[0061] Specifically, a codeword may be converted into a scrambled bit sequence by the scrambler 1010. The scrambling sequence for scrambling may be generated based on an initialization value, and the initialization value may include ID information about the wireless device. The scrambled bit sequence may be modulated into a sequence of modulation symbols by the modulator 1020. The modulation scheme may include π / 2-binary phase shift keying (π / 2-BPSK), m-phase shift keying (m-PSK), m-quadrature amplitude modulation (m-QAM), etc. The sequence of complex modulation symbols may be mapped to at least one transmission layer by the layer mapper 1030. The modulation symbols of each transmission layer may be mapped (precoded) to corresponding antenna ports by the precoder 1040. The output z from the precoder 1040 may be obtained by multiplying the output y from the layer mapper 1030 by an N*M precoding matrix W, where N is the number of antenna ports and M is the number of transmission layers. Here, the precoder 1040 may perform precoding after performing transform precoding (e.g., DFT transform) on the complex-valued modulation symbols. Alternatively, the precoder 1040 may perform precoding without performing transform precoding.
[0062] The resource mapper 1050 may map the modulated symbols of each antenna port to time-frequency resources. The time-frequency resources may include a plurality of symbols in the time domain (e.g., CP-OFDMA symbols or DFT-s-OFDMA symbols), and may include a plurality of subcarriers in the frequency domain. The signal generator 1060 may generate a radio signal from the mapped modulated symbols, and the generated radio signal may be transmitted to another device through each antenna. To this end, the signal generator 1060 may include an inverse fast Fourier transform (IFFT) module, a cyclic prefix (CP) inserter, a digital-to-analog converter (DAC), an upconverter, etc.
[0063] It may be performed in the reverse order of the signal processing procedures 1010 to 1060 Figure 3 in the wireless device for the received signal. For example, a wireless device (e.g., Figure 2 100 and 200 in) may receive a radio signal from the outside through an antenna port / transceiver. The received radio signal may be converted into a baseband signal by a signal reconstructor. To this end, the signal reconstructor may include a downconverter, an analog-to-digital converter (ADC), a CP remover, and a fast Fourier transform (FFT) module. The baseband signal may be reconstructed into a codeword through resource demapping, post-coding, demodulation, and descrambling. The codeword may be reconstructed into an original information block through decoding. Therefore, the signal processing circuit (not shown) for the received signal may include a signal reconstructor, a resource demapper, a post-encoder, a demodulator, a descrambler, and a decoder.
[0064] Figure 4 Another example of a wireless device to which the present disclosure is applied is illustrated. The wireless device may be configured in various forms according to use cases / services.
[0065] Referring to Figure 4 the wireless devices 100 and 200 may correspond to Figure 2 the wireless devices 100 and 200 of, and may include various elements, components, units, and / or modules. For example, the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit may include a communication circuit 112 and one or more transceivers 114. For example, the communication circuit 112 may include Figure 2 at least one processor 102 and 202 and / or at least one memory 104 and 204 of. For example, one or more transceivers 114 may include Figure 2At least one transceiver 106 and 206 and / or at least one antenna 108 and 208. The control unit 120 is electrically connected to the communication unit 110, the memory unit 130, and the additional component 140, and controls the overall operation of the wireless device. For example, the control unit 120 may control the electrical / mechanical operations of the wireless device based on programs / codes / commands / information stored in the memory unit 130. Additionally, the control unit 120 may send the information stored in the memory unit 130 to the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface, or store the information received from the outside (e.g., other communication devices) via the communication unit 110 through a wireless / wired interface in the memory unit 130.
[0066] The additional component 140 may be configured in various ways according to the type of the wireless device. For example, the additional component 140 may include at least one of a power unit / battery, an input / output (I / O) unit, a driving unit, and a computing unit. The wireless device may be configured as but not limited to a robot ( Figure 1 of 100a), a vehicle ( Figure 1 of 100b-1 or 100b-2), an XR device ( Figure 1 of 100c), a handheld device ( Figure 1 of 100d), a household appliance ( Figure 1 of 100e), an IoT device ( Figure 1 of 100f), a digital broadcast terminal, a holographic device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device ( Figure 1 of 400), a base station ( Figure 1 of 200), a network node, etc. According to the use case / service, the wireless device may be mobile or may be used in a fixed place.
[0067] In Figure 4In [the context], various elements, components, units, and / or modules in wireless devices 100 and 200 can all be connected to each other through a wired interface, or at least a part of them can be wirelessly connected through communication unit 110. For example, in wireless devices 100 and 200, control unit 120 and communication unit 110 can be connected via a cable, and control unit 120 and the first units (e.g., 130 and 140) can be wirelessly connected through communication unit 110. Additionally, each element, component, unit, and / or module in wireless devices 100 and 200 can also include at least one element. For example, control unit 120 can include at least one set of processors. For example, control unit 120 can be configured to be a set including a communication control processor, an application processor, an electronic control unit (ECU), a graphics processing processor, and a memory control processor, etc. In another example, memory unit 130 can include a random access memory (RAM), a dynamic RAM (DRAM), a read-only memory (ROM), a flash memory, a volatile memory, a non-volatile memory, and / or a combination thereof.
[0068] Next, an exemplary configuration will be described in detail with reference to the accompanying drawings. Figure 4 of [the device].
[0069] Figure 5 An example of a handheld device applied to the present disclosure is illustrated. The handheld device can include a smart phone, a smart tablet, a wearable device (e.g., a smart watch or smart glasses), or a portable computer (e.g., a notebook). The handheld device can be referred to as a mobile station (MS), a user terminal (UT), a mobile subscriber station (MSS), a subscriber station (SS), an advanced mobile station (AMS), or a wireless terminal (WT).
[0070] Referring to Figure 5 , the handheld device 100 can include an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140a, an interface unit 140b, and an input / output unit 140c. Antenna unit 108 can be configured as a part of communication unit 110. Blocks 110 to 130 / 140a to 140c respectively correspond to Figure 4 blocks 110 to 130 / 140 of [the device].
[0071] The communication unit 110 can send and receive signals (e.g., data, control signals, etc.) to and from other wireless devices or base stations. The control unit 120 can control the respective components of the handheld device 100 to perform various operations. The control unit 120 can include an application processor (AP). The memory unit 130 can store data / parameters / programs / codes / commands required to drive the handheld device 100. In addition, the memory unit 130 can store input / output data / information. The power supply unit 140a can supply power to the handheld device 100 and can include a wired / wireless charging circuit, a battery, etc. The interface unit 140b can support the connection between the handheld device 100 and different devices. The interface unit 140b can include various ports for connecting to external devices (e.g., audio input / output ports and video input / output ports). The input / output unit 140c can receive or output image information / signals, audio information / signals, data, and / or information input from the user. The input / output unit 140c can include a camera, a microphone, a user input unit, a display unit 140d, a speaker, and / or a haptic module.
[0072] For example, in data communication, the input / output unit 140c can obtain information / signals input from the user (e.g., touch, text, voice, image, or video), and the obtained information / signals can be stored in the memory unit 130. The communication unit 110 can convert the information / signals stored in the memory unit into a radio signal and can directly send the converted radio signal to different wireless devices or to a base station. Additionally, the communication unit 110 can receive a radio signal from different wireless devices or a base station and can reconstruct the received radio signal into the original information / signals. The reconstructed information / signals can be stored in the memory unit 130 and can be output in various forms (e.g., text, voice, image, video, or haptic form) through the input / output unit 140c.
[0073] Figure 6 Vehicles or autonomous driving vehicles applicable to the present disclosure are illustrated. The vehicle or autonomous driving vehicle can be configured as a mobile robot, an automobile, a train, a manned / unmanned aerial vehicle (AV), a ship, etc.
[0074] Referring to Figure 6 , the vehicle or autonomous driving vehicle 100 can include an antenna unit 108, a communication unit 110, a control unit 120, a driving unit 140a, a power supply unit 140b, a sensor unit 140c, and an autonomous driving unit 140d. The antenna unit 108 can be configured as part of the communication unit 110. Blocks 110 / 130 / 140a to 140d respectively correspond to Figure 4 blocks 110 / 130 / 140 of
[0075] The communication unit 110 may send and receive signals (e.g., data signals and control signals) to and from external devices such as different vehicles, base stations (e.g., base stations, roadside units, etc.), and servers. The control unit 120 may control elements of the vehicle or autonomous driving vehicle 100 to perform various operations. The control unit 120 may include an electronic control unit (ECU). The driving unit 140a may cause the vehicle or autonomous driving vehicle 100 to travel on the ground. The driving unit 140a may include an engine, a motor, a transmission system, wheels, brakes, a steering device, etc. The power supply unit 140b may supply power to the vehicle or autonomous driving vehicle 100, and may include a wired / wireless charging circuit, a battery, etc. The sensor unit 140c may obtain vehicle conditions, environmental information, user information, etc. The sensor unit 140c may include an inertial measurement unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward / backward vision sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, a lighting sensor, a pedal position sensor, etc. The autonomous driving unit 140d may implement technologies for maintaining a driving lane, technologies for automatically adjusting speed (e.g., adaptive cruise control), technologies for autonomously driving along a set path, technologies for automatically setting a path and driving when a destination is set, etc.
[0076] For example, the communication unit 110 may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140d may generate an autonomous driving path and a driving plan from the obtained data. The control unit 120 may control the driving unit 140a to cause the vehicle or autonomous driving vehicle 100 to move along the autonomous driving path according to the driving plan (e.g., speed / direction control). During autonomous driving, the communication unit 110 may obtain updated traffic condition data from an external server non-periodically / periodically, and may obtain surrounding traffic condition data from adjacent vehicles. In addition, during autonomous driving, the sensor unit 140c may obtain vehicle conditions and environmental information. The autonomous driving unit 140d may update the autonomous driving path and the driving plan based on the newly obtained data / information. The communication unit 110 may send information about the vehicle position, the autonomous driving path, the driving plan, etc. to an external server. The external server may use AI technology, etc. to predict traffic condition data in advance based on the information collected from the vehicle or autonomous driving vehicle, and provide the predicted traffic condition data to the vehicle or autonomous driving vehicle.
[0077] Figure 7 A vehicle to which the present disclosure is applied is illustrated. The vehicle may be implemented as a transportation vehicle, a train, an aircraft, a ship, etc.
[0078] Reference Figure 7 , vehicle 100 may include a communication unit 110, a control unit 120, a memory unit 130, an input / output unit 140a, and a positioning unit 140b. Here, blocks 110 to 130 / 140a to 140b respectively correspond to Figure 4 blocks 110 to 130 / 140 thereof.
[0079] The communication unit 110 may transmit / receive signals (e.g., data, control signals, etc.) to / from other vehicles or external devices such as base stations. The control unit 120 may control components of the vehicle 100 to perform various operations. The memory unit 130 may store data / parameters / programs / codes / commands that support various functions of the vehicle 100. The input / output unit 140a may output AR / VR objects based on information in the memory unit 130. The input / output unit 140a may include a HUD. The positioning unit 140b may acquire the position information of the vehicle 100. The position information may include the absolute position information of the vehicle 100, the position information within the driving route, the acceleration information, the position information of adjacent vehicles, etc. The positioning unit 140b may include GPS and various sensors.
[0080] For example, the communication unit 110 of the vehicle 100 may receive map information, traffic information, etc. from an external server and store them in the memory unit 130. The positioning unit 140b may obtain the vehicle position information through GPS and various sensors and store it in the memory unit 130. The control unit 120 may generate virtual objects based on the map information, traffic information, vehicle position information, etc., and the input / output unit 140a may display the generated virtual objects on the windows (1410 and 1420) inside the vehicle. Additionally, the control unit 120 may determine whether the vehicle 100 is operating normally within the driving route based on the vehicle position information. When the vehicle 100 abnormally deviates from the driving route, the control unit 120 may display a warning on the windshield of the vehicle through the input / output unit 140a. Furthermore, the control unit 120 may broadcast a warning message about abnormal driving to surrounding vehicles through the communication unit 110. Depending on the situation, the control unit 120 may send the position information of the vehicle and information about driving / vehicle abnormalities to relevant organizations through the communication unit 110.
[0081] Figure 8 An XR device applied to the present disclosure is illustrated. The XR device may be implemented as an HMD, a head-up display (HUD) provided in a vehicle, a television, a smart phone, a computer, a wearable device, a household appliance, a digital signage, a vehicle, a robot, etc.
[0082] Reference Figure 8, the XR device 100a may include a communication unit 110, a control unit 120, a memory unit 130, an input / output unit 140a, a sensor unit 140b, and a power supply unit 140c. Herein, blocks 110 to 130 / 140a to 140c correspond to Figure 4 the blocks 110 to 130 / 140 in
[0083] The communication unit 110 may send / receive signals (e.g., media data, control signals, etc.) to / from external devices such as other wireless devices, portable devices, or media servers. The media data may include video, images, sounds, etc. The control unit 120 may control the components of the XR device 100a to perform various operations. For example, the control unit 120 may be configured to control and / or execute processes such as video / image acquisition, (video / image) encoding, and metadata generation and processing. The memory unit 130 may store data / parameters / programs / codes / commands required to drive the XR device 100a / create XR objects. The input / output unit 140a may obtain control information, data, etc. from the outside and may output the generated XR objects. The input / output unit 140a may include a camera, a microphone, a user input unit, a display unit, a speaker, and / or a haptic module. The sensor unit 140b may obtain XR device status, surrounding environment information, user information, etc. The sensor unit 140b may include a proximity sensor, a lighting sensor, an acceleration sensor, a magnetic sensor, a gyroscope sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, an optical sensor, a microphone, and / or a radar. The power supply unit 140c supplies power to the XR device 100a and may include a wired / wireless charging circuit, a battery, etc.
[0084] For example, the memory unit 130 of the XR device 100a may include information (such as data, etc.) required to generate XR objects (such as AR / VR / MR objects). The input / output unit 140a may obtain a command to operate the XR device 100a from the user, and the control unit 120 may drive the XR device 100a according to the driving command of the user. For example, when the user wants to watch a movie or news through the XR device 100a, the control unit 120 sends content request information to another device (such as the mobile device 100b) or may send it to the media server through the communication unit 110. The communication unit 110 may download / stream content such as movies and news from another device (such as the portable device 100b) or the media server to the memory unit 130. The control unit 120 controls and / or executes processes such as video / image acquisition, (video / image) encoding, and metadata generation / processing for the content, and acquires it through the input / output unit 140a / sensor unit 140b. The XR object may be generated / output based on information about a surrounding space or a real object.
[0085] In addition, the XR device 100a is wirelessly connected to the portable device 100b through the communication unit 110, and the operation of the XR device 100a may be controlled by the portable device 100b. For example, the portable device 100b may operate as a controller for the XR device 100a. To this end, the XR device 100a may obtain the 3D position information of the portable device 100b, and then generate and output an XR object corresponding to the portable device 100b.
[0086] Figure 9 Robots applied to the present disclosure are illustrated. According to the use or field of use, robots can be classified into industrial, medical, household, military, etc.
[0087] Refer to Figure 9 , the robot 100 may include a communication unit 110, a control unit 120, a memory unit 130, an input / output unit 140a, a sensor unit 140b, and a driving unit 140c. Herein, blocks 110 to 130 / 140a to 140c correspond to Figure 4 blocks 110 to 130 / 140 therein.
[0088] The communication unit 110 can send / receive signals (e.g., driving information, control signals, etc.) to / from external devices such as other wireless devices, other robots, or a control server. The control unit 120 can perform various operations by controlling the components of the robot 100. The memory unit 130 can store data / parameters / programs / codes / commands that support various functions of the robot 100. The input / output unit 140a can obtain information from outside the robot 100 and can output information to the outside of the robot 100. The input / output unit 140a can include a camera, a microphone, a user input unit, a display unit, a speaker, and / or a haptic module, etc. The sensor unit 140b can obtain internal information of the robot 100, surrounding environment information, user information, etc. The sensor unit can include a proximity sensor, an illumination sensor, an acceleration sensor, a magnetic sensor, a gyro sensor, an inertial sensor, an IR sensor, a fingerprint recognition sensor, an ultrasonic sensor, an optical sensor, a microphone, a radar, etc. The driving unit 140c can perform various physical operations such as moving the joints of the robot. Additionally, the driving unit 140c can make the robot 100 travel on the ground or fly in the air. The driving unit 140c can include an actuator, a motor, a wheel, a brake, a propeller, etc.
[0089] Figure 10 An AI device applied to the present disclosure is illustrated. The AI device can be implemented as a fixed device or a mobile device (e.g., a TV, a projector, a smart phone, a PC, a laptop computer, a digital broadcast terminal, a tablet PC, a wearable device, a set-top box, a radio, a washing machine, a refrigerator, a digital signage, a robot, and a vehicle).
[0090] Referring to Figure 10 , the AI device 100 can include a communication unit 110, a control unit 120, a memory unit 130, an input unit 140a, an output unit 140b, a learning processor unit 140c, and a sensing unit 140d. Blocks 110 to 130 / 140a to 140d respectively correspond to Figure 4 blocks 110 to 130 / 140 of
[0091] The communication unit 110 can send and receive wired or wireless signals (e.g., sensor information, user input, learning mode, control signals, etc.) to / from external devices, different AI devices (e.g., Figure 1 100x, 200, or 400 in Figure 1 ) or an AI server (e.g.,
[0092] The control unit 120 may determine at least one executable operation of the AI device 100 based on information determined or generated using a data analysis algorithm or a machine learning algorithm. The control unit 120 may control the components of the AI device 100 to perform the determined operations. For example, the control unit 120 may request, retrieve, receive, or utilize data from the learning processor unit 140c or the memory unit 130, and may control the components of the AI device 100 to perform a prediction operation or an operation determined to be preferred among at least one executable operation. The control unit 120 may collect historical information including details about the operation of the AI device 100 or user feedback on the operation, and may store the historical information in the memory unit 130 or the learning processor unit 140c, or may send the historical information to an external device such as an AI server ( Figure 1 like 400 in). The collected historical information may be used to update the learning model.
[0093] The memory unit 130 may store data for supporting various functions of the AI device 100. For example, the memory unit 130 may store data obtained from the input unit 140a, data obtained from the communication unit 110, output data from the learning processor unit 140c, and data obtained from the sensing unit 140. In addition, the memory unit 130 may store control information and / or software code required for the operation / execution of the control unit 120.
[0094] The input unit 140a may obtain various types of data from outside the AI device 100. For example, the input unit 140a may obtain learning data for model learning and input data for applying the learning model. The input unit 140a may include a camera, a microphone, and / or a user input unit. The output unit 140b may generate visual, auditory, or tactile outputs. The output unit 140b may include a display unit, a speaker, and / or a tactile module. The sensing unit 140 may use various sensors to obtain at least one of internal information about the AI device 100, environmental information about the AI device 100, and user information. The sensing unit 140 may include a proximity sensor, a lighting sensor, an acceleration sensor, a magnetic sensor, a gyroscope sensor, an inertial sensor, an RGB sensor, an IR sensor, a fingerprint sensor, an ultrasonic sensor, an optical sensor, a microphone, and / or a radar.
[0095] The learning processor unit 140c may use the learning data to train a model including an artificial neural network. The learning processor unit 140c may communicate with an AI server ( Figure 1The learning processor unit of 400) in performs AI processing together. The learning processor unit 140c can process the information received from an external device through the communication unit 110 and / or the information stored in the memory unit 130. In addition, the output value from the learning processor unit 140c can be sent to an external device through the communication unit 110 and / or can be stored in the memory unit 130.
[0096] Figure 11 FIG. shows a wireless communication system to which the present disclosure can be applied. The wireless communication system may be referred to as an evolved UMTS terrestrial radio access network (E-UTRAN) or a Long Term Evolution (LTE) / LTE-A system.
[0097] The E-UTRAN includes at least one base station (BS) 20 that provides a control plane and a user plane to a user equipment (UE) 10. The UE 10 can be fixed or mobile and may be referred to by another term such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), a wireless device, a terminal, etc. The BS 20 is generally a fixed station that communicates with the UE 10 and may be referred to by another term such as an evolved Node B (eNB), a base transceiver system (BTS), an access point, etc.
[0098] The BSs 20 are interconnected by means of an X2 interface. The BSs 20 are also connected to an evolved packet core (EPC) 30 via an S1 interface, more specifically, connected to a mobility management entity (MME) via S1-MME and connected to a serving gateway (S-GW) via S1-U.
[0099] The EPC 30 includes an MME, an S-GW, and a packet data network gateway (P-GW). The MME has access information of the UE or capability information of the UE, and this information is generally used for mobility management of the UE. The S-GW is a gateway with the E-UTRAN as an endpoint. The P-GW is a gateway with a PDN as an endpoint.
[0100] The layers of the radio interface protocol between the UE and the network can be divided into a first layer (L1), a second layer (L2), and a third layer (L3) based on the lower three layers of the well-known Open Systems Interconnection (OSI) model in a communication system. Among them, the physical (PHY) layer belonging to the first layer provides an information transmission service by using a physical channel, and the radio resource control (RRC) layer belonging to the third layer is used to control radio resources between the UE and the network. To this end, the RRC layer exchanges RRC messages between the UE and the BS.
[0101] Figure 12 FIG. is a diagram showing a radio protocol architecture for a user plane. Figure 13It is a diagram showing the radio protocol architecture for the control plane. The user plane is a protocol stack for user data transmission. The control plane is a protocol stack for control signal transmission.
[0102] Referring to Figure 12 and Figure 13 , the PHY layer provides an information transfer service to the upper layer through the physical channel. The PHY layer is connected to the Medium Access Control (MAC) layer, which is the upper layer of the PHY layer, through the transport channel. Data is transferred between the MAC layer and the PHY layer through the transport channel. The transport channel is classified according to the way of transferring data through the radio interface and the characteristics of the data.
[0103] Data moves between different PHY layers (i.e., the PHY layer of the transmitter and the PHY layer of the receiver) through the physical channel. The physical channel can be modulated according to the Orthogonal Frequency Division Multiplexing (OFDM) scheme and uses time and frequency as radio resources.
[0104] The functions of the MAC layer include the mapping between the logical channel and the transport channel and the multiplexing and demultiplexing into transport blocks provided on the transport channel for the MAC service data unit (SDU) belonging to the logical channel through the physical channel. The MAC layer provides services to the Radio Link Control (RLC) layer through the logical channel.
[0105] The functions of the RLC layer include the concatenation, segmentation, and reassembly of the RLC SDU. To ensure various types of Quality of Service (QoS) required by the radio bearer (RB), the RLC layer provides three types of operation modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). AM RLC provides error correction through Automatic Repeat reQuest (ARQ).
[0106] The RRC layer is only defined on the control plane. The RRC layer is related to the configuration, reconfiguration, and release of the radio bearer and is responsible for the control of the logical channel, transport channel, and PHY channel. RB represents the logical route provided by the first layer (PHY layer) and the second layer (MAC layer, RLC layer, and PDCP layer) to transfer data between the UE and the network.
[0107] The functions of the Packet Data Convergence Protocol (PDCP) layer on the user plane include the transfer of user data and header compression and encryption. The functions of the PDCP layer on the control plane also include the transfer and encryption / integrity protection of control plane data.
[0108] The configuration of an RB means the process of defining the characteristics of radio protocol layers and channels to provide specific services and configuring each detailed parameter and operation method. An RB can be classified into two types: a signaling RB (SRB) and a data RB (DRB). The SRB is used as a channel through which RRC messages are sent on the control plane, and the DRB is used as a channel through which user data is sent on the user plane.
[0109] If an RRC connection is established between the RRC layer of the UE and the RRC layer of the E-UTRAN, the UE is in the RRC connected state. Otherwise, the UE is in the RRC idle state.
[0110] The downlink transport channels through which data is sent from the network to the UE include the broadcast channel (BCH) through which system information is sent and the downlink shared channel (SCH) through which user traffic or control messages are sent. Traffic or control messages for downlink multicast or broadcast services can be sent through the downlink SCH or can be sent through an additional downlink multicast channel (MCH). In addition, the uplink transport channels through which data is sent from the UE to the network include the random access channel (RACH) through which initial control messages are sent and the uplink shared channel (SCH) through which user traffic or control messages are sent.
[0111] The logical channels located above the transport channels and mapped to the transport channels include the broadcast control channel (BCCH), the paging control channel (PCCH), the common control channel (CCCH), the multicast control channel (MCCH), and the multicast traffic channel (MTCH).
[0112] The physical channel includes multiple OFDM symbols in the time domain and multiple subcarriers in the frequency domain. A subframe includes multiple OFDM symbols in the time domain. An RB is a resource allocation unit and includes multiple OFDM symbols and multiple subcarriers. In addition, each subframe can use specific subcarriers of a specific OFDM symbol (e.g., the first OFDM symbol) of the corresponding subframe for the physical downlink control channel (PDCCH) (i.e., the L1 / L2 control channel). The transmission time interval (TTI) is the unit time for transmission (e.g., a subframe or a slot).
[0113] Hereinafter, the new radio access technology (new RAT) or new radio (NR) will be described.
[0114] As communication devices increasingly require greater communication capacity, improved mobile broadband communication relative to existing radio access technologies (RATs) is needed. In addition, massive machine type communication (MTC), which provides many different services by connecting multiple devices and objects, is also one of the main issues to be considered in next-generation communication. In addition, the design of communication systems considering services or terminals sensitive to reliability or latency has been discussed. The introduction of next-generation radio access technologies that consider enhanced mobile broadband communication, massive MTC, ultra-reliable and low-latency communication (URLLC), etc. has been discussed. In the present disclosure, for ease of description, this new technology will be referred to as the new radio access technology (new RAT or NR).
[0115] Figure 14 Another wireless communication system to which the present disclosure can be applied is shown.
[0116] Specifically, Figure 14 A system architecture based on a 5G new radio access technology (NR) system is shown. Entities used in the 5G NR system (hereinafter, simply referred to as "NR") can absorb some or all of the functions of the entities (e.g., eNB, MME, S-GW) introduced in Figure 1 . Entities used in the NR system can be identified by the name "NG" to distinguish them from LTE.
[0117] Referring to Figure 14 , the wireless communication system includes one or more UEs 11, a next-generation RAN (NG-RAN), and a 5th generation core network (5GC). The NG-RAN consists of at least one NG-RAN node. The NG-RAN node is an entity corresponding to the BS20 of Figure 11 . The NG-RAN node consists of at least one gNB 21 and / or at least one ng-eNB 22. The gNB 21 provides NR user plane and control plane protocol terminations to the UE 11. The ng-eNB 22 provides E-UTRA user plane and control plane protocol terminations to the UE 11.
[0118] The 5GC includes an access and mobility management function (AMF), a user plane function (UPF), and a session management function (SMF). The AMF hosts functions such as non-access stratum (NAS) security, idle state mobility handling, etc. The AMF is an entity that includes conventional MMF functions. The UPF hosts functions such as mobility anchoring, protocol data unit (PDU) handling, etc. The UPF is an entity that includes conventional S-GW functions. The SMF hosts functions such as UE Internet protocol (IP) address allocation, PDU session control, etc.
[0119] The gNB and ng-eNB are interconnected via the Xn interface. The gNB and ng-eNB are also connected to the 5GC via the NG interface. More specifically, the gNB and ng-eNB are connected to the AMF via the NG-C interface and to the UPF via the NG-U interface.
[0120] Figure 15 An example of the functional division between the NG-RAN and the 5GC is illustrated.
[0121] Refer to Figure 15 , the gNB can provide functions such as inter-cell radio resource management (inter-cell RRM), radio bearer management (RB control), connection mobility control, radio access control, measurement configuration and regulation, dynamic resource allocation, etc. The AMF can provide functions such as NAS security, idle state mobility handling, etc. The UPF can provide functions such as mobility anchoring, PDU processing, etc. The SMF can provide functions such as UE IP address allocation, PDU session control, etc.
[0122] Figure 16 An example of the frame structure that can be applied in NR is illustrated.
[0123] Refer to Figure 16 , the frame can be configured to consist of 10 milliseconds (ms) and includes 10 subframes, each subframe being configured as 1 ms.
[0124] In NR, uplink transmission and downlink transmission can be configured based on the frame. The radio frame has a length of 10 ms and can be defined as two 5-ms half-frames (HF). The HF can be defined as five 1-ms subframes (SF). The SF can be divided into one or more time slots, and the number of time slots within the SF depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 OFDM(A) symbols. When using normal CP, each time slot includes 14 symbols. When using extended CP, each time slot includes 12 symbols. In this document, symbols can include OFDM symbols (or CP-OFDM symbols) and SC-FDMA symbols (or DFT-s-OFDM symbols).
[0125] Depending on the subcarrier spacing, one or more time slots can be included in the subframe.
[0126] Table 1 below illustrates the subcarrier spacing configuration μ.
[0127] [Table 1]
[0128]
[0129] Table 2 below illustrates the number of time slots (N) in the frame according to the subcarrier spacing configuration μ frame,μslot ) The number of time slots (N) in a subframe subframe,μ slot ) The number of symbols (N) in a time slot slot symb ) etc.
[0130] [Table 2]
[0131]
[0132] Table 3 illustrates that, in the case of using extended CP, the number of symbols per time slot, the number of time slots per frame, and the number of time slots per subframe vary according to the SCS.
[0133] [Table 3]
[0134] SCS(15*2^u) <![CDATA[N slot symb > <![CDATA[N frame,u slot > <![CDATA[N frame,u slot > 60kHz (μ = 2) 12 40 4
[0135] NR supports multiple parameter sets (or subcarrier spacings (SCS)) to support various 5G services. For example, when the SCS is 15 kHz, it supports wide areas in traditional cellular bands; and when the SCS is 30 kHz / 60 kHz, it supports dense urban areas, low latency, and wide carrier bandwidths; and when the SCS is 60 kHz or greater, it supports bandwidths greater than 24.25 GHz to overcome phase noise.
[0136] NR frequency bands can be defined as two types of frequency ranges (FR1 and FR2). The numerical values of the frequency ranges can be changed, and for example, the two types of frequency ranges (FR1 and FR2) can be as shown in Table 4 below. For ease of explanation, among the frequency ranges used in the NR system, FR1 can refer to the "below 6 GHz range", and FR2 can refer to the "above 6 GHz range" and can be called millimeter wave (mmW).
[0137] [Table 4]
[0138] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 450 MHz - 6000 MHz 15, 30, 60 kHz FR2 24250 MHz - 52600 MHz 60, 120, 240 kHz
[0139] As described above, the numerical values of the frequency ranges of the NR system can be changed. For example, as shown in Table 5 below, FR1 can include frequency bands from 410 MHz to 7125 MHz. That is, FR1 can include frequency bands of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher. For example, the frequency bands of 6 GHz (or 5850, 5900, 5925 MHz, etc.) or higher included in FR1 can include unlicensed frequency bands. The unlicensed frequency bands can be used for various purposes, such as for vehicle communication (e.g., autonomous driving).
[0140] [Table 5]
[0141] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410 MHz - 7125 MHz 15, 30, 60 kHz FR2 24250 MHz - 52600 MHz 60, 120, 240 kHz
[0142] In the NR system, OFDM(A) parameter sets (e.g., SCS, CP length, etc.) can be configured differently among multiple cells integrated into one UE. Accordingly, the (absolute time) duration of time resources (e.g., SF, time slot, or TTI) configured with the same number of symbols (collectively referred to as time unit (TU) for convenience) can be configured differently among the integrated cells.
[0143] Figure 17 An example of a time slot structure is illustrated.
[0144] Refer to Figure 17 , in the time domain, a time slot includes multiple symbols. For example, in the case of normal CP, a time slot can include 14 symbols. However, in the case of extended CP, a time slot can include 12 symbols. Alternatively, in the case of normal CP, a time slot can include 7 symbols. However, in the case of extended CP, a time slot can include 6 symbols.
[0145] In the frequency domain, a carrier can include multiple subcarriers. A resource block (RB) can be defined as multiple consecutive subcarriers in the frequency domain (e.g., 12 subcarriers). A bandwidth part (BWP) can be defined as multiple consecutive (P) RBs in the frequency domain, and the BWP can correspond to a parameter set (e.g., SCS, CP length, etc.). A carrier can include up to N (e.g., 5) BWPs. Data communication can be performed through an active BWP. Each element can be referred to as a resource element (RE) in a resource grid, and one complex symbol can be mapped to each element.
[0146] As illustrated in Table 6 below, the physical downlink control channel (PDCCH) can include one or more control channel elements (CCEs).
[0147] [Table 6]
[0148] Aggregation level Number of CCEs 1 1 2 2 4 4 8 8 16 16
[0149] That is, the PDCCH can be transmitted through a resource including 1, 2, 4, 8, or 16 CCEs. Here, a CCE includes six resource element groups (REGs), and one REG includes one resource block in the frequency domain and one orthogonal frequency division multiplexing (OFDM) symbol in the time domain.
[0150] A new unit called a control resource set (CORESET) can be introduced in NR. A UE can receive the PDCCH in the CORESET.
[0151] Hereinafter, the BWP will be described.
[0152] In the NR system, each component carrier (CC) can support up to 400 megahertz (MHz). If the UE operating in such a wideband CC always operates with the RF for the entire CC turned on, the UE battery consumption may increase. Alternatively, considering multiple use cases (e.g., eMBB, URLLC, mMTC, etc.) where operations are performed within one wideband CC, different parameter sets (e.g., subcarrier spacing (SCS)) can be supported for the corresponding frequency bands within the CC. Alternatively, the UE can have different capabilities for the maximum bandwidth. Taking this into account, the base station can instruct the UE to operate only in a partial bandwidth rather than the entire bandwidth of the wideband CC. For convenience, this partial bandwidth is defined as the bandwidth part (BWP). The BWP can include resource blocks (RBs) that are continuous on the frequency axis and can correspond to one parameter set (e.g., subcarrier spacing, cyclic prefix (CP) length, slot / mini-slot duration, etc.).
[0153] On the other hand, even within one CC configured for the UE, the base station can set multiple BWPs. For example, a BWP that occupies a relatively small frequency region can be set in the PDCCH monitoring slot, and the PDSCH indicated by the PDCCH can be scheduled on a larger BWP. Alternatively, when the UE is concentrated on a specific BWP, some UEs can be set for other BWPs for load balancing. Alternatively, considering the inter-cell interference cancellation in the frequency domain between adjacent cells, a part of the spectrum can be excluded from the entire bandwidth, and two BWPs can be set in the same slot. That is, the base station can set at least one DL / UL BWP for the UE associated with the wideband CC and activate at least one of the DL / UL BWPs set at a specific time (through L1 signaling, MAC CE, RRC signaling, etc.). In addition, a switch to another configured DL / UL BWP can be indicated (through L1 signaling, MAC CE, RRC signaling, etc.), or when the timer value based on the timer expires, a switch to a predetermined DL / UL BWP can be performed. In this case, the activated DL / UL BWP is defined as the active DL / UL BWP. However, when the UE is in the initial access process or before resuming the RRC connection, the UE may not receive the configuration for the DL / UL BWP. In this case, the DL / UL BWP assumed by the UE is defined as the initial active DL / UL BWP.
[0154] Hereinafter, the proposals of the present disclosure will be described in more detail.
[0155] The following drawings are created to explain specific examples of the present disclosure. Since the names of specific devices or the names of specific signals / messages / fields described in the drawings are presented by way of example, the technical features of the present disclosure are not limited to the specific names used in the following drawings.
[0156] In the NR system, each serving cell can set up to four BWPs, and the dormant state considers operations on a BWP basis. Therefore, it is necessary to define the dormancy behavior for each cell and BWP.
[0157] In the LTE system, the dormant state is defined to quickly perform activation / deactivation of secondary cells (SCells). When a specific SCell is set to the dormant state, the UE may not monitor the PDCCH for that cell. Thereafter, to quickly activate the corresponding SCell, measurements and reports are defined to be performed in the dormant state to monitor the channel conditions and link status of the corresponding cell. For example, when a specific SCell is set to the dormant state, the UE does not perform PDCCH monitoring, but can perform measurements and reports for channel state information (CSI) / radio resource management (RRM). In the NR system, the above-mentioned dormant state or dormancy behavior can be defined on a BWP basis.
[0158] For example, the dormancy behavior for each cell and BWP can be defined by the following method. In addition, in the present disclosure, the dormancy behavior can be cross-interpreted as UE operations based on the dormant mode, and the normal behavior can be cross-interpreted as operations other than the dormancy behavior or UE operations based on the normal mode.
[0159] (Method 1 for defining dormancy behavior) State change
[0160] The network can indicate a transition to the dormant state for a specific BWP, and the UE may not perform some or all of the PDCCH monitoring for the BWP indicated to transition to the dormant state.
[0161] (Method 2 for defining dormancy behavior) Dormant BWP
[0162] The network can designate a specific BWP as a dormant BWP. For example, it can be indicated that no PDCCH monitoring is performed by configuring a BWP with a bandwidth of 0, indicating a minimum PDCCH monitoring through BWP configuration, and not indicating the search space set configuration, etc.
[0163] In addition, the NR system considers switching between the normal state and the dormant state through L1 signaling such as DCI for faster SCell activation / deactivation. For example, the dormancy behavior of a specific cell can be activated / deactivated by the following method.
[0164] (Activation Method 1) Introduction of Special DCI
[0165] Special DCI can be defined to indicate the dormant behavior of each SCell. For example, it can be indicated that the UE monitors the special DCI in the PCell, and the network can determine whether dormancy is set for each SCell through the special DCI. The aforementioned Method 1, Method 2, etc. can be used to define the dormant behavior of the SCell.
[0166] (Activation Method 2) Enhancement of the BWP Indication Field in DCI
[0167] The BWP indication field of the existing DCI can be extended to perform BWP indication for the corresponding cell and / or specific SCell. That is, cross-carrier indication for the BWP can be performed through the existing BWP indication field.
[0168] (Activation Method 3) BWP Cross-Carrier Scheduling
[0169] Conventional cross-carrier scheduling indicates whether a cell is a scheduling cell or a scheduled cell, and in the case where the cell is a scheduled cell, pairing between carriers is performed by indicating the scheduling cell of the scheduled cell. To define the dormant behavior for the SCell, a method of indicating whether cross-carrier scheduling is performed for each BWP can also be considered. For example, in each BWP configuration of the SCell, it can be specified that the scheduling cell that can indicate the state transition when the dormant behavior is performed in the corresponding BWP. Alternatively, when specifying the dormant BWP, the scheduling cell indicating the dormant behavior in the corresponding BWP can be specified in the corresponding BWP configuration.
[0170] As described above, various methods for implementing fast activation / deactivation and dormant behavior of SCell in NR are discussed. When using the above methods, the following items need to be additionally considered.
[0171] (Problem 1) Default BWP Triggered by BWP Inactivity Timer
[0172] (Problem 2) Scheduling Information in DCI Triggering Dormant Behavior
[0173] (Problem 3) HARQ Feedback in DCI Triggering Dormant Behavior
[0174] The considerations and solutions will be described below.
[0175] In the present disclosure, a D-BWP may represent a BWP that performs a dormant behavior, and an N-BWP is a normal BWP and may refer to a BWP that performs normal BWP operations. Additionally, in the present disclosure, the dormant behavior in a specific BWP may refer to an operation in which no PDCCH is received in the BWP or PDCCH is received for a longer period than normal behavior, or an operation in which PDSCH / PUSCH scheduling for the BWP is not performed or PDSCH / PUSCH scheduling for the BWP is performed for a longer period than normal behavior. Similarly, a dormant BWP may refer to a BWP in which no PDCCH is received or PDCCH is received for a longer period than normal behavior, or a BWP in which PDSCH / PUSCH scheduling for the BWP is not performed or PDSCH / PUSCH scheduling for the BWP is performed for a longer period than a normal BWP.
[0176] Figure 18 Examples of the dormant behavior are shown. Specifically, Figure 18 (a) and (b) of show examples of operations according to the indication of the dormant state of the UE.
[0177] Referring to Figure 18 of (a), the UE performs PDCCH monitoring in the first BWP based on normal behavior. Thereafter, when the UE receives a dormant state indication, the UE does not perform PDCCH monitoring.
[0178] Referring to Figure 18 of (b), the UE performs PDCCH monitoring in the second BWP based on normal behavior. Here, PDCCH monitoring may be periodically performed based on a first period. Thereafter, when the UE receives a dormant state indication, the UE performs PDCCH monitoring periodically based on a second period. In this case, the second period may be longer than the first period.
[0179] Hereinafter, the default BWP triggered by the BWP inactivity timer will be described.
[0180] Regarding BWP operations, a BWP inactivity timer is introduced in the NR system to prevent a situation where different active BWPs are configured due to a misunderstanding between the UE and the network. If the UE does not receive a PDCCH within a specific time exceeding that specified by the timer in the active BWP, the UE may move to the default BWP pre-indicated by the network and perform PDCCH monitoring in the default BWP according to the PDCCH monitoring configuration (e.g., the CORESET and search space setting configuration for the default BWP).
[0181] Figure 19 Examples of BWP operations are shown.
[0182] Referring toFigure 19 When the UE is receiving the PDCCH on the first BWP and does not receive the PDCCH within the time set by the BWP inactivity timer in the first BWP, the UE moves to the second BWP which is the default BWP and performs PDCCH monitoring.
[0183] In addition, in the present disclosure including Figure 19 moving from the first BWP to the second BWP may mean that the active BWP changes from the first BWP to the second BWP.
[0184] When performing default BWP operation and sleep behavior together, operations inconsistent with their purposes may be performed. For example, the network may instruct a specific SCell to move to the D-BWP or switch the current BWP to the sleep state for power saving of the UE. However, a UE configured with a BWP inactivity timer may move to the default BWP and perform PDCCH monitoring after a specific period of time.
[0185] A simple way to solve this problem is to consider setting the default BWP as the D-BWP. However, in this case, additional methods are required to solve the misunderstanding between the network and the UE (which is the original purpose of the default BWP). In the present disclosure, the following method is proposed to apply the sleep operation and the BWP inactivity timer together.
[0186] When the network instructs the UE to move to the D-BWP or switch the current active BWP to the sleep state, the UE may ignore the previously set BWP inactivity timer or reset the BWP inactivity timer to a predetermined value or a value related to the sleep state indicated by the network. For example, the network may set an appropriate sleep period considering the traffic condition of the UE and pre-indicate the corresponding value to the UE. Thereafter, when the UE is instructed to move to the D-BWP or switch the current active BWP to the sleep state, the UE may set the value indicated by the network as the BWP inactivity timer value. Additionally, the inactivity timer for the sleep behavior indicated by the network may operate independently of the existing BWP inactivity timer. For example, a UE instructed to perform the sleep behavior may turn off the existing BWP inactivity timer and operate the inactivity timer for the sleep behavior. Thereafter, when the BWP inactivity timer expires or the UE is instructed to move to the N-BWP or switch to the normal state, the UE may end the sleep behavior.
[0187] In addition, when the sleep behavior ends through the inactivity timer for the sleep behavior, the UE may move to the default BWP of the corresponding cell or switch to the normal state. Alternatively, when the network ends the sleep behavior through the inactivity timer, the network may specify the BWP to which the UE will move and indicate the BWP to the UE.
[0188] Figure 20Shows another example of the BWP operation of the UE. Specifically, Figure 20 shows the case where the BWP inactivity timer is in operation in the example of Figure 19 while the UE is instructed / configured to switch to the dormant state.
[0189] Referring to Figure 20 , during the operation of the BWP inactivity timer on the first BWP, the UE receives a dormant state transition message. The dormant state transition message can be a message for instructing the UE to switch to the dormant state.
[0190] The inactivity timer for the dormant operation can start when the UE receives the dormant state transition message. Here, if the inactivity timer for the dormant behavior expires, the UE can perform PDCCH monitoring on the second BWP that is the default BWP.
[0191] Hereinafter, the scheduling information that triggers the dormant behavior in the DCI will be described.
[0192] When the movement between the D-BWP and the N-BWP is indicated by DCI or the like, and the DCI is a normal scheduling DCI, problems may occur if it is not clear whether to perform the operation of the scheduling information in the DCI. For example, when performing the operation of the PDSCH scheduling that indicates moving to the D-BWP in the DCI, additional operations may be required depending on whether the reception of the corresponding PDSCH is successful. This may mean that the PDCCH / PDSCH transmission / reception operations can continue even in the D-BWP. To solve this problem, the present disclosure proposes the following method.
[0193] (Case 1-1) The case where the DCI indicating the dormant behavior for a specific cell or the DCI indicating switching to the dormant BWP includes PDSCH scheduling information
[0194] As described above, since the PDSCH transmission / reception in the D-BWP may cause additional PDCCH / PDSCH transmission / reception, operations contrary to the purpose of the dormant BWP may be performed. Therefore, the PDSCH scheduling information for the D-BWP indicating the dormant behavior included in the DCI may be ignored. In addition, the decoding performance of the UE can be improved by transmitting known bits or a known bit sequence in the corresponding field. For this purpose, the known bit information related to the PDSCH scheduling on the field can be indicated by the network or through a previous definition.
[0195] (Case 1-2) The case where the DCI indicating the transition from the dormant behavior to the normal behavior or the DCI indicating the transition from the dormant BWP to the normal BWP includes PDSCH scheduling or uplink scheduling information
[0196] In Case 1-2, since the PDSCH scheduling information or the uplink scheduling information can reduce PDCCH transmissions in the N-BWP or the normal state, it may be desirable to apply this information. However, in Case 1-2, determining whether to apply the PDSCH scheduling information or the uplink scheduling information may be limited to cases where the PDSCH scheduling information or the uplink scheduling information is UL / DL scheduling-related information in the N-BWP where the transition occurs or PDSCH or uplink transmission-related information in the normal state. For example, when a field indicating the sleep behavior for a specific SCell is added to the DCI for scheduling the PDSCH of the PCell, the PDSCH scheduling information of the DCI may mean PDSCH-related information in the PCell.
[0197] In the following, the HARQ feedback for triggering the sleep behavior of the DCI will be described.
[0198] Since the sleep behavior can limit the PDCCH / PDSCH transmission and reception operations in the indicated cell (by definition) as much as possible, the subsequent operations of the network and the UE may be greatly affected by losses / false alarms, etc. To solve this problem, methods for improving the decoding performance can be applied, or additional confirmation operations for the sleep behavior indication may be required. To solve this problem, the present disclosure proposes ACK / NACK feedback for moving to the D-BWP or transitioning to the sleep state. For this purpose, the following methods can be considered. The methods described below can be implemented individually or in combination. In the following description, when the DCI is only configured with an indication for the sleep behavior, the UE cannot determine whether to provide a NACK, so the following proposal can be interpreted as sending ACK signaling. Alternatively, when the DCI indicating the sleep behavior also includes PDSCH scheduling, this may mean receiving an ACK / NACK for the corresponding PDSCH or an uplink transmission command for the sleep behavior in the case of uplink scheduling. That is, since both ACK and NACK can indicate that the DCI has been received normally, both ACK and NACK can indicate that the indication for the sleep behavior has been received.
[0199] (Case 2-1) Combination of sleep command and UL / DL scheduling
[0200] The DCI indicating the sleep behavior can include uplink / downlink scheduling information, and the ACK / NACK for the downlink and the scheduled uplink transmission can mean that the DCI including the sleep behavior has been correctly received, and thus the UE and the network can assume that the indicated sleep behavior is to be performed. Here, since NACK means NACK for PDSCH reception, NACK can also mean that the indication for the sleep behavior has been received.
[0201] (Case 2-1-1) The case where the target of uplink / downlink scheduling is the dormant BWP or the dormant state
[0202] It can be assumed that the UE can perform a dormant behavior after reaching the termination of the scheduled uplink / downlink scheduling, and the ACK / NACK resources or uplink resources for the corresponding scheduling in the D-BWP or the dormant state conform to the conventional ACK / NACK resource determination method and uplink transmission method. The UE that has completed the corresponding uplink / downlink transmission / reception can perform a dormant behavior, and it can be assumed that there is no subsequent scheduling or subsequent scheduling is ignored.
[0203] (Case 2-1-2) The case where the target of uplink / downlink scheduling is the scheduled cell / BWP or the normal state
[0204] In this case, ACK / NACK or uplink transmission can mean that a dormant command is normally received in the scheduled cell / BWP or the normal state, and the UE can perform a dormant behavior.
[0205] (Case 2-2) The combination of the dormant command and non-scheduling / pseudo-scheduling
[0206] Case 2-2 is the case where the dormant behavior is indicated by DCI in which only the command for the dormant behavior is valid without uplink / downlink scheduling information or in which the scheduling information field can be assumed to be dummy / dummy data. In this case, since there is no associated uplink / downlink transmission / reception, feedback information for the DCI can be sent. Here, when the DCI is not received, the UE is uncertain whether the DCI is sent, and thus it can actually mean ACK transmission. In this case, the feedback for the dormant command can be sent in the dormant BWP or the dormant state, and the feedback resources can be indicated by the DCI carrying the dormant command, or the feedback can be performed through pre-defined feedback resources.
[0207] Hereinafter, the BWP determination for the normal state will be described.
[0208] When the transition between a normal BWP and a dormant BWP is performed only by changing the state without BWP indication, for example, when the network allocates 1 bit in the DCI sent to the PCell per SCell or per SCell group to indicate only dormancy, a BWP for the dormant mode / normal mode is predefined. As an example, the network can specify one BWP (D-BWP) for the dormant mode, and if the predefined 1-bit field in the DCI is "1" or "0", the active BWP of the associated SCell is specified as the D-BWP. In the case of a dormant BWP, since multiple dormant BWPs only increase signaling overhead and there is no additional gain, it can be expected that only one dormant BWP is specified per cell. On the other hand, in the case of a common BWP, up to 4 BWPs per cell can be specified as a conventional scheme. This can mean that when a transition from the dormant mode to the normal mode occurs, it is necessary to move to one of the configured normal BWPs. The present disclosure proposes a method for selecting an active BWP in the normal mode when a UE is instructed to switch from the dormant mode to the normal mode.
[0209] (Option 1-1) The active BWP in the normal mode immediately before the dormant mode
[0210] As a first method, the active BWP in the normal mode before entering the dormant mode can be assumed to be the active BWP in the normal mode after the dormant mode. This may be useful when the time for maintaining the dormant mode is relatively short.
[0211] (Option 1-2) The default BWP or the BWP predefined by the network
[0212] When the UE switches from the dormant mode to the normal mode, the UE can move to the default BWP specified in the corresponding cell. In this case, the default BWP can be the default BWP to which the UE will move when the BWP inactivity timer expires, or the BWP for the SCell dormant behavior specified by the network using higher layer signaling, etc. When the network wants to operate the UE in a BWP wider than the default BWP or in a BWP narrower than the default BWP, the network can move the BWP in the normal mode through the conventional BWP switching procedure.
[0213] The method actually applied between the foregoing Option 1-1 and 1-2 can be specified by a previous definition, or can be configured by the network through higher layer signaling, etc. Alternatively, the option to be applied can be determined by additionally specifying a timer, etc. For example, when changing from the dormant mode to the normal mode, if a predefined timer has not expired, the UE can move to the last active BWP in the normal mode immediately before the dormant mode according to Option 1-1. After the timer expires, the UE instructed to switch to the normal mode can move to the default BWP and execute the normal mode.
[0214] In the following, the maximum number of BWPs per cell will be described.
[0215] In conventional BWP operation, up to 4 BWPs per cell can be configured for a UE. On the other hand, when introducing a dormant BWP, the limit may need to be adjusted. The present disclosure proposes a method for specifying the maximum number of BWPs in a cell that designates a dormant BWP.
[0216] (Option 2-1) If a dormant BWP is designated, increase the maximum number of BWPs by 1.
[0217] Regarding the dormant BWP, the increase in the maximum number of BWPs per cell due to the dormant BWP may not be a major issue because there is little hardware / software impact on the UE. Therefore, in a cell that designates a dormant BWP, the same operation as the previous operation can be maintained by increasing the maximum number of BWPs by 1.
[0218] (Option 2-2) The dormant BWP is not included in the number of BWPs.
[0219] As described above, on the dormant BWP, the UE does not perform most of the operations performed in the conventional BWP. Therefore, the dormant BWP is not included in the number of BWPs.
[0220] In the following, HARQ feedback for the dormant indication will be described.
[0221] As described above, the dormant behavior can limit the PDCCH / PDSCH transmission and reception operations in the indicated cell (by definition) to a maximum, and thus the subsequent operations of the network and the UE may be significantly affected by losses / false alarms, etc. To solve this problem, a method for improving the decoding performance can be applied, or additional confirmation operations may be required for the dormant behavior indication. In the following, to solve such a problem, an ACK / NACK feedback method for the dormant indication is proposed. Although the ACK / NACK feedback method for the dormant behavior of the SCell in the PCell will be described below, this method can be equivalently applied even if the SCell indicates the dormant behavior for another SCell.
[0222] As a method for indicating the dormant behavior of the SCell in the PCell, a method of attaching a dormant behavior indication field for the SCell to the DCI that schedules the PDSCH of the PCell or indicating the dormant behavior for the SCell by reinterpreting some fields in the DCI that schedules the PDSCH of the PCell can be considered. In this case, the following two cases can be considered according to the role of the DCI. In the following, the ACK / NACK feedback method for the dormant indication for each case will be described.
[0223] (Case 3-1) Combination of PDSCH scheduling information and SCell dormant indication
[0224] In Case 3-1, the ACK / NACK for the PDSCH scheduled together with the dormant indication can also be interpreted as the ACK / NACK for the dormant indication. However, since NACK can be sent even when the DCI for the PDSCH is lost, for example, multiple PDSCHs can be scheduled and the HARQ-ACK feedback for the PDSCH can be sent in one PUCCH resource, there may be the following problem: it is impossible to distinguish whether the corresponding NACK is the NACK due to the loss of the DCI or the NACK indicating the reception of the DCI (i.e., the dormant indication is received, but the decoding of the PDSCH fails). To solve this problem, a method of sending the ACK / NACK information corresponding to the PDSCH and the ACK / NACK information for the dormant indication through the same PUCCH resource is proposed. Specifically, the ACK / NACK information corresponding to the PDSCH and the ACK / NACK information for the dormant indication can be fed back / sent together from the DCI or the corresponding PDSCH through the time slot after K1 time slots indicated by the HARQ-ACK feedback timing via the DCI. More specifically, for example, the ACK / NACK information corresponding to the PDSCH can be configured with a semi-static or dynamic HARQ-ACK codebook in the same manner as in the conventional NR system, and then 1-bit HARQ-ACK corresponding to the dormant indication is attached to a specific position (e.g., the last bit or the highest bit index corresponding thereto) in the corresponding HARQ-ACK codebook. That is, Case 3-1 can mean a method of attaching an ACK / NACK field (e.g., a 1-bit field) for the dormant indication to the existing ACK / NACK reporting process for PDSCH scheduling indicated together with the dormant indication. Alternatively, 1-bit HARQ-ACK corresponding to the dormant indication can be sent in the next bit of the codebook of the HARQ-ACK bits corresponding to the PDSCH, or 1-bit HARQ-ACK corresponding to the dormant indication can be sent in a specific position (e.g., the last bit or the highest bit index corresponding thereto) in the HARQ-ACK payload corresponding to the cell to which the PDSCH is sent in the codebook.
[0225] Alternatively, the UE may not expect PDSCH scheduling for the corresponding SCell in the time slot when the SCell switches to the dormant state or in multiple time slots including the corresponding time slot. In this case, the HARQ-ACK for the dormant indication for the SCell may be sent at the position where the HARQ-ACK information for the SCell is sent at the corresponding timing in the HARQ-ACK codebook for the dormant indication sent to the corresponding PCell, etc. for the semi-static codebook. Here, if the dormant indication is an indication for an SCell group composed of multiple SCells, the same feedback may be sent at all HARQ-ACK positions for the corresponding SCell, or the feedback may be sent at the HARQ-ACK position for a specific SCell (e.g., the SCell with the lowest index). In addition, the feedback may be sent as the same value for multiple time slot timings at which PDSCH scheduling for the SCell is not expected.
[0226] In addition, the semi-static codebook and the dynamic codebook in the present disclosure may refer to the NR-based type-1 codebook and type-2 codebook.
[0227] (Case 3-2) SCell Dormant Indication without PDSCH Scheduling Information
[0228] According to Case 3-2, since there is no PDSCH scheduling indicated together with the dormant indication, it is necessary to send ACK / NACK for the PDCCH (i.e., the dormant indication). For this purpose, the following methods may be considered.
[0229] (ACK / NACK Sending Method 1) After configuring the NR-based HARQ-ACK codebook, for example, in the case of configuring a semi-static HARQ-ACK codebook, the HARQ-ACK field for the dormant indication may be appended to a specific position. Here, the specific position may be the last bit or the highest bit index corresponding thereto, and the appended HARQ-ACK field may be, for example, a 1-bit field.
[0230] (ACK / NACK Sending Method 2) When a semi-static HARQ-ACK codebook is configured, similar to the HARQ-ACK feedback method for the DCI indicating the NR SPS release, the UE may assume that there is no other unicast PDSCH reception in the same time slot as the time slot in which the PDCCH indicating the dormant state is sent when sending the HARQ-ACK at the position corresponding to the corresponding DCI in the semi-static HARQ-ACK codebook or in the time slot corresponding to the time slot in which the DCI is sent.
[0231] (ACK / NACK transmission method 3) In the same manner as in Case 3-1, the HARQ-ACK for the sleep indication can be transmitted at the HARQ-ACK position corresponding to the SCell within the HARQ-ACK codebook.
[0232] Hereinafter, the HARQ-ACK feedback timing will be described.
[0233] In the above description, the HARQ-ACK feedback timing for the sleep indication can be determined as follows.
[0234] (Option 3-1) The time slot after K1 time slots starting from the DCI
[0235] It is possible to determine the time slot after K1 (i.e., after the time slot offset between the DCI and the HARQ-ACK) starting from the time slot in which the DCI including the sleep indication has been transmitted.
[0236] (Option 3-2) K1 time slots starting from the PDSCH scheduled by the DCI
[0237] The network can determine the time slot after K1 time slots starting from the PDSCH position as the feedback timing based on the PDSCH resource allocation information in the DCI including the sleep indication. In Case 3-2, although there is no actually scheduled PDSCH, the network can allocate a virtual PDSCH to convey the HARQ-ACK feedback timing for the sleep indication.
[0238] The above proposal can be applied only when the candidate PDSCH reception time slot associated with the uplink channel carrying the HARQ-ACK information or its corresponding PDCCH monitoring occasion includes the monitoring occasion for the PDCCH indicating the sleep state. In addition, Case 3-1 can be applied only to cases other than the fallback PUCCH transmission, that is, the case where the HARQ-ACK information to be actually fed back corresponds to only a single PCell single PDSCH (in the case of a semi-static codebook) or a single 1-bit PDSCH with counter-DAI = 1. In other words, in the case of fallback PUCCH transmission, only the HARQ-ACK for the scheduled PDSCH can be fed back without additional HARQ-ACK feedback for the sleep indication.
[0239] UEs that obtain the time slot offset through the above method need to determine the start and length indicator values (SLIVs) corresponding to K1 to which the HARQ-ACK will be mapped in the PDSCH time slot. For this purpose, the present disclosure proposes a method of mapping the corresponding HARQ-ACK to a virtual SLIV or a specific SLIV candidate (e.g., the first candidate or the last candidate) indicated by DCI. This method can be applied when configuring the HARQ-ACK codebook in the ACK / NACK transmission method 2, especially in case 3-2.
[0240] In addition, in the case of a semi-static codebook, feedback is provided for the HARQ-ACK set corresponding to the current active downlink BWP of the active cell and the first active downlink BWP of the deactivated cell. When the active downlink BWP of a specific cell is a dormant BWP, the HARQ-ACK codebook corresponding to the cell can be configured by the following method. Additionally, the following method can be applied starting from X ms after indicating the dormant BWP, and the value of X can be determined by previously defined or higher layer signaling of the network.
[0241] (Option 4-1) In the deactivated cell, the HARQ-ACK corresponding to the first active downlink BWP, and the set of K1 values and SLIVs configured therein
[0242] (Option 4-2) 0 bit
[0243] (Option 4-3) The HARQ-ACK corresponding to the last BWP immediately preceding the corresponding dormant BWP, and the set of K1 values and SLIVs configured therein
[0244] In addition to the above methods, when performing a switch of the dormant behavior by switching between the BWP corresponding to the dormant behavior (dormant BWP) and the BWP corresponding to the non-dormant behavior (non-dormant BWP), the HARQ-ACK codebook configuration can conform to the dormant BWP configuration. Alternatively, if there is no configuration for the HARQ-ACK codebook configuration (e.g., the time domain resource allocation (TDRA) table and SLIV table in the dormant BWP), it can conform to the configuration of a specific BWP of the corresponding cell. Here, for example, the specific BWP can be a BWP with the lowest / highest index BWP (excluding the dormant BWP), a configured reference BWP, an initial BWP, the last non-dormant active BWP, etc.
[0245] In the method described above, when the UE receives a sleep indication again before applying the sleep behavior / non-sleep behavior according to the sleep indication to the same SCell, the UE may follow the most recently received sleep indication, or consider that an error has occurred when receiving the corresponding DCI if the two sleep indications indicate different behaviors assuming that the two sleep indications indicate the same behavior (sleep or non-sleep).
[0246] Alternatively, when the UE receives a sleep indication for an SCell, the UE may assume that no sleep indication for the corresponding cell is sent before applying the corresponding sleep behavior / non-sleep behavior or before a specific time period, or may not receive a sleep indication.
[0247] Although the case of sending a sleep indication together with downlink scheduling information has been mainly described above, a sleep indication may also be sent in the uplink scheduling DCI. Hereinafter, a feedback method for confirming whether the UE has correctly received the sleep indication when the sleep indication is sent in the uplink scheduling DCI is proposed. Here, the feedback for the sleep indication may be sent only when the UE detects an indication different from the previous indication, for example, when the UE has previously received a sleep indication but then detects a normal behavior indication, when the UE has previously received a normal behavior indication but then detects a sleep indication, and when the UE has previously received a normal behavior instruction but then detects a sleep indication, and when the UE has received an indication for a specific SCell but then receives an indication for a group of SCells.
[0248] (Feedback method 1) Method using PUSCH
[0249] In the NR system, DCI format 0_1 (uplink non-backoff DCI) may include a PUSCH resource allocation field, a UL-SCH indicator field, and a CSI request field. In this case, the CSI report and related operations of the UE may be as follows. Hereinafter, a HARQ-ACK feedback method for the sleep indication for each operation of each UE is proposed.
[0250] (Feedback method 1-1) When the UL-SCH indicator is OFF and the CSI request is ON, the UE performs an aperiodic CSI report via PUSCH.
[0251] In this case, when the UE performs a CSI report, the gNB may recognize that the UE has received the DCI (i.e., the DCI including the sleep indication), and thus may not require additional feedback related to the sleep indication.
[0252] (Feedback Method 1-2) When the UL-SCH indicator and CSI request are OFF, the UE does not perform PUSCH transmission for CSI reporting and only performs downlink measurements.
[0253] In this case, the UE may send a PUSCH to notify whether a sleep indication is received. Here, the PUSCH may be a PUSCH with empty content.
[0254] Since the above method cannot be distinguished from the normal operation of only performing downlink measurements, the network may indicate the transmission of DCI based on the sleep indication rather than downlink measurements using a specific field or a combination of specific fields in the DCI, and the UE may send a PUSCH or a PUSCH with empty content according to the PUSCH scheduling of the DCI. Here, the specific field may be an additional 1-bit field indicating that the corresponding DCI is dedicated to the sleep indication, or may be an existing field set to a specific value (e.g., the resource allocation field set to 1).
[0255] Alternatively, to distinguish from the normal operation of only performing downlink measurements, when the gNB indicates the sleep behavior or normal behavior for any SCell, the UE may send a PUSCH or a PUSCH with empty content according to the PUSCH scheduling of the corresponding DCI. In this case, downlink measurements may not be performed.
[0256] That is, according to the above method, when the uplink grant DCI indicates that the sleep indication is ON and both the UL-SCH indicator and CSI reporting trigger are OFF, a signal may be sent through the PUSCH resource allocated by the DCI. On the other hand, when the sleep indication is OFF and both the UL-SCH indicator and CSI reporting trigger are OFF, the PUSCH transmission corresponding to the DCI may be configured not to be performed.
[0257] (Feedback Method 2) Method using the HARQ-ACK feedback mechanism
[0258] When the UL-SCH indicator is OFF and the CSI request is OFF, the UE may send explicit feedback for the sleep indication.
[0259] Since this method may not be distinguishable from the normal operation of only performing downlink measurements, the network may use a combination with a specific field in the DCI to indicate the DCI transmission for the sleep indication rather than downlink measurements, and the UE may use explicit feedback to send feedback for the sleep indication.
[0260] Here, explicit feedback can be performed in the following manner: when HARQ-ACK for other PDSCHs is fed back in the corresponding time slot, feedback for the sleep indication is performed by adding 1 bit. Here, if there is no HARQ-ACK feedback for other PDSCHs, PUCCH can be used to perform feedback for the sleep indication, and its PUCCH resources can be pre-configured by RRC signaling, configured by uplink grant, or configured by a combination of signaling and uplink grant. That is to say, when the sleep indication is sent through uplink grant DCI, the feedback transmission timing and PUCCH transmission resources to be used or applied for the feedback transmission of the corresponding sleep indication can be indicated by a field in the DCI or by reinterpreting a field in the DCI.
[0261] Figure 21 is a flowchart of an example of the discontinuous reception method of the UE.
[0262] Refer to Figure 21 , the UE performs PDCCH monitoring (S2110) during the active duration.
[0263] In addition, the UE receives BWP configuration information (S2120). Here, the BWP configuration information can indicate a specific BWP.
[0264] The UE receives a PDCCH based on the PDCCH monitoring (S2130). Here, the PDCCH can include sleep indication information for a specific cell among the multiple cells configured for the UE.
[0265] Thereafter, the UE activates a specific BWP based on the sleep indication information indicating non-sleep (S2140).
[0266] Hereinafter, discontinuous reception (DRX) will be described.
[0267] Discontinuous reception (DRX) refers to an operating mode in which the UE reduces battery consumption and thus can receive downlink channels discontinuously. That is to say, a UE configured for DRX can reduce power consumption by receiving DL signals discontinuously.
[0268] The DRX operation is performed within a DRX cycle, which indicates a time interval for periodically repeating the active duration. The DRX cycle includes an active duration and a sleep period (or DRX occasion). The active duration indicates the time interval during which the UE monitors the PDCCH to receive the PDCCH.
[0269] DRX can be performed in the Radio Resource Control (RRC)_IDLE state (or mode), RRC_INACTIVE state (or mode), or RRC_CONNECTED state (or mode). In the RRC_IDLE state and RRC_INACTIVE state, DRX can be used for discontinuous reception of paging signals.
[0270] - RRC_IDLE state: The state where no radio connection (RRC connection) is established between the base station and the UE
[0271] - RRC_INACTIVE state: The state where a radio connection (RRC connection) is established between the base station and the UE but the radio connection is inactive
[0272] - RRC_CONNECTED state: The state where a radio connection (RRC connection) is established between the base station and the UE
[0273] DRX can be basically divided into idle mode DRX, connected DRX (C-DRX), and extended DRX.
[0274] The DRX applied in the IDLE state can be called idle mode DRX, and the DRX applied in the connected state can be called connected mode DRX (C-DRX).
[0275] Extended / enhanced DRX (eDRX) is a mechanism that can extend the periods of idle mode DRX and C-DRX, and can be mainly used for (massive) IoT applications. In idle mode DRX, it can be set based on system information (e.g., SIB1) whether eDRX is allowed. SIB1 can include an eDRX allowance parameter. The eDRX allowance parameter indicates whether idle mode extended DRX is allowed.
[0276] Hereinafter, idle mode DRX will be described.
[0277] In the idle mode, the UE can use DRX to reduce power consumption. One paging occasion (PO) is a subframe in which a paging - Radio Network Temporary Identifier (P-RNTI) can be sent via the Physical Downlink Control Channel (PDCCH), MTC PDCCH (MPDCCH), or Narrowband PDCCH (NPDCCH) (which addresses paging messages for NB-IoT).
[0278] In the P-RNTI transmitted via MPDCCH, the PO may indicate the starting subframe of MPDCCH repetition. In the case of transmitting P-RNTI via NPDCCH, if the subframe determined by the PO is not a valid NB-IoT downlink subframe, the PO may indicate the starting subframe of NPDCCH repetition. Therefore, the first valid NB-IoT downlink subframe after the PO is the starting subframe of NPDCCH repetition.
[0279] A paging frame (PF) is a radio frame that may include one or more paging occasions. When using DRX, the UE only needs to monitor one PO per DRX cycle. A paging narrowband (PNB) is a narrowband in which the UE performs paging message reception. The PF, PO, and PNB can be determined based on the DRX parameters provided by the system information.
[0280] Figure 22 is a flowchart illustrating an example of performing idle mode DRX operation.
[0281] Referring to Figure 22 , the UE can receive idle mode DRX configuration information (S21) from the base station via higher layer signaling (e.g., system information).
[0282] The UE can determine a paging frame (PF) and a paging occasion (PO) based on the idle mode DRX configuration information to monitor the PDCCH during the paging DRX cycle (S22). In this case, the DRX cycle can include an on-duration and a sleep duration (or DRX occasion).
[0283] The UE can monitor the PDCCH in the PO of the determined PF (S23). Here, for example, the UE only monitors one subframe (PO) per paging DRX cycle. Additionally, when the UE receives a PDCCH scrambled with P-RNTI during the on-duration (i.e., when paging is detected), the UE can perform a transition to the connected mode and send / receive data to / from the base station.
[0284] Figure 23 illustrates an example of idle mode DRX operation.
[0285] According to Figure 23 , when there is traffic directed to a UE in the RRC_IDLE state (hereinafter referred to as the "idle state"), paging for the corresponding UE is generated. The UE can wake up periodically (i.e., every (paging) DRX period) to monitor the PDCCH. In the absence of paging, the UE can transition to the connected state, receive data, and enter the sleep mode again if there is no data.
[0286] In the following, connected mode DRX (C-DRX) is described.
[0287] C-DRX refers to DRX applied in the RRC connected state. The DRX cycle for C-DRX can consist of a short DRX cycle and / or a long DRX cycle. Here, the short DRX cycle can optionally be selected.
[0288] When C-DRX is configured, the UE can perform PDCCH monitoring regarding the on-duration. If a PDCCH is successfully detected during PDCCH monitoring, the UE operates (or runs) an inactivity timer and keeps the timer in the wake state. On the other hand, if a PDCCH is not successfully detected during PDCCH monitoring, the UE can enter the sleep state after the on-duration expires.
[0289] When C-DRX is configured, the PDCCH reception occasion (e.g., the time slot having the PDCCH search space) can be configured to be discontinuous based on the C-DRX configuration. On the other hand, if C-DRX is not configured, according to the present disclosure, the PDCCH reception occasion (e.g., the time slot having the PDCCH search space) can be configured to be continuous.
[0290] In addition, PDCCH monitoring can be limited to a time interval configured according to the measurement gap, regardless of the C-DRX configuration.
[0291] Figure 24 The DRX cycle is illustrated.
[0292] Referring to Figure 24, The DRX cycle consists of an "ON duration (hereinafter, also referred to as 'DRX ON duration')" and a "timing for DRX". The DRX cycle defines the time interval at which the ON duration repeats cyclically. The ON duration indicates the duration for which the UE performs monitoring to receive the PDCCH. If DRX is configured, the UE performs PDCCH monitoring during the 'ON duration'. If a PDCCH is successfully detected during PDCCH monitoring, the UE operates an inactivity timer and remains awake. On the other hand, if a PDCCH is not successfully detected during PDCCH monitoring, the UE enters the sleep state after the 'ON duration' ends. Therefore, when DRX is configured, when performing the processes and / or methods described / proposed above, PDCCH monitoring / reception can be performed discontinuously in the time domain. For example, when DRX is configured, in the present disclosure, the PDCCH reception timing (e.g., the time slot with the PDCCH search space) can be configured discontinuously according to the DRX configuration. Otherwise, if DRX is not configured, when performing the processes and / or methods described / proposed above, PDCCH monitoring / reception can be performed continuously in the time domain. For example, when DRX is not configured, in the present disclosure, the PDCCH reception timing (e.g., the time slot with the PDCCH search space) can be configured continuously. In addition, regardless of whether DRX is configured, PDCCH monitoring can be restricted to the duration configured as a measurement gap.
[0293] Table 7 shows the UE processes related to DRX (RRC_CONNECTED state). Referring to Table 7, DRX configuration information can be received through higher layer (e.g., RRC) signaling. Whether DRX is ON (open) or OFF (closed) can be controlled by the DRX command of the MAC layer. If DRX is configured, PDCCH monitoring can be performed discontinuously.
[0294] [Table 7]
[0295]
[0296] MAC-CellGroupConfig may include the configuration information required to configure the medium access control (MAC) parameters for the cell group. MAC-CellGroupConfig may also include the configuration information about DRX. For example, MAC-CellGroupConfig may include the information for defining DRX as follows.
[0297] - The value of drx-OnDurationTimer: It defines the length of the start duration of the DRX cycle. It may be a timer related to the DRX ON duration.
[0298] -Value of drx-InactivityTimer: It defines the length of the duration for which the UE remains in the wake-up state after a PDCCH occasion that detects a PDCCH indicating initial UL or DL data.
[0299] -Value of drx-HARQ-RTT-TimerDL: It defines the length of the maximum duration from the reception of a DL initial transmission until the reception of a DL retransmission.
[0300] -Value of drx-HARQ-RTT-TimerUL: It defines the length of the maximum duration from the reception of a grant for a UL initial transmission until the reception of a grant for a UL retransmission.
[0301] -drx-LongCycleStartOffset: It defines the time length and starting point of the DRX cycle
[0302] -drx-ShortCycle (optional): It defines the time length of the short DRX cycle.
[0303] In this document, if any of drx-OnDurationTimer, drx-InactivityTimer, drx-HARQ-RTT-TimerDL, and drx-HARQ-RTT-TimerUL is operating, the UE performs PDCCH monitoring at each PDCCH occasion while remaining in the wake-up state.
[0304] Figure 25 is a flowchart of C-DRX operation.
[0305] The UE can receive RRC signaling (e.g., MAC-MainConfigIE) including DRX configuration information from the base station (S31). Here, the DRX configuration information may include the following information.
[0306] -onDurationTimer: The number of PDCCH subframes to be continuously monitored starting from the start position of the DRX cycle.
[0307] -drx-InactivityTimer: The number of PDCCH subframes to be continuously monitored when the UE decodes a PDCCH with scheduling information.
[0308] -drx-RetransmissionTimer: The number of PDCCH subframes to be continuously monitored when a HARQ retransmission is expected.
[0309] -longDRX-Cycle: The period that generates the on-duration.
[0310] -drxStartOffset: The subframe number at which the DRX cycle starts.
[0311] -drxShortCycleTimer: The number of short DRX cycles.
[0312] -shortDRX-Cycle: When the Drx-InactivityTimer expires, the number of DRX cycle operations is the same as the number of drxShortCycleTimer.
[0313] In addition, when the DRX 'ON' S32 is configured by a DRX command in a MAC command element (CE), the UE monitors the PDCCH for the ON duration of the DRX cycle based on the DRX configuration S33.
[0314] Figure 26 An example of C-DRX operation is illustrated.
[0315] If the UE receives scheduling information (e.g., DL grant) in the RRC_CONNECTED state (hereinafter referred to as the connected state), the UE may execute the DRX inactivity timer and the RRC inactivity timer.
[0316] When the DRX inactivity timer expires, the DRX mode may start. The UE may wake up from the DRX cycle and monitor the PDCCH for a predetermined period (on the duration timer). In this case, when short DRX is configured and the UE starts the DRX mode, the UE first starts with the short DRX cycle, and after the short DRX cycle is completed, starts the long DRX cycle. Here, the long DRX cycle may correspond to a multiple of the short DRX cycle. In addition, during the short DRX cycle, the UE may wake up more frequently. After the RRC inactivity timer expires, the UE may transition to the IDLE state and perform IDLE mode DRX operations.
[0317] Figure 27 An example of the power consumption depending on the UE's state is illustrated.
[0318] Refer to Figure 27 , after the UE is turned on, the UE performs the startup for application loading, the initial access / random access process for uplink and downlink synchronization with the base station, and the registration process with respect to the network. The current or power consumed during each process is in Figure 27As shown. When the transmission power of the UE is high, the current consumption of the UE increases. In addition, if there is no traffic to be sent to the UE or the base station, the UE switches to the idle mode to reduce power consumption and perform idle mode DRX operations. Further, when a paging such as a call occurrence occurs during the idle mode DRX operation, the UE switches from the idle mode to the connected mode through a cell establishment process and transmits / receives data to / from the base station.
[0319] In addition, when there is no data transmitted / received to / from the base station within a specific time or at a set timing in the connected mode, the UE performs connected mode DRX (C-DRX) operations.
[0320] Furthermore, when extended DRX (eDRX) is configured by higher layer signaling such as system information, the UE can perform eDRX operations in the idle mode or the connected mode.
[0321] The claims described in this disclosure can be combined in various ways. For example, the technical features of the method claims of this disclosure can be combined and implemented as a device, and the technical features of the device claims of this disclosure can be combined and implemented as a method. Additionally, the technical features of the method claims of this disclosure and the technical features of the device claims of this disclosure can be combined and implemented as a device, and the technical features of the method claims of this disclosure and the technical features of the device claims of this disclosure can be combined and implemented as a method.
[0322] In addition to the UE, the method proposed in this disclosure can be executed by a device configured to control the UE, the device including: at least one computer-readable recording medium that contains instructions based on being executed by at least one processor; one or more processors; and one or more memories that are operatively coupled by the one or more processors and store instructions, wherein the one or more processors execute the instructions to perform the method proposed in this disclosure. Further, it is obvious that the operations of the base station corresponding to the operations performed by the UE can be considered according to the method proposed in this disclosure.
Claims
1. A method performed by a user equipment (UE), the method comprising the following steps: Performing physical downlink control channel (PDCCH) monitoring during a discontinuous reception (DRX) on duration; Receiving bandwidth part (BWP) configuration information via a higher layer signal, wherein the BWP configuration information indicates a specific BWP; Receiving a PDCCH based on the PDCCH monitoring, wherein the PDCCH includes secondary cell (SCell) sleep information; and Transmitting acknowledgement / negative acknowledgement (ACK / NACK) information for the PDCCH including the SCell sleep information, wherein the SCell sleep information includes bits, and the bits correspond to a secondary cell group, wherein the bits have a value for sleep or a value for non - sleep, and wherein, for the secondary cell group, based on the current active BWP being a sleep BWP, the bits having the value for non - sleep indicate activation of the specific BWP provided by the BWP configuration information.
2. The method according to claim 1, wherein, The UE receives the PDCCH on a primary cell.
3. The method according to claim 1, wherein, The UE does not perform PDCCH monitoring or receive a physical downlink shared channel (PDSCH) on the sleep BWP.
4. The method according to claim 1, wherein, The sleep BWP is a BWP configured by higher layer signaling.
5. The method according to claim 1, wherein The maximum number of BWPs configurable for a cell of the UE is four.
6. The method according to claim 1, wherein, The UE receives a physical downlink shared channel (PDSCH) or the PDCCH on the specific BWP.
7. The method according to claim 1, wherein, The UE is configured with multiple cells, and the multiple cells include a primary cell and SCell, wherein the primary cell is the cell on which the UE performs an initial connection establishment procedure or a connection re - establishment procedure, and the SCell is a cell that provides additional radio resources to the UE.
8. A user equipment (UE), the UE comprising: One or more memories that store instructions; One or more transceivers; And One or more processors that are coupled to the one or more memories and the one or more transceivers, wherein the one or more processors execute the instructions to perform the following operations: Performing physical downlink control channel (PDCCH) monitoring during a discontinuous reception (DRX) on duration; Receiving bandwidth part (BWP) configuration information via a higher layer signal, wherein the BWP configuration information indicates a specific BWP; Receiving a PDCCH based on the PDCCH monitoring, wherein the PDCCH includes secondary cell (SCell) sleep information; and Transmitting acknowledgement / negative acknowledgement (ACK / NACK) information for the PDCCH including the SCell sleep information, wherein the SCell sleep information includes bits, and the bits correspond to a secondary cell group, wherein the bits have a value for sleep or a value for non - sleep, and wherein, for the secondary cell group, based on the current active BWP being a sleep BWP, the bits having the value for non - sleep indicate activation of the specific BWP provided by the BWP configuration information.
9. A device configured to control a user equipment (UE), the device comprising: One or more processors; And One or more memories, the one or more memories being operatively coupled by the one or more processors and storing instructions; Wherein the one or more processors execute the instructions to perform the following operations: Perform physical downlink control channel (PDCCH) monitoring during a discontinuous reception (DRX) on duration; Receive bandwidth part (BWP) configuration information via a high layer signal, wherein the BWP configuration information notifies a specific BWP; Receive a PDCCH based on the PDCCH monitoring, Wherein the PDCCH includes secondary cell (SCell) dormancy information; and Transmit acknowledgement / negative acknowledgement (ACK / NACK) information for the PDCCH including the SCell dormancy information, Wherein the SCell dormancy information includes a bit, and the bit corresponds to a secondary cell group, Wherein the bit has a value for dormancy or a value for non - dormancy, and Wherein, for the secondary cell group, based on the current active BWP being a dormant BWP, the bit having the value for non - dormancy notifies the activation of the specific BWP provided by the BWP configuration information.
10. At least one computer - readable recording medium including instructions executed by at least one processor, Among them, The at least one processor being configured to: Perform physical downlink control channel (PDCCH) monitoring during a discontinuous reception (DRX) on duration; Receive bandwidth part (BWP) configuration information via a high layer signal, wherein the BWP configuration information notifies a specific BWP; Receive a PDCCH based on the PDCCH monitoring, wherein the PDCCH includes secondary cell (SCell) dormancy information; and Transmit acknowledgement / negative acknowledgement (ACK / NACK) information for the PDCCH including the SCell dormancy information, Wherein the SCell dormancy information includes a bit, and the bit corresponds to a secondary cell group, Wherein the bit has a value for dormancy or a value for non - dormancy, and Wherein, for the secondary cell group, based on the current active BWP being a dormant BWP, the bit having the value for non - dormancy notifies the activation of the specific BWP provided by the BWP configuration information.
11. A method for setting a bandwidth part (BWP) performed by a base station in a wireless communication system, the method comprising the following steps: Send discontinuous reception (DRX) configuration information to a user equipment (UE); Send bandwidth part (BWP) configuration information to the UE via a high layer signal, wherein the BWP configuration information notifies a specific BWP; Send a physical downlink control channel (PDCCH) to the UE, wherein the PDCCH includes secondary cell (SCell) dormancy information, and Wherein the SCell dormancy information includes a bit, and the bit corresponds to a secondary cell group, Wherein the bit has a value for dormancy or a value for non - dormancy; Receive an acknowledgement / negative acknowledgement ACK / NACK message for the PDCCH including the SCell sleep information from the UE; and Based on the SCell sleep information including the bit having the value for non-sleep and based on the current active BWP for the UE being a dormant BWP, perform communication with the UE for the secondary cell group via the specific BWP, the bit having the value for non-sleep notifying activation of the specific BWP.
12. A base station, the base station comprising: One or more memories that store instructions; One or more transceivers; And One or more processors coupled to the one or more memories and the one or more transceivers, Wherein the one or more processors execute the instructions to perform the following operations: Send discontinuous reception DRX configuration information to a user equipment UE; Send bandwidth part BWP configuration information to the UE, wherein the BWP configuration information notifies a specific BWP; Send a physical downlink control channel PDCCH to the UE via a high layer signal, wherein the PDCCH includes secondary cell SCell sleep information, and Wherein the SCell sleep information includes a bit, and the bit corresponds to a secondary cell group, Wherein the bit has a value for sleep or a value for non-sleep; Receive an acknowledgement / negative acknowledgement ACK / NACK message for the PDCCH including the SCell sleep information from the UE; and Based on the SCell sleep information including the bit having the value for non-sleep and based on the current active BWP for the UE being a dormant BWP, perform communication with the UE for the secondary cell group via the specific BWP, the bit having the value for non-sleep notifying activation of the specific BWP.