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

Abstract

The present disclosure relates to a communication technology for merging a 5G communication system supporting a higher data transmission rate than a 4G system with an IoT technology, and a system therefor. The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car or connected car, health care, digital education, retail, and safety and security-related services. The present disclosure may provide a method and apparatus for collecting and reporting mobility history information by a terminal in a next generation mobile communication system.

Description

[0001] This application is a divisional application of the invention patent application with application date of April 9, 2021, application number 202180027365.1, and invention name “Method and device for collecting and reporting mobility history information in the next generation mobile communication system”. Technical Field

[0002] The present disclosure relates to UE and base station operations in a mobile communication system, and in particular to a method and apparatus for collecting and reporting mobility history information of a UE. Background Art

[0003] In order to meet the demand for wireless data services that have been increasing since the deployment of the 4th generation (4G) communication system, efforts have been made to develop improved 5G or pre-5G (pre-5G) communication systems. 5G or pre-5G communication systems are also referred to as "super 4G network" communication systems or "post-LTE systems". 5G communication systems are being considered for implementation in ultra-high frequency (millimeter wave) bands (e.g., 60GHz bands) to achieve higher data rates. In order to reduce the propagation loss of radio waves in ultra-high frequency bands and increase the transmission distance, beamforming, massive multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming and massive antenna technology are discussed relative to 5G communication systems. In addition, in 5G communication systems, development for system network improvements is being carried out based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP), receiving-end interference elimination, etc. In addition, in 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM) systems, and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0004] On the other hand, the Internet is evolving from a human-centered connected network where humans generate and consume information to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as things. The Internet of Everything (IoE), which combines IOT technology and big data processing technology by connecting to cloud servers, has also emerged. Technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology" have been required for IoT implementation; therefore, technologies for connection between things, such as sensor networks, machine-to-machine (M2M) communication, and machine type communication (MTC), are being studied recently. Such an IoT environment can provide intelligent Internet technology (IT) services that create new value for human life by collecting and analyzing data generated between connected things. Through the integration and combination between existing information technology (IT) and various industrial applications, IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0005] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M) communications, and machine-type communications (MTC) can be implemented through technologies corresponding to beamforming, MIMO, and array antennas of 5G communication technologies. Cloud radio access networks (cloud RAN) as an application of the above-mentioned big data processing technology can also be considered as an example of the fusion between 5G technology and IoT technology.

[0006] In the case of network establishment or optimization, the mobile communication service provider measures the signal strength in the service area that is usually expected, and based on this, deploys or readjusts the base station in the service area. The service provider loads the signal measurement equipment in the vehicle and collects the cell measurement information in the service area, but this may require a lot of time and cost. Since the process is usually performed by using a vehicle, it can be generally referred to as a "drive test". In order to support operations such as cell reselection or switching and service cell addition during movement between cells, the UE is equipped with a function capable of measuring the signal from the base station. Therefore, the UE in the service area can be used instead of the drive test, which can be referred to as "drive test minimization (MDT)". The service provider can configure the MDT operation for a specific UE through various configuration devices of the network, and the UE can collect and store the signal strength information from the serving cell and the neighboring cell in RRC connected mode (RRC_CONNECTED), RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTUVE). In addition, the UE can also store various multiple pieces of information, such as location information, time information and signal quality information. When the UE is in connected mode, the stored information may be reported to the network and the information may be transmitted to a specific server. Summary of the invention

[0007] Technical issues

[0008] The cell is changed through a cell selection process, a cell reselection process, or a handover process, and a UE that supports storage of mobility history information may enter an out of service state (for example, the UE does not reside on any cell or does not access any cell, that is, the UE is in any cell selection state, or does not reside on any suitable cell or any acceptable cell). In addition, the UE may be in an RRC idle mode (RRC_IDLE mode), an RRC inactive mode (RRC_INACTIVE mode), or an RRC connected mode (RRC_CONNECTED mode). The mobility history information in NR may include both LTE access cell information and NR access cell information, but how to include the LTE access cell information is still incomplete. In addition, in order to improve the implementation efficiency of the UE storing the mobility history information, it is necessary to update "NR external (for example, this means all cases where the UE itself does not access the NR cell)".

[0009] The technical problems that the present disclosure intends to solve are not limited to the above-mentioned technical problems, and a person of ordinary skill in the art to which the present disclosure belongs will be able to clearly understand other unmentioned technical problems from the following description.

[0010] Solution

[0011] According to an embodiment of the present disclosure, a method performed by a UE in a wireless communication system may include: identifying whether a transition is made from at least any one of any cell selection state or any cell-residing state to a normal residency state; in the case of identifying that a transition is made to a normal residency state, determining time information spent in at least any one of any cell selection state or any cell-residing state; storing the determined time information as mobility history information; and sending a message including the mobility history information to a base station.

[0012] In addition, according to another embodiment of the present disclosure, a method performed by a base station in a wireless communication system may include: receiving a radio resource control (RRC) establishment request message from a UE; sending an RRC establishment message to the UE; in a case where the UE supports storage of mobility history information, receiving an RRC establishment completion message including indication information from the UE, the indication information indicating that the mobility history information is available; sending an information request message for the UE to the UE; and receiving a response message including mobility history information in response to the information request message from the UE, wherein the mobility history information includes time information, and wherein, in a case where it is identified that the UE transitions to a normal resident state, the time information is determined based on time information spent in any cell selection state or any one of states resident on any cell.

[0013] In addition, according to another embodiment of the present disclosure, a UE in a wireless communication system may include: a transceiver; and a controller, which is configured to: identify whether the transition is from at least any one of any cell selection state or any cell-residing state to a normal residency state, and in the case of identifying that the transition is to the normal residency state, determine the time information spent in at least any one of any cell selection state or any cell-residing state, store the determined time information as mobility history information, and control the transceiver to send a message including the mobility history information to the base station.

[0014] In addition, according to another embodiment of the present disclosure, a base station in a wireless communication system may include: a transceiver; and a controller, configured to: receive a radio resource control (RRC) establishment request message from a UE through the transceiver, send an RRC establishment message to the UE through the transceiver, and if the UE supports storage of mobility history information, receive an RRC establishment completion message including indication information from the UE through the transceiver, the indication information indicating that the mobility history information is available, send an information request message for the UE to the UE through the transceiver, and receive a response message including mobility history information in response to the information request message from the UE through the transceiver, wherein the mobility history information includes time information, and wherein when the UE transitions to a normal resident state, the time information is determined based on time information spent in any cell selection state or any one of states resident on any cell.

[0015] According to another embodiment of the present disclosure, a method performed by a user equipment UE in a wireless communication system includes: receiving recorded measurement configuration information from a base station in a radio resource control RRC connected state; receiving an RRC release message including suspension configuration information from the base station; and entering an RRC inactive state based on the RRC release message, wherein, when the UE enters the RRC inactive state, the recorded measurement configuration information is not stored as a UE inactive access layer AS context.

[0016] According to another embodiment of the present disclosure, a method performed by a base station in a wireless communication system includes: sending recorded measurement configuration information to a user equipment UE in a radio resource control RRC connected state; sending an RRC release message including suspension configuration information to the UE, wherein, when the UE enters an RRC inactive state based on the RRC release message, the recorded measurement configuration information is not stored as a UE inactive access layer AS context.

[0017] According to another embodiment of the present disclosure, a user equipment UE in a wireless communication system includes: a transceiver; and a controller, coupled to the transceiver and configured to: receive recorded measurement configuration information from a base station in a radio resource control RRC connected state, receive an RRC release message including suspension configuration information from the base station, and enter an RRC inactive state based on the RRC release message, wherein when the UE enters the RRC inactive state, the recorded measurement configuration information is not stored as a UE inactive access layer AS context.

[0018] According to another embodiment of the present disclosure, a base station in a wireless communication system includes: a transceiver; and a controller, coupled to the transceiver and configured to: send recorded measurement configuration information to a user equipment UE in a radio resource control RRC connected state; send an RRC release message including suspension configuration information to the UE, wherein, when the UE enters an RRC inactive state based on the RRC release message, the recorded measurement configuration information is not stored as a UE inactive access layer AS context.

[0019] Beneficial Effects

[0020] The method and device for collecting and reporting mobility history information proposed in the present disclosure can improve the implementation efficiency of UE storing mobility history information.

[0021] Effects that can be obtained in the present disclosure are not limited to the above-mentioned effects, and a person of ordinary skill in the art to which the present disclosure pertains will be able to clearly understand other unmentioned effects from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 is a diagram showing the structure of an LTE system according to an embodiment of the present disclosure.

[0023] Figure 2 is a diagram showing a radio protocol structure in an LTE system according to an embodiment of the present disclosure.

[0024] Figure 3 is a diagram showing a structure of a next generation mobile communication system according to an embodiment of the present disclosure.

[0025] Figure 4 is a diagram showing a radio protocol structure of a next generation mobile communication system according to an embodiment of the present disclosure.

[0026] Figure 5 is a diagram illustrating a method for collecting and reporting cell measurement information according to an embodiment of the present disclosure.

[0027] Figure 6 is a diagram illustrating operations between a UE and a base station for the UE to report mobility history information to an LTE base station in an LTE system in the related art according to an embodiment of the present disclosure.

[0028] Figure 7 is a diagram illustrating an operation of a UE for reporting mobility history information to a base station in an LTE system in the related art according to an embodiment of the present disclosure.

[0029] Figure 8 2 is a diagram illustrating operations between a UE and a base station for the UE to report mobility history information to an NR base station in a next generation mobile communication system according to an embodiment of the present disclosure.

[0030] Fig. 9 is a diagram illustrating the operation of a UE for reporting mobility history information to an NR base station in a next generation mobile communication system according to an embodiment of the present disclosure.

[0031] Fig.10 is a diagram illustrating the operation of a UE for reporting mobility history information to an NR base station in a next generation mobile communication system according to an embodiment of the present disclosure.

[0032] Fig.11 is a diagram illustrating the operation of a UE for reporting mobility history information to an NR base station in a next generation mobile communication system according to an embodiment of the present disclosure.

[0033] Fig.12 is a diagram illustrating the operation of a UE for reporting mobility history information to an NR base station in a next generation mobile communication system according to an embodiment of the present disclosure.

[0034] Fig.13 is a diagram illustrating the operation of a UE for reporting mobility history information to an NR base station in a next generation mobile communication system according to an embodiment of the present disclosure.

[0035] Fig.14 is a diagram showing an internal structure of a UE according to an embodiment of the present disclosure.

[0036] Fig.15 is a diagram showing the configuration of an NR base station according to an embodiment of the present disclosure.

[0037] Fig.16 is a diagram illustrating operations between a UE and a base station for processing a logged measurement configuration if the UE transitions to an RRC inactive mode in a next generation mobile communication system according to an embodiment of the present disclosure.

[0038] Fig.17 is a diagram illustrating the operation of a UE for reporting mobility history information to an NR base station in a next generation mobile communication system according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0039] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0040] When describing the embodiments, explanations of technical contents that are well known in the technical field to which the present disclosure belongs and are not directly related to the present disclosure will be omitted. This is to convey the subject matter of the present disclosure more clearly without making it unclear due to the omission of unnecessary explanations.

[0041] For the same reason, in the accompanying drawings, some components may be exaggerated, omitted or briefly shown. In addition, the size of each component does not fully reflect its actual size, and in the accompanying drawings, the same reference numerals may be used for the same or corresponding components in different drawings.

[0042] By referring to the embodiments that will be described in detail with reference to the accompanying drawings, aspects and features of the present disclosure and methods for realizing these aspects and features will become apparent. However, the present disclosure is not limited to the embodiments disclosed below and can be implemented in various forms. The contents defined in the embodiments of the present disclosure are only provided to help those of ordinary skill in the art to fully understand the specific details of the present disclosure, and the present disclosure is only defined within the scope of the appended claims. Throughout the description of the present disclosure, the same reference numerals are used for the same elements in different drawings.

[0043] In this case, it will be understood that each box of the flowchart illustration and the combination of boxes in the flowchart illustration can be performed by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the instructions executed by the processor of the computer or other programmable data processing device create a component for implementing the functions specified in the (multiple) flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can instruct the computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-usable or computer-readable memory produce an article of manufacture including an instruction component that implements the functions specified in the (multiple) flowchart blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are performed on the computer or other programmable data processing device, thereby generating a computer-implemented process, so that the instructions executed on the computer or other programmable data processing device provide steps for implementing the functions specified in the (multiple) flowchart blocks.

[0044] In addition, each box of the flow chart may represent a module, a code segment or a code portion, which includes one or more executable instructions for implementing (multiple) specified logical functions. It should also be noted that in some alternative implementations, the functions mentioned in the box may not appear in order. For example, two boxes shown in succession can actually be executed substantially simultaneously, or these boxes can sometimes be executed in reverse order, depending on the functions involved.

[0045] In this case, the term "~ unit" used in the embodiment means but is not limited to software or hardware components that perform certain tasks, such as FPGA or ASIC. However, "~ unit" does not mean to be limited to software or hardware. The term "~ unit" can be advantageously configured to reside on an addressable storage medium and configured to execute on one or more processors. Therefore, for example, "~ unit" may include components, such as software components, object-oriented software components, class components and task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and variables. The functions provided in components and "~ units" can be combined into fewer components and "~ units", or further divided into additional components and "~ units". In addition, components and "~ units" can be implemented as one or more CPUs in an operating device or a secure multimedia card. In addition, in one embodiment, "~ unit" may include one or more processors.

[0046] In the following description, for the convenience of explanation, terms identifying access nodes, terms representing network entities, terms representing messages, terms representing interfaces between network entities, and terms representing various identity information are shown. Therefore, the present disclosure is not limited to the following terms, and other terms representing objects with equivalent technical meanings may be used.

[0047] For ease of explanation, in the present disclosure, terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard are used. However, the present disclosure is not limited by the terms and names, and it can be equally applicable to systems that comply with other standards. In the present disclosure, for ease of explanation, "eNB" can be used interchangeably with "gNB". That is, a base station described as an "eNB" can represent a "gNB".

[0048] Figure 1 is a diagram showing the structure of an LTE system according to an embodiment of the present disclosure.

[0049] refer to Figure 1 As shown in the figure, the radio access network of the LTE system may be composed of evolved Node Bs (hereinafter referred to as “ENBs”, “Node Bs” or “base stations”) 105, 110, 115 and 120, a mobility management entity (MME) 125 and a serving gateway (S-GW) 130. User equipment (hereinafter referred to as “UE” or “terminal”) 135 may access external networks through the ENBs 105 to 120 and the S-GW 130.

[0050] exist Figure 1In the LTE system, ENBs 105 to 120 correspond to the existing Node Bs of the UMTS system. The ENB is connected to the UE 135 on a radio channel and plays a more complex role than the existing Node B. In the LTE system, since all user services including real-time services such as Voice over IP (VoIP) over Internet Protocol are served on a shared channel, an entity that performs scheduling by collecting status information such as the buffer status of the UE, the available transmission power status, and the channel status is necessary, and the ENBs 105 to 120 may be responsible for this. Typically, one ENB may control multiple cells. For example, in order to achieve a transmission speed of 100 Mbps, the LTE system may use, for example, Orthogonal Frequency Division Multiplexing (hereinafter referred to as "OFDM") as a radio access technology in a 20 MHz bandwidth. In addition, the LTE system may adopt an adaptive modulation and coding (hereinafter referred to as "AMC") scheme that determines a modulation scheme and a channel coding rate to match the channel status of the UE. The S-GW 130 is an entity that provides a data bearer, and may generate or remove a data bearer under the control of the MME 125. The MME is an entity responsible for not only a mobility management function of a UE but also various control functions and may be connected to a plurality of base stations.

[0051] Figure 2 is a diagram showing a radio protocol structure in an LTE system according to an embodiment of the present disclosure.

[0052] refer to Figure 2 In the UE or ENB, the radio protocol of the LTE system consists of a packet data convergence protocol (PDCP) 205 or 240, a radio link control (RLC) 210 or 235, and a medium access control (MAC) 215 or 230. The packet data convergence protocol (PDCP) 205 or 240 may be responsible for IP header compression / decompression operations. The main functions of the PDCP may be summarized as follows.

[0053] -Header compression and decompression: ROHC only

[0054] -Transmission of user data

[0055] - In-sequence delivery of upper layer PDUs during PDCP re-establishment of RLC AM

[0056] - For split bearers in DC (supports RLC AM only): PDCP PDU routing for transmission, PDCP PDU reordering for reception

[0057] -Duplicate detection of lower layer SDUs during PDCP reestablishment of RLC AM

[0058] - For RLC AM, retransmission of PDCP SDUs during handover, and for split bearers of DC, retransmission of PDCP PDUs during PDCP data recovery,

[0059] -Encryption and decryption

[0060] - Timer-based SDU discard in uplink

[0061] The radio link control (hereinafter referred to as "RLC") 210 or 235 may perform an ARQ operation by reconfiguring a PDCP protocol data unit (PDCP PDU) with an appropriate size. The main functions of the RLC may be summarized as follows.

[0062] -Transmission of upper layer PDU

[0063] - Error correction via ARQ (for AM data transmission only)

[0064] -RLC SDU concatenation, segmentation and reassembly (only for UM and AM data transmission)

[0065] - Re-segmentation of RLC data PDU (only for AM data transmission)

[0066] - Reordering of RLC data PDUs (only for UM and AM data transmission)

[0067] - Duplicate detection (for UM and AM data transmission only)

[0068] -Protocol error detection (for AM data transmission only)

[0069] -RLC SDU discard (only for UM and AM data transmission)

[0070] -RLC reconstruction

[0071] The MAC 215 or 230 is connected to several RLC layer devices configured in one UE and can perform multiplexing of RLC PDU to MAC PDU and demultiplexing of RLC PDU from MAC PDU. The main functions of the MAC can be summarized as follows.

[0072] - Mapping between logical channels and transport channels

[0073] - Multiplexing / demultiplexing MAC SDUs belonging to one or different logical channels into / from a transport block (TB) delivered to the physical layer on a transport channel

[0074] -Dispatch information report

[0075] - Error correction through HARQ

[0076] - Priority handling between logical channels of a UE

[0077] - Priority handling between UEs through dynamic scheduling

[0078] -MBMS service logo

[0079] -Transmission format selection

[0080] -filling

[0081] The physical layer 220 or 225 may perform channel coding and modulation of upper layer data and make OFDM symbols to transmit the OFDM symbols on a radio channel, or may perform demodulation and channel decoding of OFDM symbols received on a radio channel and transfer the OFDM symbols to an upper layer.

[0082] Figure 3 is a diagram showing a structure of a next generation mobile communication system according to an embodiment of the present disclosure.

[0083] refer to Figure 3 As shown in the figure, the radio access network of the next generation mobile communication system (hereinafter referred to as NR or 2g) can be composed of a new radio node B (hereinafter referred to as NR gNB or NR base station) 310 and a new radio core network (NR CN) 305. The new radio user equipment (hereinafter referred to as NR UE or UE) 315 can access the external network through the NR gNB 310 and the NR CN 305.

[0084] exist Figure 3In the present invention, the NR gNB 310 may correspond to an evolved Node B (eNB) of an existing LTE system. The NR gNB is connected to the NR UE 315 on a radio channel, and thus can provide services superior to those of the existing Node B. In the next generation mobile communication system, all user services are served on a shared channel, so a device is required to perform scheduling by combining status information such as the buffer status of the UE, the available transmission power status, and the channel status, and the NR gNB 310 may be responsible for this. Typically, one NR gNB 310 may control multiple cells. In order to achieve ultra-high-speed data transmission compared to the existing LTE, a bandwidth equal to or higher than the existing maximum bandwidth may be applied, and beamforming technology may be additionally used in consideration of orthogonal frequency division multiplexing (hereinafter referred to as "OFDM") as a radio access technology. In addition, the NR gNB may adopt an adaptive modulation and coding (hereinafter referred to as "AMC") scheme that determines the modulation scheme and channel coding rate to match the channel status of the UE. The NR CN 305 may perform the functions of mobility support, bearer establishment, and QoS configuration. NR CN is a device responsible not only for the mobility management function of UE but also for various control functions, and can be connected to multiple base stations. In addition, the next generation mobile communication system can be interlocked with the existing LTE system, and NR CN can be connected to MME 325 through a network interface. MME can be connected to eNB 330 which is an existing base station.

[0085] Figure 4 is a diagram showing a radio protocol structure of a next generation mobile communication system according to an embodiment of the present disclosure.

[0086] Reference Figure 4 In the UE or NR base station, the radio protocol of the next generation mobile communication system may include NR SDAP401 or 445, NR PDCP 405 or 440, NR RLC 410 or 435, NR MAC 415 or 430 and NR PHY 420 or 425.

[0087] The main functions of NR SDAP 401 or 445 may include some of the following functions.

[0088] -Transmission of user plane data

[0089] - Mapping between QoS flows and DRBs for both DL and UL

[0090] - Marking of QoS flow ID in both DL and UL packets

[0091] -Reflective QoS flow to DRB mapping for UL SDAP PDU

[0092] Regarding SDAP layer devices, for each PDCP layer device, bearer or logical channel, the UE can be configured through an RRC message whether to use the header of the SDAP layer device or the function of the SDAP layer device. If the SDAP header is configured, the UE can indicate that the UE can update or reconfigure the mapping information about uplink and downlink QoS flows and data bearers through the NAS QoS reflection configuration 1-bit indicator (NAS reflection QoS) and AS QoS reflection configuration 1-bit indicator (AS reflection QoS) of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used as data processing priority to support smooth services, scheduling information, etc.

[0093] The main functions of NR PDCP 405 or 440 may include some of the following functions.

[0094] -Header compression and decompression: ROHC only

[0095] -Transmission of user data

[0096] - Sequential delivery of upper layer PDUs

[0097] - Out-of-order delivery of upper layer PDUs

[0098] - Reordering of received PDCP PDUs

[0099] - Duplicate detection of lower layer SDU

[0100] -Retransmission of PDCP SDU

[0101] -Encryption and decryption

[0102] - Timer-based SDU discard in uplink

[0103] As described above, the reordering of the NR PDCP device may mean reordering the PDCP PDUs received from the lower layer based on the PDCP sequence number (SN), and may include delivering the data to the upper layer in the reordered order, or delivering immediately regardless of the order. In addition, the reordering may include recording the lost PDCP PDUs by reordering, status reporting of the lost PDCP PDUs to the transmitting side, and retransmission requests for the lost PDCP PDUs.

[0104] The main functions of NR RLC 410 or 435 may include some of the following functions.

[0105] -Transmission of upper layer PDU

[0106] - Sequential delivery of upper layer PDUs

[0107] - Out-of-order delivery of upper layer PDUs

[0108] - Error correction via ARQ

[0109] - Connection, segmentation and reassembly of RLC SDU

[0110] - Re-segmentation of RLC data PDUs

[0111] - Reordering of RLC data PDUs

[0112] - Duplicate detection

[0113] -Protocol error detection

[0114] -RLC SDU discarded

[0115] -RLC reconstruction

[0116] As described above, the sequential delivery of the NR RLC device may mean the sequential delivery of the RLC SDU received from the lower layer to the upper layer. In the case where an initial RLC SDU is split into several RLC SDUs to be received, the sequential delivery of the NR RLC device may include the reassembly and delivery of the RLC SDU, reordering of the received RLC PDUs based on the RLC sequence number (SN) or the PDCP sequence number (SN), recording the lost RLC PDU by reordering, reporting the status of the lost RLC PDU to the transmitting side, and requesting retransmission of the lost RLC PDU. The sequential delivery of the NR RLC device may include: if there is a lost RLC SDU, only the RLC SDU before the lost RLC SDU is sequentially delivered to the upper layer; if a specific timer has expired despite the presence of a lost RLC SDU, all RLC SDUs received before the timer starts its operation are sequentially delivered to the upper layer; or if a specific timer has expired despite the presence of a lost RLC SDU, all RLC SDUs received so far are sequentially delivered to the upper layer. The NR RLC device may process the RLC PDUs in the order in which they are received (in the order of arrival, regardless of the order of sequence numbers or sequence numbers), and may transmit the processed RLC PDUs to the PDCP device in an out-of-order delivery manner. In the case of receiving segments, the NR RLC device may receive the segments stored in the buffer or to be received later, reconfigure them into a complete RLC PDU, and then transmit the reconfigured RLC PDU to the PDCP device. The NR RLC layer may not include a connection function, and this function may be performed by the NR MAC layer, or may be replaced by a multiplexing function of the NR MAC layer.

[0117] As described above, the out-of-order delivery of the NR RLC device may mean a function of directly transmitting the RLC SDU received from the lower layer to the upper layer without considering their order, and if an initial RLC SDU is split into several RLC SDUs to be received, the out-of-order delivery of the NR RLC device may include the reassembly and delivery of the RLC SDU, and the function of storing and sorting the RLC SN or PDCP SN of the received RLC PDU and recording the lost RLC PDU.

[0118] NR MAC 415 or 430 can be connected to several NR RLC layer devices configured in one UE, and the main functions of NR MAC may include some of the following functions.

[0119] - Mapping between logical channels and transport channels

[0120] -Multiplexing / demultiplexing of MAC SDU

[0121] -Dispatch information report

[0122] -HARQ function (error correction through HARQ)

[0123] - Priority handling between logical channels of a UE

[0124] - Priority handling between UEs through dynamic scheduling

[0125] -MBMS service logo

[0126] -Transmission format selection

[0127] -filling

[0128] The NR PHY layer 420 or 425 may perform channel coding and modulation of upper layer data to configure and transmit OFDM symbols on a radio channel, or may perform demodulation and channel decoding of OFDM symbols received on a radio channel to transmit the demodulated and channel-decoded symbols to an upper layer.

[0129] Figure 5 is a diagram illustrating a method for collecting and reporting cell measurement information according to an embodiment of the present disclosure.

[0130] In the case of network establishment or optimization, the mobile communication service provider can measure the signal strength in the service area that is usually expected, and based on this, the base station can be arranged or readjusted in the service area. The service provider can load the signal measurement equipment in the vehicle and collect the cell measurement information in the service area, but this may require a lot of time and cost. Since the process is usually performed by using a vehicle, it can be generally referred to as "drive test". In addition, in order to support operations such as cell reselection or switching and service cell addition during movement between cells, the UE is equipped with a function that can measure the signal from the base station. Therefore, the UE in the service area can be used instead of the drive test, which can be referred to as "drive test minimization (MDT)". The service provider can configure the MDT operation for a specific UE through various configuration devices of the network, and the UE can collect and store the signal strength information from the serving cell and the neighboring cell in RRC connected mode (RRC_CONNECTED), RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE). In addition, the UE can also store various information, such as location information, time information and signal quality information. When the UE is in connected mode, the stored information can be reported to the network, and the information can be transmitted to a specific server.

[0131] MDT operations can be simply divided into immediate MDT and recorded MDT.

[0132] A feature of immediate MDT may be to immediately report the collected information to the network. Only UEs in RRC connected mode can perform immediate reporting. In general, the Radio Resource Management (RRM) measurement process may be reused to support operations of handover and serving cell addition, and location information and time information may be additionally reported.

[0133] A feature of logged MDT may be that the collected information is stored without immediately reporting it to the network, after which the UE reports the stored information after switching to RRC connected mode. Typically, a UE in RRC idle mode or RRC inactive mode that cannot immediately report to the network may perform logged MDT. In the present disclosure, a feature of a UE in RRC inactive mode introduced in a next generation mobile communication system may be that it performs logged MDT. When a specific UE is in RRC connected mode, the network may provide the UE with configuration information for performing logged MDT operations, and the UE may collect and store the configured information after being switched to RRC idle mode or RRC inactive mode. This is related to Table 1 below.

[0134] [Table 1]

[0135]

[0136]

[0137] Figure 6 is a diagram illustrating operations between a UE and a base station for the UE to report mobility history information to an LTE base station in an LTE system in the related art according to an embodiment of the present disclosure.

[0138] refer to Figure 6 , UE 601 may be in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE).

[0139] The UE 601 in RRC idle mode may send an RRC connection request message (RRCConnectionRequest) to the base station in order to perform an RRC connection establishment process with the base station 602 (610). In response to this, the base station having received the RRC connection request message may send an RRC connection establishment message (RRCConnectionSetup) to the UE (615). The UE having received the RRC connection establishment message may apply this and may switch to RRC connection mode (616). In addition, the UE in RRC connection mode may send an RRC connection establishment completion message (RRCConnectionSetupComplete) to the base station (620). If the UE supports the storage of mobility history information and the UE has available mobility history information in the VarMobilityHistoryReport, the UE may include a mobilityHistoryAvail indicator indicating that the mobility history information is available in the RRC connection establishment completion message to be sent to the base station (620).

[0140] UE 601 in RRC inactive mode may send an RRC connection resumption request message (RRCConnectionResumeRequest) to the base station to perform an RRC connection resumption procedure with base station 602 (610). In response, the base station having received the RRC connection resumption request message may send an RRC connection resumption message (RRCConnectionResume) to the UE (615). The UE having received the RRC connection establishment message may apply this and may switch to RRC connection mode (616). In addition, the UE in RRC connection mode may send an RRC connection resumption complete message (RRCConnectionResumeComplete) to the base station (620). If the UE supports storage of mobility history information and the UE has available mobility history information in VarMobilityHistoryReport, the UE may include a mobilityHistoryAvail indicator (620) in the RRC connection resumption complete message to be sent to the base station.

[0141] UE 601 that has not yet performed security settings can perform an initial security activation process (621) with base station 602. For example, UE that has not yet performed security settings can refer to a UE that has switched from RRC idle mode to RRC connected mode. Specifically, UE 601 can send a security mode command message (SecurityModeCommand) to base station 602, and in response, the base station can send a security mode completion message (SecurityModeComplete) to the UE.

[0142] At operation 625, in order to perform the RRC connection reconfiguration process, the base station 602 may send an RRC connection reconfiguration message (RRCConnectionReconfiguration) to the UE 601 in RRC connected mode. The UE applies the received RRC connection reconfiguration message and, in response thereto, may send an RRC connection reconfiguration complete message (RRCConnectionReconfigurationComplete) to the base station (630).

[0143] At operation 635, in the case where security activation has been successfully performed, the base station 602 may perform a UE information collection procedure. In order to request mobility history information from the UE 601, the base station 602 may send a UE information request message (UEInformationRequest) to the UE (635). In order to request mobility history information, the UE information request message may include a MobilityHistoryReportReq indicator.

[0144] At operation 640, the UE 601 that has successfully performed security activation may send a UE information response message (UEInformationResponse) (640) to the base station 602. If mobilityHistoryReportReq is set to "true" in the received UE information request message, the UE may perform the following series of processes.

[0145] - The UE may include a mobilityHistoryReport and set it to include entries from the VarMobilityHistoryReport.

[0146] - The UE may include an entry for the current cell in the mobilityHistoryReport, if necessary, after removing the oldest entry, and set its fields as follows.

[0147] - The UE may set visitedCellId (visited cell ID) to the global cell identity of the current cell.

[0148] - The UE may set the field timeSpent to the time spent in the current cell.

[0149] By performing the above process, the UE may include the mobilityHistoryReport in the UE Information Response message, and may send the UE Information Response message to the base station (640).

[0150] Figure 7 is a diagram illustrating an operation of a UE reporting mobility history information to a base station in an LTE system in the related art according to an embodiment of the present disclosure.

[0151] A UE supporting storage of mobility history information may enter an out-of-service state (e.g., the UE does not reside on any cell or does not access any cell, i.e., the UE is in any cell selection state, or does not reside on any suitable cell or any acceptable cell), and change cells through a cell selection process, a cell reselection process, or a handover process. In this case, the UE may be in RRC idle mode (RRC_IDLE), RRC inactive mode (RRC_INACTIVE), or RRC connected mode (RRC_CONNECTED). The UE may store mobility history information in VarMobilityHistoryReport according to the following conditions.

[0152] Condition 1-1: When changing an E-UTRA cell consisting of a PCell in RRC_CONNECTED or a serving cell in RRC_IDLE to another E-UTRA or inter-RAT cell, or when entering no service from an E-UTRA cell

[0153] Condition 1-2: When changing an E-UTRA cell consisting of a PCell in RRC_CONNECTED or a serving cell in RRC_IDLE or RRC_INACTIVE to another E-UTRA or inter-RAT cell, or when entering no service from an E-UTRA cell

[0154] Condition 2-1: When entering E-UTRA (in RRC_CONNECTED or RRC_IDLE) when previously without service and / or using another RAT

[0155] Condition 2-2: When entering E-UTRA (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) when previously without service and / or using another RAT

[0156] In the case where the UE stores the mobility history information in varMobilityHistoryReport according to condition 1-1 or condition 1-2, if necessary, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following.

[0157] - If the global cell identity of the previous PCell / serving cell is available, the UE may include the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, the UE may include the physical cell identity and carrier frequency of the previous PCell / serving cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0158] The difference between condition 1-1 and condition 1-2 is whether the UE stores the mobility history information occurring in the RRC inactive mode. The difference is that the UE storing the mobility history information in VarMobilityHistoryReport according to condition 1-1 does not store the mobility history information occurring in the RRC inactive mode in the VarMobilityHistoryReport, while the UE storing the mobility history information in VarMobilityHistoryReport according to condition 1-2 stores the mobility history information occurring in the RRC inactive mode in the VarMobilityHistoryReport. Therefore, compared with condition 1-1, the UE storing the mobility history information in VarMobilityHistoryReport according to condition 1-2 has the advantage of being able to report more accurate mobility history information to the base station.

[0159] In the case where the UE stores the mobility history information in VarMobilityHistoryReport according to condition 2-1 or condition 2-2, if necessary, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following.

[0160] – The UE may set the field timeSpent of the entry to the time spent outside E-UTRA. The time spent outside E-UTRA may mean the time spent in no service, or the time when another RAT other than E-UTRA cells is used, or the sum of the time spent in no service and the time when another RAT other than E-UTRA cells is used.

[0161] The difference between condition 2-1 and condition 2-2 lies in whether the UE stores mobility history information occurring in RRC inactive mode. The difference is that the UE storing mobility history information in VarMobilityHistoryReport according to condition 2-1 does not store mobility history information occurring in RRC inactive mode in VarMobilityHistoryReport, while the UE storing mobility history information in VarMobilityHistoryReport according to condition 2-2 stores mobility history information occurring in RRC inactive mode in VarMobilityHistoryReport. Therefore, compared with condition 1-1, the UE storing mobility history information in VarMobilityHistoryReport according to condition 2-2 has the advantage of being able to report more accurate mobility history information to the base station.

[0162] Reference Figure 7 In the above operations through operations 705 to 745, the UE may store the mobility history information in VarMobilityHistoryReport. For example, the UE may store at least one of the following information in VarMobilityHistoryReport.

[0163] - Global cell identity of E-UTRA cell 1, or carrier frequency and physical cell identity, and time spent in E-UTRA cell 1 10 s (705)

[0164] - Global cell identity of E-UTRA cell 2, or carrier frequency and physical cell identity, and time spent in E-UTRA cell 2 5 s (710)

[0165] - Time spent in IRAT (inter-RAT) cell 1 10 seconds (715)

[0166] - Global cell identity of E-UTRA cell 3, or carrier frequency and physical cell identity, and time spent in E-UTRA cell 3 2s (720)

[0167] -Time spent in no service 3s (725)

[0168] - Global cell identity of E-UTRA cell 4, or carrier frequency and physical cell identity, and time spent in E-UTRA cell 4 5 s (730)

[0169] - Total time spent in No Service and IRAT Cell 2 20 seconds (735 and 740)

[0170] For reference, the global cell identity of the E-UTRA cell may represent the following information as shown in Table 2 below.

[0171] [Table 2]

[0172]

[0173] At operation 745, the UE in RRC connected mode may connect to the E-UTRA cell 5 as the PCell (primary cell). At operation 750, the UE may receive a UE information request message including mobilityHistoryReportReq from the LTE base station. If mobilityHistoryReportReq is set to true, at operation 755, the UE may include mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport.

[0174] At operation 760, if necessary, the UE may remove the oldest entry value from the current cell (e.g., E-UTRA cell 5), if possible, and may include the global cell identifier of the current cell (E-UTRA cell 5) and the time spent in E-UTRA cell 5 for the entry present in the VarMobilityHistoryReport in the MobilityHistoryReport.

[0175] At operation 765, the UE may include the above-mentioned mobilityHistoryReport in a UE Information Response message, and may send the UE Information Response message to the LTE base station.

[0176] Figure 8 2 is a diagram illustrating operations between a UE and a base station for the UE to report mobility history information to an NR base station in a next generation mobile communication system according to an embodiment of the present disclosure.

[0177] refer to Figure 8 , UE 801 may be in RRC idle mode (RRC_IDLE) or in RRC inactive mode (RRC_INACTIVE).

[0178] In order to perform the RRC connection establishment process with the base station 802, the UE 801 in the RRC idle mode can send an RRC connection establishment request message (RRCSetupRequest) to the base station (810). In response to this, the base station that has received the RRC connection establishment message can send an RRC connection establishment message (RRCSetup) to the UE (815). The UE that has received the RRC connection establishment message can apply this and can switch to the RRC connection mode (816). In addition, the UE in the RRC connection mode can send an RRC connection establishment completion message (RRCSetupComplete) to the base station (820). If the UE supports the storage of mobility history information and the UE has available mobility history information in the VarMobilityHistoryReport, the UE can include the mobilityHistoryAvail indicator (820) in the RRC connection establishment completion message to be sent to the base station.

[0179] In order to perform the RRC connection recovery process with the base station 802, the UE 801 in the RRC inactive mode can send an RRC connection recovery request message or an RRC connection recovery request 1 message (RRCResumeRequest or RRCResumeRequest 1) to the base station (810). In response, the base station that has received the RRC connection recovery request message can send an RRC connection recovery message (RRCResume) to the UE (815). The UE that has received the RRC connection recovery message can apply the message and can switch to the RRC connection mode (816). In addition, the UE in the RRC connection mode can send an RRC connection recovery completion message (RRCResumeComplete) to the base station (820). If the UE supports the storage of mobility history information and the UE has available mobility history information in the VarMobilityHistoryReport, the UE can include the mobilityHistoryAvail indicator in the RRC connection recovery completion message to be sent to the base station 820.

[0180] UE 801 that has not yet performed security settings can perform an initial security activation process (821) with base station 802. For example, UE that has not yet performed security settings can refer to a UE that has switched from RRC idle mode to RRC connected mode. Specifically, UE 801 can send a security mode command message (SecurityModeCommand) to base station 802, and in response, the base station can send a security mode completion message (SecurityModeComplete) to the UE.

[0181] At operation 825, in order to perform the RRC connection reconfiguration process, the base station 802 may send an RRC connection reconfiguration message (RRCReconfiguration) to the UE 801 in the RRC connection mode. The UE applies the received RRC connection reconfiguration message and, in response thereto, may send an RRC connection reconfiguration complete message (RRCReconfigurationComplete) to the base station (830).

[0182] At operation 835, in the case where security activation has been successfully performed, the base station 802 may perform a UE information collection procedure. In order to request mobility history information from the UE 801, the base station 802 may send a UE information request message (UEInformationRequest) to the UE (835). In order to request mobility history information, the UE information request message may include a MobilityHistoryReportReq indicator.

[0183] At operation 840, the UE 801 having successfully performed security activation may transmit a UE information response message (UEInformationResponse) to the base station 802 (840). If mobilityHistoryReportReq is set to "true" in the received UEInformationRequest message, the UE may perform the following series of processes.

[0184] - The UE may include the mobilityHistoryReport and set it to include entries from the VarMobilityHistoryReport.

[0185] - The UE may include an entry for the current cell in the mobilityHistoryReport, if necessary, possibly after removing the oldest entry, and set its fields as follows.

[0186] -The UE may set visitedCellId to the global cell identity of the current cell.

[0187] - The UE may set the field timeSpent to the time spent in the current cell.

[0188] By performing the above process, the UE may include the mobilityHistoryReport in the UE Information Response message, and may send the UE Information Response message to the base station (840).

[0189] Fig. 9 is a diagram illustrating the operation of a UE for reporting mobility history information to an NR base station in a next generation mobile system according to an embodiment of the present disclosure.

[0190] In the case of changing cells through a cell selection process, a cell reselection process, or a handover process, a UE supporting storage of mobility history information may enter an out-of-service state (e.g., the UE does not reside on any cell or does not access any cell, i.e., the UE is in any cell selection state, or does not reside on any suitable cell or any acceptable cell). The UE may be in RRC idle mode (RRC_IDLE), RRC inactive mode (RRC_INACTIVE), or RRC connected mode (RRC_CONNECTED). The UE may store mobility history information in the VarMobilityHistoryReport of NR if the following conditions are met.

[0191] Condition 1: When changing a cell consisting of a PCell in RRC_CONNECTED or a serving cell in RRC_IDLE or RRC_INACTIVE (for an NR cell) to another NR or E-UTRA, or when entering no service from an NR cell

[0192] Condition 2: When entering NR when there was no service previously (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE)

[0193] Condition 3: When entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) when using E-UTRA

[0194] In the case where the UE satisfies condition 1 and stores the mobility history information in the varMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry, if necessary, according to the following.

[0195] - If the global cell identity of the previous PCell / serving cell is available, the UE may store the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, the UE may include the physical cell identity and carrier frequency of the cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0196] In the case where the UE satisfies condition 2 and stores the mobility history information in the VarMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry, if necessary, according to the following.

[0197] - The UE may set the field timeSpent of the entry to the time spent without service.

[0198] If condition 2 is met, according to an embodiment of the present disclosure, the UE may suggest storing only the time spent in no service in the timeSpent field. That is, unlike the LTE system in the related art, the UE is 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 LTE system in the related art, in the case where only the time spent in no service is stored in the timeSpent field, the mobility history information of the UE may be inaccurate. However, the UE has the advantage that it can manage the VarMobilityHistoryReport of LTE and the VarMobilityHistoryReport of NR separately. That is, since the time spent in the inter-RAT cell (E-UTRA cell and / or UTRA cell) is stored and managed separately in the VarMobilityHistoryReport for LTE, it is not stored separately in the VarMobilityHistoryReport for NR, so the implementation efficiency of the UE storing the mobility history information can be improved. For example, in order to reflect the real mobility history information of the UE, the UE does not need to rearrange the order of the VarMobilityHistoryReport of LTE and the VarMobilityHistoryReport of NR.

[0199] In the case where the UE satisfies condition 3 and stores the mobility history information in the VarMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0200] - If the global cell identity of the previous PCell / serving cell (information about E-UTRA cells) is available, the UE may store the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, the UE may include the physical cell identity and carrier frequency of the cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0201] If condition 3 is met, the feature of the UE according to an embodiment of the present disclosure may be to store only the latest E-UTRA cell information in the VarMobilityHistoryReport of NR. As an example, in the case where the cell is changed from E-UTRA cell a to E-UTRA cell b, and the cell is changed from E-UTRA cell b to NR cell, the feature of the UE may be to store only information about E-UTRA cell b in the VarMobilityHistoryReport of NR. That is, since the information about E-UTRA cell a is stored in the VarMobilityHistoryReport of LTE, and the information about E-UTRA cell a is not stored in the VarMobilityHistoryReport of NR, the mobility history information of the UE may be inaccurate, but advantageously, the UE can manage the VarMobilityHistoryReport of LTE and the VarMobilityHistoryReport of NR separately. That is, since information about E-UTRA cell a is stored in VarMobilityHistoryReport of LTE, and only information about E-UTRA cell b is stored in VarMobilityHistoryReport of NR, the implementation efficiency of UE storing mobility history information can be improved. For example, in order to reflect the real mobility history information of the UE, the UE does not need to rearrange the order of VarMobilityHistoryReport of LTE and VarMobilityHistoryReport of NR.

[0202] Reference Fig. 9 In the above operations through operations 905 to 945, the UE may store the mobility history information in the VarMobilityHistoryReport of the NR. For example, the UE may store at least one of the following information in the VarMobilityHistoryReport of the NR.

[0203] - The global cell identity of NR cell 1, or the carrier frequency and physical cell identity, and the time spent in NR cell 1 (10s) (905)

[0204] - The global cell identity of NR cell 2, or the carrier frequency and physical cell identity, and the time spent in NR cell 2 5s (910)

[0205] - Global cell identity of E-UTRA cell 2, or carrier frequency and physical cell identity, and time spent in E-UTRA cell 2 2s (920)

[0206] - The global cell identity of NR cell 3, or the carrier frequency and physical cell identity, and the time spent in NR cell 3 3s (925)

[0207] -Time spent in no service 2s(945)

[0208] For reference, a feature of the UE according to the embodiment may be that the following information is not included in the VarMobilityHistoryReport of the NR.

[0209] - Global cell identity of E-UTRA cell 1, or carrier frequency and physical cell identity, and time spent in E-UTRA cell 1 10s (915)

[0210] -Time spent in no service 5s (930)

[0211] -Time spent in E-UTRA cell 1 10 seconds (935)

[0212] - Global cell identity of E-UTRA cell 3, or carrier frequency and physical cell identity, and time spent in E-UTRA cell 3 10 s (940)

[0213] In the UE according to an embodiment of the present disclosure, the global cell identity of the E-UTRA cell may follow the above embodiment, and the global cell identity of the NR cell may represent the following information as shown in Table 3 below.

[0214] [Table 3]

[0215]

[0216] At operation 950, the UE in RRC connected mode may connect to the NR cell 4 as the PCell (primary cell). At operation 955, the UE may receive a UE information request message including mobilityHistoryReportReq from the NR base station. If mobilityHistoryReportReq is set to true, at operation 960, the UE may include mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport.

[0217] At operation 965, if necessary, the UE may remove the oldest entry value from the current cell (e.g., NR cell 4) if possible, and may include the global cell identifier of the current cell (NR cell 4) and the time spent in NR cell 4 for the entry present in the VarMobilityHistoryReport in the MobilityHistoryReport.

[0218] In operation 970, the UE may include the above-mentioned mobilityHistoryReport in a UE information response message, and may send the UE information response message to the NR base station.

[0219] Fig.10 is a diagram illustrating the operation of a UE for reporting mobility history information to an NR base station in a next generation mobile system according to an embodiment of the present disclosure.

[0220] In the case of changing cells through a cell selection process, a cell reselection process, or a handover process, a UE supporting storage of mobility history information may enter an out-of-service state (e.g., the UE does not reside on any cell or does not access any cell, i.e., the UE is in any cell selection state, or does not reside on any suitable cell or any acceptable cell). The UE may be in RRC idle mode (RRC_IDLE), RRC inactive mode (RRC_INACTIVE), or RRC connected mode (RRC_CONNECTED). The UE may store mobility history information in the VarMobilityHistoryReport of NR if the following conditions are met.

[0221] Condition 1: When changing a cell consisting of a PCell in RRC_CONNECTED or a serving cell in RRC_IDLE or RRC_INACTIVE (for an NR cell) to another NR or E-UTRA, or when entering no service from an NR cell

[0222] Condition 2: When entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) when previously without service and / or using another RAT other than E-UTRA

[0223] Condition 3: When entering NR (in RRC_CONNECTED, RRC_IDLE, or RRC_INACTIVE) while using E-UTRA

[0224] In the case where the UE satisfies condition 1 and stores the mobility history information in the varMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0225] - If the global cell identity of the previous PCell / serving cell is available, the UE may store the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, the UE may include the physical cell identity and carrier frequency of the cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0226] In the case where the UE satisfies condition 2 and stores the mobility history information in the VarMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0227] - The UE may set the field timeSpent of the entry to a time other than the time for NR using E-UTRA.

[0228] If condition 2 is satisfied, according to an embodiment of the present disclosure, the UE may propose to store both the time spent in no service and the time when another RAT other than E-UTRA is used in the timeSpent field. For example, another RAT other than E-UTRA may mean UTRA. That is, since the time spent in another RAT other than E-UTRA may be stored in the mobility history information of the UE, the mobility history information of the UE may become more accurate.

[0229] In the case where the UE satisfies condition 3 and stores the mobility history information in the VarMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0230] - If the global cell identity of the previous PCell / serving cell (information about E-UTRA cells) is available, the UE may store the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, the UE may include the physical cell identity and carrier frequency of the cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0231] If condition 3 is met, the feature of the UE according to the embodiment of the present disclosure may be that only the latest E-UTRA cell information is stored in the VarMobilityHistoryReport of NR. As an example, in the case of changing the cell from E-UTRA cell a to E-UTRA cell b, and changing the cell from E-UTRA cell b to NR cell, the feature of the UE may be that only information about E-UTRA cell b is stored in the VarMobilityHistoryReport. In this case, since the information about E-UTRA cell a is not stored, the mobility history information of the UE may not be accurate, but advantageously, the UE can manage the VarMobilityHistoryReport of LTE and the VarMobilityHistoryReport of NR separately. That is, since the information about E-UTRA cell a is stored in the VarMobilityHistoryReport of LTE, and only the information about E-UTRA cell b is stored in the VarMobilityHistoryReport of NR, the implementation efficiency of the UE storing the mobility history information can be improved. For example, in order to reflect the real mobility history information of the UE, the UE does not need to rearrange the order of the VarMobilityHistoryReport of LTE and the VarMobilityHistoryReport of NR.

[0232] Reference Fig.10 In the above operations through operations 1005 to 1050, the UE may store the mobility history information in the VarMobilityHistoryReport of the NR. For example, the UE may store at least one of the following information in the VarMobilityHistoryReport of the NR.

[0233] - The global cell identity of NR cell 1, or the carrier frequency and physical cell identity, and the time spent in NR cell 1 (10s) (1005)

[0234] - The global cell identity of NR cell 2, or the carrier frequency and physical cell identity, and the time spent in NR cell 2 5s (1010)

[0235] - Global cell identity, or carrier frequency and physical cell identity of E-UTRA cell 2, and time spent in E-UTRA cell 2 2s (1020)

[0236] - The global cell identity of NR cell 3, or the carrier frequency and physical cell identity, and the time spent in NR cell 3 3s (1025)

[0237] - Total time spent in UTRA cell 1 and out of service 12 s (1040 and 1045)

[0238] For reference, a feature of the UE according to an embodiment of the present disclosure may be that the following information is not included in the VarMobilityHistoryReport of the NR.

[0239] - Global cell identity of E-UTRA cell 1, or carrier frequency and physical cell identity, and time spent in E-UTRA cell 1 10s (1015)

[0240] -Time spent in no service 5s (1030)

[0241] - Global cell identity, or carrier frequency and physical cell identity of E-UTRA cell 3, and time spent in E-UTRA cell 3 10 s (1040)

[0242] At operation 1050, the UE in RRC connected mode may be connected to the NR cell 4 which is a PCell (primary cell).

[0243] At operation 1055, the UE may receive a UE information request message including mobilityHistoryReportReq from the NR base station. If mobilityHistoryReportReq is set to true, at operation 1060, the UE may include mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport.

[0244] In operation 1065, if necessary, if possible, the UE may remove the oldest entry value from the current cell (e.g., NR cell 4), and may include the global cell identifier of the current cell (NR cell 4) and the time spent in NR cell 4 for the entry present in the VarMobilityHistoryReport in the mobilityHistoryReport.

[0245] In operation 1070, the UE may include the above-mentioned mobilityHistoryReport in a UE information response message, and may send a UE information response message to the NR base station.

[0246] Fig.11 is a diagram illustrating the operation of a UE for reporting mobility history information to an NR base station in a next generation mobile system according to an embodiment of the present disclosure.

[0247] In the case of changing cells through a cell selection process, a cell reselection process, or a handover process, a UE supporting storage of mobility history information may enter an out-of-service state (e.g., the UE does not reside on any cell or does not access any cell, i.e., the UE is in any cell selection state, or does not reside on any suitable cell or any acceptable cell). The UE may be in RRC idle mode (RRC_IDLE), RRC inactive mode (RRC_INACTIVE), or RRC connected mode (RRC_CONNECTED). The UE may store mobility history information in the VarMobilityHistoryReport of NR if the following conditions are met.

[0248] Condition 1: When changing a cell consisting of a PCell in RRC_CONNECTED or a serving cell in RRC_IDLE or RRC_INACTIVE (for an NR cell) to another NR or E-UTRA, or when entering no service from an NR cell

[0249] Condition 2: When entering NR when there was no service previously (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE)

[0250] Condition 3: When entering NR (in RRC_CONNECTED, RRC_IDLE, or RRC_INACTIVE) while using E-UTRA

[0251] Condition 4: When changing a cell consisting of a PCell in RRC_CONNECTED or a serving cell in RRC_IDLE or RRC_INACTIVE to another E-UTRA, or when entering no service

[0252] In the case where the UE satisfies condition 1 and stores the mobility history information in the varMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0253] - If the global cell identity of the previous PCell / serving cell is available, the UE may store the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, the UE may include the physical cell identity and carrier frequency of the cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0254] In the case where the UE satisfies condition 2 and stores the mobility history information in the VarMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0255] - The UE may set the field timeSpent of the entry to the time spent without service.

[0256] In the case where the UE satisfies condition 3 and stores the mobility history information in the VarMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0257] - If the global cell identity of the previous PCell / serving cell (information about E-UTRA cells) is available, the UE may store the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, the UE may include the physical cell identity and carrier frequency of the cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0258] In the case where the UE satisfies condition 4 and stores the mobility history information in the VarMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0259] - If the global cell identity of the previous PCell / serving cell (information about E-UTRA cells) is available, the UE may store the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, the UE may include the physical cell identity and carrier frequency of the cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0260] Reference Fig.11 In the above operations through operations 1105 to 1150, the UE may store the mobility history information in the VarMobilityHistoryReport of the NR. For example, the UE may store at least one of the following information in the VarMobilityHistoryReport of the NR.

[0261] - The global cell identity of NR cell 1, or the carrier frequency and physical cell identity, and the time spent in NR cell 1 (10s) (1105)

[0262] - The global cell identity of NR cell 2, or the carrier frequency and physical cell identity, and the time spent in NR cell 2 5s (1110)

[0263] - Global cell identity of E-UTRA cell 1, or carrier frequency and physical cell identity, and time spent in E-UTRA cell 1 10 s (1115)

[0264] - Global cell identity, or carrier frequency and physical cell identity of E-UTRA cell 2, and time spent in E-UTRA cell 2 2s (1120)

[0265] - The global cell identity of NR cell 3, or the carrier frequency and physical cell identity, and the time spent in NR cell 3 3s (1125)

[0266] -Time spent in no service 2s(1145)

[0267] For reference, a feature of the UE according to an embodiment of the present disclosure may be that the following information is not included in the VarMobilityHistoryReport of the NR.

[0268] -Time spent in no service 5s (1130)

[0269] - Global cell identity of E-UTRA cell 3, or carrier frequency and physical cell identity, and time spent in E-UTRA cell 3 10 s (1135)

[0270] -Time spent in UTRA 1 cell 10s (1140)

[0271] At operation 1150, the UE in RRC connected mode may be connected to the NR cell 4 which is a PCell (primary cell).

[0272] At operation 1155, the UE may receive a UE information request message including mobilityHistoryReportReq from the NR base station. If mobilityHistoryReportReq is set to true, at operation 1160, the UE may include mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport.

[0273] In operation 1165, if necessary, if possible, the UE may remove the oldest entry value from the current cell (e.g., NR cell 4), and may include the global cell identifier of the current cell (NR cell 4) and the time spent in NR cell 4 for the entry present in the VarMobilityHistoryReport in the mobilityHistoryReport.

[0274] In operation 1170, the UE may include the above-mentioned mobilityHistoryReport in a UE information response message, and may send the UE information response message to the NR base station.

[0275] Fig.12 is a diagram illustrating the operation of a UE for reporting mobility history information to an NR base station in a next generation mobile system according to an embodiment of the present disclosure.

[0276] In the case of changing cells through a cell selection process, a cell reselection process, or a handover process, a UE supporting storage of mobility history information may enter an out-of-service state (e.g., the UE does not reside on any cell or does not access any cell, i.e., the UE is in any cell selection state, or does not reside on any suitable cell or any acceptable cell). The UE may be in RRC idle mode (RRC_IDLE), RRC inactive mode (RRC_INACTIVE), or RRC connected mode (RRC_CONNECTED). The UE may store mobility history information in the VarMobilityHistoryReport of NR if the following conditions are met.

[0277] Condition 1: When changing a cell consisting of a PCell in RRC_CONNECTED or a serving cell in RRC_IDLE or RRC_INACTIVE (for an NR cell) to another NR or E-UTRA, or when entering no service from an NR cell

[0278] Condition 2: When entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) when using E-UTRA

[0279] In the case where the UE satisfies condition 1 and stores the mobility history information in the varMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0280] - If the global cell identity of the previous PCell / serving cell is available, the UE may include the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, the UE may include the physical cell identity and carrier frequency of the cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0281] In the case where the UE satisfies condition 2 and stores the mobility history information in the VarMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0282] -The global cell identity or carrier frequency and physical cell identity of the latest E-UTRA cell before entering the NR cell can be stored in the visitedCellId field, and the total time spent outside NR (which means the time spent in inter-RAT cells and the time spent in no service) can be stored in the timeSpent field. If the total time spent outside NR is stored in the timeSpent field, it is advantageous that the base station can identify the total time of the mobility of the UE before entering the NR cell. In addition, the global cell identity or carrier frequency and physical cell identity of the latest E-UTRA cell before entering the NR cell can be stored in the visitedCellId field, and the total time spent in the E-UTRA cell and in no service (the time spent in the E-UTRA cell and the time spent in no service) can be stored in the timeSpent field. If the total time spent in the E-UTRA cell and out of time is stored in the timeSpent field, the base station can grasp the mobility of the UE more inaccurately by identifying only the time spent in the E-UTRA cell before entering the NR cell and the time spent out of service, but the UE does not store the time spent in another RAT other than the E-UTRA cell in the VarMobilityHistoryReport of NR, thus facilitating the implementation of the UE storing mobility history information. In addition, the global cell identifier or carrier frequency and physical cell identifier of the latest E-UTRA cell before entering the NR cell can be stored in the visitedCellId field, and the total time spent in the E-UTRA cell (time spent in the E-UTRA cell) can be stored in the timeSpent field. If only the total time spent in the E-UTRA cell is stored in the timeSpent field, the base station can grasp the mobility of the UE more inaccurately by identifying only the time spent in the E-UTRA cell before entering the NR cell, but the UE does not store the time spent in no service and the time spent in inter-RAT cells (except E-UTRA) in the VarMobilityHistoryReport of NR, so it is advantageous to facilitate the implementation of the UE that stores mobility history information.

[0283] Reference Fig.12 In the above operations through operations 1205 to 1220, the UE may store the mobility history information in the VarMobilityHistoryReport of the NR. For example, the UE may store at least one of the following information in the VarMobilityHistoryReport of the NR.

[0284] - The global cell identity of NR cell 1, or the carrier frequency and physical cell identity, and the time spent in NR cell 1 (10s) (1205)

[0285] - The global cell identity, or the carrier frequency and physical cell identity of NR cell 2, and the total time spent in E-UTRA cell 1 and E-UTRA cell 2 (1210 and 1215) 12s

[0286] At operation 1220, the UE in the RRC connected mode may be connected to the NR cell 2 which is the PCell (primary cell).

[0287] At operation 1225, the UE may receive a UE information request message including mobilityHistoryReportReq from the NR base station. If mobilityHistoryReportReq is set to true, at operation 1230, the UE may include mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport.

[0288] In operation 1235, if necessary, if possible, the UE may remove the oldest entry value from the current cell (e.g., NR cell 2), and may include the global cell identifier of the current cell (NR cell 2) and the time spent in NR cell 2 for the entry present in the VarMobilityHistoryReport in the mobilityHistoryReport.

[0289] In operation 1240, the UE may include the above-mentioned mobilityHistoryReport in a UE information response message, and may send the UE information response message to the NR base station.

[0290] Fig.13 is a diagram illustrating the operation of a UE for reporting mobility history information to an NR base station in a next generation mobile system according to an embodiment of the present disclosure.

[0291] In the case of changing cells through a cell selection process, a cell reselection process, or a handover process, a UE supporting storage of mobility history information may enter an out-of-service state (e.g., the UE does not reside on any cell or does not access any cell, i.e., the UE is in any cell selection state, or does not reside on any suitable cell or any acceptable cell). The UE may be in RRC idle mode (RRC_IDLE), RRC inactive mode (RRC_INACTIVE), or RRC connected mode (RRC_CONNECTED). The UE may store mobility history information in the VarMobilityHistoryReport of NR if the following conditions are met.

[0292] Condition 1: When changing a cell consisting of a PCell in RRC_CONNECTED or a serving cell in RRC_IDLE or RRC_INACTIVE (for an NR cell) to another NR or E-UTRA, or when entering no service from an NR cell

[0293] Condition 2: When entering NR when there was no service previously (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE)

[0294] Condition 3: When entering NR (in RRC_CONNECTED or RRC_IDLE or RRC_INACTIVE) when using E-UTRA

[0295] In the case where the UE satisfies condition 1 and stores the mobility history information in the varMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0296] - If the global cell identity of the previous PCell / serving cell is available, the UE may store the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, the UE may include the physical cell identity and carrier frequency of the cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0297] In the case where the UE satisfies condition 2 and stores the mobility history information in the VarMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0298] - The UE may set the field timeSpent of the entry to the time spent without service.

[0299] In the case where the UE satisfies condition 3 and stores the mobility history information in the VarMobilityHistoryReport of the NR, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0300] - If the global cell identity of the previous PCell / serving cell (information about E-UTRA cells) is available, the UE may store the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, the UE may include the physical cell identity and carrier frequency of the cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0301] If the following conditions are met, the UE may store the mobility history information in the VarMobilityHistoryReport of LTE and may report this additionally when reporting the UE's mobility history information to the NR base station.

[0302] Condition 4-1: When changing a cell consisting of a PCell in RRC_CONNECTED or a serving cell in RRC_IDLE to another E-UTRA or inter-RAT cell, or when entering no service from an E-UTRA cell (e.g., a UE in RRC connected mode may refer to a PCell, and a UE in RRC idle mode may refer to a serving cell)

[0303] Condition 4-2: When changing a cell consisting of a PCell in RRC_CONNECTED or a serving cell in RRC_IDLE or RRC_INACTIVE to another E-UTRA or inter-RAT cell, or when entering out of service from an E-UTRA cell (e.g., a UE in RRC connected mode may refer to a PCell, and a UE in RRC idle mode or a UE in RRC inactive mode may refer to a serving cell)

[0304] Condition 5-1: When entering E-UTRA (in RRC_CONNECTED or RRC_IDLE) when previously no service and / or using another RAT other than NR

[0305] Condition 5-2: When entering E-UTRA (in RRC_CONNECTED or RRC_IDLE or RRC inactive mode) when previously no service and / or using another RAT other than NR

[0306] If the UE stores the mobility history information in the VarMobilityHistoryReport of LTE according to condition 4-1 or condition 4-2, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following, if necessary.

[0307] - If the global cell identity of the previous PCell / serving cell is available, the UE may store the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, the UE may include the physical cell identity and carrier frequency of the cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0308] The difference between condition 4-1 and condition 4-2 is whether the UE stores the mobility history information occurring in the RRC inactive mode. The difference is that the UE storing the mobility history information in VarMobilityHistoryReport according to condition 4-1 does not store the mobility history information occurring in the RRC inactive mode in VarMobilityHistoryReport, while the UE storing the mobility history information in VarMobilityHistoryReport according to condition 4-2 stores the mobility history information occurring in the RRC inactive mode in VarMobilityHistoryReport.

[0309] In the case where the UE stores the mobility history information in the VarMobilityHistoryReport according to Condition 5-1 or Condition 5-2, if necessary, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following.

[0310] - The UE may set the field timeSpent of the entry to the time spent outside E-UTRA. The time spent outside E-UTRA may refer to the time spent in no service, or the time when using another RAT that is not an E-UTRA cell or an NR cell, or the time spent in no service and the time when using another RAT that is not an E-UTRA cell or an NR cell.

[0311] The difference between condition 5-1 and condition 5-2 lies in whether the UE stores mobility history information occurring in RRC inactive mode. The difference is that the UE storing mobility history information in VarMobilityHistoryReport according to condition 5-1 does not store mobility history information occurring in RRC inactive mode in VarMobilityHistoryReport, while the UE storing mobility history information in VarMobilityHistoryReport according to condition 5-2 stores mobility history information occurring in RRC inactive mode in VarMobilityHistoryReport. Therefore, compared with condition 2-1, the UE storing mobility history information in VarMobilityHistoryReport according to condition 2-2 has the advantage of being able to report more accurate mobility history information to the base station.

[0312] Reference Fig.13 In the above operations through operations 1305 to 1350, the UE may store the mobility history information in the VarMobilityHistoryReport of the NR. For example, the UE may store at least one of the following information in the VarMobilityHistoryReport of the NR.

[0313] - The global cell identity of NR cell 1, or the carrier frequency and physical cell identity, and the time spent in NR cell 1 (10s) (1305)

[0314] - The global cell identity of NR cell 2, or the carrier frequency and physical cell identity, and the time spent in NR cell 2 5s (1310)

[0315] - Global cell identity, or carrier frequency and physical cell identity of E-UTRA cell 2, and time spent in E-UTRA cell 2 2s (1320)

[0316] - The global cell identity of NR cell 3, or the carrier frequency and physical cell identity, and the time spent in NR cell 3 3s (1325)

[0317] -Time spent in no service 2s(1345)

[0318] In the above operations through operations 1305 to 1350, the UE may store the mobility history information in the VarMobilityHistoryReport of LTE. For example, the UE may store at least one of the following information in the VarMobilityHistoryReport of LTE.

[0319] - Global cell identity of E-UTRA cell 1, or carrier frequency and physical cell identity, and time spent in E-UTRA cell 1 10s (1315)

[0320] -Time spent in service 5s (1330)

[0321] - Global cell identity of E-UTRA cell 3, or carrier frequency and physical cell identity, and time spent in E-UTRA cell 3 10 s (1335)

[0322] -Time spent in UTRA cell 1 10s (1340)

[0323] At operation 1350, the UE in RRC connected mode may be connected to the NR cell 4 which is a PCell (primary cell).

[0324] At operation 1355, the UE may receive a UE information request message including mobilityHistoryReportReq from the NR base station. If mobilityHistoryReportReq is set to true, at operation 1360, the UE may include mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport. In addition, the entry values ​​in LTE's mobilityHistoryReport may be included in NR's mobilityHistoryReport, or may be included in the NR UE capability response message, or LTE's mobilityHistoryReport may be included separately in LTE's mobilityHistoryReport. In this case, the entry values ​​may be arranged in the order of steps 1305 to 1350, and may then be included in the NR UE capability response message.

[0325] In operation 1365, if necessary, the UE may remove the oldest entry value from the current cell (e.g., NR cell 4), and may include the global cell identifier of the current cell (NR cell 4) and the time spent in NR cell 4 for the entries present in the VarMobilityHistoryReport in the VarMobilityHistoryReport.

[0326] In operation 1370, the UE may include the above-mentioned mobilityHistoryReport in a UE information response message, and may send the UE information response message to the NR base station.

[0327] Fig.14 is a block diagram showing the internal structure of a UE according to an embodiment of the present disclosure.

[0328] Referring to the above drawings, the UE may include a Radio Frequency (RF) processor 1410 , a baseband processor 1420 , a storage unit 1430 , and a controller 1440 .

[0329] The RF processor 1410 may perform functions such as signal band conversion and amplification for sending and receiving signals on a radio channel. That is, the RF processor 1410 up-converts the baseband signal provided by the baseband processor 1420 to an RF band signal to send the converted signal through the antenna, and down-converts the RF band signal received by the antenna to a baseband signal. For example, the RF processor 1410 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), and an analog-to-digital converter (ADC). Although only one antenna is shown in the drawings, the UE may be equipped with multiple antennas. In addition, the RF processor 1410 may include multiple RF chains. In addition, the RF processor 1410 may perform beamforming. For beamforming, the RF processor 1410 may adjust the phase and size of the signal sent or received by multiple antennas or antenna elements. In addition, the RF processor 1410 may perform MIMO, and may receive several layers during the execution of the MIMO operation.

[0330] The baseband processor 1420 performs a conversion function between a baseband signal and a bit string according to the physical layer standard of the system. For example, during data transmission, the baseband processor 1420 generates a complex symbol by encoding and modulating the transmitted bit string. In addition, during data reception, the baseband processor 1420 recovers the received bit string by demodulating and decoding the baseband signal provided from the RF processor 1410. For example, in the case of following the orthogonal frequency division multiplexing (OFDM) method, during data transmission, the baseband processor 1420 generates a complex symbol by encoding and modulating the transmitted bit string, performs mapping of the complex symbol to the subcarrier, and then configures the OFDM symbol by an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. In addition, during data reception, the baseband processor 1420 divides the baseband signal provided from the RF processor 1410 in units of OFDM symbols, recovers the signal mapped to the subcarrier by a fast Fourier transform (FFT) operation, and then recovers the received bit string by demodulation and decoding.

[0331] The baseband processor 1420 and the RF processor 1410 send and receive signals as described above. Therefore, the baseband processor 1420 and the RF processor 1410 may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. In addition, in order to support different radio access technologies, at least one of the baseband processor 1420 and the RF processor 1410 may include a plurality of communication modules. In addition, in order to process signals of different frequency bands, at least one of the baseband processor 1420 and the RF processor 1410 may include different communication modules. For example, different radio access technologies may include wireless LAN (e.g., IEEE 802.11) and cellular networks (e.g., LTE). In addition, different frequency bands may include ultra-high frequency (SHF) (e.g., 2.NR Hz or NR Hz) bands and millimeter wave (e.g., 60GHz) bands.

[0332] The storage unit 1430 stores therein data of basic programs, applications, and configuration information for UE operation. Specifically, the storage unit 1430 may store information related to a second connection node that performs wireless communication by using a second radio access technology. In addition, the storage unit 1430 provides the stored data according to a request from the controller 1440.

[0333] The controller 1440 controls the overall operation of the UE. For example, the controller 1440 sends and receives signals through the baseband processor 1420 and the RF processor 1410. In addition, the controller 1440 records data in the storage unit 1430 or reads data from the storage unit 1430. To this end, the controller 1440 may include at least one processor. For example, the controller 1440 may include a communication processor (CP) that performs communication control and an application processor (AP) that controls an upper layer, such as an application program.

[0334] Fig.15 It is a block diagram showing the configuration of an NR base station according to an embodiment of the present disclosure.

[0335] As shown in the figure, the base station is configured to include an RF processor 1510 , a baseband processor 1520 , a backhaul communication unit 1530 , a storage unit 1540 , and a controller 1550 .

[0336] The RF processor 1510 performs functions for transmitting and receiving signals on a radio channel, such as signal band conversion and amplification. That is, the RF processor 1510 up-converts the baseband signal provided by the baseband processor 1520 into an RF band signal to transmit the frequency-converted signal through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processor 1510 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC. Although in Fig.15 Only one antenna is shown in the figure, but the first access node can be equipped with multiple antennas. In addition, the RF processor 1510 may include multiple RF chains. In addition, the RF processor 1510 can perform beamforming. For beamforming, the RF processor 1510 can adjust the phase and size of the signal sent or received through multiple antennas or antenna elements. The RF processor 1510 can perform downlink MIMO operations through the transmission of one or more layers.

[0337] The baseband processor 1520 performs a conversion function between a baseband signal and a bit string according to the physical layer standard of the first radio access technology. For example, during data transmission, the baseband processor 1520 generates a complex symbol by encoding and modulating the transmitted bit string. In addition, during data reception, the baseband processor 1520 recovers the received bit string by demodulating and decoding the baseband signal provided from the RF processor 1510. For example, in the case of following the OFDM method, during data transmission, the baseband processor 1520 generates a complex symbol by encoding and modulating the transmitted bit string, performs mapping of the complex symbol to the subcarrier, and then configures the OFDM symbol by IFFT operation and CP insertion. In addition, during data reception, the baseband processor 1520 divides the baseband signal provided from the RF processor 1510 in units of OFDM symbols, recovers the signal mapped to the subcarrier by FFT operation, and then recovers the received bit string by demodulation and decoding. The baseband processor 1520 and the RF processor 1510 send and receive signals as described above. Therefore, the baseband processor 1520 and the RF processor 1510 may be referred to as a transmitter, a receiver, a transceiver, a communication unit, or a wireless communication unit.

[0338] The backhaul communication unit 1530 provides an interface for performing communication with other nodes in the network. That is, the backhaul communication unit 1530 converts a bit string sent from the master base station to other nodes (e.g., secondary base stations and core networks) into a physical signal, and converts a physical signal received from other nodes into a bit string.

[0339] The storage unit 1540 stores therein data of basic programs, applications, and configuration information for the operation of the master base station. Specifically, the storage unit 1540 may store information about bearers allocated to connected UEs and measurement results reported from connected UEs. In addition, the storage unit 1540 may store information that becomes a basis for determining whether to provide or suspend multiple connections to the UE. In addition, the storage unit 1540 provides the stored data according to a request from the controller 1550.

[0340] The controller 1550 controls the overall operation of the base station. For example, the controller 1550 sends and receives signals through the baseband processor 1520 and the RF processor 1510 or through the backhaul communication unit 1530. In addition, the controller 1550 records data in the storage unit 1540 or reads data from the storage unit 1540. To this end, the controller 1550 may include at least one processor.

[0341] At the same time, the embodiments of the present disclosure disclosed in the specification and the drawings are only for the convenience of explaining the technical content of the embodiments of the present disclosure and proposing specific examples to help understand the embodiments of the present disclosure, rather than for limiting the scope of the embodiments of the present disclosure. That is to say, it is obvious to a person skilled in the art that other modifications can be implemented based on the technical ideas of the present disclosure. In addition, the embodiments can be combined with each other as needed.

[0342] Fig.16 is a diagram illustrating operations between a UE and a base station for processing a logged measurement configuration if the UE transitions to an RRC inactive mode in a next generation mobile communication system according to an embodiment of the present disclosure.

[0343] refer to Fig.16 , UE 1601 can be in RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE).

[0344] The UE 1601 in the RRC idle mode may send an RRC connection establishment request message (RRCSetupRequest) to the base station in order to perform an RRC connection establishment process with the base station 1602 (1610). In response to this, the base station having received the RRC connection establishment request message may send an RRC connection establishment message (RRCSetup (RRC establishment)) to the UE (1615). The UE having received the RRC connection establishment message may apply this and may switch to the RRC connected mode (1616). In addition, the UE in the RRC connected mode may send an RRC connection establishment completion message (RRCSetupComplete (RRC establishment completion)) to the base station (1620).

[0345] UE 1601 in RRC inactive mode can send an RRC connection recovery request message or an RRC connection recovery request 1 message (RRCResumeRequest(RRC recovery request) or RRCResumeRequest1(RRC recovery request 1)) to the base station to perform an RRC connection recovery process with the base station 1602 (1610). In response to this, the base station that has received the RRC connection recovery request message can send an RRC connection recovery message (RRCResume(RRC recovery)) to the UE (1615). The UE that has received the RRC connection recovery message can apply this and can switch to RRC connected mode (1616). In addition, the UE in RRC connected mode can send an RRC connection recovery complete message (RRCResumeComplete(RRC recovery complete)) to the base station (1620).

[0346] UE 1601 that has not yet performed security settings may perform an initial security activation process (1621) with base station 1602. For example, UE that has not yet performed security settings may refer to a UE that has switched from RRC idle mode to RRC connected mode. Specifically, UE 1601 may send a security mode command message (SecurityModeCommand (Security Mode Command)) to base station 1602, and in response thereto, the base station may send a security mode completion message (SecurityModeComplete) (Security Mode Complete) to the UE.

[0347] At operation 1625, in order to perform the RRC connection reconfiguration process, the base station 1602 may send an RRC connection reconfiguration message (RRCReconfiguration) to the UE 1601 in the RRC connection mode. The UE may apply the received RRC connection reconfiguration message, and in response thereto, may send an RRC connection reconfiguration complete message (RRCReconfigurationComplete) to the base station (1630).

[0348] In order to start the logged measurement configuration process, the base station 1602 may send a LoggedMeasurementConfiguration message (1635) to the UE 1601 in the RRC connected mode. The UE having received the LoggedMeasurementConfiguration message may perform the following series of processes.

[0349] - The UE may remove the logged measurement configuration and the logged measurement information.

[0350] - If loggingDuration, loggingInterval and areaConfiguration are included in VarLogMeasConfig, the UE may store them.

[0351] - If the LoggedMeasurementConfiguration message includes the plmn-IdentityList, the UE may set the RPLMN and PLMN included in the plmn-IdentityList to the VarLogMeasReport as the plmn-IdentityList. If the LoggedMeasurementConfiguration message does not include the plmn-IdentityList, the UE may set the RPLMN in the VarLogMeasReport to the plmn-IdentityList.

[0352] -The UE may store the received absoluteTimeInfo, traceReference, traceRecordingSessionRef and tce-Id in VarLogMeasReport.

[0353] - If included, the UE may store the received bt-NameList, wlan-NameList, sensor-NameList and reportType in VarLogMeasConfig.

[0354] - The UE may start the T330 timer using the timer value included in the loggingDuration.

[0355] The ASN.1 structure of LoggedMeasurementConfiguration is shown in Table 4 below.

[0356] [Table 4]

[0357]

[0358]

[0359] Due to a specific reason (e.g., no data transmission / reception), the base station 1602 may send an RRC connection release message (RRCRelease (RRC Release)) including suspension configuration information (suspendConfig) to the UE 1601 in the RRC connection mode (1604). At operation 1645, the UE may store the current KgNB and KRRCInt keys, ROHC state, stored QoS flow to DRB mapping rules, C_RNTI used in the source PCell, source PCellcellIdentity and physical cell identity, spCellConfigCommon contained in the ReconfigurationWithSync of the PSCell, and other configured parameters in the UE inactive AS context. In this case, the UE may not store the parameters contained in the ReconfigurationWithySync of the PCell, the servingCellConfigCommonSIB, and the parameters included in the LoggedMeasurementConfiguration message received in operation 1635 in the UE inactive AS context. In addition, the UE may transition to an RRC inactive mode (RRC_INACTVE) (1646).

[0360] The UE according to an embodiment of the present disclosure is characterized in that the recorded measurement configuration is not stored in the UE inactive AS context. The recorded measurement configuration is configuration information that is generally applied to both RRC inactive mode and RRC idle mode, and since it is stored, updated and managed in a separate UE variable (e.g., VarLogMeasConfig and / or VarLogMeasReport), it does not need to be stored separately in the UE inactive AS context. 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 store the recorded measurement configuration separately in the UE inactive AS context. If the recorded measurement configuration is stored in the UE inactive AS context, there may be a value in the actual UE variable (e.g., VarLogMeasConfig and / or VarLogMeasReport) and a value different from the value of the recorded measurement configuration stored in the UE inactive AS contention, and this may cause subsequent failure of the UE (e.g., the UE may report erroneous recorded measurement information to the base station). Accordingly, in the UE inactive AS contention, other parameters besides the recorded measurement configuration may be stored.

[0361] Fig.17is a diagram illustrating the operation of a UE for reporting mobility history information to an NR base station in a next generation mobile communication system according to an embodiment of the present disclosure.

[0362] In the case of changing cells through a cell selection process, a cell reselection process, or a handover process, a UE supporting storage of mobility history information may enter a normal camping state (a state in which the UE camps on a suitable cell for general use), any cell selection state (a state in which the UE does not camp on any cell), or a camping on any cell state (a state in which the UE camps on an acceptable cell for limited services (emergency calls, ETWS, and CMAS)). The UE may store the mobility history information of the NR cell in RRC idle mode (RRC_IDLE), RRC inactive mode (RRC_INACTIVE), or RRC connected mode (RRC_CONNECTED). Of course, the UE may store the mobility history information of the E-UTRA cell in RRC inactive mode, which may be determined according to the UE capability or standard version. That is, in the content described later, for convenience, it is assumed that the UE in RRC inactive mode does not store the mobility history information. If the following conditions are met, the UE may store the mobility history information in the VarMobilityHistoryReport of the NR.

[0363] Condition 1: When a suitable cell consisting of a PCell in RRC_CONNECTED or a serving cell in RRC_INACTIVE (for an NR cell) or in RRC_IDLE (for an NR or E-UTRA cell) (in the case where the UE is in RRC connected mode, the NR suitable cell may refer to the PCell, and in the case where the UE is in RRC idle mode or the UE is in RRC inactive mode, the NR suitable cell may refer to the serving cell. In addition, in the case where the UE is in RRC connected mode, the E-UTRA cell may refer to the PCell, and in the case where the UE is in RRC idle mode, it may refer to the serving cell) is changed to another NR or E-UTRA cell

[0364] Condition 2: When entering any cell selection state from a normal camping state in NR or LTE

[0365] Condition 3: When entering the normal camped 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 in NR or LTE or camped on any cell,

[0366] The UE may determine which of condition 1, condition 2, or condition 3 is satisfied (1705).

[0367] If the UE satisfies condition 1 or condition 2 and stores mobility history information in the VarMobilityHistoryReport of the NR, then at operation 1710, if necessary, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following - If the global cell identity of the previous PCell / serving cell is available, the UE may include the global cell identity of the cell in the visitedCellId field of the entry. Otherwise, if the global cell identity is not available, the UE may include the physical cell identity and carrier frequency of the cell in the visitedCellId field of the entry. In addition, the UE may set the field timeSpent of the entry to the time spent in the previous PCell / serving cell.

[0368] If the UE satisfies condition 3 and stores mobility history information in VarMobilityHistoryReport of NR, then at operation 1715, if necessary, the UE may include an entry in the variable VarMobilityHistoryReport after removing the oldest entry according to the following - the UE may set the field timeSpent of the entry to the time spent in any cell selection state and / or camped on any cell state in NR or LTE.

[0369] If condition 3 is satisfied, according to an embodiment of the present disclosure, when the UE transitions to the normal camping state (i.e., the state in which the UE camps on a suitable cell), and when the UE transitions to the camping on any cell state (i.e., the state in which the UE camps on an acceptable cell), the UE may store the time spent in any cell selection state and / or the camping on any cell state in the timeSpent field for NR or E-UTRA, and the UE may not store any cell selection state and / or the camping on any cell state in the timeSpent field for the NR cell or the E-UTRA cell, respectively. For example, when entering NR in RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED, or when entering E-UTRA in RRC_IDLE or RRC_CONNECTED, the UE may include both the normal camping state and the camping on any cell state, and in this case, it may be disadvantageous for the UE to store duplicate time.

[0370] -T0: Normal resident state

[0371] -T1: Any cell selection status

[0372] -T2: Camping on any cell state

[0373] -T3: Any cell status

[0374] -T4: Camped on any cell state

[0375] -T5: Normal resident state

[0376] According to an embodiment of the present disclosure, the UE may store the time (T5-T1) in the timeSpent field at time T5. However, since the UE not following the embodiment of the present disclosure may store the time (T2-T1) in the timeSpent field at time T2, may store the time (T4-T1) in the timeSpent field at time T4, and may store the time (T5-T1) in the timeSpent field at time T5, the UE may unnecessarily store duplicate times (e.g., time (T2-T1) or time (T4-T1), and thus may report erroneous mobility history information to the base station.

[0377] At operation 1720, the UE in the RRC connected mode may be connected to a PCell (primary cell) which is a NR cell.

[0378] At operation 1725, the UE may receive a UE information request message including mobilityHistoryReportReq from the NR base station. If mobilityHistoryReportReq is set to true, at operation 1730, the UE may include mobilityHistoryReport and set it to include entries from VarMobilityHistoryReport.

[0379] At operation 1730 , as needed, the UE may remove the oldest entry value of the current cell (eg, PCell) if possible, and may include the global cell identity of the current cell and the time spent in the PCell in the VarMobilityHistoryReport.

[0380] In operation 1730, the UE may include the above-mentioned mobilityHistoryReport in a UE information response message, and may send the UE information response message to the NR base station.

Claims

1. A method performed by a user equipment UE in a wireless communication system, the method include: Receiving recorded measurement configuration information from a base station in a radio resource control RRC connected state; receiving an RRC release message including suspension configuration information from the base station; and Entering an RRC inactive state based on the RRC release message, When the UE enters the RRC inactive state, the recorded measurement configuration information is not stored as a UE inactive access layer AS context.

2. The method according to claim 1, further comprising: include: In case the logged measurement configuration information includes logging duration information and area configuration information, the logging duration and area configuration are stored in UE variables of the logged measurement report.

3. The method according to claim 1, further comprising: include: In a case where the recorded measurement configuration information includes public land mobile network PLMN identity list information, setting the PLMN identity list in the UE variable of the recorded measurement report to include the registered public land mobile network RPLMN and the PLMN included in the PLMN identity list information; and In a case where the recorded measurement configuration information does not include the PLMN identity list information, the PLMN identity list in the UE variable of the recorded measurement report is set to include the RPLMN.

4. The method according to claim 1, further comprising: include: The received absolute time information, trace reference information, trace recording session reference information and trace collection entity TCE identifier ID are stored in the UE variables of the logged measurement report.

5. The method according to claim 1, further comprising: include: In a case where the recorded measurement configuration information includes Bluetooth BT name list information, wireless local area network WLAN information and sensor name list information, the BT name list information, the WLAN information and the sensor name list information are stored in a UE variable of the recorded measurement configuration.

6. The method according to claim 1, further comprising: include: The KgNB and KRRCint keys, the robust header compression ROHC status, the stored quality of service QoS flow to data radio bearer DRB mapping rules, the cell-radio network temporary identifier C-RNTI used in the source primary cell PCell, the cell identifier and physical cell identifier of the source PCell, and the physical cell identifier of the source PCell, and the special cell SpCell configuration public information within the ReconfigurationWithSync of the PSCell are stored in the UE AS context.

7. A method performed by a base station in a wireless communication system, the method include: Sending the recorded measurement configuration information to a user equipment UE in a radio resource control RRC connected state; Sending an RRC release message including suspension configuration information to the UE, When the UE enters the RRC inactive state based on the RRC release message, the recorded measurement configuration information is not stored as a UE inactive access layer AS context.

8. The method according to claim 7, in, In case the logged measurement configuration information includes logging duration information and area configuration information, the logging duration and area configuration are stored in UE variables of the logged measurement report.

9. The method according to claim 7, in, In the case where the recorded measurement configuration information includes public land mobile network PLMN identity list information, the PLMN identity list in the UE variable of the recorded measurement report is set to include the registered public land mobile network RPLMN and the PLMN included in the PLMN identity list information, and Wherein, in a case where the recorded measurement configuration information does not include the PLMN identity list information, the PLMN identity list in the UE variable of the recorded measurement report is set to include the RPLMN.

10. The method according to claim 7, in, In case the absolute time information, the trace reference information, the trace logging session reference information and the trace collection entity TCE identifier ID that are sent are stored in the UE variables of the logged measurement report, and Wherein, in a case where the recorded measurement configuration information includes Bluetooth BT name list information, wireless local area network WLAN information and sensor name list information, the BT name list information, the WLAN information and the sensor name list information are set in the UE variable of the recorded measurement configuration.

11. A user equipment UE in a wireless communication system, the UE include: Transceiver; and A controller is coupled to the transceiver and is configured to: receiving recorded measurement configuration information from a base station in a radio resource control RRC connected state, receiving an RRC release message including suspension configuration information from the base station, and Entering an RRC inactive state based on the RRC release message, When the UE enters the RRC inactive state, the recorded measurement configuration information is not stored as a UE inactive access layer AS context.

12. The UE according to claim 11, wherein the controller is further configured to: In case the logged measurement configuration information includes logging duration information and area configuration information, the logging duration and area configuration are stored in UE variables of the logged measurement report.

13. The UE according to claim 11, wherein the controller is further configured to: In a case where the recorded measurement configuration information includes public land mobile network PLMN identity list information, setting the PLMN identity list in the UE variable of the recorded measurement report to include the registered public land mobile network RPLMN and the PLMN included in the PLMN identity list information; and In a case where the recorded measurement configuration information does not include the PLMN identity list information, the PLMN identity list in the UE variable of the recorded measurement report is set to include the RPLMN.

14. The UE according to claim 11, wherein the controller is further configured to: The received absolute time information, trace reference information, trace recording session reference information and trace collection entity TCE identifier ID are stored in the UE variables of the logged measurement report.

15. The UE according to claim 11, wherein the controller is further configured to: In a case where the recorded measurement configuration information includes Bluetooth BT name list information, wireless local area network WLAN information and sensor name list information, the BT name list information, the WLAN information and the sensor name list information are stored in a UE variable of the recorded measurement configuration.

16. The UE according to claim 11, wherein the controller is further configured to: The KgNB and KRRCint keys, the robust header compression ROHC status, the stored quality of service QoS flow to data radio bearer DRB mapping rules, the cell-radio network temporary identifier C-RNTI used in the source primary cell PCell, the cell identifier and physical cell identifier of the source PCell, and the physical cell identifier of the source PCell, and the special cell SpCell configuration public information within the ReconfigurationWithSync of the PSCell are stored in the UE AS context.

17. A base station in a wireless communication system, the base station include: Transceiver; and A controller is coupled to the transceiver and is configured to: Sending recorded measurement configuration information to a user equipment UE in a radio resource control RRC connected state; Sending an RRC release message including suspension configuration information to the UE, When the UE enters the RRC inactive state based on the RRC release message, the recorded measurement configuration information is not stored as a UE inactive access layer AS context.

18. The base station according to claim 17, in, In case the logged measurement configuration information includes logging duration information and area configuration information, the logging duration and area configuration are stored in UE variables of the logged measurement report.

19. The base station according to claim 17, in, In the case where the recorded measurement configuration information includes public land mobile network PLMN identity list information, the PLMN identity list in the UE variable of the recorded measurement report is set to include the registered public land mobile network RPLMN and the PLMN included in the PLMN identity list information, and Wherein, in a case where the recorded measurement configuration information does not include the PLMN identity list information, the PLMN identity list in the UE variable of the recorded measurement report is set to include the RPLMN.

20. The base station according to claim 17, in, In case the absolute time information, the trace reference information, the trace logging session reference information and the trace collection entity TCE identifier ID that are sent are stored in the UE variables of the logged measurement report, and Wherein, in a case where the recorded measurement configuration information includes Bluetooth BT name list information, wireless local area network WLAN information and sensor name list information, the BT name list information, the WLAN information and the sensor name list information are set in the UE variable of the recorded measurement configuration.

Images