Method and apparatus for monitoring wireless connection of multi-carrier cell in wireless communication system

The method and apparatus for RLM on multiple carriers in wireless communication systems address connection management challenges, ensuring stable and efficient service delivery by monitoring anchor and non-anchor carriers.

WO2026240567A1PCT designated stage Publication Date: 2026-11-19SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2026/096803
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2026-04-10
Filing Date
2026-05-11
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing wireless communication systems face challenges in effectively managing wireless connections in cells composed of multiple carriers, leading to potential connection failures and inefficiencies in service provision.

Method used

A method and apparatus for a terminal to perform Radio Link Monitoring (RLM) on multiple carriers, including an anchor and non-anchor carrier, to maintain wireless connections and manage connection failures.

Benefits of technology

Enhances the ability of terminals to maintain stable wireless connections and manage connection failures in cells with multiple carriers, improving service reliability and efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2026096803_19112026_PF_FP_ABST
    Figure KR2026096803_19112026_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. A method performed by a user equipment (UE) in a wireless communication system, according to various embodiments of the present disclosure, may comprise the steps of: receiving, from a base station, configuration information including information for configuring a cell including one or more downlink (DL) carriers and radio link monitoring (RLM) configuration information configured for each DL carrier from among the one or more DL carriers; and performing RLM on a first DL carrier and / or a second DL carrier from among the one or more DL carriers, wherein the first DL carrier can be an anchor carrier and the second DL carrier can be a non-anchor carrier.
Need to check novelty before this filing date? Find Prior Art

Description

Method and apparatus for monitoring wireless connection of a cell composed of multiple carriers in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. More specifically, the present disclosure relates to a method for monitoring the connection status of a terminal in a wireless communication system and an apparatus capable of performing the same.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] As a result of the aforementioned developments and advancements in mobile communication systems, it has become possible to provide a variety of services, and thus measures to effectively provide these services are required.

[0009] The present disclosure proposes an operation required for wireless connection management according to each wireless resource unit and a network operation according to the same, in a cell in which a terminal is composed of multiple carriers.

[0010] Based on the discussion described above, the disclosed embodiment aims to provide an apparatus and method capable of effectively providing services in a mobile communication system.

[0011] The technical problems to be solved by the present invention are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below.

[0012] According to various embodiments of the present disclosure, a method performed by a terminal (user equipment, UE) in a wireless communication system may include: receiving from a base station information for setting up a cell comprising one or more DL (downlink) carriers and RLM setting information set for each of the one or more DL carriers; and performing RLM (radio link monitoring) on ​​at least one of a first DL carrier or a second DL carrier among the one or more DL carriers, wherein the first DL carrier is an anchor carrier and the second DL carrier is a non-anchor carrier.

[0013] According to various embodiments of the present disclosure, in a wireless communication system, a terminal (user equipment, UE) comprises: at least one transceiver; and at least one processor communicatively coupled to the at least one transceiver. and includes at least one memory that is communicationally coupled to the at least one processor and stores instructions, wherein the instructions are executed by the at least one processor individually or in any combination, so that the terminal receives from a base station information for setting up a cell including one or more DL (downlink) carriers and RLM setting information set for each of the one or more DL carriers, and may perform RLM (radio link monitoring) on ​​at least one of the first DL carrier or the second DL carrier among the one or more DL carriers, wherein the first DL carrier is an anchor carrier and the second DL carrier is a non-anchor carrier.

[0014] According to an embodiment of the present invention, a terminal performs monitoring based on the wireless connection status on a cell composed of multiple carriers, and introduces an operation to process the connection failure, thereby enabling the terminal to maintain a wireless connection.

[0015] The effects obtainable from the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art to which the present disclosure belongs from the description below.

[0016] FIG. 1 illustrates the structure of an LTE system according to one embodiment of the present invention.

[0017] FIG. 2 illustrates a wireless protocol structure in an LTE system according to one embodiment of the present invention.

[0018] FIG. 3 illustrates the structure of a next-generation mobile communication system according to one embodiment of the present invention.

[0019] FIG. 4 illustrates the wireless protocol structure of a next-generation mobile communication system according to one embodiment of the present invention.

[0020] FIG. 5 illustrates the structure of a terminal according to one embodiment of the present disclosure.

[0021] FIG. 6 illustrates the structure of a base station according to one embodiment of the present disclosure.

[0022] FIG. 7 illustrates a cell structure of a communication system according to one embodiment of the present disclosure.

[0023] FIG. 8 illustrates an example of setting a cell including multiple carriers according to one embodiment of the present disclosure.

[0024] FIG. 9 illustrates another example of setting a cell including multiple carriers according to one embodiment of the present disclosure.

[0025] FIG. 10 illustrates another example of setting a cell including multiple carriers according to one embodiment of the present disclosure.

[0026] FIG. 11 illustrates an example of an RLM operation according to one embodiment of the present disclosure.

[0027] FIG. 12 illustrates another example of an RLM operation according to one embodiment of the present disclosure.

[0028] FIG. 13 illustrates another example of an RLM operation according to one embodiment of the present disclosure.

[0029] FIG. 14 illustrates another example of an RLM operation according to one embodiment of the present disclosure.

[0030] FIG. 15 illustrates another example of an RLM operation according to one embodiment of the present disclosure.

[0031] FIG. 16 illustrates another example of an RLM operation according to one embodiment of the present disclosure.

[0032] FIG. 17 illustrates an example of an RLF related to a RACH failure according to one embodiment of the present disclosure.

[0033] FIG. 18 is a block diagram of a terminal or user equipment (1800) according to one embodiment of the present disclosure.

[0034] FIG. 19 is a block diagram of a base station (1900) according to one embodiment of the present disclosure.

[0035] FIG. 20 is a block diagram of a network entity (2000) that performs network functions according to one embodiment of the present disclosure.

[0036] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0037] In describing the embodiments, technical details that are well known in the art to which this disclosure belongs and are not directly related to this disclosure are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.

[0038] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same or different reference numbers.

[0039] The advantages and features of the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the specification.

[0040] In the present disclosure, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams may be performed based on computer program instructions. Since these computer program instructions may be optionally loaded into at least one processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions performed through any one or any combination of at least one processor of the computer or other programmable data processing equipment create means for performing the functions described in the flow diagram block(s). Since these computer program instructions may also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the functions in a specific manner, the instructions stored in computer-available or computer-readable memory may also produce a manufactured item containing means of instruction for performing the functions described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

[0041] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks (or functions) described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to the corresponding function.

[0042] As used in the embodiments of the present disclosure, the term “part” refers to a software or hardware component, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and the “part” performs certain roles. However, the term including “part” is not limited to software or hardware. The “part” may be configured to reside in an addressable storage medium or may be configured to run on one or more processors. Thus, by example, the “part” includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and “parts” may be combined into a smaller number of components and “parts” or further separated into additional components and “parts.” In addition, the components and 'parts' may be implemented to utilize one or more CPUs (central processing units) within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0043] As stated above, it should be noted that the blocks of each flowchart and combinations of flowcharts described in this disclosure may be executed by one or more computer programs including instructions. The entirety of one or more computer programs may be stored in a single memory device, or one or more computer programs may be divided into different parts and stored across multiple memory devices.

[0044] Additionally, any / any function or operation described in this disclosure may be processed by a single processor or a combination of processors. The single processor or combination of processors is a circuitry that performs processing and may include an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural network processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system-on-chip (SoC), an IC, or similar circuitry.

[0045] Additionally, it should be noted that various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0046] Such software may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium stores one or more computer programs (software modules), and said one or more computer programs include computer-executable instructions that operate an electronic device to perform a method according to the present disclosure when executed alone or collectively by one or more processors of an electronic device.

[0047] The software may be stored in a transient or non-transient storage device, for example, in the form of read-only memory (ROM) (whether or not it is erasable or rewritable), or random access memory (RAM), memory chips, devices, or integrated circuits (ICs). Additionally, the software may be stored in the form of an optically or magnetically readable medium, for example, a compact disc (CD), a digital multifunction disc (DVD), a magnetic disc, or a magnetic tape. It should be understood that the storage device and the storage medium are examples of non-transient machine-readable storage media suitable for storing programs for implementing various embodiments of the present disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing a device or method according to any one of the claims of this specification, and a non-transient machine-readable storage medium storing such program.

[0048] In the following disclosure, determining the priority between A and B may be referred to in various ways, such as selecting the one with the higher priority according to a predetermined priority rule and performing the corresponding action, or omitting or dropping the action for the one with the lower priority.

[0049] Hereinafter, 'A or B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0050] Additionally, 'at least one of A, B, and C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0051] Additionally, 'at least one of A, B, or C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0052] Additionally, 'A / B' as described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0053] Additionally, 'A, B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0054] Additionally, 'A and B' described in the present disclosure may be understood as 'A and / or B', which may be understood as including 'A', or 'B', or 'A and B'.

[0055] Furthermore, the phrase "when conditions A and B are satisfied" as described in the present disclosure is not necessarily limited to cases where both conditions A and B are satisfied, but may be understood to include cases where either condition A or condition B is satisfied individually, cases where both conditions A and B are satisfied, or cases where one or more additional conditions are satisfied together.

[0056] Furthermore, throughout this specification, ordinal terms (and similar modifiers) such as 'first', 'second', 'third', etc. are used solely for the purpose of distinguishing various instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information, as described below. Unless clearly required otherwise by the context, the use of such ordinal terms does not require that the elements, operations, or information distinguished by such terms be structurally different, numerically distinct, or essentially different. For example, 'first signal' and 'second signal' may represent instances of the same signal transmitted at different times, signals containing the same core information even with some variations, or signals having different content or characteristics depending on the specific context. Similarly, 'first value' and 'second value' may represent the same magnitude measured or applied in different situations, or may represent different magnitudes. Such interpretation must be determined based on the specific technical context, function, and relationship described in the relevant parts of the specification and claims.

[0057] Furthermore, although terms such as "first," "second," etc., as used in this disclosure are used for various elements such as information, objects, actions, and sequences, they are not intended to limit such elements to a specific order. These terms may be understood merely as distinguishing one element from another. For example, a first element may be referred to as a second element, and likewise, a second element may be referred to as a first element.

[0058] Additionally, the terms 'first' and 'second' described in this disclosure may be understood to refer to identical or different elements. For example, if an element is information, the first information and the second information may both be information, and depending on the case, they may be the same information or different information.

[0059] Furthermore, the expressions 'if' and 'in case that' described in this disclosure or claims may be interpreted, depending on the context, as meaning 'when or upon,' 'in response to,' 'based on,' or 'according to,' and these expressions may be used interchangeably. In addition, other expressions having substantially the same meaning may be used as substitutes, provided that they do not impair the technical features of this disclosure.

[0060] Additionally, the term "not perform" as used in this disclosure or claims may be understood, depending on the context, to mean to omit or skip the corresponding step. Such a term may be replaced with other terms having the same or substantially similar meaning.

[0061] Additionally, the phrase "transmitting a message containing A and B" as described in this specification may be interpreted to include not only (i) cases where A and B are transmitted as a single message, but also (ii) cases where A and B are transmitted individually through multiple messages (e.g., transmitting a first message containing A and a second message containing B). This interpretation may also apply to cases where messages containing two or more items, such as A, B, and C, are transmitted together or individually.

[0062] In addition, 'transmitting a message containing A and transmitting a message containing B' can also be interpreted as transmitting a single message containing A and B.

[0063] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure will be expressed in the singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the circumstances presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed in the singular form, and even if a component is expressed in the singular form, it may be composed in the plural form.

[0064] The drawings or flowcharts described below illustrate exemplary methods that may be implemented in accordance with the principles of the present disclosure, and various modifications may be made to the methods illustrated in the flowcharts of the present disclosure. For example, although illustrated as a series of steps, the various steps of each drawing or flowchart may overlap, occur in parallel, occur in a different order, or occur multiple times. In other examples, any step may be omitted or replaced with another step.

[0065] The methods and devices proposed in the embodiments of the present disclosure below are not limited to each embodiment and may be utilized as a combination of all or part of the embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within the scope that does not deviate significantly from the scope of the present disclosure, at the judgment of a person skilled in the art.

[0066] In this case, any wording mentioned in different embodiments may be used interchangeably, combined, or substituted if the concepts correspond. For example, regarding the same or corresponding concepts, even if the expression 'A' is used in one embodiment and the expression 'B' is used in another embodiment, they may be understood by interchangeably, substituted, or combined.

[0067] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. Furthermore, where appropriate, such terms may be replaced with terms defined in the 3GPP (3rd generation partnership project) Technical Specifications (TS).

[0068] Hereinafter, the base station, as the entity performing resource allocation for terminals, may be at least one of gNode B, eNode B, Node B, BS (base station), wireless access unit, base station controller, or a node on a network. Additionally, the base station of the present disclosure may include a structure split into a central unit (CU) and a distributed unit (DU). In such a structure, the CU is responsible for the upper layer of the control and user plane, and the DU is responsible for wireless resource processing of the lower layer. The embodiments of the present disclosure can be equally applied to a 5G base station structure in which functions are separated into the CU and DU as described above.

[0069] The terminal may include a UE (user equipment), MS (mobile station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions.

[0070] In the present disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station.

[0071] In addition, while a 5th generation mobile communication system (5G, new radio, NR) and a 6th generation mobile communication system (6G) may be described below as examples, embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, new advanced mobile communication systems developed after 5G and 6G may be included therein. Furthermore, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) with some modifications made in the judgment of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0072] In the following description, the terms "physical channel" and "signal" may be used interchangeably with "data" or "control signal." For example, PDSCH (physical downlink shared channel) is a term referring to a physical channel through which data is transmitted, but PDSCH may also be used to refer to data. That is, in this disclosure, the expression "transmits a physical channel" may be interpreted as equivalent to the expression "transmits data or a signal through a physical channel."

[0073] In describing the present disclosure below, the term "upper layer signaling" may be a signaling corresponding to at least one or a combination of at least one of MIB (master information block), SIB (system information block), SIB M (M=1, 2, ...), RRC (radio resource control), MAC (medium access control), CE (control element), NAS (non-access stratum) signaling, or application layer messages. The RRC signaling may also be referred to as L3 signaling (layer 3 signaling).

[0074] Additionally, L1 signaling may be a signaling method corresponding to at least one or a combination of at least one of the following: a physical layer channel or signaling of a PDCCH (physical downlink control channel), a DCI (downlink control information), a UE-specific DCI, a group common DCI, a common DCI, a scheduling DCI (e.g., a DCI used for the purpose of scheduling downlink or uplink data), a non-scheduling DCI (e.g., a DCI not used for the purpose of scheduling downlink or uplink data), a PUCCH (physical uplink control channel), or an UCI (uplink control information). The above L1 signaling may also be referred to as physical layer signaling.

[0075] Hereinafter, the expression in the present disclosure or claims that information can be configured from a base station may mean that, depending on the context, a terminal receives said information from a base station through physical layer signaling or upper layer signaling, and such expression may be replaced with other terms having the same or substantially similar meaning.

[0076] The operating principle of the present invention will be described in detail below with reference to the attached drawings. In describing the present invention below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the invention. Furthermore, the terms described below are defined considering their functions in the present invention, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0077] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0078] Hereinafter, a base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. A terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while an LTE or LTE-A system may be described as an example below, embodiments of this disclosure may be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in a system to which embodiments of this disclosure can be applied, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without departing significantly from the scope of the present disclosure. In this case, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams may be executed by computer program instructions.

[0079] Since these computer program instructions can be loaded onto the processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means for performing the functions described in the flowchart block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement functions in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing means of instruction for performing the functions described in the flowchart block(s). Since the computer program instructions can also be loaded onto the computer or other programmable data processing equipment, the instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a computer-executable process can also provide steps for performing the functions described in the flowchart block(s).

[0080] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). Also, it should be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order according to the corresponding function. In this case, the term "part" as used in this embodiment refers to software or hardware components such as a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC), and the "part" may perform certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Accordingly, as an example, 'part' includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or further separated into additional components and 'parts'. Furthermore, the components and 'parts' may be implemented to utilize one or more CPUs within a device or secure multimedia card. Additionally, in an embodiment, 'part' may include one or more processors.

[0081] For the convenience of the following explanation, the present invention uses terms and names defined in the 5GS and NR specifications, which are standards defined by the 3GPP (The 3rd Generation Partnership Project) organization among existing communication standards. However, the present invention is not limited by the above terms and names and can be applied in the same way to wireless communication networks according to other standards. For example, the present invention can be applied to 3GPP 5GS / NR (e.g., 5th generation mobile communication standards).

[0082] FIG. 1 illustrates the structure of an LTE system according to one embodiment of the present invention.

[0083] Referring to FIG. 1, as illustrated, the wireless access network of an LTE system may be composed of a next-generation base station (Evolved Node B) (hereinafter ENB, Node B or base station) (105, 110, 115, 120), a Mobility Management Entity (MME) (125), and an S-GW (130, Serving-Gateway). A user terminal (User Equipment) (hereinafter UE or terminal) (135) can connect to an external network through the ENB (105 to 120) and the S-GW (130).

[0084] In FIG. 1, the ENB (105 to 120) can correspond to the existing Node B of the UMTS system. The ENB is connected to the UE (135) via a wireless channel and can perform more complex roles than the existing Node B. In an LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, can be serviced through a shared channel. Therefore, a device is required to collect status information such as the buffer status, available transmission power status, and channel status of the UEs to perform scheduling, and this can be handled by the ENB (105 to 120). A single ENB can typically control multiple cells. For example, to achieve a transmission speed of 100 Mbps, the LTE system can use Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology, for example, in a 20 MHz bandwidth. In addition, an Adaptive Modulation & Coding (AMC) method can be applied to determine the modulation scheme and channel coding rate according to the channel conditions of the terminal. The S-GW (130) is a device that provides a data bearer and can create or remove the data bearer under the control of the MME (125). The MME is a device that is responsible for various control functions as well as mobility management functions for the terminal and can be connected to multiple base stations.

[0085] FIG. 2 illustrates a wireless protocol structure in an LTE system according to one embodiment of the present invention.

[0086] Referring to FIG. 2, the wireless protocol of the LTE system can be composed of a Packet Data Convergence Protocol (PDCP) (205, 240), Radio Link Control (RLC) (210, 235), and Medium Access Control (MAC) (215, 230) at the terminal and the ENB, respectively.

[0087] PDCP can handle operations such as IP header compression and decompression. The main functions of PDCP can be summarized as follows.

[0088] - Header compression and decompression features (ROHC only)

[0089] - User data transfer function (Transfer of user data)

[0090] - Sequential delivery function (In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM)

[0091] - Order reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0092] - Duplicate detection function (Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

[0093] - Retransmission function (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of ​​PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

[0094] - Encryption and decryption functions (Ciphering and deciphering)

[0095] - Timer-based SDU discard in uplink.

[0096] Radio Link Control (RLC) (210, 235) can perform ARQ operations, etc., by reconfiguring PDCP Packet Data Units (PDUs) to an appropriate size. The main functions of RLC can be summarized as follows.

[0097] - Data transfer function (Transfer of upper layer PDUs)

[0098] - ARQ function (Error Correction through ARQ (only for AM data transfer))

[0099] - Concatenation, segmentation, and reassembly functions (Concatenation, segmentation, and reassembly of RLC SDUs (only for UM and AM data transfer))

[0100] - Re-segmentation function (Re-segmentation of RLC data PDUs (only for AM data transfer))

[0101] - Reordering function (Reordering of RLC data PDUs (only for UM and AM data transfer)

[0102] - Duplicate detection function (only for UM and AM data transfer)

[0103] - Error detection function (Protocol error detection (only for AM data transfer))

[0104] - RLC SDU deletion function (RLC SDU discard (only for UM and AM data transfer))

[0105] RLC re-establishment function

[0106] MAC (215, 230) is connected to multiple RLC layer devices configured in a terminal and can perform operations to multiplex RLC PDUs into MAC PDUs and demultiplex RLC PDUs from MAC PDUs. The main functions of MAC can be summarized as follows.

[0107] - Mapping function (Mapping between logical channels and transport channels)

[0108] - Multiplexing and demultiplexing function (Multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels)

[0109] - Scheduling information reporting function

[0110] - HARQ function (Error correction through HARQ)

[0111] - Priority handling between logical channels of one UE

[0112] - Priority handling between UEs by means of dynamic scheduling

[0113] - MBMS service identification function

[0114] - Transport format selection function

[0115] - Padding

[0116] The physical layer (220, 225) can perform channel coding and modulation of upper layer data, create OFDM symbols and transmit them to the wireless channel, or demodulate OFDM symbols received through the wireless channel and channel decode them to transmit them to the upper layer.

[0117] FIG. 3 illustrates the structure of a next-generation mobile communication system according to one embodiment of the present invention.

[0118] Referring to FIG. 3, the wireless access network of a next-generation mobile communication system (hereinafter NR or 5G) may be composed of a next-generation base station (New Radio Node B) (hereinafter NR gNB or NR base station) (310) and a next-generation wireless core network (New Radio Core Network, NR CN) (305). A next-generation wireless user terminal (New Radio User Equipment) (NR UE or terminal) (315) can connect to an external network through the NR gNB (310) and the NR CN (305).

[0119] In FIG. 3, the NR gNB (310) can correspond to the eNB (Evolved Node B) of the existing LTE system. The NR gNB is connected to the NR UE (315) via a wireless channel and can provide superior service compared to the existing Node B. In the next-generation mobile communication system, all user traffic can be serviced through a shared channel. Therefore, a device is required to collect state information such as the buffer status, available transmission power status, and channel status of the UEs to perform scheduling, and the NR NB (310) can handle this scheduling. A single NR gNB can control multiple cells. In the next-generation mobile communication system, to achieve ultra-high-speed data transmission compared to standard LTE, a bandwidth greater than the standard maximum bandwidth may be applied. Additionally, Orthogonal Frequency Division Multiplexing (OFDM) can be used as the wireless access technology, and beamforming technology can be additionally incorporated. In addition, an Adaptive Modulation & Coding (hereinafter AMC) method may be applied to determine the modulation scheme and channel coding rate according to the channel conditions of the terminal. The NR CN (305) can perform functions such as mobility support, bearer configuration, and QoS configuration. The NR CN is a device responsible for various control functions as well as mobility management functions for the terminal, and can be connected to multiple base stations. In addition, the next-generation mobile communication system can be interoperable with an LTE system, and the NR CN can be connected to the MME (325) via a network interface. The MME can be connected to the eNB (330), which is an LTE base station.

[0120] FIG. 4 illustrates the wireless protocol structure of a next-generation mobile communication system according to one embodiment of the present invention.

[0121] Referring to FIG. 4, the wireless protocol of the next-generation mobile communication system consists of the NR Service Data Adaptation Protocol (SDAP) (401, 445), NR PDCP (405, 440), NR RLC (410, 435), NR MAC (415, 430), and NR PHY (420, 425) at the terminal and the NR base station, respectively.

[0122] The main functions of NR SDAP (401, 445) may include some of the following functions.

[0123] - User data transfer function (transfer of user plane data)

[0124] - Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

[0125] - Marking QoS flow ID in both DL and UL packets for uplink and downlink

[0126] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0127] For SDAP layer devices, the terminal may receive a Radio Resource Control (RRC) message indicating whether to use the SDAP layer device header or the SDAP layer device functions for each PDCP layer device, bearer, or logical channel. If the SDAP header is configured, the terminal may be instructed to update or reset the mapping information for the uplink and downlink QoS flows and data bearers using the 1-bit NAS reflective QoS and AS reflective QoS indicators of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priorities, scheduling information, etc., to support seamless service.

[0128] The main functions of NR PDCP (405, 440) may include some of the following functions.

[0129] - Header compression and decompression features (ROHC only)

[0130] - User data transfer function (Transfer of user data)

[0131] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

[0132] - Out-of-sequence delivery of upper layer PDUs

[0133] - Reordering function (PDCP PDU reordering for reception)

[0134] - Duplicate detection function (Duplicate detection of lower layer SDUs)

[0135] - Retransmission of PDCP SDUs

[0136] - Encryption and decryption functions (Ciphering and deciphering)

[0137] - Timer-based SDU discard in uplink.

[0138] In the above description, the reordering function of the NR PDCP device may refer to a function that reorders PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number). The reordering function of the NR PDCP device may include a function that transmits data to an upper layer in the reordered order, or a function that transmits it immediately without considering the order, a function that records lost PDCP PDUs by reordering, a function that reports the status of lost PDCP PDUs to the transmitting side, and a function that requests retransmission of lost PDCP PDUs.

[0139] The main functions of NR RLC (410, 435) may include some of the following functions.

[0140] - Data transfer function (Transfer of upper layer PDUs)

[0141] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

[0142] - Out-of-sequence delivery of upper layer PDUs

[0143] - ARQ function (Error Correction through ARQ)

[0144] - Concatenation, segmentation, and reassembly functions of RLC SDUs

[0145] - Re-segmentation function (Re-segmentation of RLC data PDUs)

[0146] - Reordering function (Reordering of RLC data PDUs)

[0147] - Duplicate detection

[0148] - Error detection function (Protocol error detection)

[0149] - RLC SDU discard function

[0150] RLC re-establishment function

[0151] In the above description, the in-sequence delivery function of the NR RLC device may refer to the function of delivering RLC SDUs received from a lower layer to an upper layer in sequence. In the case where a single RLC SDU is received divided into multiple RLC SDUs, the in-sequence delivery function of the NR RLC device may include the function of reassembling and delivering them.

[0152] The in-sequence delivery function of the NR RLC device may include a function to rearrange received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number), a function to record lost RLC PDUs by rearranging the order, a function to report the status of lost RLC PDUs to the transmitting side, and a function to request retransmission of lost RLC PDUs.

[0153] The in-sequence delivery function of the NR RLC device may include a function to deliver only the RLC SDUs prior to the lost RLC SDU in order to the upper layer if there is a lost RLC SDU. The in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received before the timer started in order to the upper layer if a predetermined timer has expired, even if there is a lost RLC SDU. The in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received up to the present in order to the upper layer if a predetermined timer has expired, even if there is a lost RLC SDU. The NR RLC device may process RLC PDUs in the order they are received and deliver them to the NR PDCP device, regardless of the sequence number order (out-of-sequence delivery). When an NR RLC device receives a segment, it may receive segments stored in a buffer or to be received later, reconstruct them into a single complete RLC PDU, and then deliver it to an NR PDCP device. The NR RLC layer may not include a concatenation function, and this function may be performed by the NR MAC layer or replaced by the multiplexing function of the NR MAC layer. In the above description, the out-of-sequence delivery function of the NR RLC device may refer to the function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order. The out-of-sequence delivery function of the NR RLC device may include the function of reassembling and delivering RLC SDUs when an original single RLC SDU is received divided into multiple RLC SDUs.The out-of-sequence delivery function of the NR RLC device may include the function of storing the RLC SN or PDCP SN of the received RLC PDUs and sorting the order to record the lost RLC PDUs.

[0154] The NR MAC (415, 430) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include some of the following functions.

[0155] - Mapping function (Mapping between logical channels and transport channels)

[0156] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)

[0157] - Scheduling information reporting function

[0158] - HARQ function (Error correction through HARQ)

[0159] - Priority handling between logical channels of one UE

[0160] - Priority handling between UEs by means of dynamic scheduling

[0161] - MBMS service identification function

[0162] - Transport format selection function

[0163] - Padding

[0164] The NR PHY layer (420, 425) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0165] FIG. 5 illustrates the structure of a terminal according to one embodiment of the present disclosure.

[0166] Referring to FIG. 5, the terminal includes an RF (Radio Frequency) processing unit (510), a baseband processing unit (520), a storage unit (530), and a control unit (540).

[0167] The RF processing unit (510) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. The RF processing unit (510) up-converts the baseband signal provided by the baseband processing unit (520) into an RF band signal, transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (510) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC (digital to analog converter), an ADC (analog to digital converter), etc. Although only one antenna is shown in FIG. 5, the terminal may be equipped with multiple antennas. Additionally, the RF processing unit (510) may include multiple RF chains. Furthermore, the RF processing unit (510) may perform beamforming. For beamforming, the RF processing unit (510) can adjust the phase and magnitude of each of the signals transmitted and received through multiple antennas or antenna elements. Additionally, the RF processing unit can perform MIMO and can receive multiple layers when performing MIMO operation.

[0168] The baseband processing unit (520) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (520) generates complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (520) restores the received bit sequence by demodulating and decoding the baseband signal provided by the RF processing unit (510). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (520) generates complex symbols by encoding and modulating the transmitted bit sequence, maps the complex symbols to subcarriers, and then constructs OFDM symbols through IFFT (inverse fast Fourier transform) operation and CP (cyclic prefix) insertion. Additionally, upon receiving data, the baseband processing unit (520) divides the baseband signal provided by the RF processing unit (510) into OFDM symbol units, restores the signals mapped to subcarriers through a fast Fourier transform (FFT), and then restores the received bit sequence through demodulation and decoding.

[0169] The baseband processing unit (520) and the RF processing unit (510) transmit and receive signals as described above. Accordingly, the baseband processing unit (520) and the RF processing unit (510) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, or a communication unit. Furthermore, at least one of the baseband processing unit (520) and the RF processing unit (510) may include a plurality of communication modules to support a plurality of different wireless access technologies. Additionally, at least one of the baseband processing unit (520) and the RF processing unit (510) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. In addition, different frequency bands may include super high frequency (SHF) bands (e.g., 2 NRHz, NRHz) and millimeter wave (e.g., 60 GHz) bands.

[0170] The storage unit (530) stores data such as basic programs, application programs, and configuration information for the operation of the terminal. In particular, the storage unit (530) can store information related to a second connection node that performs wireless communication using the second wireless connection technology. Additionally, the storage unit (530) provides the stored data upon the request of the control unit (540).

[0171] The control unit (540) (or controller) controls the overall operations of the terminal. For example, the control unit (540) transmits and receives signals through the baseband processing unit (520) and the RF processing unit (510). Additionally, the control unit (540) writes and reads data to and from the storage unit (540). To this end, the control unit (540) may include at least one processor. For example, the control unit (540) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as applications.

[0172] FIG. 6 illustrates the structure of a base station according to one embodiment of the present disclosure.

[0173] As illustrated in FIG. 6, the base station is configured to include an RF processing unit (610), a baseband processing unit (620), a backhaul communication unit (630), a storage unit (640), and a control unit (650).

[0174] The RF processing unit (610) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. The RF processing unit (610) upconverts the baseband signal provided by the baseband processing unit (620) into an RF band signal, transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (610) may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Although only one antenna is shown in FIG. 6, the first connection node may be equipped with multiple antennas. Additionally, the RF processing unit (610) may include multiple RF chains. Furthermore, the RF processing unit (610) may perform beamforming. For beamforming, the RF processing unit (610) may adjust the phase and magnitude of each of the signals transmitted and received through multiple antennas or antenna elements. The RF processing unit may perform down-MIMO operation by transmitting one or more layers.

[0175] The baseband processing unit (620) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (620) generates complex symbols by encoding and modulating the transmitted bit sequence. Also, when receiving data, the baseband processing unit (620) restores the received bit sequence by demodulating and decoding the baseband signal provided by the RF processing unit (610). For example, in the case of following the OFDM method, when transmitting data, the baseband processing unit (620) generates complex symbols by encoding and modulating the transmitted bit sequence, maps the complex symbols to subcarriers, and then constructs OFDM symbols through IFFT operation and CP insertion. Additionally, upon receiving data, the baseband processing unit (620) divides the baseband signal provided by the RF processing unit (610) into OFDM symbol units, restores the signals mapped to subcarriers through FFT operations, and then restores the received bit sequence through demodulation and decoding. The baseband processing unit (620) and the RF processing unit (610) transmit and receive signals as described above. Accordingly, the baseband processing unit (620) and the RF processing unit (610) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, a communication unit, or a wireless communication unit.

[0176] The backhaul communication unit (630) provides an interface for communicating with other nodes within the network. The backhaul communication unit (630) converts a bit sequence transmitted from the main base station to other nodes, such as an auxiliary base station or a core network, into a physical signal, and converts a physical signal received from other nodes into a bit sequence.

[0177] The storage unit (640) stores data such as basic programs, application programs, and configuration information for the operation of the main station. In particular, the storage unit (640) can store information regarding bearers assigned to connected terminals, measurement results reported from connected terminals, etc. Additionally, the storage unit (640) can store information that serves as a criterion for determining whether to provide multiple connections to the terminal or to disconnect them. Furthermore, the storage unit (640) provides the stored data in response to a request from the control unit (650).

[0178] The control unit (650) (or controller) controls the overall operations of the base station. For example, the control unit (650) transmits and receives signals through the baseband processing unit (620) and the RF processing unit (610) or through the backhaul communication unit (630). Additionally, the control unit (650) writes and reads data to and from the storage unit (640). To this end, the control unit (650) may include at least one processor.

[0179] As a unit constituting a 5G cell, a single carrier can be used on a single band. Additionally, due to global frequency allocation policies, there may be regions or countries where carriers with relatively small bandwidths exist discontinuously in contiguous order. In this case, unlike when a cell is composed of a single carrier with a large bandwidth, if a large number of carriers are added and used through carrier aggregation (CA), a problem may arise where the amount of signal required to aggregate carriers with small bandwidths increases significantly when considering a similar total bandwidth.

[0180] FIG. 7 illustrates a cell structure of a communication system according to one embodiment of the present disclosure. More specifically, FIG. 7 illustrates a problem of a signal system caused by the presence of carriers with small bandwidths.

[0181] Referring to Fig. 7, a 5G system can consider small bandwidth carriers as a single cell, and accordingly, when communicating with a terminal, a signal considering a large number of cells is required. In a 6G system, configuration resources that form these small bandwidth contiguous carriers into a single cell can be considered, and accordingly, a method of communicating with a terminal is being considered.

[0182] In particular, when multiple carriers are configured into a single cell for operation, a new signaling system may be required for the operations necessary for the terminal due to the introduction of a cell definition different from the existing one, and after the initial cell configuration, measurement settings for wireless connection monitoring and troubleshooting operations in case of failure may be required.

[0183] In addition, when configuring the network to use the carriers required by the terminal, the physical characteristics of these carriers that must be used for communication may be necessary, and the network must signal this information to the terminal. This information may include the center or representative frequency of each carrier, subcarrier spacing information defined and operated by each carrier, and a synchronization signal included in or representing the carrier. In particular, the synchronization signal may be referred to as the SSB (synchronization signal block). It can be assumed that the synchronization signal is multiplexed with a signal for acquiring downlink synchronization of the terminal and information related to a specific cell (for example, information similar to the MIB (master information block) included in the PBCH (physical broadcast channel) of NR).

[0184] It can be assumed that at least one SSB is associated with (or included with) each carrier. Through this, the terminal can obtain the downlink signal strength through SSB measurement as well as synchronization with the corresponding carrier, and can use the signal strength when using each carrier and the wireless resources in subband units included in the carrier as a metric. These carriers can be classified as DL or UL carriers depending on the purpose; the DL carrier is used as a resource for the terminal to receive DL signals from the base station, and the UL carrier is used as a resource for the terminal to transmit UL signals to the base station.

[0185] Among these multiple carriers, a carrier that must be included in a cell and acts as an anchor carrier must always be configured. The anchor carrier serves as the reference carrier for mobility, and the radio signal on the anchor carrier can be considered the representative received signal of the cell. If the radio signal on the anchor carrier is poor, the terminal or network can perform cell movement to another anchor carrier. Additionally, the terminal or network can transmit and receive signals related to addition / release of other carriers through the anchor carrier. The terminal or network can also exchange signals related to the activation of other carriers and their subbands / BWPs based on the anchor carrier. A terminal in an idle / inactive state can camp on the anchor carrier, receive paging, and receive scheduling information for other non-anchor carriers through the physical downlink control channel (PDCCH) on the anchor carrier. Accordingly, the configuration of the anchor carrier's subband (SB) or the anchor carrier itself must always include PDCCH configuration. Conversely, the non-anchor carrier configuration may not have a PDCCH setting.

[0186] According to various embodiments of the present invention, various methods for signaling information required to a terminal are described in order to operate a cell including the aforementioned multiple carriers. Unless otherwise noted in the following descriptions, each carrier may refer to a DL carrier. Additionally, serving cell configuration may be performed through an RRC DL message (e.g., an RRCReconfiguration message).

[0187] FIG. 8 illustrates an example of setting up a cell including multiple carriers according to one embodiment of the present disclosure. Referring to FIG. 8, the network can be configured so that a Carrier can be exposed as Opt 1.

[0188] According to various embodiments, the serving cell configuration provided by the network may include the following information.

[0189] According to one embodiment, the serving cell setting may include carrier-specific information. Such carrier-specific information may include at least one of the following information.

[0190] - An indicator that directs adding or modifying carrier-specific information

[0191] - Serving Carrier ID indicating the terminal's carrier

[0192] - An indicator that indicates whether the aforementioned carrier is an anchor carrier

[0193] - An indicator indicating whether the aforementioned carrier is a DL, a carrier of a TDD system (e.g., a carrier that supports both DL and UL), or a UL carrier.

[0194] - Information of the UL carrier paired with the above-mentioned carrier when the carrier is for DL. In this case, among the information of each configured serving carrier, the ID of one of the UL carriers may be indicated.

[0195] - Carrier-specific physical information. Carrier-specific physical information may include subcarrier spacing information, carrier start information (e.g., point A), a center frequency value, frequency information where an SSB associated with the carrier exists (e.g., ARFCN), or information such as the type of cyclic prefix. Additionally, it may include PCI in this associated SSB.

[0196] - Information indicating BWP or subband-level resources that exist or may exist in the carrier's band.

[0197] (1) An ID designating each subband within the terminal. This ID can be uniquely assigned from the network within a single carrier.

[0198] (2) Frequency position and bandwidth information for each subband.

[0199] 1) Frequency position information: Can be indicated by reference frequency information and offset value.

[0200] a) Reference Frequency Information: This may refer to frequency information where a specific SSB exists, whether or not it is included in the corresponding subband, or the start frequency value among carrier-specific physical information. If specific SSB information is provided, that specific SSB may be used for measuring the radio signal of the resource at the subband level.

[0201] b) Frequency offset information: Can indicate a frequency greater than or smaller than the offset relative to the reference frequency. Here, the offset value can be the number of consecutive PRBs.

[0202] c) Bandwidth information: As a value of bandwidth, it can be the number of PRBs or a value in Hz of the actual frequency. This may indicate a subband of a frequency range larger or smaller than the bandwidth at a position considering the offset. Alternatively, it may refer to a band with the offset as the median value.

[0203] 2) Setting a reference signal to measure the radio signal strength of the corresponding subband: A cell-specific common signal such as SSB or a UE-specific reference signal such as CSI-RS may be set for radio resource management and / or radio link monitoring and / or beam management purposes of the corresponding subband. This setting may also be set to the same RS as the SSB included in the reference frequency information.

[0204] a) The index information of the reference RS may be included in the subband-related fields.

[0205] b) In the field for measurement configuration (e.g., layer 3 measurement configuration or L1 CSI measurement configuration), the ID of a measurement object containing an SSB as a reference RS in the frequency domain, or (if it is a UE-specific RS rather than a cell-specific common signal such as an SSB) the ID of an NZP-CSI-RS resource or resource set configured as a measurement target in the L1 CSI measurement configuration, may be configured as a reference signal for the measurement resource of the subband. Alternatively, information combined with reporting configuration information associated with an MO ID or CSI-RS resource / resource set ID (e.g., measurement ID) may also be included in the subband field.

[0206] c) The RS measurement purpose may be indicated in the RS target information. For example, an indicator for RLM use and / or beam failure detection use and / or RRM use may be associated and signaled.

[0207] [Acquire Carrier Star DL Synchronization]

[0208] A terminal that has received serving cell settings can measure SSB or CSI-RS by referring to the reference signal information of the subband assigned to each carrier. In this process, the terminal can synchronize DL signals with each subband and / or the carrier including that subband through measurement. In this process, in the case of SSB, the terminal can obtain information related to the SFN (system frame number) or slot number on the multiplexed PBCH and use it for DL ​​synchronization.

[0209] [Acquire UL Motivation by Carrier]

[0210] Some carriers may share the same TRP as the carrier that was initially attempted and successfully connected. In such cases, DL synchronization and UL synchronization may be the same as the carrier that has already been successfully connected. If they are the same, an RRC Reconfiguration message containing each (UL) carrier and SB addition configuration information may include an indicator instructing to use the same TA (timing advance), and may indicate the serving carrier ID of the UL carrier that is the subject of the identity or the carrier TA group (cTAG) ID of specific UL carriers. If the terminal is instructed to use a carrier ID or carrier TA group ID that already maintains a valid TA as the reference target for the TA, it may use the TA of the indicated ID.

[0211] If a UL carrier transmitted or received from another TRP is configured or added, the base station may provide random access configuration information applicable to the UL pair carrier of the carrier (e.g., in the case of FDD) or the carrier (e.g., TDD). After applying each carrier / SB configuration information received from the base station (e.g., after adding), the terminal may be instructed to perform an RA preamble transmission based on a PDCCH order through the anchor carrier. At this time, information indicating the UL carrier to be transmitted (e.g., serving carrier ID / index or ID / index of the UL SB of the carrier) may be provided together. Subsequently, the base station that receives the preamble may transmit a TA value, along with the preamble transmission target carrier ID or the TAG ID containing the carrier, to the DCI (downlink control information) or DL ​​MAC CE on the anchor carrier. After obtaining the TA value, the terminal may obtain UL synchronization with the carrier and subsequently perform UL transmission.

[0212] [Carrier-specific addition process]

[0213] Generally, when the terminal is in an idle / inactive state, it can obtain DL synchronization of the cell of the camping carrier, obtain system information provided on the carrier, and obtain RACH settings. The terminal can perform RACH operations according to the obtained RACH settings to obtain UL synchronization and request an RRC connection to the base station through an RRC setup request message.

[0214] The network receiving the request may transmit serving cell settings via an RRC setup message. The settings transmitted by the network may include PHY / MAC and upper-layer settings for the carrier that the terminal initially camped with. The terminal may apply these settings to configure a cell and transmit a setup complete message to the base station. The cell configuration may include an anchor carrier identifier for the carrier from which the terminal camped to obtain system information, thereby indicating that the carrier is the anchor carrier.

[0215] When configuring such a cell, the setup message may additionally include information regarding measurement settings. Alternatively, an RRC Reconfiguration message or a corresponding RRC message transmitted or received after the transmission of setup complete may include measurement setting information. The terminal may measure the measurement targets included in the measurement setting information. At this time, the terminal may include the SSBs of the reference frequencies of candidate carriers to be added as measurement targets. Upon receiving such information, the terminal may measure the corresponding measurement targets to obtain carrier-specific DL synchronization and simultaneously transmit the corresponding carrier-specific measurement results to the base station.

[0216] Based on the measurement results, the base station can transmit carrier and subband-specific settings to the terminal, based on the candidate carriers that show a good signal level to the terminal.

[0217] A terminal that has received carrier and subband-specific settings can add the corresponding carrier and subband-unit resources existing within that carrier.

[0218] The network can activate a specific subband / carrier by indicating the ID / index of the added carrier and the subband existing in the carrier, and the terminal can perform data communication through DL reception and / or UL transmission via the activated carrier or subband. As described above, regarding carriers added through serving cell settings after the initial camping carrier, the network may indicate that they are non-anchor carriers by omitting the non-anchor carrier indicator or the anchor carrier indicator.

[0219] If the SSB associated with the reference frequency of the added carrier is a CD (cell defining)-SSB, the terminal may not obtain system information through the MIB and SIB1 information contained in the said SSB. Instead, the terminal may apply configuration information exclusively transmitted by the base station for that carrier.

[0220] In the case of setting opt 1, the base station may, if necessary, instruct the release of carrier-specific resources including the carrier index after subband addition, and accordingly, the release of the relevant carrier and the release of the subband set below it may be instructed at once (for example, setting an option useful for carrier-level mobility).

[0221] Referring to FIG. 8, the case of the resource setting method opt 1 described above is illustrated.

[0222] A cell contains multiple carriers, and a carrier may contain multiple SBs within the corresponding frequency range. The ID of each SB can be assigned carrier-specifically.

[0223] FIG. 9 illustrates another example of setting up a cell including multiple carriers according to one embodiment of the present disclosure. With reference to FIG. 9, an example of Opt 2 in which the carrier is transparently transmitted is illustrated.

[0224] According to various embodiments, the serving cell configuration provided by the network may include the following information.

[0225] - The network may indicate BWP or subband-level resources that exist or may exist in each carrier's band.

[0226] (1) An ID / index designating each subband within the terminal. This ID can be uniquely assigned from the network within a single cell.

[0227] (2) Indicates the physical characteristics of the carrier to which the subband belongs.

[0228] 1) An indicator indicating whether the carrier containing the subband is an anchor carrier or not. Or an indicator indicating whether the subband is an anchor SB / BWP or not.

[0229] 2) An indicator indicating whether the carrier containing the subband is a DL, a carrier of a TDD system (e.g., a carrier that supports both DL and UL), or a UL carrier. Or an indicator indicating whether the subband is a DL, a subband that supports both DL and UL, or a UL subband.

[0230] 3) Information of the paired UL subband when the subband is for DL. In this case, among the information of each configured serving subband, the ID of one of the UL subbands can be indicated.

[0231] 4) Information on subband subcarrier spacing and the type of cyclic prefix (e.g., normal, extended).

[0232] 5) Subband reference SSB information: ARFCN and PCI in this associated SSB.

[0233] (3) Frequency position and bandwidth information of each subband

[0234] 1) Frequency position information: Can be indicated by reference frequency information and offset value.

[0235] a) Reference Frequency Information: Information regarding the frequency at which a specific SSB exists, regardless of whether it is included in the corresponding subband or not, which may indicate the ARFCN and the PCI information of the corresponding SSB. If specific SSB information is provided, that SSB may be used for radio signal measurement of resources at the subband level.

[0236] b) Frequency offset information: Can indicate a frequency greater than or smaller than the offset relative to the reference frequency. Here, the offset value can be the number of consecutive PRBs.

[0237] c) Bandwidth information: As a bandwidth value, it can be the number of PRBs or a value in Hz of the actual frequency. At a position considering the offset, it can indicate a subband of a frequency range larger or smaller than the bandwidth. Alternatively, it can refer to a band with the offset as the median value.

[0238] 2) Setting a reference signal to measure the radio signal strength of the corresponding subband: A cell-specific common signal such as SSB or a UE-specific reference signal such as CSI-RS may be set for radio resource management and / or radio link monitoring and / or beam management of the corresponding subband. The setting may also be configured to have an RS identical to the SSB included in the reference frequency information.

[0239] a) The index information of the reference RS may be included in the subband-related fields.

[0240] b) In the field for measurement configuration (e.g., layer 3 measurement configuration or L1 CSI measurement configuration), the ID of a measurement object containing an SSB as a reference RS in the frequency domain, or (if it is a UE-specific RS rather than a cell-specific common signal such as an SSB) the ID of an NZP-CSI-RS resource or resource set configured as a measurement target in the L1 CSI measurement configuration, may be configured as a reference signal for the measurement resource of the subband. Alternatively, information combined with reporting configuration information associated with an MO ID or CSI-RS resource / resource set ID (e.g., measurement ID) may also be included in the subband field.

[0241] c) The RS measurement application may be indicated in the RS target information. For example, an indicator for RLM application, and / or beam failure detection application, and / or RRM application may be associated and signaled.

[0242] According to various embodiments, when a network signals a terminal using the opt 2 method described above, the terminal may not know the explicit connection relationship between each subband and the carrier. Accordingly, in order to release a specific carrier resource, the network must perform a release for each subband included in that carrier. Likewise, in the case of addition, the network and the terminal must perform an addition for each subband included in the carrier. In the case of opt 2, when releasing or adding a carrier that has already been added within a cell, the associated subband ID needs to be newly defined and assigned.

[0243] In addition, for an SB / BWP designated as an anchor SB / BWP, the anchor SB / BWP can take over the role performed by the anchor carrier of opt 1. The anchor SB / BWP serves as the reference SB / BWP for mobility, and the downlink radio signal strength on the SB / BWP can be considered as the representative received signal strength of the cell; if this signal is poor, the terminal and the network can perform cell movement to move the cell to another anchor carrier. Furthermore, the terminal and the network can transmit and receive signals related to the addition / release of other SB / BWPs through the SB / BWP, and can exchange signals related to the activation of other SB / BWPs based on the SB / BWP. A terminal in an idle / inactive state can camp on the carrier and receive paging, and can also receive scheduling information for SB / BWPs of other non-anchor carriers through the PDCCH on the SB / BWP. Accordingly, the configuration of the SB / BWP must always include a PDCCH configuration. Relatively speaking, the configuration of a non-anchor carrier may not include a PDCCH configuration.

[0244] According to various embodiments, other [carrier-specific DL synchronization acquisition] and [carrier-specific addition process] can be performed in the same way as opt 1 described in FIG. 8.

[0245] Referring to Fig. 9, the case of the resource setting method option 2 described above is illustrated.

[0246] A cell can be composed of multiple carriers, and an SB may exist within a single carrier. In this case, the SB ID can be assigned cell-specifically.

[0247] FIG. 10 illustrates another example of setting up a cell including multiple carriers according to one embodiment of the present disclosure. With reference to FIG. 10, an example of Opt 3 is illustrated in which the carrier is transmitted transparently, but one subband includes multiple carriers.

[0248] According to various embodiments, the serving cell configuration provided by the network may include the following information.

[0249] - The network may indicate BWP or subband-level resources that exist or may exist in each carrier's band.

[0250] (1) An ID / index designating each subband within the terminal. This ID can be uniquely assigned from the network within a single cell.

[0251] (2) Indicates the physical characteristics of the carrier to which the subband belongs.

[0252] 1) An indicator indicating whether the carrier containing the subband is an anchor carrier or not. Or an indicator indicating whether the subband is an anchor BWP or not.

[0253] 2) An indicator indicating whether the carrier containing the subband is a DL, a carrier of a TDD system (e.g., a carrier that supports both DL and UL), or a UL carrier. Or an indicator indicating whether the subband is a DL, a subband that supports both DL and UL, or a UL subband.

[0254] 3) Information of the paired UL subband when the subband is for DL. In this case, among the information of each configured serving subband, the ID of one of the UL subbands can be indicated.

[0255] 4) Information on subband subcarrier spacing and the type of cyclic prefix (e.g., normal, extended).

[0256] 5) Subband reference SSB information: ARFCN and PCI in this associated SSB.

[0257] a) If the frequency range covered by the corresponding subband includes multiple carriers, SCS information, cyclic prefix type information, ARFCN or PCI information, etc. may be separately indicated for each carrier.

[0258] (3) Frequency position and bandwidth information of each subband

[0259] 1) Frequency position information: Can be indicated by reference frequency information and offset value.

[0260] a) Reference frequency information: Information on the frequency where a specific SSB exists, whether or not it is included in the corresponding subband, and may indicate the ARFCN and PCI information of the corresponding SSB. If specific SSB information is provided, the corresponding SSB may be used for radio signal measurement of resources at the subband level.

[0261] b) Frequency offset information: Can indicate a frequency greater than or smaller than the offset relative to the reference frequency. Here, the offset value can be the number of consecutive PRBs.

[0262] c) Bandwidth Information: Since this option may include subbands for multiple discontinuous carriers, the bandwidth information may be indicated by the following methods depending on the method of indicating the frequency range included for each carrier.

[0263] c-1) As Opt 3-1, it can be set to the entire band information and the information of bands excluded from the band.

[0264] c-1.1) The entire band can be indicated by applying the entire band bandwidth (e.g., A in FIG. 10) from a position on the offset (e.g., B in FIG. 10) based on the reference frequency (e.g., above the offset, below the offset, or evenly divided into intermediate values, and an example of applying above the offset is shown with reference to FIG. 10).

[0265] c-1.2) Excluded bands: Excluded bands can also be determined starting from a position on the offset (e.g., D in Fig. 10) relative to the reference frequency. At this time, information on the excluded bands (e.g., C in Fig. 10) may be provided.

[0266] c-1.3) As a bandwidth value, it can be the number of PRBs or a value in Hz of the actual frequency. At a position considering the offset, it can indicate a subband of a frequency range larger or smaller than the bandwidth. Alternatively, it can mean a band with the offset as the median value.

[0267] c-2) As Opt 3-2, it may be indicated in the form of a list of band information included for each carrier. In FIG. 10, it may mean a list of two disjoint bands divided into chunk 1 and 2.

[0268] c-2.1) Each band may be composed of the starting position of the band and bandwidth information of the band, or may be composed of the starting information of the band and frequency information of the ending position of the band. Each point may be represented by a required offset value based on a reference frequency. In FIG. 10, the starting and ending points are indicated based on the latter case. For example, the starting point of Chunk 1 may be represented by an offset value of B and the ending point by an offset value of D, and the starting point of Chunk 2 may be represented by an offset value of F and the ending point by an offset value of E.

[0269] 2) Setting a reference signal for measuring the wireless signal strength of the corresponding subband: A cell-specific common signal such as SSB or a UE-specific reference signal such as CSI-RS may be set for radio resource management and / or radio link monitoring and / or beam management of the corresponding subband. The setting may also set an RS identical to the SSB included in the reference frequency information.

[0270] a) The index information of the reference RS may be included in the subband-related fields.

[0271] b) In the field for measurement configuration (e.g., layer 3 measurement configuration or L1 CSI measurement configuration), the ID of a measurement object containing an SSB as a reference RS in the frequency domain, or (if it is a UE-specific RS rather than a cell-specific common signal such as an SSB) the ID of an NZP-CSI-RS resource or resource set configured as a measurement target in the L1 CSI measurement configuration, may be configured as a reference signal for the measurement resource of the subband. Alternatively, information combined with reporting configuration information associated with an MO ID or CSI-RS resource / resource set ID (e.g., measurement ID) may also be included in the subband field.

[0272] c) The RS measurement application may be indicated in the RS target information. For example, an indicator for RLM application, and / or beam failure detection application, and / or RRM application may be associated and signaled.

[0273] According to various embodiments, when a network signals a terminal using the opt 3 method described above, the terminal may not know the explicit connection relationship between each subband and the carrier. Accordingly, in order to release a specific carrier resource, the network must perform a release for each subband included in that carrier. Likewise, in the case of addition, the network and the terminal must perform an addition for each subband included in the carrier. In the case of opt 3, when releasing a carrier that has already been added within a cell or adding a new carrier, the subband IDs of the carrier and the previously configured carrier need to be newly defined and assigned.

[0274] According to various embodiments, other [carrier-specific DL synchronization acquisition] and [carrier-specific addition process] can be performed in the same way as opt 1 described in FIG. 8.

[0275] Referring to FIG. 10, the case of the resource allocation method option 3 described above is illustrated.

[0276] Through the methods described above, the network can configure the terminal with a carrier constituting the cell and a subband existing in that carrier.

[0277] In addition, even if methods for resource configuration and related RS configuration by carrier and SB are defined, the network may selectively configure RS for RLM purposes and deliver it to the terminal according to its needs. Depending on the purpose of each carrier and the SB associated with that carrier, RLM RS configuration can be configured according to the following various options.

[0278] FIG. 11 illustrates an example of an RLM operation according to one embodiment of the present disclosure.

[0279] Referring to RLM operation opt 1 in FIG. 11, the RLM may be operated exclusively for the DL anchor carrier. Accordingly, an RLM RS may be configured for an SB (subband) belonging to or connected to the DL anchor carrier. At this time, any of the resource configuration methods opt 1, 2, and 3 described in FIG. 8 to 10 may be used for the configuration.

[0280] - RS settings can be configured per carrier or per SB belonging to the carrier.

[0281] (1) RLM-RS can be configured for each carrier corresponding to the DL anchor carrier or for each SB of the carrier. The following information may be included as related information.

[0282] 1) RLM-RS type: SSB or CSI-RS

[0283] 2) RLM-RS RS resource ID: SSB index or CSI-RS resource ID / resource set ID. In this case, the CSI-RS resource / resource set may be an RS included in a separate CSI-RS measurement setting of the serving cell configuration, and the ID defined in that setting may be used for RLM-RS identification.

[0284] 3) RLM-RS purpose: An indicator indicating that a single RS may be used only for RLM, only for beam failure detection, or for both purposes.

[0285] - As other RLM-related settings, the following settings may be included.

[0286] (1) The following information may be set per carrier, repeated for each SB corresponding to the carrier, or set as a single representative value.

[0287] 1) RLM in-sync / out-of-sync BLER threshold information: These values ​​are used to determine the indicators that trigger when the strength of a DL reference signal, measured based on DL RSRP or RSRQ at the physical layer, satisfies or dissatisfies the BLER level of a specific PDCCH. The in-sync threshold is used to signal an in-sync indicator to the upper layer when the received signal at the physical layer is above the threshold, and the out-of-sync threshold can be used to transmit an out-of-sync signal to the upper layer when the received signal at the physical layer is below the threshold.

[0288] 2) # of consecutive counter for in-sync: If consecutive in-sync occurs for that number of times, the T310 timer or RLF (radio link failure) detection timer that has already started may be stopped.

[0289] 3) # of consecutive counter for out-of-sync: When the number of consecutive out-of-sync events is equal, the T310 timer or RLF detection timer may be started.

[0290] 4) The timer value of the T310 or RLF detection timer. This timer may be a timer that starts at the RRC layer when a set sequence of OOS is received. When this timer starts and a set sequence of IS is not received during the timer value, the terminal may declare RLF for the cell.

[0291] - Terminal operation

[0292] (1) If the currently active SB is changed to another SB, the previously operating T310 timer is stopped and can be initialized to the original timer value. The number of IS / OOS indicators previously received from the lower layer can be initialized to 0.

[0293] - RLF detection and handling

[0294] (1) When the T310 timer expires, the terminal may declare an RLF for the cell or additionally declare an RLF for the carrier (e.g., a DL anchor carrier with RLM-RS configured). In the case of declaring an RLF for the cell, the terminal may perform an RRC re-establishment operation (e.g., after selecting a cell, perform an RRC re-establishment operation to that cell).

[0295] FIG. 12 illustrates another example of an RLM operation according to one embodiment of the present disclosure.

[0296] Referring to RLM operation opt 2 in FIG. 12, RLM may be allowed not only for the DL anchor carrier but also for any DL non-anchor carrier. For example, a terminal may receive a PDCCH on the anchor carrier and simultaneously receive a PDCCH on another designated carrier. Additionally, the same RLM operation may be allowed for two or more multiple carriers, including one DL anchor carrier and one or more DL non-anchor carriers. Furthermore, it is assumed that the RLM-allowed carriers are active simultaneously; accordingly, one SB associated with each carrier may be active per carrier, i.e., two or more SBs may be active simultaneously. Accordingly, an RLM operation for guaranteeing the reception of a PDCCH can be defined for each carrier. Accordingly, an RLM RS may be configured for the SB (subband) belonging to or associated with each carrier. At this time, any of the resource configuration methods opt 1, 2, and 3 described in FIG. 8 to 10 may be used for this configuration.

[0297] - RS settings can be configured for carriers where RLM is allowed or for SBs belonging to those carriers.

[0298] (1) RLM-RS can be configured for each carrier corresponding to the DL anchor carrier or for each SB of the carrier. The following information may be included as related information.

[0299] 1) RLM-RS type: SSB or CSI-RS

[0300] 2) RS resource ID of RLM-RS: SSB index or CSI-RS resource ID / resource set ID. In this case, the CSI-RS resource / resource set may be an RS included in a separate CSI-RS measurement setting of the serving cell configuration, and the ID defined in that setting may be used for RLM-RS identification.

[0301] a) The ID of the RLM-RS may be indicated together with the index of each carrier (e.g., serving carrier index) (in which case the ID may be unique within that carrier), or, if there is no carrier index, the ID may be unique within the target carrier to which the RS is configured.

[0302] 3) RLM-RS purpose: An indicator indicating that a single RS may be used only for RLM, only for beam failure detection, or for both purposes.

[0303] - As other RLM-related settings, the following settings may be included.

[0304] (1) The following information may be set for each carrier that is allowed by RLM, repeated for each SB corresponding to the carrier, or a single representative value may be used for each SB.

[0305] 1) RLM in-sync / out-of-sync BLER threshold information: These values ​​are used to determine the indicators that trigger when the strength of a DL reference signal, measured based on DL RSRP or RSRQ at the physical layer, satisfies or dissatisfies the BLER level of a specific PDCCH. The in-sync threshold is used to signal an in-sync indicator to the upper layer when the received signal at the physical layer is above the threshold, and the out-of-sync threshold can be used to transmit an out-of-sync signal to the upper layer when the received signal at the physical layer is below the threshold.

[0306] 2) # of consecutive counter for in-sync: If consecutive in-sync occurs for that number of times, the T310 timer or RLF detection timer that has already started may be stopped.

[0307] 3) # of consecutive counter for out-of-sync: When the number of consecutive out-of-sync events is equal, the T310 timer or RLF detection timer may be started.

[0308] 4) The timer value of T310 or the RLF detection timer. The timer may be a timer that starts at the RRC layer when a set consecutive OOS is received. When the timer starts and a set consecutive IS is not received during the timer value, the terminal may declare an RLF for the cell according to the RLF detection and handling method below.

[0309] - Terminal operation

[0310] (1) If the currently active SB is changed to another SB, the previously operating T310 timer is stopped and can be initialized to the original timer value. The number of IS / OOS indicators previously received from the lower layer can be initialized to 0.

[0311] (2) The terminal can maintain and operate the timers independently without mutual interference between the timers of each carrier.

[0312] - RLF detection and handling

[0313] (1) Opt 1. When multiple T310 timers are in operation, if any one of the timers expires, the terminal may declare RLF for the cell. In this case, since the terminal cannot receive PDCCH from the carrier, it can be assumed that the necessary control information for the cell cannot be received.

[0314] 1) In this case, the terminal can perform an RRC Reestablishment operation.

[0315] (2) Opt 2. When multiple T310 timers are in operation, if all timers expire, the terminal may declare RLF for the cell. In this case, the terminal may declare RLF because it cannot receive PDCCH from all carriers.

[0316] 1) In this case, if T310 expiration occurs first for any RLM allowed carrier, the terminal may report to the base station via a valid UL carrier that the timer of the said carrier has expired. Here, a valid UL carrier may mean that the timer of the paired DL carrier has not expired. Alternatively, the terminal may report the information to the base station via a carrier that transmits predefined timer expiration information. The reported information may include a timer expiration indicator, the corresponding carrier index, the SB ID of which the timer expired, the most recent measurement information, etc.

[0317] a) The signal of the information may include a UCI, UL MAC CE, or UL RRC message.

[0318] (3) Opt 3. When multiple T310 timers are in operation, if the timer associated with the anchor carrier expires, the terminal may declare an RLF for the cell. In this case, since the PDCCH associated with the anchor carrier is more important control information, only that carrier can be considered as the target for the RLF.

[0319] 1) In this case, if T310 expiration occurs first for a non-anchor carrier, the terminal may report to the base station via a valid UL carrier that the timer of the said carrier has expired. Here, a valid UL carrier may mean that the timer of the paired DL carrier has not expired. Alternatively, the terminal may report the information to the base station via a carrier that transmits predefined timer expiration information. The reported information may include a timer expiration indicator, the corresponding carrier index, the SB ID of the timer that expired, or the most recent measurement information.

[0320] a) The signal of the information may include a UCI, UL MAC CE, or UL RRC message.

[0321] 2) Regardless of the non-anchor carrier, when the anchor carrier's timer expires, the terminal can declare the RLF of the corresponding cell and perform an RRC reestablishment operation (after selecting a cell, perform an RRC reestablishment operation to that cell).

[0322] FIG. 13 illustrates another example of an RLM operation according to one embodiment of the present disclosure.

[0323] Referring to RLM operation opt 3 of FIG. 13, RLM may be allowed not only on the DL anchor carrier but also on any DL non-anchor carrier. For example, the terminal may receive PDCCH on the anchor carrier and simultaneously receive PDCCH on another designated carrier. Accordingly, an RLM operation for guaranteeing the reception of PDCCH can be defined for each carrier. However, unlike opt 2 of FIG. 12, only one RLM operation can be activated for each carrier or SB in FIG. 13 at a time. The configuration may be any of the resource configuration methods opt 1, 2, and 3 described in FIG. 8 to 10, but the terminal may measure only the RLM RS on the activated SB or carrier and perform a timer operation accordingly.

[0324] - RS settings can be configured for carriers where RLM is allowed or for SBs belonging to those carriers.

[0325] (1) RLM-RS can be configured for each carrier corresponding to the DL anchor carrier or for each SB of the carrier. The following information may be included as related information.

[0326] 1) RLM-RS type: SSB or CSI-RS

[0327] 2) RLM-RS RS resource ID: SSB index or CSI-RS resource ID / resource set ID. In this case, the CSI-RS resource / resource set may be an RS included in a separate CSI-RS measurement setting of the serving cell configuration, and the ID defined in that setting may be used for RLM-RS identification.

[0328] a) The ID of the RLM-RS may be indicated together with the index of each carrier (e.g., serving carrier index) (in which case the ID may be unique within that carrier), or, if there is no carrier index, the ID may be unique within the target carrier to which the RS is configured.

[0329] 3) RLM-RS purpose: An indicator indicating that a single RS may be used only as RLM, only as beam failure detection, or for both purposes.

[0330] - As other RLM-related settings, the following settings may be included.

[0331] (1) The following information may be set for each carrier that is allowed by RLM, repeated for each SB corresponding to the carrier, or a single representative value may be used for each SB.

[0332] 1) RLM in-sync / out-of-sync BLER threshold information: These values ​​are used to determine the indicators that trigger when the strength of a DL reference signal, measured based on DL RSRP or RSRQ at the physical layer, satisfies or does not satisfy the BLER level of a specific PDCCH. The in-sync threshold is used to signal an in-sync indicator to the upper layer when the received signal at the physical layer is above the threshold, and the out-of-sync threshold can be used to transmit an out-of-sync signal to the upper layer when the received signal at the physical layer is below the threshold.

[0333] 2) # of consecutive counter for in-sync: If consecutive in-sync occurs for that number of times, the T310 timer or RLF detection timer that has already started may be stopped.

[0334] 3) # of consecutive counter for out-of-sync: When the number of consecutive out-of-sync events is equal, the T310 timer or RLF detection timer may be started.

[0335] 4) The timer value of the T310 or RLF detection timer. This timer may be a timer that starts at the RRC layer when a set sequence of OOS is received. When this timer starts and a set sequence of IS is not received during the timer value, the terminal may declare RLF for the cell.

[0336] - Terminal operation

[0337] (1) The terminal can perform RLM measurements on the currently active carrier or SB and start or stop the timer accordingly.

[0338] (2) If the currently active SB is changed to another SB, the previously operating T310 timer is stopped and can be initialized to the original timer value. Also, the number of IS / OOS indicators previously received from the lower layer can be initialized to 0.

[0339] - RLF detection and handling

[0340] (1) Since only one timer is operated, when the timer expires, the terminal can declare RLF for the cell.

[0341] 1) In this case, when T310 expiration occurs, the terminal may report to the base station via a valid UL carrier that the timer of the corresponding carrier / SB has expired. Here, the meaning of a valid UL carrier may be that the timer of the paired DL carrier of the corresponding UL carrier has not expired. Alternatively, the terminal may report the information to the base station via a carrier that transmits predefined timer expiration information. The reported information may include a timer expiration indicator, the corresponding carrier index, the SB ID of which the timer expired, the most recent measurement information, etc.

[0342] a) The signal of the relevant information may be transmitted via UCI, UL MAC CE, or UL RRC message.

[0343] 2) If such reporting is possible, the terminal may perform the RRC reestablishment operation after the report, or if reporting is not possible, the terminal may perform the RRC reestablishment operation without such report.

[0344] FIG. 14 illustrates another example of an RLM operation according to one embodiment of the present disclosure.

[0345] Referring to RLM operation opt 4 in FIG. 14, a case is illustrated in which RLM can be configured only in spcells, and in particular, can be operated only in the DL anchor carrier of spcells. Accordingly, cells other than spcells do not perform separate RLM configurations, RLM operations, or RLF-related operations, and for spcells, the configurations and terminal operations described in opt 1 above can be performed. Hereinafter, all RLM-related configurations and operations are described with respect to spcells.

[0346] RLM can be operated exclusively on the DL anchor carrier. Accordingly, RLM RS can be configured on the SB (subband) belonging to or connected to the DL anchor carrier. At this time, any of the resource configuration methods opt 1, 2, and 3 described in FIGS. 8 to 10 can be used for the configuration.

[0347] - RS settings can be configured per carrier or per SB belonging to the carrier:

[0348] (1) RLM-RS can be configured for each carrier corresponding to the DL anchor carrier or for each SB of the carrier. The following information may be included as related information.

[0349] 1) RLM-RS type: SSB or CSI-RS

[0350] 2) RS resource ID of RLM-RS: SSB index or CSI-RS resource ID / resource set ID. In this case, the CSI-RS resource / resource set may be an RS included in a separate CSI-RS measurement setting of the serving cell configuration, and the ID defined in that setting may be used for RLM-RS identification.

[0351] 3) RLM-RS purpose: An indicator indicating that a single RS can be used only for RLM, only for beam failure detection, or for both purposes.

[0352] - As other RLM-related settings, the following settings may be included.

[0353] (1) The following information may be set per carrier, repeated for each SB corresponding to the carrier, or set as a single representative value.

[0354] 1) RLM in-sync / out-of-sync BLER threshold information: These values ​​are used to determine the indicators that trigger when the strength of a DL reference signal, measured based on DL RSRP or RSRQ at the physical layer, satisfies or does not satisfy the BLER level of a specific PDCCH. The in-sync threshold is used to signal an in-sync indicator to the upper layer when the received signal at the physical layer is above the threshold, and the out-of-sync threshold can be used to transmit an out-of-sync signal to the upper layer when the received signal at the physical layer is below the threshold.

[0355] 2) # of consecutive counter for in-sync: If consecutive in-sync occurs for that number of times, the T310 timer or RLF detection timer that has already started may be stopped.

[0356] 3) # of consecutive counter for out-of-sync: When the number of consecutive out-of-sync events is equal, the T310 timer or RLF detection timer may be started.

[0357] 4) The timer value of the T310 or RLF detection timer. This timer may be a timer that starts at the RRC layer when a set sequence of OOS is received. When this timer starts and a set sequence of IS is not received during the timer value, the terminal may declare RLF for the cell.

[0358] - Terminal operation

[0359] (1) If the currently active SB is changed to another SB, the previously operating T310 timer is stopped and can be initialized to the original timer value. Also, the number of IS / OOS indicators previously received from the lower layer can be initialized to 0.

[0360] - RLF detection and handling

[0361] (1) When the T310 timer expires, the terminal may declare an RLF for the cell or additionally declare an RLF for the carrier (e.g., a DL anchor carrier with RLM-RS configured). In the case of declaring an RLF for the cell, the terminal may perform an RRC re-establishment operation (e.g., after selecting a cell, perform an RRC re-establishment operation to that cell).

[0362] FIG. 15 illustrates another example of an RLM operation according to one embodiment of the present disclosure.

[0363] Referring to RLM operation opt 5 in FIG. 15, RLM may be configured only on spcell, and the remaining operations may be the same as opt 2. For example, FIG. 15 illustrates a case where RLM operation is possible on a DL anchor carrier of spcell and a DL non-anchor carrier. Accordingly, cells other than spcell do not perform separate RLM configuration, RLM operation, or RLF-related operations, and for spcell, the configuration and terminal operations described in opt 2 above may be performed. Hereinafter, all RLM-related configurations and operations are described with respect to spcell.

[0364] RLM may be allowed not only on the DL anchor carrier but also on any DL non-anchor carrier. For example, a PDCCH may be received on the anchor carrier, and simultaneously, a PDCCH may be received on another designated carrier. Additionally, the same RLM operation may be allowed for two or more carriers, including one DL anchor carrier and one or more DL non-anchor carriers. Furthermore, it is assumed that the RLM-allowed carriers are simultaneously active; accordingly, one SB associated with each carrier may be active per carrier, meaning that two or more SBs may be active simultaneously. Accordingly, an RLM operation to guarantee the reception of a PDCCH can be defined for each carrier. Accordingly, an RLM RS may be configured on the SB (subband) belonging to or associated with each carrier. In this case, any of the resource configuration methods opt 1, 2, and 3 described in FIGS. 8 to 10 may be used for the configuration.

[0365] - RS settings can be configured per carrier where RLM is allowed or per SB belonging to the carrier:

[0366] (1) RLM-RS can be configured for each carrier corresponding to the DL anchor carrier or for each SB of the carrier. The following information may be included as related information.

[0367] 1) RLM-RS type: SSB or CSI-RS

[0368] 2) RLM-RS RS resource ID: SSB index or CSI-RS resource ID / resource set ID. In this case, the CSI-RS resource / resource set may be an RS included in a separate CSI-RS measurement setting of the serving cell configuration, and the ID defined in that setting may be used for RLM-RS identification.

[0369] a) The ID of this RLM-RS may be indicated together with the index of each carrier (e.g., serving carrier index) (in which case the ID may be unique within that carrier), or, if there is no carrier index, the ID may be unique within the target carrier to which the RS is configured.

[0370] 3) RLM-RS purpose: An indicator indicating that a single RS may be used only as RLM, only as beam failure detection, or for both purposes.

[0371] - As other RLM-related settings, the following settings may be included.

[0372] (1) The following information may be set for each carrier that is allowed by RLM, repeated for each SB corresponding to the carrier, or a single representative value may be used for each SB.

[0373] 1) RLM in-sync / out-of-sync BLER threshold information: These values ​​are used to determine the indicators that trigger when the strength of a DL reference signal, measured based on DL RSRP or RSRQ at the physical layer, satisfies or does not satisfy the BLER level of a specific PDCCH. The in-sync threshold is used to signal an in-sync indicator to the upper layer when the received signal at the physical layer is above the threshold, and the out-of-sync threshold can be used to transmit an out-of-sync signal to the upper layer when the received signal at the physical layer is below the threshold.

[0374] 2) # of consecutive counter for in-sync: If consecutive in-sync occurs for that number of times, the T310 timer or RLF detection timer that has already started may be stopped.

[0375] 3) # of consecutive counter for out-of-sync: When the number of consecutive out-of-sync events is equal, the T310 timer or RLF detection timer may be started.

[0376] 4) The timer value of T310 or the RLF detection timer. The timer may be a timer that starts at the RRC layer when a set consecutive OOS is received. When the timer starts and a set consecutive IS is not received during the timer value, the terminal may declare an RLF for the cell according to the RLF detection and handling method below.

[0377] - Terminal operation

[0378] (1) If the currently active SB is changed to another SB, the previously operating T310 timer is stopped and can be initialized to the original timer value. Also, the number of IS / OOS indicators previously received from the lower layer can be initialized to 0.

[0379] (2) The terminal can maintain and operate the timers independently without mutual interference between the timers of each carrier.

[0380] - RLF detection and handling

[0381] (1) Opt 1. When multiple T310 timers are in operation, if any one of the timers expires, the terminal may declare RLF for the cell. In this case, since the terminal cannot receive PDCCH from the carrier, it can be assumed that the necessary control information for the cell cannot be received.

[0382] 1) In this case, the terminal can perform an RRC Reestablishment operation.

[0383] (2) Opt 2. When multiple T310 timers are in operation, if all timers expire, the terminal may declare RLF for the cell. In this case, the terminal may declare RLF because it cannot receive PDCCH from all carriers.

[0384] 1) In this case, if T310 expiration occurs first for any RLM allowed carrier, the terminal may report to the base station via a valid UL carrier that the timer of the said carrier has expired. Here, a valid UL carrier may mean that the timer of the paired DL carrier has not expired. Alternatively, the terminal may report the information to the base station via a carrier that transmits predefined timer expiration information. The reported information may include a timer expiration indicator, the corresponding carrier index, the SB ID of which the timer expired, the most recent measurement information, etc.

[0385] a) The signal of this information may include a UCI, UL MAC CE, or UL RRC message.

[0386] (3) Opt 3. When multiple T310 timers are in operation, if the timer associated with the anchor carrier expires, the terminal may declare RLF for the cell. In this case, since the PDCCH associated with the anchor carrier is more important control information, only that carrier can be considered as the target for RLF.

[0387] 1) In this case, if T310 expiration occurs first for a non-anchor carrier, the terminal may report to the base station via a valid UL carrier that the timer of the said carrier has expired. Here, a valid UL carrier may mean that the timer of the paired DL carrier has not expired. Alternatively, the terminal may report the said information to the base station via a carrier that transmits predefined timer expiration information. The reported information may include a timer expiration indicator, the corresponding carrier index, the SB ID where the timer expired, or the most recent measurement information.

[0388] a) The signal of the information may include a UCI, UL MAC CE, or UL RRC message.

[0389] 2) Regardless of the non-anchor carrier, when the anchor carrier's timer expires, the terminal can declare the RLF of the corresponding cell and perform an RRC reestablishment operation (after selecting a cell, perform an RRC reestablishment operation to that cell).

[0390] FIG. 16 illustrates another example of an RLM operation according to one embodiment of the present disclosure.

[0391] With reference to RLM operation opt 6 in FIG. 16, RLM may be configured only in spcell, and the remaining operations may be the same as opt 3. For example, FIG. 16 illustrates a case where RLM operation is possible in spcell's DL anchor carrier and one DL non-anchor carrier, and only one SB / carrier can be activated at any given time. Accordingly, cells other than spcell do not perform separate RLM configuration and RLM operation, or RLF-related operations, and spcell can perform the configuration and terminal operations described in opt 3 as described above.

[0392] In cases other than RLM, RLF may be declared.

[0393] When a terminal in a serving cell, particularly in an spcell, performs random access and needs to transmit more than a predetermined number of RA preamble transmissions (or the maximum allowed RA preamble transmission), it may transmit an RA problem indicator from the MAC layer to the RRC layer and declare an RLF. In the case of multiple carriers, the following operations are possible.

[0394] Opt 1. The RACH problem may only apply to anchor UL carrier / UL SB. For example, if a terminal performs RA on an anchor UL carrier / UL SB and needs to transmit more than a certain number of RA preambles, the terminal's MAC may transmit a RACH problem indicator to the RRC, and the terminal may declare an RLF with the cause of the RACH problem based on this.

[0395] Opt 2. In cases where applicable to multiple UL carriers, if the terminal is not an anchor UL carrier and must transmit an RA preamble for a UL carrier / UL SB more than a predetermined number of times, the terminal may report via another valid UL carrier / SB, citing a RACH failure of the carrier as the cause. In this case, the terminal may not declare an RLF. The report may be conveyed via a UCI / UL MAC CE or UL RRC message and may also be signaled including the UL serving carrier index / UL SB index of the UL carrier. Additionally, if the terminal must transmit an RA preamble on the UL anchor carrier more than a given number of times, the terminal may declare the cell as an RLF.

[0396] Additionally, according to one embodiment, if a failure to perform RACH occurs on any UL Carrier where UL transmission is allowed, the MAC layer may indicate to the RRC layer a RACH problem for the cell. Upon receiving such indication, the RRC layer may declare an RLF for the cell.

[0397] FIG. 17 illustrates an example of an RLF related to a RACH failure according to one embodiment of the present disclosure.

[0398] As another embodiment, in the case of RLC max retransmission, when the terminal is in a logical channel that includes spcell as an allowed serving cell, if retransmission is performed more than a predefined number of times at the RLC layer of the said logical channel, the corresponding spcell and cell group may be declared as RLF. In contrast, in the case of multiple carriers, when configuring serving cells, the network may specify the UL carrier to which the UL MAC SDU of a specific logical channel can be transmitted. For example, the network may specify UL transmission per carrier when considering UL bandwidth or when seeking spatial diversity gain in PDCP duplication. If, in this case, the specified RLC max retransmission occurs in the said logical channel, the following operations are possible.

[0399] If a UL anchor carrier exists in the allowed UL carrier specified for the logical channel, the terminal can declare an RLF for the cell.

[0400] Otherwise (e.g., when no UL anchor carrier exists in the allowed UL carrier of the logical channel where RLC max retransmission occurred), the terminal may declare an RLC failure at the RLC layer and report the information as an RLC failure through a valid UL carrier or its UL SB. Such signaling may be transmitted via a UCI, UL MAC CE, or UL RRC message. The information may include the logical channel ID / index where the RLC failure occurred and / or RLC failure or max RLC retransmission as the cause value.

[0401] FIG. 18 is a block diagram of a terminal or user equipment (1800) according to one embodiment of the present disclosure.

[0402] The terminal (1800) is an electronic device capable of wireless communication and may include user equipment (UE), mobile phones, smartphones, tablets, Internet of Things (IoT) devices having various form factors, and can perform wireless communication with a base station through a wireless channel.

[0403] Referring to FIG. 18, the terminal (1800) may include at least one transceiver (1801) (hereinafter, transceiver), at least one processor (1802) (hereinafter, processor), and at least one memory (1803) (hereinafter, memory). According to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure, the transceiver (1801), processor (1802), and memory (1803) of the terminal (1800) may be operated. However, the components of the terminal (1800) are not limited to the examples of components shown in FIG. 18. In other embodiments, the terminal (1800) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (1801), processor (1802), or memory (1803) may be integrated into a single component.

[0404] The transceiver (1801) may be a basic communication circuit or communication circuitry that enables the terminal (1800) to perform wireless communication with a node or entity of a network. For example, the transceiver (1801) may enable the terminal (1800) to transmit and receive signals to and from a base station via cellular wireless communication, or to transmit and receive signals to and from another terminal via cellular wireless communication. For example, the transceiver (1801) may support at least one of various cellular wireless communication technologies including 3G (3rd generation), 4G (4th generation) LTE (long-term evolution), 5G (5th generation) NR (new radio), 6G (6th generation), etc., and the various cellular wireless communication technologies supported by the transceiver (1801) may include all subsequent generations of wireless communication.

[0405] According to one embodiment, the terminal (1800) may include a plurality of transceivers, and for example, when supporting EN-DC (E-UTRA (evolved-universal terrestrial radio access) - NR dual connectivity), it may include a first transceiver supporting 4G LTE wireless communication and a second transceiver supporting 5G NR wireless communication. According to another embodiment, when the terminal (1800) supports NR-DC (NR Dual Connectivity), the terminal (1800) may include a plurality of transceivers supporting 5G NR wireless communication. According to another embodiment, if the terminal (1800) supports short-range wireless communication, the terminal (1800) may separately include a transceiver that supports at least one of a group of wireless communication protocol standards such as those defined by Bluetooth®, wireless LAN or WLAN (wireless local area network) network (including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba and 802.11be).

[0406] According to one embodiment, the transceiver (1801) may include various circuit structures used to transmit and receive signals to and from a base station via a wireless channel. The signals may include control information and data. For example, the transceiver (1801) may be configured to include a radio frequency (RF) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (1801) may output the signal received via the wireless channel to a processor (1802) and transmit the signal output from the processor (1802) via the wireless channel.

[0407] A processor (1802) may control the overall operation of a terminal (1800) according to an embodiment of the present disclosure. The processor (1802) may be implemented as one or more IC (integrated circuit (or circuitry)) chips and may perform various data processing operations. The processor (1802) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (1803) individually, collectively, or in any combination. Additionally, the processor (1802) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0408] The processor (1802) is electrically, operatively, or communicatively coupled to the transceiver (1801) so as to control the transceiver (1801).

[0409] The processor (1802) may include at least one processor (or, processing circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. For example, the processor (1802) may include a communication processor (CP) that controls communication operations and an application processor (AP) that controls the execution of an upper layer (e.g., an application layer). In a specific embodiment, at least one part of the processor (1802) may be included in one chip, and another part of the processor (1802) may be included in a separate chip. Alternatively, at least one processor may be included in other components, e.g., a transceiver (1801) or a memory (1803).

[0410] The processor (1802) may perform, cause, or control the operation of a terminal to perform at least one or a combination of the methods according to the embodiments of the present disclosure. For example, the processor (1802) may control the operation of a terminal to process a downlink signal received from a base station or to generate an uplink signal and transmit it to a base station. To this end, the processor (1802) may control other components of the terminal (1800) to perform various operations by executing computer programs, code, or instructions stored in memory (1803).

[0411] Memory (1803) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (1803) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0412] The memory (1803) can be electrically, operatively, or communically coupled with the processor (1802) and can be accessed by the processor (1802).

[0413] A computer program, code, or instruction that can be executed by a processor (1802) may be stored in the memory (1803). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (1802) may be stored in a single memory device or may be separated and distributed across two or more memory devices. The processor (1802) may perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (1803).

[0414] According to one embodiment of the present disclosure, the operation of the terminal (1800) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (1803), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.

[0415] FIG. 19 is a block diagram of a base station (1900) according to one embodiment of the present disclosure.

[0416] The base station (1900) can perform wireless communication with at least one terminal within the area of ​​the base station (1900) through a wireless channel.

[0417] Referring to FIG. 19, a base station (1900) may include at least one transceiver (1901) (hereinafter, transceiver), at least one processor (1902) (hereinafter, processor), and at least one memory (1903) (hereinafter, memory). According to at least one or a combination thereof of methods corresponding to embodiments of the present disclosure, the transceiver (1901), processor (1902), and memory (1903) of the base station (1900) may be operated. However, the components of the base station (1900) are not limited to the examples of components shown in FIG. 19. In other embodiments, the base station (1900) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in some embodiments, any combination of the transceiver (1901), processor (1902), or memory (1903) may be integrated into a single component.

[0418] The transceiver (1901) may be a communication circuit or communication circuitry that enables the base station (1900) to perform wireless communication with a node or entity of the network. For example, the transceiver (1901) may enable the base station (1900) to transmit and receive signals to and from a terminal (X00) via cellular wireless communication or to transmit and receive signals to and from another network entity via wireless communication. For example, the transceiver (1901) may support various cellular wireless communication technologies including 3G (3rd generation), 4G (4th generation) LTE (long-term evolution), 5G (5th generation) NR (new radio), 6G (6th generation), etc., and the various cellular wireless communication technologies supported by the transceiver (1901) may include all subsequent generations of wireless communication. According to one embodiment, the transceiver (1901) may include various circuit structures used to transmit and receive signals to and from a terminal via a wireless channel. The signals may include control information and data. For example, the transceiver (1901) may be configured to include a radio frequency (RF) transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. The transceiver (1901) may output the signal received via the wireless channel to a processor (1902) and transmit the signal output from the processor (1902) via the wireless channel.

[0419] Meanwhile, according to one embodiment of the present disclosure, a base station (1900) may communicate with an entity or node of a network via wired or wireless communication. For example, the base station (1900) may communicate via wired or wireless communication with an entity or node of an adjacent base station or core network via a backhaul network. Although not shown in the drawings, when the base station (1900) performs wired communication, the base station (1900) may include a separate network interface for wired communication in addition to the transceiver (1901). The network interface may be referred to as network interface circuitry, communication interface circuitry, etc.

[0420] A processor (1902) can control the overall operation of a base station (1900) according to an embodiment of the present disclosure. The processor (1902) may be implemented as one or more IC (integrated circuit or circuitry) chips and may perform various data processing operations. The processor (1902) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (1903) individually, collectively, or in any combination. Additionally, the processor (1902) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits.

[0421] The processor (1902) is electrically, operatively, or communicatively coupled to the transceiver (1901) so as to control the transceiver (1901).

[0422] The processor (1902) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a particular embodiment, at least one part of the processor (1902) may be included in one chip, and another part of the processor (1902) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a transceiver (1901) or memory (1903).

[0423] The processor (1902) may perform, cause, or control the operation of a base station to perform at least one or a combination of the methods according to the embodiments of the present disclosure. For example, the processor (1902) may control the operation of a base station to generate a downlink signal and transmit it to a terminal, or to process an uplink signal received from a terminal. Alternatively, the base station may transmit and receive signals with an adjacent base station, transmit a signal received from a terminal to an upper node of the network, or receive a signal from an upper node of the network and transmit it to a terminal. To this end, the processor (1902) may control other components of the base station (1900) to perform various operations by executing computer programs, codes, and instructions stored in memory (1903).

[0424] Memory (1903) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (1903) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semi-permanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0425] The memory (1903) can be electrically, operatively, or communically coupled with the processor (1902) and can be accessed by the processor (1902).

[0426] A computer program, code, or instruction that can be executed by a processor (1902) may be stored in the memory (1903). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (1902) may be stored in a single memory device or may be separated and distributed among two or more memory devices. The processor (1902) may perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (1903).

[0427] According to one embodiment of the present disclosure, the operation of a base station (1900) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer programs or code) stored in memory (1903), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.

[0428] A terminal or a base station can perform various communication procedures related to the control plane or user plane by interacting with network entities based on communication through a wireless channel. For example, a terminal can communicate with network entities such as an access and mobility management function (AMF) or a session management function (SMF) through a base station. Alternatively, the base station can perform at least one communication procedure by directly transmitting and receiving signals or relaying them with network entities. The structure of the above-mentioned network entities will be explained in more detail through the drawings below.

[0429] FIG. 20 is a block diagram of a network entity (2000) that performs network functions according to one embodiment of the present disclosure.

[0430] A network entity (2000) may include one or more network functions (NF) that constitute a core network (e.g., 5G (5th generation) core, 5GC) in a communication system, or entities (devices, devices, nodes, or servers, etc.) that perform part of a network function. In this case, multiple NFs may be implemented within a single network entity, or a single NF may be distributed and implemented across multiple network entities. Additionally, when an NF is implemented within a network entity, the NF may be implemented in the form of software, and in such cases, a program for running the NF may be loaded into the memory of the network entity (2000).

[0431] A single NF can be implemented as one or more instances and can operate by being distributed across the same network entity or multiple network entities. Here, the instance is a software unit that logically executes a specific network function and may be separate from physical hardware resources. Additionally, one or more NFs may be implemented as a single network slice to operate in order to satisfy the specifications required by a specific service.

[0432] The above NF may include any one of an access and mobility management function (AMF), a session management function (SMF), a local session management function (L-SMF), a user plane function (UPF), a local user plane function (L-UPF), a policy control function (PCF), unified data management (UDM), a unified data repository (UDR), a network exposure function (NEF), a network repository function (NRF), an application function (AF), a network slice selection function (NSSF), a network data analytics function (NWDAF), a network slice admission control function (NSACF), an authentication server function (AUSF), or a data network (DN).

[0433] Referring to FIG. 20, a network entity (2000) may include at least one network interface (2001), at least one processor (2002) (hereinafter, processor), and at least one memory (2003) (hereinafter, memory). As described above, the NF may be implemented in the form of a physical device such as the network entity (2000), or may be implemented and executed in the form of a virtualized instance. When the NF is implemented in the form of an instance, it may not necessarily include physical components as illustrated in FIG. 20. In such cases, the instance may be composed of one or more logical functional units and logically represented.

[0434] According to at least one or a combination thereof of the methods corresponding to the embodiments of the present disclosure, the network interface (2001), processor (2002), and memory (2003) of the network entity (2000) may be operated. However, the components of the network entity (2000) are not limited to the examples of components shown in FIG. 20. In other embodiments, the network entity (2000) may include additional components in addition to the aforementioned components, or some components may be omitted. Also, in one embodiment, the network interface (2001), processor (2002), or memory (2003) may be implemented as a single component.

[0435] The network interface (2001) is a collective term for the transmitting and receiving parts of a network entity and may be a communication circuit for transmitting and receiving signals with a terminal (user equipment, UE), a base station, or another network entity. In this case, the communication circuit may include both a communication circuit for wireless communication and a communication circuit for wired communication. For example, the network interface (2001) may include circuits, logic, hardware, etc. configured to exchange control plane messages or user plane messages with a terminal, a base station, or other core network entities via wireless or wired communication. The network interface (2001) may operate using various protocols (e.g., NAS (Non-Access Stratum) protocol). Depending on the convenience of explanation and technical implementation, the network interface (2001) may be referred to as a communication circuitry, a network interface circuitry, or a communication interface circuitry.

[0436] A processor (2002) may control the overall operation of a network entity (2000) according to an embodiment of the present disclosure. In one embodiment, the processor (2002) may be implemented as one or more IC (integrated circuit or circuitry) chips and may perform various data processing operations. The processor (2002) may include at least one electrical circuit and may execute instructions (or programs, code, data, etc.) stored in memory (2003) individually, collectively, or in any combination. Additionally, the processor (2002) may include a single-core processor or a multi-core processor, and in a specific implementation, may be composed of a processor assembly including a plurality of processing circuits. Additionally, it should be noted that the processor (2002) may not necessarily be composed of physical hardware when the network function (2000) is implemented in an instance form according to another embodiment.

[0437] According to one embodiment, the processor (2002) is electrically, operatively, or communicatively coupled to the network interface (2001) so as to control the network interface (2001).

[0438] The processor (2002) may include at least one processor (or processor circuitry), and at least one processor may perform the following operations individually, collectively, or in any combination. In a specific embodiment, at least one part of the processor (2002) may be included in one chip, and another part of the processor (2002) may be included in a separate chip. Alternatively, at least one processor may be included in other components, such as a network interface (2001) or memory (2003).

[0439] A processor (2002) may perform or control operations of a network entity (2000) to perform at least one or a combination thereof of methods according to embodiments of the present disclosure. For example, the processor (2002) may control operations of the network entity (2000) to exchange control plane messages or user plane messages with terminals, base stations, or other core network entities via wireless or wired communication using various protocols (e.g., NAS protocols). To this end, the processor (2002) may control other components of the network entity (2000) to perform various operations by executing computer programs, code, or instructions stored in memory (2003).

[0440] Memory (2003) is a hardware storage device capable of storing information temporarily or permanently and may include one or more storage media. For example, memory (2003) may include a memory assembly comprising one or more storage media. For example, the one or more storage media may include a hard drive, flash memory, permanent memory such as ROM (read-only memory), semipermanent memory such as RAM (random access memory), cache memory, or any combination thereof.

[0441] According to one embodiment, the memory (2003) may be electrically, operatively, or communicatively coupled to the processor (2002) and may be accessed by the processor (2002).

[0442] A computer program, code, or instruction that can be executed by a processor (2002) may be stored in the memory (2003). According to one embodiment, the computer program, code, or instruction that can be executed by the processor (2002) may be stored in a single memory or separated and distributed across two or more memories. The processor (2002) may perform various functions according to the embodiments of the present disclosure by executing the instruction stored in the memory (2003).

[0443] According to one embodiment of the present disclosure, the operation of a network entity (2000) may be caused to be performed based on at least one processor (or processing circuit) configured to perform the features of the present disclosure individually, collectively, or in any combination based on the execution of instructions (or computer program or code) stored in memory (2003), based on processing circuitry not configured to execute instructions, and / or based on components of a processing circuitry not configured to execute instructions.

[0444] Methods according to the embodiments described in the claims or specification of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software.

[0445] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to embodiments described in the claims or specification of the present invention.

[0446] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, ROM (Read Only Memory), Electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disc storage devices, Compact Disc-ROM (CD-ROM), Digital Versatile Discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0447] In addition, the above program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, Local Area Network (LAN), Wide LAN (WLAN), or Storage Area Network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present invention through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present invention.

[0448] In the specific embodiments of the present invention described above, the components included in the invention are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expressions are selected to suit the situations presented for convenience of explanation, and the present invention is not limited to singular or plural components; even if a component is expressed in the plural, it may be composed of a singular form, or even if a component is expressed in the singular form, it may be composed of a plural form.

[0449] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. In a wireless communication system, a method performed by a terminal (user equipment, UE), A step of receiving from a base station configuration information including information for configuring a cell comprising one or more DL (downlink) carriers and RLM configuration information configured for each of the one or more DL carriers; and The method includes the step of performing radio link monitoring (RLM) on at least one of the first DL carrier or the second DL carrier among the one or more DL carriers mentioned above, and The above first DL carrier is an anchor carrier, and A method in which the second DL carrier is a non-anchor carrier.

2. In claim 1, the above method is, When the above RLM is performed on the first DL carrier: A step of performing a radio resource control (RRC) reestablishment operation when the first timer for the first DL carrier expires; or When the above RLM is performed simultaneously on the first DL carrier and the second DL carrier: A method comprising the step of transmitting a radio link failure (RLF) report associated with the first DL carrier or the second DL carrier on an uplink (UL) carrier associated with the unexpired timer when one of the first timer for the first DL carrier or the second timer for the second DL carrier expires.

3. In Paragraph 1, The above setting information includes information for indicating a BWP (bandwidth part) corresponding to the one or more DL carriers, and A method in which the ID of the above BWP is unique within the cell or unique within each of the one or more DL carriers.

4. The method of claim 1, wherein the RLM setting information comprises an ID (identifier) ​​of a reference signal (RS), an indicator indicating the type of the RS, an indicator indicating the purpose of the RS, and information associated with a timer for the RLF.

5. The method according to claim 1, wherein the cell is a SpCell (special cell).

6. In claim 1, the above method is, A step of determining the RLF when the number of random access preamble transmissions for the first DL carrier is greater than a preset number; or A method further comprising the step of transmitting a random access failure report of the second DL carrier on a UL carrier associated with the first DL carrier when the number of random access preamble transmissions for the second DL carrier is greater than a preset number.

7. In claim 1, the above method is, A step of determining the RLF when the number of logical channel retransmissions for the first DL carrier is greater than a preset number; or A method further comprising the step of transmitting a radio link control (RLC) failure report of the second DL carrier on a UL carrier associated with the first DL carrier when the number of logical channel retransmissions for the second DL carrier is greater than a preset number.

8. In a wireless communication system, regarding a terminal (user equipment, UE), At least one transceiver; At least one processor communicatively coupled to the above at least one transceiver; and It includes at least one memory that is communicationally coupled to the above at least one processor and stores instructions, and The above instructions are executed individually or in any combination by the above at least one processor, so that the terminal: Receive configuration information from a base station, including information for configuring a cell comprising one or more DL (downlink) carriers and RLM configuration information configured for each of the one or more DL carriers, and RLM (radio link monitoring) is performed on at least one of the first DL carrier or the second DL carrier among the above one or more DL carriers, and The above first DL carrier is an anchor carrier, and A terminal in which the second DL carrier is a non-anchor carrier.

9. In claim 8, the above commands are the terminal: When the above RLM is performed on the first DL carrier: When the first timer for the first DL carrier expires, perform a radio resource control (RRC) reestablishment operation; or When the above RLM is performed simultaneously on the first DL carrier and the second DL carrier: A terminal that transmits a radio link failure (RLF) report associated with the first DL carrier or the second DL carrier on the uplink (UL) carrier associated with the unexpired timer when one of the first timer for the first DL carrier or the second timer for the second DL carrier expires.

10. In Paragraph 8, The above setting information includes information for indicating a BWP (bandwidth part) corresponding to the one or more DL carriers, and A terminal in which the ID of the above BWP is unique within the cell or unique within each of the one or more DL carriers.

11. In claim 8, the RLM setting information comprises an ID (identifier) ​​of a reference signal (RS), an indicator indicating the type of the RS, an indicator indicating the purpose of the RS, and information associated with a timer for the RLF, a terminal.

12. In claim 1, the cell is a terminal that is a SpCell (special cell).

13. In claim 8, the above commands are the terminal: If the number of random access preamble transmissions for the first DL carrier is greater than a preset number, determine the RLF, or A terminal that transmits a random access failure report of the second DL carrier on a UL carrier associated with the first DL carrier when the number of random access preamble transmissions for the second DL carrier is greater than a preset number.

14. In claim 8, the above commands are the terminal: If the number of logical channel retransmissions for the first DL carrier is greater than a preset number, determine the RLF, or A terminal that transmits a radio link control (RLC) failure report of the second DL carrier on a UL carrier associated with the first DL carrier when the number of logical channel retransmissions for the second DL carrier is greater than a preset number.