Method and device for mobility robustness optimization for voice fallback in next generation mobile communication system

By including voice fallback information in RLF reports, the method enhances network management and resilience in next-generation mobile communication systems, addressing the challenge of lacking specific data in existing systems.

WO2024232712A1PCT designated stage expired Publication Date: 2024-11-14SAMSUNG ELECTRONICS CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/006320
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-05-10
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

In next-generation mobile communication systems, voice fallback operations are hindered by the lack of specific information about voice fallback in radio link failure (RLF) reporting, which complicates network optimization for operators managing base stations.

Method used

The method involves a terminal receiving a handover command from an NR base station, selecting a suitable or acceptable LTE cell, performing an RRC connection establishment, and storing information about the handover failure and reconnection details in the VarRLF-Report for NR, including the ID of the LTE cell and time elapsed, to facilitate better network management.

Benefits of technology

This solution enables operators to effectively manage their networks by providing critical information about voice fallback, improving network resilience and performance during handover failures.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024006320_14112024_PF_FP_ABST
    Figure KR2024006320_14112024_PF_FP_ABST
Patent Text Reader

Abstract

The present invention relates to a method and device for mobility robustness optimization for voice fallback in a next generation mobile communication system, and specifically, to an operation and device in which a terminal, when making an RLF report, includes the ID of a cell to which the terminal reconnects and information about the time elapsed since the RLF.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for optimizing mobility robustness for voice fallback in next-generation mobile communication systems

[0001] The present invention relates to a method and device for optimizing mobility robustness for voice fallback in a next-generation mobile communication system, and more particularly, to an operation and device for including information on the ID of a cell to which a terminal is reconnecting and the time elapsed from the RLF when performing an RLF report.

[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 wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) 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 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] In the present invention, when voice fallback is performed, information about this is not specifically included in RLF report information, which causes difficulties in network optimization for operators managing base stations, and this is intended to be resolved.

[0009] A method for operating a terminal in a wireless communication system according to an embodiment of the present invention may include the steps of: receiving, from an NR base station, a handover command message from an NR, the handover command message including information that a target radio access technology (RAT) is set to LTE; selecting a suitable LTE cell if an available suitable LTE cell exists when a handover failure from the NR is detected, and selecting an acceptable LTE cell if an available suitable LTE cell does not exist; entering an RRC idle mode; performing an RRC connection establishment procedure for the selected LTE cell; storing a time value from the handover failure to reconnection and an ID of the LTE cell on which the RRC connection was performed in a VarRLF-Report for the NR if the LTE cell on which the RRC connection was performed is a suitable LTE cell; and storing a time value from the handover failure to reconnection in a VarRLF-Report for the NR if the LTE cell on which the RRC connection was performed is an acceptable LTE cell.

[0010] In one embodiment, if the LTE cell on which the RRC connection is performed is an acceptable LTE cell, the ID of the LTE cell on which the RRC connection is performed may not be stored in the VarRLF-Report for NR.

[0011] The handover command message from the above NR may include an indication for voice fallback.

[0012] The method of the above terminal may further include a step of storing information indicating that the VarRLF-Report for the NR is a handover for voice fallback.

[0013] The step of storing the time value from the handover failure to the reconnection or the ID of the LTE cell where the RRC connection was performed in the VarRLF-Report for the above NR may be performed when the ID of the LTE cell is not stored in the VarRLF-Report for the above NR.

[0014] The above terminal may be a terminal that supports inter-RAT RLF reporting.

[0015] The method of the terminal may further include the steps of: establishing an RRC connection with the NR base station after updating the VarRLF-Report for the NR in relation to the selected LTE cell; receiving a terminal information request message from the NR base station; and transmitting a terminal information response message including the VarRLF-Report for the NR to the NR base station.

[0016] In another embodiment of the present invention, a terminal in a wireless communication system includes a transceiver; and a control unit, wherein the control unit is configured to receive, from an NR base station, a handover command message from an NR, the handover command message including information that a target radio access technology (RAT) is set to LTE, and when a handover failure from the NR is detected, select a suitable LTE cell if an available suitable LTE cell exists, select an acceptable LTE cell if no available suitable LTE cell exists, enter an RRC idle mode, perform an RRC connection establishment procedure for the selected LTE cell, and, if the LTE cell on which the RRC connection is performed is a suitable LTE cell, store a time value from the handover failure to reconnection and an ID of the LTE cell on which the RRC connection is performed in a VarRLF-Report for the NR, and, if the LTE cell on which the RRC connection is performed is an acceptable LTE cell, store a time value from the handover failure to reconnection in a VarRLF-Report for the NR.

[0017] According to various embodiments of the present invention, in relation to voice fallback, by including information on the ID of the cell to which a terminal is reconnecting and the time elapsed from the RLF when performing an RLF report, an operator managing a base station can perform network operation more effectively through such information.

[0018] FIG. 1 is a diagram illustrating the structure of an LTE system according to one embodiment of the present invention.

[0019] FIG. 2 is a diagram illustrating a wireless protocol structure in an LTE system according to an embodiment of the present invention.

[0020] FIG. 3 is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present invention.

[0021] FIG. 4 is a diagram showing a wireless protocol structure of a next-generation mobile communication system according to an embodiment of the present invention.

[0022] FIG. 5 is a flowchart of a process in which a terminal updates radio link failure or handover failure information in an RRC connection establishment procedure after an RRC connection re-establishment procedure fails in a next-generation mobile communication system according to an embodiment of the present invention.

[0023] FIG. 6 is a flowchart of a process in which a terminal updates radio link failure or handover failure information in an RRC connection establishment procedure after an RRC connection re-establishment procedure fails in a next-generation mobile communication system according to an embodiment of the present invention.

[0024] FIG. 7 is a flowchart of a process in which a terminal updates radio link failure or handover failure information in an RRC connection establishment procedure after an RRC connection re-establishment procedure fails in a next-generation mobile communication system according to an embodiment of the present invention.

[0025] FIG. 8 is a flowchart of a process in which a terminal updates radio link failure or handover failure information in an RRC connection establishment procedure after an RRC connection re-establishment procedure fails in a next-generation mobile communication system according to an embodiment of the present invention.

[0026] FIG. 9 is a flowchart of a process in which a terminal transmits radio link failure information or handover failure information to a base station in a next-generation mobile communication system according to an embodiment of the present invention.

[0027] FIG. 10 is a flowchart of a process in which a terminal transmits radio link failure information or handover failure information to a base station in a next-generation mobile communication system according to an embodiment of the present invention.

[0028] FIG. 11 is a flowchart of a process in which a terminal updates radio link failure or handover failure information in an RRC connection establishment procedure after an RRC connection re-establishment procedure fails in a next-generation mobile communication system according to an embodiment of the present invention.

[0029] FIG. 12 is a flowchart of a process in which a terminal updates radio link failure or handover failure information in an RRC connection establishment procedure after an RRC connection re-establishment procedure fails in a next-generation mobile communication system according to an embodiment of the present invention.

[0030] FIG. 13 is a block diagram illustrating the internal structure of a terminal according to an embodiment of the present invention.

[0031] Figure 14 is a block diagram showing the configuration of an NR base station according to one embodiment of the present invention.

[0032] 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.

[0033] In the following description of the present invention, detailed descriptions of known functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present invention. Hereinafter, embodiments of the present invention will be described with reference to the attached drawings.

[0034] 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.

[0035] For convenience of explanation, the present invention uses terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP) LTE standard. However, the present invention is not limited to these terms and names and can be equally applied to systems conforming to other standards. In the present invention, the term "eNB" may be used interchangeably with "gNB" for convenience of explanation. In other words, a base station described as an eNB may also represent a gNB.

[0036] FIG. 1 is a diagram illustrating the structure of an LTE system according to one embodiment of the present invention.

[0037] Referring to FIG. 1, as illustrated, the wireless access network of the LTE system is composed of next-generation base stations (Evolved Node Bs, hereinafter ENBs, Node Bs or base stations) (1-05, 1-10, 1-15, 1-20), an MME (1-25, Mobility Management Entity) and an S-GW (1-30, Serving-Gateway). A user equipment (UE or terminal) (1-35) connects to an external network through the ENBs (1-05 to 1-20) and the S-GW (1-30).

[0038] In Fig. 1, ENBs (1-05 to 1-20) correspond to the existing Node B of the UMTS system. ENBs are connected to UEs (1-35) via a wireless channel and perform a more complex role than the existing Node B. In the LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, is serviced through a shared channel. Therefore, a device that collects status information such as the buffer status of UEs, available transmission power status, and channel status and performs scheduling is required, and this is handled by ENBs (1-05 to 1-20). One ENB typically controls multiple cells. For example, in order to implement a transmission speed of 100 Mbps, the LTE system uses, for example, orthogonal frequency division multiplexing (OFDM) as a wireless access technology in a 20 MHz bandwidth. In addition, it applies Adaptive Modulation & Coding (AMC) method that determines modulation scheme and channel coding rate according to the channel condition of the terminal. S-GW (1-30) is a device that provides data bearers and creates or removes data bearers according to the control of MME (1-25). MME is a device that is responsible for mobility management function for terminals as well as various control functions and is connected to multiple base stations.

[0039] FIG. 2 is a diagram illustrating a wireless protocol structure in an LTE system according to an embodiment of the present invention.

[0040] Referring to Figure 2, the wireless protocol of the LTE system consists of PDCP (Packet Data Convergence Protocol 2-05, 2-40), RLC (Radio Link Control 2-10, 2-35), and MAC (Medium Access Control 2-15, 2-30) in the terminal and ENB, respectively. PDCP (Packet Data Convergence Protocol) (2-05, 2-40) is responsible for operations such as IP header compression / decompression. The main functions of PDCP are summarized as follows.

[0041] - Header compression and decompression (ROHC only)

[0042] - User data transfer function

[0043] - In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM

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

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

[0046] - 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)

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

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

[0049] Radio Link Control (RLC) (2-10, 2-35) reconfigures PDCP PDUs (Packet Data Units) to an appropriate size and performs ARQ operations, etc. The main functions of RLC are summarized as follows.

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

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

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

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

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

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

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

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

[0058] - RLC re-establishment function

[0059] MAC (2-15, 2-30) connects to multiple RLC layer devices configured in a single terminal, and multiplexes RLC PDUs into MAC PDUs and demultiplexes RLC PDUs from MAC PDUs. The main functions of MAC are summarized as follows.

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

[0061] - 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)

[0062] - Scheduling information reporting function

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

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

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

[0066] - MBMS service identification function

[0067] - Transport format selection function

[0068] - Padding function

[0069] The physical layer (2-20, 2-25) performs 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 the upper layer.

[0070] FIG. 3 is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present invention.

[0071] Referring to FIG. 3, as illustrated, the wireless access network of the next-generation mobile communication system (hereinafter referred to as NR or 2g) is composed of a next-generation base station (New Radio Node B, hereinafter referred to as NR gNB or NR base station) (3-10) and an NR CN (3-05, New Radio Core Network). A user terminal (New Radio User Equipment, hereinafter referred to as NR UE or terminal) (3-15) connects to an external network through the NR gNB (3-10) and the NR CN (3-05).

[0072] In Fig. 3, the NR gNB (3-10) corresponds to the eNB (Evolved Node B) of the existing LTE system. The NR gNB is connected to the NR UE (3-15) via a wireless channel (3-20) and can provide a service that is superior to the existing Node B. In the next-generation mobile communication system, all user traffic is serviced through a shared channel, so a device that collects status information such as the buffer status of the UEs, the available transmission power status, and the channel status and performs scheduling is required, and the NR gNB (3-10) is in charge of this. One NR gNB typically controls multiple cells. In order to implement ultra-high-speed data transmission compared to the current LTE, it can have a bandwidth higher than the existing maximum, and beamforming technology can be additionally grafted using the orthogonal frequency division multiplexing (OFDM) as a wireless access technology. In addition, it applies the Adaptive Modulation & Coding (AMC) method that determines the modulation scheme and channel coding rate according to the channel condition of the terminal. NR CN (3-05) performs functions such as mobility support, bearer setup, and QoS setup. NR CN is a device that handles various control functions as well as mobility management functions for terminals and is connected to multiple base stations. In addition, the next-generation mobile communication system can also be linked with the existing LTE system, and NR CN is connected to MME (3-25) through a network interface. MME is connected to the existing base station, eNB (3-30).

[0073] FIG. 4 is a diagram showing a wireless protocol structure of a next-generation mobile communication system according to an embodiment of the present invention.

[0074] Figure 4 is a diagram showing the wireless protocol structure of a next-generation mobile communication system to which the present invention can be applied.

[0075] Referring to FIG. 4, the wireless protocol of the next-generation mobile communication system consists of NR SDAP (4-01, 4-45), NR PDCP (4-05, 4-40), NR RLC (4-10, 4-35), and NR MAC (4-15, 4-30) in the terminal and NR base station, respectively.

[0076] Key features of NR SDAP (4-01, 4-45) may include some of the following:

[0077] - Transfer of user plane data

[0078] - Mapping function between QoS flow and data bearer for both DL and UL

[0079] - QoS flow ID marking function for uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0080] - Ability to map relective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0081] For the above SDAP layer device, the terminal can be configured by RRC message 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, and when the SDAP header is configured, the terminal can be instructed to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink with the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) of 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.

[0082] The main functions of NR PDCP (4-05, 4-40) may include some of the following functions:

[0083] - Header compression and decompression (ROHC only)

[0084] - User data transfer function

[0085] - In-sequence delivery of upper layer PDUs

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

[0087] - PDCP PDU reordering for reception

[0088] - Duplicate detection of lower layer SDUs

[0089] - Retransmission function (Retransmission of PDCP SDUs)

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

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

[0092] The reordering function of the NR PDCP device above refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order, or may include a function of transmitting data directly without considering the order, may include a function of recording lost PDCP PDUs by reordering the order, may include a function of reporting the status of lost PDCP PDUs to the transmitting side, and may include a function of requesting retransmission of lost PDCP PDUs.

[0093] The main functions of NR RLC(4-10, 4-35) may include some of the following functions:

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

[0095] - In-sequence delivery of upper layer PDUs

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

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

[0098] - Concatenation, segmentation and reassembly of RLC SDUs

[0099] - Re-segmentation of RLC data PDUs

[0100] - Reordering of RLC data PDUs

[0101] - Duplicate detection function

[0102] - Protocol error detection

[0103] - RLC SDU discard function

[0104] - RLC re-establishment function

[0105] The in-sequence delivery function of the NR RLC device above refers to the function of sequentially transmitting RLC SDUs received from a lower layer to an upper layer, and may include a function of reassembling and transmitting RLC SDUs when an RLC SDU is originally received divided into multiple RLC SDUs, may include a function of reordering received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number), may include a function of recording lost RLC PDUs by reordering the sequence, may include a function of reporting the status of lost RLC PDUs to the transmitting side, may include a function of requesting retransmission of lost RLC PDUs, may include a function of sequentially transmitting only RLC SDUs up to the lost RLC SDU to an upper layer when there is a lost RLC SDU, or may include a function of sequentially transmitting all RLC SDUs received before the timer starts when a predetermined timer expires even when there is a lost RLC SDU. Or, even if there are lost RLC SDUs, if a predetermined timer has expired, it may include a function to sequentially deliver all RLC SDUs received up to the upper layer. In addition, the NR RLC device may process the RLC PDUs in the order they are received (in the order of arrival, regardless of the order of the sequence number) and deliver them to the PDCP device out of order (out-of-sequence delivery). In the case of segments, it may receive segments stored in the buffer or to be received later, reconstruct them into a single complete RLC PDU, process them, and deliver them to the PDCP device.The above NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

[0106] The out-of-sequence delivery function of the NR RLC device above refers to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order, and may include a function of reassembling and delivering RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of received RLC PDUs and arranging the order to record lost RLC PDUs.

[0107] 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.

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

[0109] - Multiplexing / demultiplexing of MAC SDUs

[0110] - Scheduling information reporting function

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

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

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

[0114] - MBMS service identification function

[0115] - Transport format selection function

[0116] - Padding function

[0117] 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.

[0118] FIG. 5 is a flowchart of a process in which a terminal updates radio link failure information or handover failure information in an RRC connection establishment procedure after an RRC connection re-establishment procedure fails in a next-generation mobile communication system according to an embodiment of the present invention.

[0119] Referring to FIG. 5, the terminal (5-01) may be in RRC connection mode (RRC_CONNECTED) by establishing an RRC connection with an NR base station (5-02) (5-05).

[0120] In step 5-10, the terminal (5-01) may transmit a terminal capability information message (UECapabilityInformation) to the base station (5-02). The message may include an indicator for an acceptable cell, which may be an indicator for cells different from the suitable cell in the VarRLF-Report. In addition, the message may include terminal capability information indicating that the terminal can store information different from the suitable cell in the VarRLF-Report.

[0121] In step 5-15, the terminal (5-01) may detect a radio link failure (RLF) for a given reason or may experience a handover failure or reconfiguration with sync failure. For example, the terminal may detect an RLF when the T310 timer expires for the currently connected primary cell (PCell, 5-02), or may receive an RRC message (e.g., RRCReconfiguration or MobilityFromNRCommand) to perform a handover from the currently connected primary cell, but a handover failure may occur when the T304 timer expires.

[0122] In step 5-20, the terminal (5-01) can store radio link failure information (when RLF is detected) or handover failure information (when handover fails) in VarRLF-Report. Specifically, the terminal can store radio link failure information or handover failure information in VarRLF-Report according to the following procedure.

[0123]

[0124]

[0125]

[0126]

[0127] For reference, the above terminal can determine rlf-Cause through the following procedure.

[0128]

[0129] In step 5-25, the terminal (5-01) may initiate an RRC connection re-establishment procedure. However, the terminal (5-01) may not successfully perform the procedure and may fail for a given reason. For example, the terminal may start the T311 timer when initiating the RRC connection re-establishment procedure, but may not select a suitable NR cell before the T311 timer expires, thereby failing the procedure.

[0130] In step 5-30, the terminal (5-01) can transition to RRC idle mode (RRC_IDLE).

[0131] At step 5-35, the terminal (5-01) can camp on an acceptable NR cell (5-03).

[0132] In step 5-40, the terminal (5-01) may perform an RRC connection establishment procedure to establish an RRC connection with an acceptable NR cell (5-03). That is, the terminal (5-01) may transmit an RRC connection establishment request message (RRCSetupRequest) to the cell (5-03). In response, the cell may transmit (5-45) an RRC connection establishment message (RRCSetup) to the terminal. Then, the terminal may apply RRCSetup to transition (5-46) to an RRC connected mode (RRC_CONNECTED). Then, the terminal may regard or determine the cell as the current PCell. In step 5-48, the terminal according to the present disclosure is proposed to perform at least one of the proposed methods (i.e., one of the methods below or a combination of some or all of the methods below) according to the following conditions.

[0133] - If radio link failure information or handover failure information is available in VarRLF-Report and the Public Land Mobile Network (Registered PLMN) registered by the UE is included in the plmn-IdentityList stored in VarRLF-Report (if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report) or if the UE has radio link failure information or handover failure information in VarRLF-Report and the acceptable cell is currently PCell

[0134] ■ If reconnectCellId in VarRLF-Report is not set after failing to perform reestablishment

[0135] ◆ If the UE supports RLF-Report for conditional handover and if chocellId in VarRLF-Report is set

[0136] ● Method 1: You can set timeUntilReconnection in VarRLF-Report to the time that elapsed since the radio link failure or handover failure experienced in the failedPCellId stored in VarRLF-Report.

[0137] ● Method 2: The timeUntilReconnection in VarRLF-Report may not be set. By not setting the above value, when the suitable cell later retrieves the VarRLF-Report from the terminal, it can be confirmed that the terminal has established an RRC connection to the acceptable cell, thereby enabling network optimization.

[0138] ● Method 3: The elapsed time information from the radio link failure or handover failure in the failedPCellId stored in the VarRLF-Report can be set to the new timeUntilReconnection for the acceptable cell in the VarRLF-Report. Through this, when the suitable cell later retrieves the VarRLF-Report from the terminal, it can confirm that the terminal has established an RRC connection with the acceptable cell, thereby enabling network optimization.

[0139] ◆ Otherwise (else)

[0140] ● Method 5: The terminal can set timeUntilReconnection in VarRLF-Report to the time that elapsed since the last radio link failure or handover failure.

[0141] ● Method 6: The timeUntilReconnection in VarRLF-Report may not be set. If the above value is not set, when the suitable cell later retrieves the VarRLF-Report from the terminal, it can confirm that the terminal has established an RRC connection to the acceptable cell, thereby enabling network optimization.

[0142] ● Method 7: The terminal can set the elapsed time since the most recent radio link failure or handover failure to a new timeUntilReconnection for the acceptable cell in the VarRLF-Report. This allows the terminal to optimize the network by confirming that the terminal has established an RRC connection with the acceptable cell when the suitable cell later retrieves the VarRLF-Report from the terminal.

[0143] ◆ The terminal can set the global cell identity and tracking area code of the current PCell to nrReconnectCellId in reconnectCellId in VarRLF-Report. In addition, the terminal can also include an indicator indicating that the corresponding cell is an acceptable cell in the VarRLF-Report. Alternatively, the terminal may not set any information in reconnectCellId of the VarRLF-Report. Through this, when a suitable cell retrieves the VarRLF-Report from the terminal in the future, it can confirm that the terminal has established an RRC connection to the acceptable cell, thereby enabling network optimization.

[0144] In relation to the above-mentioned suggestions, the base station can control which method the terminal applies through configuration. Then, the terminal can transmit (5-50) an RRC connection establishment complete message (RRCSetupComplete) to the cell. The terminal can later transmit the VarRLF-Report to a suitable cell (5-02) through a UE information procedure, and the operator managing the suitable cell can optimize the network with the information. For example, through the timeUntilReconnection information, the operator can check how long it took for the terminal, which has radio link failure information or handover failure information in the VarRLF-Report, to re-establish an RRC connection with a specific cell after an RRC connection re-establishment failure. Therefore, if the time is too long, the operator may want to operate the operator network by installing a new cell or optimizing the existing cells. Likewise, by using reconnectCellId, the operator can determine which cell the terminal will later connect to, which information can be used to decide whether to install more cells or manage the existing cells well for operator network operation. Additionally, if the terminal has set the reconnectCellId for an acceptable cell in the VarRLF-Report, it may not report the information as a suitable cell. Since the acceptable cell is not the operator to which the terminal has subscribed, sending the reconnectCellId to the operator to which the terminal has subscribed provides network operation information of other operators.

[0145] FIG. 6 is a flowchart of a process in which a terminal updates radio link failure information or handover failure information in an RRC connection establishment procedure after an RRC connection re-establishment procedure fails in a next-generation mobile communication system according to an embodiment of the present invention.

[0146] Referring to FIG. 6, the terminal (6-01) may be in RRC connection mode (RRC_CONNECTED) by establishing an RRC connection with an NR base station (6-02) (6-05).

[0147] In step 6-10, the terminal (6-01) may transmit a terminal capability information message (UECapabilityInformation) to the base station (6-02). This may be the same as the embodiment described above.

[0148] In step 6-15, the terminal (6-01) may detect a radio link failure (RLF) for a given reason or may experience a handover failure or reconfiguration with sync failure. For example, the terminal may detect an RLF when the T310 timer expires for the currently connected primary cell (PCell, 6-02), or may receive an RRC message (e.g., RRCReconfiguration or MobilityFromNRCommand) to perform a handover from the currently connected primary cell, but a handover failure may occur when the T304 timer expires.

[0149] In step 6-20, the terminal (6-01) can store radio link failure information (when RLF is detected) or handover failure information (when handover fails) in VarRLF-Report. This can follow the embodiment described above.

[0150] In step 6-25, the terminal (6-01) may initiate an RRC connection re-establishment procedure. However, the terminal (6-01) may not successfully perform the procedure and may fail for a given reason. For example, the terminal may start the T311 timer when initiating the RRC connection re-establishment procedure, but may not select a suitable NR cell before the T311 timer expires, thereby failing the procedure.

[0151] At step 6-30, the terminal (6-01) can transition to RRC idle mode (RRC_IDLE).

[0152] At step 6-35, the terminal (6-01) can camp on an acceptable LTE cell (6-03).

[0153] In step 6-40, the terminal (6-01) may perform an RRC connection establishment procedure to establish an RRC connection with an acceptable cell (6-03). That is, the terminal (6-01) may transmit an RRC connection establishment request message (RRSetupRequest) to the cell (6-03). In response, the cell may transmit (6-45) an RRC connection establishment message (RRCSetup) to the terminal. Then, the terminal may apply RRCSetup to transition (6-46) to an RRC connected mode (RRC_CONNECTED). Then, the terminal may regard or determine the cell as the current PCell. In step 6-48, the terminal according to the present disclosure is proposed to perform at least one of the proposed methods (i.e., one of the methods below or a combination of some or all of the methods below) according to the following conditions.

[0154] - If the UE supports RLF report for inter-RAT MRO EUTRA as defined in TS 38.306, and if radio link failure information or handover failure information is available in VarRLF-Report of TS 38.331 and if the Public Land Mobile Network (Registered PLMN) registered by the UE is included in plmn-IdentityList stored in VarRLF-Report of TS 38.331, or if handover failure information is included in VarRLF-Report and an acceptable cell is currently PCell.

[0155] ■ If reconnectCellId in VarRLF-Report of TS 38.331 is not set after failing to perform reestablishment after RRC connection re-establishment procedure failure

[0156] ◆ Method 1: The terminal can set timeUntilReconnection in VarRLF-Report of TS 38.331 to the time that elapsed since the last radio link failure or handover failure.

[0157] ◆ Method 2: The timeUntilReconnection in the VarRLF-Report of the TS 38.331 standard may not be set. By not setting the above value, when the suitable cell later retrieves the VarRLF-Report from the terminal, it can confirm that the terminal has established an RRC connection to the acceptable cell, thereby enabling network optimization.

[0158] ◆ Method 3: The terminal can set the elapsed time since the most recent radio link failure or handover failure in the new timeUntilReconnection field for the acceptable cell in the VarRLF-Report of the TS 38.331 standard. This allows the terminal to optimize the network by confirming that the terminal has established an RRC connection to the acceptable cell when the suitable cell later retrieves the VarRLF-Report from the terminal.

[0159] ◆ The terminal can set the global cell identity and tracking area code of the current PCell to eutraReconnectCellId in reconnectCellId in VarRLF-Report of TS 38.331 to the global cell identity and the tracking area code of the PCell. In addition, the terminal can also include an indicator indicating that the corresponding cell is an acceptable cell in the VarRLF-Report. Alternatively, the terminal may not set any information in the reconnectCellId of the VarRLF-Report. Through this, when a suitable cell retrieves the VarRLF-Report from the terminal in the future, it can confirm that the terminal has established an RRC connection to the acceptable cell, thereby enabling network optimization.

[0160] In relation to the above-mentioned suggestions, the base station can control which method the terminal applies through configuration. In addition, the terminal can transmit (6-50) an RRC connection establishment complete message (RRCConnectionSetupComplete) to the cell. The terminal can later transmit the VarRLF-Report to a suitable cell (6-02) through a UE information procedure, and the operator managing the suitable cell can optimize the network with the information. For example, through the timeUntilReconnection information, the operator can check how long it took for the terminal, which has radio link failure information or handover failure information in the VarRLF-Report, to re-establish an RRC connection with a specific cell after an RRC connection re-establishment failure. Therefore, if the time is too long, the operator may want to operate the operator network by installing a new cell or optimizing the existing cells. Likewise, by using reconnectCellId, the operator can determine which cell the terminal will later connect to, which information can be used to decide whether to install more cells or manage the existing cells well for operator network operation. Additionally, if the terminal has set the reconnectCellId for an acceptable cell in the VarRLF-Report, it may not report the information as a suitable cell. Since the acceptable cell is not the operator to which the terminal has subscribed, sending the reconnectCellId to the operator to which the terminal has subscribed provides network operation information of other operators.

[0161] FIG. 7 is a flowchart of a process in which a terminal updates radio link failure information or handover failure information in an RRC connection establishment procedure after an RRC connection re-establishment procedure fails in a next-generation mobile communication system according to an embodiment of the present invention.

[0162] Referring to FIG. 7, a terminal (7-01) may be in RRC connection mode (RRC_CONNECTED) by establishing an RRC connection with an LTE base station (7-02). The LTE base station may be connected to an EPC or may be connected to a 5GC (7-05).

[0163] In step 7-10, the terminal (7-01) may transmit a terminal capability information message (UECapabilityInformation) to the base station (7-02). The message may include an indicator for an acceptable cell, which may be an indicator for cells different from the suitable cell in the VarRLF-Report. In addition, the message may include terminal capability information indicating that the terminal can store information different from the suitable cell in the VarRLF-Report.

[0164] In step 7-15, the terminal (7-01) may detect a radio link failure (RLF) or may experience a handover failure for a given reason. For example, the terminal may detect an RLF when the T310 timer expires for the currently connected primary cell (PCell, 7-02), or may receive an RRC message (e.g., RRCConnectionReconfiguration or MobilityFromEUTRACommand such that targetRAT-Type is set to nr) to perform a handover from the currently connected primary cell, but may experience a handover failure when the T304 timer expires.

[0165] In step 7-20, the terminal (7-01) can store radio link failure information (when RLF is detected) or handover failure information (when handover fails) in VarRLF-Report. Specifically, the terminal can store radio link failure information in VarRLF-Report according to the following procedure.

[0166]

[0167]

[0168] The above terminal can store handover failure information in VarRLF-Report according to the following procedure.

[0169]

[0170]

[0171] In step 7-25, the terminal (7-01) may initiate an RRC connection re-establishment procedure. However, the terminal (7-01) may not successfully perform the procedure and may fail for a given reason. For example, the terminal may start the T311 timer when initiating the RRC connection re-establishment procedure, but may not select a suitable LTE cell before the T311 timer expires, resulting in the procedure failing.

[0172] At step 7-30, the terminal (7-01) can transition to RRC idle mode (RRC_IDLE).

[0173] At step 7-35, the terminal (7-01) can camp on an acceptable LTE cell (7-03).

[0174] In step 7-40, the terminal (7-01) may perform an RRC connection establishment procedure to establish an RRC connection with an acceptable LTE cell (7-03). That is, the terminal (7-01) may transmit an RRC connection establishment request message (RRCConnectionRequest) to the cell (7-03). In response, the cell may transmit (7-45) an RRC connection establishment message (RRCConnectionSetup) to the terminal. Then, the terminal may apply the RRCConnectionSetup to transition (7-46) to an RRC connected mode (RRC_CONNECTED). Then, the terminal may regard or determine the cell as the current PCell. In step 7-48, the terminal according to the present disclosure is proposed to perform at least one of the proposed methods (i.e., one of the methods below or a combination of some or all of the methods below) according to the following conditions.

[0175] - If the UE has radio link failure or handover failure information available in VarRLF-Report and if the Public Land Mobile Network (Registered PLMN) registered by the UE is included in the plmn-IdentityList stored in VarRLF-Report, or if the UE has radio link failure or handover failure information in VarRLF-Report and if the RPLMN is included in the plmn-IdentityList stored in VarRLF-Report,

[0176] ■ If reconnectCellId in VarRLF-Report is not set after failing to perform reestablishment

[0177] ◆ Method 1: The terminal can set timeUntilReconnection in VarRLF-Report to the time that elapsed since the last radio link failure or handover failure.

[0178] ◆ Method 2: The timeUntilReconnection in VarRLF-Report may not be set. By not setting the above value, when the suitable cell later retrieves the VarRLF-Report from the terminal, it can be confirmed that the terminal has established an RRC connection to the acceptable cell, thereby enabling network optimization.

[0179] ◆ Method 3: The terminal can set the elapsed time since the most recent radio link failure or handover failure to a new timeUntilReconnection field in the VarRLF-Report for an acceptable cell. This allows the terminal to optimize the network by confirming that the terminal has established an RRC connection with the acceptable cell when the suitable cell later retrieves the VarRLF-Report from the terminal.

[0180] ■ The terminal can set the global cell identity and tracking area code of the current PCell to eutraReconnectCellId in reconnectCellId in VarRLF-Report. In addition, the terminal can also include an indicator indicating that the corresponding cell is an acceptable cell in the VarRLF-Report. Alternatively, the terminal may not set any information in the reconnectCellId of the VarRLF-Report. Through this, when a suitable cell retrieves the VarRLF-Report from the terminal in the future, it can confirm that the terminal has established an RRC connection to the acceptable cell, thereby enabling network optimization.

[0181] In relation to the above-mentioned suggestions, the base station can control which method the terminal applies through configuration. In addition, the terminal can transmit (7-50) an RRC connection establishment complete message (RRCConnectionSetupComplete) to the cell. The terminal can later transmit the VarRLF-Report to a suitable cell (7-02) through a UE information procedure, and the operator managing the suitable cell can optimize the network with the information. For example, through the timeUntilReconnection information, the operator can check how long it took for the terminal, which has radio link failure information or handover failure information in the VarRLF-Report, to re-establish an RRC connection with a specific cell after an RRC connection re-establishment failure. Therefore, if the time is too long, the operator may want to operate the operator network by installing a new cell or optimizing the existing cells. Likewise, by using reconnectCellId, the operator can determine which cell the terminal will later connect to, which information can be used to decide whether to install more cells or manage the existing cells well for operator network operation. Additionally, if the terminal has set the reconnectCellId for an acceptable cell in the VarRLF-Report, it may not report the information as a suitable cell. Since the acceptable cell is not the operator to which the terminal has subscribed, sending the reconnectCellId to the operator to which the terminal has subscribed provides network operation information of other operators.

[0182] FIG. 8 is a flowchart of a process in which a terminal updates radio link failure information or handover failure information in an RRC connection establishment procedure after an RRC connection re-establishment procedure fails in a next-generation mobile communication system according to an embodiment of the present invention.

[0183] Referring to FIG. 8, a terminal (8-01) may be in RRC connection mode (RRC_CONNECTED) by establishing an RRC connection with an LTE base station (8-02). The LTE base station may be connected to an EPC or may be connected to a 5GC (8-05).

[0184] In step 8-10, the terminal (8-01) may transmit a terminal capability information message (UECapabilityInformation) to the base station (8-02). The message may include an indicator for an acceptable cell, which may be an indicator for cells different from the suitable cell in the VarRLF-Report. In addition, the message may include terminal capability information indicating that the terminal can store information different from the suitable cell in the VarRLF-Report.

[0185] In step 8-15, the terminal (8-01) may detect a radio link failure (RLF) or may experience a handover failure for a given reason. For example, the terminal may detect an RLF when the T310 timer expires for the currently connected primary cell (PCell, 8-02), or may receive an RRC message (e.g., RRCConnectionReconfiguration or MobilityFromEUTRACommand such that targetRAT-Type is set to nr) to perform a handover from the currently connected primary cell, but may experience a handover failure when the T304 timer expires.

[0186] In step 8-20, the terminal (8-01) can store radio link failure information (when RLF is detected) or handover failure information (when handover fails) in VarRLF-Report. This can follow the embodiment described above.

[0187] In step 8-25, the terminal (8-01) may initiate an RRC connection re-establishment procedure. However, the terminal (8-01) may not successfully perform the procedure and may fail for a given reason. For example, the terminal may start the T311 timer when initiating the RRC connection re-establishment procedure, but may not select a suitable LTE cell before the T311 timer expires, thereby failing the procedure.

[0188] At step 8-30, the terminal (8-01) can transition to RRC idle mode (RRC_IDLE).

[0189] At step 8-35, the terminal (8-01) can camp on an acceptable NR cell (8-03).

[0190] In step 8-40, the terminal (8-01) may perform an RRC connection establishment procedure to establish an RRC connection with an acceptable NR cell (8-03). That is, the terminal (8-01) may transmit an RRC connection establishment request message (RRCSetupRequest) to the cell (8-03). In response, the cell may transmit (8-45) an RRC connection establishment message (RRCSetup) to the terminal. Then, the terminal may apply RRCSetup to transition (8-46) to an RRC connected mode (RRC_CONNECTED). Then, the terminal may regard or determine the cell as the current PCell. In step 8-48, the terminal according to the present disclosure is proposed to perform at least one of the proposed methods (i.e., one of the methods below or a combination of some or all of the methods below) according to the following conditions.

[0191] - If the UE supports RLF report for inter-RAT MRO NR as defined in TS 36.306, and if radio link failure or handover failure information is available in VarRLF-Report of TS 36.331 and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331, or if the UE supports RLF report for inter-RAT MRO NR as defined in TS 36.306, and if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 36.331 and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331, If the report is supported and radio link failure information or handover failure information is in the VarRLF-Report of TS 36.331 standard and the acceptable cell is PCell

[0192] ■ If reconnectCellId in VarRLF-Report is not set after failing to perform reestablishment of RRC connection procedure

[0193] ◆ Method 1: The terminal can set timeUntilReconnection in VarRLF-Report of TS 36.331 to the time that elapsed since the last radio link failure or handover failure.

[0194] ◆ Method 2: The timeUntilReconnection in the VarRLF-Report of the TS 36.331 standard may not be set. By not setting the above value, when the suitable cell later retrieves the VarRLF-Report from the terminal, it can confirm that the terminal has established an RRC connection to the acceptable cell, thereby enabling network optimization.

[0195] ◆ Method 3: The terminal can set the time elapsed since the most recent radio link failure or handover failure in the new timeUntilReconnection field for the acceptable cell in the VarRLF-Report of the TS 36.331 standard. This allows the terminal to optimize the network by confirming that the terminal has established an RRC connection with the acceptable cell when the suitable cell later retrieves the VarRLF-Report from the terminal.

[0196] ■ The terminal can set the global cell identity and tracking area code of the current PCell to nrReconnectCellId in reconnectCellId in VarRLF-Report of TS 36.331 to the global cell identity and the tracking area code of the PCell. In addition, the terminal can also include an indicator indicating that the corresponding cell is an acceptable cell in the VarRLF-Report. Alternatively, the terminal may not set any information in the reconnectCellId of the VarRLF-Report. Through this, when a suitable cell retrieves the VarRLF-Report from the terminal in the future, it can confirm that the terminal has established an RRC connection to the acceptable cell, thereby enabling network optimization.

[0197] In relation to the above-mentioned suggestions, the base station can control which method the terminal applies through configuration. Then, the terminal can transmit (8-50) an RRC connection establishment complete message (RRCSetupComplete) to the cell. The terminal can later transmit the VarRLF-Report to a suitable cell (8-02) through a UE information procedure, and the operator managing the suitable cell can optimize the network with the information. For example, through the timeUntilReconnection information, the operator can check how long it took for the terminal, which has radio link failure information or handover failure information in the VarRLF-Report, to re-establish an RRC connection with a specific cell after an RRC connection re-establishment failure. Therefore, if the time is too long, the operator may want to operate the operator network by installing a new cell or optimizing the existing cells. Likewise, by using reconnectCellId, the operator can determine which cell the terminal will later connect to, which information can be used to decide whether to install more cells or manage the existing cells well for operator network operation. Additionally, if the terminal has set the reconnectCellId for an acceptable cell in the VarRLF-Report, it may not report the information as a suitable cell. Since the acceptable cell is not the operator to which the terminal has subscribed, sending the reconnectCellId to the operator to which the terminal has subscribed provides network operation information of other operators.

[0198] FIG. 9 is a flowchart of a process in which a terminal transmits radio link failure information or handover failure information to a base station in a next-generation mobile communication system according to an embodiment of the present invention.

[0199] Referring to FIG. 9, the terminal (9-01) may be in RRC connection mode (RRC_CONNECTED) by establishing an RRC connection with an NR base station (9-02) (9-05).

[0200] In steps 9-10, the base station (9-02) may transmit a terminal information request message (UEInformationRequest) to the terminal (9-01) for which security has been successfully activated. The message may include rlf-ReportReq set to true.

[0201] In step 9-15, if rlf-ReportReq is set to true in the terminal information request message received in step 9-10, the terminal (9-01) can transmit a terminal information response message (UEInformationResponse) to the base station (9-02) by performing the following procedure.

[0202]

[0203] The RLF-Report included in the above terminal information response message may have the following ASN.1 structure. At this time, the terminal may configure the RLF-Report by applying the above-described embodiment and include it in the terminal information response message.

[0204]

[0205] FIG. 10 is a flowchart of a process in which a terminal transmits radio link failure information or handover failure information to a base station in a next-generation mobile communication system according to an embodiment of the present invention.

[0206] Referring to FIG. 10, a terminal (10-01) may establish an RRC connection with an LTE base station (10-02) and be in RRC connected mode (RRC_CONNECTED) (10-05). An LTE base station connected to an EPC may be referred to as an eNB, and an LTE base station connected to a 5GC may be referred to as an ng-eNB.

[0207] In step 10-10, the base station (10-02) may transmit a terminal information request message (UEInformationRequest) to the terminal (10-01) for which security has been successfully activated. The message may include rlf-ReportReq set to true.

[0208] In step 10-15, if rlf-ReportReq is set to true in the terminal information request message received in step 10-10, the terminal (10-01) can transmit a terminal information response message (UEInformationResponse) to the base station (10-02) by performing the following procedure.

[0209]

[0210] The RLF-Report included in the above terminal information response message may have the following ASN.1 structure. At this time, the terminal may configure the RLF-Report by applying the above-described embodiment and include it in the terminal information response message.

[0211]

[0212]

[0213] FIG. 11 is a flowchart of a process in which a terminal updates radio link failure or handover failure information in an RRC connection establishment procedure after an RRC connection re-establishment procedure fails in a next-generation mobile communication system according to an embodiment of the present invention.

[0214] Referring to FIG. 11, the terminal (11-01) may be in RRC connection mode (RRC_CONNECTED) by establishing an RRC connection with the NR base station (1-02).

[0215] In step 11-10, the terminal (11-01) may transmit a terminal capability information message (UECapabilityInformation) to the base station (11-02). The message may include an indicator for an acceptable cell, which may be an indicator for cells different from the suitable cell of the VarRLF-Report. In addition, the message may include capability information of the terminal that indicates that it can store information different from the suitable cell of the VarRLF-Report. The message may include capability information on whether information related to voice fallback and / or emergency service fallback can be stored in the NR RLF Report.

[0216] In step 11-15, the terminal (11-01) may receive a MobilityFromNRCommand message from the base station (11-02). The message may include a targetRAT-Type set to eutra. The message may also include a voiceFallbackIndication.

[0217] In step 11-20, the terminal (11-01) may determine that a mobility from NR failure has occurred for a given reason. For example, a mobility from NR failure may be determined to have occurred if the UE does not successfully establish a connection to the target radio access technology.

[0218] In step 11-25, if the targetRAT-Type in the received MobilityFromNRCommand is set to eutra and the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA in the MobilityFromNRCommand received in step 11-15, the UE (11-01) may store handover failure information in VarRLF-Report. This may follow at least one of the embodiments described above. Additionally, if the MobilityFormNRCommand includes voiceFallbackIndication or the mobility from NR procedure is for emergency services fallback, the UE may store an indicator indicating this in the VarRLF-Report.

[0219] In step 11-30, the terminal (11-01) may attempt to select an E-UTRA cell. For reference, the terminal may attempt to select an E-UTRA cell if the MobilityFormNRCommand includes voiceFallbackIndication or if the mobility from NR procedure is for emergency services fallback.

[0220] At step 11-35, the terminal (11-01) can transition to RRC idle mode (RRC_IDLE) if a suitable LTE cell (11-03) is selected.

[0221] In step 11-40, the terminal (11-01) can perform an RRC connection establishment procedure with a suitable LTE cell (11-03). That is, the terminal can transmit an RRC connection establishment request message (RRCConnectionRequest) to the cell (11-40). In response, the cell can transmit an RRC connection setup message (RRCConnectionSetup) to the terminal (11-45). The terminal can transition to RRC connection mode (11-46) and regard the cell as a primary cell. If the following condition 1 is satisfied and the following condition 2 is satisfied accordingly, the terminal can perform the following operation 1 (11-50).

[0222] Condition 1:

[0223] - If the UE supports RLF report for inter-RAT MRO EUTRA as defined in TS 38.306, and if radio link failure or handover failure information is available in VarRLF-Report of TS 38.331 and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 38.331,

[0224] Condition 2:

[0225] - If reconnectCellId in VarRLF-Report of TS 38.331 is not set, and EPS fallback for IMS voice or emergency services fallback was triggered in NR via MobilityFromNRCommand (i.e., if steps 11-30 and 11-35 are performed to perform this step)

[0226] Action 1:

[0227] - The terminal can set timeUntilReconnection in VarRLF-Report of TS 38.331 to the time that elapsed since the last radio link failure or handover failure.

[0228] - The terminal can set the global cell identity and tracking area code of the current PCell to eutraReconnectCellId in reconnectCellId of VarRLF-Report of TS 38.331 (set eutraReconnectCellId in reconnectCellId in VarRLF-Report of TS 38.331 to the global cell identity and the tracking area code of the PCell).

[0229] In step 11-55, the terminal (11-01) can transmit an RRC connection establishment complete message (RRCConnectionSetupComplete) to the cell (11-03).

[0230] At step 11-60, the terminal may be in RRC connection mode by establishing an RRC connection with the NR base station (11-02).

[0231] In step 11-65, the NR base station (11-02) may transmit a terminal information request message (UEInformationRequest) to the terminal (11-01) for which security has been successfully activated. The message may include rlf-ReportReq set to true.

[0232] In step 11-70, the terminal (11-01) can transmit a terminal information response message (UEInformationResponse) containing the RLF-Report to the NR base station (11-02). This can follow the embodiment described above.

[0233] FIG. 12 is a flowchart of a process in which a terminal updates radio link failure information or handover failure information in an RRC connection establishment procedure after an RRC connection re-establishment procedure fails in a next-generation mobile communication system according to an embodiment of the present invention.

[0234] Referring to FIG. 12, the terminal (12-01) may be in RRC connection mode (RRC_CONNECTED) by establishing an RRC connection with an NR base station (12-02) (12-05).

[0235] In step 12-10, the terminal (12-01) may transmit a terminal capability information message (UECapabilityInformation) to the base station (12-02). This may follow the embodiment described above.

[0236] In step 12-15, the terminal (12-01) may receive a MobilityFromNRCommand message from the base station (12-02). The targetRAT-Type of the message may be set to eutra. The message may also include a voiceFallbackIndication.

[0237] In step 12-20, the terminal (12-01) may determine that a mobility from NR failure has occurred for a given reason. For example, a mobility from NR failure may be determined to have occurred if the UE does not successfully establish a connection to the target radio access technology.

[0238] In step 12-25, the UE (12-01) may store handover failure information in VarRLF-Report if the targetRAT-Type in the received MobilityFromNRCommand is set to eutra and the UE supports Radio Link Failure Report for Inter-RAT MRO EUTRA in step 12-15. This may follow at least one of the embodiments described above. Additionally, the UE may store an indicator indicating this in VarRLF-Report if the MobilityFormNRCommand includes voiceFallbackIndication or if the mobility from NR procedure is for emergency services fallback.

[0239] In step 12-30, the terminal (12-01) may attempt to select an E-UTRA cell. For reference, the terminal may attempt to select an E-UTRA cell if the MobilityFormNRCommand includes voiceFallbackIndication or if the mobility from NR procedure is for emergency services fallback.

[0240] In step 12-35, the UE (12-01) may transition to RRC idle mode (RRC_IDLE) if no suitable E-UTRA cell is available and an acceptable E-UTRA cell supporting emergency call is selected when the UE has an ongoing emergency call.

[0241] In step 12-40, the terminal (12-01) can perform an RRC connection establishment procedure with the acceptable LTE cell (12-03). That is, the terminal can transmit an RRC connection establishment request message (RRCConnectionRequest) to the cell (12-40). In response, the cell can transmit an RRC connection setup message (RRCConnectionSetup) to the terminal (12-45). The terminal can transition to RRC connection mode (12-46) and consider the cell as a primary cell. At this time, the terminal may not store any information in VarRLF-Report. Through this, the base station that later retrieves the RLF-Report from the terminal can know that the terminal selects an acceptable E-UTRA cell that supports an emergency call if the terminal does not have timeUntilReconnection and reconnectCellId and if the MobilityFormNRCommand includes voiceFallbackIndication or if the mobility from NR procedure has an indicator for emergency services fallback in the RLF-Report. Alternatively, the terminal may perform the following operation 1 (12-50) if the following condition 1 is satisfied and the following condition 2 is satisfied accordingly.

[0242] Condition 1:

[0243] - If the UE supports RLF report for inter-RAT MRO EUTRA as defined in TS 38.306, and if radio link failure or handover failure information is available in VarRLF-Report of TS 38.331 and if the Public Land Mobile Network (Registered PLMN) in which the UE is registered is included in plmn-IdentityList stored in VarRLF-Report of TS 38.331, or if the UE supports RLF report for inter-RAT MRO EUTRA as defined in TS 38.306. If it supports and radio link failure information or handover failure information is in the VarRLF-Report of TS 38.331 standard.

[0244] Condition 2:

[0245] - If reconnectCellId in VarRLF-Report of TS 38.331 is not set, and EPS fallback for IMS voice or emergency services fallback was triggered in NR via MobilityFromNRCommand (i.e., steps 12-30 and 12-35 are performed to perform this step), or EPS fallback for IMS voice was triggered via MobilityFromNRCommand, or emergenyce service fallback was triggered via MobilityFromNRCommand.

[0246] Action 1:

[0247] - The terminal can set timeUntilReconnection in VarRLF-Report of TS 38.331 to the time that elapsed since the last radio link failure or handover failure. Note that the timeUntilReconnection may also mean a new field.

[0248] Note that whether to perform the above operation 1 or not to store any information in VarRLF-Report may be determined by the base station's settings.

[0249] At step 12-55, the terminal (12-01) can transmit an RRC connection establishment complete message (RRCConnectionSetupComplete) to the cell (12-03).

[0250] At step 12-60, the terminal may be in RRC connection mode by establishing an RRC connection with the NR base station (12-02).

[0251] At step 12-65, the NR base station (12-02) may transmit a UE information request message (UEInformationRequest) to the terminal (12-01) for which security has been successfully activated. The message may include rlf-ReportReq set to true.

[0252] In step 12-70, the terminal (12-01) can transmit a terminal information response message (UEInformationResponse) containing the RLF-Report to the NR base station (12-02). This can follow the embodiment described above.

[0253] FIG. 13 is a block diagram illustrating the internal structure of a terminal according to an embodiment of the present invention.

[0254] Referring to the above drawing, the terminal includes an RF (Radio Frequency) processing unit (13-10), a baseband processing unit (13-20), a storage unit (13-30), and a control unit (13-40).

[0255] The RF processing unit (13-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (13-10) up-converts the baseband signal provided from the baseband processing unit (13-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 (13-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 (13-10) may include multiple RF chains. Furthermore, the RF processing unit (13-10) may perform beamforming. For the above beamforming, the RF processing unit (13-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 can receive multiple layers when performing the MIMO operation.

[0256] The baseband processing unit (13-20) 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 (13-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (13-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (13-10). For example, in the case of OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (13-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 (inverse fast Fourier transform) operation and CP (cyclic prefix) insertion. In addition, when receiving data, the baseband processing unit (13-20) divides the baseband signal provided from the RF processing unit (13-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.

[0257] The baseband processing unit (13-20) and the RF processing unit (13-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (13-20) and the RF processing unit (13-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 (13-20) and the RF processing unit (13-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 (13-20) and the RF processing unit (13-10) may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include a 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.

[0258] The storage unit (13-30) stores data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (13-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 (13-30) provides the stored data at the request of the control unit (13-40).

[0259] The control unit (13-40) controls the overall operations of the terminal. For example, the control unit (13-40) transmits and receives signals through the baseband processing unit (13-20) and the RF processing unit (13-10). In addition, the control unit (13-40) records and reads data in the storage unit (13-40). For this purpose, the control unit (13-40) may include at least one processor. For example, the control unit (13-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.

[0260] Figure 14 is a block diagram showing the configuration of an NR base station according to one embodiment of the present invention.

[0261] As shown in the above drawing, the base station is configured to include an RF processing unit (14-10), a baseband processing unit (14-20), a backhaul communication unit (14-30), a storage unit (14-40), and a control unit (14-50).

[0262] The RF processing unit (14-10) performs functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (14-10) up-converts the baseband signal provided from the baseband processing unit (14-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 (14-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 (14-10) may include multiple RF chains. Furthermore, the RF processing unit (14-10) may perform beamforming. For the above beamforming, the RF processing unit (14-10) can adjust the phase and size of each signal transmitted and received through multiple antennas or antenna elements. The RF processing unit can perform a downlink MIMO operation by transmitting one or more layers.

[0263] The baseband processing unit (14-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 (14-20) generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit (14-20) restores the reception bit stream by demodulating and decoding the baseband signal provided from the RF processing unit (14-10). For example, in the case of OFDM, when transmitting data, the baseband processing unit (14-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 (14-20) divides the baseband signal provided from the RF processing unit (14-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 (14-20) and the RF processing unit (14-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (14-20) and the RF processing unit (14-10) may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0264] The above backhaul communication unit (14-30) provides an interface for performing communication with other nodes within the network. That is, the backhaul communication unit (14-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.

[0265] The storage unit (14-40) stores data such as basic programs, application programs, and setting information for the operation of the main base station. In particular, the storage unit (14-40) can store information on bearers assigned to connected terminals, measurement results reported from connected terminals, and the like. In addition, the storage unit (14-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 (14-40) provides the stored data at the request of the control unit (14-50).

[0266] The control unit (14-50) controls the overall operations of the base station. For example, the control unit (14-50) transmits and receives signals through the baseband processing unit (14-20) and the RF processing unit (14-10) or through the backhaul communication unit (14-30). In addition, the control unit (14-50) records and reads data in the storage unit (14-40). For this purpose, the control unit (14-50) may include at least one processor.

[0267] The embodiments of the present invention disclosed in this specification and drawings are merely specific examples intended to facilitate easy explanation of the technical content of the present invention and aid understanding thereof, and are not intended to limit the scope of the present invention. It will be apparent to those skilled in the art that other modifications based on the technical concepts of the present invention are possible in addition to the embodiments disclosed herein.

Claims

1. In a method for operating a terminal in a wireless communication system, A step of receiving a handover command message from the NR base station, the handover command message including information that a target RAT (radio access technology) is set to LTE; When a handover failure from NR is detected, selecting a suitable LTE cell if there is an available suitable LTE cell, or selecting an acceptable LTE cell if there is no available suitable LTE cell; Step of entering RRC idle mode; Step for performing RRC connection establishment procedure for the selected LTE cell; If the LTE cell where the RRC connection is performed is a suitable LTE cell, a step of storing the time value from the handover failure to the reconnection and the ID of the LTE cell where the RRC connection is performed in the VarRLF-Report for NR; and A method comprising the step of storing a time value from the handover failure to the reconnection in a VarRLF-Report for NR, if the LTE cell on which the RRC connection is performed is an acceptable LTE cell.

2. In paragraph 1, A method in which the ID of the LTE cell on which the RRC connection is performed is not stored in the VarRLF-Report for NR if the LTE cell on which the RRC connection is performed is an acceptable LTE cell.

3. In paragraph 1, A method wherein the handover command message from the above NR includes an indication for voice fallback.

4. In paragraph 3, A method further comprising the step of storing information indicating that the VarRLF-Report for the above NR is a handover for voice fallback.

5. In paragraph 1, A method according to claim 1, wherein the step of storing the time value from the handover failure to the reconnection or the ID of the LTE cell where the RRC connection was performed in the VarRLF-Report for the NR is performed when the ID of the LTE cell is not stored in the VarRLF-Report for the NR.

6. In paragraph 1, A method wherein the above terminal is a terminal that supports inter-RAT RLF reporting.

7. In paragraph 1, After updating the VarRLF-Report for NR with respect to the selected LTE cell, a step of establishing an RRC connection with the NR base station; A step of receiving a terminal information request message from the above NR base station; and A method further comprising the step of transmitting, to the NR base station, a terminal information response message including a VarRLF-Report for the NR.

8. In a terminal operating in a wireless communication system, Transmitter and receiver; and Includes a control unit, The above control unit, Receive a handover command message from the NR base station, which includes information that the target RAT (radio access technology) is set to LTE, When a handover failure from NR is detected, a suitable LTE cell is selected if there is an available suitable LTE cell, or an acceptable LTE cell is selected if there is no available suitable LTE cell. Entering RRC idle mode, Perform the RRC connection establishment procedure for the selected LTE cell, If the LTE cell where the RRC connection is performed is a suitable LTE cell, the time value from the handover failure to reconnection and the ID of the LTE cell where the RRC connection is performed are stored in the VarRLF-Report for NR. A terminal configured to store the time value from the handover failure to the reconnection in the VarRLF-Report for NR, if the LTE cell on which the RRC connection is performed is an acceptable LTE cell.

9. In paragraph 8, The above control unit, A terminal configured not to store the ID of the LTE cell on which the RRC connection is performed in the VarRLF-Report for NR if the LTE cell on which the RRC connection is performed is an acceptable LTE cell.

10. In paragraph 8, The handover command message from the above NR includes an indication for voice fallback, the terminal.

11. In paragraph 10, The above control unit, A terminal further configured to store information indicating that the VarRLF-Report for the above NR is a handover for voice fallback.

12. In paragraph 8, The above control unit, The operation of storing the time value from the handover failure to the reconnection or the ID of the LTE cell where the RRC connection was performed in the VarRLF-Report for the above NR is further set to be performed in the case where the ID of the LTE cell is not stored in the VarRLF-Report for the above NR, the terminal.

13. In paragraph 8, The above terminal is a terminal that supports inter-RAT RLF reporting.

14. In paragraph 8, The above control unit, After updating the VarRLF-Report for NR with respect to the above selected LTE cell, an RRC connection with the NR base station is established, Receive a terminal information request message from the above NR base station, A terminal further configured to transmit a terminal information response message including a VarRLF-Report for said NR to said NR base station.

Citation Information

Patent Citations

  • Method and apparatus for performing communication in mobile communication system

    US20210092794A1

  • Improvement of Conditional Handover Parameters in 5G

    US20220201582A1

  • Method and apparatus for RRC state transition

    US20220369414A1

  • Method and device for reporting mobility history information in wireless communication system

    WO2022139416A1