Random access method of terminal in multi-carrier single cell system and apparatus using same
The method optimizes MCSC systems by distributing connection attempts across multiple carriers using system information, addressing inefficiencies and delays in carrier selection and resource allocation.
Patent Information
- Application Number
- PCT/KR2026/096560
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-08
- Filing Date
- 2026-05-04
- Publication Date
- 2026-11-12
AI Technical Summary
In multi-carrier single-cell (MCSC) systems, resource allocation, uplink transmission timing, and random access processes become complex, leading to inefficiencies and increased connection delays due to the complexity of carrier selection and resource linkage in initial connection attempts.
A method and apparatus for Random Access (RA) in MCSC systems, where terminals and base stations utilize system information to distribute connection attempts across multiple carriers, reducing the likelihood of collisions and optimizing resource utilization.
This approach mitigates connection delays, improves resource efficiency, and enhances system throughput by evenly distributing connection requests across carriers, reducing power consumption and service degradation.
Smart Images

Figure KR2026096560_12112026_PF_FP_ABST
Abstract
Description
Random access method of a terminal in a multi-carrier single-cell system and device using the same
[0001] The present disclosure relates to a wireless communication system and provides a method and apparatus for Random Access (RA) of a terminal in a multi-carrier single cell (MCSC) system.
[0002] Wireless access systems are being widely deployed to provide various types of communication services, such as voice and data. Generally, a wireless access system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access) systems.
[0003] As more communication devices require larger communication capacities, the need for enhanced mobile broadband communication compared to existing radio access technology (RAT) is emerging. Furthermore, Massive Machine Type Communications (MTC), which connects multiple devices and objects to provide various services anytime and anywhere, is also one of the major issues to be considered in next-generation communication. In addition, communication system designs that take into account services and terminals sensitive to reliability and latency are being discussed. Thus, the introduction of next-generation radio access technologies that consider enhanced mobile broadband communication, massive MTC, and Ultra-Reliable and Low Latency Communication (URLC) is being discussed, and for convenience, this technology is referred to as new RAT or NR in this disclosure.
[0004] Mobile communication systems are evolving toward utilizing multiple carriers to enhance data transmission speeds and efficiently utilize wireless resources. In this environment, MCSC systems can be considered as structures capable of increasing system capacity and improving terminal transmission efficiency by operating multiple carriers within a single cell. However, in conventional MCSC systems, resource allocation among multiple carriers within the same cell, uplink transmission timing, control signal transmission and reception procedures, and random access processes for initial connection can become more complex. In particular, regarding the random access procedure performed by a terminal to connect to a cell or achieve uplink synchronization, the decision of which carrier to use to transmit the preamble or message, how to establish resource linkage relationships between carriers, and how the base station responds to these matters can significantly impact system performance and the efficiency of the signaling process. Therefore, there is a need for random access methods suitable for a multi-carrier single-cell environment and devices that support such methods.
[0005] In particular, since a single cell in an MCSC system consists of multiple carriers, multi-carrier scheduling is required from the initial connection phase—an earlier stage than in conventional systems—to utilize resources efficiently from the very beginning.
[0006] The technical problem that the present disclosure aims to solve is related to wireless communication systems, and the present disclosure is related to wireless communication systems, specifically providing a method and apparatus for Random Access (RA) of a terminal in a multi-carrier single cell (MCSC) system.
[0007] In a wireless communication system, the method is characterized in that a terminal (user equipment; UE) receives system information from a base station, and the terminal performs a random access process with the base station based on the system information, wherein the system information includes information related to a combination of multiple beams for multiple carriers included in a single cell.
[0008] In another aspect, a terminal, device, and computer-readable storage medium are provided for executing the above method.
[0009] In another aspect, a method of operation of a base station and a base station device are provided. In the method, the base station transmits system information to a terminal (user equipment: UE), and the base station performs a random access process with the terminal based on the system information, wherein the system information includes information related to combinations between multiple beams for multiple carriers included in a single cell.
[0010] According to the method of the present disclosure, even if multiple terminals attempt to connect to a single cell simultaneously during the initial connection phase of a terminal, the connection attempts of the terminals can be distributed in the frequency domain by utilizing multiple carriers. Accordingly, the phenomenon of connection requests being concentrated on a specific carrier can be mitigated, and the connection delay of the terminal can be reduced by lowering the possibility of random access collisions. In addition, since connection resources can be utilized more evenly across multiple carriers, the efficiency of wireless resource utilization can be improved, and the flexibility of resource allocation and scheduling by the base station can also be increased.
[0011] Furthermore, according to the method of the present disclosure, the load during the random access process can be prevented from being concentrated on specific frequency resources, thereby improving the stability of connection processing within the cell. In addition, as connection requests are distributed across multiple carriers, the base station can perform more efficient control considering the traffic status of each carrier, and as a result, the overall system throughput and operational efficiency can be improved. Moreover, the reduction of collisions and increased resource utilization efficiency during the initial connection phase can lead to a reduction in the number of retries, which can also contribute to reducing the power consumption of the terminal and mitigating the degradation of service quality.
[0012] The effects obtainable from the embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by a person skilled in the art to which the technical configuration of the present disclosure applies from the description of the embodiments of the present disclosure below. That is, unintended effects resulting from implementing the configuration described in the present disclosure can also be derived by a person skilled in the art from the embodiments of the present disclosure.
[0013] The drawings attached below are intended to aid in understanding the present disclosure and may provide embodiments of the present disclosure together with the detailed description. However, the technical features of the present disclosure are not limited to specific drawings, and features disclosed in each drawing may be combined with one another to form new embodiments. Reference numerals in each drawing may denote structural elements.
[0014] FIG. 1 illustrates a communication procedure between devices according to one embodiment of the present disclosure.
[0015] FIG. 2 illustrates a flexible network topology that can be applied to an embodiment of the present disclosure.
[0016] Figure 3 illustrates a general functional structure related to both function-based LCM and model-based LCM.
[0017] Figure 4 illustrates the execution of operations based on an AI / ML model and related signaling.
[0018] FIG. 5 illustrates a procedure for transmitting system information for THz communication (terahertz communication) to which the present disclosure applies.
[0019] FIG. 6 illustrates a beam management procedure applicable to the present disclosure.
[0020] FIG. 7 shows an electromagnetic spectrum according to one embodiment of the present disclosure.
[0021] FIG. 8 shows an example of a general NTN scenario based on a transparent payload according to one embodiment of the present disclosure.
[0022] FIG. 9 shows an example of a general NTN scenario based on a regenerated payload according to one embodiment of the present disclosure.
[0023] Figure 10 illustrates the components of an orbital parameter orbital format.
[0024] FIG. 11 illustrates an offset (e.g., K_offset and k_mac), TA value, validity duration, and epoch time for time / frequency synchronization in an NTN-based wireless communication system.
[0025] FIG. 12 illustrates terminal-specific TA and common TA.
[0026] FIGS. 13 and 14 illustrate an example of a sensing operation according to an embodiment of the present disclosure.
[0027] FIG. 15 illustrates a time / frequency resource for a sensing operation according to one embodiment of the present disclosure.
[0028] FIG. 16 illustrates a procedure related to a sensing operation according to one embodiment of the present disclosure.
[0029] Figure 17 illustrates the operation procedure of a base station supporting NES technology.
[0030] Figure 18 illustrates a procedure for cell DTX / DRX operation.
[0031] Figure 19 illustrates a procedure for CA operation using a secondary cell without an SSB.
[0032] Figure 20 illustrates a Conditional Handover (CHO) procedure.
[0033] Figure 21 illustrates a procedure for measuring and reporting CSI.
[0034] FIGS. 22, FIGS. 23, and FIGS. 24 illustrate scenarios regarding SIB1 transmission triggering.
[0035] FIG. 25 illustrates an embodiment related to the beam relationship between multiple carriers within a single cell.
[0036] FIG. 26 illustrates a carrier selection method for cases where priority information among multiple carriers is given.
[0037] FIG. 27 illustrates a carrier selection method for cases where priority information of multiple carrier mountains is not given.
[0038] Figure 28 illustrates RO dispersion among UL carriers.
[0039] Figure 29 illustrates various configuration forms of MCSC.
[0040] FIG. 30 illustrates a RACH procedure when the terminal moves.
[0041] FIG. 31 illustrates a beam combination between multiple carriers.
[0042] FIG. 32 illustrates a procedure for providing information about a combination of multiple carriers through RO.
[0043] FIGS. 33 and FIGS. 34 illustrate a procedure for providing information regarding beams of receivable carriers as message 3 and / or message 5.
[0044] FIG. 35 illustrates a procedure for providing information of multiple carriers based on message 2 instead of SIB1 based on RO.
[0045] Figure 36 illustrates a procedure in which carrier / beam-related information is provided in Message 4 instead of SIB1 based on RO.
[0046] FIGS. 37 and FIGS. 38 illustrate the MAC payload for message B.
[0047] FIG. 39 illustrates a method of operation of a terminal.
[0048] Figure 40 illustrates the signaling process between a terminal and a base station.
[0049] FIG. 41 illustrates a wireless device that can be applied to the present disclosure.
[0050] Figure 42 illustrates another example of a wireless device.
[0051] Figure 43 illustrates an example of a signal processing module structure.
[0052] Figure 44 illustrates another example of a signal processing module structure within a transmission device.
[0053] FIG. 45 illustrates an example of a wireless communication device according to an embodiment of the present disclosure.
[0054] FIG. 46 illustrates a communication system (1) to which the present disclosure applies.
[0055] The attached drawings are intended to aid in understanding the present disclosure and may provide embodiments of the present disclosure together with the detailed description. While multiple initial connections are attempted, the technical features of the present disclosure are not limited to the specific drawings, and the features disclosed in each drawing may be combined with one another to form new embodiments. Reference numerals in each drawing may denote structural elements.
[0056] The following embodiments are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature may be considered optional unless otherwise explicitly stated. Each component or feature may be implemented in a form not combined with other components or features. Additionally, some components and / or features may be combined to form embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of any embodiment may be included in other embodiments, or may be replaced with corresponding components or features of other embodiments.
[0057] In the description of the drawings, procedures or steps that could obscure the gist of the present disclosure have not been described, nor have procedures or steps that are understandable to those skilled in the art been described.
[0058] Throughout the specification, when a part is described as "comprising" or "including" a component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components. Furthermore, terms such as "...part," "...unit," and "module" as used in the specification refer to a unit that performs at least one function or operation, and may be implemented in hardware, software, or a combination of hardware and software. Additionally, "one (a or an)," "one," "the," and similar related terms may be used in the context describing the present disclosure (particularly in the context of the following claims) in a sense that includes both singular and plural forms, unless otherwise indicated in the present disclosure or clearly contradicted by the context.
[0059] In this disclosure, the embodiments are described with a focus on the data transmission and reception relationship between a base station and a mobile station. Here, the base station refers to a terminal node of a network that communicates directly with a mobile station. Specific operations described in this document as being performed by a base station may, in some cases, be performed by an upper node of the base station.
[0060] That is, in a network consisting of multiple network nodes including a base station, various operations performed for communication with a mobile station may be performed by the base station or other network nodes other than the base station. In this case, 'base station' may be replaced by terms such as fixed station, Node B, eNB (eNode B), gNB (gNode B), ng-eNB, advanced base station (ABS), or access point.
[0061] Additionally, in the embodiments of the present disclosure, the term terminal may be replaced with terms such as user equipment (UE), mobile station (MS), subscriber station (SS), mobile subscriber station (MSS), mobile terminal, or advanced mobile station (AMS). Hereinafter, for convenience, the terminal may be referred to as a UE.
[0062] Furthermore, the transmitting end refers to a fixed and / or mobile node that provides data or voice services, and the receiving end refers to a fixed and / or mobile node that receives data or voice services. Therefore, in the case of the uplink, a mobile station can be the transmitting end and a base station can be the receiving end. Similarly, in the case of the downlink, a mobile station can be the receiving end and a base station can be the transmitting end.
[0063] Embodiments of the present disclosure may be supported by standard documents disclosed in at least one of wireless access systems, such as IEEE 802.xx systems, 3GPP (3rd Generation Partnership Project) systems, 3GPP LTE (Long Term Evolution) systems, 3GPP 5G (5th generation) NR (New Radio) systems and 3GPP2 systems, for example, embodiments of the present disclosure may be supported by 3GPP TS (technical specification) 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.321 and 3GPP TS 38.331 documents.
[0064] In addition, the embodiments of the present disclosure may be applied to other wireless access systems and are not limited to the systems described above. For example, they may be applicable to systems applied after the 3GPP 5G NR system and are not limited to specific systems.
[0065] That is, obvious steps or parts not described in the embodiments of the present disclosure may be described by referring to the aforementioned documents. Additionally, all terms disclosed in this document may be explained by the aforementioned standard documents.
[0066] Hereinafter, preferred embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiment in which the technical configuration of the present disclosure can be implemented.
[0067] Additionally, specific terms used in the embodiments of the present disclosure are provided to aid in understanding the present disclosure, and the use of such specific terms may be modified in other forms without departing from the technical spirit of the present disclosure.
[0068] The following technology can be applied to various wireless access systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access).
[0069] For the sake of clarity, the following description is based on 3GPP communication systems (e.g., LTE, NR, etc.), but the technical scope of this disclosure is not limited thereto. LTE may refer to technology from 3GPP TS 36.xxx Release 8 onwards. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onwards is referred to as LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onwards may be referred to as LTE-A pro. 3GPP NR may refer to technology from TS 38.xxx Release 15 onwards. 3GPP 6G may be an example of a next-generation wireless communication system. "xxx" indicates a specific standard document number. LTE / NR / 6G may be collectively referred to as 3GPP systems.
[0070] Regarding the background technology, terms, abbreviations, etc. used in this disclosure, reference may be made to the standard documents previously disclosed in this disclosure. For example, reference may be made to standard documents 36.xxx and 38.xxx.
[0071] In the present disclosure, “A or B” may mean “only A,” “only B,” or “both A and B.” Alternatively, in the present disclosure, “A or B” may be interpreted as “A and / or B.” For example, in the present disclosure, “A, B or C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.”
[0072] A slash ( / ) or a comma used in the present disclosure may mean “and / or.” For example, “A / B” may mean “A and / or B.” Accordingly, “A / B” may mean “only A,” “only B,” or “both A and B.” For example, “A, B, C” may mean “A, B or C.”
[0073] In the present disclosure, “at least one of A and B” may mean “only A,” “only B,” or “both A and B.” Additionally, in the present disclosure, the expressions “at least one of A or B” or “at least one of A and / or B” may be interpreted as synonymous with “at least one of A and B.”
[0074] Additionally, in the present disclosure, “at least one of A, B and C” may mean “only A,” “only B,” “only C,” or “any combination of A, B and C.” Additionally, “at least one of A, B or C” or “at least one of A, B and / or C” may mean “at least one of A, B and C.”
[0075] Additionally, parentheses used in this disclosure may mean “for example.” Specifically, when indicated as “control information (PDCCH),” “PDCCH” may be proposed as an example of “control information.” In other words, the “control information” of this disclosure is not limited to “PDCCH,” and “PDCCH” may be proposed as an example of “control information.” Furthermore, even when indicated as “control information (i.e., PDCCH),” “PDCCH” may be proposed as an example of “control information.”
[0076] Technical features described individually within one drawing in this disclosure may be implemented individually or simultaneously.
[0077] The following drawings are made to illustrate a specific example of the present disclosure. The names of specific devices or specific signals / messages / fields described in the drawings are presented as examples, and therefore the technical features of the present disclosure are not limited to the specific names used in the following drawings.
[0078] The effects obtainable through a specific example of the present disclosure are not limited to those listed. For example, there may be various technical effects that a person having ordinary skill in the related art can understand or derive from the present disclosure. Accordingly, the specific effects of the present disclosure are not limited to those explicitly described in the present disclosure, but may include various effects that can be understood or derived from the technical features of the present disclosure.
[0079] FIG. 1 illustrates a communication procedure between devices according to one embodiment of the present disclosure. The embodiment of FIG. 1 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, suggestions, methods, and / or operations of the embodiments may be omitted.
[0080] Referring to FIG. 1, in step S101, the terminal and the base station may perform synchronization. For example, the terminal may be at least one of the terminal and / or the device proposed in the present disclosure. For example, the base station may be at least one of the base station, network, RAN node, NTN node / cell, TRP, terminal and / or the device proposed in the present disclosure. For example, the terminal may perform an initial cell search operation. For example, the terminal may detect at least one synchronization signal transmitted according to rules predefined by the base station. Here, for example, the synchronization signal may include a plurality of synchronization signals (e.g., primary synchronization signal, secondary synchronization signal, etc.) classified according to structure or use. Through this, the terminal may identify the boundaries of the base station's frame, subframe, time unit, slot, and / or symbol, and the terminal may obtain information about the base station (e.g., cell identifier).
[0081] In step S103, the terminal may obtain system information transmitted by the base station. For example, the system information may include information related to the attributes, characteristics, and / or capabilities of the base station required to connect to the base station and use services. For example, the system information may be classified according to content (e.g., whether it is essential for connection), transmission structure (e.g., the channel used, whether it is provided on demand), etc. For example, the system information may be classified into a master information block (MIB) and a system information block (SIB). For example, if necessary, the terminal may transmit a signal requesting the system information prior to receiving the system information. For example, the request and provision of the system information may be performed after a random access procedure described later.
[0082] In step S105, the terminal and the base station may perform a random access procedure. For example, the terminal may transmit and / or receive at least one message for the random access procedure (e.g., a random access preamble, a random access response message, etc.) based on information related to the base station's random access channel obtained through system information (e.g., channel location, channel structure, structure of a supported preamble, etc.). For example, the terminal may transmit a preamble (e.g., Msg1) through the random access channel, and the terminal may receive a random access response message (e.g., Msg2). The terminal may transmit a message (e.g., Msg3) containing information related to the terminal (e.g., identification information) to the base station using scheduling information included in the random access response message, and the terminal may receive a message (e.g., Msg4) for contention resolution and / or connection establishment. For example, Msg1 and Msg3 can be transmitted and received as a single message (e.g., MsgA), and / or Msg2 and Msg4 can be transmitted and received as a single message (e.g., MsgB).
[0083] In step S107, the terminal and the base station may perform signaling of control information. Here, for example, the control information may be defined in various layers, such as a layer controlling the connection (e.g., the RRC (radio resource control) layer), a layer handling the mapping between the logical channel and the transmission channel (e.g., the MAC (media access control) layer), and a layer handling the physical channel (e.g., the PHY (physical) layer). For example, the terminal and the base station may perform at least one of signaling to establish a connection, signaling to determine settings related to communication, and / or signaling to indicate allocated resources. For example, the control information may be signaled / transmitted through a control channel. For example, the control information and / or the control channel may be used to schedule at least one of data, a data channel (e.g., a shared channel), and / or control information on the data channel.
[0084] In step S109, the terminal and the base station may transmit and / or receive data. For example, the terminal and the base station may process data based on the signaling of control information and transmit and / or receive it. For example, when transmitting data, the terminal or the base station may perform at least one of channel encoding, rate matching, scrambling, constellation mapping, layer mapping, waveform modulation, antenna mapping, and / or resource mapping on the information bits. For example, when receiving data, the terminal or the base station may perform at least one of signal extraction from resources, antenna-specific waveform demodulation, signal placement considering layer mapping, constellation demapping, descrambling, and / or channel decoding.
[0085] For example, the layers of the radio interface protocol between a terminal and a base station can be classified into L1 (layer 1), L2 (layer 2), L3 (layer 3), etc. For example, the physical layer belonging to layer 1 can provide information transfer services using a physical channel, and the radio resource control (RRC) layer located at layer 3 can perform the role of controlling radio resources between the terminal and the base station. To this end, for example, the RRC layer can exchange RRC messages between the terminal and the base station.
[0086] FIG. 2 illustrates a flexible network topology that can be applied to an embodiment of the present disclosure.
[0087] Referring to FIG. 2, a network topology in which the radio access network (RAN) is configured more flexibly and resiliently can be considered to compensate for incomplete areas of network coverage. To this end, various nodes such as Integrated Access and Backhaul (IAB) nodes, relays, and Radio Frequency Repeaters (RF Repeaters) may be applied, and a Non-Terrestrial Network (NTN) may be integrated. For example, an IAB node may correspond to a node that provides wireless backhaul. For example, a relay may refer to any intermediate point, and in the case of a sidelink relay where a terminal functions as a relay, it may collectively refer to a terminal-to-network (U2N) relay and a terminal-to-terminal (U2U) relay. For example, an RF repeater may correspond to a node that performs simple signal amplification and forwarding functions, while a network-controlled repeater may not only perform signal amplification and forwarding but also adjust transmit / receive settings based on information provided by the network. For example, an NTN node may correspond to a satellite or aircraft that provides NTN coverage that is difficult for terrestrial networks to provide. In addition to these examples, various intermediate points can be introduced to improve the network topology.
[0088] For example, a split RAN can support the division of a base station into one centralized unit (CU) and one or more distributed units (DU). The CU and DU may correspond to logical units. The CU may be further divided into a control plane (CP) portion and one or more user plane (UP) portions. Since a failure in the CU-CP affects not only the CU-UP but also the DU, various intermediate points may be introduced to compensate for this.
[0089] For example, an intermediate point may correspond to a terminal or a base station depending on its relative relationship with other nodes. For example, an IAB node may include a mobile-termination (MT) portion and a DU. The MT can connect the IAB node to a donor node. The DU of the IAB node may serve other terminals or connect to other IAB nodes to provide multi-hop wireless backhaul to terminals. In other words, an IAB node may correspond to a base station in its relative relationship with user-side nodes and to a terminal in its relative relationship with network-side nodes.
[0090] In some examples of the present disclosure, the description of a terminal may apply equally to an intermediate point corresponding to a terminal in relation to a network-side endpoint as well as to a user-side endpoint. For example, in some examples of the present disclosure, the description of a base station may apply equally to an intermediate point corresponding to a base station in relation to a user-side endpoint as well as to a network-side endpoint. However, in most cases where there is no additional description of the operation of three or more entities, the communication entities in the present disclosure are briefly described by the term terminal and / or base station (or first node and / or second node), wherein the term terminal and / or base station (or first node and / or second node) is interpreted to include or replace any endpoint or any intermediate point in relation to other nodes.
[0091] That is, for the sake of brevity of description in some examples of the present disclosure, the subject of the operation may be referred to as a base station and / or terminal (or a first node and / or a second node). Additionally, the term base station and / or terminal (or a first node and / or a second node) may be interpreted or substituted as in the following examples: for example, the base station (or the first node) and the terminal (or the second node) may correspond to a first endpoint and a second endpoint, respectively; may correspond to an endpoint and an intermediate point, respectively; may correspond to an intermediate point and an endpoint, respectively; and may correspond to a first intermediate point and a second intermediate point, respectively.
[0092] In the present disclosure, there may be no intermediate points between a base station and a terminal, or there may be one or more. If intermediate points exist, the intermediate points may correspond to IAB nodes, relays, RF repeaters, NTN (non-terrestrial network) nodes, or nodes supporting other functions. The intermediate points may be nodes with a fixed location or nodes with an indefinite location.
[0093] For example, as core implementation technologies for 6G systems, technologies such as artificial intelligence (AI), THz (Terahertz) communication, optical wireless technology, Free Space Optics backhaul network (FSO), Massive Multiple-Input Multiple-Output technology (MIMO), blockchain, 3D networking, quantum communication, unmanned aerial vehicles, cell-free communication, wireless information and energy transfer (WIET), integration of sensing and communication, integration of access backhaul networks, holographic beamforming, big data analysis, and large intelligent surface (LIS) may be adopted.
[0094] Artificial intelligence (AI) is explained below.
[0095] The introduction of AI into communications can streamline and enhance real-time data transmission. AI can determine how complex target tasks are performed using numerous analyses. In other words, AI can increase efficiency and reduce processing latency. Time-consuming tasks such as handover, network selection, and resource scheduling can be performed instantly using AI. AI can also play a significant role in machine-to-machine, machine-to-human, and human-to-machine communication. Furthermore, AI can enable rapid communication in Brain-Computer Interfaces (BCI). AI-based communication systems can be supported by metamaterials, intelligent structures, intelligent networks, intelligent devices, intelligent cognitive radios, self-sustaining wireless networks, and machine learning (ML).
[0096] The following describes a functional framework for AI / ML operations.
[0097] Below, the following terms can be defined as follows.
[0098] - Data collection: Data collected from network nodes, management entities, or terminals, serving as a basis for AI model training, data analysis, and inference.
[0099] - AI Model: A data-driven algorithm that applies AI technology to generate a set of outputs containing predictive information and / or decision parameters based on a set of inputs.
[0100] - AI / ML Training: An online or offline process of training an AI model by learning features and patterns that best represent data and acquire an AI / ML model trained for inference.
[0101] - AI / ML Inference: A process of making predictions or deriving decisions based on collected data and AI models using trained AI models.
[0102] For example, Life Cycle Management (LCM) procedures for AI / ML models (i.e., model training, model deployment, model inference, model monitoring, model updating, etc.) can be classified into functionality-based LCM and model-based LCM. In functionality-based LCM, AI / ML models may not be identifiable within the network, and the network can direct the activation, deactivation, fallback, or switching of AI / ML functions. In model-ID (identifier)-based LCM, AI / ML models can be identified within the network, and the network or terminal can activate, deactivate, select, or switch AI / ML models via the model ID.
[0103] Figure 3 illustrates a general functional structure related to both function-based LCM and model-based LCM. Some functions or some data / information / command flows (i.e., arrows) illustrated in Figure 3 may be omitted.
[0104] Referring to FIG. 3, a general functional framework may be configured to include a data collection function (10), a model training function (20), a management function (30), an inference function (40), and a model storage function (50).
[0105] The data collection function (10) is a function that provides input data to the model training function (20), management function (30), and inference function (40). The data collection function (10) performs data preparation based on raw data and can provide input data processed through data preparation. Examples of raw data may include received data / measurement data from terminals or other network entities, inference / output of AI / ML models, etc. The data collection function (10) may be performed by a single entity (e.g., terminal, network node, etc.) but may also be performed by multiple entities.
[0106] Here, training data (11) refers to data required as input for the AI / ML model training function (20). monitoring data (12) refers to data required as input for the management (30) of the AI / ML model or AI / ML function. inference data (13) refers to data required as input for the AI / ML inference function (30).
[0107] The model training function (20) is a function that performs AI / ML model training, validation, and testing, which can generate model performance metrics that can be used as part of the AI / ML model testing procedure. If necessary, the model training function (20) can perform data preparation (e.g., data pre-processing and cleaning, forming and transformation) based on the training data (11) delivered from the data collection function (10).
[0108] Trained / Updated Model (21): If there is a Model Storage function (50), it is used to transfer trained, validated, and tested AI / ML models to the Model Storage function (50) or to transfer updated versions of the models to the Model Storage function (50).
[0109] The management function (30) is a function that supervises the operation of an AI / ML model or an AI / ML function. Additionally, the management function (30) may make decisions to ensure appropriate inference operations based on data received from the data collection function (10) (i.e., monitoring data (12)) and / or data received from the inference function (40) (i.e., inference output (41)).
[0110] Management Instruction (32) is information required as input to manage the inference function (40). The relevant information may include the selection / (de)activation / switching of an AI / ML model or an AI / ML-based function, and may also include a fallback to a non-AI / ML operation (i.e., not relying on the inference process).
[0111] A Model Transfer / Delivery Request (33) can be used to request Model(s) from Model Storage (50).
[0112] Performance Feedback / Retraining Request (31) refers to information required as input to the Model Training function (20) (e.g., for the purpose of re-training or updating the model).
[0113] The inference function (40) is a function that provides an output from the process of applying an AI / ML model or AI / ML function using data (i.e., inference data (13)) provided by the data collection (10) as input. Data preparation (e.g., data preprocessing and cleaning, formatting and transformation) may also be performed based on the inference data (13) delivered by the data collection (10). The inference function (40) may also perform data preparation based on the inference data (13) provided by the data collection function (10) if necessary.
[0114] Inference Output (41) is data used by the Management function (30) to monitor the performance of an AI / ML model or AI / ML function. Inference Output (41) may include the inference output of an AI / ML model generated by the Inference function (30), and the details of the inference output may vary depending on the use case.
[0115] The Model Storage function (50) is a function that stores a trained / updated model that can be used to perform the Inference function (40). The Model Storage function (50) exemplified in FIG. 3 can be used as a reference point (if any) applicable to protocol termination, model transmission / delivery, and related processes. Additionally, the Model Storage function (50) is an example and is not intended to restrict the storage location of the actual AI / ML model, and may be omitted.
[0116] Model Transfer / Delivery (51) is used to transfer an AI / ML model to an inference function.
[0117] Cooperation levels can be defined as follows based on the capability of AI / ML functions among multiple nodes, and variations resulting from the combination of the following multiple levels or the separation of any one level are also possible.
[0118] 0a) No collaboration framework: The AI / ML algorithm is based on a pure implementation and does not require changes to the wireless interface.
[0119] 0b) This level corresponds to a framework that involves a wireless interface modified to fit efficient implementation-based AI / ML algorithms but without cooperation.
[0120] 1) Inter-node support is involved to improve the AI / ML algorithms of each node. For example, this applies when a specific node receives support from other nodes (for training, adaptation, etc.) and vice versa. At this level, model exchange between network nodes is not required.
[0121] 2) Collaborative AI / ML operations can be performed among multiple nodes. This level requires the exchange of AI / ML model commands or network nodes.
[0122] FIG. 3 is a diagram illustrating an overall functional framework for an AI / ML model, and all functions and / or all data / information / command signals exemplified in FIG. 2 may not be performed within a specific node, and only some may be performed.
[0123] AI / ML models can be classified into one-side models and two-side models depending on whether training and / or inference are performed on a single node or jointly / sequentially on multiple nodes.
[0124] A one-sided model can refer to an AI / ML model where inference is performed entirely by a single node (e.g., a terminal or a network). Here, the training of the AI / ML model can also be performed entirely by a single node. The training and inference of the AI / ML model may be performed by the same node, or they may be performed by different nodes.
[0125] A two-sided model may refer to an AI / ML model in which joint inference is performed across multiple nodes (e.g., terminals and networks). Joint inference means that inference is performed jointly across multiple nodes; for example, a first part of the inference may be performed by a first node, and the remainder by a second node. Two-sided models can be classified into various types as follows, depending on the training method of the AI / ML model.
[0126] i) First type: An AI / ML model can be trained on a single node. In this case, collaborative training can be performed. Subsequently, the trained model can be distributed to other nodes / entities.
[0127] ii) Second type: Joint training of AI / ML models may be performed on multiple nodes / entities (e.g., networks and terminals). Joint training may mean that model creation (e.g., the CSI (channel state information) creation part) and model reconstruction are trained in the same loop for forward activation and backward gradient. In this type, joint training may include both simultaneous training (model creation training and model reconstruction training are performed simultaneously) and sequential training (model reconstruction training is performed after model creation training).
[0128] iii) Third type: Separate training of AI / ML models can be performed at multiple nodes (e.g., networks and terminals). Separate training may mean that training starts sequentially at one node and continues at another node. In this case, if the first node performs the AI / ML model first and shares the training data with the second node, the second node can perform the AI / ML model using the shared training data. For example, training for the CSI generation part may be performed by the terminal, and CSI reconstruction may be performed by the network.
[0129] The operation described in the present disclosure below can be explained / interpreted based on an AI / ML model as shown in Figure 4 below, even without separate mention (i.e., without explicit mention of being by / based on / for an AI / ML model).
[0130] Additionally, unless specifically limited in the description of the present disclosure, an AI / ML model may correspond to a one-side model or a two-side model in which inference is performed entirely by a single node.
[0131] Figure 4 illustrates the execution of operations based on an AI / ML model and related signaling. Specific details regarding Figure 4 are as follows.
[0132] Step S401: In the description of the present disclosure below, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as the signaling or a set of signaling of Step 1 used to perform an operation based on an AI / ML model, unless otherwise noted. For example, it may correspond to training data for training (i.e., generation and / or reconstruction) the AI / ML model of FIG. 3, or to inference data used for inference of the AI / ML model, or to feedback to the AI / ML model, etc. If signaling between nodes is not required prior to the operation based on the AI / ML model in the present disclosure, this step may be omitted. If a one-sided model is used in the present disclosure, unidirectional / bidirectional signaling (set) in the present disclosure may correspond to this signaling. Additionally, where a two-sided model is used in the present disclosure, unidirectional / bidirectional signaling in the present disclosure may correspond to the signaling in the present disclosure, and repetitive signaling operations may also correspond to the signaling in the present disclosure.
[0133] For example, in AI / ML model-based beam management, when a base station predicts (i.e., infers) high-quality beam(s) based on an AI / ML model, the base station can receive quality / intensity information for multiple beams from the terminal. Additionally, when a terminal predicts (i.e., infers) high-quality beam(s) based on an AI / ML model, the terminal can receive multiple beams from the base station.
[0134] S402 Step: In the description of the present disclosure below, an operation (e.g., computation, selection, prediction, etc.) at a specific node (e.g., terminal, network, etc.) or a common operation (e.g., computation, selection, prediction, etc.) at multiple nodes (e.g., terminal, network, etc.) may correspond to a two-stage operation based on one or more functions in the functional framework of an AI / ML model, unless otherwise noted. For example, it may correspond to the training (i.e., creation and / or reconstruction) of the AI / ML model of FIG. 3 or to the inference of the AI / ML model. When a one-side model is used, an operation performed by a single node in the present disclosure may correspond to the operation, and when a two-side model is used, a common operation performed by multiple nodes in the present disclosure may correspond to the operation.
[0135] For example, in an AI / ML model-based BM, a base station can predict (infer) high-quality beam(s) based on an AI / ML model by using quality / intensity information for multiple beams received from a terminal as inference data. Additionally, a terminal can measure multiple beams received from a base station and predict (infer) high-quality beam(s) based on an AI / ML model by using the measurement results as inference data.
[0136] S403 Step: In the description of the present disclosure below, signaling (e.g., information / data / channel / signal, etc.) or a set of signaling between a specific node (e.g., terminal, network, etc.) and another node may be interpreted as the signaling or a set of signaling generated as a result of an operation based on an AI / ML model, even if not otherwise mentioned. For example, it may correspond to the output resulting from the inference of the AI / ML model of FIG. 3. If signaling between nodes is not required as a result of an operation based on an AI / ML model in the present disclosure, Step 3 may be omitted. If a one-side model is used in the present disclosure, unidirectional / bidirectional signaling (set) in the present disclosure may correspond to the signaling in Step 3. Additionally, if a two-side model is used in the present disclosure, unidirectional / bidirectional signaling in the present disclosure may correspond to the signaling, and repetitive signaling operations may also correspond to the signaling.
[0137] For example, in AI / ML model-based beam management, a base station may transmit beam(s) predicted based on an AI / ML model as candidates to a terminal so that the terminal can determine the optimal beam. Additionally, the terminal may report the beam(s) predicted based on an AI / ML model to the base station to request the base station to transmit candidate beams as candidates for determining the optimal beam.
[0138] FIG. 5 illustrates a procedure for transmitting system information for THz communication to which the present disclosure applies. Although this example is written with THz in mind, it is also applicable to 6G communication environments where THz is not applied. Furthermore, the procedure illustrated in FIG. 5 can be combined with various embodiments of the present disclosure described below. For example, the embodiments described below may be performed based on the system information obtained by the procedure illustrated in FIG. 5.
[0139] Referring to FIG. 5, in step 501, the base station (520) can transmit system information of cell #1 through cell #2. For example, the base station (520) provides at least two cells, where cell #1 uses a THz frequency band and cell #2 uses a frequency band other than the THz frequency band. Here, the system information may include at least one information / state / parameter / setting generated at the higher layer and the physical layer, respectively. For example, at least one information / state / parameter / setting generated at the higher layer may include at least one of SFN (System Frame Number), control information setting for SIB1 (System Information Block 1), information related to cell selection / entry, and subcarrier spacing, and at least one information / state / parameter / setting generated at the physical layer may include at least one of SFN, half frame indicator, and SSB index (Synchronization Signal / PBCH Block index; SSB index). However, this is merely an example, and system information may include information, status, parameters, and settings related to Cell #1 / Cell #2 generated at various types of physical layers / upper layers. To this end, as an example, Cell #1 and Cell #2 may have a secondary cell and primary cell relationship.
[0140] In step 503, the UE (510) can obtain synchronization for cell #1. Synchronization can be obtained by detecting a synchronization signal. Generally, synchronization is obtained prior to receiving system information, but since the system information for cell #1 is received in cell #2, synchronization for cell #1 can be obtained after receiving system information. For example, the UE (510) can obtain synchronization based on system information. However, unlike FIG. 5, synchronization may be obtained prior to step 501 according to other examples.
[0141] In step 505, the UE (510) may transmit a signal to connect to Cell #1. For example, the signal may include information for connecting to Cell #1 (e.g., a random access preamble). The structure of the signal and the resource for transmitting the signal (e.g., a channel) may be identified through system information. Subsequently, in step 507, the UE (510) and the base station (520) may perform a connection procedure to Cell #1 and perform communication. In this step, operations according to various embodiments described below may be performed.
[0142] For example, the procedure described with reference to FIG. 5 may be performed when the UE (501) first connects to cell #1 of the base station (520). Alternatively, a similar procedure may be performed when the UE (501) handovers to cell #1 of the base station (520). However, in the case of a handover, the system information of cell #1 may be received from a cell of a different base station other than cell #2 of the base station (520).
[0143] Communication in the THz band is expected to experience severe path loss, and to overcome this, terminals and base stations must use very sharp beams. The use of sharp beams means that terminals and base stations must perform beam control along with beamforming, and the number of beams used becomes very large. Therefore, it takes a very long time to align the transmit and receive beams between the base station and the terminal. In addition, if the beam alignment between the base station and the terminal is misaligned due to the movement or motion of the terminal, time is frequently required to realign the beams, which may result in an unstable link. Accordingly, a beam management procedure as shown in Fig. 6 below may be used.
[0144] FIG. 6 illustrates a beam management procedure applicable to the present disclosure.
[0145] FIG. 6 illustrates an example of a procedure for searching and / or selecting beams for THz communication, but is not limited to a THz environment, and the present disclosure is applicable in a 6G communication environment.
[0146] Additionally, the procedure illustrated in FIG. 6 may be combined with various embodiments of the present disclosure described below. Here, the beam may be interpreted as 'spatial (setting) information', 'spatial domain filter', 'spatial domain transmission filter', 'spatial domain reception filter', or / and a term having an equivalent technical meaning capable of distinguishing the beam (e.g., Reference signal, SSB (Synchronization Signal Block) Index, TRP (transmission reception point), panel, cell, TP (transmission point), base station, control resource-related information (e.g., CORESET (control resource set)-related information, etc.).
[0147] Referring to FIG. 6, in step 601, the base station (620) configures resources for beam management. Here, the resources may include at least one of time-frequency resources, channels, and spatial resources (e.g., antenna ports). For example, the base station (620) may utilize a beam search signal (BSS) that is transmitted spatially separated from the existing downlink signal / channel for beam search. Here, the BSS may be transmitted based on a dedicated port for beam search. The dedicated port may be a port different from the port for transmitting the existing downlink signal / channel (e.g., synchronization signal (e.g., SSB, etc.), data channel (e.g., PDSCH, etc.)). BSS is a term defined for convenience of explanation, and the technical concept according to the present embodiment is not limited to the term BSS itself. That is, a signal transmitted based on a dedicated port defined / configured for beam search may be included in the technical concept according to the present embodiment.
[0148] In step 603, the base station (620) may transmit measurement signals using multiple transmission beams. For example, the measurement signals may include at least one of a reference signal and a synchronization signal. At this time, the measurement signals may be transmitted as many times as the number of beams requiring measurement, and may be transmitted using a multi-beam transmission method that forms multiple beams simultaneously to reduce sweeping time. Here, multi-beam transmission may be performed based on at least one of a multi-panel, a sub-array, and a true time delay (TTD).
[0149] In step 605, the UE (610) can transmit a feedback signal to the base station (620). The feedback signal may indicate at least one beam selected by the UE (610). The UE (610) can select at least one preferred beam based on the measurement signals received in step 603. In step 607, the UE (610) and the base station (620) can communicate. At this time, the UE (610) and the base station (620) can communicate using the beam selected in step 605. If channel reciprocity is established, the transmission beam of the UE (610) can also be determined through steps 603 and 605, so the transmission operation of the UE (610) can also be performed using the beam selected in step 605. If channel mutuality is not established, a procedure including the transmission of measurement signals of the UE (610) and the transmission of feedback signals of the base station (620) may be performed first to determine the transmission beam of the UE (610). In step 607, operations according to various embodiments described below may be performed.
[0150] FIG. 7 shows an electromagnetic spectrum according to one embodiment of the present disclosure.
[0151] Referring to Fig. 7, the data transmission rate can be increased by expanding the bandwidth. This can be achieved by using sub-THz communication with a wide bandwidth and applying advanced large-scale MIMO technology. THz waves, also known as sub-millimeter radiation, generally represent a frequency band between 0.1 THz and 10 THz with corresponding wavelengths in the range of 0.03 mm to 3 mm.
[0152] For example, the 100 GHz–300 GHz band range (Sub-THZ band) can be considered the primary portion of the THz band for cellular communication. Adding the sub-THZ band to the mmWave band can increase 6G cellular communication capacity. Among the defined THz bands, the 300 GHz–3 THz band is located in the far-infrared frequency band. Although the 300 GHz–3 THz band is part of the broadband, it lies at the boundary of the broadband and immediately following the radio wave band. Therefore, this 300 GHz–3 THz band exhibits similarities to RF. Key characteristics of THz communication may include (i) widely available bandwidth to support very high data transfer rates, and (ii) high path loss occurring at high frequencies (making highly directional antennas indispensable). The narrow beam width generated by highly directional antennas can reduce interference. The small wavelength of THz signals allows a much larger number of antenna elements to be integrated into devices and base stations operating in this band. This enables the use of advanced adaptive array technology that can overcome range limitations.
[0153] At this time, transmitting system information (i.e., information related to the attributes, characteristics, and / or capabilities of the base station required to use the service, etc.) in the THz frequency band may be inefficient because, in the case of the high frequency band, beam sweeping must be performed more frequently to cover the entire area of the cell as the beam width becomes narrow. In particular, transmitting system information in this manner is even more inefficient when there are not many users in the cell. Accordingly, a system information transmission procedure as shown in FIG. 5 described above may be used.
[0154] Non-terrestrial networks (NTN) are described below.
[0155] For example, NTN may represent a network or network segment that utilizes RF (radio frequency) resources mounted on a satellite (or UAS (unmanned aerial system) platform). The use of NTN services may be considered to secure wider coverage or to provide wireless communication services in locations where the installation of wireless communication base stations is difficult. NTN services may collectively refer to wireless communication systems that provide services to terminals by installing base stations on satellites rather than on the ground (e.g., geostationary-orbit, low-Earth orbit, medium-geometry orbit satellites, etc.), airplanes, unmanned airships, drones, etc. The satellite described in this disclosure may move at high speed from a specific location on Earth, and the satellite beam directed toward Earth may correspond to an area on Earth where the satellite can provide services to users.
[0156] As an example of the present disclosure, NTN scenarios may be classified into Earth-fixed cell scenarios and Earth-moving cell scenarios depending on the type of cell supported by the satellite. An Earth-fixed cell scenario refers to a scenario in which a cell is maintained permanently within a specific position on the Earth's surface or for a specific service period based on the satellite's beam steering function. An Earth-moving cell scenario refers to a scenario in which a cell within the Earth's surface continues to move as it is serviced by a fixed beam without the satellite's beam steering function being utilized.
[0157] As another example of the present disclosure, NTN scenarios can be classified into a typical scenario based on a transparent payload and a typical scenario based on a regenerative payload, depending on the characteristics of the payload.
[0158] FIG. 8 illustrates an example of a general NTN scenario based on a transparent payload according to an embodiment of the present disclosure. The embodiment of FIG. 8 may be combined with various embodiments of the present disclosure.
[0159] Referring to FIG. 8, a satellite (or UAS platform) can establish a service link with a UE. The satellite (or UAS platform) can be connected to a gateway via a feeder link. The satellite can be connected to a data network via the gateway. A beam footprint may refer to an area where signals transmitted by the satellite can be received.
[0160] FIG. 9 illustrates an example of a general NTN scenario based on a regenerated payload according to an embodiment of the present disclosure. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure.
[0161] Referring to FIG. 9, a satellite (or UAS platform) can establish a service link with a UE. A satellite (or UAS platform) connected to a UE can be connected to another satellite (or UAS platform) via inter-satellite links (ISL). Another satellite (or UAS platform) can be connected to a gateway via a feeder link. Based on a replay payload, the satellite can be connected to a data network via another satellite and a gateway. If no ISL exists between the satellite and another satellite, a feeder link between the satellite and the gateway may be required.
[0162] FIGS. 8 and 9 are merely examples of NTN scenarios, and NTN can be implemented based on various scenarios. For example, a satellite (or UAS platform) can implement a regenerative (with on-board processing) payload. For example, a satellite (or UAS platform) can generate multiple beams across a designated service area depending on the field of view of the satellite (or UAS platform). For example, the field of view of the satellite (or UAS platform) may vary depending on the on-board antenna diagram and the minimum elevation angle. For example, a regenerative payload may include radio frequency filtering, frequency conversion, and amplification. Thus, the waveform signal repeated by the payload may not be altered. For example, a regenerative payload may include radio frequency filtering, frequency conversion and amplification, demodulation / decoding, switching and / or routing, and coding / modulation. For example, the playback payload can be substantially the same as carrying all or part of the base station functions on a satellite (or UAS platform).
[0163] The following describes procedures for maintaining network service continuity and satellite coverage in wireless communication systems utilizing NTN elements (e.g., initial cell selection, mobility management in idle mode, and mobility management in connected mode).
[0164] 1) Initial cell selection procedure
[0165] The terminal can search for the first satellite-based NTN cell (or the satellite broadcasting the cell) upon power turn-on. At this time, if the terminal possesses satellite orbit information (ephemeris data) and / or round-to-trip (RTT) information available for performing a cell entry procedure (e.g., random access procedure), the terminal can use such information to shorten the time required for the cell search procedure and cell search. To this end, the terminal may require (initial) system information containing satellite orbit (ephemeris) information to identify the precise location of the cell, and (initial) system information may be set / determined / generated based on orbital plane information already possessed by the terminal. For example, satellite-level orbit parameters for all satellites capable of providing services to the terminal via a terminal uSIM (universal subscriber identity module) containing a satellite ID or index may be provided to the terminal in advance. Subsequently, since the satellite ID of the service satellite is included in the system information and broadcast, the terminal can use this to derive the orbital data (ephemeris data) and / or the location coordinates of the service satellite associated with the service satellite stored in the uSIM. Additionally, to assist with mobility handling, the terminal can obtain information related to neighboring satellites through the system information and / or dedicated RRC (Radio Resource Control) signaling.
[0166] Here, satellite ephemeris information transmitted to the terminal via system information and / or RRC signaling may be implemented / supported in i) position and velocity state vector orbital format and ii) orbital parameter ephemeris format. For example, the position and velocity state vector orbital format may consist of 17 bytes or less (e.g., 132 bits). The field size for position (x, y, z)(m) may be 78 bits, and the field size for velocity (vx, vy, vz)(m / s) may be 54 bits.
[0167] The orbital parameter ephemeris format can be composed of 21 bytes or less (e.g., 164 bits).
[0168] Figure 10 illustrates the components of an orbital parameter orbital format.
[0169] In Fig. 10, each symbol may have the following meanings.
[0170] - Semi-major axis (half of the major axis of an elliptical satellite orbit) "α" [m] (e.g., 33 bits)
[0171] - Eccentricity "e" (in an elliptical satellite orbit, 0 <e<1)(예: 20 비트)
[0172] - Periapsis (refers to the angle from the orbital periapsis, the point where an object is closest to the center body as it orbits, to the ascending node; determines the direction of the ellipse in the orbital plane) " ω (e.g., 28 bits) [rad]
[0173] - Longitude of ascending node (the angle measured counterclockwise from a reference point (e.g., the vernal equinox in the solar system)) to the ascending node (the point where the orbit passes from below the reference plane upward) "Ω" (e.g., 28 bits)[rad]
[0174] - (Orbit) Inclination (refers to the degree of tilt of an ellipse relative to a reference plane, measured as the angle between the orbital plane and the reference plane at the ascending node) "i" (e.g., 27 bits)[rad]
[0175] - Mean anomaly (an angle that changes continuously over time; mathematically convenient but does not correspond to a geometric angle) "M0" = M(t0) at epoch t0 [JD] (e.g., 28 bits) [rad]
[0176] 1) Mobility management in idle mode
[0177] For example, during idle mode, the location of a terminal can be identified at the tracking area level / unit. Here, a tracking area is defined as a set of cells, and each cell may belong to a tracking area identified by a tracking area code (TAC). The TAC may be transmitted via system information on a broadcast channel. Multiple cells may belong to the same tracking area, and the same TAC corresponding to that same tracking area may be broadcast. The location of the terminal may be known to the network when the terminal's power is first turned on (i.e., when the registration procedure is performed). The registration request message transmitted by the terminal for the registration procedure may include the TAC of the cell the terminal is currently camped in. If the terminal changes cells as it moves, the tracking area of that cell can be determined by decoding the system information of the changed cell. The terminal may move within the same tracking area without performing updates. When a terminal enters a new cell using a different TAC, the terminal can register in the new cell and transmit a new TAC to update the network regarding its location. Accordingly, as the tracking area increases, signaling from the terminal to the network is reduced, thereby minimizing the terminal's power consumption.
[0178] For example, if the network needs to reach a terminal in idle mode (e.g., incoming call), the network may page the terminal from all cells within the last tracking area where the terminal registered. If the tracking area is very large and contains many cells, the number of pages may increase because the network pages the terminal from all cells within the TAC. If the same model is used in the satellite system and each satellite broadcasts the TAC, the tracking area may sweep across the ground as the satellite orbits the Earth. In this case, even a stationary terminal must perform registration updates frequently, which can affect terminal battery life and increase uplink signal strength. To address this, the system can be designed so that the tracking area does not change its geographical location on Earth. Instead of the tracking area shifting when the satellite moves, the satellite changes the tracking area as it enters a new geographical area, and the TAC broadcast by the satellite can be updated to reflect the corresponding new geographical area.
[0179] Simultaneously, if the terminal detects a new TAC on the broadcast channel, it may perform a tracking area update procedure. Accordingly, unless the physical location on Earth is changed, the tracking area of the terminal can be maintained in a fixed state.
[0180] 2) Mobility management in connected mode
[0181] While the terminal is in connected mode, mobility management procedures may be handled by handover. For terrestrial / NTN networks, a handover may be triggered by the network based on measurements reported by the terminal regarding the signal quality of the current cell and adjacent cells. Within the handover procedure, downtime is defined as the time from when the terminal stops transmitting and receiving with the source base station until when it resumes transmitting and receiving with the target base station.
[0182] Meanwhile, the interruption time may differ between the uplink and downlink. For the downlink, the interruption time can be defined as the time from when the network transmits a synchronized RRC reset message until the target base station receives the RRC Reconfiguration Complete message. The base station cannot send data after the time the RRC reset message is transmitted and can resume communication after receiving the RRC Reconfiguration Complete message. For the uplink, the terminal can potentially continue transmitting data to the source base station until the synchronized RRC reset message is received. The interruption time can be defined as the time from when the terminal receives the synchronized RRC reset message until the target base station receives the RRC Reconfiguration Complete message.
[0183] Since the propagation delay of satellite-based NTNs is much greater than that of ground systems, additional latency may occur for mobility signals, such as measurement reporting, receiving handover (HO) commands, and HO requests / acknowledgements (when the target cell originates from a different satellite). Geostationary Earth Orbit (GEO) scenarios are characterized by much greater propagation delays than low Earth Orbiting (LEO) scenarios, although the latter must account for satellite movement. To prevent extended service interruptions, latency associated with mobility signals must be addressed in both cases. In addition to the measurement-triggered handover described above, handover triggering based on the positions of the terminal and satellite (or the distance between the terminal and the satellite), handover triggering based on the timing advance (TA) of the target cell, handover triggering based on deterministic satellite movement / regional time, and handover triggering based on the elevation angle of the source / target cell may be utilized. Additionally or alternatively, the terminal may be provided in advance with handover settings and conditions that trigger the handover (e.g., the positions of the terminal and satellite, the strength of the signal transmitted by the terminal and satellite, etc.). For example, the terminal may receive handover settings and conditions that trigger the handover through information regarding the new cell that becomes the handover target. Accordingly, the terminal can monitor the handover conditions and, if the conditions are satisfied, perform a handover to the target cell.
[0184] Meanwhile, as described above, since wireless communication systems utilizing NTN elements have a very large Round-Trip Time (RTT) value compared to terrestrial communication systems, various types of offset and TA values can be set / defined / instructed / signaled for efficient time / frequency synchronization.
[0185] FIG. 11 illustrates an offset (e.g., K_offset and k_mac), TA value, validity duration, and epoch time for time / frequency synchronization in an NTN-based wireless communication system.
[0186] Referring to FIG. 11, each of the above values will be explained in detail.
[0187] i) K_offset and k_mac
[0188] K_offset disclosed in FIG. 11 is an offset value representing the RTT of the uplink time synchronization reference point (RP). Here, K_offset may correspond to the sum of the service link RTT and the common TA (if indicated). k_mac shown in FIG. 11 is an offset value representing the RTT between the RP (reference point) and the base station. For example, K_offset may be applied to i) the physical uplink shared channel (PUSCH) transmission timing scheduled by the DCI and the DCI, ii) the random access response (RAR) and the PUSCH transmission timing based on the RAR, iii) the PUSCH transmission timing based on a set grant, iv) the PUCCH transmission timing according to message B (MsgB), v) the non-periodic SRS (Sounding Reference Signal) / CSI resource transmission timing, etc. For example, k_mac can be applied to terminal actions and assumptions regarding downlink configurations directed by MAC-CE (Medium Access Control Element) commands in PDSCH. In the beam failure recovery procedure, for the transmission of PRACH in uplink slot n, the terminal can monitor the corresponding PDCCH starting from downlink slot "n+k_mac+4" within the corresponding RAR window.
[0189] For example, the cell-specific K_offset can be signaled via system information associated with the NTN. A value range for the cell-specific K_offset (0 to 1023 ms) covering all scenarios may be used. The differential terminal-specific K_offset can be signaled via MAC CE, and the corresponding differential terminal-specific value range is 0 to 63 ms. The total terminal-specific K_offset value is equal to the cell-specific K_offset value minus the differential terminal-specific K_offset value. k_mac can be provided from the network when downlink and uplink frame timings are not aligned at the base station. Updates to k_mac are not supported, and the value range may be 1 to 512 ms. If the terminal does not receive a k_mac value from the network, the terminal may assume k_mac to 0. The reference SCS value for the unit of K_offset in FR1 may be 15 kHz.
[0190] - Terminal-specific (UE-specific) TA and common TA
[0191] In an NTN-based communication system, a terminal can calculate a TA based on the terminal's GNSS (global navigation satellite system) capabilities (e.g., terminal location) and upper-layer parameters related to satellite orbits (ephemeris) transmitted from a base station, and this is designated as the terminal-specific TA. If upper-layer parameters related to satellite orbits are not received from the base station, the terminal-specific TA may be set to 0. Additionally, the TA calculated based on common TA parameters (e.g., TACommon, TACommonDrift, and / or TACommonDriftVariation), which are upper-layer parameters transmitted from the base station, is designated as the common TA. If common TA parameters are not transmitted from the base station, the common TA may be set to 0. Accordingly, in an NTN-based communication system, the total TA value can be calculated as N_TA + N_TA,offset + terminal-specific TA + common TA. Here, N_TA,offset means the TA offset value provided to the terminal per serving cell, and N_TA means the value derived based on the timing advance command.
[0192] FIG. 12 illustrates terminal-specific TA and common TA.
[0193] Referring to FIG. 12, the terminal-specific TA is calculated to compensate for transmission delays for the service link, and the common TA is calculated to compensate for transmission delays between the RP and the satellite.
[0194] - Valid interval and epoch time
[0195] Here, the effective period refers to the (maximum) time interval during which the terminal can apply previously acquired support information (from the epoch time) without acquiring new support information (e.g., serving and / or neighboring satellite orbits (ephemeris) and common TA parameters, etc.). Configuration information related to the effective period may be broadcast from the base station via system information related to NTN on a per-cell basis.
[0196] For example, the valid interval length range may be configured as {5s, 10s, 15s, 20s, 25s, 30s, 35s, 40s, 45s, 50s, 55s, 60s, 120s, 180s, 240s, 900s}, but is not limited thereto. A valid timer with a valid interval value set may (re)start at the epoch time of the support information. If new or additional support information is not available within the valid period, the terminal may assume that uplink synchronization has been lost.
[0197] For example, serving satellite orbits (ephemeris) and common TA parameters are signaled in the same System Information Block (SIB) message and may have the same epoch time. If the epoch time is explicitly provided via the SIB, the epoch time of the support information (satellite orbits (ephemeris) and common TA parameters) is the start time of the downlink (DL) subframe, indicated by the SFN, and the subframe number signaled along with the support information. If the epoch time is not explicitly indicated via the SIB, the epoch time of the support information may be implicitly known as the end of the system information window in which NTN-specific system information (e.g., SIB19) is transmitted. If the epoch time is provided via dedicated signaling, the epoch time of the support information is the start time of the DL subframe and may be indicated by the SFN and the subframe number.
[0198] For example, in the case of a serving cell, if the epoch time is explicitly indicated by the SFN and subframe number, the terminal may consider that frame as the next SFN after the frame in which the message indicating the epoch time was received, or the current SFN. In the case of a neighboring cell, if the epoch time is explicitly indicated by the SFN and subframe number, the terminal may consider that frame as the frame closest to the frame in which the message indicating the epoch time was received.
[0199] Integrated sensing and communication (ISAC) is described below.
[0200] Wireless sensing is a technology that utilizes radio frequencies to determine the instantaneous linear velocity, angle, and distance (range) of an object, thereby obtaining information about the characteristics of the environment and / or objects within that environment. Since radio frequency sensing capabilities do not require connecting to objects via devices within a network, they can provide services for determining object locations without the need for devices. The ability to obtain range, velocity, and angle information from radio frequency signals can provide a wide range of new functions, such as various object detection, object recognition (e.g., vehicles, humans, animals), high-precision localization, tracking, and activity recognition. Wireless sensing services can provide information to various industries, enabling applications such as intruder detection, assisted vehicle steering and navigation, trajectory tracking, collision avoidance, traffic management, and health and traffic management. In some cases, wireless sensing may utilize non-3GPP type sensors (e.g., radar, cameras) to further support 3GPP-based sensing. For example, the operation of a wireless sensing service (sensing operation) may rely on the transmission, reflection, and scattering processing of wireless sensing signals. Therefore, wireless sensing can provide an opportunity to enhance existing communication systems from communication networks to wireless communication and sensing networks.
[0201] FIGS. 13 and 14 illustrate an example of a sensing operation according to an embodiment of the present disclosure. The embodiment of FIGS. 13 and 14 may be combined with various embodiments of the present disclosure.
[0202] Specifically, FIG. 13 shows an example of sensing using a sensing receiver and a sensing transmitter at the same location (e.g., monostatic sensing), and FIG. 14 shows an example of sensing using a separated sensing receiver and a sensing transmitter (e.g., bistatic sensing).
[0203] For example, in a wireless communication system based on a 6G network of the present disclosure, referring to FIG. 13, the sensing transmitter and the sensing receiver may be configured to be included in a single base station or a single terminal. Alternatively, referring to FIG. 14, the sensing transmitter and the sensing receiver may be configured to be included in different base stations, in different terminals, or in a terminal and a base station, respectively.
[0204] In this regard, based on whether the sensing transmitter and the sensing receiver are each included in a base station or a terminal, the following six types of sensing modes can be defined.
[0205] - Mode 1: A mode in which the sensing transmitter and sensing receiver are contained within a single base station (e.g., base station-based sensing mode in monostatic mode)
[0206] - Second mode: A mode in which the sensing transmitter is included in the first base station and the sensing receiver is included in a second base station different from the first base station (e.g., base station-based sensing mode in bistatic mode)
[0207] - Third mode: A mode in which the sensing transmitter is included in the base station and the sensing receiver is included in the terminal (e.g., base station-terminal sensing mode)
[0208] - 4th Mode: A mode in which the sensing transmitter is included in the terminal and the sensing receiver is included in the base station (e.g., terminal-base station sensing mode)
[0209] - 5th Mode: A mode in which the sensing transmitter and the sensing receiver are contained in a single terminal (e.g., terminal-based sensing mode in monostatic mode)
[0210] - 6th mode: A mode in which the sensing transmitter is included in the first terminal and the sensing receiver is included in a second terminal different from the first terminal (e.g., terminal-based sensing mode in bistatic mode)
[0211] In a wireless communication system based on a 6G network of the present disclosure, one or more of the six types of sensing modes described above may be utilized independently or in combination.
[0212] In relation to the above sensing operation, a sensing transmitter may transmit a sensing signal for sensing one or more objects (and / or the environment surrounding the objects). For example, the sensing signal may correspond to a radio (frequency) signal defined to be transmittable by a base station / terminal in a wireless communication system based on the 6G network of the present disclosure. A sensing receiver may receive a signal that is scattered / reflected by one or more objects (and / or the environment surrounding the objects) from the sensing signal transmitted from the sensing transmitter. In the sensing receiver, sensing data may be derived from the scattered / reflected signal, and sensing results may be generated / obtained through processing of the sensing data. Here, the sensing result may include characteristic information (e.g., location, distance, speed, angle, etc.) about one or more objects (and / or the environment surrounding the objects). The sensing result thus generated / acquired may be utilized for wireless sensing services (e.g., detection, tracking, etc. of objects and / or environments) provided by a wireless communication system based on the 6G network of the present disclosure, or may be provided / disclosed to a trusted third party.
[0213] Additionally, although the sensing operation in FIG. 9 is described using a representative example of operation in a wireless communication system based on a 6G network, it can be extended and applied to cases where terminals / base stations / signals based on networks of conventional generations (e.g., 4G, 5G, etc.) are utilized.
[0214] Additionally, in relation to the wireless sensing described in the present disclosure, in a wireless communication system based on a 6G network of the present disclosure, time / frequency resources for sensing operations and time / frequency resources for general communication (e.g., UL / DL / sidelink-based communication, etc.) may be scheduled / configured separately.
[0215] FIG. 15 illustrates a time / frequency resource for a sensing operation according to one embodiment of the present disclosure. The embodiment of FIG. 15 may be combined with various embodiments of the present disclosure.
[0216] Referring to FIG. 15, the time / frequency resources (hereinafter, sensing resources) for the aforementioned sensing operation (e.g., sensing operation based on FIG. 9) can be set / assigned separately from the time / frequency resources (hereinafter, communication resources) for general communication.
[0217] For example, sensing resources may be configured / assigned in units of symbols in the time domain and / or in units of resource blocks in the frequency domain. Resources other than those configured / assigned to the sensing resources may be utilized as resources for general communication. That is, sensing resources and communication resources may be configured / assigned based on time-division multiplexing (TDM) and / or frequency-division multiplexing (FDM) methods in terms of base station / terminal operation. Additionally, or alternatively, sensing resources may be configured / assigned based on other units in the time domain (e.g., slot, frame, absolute time (ms, us), etc.) and / or other units in the frequency domain (e.g., subcarrier, carrier, absolute frequency (MHz, GHz), etc.).
[0218] For example, in relation to the setting / allocation / scheduling of resources for general communication described in this disclosure, it may be necessary to consider the relationship between said resources and the aforementioned sensing resources. For example, when setting / allocating resources for general communication according to an embodiment of this disclosure, said resources may be set / allocated to rate-match or puncturing resource areas corresponding to the sensing resources. For example, when scheduling resources for general communication according to an embodiment of this disclosure, said resources may be scheduled so as not to overlap with resource areas corresponding to the sensing resources. If resources for general communication and resource areas corresponding to the sensing resources according to an embodiment of this disclosure are set / allocated / scheduled to overlap, either one or both operations may be dropped, skipped, or postponed based on priority, predefined rules, etc. That is, in an embodiment of the present disclosure, resources related to general communication can be configured / assigned / scheduled so as not to overlap with the aforementioned sensing resources.
[0219] Additionally, various channel modeling methods may be applied in relation to the wireless sensing described in this disclosure. Channel modeling related to sensing may mean constructing a path for transmitting and receiving sensing signals and / or scattered / reflected signals by considering the object to be sensed and / or the environment to which the object belongs. Since channel modeling may be related to the performance / requirements of sensing in a wireless communication system, it may be an important matter for verifying the validity of the sensing function.
[0220] Channels related to sensing can be classified into channels between an object (e.g., target of interest) and a sensing transmitter / receiver, and channels between the environment to which the object belongs and a sensing transmitter / receiver. In this regard, channel modeling related to sensing can be classified based on the sensing mode (e.g., the six types of modes mentioned above), whether it is an object or an environment, and / or sensing scenarios. For example, channel modeling for a target in a base station / terminal-based monostatic sensing mode, channel modeling for a target in a base station / terminal-based bistatic sensing mode, channel modeling for an environment in a base station / terminal-based monostatic sensing mode, and channel modeling for an environment in a base station / terminal-based bistatic sensing mode can be configured with different optimizations. For example, when various sensing scenarios are classified, they can be classified into channel modeling for detection location and tracking scenarios, channel modeling for motion recognition, and channel modeling for imaging / environment reconstruction scenarios. Additionally, channel modeling related to sensing may be based on statistical channel modeling techniques and / or deterministic channel modeling techniques. For example, modeling for sensing in a wireless communication system based on a 6G network of the present disclosure may be based on stochastic geometry channel modeling techniques and / or hybrid with ray tracing channel modeling techniques. Here, the stochastic geometry channel model may be based on various statistical characteristics of the channel state. Furthermore, the hybrid channel model may be based on both ray tracing techniques and stochastic techniques.In the case of a hybrid approach, channels for objects requiring high accuracy and consistency (e.g., targets of interest) can be modeled using ray tracing techniques, while channels for the environment can be modeled using probabilistic techniques.
[0221] FIG. 16 illustrates a procedure related to a sensing operation according to one embodiment of the present disclosure. The embodiment of FIG. 16 may be combined with various embodiments of the present disclosure.
[0222] For example, in a wireless communication system based on a 6G network of the present disclosure, in the case of a sensing operation in which a terminal participates, the base station may need to verify the terminal's capability regarding said sensing operation (S161). In this regard, the terminal may be configured to report capability information to the base station regarding whether it supports the sensing operation. Additionally, or alternatively, if the terminal is defined in advance in the specification as supporting the sensing operation, the procedure may be omitted. Furthermore, in the case of a sensing operation in which only the base station participates, the base station may be configured to report capability information regarding whether it supports the sensing operation to the entity setting / controlling its sensing operation (e.g., a network entity at the upper layer / level of the base station).
[0223] For example, a base station may perform signaling with a terminal to exchange configuration information related to a sensing operation (S162). For example, the base station may set / instruct the terminal information regarding the mode of the sensing operation, the subject of the sensing operation (e.g., a sensing transmitter, a sensing receiver), the resources for the sensing operation, the target of utilization of the sensing results (e.g., a type of wireless sensing service based on a 6G network, a trusted third party), and channel modeling for sensing (e.g., a channel between the base station / terminal and an object / environment). For example, the base station may receive such information from a network entity at a higher level / layer of the base station.
[0224] For example, the base station and / or terminal may perform a sensing operation on the information set / instructed (S163). For example, the base station and / or terminal may perform procedures such as transmitting a sensing signal, receiving scattered / reflected signals, deriving sensing data, obtaining a sensing result through processing the sensing data, and providing the sensing result, in the role of a sensing transmitter and / or sensing receiver. As an example, in the operation of the base station / terminal described in this disclosure, the sensing result provided through the sensing operation may be utilized.
[0225] The following describes Network Energy Saving technologies. Energy saving in base stations is considered important in wireless communication systems, including 3GPP, because it contributes to building eco-friendly networks by reducing carbon emissions and lowering the operational expenditure (OPEX) of telecommunications operators. In particular, as the introduction of 5G communication requires high transmission rates, base stations must be equipped with a larger number of antennas and provide services through wider bandwidths and frequency bands. Accordingly, 5G systems are adopting various technologies to reduce energy consumption under the name NES (Network Energy Savings), and related technologies are continuously being standardized.
[0226] For example, in an inter-band carrier aggregation environment for cells placed in the same location and frequency range 1, the terminal can measure a synchronization signal block transmitted from the main cell or another auxiliary cell for time / frequency synchronization of the auxiliary cell and first layer / third layer measurement, and based on this, auxiliary cell operation without a synchronization signal block can be supported.
[0227] In addition, alignment between cell discontinuous transmission / discontinuous reception and terminal discontinuous reception, and exchange of information between nodes regarding cell discontinuous transmission / discontinuous reception can be supported in RRC connection mode. Furthermore, channel state information, beam management, measurement, reporting, and related signaling procedures can be enhanced for the efficient adaptation of spatial elements and power offset values.
[0228] In addition, prevention of camping by conventional terminals in cells to which network energy saving technology is applied, improvement of conditional handover procedures in network energy saving mode, beam activation between nodes, paging restriction in limited areas, and corresponding wireless resource management / radio frequency requirements can be supported together.
[0229] For example, depending on the application of NES technology, the base station can perform operations such as controlling on / off for a certain duration in the time axis, controlling transmit / receive resources for UE-common or UE-specific signals / channels, changing the amount of resources in the frequency axis, controlling transmission power, or turning on / off antenna ports, TRPs (transmission-reception points), etc. in the spatial domain.
[0230] Figure 17 illustrates the operation procedure of a base station supporting NES technology.
[0231] Referring to FIG. 17, for example, a base station can identify an NES solution to be applied (S171). The NES solution may be related to the control of signal transmission and reception (e.g., on / off), beam operation, handover procedures, channel measurement and reporting, etc. Which NES solution to apply may be adaptively selected based on the current situation (e.g., cell load level, characteristics of connected terminals, etc.) or may be predefined.
[0232] For example, a base station that has identified an NES solution can perform signaling for the NES (S172). The specific signaling procedure may vary depending on the identified NES solution. For example, the base station may transmit common information regarding the NES solution, transmit configuration information necessary for NES operation to at least one terminal, or transmit control information regarding the progress of NES operation to at least one terminal. Additionally, the base station may receive capability information related to the NES from at least one terminal.
[0233] Subsequently, for example, the base station can perform operations for NES (S173). At this time, the base station can perform operations for NES based on the signaling performed earlier. That is, depending on the system information, configuration information, and control information transmitted through the signaling, the base station can turn on / off the transmission and reception of a specific signal, turn on / off elements of the spatial domain, or adjust resources for the transmission and reception of a measurement signal.
[0234] NES technology can be performed through a procedure as shown in Fig. 17. Examples of NES solutions that can be performed by a procedure as shown in Fig. 17 are as follows.
[0235] 1) Intra-system energy saving solution: A RAN node may request a neighboring RAN node to switch at least one SSB beam into its inactive cell, or perform paging using a limited set of beams to an inactive terminal (e.g., a stationary terminal).
[0236] 2) Inter-system energy saving solution: An NG-RAN (Next Generation-Radio Access Network) node owning a capacity booster cell can autonomously switch the cell to an inactive state.
[0237] 3) SSB-less secondary cell solution: If no SSB or SMTC (SSB-based RRM measurement timing configuration) setting is provided for the secondary cell, the terminal can obtain timing references and AGC (Automatic Gain Control) sources from other serving cells. In FR1 or FR2, the base station can set up intra-band CA or inter-band CA including the secondary cell without SSB transmission, in which case SSB / SIB transmission can be triggered by the terminal's WUS (wake-up signal). Accordingly, as the period of common channels / signals such as SSB increases, the base station can remain in a sleep state for a longer time.
[0238] 4) Cell DTX / DRX (Discontinuous Transmission / Discontinuous Reception) Solution: To reduce the downlink transmission / uplink reception activity time of a base station, periodic cell DTX / DRX patterns (e.g., active and inactive periods) may be set commonly for terminals within a cell having the corresponding feature. Here, the cell DTX pattern and the cell DRX pattern may be set and activated separately, and up to two cell DTX / DRX patterns may be set per MAC entity. When cell DTX is set and activated, at least one of monitoring for SPS (Semi-Persistent Scheduling) opportunities or monitoring for PDCCH may be suspended during the cell DTX inactive period. When cell DRX is set and activated, at least one of transmission from CG (Configured Grant) resources or SR (Scheduling Request) transmission may be suspended during the cell DRX inactive period. Cell DTX / DRX can be enabled / disabled via RRC signaling or L1 group common signaling.
[0239] For example, parameters such as active duration and cycle may be set for the cell DTX / DRX. The active duration is the period during which the terminal waits to receive a PDCCH or SPS opportunity and transmit an SR or CG, and the cycle specifies the periodic repetition of the active duration and the inactive duration. When both the cell DTX and cell DRX are set, parameters such as the active duration and cycle are common. If the base station recognizes an emergency call or public safety-related service (e.g., MPS or MCS), the network may release or disable the cell DTX / DRX settings so as not to affect the service. Additionally, at least some overlap is required between the active duration of the terminal's connected mode DRX and the active duration of the cell DTX / DRX. For example, the period of the terminal's connected mode DRX may be a multiple of the cell DTX / DRX period, or vice versa.
[0240] 5) Conditional Handover (CHO) Solution: A CHO procedure is performed in such a way that the execution of a handover is determined by the terminal, and is used while NES technology is applied (e.g., when a cell enables or disables cell DTX / DRX). In this case, the terminal may use an NES-specific CHO event to execute a CHO for a candidate cell, and as an additional triggering condition for this, the reception of a DCI that enables CHO condition(s) set as an NES event indication may be applied.
[0241] 6) Spatial and power domain adaptation solution: To support the base station for transceiver muting and / or transmission power adaptation, the terminal may be configured to report multiple CSI entries in the CSI report based on multiple sub-configurations. Each sub-configuration corresponds to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset between the data channel (e.g., PDSCH) and CSI-RS. Depending on the application of the spatial and power domain adaptation solution, CSI configuration, measurement, and / or reporting operations may be affected.
[0242] Figure 18 illustrates a procedure for cell DTX / DRX operation.
[0243] Referring to FIG. 18, a base station DTX / DRX is proposed for NES purposes to operate the base station in sleep mode for a relatively long time without frequent wake-up. By setting the cell DTX and setting the on-duration of the terminals' C-DRX within the active period of the cell DTX, the base station can reduce energy consumption by using DTX transmission in low system load conditions.
[0244] For example, the base station may transmit system information to the terminal (S181). The terminal may check information related to cell DTX / DRX (S182). For example, the system information may include a Master Information Block (MIB), SIB1, etc. In relation to NES technology, the MIB may include information related to cell barring (e.g., cellBarred), and SIB1 may include information related to the cell barring status (e.g., cellBarredNES). Specifically, if cellBarred included in the MIB is set to a value indicating that it is not barred (e.g., notBarred), the terminal may determine that the cell is not barred, regardless of whether it supports NES cell DTX / DRX.
[0245] Conversely, if cellBarred included in the received MIB is set to a value indicating that the cell is blocked (e.g., barred), a terminal that does not support NES cell DTX / DRX can determine that the cell is blocked. However, if the terminal has the capability to support NES cell DTX / DRX, the terminal checks SIB1 to determine the cell blocking status. If cellBarred in the MIB is set to barred and cellBarredNES is absent in SIB1, a terminal that supports NES cell DTX / DRX can treat the cell as blocked and perform cell-reselection to another cell. On the other hand, if cellBarred in the MIB is set to barred and cellBarredNES is included in SIB1, a terminal that supports NES cell DTX / DRX can determine that the cell is not blocked.
[0246] For example, it is assumed that the terminal has the capability to support NES cell DTX / DRX, and that cellBarred in the MIB is set to notBarred or cellBarred in the MIB is set to barred, and cellBarredNES is included in SIB1. Accordingly, the terminal can perform a random access procedure to connect to the base station (S183) and then perform communication. At this time, the base station performs a cell DTX / DRX operation and transmits configuration information related to the cell DTX / DRX operation to the terminal (S184). The configuration information related to the cell DTX / DRX operation (e.g., CellDTXDRX-Config) includes at least one parameter related to the cell DTX / DRX, and may include, for example, at least one of an on-duration timer, a cycle start offset, a slot offset, a configuration type (e.g., DTX, DRX, or DTX-DRX), and an activation state of the DTX / DRX (e.g., active, inactive). In addition, the configuration information may further include information for receiving and interpreting control information related to cell DRX / DRX (e.g., DCI-related information).
[0247] Subsequently, the base station transmits control information related to cell DTX / DRX to the terminal (S185). The control information related to cell DTX / DRX may include DCI having a specified format (e.g., format 2_9). When an operation for a serving cell according to at least one of cell DTX operation and cell DRX operation is set by configuration information (e.g., cellDTXDRX-Config), the terminal can identify a set of search spaces (e.g., Type3-PDCCH CSS set) for monitoring PDCCH that transmits control information of the specified format during the active time through an upper layer parameter (e.g., SearchSpace), and obtain the location of information about the serving cell within the control information through an upper layer parameter (e.g., positionInDCI-cellDTRX). Then, the terminal can obtain the control information based on the identified set of search spaces and location.
[0248] For example, control information related to cell DTX / DRX may be used to indicate the activation or deactivation of cell DTX and / or cell DRX, and / or to provide an NES-mode indicator, and may include, for example, at least one block including a cell DTX / DRX indicator and an NES-mode indicator. In this case, if the serving cell is set as a supplementary uplink (SUL) carrier, the instruction to activate or deactivate cell DRX by the cell DTX / DRX indicator may be applied to both the UL carrier and the supplementary uplink carrier.
[0249] Subsequently, the terminal and the base station can communicate based on the cell DTX / DRX (S186). Specifically, the base station can turn on / off the transmission and reception of signals according to the settings related to the cell DTX / DRX, and accordingly, the terminal can selectively monitor signals from the base station. During DTX-OFF, the base station enters sleep mode to reduce energy consumption. At this time, the base station DTX cycle can be aligned with the terminal DRX cycle. The base station DTX-ON can completely cover the terminal's DRX-ON. Furthermore, for NES purposes, the base station can align the transmission of Xn (interface between nodes) / NG (interface between the base station and the core network) with the transmission of Uu (interface between the base station and the terminal). The DTX / DRX mechanism triggers the switching of reference signal resource set groups, and the base station may perform dormancy-like behavior by transmitting SSB, SIB, and CSI-RS sparingly or not transmitting them at all to reduce energy consumption. Depending on the base station's configuration, the terminal may receive downlink signals / channels sparingly or not receive them at all. Once the base station DTX / DRX operation is triggered, during the DTX / DRX OFF period, the terminal may receive the corresponding CSI-RS, SSB, or PDCCH discontinuously.
[0250] Figure 19 illustrates a procedure for CA operation using a secondary cell without an SSB.
[0251] Referring to FIG. 19, the base station transmits configuration information for a secondary cell to the terminal (S191). For example, the base station transmits configuration information for CA to provide a service to the terminal through a CA operation. Here, the CA operation may be an intra-band CA or an inter-band CA. For example, the configuration information for a secondary cell may include information for adding a secondary cell, and specifically, may include a cell index, a physical cell identifier, information related to DL and UL (uplink) settings, information related to bandwidth, information related to cell DTX / DRX, information related to downlink frequency (e.g., FrequencyInfoDL), etc.
[0252] Subsequently, the terminal determines the settings for CA operation (S193) and can perform communication using the base station's primary cell and secondary cell. To this end, the terminal can verify that the secondary cell is an SSB-less secondary cell based on information related to the downlink frequency included in the setting information, and can verify the relevant parameters (S192). For example, the terminal can determine that the secondary cell is an SSB-less secondary cell by confirming the existence of a parameter indicating that it is an SSB-less secondary cell (e.g., SSBlessSCell), and can verify the timing reference and AGC source for the secondary cell based on information regarding the reference cell (e.g., referenceCell). For example, the reference cell may be the primary cell. Therefore, the terminal can use the primary cell as the timing reference and AGC source for communication in the secondary cell. Subsequently, the primary cell and the secondary cell can perform communication with the terminal (S194 and S195).
[0253] FIG. 20 illustrates a Conditional HandOver (CHO) procedure. The order of the actions illustrated in FIG. 20 may vary depending on the case.
[0254] Referring to FIG. 20, the base station transmits configuration information for the CHO to the terminal (S201). The configuration information for the CHO may include information related to conditional reconfiguration (e.g., ConditionalReconfiguration, CondReconfigToAddModList) and information related to the configuration for reporting (e.g., ReportConfigNR). Here, the information related to the configuration for reporting may include information related to events related to reporting, identifiers of events (e.g., condEventId), information indicating whether it is an NES-specific CHO event (e.g., nesEvent), etc. For example, event information indicating that it is an NES-specific CHO event is received.
[0255] The base station transmits information enabling an NES-specific CHO execution condition to the terminal (S202). The information enabling an NES-specific CHO execution condition may be transmitted via control information of a specified format (e.g., DCI format 2_9). The information enabling an NES-specific CHO execution condition may be referred to as an NES-mode indicator, and, for example, as 1-bit information, an associated upper layer parameter (e.g., nesEvent) is set, and if the serving cell of the associated block in the corresponding DCI is the primary cell, it indicates that an NES-specific CHO execution condition is enabled.
[0256] Subsequently, the terminal performs a measurement (S203) and transmits the measurement report to the base station (S204). The base station determines the CHO based on the measurement report (S205) and performs signaling for a handover request with adjacent base stations indicated by the measurement report (S206). The base station determines the adjacent base stations that have affirmed admission through signaling as candidate base stations and transmits information about the candidate base stations to the terminal (S207). Accordingly, the terminal evaluates the CHO execution conditions for the candidate base stations (S208). Accordingly, when a candidate cell satisfying the conditions is determined, the terminal detaches from the old cell and synchronizes with the new cell (S209). At this time, since the terminal previously received event information indicating that it is an NES-specific CHO event and also received information activating the NES-specific CHO execution conditions, it can determine whether the event is satisfied. In other words, when an NES-mode indicator is received through a lower layer and conditional triggering configuration information (e.g., condTriggerConfig) includes information indicating that it is an NES-specific CHO event (e.g., nesEvent), the terminal determines that an event associated with a corresponding measurement identifier (e.g., measId) is satisfied, and accordingly, can determine that the CHO execution condition is satisfied.
[0257] Figure 21 illustrates a procedure for measuring and reporting CSI.
[0258] Referring to FIG. 21, the base station transmits configuration information for CSI to the terminal (S211). The configuration information for CSI may include information related to CSI-RS resources or resource sets (e.g., time-frequency resource information, sequence information, power information, etc.), information related to CSI reporting (e.g., quantity information, report type information, report resource information, codebook information, etc.), and information related to CSI measurement.
[0259] Here, to assist the base station with base station transceiver muting and / or transmit power adaptation, the terminal may be configured to report multiple CSI entries in the CSI report based on multiple sub-configurations.
[0260] Here, each sub-configuration corresponds to a spatial domain adaptation pattern (e.g., a subset of available spatial elements) and / or a power offset. Additionally, regarding CSI reporting, a higher-level parameter included in the configuration information (e.g., CSI-ReportConfig) may include a list of sub-configurations, each sub-configuration being identified by an identifier (e.g., csi-ReportSubConfigID) and may correspond to a list of at least one CSI-RS (Channel State Information-Reference Signal) resource, a CSI-RS antenna port subset, and / or, a power offset for a PDSCH related to the CSI-RS in addition to a parameter related to the power control offset of the CSI-RS resource(s) (e.g., powerControlOffset).
[0261] In this case, the configuration related to CSI may include multiple sub-configurations. Accordingly, when interpreting configuration information for CSI, the terminal can determine CSI-RS resources, CSI-RS port mapping, power offset, codebook type, report items, etc. by considering the sub-configurations. When the terminal is configured with configuration information related to CSI reporting that includes sub-configurations (e.g., CSI-ReportConfig), the terminal does not expect the upper-level parameter related to the report item (e.g., reportQuantity) to be set to 'cri-RSRP', 'cri-SINR', 'cri-SINR-Index', 'cri-RSRP-Index', 'none', 'ssb-Index-RSRP', 'ssb-Index-SINR', 'ssb-Index-RSRP-Index', 'ssb-Index-SINR-Index', or 'tdcp'. Additionally, if the CSI reporting type is set to semi-persistent CSI reporting or aperioditic CSI reporting, the base station may activate / trigger only some of the sub-settings configured for the terminal via MAC-CE or DCI. That is, the trigger state for aperioditic CSI reporting can be set as needed, and the activation of semi-persistent CSI reporting can be controlled by an activation command.
[0262] For example, regarding the configuration of a report item, the terminal can determine the CSI-RS port index for each CSI-RS resource based on information related to a port-subset for each sub-configuration (hereinafter referred to as the 'port-subset indicator'). The port-subset indicator may include a bitmap for specifying some of the antenna ports for the corresponding CSI-RS resource. Accordingly, the terminal can identify at least one antenna port for the corresponding sub-configuration based on the positions of bits set to a positive value (e.g., 1) in the port-subset indicator.
[0263] For example, regarding the settings for a report item, the terminal can determine the codebook type based on the existence of sub-settings. Specifically, if sub-settings are configured for a CSI report, the terminal may exclude the configuration of at least one codebook type. However, depending on the capabilities of the terminal, it is possible to configure the said at least one codebook type.
[0264] For example, regarding the settings for a report item, a power offset value and an NZP (Non-Zero Power) CSI-RS resource set may be set for each sub-setting. In this case, the interpretation of the NZP CSI-RS resource set for each sub-setting may vary depending on whether the power offset value and the NZP CSI-RS resource set are set for each sub-setting.
[0265] In determining the Channel Quality Indicator (CQI), a higher-level parameter related to the time limit for channel measurements (e.g., timeRestrictionForChannelMeasurements) may be set. In this case, the terminal must derive a channel estimate to determine the CSI based on the most recent CSI reference resource. At this time, if Cell DTX is enabled for the base station, the Cell DTX activation time may be taken into account.
[0266] For example, the CSI is derived based on the CSI reference resource. The CSI reference resource is defined as a group of downlink physical resource blocks corresponding to the bands related to the CSI derived in the frequency domain, and is defined as a single downlink slot determined in the time domain based on upper-layer parameters and subcarrier spacing. After receiving the CSI-RS, the terminal must transmit the CSI report no later than the CSI reference resource. In this case, if sub-configurations are set for the CSI report, the CSI reference resource is considered for each sub-configuration.
[0267] For example, when configured to report at least one of the CQI index, PMI (Precoding Matrix Indicator), and RI (Rank Indicator), in a CSI reference resource, the terminal may assume specific values for the symbol position and number occupied in control signaling, the number of PDSCH (physical downlink shared channel) and DMRS (Demodulation Reference Signal) symbols, the subcarrier spacing of the BWP (Bandwidth Part), the bandwidth for CQI reporting, the CP (Cyclic Prefix) length and subcarrier spacing of the reference resource, and the RV (redundancy version), for the purpose of deriving at least one of the CQI index, PMI, and RI. In this case, when sub-settings are configured for CSI reporting, assumptions regarding the antenna port, EPRE (Energy Per Resource Element), etc., may be determined based on the sub-settings.
[0268] Subsequently, the base station transmits at least one CSI-RS (S212). Accordingly, the terminal can receive at least one CSI-RS and perform a measurement. At least one CSI-RS may be transmitted through a CSI-RS resource or resource set configured by the configuration information.
[0269] In this case, if the terminal is configured as a DRX, the terminal may perform measurements as follows. For example, if the terminal is configured to monitor power saving-related control information (e.g., DCI format 2_6) and, in a situation where the DRX-related timer (e.g., drx-onDurationTimer) is not started by the upper-level parameter (e.g., ps-TransmitOtherPeriodicCSI), and is configured to report CSI using a reporting configuration type set to periodic reporting and a reporting item set to an item other than cri-RSRP and ssb-index-RSRP, the most recent CSI measurement opportunity occurs during the time indicated by drx-onDurationTimer in the DRX-related configuration information (e.g., DRX-Config), in addition to the DRX active time or the DRX active time for the CSI to be reported. As another example, if the terminal is configured to monitor power saving-related control information (e.g., DCI Format 2_6) and, under conditions where drx-onDurationTimer is not initiated by a higher-level parameter (e.g., ps-TransmitPeriodicL1-RSRP), is configured to report L1-RSRP using a report setting type set to periodic reporting and a report item set to cri-RSRP, the most recent CSI measurement opportunity occurs during the time indicated by drx-onDurationTimer within the DRX-related setting information (e.g., DRX-Config), excluding the DRX active time or the DRX active time for the CSI to be reported. Additionally, the most recent CSI measurement opportunity occurs within the DRX active time for the CSI to be reported.
[0270] Meanwhile, the base station may perform cell DTX / DRX operations. In this case, during the non-active period of the cell DTX, the terminal configured as the cell DTX is not expected to receive periodic CSI-RS and semi-static CSI-RS configured in the CSI reporting configuration associated with a reporting item including at least an RI (rank indicator). When the cell DTX is activated for a serving cell, the most recent CSI measurement opportunity of the semi-static CSI-RS resource or periodic CSI-RS resource occurs within the active periods of the cell DTX for CSI reporting, configured by the configuration information related to CSI reporting associated with at least an RI (e.g., CSI-ReportConfig).
[0271] A terminal that has received at least one CSI-RS determines the CSI (S213). For example, the terminal performs a CSI calculation. At this time, the terminal may perform the CSI calculation based on CSI processing criteria. The terminal may indicate the number of supported concurrent CSI calculations, i.e., the number of concurrently run CSI processing units (CPUs), NCPU. The terminal may determine the number of CPUs for the corresponding CSI report based on at least one of the NCPU, the number of CPUs for each CSI report, the number of CPUs currently occupied, and the settings of the report item. For example, for configuration information related to a CSI report (e.g., CSI-ReportConfig) that includes a report item parameter (e.g., reportQuantity) not set to 'none', the CPU(s) may be occupied for at least one OFDM symbol, where the number of at least one symbol may be determined based on the CSI-RS resource or CSI-IM resource associated with the sub-settings.
[0272] For example, if configuration information related to CSI reporting (e.g., CSI-ReportConfig) includes multiple sub-configurations, the number of CPUs occupied by CSI reporting is determined based on the number of CSI-RS resources corresponding to the sub-configurations. In this case, the number of CSI-RS resources may be determined based on the number of times it is referred by the configuration information related to CSI reporting (e.g., CSI-ReportConfig) or the number of sub-configurations that refer to the said CSI-RS resources.
[0273] For example, the terminal that has determined the CSI transmits the CSI report to the base station (S214). The terminal may transmit CSI(s) for at least one sub-configuration according to the report item parameter (e.g., reportQuantity) set for the configuration information related to the CSI report (e.g., CSI-ReportConfig). For example, the CSI report may include at least one of PMI, CQI, RI, CRI, SSBRI, LI, and RSRP. In this case, the CSI report may include a Part 1 CSI report and a Part 2 CSI report. Additionally, the CSI report may be transmitted via at least one of PUCCH or PUSCH.
[0274] For example, when a terminal multiplexes CSI reports containing Part 2 CSI reports to a PUCCH (physical uplink control channel) resource, the terminal determines the number of PRBs (physical resource blocks) for the PUCCH resource and the number of Part 2 CSI reports, assuming that each CSI report or each CSI sub-report included in the CSI report indicates Rank 1 or a Rank combination {1, 1}. When a higher-level parameter related to the CSI report mode (e.g., csi-ReportMode) is set to 'Mode2', the terminal determines the number of PRBs for the PUCCH resource and the number of Part 2 CSI reports, assuming that each CRI of the CSI report is associated with a resource pair.
[0275] For example, if a CSI report in PUSCH contains two parts, the terminal may omit part of the Part 2 CSI. The omission of the Part 2 CSI follows the priority order. Except where the corresponding CSI report contains at least one CSI sub-report including Part 2 that corresponds to a sub-configuration from a list of sub-configurations provided by a higher-level parameter (e.g., csi-ReportSubConfigList) included in the information related to the CSI report (e.g., CSI-ReportConfig), when omitting Part 2 CSI information for a specific priority level, the terminal must exclude all information for that priority level.
[0276] For report configurations related to information (e.g., CSI-ReportConfig) concerning a CSI report that includes a list of sub-configurations, the following processing is possible. For a corresponding CSI report that includes at least one CSI sub-report, the omission of Part 2 CSI is performed at the sub-configuration level within the same priority level. Here, the sub-configuration having a lower index value has a higher priority.
[0277] For example, if a CSI report consists of two parts, the terminal may omit part of the Part 2 CSI. The omission of the Part 2 CSI follows a priority order. For a report configuration associated with information related to the CSI report (e.g., CSI-ReportConfig) containing a list of sub-configurations, the omission of the Part 2 CSI for a given CSI report containing at least one CSI sub-report is defined in Section 5.2.3. The Part 2 CSI is omitted starting from the lowest priority level up to a Part 2 CSI code rate that is less than or equal to the code rate set by the upper-level parameter (e.g., maxCodeRate).
[0278] Additionally, when a CQI request field within a DCI triggers CSI report(s) in a PUSCH, the first uplink symbol carrying the CSI report(s) does not precede a symbol specified after a certain interval from the last symbol of the PDCCH that carried the DCI. This can be understood as a measure to guarantee the CSI calculation time. In this case, if multiple sub-configurations are configured for the CSI report, the starting position of the aforementioned certain interval may be determined based on all triggered sub-configurations.
[0279] For example, CSI is transmitted via PUCCH or PUSCH and can be represented as a bit sequence of a fixed size.
[0280] The following describes the on-demand SSB.
[0281] For example, for a terminal in a connection mode in which carrier aggregation is configured, procedures and signaling methods may be defined to support on-demand synchronous signal block auxiliary cell operation in both same-band carrier aggregation and cross-band carrier aggregation. In this case, as a triggering method, at least one of a terminal uplink wake-up signal using an existing signal or channel, a cell on / off instruction via backhaul, or auxiliary cell enable / disable signaling may be considered. Additionally, on-demand synchronous signal block transmission may be used by the terminal for at least auxiliary cell time / frequency synchronization, first layer / third layer measurement, and auxiliary cell activation in frequency ranges 1 and 2 of the non-shared spectrum.
[0282] For example, procedures and signaling methods for supporting on-demand system information block 1 for a terminal in idle mode or inactive mode may be considered. In this case, a triggering method using an uplink wake-up signal utilizing an existing signal or channel may be considered. Additionally, a wake-up signal setting may be provided to the terminal. Furthermore, if necessary, information exchange between at least base stations may be supported for setting the wake-up signal. In addition, a check point may be set to determine whether the normative operation is in progress.
[0283] For example, adaptations of common signals or channel transmissions may be defined. For example, adaptations of synchronous signal blocks in the time domain, such as adaptations of periodicity, may be performed. Additionally, adaptations of physical random access channels may be performed in the time domain. Furthermore, adaptations of physical random access channels in the spatial domain, such as non-uniform physical random access channel resource configurations per synchronous signal block, may be considered, and if their validity is recognized, regulations regarding them may be established. Additionally, adaptations of paging opportunities, including limiting paging opportunities in the time domain, may be performed. In this case, there may be no increase in paging delay time.
[0284] For example, energy consumption can be reduced by having a base station transmit an SSB to a specific cell via On-Demand SSB, and by not transmitting an SSB to that cell when the On-Demand SSB process is not present. In existing NR systems, it was difficult to reduce energy consumption even when the base station had no data to receive or send, as SSBs had to be transmitted periodically at all times for purposes such as time / frequency synchronization or Radio Resource Management (RRM) measurements. Considering this, the base station can reduce energy consumption by refraining from transmitting SSBs and only performing transmissions when the On-Demand SSB process is involved. The On-Demand SSB process can be triggered through one of the following methods.
[0285] 1) The terminal requests the base station's SSB transmission by transmitting an uplink signal / channel (e.g., PRACH, PUCCH, PUSCH, SRS, etc. in an NR system).
[0286] 2) Base station (or TRP (Transmission Reception Point)) #1 requests SSB transmission from base station (or TRP) #2 via inter-base station interface or backhaul signaling, etc.
[0287] 3) Signaling whether to transmit an SSB for the corresponding secondary cell through secondary cell enable / disable signaling
[0288] For example, the above operation may be limited to on-demand SSB operation for terminals in connection mode and secondary cells, taking into account coexistence with existing NR terminals.
[0289] For example, an on-demand SSB operation can be defined considering a disabled or idle mode terminal or an initial connection terminal.
[0290] In addition, CA including the said secondary cell can be applied to both intra-band CA and inter-band CA, and the SSB on the said secondary cell transmitted through the on-demand SSB process can be utilized for at least time / frequency synchronization, L1 / L3 measurement, secondary cell activation, etc.
[0291] The following describes on-demand SIB1 transmission.
[0292] A method to reduce energy consumption can be discussed in which the base station transmits a SIB1 for a specific cell through an on-demand SIB1 process, and does not transmit a SIB1 for that cell when there is no on-demand SIB1 process. In existing NR systems, it was difficult to reduce energy consumption even when the base station had no data to receive or send, because the base station always had to periodically provide a SIB1 containing system information, random access information, etc., for terminals in initial access or idle mode to access the cell.
[0293] Considering this, the base station can reduce energy consumption by not performing SIB1 transmission until an on-demand SIB1 process is involved. The base station's SIB1 transmission can be triggered by the terminal transmitting an uplink signal / channel, and specifically, the following scenarios may be considered, but are not limited to them.
[0294] FIGS. 22, FIGS. 23, and FIGS. 24 illustrate scenarios regarding SIB1 transmission triggering.
[0295] Referring to FIG. 22, a terminal that receives an SSB (and / or other downlink signal / channel) in cell #1 and recognizes that SIB1 is not being transmitted on cell #1 can trigger the transmission of SIB1 by transmitting a signal requesting SIB1 based on information provided in the SSB (and / or other downlink signal / channel) and / or predetermined information (in this disclosure, for convenience, such signal is referred to as a WUS (wake-up signal)). A base station that receives the WUS can transmit a specific DL signal / channel on cell #1 in response thereto (or without transmitting the DL signal / channel) and can transmit SIB1 on cell #1.
[0296] Referring to FIG. 23, a terminal that receives an SSB (and / or other downlink signal / channel such as SIB1) at cell #1 and realizes that SIB1 is not being transmitted on cell #2 may attempt to camp-on through cell #2. The terminal may trigger the transmission of SIB1 to cell #2 by transmitting a signal (WUS) requesting SIB1 on cell #1 based on information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. A base station that receives the WUS may transmit a specific DL signal / channel (on cell #1 or cell #2) in response, or transmit SIB1 to cell #2 on cell #1 or cell #2 (or without transmitting the DL signal / channel).
[0297] Referring to FIG. 24, a terminal that receives an SSB (and / or other downlink signal / channel such as SIB1) at cell #1 and realizes that SIB1 is not being transmitted on cell #2 may attempt to camp-on through cell #2. The terminal may trigger the transmission of SIB1 for cell #2 by transmitting a signal (WUS) requesting SIB1 on cell #2 based on information provided in the received SSB (and / or other downlink signal / channel such as SIB1) and / or predetermined information. A base station that receives the WUS may transmit a specific DL signal / channel (on cell #1 or cell #2) in response (or without transmitting the DL signal / channel) and transmit SIB1 for cell #2 on cell #1 or cell #2.
[0298] For example, a base station can reduce energy consumption by controlling common signal / channel transmissions such as SSB, PRACH, and paging. For instance, while completely turning off the SSB can significantly reduce the energy consumption of the base station, the absence of an SSB that performs functions such as time / frequency synchronization or RRM measurement may result in unstable operation for the corresponding cell from the terminal's perspective. Considering this, the base station can achieve energy savings by changing the transmission pattern of the SSB (e.g., transmission period, period per SSB candidate index, SSB candidate index transmitted within one transmission period, transmission power, etc.) according to the situation.
[0299] In the case of PRACH resources, in the case of contention-based random access, energy consumption can increase because the base station always attempts to receive from the configured PRACH resources since it is unknown when the terminal will transmit PRACH. Considering this, the energy of the base station can be saved by applying methods to adjust the amount of PRACH resources (e.g., adjusting the cycle of PRACH resources, adjusting the amount of resources by pre-configuring PRACH resource sets #1 and #2 and giving instructions such as whether to turn on only one set or both sets, or providing the corresponding amount of PRACH resources for each SSB index uniformly or non-uniformly).
[0300] In the case of paging, conventionally, paging frames (PF) and / or paging occasions (PO) were distributed along the time axis within a DRX cycle (or paging cycle), and terminals attempted to receive paging at specific PF / POs derived from their ID-based formulas. From the base station's perspective, if it was intended to transmit paging to multiple terminals simultaneously, it was necessary to transmit paging while frequently interrupting the system. To reduce the resulting energy consumption of the base station, it is possible to consider placing the PF and / or PO for paging reception as close to the time axis as possible, or placing them using different frequency axis resources within the same timeframe.
[0301] The symbols / abbreviations / terms used in this specification are as follows.
[0302] - PDCCH: Physical Downlink Control Channel
[0303] - DCI: Downlink Control Information
[0304] - CA: Carrier Aggregation
[0305] - UCI: Uplink Control Information
[0306] - MCSC: Multi-Carriers Single Carriers
[0307] In this disclosure, regarding a multi-carrier single cell (hereinafter referred to as MCSC), we propose considerations for cases where multiple carriers are scheduled within a single cell. Generally, when a cell is configured with a single carrier, it may be necessary to utilize multiple carriers from the initial connection stage. Conventionally, when attempting an initial connection, the terminal proceeds with the RACH procedure using a single carrier, then proceeds to RRC Connected, followed by authentication, security processing, and USIM-related processing. Subsequently, the UE capability is transmitted over the uplink, and multi-carrier or multi-cell scheduling becomes possible.
[0308] In contrast, since the cells in the MCSC system are composed of multiple carriers from the beginning, it can be said that initial multi-carrier scheduling through a faster UE Capability Report than conventional methods is required to utilize the full support of the cells from the start. Accordingly, the present disclosure presents methods for a network to rapidly acquire the capability of a specific terminal and methods for operating multiple carriers from the initial connection stage through said methods.
[0309] A cell can generally be described as the smallest unit of a network that includes a channel for synchronization, a channel for sending network system information, initial information for terminal connection, operation and management upon connection, and finally, mobile communication-related application services received wirelessly. In the past (3G / 4G / 5G), the structure was such that a single wireless resource, the carrier, was connected to a single cell in a one-to-one mapping relationship.
[0310] In contrast, the present disclosure proposes various operational and behavioral principles when multiple carriers are interconnected in a single cell. A system in which multiple carriers are interconnected and operated within a single cell is referred to in this disclosure as a Multi-Carriers Single Cell (MCSC). Since an MCSC is also a type of cell, it must provide various basic services that are required to be provided by the preceding cell. The basic services of the cell may include synchronous channel transmission, broadcasting of basic network information, and the execution of RACH procedures for initial connection (RRC_Connected).
[0311] In particular, the function of continuously providing specific services to a specific terminal while maintaining a connection with the network after the initial terminal connection can be considered the most important role of a cell. While conventional cell configurations provided these functions with only one carrier per cell, the present disclosure proposes an operation or method of operation different from the conventional (3G / 4G / 5G) based on the assumption that these functions can be performed across multiple carriers.
[0312] In the following description, the proposed methods are explained using the term MCSC, wherein MCSC may refer to a structure in which a single cell is composed of multiple carriers. However, the proposed methods are not limited to such terms or definitions, and as long as the spirit of the invention is maintained, they can be generally applied to other situations in which a single cell operating unit is configured to include one or more radio frequency resources (e.g., carrier, BWP, band).
[0313] In cases where multiple carriers operate simultaneously within a single cell, the operation of the RACH procedure in the RRC_IDLE state is described as a key aspect of this disclosure. The RACH procedure begins when a terminal first attempts to connect to a base station by first transmitting a RACH Preamble (Message 1) and receiving a Random Access Response (RAR) (Message 2). Subsequently, based on the uplink scheduling information contained within the RAR, the terminal transmits its Temporary ID information (Message 3) to the uplink, and upon receiving Confirm information (Message 4) regarding the Temporary ID from the final base station, the connection between the base station and the terminal is considered complete. The process leading up to the completion of the connection through the exchange of basic information between the terminal and the base station, from Message 1 to Message 4, can be referred to as the RACH procedure.
[0314] For example, after the connection is established, additional user data and control information regarding specific services are transmitted and received between the base station and the terminal, allowing the terminal to receive wireless-related services from the base station. In the past (3G / 4G / 5G), this series of processes proceeded with a single carrier, but since 4G LTE-A, carrier aggregation has made it possible to receive services simultaneously in multiple cells. In fact, it can be said that such services were possible only after the RACH procedure in a single cell (or single carrier) had already been completed and a significant amount of information had been exchanged between the base station and the terminal. Previously, in the configuration of a single cell consisting of a single carrier, only the method of the initial connection RACH procedure utilizing a single carrier was considered. However, from the perspective of a cell composed of multiple carriers, such as MCSC, it is necessary to utilize the entire resources from the initial stage without restricting the use of resources from multiple carriers within the same cell from the initial connection stage.
[0315] In addition, conventionally, even when operating multiple cells (or carriers), the terminal would inform the base station in advance of the information regarding the multiple cells (or carriers) it can support, and the network / base station would inform the terminal to transmit and receive data via multiple carriers or cells based on this information, thereby enabling the base station to schedule the necessary data for the multiple carriers or cells. However, in the case of a terminal undergoing initial connection, the network cannot receive the aforementioned information from the terminal in advance during the RACH procedure, and if the network is unaware of this information, the base station cannot perform multi-carrier scheduling for the RACH procedure of the terminal undergoing initial connection. When a specific cell operates multiple carriers rather than a single carrier from the beginning, it is necessary to know in advance from the terminal which carrier among the multiple carriers it can transmit and receive data via.
[0316] For example, if UE-supported carrier information (e.g., band or RF-related information) is not known when a terminal requests connection, the system operates using only a single carrier for a considerable period as in the past. Only after the terminal uploads information regarding the carriers it supports or related combinations does multi-carrier service become available to that terminal. Consequently, even if the cell is configured with multiple carriers from the start and the terminal is capable of simultaneous transmission and reception for multiple carriers, it cannot utilize multiple carriers from the outset. Therefore, it is crucial to determine how the terminal informs the network / base station of the carriers (band or RF information) it supports during the RACH procedure phase, which is the initial connection state. If this information is provided promptly, the cell can efficiently schedule the terminal using its various carriers, and unlike conventional operations performed with only a single carrier, load balancing effects can also be expected.
[0317] The present disclosure proposes the operation of a base station and a terminal to support a RACH procedure utilizing one or more carriers in a situation where an MCSC is in operation.
[0318] In this disclosure, we intend to primarily propose two methods in MCSC. The first is to provide information on carriers that the terminal can simultaneously transmit and receive to the base station from the initial stage of requesting a connection (RRC Connection), rather than providing this information to the base station at a specific point in time after a long period has passed since the connection (RRC Connection) was completed, as in conventional (3G / 4G / 5G) methods. The second is to provide this information during the RACH procedure so that the base station utilizes the information on carriers that the terminal can currently receive to schedule multiple carriers from the RRC_Connected state or immediately after the RRC connection preparation.
[0319] To this end, there is broadcasting information that the base station provides in advance to terminals performing the RACH procedure, which is referred to as SIB1 in this disclosure.
[0320] In this case, SIB1 as referred to in the present disclosure refers to a transmission unit of system information that is transmitted and received by operating similarly to the 5G standard, and the main concepts are explained based on this in the following description. However, as long as the concept of the proposed methods is maintained, the term used does not limit the application of the proposed methods.
[0321] For example, SIB1 contains various information that the terminal must consider when initially connecting, and when the terminal requests an initial connection (RRC Connection), it operates based on the SIB1 information previously received from the network. SIB1 may include the beam direction (e.g., SSB ID) of the synchronization channel (e.g., SSB) previously received by the terminal, specific RACH resources (preamble / frequency / time in Message 1), or RO-related mapping information. A terminal intending to perform the RACH procedure makes a connection request based on this information; it selects the SSB ID=X of a specific beam direction based on the previously received SSBs, selects the RACH resource corresponding to X, and transmits it. Through the RACH resource mapped to a specific resource, the base station can determine which beam direction the terminal is currently located in and transmit a RAR (Message 2) in that direction. When the terminal receives the RAR (Message 2) information in that direction, the terminal can transmit Message 3 (RRC Connection Request) again in that direction. When the base station receives message 3 information, it sends message 4 in the direction of the corresponding beam, and when the terminal transmits an ACK signal for message 4, the initial connection process is completed. This process is an operation performed on a single carrier in the conventional RACH procedure.
[0322] Then, for example, in the case of multi-carriers, a RACH Occasion (RO) can be defined according to the mapping relationship between the SSB beam direction and the preamble, frequency, and time resources for the resources of Message 1. There may be a carrier that transmits information regarding the RO. Among the various carriers, there may be a main carrier, which can be referred to as the anchor carrier. The remaining carriers can be referred to as non-anchor carriers. According to an embodiment, the terminal must support at least one of the various carriers constituting the cell, and the supported carrier may be the anchor carrier from the perspective of the terminal.
[0323] Proposal 1: A method in which an RO Group is configured to be connected to each carrier's individual beam, allowing the terminal to select the RO for a single individual beam.
[0324] The method proposed in the present disclosure assumes a situation in which, in an MCSC situation, one or more carriers selectable as RO are set for the terminal, and there are RSs measurable on each carrier, and the RSs can be distinguished by different beam indices.
[0325] At this time, a method is proposed in which a base station provides relation (or association) information to a terminal to establish a relationship between RSs transmitted on different carriers, and a method is proposed in which the terminal selects an RO based on the said relation information.
[0326] Here, RO stands for RACH Occasion and represents the time and frequency location in a specific preamble where RACH message 1 can be transmitted. Since there may be combinations of time resources, frequency resources, and preambles included in those resources for various beams, such combinations of time, frequency, and preambles can be expressed as RO groups, etc.
[0327] Conventionally (4G / 5G), since there is only one carrier per cell, SIB1 was used to indicate which RO is mapped to for multiple beams (e.g., SSB IDs) of the carrier within that cell. However, in the situation assumed in the present disclosure, since there are multiple carriers in a single cell, information regarding the beams (e.g., SSB IDs) of each carrier may also need to be included in broadcasting configuration information such as SIB1.
[0328] Furthermore, for example, for each beam, RO resources (preamble / frequency / time / UL carrier) can be allocated only to anchor carriers, or RO resources can be allocated to beams of non-anchor carriers as well. Even if RO resources are configured for the beam directions of all carriers in a specific cell, the terminal can select one beam among the multiple carriers, and the RACH procedure can proceed based on that beam direction. Additionally, in this proposal, relationship information regarding the beams of anchor carriers and non-anchor carriers constituting the cell can be included in broadcasting system information such as SIB1. This relationship information can contribute to the terminal understanding the relationships between the beams of all carriers within the cell.
[0329] FIG. 25 illustrates an embodiment related to the beam relationship between multiple carriers within a single cell.
[0330] Referring to FIG. 25, in one embodiment, the cell is composed of three carriers: Carrier 1 + Carrier 2 + Carrier 3, from a carrier perspective. It is assumed that the cell is composed of one beam of Carrier 1 + two beams of Carrier 2 + four beams of Carrier 3 from a beam perspective. Information such as SIB1 may include information on how many carriers the cell is composed of, which beams each carrier is composed of, and which RO each beam is mapped to.
[0331] For example, as shown in Fig. 25, it is assumed that the cell is configured such that the beams of different carriers overlap each other. In this case, if the terminal at position A is capable of RF support for three carriers, it may be possible to transmit and receive simultaneously for one beam each of Carrier 1, Carrier 2, and Carrier 3. The terminal at position A can use the RO corresponding to the beam of Carrier 1, the RO corresponding to the beam of Carrier 2, and the RO corresponding to Carrier 3. Here, broadcasting information such as SIB1 can be used to indicate that there is a relationship between the preceding seven beams (e.g., Carrier 1 - 1 beam [Beam 0] + Carrier 2 - 2 beams [Beam 1, 2] + Carrier 3 - 4 beams [Beam 3, 4, 5, 6,]). In this case, it is assumed that Beam 0 - Beam 1 - Beam 3 or Beam 4 are related to each other. At this time, if the terminal selects the RO for beam 0 among the beams that can be transmitted and received, the base station cannot know exactly where the terminal is located within the cell. In contrast, if the terminal selects the RO for beam 4, the base station will be able to estimate that the terminal is at location A.
[0332] For example, an anchor carrier is a single carrier that the terminal must support at a minimum, whereas non-anchor carriers may be supported depending on the terminal's class or capability. However, by selecting the RO for Beam 4 and transmitting a preamble, the terminal indicates that it is capable of transmitting and receiving Carrier 1 + Carrier 3 for Beams 0, 1, and 4. Additionally, information that the terminal supports up to Carrier 2 can be provided via a subsequent uplink channel transmission (e.g., Message 3 or Message 5).
[0333] Method 1: When there is no non-anchor carrier satisfying the conditions, a method of selecting RO from among the anchor carrier beams and then scheduling messages 2 / 3 / 4 with the anchor carrier.
[0334] According to an embodiment, if there is no relationship information between the beams of non-anchor carriers and the beams of anchor carriers on SIB1, the terminal selects an RO corresponding to the beam of an anchor carrier.
[0335] According to an embodiment, if there is relationship information between the beams of non-anchor carriers and the beams of anchor carriers in SIB1, but there is no beam among the beams of non-anchor carriers that satisfies the reception level, the RO corresponding to the beam of the anchor carrier is selected.
[0336] Method 2: If there is a non-anchor carrier that satisfies the conditions, the terminal selects an RO from among the beams of that carrier, and then schedules messages 2 / 3 / 4 through anchor carriers and non-anchor carriers.
[0337] According to an embodiment, a cell is composed of carriers 1 + 2 + 3 + 4 + 5, and the carrier priority is given as 1 < 2 < 3 < 4 < 5. There is relationship information between the beams of non-anchor carriers and the beams of anchor carriers, and if the carriers supported by the terminal are 1, 3, and 4, then an RO is selected for the beam that satisfies the reception level among the beams of carrier 4, which has the highest priority.
[0338] Proposal 2: A method in which the capabilities of different carrier / beam combinations are set / linked by RO (group) and / or preamble index (group), and the terminal selects and transmits the RO / preamble set / linked to its own capability.
[0339] The method proposed in the present disclosure assumes a situation in which, in an MCSC situation, one or more carriers selectable as RO by a terminal are configured, and there exist RSs measurable on each carrier, and the RSs can be distinguished by different beam indices. At this time, a method is proposed in which a base station provides relationship information to the terminal to establish a relationship between RSs transmitted on different carriers, and a method is proposed in which the terminal selects an RO based on the relationship information and the terminal's capabilities.
[0340] This proposal applies to cases where a cell is composed of multiple carriers, and the base station provides information regarding the combination of beams of the carriers. For example, referring to Fig. 25, where Carrier 1 is composed of Beam 0, Carrier 2 is composed of Beams 1 and 2, and Carrier 3 is composed of Beams 3, 4, 5, and 6, if we assume there are two beam relationships such as Beam 0 - Beam 1 - Beam 3 or Beam 4, information on these two relationships can be provided through SIB1. In this case, when mapping ROs, ROs are not assigned only to each beam of all carriers, but are also assigned to all sub-relationships related to the relationship information of specific beams. For example, if Proposal 1 is a method of assigning four ROs to each beam, Proposal 2 is a method of assigning ROs to combinations of individual beams of multiple carriers. For example, since there are two relationships, Beam 0 - Beam 1 - Beam 3 and Beam 0 - Beam 1 - Beam 4, mapping and assignment for RO must assign RO for six beam combinations: Beam 0, Beam 0-Beam 1, Beam 0-Beam 1-Beam 3, Beam 0-Beam 1-Beam 4, Beam 0-Beam 4, and Beam 0-Beam 3. Therefore, in this case, SIB1 may not need to include information about the priority between carriers.
[0341] Proposal 2 has the advantage of being able to immediately determine the combination of carriers that the terminal supports the maximum among the relationships between the current beams through the RO of Message 1. In Proposal 1, when a terminal transmits Message 1 for Beam 4, since the anchor carrier Beam 0 must be supported, it is known that Beam 0 of Carrier 1 and Beam 4 of Carrier 3 are supported, but there is a possibility that the base station may not know whether Carrier 2 is supported. In contrast, in Proposal 2, the combination of carriers can be determined by performing RO selection by selecting the carrier that it supports from among the ROs of Beam 0-Beam 1-Beam 4 or Beam 0-Beam 4 or Beam 0-Beam 1 combinations starting from the transmission stage of Message 1.
[0342] Method 1: If there is no non-anchor carrier that satisfies / supports the conditions of the terminal, select RO from among the beams among the anchor carriers, and then schedule messages 2 / 3 / 4 with the anchor carrier.
[0343] According to an embodiment, if there is no relationship information between the beams of non-anchor carriers and the beams of anchor carriers on SIB1, the terminal selects an RO corresponding to the beam of an anchor carrier.
[0344] According to the embodiment, if there is relationship information between the beams of non-anchor carriers and the beams of anchor carriers in SIB1, but there is no beam among the beams of non-anchor carriers that satisfies the reception level, the RO corresponding to the beam of the anchor carrier is selected.
[0345] Method 2: If there are non-anchor carriers satisfying the conditions, select RO from among the combinations of beams of those carriers, and then schedule messages 2 / 3 / 4 through anchor carriers and non-anchor carriers.
[0346] According to an embodiment, if the terminal at position A of FIG. 25 supports carriers 1, 2, and 3, an RO matching the combination of beam 0-beam 1-beam 4 is selected.
[0347] According to an embodiment, when the terminal at position A of FIG. 25 supports carriers 1 and 2, an RO matching the combination of beam 0 and beam 1 is selected.
[0348] According to an embodiment, if the terminal at position A of FIG. 25 supports carriers 1 and 3, an RO matching the combination of beam 0 and beam 4 is selected.
[0349] FIG. 26 illustrates a carrier selection method for cases where priority information among multiple carriers is given.
[0350] First, carriers supporting the cell and priority information for each carrier can be received (S261). At this time, the anchor carrier may have the lowest priority.
[0351] Afterwards, the carrier with the highest priority among the carriers supported by the terminal and the carriers supported by the base station can be selected (S262).
[0352] Here, it is determined whether there is a beam that meets the conditions in the carrier (S263). If there is a beam, the RO of that beam can be selected (S265). If there is no beam, it is determined whether the carrier is an anchor carrier (S264). If it is an anchor carrier, the RO of that beam can be selected (S266). If it is not an anchor carrier, the carrier with the next highest priority among the carriers supported by the terminal and the carriers supported by the base station can be selected (S267).
[0353] FIG. 27 illustrates a carrier selection method for cases where priority information of multiple carrier mountains is not given.
[0354] First, information regarding the combination of carriers supporting the cell and the beams of each carrier and the relationship between the beams can be received (S271).
[0355] Afterwards, it is determined whether a combination of beams matching the conditions of each carrier has been found (S272). If it has not been found, the cell can be re-searched (S273). If it has been found, an RO corresponding to the combination of beams can be selected, or an RO corresponding to a sub-combination of the combination can be selected (S274).
[0356] For example, when selecting ROs for combinations of beams within a given carrier, the number of ROs can increase exponentially if the number of carriers is large and there are an excessive number of beams within them. Therefore, one can consider a method of operating the network by allocating ROs based on combinations of only a subset of carriers, and classifying terminals according to the number or types of supported carriers and terminal capabilities.
[0357] Proposal 3: Method for managing carrier / beam related information using RACH message 2.
[0358] Some information regarding the related combinations and individual information of carriers and beams can be provided using Message 2, and based on that information, methods can be considered for the terminal to provide the base station with carrier / beam information that meets the conditions in Message 3 in the next step.
[0359] For example, the RAR in Message 2 provides information on candidate carriers and beams related to the corresponding carrier beam, so that Message 3 can provide the network with carrier and beam-related information that meets the conditions among the candidate information.
[0360] According to an embodiment, only ROs of specific carriers (e.g., anchor carriers) are assigned, and when a terminal selects an RO that meets reception conditions and transmits Message 1, the base station provides information on related candidate non-anchor beams that match the corresponding beam in Message 2, and can provide carrier and beam-related information that meets conditions from the information on related candidate non-anchor beams known through Message 2 (RAR) in Message 3. When such a process is used, multi-carrier scheduling operation may be possible from the subsequent step (e.g., the step related to Message 4).
[0361] Proposal 4: Method for designating / setting scheduling carriers through the distribution of RO resources across multiple UL carriers.
[0362] For example, when ROs are configured by beam or as a combination of carriers and beams, resources such as frequency, time, and preamble can be allocated, but this may result in excessive resource usage. When a cell consists of multiple carriers, there may be multiple UL carriers. In this case, distributing the ROs among the UL carriers can increase resource usage efficiency.
[0363] Figure 28 illustrates RO dispersion among UL carriers.
[0364] Referring to FIG. 28, for a terminal in area A, all ULs of Carrier 1 and Carrier 2 can be used. It is assumed that there is a relationship between the two carriers, where Carrier 1 is an anchor carrier and Carrier 2 is a non-anchor carrier. For example, when deploying RO, if the Carrier 1 beam is assigned to the UL of Carrier 1 and the Carrier 2 beam is assigned to the UL of Carrier 2, the terminal can select which DL carrier to schedule the Physical Layer Control Signaling (e.g., PDCCH or DCI) that schedules Message 2 (RAR) according to its reception level. When deploying RO to multiple UL carriers, a multi-carrier scheduling operation method can be determined based on which carrier to transmit Message 1 to.
[0365] Method 1: When a cell is composed of multiple DL carriers and UL carriers, ROs can be distributed among multiple UL carriers. In this case, a method of operating multiple carriers by selecting a specific UL carrier and selecting an RO from that carrier can be considered.
[0366] For example, through a method of selecting an RO within a frequency and a method of selecting one UL carrier among the UL carriers, it is possible to select and specify how many carriers are scheduled after Message 2 (RAR) and on which carrier DL physical layer control signaling is operated. Specifically, if the RO is assigned per beam, the selection of the UL carrier can provide the network with specific information on which combination of carriers and beams is used, or to determine which DL carrier the DCI of Message 2 (RAR) is scheduled on, which can be seen as the DL carriers linked to each UL carrier being selected as the scheduling carriers.
[0367] Figure 29 illustrates various configuration forms of MCSC.
[0368] Referring to Fig. 29, at various locations, a terminal can determine which carriers meet the conditions for transmitting and receiving services in an RRC idle state by receiving through a broadcasting channel such as SIB1. Based on this information, for a terminal that has completed initial connection, a method is required to provide this information when receiving with multiple carriers in an RRC idle state, or when receiving a specific channel as a non-anchor carrier and then moving to an area within the cell where the corresponding carrier cannot be received. In this case as well, this information can be provided through the RACH procedure described above.
[0369] For example, a terminal assigns a specific RO to a RACH that can update the currently available carriers. For instance, while transmitting or receiving a specific service such as MBMS (Multimedia Broadcast Multicast Service) using one of the non-anchor carriers, if the terminal becomes unable to use that carrier in a specific area of the cell, it can trigger a pre-designated RO (e.g., sending Message 1 or Message A) to update information on other currently available carriers. Specifically, for instance, if a terminal needs to notify the base station because there has been a change in the carriers satisfying the current conditions while in an RRC idle / inactive state, it triggers the RACH procedure via the RO of Message 1 and uses uplink channels (e.g., PUSCH channels after Message 3 / Message 5) to provide information regarding carriers and beams that meet the conditions from the terminal's perspective, thereby allowing the base station to recognize the situation.
[0370] FIG. 30 illustrates a RACH procedure when the terminal moves.
[0371] According to an embodiment, while receiving a broadcast service such as MBMS through a non-anchor carrier 2 in an RRC idle / inactive state, if the terminal fails to receive carrier 2 while moving to a specific area within the cell, the terminal can initiate a RACH procedure using a specific RO. Subsequently, information on carriers / beams capable of transmitting and receiving in that area can be provided, and the service can be continuously received thereafter.
[0372] For example, if a terminal in area A of Fig. 30 is receiving MBMS service in the RRC_Idle / INACITVE state via the beam of Carrier 2, it can receive MBMS service if it suddenly moves in the direction of the arrow. In this case, to continue the service, the base station can switch the MBMS service to C1 or switch to the RRC-Connected state to continue the service through Unicast transmission. At this time, area A is receivable for two carriers, but if it moves in the direction of the arrow, the number of receivable carriers decreases to one. In this case, if the terminal is in the RRC_Connected state, measurement and reporting can be processed via C-RNTI-based PUSCH or PDSCH. For example, if it is in the RRC idle / inactive state, it can perform measurement and reporting through the RACH message processes 1 / 2 / 3 / 4 / 5 to report information about the carriers available to it at that time to the base station.
[0373] According to an embodiment, in the case of a terminal in an RRC idle / inactive state, the terminal is enabled to perform measurements of non-anchor carriers. In this case, the terminal is enabled to perform measurements only on carriers supported by the terminal, and by triggering reports via RO when necessary or by periodically transmitting uplink channels, the base station can provide information in advance on what actions to take when multi-carrier operation is required for a specific terminal in the current cell.
[0374] According to an embodiment, instructions for measuring each carrier when RRC is idle / deactivated can be given to the terminal via SIB1, message 2, message 4, or PDSCH.
[0375] For example, measurements can be performed for each carrier in the current combination. Subsequently, it can be determined whether there is a change in the receivable carriers for non-anchor carriers. If there is a change, the RO selection can trigger the RACH procedure to report on the receivable carriers and measurement status. If there is no change, measurements can be performed for each carrier in the current combination.
[0376] Proposal 5: A method for dividing an RO group into combinations of individual beams of each carrier and having a terminal select one of the ROs.
[0377] The method proposed in the present disclosure assumes a situation in which one or more selectable ROs are set in the context of an MCSC, one or more carriers are included in the configuration of the MCSC, and each carrier has measurable RSs, and the RSs can be distinguished by different beam indices.
[0378] In this case, one or more beam indices, for example, RSs, may be related or associated with a single RO, and the number of beam indices associated with each RO may vary from RO to RO. Here, a method is proposed in which the base station provides the above information to the terminal, and the terminal selects an RO based on the above information.
[0379] Conventionally (3G / 4G / 5G), since there is only one carrier per cell, the base station provided the terminal with information regarding which RO is mapped to SIB1 for multiple beams (e.g., SSB IDs) of a single carrier within that cell. However, in the situation assumed in the present disclosure, since multiple carriers exist within a single cell, the beams (e.g., SSB IDs) of each carrier may now also need to be included in broadcasting system information such as SIB1. Furthermore, while the base station can allocate RO resources (preamble / frequency / time / UL carrier) only to anchor carriers for each beam, it may be necessary to distribute and allocate RO resources according to frequency / preamble / time / UL carrier by considering various combinations including beams of non-anchor carriers to support multi-carrier scheduling from the initial connection attempt.
[0380] FIG. 31 illustrates a beam combination between multiple carriers.
[0381] Referring to FIG. 31, RO resources can be configured and allocated for each of the beams of Carrier 1, the beams of Carrier 3, and all beams of Carrier 2, either individually or in combination. Carrier 1 is assumed to be an anchor carrier, and all terminals must support at least that carrier. It is assumed that there are different beams in different directions containing only Carrier 1 in FIG. 31. This proposal is primarily applicable when the transport terminals operating the carriers within a cell are not collocated. Specifically, if the entire omnidirectional beam (Omni-beam) of Carrier 2 overlaps with a portion of a beam of Carrier 1 facing east, ROs can be allocated for the individual corresponding beams in the area where only Carrier 1 can be received, and for the case where beams of Carrier 1 and Carrier 2 can be received simultaneously. Then, an RO is assigned to one individual single beam of Carrier 1 that is oriented northward, and an RO is assigned to each of the three individual single beams of Carrier 3 for regions that do not overlap at all with the northward beam of Carrier 1. Additionally, an RO can be assigned to the three regions that overlap between Carrier 1 and Carrier 3. Finally, an RO can be assigned to each beam region of Carrier 1 that does not overlap with other carriers, such as the westward beam of Carrier 1.
[0382] If RO is allocated in this way, when the terminal selects an RO for a beam combination of carriers that satisfy the conditions (capable of transmitting and receiving), multi-carrier scheduling can be performed using the beams of carriers that satisfy the conditions starting from Message 2 (RAR).
[0383] Method 1: A terminal selects one RO from several ROs allocated for a beam combination of carriers satisfying conditions at a specific time / specific area and transmits Message 1 based on the RO resource.
[0384] For example, information regarding the ROs of combinations between beams of non-anchor carriers and beams of anchor carriers, or of single beams, is provided to the terminal in the form of resources for preamble / frequency / time / UL carriers, and the terminal can inform the base station of the beam combinations of carriers through the ROs for combinations of carriers that satisfy the conditions.
[0385] For example, the terminal at position C in Fig. 31 selects RO only for the westward beam of Carrier 1, even though it supports Carrier 3 and Carrier 2.
[0386] For example, if the terminal at position A in Fig. 31 supports Carrier 1 and Carrier 2, it selects the combined RO of the eastward beam of Carrier 1 and the Omni-beam of Carrier 2, and multi-carrier scheduling for Carrier 1 and Carrier 2 is possible from Message 2 onwards. If the terminal supports only the anchor carrier (Carrier 1), even if it is at position A, the terminal selects the RO for the single beam corresponding to the beam of Carrier 1.
[0387] Method 2: Assigning individual ROs based on combinations of carriers / beams requires a lot of frequency / preamble / time resources, so some RO resource allocation information can be assigned to the UL of another carrier that has a UL in addition to the anchor carrier.
[0388] For example, using broadcasting information such as SIB1, the RO of the entire combination of carrier beams can be allocated to a portion of the UL carriers of non-anchor carriers instead of being allocated to the UL resources of a single carrier (e.g., anchor carrier). This allows the terminal to select the RO resources from the corresponding UL carriers, thereby enabling the base station to know which combinations of carrier beams the terminal can transmit and receive.
[0389] For example, in the case of a terminal at position A in Fig. 31, if RO allocation for the westward beam of Carrier 1 is allocated from the Carrier 1 UL resource and RO for the Omni-beam of Carrier 2 is allocated to the Carrier 2 UL carrier, it can be said that a terminal located in the overlapping area where transmission and reception of Carrier 1 and Carrier 2 are possible can only transmit and receive with Carrier 1 if it uses the Carrier 1 UL. Additionally, since it is known that the terminal can use both Carrier 1 and Carrier 2 simultaneously if it uses the Carrier 2 UL, distributing the RO resources can prevent the allocation of many ROs from being concentrated on a single specific UL carrier (e.g., anchor UL carrier).
[0390] For example, it can be assumed that information about a scheduled PUSCH or PDSCH from a DL carrier linked to a UL carrier is transmitted in physical layer control signaling.
[0391] FIG. 32 illustrates a procedure for providing information about a combination of multiple carriers through RO.
[0392] First, information regarding the combination of carriers supporting the cell and the beams of each carrier and the relationship between the beams can be received (S321).
[0393] Afterwards, the carrier supported by the terminal can be determined among the carriers constituting the cell (S322).
[0394] Afterwards, it is determined whether a combination of beams matching the conditions of each carrier has been found (S323). If no combination is found, scheduling is performed using only anchor carriers (S324). If a combination is found, an RO corresponding to the combination of beams or an RO corresponding to a sub-combination of the combination can be selected (S325).
[0395] For example, the terminal must always support an anchor carrier to attempt to connect to the cell at least. Even if the terminal supports multiple carriers within the cell, if no beam of a non-anchor carrier is received in a specific area or at a specific time, Message 1 may select an RO among the beams of anchor carriers and start the RACH procedure.
[0396] Proposal 6: A method in which a terminal notifies beam-related information of carriers satisfying specific conditions via message 3 or message 5.
[0397] The method proposed in the present disclosure assumes a situation in which one or more selectable ROs are configured in the context of an MCSC, one or more carriers are included in the configuration of the MCSC, each carrier has measurable RSs, and the RSs can be distinguished by different beam indices.
[0398] At this time, a method is proposed in which the terminal selects a suitable carrier and / or beam index based on the results of measuring RSs, and reports the selected result to the base station through the steps of message 3 and / or message 5 during the RACH procedure.
[0399] In this proposal, the terminal can provide information regarding carrier / beam combinations that satisfy conditions (capable of transmission and reception) via Message 3 or Message 5. In cases where the number of carriers constituting a cell is large, if we assume that RO for many combinations of carrier beams in Message 1 is allocated to resources such as frequency, preamble, time, and UL carriers, excessive RO usage may occur, leading to significant resource waste. As with the proposed method, if the terminal includes information on carriers / beams that satisfy conditions (capable of transmission and reception) among its currently supported carriers in Message 3 or Message 5 and transmits it to the base station, efficient RO resource management can be achieved. This utilizes the payload size of Message 3 or Message 5, which allows for the transmission of more information than that provided in Message 1.
[0400] Method 1: Among the carriers constituting the cell received by the terminal as broadcasting information (e.g., SIB1), the terminal can transmit information on carriers / beams that satisfy the conditions (information of carriers capable of transmission and reception) among the carriers currently supported by the terminal to the base station when transmitting message 3.
[0401] For example, the terminal configures the RO for transmitting RACH message 1 by utilizing only the beam information of anchor carriers, and after receiving the RAR of RACH message 2, informs the information of carriers / beams that satisfy the conditions (capable of transmission and reception) through RACH message 3 based on the terminal's measurement. Therefore, the base station can operate multi-carrier scheduling starting from RACH message 4.
[0402] For example, the terminal may provide the base station with information on carriers or beams that satisfy the conditions (receiveable) at the current time in the cell in RACH message 3, and / or information on carriers supported in the cell regardless of whether transmission or reception is taking place at the current time.
[0403] Method 2: Through RACH message 5, the terminal can inform the base station of carrier / beam information that satisfies the conditions (information of carriers capable of transmitting and receiving) among the carriers that make up the cell received by the terminal as broadcasting information (e.g., SIB1) and among the carriers supported by the terminal.
[0404] For example, the RACH procedure can be performed with a single carrier as in conventional (3G / 4G / 5G) methods, and the base station can be notified by including information on carriers and / or beams capable of transmitting and receiving in the information transmitted via RACH message 5. Therefore, after RACH message 5 and immediately after RRC Connected, multi-carrier scheduling can be enabled starting from the first downlink.
[0405] For example, in RACH message 5, the terminal may provide the base station with information on carriers and / or beams that satisfy specific conditions (capable of transmission and reception) at the current time in the cell and / or information on carriers supported in the cell regardless of whether transmission and reception are possible at the current time.
[0406] FIGS. 33 and FIGS. 34 illustrate a procedure for providing information regarding beams of receivable carriers as message 3 and / or message 5.
[0407] Referring to FIG. 33, information regarding carriers supporting the cell and the beams of the carriers can be provided (S331). Subsequently, it is determined whether there is an optimal beam for the beams of non-anchor carriers (S332). If there is an optimal beam, the receivable carriers and / or beams can be reported via Message 3 / Message 5 (S334). If there is no optimal beam, the process proceeds with single carriers, and later, the receivable beams or carriers can be reported through carrier / beam-related measurements (S333).
[0408] Referring to FIG. 34, the terminal can select RO among the anchor carrier beams and transmit message 1 (S341). Afterwards, the base station transmits message 2 (RAR) to the terminal (S342).
[0409] The message 2 may include information related to multiple carriers.
[0410] Afterwards, carrier and beam information that can be received from Message 3 can be reported (S343).
[0411] Afterwards, multi-carrier scheduling operation may be possible based on reports of receivable carrier and beam information (S344).
[0412] Proposal 7: A method to provide carrier / beam-related information using RACH Message 2 / Message 4
[0413] For example, through RACH message 1 / RACH message 3, the terminal can provide information about the carriers it supports among the carriers constituting the current cell, which it has learned about through broadcasting information such as SIB1. Subsequently, information regarding candidate carriers / beams, carrier or beam relationships, combinations, or measurements may be instructed to the terminal along with RACH message 2 (RAR) or RACH message 4 (RRC setup message information). Based on this information, the terminal can provide the base station with beam-related information for carriers that satisfy the conditions (capable of transmission and reception) among the measurement results, by including it in RACH message 3 / RACH message 5.
[0414] For example, the present proposal provides some information regarding the related combinations and individual information of carriers and beams using RACH message 2 and / or RACH message 4, and proposes a method in which, in the step following the downlink message that provided the information, the terminal provides carrier / beam information that meets the conditions through RACH message 3 / 5 or uplink channels after that channel.
[0415] Method 1: Provides some or all combinations of carriers supported by the terminal and transmit / receive beam directions among the constituent carriers of the cell via RACH message 1. If candidate information for beams / carriers that the terminal needs to look up (information regarding relationships / combinations / measurements between beams, etc.) is provided in RACH message 2 (RAR), the terminal can provide information that meets the conditions from the candidate information through uplink channels after RACH message 3.
[0416] For example, when configuring ROs, ROs can be configured / assigned to combinations of carrier resources, or ROs can be configured / assigned only to beams of anchor carriers.
[0417] For example, RACH message 2 (RAR) may also include information regarding the relationship / combination / measurement between a type of beam of carriers supported by the terminal. Through the instructions in such information, the terminal can find information that the terminal must include in message 3 / message 3 and subsequent uplink channels for carriers / beams that meet the conditions, based on the measurement results performed before / after receiving the RACH message 2 for a certain carrier / beam.
[0418] For example, after transmitting RACH message 3, the base station may be able to perform multi-carrier scheduling operations.
[0419] FIG. 35 illustrates a procedure for providing information of multiple carriers based on message 2 instead of SIB1 based on RO.
[0420] Referring to FIG. 35, a terminal can select an RO among the anchor carrier beams and transmit Message 1 (S351). The network can provide information about candidate carriers / beams that can be combined with the RO via RACH RAR (Message 2) (S352). Based on the information included in Message 2, information related to carriers / beams that meet the conditions can be included in Message 3 and transmitted (S353). Based on this, multi-carrier scheduling can be operated (S354).
[0421] Method 2: The terminal can provide a combination of carriers supported by the terminal among the carriers constituting the cell via RACH message 3, and based on that information, provide candidate information for carriers / beams in RACH message 4 (RRC setup message), for example, information regarding the relationship / combination / measurement between beams, and then provide the information that meets the terminal's conditions from the candidate information by including it in RACH message 5 / message 5 and subsequent uplink channels.
[0422] For example, RACH message 4 (RRC setup message) may contain relevant information regarding the relationship / combination / measurement between a type of beam of carriers supported by the terminal. Based on the measurement results performed before / after receiving RACH message 4 according to the instructions in such information, the terminal can find information regarding carriers / beams that meet the conditions and need to be included in message 5 / after message 5 in the uplink channel.
[0423] For example, after transmitting RACH message 5, the base station may be able to perform multi-carrier scheduling operations.
[0424] Figure 36 illustrates a procedure in which carrier / beam-related information is provided in Message 4 instead of SIB1 based on RO.
[0425] Referring to FIG. 36, the terminal can select RO among the anchor carrier beams and transmit Message 1 (S361). Subsequently, it can receive RAR (same as before) from the base station via Message 2 (S362). Subsequently, it can transmit the carrier combinations supported in Message 3 (S363). Subsequently, it can provide candidate information related to carrier / beam combinations via Message 4 (S364). Subsequently, it can report receivable carrier / beam related information via Message 5 (same as before) (S365). Based on this, multi-carrier scheduling can be operated (S366).
[0426] Proposal 8: Method of operating multicarrier scheduling in a 2-phase RACH procedure
[0427] In 5G NR, a simpler 2-step RACH procedure consisting of Message A and Message B has been introduced compared to the existing 4-step Message 1 / 2 / 3 / 4. The conventional 4-step RACH procedure is referred to as 4-step RACH, while the 2-step RACH procedure newly introduced in 5G is called 2-step RACH. In 2-step RACH, Message A is separated into Message A RACH (Message 1) and Message A PUSCH (Message 3), and these two are sent simultaneously with a time delay; Message B can be understood as sending either Message 2 (Fallback RAR) or Message 4 (Success RAR). Through this 2-step RACH procedure, the conventional 4-step RACH procedure can be executed more quickly and simply.
[0428] Method 1: By providing the base station with a beam combination of carriers supported by the terminal / a beam combination of carriers that the terminal satisfies the conditions at the current time (capable of transmitting and receiving) via message A RACH and / or message A PUSCH, multi-carrier scheduling can be performed starting from message B.
[0429] For example, the methods of Proposal 5 can be considered for message A RACH.
[0430] For example, the methods of Proposal 5 and Proposal 6 can be considered for message A PUSCH. Through this, multi-carrier scheduling can be enabled from message B onwards.
[0431] According to an embodiment, as in Proposal 8, the combination of carriers supporting the terminal and the corresponding carrier can be reported through message A RACH and message A PUSCH, and relevant information regarding the relationship / combination / measurement of a type of beam between the carriers can be provided through message B PDSCH. Then, after the RRC connected state, the base station can provide information on carriers / beams that satisfy the current conditions (transmit / receive) of the terminal in the first PUSCH transmitted. From thereafter, multi-carrier scheduling can be enabled.
[0432] According to an embodiment, when message B is scheduled as a Fallback RAR, the methods of the aforementioned proposals for providing information in message 3 regarding Fallback RAR information can be applied as is.
[0433] According to an embodiment, when message B is scheduled as Success RAR, candidate information for carriers / beams applied in message 4, for example, information regarding relationships / combinations / measurements between beams, can be provided in advance for Success RAR information, and the terminal may also apply a method of providing information that meets the conditions from the candidate information by including the information in RACH message 5 / PUSCH following message B.
[0434] FIGS. 37 and 38 illustrate a MAC payload for message B. FIGS. 37 and 38 illustrate a Fallback RAR and a Success RAR in comparison, but the MAC payload for message B is not necessarily implemented in the same way as FIGS. 37 and 38, and this is merely an example.
[0435] Through the present disclosure, in the RACH procedure process in which an RRC connection is first requested, the terminal can enable multi-carrier operation from the RACH procedure process by providing the network (or base station) in advance with information regarding its receiveable carrier and carriers supported within the current cell. Through these proposals, when multiple carriers constitute a single cell, various methods for operating as a multi-carrier in the initial state can be considered.
[0436] In the present disclosure, the phrase "can inform of A" may be used with the same meaning as "can provide information regarding A."
[0437] FIG. 39 illustrates a method of operation of a terminal. An embodiment of FIG. 39 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of the embodiments may be omitted.
[0438] Referring to FIG. 39, the terminal can receive system information from a base station (S391). At this time, the system information may include information related to the combination of multiple beams for multiple carriers included in a single cell.
[0439] The above terminal can perform a random access process with the base station based on the above system information (S392).
[0440] According to an embodiment, information related to the combination may include relationship information between two or more beams among the plurality of beams.
[0441] For example, the above relationship information may include information indicating the association between specific beams corresponding to different carrier waves.
[0442] Here, the above relationship information can be used with the same meaning as the relationship information in Proposal 1: a method in which the terminal selects an RO for each individual beam by setting up the connection of the RO Group to each individual beam of each carrier.
[0443] In addition, the terminal can select a random access occasion (RO) for performing the random access process based on the relationship information.
[0444] Here, the specific RO selection process can be performed by referring to the process disclosed in FIG. 26 or FIG. 27.
[0445] According to an embodiment, the system information may include information related to the priority among the plurality of beams.
[0446] For example, the terminal may select a random access occasion (RO) for performing the random access process based on information related to the priority.
[0447] Here, the above priority can be used as the same concept as the priority in FIG. 26.
[0448] According to an embodiment, information related to the combination may include information regarding a combination of beams that can be transmitted or received by the terminal.
[0449] In addition, information related to the above combination may include information related to at least one of a random access occasion (RO) corresponding to each of the beams that can be transmitted or received by the terminal, or an RO corresponding to the combination of the beams that can be transmitted or received.
[0450] For example, the terminal performs downlink reception based on the random access process, wherein the downlink reception may be performed based on one or more of the plurality of carriers.
[0451] Additionally, during the above random access process, uplink transmission can be performed based on one of the plurality of carriers.
[0452] Accordingly, according to the method proposed in this disclosure, even if uplink transmission is performed based on a single carrier, multiple carriers can be utilized for subsequent downlink reception.
[0453] According to an embodiment, the random access process may be performed through i) a random access occasion (RO) corresponding to one beam among the plurality of beams, or ii) an RO corresponding to a combination of two or more beams.
[0454] For example, the above system information may include information related to reception level reference conditions for a plurality of beams.
[0455] In addition, for example, the terminal may select a random access occasion (RO) for performing the random access process based on information related to the reception level reference condition.
[0456] For example, the above random access process may involve the terminal transmitting a preamble to the base station, the terminal receiving a random access response (RAR) containing an uplink grant from the base station, the terminal transmitting message 3 (Msg3) to the base station based on the uplink grant, and monitoring contention resolution.
[0457] For example, the above random access process may involve the terminal transmitting a first message (message A; MsgA) containing a preamble to the base station, and receiving a second message (message B; MsgB) containing a random access response (RAR) from the base station in response to the first message.
[0458] FIG. 40 illustrates a signaling process between a terminal and a base station. An embodiment of FIG. 40 may be combined with various embodiments of the present disclosure, and some descriptions, functions, procedures, proposals, methods, and / or operations of said embodiments may be omitted.
[0459] Referring to FIG. 40, the base station can transmit system information to the terminal (S401). At this time, the system information may include information related to the combination of multiple beams for multiple carriers included in a single cell.
[0460] Afterwards, the base station can perform a random access process with the terminal based on the system information (S402).
[0461] According to an embodiment, information related to the combination may include relation information between two or more beams among the plurality of beams. The relation information may include information indicating the association between specific beams corresponding to different carrier waves. Additionally, the terminal may select a random access occasion (RO) for performing the random access process based on the relation information.
[0462] According to an embodiment, the system information may include information regarding the priority among the plurality of beams. For example, the terminal may select a random access occasion (RO) for performing the random access process based on the information regarding the priority.
[0463] According to an embodiment, information related to the combination may include information regarding a combination of beams that can be transmitted or received by the terminal. Additionally, information related to the combination may include information related to at least one of a random access occasion (RO) corresponding to each of the beams that can be transmitted or received by the terminal, or an RO corresponding to the combination of the beams that can be transmitted or received.
[0464] For example, the terminal performs downlink reception based on the random access process, wherein the downlink reception may be performed based on one or more of the plurality of carriers. Additionally, during the random access process, uplink transmission may be performed based on one of the plurality of carriers.
[0465] According to an embodiment, the random access process may be performed through i) a random access occasion (RO) corresponding to one beam among the plurality of beams, or ii) an RO corresponding to a combination of two or more beams.
[0466] For example, the system information may include information related to reception level reference conditions for a plurality of beams. Additionally, the terminal may select a random access occasion (RO) for performing the random access process based on the information related to the reception level reference conditions.
[0467] Specific operations related to FIG. 40 can be performed by referring to the operations of FIG. 39.
[0468] The signaling operation is described from the base station's perspective as follows.
[0469] A base station transmits system information to a terminal, and the base station performs a random access process with the terminal based on the system information, wherein the system information may include information related to combinations between multiple beams for multiple carriers included in a single cell.
[0470] According to the method proposed in this disclosure, during the initial connection phase of a terminal, even if multiple terminals attempt to connect to a single cell, connection attempts between terminals can be distributed in the frequency domain by utilizing multiple carrier waves. This reduces connection delay and increases the efficiency of resource utilization, and also improves resource scheduling efficiency.
[0471] FIG. 41 illustrates a wireless device that can be applied to the present disclosure.
[0472] Referring to FIG. 41, the first wireless device (100) and the second wireless device (200) can transmit and receive wireless signals through various wireless access technologies (e.g., LTE, NR).
[0473] The first wireless device (100) includes at least one processor (102) and at least one memory (104), and may additionally include at least one transceiver (106) and / or at least one antenna (108). The at least one processor (102, hereinafter simply referred to as processor) controls at least one memory (104, hereinafter simply referred to as memory) and / or at least one transceiver (106, hereinafter simply referred to as transceiver or transceiver), and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document. For example, the processor (102) may process information within the memory (104) to generate a first information / signal, and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through a transceiver (106) and then store information obtained from signal processing of the second information / signal in a memory (104). The memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, the memory (104) may store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequence diagrams disclosed in this document. Here, the processor (102) and the memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver (106) may be connected to the processor (102) and may transmit and / or receive a wireless signal through one or more antennas (108). The transceiver (106) may include a transmitter and / or a receiver. The transceiver (106) may be used in combination with an RF (Radio Frequency) unit.In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.
[0474] At least one processor (102) is characterized in that the first wireless device (100) receives system information from the second wireless device (200) and performs a random access process based on the system information, wherein the system information includes information related to the combination of multiple beams for multiple carriers included in a single cell. The specific operation has been described above with reference to FIGS. 38 and 39.
[0475] The second wireless device (200) includes at least one processor (202) and at least one memory (204), and may additionally include at least one transceiver (206) and / or at least one antenna (208). The processor (202) controls the memory (204) and / or transceiver (206) and may be configured to implement the descriptions, functions, procedures, proposals, methods and / or sequences of operation disclosed herein. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeable with an RF unit. In this disclosure, a wireless device may refer to a communication modem / circuit / chip.
[0476] The processor (202) is characterized in that at least one processor (102) transmits system information from the second wireless device (200) to the first wireless device (100) and performs a random access process based on the system information, wherein the system information includes information related to the combination of multiple beams for multiple carriers included in a single cell. The specific operation has been described above with reference to FIGS. 38 and 39.
[0477] Figure 42 illustrates another example of a wireless device.
[0478] According to FIG. 42, the wireless device may include at least one processor (102, 202), at least one memory (104, 204), at least one transceiver (106, 206), and one or more antennas (108, 208).
[0479] The difference between the example of the wireless device described in FIG. 41 and the example of the wireless device in FIG. 42 is that in FIG. 41, the processor (102, 202) and the memory (104, 204) are separated, whereas in the example of FIG. 42, the memory (104, 204) is included in the processor (102, 202). For example, the processor and the memory may form a single chipset.
[0480] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors (102, 202) may generate one or more Protocol Data Units (PDUs) and / or Service Data Units (SDUs) according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this document and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and / or flowcharts disclosed in this document.
[0481] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). One or more processors (102, 202) may also be implemented as at least one computer-readable medium (CRM) containing instructions based on being executed by at least one processor.
[0482] For example, in at least one computer-readable storage medium (CRM) comprising instructions that are executed by at least one processor to perform operations,
[0483] The above operations are characterized in that the first wireless device (100) receives system information from the second wireless device (200) and performs a random access process based on the system information, wherein the system information includes information related to the combination of multiple beams for multiple carriers included in a single cell. The specific operation has been described above with reference to FIGS. 38 and 39.
[0484] The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions.
[0485] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, code, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.
[0486] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc., of this document to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the descriptions, functions, procedures, proposals, methods and / or operation flowcharts, etc., disclosed in this document from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and receive user data, control information, wireless signals / channels, etc., as described in the descriptions, functions, procedures, proposals, methods, and / or flowcharts of operation disclosed in this document through one or more antennas (108, 208). In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.
[0487] FIG. 43 illustrates an example of a signal processing module structure. Here, signal processing may be performed in the processor (102, 202) of FIG. 41.
[0488] Referring to FIG. 43, a transmission device (e.g., a processor, a processor and memory, or a processor and a transceiver) within a terminal or base station may include a scrambler (301), a modulator (302), a layer mapper (303), an antenna port mapper (304), a resource block mapper (305), and a signal generator (306).
[0489] The transmission device can transmit one or more codewords. Each coded bit within a codeword is scrambled by a scrambler (301) and transmitted over a physical channel. A codeword may be referred to as a data sequence and may be equivalent to a transmission block, which is a data block provided by the MAC layer.
[0490] The scrambled bits are modulated into complex-valued modulation symbols by a modulator (302). The modulator (302) can modulate the scrambled bits according to a modulation scheme to arrange them into complex-valued modulation symbols representing positions on a signal constellation. There are no restrictions on the modulation scheme, and m-PSK (m-Phase Shift Keying) or m-QAM (m-Quadrature Amplitude Modulation), etc., may be used for modulating the encoded data. The modulator may be referred to as a modulation mapper.
[0491] The complex modulation symbols above can be mapped to one or more transmission layers by a layer mapper (303). The complex modulation symbols on each layer can be mapped by an antenna port mapper (304) for transmission on an antenna port.
[0492] The resource block mapper (305) can map complex modulation symbols for each antenna port to appropriate resource elements within a virtual resource block allocated for transmission. The resource block mapper can map the virtual resource block to a physical resource block according to an appropriate mapping scheme. The resource block mapper (305) can assign complex modulation symbols for each antenna port to appropriate subcarriers and multiplex them according to the user.
[0493] The signal generator (306) can generate a complex-valued time domain OFDM symbol signal by modulating a complex modulation symbol for each antenna port, for example, an antenna-specific symbol, using a specific modulation method, for example, OFDM (Orthogonal Frequency Division Multiplexing). The signal generator can perform an Inverse Fast Fourier Transform (IFFT) on the antenna-specific symbol, and a Cyclic Prefix (CP) can be inserted into the time domain symbol after the IFFT is performed. The OFDM symbol is transmitted to a receiving device through each transmitting antenna after undergoing digital-to-analog conversion, frequency uplink conversion, etc. The signal generator may include an IFFT module, a CP inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.
[0494] FIG. 44 illustrates another example of a signal processing module structure within a transmission device. Here, signal processing can be performed in a processor of a terminal / base station, such as the processor (102, 202) of FIG. 41.
[0495] Referring to FIG. 44, a transmission device (e.g., a processor, a processor and memory, or a processor and a transceiver) within a terminal or base station may include a scrambler (401), a modulator (402), a layer mapper (403), a precoder (404), a resource block mapper (405), and a signal generator (406).
[0496] For one codeword, the transmission device can scramble the coded bits within the codeword by the scrambler (401) and then transmit them through the physical channel.
[0497] The scrambled bits are modulated into complex modulation symbols by a modulator (402). The modulator may modulate the scrambled bits according to a predetermined modulation scheme to arrange them into complex modulation symbols representing positions on a signal constellation. There are no restrictions on the modulation scheme, and pi / 2-BPSK (pi / 2-Binary Phase Shift Keying), m-PSK (m-Phase Shift Keying), or m-QAM (m-Quadrature Amplitude Modulation), etc., may be used for modulating the encoded data.
[0498] The complex modulation symbol above can be mapped to one or more transmission layers by the layer mapper (403).
[0499] Complex modulation symbols on each layer can be precoded by a precoder (404) for transmission on an antenna port. Here, the precoder may perform precoding after performing transform precoding on the complex modulation symbols. Alternatively, the precoder may perform precoding without performing transform precoding. The precoder (404) may process the complex modulation symbols in a MIMO manner according to multiple transmission antennas to output antenna-specific symbols and distribute the antenna-specific symbols to the corresponding resource block mapper (405). The output z of the precoder (404) can be obtained by multiplying the output y of the layer mapper (403) by an N-X-M precoding matrix W. Here, N is the number of antenna ports and M is the number of layers.
[0500] The resource block mapper (405) maps the demodulation modulation symbol for each antenna port to the appropriate resource element within the virtual resource block allocated for transmission.
[0501] The resource block mapper (405) can assign complex modulation symbols to appropriate subcarriers and multiplex them according to the user.
[0502] The signal generator (406) can generate a complex-valued time domain Orthogonal Frequency Division Multiplexing (OFDM) symbol signal by modulating a complex modulated symbol using a specific modulation method, such as OFDM. The signal generator (406) can perform an Inverse Fast Fourier Transform (IFFT) on an antenna-specific symbol, and a Cyclic Prefix (CP) can be inserted into the time domain symbol after the IFFT is performed. The OFDM symbol is transmitted to a receiving device through each transmitting antenna after undergoing digital-to-analog conversion, frequency uplink conversion, etc. The signal generator (406) may include an IFFT module, a CP inserter, a Digital-to-Analog Converter (DAC), a frequency uplink converter, etc.
[0503] The signal processing process of the receiving device may be configured as the inverse of the signal processing process of the transmitter. Specifically, the processor of the receiving device performs decoding and demodulation for a wireless signal received from the outside through the antenna port(s) of the transmitter and receiver. The receiving device may include multiple receiving antennas, and each signal received through the receiving antennas is restored to a baseband signal, then undergoes multiplexing and MIMO demodulation to be restored to the data sequence that the transmitting device originally intended to transmit. The receiving device (1820) may include a signal restorer for restoring the received signal to a baseband signal, a multiplexer for combining and multiplexing the received processed signals, and a channel demodulator for demodulating the multiplexed signal sequence into the corresponding codeword. The signal restorer, multiplexer, and channel demodulator may be configured as a single integrated module or as separate independent modules that perform their functions. More specifically, the signal restorer may include an analog-to-digital converter (ADC) that converts an analog signal into a digital signal, a CP remover that removes CP from the digital signal, an FFT module that applies a fast Fourier transform (FFT) to the signal from which CP has been removed to output a frequency domain symbol, and a resource element demapper / equalizer that restores the frequency domain symbol to an antenna-specific symbol. The antenna-specific symbol is restored to a transport layer by a multiplexer, and the transport layer is restored to a codeword that the transmitting device intended to transmit by a channel demodulator.
[0504] FIG. 45 illustrates an example of a wireless communication device according to an embodiment of the present disclosure.
[0505] Referring to FIG. 45, a wireless communication device, for example, a terminal, may include at least one of a processor (2310), such as a digital signal processor (DSP) or a microprocessor, a transceiver (2335), a power management module (2305), an antenna (2340), a battery (2355), a display (2315), a keypad (2320), a Global Positioning System (GPS) chip (2360), a sensor (2365), a memory (2330), a Subscriber Identification Module (SIM) card (2325), a speaker (2345), and a microphone (2350). The antenna and the processor may be multiple.
[0506] The processor (2310) can implement the functions, procedures, and methods described in the present disclosure. The processor (2310) of FIG. 44 may be the processor (102, 202) of FIG. 41.
[0507] The memory (2330) is connected to the processor (2310) and stores information related to the operation of the processor. The memory may be located inside or outside the processor and may be connected to the processor through various technologies such as wired or wireless connections. The memory (2330) of FIG. 45 may be the memory (104, 204) of FIG. 41.
[0508] The user can input various types of information, such as phone numbers, using various techniques, such as pressing a button on the keypad (2320) or using a microphone (2350) to activate sound. The processor (2310) receives and processes the user's information and can perform appropriate functions, such as making a call to the input phone number. In some scenarios, data may be retrieved from a SIM card (2325) or memory (2330) to perform appropriate functions. In some scenarios, the processor (2310) can display various types of information and data on a display (2315) for the user's convenience.
[0509] A transceiver (2335) is connected to a processor (2310) to transmit and / or receive a wireless signal, such as a Radio Frequency (RF) signal. The processor may control the transceiver to initiate communication or to transmit a wireless signal containing various types of information or data, such as voice communication data. The transceiver includes a transmitter and a receiver for transmitting and receiving wireless signals. An antenna (2340) may facilitate the transmission and reception of wireless signals. In some embodiments, when the transceiver receives a wireless signal, it may forward and convert the signal to a baseband frequency for processing by the processor. The processed signal may be processed by various techniques, such as being converted into audible or readable information to be output through a speaker (2345). The transceiver of FIG. 45 may be the transceiver (106, 206) of FIG. 41.
[0510] Although not illustrated in FIG. 45, various components such as a camera and a USB (Universal Serial Bus) port may be additionally included in the terminal. For example, the camera may be connected to the processor (2310).
[0511] FIG. 45 is merely one example of an implementation of a terminal, and is not limited thereto. The terminal is not required to include all the elements of FIG. 44. For example, some components, such as a keypad (2320), a Global Positioning System (GPS) chip (2360), a sensor (2365), and a SIM card (2325), may not be essential and, in this case, may not be included in the terminal.
[0512] FIG. 46 illustrates a communication system (1) to which the present disclosure applies.
[0513] Referring to FIG. 46, the communication system (1) to which the present disclosure applies includes a wireless device, a base station, and a network. Here, the wireless device refers to a device that performs communication using wireless access technology (e.g., 5G NR (New RAT), LTE (Long Term Evolution)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, the wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Thing) device (100f), and an AI device / server (400). For example, the vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, the vehicle may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and can be implemented in the form of HMDs (Head-Mounted Devices), HUDs (Head-Up Displays) equipped in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Portable devices may include smartphones, smartpads, wearable devices (e.g., smartwatches, smart glasses), computers (e.g., laptops, etc.). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, base stations and networks may be implemented as wireless devices, and a specific wireless device (200a) may operate as a base station / network node to other wireless devices.
[0514] Wireless devices (100a to 100f) can be connected to a network (300) through a base station (200). Artificial Intelligence (AI) technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) through the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices (100a to 100f) may communicate with each other through the base station (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without going through the base station / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).
[0515] Wireless communication / connection (150a, 150b, 150c) can be established between wireless devices (100a~100f) / base station (200) and base station (200) / base station (200). Here, wireless communication / connection can be achieved through various wireless access technologies (e.g., 5G NR), such as uplink / downlink communication (150a), sidelink communication (150b) (or D2D communication), and inter-base station communication (150c) (e.g., relay, IAB (Integrated Access Backhaul)). Through wireless communication / connection (150a, 150b, 150c), wireless devices and base stations / wireless devices, and base stations and base stations can transmit / receive wireless signals to / from each other. For example, wireless communication / connection (150a, 150b, 150c) can transmit / receive signals through various physical channels. To this end, based on various proposals of the present disclosure, at least some of the following may be performed: various configuration information setting processes for transmitting / receiving wireless signals, various signal processing processes (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), resource allocation processes, etc.
[0516] The claims described in this disclosure may be combined in various ways. For example, the technical features of the method claims of this disclosure may be combined to be implemented as a device, and the technical features of the device claims of this disclosure may be combined to be implemented as a method. Additionally, the technical features of the method claims of this disclosure and the technical features of the device claims of this disclosure may be combined to be implemented as a device, and the technical features of the method claims of this disclosure and the technical features of the device claims of this disclosure may be combined to be implemented as a method.
Claims
In terms of method, The terminal receives system information from the base station; and The above terminal performs a random access process with the base station based on the above system information, A method characterized in that the above system information includes information related to the combination of multiple beams for multiple carriers included in a single cell. A method according to claim 1, characterized in that the information related to the combination includes relation information between two or more beams among the plurality of beams. A method according to claim 2, wherein the relationship information comprises information indicating the association relationship between specific beams corresponding to different carrier waves. A method according to claim 2, wherein the terminal selects a random access occasion (RO) for performing the random access process based on the relationship information. A method according to claim 1, wherein the system information includes information related to the priority among the plurality of beams. A method according to claim 5, wherein the terminal selects a random access occasion (RO) for performing the random access process based on information related to the priority. A method according to claim 1, wherein the information related to the combination includes information regarding a combination of beams that can be transmitted or received by the terminal. A method according to claim 7, wherein the information related to the combination comprises information related to at least one of a random access occasion (RO) corresponding to each of the beams that can be transmitted or received by the terminal, or an RO corresponding to the combination of the beams that can be transmitted or received. A method according to claim 1, wherein the terminal performs downlink reception based on the random access process, and the downlink reception is performed based on one or more of the plurality of carriers. A method according to claim 9, wherein the uplink transmission during the random access process is performed based on one of the plurality of carriers. A method according to claim 1, wherein the random access process is performed through i) a random access occasion (RO) corresponding to one beam among the plurality of beams or ii) an RO corresponding to a combination of two or more beams. A method according to claim 1, wherein the system information includes information related to reception level reference conditions for a plurality of beams. A method according to claim 12, wherein the terminal selects a random access occasion (RO) for performing the random access process based on information related to the reception level reference condition. A method according to claim 1, wherein the random access process comprises the terminal transmitting a preamble to the base station, the terminal receiving a random access response (RAR) including an uplink grant from the base station, the terminal transmitting message 3 (Msg3) to the base station based on the uplink grant, and monitoring contention resolution. The terminal (user equipment: UE) is, At least one transmitter / receiver; At least one memory; and The above includes at least one transceiver and at least one processor connected to the above at least one memory, The above at least one memory includes instructions that are executed by the above at least one processor to perform operations, wherein The above operations are: Receive system information from a base station; and Based on the above system information, perform a random access process with the above base station, A device characterized in that the above system information includes information related to the combination of multiple beams for multiple carriers included in a single cell. A method according to claim 1, characterized in that the information related to the combination includes relation information between two or more beams among the plurality of beams. A method according to claim 16, wherein the relationship information comprises information indicating the association between specific beams corresponding to different carrier waves. A method according to claim 16, wherein the terminal selects a random access occasion (RO) for performing the random access process based on the relationship information. A method according to claim 1, wherein the system information includes information related to the priority among the plurality of beams. A method according to claim 19, wherein the terminal selects a random access occasion (RO) for performing the random access process based on information related to the priority. A method according to claim 1, wherein the information related to the combination includes information regarding a combination of beams that can be transmitted or received by the terminal. A method according to claim 21, wherein the information related to the combination comprises information related to at least one of a random access occasion (RO) corresponding to each of the beams that can be transmitted or received by the terminal, or an RO corresponding to the combination of the beams that can be transmitted or received. A method according to claim 1, wherein the terminal performs downlink reception based on the random access process, and the downlink reception is performed based on one or more of the plurality of carriers. A method according to claim 23, wherein the uplink transmission during the random access process is performed based on one of the plurality of carriers. A method according to claim 1, wherein the random access process is performed through i) a random access occasion (RO) corresponding to one beam among the plurality of beams or ii) an RO corresponding to a combination of two or more beams. A method according to claim 1, wherein the system information includes information related to reception level reference conditions for a plurality of beams. In claim 26, the method is characterized in that the terminal selects a random access occasion (RO) for performing the random access process based on information related to the reception level reference condition. A method according to claim 1, wherein the random access process comprises the terminal transmitting a preamble to the base station, the terminal receiving a random access response (RAR) including an uplink grant from the base station, the terminal transmitting message 3 (Msg3) to the base station based on the uplink grant, and monitoring contention resolution. The device, At least one memory; and The above includes at least one processor operably coupled with at least one memory, The above at least one memory includes instructions that are executed by the above at least one processor to enable the terminal to perform operations, wherein The above operations are: Receive system information from a base station; and Based on the above system information, perform a random access process with the above base station, A device characterized in that the above system information includes information related to the combination of multiple beams for multiple carriers included in a single cell. At least one computer-readable storage medium (CRM) comprising instructions executed by at least one processor to cause a terminal to perform operations, The above operations are: Receive system information from a base station; and Based on the above system information, perform a random access process with the above base station, The above system information is characterized by including information related to the combination of multiple beams for multiple carriers included in a single cell. In terms of method, A base station transmits system information to a terminal (user equipment: UE); and The above base station performs a random access process with the terminal based on the above system information, A method characterized in that the above system information includes information related to the combination of multiple beams for multiple carriers included in a single cell. The base station is, At least one transmitter / receiver; At least one memory; and The above includes at least one transceiver and at least one processor connected to the above at least one memory, The above at least one memory includes instructions that are executed by the above at least one processor to perform operations, wherein The above operations are: Transmit system information to a terminal (user equipment: UE); and Based on the above system information, a random access process is performed with the above terminal, A device characterized in that the above system information includes information related to the combination of multiple beams for multiple carriers included in a single cell.
