Method and apparatus for controlling activation of a cell group in a wireless communication system
By introducing a sleep mode based on BWP in the mobile communication system, and using RRC messages and MAC CE to manage the activation and deactivation of cell groups, the problems of terminal battery consumption and data transmission latency are solved, achieving efficient terminal battery management and fast cell group handover.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- SAMSUNG ELECTRONICS CO LTD
- Filing Date
- 2021-07-14
- Publication Date
- 2026-05-29
AI Technical Summary
In mobile communication systems, existing technologies struggle to efficiently control the activation and deactivation of cell groups, leading to increased terminal battery consumption or data transmission delays.
The hibernation mode adopts a bandwidth portion (BWP) unit and manages the activation and deactivation of cell groups through RRC messages and MAC control elements (CE), reducing the terminal's PDCCH monitoring of multiple cells and enabling rapid activation and deactivation of carrier aggregation or dual connectivity.
It effectively reduces terminal battery consumption, lowers data transmission latency, and supports rapid activation and deactivation of cell groups, thereby improving system efficiency.
Smart Images

Figure CN115943715B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to methods and apparatus for activating or deactivating cell groups in a wireless communication system. Background Technology
[0002] Following the commercialization of fourth-generation (4G) communication systems, efforts have been made to develop improved fifth-generation (5G) or near-5G communication systems to meet the growing demand for wireless data services. Therefore, 5G or near-5G communication systems are referred to as "super-4G network communication systems" or "post-Long Term Evolution (LTE) systems." The 5G communication system defined by the 3rd Generation Partnership Project (3GPP) is called a New Radio (NR) system. To achieve high data rates, the implementation of 5G communication systems in the ultra-high frequency band (millimeter wave (mmW)) (e.g., 60 GHz) is considered. To reduce path loss of radio waves and increase the transmission distance of radio waves in the ultra-high frequency band, technologies such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antennas have been discussed and applied to NR systems for 5G communication systems. In addition, to improve the system network in 5G communication systems, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and interference cancellation are being developed. Furthermore, in 5G communication systems, advanced coding and modulation (ACM) schemes such as hybrid frequency shift keying (FSK) and quadrature amplitude modulation (FQAM) or sliding window superposition coding (SWSC) are being developed, as well as enhanced network access schemes such as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), or sparse code multiple access (SDMA).
[0003] The Internet is evolving from a human-centric network of connections through which humans create and consume information to the Internet of Things (IoT), in which distributed elements, such as objects, exchange and process information. The Internet of Everything (IoE) technology has also emerged, combining IoT technology with big data processing technology through connections to cloud servers. To implement IoT, technological elements are required, such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology. Therefore, technologies for inter-object connectivity, such as sensor networks, machine-to-machine (M2M) communication, or machine-type communication (MTC), have recently been researched. In the IoT environment, intelligent Internet technology (IT) services can be provided, collecting and analyzing data generated by connected objects and creating new value in people's lives. Through the convergence and integration of existing information technology (IT) with various industries, IoT can be applied to areas such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.
[0004] Therefore, various attempts have been made to apply 5G communication systems to IoT networks. For example, 5G communication, such as sensor networks, M2M communication, or MTC, is achieved through technologies such as beamforming, MIMO, or array antennas. The application of cloud RAN as a big data processing technology can also be considered an example of the integration of 5G and IoT technologies.
[0005] With the development of wireless communication systems, there is a need for methods to efficiently control the activation of cell groups in mobile communication systems that support carrier aggregation or dual connectivity. Summary of the Invention
[0006] [Technical Solution]
[0007] Methods and apparatus are provided for controlling the activation and deactivation of cell groups in a mobile communication system. Attached Figure Description
[0008] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings, in which:
[0009] Figure 1A A diagram showing the structure of a Long Term Evolution (LTE) system according to an embodiment of the present disclosure is provided;
[0010] Figure 1B A diagram illustrating the radio protocol architecture in an LTE system according to an embodiment of the present disclosure is shown;
[0011] Figure 1C A diagram showing the structure of a next-generation mobile communication system according to an embodiment of the present disclosure;
[0012] Figure 1D A diagram illustrating the radio protocol architecture of a next-generation mobile communication system according to an embodiment of the present disclosure is shown;
[0013] Figure 1E A diagram illustrates a process for providing services to a terminal in a next-generation mobile communication system by efficiently utilizing wide frequency bandwidth, according to an embodiment of the present disclosure.
[0014] Figure 1F A diagram illustrating the process by which a terminal switches from Radio Resource Control (RRC) idle mode to RRC connected mode in a next-generation mobile communication system according to an embodiment of the present disclosure;
[0015] Figure 1G A diagram illustrating the state transition or bandwidth portion (BWP) switching process for each bandwidth according to an embodiment of this disclosure is shown.
[0016] Figure 1H This is a diagram illustrating a discontinuous reception (DRX) configuration or DRX operation method for reducing terminal battery consumption according to an embodiment of this disclosure;
[0017] Figure 1I A diagram is shown illustrating a method for operating a dormant BWP in an active secondary cell (SCell) according to an embodiment of the present disclosure;
[0018] Figure 1J Embodiment 1 of a method for operating a dormant BWP in an activated SCell according to embodiments of the present disclosure is shown;
[0019] Figure 1K Embodiment 2 of a method for operating a dormant BWP in an activated SCell according to an embodiment of the present disclosure is shown;
[0020] Figure 1L Embodiment 3 of a method for operating a dormant BWP in an activated SCell according to an embodiment of the present disclosure is shown;
[0021] Figure 1M A diagram is shown illustrating Embodiment 4, which extends Embodiment 1, Embodiment 2, or Embodiment 3 of this disclosure and further applies it to a terminal in RRC disabled mode;
[0022] Figure 1N A diagram illustrates media access control (MAC) control information that transitions the state to an active state, a dormant state, or a disabled state according to an embodiment of this disclosure;
[0023] Figure 10A flowchart is shown of the first signaling process for configuring or releasing dual connectivity, or configuring, releasing, activating, resuming, suspending or deactivating a secondary cell group (SCG) configured with dual connectivity, according to an embodiment of this disclosure.
[0024] Figure 1P A flowchart is shown of a second signaling process for configuring or releasing dual connections, or configuring, releasing, activating, resuming, suspending or deactivating an SCG configured with dual connections, according to an embodiment of this disclosure.
[0025] Figure 1Q A flowchart is shown of a third signaling process for configuring or releasing dual connections, or configuring, releasing, activating, resuming, suspending or deactivating an SCG configured with dual connections, according to an embodiment of this disclosure.
[0026] Figure 1R A diagram illustrating the operation of a terminal according to an embodiment of the present disclosure is shown;
[0027] Figure 1S A block diagram illustrating the structure of a terminal according to an embodiment of the present disclosure is shown; and
[0028] Figure 1T A block diagram showing the configuration of a transmit-receive point (TRP) device in a wireless communication system according to an embodiment of the present disclosure is shown. Detailed Implementation
[0029] Other aspects will be set forth in part in the description which follows, and in part will be obvious from the description or may be learned by practice of the embodiments set forth in this disclosure.
[0030] According to embodiments of this disclosure, a method performed by a user equipment (UE) for controlling the activation of a cell group includes: receiving a radio resource control (RRC) message from a base station, the RRC message including configuration information indicating the number of temporary reference signals; receiving a media access control element (MAC CE) from the base station indicating the activation of a secondary cell (SCell); receiving temporary reference signals from the base station; measuring the temporary reference signals based on the MAC CE and the RRC message; and transmitting the measurement results regarding the temporary reference signals to the base station.
[0031] MAC CE can be included in the Physical Downlink Shared Channel (PDSCH).
[0032] MAC CE can include resource information for temporary reference signals.
[0033] MAC CE can include time offset information for a temporary reference signal.
[0034] The temporary reference signal can be measured within the first active downlink bandwidth portion (BWP).
[0035] According to embodiments of this disclosure, a method performed by a base station for controlling the activation of a cell group includes: transmitting a Radio Resource Control (RRC) message to a User Equipment (UE), the RRC message including configuration information indicating the number of temporary reference signals; transmitting a Media Access Control (MAC) control element (MAC CE) indicating activation of a secondary cell (SCell) to the UE; transmitting temporary reference signals to the UE; and receiving measurement results from the UE regarding the temporary reference signals, wherein the measurement results are based on the MAC CE and the RRC message.
[0036] MAC CE can be included in the Physical Downlink Shared Channel (PDSCH).
[0037] MAC CE can include resource information for temporary reference signals.
[0038] MAC CE can include time offset information for a temporary reference signal.
[0039] The temporary reference signal can be measured by the UE within the first active downlink bandwidth portion (BWP).
[0040] According to embodiments of this disclosure, a user equipment (UE) for controlling the activation of a cell group includes: a memory; a transceiver; and a processor connected to the memory and the transceiver and configured to: receive a radio resource control (RRC) message from a base station, the RRC message including configuration information indicating the number of temporary reference signals; receive a media access control element (MAC CE) from the base station indicating the activation of a secondary cell (SCell); receive temporary reference signals from the base station; measure the temporary reference signals based on the MAC CE and the RRC message; and transmit the measurement results regarding the temporary reference signals to the base station.
[0041] MAC CE can be included in the Physical Downlink Shared Channel (PDSCH).
[0042] MAC CE can include resource information for temporary reference signals.
[0043] MAC CE can include time offset information for a temporary reference signal.
[0044] The temporary reference signal can be measured within the first active downlink bandwidth portion (BWP).
[0045] [Invention Model]
[0046] Before proceeding with the detailed description below, it may be advantageous to define certain words and phrases used throughout this patent document. The terms “include” and “comprise” and their derivatives mean including but not limited to; the term “or” is inclusive, meaning and / or; the phrases “associated with” and “associated with” and their derivatives may mean including, contained within, interconnected with, including, contained within, connected to or connected to, linked to or coupled to, communicable with, cooperating with, intertwined, juxtaposed, proximate with, bound to or bound to, having, possessing the attributes of, etc.; and the term “controller” means any means, system, or part thereof that controls at least one operation, such means may be implemented in hardware, firmware, or software, or some combination of at least two of hardware, firmware, or software. It should be noted that the functionality associated with any particular controller can be centralized or distributed, whether local or remote.
[0047] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and implemented in a computer-readable medium. The terms "application program" and "program" mean one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of media accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data, as well as media that can store data and subsequently rewrite it, such as rewritable optical discs or erasable memory devices.
[0048] Throughout this patent document, definitions are provided for certain words and phrases, and those skilled in the art will understand that, in many instances (if not most), such definitions apply to the previous and future use of the words and phrases so defined.
[0049] The following discussion Figures 1A to 1TThe various embodiments described in this patent document to illustrate the principles of this disclosure are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or apparatus.
[0050] In the following description of embodiments of the present disclosure, embodiments will be described in detail with reference to the accompanying drawings. In the following description of embodiments of the present disclosure, descriptions of techniques well-known in the art and not directly related to the present disclosure are omitted. This is to clearly convey the spirit of the present disclosure by omitting unnecessary descriptions.
[0051] Throughout this disclosure, the expression "at least one of a, b, or c" indicates only a; only b; only c; both a and b; both a and c; both b and c; all of a, b, and c, or variations thereof.
[0052] Examples of terminals may include user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, multimedia system capable of performing communication functions, etc.
[0053] In this disclosure, the controller may also be referred to as a processor.
[0054] Throughout this specification, a layer (or layer device) may also be referred to as an entity.
[0055] For the same reasons, some elements in the accompanying drawings are enlarged, omitted, or shown schematically. Furthermore, the size of each element may not substantially reflect its actual size. In each drawing, the same or corresponding elements are indicated by the same reference numerals.
[0056] The advantages and features of this disclosure, as well as methods for achieving these advantages and features, will become apparent from the following detailed description of embodiments of this disclosure taken in conjunction with the accompanying drawings. However, this disclosure may be implemented in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art, and this disclosure is defined only by the appended claims. In this specification, the same reference numerals denote the same elements.
[0057] It will be understood that each box in the flowchart illustration, and combinations of boxes in the flowchart illustration, can be implemented by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, the instructions, executed by the processor of the computer or other programmable data processing apparatus, produce means for implementing the functions specified in the flowchart boxes. Since these computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can direct the computer or other programmable data processing apparatus to operate in a particular manner, the instructions stored in the computer-usable or computer-readable storage medium can produce an article of manufacture including instruction means for implementing the functions specified in the flowchart boxes. Since the computer program instructions can also be loaded into a computer or other programmable data processing apparatus, a series of operational steps can be executed on the computer or other programmable data processing apparatus to produce a computer-executable process; therefore, the instructions that execute on the computer or other programmable data processing apparatus can provide steps for implementing the functions specified in the flowchart boxes.
[0058] Additionally, each box may represent a code module, segment, or section that includes one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions mentioned in the boxes may not occur in the order shown. For example, two boxes shown consecutively may actually execute substantially simultaneously, or the boxes may sometimes execute in reverse order, depending on the functionality involved.
[0059] As used in embodiments of this disclosure, the term "~unit" refers to a software or hardware component, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), that performs certain tasks. However, "~unit" is not limited to software or hardware. The term "~unit" can be configured to reside in addressable memory or to operate one or more processors. Thus, for example, "~unit" can include components (such as software components, object-oriented software components, class components, and task components), processes, functions, attributes, programs, subroutines, code snippets, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided in components and "~units" can be combined into fewer components and "~units," or further divided into additional components and "~units." Furthermore, components and "~units" can be implemented to operate one or more central processing units (CPUs) in a device or secure multimedia card. Additionally, units in embodiments of this disclosure can include one or more processors.
[0060] In the following text, the terms used to identify access nodes, indicate network entities, indicate messages, indicate interfaces between network entities, and indicate various identification information are illustrative for ease of explanation. Therefore, the terminology used in this disclosure is not limited, and other terms representing objects with the same technical meaning may be used.
[0061] In the following text, for ease of explanation, some terms and names defined in the 3GPP LTE standard may be used. However, this disclosure is not limited to these terms and names and may also be applied to systems conforming to other standards. In this disclosure, for ease of explanation, Evolved Node B (eNB) may be used interchangeably with Next Generation Node B (gNB). That is, a base station described as eNB may refer to a gNB. Additionally, the term "terminal" may refer to other wireless communication devices, as well as mobile phones, NB-IoT devices, and sensors.
[0062] In next-generation mobile communication systems, carrier aggregation (CA) or dual connectivity (DC) can be used to provide terminals with services featuring high data rates and low transmission latency. However, a method is needed to prevent processing latency that may occur when carrier aggregation or dual connectivity is configured and activated in a terminal connected to the network, or when carrier aggregation or dual connectivity is used and then deactivated. Specifically, when a terminal keeps multiple cells active to use carrier aggregation or dual connectivity, the terminal must perform physical downlink control channel (PDCCH) monitoring on each of the multiple cells, thereby increasing the terminal's battery consumption. Conversely, when a terminal keeps multiple cells disabled to reduce battery consumption, data transmit / receive latency may occur due to the latency generated by activating multiple cells when using carrier aggregation or dual connectivity. In this disclosure, a cell can refer to a primary cell (PCell), a secondary cell (SCell) (e.g., an SCell configured in a primary cell group (MCG)), a primary-secondary cell (PSCell) (e.g., a PCell in a secondary cell group (SCG)), or an SCell (e.g., an SCell configured in an SCG)).
[0063] This disclosure provides novel sleep, pause, or disable modes that enable terminals connected to the network in RRC connectivity mode in next-generation mobile communication systems to quickly activate and deactivate carrier aggregation or dual connectivity. This disclosure provides methods for operating the new sleep (sleep, hibernation, or pause) modes on a per-bandwidth-part (BWP) basis (BWP level), per-cell basis, or per-cell-group (e.g., SCG) basis to quickly activate carrier aggregation or dual connectivity and reduce terminal battery consumption.
[0064] Figure 1AA diagram showing the structure of an LTE system according to an embodiment of the present disclosure is provided.
[0065] refer to Figure 1A The radio access network in the LET system may include next-generation base stations (hereinafter referred to as Evolved Node B (ENB), Node B, or base station) 1a-05, 1a-10, 1a-15, and 1a-20, Mobility Management Entity (MME) 1a-25, and Serving Gateway (S-GW) 1a-30. User terminals (hereinafter referred to as User Equipment (UE) or terminals) 1a-35 may access external networks via ENB 1a-05 to 1a-20 and S-GW 1a-30.
[0066] exist Figure 1A In this context, ENBs 1a-05 to 1a-20 can correspond to existing Node Bs in a Universal Mobile Telecommunications System (UMTS). The ENB connects to the UE 1a-35 via a radio channel and performs more complex functions than an existing Node B. In LTE systems, all user services based on real-time services such as VoIP are provided through shared channels, thus requiring devices to collect state information (such as the UE's buffer state, available transmit power state, channel state, etc.) and perform scheduling. ENBs 1a-05 to 1a-20 can handle these functions. A single ENB can typically control multiple cells. For example, to achieve a data rate of 100 Mbps, an LTE system can, for instance, use Orthogonal Frequency Division Multiplexing (OFDM) as the radio access technology in a 20 MHz bandwidth. Additionally, LTE systems can apply Adaptive Modulation and Coding (AMC), which determines the modulation scheme and channel coding rate based on the UE's channel state. The S-GW 1a-30 is the device that provides data bearers and can add or release data bearers under the control of the MME 1a-25. The MME1a-25 is a device that not only performs mobility management functions for the UE but also performs various control functions, and can be connected to multiple base stations.
[0067] Figure 1B A diagram illustrating the radio protocol architecture in an LTE system according to an embodiment of the present disclosure is shown.
[0068] refer to Figure 1B The radio protocols of the LTE system may include Packet Data Convergence Protocol (PDCP) 1b-05 and 1b-40, Radio Link Control (RLC) 1b-10 and 1b-35, and Media Access Control (MAC) 1b-15 and 1b-30 at the UE and ENB, respectively.
[0069] PDCP 1b-05 and 1b-40 can handle IP header compression / decompression, etc. The main functions of PDCP are summarized below. However, this disclosure is not limited to the examples below.
[0070] - Header compression and decompression: Robust header compression only (ROHC)
[0071] -Transmission of user data
[0072] -In the PDCP reconstruction process for RLC positive response mode (AM), upper-layer packet data units (PDUs) are transmitted sequentially.
[0073] - For split bearers in the DC (RLC AM only): route transmitted PDCP PDUs and reorder received PDCP PDUs.
[0074] - For RLC AM, repeat detection of low-level SDU during PDCP reconstruction.
[0075] - For RLC AM, retransmit PDCP SDU during handover, and for separate bearers in DC, retransmit PDCP PDU during PDCP data recovery.
[0076] - Encryption and decryption
[0077] - Timer-based SDU dropping in the uplink
[0078] RLC 1b-10 and 1b-35 can reconfigure PDCP PDUs to an appropriate size and can perform Automatic Repeat Request (ARQ) operations. The main functionalities of the RLC are summarized below. However, this disclosure is not limited thereto.
[0079] -Transmission of upper-layer PDUs
[0080] -ARQ (Error correction via ARQ (AM data transmission only))
[0081] - Cascading, segmentation, and reassembly of RLC SDUs (only for Negative Acknowledgment (UM) and AM data transmissions)
[0082] - Re-segmentation of RLC data PDUs (AM data transmission only)
[0083] - Reordering of RLC data PDUs (UM and AM data transfers only)
[0084] - Duplicate detection (only for UM and AM data transmissions)
[0085] - Protocol error detection (AM data transmission only)
[0086] -RLC SDU discard (only for UM and AM data transfers)
[0087] -RLC Reconstruction
[0088] MAC 1b-15 and 1b-30 can connect to multiple RLC layers configured in a UE, multiplex RLC PDUs into MAC PDUs, and demultiplex MAC PDUs from RLC PDUs. The main functions of the MAC are summarized below. However, this disclosure is not limited to the examples below.
[0089] - Mapping between logical channels and transmission channels
[0090] - Multiplexing MAC SDUs belonging to one or different logical channels into a transport block (TB) passed to the physical layer on the transport channel / Demultiplexing the MAC SDUs from the transport block passed from the physical layer on the transport channel
[0091] - Scheduling Information Report
[0092] - Hybrid Automatic Repeat Request (HARQ) (Error correction via HARQ)
[0093] Priority handling between logical channels in a UE
[0094] Priority handling among UEs via dynamic scheduling
[0095] -Multimedia Broadcast Multicast Service (MBMS) identifier
[0096] - Conveyor Format Selection
[0097] -filling
[0098] Physical (PHY) layers 1b-20 and 1b-25 can perform channel coding and modulation on upper-layer data, convert data into OFDM symbols, and transmit OFDM symbols via a wireless channel; or they can demodulate OFDM symbols received via a wireless channel, perform channel decoding on OFDM symbols, and pass OFDM symbols to higher layers. However, this disclosure is not limited to the following examples.
[0099] Figure 1C A diagram showing the structure of a next-generation mobile communication system according to an embodiment of the present disclosure is provided.
[0100] refer to Figure 1C The radio access network for next-generation mobile communication systems (hereinafter referred to as NR or 5G) may include next-generation base stations (e.g., new radio node B (NR gNB) or NR base stations) 1c-10 and a new radio core network (NRCN) 1c-05. User terminals (e.g., new radio user equipment (NR UE) or terminals) 1c-15 may access external networks 1c-20 through NR gNB 1c-10 and NR CN 1c-05.
[0101] exist Figure 1C In this context, the NR gNB 1c-10 corresponds to the Evolved Node B (eNB) of the existing LTE system. The NR gNB 1c-10 connects to the NR UE 1c-15 via a radio channel and can provide better service than existing eNBs. In next-generation mobile communication systems, all user services are provided through shared channels, thus requiring devices to collect state information (such as UE buffer state, available transmit power state, and channel state) and perform scheduling. The NR gNB 1c-10 is responsible for these functions. One NR gNB 1c-10 typically controls multiple cells. To achieve ultra-high-speed data transmission compared to current LTE, it can provide the maximum available bandwidth or greater, and beamforming can be applied using OFDM as the radio access technology. Additionally, AMC (Advanced Modulation Control) can be applied to determine the modulation scheme and channel coding rate based on the UE's channel state. The NR CN 1c-05 can perform functions such as mobility support, bearer configuration, and quality of service (QoS) configuration. The NR CN 1c-05 is a device that performs various control functions and performs mobility management functions for the UE, and can connect to multiple base stations. Furthermore, the next-generation mobile communication system can work with the existing LTE system, and the NR CN 1c-05 can connect to the MME 1c-25 via a network interface. The MME 1c-25 can connect to the eNB 1c-30, which serves as an existing base station.
[0102] Figure 1D A diagram illustrating the radio protocol architecture of a next-generation mobile communication system according to an embodiment of the present disclosure is shown.
[0103] refer to Figure 1D The radio protocols for next-generation mobile communication systems include NR Service Data Adaptation Protocol (SDAP) 1d-01 and 1d-45, NR Packet Data Convergence Protocol (PDCP) 1d-05 and 1d-40, NR RLC 1d-10 and 1d-35, and NR MAC 1d-15 and 1d-30 at the UE and NR base station, respectively.
[0104] The main functions of NR SDAP 1d-01 and 1d-45 may include some of the following functions. However, this disclosure is not limited to the following examples.
[0105] -Transmission of user plane data
[0106] Mapping between QoS streams and data radio bearers (DRBP for both DL and UL)
[0107] -Tag the QoS flow ID in both DL and UL packets.
[0108] - Reactive QoS flow mapping from UL SDAP PDU to DRB
[0109] Regarding the SDAP layer, for each PDCP layer device, each bearer, or each logical channel, the UE can receive configurations via Radio Resource Control (RRC) messages indicating whether to use the SDAP layer header or its functionality. When the SDAP header is configured, a single Non-Access Plane (NAS) QoS Responsive Indicator (NAS Responsive QoS) and a single AS QoS Responsive Indicator (AS Responsive QoS) in the SDAP header can instruct the UE to update or reconfigure the mapping information between uplink and downlink QoS flows and data bearers. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used for data processing priority, scheduling information, etc., to support smooth service.
[0110] The main functions of NR PDCP 1d-05 and 1d-40 may include some of the following functions. However, this disclosure is not limited to the following examples.
[0111] -Header compression and decompression: ROHC only
[0112] -Transmission of user data
[0113] - Sequential transmission of upper-layer PDUs
[0114] -Disordered transmission of upper-layer PDUs
[0115] -PDCP PDU reordering for reception
[0116] -Repetition detection of low-level SDUs
[0117] -PDCP SDU retransmission
[0118] - Encryption and decryption
[0119] - Timer-based SDU dropping in the uplink
[0120] The reordering function of an NR PDCP device may include reordering PDCP PDUs received from lower layers in sequence based on PDCP sequence numbers (SNs), and transmitting data to higher layers in the reordered order. Alternatively, the reordering function of an NR PDCP device may include transmitting directly regardless of order, reordering and recording lost PDCP PDUs, reporting the status of lost PDCP PDUs to the transmitter, and requesting retransmission of lost PDCP PDUs.
[0121] The main functions of NR RLC 1d-10 and 1d-35 may include some of the following functions. However, this disclosure is not limited to the following examples.
[0122] -Transmission of upper-layer PDUs
[0123] - Sequential transmission of upper-layer PDUs
[0124] -Disordered transmission of upper-layer PDUs
[0125] -ARQ (Error correction via ARQ)
[0126] Cascading, segmentation, and reassembly of RLC SDUs
[0127] - Resegmentation of RLC data PDUs
[0128] - Reordering of RLC data PDUs
[0129] -Duplicate detection
[0130] -Protocol error detection
[0131] -RLC SDU discard
[0132] -RLC Reconstruction
[0133] The sequential delivery function of an NR RLC device refers to the function of sequentially delivering RLC SDUs received from lower layers to higher layers. The sequential delivery function of an NR RLC device may include at least one of the following functions: reassembling and transmitting the received RLC SDUs when an original RLC SDU is divided into multiple RLC SDUs and received; reordering received RLC PDUs based on the RLC sequence number (SN) or PDCP sequence number (SN); reordering and recording lost RLC PDUs; reporting the status of lost RLC PDUs to the transmitter; requesting retransmission of lost RLC PDUs; transmitting only RLC SDUs preceding the lost RLC SDU sequentially to higher layers when a lost RLC SDU exists; transmitting all RLC SDUs received before the timer starts sequentially to higher layers even if a lost RLC SDU exists, even if a specific timer has expired; or transmitting all RLC SDUs received up to that time sequentially to higher layers even if a lost RLC SDU exists, even if a specific timer has expired.
[0134] Furthermore, through the out-of-order delivery function of the NR RLC layer, RLC PDUs can be processed in the order of reception (arrival order regardless of sequence number) and then transmitted to the PDCP device regardless of the order. It can also receive segments stored in a buffer or to be received, reconfigure them into a complete RLC PDU, process that RLC PDU, and then transmit it to the PDCP device. The NR RLC layer may not include concatenation functionality, and concatenation functionality can be implemented in the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.
[0135] The out-of-order delivery function of an NR RLC device may include the function of directly delivering RLC SDUs received from lower layers to higher layers regardless of order. The out-of-order delivery function of an NR RLC device may include at least one of the following functions: when an RLC SDU is divided into multiple RLC SDUs and received, reassembling and transmitting the received RLC SDUs, or storing the RLC SN or PDCP SN of the received RLC PDUs, and sorting and recording lost RLC PDUs.
[0136] NR MACs 1d-15 and 1d-30 can connect to multiple NR RLC layers configured in a UE, and the main functions of the NR MAC can include some of the following functions. However, this disclosure is not limited to the following examples.
[0137] - Mapping between logical channels and transmission channels
[0138] - MAC SDU multiplexing / demultiplexing
[0139] - Scheduling Information Report
[0140] -HARQ (Error correction via HARQ)
[0141] Priority handling between logical channels in a UE
[0142] Priority handling among UEs via dynamic scheduling
[0143] -MBMS identifier
[0144] - Conveyor Format Selection
[0145] -filling
[0146] The NR PHY layers 1d-20 and 1d-25 can perform channel coding and modulation on higher-layer data, convert data into OFDM symbols, and transmit OFDM symbols via a wireless channel; or they can demodulate OFDM symbols received via a wireless channel, perform channel decoding on OFDM symbols, and transmit OFDM symbols to higher layers.
[0147] Because next-generation mobile communication systems can use very high frequency bands, the frequency bandwidth can also be extremely wide. However, supporting all such wide bandwidths requires significant complexity and incurs high costs. Therefore, next-generation mobile communication systems can introduce the concept of Bandwidth Parts (BWPs), and multiple BWPs can be configured in a single cell (e.g., SpCell or SCell), with data being transmitted / received in one or more BWPs according to the instructions of the base station.
[0148] This disclosure provides a state transition method or a BWP handover method, and specific operations when a dormant BWP according to this disclosure is introduced, taking into account the state of the secondary cell (SCell) and multiple BWPs configured in the SCell. Furthermore, this disclosure provides a method for managing dormant modes and performing state transitions or BWP handover methods on a BWP-by-BWP (BWP level) basis. Additionally, this disclosure provides specific operations for BWPs based on the state of each SCell or the state or mode (e.g., active, disabled, or dormant) of each BWP.
[0149] According to embodiments of this disclosure, multiple BWPs can be configured for each DL or each UL in a cell (e.g., SPCell or PCell), and active BWPs (active DL or UL BWPs), dormant BWPs (dormant BWPs or dormant DL BWPs), or disabled BWPs (disabled or deactivated DL / UL BWPs) can be configured and operated via BWP switching. That is, data rates can be increased in a manner similar to carrier aggregation by switching a cell's DL or UL BWP to an active state. Additionally, battery consumption can be reduced by allowing the terminal to avoid performing PDCCH monitoring on the cell by switching DL BWPs to or to a dormant BWP. Furthermore, fast cell or BWP activation can be supported by allowing the terminal to perform channel measurements on DL BWPs and report the channel measurement results. Additionally, terminal battery consumption can be reduced by switching a DL (or UL) BWP in a cell to a disabled state. BWP-to-BWP state transition indications or BWP switching indications for each cell can be configured and indicated via RRC messages, MAC control elements (CE), or downlink control information (DCI) of the PDCCH. The dormant BWP can also be extended and applied to dual connectivity, for example, to PSCells in an SCG. According to embodiments of this disclosure, the dormant BWP can be extended and applied to the concept of cell group suspension or cell group deactivation. The base station can instruct a cell group (e.g., SCG) in a terminal configured for dual connectivity to suspend or deactivate the cell group, thereby suspending data transmission or reception, suspending PDCCH monitoring, or intermittently performing PDCCH monitoring within the indicated cell group at long intervals, thereby reducing the terminal's power consumption. Upon receiving an instruction to suspend or deactivate a cell group, the terminal can perform a channel measurement procedure in the indicated cell group and report the channel measurement results to the network (e.g., MCG or SCG), thereby supporting rapid activation of dual connectivity. For a cell group indicated to be suspended or deactivated, the terminal can perform a channel measurement procedure, or it can maintain and store the cell group configuration information instead of discarding or releasing it, or it can restore the cell group configuration information according to a cell group activation or recovery instruction in the network. For example, the configuration information of cell groups (e.g., configuration information or bearer information for each PDCP, RLC, or MAC layer) or the configuration information of each cell can be stored or maintained as is in the terminal. Upon receiving an instruction to restore or activate a cell group that was instructed to be suspended or deactivated, the terminal can restore, recover, or reapply the configuration information of the cell group, restore the bearer, restart data transmission or reception, restart PDCCH monitoring, execute channel measurement reports, and periodically reactivate the configured transmission resources.
[0150] Cell group configuration information, or previously configured cell group configuration information, or messages indicating cell group activation or deactivation (e.g., RRC messages or RRCReconfiguration), may include first channel measurement configuration information for quickly activating the cell group. To quickly activate the cell group and rapidly perform channel measurements in the cells within the cell group (e.g., PCell, PSCell, or SCell), the first channel measurement configuration information may be included and configured in the cell's configuration information. For example, to enable a base station to frequently transmit or transmit multiple channel measurement signals (which may be reference signals), the first channel measurement configuration information may include configuration information such as: the time period of the frequent channel measurement signals (e.g., radio resources), or transmission resource information (frequency or time transmission resources for the frequent channel measurement signals to be transmitted), or intervals or counts (the number of times the frequent channel measurement signals are transmitted), or timer values (the time for the frequent channel measurement signals to be transmitted), or time periods (the interval between the transmission of the frequent channel measurement signals (e.g., time units (time slots, subframes, or symbols)), or transmission resources, time periods, intervals, or times for reporting measurement results to the terminal. By using the first channel measurement configuration information, the base station can not only easily configure short reporting time periods (or transmission resources) for reporting channel measurement results to the terminal, but also configure transmission resources for channel measurement, enabling the base station to frequently transmit or transmit multiple channel measurement signals (or transmission resources) to support rapid channel measurement or multiple signal measurements.
[0151] Additionally, cell group configuration information, or previously configured cell group configuration information, or messages indicating cell group activation or restoration (e.g., RRC messages or RRCReconfiguration) may include second channel measurement configuration information for measuring signals of cells (PSCell, PCell, or SCell) within the cell group. This second channel measurement configuration information may include general channel measurement configuration information, such as transmission resources, time periods, time intervals, or counts for channel measurement signals, or transmission resources, time periods, or time intervals used for channel measurement reporting.
[0152] In embodiments of this disclosure, by applying first channel measurement configuration information or second channel measurement configuration information according to the following conditions, the terminal can measure the channel and report the measurement results to the base station.
[0153] -1> When the terminal receives a message indicating activation (or restoration) of a cell (PCell, PSCell, or SCell) or cell group (e.g., a PDCCH indicator, MAC control information (or MAC control element, hereinafter referred to as MACCE), or an RRC message),
[0154] --2> When the first channel measurement configuration information is configured in the terminal
[0155] ---3> The terminal can identify that the base station will frequently transmit many channel measurement signals based on the first channel measurement configuration information, and can temporarily measure many or frequent channel measurement signals based on the first channel measurement configuration information (e.g., until the time period configured in the first channel measurement configuration information (e.g., subframe, time slot, or symbol), or during a permitted (or predetermined) time period, or during a specific time period (e.g., when the timer is running), or until the first condition is met). Additionally, based on the time period or transmission resources configured in the first channel measurement configuration information, the terminal can report the channel measurement results until the time period configured in the first channel measurement configuration information (e.g., subframe, time slot, or symbol), or during a permitted (or predetermined) time period, or during a specific time period (e.g., when the timer is running), or until the first condition is met. Therefore, since the terminal can quickly measure frequent channel measurement signals and quickly report the results, the terminal can quickly activate (or restore) the cell (PCell, SCell, or PSCell) or quickly receive scheduling information. When a second channel measurement configuration is configured in the terminal after a time period (e.g., subframe, time slot, or symbol) configured in the first channel measurement configuration, or after an allowed (or predetermined) time period, or after a specific time period (e.g., when a timer expires), or after a first condition is met, the terminal can stop or release the application of the first channel measurement configuration information and can measure channel measurement signals according to the second channel measurement configuration information. For example, the terminal can fall back from the first channel measurement configuration information to the second channel measurement information, or it can apply the second channel information without applying the first channel measurement configuration information. Additionally, the terminal can report channel measurement results according to the time period or transmission resources configured in the second channel measurement configuration information. When the second channel measurement configuration information is not configured, the terminal may not perform channel measurements.
[0156] --2> Otherwise (when the first channel measurement configuration information is configured in the terminal)
[0157] ---3> When the second channel measurement configuration information is configured in the terminal, the terminal can measure the channel measurement signal according to the second channel measurement configuration information. Additionally, the terminal can report the channel measurement results according to the time period or transmission resources configured in the second channel measurement configuration information. When the second channel measurement configuration information is not configured, the terminal may not perform channel measurement.
[0158] In embodiments of this disclosure, the first channel measurement configuration information can be extended, configured, and used when a cell group (e.g., PSCell) is activated, when a cell group is restored, or when an SCell is activated, or when an RRC connection is restored in RRC disabled mode.
[0159] In embodiments of this disclosure, the first condition may be one of the following conditions. Hereinafter, when a first cell is activated, or when a cell group is activated, or when a cell group is restored, or when a terminal in RRC disabled mode restores connection during RRC connection restoration, an efficient condition is proposed as the first condition that the base station does not need to unnecessarily transmit many transmission resources or frequently transmit transmission resources. For example, the terminal may apply first channel measurement configuration information and may execute a channel measurement process or a channel measurement reporting process until one of the following conditions is met.
[0160] - The terminal may determine that the first condition is met under at least one of the following circumstances: the terminal successfully completes the random access procedure in a cell (e.g., PCell, SCell, or PSCell) or a cell in a cell group (e.g., PSCell or SCell); the terminal successfully completes the random access procedure and is allocated a first UL transmission resource; or the terminal is first indicated to the terminal with a UL transmission resource.
[0161] --For example, more specifically, when a terminal performs a contention-free random access (CFRA) procedure (e.g., when a pre-assigned preamble or terminal cell identifier (e.g., a cell radio network temporary identifier (C-RNTI)) is assigned)
[0162] ---The successful completion of the random access procedure can be determined under at least one of the following conditions, thus allowing the terminal to determine that the first condition is met: when the terminal transmits a pre-specified preamble and receives a Random Access Response (RAR) message, or when the terminal receives a PDCCH indication for RAR. Alternatively, the terminal can determine that the first condition is met when UL transport resources are first received after RAR reception.
[0163] --When a terminal performs a contention-based random access (CBRA) procedure (e.g., when a pre-assigned preamble or terminal cell identifier (e.g., C-RNTI) has not been assigned)
[0164] ---A successful random access procedure to the target base station can be determined under at least one of the following conditions, thus allowing the terminal to determine that a first condition is met: the terminal transmits a preamble (e.g., any preamble) to the cell, receives a RAR message, transmits message 3 (e.g., a handover completion message) using UL transmission resources allocated, included, or indicated in the RAR message, and receives a contention resolution MAC CE indicating contention has been resolved from the base station via message 4; or the terminal receives UL transmission resources via a PDCCH corresponding to the terminal's C-RNTI. In another method, when the size of the UL transmission resources allocated in the RAR message is sufficient, message 3 has been transmitted, and the terminal can also transmit UL data, it can be determined that UL transmission resources have been received for the first time, and the terminal can determine that the first condition is met. That is, upon receiving the RAR, the terminal can determine that UL transmission resources have been received for the first time and that the first condition is met.
[0165] -1> When a two-step random access procedure is configured or indicated in the terminal and is executed.
[0166] -1> Alternatively, when a 2-step random access procedure is not configured or indicated, but the terminal supports a 2-step random access procedure in the UE capabilities, the 2-step random access procedure is supported in the cell's system information, and information for the 2-step random access procedure (e.g., 2-step random access resources or thresholds for determining whether to perform the 2-step random access procedure) is broadcast in the system information. The terminal receives the system information, and when the signal strength is better or greater than the threshold broadcast in the system information, and therefore the terminal performs a 2-step random access procedure on the cell,
[0167] --2>When the two-step random access process is successfully completed, the terminal can determine that the first condition is met.
[0168] --2> In particular, a two-step random access procedure can be performed by using either the CBRA method or the CFRA method.
[0169] ---3> When the terminal performs a CBRA-based two-step random access procedure,
[0170] ----4> The terminal can transmit a preamble using transport resources for two-step random access (e.g., PRACH timing, transport resources configured by the base station via RRC messages, or transport resources broadcast in system information), and can transmit data (e.g., MsgA MAC PDU) using transport resources for data transmission (e.g., PUSCH timing). This data may include MAC control information (C-RNTI MAC CE), which includes the UE identifier (C-RNTI) or an RRC message (RRCReconfigurationComplete message or handover completion message).
[0171] ----4> The terminal can monitor the PDCCH scrambled by the UE identifier (C-RNTI) or the first identifier (MsgB-RNTI). The first identifier is obtained by the transmission preamble time or frequency.
[0172] ----4> When the terminal receives a PDCCH scrambled with the UE identifier, or is allocated DL transmission resources through the PDCCH, or receives MAC control information for timing adjustment (Timing Advance Command MAC CE) through the DL transmission resources,
[0173] -----5> The terminal can confirm that it has successfully completed the two-step random access process and that the first condition is met.
[0174] ----4> When the terminal does not receive the PDCCH scrambled by the first identifier (MsgB-RNTI), or is allocated DL transmission resources through the PDCCH, or receives a back-off RAR for the preamble transmitted by the terminal through DL transmission resources (i.e., when the base station receives the preamble but does not receive MsgA, and receives a back-off RAR for the transmitted MsgA through another transmission resource),
[0175] -----5> The terminal can transmit data (MsgA MAC PDU) through the transmission resources indicated in the rollback RAR.
[0176] -----5> The terminal can monitor the PDCCH scrambled by the UE identifier (C-RNTI).
[0177] -----5> When the terminal receives a PDCCH scrambled with the UE identifier, or is allocated UL transmission resources through the PDCCH, the terminal can determine that it has successfully completed the two-step random access procedure and can determine that the first condition is met.
[0178] ---3> When the terminal performs a CFRA-based two-step random access procedure,
[0179] ----4> The terminal can transmit a preamble using transport resources for two-step random access (e.g., PRACH timing, or transport resources specified by the base station via RRC messages), and can transmit data (e.g., MsgA MAC PDU) using transport resources for data transmission (e.g., PUSCH timing). This data may include MAC control information (C-RNTI MACCE), which includes the UE identifier (C-RNTI) or an RRC message (RRCReconfigurationComplete message or handover completion message).
[0180] ----4> The terminal can monitor the PDCCH scrambled by the UE identifier (C-RNTI) or the first identifier (MsgB-RNTI). The first identifier is obtained by the transmission preamble time or frequency.
[0181] ----4> When the terminal receives a PDCCH scrambled with the UE identifier, or is allocated DL transmission resources through the PDCCH, or receives MAC control information for timing adjustment (Timing Advance Command MAC CE) through the DL transmission resources,
[0182] -----5> The terminal can confirm that it has successfully completed the two-step random access process and that the first condition is met.
[0183] ----4> When the terminal receives a PDCCH scrambled with the first identifier (MsgB-RNTI), or is allocated DL transmission resources through the PDCCH, or receives a back-off RAR for the preamble transmitted by the terminal through the DL transmission resources (i.e., when the base station receives the preamble but does not receive MsgA, and receives a back-off RAR for the transmitted MsgA through another transmission resource),
[0184] -----5> The terminal can confirm that it has successfully completed the two-step random access process and that the first condition is met.
[0185] -----5> The terminal can transmit data (MsgA MAC PDU) through the transmission resources indicated in the rollback RAR.
[0186] -1> When the random access procedure begins or the preamble of the random access procedure is transmitted, the terminal can determine that the first condition is met.
[0187] -1> In another approach, when a two-step random access procedure is configured or indicated in the terminal, the terminal can determine that the first condition is met. For example, the terminal can determine that the first condition is met before the two-step random access procedure begins.
[0188] -1> In another method, the terminal can determine that the first condition is met when a two-step random access procedure is configured or indicated in the terminal via a message and the transmission resources (PUSCH) configured for data transmission during the two-step random access procedure are greater than a first threshold, or when a configuration value for timing adjustment (timing advance value) is included in the RRC message. The first threshold can be configured by the base station in the RRC message (e.g., RRCReconfiguration), broadcast in system information, or configured in the size of the data that the terminal must transmit. For example, the terminal can determine that the first condition is met before the two-step random access procedure begins. In another method, when the configuration value for timing adjustment (timing advance value) is included or the two-step random access procedure is configured in the RRC message, the terminal may not transmit a preamble and can directly transmit data using the configured transmission resources (e.g., transmission resources configured via the RRC message, or transmission resources indicated by the PDCCH of the target base station monitored by the terminal). Therefore, in the above cases, the terminal can determine that the first condition is met before the two-step random access procedure begins, or when transmitting data, or before transmitting data. In another method, when the configuration value for timing adjustment (timing advance value) is included or the two-step random access procedure is configured in the RRC message, the terminal may not transmit a preamble and may directly transmit data via the configured transport resources (PUSCH) (e.g., transport resources configured via the RRC message, or transport resources indicated by the PDCCH of the target base station monitored by the terminal). In this above case, the terminal may determine that the first condition is met when the configured transport resources (PUSCH) (e.g., transport resources configured in the RRC message, or transport resources indicated by the PDCCH of the target base station monitored by the terminal) are greater than a first threshold, or when the configuration value for timing adjustment (timing advance value) is included in the RRC message, or before the two-step random access procedure begins, or when data is transmitted, or before data is transmitted.
[0189] -1> When a terminal in RRC disabled mode transmits an RRCResumeRequest message and receives an RRCResume message (or an RRCSetup message) in response, the terminal can determine that the first condition is met.
[0190] When the first condition is met, a higher layer (e.g., the RRC layer) can indicate to a lower layer (e.g., the PDCP layer, RLC layer, MAC layer, or PHY layer) using an indicator. Alternatively, a lower layer (e.g., the PDCP layer, RLC layer, MAC layer, or PHY layer) can indicate to a higher layer (e.g., the RRC layer).
[0191] In this disclosure, the term “BWP” may be used without distinguishing between UL and DL, and may refer to each of the UL BWP and DL BWP depending on the context.
[0192] In this disclosure, the term “link” may be used without distinguishing between UL and DL, and may refer to each of UL and DL depending on the context.
[0193] In this disclosure, the term "cell" can refer to a PCell or SCell (e.g., an SCell configured in an MCG), a PSCell (e.g., a PCell in an SCG), or an SCell (e.g., an SCell configured in an SCG). In this disclosure, a dormant BWP can be configured or introduced for the SCell or PSCell of a terminal performing carrier aggregation or dual connectivity, and battery consumption of the terminal can be reduced by not monitoring the PDCCH in the dormant BWP. Additionally, in this disclosure, when channel measurements (e.g., channel state information (CSI) or channel quality information (CQI) measurements or reports) are performed and reported in the dormant BWP, or when beam measurements, beam tracking, or beam manipulation are performed and thus require data transmission, data transmission can be quickly initiated in the dormant BWP by switching to or activating a regular BWP. A dormant BWP can be unconfigured or applied to an SpCell (PCell in the MCG or PCell (or PSCell) in the SCG) or an SCell configured with a Physical Uplink Control Channel (PUCCH), in which the channel should continue to be monitored, feedback should be transmitted or received, or synchronization should be identified and maintained.
[0194] When a terminal is instructed to switch to a dormant BWP or to activate a dormant BWP via a PSCell for an SCell in an SCG, the terminal can perform channel measurement procedures on the dormant BWP in the SCell and report the measured channel measurement results via transmission resources of the PCell in the MCG (e.g., via the Physical Uplink Control Channel (PUCCH) transmission resources of the PCell) or transmission resources of the SCell configured with the PUCCH of the MCG (e.g., via PUCCH transmission resources). For each cell or each BWP, the terminal can configure which cell or which cell's BWP's channel measurement results to report via an RRC message.
[0195] When a terminal is instructed to switch to a dormant BWP or to activate a dormant BWP via a PSCell for an SCell in an SCG, the terminal can perform channel measurement procedures on the dormant BWP in the SCell and report the measured channel measurement results via the transmission resources of the PSCell in the SCG (e.g., via the PUCCH transmission resources of the PSCell) or via the transmission resources of the SCell configured with the PUCCH of the SCG (e.g., via the PUCCH transmission resources). For each cell or each BWP, the terminal can configure which cell or which cell's BWP's channel measurement results to report via an RRC message.
[0196] When a terminal is instructed to switch to a dormant BWP, activate a dormant BWP via a PCell for a PSCell or SCell in an SCG, or suspend a cell group (or PSCell) in an SCG (SCG suspended or cell group suspended), the terminal can perform channel measurement results on the BWP (configured via RRC message or the most recently activated BWP) or dormant BWP of the PSCell or SCell. The measured channel measurement results can be reported via the transmission resources of the PCell in the MCG (e.g., via the PUCCH transmission resources of the PCell), the transmission resources of the SCell configured with the PUCCH of the MCG (e.g., via the PUCCH transmission resources), or the transmission resources of the PSCell in the SCG (e.g., via the PUCCH transmission resources of the PSCell). For each cell or each BWP, the terminal can configure which cell or which cell's BWP's channel measurement results are reported via an RRC message.
[0197] This disclosure provides various implementations of operations based on DCI, MAC CE, or RRC messages in the PDCCH to operate the dormant BWP or cell group pause state for the terminal's SCell (SCell in the MCG when carrier aggregation is configured, or SCell in the SCG when dual connectivity is configured) or PSCell (PCell in the SCG when dual connectivity is configured).
[0198] A network or base station can configure SPCells (PCells and PSCells) and multiple SCells in a terminal. When a terminal communicates with one base station, an SPCell can refer to a PCell, and when a terminal communicates with two base stations (a primary base station and a secondary base station), an SPCell can refer to either the PCell of the primary base station or the PCell of the secondary base station. A PCell or PSCell can be the primary cell used when the terminal and base station communicate with each other at each MAC layer, and can refer to the cell that performs synchronization timing, performs random access, transmits HARQ ACK / NACK feedback via PUCCH transmission resources, and transmits and receives most control signals. The technique by which a base station increases transmission resources and increases UL or DL data transmission resources by operating multiple SCells together with an SPCell is called carrier aggregation or dual connectivity.
[0199] When a terminal is configured to have an SPCell and multiple SCells via RRC messages, the terminal can be configured to have a state or mode for each cell (PCell, PSCell, or SCell), or each SCell, or each SCell's BWP or cell group via RRC messages, MACCE, or DCI in PDCCH. The cell state or mode can be configured as active (activated) mode or active (activated) state, and disabled (deactivated) mode or disabled (deactivated) state. When a cell is in active mode or active state, this can mean that the terminal can transmit UL data to the base station or receive DL data from the base station in an active cell or in a BWP other than an activated BWP, an activated regular BWP, or an activated dormant BWP in an active cell. It can monitor the PDCCH to check the base station's indications, perform channel measurements on the DL of the active cell (or a BWP other than an activated regular BWP, an activated dormant BWP, or an activated dormant BWP in the cell), and periodically report measurement information to the base station. It can also periodically transmit pilot signals (Sound Reference Signals (SRS)) to the base station to enable the base station to perform UL channel measurements. Alternatively, based on the base station's indication to the active cell (e.g., PDCCH, MAC CE, or RRC message), the terminal can activate a BWP to a dormant BWP or switch a dormant BWP. When a dormant BWP is activated in an active cell, the terminal can perform channel measurement reporting and can execute the process of reporting channel measurement results without performing PDCCH monitoring in the cell.
[0200] In another approach, when the cell with the dormant BWP activated is an SCell, the terminal may not monitor the PDCCH, or may not receive DL data, or may perform channel measurements or measurement result reports, or may suspend configurable periodic transmission resources (e.g., type 1 periodic transmission resources (configurable uplink license type 1)), or may clear or initialize configurable periodic transmission resources (e.g., type 2 periodic transmission resources (configurable uplink license type 2)). Alternatively, the terminal may not transmit a sounding reference signal (SRS), or may not transmit UL data, or may not transmit a PUCCH (e.g., a scheduling request (SR) or a preamble for random access). However, when the cell that has activated the dormant BWP or indicated the cell group to be suspended is a PSCell, the terminal may not monitor the PDCCH, or may perform PDCCH monitoring at very long intervals, or may not receive DL data, or may perform channel measurements or measurement result reports, or may suspend configurable periodic transmission resources (e.g., type 1 periodic transmission resources (configurable uplink license type 1)), or may clear or initialize configurable periodic transmission resources (e.g., type 2 periodic transmission resources (configurable uplink license type 2)). Alternatively, the terminal may transmit SRS, or may not transmit UL data, or may transmit PUCCH (e.g., SRS or a preamble for random access), or may perform a random access procedure.
[0201] When the cell to which the BWP other than the dormant BWP is activated is an SCell, the terminal may monitor the PDCCH, receive DL data, perform channel measurements or report measurement results, restore configurable periodic transmission resources (e.g., type 1 periodic transmission resources (configurable uplink license type 1)), or configure or activate configurable periodic transmission resources (e.g., type 2 periodic transmission resources (configurable uplink license type 2)). Alternatively, the terminal may transmit SRS, transmit UL data, transmit PUCCH (e.g., SRS or preamble for random access), or perform a random access procedure.
[0202] When activated to a BWP other than a dormant BWP, or when the cell indicating cell group recovery (SCG recovery) is a PSCell, the terminal may perform PDCCH monitoring, receive DL data, perform channel measurements or report measurement results, recover configurable periodic transmission resources (e.g., type 1 periodic transmission resources (configurable uplink license type 1)), or configure or activate configurable periodic transmission resources (e.g., type 2 periodic transmission resources (configurable uplink license type 2)). Alternatively, the terminal may transmit SRS, transmit UL data, transmit PUCCH (e.g., SRS or preamble for random access), or perform a random access procedure.
[0203] When a cell is in disabled mode or disabled state, this can mean that because the terminal has disabled the BWP configured in the cell, or the configured BWP is not activated, or there is no activated BWP in the configured BWP, the terminal may not transmit data to / receive data from the base station, not monitor the PDCCH to check the base station's indication, not perform channel measurements, not perform measurement reports, and not transmit pilot signals.
[0204] Therefore, to activate a cell in disabled mode, the base station can first configure the frequency measurement configuration information in the terminal via RRC messages, and the terminal can perform cell or frequency measurements based on the frequency measurement configuration information. The base station can receive the terminal's cell or frequency measurement reports and then activate the disabled cell based on the frequency / channel measurement information. Therefore, when the base station activates carrier aggregation or dual connectivity and begins transmitting data to or receiving data from the terminal, significant latency occurs.
[0205] This disclosure provides methods for configuring or introducing a dormant BWP or a dormant state for a BWP in each active cell (e.g., an active SCell or an active PSCell) to reduce terminal battery consumption and quickly initiate data transmission or reception. Additionally, this disclosure provides methods for configuring or introducing a dormant BWP in each active cell. Furthermore, this disclosure provides methods for configuring or introducing a cell group state for each cell group as active, dormant, suspended, disabled, or resumed when dual connectivity is configured in the terminal. Additionally, this disclosure provides methods for executing cell group pause (SCG pause or cell group pause) or cell group resume (SCG resume or cell group resume) indications that indicate cell group state transitions.
[0206] In a dormant BWP or dormant BWP (dormant BWP in an activated SCell) in an activated cell, or when a dormant BWP is activated, the terminal may not transmit data to / receive data from the base station, may not monitor the PDCCH to check the base station's indication, or may not transmit pilot signals but can perform channel measurements. It can also report the measured frequency / cell / channel measurement results periodically or when events occur, depending on the base station configuration. Therefore, since the terminal does not monitor the PDCCH and transmit pilot signals in a dormant BWP in an activated cell, battery consumption can be reduced compared to a regular BWP in an activated cell (or a BWP other than a dormant BWP) or when a regular BWP in an activated cell (or a BWP other than a dormant BWP) is activated. Furthermore, unlike when the cell is deactivated, because the terminal performs channel measurement reports, the base station can quickly activate a regular BWP in the activated cell based on the measurement report or the measurement report of the dormant BWP in the activated cell, potentially enabling rapid use of carrier aggregation and reducing transmission latency.
[0207] Therefore, in this disclosure, when a cell is in an active mode or active state, this can mean that the terminal can transmit UL data to the base station or receive DL data from the base station in a cell in an active mode or in a BWP in an active cell other than an active BWP, an active regular BWP, or an active dormant BWP; can monitor the PDCCH to check the base station's indication; can perform channel measurements on the DL of a cell in an active mode or active state (or on a BWP other than an active BWP, an active regular BWP, or an active dormant BWP in the cell); can periodically report measurement information to the base station; and can periodically transmit pilot signals to the base station to enable the base station to perform UL channel measurements. Additionally, in this disclosure, when a cell is in an active mode or active state, this can mean that the terminal, in an active dormant BWP in an active cell, may not transmit UL data to the base station or receive DL data from the base station, or may not monitor the PDCCH to check the base station's indicators, but may perform channel measurements on the DL of the active dormant BWP in an active cell and may periodically report measurement information to the base station.
[0208] When the cell that has activated the dormant BWP or indicated the cell group to be suspended is a PSCell, the terminal may not monitor the PDCCH, or may perform PDCCH monitoring at very long intervals, or may not receive DL data, or may perform channel measurements or measurement result reports, or may suspend configurable periodic transmission resources (e.g., type 1 periodic transmission resources (configurable uplink license type 1)), or may clear or initialize configurable periodic transmission resources (e.g., type 2 periodic transmission resources (configurable uplink license type 2)). Alternatively, the terminal may transmit SRS, or may not transmit UL data, or may transmit PUCCH (e.g., SRS or a preamble for random access), or may perform a random access procedure.
[0209] In this disclosure, a dormant BWP can indicate the status of a BWP or can be used as a logical name to indicate a specific BWP. Therefore, a dormant BWP can be activated, deactivated, or switched. For example, an indication to switch a second BWP activated in a first cell to a dormant BWP, an indication to switch the first cell to a dormant or sleep mode, or an indication to activate a dormant BWP in the first cell can be interpreted as having the same meaning.
[0210] Furthermore, in this disclosure, a regular BWP can refer to any BWP configured in each cell of the terminal via RRC messages, excluding the dormant BWP. In a regular BWP, the terminal can transmit UL data to the base station or receive DL data from the base station, monitor the PDCCH to check the base station's indications, perform channel measurements on the DL and periodically report measurement information to the base station, and periodically transmit pilot signals (SRS) to the base station to cause the base station to perform UL channel measurements. Additionally, a regular BWP can indicate a first active BWP, a default BWP, a first active BWP activated from dormancy, or an initial BWP.
[0211] In one approach, among the BWPs configured in each cell of the terminal, only one dormant BWP can be configured for DL. Alternatively, in another approach, among the BWPs configured in each cell of the terminal, only one dormant BWP can be configured for UL or DL.
[0212] In this disclosure, the state of a cell group can be configured as active, suspended, or disabled. The state of a cell group can be indicated by an indicator of the DCI in a bitmap or PDCCH, or by MAC control information, or by an indicator of an RRC message. In embodiments of this disclosure, when the cell group state is indicated as active, the terminal can store cell group configuration information configured or indicated in an RRC message (e.g., an RRCReconfiguration message, an RRCSetup message, or an RRCResume message), and can apply this configuration information to the terminal, or restore or recover the cell group configuration information. The terminal can monitor the PDCCH according to the configuration of the RRC messages in the configured SCell, PCell, or PSCell in the cell group, or can receive DL data, or can perform channel measurements or measurement result reports, or can restore configured periodic transmission resources (e.g., type 1 periodic transmission resources (configured uplink license type 1)), or can configure or activate configured periodic transmission resources (e.g., type 2 periodic transmission resources (configured uplink license type 2)). Alternatively, the terminal may transmit SRS, or UL data, or PUCCH (e.g., SRS or a preamble for random access), or perform a random access procedure.
[0213] When the cell group status is indicated as suspended or disabled, the terminal may store the cell group configuration information configured or indicated in RRC messages (e.g., RRCReconfiguration, RRCSetup, or RRCResume messages), and may not discard the configuration information but may stop applying it. The terminal may not monitor the PDCCH according to the configuration of the RRC messages in the configured SCell, PCell, or PSCell of the cell group, or may perform PDCCH monitoring at long intervals, or may not receive DL data, or may perform channel measurements or measurement result reports, or may suspend configured periodic transmission resources (e.g., Type 1 periodic transmission resources (configured uplink license type 1)), or may clear or initialize configured periodic transmission resources (e.g., Type 2 periodic transmission resources (configured uplink license type 2)). Alternatively, the terminal may transmit SRS, or may not transmit UL data, or may transmit PUCCH (e.g., SRS or a preamble for random access), or may perform a random access procedure.
[0214] When the cell group status is indicated as disabled or when the release of cell group configuration information is indicated, the terminal can release or discard the cell group configuration information configured or indicated in an RRC message (e.g., RRCReconfiguration message, RRCSetup message, or RRCResume message).
[0215] Figure 1E A diagram illustrates a process for providing services to a terminal in a next-generation mobile communication system by efficiently utilizing wide frequency bandwidth, according to an embodiment of the present disclosure.
[0216] refer to Figure 1E It will describe how next-generation mobile communication systems can efficiently use extremely wide frequency bandwidth to provide services to terminals with different capabilities (or categories) and reduce battery consumption.
[0217] A single cell served by a base station can serve an extremely wide frequency band, as in 1e-05. However, to provide services to terminals with different capabilities, a base station can divide the wide frequency band into multiple BWPs and manage them as a single cell.
[0218] First, the initially activated terminal can search the entire frequency band provided by the service provider (Public Land Mobile Network (PLMN)) in units of resource blocks (e.g., 12 resource blocks (RBs)). The terminal can begin monitoring the primary synchronization sequence (PSS) / secondary synchronization sequence (SSS) (1e-10) across the entire system bandwidth in units of resource blocks. When the terminal detects a PSS / SSS signal (1e-01 or 1e-02) while monitoring the PSS / SSS in units of resource blocks, the terminal can read and decode the PSS / SSS signal to identify the boundary between subframes and radio transmission resource frames (radio frames). Therefore, subframes can be distinguished in 1ms increments, and the terminal can synchronize the DL signal with the base station. A resource block (RB) can be defined as a two-dimensional unit with a specific frequency resource and a specific time resource. For example, the time resource can be defined in 1ms increments, and the frequency resource can be defined as 12 subcarriers (1 carrier × 15kHz = 180kHz). Upon synchronization, the terminal can identify the Control Resource Set (CORESET) information and Initial Access BWP information (1e-15 and 1e-20) by recognizing the Master System Information (MIB) or Minimum System Information (MSI). CORESET information refers to the location of time / frequency transmission resources used to transmit control signals from the base station, and indicates, for example, the location of resources used to transmit the PDCCH channel. In other words, CORESET information indicates where to transmit the first system information (System Information Block 1 (SIB1)) and can indicate which frequency / time resources to use for transmitting the PDCCH. When the terminal receives the first system information, it can identify information about the initial BWP. When the terminal completes synchronization of the DL signal with the base station and can receive control signals, it can perform a random access procedure in the initial BWP of the cell where it is camped, request RRC connection configuration, receive RRC messages, and perform RRC connection configuration.
[0219] In RRC connection configuration, multiple BWPs can be configured for a single cell (Pcell, PSCell, Spcell, or SCell). Within a single cell, multiple BWPs can be configured for a DL and multiple BWPs can be configured for a UL.
[0220] Multiple BWPs can be indicated by a BWP identifier and configured to be used as the initial BWP, or the default BWP, or the first active BWP, or the dormant BWP, or the first active BWP activated from dormancy.
[0221] The initial BWP can be used as a cell-specific BWP, one per cell, and can also be used by terminals that access the cell first to configure the connection in the cell through a random access procedure, or by terminals that configure the connection to perform a synchronization BWP. Additionally, the base station can configure an initial DL BWP to be used in the DL and an initial ULBWP to be used in the UL for each cell. Configuration information about the initial BWP can be broadcast in the first system information (System Information 1 (SIB1)) indicated by CORESET, and the base station can reconfigure the connection in the access terminal via RRC messages. In both the UL and DL, the initial BWP can be used by being designated as BWP identifier 0. That is, all terminals accessing the same cell can use the same initial BWP by designating the same initial BWP as the same BWP identifier #0. This is because, when performing a random access procedure, the base station can transmit RAR messages in the initial BWP that can be read by all terminals, thus facilitating the CBRA procedure.
[0222] The first active BWP can be configured differently for each terminal (UE-specific) and can be indicated by a BWP identifier from multiple BWPs. A first active BWP can be configured for each of the DL and UL, and each of the first active DL BWP and the first active UL BWP can be configured as a BWP identifier. When multiple BWPs are configured in a cell, the first active BWP can be used to indicate which BWP should be activated and used first. For example, when a PCell or PSCell and multiple SCells are configured in a terminal, and multiple BWPs are configured in each PCell, PSCell, or SCell, if a PCell, PSCell, or SCell is activated, the terminal can activate and use the first active BWP from the multiple BWPs configured in the PCell, PSCell, or SCell. For DL, the first active DL BWP can be activated and used, and for UL, the first active UL BWP can be activated and used.
[0223] When a terminal receives an instruction to activate a disabled cell or BWP via RRC messages, MAC control information, or DCI, it can perform the following operations: The terminal activates the first active DL BWP (or the BWP configured or indicated via RRC messages) by switching the currently active or active DL BWP, or the terminal activates the first active ULBWP (or the BWP configured or indicated via RRC messages) by switching the currently active or active UL BWP. Additionally, this operation can be performed when the terminal receives an instruction to switch a cell or BWP to a dormant state or to activate a dormant BWP via RRC messages, MAC control information, or DCI. This is because when a cell or BWP is activated, the first active DL BWP will be activated by switching the currently active or active DL BWP (or the BWP configured or indicated via RRC messages), or the first active DL BWP will be activated by switching the UL BWP (or the BWP configured or indicated via RRC messages). Therefore, even when performing channel measurement reporting in a dormant state, the base station can effectively use carrier aggregation only when frequency / channel measurement and reporting should be performed for the first active DL / UL BWP.
[0224] A default BWP can be configured differently for each terminal (UE-specific) and can be indicated by a BWP identifier from multiple BWPs. In embodiments of this disclosure, the default BWP can be configured only for DL. The default BWP can be used as the BWP to which an active BWP from multiple DL BWPs will fall back after a specific time. For example, a BWP disable timer can be configured for each cell or each BWP via an RRC message, and the BWP disable timer can be started or restarted when data transmission / reception occurs in an active BWP other than the default BWP, or when an active BWP switches to another BWP. When the BWP disable timer expires, the terminal can fall back from the active DL BWP in the cell or switch to the default bandwidth. A handover can refer to the process of deactivating the currently active BWP and activating the BWP that indicates the handover, and the handover can be triggered by an RRC message, MAC control information (MAC CE), or L1 signaling (DCI in PDCCH). Switching can be triggered in response to an indication of a BWP to be switched or activated, and the BWP can be indicated by a BWP identifier (e.g., 0, 1, 2, 3, or 4).
[0225] The reason for using the default BWP only for DL applications is that the terminal is instructed by the base station to fall back to the default BWP after a specific time for each cell (e.g., DCI in PDCCH), thus facilitating base station scheduling. For example, when a base station configures the default BWP of a terminal accessing a cell as the initial BWP, the base station can continue transmitting scheduling instructions only in the initial BWP after a specific time. When the default BWP is not configured in the RRC message, the initial BWP can be considered the default BWP, and the terminal can fall back to the initial BWP when the BWP disable timer expires.
[0226] In another approach, to increase the implementation flexibility of the base station, a default BWP can be defined and configured for the UL and used just like the default BWP for the DL.
[0227] A dormant BWP refers to a BWP in dormant mode within an activated cell, or a dormant BWP (a dormant BWP in an activated SCell). When a dormant BWP is activated, the terminal may not transmit / receive data from the base station, may not monitor the PDCCH to check for base station indications, or may not transmit pilot signals but can perform channel measurements. It can also periodically report the measured frequency / cell / channel measurement results, depending on the base station configuration, or when events occur. Therefore, since the terminal does not monitor the PDCCH and transmit pilot signals in a dormant BWP within an activated cell, battery consumption can be reduced compared to a regular BWP (or a BWP other than a dormant BWP) in an activated cell, or when a regular BWP (or a BWP other than a dormant BWP) in an activated cell is activated. Furthermore, unlike when a cell is deactivated, because the terminal performs channel measurement reports, the base station can quickly activate a regular BWP in an activated cell based on the measurement reports or the measurement reports from a dormant BWP in an activated cell, thereby enabling rapid use of carrier aggregation and reducing transmission latency.
[0228] When a terminal operates a BWP in an activated cell as a dormant BWP, or when an activated BWP in an activated cell is a dormant BWP, or when switching to a dormant BWP in a cell, or when the base station indicates via DCI, MAC CE, or RRC messages in the PDCCH to switch a BWP in an activated cell from a dormant BWP to a regular BWP (or a BWP other than a dormant BWP), or when the base station indicates to switch or convert an active BWP from a dormant BWP to a regular BWP, or when the base station indicates to switch, convert, or activate an active BWP from a dormant BWP to a regular BWP (e.g., a first active BWP activated from dormancy), the first active BWP (or the first active non-dormant BWP or a BWP configured or indicated via an RRC message) that is activated from a dormant state or from a dormant BWP can be a BWP that the base station wants to activate by switching the current or activated BWP in the activated cell according to the indication, or a BWP that is to be activated from a dormant state configured in the RRC message.
[0229] Figure 1F This illustration shows the process by which a terminal switches from RRC idle mode to RRC connected mode in a next-generation mobile communication system according to an embodiment of this disclosure. (Reference) Figure 1F This section describes how to configure multiple BWPs and configure a default BWP, a first active BWP, or a dormant BWP.
[0230] A cell served by a base station can serve an extremely wide frequency band. First, the terminal can search the entire frequency band provided by the service provider (PLMN) in units of certain resource blocks (e.g., 12 resource blocks (RBs)). The terminal can then begin monitoring the PSS / SSS across the entire system bandwidth in units of resource blocks. When the terminal detects a PSS / SSS signal while monitoring the PSS / SSS in units of resource blocks, it can read and decode the PSS / SSS signal to identify the boundary between subframes and radio transmission resource frames (radio frames). Upon completion of synchronization, the terminal can read the system information of the cell it is currently camped on. That is, the terminal can identify CORESET information by recognizing the MIB or MSI, and can identify the initial BWP information (1f-01 and 1f-05) by reading the system information. CORESET information refers to the location of time / frequency transmission resources used to transmit control signals from the base station, and can indicate, for example, the location of resources used to transmit PDCCH channels.
[0231] When the terminal completes the synchronization of the DL signal with the base station and can receive control signals, the terminal can perform a random access procedure in the initial BWP, receive RAR, request RRC connection configuration, receive RRC messages, and perform RRC connection configuration (1f-10, 1f-15, 1f-20, 1f-25, and 1f-30).
[0232] When basic RRC connection configuration is completed, the base station can transmit an RRC message inquiring about the terminal's capabilities to identify UE capabilities (UECapabilityEnquiry) (1f-35). Alternatively, the base station can inquire about the terminal's capabilities from the Mobility Management Entity (MME) or the Access and Mobility Management Function (AMF) to identify UE capabilities. This is because the MME or AMF may have already stored the terminal's capability information when it previously accessed the terminal. When the base station does not have the desired UE capability information, it can request UE capabilities from the terminal. When the terminal reports its UE capabilities, it can report the following as UE capabilities to the base station: whether the terminal supports dormant BWPs for SCells in each cell group (MCG or SCG); or whether the terminal supports implementations 1, 2, 3, or 4 of this disclosure; or whether the terminal supports dormant BWPs for PSCells in each cell group; or whether the terminal supports cell group pause or resume procedures for PSCells in each cell group; or the number of cell groups supported. In addition, during the RRC connection recovery process, the terminal may report at least one of the following as UE capabilities to the base station via the RRC Resume message: whether the terminal can store and restore the configuration information of the SCell in the MCG or the SCell or PSCell in the SCG; or whether the terminal can discard the configuration information; or whether the terminal can reconfigure a part of the configuration information; or whether the terminal can activate the configuration information.
[0233] The reason a base station sends an RRC message to a terminal to identify the terminal's capabilities is to identify the terminal's capabilities, such as how many frequency bands the terminal can read or the frequency band area the terminal can read. After identifying the terminal's capabilities, the base station can configure an appropriate BWP in the terminal. When the terminal receives an RRC message inquiring about its capabilities, in response, it can indicate the bandwidth range supported by the terminal or the bandwidth range supported in the current system bandwidth by means of the offset from the reference center frequency, or directly indicate the start and end points of the supported frequency bandwidth, or indicate it by the center frequency and bandwidth (1f-40).
[0234] BWPs can be configured via RRCSetup, RRCResume (1f-25), or RRCReconfiguration (1f-45, 1f-70, and 1f-85) messages configured through the RRC connection. RRC messages can include configuration information for PCell, PSCell, or multiple cells, and multiple BWPs can be configured for each cell (PCell, PSCell, or SCell). When multiple BWPs are configured for each cell, multiple BWPs to be used in the DL of each cell can be configured. In the case of Frequency Division Duplex (FDD) systems, multiple BWPs to be used in the UL of each cell can be configured separately from the DL BWPs. In the case of Time Division Duplex (TDD) systems, multiple BWPs to be used in both the DL and UL of each cell can be configured.
[0235] The information used to configure the BWP for each cell (PCell, PSCell, or SCell) may include some of the following information.
[0236] 1) DL BWP configuration information for the community
[0237] --Initial DL BWP Configuration Information
[0238] --Multiple BWP configuration information and a corresponding BWP identifier (ID) for each BWP.
[0239] --Initial state configuration information for the cell or DL BWP (e.g., active, dormant, or disabled).
[0240] --The BWP identifier indicating the first active DL BWP
[0241] --Indicates the BWP identifier of the default BWP
[0242] --Configuration information for PDCCH monitoring of each BWP, such as CORESET information, search space resource information, PDCCH transmission resources, time period or subframe number information.
[0243] -- BWP identifier indicating a dormant BWP
[0244] --BWP identifier indicating the first active BWP activated from dormancy.
[0245] --BWP disables timer configuration and timer values
[0246] 2) UL BWP configuration information for the community
[0247] --Initial UL BWP Configuration Information
[0248] --Multiple BWP configuration information and a corresponding BWP identifier (ID) for each BWP.
[0249] --Initial state configuration information for the cell or UL BWP (e.g., active, dormant, or disabled).
[0250] --The BWP identifier indicating the first active UL BWP
[0251] --Configuration information related to the transmission resources used to perform channel measurements and report the results in a dormant BWP or a BWP other than a dormant BWP (e.g., PUCCH transmission resource information for PCell, PUCCH SCell, or PSCell).
[0252] In embodiments of this disclosure, the configured initial BWP, default BWP, or first active BWP may be used for the following reasons, and may be operated as follows for various purposes.
[0253] The initial BWP can be used as a cell-specific BWP, one per cell, and can also be used by terminals that access the cell first to configure the connection in the cell through a random access procedure, or by terminals that configure the connection to execute a synchronization BWP. Additionally, the base station can configure an initial DL BWP for use in the DL and an initial ULBWP for use in the UL for each cell. Configuration information about the initial BWP can be broadcast in the first system information SIB1 indicated by CORESET, and the base station can reconfigure the connection in the access terminal via RRC messages. In each of the UL and DL, the initial BWP can be used by being designated as BWP identifier 0. That is, all terminals accessing the same cell can use the same initial BWP by designating the same initial BWP as the same BWP identifier #0. This is because, when performing a random access procedure, the base station can transmit RAR messages in the initial BWP that can be read by all terminals, thus facilitating the CBRA procedure.
[0254] The first active BWP can be configured differently for each terminal (UE-specific) and can be indicated by a BWP identifier from multiple BWPs. A first active BWP can be configured for each of the DL and UL, and each of the first active DL BWP and the first active UL BWP can be configured as a BWP identifier. When multiple BWPs are configured in a cell, the first active BWP can be used to indicate which BWP should be activated and used first. For example, when a PCell or PSCell and multiple SCells are configured in a terminal, and multiple BWPs are configured in each PCell, PSCell, or SCell, if a PCell, PSCell, or SCell is activated, the terminal can activate and use the first active BWP from the multiple BWPs configured in the PCell, PSCell, or SCell. For DL, the first active DL BWP can be activated and used, and for UL, the first active UL BWP can be activated and used.
[0255] When a terminal receives an instruction via RRC message, MAC control information, or DCI in the PDCCH to activate a cell or BWP in a disabled or dormant state, or an instruction to switch from a disabled or dormant BWP to a regular BWP, or an instruction to activate a disabled or dormant BWP, the terminal can perform the following operations: The terminal activates a first active DL BWP (or a BWP configured or indicated via an RRC message) by switching the currently active or active DLBWP, or the terminal activates a first active UL BWP (or a BWP configured or indicated via an RRC message) by switching the currently active or active UL BWP. Additionally, when a terminal receives an instruction via RRC message, MAC control information, or DCI in the PDCCH to switch an activated cell or BWP to a dormant state, or an instruction to switch to a dormant BWP, or an instruction to activate a dormant BWP, the terminal can switch or activate a BWP to a dormant BWP, or put a BWP into dormancy.
[0256] Switching to a dormant state or a dormant BWP, or activating a dormant BWP, can refer to performing the following operations while in a dormant state. That is, without performing PDCCH monitoring, the terminal can perform measurement channel operations and report the results to the base station in a DL BWP (or a dormant BWP). In another approach, when an activated SCell or BWP is activated or switched to a regular BWP, since the first active DL BWP will be activated by switching DL BWPs and the first active DL BWP will be activated by switching UL BWPs, the dormant BWP can be configured as the first active DL or UL BWP or the default BWP. The default BWP can be configured differently for each terminal (UE-specific) and can be indicated by a BWP identifier from multiple BWPs. In embodiments of this disclosure, the default BWP can be configured only for DL. The default BWP can be used as the BWP to which an activated BWP from multiple DL BWPs will fall back after a specific time. For example, a BWP disable timer can be configured for each cell or each BWP via an RRC message. The BWP disable timer can be started or restarted when data transmission / reception occurs in an active BWP other than the default BWP, or when an active BWP switches to another BWP. When the BWP disable timer expires, the terminal can fall back from the active DL BWP in the cell or switch to the default bandwidth. A handover can refer to the process of disabling the currently active BWP and activating the BWP that indicates the handover, and handover can be triggered by RRC messages, MAC control information (MAC CE), or L1 signaling (DCI in PDCCH). Handover can be triggered in response to an indication to switch to or activate a BWP, and the BWP can be indicated by a BWP identifier (e.g., 0, 1, 2, 3, or 4).
[0257] The reason for using the default BWP only for DL applications is that the terminal is instructed by the base station to fall back to the default BWP after a specific time for each cell (e.g., DCI in PDCCH), thus facilitating base station scheduling. For example, when a base station configures the default BWP of a terminal accessing a cell as the initial BWP, the base station can continue transmitting scheduling instructions only in the initial BWP after a specific time. When the default BWP is not configured in the RRC message, the initial BWP can be considered the default BWP, and the terminal can fall back to the initial BWP when the BWP disable timer expires.
[0258] In another approach, to increase the implementation flexibility of the base station, a default BWP can be defined and configured for the UL and used just like the default BWP for the DL.
[0259] A dormant BWP refers to a BWP in dormant mode within an activated cell, or a dormant BWP (a dormant BWP in an activated SCell). When a dormant BWP is activated, the terminal may not transmit / receive data from the base station, may not monitor the PDCCH to check for base station indications, or may not transmit pilot signals but can perform channel measurements. It can also periodically report the measured frequency / cell / channel measurement results, depending on the base station configuration, or when events occur. Therefore, since the terminal does not monitor the PDCCH and transmit pilot signals in a dormant BWP within an activated cell, battery consumption can be reduced compared to a regular BWP (or a BWP other than a dormant BWP) in an activated cell, or when a regular BWP (or a BWP other than a dormant BWP) in an activated cell is activated. Furthermore, unlike when a cell is deactivated, because the terminal performs channel measurement reports, the base station can quickly activate a regular BWP in an activated cell based on the measurement reports or the measurement reports from a dormant BWP in an activated cell, thereby enabling rapid use of carrier aggregation and reducing transmission latency.
[0260] When a terminal operates a BWP in an activated cell as a dormant BWP, or when the activated BWP in the activated cell is a dormant BWP, or when switching to a dormant BWP in a cell, or when the base station indicates via DCI, MAC CE, or RRC messages in the PDCCH to switch a BWP in the activated cell from a dormant BWP to a regular BWP (or a BWP other than a dormant BWP), or when the base station indicates to switch or convert an active BWP from a dormant BWP to a regular BWP, or when the base station indicates to switch, convert, or activate an active BWP from a dormant BWP to a regular BWP (e.g., a first active BWP activated from dormancy), the first active BWP activated from dormancy (or the first active non-dormant BWP) can be a BWP that the base station indicates to switch from a BWP in the activated cell, or a first active BWP activated from dormancy as configured in the RRC message.
[0261] In this disclosure, when the first BWP is switched to the second BWP, this can be interpreted as either activating the second BWP or deactivating the activated first BWP and activating the second BWP.
[0262] In the RRC Setup message, RRC Resume message (1f-25), or RRC Reconfiguration message (1f-45) of the RRC connection configuration, a state transition timer can be configured, enabling the terminal itself to perform state transitions even if it does not receive an indication from the base station via RRC messages, MAC control information, or DCI in the PDCCH. For example, a cell deactivation timer (SCellDeactivationTimer) can be configured for each cell, and when the cell deactivation timer expires, the cell can transition to a disabled state. According to embodiments of this disclosure, by configuring a DL (or UL) BWP hibernation timer (DLBWPHibernationTimer or ULBWPHibernationTimer) for each cell or each BWP of each cell and by configuring a cell hibernation timer (SCellHibernationTimer) for each cell, when the cell hibernation timer or DL (or UL) BWP hibernation timer expires, the cell or DL (or UL) BWP can transition to a hibernation state or switch to a hibernating BWP. For example, when the cell sleep timer or DL (or UL) BWP sleep timer expires, the activated cell or DL (UL) BWP can transition to a sleep state or switch to a sleep BWP, while a disabled or sleepy cell or DL (or UL) BWP may not transition to a sleep state or sleep BWP. The BWP sleep timer can be started when an instruction to switch or activate a BWP is received via RRC message, MAC CE, or PDCCH DCI, or it can be stopped when an instruction to switch to a sleep BWP, a sleep instruction, or an instruction to activate a sleep BWP is received via RRC message, MAC CE, or PDCCH DCI. According to embodiments of this disclosure, for each cell or DL (or UL) BWP, a sleep cell or DL (or UL) sleep BWP can be transitioned to a disabled state by configuring a sleep cell deactivation timer (dormantSCellDeactivationTimer) or a sleep state or DL (or UL) sleep BWP deactivation timer (dormantDLDeactivationTimer or dormantULDeactivationTimer). When the dormant cell deactivation timer or the dormant state or DL (or UL) dormant BWP deactivation timer expires, only the dormant cell or DL (or UL) dormant BWP can be switched to the disabled state, while the active or disabled cell or DL (or UL) BWP can remain in the disabled state.The hibernation timer for a dormant BWP can be started upon receiving an instruction to switch to a dormant BWP, or a hibernation instruction, or an instruction to activate a dormant BWP via an RRC message, MAC CE, or PDCCH DCI. Alternatively, it can be stopped upon receiving an instruction to deactivate or activate a BWP or cell via an RRC message, MAC CE, or PDCCH DCI, or an instruction to activate a dormant BWP (e.g., a BWP other than the one configured via RRC). When both a cell deactivation timer (SCellDeactivationTimer) (or DL (or UL) BWP hibernation timer) and a cell hibernation timer (SCellHibernationTimer) (or DL (or UL) hibernation BWP deactivation timer) are configured together, the cell hibernation timer (SCellHibernationTimer) (or DL (or UL) hibernation BWP hibernation timer) can be prioritized. In other words, when a cell hibernation timer (SCellHibernationTimer) (or DL (or UL) BWP hibernation timer) is configured, the cell or DL (or UL) BWP can remain active even if the cell deactivation timer (SCellDeactivationTimer) (or DL (or UL) hibernation BWP deactivation timer) expires. In other words, when a cell hibernation timer (or DL (or UL) BWP hibernation timer) is configured, the cell or DL (or UL) BWP can transition from an active state to a hibernation state or switch to a hibernation BWP upon timer expiration. Furthermore, a hibernation cell, or a cell or BWP that has transitioned to hibernation due to the expiration of its BWP deactivation timer, can gradually transition back to a disabled state. Therefore, when a cell hibernation timer or BWP hibernation timer is configured, the cell deactivation timer or hibernation BWP deactivation timer does not affect the state transition of the cell or DL (or UL) BWP, and even if the cell deactivation timer or hibernation BWP deactivation timer expires, the cell or DL (or UL) BWP does not need to directly transition to a disabled state when a cell hibernation timer or BWP hibernation timer is configured.
[0263] When the cell deactivation timer (or DL (or UL)BWP sleep timer) is not configured in the RRC message, the terminal can assume that the cell deactivation timer (or DL (or UL)BWP sleep timer) is configured to an infinite value.
[0264] In the RRC Setup message, RRC Resume message (1f-25), or RRC Reconfiguration message (1f-45, 1f-70, and 1f-85) of the RRC connection configuration, frequency measurement configuration information and frequency measurement interval configuration information can be configured, and frequency measurement object information can be included. In the RRC Setup message, RRC Resume message (1f-25), or RRC Reconfiguration message (1f-45, 1f-70, and 1f-85) of the RRC connection configuration, functions for reducing terminal power consumption (power saving mode) can be configured. Additionally, along with the power reduction functions, the following configuration information can be configured: such as discontinuous reception (DRX) period, offset, on-time continuation period (the interval at which the terminal should monitor the PDCCH) or time information, or short-term information or time information from the base station indicating when to monitor or detect the PDCCH before the on-time continuation period in the DRX period. When a function to reduce terminal power consumption is configured in the RRC message, the terminal can configure the DRX period and detect the Wake-Up Signal (WUS) during the interval configured to monitor the base station's PDCCH before the call continuation period. Additionally, the base station can use the DCI in the PDCCH of the WUS to indicate to the terminal whether to skip (or not perform) or perform PDCCH monitoring in the immediately following call continuation period. The terminal should always monitor the PDCCH during the call continuation period, and when the base station uses the WUS to indicate to the terminal that PDCCH monitoring should not be performed during the call continuation period, the terminal's battery consumption can be reduced.
[0265] Once RRC connection configuration is complete, the terminal can configure multiple BWPs (1f-55 and 1f-80) according to the instructions configured in the RRC message. To reduce battery consumption, one or a few of the configured BWPs can be activated. For example, the base station can indicate which BWP to activate. The base station can indicate BWP activation via RRC messages, MAC control information (MAC CE), or L1 signaling (PHY layer control signaling, such as DCI in PDCCH) to indicate a switch from the initial access BWP to a new BWP. In another approach, new bitmap information can be defined in the DCI in the PDCCH, and this new bitmap information can indicate whether to activate a regular BWP (or a BWP other than a dormant BWP), activate a dormant BWP, or deactivate a BWP. In yet another approach, bitmap information can indicate whether to activate a regular BWP (e.g., the first active BWP to be activated from dormancy), activate a dormant BWP, switch to a dormant BWP, or perform a BWP handover. Since many new users can connect in the initial access BWP, it may be more advantageous in terms of scheduling to allocate a new BWP and manage the connected users individually. This is because the initial access BWP is not configured for each terminal, but can be shared and used by all terminals. To reduce signaling overhead, the default BWP can be dynamically indicated via MAC control information, L1 signaling, or system information.
[0266] RRC messages (RRCSetup, RRCResume (1f-25), or RRCReconfiguration (1f-45, 1f-70, and 1f-85)) may include cell group configuration information. This cell group configuration information may include some of the following: It may indicate the status, procedures, and application or release of configuration information for each cell group.
[0267] - Indicates the cell group identifier (e.g., cell group identifier or index) within the cell group.
[0268] - An indicator that indicates the status of a cell group (e.g., active, paused, or disabled).
[0269] - An indicator indicating the status of a cell group (e.g., an indicator for pausing (or deactivating) a cell group (e.g., the Cellgroup(SCG) Pause Indicator) or an indicator for resuming a cell group (e.g., the Cellgroup(SCG) Resume Indicator)).
[0270] - Indicators that trigger the corresponding protocol layer (e.g., SDAP layer, PDCP layer, RLC layer, or MAC layer) process based on the indicator indicating the cell group status (e.g., PDCP reconstruction indicator, PDCP data recovery indicator, indicator to trigger a new process, RLC reconstruction indicator, MAC layer reset indicator, or MAC layer partial reset indicator).
[0271] - When an indicator includes the status of a paused (or disabled) cell group, second DRX configuration information (e.g., monitoring interval, active time period (connection continuation time) length, time period, or offset) can be configured to perform PDCCH monitoring at long intervals in the PSCell of the cell group. For example, when a terminal receives an indicator to pause a cell group, the terminal can reduce its power consumption by applying the second DRX configuration information to perform PDCCH monitoring at long intervals. In another approach, when a terminal receives an indicator to pause a cell group, the terminal can activate the DL BWP or switch to the dormant BWP of the PSCell of the cell group by applying the BWP configuration information of the cell group's PSCell, and terminal operations can be performed in the cell where the dormant BWP is activated, according to this disclosure. Additionally, when a terminal receives an indicator to pause a cell group, the terminal can disable all SCells configured in the cell group. In another approach, when the terminal receives an indication to suspend the cell group, the terminal can activate or switch to a dormant BWP in a SCell configured with a dormant BWP in a PSCell within the cell group. The terminal can then perform terminal operations in a cell where the dormant BWP is activated, or deactivate a SCell without a dormant BWP. In yet another approach, when the terminal receives an indication to suspend the cell group in an RRC message, the terminal can activate, deactivate, put the BWP to sleep, or activate a dormant BWP on each SCell according to the indication or configuration information for each SCell in the cell group included in the RRC message. Alternatively, before or after receiving the indication to suspend the cell group, the terminal can activate, deactivate, put the BWP to sleep, or activate a dormant BWP on each SCell in the cell group via an indication (e.g., a bitmap) in the PDCCH, MAC control information, or an RRC message.
[0272] - Configuration information related to the transmission resources used to perform channel measurements and report the results in a dormant BWP or a BWP other than a dormant BWP (e.g., PUCCH transmission resource information for PCell, PUCCH SCell, or PSCell).
[0273] When an indicator includes a state indication for restoring (or activating) a cell group, first DRX configuration information (e.g., monitoring interval, active time period (connection continuation time) length, time period, or offset) can be configured to re-perform PDCCH monitoring in the cell group's PSCell. Alternatively, the terminal can restore and apply the first DRX configuration information stored for the cell group. For example, when the terminal receives an indication to restore a cell group, it can perform PDCCH monitoring by applying the first DRX configuration information received from or stored in an RRC message to restore data transmission or reception. In another approach, when the terminal receives an indication to restore a cell group, it can activate or switch a DL BWP in the cell group's PSCell to a BWP other than a dormant BWP (e.g., a BWP configured in an RRC message) by applying the BWP configuration information of the PSCell in the cell group, and can perform terminal operations in cells where a regular BWP (other than a dormant BWP) is activated, according to this disclosure. Alternatively, when the terminal receives an indication to restore a cell group, it can trigger a random access procedure in the cell group's PSCell by applying random access configuration information (random access transport resource information for preamble transmission (time or frequency transport resources) or specified preamble information) received from or stored in the RRC message. In another approach, when the terminal receives an indication to restore a cell group, if the RRC message includes random access configuration information (random access transport resource information for preamble transmission (time or frequency transport resources) or specified preamble information), the terminal can trigger a random access procedure (e.g., a CFRA procedure) in the cell group's PSCell by applying the random access configuration information. When the RRC message does not include random access configuration information indicating the restoration or activation of a cell group (random access transport resource information for preamble transmission (time or frequency transport resources) or specified preamble information), the terminal can trigger a random access procedure (e.g., a CFRA procedure) in the cell group's PSCell, or it can trigger a random access procedure based on system information (CBRA or two-step random access). If the terminal stores random access configuration information (random access transport resource information for preamble transmission (time or frequency transport resources) or specified preamble information) before receiving an indication to restore the cell group, the terminal may release or discard the random access configuration information. Alternatively, the terminal may perform PDCCH monitoring in the indicated or configured cell group or cell, and may trigger and execute a random access procedure based on the indication in the PDCCH.
[0274] - When an indicator indicating the state of restoring (or activating) a cell group is included, or when the terminal receives an indicator indicating the restoration of a cell group, the terminal can activate all SCells configured in the cell group. In another approach, when the terminal receives an indicator indicating the restoration of a cell group, the terminal can activate or switch to a BWP in an SCell other than a dormant BWP (e.g., a BWP configured in an RRC message or a first active BWP), where the SCell is one of the SCells configured in the cell group that has a dormant BWP configured. Terminal operations can be performed in cells where BWPs other than the dormant BWP are activated, or SCells without a dormant BWP can be activated, according to this disclosure. In yet another approach, when the terminal receives an indicator indicating the restoration of a cell group in an RRC message, the terminal can perform activation, deactivation, dormancy, or activation of a dormant BWP on each SCell according to the indicator or configuration information of each SCell in the cell group included in the RRC message. Alternatively, before or after the terminal receives the indication to restore the cell group, the terminal may perform activation, deactivation, hibernation, or activation of a hibernating BWP on each SCell in the cell group via an indication (e.g., a bitmap), MAC control information, or RRC message in the PDCCH.
[0275] - Add an indicator for cell group configuration.
[0276] -Release the indicator for cell group configuration
[0277] - Security configuration information (security key information, or cell group security information, or additional information (e.g., SK counter)).
[0278] - Indicators that indicate handover, cell group addition, or cell group modification (e.g., the ReconfigurationWithSync indicator or the mobilitycontrolInfo indicator).
[0279] - When an RRC message (e.g., an RRCReconfiguration message) includes an indicator for suspending a cell group, it may omit indicators indicating handover, cell group addition, or cell group modification (e.g., the ReconfigurationWithSync indicator or the mobilitycontrolInfo indicator). Conversely, when an RRC message includes an indicator for restoring a cell group or configuration information for configuration, it may include indicators indicating handover, cell group addition, or cell group modification (e.g., the ReconfigurationWithSync indicator or the mobilitycontrolInfo indicator). This is because when a cell group is restored, the connection to the cell group should be re-established, thus requiring synchronization, receiving system information, or, if necessary, performing a random access procedure.
[0280] The following describes a dormant BWP in a next-generation mobile communication system newly provided by this disclosure, and the terminal operation in each BWP when switching or transforming each BWP will be described in detail.
[0281] Figure 1G A diagram illustrating the state transition or BWP switching process for each bandwidth according to an embodiment of this disclosure is shown.
[0282] refer to Figure 1G Each cell (e.g., SCell or PSCell) in each cell group of the terminal can have its BWP activated to a regular BWP (1g-01), activated to a dormant BWP (1g-02), or deactivated (1g-03). The terminal can activate or deactivate a regular BWP or a dormant BWP based on the instructions of the RRC message, MAC control information, or DCI configuration information in the PDCCH.
[0283] According to this disclosure, the following operations may be performed due to instructions or configuration in one of the following situations: state transition (activation, deactivation, or hibernation) operation for each BWP in the cell, or operation to activate a regular BWP, or activate a hibernating BWP, or activate a first active BWP activated from hibernation, or deactivate a regular BWP or a hibernating BWP.
[0284] - When the BWP status of a cell is configured via an RRC message, or when the BWP of each cell is configured via an RRC message and a dormant BWP is configured in the cell, or when the first active BWP is configured as a dormant BWP, the cell can be started by switching to a dormant BWP or activating a dormant BWP, and operations can be performed in the dormant BWP.
[0285] -When a cell activation, deactivation, or hibernation MAC CE is received.
[0286] - When a MAC CE is received indicating to activate or deactivate a regular BWP, or the first active BWP activated from hibernation, or a hibernation BWP.
[0287] - When a DCI is received in the PDCCH of a regular BWP, the first active BWP activated from dormancy, or a dormant BWP, indicating activation or deactivation of the regular BWP.
[0288] - When no cell sleep timer is configured in the active cell and the configured cell deactivation timer expires.
[0289] - When a BWP sleep timer is not configured in the active BWP and a configured BWP state deactivation timer (e.g., bwpInactivityTimer) expires.
[0290] In addition, the state transition operation or hibernation BWP operation method according to this disclosure may have the following characteristics.
[0291] - In an SPCell (PCell or PSCell) (or the cell's DL BWP or UL BWP), a dormant BWP may not be configured, and only a regular BWP may be configured and always active. Since the SPCell synchronizes and transmits and receives master control signals, its connection to the base station is lost when its BWP is dormant or disabled and operates as a dormant BWP; therefore, the SPCell should always remain active.
[0292] - When a PUCCH is configured in a SCell or SCell's BWP, a dormant state or dormant BWP may not be configured. In this case, since another cell should be sending feedback such as HARQ ACK / NACK via PUCCH, an active state or regular BWP should be activated and used.
[0293] - Due to this characteristic, the cell deactivation timer or BWP sleep timer can be excluded from SPCell or SPCell BWP and SCell or SCell BWP configured with PUCCH, and can run only in other SCells.
[0294] - The cell or BWP hibernation timer (SCellHibernationTimer) can take precedence over the cell or BWP state deactivation timer (SCellDeactivationTimer). When a value is set as a timer value via an RRC message, the same value can be applied to all cells. Alternatively, the base station can set different timer values for each SCell or each BWP by considering the characteristics of each cell or each BWP.
[0295] - When a cell or BWP is not indicated as active or dormant in an RRC message, the cell or BWP can initially operate essentially in a disabled state.
[0296] In this disclosure, the term "UL" may refer to a UL BWP, and the term "DL" may refer to a DL BWP. This is because only one active or dormant BWP can be operated for each UL or each DL.
[0297] The following describes a method for operating state transitions or switching on a BWP-by-BWP (BWP level) basis according to this disclosure to quickly activate carrier aggregation or dual connectivity and reduce terminal battery consumption.
[0298] In this disclosure, if referenced Figure 1F As described above, a BWP can be configured for each cell in an RRCSetup, RRCReconfiguration, or RRCResume message. The RRC message can include configuration information about PCell, PSCell, or multiple cells, and multiple BWPs can be configured for each cell (PCell, PSCell, or SCell). When multiple BWPs are configured for each cell in an RRC message, multiple BWPs to be used in the DL of each cell can be configured. In the case of an FDD system, multiple BWPs to be used in the UL of each cell can be configured separately from the DL BWPs. In the case of a TDD system, multiple BWPs to be used in both the DL and UL of each cell can be configured.
[0299] According to the first method in the information configuration method for BWP configuration for each cell (PCell, PSCell, or SCell), the BWP configuration information may include one or more of the following information. In the BWP configuration information, new indicators may be introduced into the BWP to indicate whether each BWP is a regular BWP (e.g., a BWP that can operate in an active or disabled state or can be configured in an active or disabled state) or a dormant BWP (e.g., a BWP that can operate in a dormant state or can be configured in a dormant state). For example, a BWP identifier may be used to indicate whether each BWP is a dormant BWP.
[0300] 1) DL BWP configuration information for each cell
[0301] --Initial DL BWP Configuration Information
[0302] --Multiple BWP configuration information and a corresponding BWP identifier (ID) for each BWP.
[0303] --Initial DL state configuration information for the cell (e.g., active, dormant, or disabled state).
[0304] --The BWP identifier indicating the first activity DL BWP
[0305] --Indicates the BWP identifier of the default BWP
[0306] --The BWP identifier in the BWP configuration information that indicates a hibernating BWP, or a 1-bit indicator for each BWP that indicates a hibernating BWP.
[0307] When the first active DL BWP is configured as a dormant BWP, the first active UL BWP may also need to be configured as a dormant BWP.
[0308] --BWP disables timer configuration and timer values
[0309] --First activate the BWP identifier from the dormant BWP
[0310] 2) UL BWP configuration information for each cell
[0311] --Initial UL BWP Configuration Information
[0312] --Multiple BWP configuration information and a corresponding BWP identifier (ID) for each BWP.
[0313] --Initial UL state configuration information for the cell (e.g., active, dormant, or disabled).
[0314] --The BWP identifier indicating the first active UL BWP
[0315] --The BWP identifier in the BWP configuration information that indicates a hibernating BWP, or a 1-bit indicator for each BWP that indicates a hibernating BWP.
[0316] When the first active DL BWP is configured as a dormant BWP, the first active UL BWP may also need to be configured as a dormant BWP.
[0317] --First activate the BWP identifier from the dormant BWP
[0318] The following methods can be used to configure SRS-related configuration information.
[0319] 1) Implementation method for configuring SRS
[0320] - The first SRS configuration information indicates the SRS configuration information for a BWP other than a regular BWP, or a dormant BWP, or a PSCell (or SCell) in a cell group where the cell group is not suspended, or a PSCell (or SCell) in a cell group where the cell group is restored or activated (e.g., an indicator indicating whether it is an SRS configuration information, time period, offset, or dormant BWP for SRS transmission resources).
[0321] - The second SRS configuration information indicates the SRS configuration information for a BWP used for a dormant BWP, or a PSCell (or SCell) in a cell group where the cell group is suspended or deactivated, or a PSCell (or SCell) in a cell group where the cell group has not been restored (e.g., an indicator of whether it is an SRS configuration information for SRS transmission resources, a time period, an offset, or a dormant BWP).
[0322] The first and second SRS configuration information can be distinguished based on indicators that specify whether the SRS configuration information is for a dormant BWP or PSCell (or SCell) in a cell group that has been suspended or deactivated. For example, the first and second SRS configuration information can be distinguished by the indicator value, by whether the indicator value is configured, or by the presence or absence of the indicator value. Alternatively, the first and second SRS configuration information can be distinguished by defining different names for them.
[0323] - In Embodiment 1 of this disclosure, the second SRS configuration information can always be configured when a dormant BWP (e.g., the dormant BWP identifier in the DL BWP configuration information) is configured in the serving cell (PSCell or SCell), or when a cell group pause is indicated, supported, or configured. Alternatively, when a dormant BWP (e.g., the dormant BWP identifier in the DL BWP configuration information) is configured in the serving cell (PSCell or SCell), or when a cell group pause is indicated, supported, or configured, an indicator indicating whether it is the first SRS configuration information or the second SRS configuration information can be configured. For example, when the dormant BWP identifier is configured in the DL BWP configuration information, or when a cell group pause is indicated, supported, or configured, the second SRS configuration information may have to be configured in each UL BWP configuration information. For example, when a dormant BWP identifier is configured in the DL BWP configuration information, or when cell group suspension is indicated, supported, or configured, it may be necessary to configure a second SRS configuration information for the ULBWP or a UL BWP with the same BWP identifier as the DL dormant BWP in the UL BWP configuration information. Alternatively, in the case of TDD or unpaired spectrum, when a dormant BWP identifier is configured in the DL BWP configuration information, it may be necessary to configure a second SRS configuration information for the UL BWP or a UL BWP with the same BWP identifier as the DL dormant BWP in the UL BWP configuration information.
[0324] For example, in Embodiment 1 of this disclosure, when the DL BWP is switched or activated to a BWP (or a regular BWP) other than a dormant BWP in an activated cell, or when no cell group suspension is indicated, or when a cell group resumption is indicated, the terminal can apply first SRS configuration information in the UL BWP of the activated cell (SCell or PSCell), and can transmit SRS based on the SRS transmission resources, time period, or offset corresponding to the first SRS configuration information. When the DL BWP is switched or activated to a dormant BWP in an activated cell, or when a cell group suspension is indicated, or when the cell group is not in an active state (or in a disabled or suspended state), the terminal can apply second SRS configuration information in the UL BWP of a cell (PSCell or SCell) in a suspended or deactivated cell group, and can transmit SRS based on the SRS transmission resources, time period, or offset corresponding to the second SRS configuration information. For example, the SRS transmission resources configured for a dormant BWP in the second SRS configuration information can be configured to be much smaller than the SRS transmission resources configured for a regular BWP in the first SRS configuration information, or the SRS transmission resource time period configured in the second SRS configuration information can be configured to be much longer than the SRS transmission resource time period configured in the first SRS configuration information, thereby improving the power saving effect of the terminal in a dormant BWP or suspended cell group. For example, the SRS transmission time period of the second SRS configuration information can be configured to be equal to or greater than 100ms. In another method, when the DL BWP is activated to a dormant BWP, or when a cell group is indicated to be suspended, or when the cell group is not in an active state (or in a disabled or suspended state), if the second SRS configuration information is not configured, the terminal can apply the first SRS configuration information to the ULBWP and can transmit SRS based on the SRS transmission resources, time period, or offset corresponding to the first SRS configuration information. In another approach, if the second SRS configuration information is not configured, the terminal may not transmit SRS when the DL BWP is activated to a dormant BWP, when the cell group is indicated to be paused, or when the cell group is not active (or is disabled or paused).
[0325] 2) Implementation method for configuring SRS
[0326] - In Embodiment 2 of this disclosure, the first SRS configuration information and the second SRS configuration information may be included as one SRS configuration information, and may be configured respectively as SRS configuration information (e.g., SRS transmission resources, time period or offset) for a regular BWP, or a BWP other than a dormant BWP, or a PSCell (or SCell) in a cell group where the cell group is not suspended, or a PSCell (or SCell) in a cell group where the cell group is restored or activated, and as SRS configuration information (e.g., SRS transmission resources, time period or offset) for a dormant BWP, or a PSCell (or SCell) in a cell group where the cell group is suspended or deactivated, or a PSCell (or SCell) in a cell group where the cell group is not restored.
[0327] - The first SRS configuration information indicates the SRS configuration information of a regular BWP or a BWP other than a dormant BWP, or a PSCell (or SCell) in a cell group that is not suspended, or a PSCell (or SCell) in a cell group that has been restored or activated (e.g., an indicator of whether it is an SRS configuration information, time period, offset, or dormant BWP for SRS transmission resources).
[0328] - The second SRS configuration information indicates the SRS configuration information for a BWP used for a dormant BWP, or a PSCell (or SCell) in a cell group that is suspended or deactivated, or a PSCell (or SCell) in a cell group that has not been restored (e.g., an indicator of whether it is an SRS configuration information for SRS transmission resources, a time period, an offset, or a dormant BWP).
[0329] - In Embodiment 2 of this disclosure, the second SRS configuration information can always be configured when a dormant BWP (e.g., the dormant BWP identifier in the DL BWP configuration information) is configured in the serving cell (PSCell or SCell), or when a cell group pause is indicated, supported, or configured. Alternatively, when a dormant BWP (e.g., the dormant BWP identifier in the DL BWP configuration information) is configured in the serving cell (PSCell or SCell), or when a cell group pause is indicated, supported, or configured, an indicator indicating whether it is the first SRS configuration information or the second SRS configuration information can be configured. For example, when a dormant BWP identifier is configured in the DL BWP configuration information, the second SRS configuration information may need to be configured in each UL BWP configuration information. For example, when a dormant BWP identifier is configured in the DL BWP configuration information, or when a cell group pause is indicated, supported, or configured, the second SRS configuration information may need to be configured in the UL BWP configuration information for the UL BWP or a UL BWP with the same BWP identifier as the DL dormant BWP. In another approach, in the case of TDD or unpaired spectrum, when a dormant BWP identifier is configured in the DL BWP configuration information, or when cell group suspension is indicated, supported, or configured, it may be necessary to configure a second SRS configuration information for the UL BWP or a UL BWP with the same BWP identifier as the DL dormant BWP in the UL BWP configuration information.
[0330] ---For example, in Embodiment 2 of this disclosure, when the DL BWP is switched or activated to a BWP (or a regular BWP) other than a dormant BWP in the activated cell, or when no cell group suspension is indicated, or when a cell group resumption is indicated, the terminal can apply first SRS configuration information in the UL BWP of the activated cell, and can transmit SRS based on the SRS transmission resources, time period, or offset corresponding to the first SRS configuration information. When the DL BWP is switched or activated to a dormant BWP in the activated cell, or when a cell group suspension is indicated, or when the cell group is not in an active state (or in a disabled or suspended state), the terminal can apply second SRS configuration information in the UL BWP of the activated cell, and can transmit SRS based on the SRS transmission resources, time period, or offset corresponding to the second SRS configuration information. For example, the SRS transmission resources configured in the second SRS configuration information can be configured to be much smaller than the SRS transmission resources configured in the first SRS configuration information, or the SRS transmission resource time period configured in the second SRS configuration information can be configured to be much longer than the SRS transmission resource time period configured in the first SRS configuration information, thereby improving the power saving effect of the terminal in the dormant BWP. For example, the SRS transmission time period in the second SRS configuration information can be configured to be equal to or greater than 10ms. In another method, when the DL BWP is activated to the dormant BWP, or when the cell group is indicated to be paused, or when the cell group is not in an active state (or in a disabled or paused state), if the second SRS configuration information is not configured, the terminal can apply the first SRS configuration information to the ULBWP and can transmit SRS based on the SRS transmission resources, time period, or offset corresponding to the first SRS configuration information. In another approach, if the second SRS configuration information is not configured, the terminal may not transmit SRS when the DL BWP is activated to a dormant BWP, when the cell group is indicated to be paused, or when the cell group is not active (or is disabled or paused).
[0331] 3) Implementation method for configuring SRS
[0332] - In Embodiment 3 of this disclosure, the second SRS configuration information may be configured only for BWPs or BWPs configured as UL dormant BWPs (BWPs indicated by the dormant BWP identifier) in the UL BWP configuration information. That is, SRS configuration (e.g., SRS transmission resources, time periods, or offsets) for dormant BWPs or cell group pause indications or configurations. Alternatively, the first SRS configuration information may be configured only for BWPs configured as BWPs other than UL dormant BWPs (BWPs not indicated by the dormant BWP identifier) in the UL BWP configuration information. That is, SRS configuration information (e.g., SRS transmission resources, time periods, or offsets) for regular BWPs or BWPs other than dormant BWPs. In another approach, in the case of TDD or unpaired spectrum, when a dormant BWP identifier is configured in the DL BWP configuration information, it may be necessary to configure the second SRS configuration information in the UL BWP configuration information for UL dormant BWPs (BWPs indicated by the dormant BWP identifier) or UL BWPs with the same BWP identifier as the DL dormant BWP.
[0333] For example, in Embodiment 3 of this disclosure, when the DL BWP is switched or activated to a BWP (or a regular BWP) in the activated cell other than the dormant BWP, the terminal can apply first SRS configuration information in the UL BWP of the activated cell and can transmit SRS based on the SRS transmission resources, time periods, or offsets corresponding to the first SRS configuration information. When the DL BWP is switched or activated to a dormant BWP in the activated cell, the terminal can apply second SRS configuration information in the UL BWP of the activated cell and can transmit SRS based on the SRS transmission resources, time periods, or offsets corresponding to the second SRS configuration information. For example, the SRS transmission resources configured for the dormant BWP in the second SRS configuration information can be configured to be much smaller than the SRS transmission resources configured for the regular BWP in the first SRS configuration information, or the SRS transmission resource time period configured for the dormant BWP in the second SRS configuration information can be configured to be much longer than the SRS transmission resource time period configured for the regular BWP in the first SRS configuration information, thereby improving the power saving effect of the terminal in the dormant BWP. For example, the SRS transmission time period in the second SRS configuration information can be configured to be equal to or greater than 100ms. In another method, when the DL BWP is activated to a dormant BWP, if the second SRS configuration information is not configured, the terminal can apply the first SRS configuration information to the ULBWP and can transmit SRS based on the SRS transmission resources, time period, or offset corresponding to the first SRS configuration information. In another embodiment of this disclosure, when the DL BWP is activated to a dormant BWP, if the second SRS configuration information is not configured, the terminal may not transmit SRS.
[0334] As another method for configuring information for BWP configuration for each cell (PCell, Pscll, or SCell), the second method may not configure the configuration information (e.g., search space, PDCCH transmission resources, or time period) required to read the PDCCH of the BWP corresponding to the dormant BWP (in another approach, the time period may be configured to be very long along with other configuration information), and may configure the configuration information (e.g., search space, PDCCH transmission resources, or time period) required to read the PDCCH of a regular BWP. This is because a dormant BWP is a BWP that does not read the PDCCH to reduce terminal battery consumption and is used to perform channel measurements and report the channel measurement results to the PCell to enable rapid activation of the BWP or cell, allowing for rapid allocation of UL or DL transmission resources. Therefore, in this disclosure, the term "dormant BWP" may refer to a BWP that is not configured with configuration information (e.g., search space, PDCCH transmission resources, or time period) for PDCCH monitoring, or may refer to a BWP indicated by a dormant BWP identifier, or may refer to a BWP that is configured with configuration information for PDCCH monitoring but is configured to perform monitoring over a long period. In another approach, within this disclosure, the term "dormant BWP" can refer to a BWP for which PDCCH transmission resources or time periods are not configured in the configuration information used for PDCCH monitoring, so that PDCCH monitoring is not performed in the cell where the dormant BWP is configured, but search space information or cross-carrier scheduling configuration information is configured, so that handover or indication for the dormant BWP is received in another cell via cross-carrier scheduling. Since data transmission / reception is not possible in a dormant BWP, PDCCH configuration information (PDCCH-config) can be configured only for the dormant BWP (or the first BWP) (e.g., only search space information can be configured). Conversely, since PDCCH monitoring should also be performed in a regular BWP (or a second BWP) other than the dormant BWP and data transmission / reception should be possible, PDCCH configuration information (e.g., CORESET configuration information, or search space configuration information, or PDCCH transmission resources, or time periods), or PDSCH configuration information, or PUSCH configuration information, or random access related configuration information can be further configured.
[0335] Therefore, while a regular UL or DL BWP should be configured for each cell, a dormant BWP may or may not be configured for each cell, and the configuration of the regular and / or dormant BWPs can depend on the base station implementation, depending on the purpose. Additionally, the first active BWP, or the default BWP, or the initial BWP can be configured as a dormant BWP, depending on the base station implementation.
[0336] In a dormant BWP, the terminal may not transmit / receive data to / from the base station, may not monitor the PDCCH to check the base station's indications, may not transmit pilot signals but can still perform channel measurements, and may periodically or when events occur, report the measured frequency / cell / channel measurement results according to the base station configuration. Therefore, since the terminal does not monitor the PDCCH and does not transmit pilot signals in a dormant BWP, battery consumption can be reduced compared to active mode. Furthermore, unlike disabled mode, because the terminal performs channel measurement reporting, the base station can quickly activate cells configured with a dormant BWP for carrier aggregation based on the measurement reports from the dormant BWP. In embodiments of this disclosure, the dormant BWP can be configured in the DLBWP configuration information and can be used only for the DLBWP.
[0337] In this disclosure, terminal operations for a dormant BWP 1g-02, or terminal operations in a SCell or PSCell activated when a dormant BWP is activated, are as follows. However, this disclosure is not limited thereto.
[0338] - When the terminal is instructed to operate or is activated by a dormant BWP for a specific serving cell (PCell, PSCell, or SCell) from a PCell or SPCell, or when the terminal receives an instruction to put a specific serving cell (e.g., SCell) or a BWP (e.g., DLBWP) of a serving cell (e.g., SCell) into sleep or an instruction to activate a dormant BWP via a DCI (L1 control signal), MAC CE, or RRC message in the PDCCH, or when the terminal receives an instruction to put a BWP (e.g., DLBWP) of a serving cell (e.g., SCell) into sleep or an instruction to activate a dormant BWP via a DCI (L1 control signal), MAC CE, or RRC message in the PDCCH. When the terminal receives an indication to switch to a dormant BWP (when the terminal receives this indication via the L1 control signal of the PDCCH, the terminal can receive the indication via its own cell's PDCCH through self-scheduling, or via the PDCCH of the cell in the PCell through cross-carrier scheduling), or when a BWP dormant timer is configured and expires, when the activated BWP of the activated cell is a dormant BWP, or when the activated BWP of the activated cell is not a regular BWP, the terminal may perform one or more of the following operations.
[0339] -- You can switch a UL BWP or DL BWP to a BWP configured in RRC (e.g., hibernate a BWP), and you can activate or hibernate that BWP.
[0340] --Can stop cell deactivation timers configured or running in the cell or BWP.
[0341] --When a BWP sleep timer is configured in the BWP of the cell, the BWP sleep timer can be stopped.
[0342] --This can start or restart the hibernation BWP deactivation timer in the BWP of the cell.
[0343] --You can stop the BWP disable timer configured for the cell's BWP. This is to prevent unnecessary BWP handover processes within the cell.
[0344] --Periodic DL transport resources (DL SPS or configured downlink allocation) or periodic UL transport resources (UL SPS or configured uplink license type 2) configured in the BWP of a cell can be cleared. The term "clear" means that the terminal has stored configuration information such as time period information configured in RRC messages, but the information about periodic transport resources indicated or activated by L1 signaling (e.g., DCI) is removed and no longer used. The operation of clearing configured periodic DL transport resources (DL SPS or configured downlink allocation) or allocated periodic UL transport resources (UL SPS or configured uplink license) can only be performed when the BWP transitions from an active state to a dormant state. This is because when the BWP transitions from a disabled state to a dormant state, there is no information about periodic transport resources indicated or activated by L1 signaling. In another approach, periodic transport resources can only be cleared when periodic DL transport resources or periodic UL transport resources are configured, or when periodic DL transport resources or periodic UL transport resources are configured and used.
[0345] --Periodic UL transport resources configured in the cell's BWP (configured uplink license type 1 in RRC) can be suspended. The term "suspend" means that the transport resource configuration information configured in the RRC message is stored in the terminal but is no longer used. The operation of suspending configured periodic UL transport resources (configured uplink license type 1) can only be performed when the BWP transitions from an active state to a dormant state. This is because periodic transport resources are not used when the BWP transitions from a disabled state to a dormant state. Alternatively, periodic transport resources can only be cleared when periodic DL transport resources or periodic UL transport resources are configured, or when periodic DL transport resources or periodic UL transport resources are configured and used.
[0346] -- This can clear all HARQ buffers configured in UL or DL BWP.
[0347] --The terminal may not transmit SRS for the cell-specific UL BWP.
[0348] --In another approach, when a first SRS configuration (or SRS configuration information for a regular BWP (other than a dormant BWP, e.g., SRS transmission resources, time periods, or offsets)) or a second SRS configuration (or SRS configuration information for a dormant BWP, e.g., SRS transmission resources, time periods, or offsets)) is configured in the UL BWP configuration information, the terminal can benefit from network power control or scheduling, or can transmit SRS to quickly reactivate the terminal's UL BWP. For example, when a DL BWP is switched or activated to a BWP (or a regular BWP) other than a dormant BWP in an activated SCell (when the activated BWP is not a dormant BWP), the terminal can apply the first SRS configuration information in the UL BWP of the activated cell and can transmit SRS based on the SRS transmission resources, time periods, or offsets corresponding to the first SRS configuration information. When a DLBWP is switched over or activated to a dormant BWP in an activated cell (when the activated BWP is a dormant BWP), the terminal can apply the second SRS configuration information in the UL BWP of the activated cell and can transmit SRS based on the SRS transmission resources, time periods, or offsets corresponding to the second SRS configuration information. For example, the SRS transmission resources configured for the dormant BWP in the second SRS configuration information can be configured to be much smaller than the SRS transmission resources configured for the regular BWP in the first SRS configuration information, or the SRS transmission resource time period configured for the dormant BWP in the second SRS configuration information can be configured to be much longer than the SRS transmission resource time period configured for the regular BWP in the first SRS configuration information, thereby improving the power saving effect of the terminal in the dormant BWP. For example, the SRS transmission time period in the second SRS configuration information can be configured to be equal to or greater than 100ms. In another approach, when the DL BWP is activated to a dormant BWP, if the second SRS configuration information is not configured, the terminal can apply the first SRS configuration information to the UL BWP and can transmit SRS based on the SRS transmission resources, time period, or offset corresponding to the first SRS configuration information. In yet another approach, when the DL BWP is activated to a dormant BWP, if the second SRS configuration is not configured, the terminal may not transmit SRS.
[0349] --In another approach, when a DL BWP is switched or activated to a DL dormant BWP in an activated cell (when the activated BWP is a dormant BWP), the terminal can switch or activate a UL BWP to a UL dormant BWP. The UL dormant BWP can be indicated as a dormant BWP by the BWP identifier in the UL BWP configuration information configured in the RRC message (e.g., in the case of FDD, unpaired spectrum, or TDD). In another approach, a UL BWP with the same BWP identifier as the DL dormant BWP can be a dormant BWP (e.g., in the case of unpaired spectrum or TDD). The terminal can apply second SRS configuration information configured in the UL dormant BWP and can transmit SRS based on the SRS transmission resources, time periods, or offsets corresponding to the second SRS configuration information.
[0350] --In another approach, the current UL BWP or the most recently activated UL BWP can be activated as is.
[0351] --In the cell's BWP, the terminal can perform channel measurements (Channel State Information (CSI), Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), Grade Indicator (RI), Precoding Type Indicator (PTI), or CSI-Reference Signal (RS) Indicator (CRI)), and can execute measurement reports for DL according to the base station configuration. For example, channel or frequency measurement reports can be executed periodically.
[0352] --In the BWP of the cell, UL data can be transmitted without going through UL-SCH.
[0353] --In the BWP of the cell, the random access procedure may not be performed.
[0354] --In the BWP of the cell, the terminal does not need to monitor the PDCCH.
[0355] --The terminal may not need to monitor the PDCCH for the cell's BWP. However, in cross-scheduling scenarios, the terminal can receive indications by monitoring the PDCCH of a cell (e.g., SCell) in the scheduled cell (e.g., PCell).
[0356] --In the cell's BWP, PUCCH or SPUCCH transmissions can be omitted.
[0357] --This allows the DL BWP to go into sleep mode, perform and report channel measurements, and disable and not use the cell's UL BWP. The reason is that in a dormant cell, channel measurements are performed only for the DL BWP, and the measurement results are reported in the UL BWP with a PUCCH in an SPCell (PCell or PSCell) or SCell.
[0358] When a handover is indicated for a DL or when a dormant BWP is activated, or when a BWP is indicated to be dormant, a random access procedure can be performed without canceling the handover. This is because when a random access procedure is performed in a cell, a preamble is transmitted via the UL and a RAR is received via the DL through the PCell. Therefore, no problem occurs even when the DL BWP is dormant or handover to a dormant BWP.
[0359] In this disclosure, the terminal operation is as follows when a regular BWP (active BWP) 1g-01 of the activated SCell is activated, or when a BWP other than a dormant BWP is activated. However, this disclosure is not limited thereto.
[0360] When the terminal receives an indication to activate a regular BWP (e.g., a DL BWP) or a regular BWP other than a dormant BWP in the current cell (PCell, PSCell, or SCell) via a DCI (L1 control signal), MAC CE, or RRC message in the PDCCH, or when it receives an indication to switch a BWP (e.g., a DL BWP) to an active BWP (or a BWP other than a dormant BWP) via a DCI (L1 control signal), MAC CE, or RRC message in the PDCCH, or when the activated BWP in the currently activated cell is a regular BWP, or when the activated BWP in the currently activated cell is not a dormant BWP (when this indication is received via an L1 control signal in the PDCCH, the indication may be received via self-scheduling through the PDCCH of its own cell, or the indication may be received via cross-carrier scheduling through the PDCCH of the cell in the PCell), the terminal may perform one or more of the following operations.
[0361] --You can switch to or activate the indicated UL or DL BWP. Alternatively, the UL or DL BWP can be switched to a specified BWP (e.g., the first active UL or DL BWP) and that BWP can be activated.
[0362] --SRS can be transmitted in an activated BWP, enabling the base station to perform channel measurements on the UL. For example, SRS can be transmitted periodically.
[0363] --In another approach, when a first SRS configuration (or SRS configuration information for a regular BWP (other than a dormant BWP, e.g., SRS transmission resources, time periods, or offsets)) or a second SRS configuration (or SRS configuration information for a dormant BWP, e.g., SRS transmission resources, time periods, or offsets)) is configured in the UL BWP configuration information, the terminal can benefit from network power control or scheduling, or can transmit SRS to quickly deactivate the terminal's UL BWP. For example, when a DL BWP is switched or activated to a BWP (or a regular BWP) of an activated SCell other than a dormant BWP (when the first active BWP is not a dormant BWP), the terminal can apply the first SRS configuration information in the UL BWP of the activated cell and can transmit SRS based on the SRS transmission resources, time periods, or offsets corresponding to the first SRS configuration information. When a DL BWP is switched over or activated to a dormant BWP in an activated cell (when the first active BWP is a dormant BWP), the terminal can apply second SRS configuration information to the UL BWP in the activated cell and can transmit SRS based on the SRS transmission resources, time periods, or offsets corresponding to the second SRS configuration information. For example, the SRS transmission resources configured for the dormant BWP in the second SRS configuration information can be configured to be much smaller than the SRS transmission resources configured for the regular BWP in the first SRS configuration information, or the SRS transmission resource time period configured for the dormant BWP in the second SRS configuration information can be configured to be much longer than the SRS transmission resource time period configured for the regular BWP in the first SRS configuration information, thereby improving the terminal's power saving effect. For example, the SRS transmission time period in the second SRS configuration information can be configured to be equal to or greater than 100ms. In another method, when a DL BWP is activated to a dormant BWP, if the second SRS configuration information is not configured, the terminal can apply the first SRS configuration information to the UL BWP and can transmit SRS based on the SRS transmission resources, time periods, or offsets corresponding to the first SRS configuration information. In another approach, when the DL BWP is activated to a dormant BWP, the terminal may not transmit SRS if the second SRS configuration information is not configured.
[0364] --In another approach, when the DL BWP is switched or activated to a BWP other than the DL dormant BWP or a regular BWP in the activated SCell (when the first active BWP is not a dormant BWP), the terminal can switch or activate the UL BWP to the BWP that was first activated from dormancy as configured in the RRC. The BWP that was first activated from UL dormancy can be indicated as the BWP activated from dormancy by the BWP identifier in the ULBWP configuration information configured in the RRC message (e.g., in the case of FDD, unpaired spectrum, or TDD). In another approach, the UL BWP with the same BWP identifier as the DL dormant BWP can be a dormant BWP (e.g., in the case of unpaired spectrum or TDD). The terminal can apply the first SRS configuration information configured in the BWP that was first activated from dormancy and can transmit SRS based on the SRS transmission resources or time period or offset corresponding to the first SRS configuration information.
[0365] --In another approach, the current UL BWP or the most recently activated UL BWP can be activated as is.
[0366] --In another approach, when the first active DL BWP is not a dormant BWP,
[0367] - When a cell is in a disabled state before receiving MAC control information indicating cell activation or deactivation, or when a cell is configured to be in an active state in the cell configuration or configuration information via an RRC message.
[0368] ----The UL BWP or DL BWP can be activated to the BWP indicated by the first active UL BWP identifier or the first active DL BWP identifier in the RRC configuration information.
[0369] --In another approach, when the first active DL BWP is a dormant BWP,
[0370] ----This can stop BWP and disable the timer.
[0371] ----When a cell is in a disabled state before receiving MAC control information indicating cell activation or deactivation, or when a cell is configured to be in an active state in the cell configuration or configuration information via an RRC message.
[0372] ----A UL BWP or DL BWP can be activated to the BWP indicated by the first active UL BWP identifier (or dormant BWP identifier) or the first active DL BWP identifier (or dormant BWP identifier) in the RRC configuration information. For example, when the first active DL BWP is configured as a dormant BWP, the first active UL BWP can also be configured as a dormant BWP.
[0373] In another method, the DL BWP can be activated to the BWP indicated by the first active DL BWP identifier (or dormant BWP identifier) in the RRC configuration information. The UL BWP can also be activated to the BWP indicated by the dormant BWP identifier (or first active UL BWP identifier) in the RRC configuration information.
[0374] --When a PUCCH is configured in an activated BWP, a PUCCH transmission can be performed.
[0375] --The BWP or cell deactivation timer can be started or restarted. Alternatively, the BWP or cell deactivation timer can be started or restarted only if no BWP or cell sleep timer is configured. The BWP or cell sleep timer can be configured in an RRC message, and the BWP or cell can sleep when the BWP or cell sleep timer expires. For example, the BWP or cell deactivation timer can be started or restarted only in a sleeping BWP or cell.
[0376] --When a suspended Type 1 configuration transport resource exists, the stored Type 1 transport resource can be initialized and used as configured. A Type 1 configuration transport resource is a periodic transport resource (UL or DL) previously allocated via RRC messages, and refers to a transport resource that can be activated and used via RRC messages.
[0377] --Can be used for BWP trigger power headroom report (PHR).
[0378] --In an activated BWP, the terminal can report channel measurement results (CSI, CQI, PMI, RI, PTI, or CRI) according to the base station configuration used for DL.
[0379] --In an activated BWP, the PUCCH can be monitored to read the base station's indications.
[0380] --To read cross-scheduling data for the active BWP, you can monitor the PDCCH.
[0381] --The BWP disable timer can be started or restarted. Alternatively, the BWP disable timer can be started or restarted only if the BWP sleep timer is not configured. The BWP sleep timer can be configured in an RRC message, and when the BWP sleep timer expires, the BWP can switch to sleep or hibernate. For example, the BWP disable timer can be started or restarted only in a hibernating BWP.
[0382] --When a BWP sleep timer is configured for BWP
[0383] ---BWP sleep timer can be used to start or restart BWP.
[0384] In this disclosure, the terminal operation when BWP is disabled (BWP disabled) 1g-03 or when BWP or the cell is deactivated is as follows. However, this disclosure is not limited thereto.
[0385] When the terminal receives an indication to disable the BWP (e.g., DL BWP) of the current cell (PCell, PSCell, or SCell) via a DCI (L1 control signal), MAC CE, or RRC message in the PDCCH, or when it receives an indication to disable the BWP (e.g., DL BWP) or switch to disabling the BWP via a DCI (L1 control signal), MAC CE, or RRC message in the PDCCH (when this indication is received via the L1 control signal of the PDCCH, it can be received via self-scheduling through the PDCCH of its own cell, or it can be received via cross-carrier scheduling through the PDCCH of the cell in the PCell), or when the BWP in the cell or the cell deactivation timer expires, or when the activated SCell is deactivated, or when the BWP of the cell is deactivated, the terminal may perform one or more of the following operations.
[0386] --The UL or DL BWP of the cell or indicator can be disabled.
[0387] --The terminal can stop BWP disable timers configured and running in the cell or BWP (e.g., disable timers for DL BWP).
[0388] --Periodic DL transport resources (DL SPS or configured downlink allocations) or periodic UL transport resources (UL SPS or configured uplink license type 2) configured in a cell or BWP can be cleared. The term "clear" means that the terminal has stored configuration information such as time period information configured in RRC messages, but the information about periodic transport resources indicated or activated by L1 signaling (e.g., DCI) is removed and no longer used. Periodic transport resources can be referred to as type 2 configured transport resources. Furthermore, the operation of clearing periodic transport resources can only be performed when the cell transitions from an active state to a disabled state. This is because periodic transport resources do not exist in the dormant state, so a clearing operation is not required when the cell transitions from a dormant state to a disabled state. In another approach, periodic transport resources can only be cleared when periodic DL transport resources or periodic UL transport resources are configured, or when periodic DL transport resources or periodic UL transport resources are configured and used.
[0389] --Periodic UL transport resources configured in a cell or BWP (configured uplink license type 1 in RRC) can be suspended. The term "suspended" means that the transport resource configuration information configured in the RRC message is stored in the terminal but is no longer used. Periodic transport resources can be referred to as type 1 configured transport resources. Furthermore, the operation of clearing periodic transport resources can only be performed when the cell transitions from an active state to a disabled state. This is because periodic transport resources do not exist in the dormant state, so a clearing operation is not required when the cell transitions from a dormant state to a disabled state. In another approach, periodic transport resources can only be cleared when periodic DL transport resources or periodic UL transport resources are configured, or when periodic DL transport resources or periodic UL transport resources are configured and used.
[0390] -- This can clear all HARQ buffers configured for a cell or BWP.
[0391] --When there are PUSCH transport resources configured for periodic channel measurement reports (semi-continuous CSI reports) for a cell or BWP, the PUSCH transport resources can be cleared.
[0392] --The terminal may not transmit SRS for cell or BWP.
[0393] --The terminal may not perform channel measurements (CSI, CQI, PMI, RI, PTI, or CRI) for the cell or BWP, and may not perform reports for the DL.
[0394] --In a cell or BWP, UL data can be transmitted without UL-SCH.
[0395] --For cells or BWPs, the random access procedure may not be performed.
[0396] --In a cell or BWP, the terminal may not need to monitor the PDCCH.
[0397] --For cells or BWPs, the terminal may not need to monitor the PDCCH. Furthermore, even in cross-scheduling scenarios, the terminal may not need to monitor the cell's PDCCH within the scheduled cell.
[0398] --In a cell or BWP, PUCCH or SPUCCH transmissions may not be performed.
[0399] According to embodiments of this disclosure, when an operating cell or BWP is in an active, disabled, or dormant state and a cell or BWP transition or handover is performed, it can be performed on a BWP-by-BWP basis. When a state transition or handover is performed on a BWP-by-BWP basis, a BWP (DL BWP or UL BWP) with a state transition or handover indication can perform the state transition or handover according to the state transition or handover indication. For example, when a BWP (DL BWP or UL BWP) transitions from an active state to a dormant state or is switched (or activated) to a dormant BWP, the BWP can transition to a dormant state or can be switched (or activated) to a dormant BWP.
[0400] In this disclosure, the term "BWP handover" can mean: when a BWP handover is indicated by a DCI in the PDCCH and when a handover is indicated by a BWP identifier during downlink allocation, the DL BWP is switched to the BWP indicated by the BWP identifier; and when a BWP handover is indicated by a DCI in the PDCCH and when a handover is indicated by a BWP identifier during UL license allocation, the UL BWP can be switched to the BWP indicated by the BWP identifier. Furthermore, since the DCI format in the PDCCH differs between the format used for downlink allocation (format1) and the format used for UL license allocation (format0), the terminal can operate according to the DCI format even without separate descriptions of UL and DL.
[0401] The method for operating state transitions on a BWP-by-BWP (BWP level) basis according to this disclosure, and the operation of the BWP according to each state, can be extended and applied to various implementations. Specific implementations that extend and apply the content provided by this disclosure will now be described below.
[0402] Figure 1H A diagram is shown of a discontinuous frequency reduction (DRX) configuration or DRX operation method for reducing terminal battery consumption according to an embodiment of the present disclosure.
[0403] refer to Figure 1H Base stations can be accessed through methods such as Figure 1F The RRC message shown configures DRX functionality in the terminal, such as DRX period, start point, offset, or connection continuation time (active period or active time). According to embodiments of this disclosure, the base station can configure DRX functionality in PCell, SPCell, or PSCell.
[0404] When DRX functionality is configured in the PCell (SPCell or PSCell), the terminal can apply DRX functionality by considering the DRX period 1h-03 and the DRX start time or offset. When DRX functionality is applied, the terminal can monitor only the PDCCH or DCI within the PDCCH that can be received from the base station in the PCell during the DRX active period (call-on continuation time or active time) 1h-01. Furthermore, outside the active period of DRX functionality (outside the active time) 1h-02, the terminal can choose not to monitor the PDCCH or DCI within the PDCCH, thereby reducing terminal battery consumption.
[0405] like Figure 1F As shown, the base station can configure a power-saving function (power-saving mode) in the terminal via RRC messages to further reduce the terminal's battery consumption. When the power-saving function is configured together with the DRX function, the terminal can monitor the PDCCH outside the short period of 1h-04 configured in the RRC, prior to the active time 1h-01 that the terminal should monitor the PDCCH in the DRX function, and can monitor and receive WUS outside the active time period. The base station can use the DCI bit in the PDCCH of the WUS to indicate whether the terminal should perform PDCCH monitoring or not during the next active time periods 1h-05 and 1h-07.
[0406] In other words, terminals configured with power-saving or DRX functions can monitor the WUS during the short period of 1h-04 configured in the RRC message before each activity time 1h-05. When the DCI bit in the received WUS regarding the PDCCH for the next activity time 1h-05 and 1h-07 has a value of 0 (or 1), this indicates that the terminal may not monitor the PDCCH during the next activity time 1h-07, or may not monitor the PDCCH by not running a timer corresponding to the next activity time in the MAC layer. When the DCI bit in the received WUS regarding the PDCCH for the next activity time 0h-05 and 1h-07 has a value of 1 (or 1), this indicates that the terminal may monitor the PDCCH during the next activity time 1h-05, or may monitor the PDCCH by running a timer corresponding to the next activity time in the MAC layer.
[0407] During the activity periods 1h-01 and 1h-05, the terminal may not monitor WUS or the PDCCH used for WUS.
[0408] When monitoring WUS during the short time period 1h-04 configured in the RRC message prior to each activity time 1h-05, terminals configured with power-saving or DRX functions can detect signals by identifying the PDCCH using a first RNTI identifier (e.g., PS-RNTI). The first RNTI identifier (e.g., PS-RNTI) can be configured in multiple terminals, and the base station can use the first RNTI identifier (e.g., PS-RNTI) to indicate whether these multiple terminals will monitor the PDCCH in the next activity time period.
[0409] When monitoring and detecting the PDCCH during the activity period 1h-05, terminals configured with power-saving or DRX functions can detect signals based on a second RNTI (e.g., C-RNTI), a third RNTI (e.g., MCS-C-RNTI), or a fourth RNTI (e.g., SPS-C-RNTI or CS-RNTI) uniquely configured in the terminal via RRC messages. The second RNTI (e.g., C-RNTI) can be used to indicate the terminal's general scheduling, the third RNTI (e.g., MCS-C-RNTI) can be used to indicate the terminal's modulation or coding scheme (MCS), and the fourth RNTI (e.g., SPS-C-RNTI or CS-RNTI) can be used to indicate the terminal's periodic transmission resources.
[0410] Figure 1I A diagram is shown illustrating a method for operating a dormant BWP in an activated SCell or PSCell, according to an embodiment of this disclosure.
[0411] like Figure 1F As shown, for carrier aggregation, the base station can configure multiple SCells in the terminal and assign an identifier to each SCell via RRC messages, and can configure a sleep BWP for each SCell. Additionally, for dual connectivity, the base station can configure multiple cell groups and assign cell group identifiers, and can assign or indicate a cell group pause indicator for each cell group or PSCell within each cell group, or can configure a sleep bandwidth. Furthermore, the base station can include and configure multiple SCells within each SCell group. A SCell group can include multiple SCells. SCell group identifiers can be assigned to each SCell group, and multiple SCell identifiers can be configured to be included in or mapped to each SCell group identifier. SCell identifier values or SCell group identifier values can be assigned to specific values and can have integer values (or natural numbers). Alternatively, the PSCell for each cell group can be indicated by the cell group identifier.
[0412] refer to Figure 1IThe base station can define a new bitmap in the DCI of the PDCCH transmitted in the PCell, and can map each bit of the bitmap to indicate each SCell identifier value, or each SCell group identifier value, or cell group (or SCG) identifier, or PSCell (or SCell) of the cell group (or SCG). For the SCell corresponding to this bit, or the SCell belonging to the SCell group, or the PSCell (or SCell) of the cell group (or SCG), or the PSCell (or SCell) of the cell group (or SCG), the base station can define the bit value of each bit to indicate whether to switch to a dormant BWP, or whether to activate a dormant BWP, or whether to suspend the cell group, or whether to resume the cell group. In addition, for the SCell corresponding to this bit, or the SCell belonging to the SCell group, or the cell group (or SCG) identifier, or the PSCell (or SCell) of the cell group (or SCG), the base station can indicate whether to switch from a dormant BWP to a dormant BWP (e.g., from a dormant first active BWP) or whether to activate a regular BWP (e.g., from a dormant first active BWP).
[0413] After receiving the DCI from the PDCCH in PCell 1i-01, the terminal can read the DCI and determine whether a bitmap exists that includes the following indications: an indication for a BWP (e.g., handover or activation to a dormant BWP or handover or activation to a regular BWP) for an SCell or SCell group, or an indication for suspending or resuming a PSCell (or SCell) in a cell group (or SCG). When this bitmap exists, for each SCell indicated by each bit of the bitmap, or SCells 1i-02 and 1i-03 belonging to an SCell group, or a cell group (or SCG), or a PSCell (or SCell) of a cell group (or SCG), the terminal can handover or activate a BWP, or suspend or resume a cell group, based on the bit values. For example, when a bit in the bitmap indicates the first SCell (or first SCell identifier) 1i-02 or a PSCell (or SCell) within a cell group (or SCG) or a cell group (or SCG), or indicates a SCell group (or SCell group identifier) including the first SCell, if the bit value is 0 (or 1), then for the first SCell 1i-02, or the cell group (or SCG), or the PSCell (or SCell) within a cell group (or SCG), the terminal can activate BWP1i-21 to a dormant BWP 1i-22, or switch the current BWP to a dormant BWP 1i-22. Alternatively, when the current BWP is not a dormant BWP, the terminal can switch or activate the currently activated BWP 1i-21 to a dormant BWP 1i-22 (1i-25), or suspend or deactivate the cell group. In another approach, the PSCell (or SCell) in the cell group (or SCG) or cell group (or SCG) can be maintained as is, the second DRX configuration information or the second SRS configuration information according to this disclosure can be applied, and PDCCH monitoring or SRS transmission can be performed with a long cycle, thereby reducing the power consumption of the terminal.
[0414] After receiving the DCI from the PDCCH in PCell 1i-01, the terminal can read the DCI and determine whether a bitmap exists that includes the following indications: an indication for the BWP of an SCell or SCell group (e.g., handover or activation to a dormant BWP or handover or activation to a regular BWP), or an indication for the BWP of a PSCell (or SCell) in a cell group (or SCG) or a cell group (or SCG), or an indication to suspend or resume a cell group. When this bitmap exists, for each SCell indicated by each bit of the bitmap, or SCells 1i-02 and 1i-03 belonging to an SCell group, or a cell group (or SCG), or a PSCell (or SCell) of a cell group (or SCG), the terminal can switch or activate the BWP, or suspend or resume the cell group, based on the bit values. For example, when a bit in the bitmap indicates a second SCell (or second SCell identifier) 1i-03 or a SCell group (or SCell group identifier) or cell group (or SCG) that includes the second SCell, or a PSCell (or SCell) within a cell group (or SCG), if the bit value is 1 (or 0), then when the currently active BWP of the second SCell 1i-03 is a dormant BWP 1i-32, or when the currently active BWP is not a dormant BWP, or when the current BWP (or cell) is active and the current BWP is activated to a dormant BWP 1i-32 (or when activated to a BWP other than a dormant BWP), the terminal can switch or activate the BWP of the second SCell 1i-03 to the BWP 1i-33 configured in the RRC message (e.g., the first active BWP activated from dormancy) (1i-35), or can restore or activate the cell group. When the bit value is 1 (or 0), and the SCell indicated by this bit, or a SCell belonging to an SCell group, or a PSCell (or SCell) within a cell group (or SCG), should be switched or activated to a BWP other than a dormant BWP, or the cell group should be restored for each SCell or each SCell belonging to an SCell group, if the SCell is in a disabled state or the SCell is in an active state and the activated BWP is not a dormant BWP (or a regular BWP), then this bit value may not be applied, may be ignored, or may not be read. Alternatively, when the PSCell (or SCell) within a cell group (or SCG) or a cell group (or SCG) is already in an active or restored state, this bit value may not be applied, may be ignored, or may not be read.Additionally, when the bit value is 0 (or 1), and therefore the SCell indicated by that bit, or a SCell belonging to an SCell group, or a PSCell (or SCell) within a cell group (or SCG), should be switched or activated to a dormant BWP, or the cell group should be paused for each SCell or each SCell belonging to an SCell group, if the SCell is active and the activated BWP is a dormant BWP, then this bit value may not be applied, may be ignored, or may not be read. Alternatively, when the PSCell (or SCell) within a cell group (or SCG), or a cell group (or SCG), is already paused or deactivated, this bit value may not be applied, may be ignored, or may not be read.
[0415] Figure 1J Embodiment 1 of a method for operating a dormant BWP in an activated SCell according to an embodiment of the present disclosure is shown.
[0416] In Embodiment 1 of this disclosure, as Figure 1F As shown, for carrier aggregation, the base station can configure multiple SCells in the terminal via RRC messages and can assign an identifier to each SCell. It can also configure a dormant BWP for each SCell, or not configure a dormant BWP for a specific SCell. Alternatively, for dual connectivity, the base station can configure one or more cell groups and can configure an identifier for each cell group or a state for each cell group, or configure a dormant BWP for each PSCell (or SCell) in each cell group, or not configure a dormant BWP for a specific cell. Furthermore, the base station can include and configure multiple SCells in each SCell group, and a SCell group can include multiple SCells. An SCell group identifier can be assigned to each SCell group, and multiple SCell identifiers can be configured to be included in or mapped to each SCell group identifier. SCell identifier values or SCell group identifier values or cell group (or SCG) identifiers can be assigned to specific values and can have integer values (or natural numerical values). In this disclosure, the SCell group or SCell group identifier configured for or applying Embodiment 1 of this disclosure can be referred to as the first SCell group. In Embodiment 1 of this disclosure, the first SCell group can indicate a group identifier that applies the following operations: the terminal monitors the operation of DCI in PDCCH, and indicates the bitmap value of DCI received during a short period of time (outside of the active period) or a period of time outside of the active period.
[0417] refer to Figure 1J The base station can configure power-saving or DRX functions in each of multiple terminals via RRC messages, such as... Figure 1F As shown. The base station can configure time information, or configuration information regarding the first DCI format, in each terminal via RRC messages, for the short period 1j-02 of the first DCI format or WUS to be detected in PCell 1j-01 or SPCell before the active period 1j-30 of the DRX cycle. Additionally, when the terminal detects the first DCI format in PCell or SPCell during the short period 1j-02, the base station can configure the position of the bitmap in the first DCI format via RRC messages. This bitmap includes an indication of the first SCell group for each terminal. Through RRC messages, the base station can configure the search space or terminal identifier (e.g., PS-RNTI) for PDCCH monitoring in the terminal for detecting the first DCI format during the short period 1j-02. Since the terminal does not monitor the DCI in the PDCCH when switching to or activating a dormant BWP in an SCell or PSCell, receiving the DCI or bitmap in the PDCCH in an SCell other than PCell or SPCell can be very inefficient. Therefore, the terminal can monitor the DCI in the PDCCH in the PCell or SpCell.
[0418] For example, a base station can configure power-saving or DRX functions in multiple terminals, and can transmit a first DCI format 1j-03 via PDCCH transmission resources during a short time period 1j-02 configured before the next active time period 1j-30 of the DRX cycle configured in the terminal. The first DCI format 1j-03 may include bitmaps 1j-04 and 1j-05, which include indication information about the dormant BWP of a first SCell group configured in each of the multiple terminals, or an indication of pausing or resuming a cell group (or SCG) or a PSCell (or SCell) in a cell group (or SCG).
[0419] The first terminal 1j-10, which applies the information configured in the RRC message, can perform PDCCH monitoring based on the identifier PS-RNTI configured within a short time period 1j-02 before the next active time 1j-30 of the DRX cycle, and can detect the first DCI format 1j-03 transmitted from the base station in the search space. When the first DCI format 1j-03 is detected, the first terminal 1j-10 can read the bitmap 1j-04 in the first DCI format 1j-03 through the time information or location information configured in the RRC message. This bitmap includes indication information about the dormant BWP of the PSCell (or SCell) in the first SCell group or cell group (or SCG) of the first terminal 1j-10, or information indicating the suspension or resumption of the PSCell (or SCell) in the cell group (or SCG). The length of bitmap 1j-04 can be configured to be the same as the number of PSCells (or SCells) in the first SCell group or cell group (or SCG) or cell group (or SCG) configured in the first terminal 1j-10, and can be configured to be up to a specific number (e.g., 5). Each of bits 1j-11 and 1j-12 of bitmap 1j-04 can be mapped to each of the first SCell group in ascending order of the SCell group identifier values of the first SCell group configured in the first terminal 1j-10, starting from the right bit of the bitmap (e.g., from the least significant bit (LSB)). In another approach, each of bits 1j-11 and 1j-12 can be mapped to each of the first SCell group in descending order of the SCell group identifier values of the first SCell group configured in the first terminal 1j-10, starting from the right bit of the bitmap (e.g., from the LSB). In another approach, each of bits 1j-11 and 1j-12 of the bitmap can be mapped to each of the first SCell groups in ascending order of the SCell group identifier values configured in the first terminal 1j-10, starting from the left bit of the bitmap (e.g., from the most significant bit (MSB)). Alternatively, each of bits 1j-11 and 1j-12 of the bitmap can be mapped to each of the first SCell groups in descending order of the SCell group identifier values configured in the first terminal 1j-10, starting from the left bit of the bitmap (e.g., from the MSB). New bits can be defined in the first DCI format 1j-03 of the PDCCH, and these new bits can be used to indicate the suspension or resumption of a cell group (or SCG) or a PSCell (or SCell) within a cell group (or SCG).
[0420] When the bit value of each of bits 1j-11 and 1j-12 in the bitmap is 0, for each active SCell in the first SCell group corresponding to that bit, bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP (when a dormant BWP is configured). In another approach, when the bit value of each of bits 1j-11 and 1j-12 in the bitmap is 0, if the active BWP is not a dormant BWP (or a regular BWP) for each active SCell in the first SCell group corresponding to that bit, bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP.
[0421] When the bit value of each of bits 1j-11 and 1j-12 in the bitmap is 1, for each active SCell included in the first SCell group corresponding to that bit, bit value 1 can indicate switching to a regular BWP (e.g., the first active BWP activated from sleep) or activation to a regular BWP (e.g., the first active BWP activated from sleep). In another approach, when the bit value of each of bits 1j-11 and 1j-12 in the bitmap is 1, if the currently active BWP is a sleep BWP (or not a regular BWP) of each active SCell included in the first SCell group corresponding to that bit, bit value 1 can indicate switching to a regular BWP (e.g., the first active BWP activated from sleep) or activation to a regular BWP (e.g., the first active BWP activated from sleep). Otherwise (when the currently active BWP is not a dormant BWP (or a regular BWP) of each active SCell in the first SCell group corresponding to that bit), the first terminal 1j-10 may maintain, continue to use or apply, or activate the currently active BWP. In another approach, when the bit value of each of bits 1j-11 and 1j-12 of the bitmap is 1, the bit value 1 may indicate a switch from a dormant BWP to a regular BWP (e.g., from a dormant, active BWP) or activation to a regular BWP (e.g., from a dormant, active BWP), or maintain, continue to use or apply, or activate the currently active BWP of each active SCell in the first SCell group corresponding to that bit.
[0422] After receiving the DCI from the PDCCH in PCell 1j-01, the terminal can read the DCI and determine whether a bitmap exists that includes the following indications: an indication of the BWP for a cell group (or SCG) or a PSCell (or SCell) within a cell group (or SCG), or an indication to suspend or resume a cell group. When this bitmap exists, the terminal can switch or activate the BWP, or suspend or resume the cell group, based on the bit value of the cell group (or SCG) or PSCell (or SCell) indicated by each bit of the bitmap. For example, when a bit in the bitmap indicates a PSCell (or SCell) within a cell group (or SCG) and the bit value is 1 (or 0), the terminal can resume or activate the cell group. When the bit value is 1 (or 0), indicating that the cell group (or SCG) or PSCell (or SCell) within that cell group (or SCG) should be switched or activated to a BWP other than a dormant BWP, or that the cell group should be restored, if the PSCell (or SCell) within the cell group (or SCG) is already active or restored, this bit value can be omitted, ignored, or not read. Alternatively, for example, when a bit in the bitmap indicates a cell group (or SCG) or PSCell (or SCell) within the cell group (or SCG) and the bit value is 0 (or 1), the terminal can switch or activate the BWP of the cell group (or SCG) or PSCell (or SCell) within the cell group corresponding to that bit to a dormant BWP, or can suspend or deactivate that cell group. When the bit value is 0 (or 1), indicating that the cell group (or SCG) or the PSCell (or SCell) within the cell group (or SCG) should be switched to or activated to a dormant BWP, or that the cell group should be paused for the SCell or each SCell belonging to the SCell group, if the SCell is active and the activated BWP is a dormant BWP, this bit value may not be applied, ignored, or read. Alternatively, when the cell group (or SCG) or the PSCell (or SCell) within the cell group (or SCG) is already paused or deactivated, this bit value may not be applied, ignored, or read.
[0423] The first DCI format in the PDCCH according to Embodiment 1 of this disclosure can be used for a short period of time, and the terminal may not be accompanied by DL transmission resources (e.g., PDSCH) or UL transmission resources (e.g., PUSCH). Therefore, in Embodiment 1 of this disclosure, the terminal can receive the first DCI format in the PDCCH and may not transmit ACK or NACK information (e.g., HARQ ACK or NACK).
[0424] Figure 1K Embodiment 2 of a method for operating a dormant BWP in an activated SCell according to an embodiment of the present disclosure is shown.
[0425] In Embodiment 2 of this disclosure, for carrier aggregation, the base station can configure multiple SCells in the terminal via RRC messages and can assign an identifier to each SCell, such as... Figure 1F As shown. Alternatively, for dual connectivity, the base station can configure one or more cell groups and can configure a cell group identifier or a cell group state for each cell group, or can configure a dormant BWP for each PSCell (or SCell) in each cell group, and can not configure a dormant BWP for a specific cell. The base station can configure a dormant BWP for each cell, and can not configure a dormant BWP for a specific cell. In addition, the base station can include and configure multiple SCells in each SCell group, and an SCell group can include multiple SCells. An SCell group identifier can be assigned to each SCell group, and multiple SCell identifiers can be configured to be included in or mapped to each SCell group identifier. SCell identifier values, SCell group identifier values, or cell group (or SCG) identifiers can be assigned to specific values and can have integer values (or natural numerical values). In this disclosure, the SCell group or SCell group identifier configured for or applying Embodiment 2 of this disclosure can be referred to as a second SCell group. In Embodiment 2 of this disclosure, the second SCell group can indicate a group identifier that performs the following operations: the terminal monitors the operation of the DCI in the PDCCH, and indicates the bitmap value of the DCI received during the active time period (during the active time).
[0426] refer to Figure 1K The base station can configure power-saving or DRX functions in the terminal via RRC messages, such as... Figure 1FAs shown. The base station can configure configuration information in the terminal via RRC messages regarding the second DCI format (e.g., DCI format 0_1 or DCI format 1_1) that should be detected by the terminal for PCell or SPCell during the active time period 1k-30 of the DRX cycle. When the terminal detects the second DCI format in PCell or SPCell, the terminal can determine whether a bitmap containing an indication of the terminal's second SCell group exists in the second DCI format. Additionally, via RRC messages, the base station can configure the search space or terminal identifier (e.g., C-RNTI, MCS-C-RNTI, or SPS-C-RNTI (or CS-RNTI)) for PDCCH monitoring during the active time period 1k-30 to detect the second DCI format. Since the terminal does not monitor the DCI in the PDCCH when switching to or activating a dormant BWP in an SCell or PSCell, receiving the DCI or bitmap in the PDCCH in SCells other than PCell or SPCell can be very inefficient. Therefore, the terminal can monitor the DCI in the PDCCH in PCell or SPCell.
[0427] For example, a base station can transmit a second DCI format 1k-03 to a terminal in a PCell or SPCell via PDCCH transmission resources during an active time period of 1k-30, and the second DCI format 1k-03 may include a bitmap 1k-04, which includes indication information about the dormant BWP configured in the terminal for the second SCell group, or an indication of pausing or resuming a cell group (or SCG) or a PSCell (or SCell) in a cell group (or SCG).
[0428] The first terminal 1k-10, which applies the information configured in the RRC message, can perform PDCCH monitoring based on a terminal identifier (e.g., C-RNTI, MCS-C-RNTI, or SPS-C-RNTI (or CS-RNTI)) configured as an identifier during the active time period 1k-30 of the DRX cycle, and can detect the second DCI format 1k-03 transmitted from the base station in the search space. When the second DCI format 1k-03 is detected, the first terminal 1k-10 can read bitmap 1k-04 in the second DCI format 1k-03, which includes indication information about the dormant BWP of the PSCell (or SCell) in the second SCell group or cell group (or SCG) of the first terminal 1k-10, or information indicating the suspension or resumption of the PSCell (or SCell) in the cell group (or SCG). The length of bitmap 1k-04 can be configured to be the same as the number of PSCells (or SCells) in the second SCell group or cell group (or SCG) or cell group (or SCG) configured in the first terminal, or it can be configured to be up to a specific number (e.g., 5). Each of bits 1k-11, 1k-12, 1k-13, 1k-14, and 1k-15 of bitmap 1k-04 can be mapped to each second SCell group in ascending order of the SCell group identifier values of each second SCell group configured in the first terminal, starting from the right bit of the bitmap (e.g., from the LSB). In another method, each of bits 1k-11, 1k-12, 1k-13, 1k-14, and 1k-15 of bitmap k1-04 can be mapped to each second SCell group in descending order of the SCell group identifier values of each second SCell group configured in the first terminal, starting from the right bit of the bitmap (e.g., from the LSB). In another method, each of bits 1k-11, 1k-12, 1k-13, 1k-14, and 1k-15 of bitmap 1k-04 can be mapped to each second SCell group in ascending order of the SCell group identifier values configured in the first terminal, starting from the left bit of the bitmap (e.g., from the MSB). In yet another method, each of bits 1k-11, 1k-12, 1k-13, 1k-14, and 1k-15 of bitmap 1k-04 can be mapped to each second SCell group in descending order of the SCell group identifier values configured in the first terminal, starting from the left bit of the bitmap (e.g., from the MSB). New bits can be defined in the second DCI format 1k-03 of the PDCCH, and these new bits can be used to indicate the suspension or resumption of a cell group (or SCG) or a PSCell (or SCell) within a cell group (or SCG).
[0429] When the bit value of each of bits 1k-11, 1k-12, 1k-13, 1k-14, and 1k-15 in the bitmap is 0, for each active SCell included in the second SCell group corresponding to that bit, bit value 0 can indicate switching to a dormant BWP or activation to a dormant BWP (when a dormant BWP is configured). Alternatively, when the bit value of each of bits 1k-11, 1k-12, 1k-13, 1k-14, and 1k-15 in the bitmap is 0, if the active BWP is not a dormant BWP (or a regular BWP) for each active SCell included in the second SCell group corresponding to that bit, bit value 0 can indicate switching to a dormant BWP or activation to a dormant BWP.
[0430] When the bit value of each of bits 1k-11, 1k-12, 1k-13, 1k-14, and 1k-15 in the bitmap is 1, for each active SCell included in the second SCell group corresponding to that bit, the bit value 1 can indicate a switch to a regular BWP (e.g., a first active BWP activated from sleep) or activation to a regular BWP (e.g., a first active BWP activated from sleep). In another approach, when the bit value of each of bits 1k-11, 1k-12, 1k-13, 1k-14, and 1k-15 in the bitmap is 1, if the currently active BWP is a sleep BWP (or not a regular BWP) of each active SCell included in the second SCell group corresponding to that bit, the bit value 1 can indicate a switch to a regular BWP (e.g., a first active BWP activated from sleep) or activation to a regular BWP (e.g., a first active BWP activated from sleep). Otherwise (when the currently active BWP is not a dormant BWP (or a regular BWP) of each of the active SCells included in the second SCell group corresponding to that bit), the first terminal 1k-10 may maintain, continue to use or apply, or activate the currently active BWP. In another method, when the bit value of each of bits 1k-11, 1k-12, 1k-13, 1k-14, and 1k-15 of the bitmap is 1, the bit value 1 may indicate a switch from a dormant BWP to a regular BWP (e.g., from a dormant first active BWP) or activation to a regular BWP (e.g., from a dormant first active BWP), or maintain, continue to use or apply, or activate the currently active BWP of each of the active SCells included in the second SCell group corresponding to that bit.
[0431] After receiving the DCI from the PDCCH in PCell 1k-01, the terminal can read the DCI and determine whether a bitmap exists that includes the following indications: an indication of the BWP for a cell group (or SCG) or a PSCell (or SCell) within a cell group (or SCG), or an indication to suspend or resume the cell group. When this bitmap exists, the terminal can switch or activate the BWP, or suspend or resume the cell group, based on the bit value of the cell group (or SCG) or PSCell (or SCell) within the cell group (or SCG) indicated by each bit of the bitmap. For example, when a bit in the bitmap indicates a PSCell (or SCell) within a cell group (or SCG) and the bit value is 1 (or 0), the terminal can resume or activate the cell group. When the bit value is 1 (or 0), indicating that the cell group (or SCG) or PSCell (or SCell) within that cell group (or SCG) should be switched or activated to a BWP other than a dormant BWP, or that the cell group should be restored, if the PSCell (or SCell) within the cell group (or SCG) or SCG is already active or restored, this bit value can be omitted, ignored, or not read. Alternatively, for example, when a bit in the bitmap indicates a PSCell (or SCell) within a cell group (or SCG) or SCG and the bit value is 0 (or 1), the terminal can switch or activate the BWP of the corresponding cell group (or SCG) or PSCell (or SCell) within that cell group (or SCG) to a dormant BWP, or can suspend or deactivate that cell group. When the bit value is 0 (or 1), indicating that the cell group (or SCG) or the PSCell (or SCell) within the cell group (or SCG) should be switched to or activated to a dormant BWP, or that the cell group should be paused for the SCell or each SCell belonging to the SCell group, if the SCell is active and the activated BWP is a dormant BWP, this bit value may not be applied, ignored, or read. Alternatively, when the cell group (or SCG) or the PSCell (or SCell) within the cell group (or SCG) is already paused or deactivated, this bit value may not be applied, ignored, or read.
[0432] According to Embodiment 2 of this disclosure, the second DCI format in the PDCCH can be used during the active time period, and the terminal can be accompanied by DL transmission resources (e.g., PDSCH) or UL transmission resources (e.g., PUSCH) for the terminal's PCell or SPCell. Therefore, in Embodiment 2 of this disclosure, the terminal can receive the second DCI format in the PDCCH and can transmit ACK or NACK information (e.g., HARQ ACK or NACK) for scheduling information (DL transmission resources or UL transmission resources) of the PCell or SPCell indicated in the second DCI format. Therefore, in Embodiment 2 of this disclosure, the base station can determine whether the terminal has successfully received the indication of the second DCI format.
[0433] The base station can configure the first SCell group configuration information applicable to Embodiment 1 of this disclosure and the second SCell group configuration applicable to Embodiment 2 of this disclosure in the RRCSetup message, RRCResume message 1f-25, or RRCReconfiguration message 1f-45 of the RRC connection configuration in the terminal. In the RRC message, the base station can assign a SCell identifier to each SCell of the terminal, and can assign a first SCell group identifier to each first SCell group, and can assign a second SCell group identifier to each second SCell group. Additionally, the base station can assign a first SCell group set identifier indicating a first SCell group, and can assign a second SCell group set identifier indicating a second SCell group. Furthermore, each SCell identifier can be included or mapped to each first SCell group or each second SCell group. The base station can only configure the SCell or SCell identifier to be included or mapped to the first SCell group or second SCell group when a dormant BWP (e.g., DL dormant BWP) is configured for the SCell.
[0434] Figure 1L Embodiment 3 of a method for operating a dormant BWP in an activated SCell according to an embodiment of the present disclosure is shown.
[0435] In embodiment 3 of this disclosure, for carrier aggregation, the base station can configure multiple SCells in the terminal via RRC messages and can assign an identifier to each SCell, such as... Figure 1FAs shown, a dormant BWP can be configured for each SCell, or it can be configured without specifying a particular SCell. Alternatively, for dual connectivity, the base station can configure one or more cell groups and can configure a cell group identifier or a cell group state for each cell group, or it can configure a dormant BWP for each PSCell (or SCell) in each cell group, or it can be configured without specifying a particular cell. The SCell identifier value can be assigned a specific value and can have an integer value (or a natural numerical value). To operate or apply Embodiment 3 of this disclosure, the SCell identifier or cell group (or SCG) identifier configured in the RRC message can be used. In Embodiment 3 of this disclosure, the SCell identifier or cell group (or SCG) identifier can indicate each SCell or each SCell identifier or cell group (or SCG) identifier that operates as follows: applying the DCI monitored by the terminal in the PDCCH and indicating the bitmap value of the DCI received during the active time period (within the active time).
[0436] refer to Figure 1L The base station can configure power-saving or DRX functions in the terminal via RRC messages, such as... Figure 1F As shown. The base station can configure configuration information in the terminal via RRC messages regarding the third DCI format (e.g., DCI format 1_1) that the terminal should detect for PCell or SPCell during the active time period 11-30 of the DRX cycle. When the terminal detects the third DCI format in PCell or SPCell, the terminal can determine whether there is a bitmap in the third DCI format that includes an indication of the terminal's identifier for each SCell or each PSCell or each SCell.
[0437] The third DCI format may include a resource allocation field, a field for frequency transmission resource allocation (frequency domain resource allocation), a modulation and coding scheme (MCS) field, a new data indicator (NDI) field, a redundancy version (RV) field, a HARQ process number field, an antenna port field, or a DMRS sequence initialization (DMRS SI) field. However, this disclosure is not limited thereto.
[0438] In the detected third DCI format, when the type indicated by the transmission resource type field (e.g., resourceAllocation) is the first type (e.g., resourceAllocationType0) and all bits of the field used for frequency transmission resource allocation are 0 or a specific value, or when the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the field used for frequency transmission resource allocation are 1 or a specific value, the terminal may not interpret subsequent bits or fields as MCS fields, or NDI fields, or RV fields, or HARQ process number fields, or antenna port fields, or DMRS SI fields. Instead, it may treat and read subsequent bits or fields as bitmap fields indicating switching or activation to a dormant BWP or switching or activation from a dormant BWP to a regular BWP configured in each SCell or PSCell in the terminal, or bits indicating pausing or resuming a cell group (or SCG) or a PSCell (or SCell) in a cell group (or SCG), and may apply the information indicated in the bitmap. In the detected third DCI format, when the type indicated by the transmission resource type field (e.g., resourceAllocation) is the first type (e.g., resourceAllocationType0) and all bits of the field used for frequency transmission resource allocation are not 0 or a specific value, or when the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the field used for frequency transmission resource allocation are not 1 or a specific value, the terminal may interpret, read and apply the subsequent fields or bits as the MCS field, or the NDI field, or the RV field, or the HARQ process number field, or the antenna port field, or the DMRS SI field.
[0439] Suppose a terminal detects the third DCI field in the PDCCH and scrambles or detects the third DCI field using a second terminal identifier (e.g., SPS-C-RNTI (or CS-RNTI)). When the type indicated by the transmission resource type field (e.g., resourceAllocation) in the third DCI format is the first type (e.g., resourceAllocationType0) and all bits of the field used for frequency transmission resource allocation are 0, or when the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the field used for frequency transmission resource allocation are 1, a special command configured in the terminal to activate or release periodic transmission resources can be indicated.
[0440] Therefore, in Embodiment 3 of this disclosure, only when the third DCI field in the PDCCH is detected by scrambling with the first terminal identifier (e.g., C-RNTI or MCS-C-RNTI), when the type indicated by the transmission resource type field (e.g., resourceAllocation) in the third DCI format is the first type (e.g., resourceAllocationType0) and all bits of the field used for frequency transmission resource allocation are 0 or a specific value, or when the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the field used for frequency transmission resource allocation are 1 or a specific value, the subsequent fields can be interpreted as a bitmap indicating the sleep BWP operation of each SCell of the terminal, or bits indicating the suspension or resumption of a cell group (or SCG) or a PSCell (or SCell) in a cell group (or SCG).
[0441] Through RRC messages, the base station can configure the search space or terminal identifier (e.g., C-RNTI or MCS-C-RNTI) for PDCCH monitoring in the terminal to detect the third DCI format during the activity period 11-30.
[0442] For example, the base station can transmit the third DCI format 1l-03 to the terminal in the PCell or SPCell through the transmission resources of the PDCCH during the active time period 1l-30, and the third DCI format 1l-03 may include bitmap 1l-04, which includes indication information about the dormant BWP of the third SCell group configured in the terminal, or bits indicating the suspension or resumption of the cell group (or SCG) or PSCell (or SCell) in the cell group (or SCG).
[0443] The first terminal 1l-10, which applies the information configured in the RRC message, can perform PDCCH monitoring (by scrambling) based on the first terminal identifier (e.g., C-RNTI or MCS-C-RNTI) configured as an identifier in the active time period 1l-30 of the DRX cycle, and can detect the third DCI format 1l-03 transmitted from the base station in the search space. When the third DCI format 1l-03 is detected, and when the type indicated by the transmission resource type field (e.g., resourceAllocation) is the first type (e.g., resourceAllocationType0) and all bits of the field used for frequency transmission resource allocation are 0, or when the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the field used for frequency transmission resource allocation are 1 (1l-20), the first terminal 1l-10 can interpret the subsequent fields as a bitmap indicating the sleep BWP operation of each SCell of the terminal, and can read bitmap 1l-04, which includes indication information about the sleep BWP of multiple SCells (or SCell identifiers) configured in the first terminal 1l-10, or bits indicating the suspension or resumption of cell group (or SCG) or PSCell (or SCell) in cell group (or SCG).
[0444] When the above conditions are met, since bitmap 1l-04 is interpreted by replacing the MCS field, NDI field, RV field, HARQ process number field, antenna port field, or DMRS SI field, bitmap 1l-04 can have a fixed length, such as 15 or 16 bits.
[0445] The bitmap mapping method in Embodiment 3 of this disclosure is as follows. For example, in the first bitmap method, each of bits 11-11, 11-12, 11-13, 11-14, and 11-15 of bitmap 11-04 can be mapped to each SCell in ascending or descending order of the SCell identifier values configured in the first terminal 11-10, starting from the right bit (e.g., from the LSB) or left bit (e.g., from the MSB) of the bitmap.
[0446] In another method, in the first bitmap mapping method, each of bits 11-11, 11-12, 11-13, 11-14, and 11-15 of bitmap 11-04 can be mapped to each SCell in ascending order of the SCell identifier values in the cell group (MCG or SCG) configured in the first terminal 11-10, starting from the right bit of the bitmap (e.g., from the LSB). When the terminal receives the third DCI format in the PCcell, each bit value can be mapped to the bitmap in ascending order of the SCell identifier values only for SCells belonging to the MCG. When the terminal receives the third DCI format in the PSCell, each bit value can be mapped to the bitmap in ascending order of the SCell identifier values only for SCells belonging to the SCG. Therefore, the bitmap is limited to and mapped to SCells belonging to one cell group because 32 SCell identifiers can be configured in a terminal, and the bitmap is 15 or 16 bits.
[0447] In another method, in the first bitmap mapping method, each of bits 11-11, 11-12, 11-13, 11-14, and 11-15 of bitmap 11-04 can be mapped to each SCell in descending order of the SCell identifier values in the cell group (MCG or SCG) configured in the first terminal 11-10, starting from the right bit of the bitmap (e.g., from the LSB). When the terminal receives the third DCI format in the PCcell, each bit value can be mapped to the bitmap in ascending order of the SCell identifier values only for SCells belonging to the MCG. When the terminal receives the third DCI format in the PSCell, each bit value can be mapped to the bitmap in descending order of the SCell identifier values only for SCells belonging to the SCG. Therefore, the bitmap is limited to and mapped to SCells belonging to one cell group because 32 SCell identifiers can be configured in a terminal, and the bitmap is 15 or 16 bits.
[0448] In another method, in the first bitmap mapping method, each of bits 11-11, 11-12, 11-13, 11-14, and 11-15 of bitmap 11-04 can be mapped to each SCell in descending order of the SCell identifier values in the cell group (MCG or SCG) configured in the first terminal 11-10, starting from the left bit of the bitmap (e.g., from the MSB). When the terminal receives the third DCI format in the PCcell, each bit value can be mapped to the bitmap in ascending order of the SCell identifier values only for SCells belonging to the MCG. When the terminal receives the third DCI format in the PSCell, each bit value can be mapped to the bitmap in descending order of the SCell identifier values only for SCells belonging to the SCG. Therefore, the bitmap is limited to and mapped to SCells belonging to one cell group because 32 SCell identifiers can be configured in a terminal, and the bitmap is 15 or 16 bits. In addition, new bits can be defined in the third DCI format 1l-03 of PDCCH, and these new bits can be used to indicate information about pausing or resuming a cell group (or SCG) or a PSCell (or SCell) within a cell group (or SCG).
[0449] When rules are applied that map from the left or right bit of a bitmap, the number of bitmaps that need to be read by the terminal is reduced, resulting in faster terminal processing.
[0450] When the bit value of each of bits 1l-11, 1l-12, 1l-13, 1l-14, and 1l-15 in bitmap 1l-04 is 0, bit value 0 can indicate switching to a dormant BWP or activation to a dormant BWP for each active SCell corresponding to that bit (when a dormant BWP is configured or included in the first SCell group or the second SCell group). In another approach, when the bit value of each of bits 1l-11, 1l-12, 1l-13, 1l-14, and 1l-15 in bitmap 1l-04 is 0, bit value 0 can indicate switching to a dormant BWP or activation to a dormant BWP if the active BWP is not a dormant BWP (or a regular BWP) for each active SCell corresponding to that bit. When a hibernation BWP is not configured in each of the corresponding active SCells in bitmap 1l-11, 1l-12, 1l-13, 1l-14 and 1l-15 of bitmap 1l-04, terminal 1l-10 may ignore, not read, or not apply the bit value.
[0451] When the bit value of each of bits 1l-11, 1l-12, 1l-13, 1l-14, and 1l-15 in bitmap 1l-04 is 1, for each active SCell corresponding to that bit, bit value 1 can indicate a switch to a regular BWP (e.g., the first active BWP activated from sleep) or activation to a regular BWP (e.g., the first active BWP activated from sleep). In another approach, when the bit value of each of bits 1l-11, 1l-12, 1l-13, 1l-14, and 1l-15 in bitmap 1l-04 is 1, if the currently active BWP is the sleep BWP (or not a regular BWP) of each active SCell corresponding to that bit, bit value 1 can indicate a switch to a regular BWP (e.g., the first active BWP activated from sleep) or activation to a regular BWP (e.g., the first active BWP activated from sleep). Otherwise (when the currently active BWP is not the dormant BWP (or regular BWP) of each active SCell corresponding to that bit), terminal 1l-10 may maintain, continue to use or apply, or activate the currently active BWP. In another approach, when the bit value of each of bits 1l-11, 1l-12, 1l-13, 1l-14, and 1l-15 of bitmap 1l-04 is 1, the bit value 1 may indicate a switch from a dormant BWP to a regular BWP (e.g., from the first active BWP activated from dormancy) or activation to a regular BWP (e.g., from the first active BWP activated from dormancy), or maintain or continue to use, apply, or activate the currently active BWP of each active SCell corresponding to that bit. When no dormant BWP is configured in the active SCell corresponding to the bit in the bitmap, terminal 1l-10 may ignore, not read, or not apply the bit value.
[0452] After receiving the DCI from the PDCCH in PCell 1l-01, the terminal can read the DCI and determine whether a bitmap exists that includes an indication of the BWP for a cell group (or SCG) or a PSCell (SCell) within a cell group (or SCG), or an indication to suspend or resume a cell group. When such a bitmap exists, the terminal can switch or activate the BWP or suspend or resume the cell group based on the bit value of the cell group (or SCG) or PSCell (or SCell) indicated by each bit of the bitmap. For example, when a bit in the bitmap indicates a PSCell (or SCell) within a cell group (or SCG) and the bit value is 1 (or 0), the terminal can resume or activate the cell group. When the bit value is 1 (or 0), indicating that the cell group (or SCG) or PSCell (or SCell) within that cell group (or SCG) should be switched or activated to a BWP other than a dormant BWP, or that the cell group should be restored, if the PSCell (or SCell) within the cell group (or SCG) is already active or restored, the terminal may not apply, ignore, or not read the bit value. Alternatively, for example, when a bit in the bitmap indicates a cell group (or SCG) or PSCell (or SCell) within the cell group (or SCG) and the bit value is 0 (or 1), the terminal can switch or activate the BWP of the cell group (or SCG) or PSCell (or SCell) corresponding to that bit value to a dormant BWP, or can suspend or deactivate that cell group. When the bit value is 0 (or 1), indicating that the cell group (or SCG) or the PSCell (or SCell) within the cell group (or SCG) should be switched to or activated to a dormant BWP, or that the cell group should be paused for the SCell or each SCell belonging to the SCell group, if the SCell is active and the activated BWP is a dormant BWP, this bit value may not be applied, ignored, or read. Alternatively, when the cell group (or SCG) or the PSCell (or SCell) within the cell group (or SCG) is already paused or deactivated, this bit value may not be applied, ignored, or read.
[0453] The third DCI format of the PDCCH according to Embodiment 3 of this disclosure can be used during the active period, and the terminal may not be accompanied by DL transmission resources (e.g., PDSCH) or UL transmission resources (e.g., PUSCH) for the terminal's PCell or SPCell. Therefore, in Embodiment 3 of this disclosure, the terminal can receive the third DCI format of the PDCCH and may not transmit ACK or NACK information (e.g., HARQ ACK or NACK) regarding the indication of the third DCI format.
[0454] When applying Embodiment 1, Embodiment 2, or Embodiment 3 of this disclosure, if the DL hibernation BWP configured in the terminal's SCell or PSCell is not configured as the DL default BWP, the BWP disable timer used to switch or convert the hibernation BWP to the default BWP does not need to be used. This is because when the default BWP is configured as a regular BWP other than the hibernation BWP, the BWP will automatically switch from the hibernation BWP to the regular BWP when the timer expires, which may cause battery consumption due to PDCCH monitoring.
[0455] Figure 1M A diagram is shown illustrating Embodiment 4, which extends Embodiment 1, Embodiment 2, or Embodiment 3 of this disclosure and applies it to a terminal in RRC disabled mode.
[0456] In Embodiment 4 of this disclosure, under RRC connection mode, the terminal can continue to store SCell configuration information (e.g., reference) of the cell group (e.g., SCG) configured or stored for Embodiments 1, 2, or 3 of this disclosure. Figure 1F The described configuration information) or PSCell (or SCell) configuration information is not released or discarded, even when the terminal transitions to RRC disabled mode. Additionally, when performing an RRC connection restoration procedure, a terminal in RRC disabled mode can determine whether to discard, release, maintain and apply, or reconfigure the SCell configuration information of the cell group (e.g., SCG) stored in the terminal (e.g., in the description of configuration information) or PSCell (or SCell) configuration information without releasing or discarding the configuration information, even when the terminal transitions to RRC disabled mode. Figure 1P The configuration information described or provided in the document (or PSCell (or SCell) configuration information). Additionally, when the base station transmits an RRCLease message to the terminal including a configuration or indicator to switch the terminal to RRC disabled mode, the base station may transmit an RRCLease message to the terminal including an indicator or configuration information indicating whether to discard or release, maintain and apply, or reconfigure the SCell configuration information of the cell group (e.g., SCG) stored in the terminal (e.g., reference). Figure 1P The described configuration information) or PSCell (or SCell) configuration information. Additionally, the terminal can move in RRC disabled mode, and when performing a RAN Notification Area (RNA) update, the terminal can receive and apply an indicator or configuration information via an RRC Release message transmitted from the base station to the terminal. This indicator or configuration information indicates whether to discard or release, maintain and apply, or reconfigure the SCell configuration information of the cell group (e.g., SCG) stored in the terminal (e.g., reference). Figure 1F The configuration information described) or PSCell (or SCell) configuration information.
[0457] In the RRC message, the SCell configuration information of the cell group (e.g., SCG) (e.g., reference) Figure 1F In the configuration information described and the PSCell (or SCell) configuration information, the base station can allow the first active BWP of the DL or UL BWP configuration information of each cell to be configured as a dormant BWP; and when the terminal activates each SCell, each cell group or PSCell in each cell group, the base station can directly operate the DL BWP or ULBWP of each SCell or each cell group or PSCell in each cell group as a dormant BWP, or can suspend or resume the cell group, thereby reducing the terminal's battery consumption.
[0458] In another approach, the SCell configuration information (e.g., reference) of the cell group (e.g., SCG) in the RRC message is used. Figure 1F In the configuration information described or the PSCell (or SCell) configuration information, the base station may not configure the first active BWP of the DL or UL BWP configuration information of each cell as a dormant BWP; and when the terminal activates or resumes each SCell, each cell group or PSCell in each cell group, the base station may always activate the DL BWP or UL BWP of each SCell or each cell group or PSCell in each cell group to the first active BWP, or switch or activate it to a dormant BWP according to implementation method 1, implementation method 2 or implementation method 3, or may pause or resume the cell group, thereby reducing the battery consumption of the terminal.
[0459] Implementation 4 of this disclosure can be extended and applied to the configuration information of each SCell of the MCG or SCG of a terminal configured with dual connectivity, or the configuration information of the PSCell. That is, when the terminal switches to RRC disabled mode, the SCell configuration information or PSCell configuration information of the SCG can still be stored; and when the base station performs an RRC connection restoration process or switches the terminal to RRC disabled mode, the base station can transmit an RRC message to the terminal including indicators or configuration information such as RRCResume, RRCReconfiguration, or RRCRelease, which indicates whether to discard or release, maintain and apply, or reconfigure the SCell configuration information of the MCG or SCG stored in the terminal (e.g., referencing...). Figure 1F (Description of configuration information) or PSCell configuration information.
[0460] refer to Figure 1M Terminal 1m-01 can establish a network connection with base station 1m-02 and can transmit / receive data (1m-05). When the base station needs to switch the terminal to RRC disabled mode for a specific reason, the base station can transmit an RRC Release message 1m-20 to the terminal and switch the terminal to RRC disabled mode. The base station can transmit an RRC message (e.g., RRC Release) to the terminal including an indicator or configuration information indicating whether to discard or release, maintain and apply, or reconfigure the SCell configuration information of the MCG or SCG stored in the terminal (e.g., reference). Figure 1F The configuration information described refers to the PSCell (or SCell) configuration information of a cell group (e.g., SCG). In the case of dual connectivity for the terminal application, it can be determined whether to suspend and resume the primary cell group bearer configuration or RRC configuration information, or the SCell configuration information of the MCG or SCG. This can be determined by querying the secondary cell base station to request whether to suspend and resume the secondary cell group bearer configuration and RRC configuration, and receiving a response from the secondary cell base station. In the RRC Release message, the base station can configure a list of frequencies to be measured by the terminal in RRC idle mode or RRC disabled mode, or frequency measurement configuration information, or frequency measurement time period.
[0461] When a terminal in RRC disabled mode receives a paging message (1m-25), needs to transmit UL data, or needs to update RNA while moving, it can perform the RRC connection restoration process.
[0462] When a terminal needs to configure a connection, it can perform a random access procedure and send an RRRCResumeRequest message (1m-30) to the base station. In this case, the terminal operations related to message transmission are as follows.
[0463] 1. The terminal can recognize system information, and when the system information indicates that a complete Terminal Connection Recovery Identifier (I-RNTI or Full Recovery ID) should be transmitted, the terminal can prepare to transmit a message including the stored complete Terminal Connection Recovery Identifier (I-RNTI). When the system information indicates that a truncated Terminal Connection Recovery Identifier (truncated I-RNTI or truncated Recovery ID) should be transmitted, the terminal can configure a truncated Terminal Connection Recovery Identifier (truncated Recovery ID) from the stored complete Terminal Connection Recovery Identifier (I-RNTI) using a specific method, and can prepare to transmit a message including the truncated Terminal Connection Recovery Identifier.
[0464] 2. The terminal can recover RRC connection configuration information and security context information from the stored terminal context.
[0465] 3. The terminal can update the new KgNB security key corresponding to the MCG based on the current KgNB security key, the next hop (NH) value, and the NH change counter (NCC) value received and stored in the RRCRelease message.
[0466] 4. When the terminal receives the SCG counter value (or sk counter) in the RRCRelease message, the terminal can update the new SKgNB security key corresponding to the SCG based on the KgNB security key and the SCG counter value (or sk counter).
[0467] 5. Terminals can obtain new security keys (K_RRCenc, K_RRC_int, K_UPint, and K_UPenc) to be used in the integrity protection and authentication process, as well as in the encryption and decryption process, by using the newly updated KgNB security key.
[0468] 6. When the terminal receives the SCG counter value (or sk counter) in the RRCrease message, the terminal can obtain the new security key (SK_RRCenc, SK_RRC_int, SK_UPint, and SK_UPenc) to be used in the integrity protection and verification process, as well as the encryption and decryption process, by using the newly updated SKgNB security key corresponding to the SCG.
[0469] 7. The terminal can calculate the Message Authentication Code (MAC-I) for integrity and can prepare to transmit a message including the MAC-I.
[0470] 8. The terminal may restore signaling radio bearer 1 (SRB1) (since the terminal will receive the RRCResume message via SRB1 in response to the RRCResumeRequest message to be transmitted, the terminal should restore SRB1 in advance).
[0471] 9. The terminal can configure the RRCResumeRequest message and can send the RRCResumeRequest message to the lower layer.
[0472] 10. For all bearers corresponding to the MCG except SRB0 (RBs terminated by the MCG), the integrity protection and verification process can be restored by applying the updated security key and the previously configured algorithm, and the integrity verification and protection can be applied to the data subsequently transmitted and received (in order to improve the reliability and security of the data subsequently transmitted / received from SRB1 or DRB).
[0473] 11. For all bearers corresponding to the MCG except SRB0 (RBs terminated by the MCG), the encryption and decryption process can be resumed by applying an updated security key and the previously configured algorithm, and the encryption and decryption can be applied to subsequently transmitted and received data (in order to improve the reliability and security of data subsequently transmitted / received from SRB1 or DRB).
[0474] 12. When the terminal receives the SCG counter value (or sk counter) in the RRRCRelease message, the terminal can resume the integrity protection and verification process by applying the updated security key and the previously configured algorithm to all bearers corresponding to the SCG (RBs where the SCG is terminated), and can apply integrity verification and protection to subsequently transmitted and received data (in order to improve the reliability and security of data subsequently transmitted / received from the DRB).
[0475] 13. When the terminal receives the SCG counter value (or sk counter) in the RRRCRelease message, the terminal can resume the encryption and decryption process by applying the updated security key and the previously configured algorithm to all bearers corresponding to the SCG (RBs where the SCG is terminated), and can apply the encryption and decryption to the data subsequently transmitted and received (in order to improve the reliability and security of the data subsequently transmitted / received from the DRB).
[0476] When a terminal needs to configure a connection and perform a random access procedure, transmits an RRCResumeRequest message to the base station, and then receives an RRCResume message (1m-35) in response, the terminal operates as follows. When the RRC message includes an indicator instructing the terminal to report in RRC disabled mode if valid frequency measurement results exist, the terminal can configure the frequency measurement results and report them in the RRCResumeComplete message. Additionally, the base station can transmit an RRC message (RRRCResume) to the terminal including an indicator or configuration information indicating whether to discard or release, maintain and apply, or reconfigure the SCell configuration information of the MCG or SCG stored in the terminal (e.g., refer to...). Figure 1F (Description of configuration information).
[0477] 1. When a message is received, the terminal can restore the PDCP state corresponding to the MCG, reset the counter value, and rebuild the PDCP layer of SRB2 and all DRBs (RBs that terminate the MCG) corresponding to the MCG.
[0478] 2. When the SCG counter value (or sk counter) is received in a message, the terminal can update the new SKgNB security key corresponding to the SCG based on the KgNB security key and the SCG counter value (sk counter). The terminal can obtain the new security keys (SK_RRCenc, SK_RRC_int, SK_UPint, and SK_UPenc) to be used in the integrity protection and verification process, as well as the encryption and decryption process, by using the newly updated SKgNB security key corresponding to the SCG.
[0479] 3. When the message includes MCG (Master Cell Group) configuration information,
[0480] - The MCG configuration information included in this message can be executed and applied. The MCG information may include configuration information about the RLC layer belonging to the MCG, logical channel identifiers, and bearer identifiers.
[0481] 4. When the message includes radiobearer configuration information (radioBearerConfig),
[0482] - The bearer configuration information (radioBearerConfig) included in this message can be executed and applied. The bearer configuration information (radioBearerConfig) may include configuration information for the PDCP layer, configuration information for the SDAP layer, logical channel identifier, and bearer identifier for each bearer.
[0483] 5. When the message includes SCG (masterCellgroup) configuration information,
[0484] - The SCG configuration information included in this message can be executed and applied. The SCG information may include configuration information about the RLC layer belonging to the SCG, logical channel identifiers, and bearer identifiers.
[0485] 6. When the message includes secondary bearer configuration information (radioBearerConfig),
[0486] - The secondary bearer configuration information (radioBearerConfig) included in this message can be executed and applied. The secondary bearer configuration information (radioBearerConfig) may include configuration information for the PDCP layer, configuration information for the SDAP layer, logical channel identifier, and bearer identifier for each secondary bearer.
[0487] 7. The terminal can restore SRB2 and all DRBs corresponding to MCG (RBs that terminate MCG).
[0488] 8. When the message includes frequency measurement configuration information (measConfig),
[0489] - The frequency measurement configuration information included in this message can be executed and applied. In other words, frequency measurements can be performed based on this configuration.
[0490] 9. The terminal can switch to RRC connection mode.
[0491] 10. The terminal can indicate to higher layers that a suspended RRC connection has been restored.
[0492] 11. The terminal can configure the RRCResumeComplete message and send it to the lower layer (1m-40).
[0493] When a terminal has the bearer configuration information and terminal context information for a suspended SCG, it can perform frequency measurements based on system information or the frequency configuration information configured in the RRCRelease or RRCResume message. When a valid measurement result exists, the terminal can transmit an RRCResumeComplete message including an indicator to indicate the existence of a valid measurement result. When the base station receives the indicator, if it needs to resume frequency aggregation or dual connectivity, the base station can instruct the terminal to report the frequency measurement result (1m-45) and can receive the frequency measurement result, or it can receive the frequency measurement result in the RRCResumeComplete message (1m-50). When the frequency measurement result is received, the base station can query the secondary cell base station whether to resume the bearer information of the suspended SCG, can receive a response, can confirm, and can transmit an RRCReconfiguration message to the terminal (1m-60) to indicate whether to resume or release the SCG bearer. Additionally, the base station can transmit an RRC message (e.g., RRCReconfiguration) to the terminal, which includes an indicator or configuration information indicating whether to discard or release, maintain and apply, or reconfigure the SCell configuration information of the MCG or SCG stored in the terminal (e.g., reference). Figure 1F (Description of configuration information).
[0494] exist Figure 1M In implementation 4, the SCell configuration information of the cell group (e.g., SCG) in the RRC message (e.g., RRC Resolve, RRC Resume, or RRC Reconfiguration) is referenced. Figure 1FIn the configuration information described (or PSCell (or SCell) configuration information), the base station may allow the first active BWP of the DL or UL BWP configuration information of each cell to be configured as a dormant BWP; and when the terminal activates each SCell or PSCell in each cell group (SCG), the base station may directly operate the DL BWP or UL BWP of each SCell or PSCell as a dormant BWP, or may pause or resume the cell group, thereby reducing the terminal's battery consumption. For example, for each SCell or PSCell, when the SCell state is configured to be active, or the cell group state is configured to be active, suspended, or disabled, or when an instruction to suspend or resume the cell group is configured in the SCell configuration information or cell group configuration information of an RRC message (e.g., RRC Release, RRC Resume, or RRC Reconfiguration), or when an instruction to activate the SCell is received in the MAC control information according to an embodiment of this disclosure, the SCell or PSCell can be activated, resumed, or suspended. Furthermore, the DL BWP or UL BWP of the SCell or PSCell can be activated directly when the SCell or PSCell is activated, thereby reducing the battery consumption of the terminal.
[0495] When a terminal in RRC disabled mode switches to RRC connected mode and restores, applies, or reconfigures the SCell configuration information or PSCell (or SCell) configuration information of the cell group (e.g., SCG) disclosed herein, according to Embodiment 1, Embodiment 2, Embodiment 3, or Embodiment 4 of this disclosure, handover or activation can be performed between BWPs for each activated SCell or PSCell (or SCell) in the cell group, or a dormant BWP can be activated or applied. Furthermore, Embodiment 4 of this disclosure can be applied even during handover.
[0496] When in implementation method 1 or implementation method 2 or implementation method 3 or Figure 1NWhen a MAC control message receives an indicator indicating the suspension, resumption, activation, or deactivation of a cell group or a PSCell within a cell group, the PHY or MAC layer receiving the indicator can transmit the indicator to a higher layer (e.g., MAC layer, RLC layer, PDCP layer, or RRC layer). When a higher layer receives an indicator (e.g., suspend, resume, activate, or deactivate a cell group) from a lower layer, the higher layer can execute the corresponding protocol layer procedure for suspending, resuming, activating, or deactivating the cell group. Alternatively, as in Embodiment 4 of this disclosure, when an indicator indicating the suspension, resumption, activation, or deactivation of a cell group or a PSCell within a cell group is received via an RRC message, the RRC layer receiving the indicator can transmit the indicator to a lower layer (e.g., PHY layer, MAC layer, RLC layer, or PDCP layer). When a lower layer receives an indicator (e.g., suspend, activate, or deactivate a cell group) from a higher layer (e.g., RRC layer), the lower layer can execute the corresponding protocol layer procedure for suspending, resuming, activating, or deactivating the cell group.
[0497] Various implementation methods can be configured and operated by combining or extending the implementation methods 1, 2, 3 and 4 of this disclosure.
[0498] Figure 1N A diagram illustrating MAC control information indicating the state transition of a cell, cell group, or cell group according to an embodiment of the present disclosure to an active (or recovered), dormant (or suspended), or disabled state.
[0499] Activities and disabling MAC CE according to this disclosure can have implementations according to this disclosure. Figure 1N The structure can be divided into MAC CE format 1n-05, which supports 7 SCells with a size of 1 byte, and MAC CE format 1n-10, which supports 31 SCells with a size of 4 bytes. In addition, MAC CE has the following characteristics.
[0500] - When the terminal does not receive a dormant MAC CE but only an active and disabled MAC CE, the terminal will operate as follows.
[0501] --Each field in the MAC CE for both active and disabled SCells indicates a specific SCell identifier, and the value of each field indicates whether the SCell is active or disabled. When the indicator value of the SCell indicated by the SCell identifier is 1, the SCell is activated if its state is disabled. However, when the SCell's state is not disabled, this indicator value is ignored. When the indicator value of the SCell indicated by the SCell identifier is 0, the SCell is disabled. That is, when the SCell's indicator value is 0, the SCell is disabled regardless of its state.
[0502] New MAC CEs can be designed to support and extend various implementations of this disclosure, or existing MAC CE functionality can be extended.
[0503] For example, references can be applied. Figure 1N The MAC CE described can be extended. Figure 1N The reserved bits (R bits) in 1n-05 or 1n-10 are used to expand and apply the reference. Figure 1N The described function.
[0504] - For example, when a reserved bit (e.g., the R field) is configured to 0 (or 1), a 1-bit indicator (e.g., the C field) indicating the identifier of each cell (SCell) can be defined and used as follows. In another approach, when a reserved bit (e.g., the R field) is configured to 0 (or 1), this can signify an indication to disable or suspend a cell group (e.g., an SCG). For example, a cell, BWP, or cell group in a disabled or suspended state can transition to a disabled state or remain in a disabled state, and a cell, BWP, or cell group in an active (or restored) state can transition to a disabled state. The indicator can be sent to higher layers.
[0505] --When the 1-bit indicator is configured to 0 (or 1), state transitions for each cell (e.g., SCell or SCell in MCG or SCG) or BWP can be performed as follows.
[0506] --- Switch a cell or BWP that is in a disabled state to a disabled state, or keep it in a disabled state.
[0507] --- Switch an active cell or BWP to a disabled state.
[0508] --When the 1-bit indicator is configured to 1, state transitions for each cell (e.g., SCell or SCell in MCG or SCG) can be performed as follows.
[0509] --- Switch an active cell or BWP to active status, or maintain active status.
[0510] ---Transform a disabled cell or BWP into an active state.
[0511] - When the reserved bit (R bit) is configured to 1 (or 1), a 1-bit indicator indicating the identifier of each cell (SCell) can be defined and used as follows. In another embodiment of this disclosure, a new logical identifier can be defined, which can be defined as follows and a new MAC CE can be defined and used. In another approach, when the reserved bit (e.g., the R field) is configured to 1 (or 0), this can signify an indication of activating or resuming a cell group (e.g., SCG). For example, a cell, BWP, or cell group in an active or resumed state can transition to an active state or can remain active, and a cell, BWP, or cell group in a disabled state (e.g., suspended state) can transition to an active state. The indicator can be given to higher layers.
[0512] --When the 1-bit indicator is configured to 0 (or 1), state transitions for each cell (e.g., SCell or SCell in MCG or SCG) or BWP can be performed as follows.
[0513] --- Switch a cell or BWP that is in a disabled state to a disabled state or keep it in a disabled state.
[0514] --- Switch an active cell or BWP to a disabled state.
[0515] --When the 1-bit indicator is configured to 1, state transitions can be performed for each cell (e.g., SCell or SCell in MCG or SCG) or BWP, as follows.
[0516] --- To switch an active cell or BWP to active status or maintain active status.
[0517] ---Transform a disabled cell or BWP into an active state.
[0518] For example, the functionality of the MAC CE can be extended and designed differently to indicate the state transition or handover of a cell or BWP, and can be applied to various embodiments of this disclosure. For example, new MAC control information can be designed, which may include cell group identifiers and cell identifiers, BWP identifiers, or bitmap information to indicate the activation (recovery), hibernation (or suspension), or deactivation (or suspension) of a cell group, cell, or BWP.
[0519] The process of reporting power margin according to embodiments of this disclosure will now be described.
[0520] The first implementation method for reporting power margin is as follows.
[0521] In Embodiment 1 of this disclosure, a power headroom reporting procedure can be used to provide the following information to the base station (serving gNB) serving the terminal. The power headroom can indicate the difference between the maximum transmit power (or calculated or nominal maximum transmit power) that the terminal can transmit in each active serving cell (PCell, SCell, PSCell, or SPCell) and the power measured for UL data transmission (UL-SCH) or SRS transmission, or it can indicate the difference between the maximum transmit power that the terminal can transmit and the power measured for PUCCH transmission and UL data transmission in an SPCell (PCell or PSCell) of another MAC layer (e.g., LTE MAC or E-UTRA MAC). The power headroom value can be configured in the MAC control information using the power headroom reporting procedure, and the power headroom can be reported to the base station via UL transmission resource transmission MAC control information.
[0522] - Type 1 power margin is the difference between the maximum transmit power (or calculated or nominal maximum transmit power) that the terminal can transmit for each active serving cell (PCell, SCell, PSCell, or SPCell) and the power measured for UL data transmission (UL-SCH), and can be reported.
[0523] Type 2 power margin is the difference between the maximum transmit power that the terminal can transmit (or the calculated or nominal maximum transmit power) and the power measured by the SpCell (PCell or PSCell) of another MAC layer (e.g., LTE MAC or E-UTRA MAC when dual connectivity is configured) for PUCCH transmission or UL data transmission (UL-SCH), and can be reported.
[0524] Type 3 power margin is the difference between the maximum transmit power (or calculated or nominal maximum transmit power) that a terminal can transmit for each active serving cell (PCell, SCell, PSCell, or SpCell) and the power measured for SRS transmission, and it can be reported.
[0525] Terminals can receive configuration information for power headroom reporting via RRC messages (e.g., RRCReconfiguration), and the RRC layer can adjust the power headroom reporting process using the following parameters.
[0526] - A timer value used for periodically reporting power headroom (phr-PeriodicTimer): For example, the power headroom reporting process can be triggered when the periodic power headroom reporting timer expires.
[0527] - Timer value for disabling power headroom reporting (phr-ProhibitTimer): For example, when the power headroom reporting disabling timer expires, the power headroom reporting process may not be triggered.
[0528] - The threshold used to trigger a power margin report (phr-Tx-PowerFactorChange);
[0529] - An indicator that takes into account the Type 2 power margin report of another cell or MAC layer (phr-Type2OtherCell);
[0530] - Indicates an indicator that takes into account the power margin report of another cell group (phr-ModeOtherCG);
[0531] - An indicator that indicates multiple power headroom reports (multiplePHR).
[0532] It can be done as follows Figure 1F Use the RRC message shown (e.g., RRCReconfiguration) to configure parameters.
[0533] The power margin reporting process can be triggered when an event occurs or one of the following conditions is met.
[0534] - The power headroom reporting process can be triggered when the power headroom reporting prohibition timer (phr-ProhibitTimer) expires or has expired, and the path loss in at least one active serving cell at a specific MAC layer changes by the threshold (phr-Tx-PowerFactorChange) dB configured in the RRC message. This path loss can be used as a path loss reference value when the MAC layer has (or receives) UL transmission resources for new transmissions after the most recent transmit power headroom at the MAC layer.
[0535] - The power margin reporting process can be triggered when the periodic power margin reporting timer expires.
[0536] - The power headroom reporting function can be triggered when it is configured or reconfigured at a higher level (e.g., the RRC layer). This configuration or reconfiguration may not be used to disable the power headroom reporting function.
[0537] - When a specific cell with a UL configured with a specific MAC layer is activated, the power margin reporting process can be triggered.
[0538] - The power margin reporting process can be triggered when a PSCell is added, newly added, or modified (or when dual connectivity is configured and a PSCell is newly added or modified in the SCG).
[0539] - When the Power Headroom Report Prohibit Timer expires or has expired, and the MAC layer has (or receives) UL transmission resources for new transmission, the Power Headroom Report procedure can be triggered if the following conditions are true or met for a specific active serving cell of a UL configured with a specific MAC layer.
[0540] --When there are UL transmission resources allocated for PUCCH transmission or transmission in the cell and the MAC layer has UL resources for PUCCH transmission or transmission in the cell, the power margin reporting process can be triggered if the power backoff required for cell power management (e.g., reducing interference from another frequency or avoiding harm to the human body) changes the threshold (phr-Tx-PowerFactorChange) dB configured in the RRC message after the power margin of the most recently transmitted transmission changes.
[0541] When one or more events occur or one or more conditions are met, thus triggering the power margin reporting process, the MAC layer can operate as follows.
[0542] When the MAC layer has or receives a UL assigned for a new transmission, the MAC layer can operate as follows.
[0543] -1> When the UL transmission resource following the most recent MAC reset process is the first UL transmission resource allocated for a new transmission.
[0544] --2> The periodic power margin reporting timer, used for periodically reporting power margin, can be started.
[0545] -1> When it is determined (or judged) that the power margin reporting process has been triggered and has not been canceled.
[0546] -1> When the allocated UL transmission resources may include MAC control information (MAC CE or MAC control element) or its sub-header (e.g., MAC sub-header) for power margin reporting configured to be transmitted by the MAC layer, or may be transmitted via transmission resources due to a Logical Channel Prioritization (LCP) process (e.g., the process of allocating UL transmission resources to data or MAC control information),
[0547] --2> When the indicator indicating multiple power headroom reports (multiplePHR) is configured to (or configured to report) true.
[0548] ---3> For each activated serving cell connected to a specific MAC layer or configured with a UL on a specific MAC layer.
[0549] ----4> The type 1 or type 3 power margin value of the UL carrier (or frequency) corresponding to the cell can be obtained (or calculated).
[0550] ----4> When the MAC layer has or receives UL transmission resources allocated for transmission of the serving cell
[0551] ----4> Alternatively, when another MAC layer is configured, which has or receives UL transmission resources allocated for the serving cell's transmission, and the indicator (phr-ModeOtherCG) indicating that power margin reporting takes into account another cell group is configured to true (or configured to report true) is displayed via a higher layer (RRC layer),
[0552] -----5> The maximum transmit power value corresponding to the serving cell (or the power value required for power margin calculation) can be obtained from the physical (PHY) layer.
[0553] ---3> When the indicator (phr-Type2OtherCell) that takes into account another cell or MAC layer type 2 power margin report is configured to true (or configured to report);
[0554] ----4> When the other MAC layer is an E-UTRA MAC layer
[0555] -----5> The value of the Type 2 power margin report for the SPCell of another MAC layer can be obtained (or calculated).
[0556] -----5> When the indicator (phr-ModeOtherCG) for power margin reporting of another cell group, as indicated by the higher layer (RRC layer), is configured to true (or configured to report a true value),
[0557] -----6> The maximum transmit power value of SPCell for another MAC layer (E-UTRA MAC layer) can be obtained from the physical layer (or the power value required for power margin calculation).
[0558] ---3> It can instruct the multiplexing and reassembly process to generate and transmit MAC control information (MAC layer multiplexing and reassembly process) reporting multiple power margins based on values reported from the physical layer.
[0559] --2> When the indicator indicating multiple power headroom reports (multiplePHR) is not configured to (or not configured to report) true, or when indicating a single power headroom report, or when using a single power headroom report format,
[0560] ---3> The Type 1 power margin value of the UL carrier (or frequency) of the serving cell (or PCell) can be obtained (or calculated) from the physical layer.
[0561] ---3> The maximum transmit power value (or the power value required for power margin calculation) for the serving cell (or PCell) can be obtained from the physical layer.
[0562] ---3> It can instruct the multiplexing and reassembly process to generate and transmit MAC control information that reports a power margin based on the value reported from the physical layer (MAC layer multiplexing and reassembly process).
[0563] --2> A timer that is used to periodically report power margin can be started or restarted.
[0564] --2> The timer used to disable power margin reporting can be started or restarted.
[0565] --2> You can cancel all triggered power margin or power margin reporting processes.
[0566] According to the power headroom reporting process of this disclosure, since the terminal reports power headroom to the base station for each cell, the base station can adjust or manage the terminal's UL transmit power. However, in the case of a cell (SCell) or serving cell configured with a dormant BWP according to this disclosure, or a suspended (or disabled) cell group or cell, when the current or activated BWP (or DL BWP) of the activated serving cell is a dormant BWP, or when activated to a BWP indicated by a dormant BWP identifier, or when the cell group is a suspended (or disabled) cell (e.g., PSCell or SCell), even if power headroom is reported, it is impossible to perform UL data transmission or PUCCH transmission in the dormant BWP or the suspended (or disabled) cell group or cell, thus performing unnecessary power headroom reporting.
[0567] Therefore, in order to reduce unnecessary processing load on the terminal and prevent waste of transmission resources caused by unnecessary power margin reports, the terminal can first determine whether the cell is active or deactivated, and can perform the following process: for the active cell, determine whether the active BWP (e.g., DL BWP) of the active cell is a dormant BWP (or a BWP with a dormant BWP identifier configured in the RRC message) or a non-dormant BWP (or a BWP without a dormant BWP identifier configured in the RRC message), or whether the cell group or cell (e.g., PSCell) is suspended (or deactivated) or activated (or restored). In another approach, the terminal can first determine whether the cell is active or deactivated, and can perform the following procedure: when a dormant BWP is configured (e.g., when a dormant BWP identifier is configured for the cell in an RRC message), for the active cell, determine whether the active BWP (e.g., DL BWP) of the active cell is a dormant BWP (or a BWP with a dormant BWP identifier configured in an RRC message) or a non-dormant BWP (or a BWP without a dormant BWP identifier configured in an RRC message). For cells without a configured dormant BWP, the process of identifying the active BWP can be omitted (or not performed).
[0568] In the case of a cell (SCell) or serving cell with a dormant BWP configured, during the identification process, the power headroom reporting procedure may not be triggered when the currently active or activated BWP (or DL BWP) of the activated serving cell is a dormant BWP, or when activated to a BWP indicated by the dormant BWP identifier, or when the cell group or cell (e.g., PSCell or SCell) is paused (or disabled), and the cell's power headroom may not be reported even if the power headroom reporting procedure is triggered by another cell. In another approach, in the case of a cell (SCell) or serving cell with a dormant BWP configured, the power headroom reporting procedure may be triggered only when the currently active or activated BWP (or DL BWP) of the activated serving cell is not a dormant BWP, or when not activated to a BWP indicated by the dormant BWP identifier, or when the cell group or cell (e.g., PSCell or SCell) is not paused (or disabled, activated, or restored). Therefore, even if the power headroom reporting process is triggered by another cell, power headroom can only be reported if the current or activated BWP (or DL BWP) of the activated serving cell is not a dormant BWP, or if it is not activated to the BWP indicated by the dormant BWP identifier, or if the cell group or cell (e.g., PSCell or SCell) is not suspended (or not deactivated, activated, or restored). Thus, the proposed process can reduce unnecessary processing load and prevent waste of transmission resources due to unnecessary power headroom reporting. Specific implementations of the proposed process are described in Implementation 2 of this disclosure, which takes into account the following dormant BWP.
[0569] In Implementation 2 of this disclosure, which takes into account a dormant BWP, a power headroom reporting procedure can be used to provide the following information to the base station (serving gNB) serving the terminal. The power headroom can indicate the difference between the maximum transmit power (or calculated or nominal maximum transmit power) that the terminal can transmit in each active serving cell (PCell, SCell, PSCell, or SPCell) and the power measured for UL data transmission (UL-SCH) or SRS transmission, or it can indicate the difference between the maximum transmit power that the terminal can transmit and the power measured for PUCCH transmission and UL data transmission in an SPCell (PCell or PSCell) at another MAC layer (e.g., LTE MAC or E-UTRA MAC). The power headroom value can be configured in the MAC control information through the power headroom reporting procedure, and the power headroom can be reported to the base station through UL transmission resource transmission MAC control information.
[0570] - Type 1 power margin is the difference between the maximum transmit power (or calculated or nominal maximum transmit power) that the terminal can transmit for each active serving cell (PCell, SCell, PSCell, or SPCell) and the power measured for UL data transmission (UL-SCH), and can be reported.
[0571] Type 2 power margin is the difference between the maximum transmit power that the terminal can transmit (or the calculated or nominal maximum transmit power) and the power measured by the SpCell (PCell or PSCell) of another MAC layer (e.g., LTE MAC or E-UTRA MAC when dual connectivity is configured) for PUCCH transmission or UL data transmission (UL-SCH), and can be reported.
[0572] Type 3 power margin is the difference between the maximum transmit power (or calculated or nominal maximum transmit power) that a terminal can transmit for each active serving cell (PCell, SCell, PSCell, or SpCell) and the power measured for SRS transmission, and it can be reported.
[0573] According to Embodiment 2 of this disclosure, which takes into account the reporting power margin of the dormant BWP, the following is an implementation method.
[0574] In Embodiment 2 of this disclosure, the terminal can receive configuration information for power margin reporting via RRC messages (e.g., RRCReconfiguration), and the RRC layer can adjust the power margin reporting process by using the following parameters.
[0575] - A timer value used for periodically reporting power headroom (phr-PeriodicTimer): For example, the power headroom reporting process can be triggered when the periodic power headroom reporting timer expires.
[0576] - Timer value used to disable power headroom reporting (phr-ProhibitTimer): For example, when the power headroom reporting disable timer expires, the power headroom reporting process is not triggered.
[0577] - The threshold used to trigger a power margin report (phr-Tx-PowerFactorChange);
[0578] - An indicator that takes into account the Type 2 power margin report of another cell or MAC layer (phr-Type2OtherCell);
[0579] - Indicates an indicator that takes into account the power margin report of another cell group (phr-ModeOtherCG);
[0580] - An indicator that indicates multiple power headroom reports (multiplePHR).
[0581] It can be done as disclosed herein. Figure 1F Use the RRC message shown (e.g., RRCReconfiguration) to configure parameters.
[0582] In Implementation 2 of the reporting power margin process taking into account the dormant BWP according to this disclosure, the power margin reporting process can be triggered when an event occurs or one of the following conditions is met.
[0583] - The power headroom reporting process can be triggered when the power headroom reporting prohibition timer (phr-ProhibitTimer) expires or has expired, the BWP (or DL BWP) of the active serving cell in a specific MAC layer is activated, and the path loss of at least one active serving cell (either the activated BWP (or DL BWP) of the active serving cell or the current BWP (or the currently active DL BWP) of the active serving cell is changed by the threshold (phr-Tx-PowerFactorChange) dB configured in the RRC message. This path loss can be used as a path loss reference value when the MAC layer has (or receives) UL transmission resources for new transmissions after the most recent transmit power headroom at the MAC layer.
[0584] - The power margin reporting process can be triggered when the periodic power margin reporting timer expires.
[0585] - The power headroom reporting function can be triggered when it is configured or reconfigured at a higher level (e.g., the RRC layer). This configuration or reconfiguration may not be used to disable the power headroom reporting function.
[0586] - When a specific cell of a UL configured with a specific MAC layer is activated and the first active DLBWP (or the first active DLBWP identifier (firstActiveDownlinkBWP-Id)) configured in the cell is not configured as a dormant BWP, the power margin reporting process can be triggered.
[0587] - The power margin reporting process can be triggered when a PSCell, cell group, or cell is added, newly added, or modified (or when dual connectivity is configured and a PSCell is newly added or modified in the SCG), or when a PSCell, cell group, or cell is activated or restored.
[0588] - In another approach, when a PSCell is added, newly added, or modified (or when dual connectivity is configured, or when a PSCell is newly added or modified in an SCG), or when a PSCell, cell group, or cell is activated or restored, the power margin reporting process can be triggered if the first active DL BWP (or the first active DL BWP identifier (firstActiveDownlinkBWP-Id) configured in the cell is not configured as a dormant BWP.
[0589] - When the power headroom reporting prohibit timer expires or has expired, and the MAC layer has (or receives) UL transmission resources for new transmission, the power headroom reporting process can be triggered if the following conditions are true or met for a specific active serving cell of a UL configured with a specific MAC layer.
[0590] --When there are UL transmission resources allocated for PUCCH transmission or transmission in the cell and the MAC layer has UL resources for PUCCH transmission or transmission in the cell, the power margin reporting process can be triggered if the power backoff required for cell power management (e.g., reducing interference from another frequency or avoiding harm to the human body) changes the threshold (phr-Tx-PowerFactorChange) dB configured in the RRC message after the power margin of the most recently transmitted transmission changes.
[0591] - The power margin reporting process can be triggered when a UL BWP is activated (or when it is activated to the first active UL BWP), or when a DL BWP (or an activated BWP or the current BWP (or DL BWP)) configured with a specific active SCell of UL in a specific MAC layer switches from a dormant BWP or is activated to a regular BWP (or a BWP other than a dormant BWP (non-dormant BWP)) or when a non-dormant BWP configured in an RRC message to be activated from dormancy first (indicated by firstActiveNonDormantDownlinkBWP-Id or BWP identifier other than a dormant BWP) is activated.
[0592] - A power headroom reporting procedure can be triggered when a DL BWP (or activated BWP or current BWP (or DL BWP)) of a specific activated SCell configured with UL in a specific MAC layer is activated to the BWP specified in the RRC message as the first BWP to be activated from sleep by the BWP identifier (firstOutsideActiveTimeBWP-Id or firstWithinActiveTimeBWP-Id). Activation of a BWP can be indicated by the DCI in the PDCCH.
[0593] - The power margin reporting process can be triggered when a UL BWP is activated (or when it is activated to the first active UL BWP), or when a DL BWP (or an activated BWP or the current BWP (or DL BWP)) configured with a specific active SCell of a UL in a specific MAC layer switches from a dormant BWP or is activated to a regular BWP (or a BWP other than a dormant BWP (non-dormant BWP)) or when a non-dormant BWP configured in an RRC message that was first activated from dormancy (a BWP other than a dormant BWP indicated by firstActiveNonDormantDownlinkBWP-Id, firstOutsideActiveTimeBWP-Id, or firstWithinActiveTimeBWP-Id or BWP identifier), or when the first SRS configuration information or the second SRS configuration information is configured (or when the activated BWP (or DL BWP) or the current BWP (or the activated current DL BWP) of the active serving cell is a dormant BWP and the first SRS configuration information or the second SRS configuration information is configured).
[0594] - The power headroom reporting process can be triggered when the power headroom reporting prohibition timer (phr-ProhibitTimer) expires or has expired, when the BWP (or DL BWP) of the active serving cell in a specific MAC layer is activated and the activated BWP (or DL BWP) is not a dormant BWP, or when the activated BWP (or DL BWP) or the current BPW (or the activated current BWP) of the active serving cell is not a dormant BWP, or when the first SRS configuration information or the second SRS configuration information is configured (or when the activated BWP (or DL BWP) or the current BWP (or the activated current DL BWP) of the active serving cell is a dormant BWP and the first SRS configuration information or the second SRS configuration information is configured), if the path loss changes by the threshold (phr-Tx-PowerFactorChange) dB configured in the RRC message for at least one active serving cell. This path loss can be used as a path loss reference value when the MAC layer has (or receives) UL transmission resources for a new transmission after the most recent transmit power headroom in the MAC layer.
[0595] When one or more events occur or one or more conditions are met, thus triggering the power margin reporting process, the MAC layer can operate as follows.
[0596] When the MAC layer has or receives a UL assigned for a new transmission, the MAC layer can operate as follows.
[0597] -1> When the UL transmission resource following the most recent MAC reset process is the first UL transmission resource allocated for a new transmission.
[0598] --2> The periodic power margin reporting timer, used for periodically reporting power margin, can be started.
[0599] -1> When it is determined or judged that the power margin reporting process has been triggered and will not be canceled.
[0600] -1> When the allocated UL transmission resources may include MAC control information (MAC CE or MAC control element) or its sub-headers (e.g., MAC sub-headers) for power margin reporting configured to be transmitted by the MAC layer, or may be transmitted via transmission resources due to an LCP process (e.g., the process of allocating UL transmission resources to data or MAC control information),
[0601] --2> When the indicator indicating multiple power headroom reports (multiplePHR) is configured to (or configured to report) true.
[0602] ---3> For each activated serving cell connected to a specific MAC layer or configured with a UL on a specific MAC layer.
[0603] ---3> When the BWP (or DL BWP) of the serving cell is activated and the activated BWP (or DL BWP) is not a dormant BWP, or when the activated BWP (or DL BWP) or the current BWP (or the activated current DL BWP) of the serving cell is not a dormant BWP, or when the cell group or cell (e.g., PSCell) is not paused or deactivated.
[0604] ---3> When the BWP (or DL BWP) of the activated serving cell is activated and the activated BWP (or DL BWP) is not a dormant BWP, or when the activated BWP (or DL BWP) or the current BWP (or the activated current DL BWP) of the activated serving cell is not a dormant BWP, or when the cell group or cell (e.g., PSCell) is not paused or disabled, or when the first SRS configuration information or the second SRS configuration information is configured (or when the activated BWP (or DL BWP) or the current BWP (or the activated current DL BWP) of the activated serving cell is a dormant BWP and the first SRS configuration information or the second SRS configuration information is configured)
[0605] ----4> The type 1 or type 3 power margin value of the UL carrier (or frequency) corresponding to the cell can be obtained (or calculated).
[0606] ----4> When the MAC layer has or receives UL transmission resources allocated for transmission of the serving cell
[0607] ----4> Alternatively, when another MAC layer is configured, which has or receives UL transmission resources allocated for the serving cell's transmission, and the indicator (phr-ModeOtherCG) indicating that power margin reporting takes into account another cell group is configured to true (or configured to report true) is displayed via a higher layer (RRC layer),
[0608] -----5> The maximum transmit power value corresponding to the serving cell (or the power value required for power margin calculation) can be obtained from the physical (PHY) layer.
[0609] ---3> When the indicator (phr-Type2OtherCell) that takes into account another cell or MAC layer type 2 power margin report is configured to true (or configured to report);
[0610] ----4> When the other MAC layer is an E-UTRA MAC layer
[0611] -----5> The value of the Type 2 power margin report for the SPCell of another MAC layer can be obtained (or calculated).
[0612] -----5> When the indicator (phr-ModeOtherCG) for power margin reporting of another cell group, as indicated by the higher layer (RRC layer), is configured to true (or configured to report a true value),
[0613] -----6> The maximum transmit power value of SPCell for another MAC layer (E-UTRA MAC layer) can be obtained from the physical layer (or the power value required for power margin calculation).
[0614] ---3> It can instruct the multiplexing and reassembly process to generate and transmit MAC control information (MAC layer multiplexing and reassembly process) reporting multiple power margins based on values reported from the physical layer.
[0615] --2> When the indicator indicating multiple power headroom reports (multiplePHR) is not configured to (or not configured to report) true, or when indicating a single power headroom report, or when using a single power headroom report format,
[0616] ---3> The Type 1 power margin value of the UL carrier (or frequency) of the serving cell (or PCell) can be obtained (or calculated) from the physical layer.
[0617] ---3> The maximum transmit power value (or the power value required for power margin calculation) for the serving cell (or PCell) can be obtained from the physical layer.
[0618] ---3> It can instruct the multiplexing and reassembly process to generate and transmit MAC control information that reports a power margin based on the value reported from the physical layer (MAC layer multiplexing and reassembly process).
[0619] --2> A timer that is used to periodically report power margin can be started or restarted.
[0620] --2> The timer used to disable power margin reporting can be started or restarted.
[0621] --2> You can cancel all triggered power margin or power margin reporting processes.
[0622] Figure 10 A flowchart is shown of a first signaling process for configuring or releasing dual connections, or activating, resuming, suspending or deactivating an SCG configured with dual connections, according to an embodiment of this disclosure.
[0623] refer to Figure 10 The terminal can be configured with an RRC connection to a network or base station, as disclosed herein. Figure 1F As shown, it can perform data transmission or reception with base stations (e.g., MCG, master node (MN), or cells of MCG (PCell or SCell)).
[0624] For specific reasons (e.g., when a high data rate is required at the request of a terminal (IO-05), or when high QoS requirements must be met), a base station may configure dual connectivity in a terminal. For example, the terminal may send a request to the base station to configure, release, activate, deactivate, resume, or suspend dual connectivity, a cell group (e.g., SCG), or a cell. The terminal's request message may include a frequency (or channel) measurement result report, or a cell group identifier, or a cell identifier, or a measurement result (IO-05). Alternatively, the base station may determine whether to configure, release, add, deactivate, activate, resume, modify, reconfigure, or suspend dual connectivity, a cell group (e.g., SCG), or a cell by considering the amount of DL (or UL) data or buffer size.
[0625] The primary base station (MN or MCG) can receive frequency or channel measurement reports for frequencies or channels received from the base station and can determine the secondary base station (secondary node (SN) or SCG) for configuring dual connectivity based on the measurement reports. Alternatively, the primary base station can determine whether to configure, release, add, disable, activate, restore, modify, reconfigure, or suspend dual connectivity, cell group (e.g., SCG), or cell by considering the amount of DL (or UL) data or buffer size. In order to configure, release, add, disable, activate, restore, modify, reconfigure, or suspend dual connectivity, cell group (e.g., SCG), or cell to the determined secondary base station, the primary base station can transmit a request message 1o-10 to the secondary base station via the Xn interface (e.g., an interface between base stations) or the Sn interface (an interface between a base station and an AMF, UMF, or a base station) to request the configuration or addition of an SCG to the terminal. To configure, release, add, disable, activate, restore, modify, reconfigure, or suspend dual connectivity, cell groups (e.g., SCGs), or cells for a secondary base station, each individual new request message can be defined and used. Alternatively, new indicators can be defined in existing messages (e.g., SN add request message, SN modify request message, or SN release request message) to indicate (or request) the configuration, release, addition, disabling, activation, restoration, modification, reconfiguration, or suspension of cell groups (e.g., SCGs) or cells. Request messages 1o-10 may include information such as cell group configuration information currently configured in the terminal (e.g., MCG configuration information), or bearer configuration information, or terminal capability information, or frequency (or channel) measurement results information of the terminal. By referring to the above information, the secondary base station can configure the SCG configuration information or bearer configuration information to adapt to the terminal capability, or not exceed the terminal capability, or match the MCG bearer configuration information when an SCG is configured in the terminal.
[0626] When a secondary base station that has received request messages 1o-10 rejects the request message, the secondary base station can configure the rejection message and transmit the rejection message to the primary base station (1o-15) via the Xn interface (e.g., an interface between base stations) or the Sn interface (an interface between a base station and an AMF, UMF, or between base stations). When a secondary base station accepts the request message, the secondary base station can transmit a request acceptance message to the primary base station (1o-15) via the Xn interface (e.g., an interface between base stations) or the Sn interface (an interface between a base station and an AMF, UMF, or between base stations). The request acceptance message includes configuration information or indicators for configuring, releasing, adding, disabling, activating, resuming, modifying, reconfiguring, or suspending dual connectivity, cell groups (e.g., SCGs), or cells. The request acceptance message may include some of the following information.
[0627] - An identifier that is the same as the message identifier included in the request message, or an indicator that indicates acceptance of the request in the request message.
[0628] - Configuration information or indicators (e.g., configuration information or indicators for MCG) used to configure, release, add, deactivate, activate, restore, modify, reconfigure, or pause dual connectivity, cell groups (e.g., SCG), or cells.
[0629] - Including a first RRC message (e.g., an RRCReconfiguration message) for configuring, releasing, adding, disabling, activating, restoring, modifying, reconfiguring, or pausing dual connectivity, cell groups (e.g., SCGs), or cell configuration information or indicators.
[0630] - The first RRC message may include some of the following information.
[0631] --A first RRC message identifier (e.g., rrc-Transaction identifier) used to identify the first RRC message. Since the terminal and base station (e.g., a secondary base station) transmit or receive multiple RRC messages between them, an identifier used to identify each RRC message can be included in the RRC message. For example, the same first RRC identifier can be included in an RRC message transmitted by the transmitter (e.g., RRCReconfiguration), or an RRC message transmitted by the receiver that corresponds to the RRC message (e.g., RRCReconfiguration) (e.g., RRCReconfigurationComplete), or an RRC message corresponding to the RRC message transmitted by the transmitter.
[0632] --Configuration information or indicators (e.g., configuration information or indicators for a terminal) used to configure, release, add, disable, activate, restore, modify, reconfigure, or pause dual connectivity, cell groups (e.g., SCG), or cells.
[0633] --Indicators indicating the status of a cell group (e.g., active, disabled, paused, or resumed).
[0634] --A cell group identifier used to identify cells within a cell group. The cell group identifier can be assigned by the primary base station, or one of the allowed (or preset) identifiers can be assigned by the secondary base station.
[0635] --Cell group or cell configuration information
[0636] --Bearer configuration information. For example, indicator information indicating the operation of each bearer's protocol layer (e.g., SDAP layer, PDCP layer, RLC layer, or MAC layer) (e.g., PDCP pause indicator, PDCP rebuild indicator, PDCP data recovery indicator, RLC rebuild indicator, MAC partial reset indicator, MAC reset indicator, or indicator triggering a new operation).
[0637] --When including configuration information or indicators for configuring, adding, activating, restoring, modifying, or reconfiguring dual connectivity, cell groups (e.g., SCGs), or cells, a first indicator (e.g., mobilityControlInfor or ReconfigurationWithSync) may also be included. When including configuration information or indicators for releasing, disabling, reconfiguring, or pausing dual connectivity, cell groups (e.g., SCGs), or cells, a first indicator (e.g., mobilityControlInfor or ReconfigurationWithSync) may not be included. The first indicator may be an indicator that triggers a random access procedure in a cell group or cell, or an indicator that performs signal synchronization with a new cell, or an indicator that indicates frequency shifting of a terminal, or an indicator that indicates modification of a cell group (or cell).
[0638] --When including configuration information or indicators for configuring, adding, activating, restoring, modifying, or reconfiguring dual connectivity, cell groups (e.g., SCGs), or cells, random access configuration information may also be included. When including configuration information or indicators for releasing, disabling, reconfiguring, or suspending dual connectivity, cell groups (e.g., SCGs), or cells, random access configuration information may not be included. Random access configuration information may include random access transport resource information (time or frequency transport resources) for preamble transmission, or specified preamble information for cell groups or cells.
[0639] --Time information indicating when to activate, resume, deactivate, or suspend dual connectivity, cell group (e.g., SCG), or cell (PSCell or SCG SCell) (e.g., information indicating timing (e.g., X), time unit, subframe, slot, or symbol unit; for example, when a message is received in the nth time unit, the time information indicates whether the cell is activated, resumed, deactivated, or suspended in the n+Xth time unit).
[0640] When the primary base station receives a request to receive message 1o-15, it can identify the request to accept message and can transmit a second RRC message 1o-20 (e.g., RRCReconfiguration) to the terminal, which includes information contained in the request to accept message (e.g., the first RRC message included in the request to accept message 1o-15). The second RRC message may include some of the following information.
[0641] --A second RRC message identifier (e.g., an rrc-Transaction identifier) used to identify the second RRC message. Since the terminal and the base station (e.g., the primary base station) transmit or receive multiple RRC messages between them, the RRC messages may include an identifier used to identify each RRC message. For example, the same second RRC identifier may be included in an RRC message transmitted by the transmitter (e.g., RRCReconfiguration), or an RRC message transmitted by the receiver that corresponds to the RRC message (e.g., RRCReconfiguration) (e.g., RRCReconfigurationComplete), or an RRC message corresponding to the RRC message transmitted by the transmitter.
[0642] - The first RRC message included in the request acceptance message 1o-15
[0643] - Configuration information or indicators (e.g., terminal-specific configuration information or indicators) used to configure, release, add, disable, activate, restore, modify, reconfigure, or pause dual connectivity, cell groups (e.g., SCG), or cells.
[0644] - Indicators indicating the status of a cell group (e.g., active, disabled, paused, or resumed).
[0645] - A cell group identifier used to identify cells within a cell group. The cell group identifier can be assigned by the primary base station, or one of the allowed identifiers can be assigned by the secondary base station.
[0646] - Cell group or cell configuration information
[0647] - Bearer configuration information. For example, indicator information indicating the operation of each bearer's protocol layer (e.g., SDAP layer, PDCP layer, RLC layer, or MAC layer) (e.g., PDCP pause indicator, PDCP rebuild indicator, PDCP data recovery indicator, RLC rebuild indicator, MAC partial reset indicator, MAC reset indicator, or indicator triggering a new operation).
[0648] - When including configuration information or indicators for configuring, adding, activating, restoring, modifying, or reconfiguring dual connectivity, cell groups (e.g., SCGs), or cells, a first indicator (e.g., mobilityControlInfor or ReconfigurationWithSync) may also be included. When including configuration information or indicators for releasing, disabling, reconfiguring, or pausing dual connectivity, cell groups (e.g., SCGs), or cells, a first indicator (e.g., mobilityControlInfor or ReconfigurationWithSync) may not be included. The first indicator may be an indicator that triggers a random access procedure in a cell group or cell, an indicator that performs signal synchronization with a new cell, an indicator that indicates frequency shifting for the terminal, or an indicator that indicates modification of a cell group (or cell). In another approach, the terminal may perform PDCCH monitoring in the indicated or configured cell group or cell and may trigger and execute a random access procedure based on an indication indicated in the PDCCH. For example, a higher layer (e.g., the RRC layer) may transmit an indicator that triggers a random access procedure to a lower layer (e.g., the MAC layer).
[0649] - Random access configuration information may also be included when including configuration information or indicators for configuring, adding, activating, restoring, modifying, or reconfiguring dual connectivity, cell groups (e.g., SCGs), or cells. Random access configuration information may be excluded when including configuration information or indicators for releasing, disabling, reconfiguring, or suspending dual connectivity, cell groups (e.g., SCGs), or cells. Random access configuration information may include random access transport resource information (time or frequency transport resources) for preamble transmission, or specified preamble information for cell groups or cells.
[0650] - Time information indicating when to activate, resume, deactivate, or suspend dual connectivity, cell group (e.g., SCG), or cell (PSCell or SCG SCell) (e.g., information indicating timing (e.g., X), time unit, subframe, slot, or symbol unit; for example, when a message is received in the nth time unit, the time information indicates whether the cell is activated, resumed, deactivated, or suspended in the n+Xth time unit).
[0651] When the terminal receives the second RRC message 1o-20, the terminal can read and identify the second RRC message, or read the information included in the second RRC message (e.g., the first RRC message included in the second RRC message), and can configure, add, modify, resume, suspend, or disable dual connectivity or cell groups (e.g., SCG). Additionally, when a first indicator for triggering a random access procedure is included in the second or first RRC message, the terminal can trigger a random access procedure for the configured or indicated cell group or cell. When executing a random access procedure, if random access information exists in the RRC message or if stored random access information exists, the terminal can execute the random access procedure based on the stored random access information or the random access information or system information received in the RRC message (e.g., CFRA procedure (e.g., 4-step random access or 2-step random access)). When random access information does not exist in the RRC message, the terminal can execute a random access procedure (e.g., CBRA procedure (e.g., 4-step random access or 2-step random access)). In another approach, the terminal can perform PDCCH monitoring within the indicated or configured cell group or cell, and can trigger and execute a random access procedure based on the indications in the PDCCH. For example, a higher layer (e.g., the RRC layer) can transmit an indication to a lower layer (e.g., the MAC layer) to trigger the random access procedure.
[0652] The terminal can receive the second RRC message 1o-20 or the configuration information received by the application, and can generate the third RRC message 1o-25 or the fourth RRC message, and can transmit the third RRC message or the fourth RRC message to the base station. The third RRC message may include some of the following information.
[0653] - A second RRC message identifier having the same value as the second RRC message identifier included in the second RRC message.
[0654] - An indicator or identifier that indicates successful reception of the second RRC message.
[0655] - The fourth RRC message includes a response indicating successful reception of the first RRC message generated and transmitted by the secondary base station. The fourth RRC message may include some of the following information.
[0656] --The first RRC message identifier has the same value as the first RRC message identifier included in the first RRC message.
[0657] -- An indicator or identifier that indicates successful reception of the first RRC message.
[0658] --Indicator of successful application of the first RRC message response
[0659] When a base station (e.g., the primary base station) receives a third RRC message, it can determine whether the third RRC message is a response to the second RRC message using a second identifier. The base station can identify a fourth RRC message included in the third RRC message, and can include the fourth RRC message in a configuration completion message indicating that configuration is complete to the SCG base station. This configuration completion message (1o-30) can be transmitted to the secondary base station via the Xn interface (e.g., an interface between base stations) or the Sn interface (an interface between the base station and the AMF, UMF, or other base stations). The configuration completion message may include some of the following information.
[0660] - The fourth RRC message included in the third RRC message
[0661] - An indicator or identifier that indicates that the configuration (cell group addition, modification, or release) or indication (e.g., cell group activation, deactivation, suspension, or resumption) indicated in the request acceptance message or the first RRC message has been completed.
[0662] When a base station (e.g., a secondary base station) receives a configuration complete message, it can read or identify the fourth RRC message included in the configuration complete message, and can determine whether the fourth RRC message is a response message to the first RRC message using a first identifier. It can be determined whether the configuration or instruction indicated by the base station has been successfully completed. When the secondary base station receives the configuration complete message or the fourth RRC message, it can transmit an indication to the primary base station as a response message indicating successful receipt of the configuration complete message or the fourth RRC message.
[0663] Figure 1P A flowchart is shown of a second signaling process for configuring or releasing dual connections, or configuring, releasing, activating, resuming, suspending, or deactivating an SCG configured with dual connections, according to an embodiment of this disclosure.
[0664] refer to Figure 1P The terminal can be configured with an RRC connection to a network or base station, as disclosed herein. Figure 1F As shown, it can perform data transmission or reception with base stations (e.g., cells of MCG, MN, or MCG (PCell or SCell)).
[0665] For specific reasons (e.g., when a high data rate is required at the request of a terminal (1p-05), or when high QoS requirements must be met), a base station can configure dual connectivity in a terminal. For example, the terminal can send a request to the base station to configure, release, activate, deactivate, resume, or suspend dual connectivity, a cell group (e.g., SCG), or a cell. The terminal's request mes...
Claims
1. A method performed by a user equipment (UE) for activating a secondary cell (SCell), the method comprising: Receive Radio Resource Control (RRC) messages from the base station, which include cell configuration information. The cell configuration information includes a BWP identifier indicating the first downlink bandwidth portion (BWP) for activating the SCell, and information about a reference signal for activating the SCell. The information regarding the reference signals used to activate the SCell indicates the interval between the reference signals used to activate the SCell and the number of reference signals used to activate the SCell; Receive from the base station a Media Access Control (MAC) control element (CE) for activating the SCell; Based on the interval between the reference signals used to activate the SCell and the number of reference signals used to activate the SCell, the reference signal for activating the SCell is received from the base station in the first downlink BWP indicated by the BWP identifier; and Activate the SCell.
2. The method according to claim 1, wherein, The RRC message also includes a BWP identifier indicating the first uplink BWP used to activate the SCell.
3. The method according to claim 2, further comprising: In response to the MAC CE used to activate the SCell, the first uplink BWP is activated.
4. The method according to claim 1, wherein, The cell configuration information also includes information about channel measurement signals.
5. A method performed by a base station for activating a secondary cell (SCell), the method comprising: Transmit a Radio Resource Control (RRC) message containing cell configuration information to the User Equipment (UE). The cell configuration information includes a BWP identifier indicating the first downlink bandwidth portion (BWP) for activating the SCell, and information about a reference signal for activating the SCell. The information regarding the reference signals used to activate the SCell indicates the interval between the reference signals used to activate the SCell and the number of reference signals used to activate the SCell; Transmit a Media Access Control (MAC) CE to the UE for activating the secondary cell SCell; and Based on the interval between the reference signals used to activate the SCell and the number of reference signals used to activate the SCell, the reference signal for activating the SCell is transmitted to the UE in the first downlink BWP indicated by the BWP identifier. Specifically, the SCell is activated at the UE.
6. The method according to claim 5, wherein, The RRC message also includes a BWP identifier indicating the first uplink BWP used to activate the SCell.
7. The method according to claim 6, wherein, In response to the MAC CE used to activate the SCell, the first uplink BWP is activated at the UE.
8. The method according to claim 5, wherein, The cell configuration information also includes information about channel measurement signals.
9. A user equipment (UE) configured to activate a secondary cell (SCell), the UE comprising: Memory; transceiver; as well as A processor, connected to the memory and the transceiver, and the processor is configured to: Receive Radio Resource Control (RRC) messages from the base station, which include cell configuration information. The cell configuration information includes a BWP identifier indicating the first downlink bandwidth portion (BWP) for activating the SCell, and information about a reference signal for activating the SCell. The information regarding the reference signals used to activate the SCell indicates the interval between the reference signals used to activate the SCell and the number of reference signals used to activate the SCell; Receive from the base station a Media Access Control (MAC) control element (CE) for activating the SCell; Based on the interval between the reference signals used to activate the SCell and the number of reference signals used to activate the SCell, the reference signal for activating the SCell is received from the base station in the first downlink BWP indicated by the BWP identifier; and Activate the SCell.
10. The UE according to claim 9, wherein, The RRC message also includes a BWP identifier indicating the first uplink BWP used to activate the SCell.
11. The UE according to claim 10, wherein, The processor is also configured to: In response to the MAC CE used to activate the SCell, the first uplink BWP is activated.
12. The UE according to claim 9, wherein, The cell configuration information also includes information about channel measurement signals.
13. A base station configured to activate a secondary cell (SCell), the base station comprising: Memory; transceiver; as well as A processor, connected to the memory and the transceiver, and the processor is configured to: Transmit a Radio Resource Control (RRC) message containing cell configuration information to the User Equipment (UE). The cell configuration information includes a BWP identifier indicating the first downlink bandwidth portion (BWP) for activating the SCell, and information about a reference signal for activating the SCell. The information regarding the reference signals used to activate the SCell indicates the interval between the reference signals used to activate the SCell and the number of reference signals used to activate the SCell; Transmit a Media Access Control (MAC) CE to the UE for activating the secondary cell SCell; and Based on the interval between the reference signals used to activate the SCell and the number of reference signals used to activate the SCell, the reference signal for activating the SCell is transmitted to the UE in the first downlink BWP indicated by the BWP identifier. Specifically, the SCell is activated at the UE.
14. The base station according to claim 13, wherein, The RRC message also includes a BWP identifier indicating the first uplink BWP used to activate the SCell.
15. The base station according to claim 14, wherein, In response to the MAC CE used to activate the SCell, the first uplink BWP is activated at the UE.
16. The base station according to claim 13, wherein, The cell configuration information also includes information about channel measurement signals.