KR20210125882A - Method and apparatus for collecting and reporting mobility history information in a next-generation mobile communication system - Google Patents

Abstract

The present invention relates to a communication technique that combines a 5G communication system with an IoT technology to support higher data rates after a 4G system and a system thereof. The present invention can be applied to intelligent services (eg, smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety related services, etc.) based on a 5G communication technology and an IoT-related technology. The present invention provides a method for allowing a terminal to collect and report mobile history information in a next generation mobile communication system and a device thereof.

Description

Method and apparatus for collecting and reporting mobility history information in a next-generation mobile communication system

The present disclosure relates to an operation of a mobile communication system terminal and a base station, and more particularly, to a method and apparatus for collecting and reporting mobility history information of a terminal.

Efforts are being made to develop an improved 5G communication system or pre-5G communication system in order to meet the increasing demand for wireless data traffic after the commercialization of the 4G communication system. For this reason, the 5G communication system or the pre-5G communication system is called a 4G network after (Beyond 4G Network) communication system or an LTE system after (Post LTE) system. In order to achieve a high data rate, the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (eg, such as a 60 gigabyte (60 GHz) band). In order to mitigate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, in the 5G communication system, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used. ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, for network improvement of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud RAN), and an ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation Technology development is underway. In addition, in the 5G system, FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), which are advanced coding modulation (ACM) methods, and FBMC (Filter Bank Multi Carrier), which are advanced access technologies, NOMA (non orthogonal multiple access), and sparse code multiple access (SCMA) are being developed.

On the other hand, the Internet is evolving from a human-centered connection network where humans create and consume information to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. Internet of Everything (IoE) technology, which combines big data processing technology through connection with cloud servers, etc. with IoT technology, is also emerging. In order to implement IoT, technology elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. , M2M), and MTC (Machine Type Communication) are being studied. In the IoT environment, an intelligent IT (Internet Technology) service that collects and analyzes data generated from connected objects and creates new values in human life can be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, advanced medical service, etc. can be applied to

Accordingly, various attempts are being made to apply the 5G communication system to the IoT network. For example, in technologies such as sensor network, machine to machine (M2M), and machine type communication (MTC), 5G communication technology is implemented by techniques such as beam forming, MIMO, and array antenna. there will be The application of a cloud radio access network (cloud RAN) as the big data processing technology described above is an example of the convergence of 5G technology and IoT technology.

When constructing or optimizing a network, a mobile communication service provider usually measures the signal strength in an expected service area, and then goes through a process of arranging or re-adjusting base stations in the service area based on this. The operator loads the signal measurement equipment on the vehicle and collects the cell measurement information in the service area, which requires a lot of time and money. The process is generally referred to as a drive test, using a vehicle. In order to support operations such as cell reselection, handover, and serving cell addition when the UE moves between cells, the UE is equipped with a function of measuring a signal with the base station. Therefore, instead of the drive test, a terminal in the service area can be used, which is called minimization of drive test (MDT). The operator can set the MDT operation to specific terminals through various components of the network, and the terminals are in RRC connected mode (RRC_CONNECTED), RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) serving cell and neighboring cells Collects and stores signal strength information from In addition, various information such as location information, time information, and signal quality information is also stored. The stored information may be reported to the network when the terminals are in the connected mode, and the information is transmitted to a specific server.

A terminal supporting the storage of mobility history information may change a cell through a cell selection process, a cell reselection process, or a handover process, or out of service (eg, if no cell camp-on or access is made to any cell). ) can be entered. The UE may be in an RRC idle mode (RRC_IDLE), an RRC inactive mode (RRC_INACTIVE), or an RRC connected mode (RRC_CONNECTED). Although the NR mobility history information may include both LTE and NR visited cell information, a method for including LTE visited cell information is still insufficient. In addition, 'Outside NR' needs to be updated to increase the efficiency of terminal implementation.

In order to solve the above problems, the present invention is out of service and / or E when entering an NR cell (eg, RRC connected mode terminal or RRC idle mode terminal or RRC deactivation mode) while in out of service before - It is characterized in that the time spent in RATs other than UTRA is stored in the timeSpent field, and only the most recent E-UTRA cell information is stored in the VarMobilityHistoryReport of the NR when entering the NR cell while using E-UTRA.

Through the method and apparatus for collecting and reporting mobility history information proposed in the present invention, it is possible to increase the efficiency of terminal implementation.

1A is a diagram illustrating the structure of an LTE system according to an embodiment of the present invention.
1B is a diagram illustrating a radio protocol structure in an LTE system according to an embodiment of the present invention.
1C is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present invention.
1D is a diagram illustrating a radio protocol structure of a next-generation mobile communication system according to an embodiment of the present invention.
1E is a diagram for describing a technique for collecting and reporting cell measurement information according to an embodiment of the present invention.
1f is a flowchart of a process in which a terminal reports mobility history information to an LTE base station in a conventional LTE system according to an embodiment of the present invention.
1G is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to a base station in a conventional LTE system according to an embodiment of the present invention.
1H is a flowchart of a process in which a terminal reports mobility history information to an NR base station in a next-generation mobile communication system according to an embodiment of the present invention.
1I is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to an NR base station in a next-generation mobile system according to an embodiment of the present invention.
1J is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to an NR base station in a next-generation mobile system according to an embodiment of the present invention.
1K is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to an NR base station in a next-generation mobile system according to an embodiment of the present invention.
11 is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to an NR base station in a next-generation mobile system according to an embodiment of the present invention.
FIG. 1m is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to an NR base station in a next-generation mobile communication system according to an embodiment of the present invention.
1N is a block diagram illustrating an internal structure of a terminal according to an embodiment of the present invention.
1O is a block diagram showing the configuration of an NR base station according to an embodiment of the present invention.
1P is a flowchart of a process of processing a logged measurement configuration when a UE transitions to an RRC deactivation mode in a next-generation mobile communication system according to an embodiment of the present invention.
1q is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to an NR base station in a next-generation mobile system according to an embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

In describing the embodiments, descriptions of technical contents that are well known in the technical field to which the present invention pertains and are not directly related to the present invention will be omitted. This is to more clearly convey the gist of the present invention without obscuring the gist of the present invention by omitting unnecessary description.

For the same reason, some components are exaggerated, omitted, or schematically illustrated in the accompanying drawings. In addition, the size of each component does not fully reflect the actual size. In each figure, the same or corresponding elements are assigned the same reference numerals.

Advantages and features of the present invention, and a method for achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only these embodiments allow the disclosure of the present invention to be complete, and common knowledge in the art to which the present invention pertains. It is provided to fully inform the possessor of the scope of the invention, and the present invention is only defined by the scope of the claims. Like reference numerals refer to like elements throughout.

At this time, it will be understood that each block of the flowchart diagrams and combinations of the flowchart diagrams may be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions performed by the processor of the computer or other programmable data processing equipment are not described in the flowchart block(s). It creates a means to perform functions. These computer program instructions may also be stored in a computer-usable or computer-readable memory that may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory. It is also possible that the instructions stored in the flow chart block(s) produce an article of manufacture containing instruction means for performing the function described in the flowchart block(s). The computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It is also possible that instructions for performing the processing equipment provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is also possible for the functions recited in blocks to occur out of order. For example, two blocks shown one after another may in fact be performed substantially simultaneously, or it is possible that the blocks are sometimes performed in the reverse order according to the corresponding function.

At this time, the term '~ unit' used in this embodiment means software or hardware components such as FPGA or ASIC, and '~ unit' performs certain roles. However, '-part' is not limited to software or hardware. The '~ unit' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors. Thus, as an example, '~' denotes components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, components and '~ units' may be implemented to play one or more CPUs in a device or secure multimedia card. Also, in an embodiment, '~ unit' may include one or more processors.

A term for identifying an access node used in the following description, a term referring to network entities, a term referring to messages, a term referring to an interface between network objects, and a term referring to various identification information and the like are exemplified for convenience of description. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

For convenience of description, the present invention uses terms and names defined in the 3GPP LTE (3rd Generation Partnership Project Long Term Evolution) standard. However, the present invention is not limited by the above terms and names, and may be equally applied to systems conforming to other standards. In the present invention, eNB may be used interchangeably with gNB for convenience of description. That is, a base station described as an eNB may represent a gNB.

1A is a diagram illustrating the structure of an LTE system according to an embodiment of the present invention.

Referring to Figure 1a, as shown, the radio access network of the LTE system is a next-generation base station (Evolved Node B, hereinafter ENB, Node B or base station) (1a-05, 1a-10, 1a-15, 1a-20) and It consists of MME (1a-25, Mobility Management Entity) and S-GW (1a-30, Serving-Gateway). User equipment (hereinafter referred to as UE or terminal) 1a-35 accesses an external network through ENBs 1a-05 to 1a-20 and S-GW 1a-30.

In FIG. 1A , ENBs 1a-05 to 1a-20 correspond to existing Node Bs of the UMTS system. ENB is connected to the UE (1a-35) through a radio channel and performs a more complex role than the existing Node B. In the LTE system, all user traffic, including real-time services such as VoIP (Voice over IP) through the Internet protocol, are serviced through a shared channel, so the state information such as buffer status of UEs, available transmission power status, and channel status A device for scheduling is required, and the ENB (1a-05 ~ 1a-20) is responsible for this. One ENB typically controls multiple cells. For example, in order to implement a transmission rate of 100 Mbps, the LTE system uses, for example, orthogonal frequency division multiplexing (OFDM) in a 20 MHz bandwidth as a radio access technology. In addition, an Adaptive Modulation & Coding (AMC) scheme that determines a modulation scheme and a channel coding rate according to the channel state of the terminal is applied. The S-GW (1a-30) is a device that provides a data bearer, and creates or removes a data bearer under the control of the MME (1a-25). The MME is a device responsible for various control functions as well as the mobility management function for the UE, and is connected to a number of base stations.

1B is a diagram illustrating a radio protocol structure in an LTE system according to an embodiment of the present invention.

Referring to FIG. 1b, the radio protocol of the LTE system is PDCP (Packet Data Convergence Protocol 1b-05, 1b-40), RLC (Radio Link Control 1b-10, 1b-35), MAC (Medium Access) in the UE and ENB, respectively. Control 1b-15, 1b-30). PDCP (Packet Data Convergence Protocol) (1b-05, 1b-40) is in charge of operations such as IP header compression/restore. The main functions of PDCP are summarized below.

- Header compression and decompression (ROHC only)

- Transfer of user data

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

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

- Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

- 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)

- Encryption and decryption function (Ciphering and deciphering)

- Timer-based SDU discard in uplink.

The radio link control (Radio Link Control, hereinafter referred to as RLC) 1b-10 and 1b-35 reconfigures a PDCP packet data unit (PDU) to an appropriate size to perform ARQ operation and the like. The main functions of RLC are summarized below.

- Data transfer function (Transfer of upper layer PDUs)

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

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

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

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

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

- Protocol error detection (only for AM data transfer)

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

- RLC re-establishment function (RLC re-establishment)

The MACs 1b-15 and 1b-30 are connected to several RLC layer devices configured in one terminal, and perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC are summarized below.

- Mapping function (Mapping between logical channels and transport channels)

- 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)

- Scheduling information reporting function (Scheduling information reporting)

- HARQ function (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification

- Transport format selection

- Padding function

The physical layer (1b-20, 1b-25) channel-codes and modulates upper layer data, creates OFDM symbols and transmits them over a radio channel, or demodulates and channel-decodes OFDM symbols received through the radio channel and transmits them to higher layers do the action

1C is a diagram illustrating the structure of a next-generation mobile communication system according to an embodiment of the present invention.

1c, as shown, the radio access network of the next-generation mobile communication system (hereinafter referred to as NR or 2g) is a next-generation base station (New Radio Node B, hereinafter, NR gNB or NR base station) 1c-10 and NR CN 1c -05, New Radio Core Network). A user terminal (New Radio User Equipment, hereinafter NR UE or terminal) 1c-15 accesses an external network through NR gNB 1c-10 and NR CN 1c-05.

In FIG. 1c , an NR gNB 1c-10 corresponds to an Evolved Node B (eNB) of an existing LTE system. The NR gNB is connected to the NR UE 1c-15 through a radio channel and can provide a superior service than the existing Node B. In the next-generation mobile communication system, since all user traffic is serviced through a shared channel, a device for scheduling by collecting status information such as buffer status, available transmission power status, and channel status of UEs is required. (1c-10) is in charge. One NR gNB 1c-10 typically controls multiple cells. In order to implement ultra-high-speed data transmission compared to current LTE, it can have more than the existing maximum bandwidth, and additional beamforming technology can be grafted using Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as a radio access technology. . In addition, an Adaptive Modulation & Coding (AMC) scheme that determines a modulation scheme and a channel coding rate according to the channel state of the terminal is applied. The NR CN (1c-05) performs functions such as mobility support, bearer setup, QoS setup, and the like. The NR CN is a device in charge of various control functions as well as the mobility management function for the terminal and is connected to a number of base stations. In addition, the next-generation mobile communication system can be linked with the existing LTE system, and the NR CN is connected to the MME (1c-25) through a network interface. The MME is connected to the existing base station eNB (1c-30).

1D is a diagram illustrating a radio protocol structure of a next-generation mobile communication system to which the present invention can be applied.

Referring to FIG. 1D , the radio protocol of the next-generation mobile communication system is NR SDAP (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), and NR RLC (1d-10) in the terminal and the NR base station, respectively. , 1d-35), NR MAC (1d-15, 1d-30), and NR PHY (1d-20, 1d-25).

The main functions of the NR SDAPs 1d-01 and 1d-45 may include some of the following functions.

- transfer of user plane data

- Mapping between a QoS flow and a DRB for both DL and UL for uplink and downlink

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

- A function of mapping a relective QoS flow to a data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

With respect to the SDAP layer device, the UE can receive a configuration of whether to use the header of the SDAP layer device or the function of the SDAP layer device for each PDCP layer device, for each bearer, or for each logical channel with an RRC message, and the SDAP header If is set, the UE uses the uplink and downlink QoS flow and data bearer mapping information with the NAS QoS reflection setting 1-bit indicator (NAS reflective QoS) and the AS QoS reflection setting 1-bit indicator (AS reflective QoS) of the SDAP header. can be instructed to update or reset . The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used as data processing priority and scheduling information to support a smooth service.

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

Header compression and decompression (ROHC only)

- Transfer of user data

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- Order reordering function (PDCP PDU reordering for reception)

- Duplicate detection of lower layer SDUs

- Retransmission of PDCP SDUs

- Encryption and decryption function (Ciphering and deciphering)

- Timer-based SDU discard in uplink.

In the above, 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 a PDCP sequence number (SN), and a function of delivering data to a higher layer in the reordered order. may include, or may include a function of directly delivering without considering the order, may include a function of reordering the order to record the lost PDCP PDUs, and report the status of the lost PDCP PDUs It may include a function for the transmitting side, and may include a function for requesting retransmission for lost PDCP PDUs.

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

- Data transfer function (Transfer of upper layer PDUs)

- In-sequence delivery of upper layer PDUs

- Out-of-sequence delivery of upper layer PDUs

- ARQ function (Error Correction through ARQ)

- Concatenation, segmentation and reassembly of RLC SDUs

- Re-segmentation of RLC data PDUs

- Reordering of RLC data PDUs

- Duplicate detection

- Protocol error detection

- RLC SDU discard function (RLC SDU discard)

- RLC re-establishment function (RLC re-establishment)

In the above description, the in-sequence delivery function of the NR RLC device refers to a function of sequentially delivering RLC SDUs received from a lower layer to an upper layer, and an original RLC SDU is divided into several RLC SDUs and received. , it may include a function of reassembling it and delivering it, and may include a function of rearranging the received RLC PDUs based on an RLC sequence number (SN) or PDCP SN (sequence number), and rearranging the order It may include a function of recording the lost RLC PDUs, a function of reporting a status on the lost RLC PDUs to the transmitting side, and a function of requesting retransmission of the lost RLC PDUs. and, if there is a lost RLC SDU, it may include a function of sequentially delivering only RLC SDUs before the lost RLC SDU to the upper layer, or if a predetermined timer expires even if there is a lost RLC SDU It may include a function of sequentially delivering all RLC SDUs received before the start of RLC to the upper layer, or if a predetermined timer expires even if there are lost RLC SDUs, all RLC SDUs received so far are sequentially transferred to the upper layer. It may include a function to transmit. In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival regardless of the sequence number and sequence number) and delivered to the PDCP device out of sequence (out-of sequence delivery). Segments stored in the buffer or to be received later are received, reconstructed into one complete RLC PDU, processed and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

In the above, the out-of-sequence delivery function of the NR RLC device refers to a function of directly delivering RLC SDUs received from a lower layer to a higher layer regardless of order, and one RLC SDU originally has several RLCs. When received after being divided into SDUs, it may include a function of reassembling and delivering it, and may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs, arranging the order, and recording the lost RLC PDUs. can

The NR MACs 1d-15 and 1d-30 may be connected to several NR RLC layer devices configured in one UE, and the main function of the NR MAC may include some of the following functions.

- Mapping function (Mapping between logical channels and transport channels)

- Multiplexing/demultiplexing of MAC SDUs

- Scheduling information reporting function (Scheduling information reporting)

- HARQ function (Error correction through HARQ)

- Priority handling between logical channels of one UE

- Priority handling between UEs by means of dynamic scheduling

- MBMS service identification

- Transport format selection

- Padding function

The NR PHY layer (1d-20, 1d-25) channel-codes and modulates the upper layer data, creates an OFDM symbol and transmits it to the radio channel, or demodulates and channel-decodes the OFDM symbol received through the radio channel to the upper layer. You can perform a forwarding action.

1E is a diagram for describing a technique for collecting and reporting cell measurement information according to an embodiment of the present invention.

When constructing or optimizing a network, a mobile communication service provider usually measures the signal strength in an expected service area, and then goes through a process of arranging or re-adjusting base stations in the service area based on this. The operator loads the signal measurement equipment on the vehicle and collects the cell measurement information in the service area, which requires a lot of time and money. The process is generally referred to as a drive test, using a vehicle. In order to support operations such as cell reselection, handover, and serving cell addition when the UE moves between cells, the UE is equipped with a function of measuring a signal with the base station. Therefore, instead of the drive test, a terminal in the service area can be used, which is called minimization of drive test (MDT). The operator can set the MDT operation to specific terminals through various components of the network, and the terminals are in RRC connected mode (RRC_CONNECTED), RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE) serving cell and neighboring cells Collects and stores signal strength information from In addition, various information such as location information, time information, and signal quality information is also stored. The stored information may be reported to the network when the terminals are in the connected mode, and the information is transmitted to a specific server.

The MDT operation is largely classified into immediate MDT and logged MDT.

Immediate MDT is characterized by reporting the collected information directly to the network. Since it needs to be reported immediately, only the RRC connected mode UE can perform this. In general, the RRM measurement process for supporting operations such as handover and serving cell addition is recycled, and location information and time information are additionally reported.

Logged MDT is characterized in that the collected information is stored without directly reporting to the network, and after the terminal switches to the RRC connected mode, the stored information is reported. Usually, the UE in the RRC idle mode or RRC deactivation mode that cannot directly report to the network performs this. In the present invention, the terminal of the RRC inactive mode introduced in the next-generation mobile communication system performs Logged MDT. When a specific terminal is in the RRC connected mode, the network provides configuration information for performing a Logged MDT operation to the terminal, and after the terminal switches to the RRC idle mode or RRC inactive mode, the configured information is collected and stored.

1f is a flowchart of a process in which a terminal reports mobility history information to an LTE base station in a conventional LTE system according to an embodiment of the present invention.

Referring to FIG. 1f , the terminal 1f-01 may be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE).

The RRC idle mode terminal 1f-01 may transmit an RRC connection request message (RRCConnectionRequest) to the base station 1f-10 to perform an RRC connection establishment procedure with the base station 1f-02. Upon receiving the RRC connection request message, the base station may transmit an RRC connection setup message (RRCConnectionSetup) to the terminal in response thereto (1f-15). Upon receiving the RRC connection establishment message, the UE may apply it and transition to the RRC connection mode (1f-16). In addition, the RRC connection mode terminal may transmit an RRC connection setup completion message (RRCConnectionSetupComplete) to the base station (1f-20). If the UE supports storage of mobility history information and there is mobility history information in VarMobilityHistoryReport (If the UE supports storage of mobility history information and the UE has mobility history information available in VarMobilityHistoryReport), the UE sets the mobilityHistoryAvail indicator to RRC connection It may be included in the completion message and transmitted to the base station (1f-20).

The RRC deactivation mode terminal 1f-01 may transmit an RRC connection resumption request message (RRCConnectionResumeRequest) to the base station 1f-10 to perform an RRC connection resumption procedure with the base station 1f-02. Upon receiving the RRC connection resumption request message, the base station may transmit an RRC connection resumption message (RRCConnectionResume) to the terminal in response thereto (1f-15). Upon receiving the RRC connection resumption message, the UE may apply it and transition to the RRC connected mode (1f-16). In addition, the RRC connected mode terminal may transmit an RRC connection resumption completion message (RRCConnectionResumeComplete) to the base station (1f-20). If the UE supports storage of mobility history information and there is mobility history information in VarMobilityHistoryReport (If the UE supports storage of mobility history information and the UE has mobility history information available in VarMobilityHistoryReport), the UE resumes the RRC connection with the mobilityHistoryAvail indicator It can be included in the completion message and transmitted to the base station (1f-20).

The terminal 1f-01 without security setting may perform an initial security activation procedure with the base station 1f-02 (1f-21). For example, a terminal that has not configured security may mean a terminal that has switched from an RRC idle mode to an RRC connected mode. Specifically, the terminal 1f-01 may transmit a security mode command message (SecurityModeCommand) to the base station 1f-02, and in response to this, the base station may transmit a security mode completion message (SecurityModeComplete) to the terminal.

In order to perform the RRC connection reconfiguration procedure in step 1f-25, the base station 1f-02 may transmit an RRC connection reconfiguration message (RRCConnectionReconfiguration) to the RRC connected mode terminal 1f-01. The terminal may apply the received RRC connection reconfiguration message and transmit an RRC connection reconfiguration complete message (RRCConnectionReconfigurationComplete) to the base station in response thereto (1f-30).

In step 1f-35, the base station 1f-02 may perform a UE information procedure when security activation is successfully performed. The base station 1f-02 may transmit (1f-35) a terminal information request message (UEInformationRequest) to the terminal in order to request mobility history information from the terminal 1f-01. The terminal information request message may include a MobilityHistoryReportReq indicator.

The terminal 1f-01 that has successfully activated the security in step 1f-40 may transmit (1f-40) a terminal information response message (UEInformationResponse) to the base station 1f-02. If mobilityHistoryReportReq is set to true in the received terminal information request message (If mobilityHistoryReportReq is set to true), the terminal may perform the following series of procedures.

- Information in VarMobilityHistoryReport can be included in mobilityHistoryReport (include the mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport )

- If necessary, delete the oldest information, and include in the mobilityHistoryReport an entry for the current cell, possibly after removing the oldest entry if required, set its fields as follows )

- You can set the global cell identifier of the current cell as visitedCellId (set visitedCellId to the global cell identity of the current cell)

- You can set the time spent in the current cell in the timeSpent field (set field timeSpent to the time spent in the current cell)

The terminal may transmit (1f-40) to the base station by including the mobilityHistoryReport in the terminal information response message by performing the above procedure.

1G is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to a base station in a conventional LTE system according to an embodiment of the present invention.

A terminal supporting the storage of mobility history information may change a cell through a cell selection process, a cell reselection process, or a handover process, or out of service (eg, if no cell camp-on or access is made to any cell). ) can be entered. At this time, the terminal may be in an RRC idle mode (RRC_IDLE), an RRC inactive mode (RRC_INACTIVE), or an RRC connected mode (RRC_CONNECTED). The terminal may store mobility history information in VarMobilityHistoryReport according to the following conditions.

Condition 1-1: Change from an E-UTRA cell (eg, an RRC connected mode terminal may mean a PCell, and an RRC idle mode terminal may mean a serving cell) to another E-UTRA cell or an inter-RAT cell or when entering out of serving in E-UTRA cell (upon change of cell, consisting of PCell in RRC_CONNECTED or serving cell in RRC_IDLE, to another E-UTRA or inter-RAT cell or when entering out of service)

Condition 1-2: E-UTRA cell (eg, RRC connected mode terminal may mean PCell, RRC idle mode terminal or RRC deactivation mode terminal may mean serving cell) in another E-UTRA cell or Upon change of cell, consisting of PCell in RRC_CONNECTED or serving cell in RRC_IDLE or RRC_INACTIVE, to another E-UTRA or inter-RAT cell or when entering out of service)

Condition 2-1: When entering an E-UTRA cell (for example, an RRC connected mode terminal or an RRC idle mode terminal) while being previously out of service and/or using another RAT (upon entering E-UTRA (in RRC_CONNECTED) or RRC_IDLE) while previously out of service and/ or using another RAT)

Condition 2-2: In the case of entering an E-UTRA cell (eg, RRC connected mode terminal or RRC idle mode terminal or RRC deactivation mode) while being in out of service before and/or using another RAT (upon entering E- UTRA (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) while previously out of service and/ or using another RAT)

If the terminal stores mobility history information in VarMobilityHistoryReport according to condition 1-1 or condition 1-2, if necessary, it can delete the previous entry value and store the following information in VarMobilityHistoryReport in the entry in VarMobilityHistoryReport (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell, the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

A terminal that stores mobility history information in VarMobilityHistoryReport according to condition 1-1 does not store mobility history information generated in RRC deactivation mode in VarMobilityHisotryReport, and a terminal that stores mobility history information in VarMobilityHistoryReport according to condition 1-2 is in RRC deactivation mode There is a difference in that the mobility history information generated in VarMobilityHisotryReport is stored. Accordingly, the terminal storing the mobility history information in VarMobilityHistoryReport according to condition 1-2 has an advantage in that it can report accurate mobility history information to the base station compared to condition 1-1.

If the UE stores mobility history information in VarMobilityHistoryReport according to condition 2-1 or condition 2-2, if necessary, it deletes the previous entry value and stores the following information in VarMobilityHistoryReport in the entry in VarMobilityHistoryReport (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- Time spent outside E-UTRA can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent outside E-UTRA). The time out of E-UTRA may mean staying out of service or using a RAT other than the E-UTRA cell, or staying in out of service and using a RAT other than the E-UTRA cell. .

A terminal that stores mobility history information in VarMobilityHistoryReport according to condition 2-1 does not store mobility history information generated in RRC deactivation mode in VarMobilityHisotryReport, and a terminal that stores mobility history information in VarMobilityHistoryReport according to condition 2-2 is in RRC deactivation mode There is a difference in that the mobility history information generated in VarMobilityHisotryReport is stored. Accordingly, the terminal storing the mobility history information in VarMobilityHistoryReport according to condition 1-2 has an advantage in that it can report accurate mobility history information to the base station compared to condition 1-1.

Referring to FIG. 1G , the terminal may store mobility history information in VarMobilityHistoryReport in the manner described above through steps 1g-05 to 1g-45. As an example, the terminal may store at least one of the following information in VarMobilityHistoryReport.

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 1, and time spent in E-UTRA cell 1 10s (1g-05)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 2, and time spent in E-UTRA cell 2 5s (1g-10)

- Time spent in IRAT (inter-RAT) cell 1 10s (1g-15)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 3, and time spent in E-UTRA cell 3 2s (1g-20)

- Time spent out of service 3s (1g-25)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 4, and time spent in E-UTRA cell 4 5s (1g-30)

- Total time spent in out of service and IRAT cell 2 20s (1g-35, 1g-40)

For reference, the global cell identifier for the E-UTRA cell may mean the following information.

In step 1g-45, the UE in the RRC connected mode may have E-UTRA cell 5 connected to the PCell (Primary Cell).

In step 1g-50, the terminal may receive a terminal information request message including mobilityHistoryReportReq from the LTE base station. If mobilityHistoryReportReq is set to true (if mobilityHistoryReportReq is set to true), in steps 1g-55, the terminal may include the entry value in the aforementioned mobilityHistoryReport in mobilityHistoryReport (include the mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport )

In step 1g-60, if necessary for the current cell (eg, E-UTRA cell 5), delete the previous entry value and add the global cell identifier for the current cell (E-UTRA cell 5) to the entry in VarMobilityHistoryReport and The time spent in E-UTRA cell 5 may be included in VarMobilityHistoryReport.

In step 1g-65, the terminal may transmit the above-described mobilityHistoryReport to the LTE base station by including the above-described mobilityHistoryReport in the terminal information response message.

1H is a flowchart of a process in which a terminal reports mobility history information to an NR base station in a next-generation mobile communication system according to an embodiment of the present invention.

Referring to FIG. 1H , the terminal 1h-01 may be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE).

The RRC idle mode terminal 1h-01 may transmit an RRC connection request message (RRCSetupRequest) to the base station 1h-10 to perform an RRC connection establishment procedure with the base station 1h-02. Upon receiving the RRC connection request message, the base station may transmit an RRC connection establishment message (RRCSetupSetup) to the terminal in response thereto (1h-15). Upon receiving the RRC connection establishment message, the UE may apply it and transition to the RRC connection mode (1h-16). In addition, the RRC connected mode terminal may transmit an RRC connection setup complete message (RRCSetupComplete) to the base station (1h-20). If the UE supports storage of mobility history information and there is mobility history information in VarMobilityHistoryReport (If the UE supports storage of mobility history information and the UE has mobility history information available in VarMobilityHistoryReport), the UE sets the mobilityHistoryAvail indicator to RRC connection It may be included in the completion message and transmitted to the base station (1h-20).

RRC deactivation mode terminal 1h-01 transmits an RRC connection resumption request message or RRC connection resumption request 1 message (RRCResumeRequest or RRCResumeRequest1) to the base station to perform an RRC connection resumption procedure with the base station 1h-02 (1h-10) )can do. Upon receiving the RRC connection resumption request message, the base station may transmit an RRC connection resumption message (RRCResume) to the terminal in response thereto (1h-15). Upon receiving the RRC connection resume message, the UE may apply it and transition to the RRC connected mode (1h-16). In addition, the RRC connected mode terminal may transmit an RRC connection resumption completion message (RRCResumeComplete) to the base station (1h-20). If the UE supports storage of mobility history information and there is mobility history information in VarMobilityHistoryReport (If the UE supports storage of mobility history information and the UE has mobility history information available in VarMobilityHistoryReport), the UE resumes the RRC connection with the mobilityHistoryAvail indicator It may be included in the completion message and transmitted to the base station (1h-20).

The terminal 1h-01 without security setting may perform an initial security activation procedure with the base station 1h-02 (1h-21). For example, a terminal that has not configured security may mean a terminal that has switched from an RRC idle mode to an RRC connected mode. Specifically, the terminal 1h-01 may transmit a security mode command message (SecurityModeCommand) to the base station 1h-02, and in response to this, the base station may transmit a security mode completion message (SecurityModeComplete) to the terminal.

In order to perform the RRC connection reconfiguration procedure in step 1h-25, the base station 1h-02 may transmit an RRC connection reconfiguration message (RRCReconfiguration) to the RRC connected mode terminal 1h-01. The terminal may apply the received RRC connection reconfiguration message and transmit an RRC connection reconfiguration complete message (RRCReconfigurationComplete) to the base station in response thereto (1h-30).

In step 1h-35, the base station 1h-02 may perform a UE information procedure when security activation is successfully performed. The base station 1h-02 may transmit (1h-35) a terminal information request message (UEInformationRequest) to the terminal in order to request mobility history information from the terminal 1h-01. The terminal information request message may include a MobilityHistoryReportReq indicator.

The terminal 1h-01 that has successfully activated the security in step 1h-40 may transmit (1h-40) a terminal information response message (UEInformationResponse) to the base station 1h-02. If mobilityHistoryReportReq is set to true in the received terminal information request message (If mobilityHistoryReportReq is set to true), the terminal may perform the following series of procedures.

- Information in VarMobilityHistoryReport can be included in mobilityHistoryReport (include the mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport )

- If necessary, delete the oldest information, and include in the mobilityHistoryReport an entry for the current cell, possibly after removing the oldest entry if required, set its fields as follows )

- You can set the global cell identifier of the current cell as visitedCellId (set visitedCellId to the global cell identity of the current cell)

- You can set the time spent in the current cell in the timeSpent field (set field timeSpent to the time spent in the current cell)

The terminal may transmit (1h-40) to the NR base station by including the mobilityHistoryReport in the terminal information response message by performing the above procedure.

1I is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to an NR base station in a next-generation mobile system according to an embodiment of the present invention.

A terminal supporting the storage of mobility history information may change a cell through a cell selection process, a cell reselection process, or a handover process, or out of service (eg, if no cell camp-on or access is made to any cell). ) can be entered. The UE may be in an RRC idle mode (RRC_IDLE), an RRC inactive mode (RRC_INACTIVE), or an RRC connected mode (RRC_CONNECTED). The terminal may store mobility history information in VarMobilityHistoryReport of NR when the following condition is satisfied.

Condition 1: Change from an NR cell (eg, an RRC connected mode terminal may mean a PCell, an RRC idle mode terminal or an RRC inactive terminal may mean a serving cell) to another NR cell or E-UTRA cell, or (upon change of cell, consisting of PCell in RRC_CONNECTED or serving cell in RRC_IDLE or RRC_INACGIVE (for NR cell), to another NR or E-UTRA or when entering out of service)

Condition 2: When entering the NR cell (eg, RRC connected mode terminal or RRC idle mode terminal or RRC deactivation mode) after being out of service before (upon entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) while previously out of service)

Condition 3: In case of entering NR cell after using E-UTRA (upon entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) while using E-UTRA)

If condition 1 is satisfied and the terminal stores mobility history information in NR's VarMobilityHistoryReport, if necessary, it deletes the previous entry value and stores the following information in the entry in VarMobilityHistoryReport in NR's VarMobilityHistoryReport (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell, the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

If condition 2 is satisfied and the terminal stores mobility history information in VarMobilityHistoryReport of NR, if necessary, delete the previous entry value and store the following information in the entry in VarMobilityHistoryReport in VarMobilityHistoryReport of NR (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- Time spent in out of service can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent out of service)

When condition 2 is satisfied, the terminal according to this temporary example proposes to store only the time spent in out of service in the timeSpent field. That is, unlike the conventional LTE system, it may be characterized in that the time spent in the inter-RAT cell (E-UTRA cell and/or UTRA cell) is not stored in the timeSpent field. Unlike the conventional system, when only the time spent out of service is stored in the timeSpent field, the mobility history information of the terminal may be inaccurate. However, the UE has the advantage of being able to separately manage VarMobilityHistoryReport for LTE and VarMobilityHistoryReport for NR. That is, the time spent in the inter-RAT cell (E-UTRA cell and/or UTRA cell) is separately stored and managed in VarMobilityHistoryReport for LTE. For example, in order to reflect the actual UE mobility history information, the UE does not need to rearrange the order of VarMobilityHistoryReport for LTE and VarMobilityHistoryReport for NR.

If condition 3 is satisfied and the UE stores mobility history information in VarMobilityHistoryReport of NR, if necessary, it deletes the previous entry value and stores the following information in the entry in VarMobilityHistoryReport in VarMobilityHistoryReport of NR (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell (information about the E-UTRA cell), the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

The terminal according to this temporary example is characterized in that, when condition 3 is satisfied, only the most recent E-UTRA cell information is stored in VarMobilityHistoryReport of NR. As an example, when changing a cell from E-UTRA cell a to E-UTRA cell b, and changing from E-UTRA cell b to NR cell, only information about E-UTRA cell b is stored in VarMobilityHistoryReport of NR. can Since this does not store information on E-UTRA cell a, although mobility history information of the terminal may be inaccurate, there is an advantage that the terminal can separately manage VarMobilityHistoryReport for LTE and VarMobilityHistoryReport for NR. That is, since information on E-UTRA cell a is stored in VarMobilityHistoryReport for LTE, and only information on E-UTRA cell b is stored in VarMobilityHistoryReport of NR, the efficiency of UE implementation can be increased. For example, in order to reflect the actual UE mobility history information, the UE does not need to rearrange the order of VarMobilityHistoryReport for LTE and VarMobilityHistoryReport for NR.

Referring to FIG. 1I , the UE may store mobility history information in VarMobilityHistoryReport of NR through steps 1i-05 to 1i-50 as described above. As an example, the UE may store at least one of the following information in VarMobilityHistoryReport of NR.

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 1, and time spent in NR cell 1 10s (1i-05)

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 2, and time spent in NR cell 2 5s (1i-10)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 2, and time spent in E-UTRA cell 2 2s (1i-20)

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 3, and time spent in NR cell 3 3s (1i-25)

- Time spent in out of service 2s (1i-45)

For reference, the terminal according to the present embodiment may be characterized in that the following information is not included in the NR VarMobiltiyHistoryReport.

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 1, and time spent in E-UTRA cell 1 10s (1i-15)

- Time spent out of service 5s (1i-30)

- Time spent in UTRA cell 1 10s (1i-35)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 3, and time spent in E-UTRA cell 3 10s (1i-40)

In the UE according to this embodiment, the global cell identifier for the E-UTRA cell may follow the above-described embodiment, and the global cell identifier for the NR cell may mean the following information.

In step 1i-50, the UE in the RRC connected mode may have NR cell 4 connected to the PCell (Primary Cell).

In step 1i-55, the terminal may receive a terminal information request message including mobilityHistoryReportReq from the NR base station. If mobilityHistoryReportReq is set to true (if mobilityHistoryReportReq is set to true), in steps 1i-60, the terminal may include the entry value in the aforementioned mobilityHistoryReport in mobilityHistoryReport (include the mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport )

In step 1i-65, if necessary for the current cell (eg, NR cell 4), delete the previous entry value, and in the entry in VarMobilityHistoryReport, the global cell identifier for the current cell (NR cell 4) and NR cell 4 You can include the time spent in the VarMobilityHistoryReport.

In step 1i-70, the terminal may transmit the above-described mobilityHistoryReport to the NR base station by including the mobilityHistoryReport in the terminal information response message.

FIG. 1J is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to an NR base station in a next-generation mobile system according to an embodiment of the present invention.

A terminal supporting the storage of mobility history information may change a cell through a cell selection process, a cell reselection process, or a handover process, or out of service (eg, if no cell camp-on or access is made to any cell). ) can be entered. The UE may be in an RRC idle mode (RRC_IDLE), an RRC inactive mode (RRC_INACTIVE), or an RRC connected mode (RRC_CONNECTED). The terminal may store mobility history information in VarMobilityHistoryReport of NR when the following condition is satisfied.

Condition 1: Change from an NR cell (eg, an RRC connected mode terminal may mean a PCell, an RRC idle mode terminal or an RRC inactive terminal may mean a serving cell) to another NR cell or E-UTRA cell, or (upon change of cell, consisting of PCell in RRC_CONNECTED or serving cell in RRC_IDLE or RRC_INACGIVE (for NR cell), to another NR or E-UTRA or when entering out of service)

Condition 2: Previously in out of service and/or using an inter-RAT cell other than the E-UTRA cell, entering the NR cell (eg, RRC connected mode terminal or RRC idle mode terminal or RRC deactivation mode) (upon entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) while previously out of service and/or using another RAT except E-UTRA)

Condition 3: In case of entering NR cell after using E-UTRA (upon entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) while using E-UTRA)

If condition 1 is satisfied and the terminal stores mobility history information in NR's VarMobilityHistoryReport, if necessary, it deletes the previous entry value and stores the following information in the entry in VarMobilityHistoryReport in NR's VarMobilityHistoryReport (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell, the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

If condition 2 is satisfied and the terminal stores mobility history information in VarMobilityHistoryReport of NR, if necessary, delete the previous entry value and store the following information in the entry in VarMobilityHistoryReport in VarMobilityHistoryReport of NR (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- Out of service and/or time spent in RAT other than E-UTRA can be stored in the timeSpent field (set the field timeSpent of the entry as the time outside NR except using E-UTRA)

When condition 2 is satisfied, the UE according to this temporary example proposes to store in the timeSpent field in consideration of both the out of service stay time and the time using RATs other than E-UTRA. As an example, RATs other than E-UTRA may mean UTRA. Since the time spent in RATs other than E-UTRA can be stored in the mobility history information of the terminal, the mobility history information of the terminal may be more accurate.

If condition 3 is satisfied and the UE stores mobility history information in VarMobilityHistoryReport of NR, if necessary, it deletes the previous entry value and stores the following information in the entry in VarMobilityHistoryReport in VarMobilityHistoryReport of NR (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell (information about the E-UTRA cell), the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

The terminal according to this temporary example is characterized in that when condition 3 is satisfied, only the most recent E-UTRA cell information is stored in VarMobilityHistoryReport. As an example, when changing a cell from E-UTRA cell a to E-UTRA cell b, and changing from E-UTRA cell b to an NR cell, only information about E-UTRA cell b may be stored in VarMobilityHistoryReport. . Since this does not store information on E-UTRA cell a, although mobility history information of the terminal may be inaccurate, there is an advantage that the terminal can separately manage VarMobilityHistoryReport for LTE and VarMobilityHistoryReport for NR. That is, since information on E-UTRA cell a is stored in VarMobilityHistoryReport for LTE, and only information on E-UTRA cell b is stored in VarMobilityHistoryReport of NR, the efficiency of UE implementation can be increased. For example, in order to reflect the actual UE mobility history information, the UE does not need to rearrange the order of VarMobilityHistoryReport for LTE and VarMobilityHistoryReport for NR.

Referring to FIG. 1j , the UE may store mobility history information in the NR VarMobilityHistoryReport through steps 1j-05 to 1j-50 as described above. As an example, the UE may store at least one of the following information in VarMobilityHistoryReport of NR.

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 1, and time spent in NR cell 1 10s (1j-05)

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 2, and time spent in NR cell 2 5s (1j-10)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 2, and time spent in E-UTRA cell 2 2s (1j-20)

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 3, and time spent in NR cell 3 3s (1j-25)

- Total time spent in UTRA cell 1 and out of service 12s (1j-40, 1j-45)

For reference, the terminal according to the present embodiment may be characterized in that the following information is not included in the NR VarMobiltiyHistoryReport.

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 1, and time spent in E-UTRA cell 1 10s (1j-15)

- Time spent out of service 5s (1j-30)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 3, and time spent in E-UTRA cell 3 10s (1i-40)

In step 1j-50, the UE in the RRC connected mode may have NR cell 4 connected to the PCell (Primary Cell).

In step 1j-55, the terminal may receive a terminal information request message including mobilityHistoryReportReq from the NR base station. If mobilityHistoryReportReq is set to true (if mobilityHistoryReportReq is set to true), in step 1j-60, the terminal may include the entry value in mobilityHistoryReport described above in mobilityHistoryReport (include the mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport )

In step 1j-65, if necessary for the current cell (for example, NR cell 4), delete the previous entry value, and in the entry in VarMobilityHistoryReport, the global cell identifier for the current cell (NR cell 4) and NR cell 4 You can include the time spent in the VarMobilityHistoryReport.

In step 1j-70, the terminal may transmit the above-described mobilityHistoryReport to the NR base station by including the mobilityHistoryReport in the terminal information response message.

1K is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to an NR base station in a next-generation mobile system according to an embodiment of the present invention.

A terminal supporting the storage of mobility history information may change a cell through a cell selection process, a cell reselection process, or a handover process, or out of service (eg, if no cell camp-on or access is made to any cell). ) can be entered. The UE may be in an RRC idle mode (RRC_IDLE), an RRC inactive mode (RRC_INACTIVE), or an RRC connected mode (RRC_CONNECTED). The terminal may store mobility history information in VarMobilityHistoryReport of NR when the following condition is satisfied.

Condition 1: Change from an NR cell (eg, an RRC connected mode terminal may mean a PCell, an RRC idle mode terminal or an RRC inactive terminal may mean a serving cell) to another NR cell or E-UTRA cell, or (upon change of cell, consisting of PCell in RRC_CONNECTED or serving cell in RRC_IDLE or RRC_INACGIVE (for NR cell), to another NR or E-UTRA or when entering out of service)

Condition 2: When entering the NR cell (eg, RRC connected mode terminal or RRC idle mode terminal or RRC deactivation mode) after being out of service before (upon entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) while previously out of service)

Condition 3: In case of entering NR cell after using E-UTRA (upon entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) while using E-UTRA)

Condition 4: E-UTRA cell (eg, RRC connected mode terminal may mean PCell, RRC idle mode or RRC inactive mode terminal may mean serving cell) to another E-UTRA cell or E -upon change of cell, consisting of PCell in RRC_CONNECTED or serving cell in RRC_IDLE or RRC_INACTIVE, to another E-UTRA or when entering out of service

If condition 1 is satisfied and the terminal stores mobility history information in NR's VarMobilityHistoryReport, if necessary, it deletes the previous entry value and stores the following information in the entry in VarMobilityHistoryReport in NR's VarMobilityHistoryReport (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell, the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

If condition 2 is satisfied and the terminal stores mobility history information in NR's VarMobilityHistoryReport, if necessary, it deletes the previous entry value and stores the following information in the VarMobilityHistoryReport entry in NR's VarMobilityHistoryReport (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- Time spent in out of service can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent out of service)

If condition 3 is satisfied and the UE stores mobility history information in VarMobilityHistoryReport of NR, if necessary, it deletes the previous entry value and stores the following information in the entry in VarMobilityHistoryReport in VarMobilityHistoryReport of NR (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell (information about the E-UTRA cell), the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

If condition 4 is satisfied and the terminal stores mobility history information in VarMobilityHistoryReport of NR, if necessary, delete the previous entry value and store the following information in VarMobilityHistoryReport of NR (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell (information about the E-UTRA cell), the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

Referring to FIG. 1K , the UE may store mobility history information in VarMobilityHistoryReport of NR through steps 1k-05 to 1k-50 as described above. As an example, the UE may store at least one of the following information in VarMobilityHistoryReport of NR.

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 1, and time spent in NR cell 1 10s (1k-05)

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 2, and time spent in NR cell 2 5s (1k-10)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 1, and time spent in E-UTRA cell 1 10s (1k-15)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 2, and time spent in E-UTRA cell 2 2s (1k-20)

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 3, and time spent in NR cell 3 5s (1k-25)

- Time spent out of service 2s (1k-45)

For reference, the terminal according to the present embodiment may be characterized in that the following information is not included in the NR VarMobiltiyHistoryReport.

- Time spent out of service 5s (1k-35)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 3, and time spent in E-UTRA cell 3 10s (1k-35)

- Time spent in UTRA cell1 10s (1k-40)

In step 1k-50, the UE in the RRC connected mode may have NR cell 4 connected to the PCell (Primary Cell).

In step 1k-55, the terminal may receive a terminal information request message including mobilityHistoryReportReq from the NR base station. If mobilityHistoryReportReq is set to true (if mobilityHistoryReportReq is set to true), in step 1k-60, the terminal may include the entry value in the aforementioned mobilityHistoryReport in mobilityHistoryReport (include the mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport )

In step 1k-65, if necessary for the current cell (for example, NR cell 4), delete the previous entry value, and in the entry in VarMobilityHistoryReport, the global cell identifier for the current cell (NR cell 4) and NR cell 4 You can include the time spent in the VarMobilityHistoryReport.

In step 1k-70, the terminal may transmit the above-described mobilityHistoryReport to the NR base station by including the mobilityHistoryReport in the terminal information response message.

11 is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to an NR base station in a next-generation mobile system according to an embodiment of the present invention.

A terminal supporting the storage of mobility history information may change a cell through a cell selection process, a cell reselection process, or a handover process, or out of service (eg, if no cell camp-on or access is made to any cell). ) can be entered. The UE may be in an RRC idle mode (RRC_IDLE), an RRC inactive mode (RRC_INACTIVE), or an RRC connected mode (RRC_CONNECTED). The terminal may store mobility history information in VarMobilityHistoryReport of NR when the following condition is satisfied.

Condition 1: Change from an NR cell (eg, an RRC connected mode terminal may mean a PCell, an RRC idle mode terminal or an RRC inactive terminal may mean a serving cell) to another NR cell or E-UTRA cell, or (upon change of cell, consisting of PCell in RRC_CONNECTED or serving cell in RRC_IDLE or RRC_INACGIVE (for NR cell), to another NR or E-UTRA or when entering out of service)

Condition 2: In case of entering NR cell while using E-UTRA (upon entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) while using E-UTRA)

If condition 1 is satisfied and the terminal stores mobility history information in NR's VarMobilityHistoryReport, if necessary, it deletes the previous entry value and stores the following information in the entry in VarMobilityHistoryReport in NR's VarMobilityHistoryReport (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell, the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

If condition 2 is satisfied and the terminal stores mobility history information in VarMobilityHistoryReport of NR, if necessary, delete the previous entry value and store the following information in the entry in VarMobilityHistoryReport in VarMobilityHistoryReport of NR (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- Store the global cell identifier or carrier frequency and physical cell identifier of the most recent E-UTRA cell in the visitedCellId field before entering the NR cell, and the total time out of NR (time in inter-RAT cell and out of service) time) can be stored in the timeSpent field. When the total time deviating from NR is stored in the timeSpent field, the base station has the advantage of being able to check the total time for mobility of the terminal before entering the NR cell. Alternatively, the global cell identifier or carrier frequency and physical cell identifier of the most recent E-UTRA cell before entering the NR cell are stored in the visitedCellId field, and the total time spent in the E-UTRA cell and out of service (stayed in the E-UTRA cell) time, time spent out of service) can be stored in the timeSpent field. When the total time spent in the E-UTRA cell and out of service is stored in timeSpent, the base station checks only the time spent in the E-UTRA cell and the time spent in the out of service before entering the NR cell to make the mobility of the terminal more inaccurate. However, since the UE does not store the time spent in RATs other than the E-UTRA cell in the VarMobilityHistoryReport of the NR, there is an advantage of easy UE implementation. Alternatively, the global cell identifier or carrier frequency and physical cell identifier of the most recent E-UTRA cell before entering the NR cell are stored in the visitedCellId field, and the total time spent in the E-UTRA cell (the time spent in the E-UTRA cell) is timeSpent You can store it in a field. If only the total time spent in the E-UTRA cell is stored in timeSpent, the base station may check only the time spent in the E-UTRA cell before entering the NR cell to more inaccurately determine the mobility of the terminal, but the terminal stays out of service Since the time and the time spent in the inter-RAT cell except for E-UTRA are not stored in the VarMobilityHistoryReport of the NR, there is an advantage of easy terminal implementation.

Referring to FIG. 11 , the UE may store mobility history information in VarMobilityHistoryReport of NR in the manner described above through steps 11-05 to 11-20. As an example, the UE may store at least one of the following information in VarMobilityHistoryReport of NR.

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 1, and time spent in NR cell 1 10s (11-05)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 2, and total time spent in E-UTRA cell 1 and E-UTRA cell 2 12s (1l-10, 1l-15).

In step 11-20, the UE in the RRC connected mode may have NR cell 2 connected to the PCell (Primary Cell).

In step 11-25, the terminal may receive a terminal information request message including mobilityHistoryReportReq from the NR base station. If mobilityHistoryReportReq is set to true (if mobilityHistoryReportReq is set to true), in steps 11-30, the terminal may include the entry value in mobilityHistoryReport described above in mobilityHistoryReport (include the mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport )

In step 11-35, if necessary for the current cell (for example, NR cell 2), delete the previous entry value, and in the entry in VarMobilityHistoryReport, the global cell identifier for the current cell (NR cell 2) and NR cell 2 You can include the time spent in the VarMobilityHistoryReport.

In step 11-40, the terminal may transmit the above-described mobilityHistoryReport to the NR base station by including the mobilityHistoryReport in the terminal information response message.

FIG. 1m is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to an NR base station in a next-generation mobile system according to an embodiment of the present invention.

A terminal supporting the storage of mobility history information may change a cell through a cell selection process, a cell reselection process, or a handover process, or out of service (eg, if no cell camp-on or access is made to any cell). ) can be entered. The UE may be in an RRC idle mode (RRC_IDLE), an RRC inactive mode (RRC_INACTIVE), or an RRC connected mode (RRC_CONNECTED). The terminal may store mobility history information in VarMobilityHistoryReport of NR when the following condition is satisfied.

Condition 1: Change from an NR cell (eg, an RRC connected mode terminal may mean a PCell, an RRC idle mode terminal or an RRC inactive terminal may mean a serving cell) to another NR cell or E-UTRA cell, or (upon change of cell, consisting of PCell in RRC_CONNECTED or serving cell in RRC_IDLE or RRC_INACGIVE (for NR cell), to another NR or E-UTRA or when entering out of service)

Condition 2: When entering the NR cell (eg, RRC connected mode terminal or RRC idle mode terminal or RRC deactivation mode) after being out of service before (upon entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) while previously out of service)

Condition 3: In case of entering NR cell after using E-UTRA (upon entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) while using E-UTRA)

If condition 1 is satisfied and the terminal stores mobility history information in NR's VarMobilityHistoryReport, if necessary, it deletes the previous entry value and stores the following information in the entry in VarMobilityHistoryReport in NR's VarMobilityHistoryReport (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell, the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

If condition 2 is satisfied and the terminal stores mobility history information in NR's VarMobilityHistoryReport, if necessary, it deletes the previous entry value and stores the following information in the VarMobilityHistoryReport entry in NR's VarMobilityHistoryReport (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- Time spent in out of service can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent out of service)

If condition 3 is satisfied and the UE stores mobility history information in VarMobilityHistoryReport of NR, if necessary, it deletes the previous entry value and stores the following information in the entry in VarMobilityHistoryReport in VarMobilityHistoryReport of NR (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell (information about the E-UTRA cell), the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

The terminal may store mobility history information in VarMobilityHistoryReport of LTE when the following conditions are satisfied, and may additionally report it when reporting mobility history information of the terminal to an NR base station.

Condition 4-1: Change from an E-UTRA cell (eg, an RRC connected mode terminal may mean a PCell, and an RRC idle mode terminal may mean a serving cell) to another E-UTRA cell or an inter-RAT cell or when entering out of serving in E-UTRA cell (upon change of cell, consisting of PCell in RRC_CONNECTED or serving cell in RRC_IDLE, to another E-UTRA or inter-RAT cell or when entering out of service)

Condition 4-2: E-UTRA cell (eg, RRC connected mode terminal may mean PCell, RRC idle mode terminal or RRC deactivation mode terminal may mean serving cell) in another E-UTRA cell or Upon change of cell, consisting of PCell in RRC_CONNECTED or serving cell in RRC_IDLE or RRC_INACTIVE, to another E-UTRA or inter-RAT cell or when entering out of service)

Condition 5-1: When entering an E-UTRA cell (for example, an RRC connected mode terminal or an RRC idle mode terminal) while using a RAT other than the NR and/or out of service before (upon entering E-UTRA) (in RRC_CONNECTED or RRC_IDLE) while previously out of service and/ or using another RAT except NR)

Condition 5-2: Previously out of service and / or while using another RAT other than NR When entering the E-UTRA cell (eg, RRC connected mode terminal or RRC idle mode terminal or RRC deactivation mode) (upon entering E-UTRA (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) while previously out of service and/ or using another RAT except NR)

If the terminal stores mobility history information in VarMobilityHistoryReport of LTE according to condition 4-1 or condition 4-2, if necessary, delete the previous entry value and store the following information in VarMobilityHistoryReport of LTE in the entry in VarMobilityHistoryReport (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell, the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

A terminal that stores mobility history information in VarMobilityHistoryReport according to condition 4-1 does not store mobility history information generated in RRC deactivation mode in VarMobilityHisotryReport, and a terminal that stores mobility history information in VarMobilityHistoryReport according to condition 4-2 is in RRC deactivation mode There is a difference in that the mobility history information generated in VarMobilityHisotryReport is stored.

If the terminal stores mobility history information in VarMobilityHistoryReport according to condition 5-1 or condition 5-2, if necessary, it can delete the value of the previous entry and store the following information in VarMobilityHistoryReport in the entry in VarMobilityHistoryReport (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- Time out of E-UTRA can be stored in the timeSpent field. At this time, the time out of E-UTRA stays in out of service or uses RAT other than E-UTRA cell and NR cell, or stays in out of service and RAT other than E-UTRA cell and NR cell can mean the time to use .

A terminal that stores mobility history information in VarMobilityHistoryReport according to condition 5-1 does not store mobility history information generated in RRC deactivation mode in VarMobilityHisotryReport, and a terminal that stores mobility history information in VarMobilityHistoryReport according to condition 5-2 is in RRC deactivation mode There is a difference in that the mobility history information generated in VarMobilityHisotryReport is stored.

Referring to FIG. 1M , the UE may store mobility history information in VarMobilityHistoryReport of NR in the manner described above through steps 1m-05 to 1m-50. As an example, the UE may store at least one of the following information in VarMobilityHistoryReport of NR.

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 1, and time spent in NR cell 1 10s (1m-05)

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 2, and time spent in NR cell 2 5s (1m-10)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 2, and time spent in E-UTRA cell 2 5s (1m-20)

- Global cell identifier or carrier frequency and physical cell identifier for NR cell 3, and time spent in NR cell 3 3s (1m-25)

- Time spent out of service 2s (1m-45)

The UE may store mobility history information in VarMobilityHistoryReport of LTE as described above through steps 1m-05 to 1m-50. As an example, the terminal may store at least one of the following information in VarMobilityHistoryReport of LTE.

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 1, and time spent in E-UTRA cell 1 10s (1m-15)

- Time spent out of service 5s (1m-30)

- Global cell identifier or carrier frequency and physical cell identifier for E-UTRA cell 3, and time spent in E-UTRA cell 3 10s (1m-35)

- Time spent in UTRA cell 1 10s (1m-40)

In step 1m-50, the UE in the RRC connected mode may have NR cell 4 connected to the PCell (Primary Cell).

In steps 1m-55, the terminal may receive a terminal information request message including mobilityHistoryReportReq from the NR base station. If mobilityHistoryReportReq is set to true (if mobilityHistoryReportReq is set to true), in steps 1m-60, the terminal may include the entry value in mobilityHistoryReport of NR described above in mobilityHistoryReport (include the mobilityHistoryReport and set it to include) entries from VarMobilityHistoryReport ). Additionally, the entry value in the LTE mobilityHistoryReport may be included in the NR mobilityHistoryReport to be included in the NR terminal capability response message, or the LTE mobilityHistoryReport may be separately included in the NR terminal capability response message. At this time, it may be included in the NR terminal capability response message by arranging in the order of steps 1m-05 to 1m-50.

In step 1m-65, if necessary for the current cell (eg, NR cell 4), delete the oldest entry value, and add the global cell identifier for the current cell (NR cell 4) to the entry in the VarMobilityHistoryReport of NR and the NR cell 4 You can include the time spent in VarMobilityHistoryReport.

In step 1m-70, the terminal may transmit the above-described mobilityHistoryReport to the NR base station by including the mobilityHistoryReport in the terminal information response message.

1N is a block diagram illustrating an internal structure of a terminal according to an embodiment of the present invention.

Referring to the drawings, the terminal includes a radio frequency (RF) processing unit 1n-10, a baseband processing unit 1n-20, a storage unit 1n-30, and a control unit 1n-40. .

The RF processing unit 1n-10 performs a function for transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of the signal. That is, the RF processing unit 1n-10 up-converts the baseband signal provided from the baseband processing unit 1n-20 into an RF band signal, transmits it through an antenna, and receives the RF band signal through the antenna. down-converts to a baseband signal. For example, the RF processing unit 1n-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital to analog converter (DAC), an analog to digital converter (ADC), and the like. can In the figure, only one antenna is shown, but the terminal may include a plurality of antennas. Also, the RF processing unit 1n-10 may include a plurality of RF chains. Furthermore, the RF processing unit 1n-10 may perform beamforming. For the beamforming, the RF processing unit 1n-10 may adjust the phase and magnitude of each of signals transmitted and received through a plurality of antennas or antenna elements. In addition, the RF processing unit may perform MIMO, and may receive multiple layers when performing MIMO operation.

The baseband processing unit 1n-20 performs a function of converting between a baseband signal and a bit stream according to a physical layer standard of a system. For example, when transmitting data, the baseband processing unit 1n-20 generates complex symbols by encoding and modulating a transmitted bit stream. Also, when receiving data, the baseband processing unit 1n-20 restores a received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit 1n-10. For example, when transmitting data according to an orthogonal frequency division multiplexing (OFDM) scheme, the baseband processing unit 1n-20 encodes and modulates a transmission bit stream to generate complex symbols, and convert the complex symbols to subcarriers. After mapping to , OFDM symbols are constructed through inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. Also, upon data reception, the baseband processing unit 1n-20 divides the baseband signal provided from the RF processing unit 1n-10 into OFDM symbol units, and maps them to subcarriers through fast Fourier transform (FFT). After restoring the received signals, the received bit stream is restored through demodulation and decoding.

The baseband processing unit 1n-20 and the RF processing unit 1n-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 1n-20 and the RF processing unit 1n-10 may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Furthermore, at least one of the baseband processing unit 1n-20 and the RF processing unit 1n-10 may include a plurality of communication modules to support a plurality of different radio access technologies. In addition, at least one of the baseband processing unit 1n-20 and the RF processing unit 1n-10 may include different communication modules to process signals of different frequency bands. For example, the different wireless access technologies may include a wireless LAN (eg, IEEE 802.11), a cellular network (eg, LTE), and the like. In addition, the different frequency bands may include a super high frequency (SHF) (eg, 2.NRHz, NRhz) band and a millimeter wave (eg, 60GHz) band.

The storage unit 1n-30 stores data such as a basic program, an application program, and setting information for the operation of the terminal. In particular, the storage unit 1n-30 may store information related to a second access node that performs wireless communication using a second wireless access technology. In addition, the storage unit 1n-30 provides stored data according to the request of the control unit 1n-40.

The controller 1n-40 controls overall operations of the terminal. For example, the control unit 1n-40 transmits and receives signals through the baseband processing unit 1n-20 and the RF processing unit 1n-10. In addition, the control unit 1n-40 writes and reads data in the storage unit 1n-40. To this end, the controller 1n-40 may include at least one processor. For example, the controller 1n-40 may include a communication processor (CP) that controls for communication and an application processor (AP) that controls an upper layer such as an application program.

1O is a block diagram showing the configuration of an NR base station according to an embodiment of the present invention.

As shown in the figure, the base station includes an RF processing unit 1o-10, a baseband processing unit 1o-20, a backhaul communication unit 1o-30, a storage unit 1o-40, and a control unit 1o-50. is comprised of

The RF processing unit 1o-10 performs a function for transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of the signal. That is, the RF processing unit 1o-10 up-converts the baseband signal provided from the baseband processing unit 1o-20 into an RF band signal, transmits it through an antenna, and receives the RF band signal through the antenna. down-converts to a baseband signal. For example, the RF processing unit 1o-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. Although only one antenna is shown in the drawing, the first access node may include a plurality of antennas. Also, the RF processing unit 1o-10 may include a plurality of RF chains. Furthermore, the RF processing unit 1o-10 may perform beamforming. For the beamforming, the RF processing unit 1o-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 may perform a downlink MIMO operation by transmitting one or more layers.

The baseband processing unit 1o-20 performs a function of converting a baseband signal and a bit stream according to the physical layer standard of the first radio access technology. For example, when transmitting data, the baseband processing unit 1o-20 generates complex symbols by encoding and modulating the transmitted bit stream. Also, when receiving data, the baseband processing unit 1o-20 restores a received bit stream by demodulating and decoding the baseband signal provided from the RF processing unit 1o-10. For example, in the case of OFDM, when transmitting data, the baseband processing unit 1o-20 generates complex symbols by encoding and modulating a transmission bit stream, maps the complex symbols to subcarriers, and then IFFT OFDM symbols are constructed through operation and CP insertion. Also, upon data reception, the baseband processing unit 1o-20 divides the baseband signal provided from the RF processing unit 1o-10 into OFDM symbol units, and restores signals mapped to subcarriers through FFT operation. After that, the received bit stream is restored through demodulation and decoding. The baseband processing unit 1o-20 and the RF processing unit 1o-10 transmit and receive signals as described above. Accordingly, the baseband processing unit 1o-20 and the RF processing unit 1o-10 may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

The backhaul communication unit 1o-30 provides an interface for communicating with other nodes in the network. That is, the backhaul communication unit 1o-30 converts a bit string transmitted from the main base station to another node, for example, an auxiliary base station, a core network, etc. into a physical signal, and converts the physical signal received from the other node into a bit convert to heat

The storage unit 1o-40 stores data such as a basic program, an application program, and setting information for the operation of the main station. In particular, the storage unit 1o-40 may store information on a bearer allocated to an accessed terminal, a measurement result reported from the accessed terminal, and the like. Also, the storage unit 1o-40 may store information serving as a criterion for determining whether to provide or stop multiple connections to the terminal. In addition, the storage unit 1o-40 provides the stored data according to the request of the control unit 1o-50.

The control unit 1o-50 controls overall operations of the main station. For example, the control unit 1o-50 transmits and receives signals through the baseband processing unit 1o-20 and the RF processing unit 1o-10 or through the backhaul communication unit 1o-30. In addition, the control unit 1o-50 writes and reads data in the storage unit 1o-40. To this end, the control unit 1o-50 may include at least one processor.

On the other hand, the embodiments disclosed in the present specification and drawings are only presented as specific examples to easily explain the technical content of the present disclosure and help the understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is apparent to those of ordinary skill in the art to which the present disclosure pertains that other modifications can be implemented based on the technical spirit of the present disclosure. In addition, each of the above embodiments may be operated in combination with each other as needed.

1P is a flowchart of a process of processing logged measurement configuration when a UE transitions to an RRC deactivation mode in a next-generation mobile communication system according to an embodiment of the present invention.

Referring to FIG. 1P , the UE 1p-01 may be in an RRC idle mode (RRC_IDLE) or an RRC inactive mode (RRC_INACTIVE).

The RRC idle mode terminal 1p-01 may transmit (1p-10) an RRC connection request message (RRCSetupRequest) to the base station to perform an RRC connection establishment procedure with the base station 1p-02. Upon receiving the RRC connection request message, the base station may transmit an RRC connection setup message (RRCSetupSetup) to the terminal in response thereto (1p-15). Upon receiving the RRC connection establishment message, the UE may apply it and transition to the RRC connection mode (1p-16). In addition, the RRC connected mode terminal may transmit an RRC connection setup complete message (RRCSetupComplete) to the base station (1p-20).

RRC deactivation mode terminal 1p-01 transmits an RRC connection resumption request message or RRC connection resumption request 1 message (RRCResumeRequest or RRCResumeRequest1) to the base station to perform an RRC connection resumption procedure with the base station 1p-02 (1p-10) )can do. Upon receiving the RRC connection resumption request message, the base station may transmit an RRC connection resumption message (RRCResume) to the terminal in response thereto (1p-15). Upon receiving the RRC connection resumption message, the UE may apply it and transition to the RRC connected mode (1p-16). In addition, the RRC connected mode terminal may transmit an RRC connection resumption completion message (RRCResumeComplete) to the base station (1p-20).

The terminal 1p-01 without security setting may perform an initial security activation procedure with the base station 1p-02 (1p-21). For example, a terminal that has not configured security may mean a terminal that has switched from an RRC idle mode to an RRC connected mode. Specifically, the terminal 1p-01 may transmit a security mode command message (SecurityModeCommand) to the base station 1p-02, and in response to this, the base station may transmit a security mode completion message (SecurityModeComplete) to the terminal.

In order to perform the RRC connection reconfiguration procedure in step 1p-25, the base station 1p-02 may transmit an RRC connection reconfiguration message (RRCReconfiguration) to the RRC connected mode terminal 1p-01. The terminal may apply the received RRC connection reconfiguration message and transmit an RRC connection reconfiguration complete message (RRCReconfigurationComplete) to the base station in response thereto (1p-30).

The base station 1p-02 may transmit (1p-35) a LoggedMeasurementConfiguration message to the RRC connected mode terminal 1p-01 to initiate a Logged measurement configuration procedure. Upon receiving the LoggedMeasurementConfiguration message, the terminal may perform the following series of processes.

- Logged measurement configuration and logged measurement information can be deleted.

- You can save loggingDuration, loggingInterval, and areaConfiguration (if included) in VarLogMeasConfig.

- If plmn-IdentityList is included in the LoggedMeasurementConfiguration message, RPLMNs in VarLogMeasReport and PLMNs included in plmn-IdentityList can be set in plmn-IdentityList. If plmn-IdentityList is not included in the LoggedMeasurementConfiguration message, RPLMN can be set to plmn-IdentityList in VarLogMeasReport.

- The absoluteTimeInfo, traceReference, traceRecordingSessionRef, and tce-Id received in VarLogMeasReport can be saved.

- If included, the received bt-NameList, wlan-NameList, sensor-NameList, and reportType can be stored in VarLogMeasConfig.

- You can start the T330 timer with the timer value included in loggingDuration.

The ASN.1 structure for the LoggedMeasurementConfiguration is as follows.

The base station 1p-02 transmits an RRC connection release message (RRCRelease) containing reservation configuration information (suspendConfig) to the RRC connected mode terminal 1p-01 for a predetermined reason (eg, when there is no data transmission/reception) (1p- 40) can be done.

In step 1p-45, the UE is currently in the UE Inactive AS Context with KgNB and KRRCInt keys, ROHC state, stored QoS flow to DRB mapping rules, C-RNTI used in the source PCell, cellIdentity and physical cell identity of the source PCell, PSCell SpCellConfigCommon stored in ReconfigurationWithSync of , can store other configured parameters. At this time, the UE may not store the parameters contained in ReconfigurationWithySync of the PCell, the servingCellConfigCommonSIB, and the parameters contained in the LoggedMeasurementConfiguration message received in step 1p-35 in the UE Inactive AS Context. In addition, the UE may make a transition (1p-46) to the RRC deactivation mode (RRC_INACTIVE).

The terminal according to an embodiment of the present disclosure has a feature that does not store the logged measurement configuration in the UE Inactive AS Context. Logged measurement configuration is configuration information commonly applied to both RRC inactive mode and RRC idle mode, and is stored and updated in a separate terminal variable (eg, VarLogMeasConfig and/or VarLogMeasReport) and is managed, so it is stored separately in the UE Inactive AS Context. because there is no need That is, since the UE Inactive AS Context has the purpose of storing and using the RRC configuration information used in the RRC connected mode (RRC_CONNECTED), it is not necessary to separately store the Logged measurement configuration in the UE Inactive AS Context. If the Logged measurement configuration is stored in the UE Inactive AS Context, the values in the actual terminal variables (eg, VarLogMeasConfig and/or VarLogMeasReport) and the Logged measurement configuration stored in the UE Inactive AS Context may have different values. There is a disadvantage in that it may cause a malfunction (eg, report incorrect logged measurement information to the base station) in the future.

1q is a diagram for explaining an operation of a terminal in which a terminal reports mobility history information to an NR base station in a next-generation mobile system according to an embodiment of the present invention.

A terminal supporting the storage of mobility history information may change a cell through a cell selection process, a cell reselection process, and a handover process, or a camped normally state (a state camped on a suitable cell for public use), any cell selection state (state that has not camped on any cell), camped on any cell state (limited service (state camped on acceptable cell for emergency calls, ETWS and CMAS). The terminal is in the NR cell Mobility history information can be stored in RRC idle mode (RRC_IDLE), RRC inactive mode (RRC_INACTIVE), or RRC connected mode (RRC_CONNECTED) for E-UTRA cells, and RRC idle mode (RRC_IDLE) or RRC connected mode (RRC_CONNECTED) for E-UTRA cells Mobility history information can be stored in. Of course, mobility history information can be stored in the RRC deactivation mode for E-UTRA cells, but this may be determined according to the capability or standard release of the UE. It is assumed that the UE in RRC deactivation mode does not store mobility history information for -UTRA The UE may store mobility history information in VarMobilityHistoryReport of NR when the following conditions are satisfied.

Condition 1: When a suitable cell is changed (for an NR suitable cell, an RRC connected mode terminal may mean a PCell, an RRC idle mode terminal or an RRC deactivation mode terminal may mean a serving cell, and an RRC connection for an E-UTRA cell mode terminal may mean PCell, RRC idle mode terminal may mean serving cell); A suitable cell change may mean a change from an NR suitable cell to an E-UTRA suitable cell or another NR suitable cell or a change from an E-UTRA suitable cell to another E-UTRA suitable cell or an NR suitable cell (upon change). of suitable cell, consisting of PCell in RRC_CONNECTED or serving cell in RRC_INACTIVE (for NR cell) or in RRC_IDLE (for NR or E-UTRA cell), to another NR or E-UTRA cell)

Condition 2: In case of transition to any cell selection state after being in camped normal state in NR or E-UTRA (when entering any cell selection state from camped normally state in NR or LTE)

Condition 3: For NR or E-UTRA, if it is in any cell selection state or camped on any cell state before and transitions to a camped normal state in NR (in this case, the state of the terminal is RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED) or NR Or, for E-UTRA, if it is in any cell selection state or camped on any cell state before and transitions to a camped normal state in E-UTRA (in this case, the state of the terminal is RRC_IDLE or RRC_CONNECTED) (upon entering camped normally state) in NR (in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED) or E-UTRA (in RRC_IDLE or RRC_CONNECTED) while previously in any cell selection state or camped on any cell state in NR or LTE)

The terminal may determine which condition among condition 1, condition 2, or condition 3 is satisfied (1q-05).

If condition 1 or condition 2 is satisfied and the UE stores mobility history information in VarMobilityHistoryReport of NR, in step 1q-10, if necessary, the UE deletes the most recent entry value and adds the following information to the entry in VarMobilityHistoryReport. (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- If there is a global cell identifier of the previous PCell or serving cell, the global cell identifier of the previous PCell or serving cell can be stored in the visitedCellId field (if the global cell identity of the previous PCell/ serving cell is available, include the global cell identity of that cell in the field visitedCellId of the entry). Otherwise, the carrier frequency and physical cell identifier of the previous PCell or serving cell may be stored in the visitedCellId field (else, include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry). And the time spent in the previous PCell or serving cell can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in the previous PCell/ serving cell)

If condition 3 is satisfied and the UE stores mobility history information in VarMobilityHistoryReport of NR, in step 1q-15, if necessary, the UE deletes the previous entry value if necessary and adds the following information to the entry in VarMobilityHistoryReport in VarMobilityHistoryReport of NR Can save (include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following)

- For NR or E-UTRA, the time spent in any cell selection state and/or camped on any cell state can be stored in the timeSpent field (set the field timeSpent of the entry as the time spent in any cell selection state and/or camped on any cell state in NR or LTE).

When the terminal according to an embodiment of the present disclosure meets condition 3, any cell selection state and/or for NR or E-UTRA at the time of transition to a camped normally state (ie, a state camped on a suitable cell) It is proposed to store the time spent in the camped on any cell state in the timeSpent field, and at the time of transition to the camped on any cell state (that is, the state camped on an acceptable cell), any cell for NR or E-UTRA separately It is proposed not to store the time spent in the selection state and/or camped on any cell state in the timeSpent field. As an example, entering with NR or E-UTRA (upon entering NR in RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED or upon entering E-UTRA in RRC_IDLE or RRC_CONNECTED) may include both the camped normally state and camped on any cell state. , the terminal may have a disadvantage of storing redundant time.

- T0: camped normally state

- T1: any cell selection state

- T2: camped on any cell state

- T3: any cell state

- T4: camped on any cell state

- T5: camped normally state

If the terminal according to an embodiment of the present disclosure can store the time (T5-T1) at the time T5 in the timeSpent field. However, the terminal not according to an embodiment of the present disclosure stores the time of (T2-T1) at the time T2 in the timeSpent field, the time of (T4-T1) at the time T4 in the timeSpent field, and at the time T5 ( Since the time T5-T1) can be stored in the timeSpent field, an unnecessarily duplicated time (eg, T2-T1 time or T4-T1 time) can be stored to report incorrect mobility history information to the base station.

In step 1q-20, the UE in the RRC connected mode may be connected to a primary cell (PCell) that is an NR cell.

In step 1q-25, the terminal may receive a terminal information request message including mobilityHistoryReportReq from the NR base station. If mobilityHistoryReportReq is set to true (if mobilityHistoryReportReq is set to true), in step 1q-30, the terminal may include the entry value in the aforementioned mobilityHistoryReport in mobilityHistoryReport (include the mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport )

In step 1q-30, if necessary for the current cell (eg, PCell), the previous entry value is deleted, and the global cell identifier for the current cell and the time spent in the PCell can be included in the entry in VarMobilityHistoryReport in VarMobilityHistoryReport. .

In step 1q-30, the terminal may transmit the above-described mobilityHistoryReport to the NR base station by including the mobilityHistoryReport in the terminal information response message.

Claims (1)

A control signal processing method in a wireless communication system, comprising:
receiving a first control signal transmitted from a base station;
processing the received first control signal; and
and transmitting a second control signal generated based on the processing to the base station.

Images