Method and apparatus for stopping wireless access network-based notification area update for mobile integrated access and backhaul node in wireless communication system
The control signal processing method addresses the congestion issue during RNAU by optimizing the RANU procedure for multiple terminals within the mobile IAB cell, ensuring smooth communication during changes in cell configuration and settings due to mobile IAB node movement.
Patent Information
- Application Number
- PCT/KR2024/006270
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-18
- Filing Date
- 2024-05-09
- Publication Date
- 2024-11-21
AI Technical Summary
During the migration of distributed units due to the movement of mobile Integrated Access and Backhaul (IAB) nodes, cell configuration and settings may change, leading to congestion in radio resources when multiple inactive terminals simultaneously perform Radio Access Network (RAN)-based Notification Area Updates (RNAU), disrupting smooth communication.
A control signal processing method that receives and processes a first control signal from a base station, generating a second control signal to prevent wireless section congestion by optimizing the RANU procedure for multiple terminals within the mobile IAB cell.
This method effectively prevents wireless section congestion during RANU of multiple terminals, ensuring smooth communication by optimizing the RNAU process, even during changes in cell configuration and settings caused by mobile IAB node movement.
Smart Images

Figure KR2024006270_21112024_PF_FP_ABST
Abstract
Description
Method and device for stopping wireless access network-based notification area updates for mobile integrated access and backhaul nodes in a wireless communication system
[0001] The present disclosure relates to a method and device for performing the same on a terminal in a mobile communication system. Specifically, the present disclosure relates to updating a Radio Access Network (RAN)-based Notification Area (RNA) of access terminals according to the movement of a mobile IAB node.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.
[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.
[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.
[0005] In addition, standardization of radio interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover (CHO) and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.
[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).
[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.
[0008] As described above and with the development of mobile communication systems, various services have become available, and methods for effectively providing these services are required.
[0009] When a distributed unit (DU) migrates due to the movement of a mobile IAB (mIAB) node, the cell configuration and settings may change, and the RAN-based Notification Area code may also change simultaneously. In this situation, if multiple inactive terminals simultaneously perform the RAN-based Notification Area Update (RNAU) procedure, wireless resource congestion may occur, hindering smooth communication.
[0010] In order to solve the above-described problem, a method for processing a control signal in a wireless communication system according to an embodiment of the present disclosure may be characterized by including the steps of: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.
[0011] A method and device according to an embodiment of the present disclosure can prevent radio section congestion according to RANU of a plurality of terminals within an mIAB cell.
[0012] Figure 1 is a diagram illustrating the structure of an LTE system.
[0013] Figure 2 is a diagram showing the wireless protocol structure of an LTE system.
[0014] Figure 3 is a diagram illustrating the structure of a wireless communication system.
[0015] FIG. 4 is a diagram illustrating a wireless protocol structure of a wireless communication system according to an embodiment of the present disclosure.
[0016] FIG. 5 is a block diagram illustrating the internal structure of a terminal according to an embodiment of the present disclosure.
[0017] FIG. 6 is a block diagram showing the configuration of an NR base station according to an embodiment of the present disclosure.
[0018] Figure 7 illustrates the process involved in the movement of an mIAB node.
[0019] FIG. 8 illustrates a process related to DU migration of mIAB according to one embodiment of the present disclosure.
[0020] FIG. 9 illustrates a process related to DU migration of mIAB according to one embodiment of the present disclosure.
[0021] FIG. 10 is a block diagram showing an example of a configuration of a terminal according to one embodiment of the present disclosure.
[0022] FIG. 11 is a block diagram showing an example of a configuration of a base station according to one embodiment of the present disclosure.
[0023] The operating principles of the present invention will be described in detail below with reference to the attached drawings. In the following description of the present invention, detailed descriptions of known functions or components will be omitted if they are deemed to unnecessarily obscure the gist of the invention. Furthermore, the terms described below are defined based on their functions in the present invention and may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the overall content of this specification.
[0024] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.
[0025] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. The embodiments are provided solely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined solely by the scope of the claims.
[0026] The terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, and terms referring to various identification information are provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects with equivalent technical meanings may be used.
[0027] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station. In addition, although the LTE or LTE-A system may be described below as an example, the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in a system to which the embodiments of the present disclosure may be applied, and 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications, as determined by a person skilled in the art, without significantly departing from the scope of the present disclosure. It will be appreciated that each block of the processing flow diagrams and combinations of the flow diagrams can be executed by computer program instructions.
[0028] These computer program instructions may be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus, so that the instructions executed by the processor of the computer or other programmable data processing apparatus create means for performing the functions described in the flowchart block(s). These computer program instructions may also be stored in a computer-available or computer-readable memory that can be directed to a computer or other programmable data processing apparatus to implement functions in a particular manner, so that the instructions stored in the computer-available or computer-readable memory can produce an article of manufacture that includes instruction means for performing the functions described in the flowchart block(s). The computer program instructions may also be installed on a computer or other programmable data processing apparatus, so that a series of operational steps are performed on the computer or other programmable data processing apparatus to create a computer-implemented process, so that the instructions executing on the computer or other programmable data processing apparatus can provide steps for performing the functions described in the flowchart block(s).
[0029] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for executing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions mentioned in the blocks may occur out of order. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order depending on the corresponding function. In this case, the term '~unit' used in the present embodiment means software or a hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the '~unit' may perform certain roles. However, the '~unit' is not limited to software or hardware. The '~unit' may be configured to be on an addressable storage medium and may be configured to execute one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~ units' may be implemented to reproduce one or more CPUs within a device or a secure multimedia card. Also, in an embodiment, the '~ unit' may include one or more processors.
[0030] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.
[0031] As a representative example of a broadband wireless communication system, the LTE system adopts the Orthogonal Frequency Division Multiplexing (OFDM) method in the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (or UE) transmits data or control signals to a base station (or eNB, gNB), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method distinguishes the data or control information of each user by allocating and operating the time-frequency resources to be transmitted to each user so that they do not overlap, that is, so as to achieve orthogonality.
[0032] As a future communications system beyond LTE, 5G communications systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communications systems include enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable low-latency communications (URLLC).
[0033] In one embodiment, eMBB may aim to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB should be able to provide a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from the perspective of a single base station. Furthermore, a 5G communication system may need to provide both the peak data rate and the increased user-perceived data rate of a terminal. To meet these requirements, a 5G communication system may require improvements in various transmission and reception technologies, including improved multiple-input multiple-output (MIMO) transmission technology. Furthermore, while current LTE transmits signals using a maximum 20 MHz transmission bandwidth in the 2 GHz band, a 5G communication system can use a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz band, thereby meeting the data transmission rates required by the 5G communication system.
[0034] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC may require support for large-scale terminal connections within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km^2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements, which may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC should be comprised of low-cost terminals, and since frequent battery replacement is unlikely, very long battery lifespans, such as 10 to 15 years, may be required.
[0035] Finally, URLLC is a cellular-based wireless communication service used for specific purposes (mission-critical), such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, the communication provided by URLLC may need to provide very low latency (ultra-low latency) and very high reliability (ultra-reliability). For example, a service supporting URLLC may have to satisfy an air interface latency of less than 0.5 milliseconds and may also have a requirement of a packet error rate (PER) of 10^-5 or less. Therefore, for services supporting URLLC, 5G systems may be required to provide a smaller transmission time interval (TTI) than other services, while simultaneously allocating a wide range of resources in the frequency band to ensure the reliability of the communication link.
[0036] The three services considered in the aforementioned 5G communication system—eMBB, URLLC, and mMTC—can be multiplexed and transmitted in a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters may be used between services. However, the aforementioned mMTC, URLLC, and eMBB are merely examples of different service types, and the service types applicable to this disclosure are not limited to the aforementioned examples.
[0037] For convenience of explanation, the present invention uses terms and names defined in the 5GS and NR standards, which are standards defined by the 3rd Generation Partnership Project (3GPP) among the existing communication standards. However, the present invention is not limited to the above terms and names and can be equally applied to wireless communication networks that follow other standards. For example, the present invention can be applied to the 3GPP 5GS / NR (5th generation mobile communication standard).
[0038] Figure 1 is a diagram illustrating the structure of an LTE system.
[0039] Referring to FIG. 1, as illustrated, a wireless access network of an LTE system may be composed of evolved Node Bs (eNBs) (hereinafter, referred to as Node Bs or base stations) (1-05, 1-10, 1-15, 1-20), a mobility management entity (MME) (1-25), and an S-GW (1-30, Serving-Gateway). User equipment (UEs or terminals) (1-35) may access an external network through eNBs (1-05 to 1-20) and S-GWs (1-30).
[0040] In Fig. 1, ENBs (1-05 to 1-20) may correspond to existing Node Bs of a UMTS system. ENBs are connected to UEs (1-35) via a wireless channel and may perform more complex roles than existing Node Bs. In an LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, can be serviced through a shared channel. Therefore, a device that collects status information such as buffer status, available transmission power status, and channel status of UEs and performs scheduling is required, and ENBs (1-05 to 1-20) may be responsible for this. One ENB can typically control multiple cells. For example, in order to achieve a transmission rate of 100 Mbps, an LTE system may use, for example, Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology in a 20 MHz bandwidth. Additionally, an adaptive modulation and coding (AMC) method can be applied, which determines the modulation scheme and channel coding rate according to the channel condition of the terminal. The S-GW (1-30) is a device that provides a data bearer and can create or remove a data bearer according to the control of the MME (1-25). The MME is a device that is responsible for various control functions as well as mobility management functions for the terminal and can be connected to multiple base stations.
[0041] Figure 2 is a diagram showing the wireless protocol structure of an LTE system.
[0042] Referring to Figure 2, the wireless protocol of the LTE system may be composed of Packet Data Convergence Protocol (PDCP) (2-05, 2-40), Radio Link Control (RLC) (2-10, 2-35), and Medium Access Control (MAC) (2-15, 2-30) in the terminal and ENB, respectively. PDCP may be responsible for operations such as IP header compression / decompression. The main functions of PDCP can be summarized as follows.
[0043] - Header compression and decompression (ROHC only)
[0044] - User data transfer function
[0045] - In-sequence delivery of upper layer PDUs (protocol data units) at PDCP re-establishment procedure for RLC AM
[0046] - Order reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)
[0047] - Duplicate detection function (Duplicate detection of lower layer SDUs (service data units) at PDCP re-establishment procedure for RLC AM)
[0048] - Retransmission function (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of PDCP PDUs at PDCP data-recovery procedure, for RLC AM)
[0049] - Encryption and decryption functions (Ciphering and deciphering)
[0050] - Timer-based SDU discard in uplink.
[0051] Radio Link Control (RLC) (2-10, 2-35) can perform ARQ operations, etc. by reconfiguring PDCP packet data units (PDUs) to an appropriate size. The main functions of RLC can be summarized as follows.
[0052] - Data transfer function (Transfer of upper layer PDUs)
[0053] - ARQ function (Error Correction through ARQ (only for AM data transfer))
[0054] - Concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer)
[0055] - Re-segmentation of RLC data PDUs (only for AM data transfer)
[0056] - Reordering of RLC data PDUs (only for UM and AM data transfer)
[0057] - Duplicate detection (only for UM and AM data transfer)
[0058] - Error detection function (Protocol error detection (only for AM data transfer))
[0059] - RLC SDU discard function (RLC SDU discard (only for UM and AM data transfer))
[0060] - RLC re-establishment function
[0061] MAC (2-15, 2-30) connects to multiple RLC layer devices configured in a single terminal and can perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC can be summarized as follows.
[0062] - Mapping function (Mapping between logical channels and transport channels)
[0063] - Multiplexing and demultiplexing function (Multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels)
[0064] - Scheduling information reporting function
[0065] - HARQ function (Error correction through HARQ)
[0066] - Priority handling between logical channels of one UE
[0067] - Priority handling between UEs by means of dynamic scheduling
[0068] - MBMS service identification function
[0069] - Transport format selection function
[0070] - Padding function
[0071] The physical layer (2-20, 2-25) can perform the operation of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.
[0072] Figure 3 is a diagram illustrating the structure of a wireless communication system.
[0073] Referring to FIG. 3, a wireless access network of a wireless communication system (hereinafter, may be referred to as an NR or 5G system) may be composed of a next-generation base station (e.g., a New Radio Node B) (hereinafter, may be referred to as an NR gNB or NR base station) (3-10) and a next-generation radio core network (a New Radio Core Network, NR CN) (3-05). A next-generation radio user equipment (a New Radio User Equipment, NR UE) (hereinafter, may be referred to as a terminal) (3-15) may access an external network via the NR gNB (3-10) and the NR CN (3-05).
[0074] In Fig. 3, the NR gNB (3-10) may correspond to an eNB (Evolved Node B) of an existing LTE system. The NR gNB is connected to an NR UE (3-15) via a wireless channel and can provide a service superior to that of the eNB of an existing LTE system. In the next-generation mobile communication system, all user traffic can be serviced through a shared channel. Therefore, a device that collects status information such as buffer status, available transmission power status, and channel status of UEs and performs scheduling is required, and the scheduling can be performed by the NR NB (3-10). One NR gNB can control multiple cells.
[0075] In next-generation mobile communication systems, bandwidths exceeding the maximum bandwidth of the LTE system may be applied to achieve ultra-high-speed data transmission compared to LTE. Furthermore, beamforming technology may be additionally incorporated into Orthogonal Frequency Division Multiplexing (OFDM) as a wireless access technology. Furthermore, Adaptive Modulation & Coding (AMC), which determines the modulation scheme and channel coding rate based on the channel conditions of the terminal, may be applied.
[0076] The NR CN (3-05) can perform functions such as mobility support, bearer setup, and QoS configuration. The NR CN is a device that handles not only mobility management for terminals but also various control functions, and can be connected to multiple base stations. Furthermore, the next-generation mobile communication system can also be interoperable with the LTE system, and the NR CN can be connected to the MME (3-25) via a network interface. The MME can be connected to an eNB (3-30), which is an LTE base station.
[0077] FIG. 4 is a diagram illustrating a wireless protocol structure of a wireless communication system according to an embodiment of the present disclosure.
[0078] Referring to FIG. 4, the wireless protocol of the next-generation mobile communication system consists of NR Service Data Adaptation Protocol (SDAP) (4-01, 4-45), NR PDCP (4-05, 4-40), NR RLC (4-10, 4-35), NR MAC (4-15, 4-30), and NR PHY (4-20, 4-25) in each of the terminal and NR base station.
[0079] The main functions of NR SDAP (4-01, 4-45) may include at least some of the following functions:
[0080] - Transfer of user plane data
[0081] - Mapping function between QoS flow and data bearer for both DL and UL
[0082] - QoS flow ID marking function for uplink and downlink (marking QoS flow ID in both DL and UL packets)
[0083] - Ability to map reflective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).
[0084] For SDAP layer devices, the terminal can be configured, via Radio Resource Control (RRC) messages, for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device.
[0085] When the SDAP header is set, the terminal can instruct the terminal to update or reset mapping information between QoS flows and data bearers for the uplink and downlink through a 1-bit indicator for reflecting Non-Access Stratum (NAS) Quality of Service (QoS) settings (NAS reflective QoS) and a 1-bit indicator for reflecting Access Stratum (AS) QoS settings (AS reflective QoS) in the SDAP header. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support a smooth service.
[0086] The main functions of NR PDCP (4-05, 4-40) may include at least some of the following functions:
[0087] - Header compression and decompression (ROHC only)
[0088] - User data transfer function
[0089] - In-sequence delivery of upper layer PDUs
[0090] - Out-of-sequence delivery of upper layer PDUs
[0091] - PDCP PDU reordering for reception
[0092] - Duplicate detection of lower layer SDUs
[0093] - Retransmission function (Retransmission of PDCP SDUs)
[0094] - Encryption and decryption functions (Ciphering and deciphering)
[0095] - Timer-based SDU discard in uplink.
[0096] In the above, the reordering function of the NR PDCP device may refer to a function of reordering PDCP PDUs received from a lower layer in order based on a PDCP SN (sequence number). The reordering function of the NR PDCP device may include a function of transmitting data to an upper layer in the reordered order, or a function of transmitting data directly without considering the order, a function of recording lost PDCP PDUs by reordering the order, a function of reporting a status of lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of lost PDCP PDUs.
[0097] The main features of NR RLC(4-10, 4-35) may include some of the following:
[0098] - Data transfer function (Transfer of upper layer PDUs)
[0099] - In-sequence delivery of upper layer PDUs
[0100] - Out-of-sequence delivery of upper layer PDUs
[0101] - ARQ function (Error Correction through ARQ)
[0102] - Concatenation, segmentation and reassembly of RLC SDUs
[0103] - Re-segmentation of RLC data PDUs
[0104] - Reordering of RLC data PDUs
[0105] - Duplicate detection function
[0106] - Protocol error detection
[0107] - RLC SDU discard function
[0108] - RLC re-establishment function
[0109] In the above, the in-sequence delivery function of the NR RLC device may refer to the function of sequentially delivering RLC SDUs received from the lower layer to the upper layer. If a single RLC SDU is originally received divided into multiple RLC SDUs, the in-sequence delivery function of the NR RLC device may include the function of reassembling and delivering them.
[0110] The in-sequence delivery function of the NR RLC device may include a function to reorder received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number), a function to record lost RLC PDUs by reordering them, a function to report status of lost RLC PDUs to the transmitter, and a function to request retransmission of lost RLC PDUs.
[0111] The in-sequence delivery function of the NR RLC device may include a function to sequentially deliver only the RLC SDUs up to the lost RLC SDU to the upper layer when there is a lost RLC SDU.
[0112] The in-sequence delivery function of the NR RLC device may include a function to deliver to the upper layer in sequence all RLC SDUs received before a predetermined timer starts if there are lost RLC SDUs and a predetermined timer has expired.
[0113] The in-sequence delivery function of the NR RLC device may include a function to deliver all RLC SDUs received so far to the upper layer in order if a predetermined timer has expired, even if there are lost RLC SDUs.
[0114] An NR RLC device can process RLC PDUs in the order they are received and deliver them to an NR PDCP device, regardless of the order of the sequence number (out-of-sequence delivery).
[0115] When an NR RLC device receives a segment, it can receive segments that are stored in a buffer or will be received later, reconstruct them into a complete RLC PDU, and then transmit them to the NR PDCP device.
[0116] The NR RLC layer may not include concatenation functionality, and the functionality may be performed by the NR MAC layer or replaced by the multiplexing functionality of the NR MAC layer.
[0117] In the above, the out-of-sequence delivery function of the NR RLC device may refer to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order. The out-of-sequence delivery function of the NR RLC device may include the function of reassembling and delivering the RLC SDUs when an original RLC SDU is received fragmented into multiple RLC SDUs. The out-of-sequence delivery function of the NR RLC device may include the function of storing and arranging the RLC SN or PDCP SN of the received RLC PDUs to record the lost RLC PDUs.
[0118] NR MAC (4-15, 4-30) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions.
[0119] - Mapping function (Mapping between logical channels and transport channels)
[0120] - Multiplexing / demultiplexing of MAC SDUs
[0121] - Scheduling information reporting function
[0122] - HARQ function (Error correction through HARQ)
[0123] - Priority handling between logical channels of one UE
[0124] - Priority handling between UEs by means of dynamic scheduling
[0125] - MBMS service identification function
[0126] - Transport format selection function
[0127] - Padding function
[0128] The NR PHY layer (4-20, 4-25) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.
[0129] FIG. 5 is a block diagram illustrating the structure of a terminal according to an embodiment of the present disclosure.
[0130] Referring to the above drawing, the terminal includes an RF (Radio Frequency) processing unit (5-10), a baseband processing unit (5-20), a storage unit (5-30), and a control unit (5-40).
[0131] The RF processing unit (5-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. The RF processing unit (5-10) up-converts the baseband signal provided from the baseband processing unit (5-20) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (5-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital to analog convertor (DAC), an analog to digital convertor (ADC), etc. In the drawing, only one antenna is shown, but the terminal may be equipped with multiple antennas. In addition, the RF processing unit (5-10) may include multiple RF chains. Furthermore, the RF processing unit (5-10) may perform beamforming. For the above beamforming, the RF processing unit (5-10) can adjust the phase and size of each signal transmitted and received through multiple antennas or antenna elements. In addition, the RF processing unit can perform MIMO and receive multiple layers when performing the MIMO operation.
[0132] The baseband processing unit (5-20) above performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (5-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (5-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (5-10). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (5-20) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processing unit (5-20) divides the baseband signal provided from the RF processing unit (5-10) into OFDM symbol units, restores signals mapped to subcarriers through FFT (fast Fourier transform), and then restores the received bit string through demodulation and decoding.
[0133] The baseband processing unit (5-20) and the RF processing unit (5-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (5-20) and the RF processing unit (5-10) may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit (5-20) and the RF processing unit (5-10) may include a plurality of communication modules to support a plurality of different wireless access technologies. In addition, at least one of the baseband processing unit (5-20) and the RF processing unit (5-10) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include wireless LAN (e.g., IEEE 802.11), a cellular network (e.g., LTE), etc. Additionally, the different frequency bands may include a super high frequency (SHF) (e.g., 2.NRHz, NRhz) band and a millimeter wave (mm wave) (e.g., 60GHz) band.
[0134] The storage unit (5-30) stores data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (5-30) can store information related to a second access node that performs wireless communication using a second wireless access technology. In addition, the storage unit (5-30) provides the stored data at the request of the control unit (5-40).
[0135] The control unit (5-40) controls the overall operations of the terminal. For example, the control unit (5-40) transmits and receives signals through the baseband processing unit (5-20) and the RF processing unit (5-10). In addition, the control unit (5-40) records and reads data in the storage unit (5-40). For this purpose, the control unit (5-40) may include at least one processor. For example, the control unit (5-40) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. The control unit (5-40) may include a multi-connection processing unit (5-42).
[0136] FIG. 6 is a block diagram showing the configuration of an NR base station according to an embodiment of the present disclosure.
[0137] As shown in the above drawing, the base station is configured to include an RF processing unit (6-10), a baseband processing unit (6-20), a backhaul communication unit (6-30), a storage unit (6-40), and a control unit (6-50).
[0138] The RF processing unit (6-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. The RF processing unit (6-10) up-converts the baseband signal provided from the baseband processing unit (6-20) into an RF band signal and transmits it through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processing unit (6-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. In the drawing, only one antenna is shown, but the first access node may have multiple antennas. In addition, the RF processing unit (6-10) may include multiple RF chains. Furthermore, the RF processing unit (6-10) may perform beamforming. For the beamforming, the RF processing unit (6-10) may adjust the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. The above RF processing unit can perform a downlink MIMO operation by transmitting one or more layers.
[0139] The baseband processing unit (6-20) above performs a conversion function between a baseband signal and a bit stream according to the physical layer specifications of the first wireless access technology. For example, when transmitting data, the baseband processing unit (6-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (6-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (6-10). For example, in the case of OFDM, when transmitting data, the baseband processing unit (6-20) generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through IFFT operation and CP insertion. In addition, when receiving data, the baseband processing unit (6-20) divides the baseband signal provided from the RF processing unit (6-10) into OFDM symbol units, restores the signals mapped to subcarriers through FFT operation, and then restores the received bit string through demodulation and decoding. The baseband processing unit (6-20) and the RF processing unit (6-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (6-20) and the RF processing unit (6-10) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.
[0140] The above backhaul communication unit (6-30) provides an interface for communicating with other nodes within the network. The above backhaul communication unit (6-30) converts a bit string transmitted from the main base station to other nodes, such as auxiliary base stations and core networks, into a physical signal, and converts a physical signal received from the other nodes into a bit string.
[0141] The storage unit (6-40) stores data such as basic programs, application programs, and configuration information for the operation of the main base station. In particular, the storage unit (6-40) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (6-40) can store information that serves as a judgment criterion for whether to provide or terminate multiple connections to a terminal. In addition, the storage unit (6-40) provides the stored data at the request of the control unit (6-50).
[0142] The control unit (6-50) controls the overall operations of the base station. For example, the control unit (6-50) transmits and receives signals through the baseband processing unit (6-20) and the RF processing unit (6-10) or through the backhaul communication unit (6-30). In addition, the control unit (6-50) records and reads data in the storage unit (6-40). For this purpose, the control unit (6-50) may include at least one processor. The control unit (6-50) may include a multi-connection processing unit (6-52).
[0143] Figure 7 illustrates the process involved in the movement of an mIAB node. Specifically, Figure 7 is a flowchart illustrating situations that may typically occur when an IAB node is moved.
[0144] Figure 7 assumes that Inactive terminal 1, Inactive terminal 2, and a connected terminal (Conn UE) have established camping and RRC connection to mIAB cell 1. In this case, the mIAB node can be linked to a source donor central unit (CU).
[0145] Afterwards, by the movement of the mIAB node, migration to the target donor CU is performed, and in the process, mIAB cell 1 can be turned off and mIAB cell 2 can be turned on. At this time, mIAB cell 2 can transmit SSB (SS / PBCH Block) and system information to the terminal based on the new NCGI (NR Cell Global Identifier) and PCI (Physical Cell Identity). Accordingly, inactive terminal 1 and inactive terminal 2 perform cell reselection based on mIAB cell 2, and the connected terminal (Conn UE in FIG. 7) can perform conditional handover (CHO) to mIAB cell 2 according to the settings in the existing cell (mIAB cell 1).
[0146] If the RAN-based Notification Area (RNA) of the target donor CU is different from the RNA of the source donor CU and is not included in the RNA list previously set for inactive terminal 1 or inactive terminal 2, inactive terminal 1 or inactive terminal 2 must perform a RAN update (RNAU). To do this, inactive terminal 1 or inactive terminal 2 can perform random access.
[0147] At this time, all terminals that camped together and performed cell reselection to mIAB cell2 (e.g., active terminal 1 and inactive terminal 2 in FIG. 7) and terminals in connected mode for which conditional handover was set can perform random access at relatively similar times (e.g., in FIG. 7, Tx of Random Access Preamble (RAP) or Rx of Random Access Request (RAR) can be performed within a short time interval). Accordingly, congestion may occur in random access time resources, and only a small number of terminals can succeed in random access to the network. For example, in FIG. 7, only inactive terminal 1 obtained a UL grant and transmitted an RRC message for RAN update.
[0148] To solve the above-described problem, the RNAU procedure itself at the terminal can be simplified, but it is also possible to retrieve the inactive context of the terminal between donor nodes according to the movement status of the mIAB node without performing the RNAU procedure at the terminal.
[0149] Handover of Mobile Termination (MT) and distributed unit (DU) migration due to movement of mIAB node can be performed through the following procedures.
[0150] The mIAB node consists of an mIAB DU and a MT. The MT is connected to the cell of the parent IAB node and can exchange control plane data and user plane data. The DU forms a cell for terminals receiving services from the mIAB node and can transmit DL data and receive UL data with the terminals. The DU can receive DL data and UL data to be transmitted from terminals from a donor node connected to the MT, or transmit DL data and UL data received from terminals to the donor node through the MT. The donor node can exchange DL data and UL data with the core network.
[0151] It is assumed that the wireless connection section of the MT is connected to a DU controlled by a donor node (CU1) or a donor DU controlled by CU1. In Fig. 7, the connection between the DU or donor DU and the mIAB node is omitted, and the source donor CU (i.e., donor node CU1) or the target donor CU (i.e., donor node CU2) is directly represented.
[0152] As the mIAB node moves, the DU controlled by the existing donor node CU1 or the MT connected to the cell of the donor DU may change the connection to the DU controlled by the donor node CU2 or the cell of the donor DU due to the degradation of the wireless connection section. This can be expressed as a handover of the MT of the mIAB node. The handover can be performed in a similar manner to the handover of the existing terminal. After the handover of the MT is performed, the DU of the mIAB node can also change its donor node from CU1 to CU2. This process can be called a migration of the DU.
[0153] During the DU migration process, a DU can operate two logical DUs. The source logical DU is the DU that operates the cell associated with the source donor CU (i.e., CU1), and the target logical DU is the DU that operates the cell associated with the target donor CU (i.e., CU2). The cells operated by each DU can operate at the same time, and in that case, they operate the cells through different radio physical resources. That is, the signals of the cell of the source logical DU can be transmitted and / or received through different radio physical resources, and the signals of the cell of the target logical DU can be transmitted and / or received.
[0154] During the DU migration process, the target logical DU and CU2, i.e., the target donor CU of the DU migration, and the F1 interface are set up, and after receiving the activated cell configuration information of the target logical DU from CU2, the mIAB DU starts operating the cell of the target logical DU (i.e., mIAB cell 2 in FIG. 7). At this point, the cell of the logical DU linked to the existing CU1 (e.g., cell 1 in FIG. 7) is already operating, and cell 2 is also operating, so there may be a time period in which cell 1 and cell 2 operate simultaneously for a certain period of time after cell 2 starts operating (i.e., until cell 1 stops operating).
[0155] FIG. 8 illustrates a process related to DU migration of mIAB according to one embodiment of the present disclosure. Specifically, FIG. 8 illustrates a process in which only RNA is changed without cell change during DU migration of mIAB.
[0156] Figure 8 illustrates a case where, during DU migration of an mIAB node, the donor CU changes, and the RNA changes instead of the PCI and cell frequency being the same as the cell set from the existing source donor CU. A terminal that had previously camped on a stationary cell can camp on a cell of the source logical DU of the DU of the mIAB node.
[0157] During this process, the UE performs cell reselection, selects the source logical DU cell of the mIAB node considering the radio connection status, and reads SIB1 to recognize that the cell broadcasts an mIAB cell indicator and a 1-bit indicator to suspend RNAU update. The UE, upon receiving the mIAB cell indicator and the suspending RNAU indicator, decides to camp on the cell. Afterwards, the UE compares its own RNA list with the cell's RNA information transmitted in the SIB, and if the cell's RNA is not included in the list, the UE performs an RNA update. At this time, the UE can transmit an RRCResumeRequest message to the cell using the RACH. The donor CU of the mIAB node can request UE inactive context retrieval of the UE from the last serving gNB by referring to the last serving gNB-related information (e.g., short MAC-I) of the message. The last serving gNB that receives this request can return the terminal's inactive UE context back to the donor CU of the mIAB node.
[0158] After the RNAU of the terminal, if the mIAB performs DU migration according to the movement, and as a result, a target logical DU cell is created and a new RNA code is set in the cell, the inactive context UE of the terminal can be transferred between the source donor CU and the target donor CU involved in the DU migration without the RNAU of the terminal.
[0159] For example, as in FIG. 8, a source donor CU of an mIAB DU that has retrieved a UE inactive context while camping on a stationary cell and then on an mIAB source cell can, upon or after the DU's migration, transfer the UE inactive context of at least some of the UEs for which it has retrieved the inactive UE context by performing RNAU to the mIAB cell to the target donor CU. In this case, the source donor CU can use the Xn message.
[0160] After DU migration, the mIAB target DU cell can broadcast new RNA info, RNAU suspending indicator, and mIAB cell indicator through the same PCI as before. This broadcast can be performed through SIB or SIB1.
[0161] When RNA changes through SIB, the terminal can recognize the RNA change through the system information update procedure. However, if the terminal has previously received an RNAU suspending indicator, the terminal may not perform the RNAU procedure according to the RNA change through the system information update in the cell of the same PCI.
[0162] That is, if the terminal acquires the suspending RNAU indicator and the mIAB cell indicator through SIB and camps on a cell that broadcasts the acquired suspending RNAU indicator and the mIAB cell indicator, it can perform RNAU at the camping time. However, the terminal does not perform the RNAU operation in the case of updating the RNA code of the camping cell through system information update.
[0163] Additionally, when a terminal reselects a cell from the cell it was currently camping in, it can perform an RNAU operation in that cell. For example, if the RNA information transmitted by the target cell is not included in the RNA list configured by the terminal, the terminal performs an RNAU operation.
[0164] The above can be expressed as shown in Table 1 below.
[0165]
[0166] FIG. 9 illustrates a process related to DU migration of an mIAB according to an embodiment of the present disclosure. Specifically, FIG. 9 illustrates a process in a case where DU migration of an mIAB always involves a cell change.
[0167] Figure 9 illustrates a case where, during DU migration of an mIAB node, the donor CU changes, and the PCI and cell frequencies are the same as those set by the existing source donor CU, but the RNA changes. A terminal that was previously camped on a stationary cell can camp on a cell of the source logical DU of the DU of the mIAB node.
[0168] During this process, the UE performs cell reselection, selects the source logical DU cell of the mIAB node considering the radio connection status, and reads SIB1 to recognize that the cell broadcasts an mIAB cell indicator and a 1-bit indicator to suspend (or not to suspend) RNA update. The UE, upon receiving the mIAB cell indicator and the suspending RNAU indicator, decides to camp on the cell. Afterwards, the UE compares its own RNA list with the cell's RNA information transmitted in the SIB, and if the cell's RNA is not included in the list, the UE performs an RNA update. At this time, the UE can transmit an RRCResumeRequest message to the cell using the RACH. The donor CU of the mIAB node can request UE inactive context retrieval of the UE from the last serving gNB by referring to the last serving gNB-related information (e.g., short MAC-I) of the message. The last serving gNB that receives this request can return the terminal's inactive UE context back to the donor CU of the mIAB node.
[0169] After the RNAU of the terminal, if the mIAB performs DU migration according to the movement, and as a result, a target logical DU cell is created and a new RNA code is set in the cell, the inactive context UE of the terminal can be transferred between the source donor CU and the target donor CU involved in the DU migration without the RNAU of the terminal.
[0170] For example, as in FIG. 9, a source donor CU of an mIAB DU that has retrieved a UE inactive context while camping on a stationary cell and then on an mIAB source cell can, at the time of or after the DU's migration, transfer the UE inactive context of at least some of the UEs that retrieved the inactive UE context by performing RNAU to the mIAB cell to the target donor CU. In this case, the source donor CU can use the Xn message.
[0171] The target logical DU can start operating a cell with new PCI and RNA info, which can be broadcast as system information. After this, the source logical DU can turn off the existing cell, so that the terminal can perform cell reselection to the target cell. If the SIB received by the terminal includes a suspending RNAU indicator and an mIAB cell indicator, the terminal does not perform RNAU.
[0172] That is, when the terminal performs cell reselection from a stationary cell (a cell where the mIAB cell indicator is not broadcast) to an mIAB cell, and decides to camp on that cell, if the SIB broadcast by that cell includes the mIAB cell indicator and the suspending RNAU indicator, the terminal can perform RNAU as needed. Even if the terminal reselects from that cell to another mIAB cell later, if the mIAB cell is a cell that broadcasts the suspending RNAU indicator and the mIAB cell indicator, the terminal does not perform RNAU. Here, the term "as needed" can be understood to mean that RNAU can be performed if the RNA info broadcast by the cell is not included in the RNA list that the terminal has, as in the existing RNAU performing condition.
[0173] Afterwards, the terminal does not perform RNAU when reselecting cells within the mIAB until it reselects cells to a stationary cell (a cell where the mIAB cell indicator is not broadcast) and camps.
[0174] In one embodiment, when a terminal is RRC REelase to an inactive state, the RRCrelease with suspendConfig field or the RRCReelase message may include an instruction not to perform RNAU when camping by reselecting to an mIAB cell. A terminal that receives the message and transitions to inactive may not perform RNAU when camping by reselecting to an mIAB cell.
[0175] In one embodiment, instead of a suspending RNA indicator, the absence of RNA code or RNA info transmitted in SIB1 itself may serve as a substitute for a suspending RNA indicator. A terminal that recognizes that the corresponding RNA info is not present in SIB1 may not perform RNAU, regardless of the RNA update execution conditions in FIGS. 8 and 9 above.
[0176] In FIG. 8 and FIG. 9, the terminal inactive UE context information transmitted from the source donor CU of the DU to the target donor CU through the Xn message may include the following information. The information in Table 2 below is terminal-specific information.
[0177]
[0178] FIG. 10 is a block diagram showing an example of a configuration of a terminal according to one embodiment of the present disclosure.
[0179] As illustrated in FIG. 10, the terminal of the present disclosure may include a processor (1030), a transceiver (1010), and a memory (1020). However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. Furthermore, the processor (1030), the transceiver (1010), and the memory (1020) may be implemented in the form of a single chip.
[0180] According to one embodiment, the processor (1030) may control a series of processes that enable the terminal to operate according to the embodiments of the present disclosure described above. For example, according to the embodiments of the present disclosure, the components of the terminal may be controlled to perform a transmission and reception method of the terminal depending on whether the base station mode is the base station energy saving mode or the base station normal mode. There may be one or more processors (1030), and the processors (1030) may perform transmission and reception operations of the terminal in a wireless communication system that applies the carrier bundle of the present disclosure described above by executing a program stored in the memory (1020).
[0181] The transceiver (1010) can transmit and receive signals with a base station. The signals transmitted and received with the base station can include control information and data. The transceiver (1010) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, an RF receiver that low-noise amplifies a received signal and down-converts the frequency, etc. However, the transceiver (1010) is only one embodiment, and the components of the transceiver (1010) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1010) can receive a signal through a wireless channel and output it to the processor (1030), and transmit a signal output from the processor (1030) through the wireless channel.
[0182] According to one embodiment, the memory (1020) can store programs and data necessary for the operation of the terminal. In addition, the memory (1020) can store control information or data included in signals transmitted and received by the terminal. The memory (1020) can be configured as a storage medium or a combination of storage media such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (1020). According to one embodiment, the memory (1020) can store a program for performing transmission and reception operations of the terminal depending on whether the base station mode of the embodiments of the present disclosure described above is a base station energy saving mode or a base station normal mode.
[0183] FIG. 11 is a block diagram showing an example of a configuration of a base station according to one embodiment of the present disclosure.
[0184] As illustrated in FIG. 11, the base station of the present disclosure may include a processor (1130), a transceiver (1110), and a memory (1120). However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. Furthermore, the processor (1130), the transceiver (1110), and the memory (1120) may be implemented in the form of a single chip.
[0185] The processor (1130) may control a series of processes so that the base station can operate according to the above-described embodiment of the present disclosure. For example, the processor may control components of the base station to perform a method for scheduling a terminal according to whether the base station mode is the base station energy saving mode or the base station normal mode according to the embodiment of the present disclosure. There may be one or more processors (1130), and the processors (1130) may execute a program stored in the memory (1120) to perform the method for scheduling a terminal according to whether the base station mode of the above-described present disclosure is the base station energy saving mode or the base station normal mode.
[0186] The transceiver (1110) can transmit and receive signals with the terminal. The signals transmitted and received with the terminal can include control information and data. The transceiver (1110) can be configured with an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, an RF receiver that low-noise amplifies the received signal and down-converts the frequency, etc. However, the transceiver (1110) is only one embodiment, and the components of the transceiver (1110) are not limited to the RF transmitter and RF receiver. In addition, the transceiver (1110) can receive a signal through a wireless channel and output it to the processor (1130), and transmit a signal output from the processor (1130) through the wireless channel.
[0187] According to one embodiment, the memory (1120) can store programs and data required for the operation of the base station. In addition, the memory (1120) can store control information or data included in signals transmitted and received by the base station. The memory (1120) can be configured as a storage medium or a combination of storage media, such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD. In addition, there can be a plurality of memories (1120). According to one embodiment, the memory (1120) can store a program for performing a method for scheduling a terminal depending on whether the base station mode, which is an embodiment of the present disclosure described above, is a base station energy saving mode or a base station normal mode.
[0188] The methods according to the embodiments described in the claims or specification of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software.
[0189] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present invention.
[0190] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.
[0191] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present invention via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present invention.
[0192] In the specific embodiments of the present invention described above, components included in the invention are expressed in the singular or plural form depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present invention is not limited to singular or plural components. Even components expressed in the plural form may be composed of singular elements, or even components expressed in the singular form may be composed of plural elements.
[0193] While the detailed description of the present invention has described specific embodiments, it is clear that various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims but also by equivalents thereof.
Claims
1. A method performed by a terminal of a wireless communication system, A step of receiving first system information from a mobile integrated access and backhaul (mIAB) node providing a first cell, wherein the first system information includes a RNA (Ran-based notification area) update stop indicator and first RNA information; Step of camping in the above first cell; A step of performing a first RNA update based on the first RNA information; and A step of receiving second system information including second RNA information from the mIAB (mobile integrated access and backhaul) node providing the second cell, If the first RNA information and the second RNA information are the same or different, the second RNA update based on the second RNA information is not performed. method.
2. In claim 1, The first system information includes a first cell identifier, the second system information includes a second cell identifier, and the first cell identifier and the second cell identifier are the same. method.
3. In claim 1, The first system information includes a first cell identifier, the second system information includes a second cell identifier, and the first cell identifier and the second cell identifier are different. method.
4. In claim 1, Further comprising the step of transmitting an RRC (radio resource control) connection resumption request message to the mIAB node, The above RRC connection resumption request message includes information related to the previous serving base station of the terminal, The first donor CU (central unit) for the first cell receives the inactive UE context of the terminal from the previous serving base station based on the information related to the previous serving base station. method.
5. In claim 4, The first donor CU transfers the inactive UE context to the second donor CU for the second cell. method.
6. A method performed by a mIAB (mobile integrated access and backhaul) node in a wireless communication system, A step of transmitting first system information including first RNA information to a terminal through a first cell; A step of generating a second cell generated based on the movement of the above mIAB node; and Comprising a step of transmitting second system information including second RNA information to the terminal through the second cell, The above first system information further includes an RNA (Ran-based notification area) update stop indicator, A first RNA update is performed based on the above first RNA information, If the first RNA information and the second RNA information are the same or different, the second RNA update based on the second RNA information is not performed. method.
7. In claim 6, The first system information includes a first cell identifier, the second system information includes a second cell identifier, and the first cell identifier and the second cell identifier are the same. method.
8. In claim 6, The first system information includes a first cell identifier, the second system information includes a second cell identifier, and the first cell identifier and the second cell identifier are different. method.
9. In claim 6, Further comprising a step of receiving an RRC (radio resource control) connection resumption request message regarding the first RNA update from the terminal, The above RRC connection resumption request message includes information related to the previous serving base station of the terminal, The first donor CU (central unit) for the first cell receives the inactive UE context of the terminal from the previous serving base station based on the information related to the previous serving base station. method.
10. In claim 9, The first donor CU transfers the inactive UE context to the second donor CU for the second cell. method.
11. In the terminal of a wireless communication system, Transmitter and receiver; and Including a control unit connected to the above transmitter and receiver, The above control unit: Receive first system information from a mobile integrated access and backhaul (mIAB) node providing the first cell, Camping in the above first cell, Performing a first RNA update based on the above first RNA information, and is configured to receive second system information including second RNA information from the mIAB (mobile integrated access and backhaul) node providing the second cell; The above first system information includes an RNA (Ran-based notification area) update stop indicator and first RNA information, If the first RNA information and the second RNA information are the same or different, the second RNA update based on the second RNA information is not performed. Terminal.
12. In claim 11, The first system information includes a first cell identifier, the second system information includes a second cell identifier, and the first cell identifier and the second cell identifier are the same or different. Terminal.
13. In claim 11, The above control unit: It is set to transmit an RRC (radio resource control) connection resumption request message to the above mIAB node, The above RRC connection resumption request message includes information related to the previous serving base station of the terminal, The first donor CU (central unit) for the first cell receives the inactive UE context of the terminal from the previous serving base station based on the information related to the previous serving base station, The first donor CU transfers the inactive UE context to the second donor CU for the second cell. Terminal.
14. In the mIAB (mobile integrated access and backhaul) node of a wireless communication system, Transmitter and receiver; and Including a control unit connected to the above transmitter and receiver, The above control unit: Transmitting first system information including first RNA information to the terminal through the first cell, Generate a second cell based on the movement of the above mIAB node, It is set to transmit second system information including second RNA information to the terminal through the second cell, The above first system information further includes an RNA (Ran-based notification area) update stop indicator, A first RNA update is performed based on the above first RNA information, If the first RNA information and the second RNA information are the same or different, the second RNA update based on the second RNA information is not performed. mIAB node.
15. In claim 14, The first system information includes a first cell identifier, the second system information includes a second cell identifier, and the first cell identifier and the second cell identifier are the same or different. mIAB node.
Citation Information
Patent Citations
Method and device for configuring ran-based notification area
US20200059851A1
KR20190102052A
