Method and apparatus for reporting mobility state in wireless communication system

Abstract

The present disclosure relates to a method and apparatus for reporting a mobility state in a mobile communication system. A method for reporting a mobility state of a terminal in a mobile communication system according to one embodiment of the present disclosure may include: a step of triggering an RRC connection re-establishment procedure in a Radio Resource Control (RRC) connected mode; a step of determining a mobility state in the RRC connected mode; a step of performing cell selection to select a suitable cell; a step of transmitting an RRC Re-establishment Request message to the selected suitable cell; and a step of, when an RRC setup message is received from the suitable cell in response to the RRC Re-establishment Request, including the mobility state in an RRC connection re-establishment completion message and transmitting it to the suitable cell.

Description

Technology Field

[0001] The present disclosure relates to a method and apparatus for reporting a mobility state in a mobile communication system. Background Technology

[0002] Efforts are being made to develop improved 5G communication systems or pre-5G communication systems to meet the increasing demand for wireless data traffic following the commercialization of 4G communication systems. For this reason, 5G communication systems or pre-5G communication systems are referred to as systems beyond 4G networks or systems after LTE systems.

[0003] To achieve high data transmission rates, 5G communication systems are being considered for implementation in the mmWave band (e.g., the 60 GHz band). To mitigate path loss and increase the transmission distance of radio waves in the mmWave band, beamforming, massive MIMO, full Dimensional MIMO (FD-MIMO), array antenna, analog beamforming, and large-scale antenna technologies are being discussed for 5G communication systems.

[0004] In addition, to improve the network of the system, technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation are being developed in 5G communication systems. Furthermore, in 5G systems, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access) are being developed.

[0005] Meanwhile, the Internet is evolving from a human-centered network where humans generate and consume information into an IoT (Internet of Things) network where distributed components, such as objects, exchange and process information. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technology through connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; recently, technologies such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) are being researched for connecting objects.

[0006] In an IoT environment, intelligent IT (Internet Technology) services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT (Information Technology) and various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0007] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, Machine to Machine (M2M), and Machine Type Communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud RAN as a big data processing technology, as previously described, can also be considered an example of the convergence of 5G and IoT technologies.

[0008] As described above, with the advancement of wireless communication systems, methods and devices for reporting mobility status in mobile communication systems are required. The problem to be solved

[0009] The present disclosure provides a method and apparatus for reporting a mobility state in a mobile communication system. means of solving the problem

[0010] A method for reporting a mobility state of a terminal in a mobile communication system according to one embodiment of the present disclosure may include: triggering an RRC connection re-establishment procedure in a Radio Resource Control (RRC) connected mode; determining a mobility state in the RRC connected mode; performing cell selection to select a suitable cell; transmitting an RRC Re-establishment Request message to the selected suitable cell; and, when an RRC setup message is received from the suitable cell in response to the RRC Re-establishment Request, including the mobility state in an RRC connection re-establishment completion message and transmitting it to the suitable cell. Effects of the invention

[0011] According to one embodiment of the present disclosure, a method and apparatus for reporting a mobility state in a mobile communication system may be provided. Brief explanation of the drawing

[0012] Figure 1a is a diagram illustrating the structure of an LTE system. Figure 1b is a diagram illustrating the wireless protocol structure in an LTE system. Figure 1c is a diagram illustrating the structure of a next-generation mobile communication system. Figure 1d is a diagram showing the wireless protocol structure of a next-generation mobile communication system. FIG. 1e is a drawing illustrating a technique for collecting and reporting cell measurement information according to one embodiment of the present disclosure. FIG. 1f is a flowchart of the process of a terminal reporting a mobility state to an LTE base station in an LTE system according to one embodiment of the present disclosure. FIG. 1g is a flowchart of a process in which a terminal reports a mobility state to an NR base station in an NR system according to one embodiment of the present disclosure. FIG. 1h is a flowchart of a process in which a terminal reports a mobility state to an NR base station in an NR system according to another embodiment of the present disclosure. FIG. 1i is a diagram illustrating a terminal operation in which a terminal reports a mobility state to an NR base station in an NR system according to one embodiment of the present disclosure. FIG. 1j is a flowchart of the process in which a terminal reports a mobility state to an NR base station in an NR system according to another embodiment of the present disclosure. FIG. 1k is a diagram illustrating a terminal operation in which a terminal reports a mobility state to an NR base station in an NR system according to another embodiment of the present disclosure. FIG. 11 is a block diagram illustrating the internal structure of a terminal according to one embodiment of the present disclosure. FIG. 1m is a block diagram showing the configuration of a base station according to one embodiment of the present disclosure. Specific details for implementing the invention

[0013] Embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. In describing the embodiments, technical details that are well known in the art to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is intended to convey the essence of the present disclosure more clearly without obscuring it by omitting unnecessary explanations.

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

[0015] The advantages and features of the present disclosure and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the disclosure of 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 only by the scope of the claims. Throughout the specification, like reference numerals refer to like components.

[0016] At this point, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing the means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).

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

[0018] In this embodiment, the term "part" refers to a software or hardware component such as an FPGA (Field Programmable Gate Array) or an ASIC (Application Specific Integrated Circuit), and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Thus, as an example, the "part" includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and "parts" may be combined into a smaller number of components and "parts" or further separated into additional components and "parts." In addition, the components and 'parts' may be implemented to utilize one or more CPUs within the device or secure multimedia card. Also, in the embodiments, 'parts' may include one or more processors.

[0019] In describing the present disclosure below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the present disclosure. Embodiments of the present disclosure will be described below with reference to the attached drawings.

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

[0021] For convenience of explanation, the present disclosure uses terms and names defined in the 3GPP LTE (3rd Generation Partnership Project Long Term Evolution) standard. However, the present disclosure is not limited by the above terms and names and may be applied equally to systems conforming to other standards. In the present disclosure, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as eNB may represent a gNB. Additionally, the term terminal may refer to mobile phones, NB-IoT devices, sensors, as well as other wireless communication devices.

[0022] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. Of course, it is not limited to the above examples.

[0023] In particular, the present disclosure is applicable to 3GPP NR (5th generation mobile communication standard). Furthermore, the present disclosure is applicable to intelligent services based on 5G communication technology and IoT-related technology (e.g., smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail, security and safety-related services, etc.). In the present disclosure, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as eNB may represent a gNB. Additionally, the term terminal may refer to mobile phones, NB-IoT devices, sensors, as well as other wireless communication devices.

[0024] Wireless communication systems are evolving from providing early voice-oriented services to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards like 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.

[0025] As a representative example of a broadband wireless communication system, the LTE system employs the Orthogonal Frequency Division Multiplexing (OFDM) method for the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method for the uplink (UL). The uplink refers to a wireless link through which a terminal (User Equipment; UE or Mobile Station) transmits data or control signals to a base station (eNode B or BS; Base Station), and the downlink refers to a wireless link through which a base station transmits data or control signals to a terminal.

[0026] In addition, although embodiments of the present disclosure are described below using LTE, LTE-A, LTE Pro, or 5G (or NR, next-generation mobile communication) systems as examples, embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. Furthermore, embodiments of the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.

[0027] Figure 1a is a diagram illustrating the structure of an LTE system.

[0028] Referring to FIG. 1a, as illustrated, the wireless access network of the LTE system consists of a plurality of base stations (Evolved Node B, hereinafter ENB, Node B or base station) (1a-05, 1a-10, 1a-15, 1a-20), an MME (1a-25, Mobility Management Entity), and an S-GW (1a-30, Serving-Gateway). A user terminal (User Equipment, hereinafter UE or terminal) (1a-35) connects to an external network through the ENB (1a-05, 1a-10, 1a-15, 1a-20) and the S-GW (1a-30).

[0029] Base stations (Evolved Node B, hereinafter eNB, Node B or base station) (1a-05, 1a-10, 1a-15, 1a-20) serve as access nodes of a cellular network and provide wireless access to terminals connected to the network. That is, the base stations (1a-05, 1a-10, 1a-15, 1a-20) collect state information such as the buffer status, available transmission power status, and channel status of terminals to service the traffic of users, and perform scheduling to support the connection between the terminals and the core network (CN).

[0030] Additionally, base stations (1a-05, 1a-10, 1a-15, 1a-20) can correspond to the existing Node B of the UMTS (Universal Mobile Telecommunications System). The ENB (1a-05, 1a-10, 1a-15, 1a-20) is connected to the UE (1a-35) via a wireless channel and can perform more complex roles than the existing Node B. In an LTE system, since all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, is serviced through a shared channel, a device is required to collect status information such as the buffer status, available transmission power status, and channel status of the UEs to perform scheduling, and this is handled by the ENB (1a-05, 1a-10, 1a-15, 1a-20). Typically, a single ENB can control multiple cells. To achieve a transmission speed of 100 Mbps, the LTE system uses Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as a wireless access technology in a bandwidth of, for example, 20 MHz. In addition, it applies an Adaptive Modulation & Coding (hereinafter referred to as AMC) method that determines the modulation scheme and channel coding rate according to the channel conditions of the terminal.

[0031] The MME (1a-25) is a device responsible for various control functions as well as mobility management functions for terminals, and is connected to multiple base stations. The S-GW (1a-30) is a device that provides data bearers. The MME (1a-25) and S-GW (1a-30) can perform authentication and bearer management for terminals connected to the network, and process packets received from base stations (1a-05, 1a-10, 1a-15, 1a-20) or packets to be delivered to base stations (1a-05, 1a-10, 1a-15, 1a-20).

[0032] Figure 1b is a diagram illustrating the wireless protocol structure in an LTE system.

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

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

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

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

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

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

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

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

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

[0042] Radio Link Control (hereinafter referred to as RLC) (1b-10, 1b-35) reconstructs PDCP Packet Data Units (PDUs) into an appropriate size to perform ARQ operations, etc. The main functions of RLC are summarized as follows.

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

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

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

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

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

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

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

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

[0051] RLC re-establishment function

[0052] MAC (1b-15, 1b-30) is connected to multiple RLC layer devices configured in a terminal and performs the operation of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC are summarized as follows.

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

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

[0055] - Scheduling information reporting function

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

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

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

[0059] - MBMS service identification function

[0060] - Transport format selection function

[0061] - Padding

[0062] The physical layer (1b-20, 1b-25) performs the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0063] Although not shown in FIG. 1b, there is a Radio Resource Control (RRC) layer above the PDCP layer of the terminal and the base station, respectively, and this RRC layer can exchange connection and measurement-related setting control messages for radio resource control.

[0064] Figure 1c is a diagram illustrating the structure of a next-generation mobile communication system.

[0065] Referring to FIG. 1c, as illustrated, the wireless access network of a next-generation mobile communication system (5G or NR system) consists of a next-generation base station (New Radio Node B, hereinafter NR gNB or NR base station) (1c-10) and an NR CN (1c-05, New Radio Core Network, or NG CN: Next Generation Core Network). A user terminal (New Radio User Equipment, hereinafter NR UE or terminal) (1c-15) connects to an external network through the NR gNB (1c-10) and the NR CN (1c-05).

[0066] In FIG. 1c, the NR gNB (1c-10) corresponds to the eNB (Evolved Node B) of the LTE system. The NR gNB is connected to the NR UE (1c-15) via a wireless channel and can provide superior service compared to Node B. In next-generation mobile communication systems, since all user traffic is serviced through a shared channel, a device is required to collect status information such as the buffer status, available transmission power status, and channel status of the UEs to perform scheduling, and this is handled by the NR NB (1c-10). A single NR gNB typically controls multiple cells. To achieve ultra-high-speed data transmission compared to LTE systems, next-generation mobile communication systems (5G or NR systems) can have a maximum bandwidth greater than the existing maximum bandwidth, and can additionally apply beamforming technology by using Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as a wireless access technology. In addition, an Adaptive Modulation & Coding (AMC) method can be applied to determine the modulation scheme and channel coding rate according to the channel conditions of the terminal. The NR CN (1c-05) performs functions such as mobility support, bearer configuration, and QoS configuration. The NR CN is a device responsible for various control functions as well as mobility management functions for the terminal, and is connected to multiple base stations. Furthermore, the next-generation mobile communication system (5G or NR system) can be interconnected with the LTE system, and the NR CN (1c-05) can be connected to the MME (1c-25) via a network interface. The MME (1c-25) is connected to the existing base station eNB (1c-30).

[0067] Figure 1d is a diagram showing the wireless protocol structure of a next-generation mobile communication system.

[0068] FIG. 1d is a diagram showing the wireless protocol structure of a next-generation mobile communication system to which the present invention can be applied.

[0069] Referring to FIG. 1d, the wireless protocol of a next-generation mobile communication system (5G or NR system) consists of NR SDAP (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), NR RLC (1d-10, 1d-35), and NR MAC (1d-15, 1d-30) at the terminal and the NR base station, respectively.

[0070] The main functions of NR SDAP(1d-01, 1d-45) may include some of the following functions.

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

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

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

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

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

[0076] The main functions of NR PDCP (1d-05, 1d-40) may include some of the following functions.

[0077] Header compression and decompression (ROHC only)

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

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

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

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

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

[0083] - Retransmission of PDCP SDUs

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

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

[0086] Here, the reordering function of the NR PDCP device 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 a function of transmitting immediately without considering the order, may include a function of recording lost PDCP PDUs by reordering, 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.

[0087] The main functions of NR RLC(1d-10, 1d-35) may include some of the following functions.

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

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

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

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

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

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

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

[0095] - Duplicate detection

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

[0097] - RLC SDU discard function

[0098] RLC re-establishment function

[0099] Here, the in-sequence delivery function of the NR RLC device refers to the function of delivering RLC SDUs received from the lower layer to the upper layer in sequence. More specifically, when an original RLC SDU is received divided into multiple RLC SDUs, the system may include a function to reassemble and transmit them, a function to rearrange the received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number), a function to record the lost RLC PDUs by rearranging the order, a function to report the status of the lost RLC PDUs to the transmitting side, a function to request retransmission of the lost RLC PDUs, a function to transmit only the RLC SDUs prior to the lost RLC SDU in order to the upper layer if there is a lost RLC SDU, a function to transmit all RLC SDUs received before the timer started in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU, or a function to transmit all RLC SDUs received up to the present in order to the upper layer if a predetermined timer has expired even if there is a lost RLC SDU.

[0100] At this time, RLC PDUs may be processed in the order they are received (regardless of the order of sequence numbers, in the order of arrival) and delivered to the PDCP device out of order (out-of-sequence delivery), or in the case of segments, segments stored in a buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and this function may be performed by the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

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

[0102] The NR MAC (1d-15, 1d-30) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include some of the following functions.

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

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

[0105] - Scheduling information reporting function

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

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

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

[0109] - MBMS service identification function

[0110] - Transport format selection function

[0111] - Padding

[0112] The NR PHY layer (1d-20, 1d-25) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them over a wireless channel, or demodulating OFDM symbols received through a wireless channel and channel decoding them to transmit them to the upper layer.

[0113] FIG. 1e is a drawing illustrating a technique for collecting and reporting cell measurement information according to one embodiment of the present disclosure.

[0114] When building or optimizing a network, a Mobile Virtual Network Operator (MVNO) can measure signal strength in a typically expected service area and perform the process of deploying or readjusting base stations within the service area based on the specified signal strength. The MVNO carries signal measurement equipment in a vehicle and collects cell measurement information in a typically expected service area, which requires a significant amount of time and cost. The process of collecting the aforementioned cell measurement information generally utilizes a vehicle and is commonly referred to as a Drive Test (1e-30).

[0115] The terminal (1e-25) is equipped with a function to measure signals and transmit the measurement results to a base station in order to support operations such as cell reselection, handover, or adding a serving cell when moving between cells. Therefore, instead of a Drive Test, terminals (1e-25) within the service area can be utilized, which can be defined as MDT (Minimization of Drive Test). A mobile communication operator can set MDT operations for specific terminals through various configuration devices of the network. Additionally, terminals can collect and store signal strength information from serving cells and surrounding cells in RRC connection mode (RRC_CONNECTED), RRC idle mode (RRC_IDLE), or RRC inactive mode (RRC_INACTIVE). Furthermore, terminals can also store various information such as location information, time information, and signal quality information. The information that a terminal can store is not limited to the examples described above. Information stored in the terminal in this way can be reported to the network when the terminals are in connection mode, and this information can be transmitted to a specific server.

[0116] The aforementioned MDT operations can be broadly classified into Immediate MDT and Logged MDT.

[0117] Immediate MDT is characterized by reporting collected information to the network immediately. Since the terminal must report the collected information to the network immediately, only terminals in RRC connection mode can perform this. For example, Immediate MDT can be performed by reusing the Radio Resource Management (RRM) measurement process to support operations such as handover and adding serving cells, and additional location information, time information, etc., can be reported to the network.

[0118] Logged MDT is characterized by storing the collected information without immediately reporting it to the network, and subsequently reporting the stored information after the terminal switches to RRC connection mode. For example, a terminal in RRC idle mode or RRC disabled mode, which cannot immediately report collected information to the network, may perform Logged MDT. In one embodiment of the present disclosure, a terminal in RRC disabled mode introduced in a next-generation mobile communication system is characterized by performing Logged MDT. When a specific terminal is in RRC connection mode, the network may provide configuration information for performing Logged MDT operations to the terminal in connection mode. Additionally, the terminal may collect and store the configured information after switching to RRC idle mode or RRC disabled mode.

[0119] Table 1 below summarizes the MDT modes (Immediate MDT or Logged MDT) that a terminal can perform depending on the terminal's RRC state.

[0120] [Table 1]

[0121]

[0122] FIG. 1f is a flowchart of the process of a terminal reporting a mobility state to an LTE base station in an LTE system according to one embodiment of the present disclosure.

[0123] In one embodiment, a terminal in an LTE system may determine a mobility state in RRC idle mode or RRC disabled mode and report it to an LTE base station. The terminal may not determine a mobility state and report it to an LTE base station when maintaining an RRC connection mode.

[0124] Referring to FIG. 1f, in step 1f-05, the terminal (1f-01) may be in RRC idle mode (RRC_IDLE) or RRC disabled mode (RRC_INACTIVE).

[0125] In step 1f-10, a terminal (1f-01) in RRC idle mode or RRC disabled mode may receive or acquire System Information from a base station (1f-02). The System Information may include information for the terminal (1f-01) to perform a cell selection or cell reselection process. In one embodiment, the System Information may include parameters (speedStateReselectionPars) for determining the mobility state of the terminal (1f-01). These parameters (speedStateReselectionPars) for determining the mobility state of the terminal (1f-01) may include the following information (or parameters).

[0126] - t-Evaluation: The duration of evaluating criteria to enter mobility states. For example, one of the values ​​such as 30 seconds, 60 seconds, 120 seconds, 180 seconds, 240 seconds can be signaled.

[0127] ■ t-Evaluation is T CRmax This may mean the time used to determine the allowable number of cell reselections (This specifies the duration for evaluating the allowed amount of cell reselection(s))

[0128] - t-HystNormal: The additional duration for evaluating criteria to enter normal mobility state. For example, one of the values ​​such as 30 seconds, 60 seconds, 120 seconds, 180 seconds, 240 seconds can be signaled.

[0129] ■ t-HystNormal is T CRmaxHyst This may mean an additional time period value before the terminal can enter a normal mobility state.

[0130] - n-CellChangeMedium: The number of cell changes to enter medium mobility state. For example, it can be signaled as an integer value from 1 to 16.

[0131] ■ n-CellChangeMedium is N CR_M This may mean the maximum number of cell reselections to enter the medium mobility state.

[0132] - n-CellChangeHigh: The number of cell changes to enter high mobility state. For example, it can be signaled as an integer value from 1 to 16, and can be signaled as a value greater than n-CellChangeMedium.

[0133] ■ n-CellChangeHigh is N CR_H This may mean the maximum number of cell reselections to enter a high mobility state.

[0134] - q-HystSF: Velocity-based ScalingFator parameter

[0135] ■ sf-Medium: An additional hysteresis parameter value used in medium mobility states. For example, it can be signaled with a value of -6 dB, -4 dB, -2 dB, or 0 dB.

[0136] ■ sf-High: An additional hysteresis parameter value used in high mobility conditions. For example, it can be signaled as one of -6 dB, -4 dB, -2 dB, or 0 dB.

[0137] In step 1f-15, the RRC idle mode or RRC disabled mode terminal (1f-01) can perform a cell selection or cell re-selection process.

[0138] In step 1f-20, the RRC idle mode or RRC disabled mode terminal (1f-01) can determine a mobility state. The terminal (1f-01) can determine a mobility state based on the following predetermined conditions.

[0139] - Medium mobility state criteria

[0140] ■ T CRmax During this time, the number of cell re-selections is N CR_M Exceeding and N CR_H If it does not exceed (If number of cell reselections during time period T CRmax exceeds N CR_M and not exceeds N CR_H )

[0141] - High mobility state criteria

[0142] ■ T CRmax During this time, the number of cell re-selections is N CR_H If the number of cell reselections during time period T exceeds CRmax exceeds N CR_H )

[0143] - Normal mobility state criteria

[0144] ■ T CRmax If the criteria for either Medium or High mobility state are not met during time period T CrmaxHyst )

[0145] In step 1f-25, the terminal (1f-01) in RRC idle mode or RRC disabled mode may initiate an RRC connection establishment procedure or an RRC connection resume procedure to establish an RRC connection with the base station (1f-02). That is, in step 1f-25, the terminal (1f-01) may send an RRC connection request message (RRCConnectionRequest) or an RRC connection resume request message (RRCConnectionResumeRequest) to the base station (1f-02).

[0146] In step 1f-30, the base station (1f-02) may send an RRC connection setup message (RRCConnectionSetup) or an RRC connection resumption message (RRCConnectionResume) to the terminal (1f-01) in response to an RRC connection request message or an RRC connection resumption request message.

[0147] In step 1f-31, the terminal (1f-01) that receives an RRC connection establishment message or an RRC connection resumption message can transition to an RRC connection mode (RRC_CONNECTED).

[0148] In step 1f-35, the terminal (1f-01) in RRC connection mode may transmit an RRC connection setup complete message (RRCConnectionSetupComplete) or an RRC connection resume complete message (RRCConnectionResumeComplete) to the base station (1f-02). At this time, the RRC connection setup complete message or the RRC connection resume complete message may include the mobility status of the terminal (1f-01). For example, the RRC connection setup complete message or the RRC connection resume complete message may include a parameter indicating the mobility status of the terminal (1f-01). mobilityState ...may be included. Specifically, the mobility state immediately before the terminal (1f-01) transitions to the RRC connection mode (RRC_CONNECTED) may be included in the RRC connection setup completion message or the RRC resumption completion message. For example, the terminal (1f-01) is a parameter representing the mobility state of the terminal (1f-01). mobilityState The terminal (1f-01) can be set to the mobility state immediately before transitioning to the RRC connection mode (RRC_CONNECTED) and included in the RRC connection setup completion message or the RRC resumption completion message. mobilityState and set it to the mobility state (as specified in TS 36.304) of the UE just prior to entering RRC_CONNECTED state).

[0149] FIG. 1g is a flowchart of a process in which a terminal reports a mobility state to an NR base station in an NR system according to one embodiment of the present disclosure.

[0150] A terminal in an NR system according to one embodiment of the present disclosure may determine a mobility state in an RRC idle mode or an RRC disabled mode and report it to an NR base station. When the terminal receives an RRC setup message (RRCSetup) from a base station in response to an RRC re-establishment request message (RRCReestablishmentRequest) while maintaining an RRC connection mode, it may report the mobility state determined in the RRC idle mode or RRC disabled mode to the NR base station by including it in an RRC setup completion message (RRCSetupComplete).

[0151] Referring to Fig. 1g, in step 1f-10, the terminal (1g-01) may be in RRC idle mode (RRC_IDLE) or RRC disabled mode (RRC_INACTIVE).

[0152] In step 1g-10, a terminal (1g-01) in RRC idle mode or RRC disabled mode may receive or acquire System Information from a base station (1g-02). The System Information may include information for the terminal (1g-01) to perform a cell selection or cell reselection process. In one embodiment, the System Information may include parameters (speedStateReselectionPars) for determining the mobility state of the terminal (1g-01). These parameters (speedStateReselectionPars) for determining the mobility state of the terminal (1g-01) may include the following information (or parameters).

[0153] - t-Evaluation: The duration of evaluating criteria to enter mobility states. For example, one of the values ​​such as 30 seconds, 60 seconds, 120 seconds, 180 seconds, 240 seconds can be signaled.

[0154] ■ t-Evaluation is T CRmax This may mean the time used to determine the allowable number of cell reselections (This specifies the duration for evaluating the allowed amount of cell reselection(s))

[0155] - t-HystNormal: The additional duration for evaluating criteria to enter normal mobility state. For example, one of the values ​​such as 30 seconds, 60 seconds, 120 seconds, 180 seconds, 240 seconds can be signaled.

[0156] ■ t-HystNormal is T CRmaxHyst This may mean an additional time period value before the terminal can enter a normal mobility state.

[0157] - n-CellChangeMedium: The number of cell changes to enter medium mobility state. For example, it can be signaled as an integer value from 1 to 16.

[0158] ■ n-CellChangeMedium is N CR_M This may mean the maximum number of cell reselections to enter the medium mobility state.

[0159] - n-CellChangeHigh: The number of cell changes to enter high mobility state. For example, it can be signaled as an integer value from 1 to 16, and can be signaled as a value greater than n-CellChangeMedium.

[0160] ■ n-CellChangeHigh is N CR_H This may mean the maximum number of cell reselections to enter a high mobility state.

[0161] - q-HystSF: Velocity-based ScalingFator parameter

[0162] ■ sf-Medium: An additional hysteresis parameter value used in medium mobility states. For example, it can be signaled with a value of -6 dB, -4 dB, -2 dB, or 0 dB.

[0163] ■ sf-High: An additional hysteresis parameter value used in high mobility conditions. For example, it can be signaled as one of -6 dB, -4 dB, -2 dB, or 0 dB.

[0164] In step 1g-15, the RRC idle mode or RRC disabled mode terminal (1g-01) can perform a cell selection or cell re-selection process.

[0165] In step 1g-20, the RRC idle mode or RRC disabled mode terminal (1g-01) can determine a mobility state. The terminal (1g-01) can determine a mobility state based on the following predetermined conditions.

[0166] - Medium mobility state criteria

[0167] ■ T CRmax During this time, the number of cell re-selections is N CR_M Equal to or greater than N CR_H If it is less than or equal to (If number of cell reselections during time period T CRmax is greater than or equal to N CR_M but less than or equal to N CR_H )

[0168] - High mobility state criteria

[0169] ■ T CRmax During this time, the number of cell re-selections is N CR_H If the number of cell reselections during time period T exceeds CRmax is greater than N CR_H )

[0170] - Normal mobility state criteria

[0171] ■ T CRmax If the criteria for either Medium or High mobility state are not met during time period T CrmaxHyst ) or T CRmax During this time, the number of cell re-selections is N CR_M If the number of cell reselections during time period T is less than (If the number of cell reselections during time period T CRmax is less than N CR_M )

[0172] In step 1g-25, a terminal (1g-01) in RRC idle mode or RRC disabled mode may initiate an RRC connection establishment procedure or an RRC connection resume procedure to establish an RRC connection with a base station (1g-02). That is, in step 1g-25, the terminal (1g-01) may transmit an RRC connection request message (RRCSetupRequest) or an RRC connection resume request message (RRCResumeRequest or RRCResumeRequest1) to the base station (1g-02).

[0173] In step 1g-30, the base station (1g-02) may send an RRC connection setup message (RRCSetup) or an RRC connection resumption message (RRCResume) to the terminal (1g-01) in response to an RRC connection request message or an RRC connection resumption request message.

[0174] In step 1g-31, the terminal (1g-01) that receives an RRC connection establishment message or an RRC connection resumption message can transition to an RRC connection mode (RRC_CONNECTED).

[0175] In step 1g-35, the terminal (1g-01) in RRC connection mode may transmit an RRC connection setup completion message (RRCSetupComplete) or an RRC connection resumption completion message (RRCResumeComplete) to the base station (1g-02). At this time, the RRC connection setup completion message or the RRC connection resumption completion message may include the mobility status of the terminal (1g-01). For example, the RRC connection setup completion message or the RRC connection resumption completion message may include a parameter indicating the mobility status of the terminal (1g-01). mobilityState ...may be included. Specifically, the mobility state immediately before the terminal (1g-01) transitions to the RRC connection mode (RRC_CONNECTED) may be included in the RRC connection setup completion message or the RRC resumption completion message. For example, the terminal (1g-01) is a parameter representing the mobility state of the terminal (1g-01). mobilityState The terminal (1g-01) can be set to the mobility state immediately before transitioning to the RRC connection mode (RRC_CONNECTED) and included in the RRC connection setup completion message or the RRC resumption completion message. mobilityState and set it to the mobility state (as specified in TS 38.304) of the UE just prior to entering RRC_CONNECTED state).

[0176] In step 1g-40, an RRC connection re-establishment procedure may be triggered by the following predetermined conditions. In one embodiment, the predetermined conditions may mean at least one of the following.

[0177] - When a radio link failure (RLF) occurs for the Master Cell Group (MCG) and the T316 timer is not configured (upon detecting radio link failure of the MCG and T316 is not configured)

[0178] - In the event of re-configuration with sync failure of the MCG

[0179] - In the event of mobility from NR failure (upon mobility from NR failure)

[0180] - In the event of an RRC connection reconfiguration failure (upon an RRC connection reconfiguration failure)

[0181] - When the SRB1 or SRB2 under consideration receives an integrity check failure from lower layers, except if the integrity check failure is detected on the RRCReestablishment message)

[0182] In step 1g-40, the terminal (1g-01) in RRC connection mode can perform the following operations when the RRC connection reset procedure is initiated.

[0183] - Stop timer T310 if running

[0184] - Stop timer T312 if running

[0185] - Stop timer T304 if running

[0186] - Can drive the T311 timer.

[0187] - You can reset the MAC layer device (reset MAC)

[0188] - A cell selection process can be performed. For example, the cell selection process can be performed based on 3GPP standard document TS 38.304.

[0189] In step 1g-45, the terminal (1g-01) in RRC connection mode can select a suitable NR cell. If a suitable NR cell is selected, the terminal (1g-01) can stop the running T311 timer and start the T301 timer.

[0190] In step 1g-50, the RRC connection mode terminal (1g-01) can send an RRC connection re-establishment request message (RRCReestablishmentRequest) to a selected suitable NR cell. Here, the suitable cell may be a cell to which the terminal is currently connected, or a new cell.

[0191] In step 1g-55, the NR base station (1g-02) that receives the RRC connection re-establishment request message can transmit an RRC connection setup message (RRCSetup) to the terminal (1g-01) in RRC connection mode. In one embodiment, if the terminal context of the terminal (1g-01) cannot be retrieved, the base station (1g-02) can transmit an RRC connection setup message to the terminal (1g-01) in RRC connection mode (if the UE context cannot be retrieved, the network can respond with an RRCSetup).

[0192] In step 1g-60, the terminal (1g-01) in RRC connection mode applies the received RRC connection setup message and, in response, can transmit an RRC connection setup completion message (RRCSetupComplete) to the NR base station (1g-02). In one embodiment of the present disclosure, the terminal (1g-01) may include the mobility state determined (or derived) before the terminal (1g-01) transitions to the RRC connection mode state in the RRC connection setup completion message (include the mobilityState in the RRCSetupComplete message and set it to the mobility state (as specified in TS 38.304) of the UE just prior to entering the RRC_CONNECTED state). For example, the terminal (1g-01) in RRC connection mode may include the mobility state determined or derived in step 1g-20 in the RRC connection setup completion message in step 1g-60 and transmit it.

[0193] The following problems may exist in an RRC connection mode terminal according to one embodiment of the present disclosure.

[0194] - Problem 1: The mobility status reported in the 1g-35 stage must be stored even after transitioning to RRC connection mode. This has the disadvantage of unnecessarily maintaining the mobility status of the terminal reported to the base station.

[0195] - Problem 2: The mobility status reported in the 1g-35 stage may differ from the terminal mobility status in the 1g-60 stage. In other words, this may result in reporting an incorrect mobility status to the base station.

[0196] FIG. 1h is a flowchart of a process in which a terminal reports a mobility state to an NR base station in an NR system according to another embodiment of the present disclosure.

[0197] A terminal in an NR system according to one embodiment of the present disclosure can determine a mobility state through the most recent cell selection or cell reselection procedure regardless of the RRC state (RRC idle mode, RRC disabled mode, or RRC connected mode) and report it to an NR base station. The terminal can determine or derive a mobility state based on the cell selection or cell reselection procedure in the RRC connected mode. When a terminal in the RRC connected mode receives an RRC connected setup message (RRCSetup) from a base station in response to an RRC connected reset request message (RRCReestablishmentRequest), it can report the mobility state determined in the RRC connected mode to the NR base station by including it in an RRC connected setup completion message (RRCSetupComplete). According to one embodiment, the two aforementioned problems can be solved.

[0198] Referring to FIG. 1h, in step 1h-05, the terminal (1h-01) may be in RRC idle mode (RRC_IDLE) or RRC disabled mode (RRC_INACTIVE).

[0199] In step 1h-10, a terminal (1h-01) in RRC idle mode or RRC disabled mode may receive or acquire System Information from a base station (1h-02). The System Information may include information for the terminal (1h-01) to perform a cell selection or cell reselection process. In one embodiment, the System Information may include parameters (speedStateReselectionPars) for determining the mobility state of the terminal (1h-01). These parameters (speedStateReselectionPars) for determining the mobility state of the terminal (1h-01) may include the following information (or parameters).

[0200] - t-Evaluation: The duration of evaluating criteria to enter mobility states. For example, one of the values ​​such as 30 seconds, 60 seconds, 120 seconds, 180 seconds, 240 seconds can be signaled.

[0201] ■ t-Evaluation is T CRmax This may mean the time used to determine the allowable number of cell reselections (This specifies the duration for evaluating the allowed amount of cell reselection(s))

[0202] - t-HystNormal: The additional duration for evaluating criteria to enter normal mobility state. For example, one of the values ​​such as 30 seconds, 60 seconds, 120 seconds, 180 seconds, 240 seconds can be signaled.

[0203] ■ t-HystNormal is T CRmaxHyst This may mean an additional time period value before the terminal can enter a normal mobility state.

[0204] - n-CellChangeMedium: The number of cell changes to enter medium mobility state. For example, it can be signaled as an integer value from 1 to 16.

[0205] ■ n-CellChangeMedium is N CR_M This may mean the maximum number of cell reselections to enter the medium mobility state.

[0206] - n-CellChangeHigh: The number of cell changes to enter high mobility state. For example, it can be signaled as an integer value from 1 to 16, and can be signaled as a value greater than n-CellChangeMedium.

[0207] ■ n-CellChangeHigh is N CR_H This may mean the maximum number of cell reselections to enter a high mobility state.

[0208] - q-HystSF: Velocity-based ScalingFator parameter

[0209] ■ sf-Medium: An additional hysteresis parameter value used in medium mobility states. For example, it can be signaled with a value of -6 dB, -4 dB, -2 dB, or 0 dB.

[0210] ■ sf-High: An additional hysteresis parameter value used in high mobility conditions. For example, it can be signaled as one of -6 dB, -4 dB, -2 dB, or 0 dB.

[0211] In step 1h-15, the RRC idle mode or RRC disabled mode terminal (1h-01) can perform a cell selection or cell re-selection process.

[0212] In step 1h-20, the RRC idle mode or RRC disabled mode terminal (1h-01) can determine a mobility state. The terminal (1h-01) can determine a mobility state based on the following predetermined conditions.

[0213] - Medium mobility state criteria

[0214] ■ T CRmax During this time, the number of cell re-selections is N CR_M Equal to or greater than N CR_H If it is less than or equal to (If number of cell reselections during time period T CRmax is greater than or equal to N CR_M but less than or equal to N CR_H )

[0215] - High mobility state criteria

[0216] ■ T CRmax During this time, the number of cell re-selections is N CR_H If the number of cell reselections during time period T exceedsCRmax is greater than N CR_H )

[0217] - Normal mobility state criteria

[0218] ■ T CRmax If the criteria for either Medium- or High mobility state are not met during time period T CrmaxHyst ) or T CRmax During this time, the number of cell re-selections is N CR_M If the number of cell reselections during time period T is less than (If the number of cell reselections during time period T CRmax is less than N CR_M )

[0219] In step 1h-25, the terminal (1h-01) in RRC idle mode or RRC disabled mode may initiate an RRC connection establishment procedure or an RRC connection resume procedure to establish an RRC connection with the base station (1h-02). That is, in step 1h-25, the terminal (1h-01) may transmit an RRC connection request message (RRCSetupRequest) or an RRC connection resume request message (RRCResumeRequest or RRCResumeRequest1) to the base station (1h-02).

[0220] In step 1h-30, the base station (1h-02) may send an RRC connection setup message (RRCSetup) or an RRC connection resumption message (RRCResume) to the terminal (1h-01) in response to an RRC connection request message or an RRC connection resumption request message.

[0221] In step 1h-31, the terminal (1h-01) that receives an RRC connection establishment message or an RRC connection resumption message can transition to an RRC connection mode (RRC_CONNECTED).

[0222] In step 1h-35, the terminal (1h-01) in RRC connection mode may transmit an RRC connection setup completion message (RRCSetupComplete) or an RRC connection resumption completion message (RRCResumeComplete) to the base station (1h-02). At this time, the RRC connection setup completion message or the RRC connection resumption completion message may include the mobility status of the terminal (1h-01). For example, the RRC connection setup completion message or the RRC connection resumption completion message may include a parameter indicating the mobility status of the terminal (1h-01). mobilityState ...may be included. Specifically, the mobility state immediately before the terminal (1h-01) transitions to the RRC connection mode (RRC_CONNECTED) may be included in the RRC connection setup completion message or the RRC resumption completion message. For example, the terminal (1h-01) is a parameter representing the mobility state of the terminal (1h-01). mobilityState The terminal (1h-01) can be set to the mobility state immediately before transitioning to the RRC connection mode (RRC_CONNECTED) and included in the RRC connection setup completion message or the RRC resumption completion message. mobilityState and set it to the mobility state (as specified in TS 38.304) of the UE just prior to entering RRC_CONNECTED state).

[0223] In step 1h-40, the RRC connection re-establishment procedure may be triggered by the following predetermined conditions. In one embodiment, the predetermined conditions may mean at least one of the following.

[0224] - When a radio link failure (RLF) occurs for the Master Cell Group (MCG) and the T316 timer is not configured (upon detecting radio link failure of the MCG and T316 is not configured)

[0225] - In the event of re-configuration with sync failure of the MCG

[0226] - In the event of mobility from NR failure (upon mobility from NR failure)

[0227] - In the event of an RRC connection reconfiguration failure (upon an RRC connection reconfiguration failure)

[0228] - When the SRB1 or SRB2 under consideration receives an integrity check failure from lower layers, except if the integrity check failure is detected on the RRCReestablishment message)

[0229] In step 1h-40, the terminal (1h-01) in RRC connection mode can perform the following actions when the RRC connection reset procedure is initiated.

[0230] - Stop timer T310 if running

[0231] - Stop timer T312 if running

[0232] - Stop timer T304 if running

[0233] - Can drive the T311 timer.

[0234] - You can reset the MAC layer device (reset MAC)

[0235] - A cell selection process can be performed. For example, the cell selection process can be performed based on the 3GPP standard document TS 38.304. And the RRC connection mode terminal (1h-01) can perform a mobility state determination procedure (determining the mobility state by applying mobility state conditions based on the aforementioned 1h-20 step).

[0236] In step 1h-45, the terminal (1h-01) in RRC connection mode can select a suitable NR cell. If a suitable NR cell is selected, the terminal (1h-01) can stop the running T311 timer and start the T301 timer. Here, the suitable cell may be a cell to which the terminal is currently connected, or a new cell.

[0237] In step 1h-50, the RRC connection mode terminal (1h-01) can send an RRC connection re-establishment request message (RRCReestablishmentRequest) to a selected suitable NR cell (1h-02).

[0238] Upon receiving an RRC connection re-establishment request message in step 1h-55, the NR base station (1h-02) can transmit an RRC connection setup message (RRCSetup) to the terminal (1h-01) in RRC connection mode. In one embodiment, if the terminal context of the terminal (1h-01) cannot be retrieved, the base station (1h-02) can transmit an RRC connection setup message to the terminal (1h-01) in RRC connection mode (if the UE context cannot be retrieved, the network can respond with an RRCSetup).

[0239] In step 1h-60, the terminal (1h-01) in RRC connection mode applies the received RRC connection setup message and, in response, can transmit an RRC connection setup completion message (RRCSetupComplete) to the NR base station (1h-02). In one embodiment of the present disclosure, the terminal (1h-01) may include the mobility status determined or derived in step 1h-41 in the RRC connection setup completion message.

[0240] According to one embodiment, the two aforementioned problems can be resolved. That is, the terminal (1h-01) does not need to store the mobility state already reported in step 1h-35. Additionally, since the terminal (1h-01) reports the mobility state determined in step 1h-41 to the base station, it may not report an incorrect mobility state to the base station (1h-02). However, since the terminal (1h-01) performs a cell selection process in step 1h-40, it is highly likely that the normal mobility state will be included in the RRC connection setup completion message in step 1h-60.

[0241] FIG. 1i is a diagram illustrating a terminal operation in which a terminal reports a mobility state to an NR base station in an NR system according to one embodiment of the present disclosure.

[0242] Referring to Fig. 1i, in step 1i-05, the terminal may be in RRC connection mode (RRC_CONNECTED).

[0243] In step 1i-10, the terminal in RRC connection mode may initiate an RRC connection re-establishment procedure according to certain conditions. The certain conditions may follow the aforementioned embodiments.

[0244] In steps 1i-15, the terminal can drive the T311 timer and perform a cell selection process. At this time, the mode terminal of the RRC connection can perform a mobility state determination procedure.

[0245] In step 1i-20, the terminal in RRC connection mode can select a suitable NR cell. Here, the suitable cell may be the cell to which the terminal is currently connected, or it may be a new cell.

[0246] In step 1i-25, the terminal can send an RRC connection re-establishment request message (RRCReestablishmentRequest) to the selected suitable NR cell.

[0247] In step 1i-30, the terminal can receive a downlink RRC message in response to an RRC connection re-establishment request message.

[0248] In step 1i-35, the terminal can determine whether the received downlink RRC message is an RRC connection setup message (RRCSetup) or an RRC connection re-establishment message (RRCReestablishment).

[0249] If the terminal in RRC connection mode receives the RRC connection re-establishment message in step 1i-30, it may discard the mobility status determined (or derived) in the previous step (step 1i-15 or step 1i-20) and transmit the RRC connection re-establishment complete message (RRCReestablishmentComplete) to the selected suitable NR cell. If the terminal in RRC connection mode can include the determined (or derived) mobility status in the RRC connection re-establishment complete message, the terminal may include the determined (or derived) mobility status in the RRC connection re-establishment complete message and transmit it to the selected suitable NR cell.

[0250] If the terminal in RRC connection mode receives the RRC connection setup message (RRCSetup) in step 1i-30, it may include the mobility status from the previous step (step 1i-15 or step 1i-20) in the RRC connection re-establishment completion message (RRCReestablishmentComplete) and transmit it to the selected suitable NR cell.

[0251] FIG. 1j is a flowchart of the process in which a terminal reports a mobility state to an NR base station in an NR system according to another embodiment of the present disclosure.

[0252] A terminal in an NR system according to an embodiment of the present disclosure is characterized by determining a mobility state in an RRC idle mode or an RRC disabled mode. In one embodiment, a terminal in an RRC connection mode may not determine a mobility state. Accordingly, when a terminal in an RRC connection mode receives an RRC connection setup message (RRCSetup) from a base station in response to an RRC connection reset request message (RRCReestablishmentRequest), it may report to the NR base station without including a mobility state in an RRC connection setup completion message (RRCSetupComplete).

[0253] Referring to Fig. 1j, in step 1j-05, the terminal (1j-01) may be in RRC idle mode (RRC_IDLE) or RRC disabled mode (RRC_INACTIVE).

[0254] In step 1j-10, a terminal (1j-01) in RRC idle mode or RRC disabled mode may receive or obtain system information from a base station (1j-02). The system information may include information for the terminal (1j-01) to perform a cell selection or cell reselection process. In one embodiment, the system information may include parameters (speedStateReselectionPars) for determining the mobility state of the terminal (1j-01). These parameters (speedStateReselectionPars) for determining the mobility state of the terminal (1j-01) may include the following information (or parameters).

[0255] - t-Evaluation: The duration of evaluating criteria to enter mobility states. For example, one of the values ​​such as 30 seconds, 60 seconds, 120 seconds, 180 seconds, 240 seconds can be signaled.

[0256] ■ t-Evaluation is T CRmax This may mean the time used to determine the allowable number of cell reselections (This specifies the duration for evaluating the allowed amount of cell reselection(s))

[0257] - t-HystNormal: The additional duration for evaluating criteria to enter normal mobility state. For example, one of the values ​​such as 30 seconds, 60 seconds, 120 seconds, 180 seconds, 240 seconds can be signaled.

[0258] ■ t-HystNormal is T CRmaxHyst This may mean an additional time period value before the terminal can enter a normal mobility state.

[0259] - n-CellChangeMedium: The number of cell changes to enter medium mobility state. For example, it can be signaled as an integer value from 1 to 16.

[0260] ■ n-CellChangeMedium is N CR_M This may mean the maximum number of cell reselections to enter the medium mobility state.

[0261] - n-CellChangeHigh: The number of cell changes to enter high mobility state. For example, it can be signaled as an integer value from 1 to 16, and can be signaled as a value greater than n-CellChangeMedium.

[0262] ■ n-CellChangeHigh is N CR_H This may mean the maximum number of cell reselections to enter a high mobility state.

[0263] - q-HystSF: Velocity-based ScalingFator parameter

[0264] ■ sf-Medium: An additional hysteresis parameter value used in medium mobility states. For example, it can be signaled with a value of -6 dB, -4 dB, -2 dB, or 0 dB.

[0265] ■ sf-High: An additional hysteresis parameter value used in high mobility conditions. For example, it can be signaled as one of -6 dB, -4 dB, -2 dB, or 0 dB.

[0266] In step 1j-15, the RRC idle mode or RRC disabled mode terminal (1j-01) can perform a cell selection or cell re-selection process.

[0267] In step 1j-20, the RRC idle mode or RRC disabled mode terminal (1j-01) can determine a mobility state. The terminal (1j-01) can determine a mobility state based on the following predetermined conditions.

[0268] - Medium mobility state criteria

[0269] ■ T CRmax During this time, the number of cell re-selections is N CR_M Equal to or greater than N CR_H If it is less than or equal to (If number of cell reselections during time period T CRmax is greater than or equal to N CR_M but less than or equal to N CR_H )

[0270] - High mobility state criteria

[0271] ■ T CRmax During this time, the number of cell re-selections is N CR_H If the number of cell reselections during time period T exceedsCRmax is greater than N CR_H )

[0272] - Normal mobility state criteria

[0273] ■ T CRmax If the criteria for either Medium or High mobility state are not met during time period T CrmaxHyst ) or T CRmax During this time, the number of cell re-selections is N CR_M If the number of cell reselections during time period T is less than (If the number of cell reselections during time period T CRmax is less than N CR_M )

[0274] In step 1j-25, the terminal (1j-01) in RRC idle mode or RRC disabled mode may initiate an RRC connection establishment procedure or an RRC connection resume procedure to establish an RRC connection with the base station (1j-02). That is, in step 1j-25, the terminal (1j-01) may transmit an RRC connection request message (RRCSetupRequest) or an RRC connection resume request message (RRCResumeRequest or RRCResumeRequest1) to the base station (1j-02).

[0275] In step 1j-30, the base station (1j-02) may send an RRC connection setup message (RRCSetup) or an RRC connection resumption message (RRCResume) to the terminal (1j-01) in response to an RRC connection request message or an RRC connection resumption request message.

[0276] In step 1j-31, the terminal (1j-01) that receives an RRC connection establishment message or an RRC connection resumption message can transition to an RRC connection mode (RRC_CONNECTED).

[0277] In step 1j-35, the terminal (1j-01) in RRC connection mode may transmit an RRC connection setup completion message (RRCSetupComplete) or an RRC connection resumption completion message (RRCResumeComplete) to the base station terminal (1j-02). At this time, the RRC connection setup completion message or the RRC connection resumption completion message may include the mobility status of the terminal (1j-01). For example, the RRC connection setup completion message or the RRC connection resumption completion message may include a parameter indicating the mobility status of the terminal (1j-01). mobilityState ...may be included. Specifically, the mobility state immediately before the terminal (1j-01) transitions to the RRC connection mode (RRC_CONNECTED) may be included in the RRC connection setup completion message or the RRC resumption completion message. For example, the terminal (1j-01) may have a parameter representing the mobility state of the terminal (1j-01). mobilityState The terminal (1j-01) can be set to the mobility state immediately before transitioning to the RRC connection mode (RRC_CONNECTED) and included in the RRC connection setup completion message or the RRC resumption completion message. mobilityState and set it to the mobility state (as specified in TS 38.304) of the UE just prior to entering RRC_CONNECTED state).

[0278] In step 1j-40, an RRC connection re-establishment procedure may be triggered by the following predetermined conditions. In one embodiment, the predetermined conditions may mean at least one of the following.

[0279] - When a radio link failure (RLF) occurs for the Master Cell Group (MCG) and the T316 timer is not configured (upon detecting radio link failure of the MCG and T316 is not configured)

[0280] - In the event of re-configuration with sync failure of the MCG

[0281] - In the event of mobility from NR failure (upon mobility from NR failure)

[0282] - In the event of an RRC connection reconfiguration failure (upon an RRC connection reconfiguration failure)

[0283] - When the SRB1 or SRB2 under consideration receives an integrity check failure from lower layers, except if the integrity check failure is detected on the RRCReestablishment message)

[0284] In step 1j-40, the terminal (1j-01) in RRC connection mode can perform the following actions when the RRC connection reset procedure is initiated.

[0285] - Stop timer T310 if running

[0286] - Stop timer T312 if running

[0287] - Stop timer T304 if running

[0288] - Can drive the T311 timer.

[0289] - You can reset the MAC layer device (reset MAC)

[0290] - A cell selection process can be performed. For example, the cell selection process can be performed based on 3GPP standard document TS 38.304.

[0291] In step 1j-45, the terminal (1j-01) in RRC connection mode can select a suitable NR cell. If a suitable NR cell is selected, the terminal (1j-01) can stop the running T311 timer and start the T301 timer. Here, the suitable cell may be a cell to which the terminal is currently connected, or a new cell.

[0292] In step 1j-50, the RRC connection mode terminal (1j-01) can send an RRC connection re-establishment request message (RRCReestablishmentRequest) to a selected suitable NR cell (1j-02).

[0293] Upon receiving an RRC connection re-establishment request message in step 1j-55, the NR base station (1j-02) can transmit an RRC connection setup message (RRCSetup) to a terminal (1j-01) in RRC connection mode. In one embodiment, if the terminal context of the terminal (1j-01) cannot be retrieved, the base station (1j-02) can transmit an RRC connection setup message to the terminal (1j-01) in RRC connection mode (if the UE context cannot be retrieved, the network can respond with an RRCSetup).

[0294] In step 1j-60, the terminal (1j-01) in RRC connection mode applies the received RRC connection setup message and, in response, can transmit an RRC connection setup completion message (RRCSetupComplete) to the NR base station (1j-02). In one embodiment of the present disclosure, the terminal (1j-01) may not include the mobility state in the RRC connection setup completion message.

[0295] FIG. 1k is a diagram illustrating a terminal operation in which a terminal reports a mobility state to an NR base station in an NR system according to another embodiment of the present disclosure.

[0296] Referring to Fig. 1k, in step 1k-05, the terminal may be in RRC idle mode, RRC disabled mode, or RRC connected mode.

[0297] In step 1k-10, if the terminal is in RRC idle mode or RRC disabled mode, it may perform a cell selection or cell reselection process and send an RRC connection setup request message (RRCSetupRequest), an RRC connection resumption request message (RRCResumeRequest), or an RRC connection resumption request 1 message (RRCResumeRequest1) to the (re)selected NR cell. Even after sending these messages, the terminal may continue to perform the cell reselection process and determine the mobility state based on the reselection process.

[0298] In step 1k-10, if the terminal is in RRC connection mode, it may select a suitable NR cell and send an RRC connection re-establishment request message (RRCReestablishmentRequest) to the selected suitable NR cell. A terminal in RRC connection mode may not determine a mobility state.

[0299] In step 1k-15, the terminal may receive an RRC connection establishment message (RRCSetup) in response to step 1k-10.

[0300] In step 1k-20, the terminal can determine whether the received RRC connection establishment message is a response message to the RRC connection re-establishment request message.

[0301] In step 1k-25, if the RRC connection mode terminal receives an RRC connection establishment message in response to an RRC connection re-establishment request message, it may send an RRC connection establishment completion message without including the terminal's mobility status in the RRC connection establishment completion message.

[0302] In step 1k-30, if a terminal in RRC idle mode or RRC disabled mode receives an RRC setup message in response to an RRC setup request message (RRCSetupRequest), an RRC resumption request message (RRCResumeRequest), or an RRC resumption request 1 message (RRCResumeRequest1), it may transmit an RRC setup completion message by including the mobility state derived before transitioning to RRC connection mode in the RRC setup completion message.

[0303] A terminal according to one embodiment of the present disclosure includes a mobility state in an RRC connection setup message when it receives an RRC connection setup message in response to an RRC connection setup request message (RRCSetupRequest), an RRC connection resumption request message (RRCResumeRequest), or an RRC connection resumption request 1 message (RRCResumeRequest1), and may not include a mobility state in an RRC connection setup completion message when it receives an RRC connection establishment message in response to an RRC connection re-establishment request message.

[0304] FIG. 11 is a block diagram illustrating the internal structure of a terminal according to one embodiment of the present disclosure.

[0305] Referring to FIG. 11, the terminal may include an RF (Radio Frequency) processing unit (11-10), a baseband processing unit (11-20), a storage unit (11-30), and a control unit (11-40). Of course, it is not limited to the example described above, and the terminal may include fewer or more configurations than the configuration shown in FIG. 11.

[0306] The RF processing unit (1l-10) can perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1l-10) can up-convert a baseband signal provided by the baseband processing unit (1l-20) into an RF band signal and transmit it through an antenna, and down-convert an RF band signal received through an antenna into a baseband signal. For example, the RF processing unit (1l-10) may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC (digital to analog converter), an ADC (analog to digital converter), etc. Of course, it is not limited to these examples. Although only one antenna is shown in FIG. 1l, the terminal may be equipped with multiple antennas. In addition, the RF processing unit (1l-10) may include multiple RF chains. Furthermore, the RF processing unit (1l-10) may perform beamforming. For beamforming, the RF processing unit (1l-10) can adjust the phase and magnitude of each of the signals transmitted and received through multiple antennas or antenna elements. Additionally, the RF processing unit (1l-10) can perform MIMO and can receive multiple layers when performing MIMO operation.

[0307] The baseband processing unit (1l-20) can perform conversion functions between baseband signals and bit sequences according to the physical layer specifications of the system. For example, when transmitting data, the baseband processing unit (1l-20) generates complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (1l-20) can restore the received bit sequence by demodulating and decoding the baseband signal provided by the RF processing unit (1l-10). For example, in the case of following the OFDM (orthogonal frequency division multiplexing) method, when transmitting data, the baseband processing unit (1l-20) generates complex symbols by encoding and modulating the transmitted bit sequence, maps the generated complex symbols to subcarriers, and then constructs OFDM symbols through IFFT (inverse fast Fourier transform) operations and CP (cyclic prefix) insertion. Additionally, upon receiving data, the baseband processing unit (1l-20) can divide the baseband signal provided by the RF processing unit (1l-10) into OFDM symbol units, restore the signals mapped to subcarriers through a fast Fourier transform (FFT), and then restore the received bit sequence through demodulation and decoding.

[0308] The baseband processing unit (1l-20) and the RF processing unit (1l-10) can transmit and receive signals as described above. Accordingly, the baseband processing unit (1l-20) and the RF processing unit (1l-10) may be referred to as a transmitting unit, a receiving unit, a transmitting and receiving unit, or a communication unit. Furthermore, at least one of the baseband processing unit (1l-20) and the RF processing unit (1l-10) may include a plurality of communication modules to support a plurality of different wireless access technologies. Additionally, at least one of the baseband processing unit (1l-20) and the RF processing unit (1l-10) may include different communication modules to process signals of different frequency bands. For example, different wireless access technologies may include wireless LAN (e.g., IEEE 802.11), cellular network (e.g., LTE), etc. In addition, different frequency bands may include super high frequency (SHF) bands (e.g., 2.NRHz, NRHz) and millimeter wave (e.g., 60GHz) bands. The terminal can transmit and receive signals with a base station using a baseband processing unit (11-20) and an RF processing unit (11-10), and the signals may include control information and data.

[0309] The storage unit (1l-30) can store data such as basic programs, application programs, and setting information for the operation of the terminal. In particular, the storage unit (1l-30) can store data information such as basic programs, application programs, and setting information for the operation of the terminal described above. Additionally, the storage unit (1l-30) can provide the stored data upon a request from the control unit (1l-40).

[0310] The control unit (1l-40) can control the overall operations of the terminal. For example, the control unit (1l-40) transmits and receives signals through the baseband processing unit (1l-20) and the RF processing unit (1l-10). Additionally, the control unit (1l-40) writes and reads data to and from the storage unit (1l-40). To this end, the control unit (1l-40) may include at least one processor. For example, the control unit (1l-40) may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as applications. Additionally, according to one embodiment of the present disclosure, the control unit (1l-40) may include a multi-connection processing unit (1l-42) configured to process a process operating in a multi-connection mode. Additionally, at least one component within the terminal may be implemented as a single chip.

[0311] FIG. 1m is a block diagram showing the configuration of a base station according to one embodiment of the present disclosure.

[0312] As illustrated in FIG. 1m, the base station may include an RF processing unit (1m-10), a baseband processing unit (1m-20), a backhaul communication unit (1m-30), a storage unit (1m-40), and a control unit (1m-50). Of course, it is not limited to the example described above, and the base station may include fewer or more configurations than the configuration illustrated in FIG. 1m.

[0313] The RF processing unit (1m-10) can perform functions for transmitting and receiving signals through a wireless channel, such as signal band conversion and amplification. That is, the RF processing unit (1m-10) can up-convert a baseband signal provided by the baseband processing unit (1m-20) into an RF band signal and transmit it through an antenna, and down-convert an RF band signal received through an antenna into a baseband signal. For example, the RF processing unit (1m-10) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Although only one antenna is shown in FIG. 1m, the RF processing unit (1m-10) may be equipped with multiple antennas.

[0314] Additionally, the RF processing unit (1m-10) may include a plurality of RF chains. Furthermore, the RF processing unit (1m-10) may perform beamforming. For beamforming, the RF processing unit (1m-10) may adjust the phase and magnitude of each of the signals transmitted and received through a plurality of antennas or antenna elements. The RF processing unit (1m-10) may perform down-to-down MIMO operation by transmitting one or more layers.

[0315] The baseband processing unit (1m-20) can perform conversion functions between baseband signals and bit sequences according to physical layer specifications. For example, when transmitting data, the baseband processing unit (1m-20) can generate complex symbols by encoding and modulating the transmitted bit sequence. Additionally, when receiving data, the baseband processing unit (1m-20) can restore the received bit sequence by demodulating and decoding the baseband signal provided by the RF processing unit (1m-10). For example, in the case of an OFDM method, when transmitting data, the baseband processing unit (1m-20) can generate complex symbols by encoding and modulating the transmitted bit sequence, map the complex symbols to subcarriers, and then construct OFDM symbols through IFFT operations and CP insertion. Additionally, upon receiving data, the baseband processing unit (1m-20) can divide the baseband signal provided by the RF processing unit (1m-10) into OFDM symbol units, restore the signals mapped to subcarriers through FFT operations, and then restore the received bit sequence through demodulation and decoding. The baseband processing unit (1m-20) and the RF processing unit (1m-10) transmit and receive signals as described above. Accordingly, the baseband processing unit (1m-20) and the RF processing unit (1m-10) may be referred to as a transmitting unit, a receiving unit, a transceiver unit, a communication unit, or a wireless communication unit. A base station can transmit and receive signals with a terminal using the baseband processing unit (1m-20) and the RF processing unit (1m-10), and the signal may include control information and data.

[0316] The backhaul communication unit (1m-30) can provide an interface for communicating with other nodes within the network. That is, the backhaul communication unit (1m-30) can convert a bit sequence transmitted from a base station to another node, e.g., an auxiliary base station, a core network, etc., into a physical signal, and can convert a physical signal received from another node into a bit sequence.

[0317] The storage unit (1m-40) can store data such as basic programs, application programs, and configuration information for the operation of the base station. In particular, the storage unit (1m-40) can store information regarding bearers assigned to connected terminals, measurement results reported from connected terminals, etc. Additionally, the storage unit (1m-40) can store information that serves as a criterion for determining whether to provide or disconnect multiple connections to the terminal. Furthermore, the storage unit (1m-40) can provide the stored data upon a request from the control unit (1m-50). The storage unit (1m-40) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, the storage unit (1m-40) may be composed of multiple memories.

[0318] The control unit (1m-50) can control the overall operations of the base station. For example, the control unit (1m-50) can transmit and receive signals through the baseband processing unit (1m-20) and the RF processing unit (1m-10) or through the backhaul communication unit (1m-30). Additionally, the control unit (1m-50) writes and reads data to and from the storage unit (1m-40). To this end, the control unit (1m-50) may include at least one processor. Additionally, according to one embodiment of the present disclosure, the control unit (1m-50) may include a multiple connection processing unit (1m-52) configured to process a process operating in a multiple connection mode.

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

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

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

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

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

[0324] Meanwhile, the embodiments disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of this disclosure and to aid in understanding this disclosure, and are not intended to limit the scope of this disclosure. That is, it is obvious to those skilled in the art that other variations based on the technical concept of this disclosure are possible. Furthermore, each embodiment may be combined and operated with one another as needed. For example, parts of one embodiment of this disclosure and another embodiment may be combined with each other. Additionally, other variations based on the technical concept of the embodiments described above may be implemented in other systems, such as LTE systems, 5G or NR systems.

Claims

Claim 1 A method for a terminal to report a mobility state, comprising: receiving system information from a base station including parameters (speedStateReselectionPars) for determining the mobility state of the terminal; transmitting at least one of a radio resource control (RRC) connection resumption request message (RRCResumeRequest) or an RRC connection resumption request message 1 (RRCResumeRequest1) to the base station; receiving an RRC connection setup message (RRCSetup) from the base station; and transmitting an RRC connection setup completion message (RRCSetupComplete) to the base station, wherein if the RRCSetup is received as a response to at least one of the RRCResumeRequest or the RRCResumeRequest1, the mobility state of the terminal is included in the RRCSetupComplete. Claim 2 A method according to claim 1, further comprising the step of determining the mobility state of the terminal based on the system information. Claim 3 delete Claim 4 A method according to claim 1, further comprising the step of transmitting an RRC connection re-establishment request message (RRCReestablishmentRequest) to the base station, wherein when the RRCSetup is received as a response to the RRCReestablishmentRequest, the mobility state of the terminal is not included in the RRCSetupComplete. Claim 5 A method for a base station to receive a report on a mobility state, comprising: transmitting system information to the terminal including parameters (speedStateReselectionPars) for determining the mobility state of the terminal; receiving at least one of a radio resource control (RRC) connection resumption request message (RRCResumeRequest) or an RRC connection resumption request message 1 (RRCResumeRequest1) from the terminal; transmitting an RRC connection setup message (RRCSetup) to the terminal; and receiving an RRC connection setup completion message (RRCSetupComplete) from the terminal, wherein if the RRCSetup is transmitted as a response to at least one of the RRCResumeRequest or the RRCResumeRequest1, the mobility state of the terminal is included in the RRCSetupComplete. Claim 6 A method according to claim 5, wherein the mobility state of the terminal is determined at the terminal based on the system information. Claim 7 delete Claim 8 A method according to claim 5, further comprising the step of receiving an RRC connection re-establishment request message (RRCReestablishmentRequest) from the terminal, wherein when the RRCSetup is transmitted in response to the RRCReestablishmentRequest, the mobility state of the terminal is not included in the RRCSetupComplete. Claim 9 A terminal reporting a mobility state, comprising: a memory; a transceiver; and at least one processor, wherein the at least one processor is configured to receive system information from a base station including parameters (speedStateReselectionPars) for determining the mobility state of the terminal, transmit at least one of a radio resource control (RRC) connection resumption request message (RRCResumeRequest) or an RRC connection resumption request message 1 (RRCResumeRequest1) to the base station, receive an RRC connection setup message (RRCSetup) from the base station, and transmit an RRC connection setup completion message (RRCSetupComplete) to the base station, wherein when the RRCSetup is received as a response to at least one of the RRCResumeRequest or the RRCResumeRequest1, the mobility state of the terminal is included in the RRCSetupComplete. Claim 10 In claim 9, the terminal is configured such that at least one processor determines the mobility state of the terminal based on the system information. Claim 11 delete Claim 12 A terminal according to claim 9, wherein the at least one processor is configured to transmit an RRC connection re-establishment request message (RRCReestablishmentRequest) to the base station, and when the RRCSetup is received in response to the RRCReestablishmentRequest, the mobility state of the terminal is not included in the RRCSetupComplete. Claim 13 A base station receiving a report on a mobility state, comprising: a memory; a transceiver; and at least one processor, wherein the at least one processor is configured to transmit system information including parameters (speedStateReselectionPars) for determining the mobility state of a terminal to the terminal, receive at least one of a radio resource control (RRC) connection resumption request message (RRCResumeRequest) or an RRC connection resumption request message 1 (RRCResumeRequest1) from the terminal, transmit an RRC connection setup message (RRCSetup) to the terminal, and receive an RRC connection setup completion message (RRCSetupComplete) from the terminal, wherein when the RRCSetup is transmitted as a response to at least one of the RRCResumeRequest or the RRCResumeRequest1, the mobility state of the terminal is included in the RRCSetupComplete. Claim 14 A base station according to claim 13, wherein the mobility state of the terminal is determined at the terminal based on the system information. Claim 15 A base station according to claim 13, wherein at least one processor is configured to receive an RRC connection re-establishment request message (RRCReestablishmentRequest) from the terminal, and when the RRCSetup is transmitted in response to the RRCReestablishmentRequest, the mobility state of the terminal is not included in the RRCSetupComplete.

Images