Method and apparatus for recording connection establishment failure information in wireless communication system
By providing user equipment (UE) with a method of recording and reporting RRC connection failure information in a wireless communication system, the problem of difficulty in recording and reporting of connection failure information in the NR system is solved, and the system's information storage and reporting efficiency is improved.
Patent Information
- Application Number
- CN202380031031.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-31
- Filing Date
- 2023-03-30
- Publication Date
- 2024-11-12
AI Technical Summary
In wireless communication systems, prior art is difficult to effectively record and report information on failed establishment or recovery of radio resource control (RRC) connections in NR systems.
Provide a method and device, the user equipment (UE) initiates a connection establishment or recovery process on the cell and starts a timer to identify that when the timer expires, if the cell identification does not equal the stored connection failure report, the failure information is stored and Clear old information and send messages including new and old information.
It realizes the effective storage and reporting of RRC connection establishment or recovery failure information in the NR system, and optimizes network performance and device operation.
Smart Images

Figure CN118947213A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a wireless communication system, and more particularly to a method and apparatus for logging connection establishment failure information in a wireless communication system. Background Art
[0002] 5G mobile communication technology defines a wide frequency band so that high transmission rates and new services are possible, and can be realized not only in "below 6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands called mmWave (millimeter wave) including 28 GHz and 39 GHz. In addition, the implementation of the sixth generation (6G) mobile communication technology (called a super 5G system) in the terahertz frequency band (e.g., 95 GHz to 3 THz frequency band) has been considered in order to achieve a transmission rate fifty times faster than that of 5G mobile communication technology and an ultra-low latency of one tenth of that of 5G mobile communication technology.
[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), and massive machine type communication (mMTC), there has been ongoing standardization on the following technologies: beamforming and massive MIMO for mitigating radio wave path loss in mmWave and increasing radio wave transmission distance in mmWave, parameter sets supporting dynamic operation for efficient utilization of mmWave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods such as LDPC (low-density parity check) codes for large-volume data transmission and polar codes for highly reliable transmission of control information, L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.
[0004] Currently, in view of the services supported by the 5G mobile communication technology, discussions are ongoing on the improvement and performance enhancement of the initial 5G mobile communication technology, and there is already physical layer standardization on the following technologies, such as V2X (Vehicle to Everything) for assisting driving decisions made by autonomous vehicles based on information about the position and status of the vehicle transmitted by the vehicle and for enhancing user convenience, NR-U (New Radio Unlicensed) for system operation intended to comply with various regulatory-related requirements in unlicensed bands, NR UE power saving, non-terrestrial network (NTN) (which is UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is not available), and positioning.
[0005] In addition, there is ongoing standardization of air interface architecture / protocol aspects of technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional switching and DAPS (Dual Active Protocol Stack) switching, and two-step random access (two-step RACH for NR) for simplifying the random access process. Standardization is also ongoing on the 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and the system architecture / services of mobile edge computing (MEC) for receiving services based on UE location.
[0006] As 5G mobile communication systems are commercialized, the number of connected devices, which has been growing exponentially, will be connected to the communication network, and it is therefore expected that enhanced functions and performance of the 5G mobile communication systems and the integrated operation of connected devices will be necessary. To this end, new research related to extended reality (XR) is arranged for effectively supporting AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., improving 5G performance and reducing complexity by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.
[0007] Furthermore, such developments in 5G mobile communication systems will serve as a foundation not only for the development of new waveforms that provide terahertz band coverage for 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas, metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum), and RIS (reconfigurable smart surface), but also for the development of full-duplex technology that improves the frequency efficiency of 6G mobile communication technology and improves system networks, AI-based communication technology for achieving system optimization by leveraging satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for achieving services at a complexity level that exceeds the operational capability limits of UEs by utilizing ultra-high-performance communication and computing resources.
[0008] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above may be applicable as prior art with respect to the present disclosure. Summary of the invention
[0009] Technical issues
[0010] With the development of wireless communication systems, there is a need for a method and apparatus for effectively recording and reporting radio resource control (RRC) connection establishment or recovery failure information by a UE in a NR system.
[0011] Solution to the problem
[0012] In an embodiment, a method of a user equipment (UE) in a wireless communication system is provided. The method includes: initiating a connection establishment procedure or a connection recovery procedure on a cell, and starting a timer corresponding to the connection establishment procedure or the connection recovery procedure, identifying expiration of the timer, and if a cell identifier of the cell is not equal to a cell identifier stored in a UE variable for connection failure reporting, storing first connection failure report information stored in the UE variable in a new entry of a UE variable list for multiple connection failure reports, clearing the UE variable and storing second connection failure report information of the cell in the UE variable, and sending a message including the UE variable and the UE variable list.
[0013] In an embodiment, a UE in a wireless communication system is provided. The UE includes a transceiver and a controller operably coupled to the transceiver. The controller is configured to: initiate a connection establishment procedure or a connection recovery procedure on a cell, and start a timer corresponding to the connection establishment procedure or the connection recovery procedure, identify that the timer expires, and when a cell identifier of the cell is not equal to a cell identifier stored in a UE variable for connection failure reporting, store first connection failure report information stored in the UE variable in a new entry of a UE variable list for multiple connection failure reports, clear the UE variable and store second connection failure report information of the cell in the UE variable, and send a message including the UE variable and the UE variable list via the transceiver.
[0014] Advantageous Effects of the Invention
[0015] According to an embodiment of the present disclosure, in a NR system, the UE can effectively store RRC connection establishment or recovery failure information and report it to the NR cell. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent through the following description in conjunction with the accompanying drawings, in which:
[0017] Figure 1 The structure of an LTE system according to an embodiment of the present disclosure is shown;
[0018] Figure 2 A radio protocol structure in an LTE system according to an embodiment of the present disclosure is shown;
[0019] Figure 3The structure of a next generation mobile communication system according to an embodiment of the present disclosure is shown;
[0020] Figure 4 A radio protocol structure of a next generation mobile communication system according to an embodiment of the present disclosure is shown;
[0021] Figure 5 A technique for collecting and reporting cell measurement information according to an embodiment of the present disclosure is shown;
[0022] Figure 6 A flowchart showing a process in which a UE stores single RRC connection establishment / recovery failure information and reports it to an NR cell in an NR system according to an embodiment of the present disclosure;
[0023] Figure 7 A flowchart showing a process in which a UE stores a plurality of RRC connection establishment / recovery failure information and reports the same to an NR base station in an NR system according to an embodiment of the present disclosure;
[0024] Figure 8 A flowchart showing a process in which a UE stores a plurality of RRC connection establishment / recovery failure information and reports the same to an NR base station in an NR system according to an embodiment of the present disclosure;
[0025] Fig. 9 A flowchart showing a process in which a UE stores a plurality of RRC connection establishment / recovery failure information and reports the same to an NR cell in an NR system according to an embodiment of the present disclosure;
[0026] Fig.10 A flowchart of a UE performing measurement logging according to an embodiment of the present disclosure is shown;
[0027] Fig.11 shows the internal structure of a UE according to an embodiment of the present disclosure; and
[0028] Fig.12 The configuration of an NR base station according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION
[0029] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used throughout this patent document: the terms "include" and "comprising" and their derivatives are meant to include, but are not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with" and their derivatives may mean include, be included within, interconnected with, contain, be contained within, connect to or be connected with, be coupled to or be coupled with, be communicative with, cooperate with, interleave, juxtapose, be proximate to, be bound to or be bound with, have, have the property of, etc.; and the term "controller" means any device, system, or portion thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or some combination of at least two thereof. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.
[0030] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a portion thereof suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disc (DVD) or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and rewrite data later, such as rewritable optical disks or erasable memory devices.
[0031] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
[0032] Discussed below Figures 1 to 12 The various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.
[0033] Hereinafter, the operating principle of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, when it is determined that a detailed description of a known function or configuration incorporated herein may make the subject matter of the present disclosure unnecessarily unclear, the description will be omitted. The terms to be described below are terms defined in consideration of the functions in the present disclosure, and may differ depending on the user, the user's intention or custom. Therefore, the definition of the terms should be based on the content in the entire specification.
[0034] In the following description of the present disclosure, when it is determined that a detailed description of a known function or configuration incorporated herein may make the subject matter of the present disclosure unnecessarily unclear, the description will be omitted. Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
[0035] In the following description, for the sake of convenience, terms for identifying access nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are illustratively used. Therefore, the present disclosure is not limited to the terms used below, and other terms relating to subjects with equivalent technical meanings may be used.
[0036] In the following description, for ease of description, the present disclosure will be described using terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard. However, the present disclosure is not limited to these terms and names and can be applied to systems conforming to other standards in the same manner. In the present disclosure, the term "eNB" can be used interchangeably with the term "gNB". That is, a base station described as an "eNB" can indicate a "gNB".
[0037] Figure 1 The structure of an LTE system according to an embodiment of the present disclosure is shown.
[0038] refer to Figure 1 As shown in the figure, the radio access network of the LTE system is composed of next-generation base stations (evolved node B, hereinafter referred to as ENB, node B or base station) 1-05, 1-10, 1-15 and 1-20, mobility management entity (MME) 1-25 and serving gateway (S-GW) 1-30. User equipment (hereinafter referred to as UE or terminal) 1-35 accesses the external network through ENB 1-05 to 1-20 and S-GW 1-30.
[0039] exist Figure 1In the LTE system, ENB 1-05 to 1-20 correspond to the existing Node B of the UMTS system. The ENB is connected to the UE 1-35 through a radio channel and performs 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 can be served through a shared channel, a device for scheduling by collecting status information such as the buffer status of the UE, the available transmission power status, the channel status, etc. is required, and the ENB 1-05 to 1-20 is responsible for this. One ENB usually controls multiple cells. For example, in order to achieve a transmission rate of 100Mbps, the LTE system uses, for example, orthogonal frequency division multiplexing (hereinafter referred to as OFDM) in a 20MHz bandwidth as a radio access technology. In addition, an adaptive modulation and coding (hereinafter referred to as AMC) scheme that determines the modulation scheme and the channel coding rate based on the channel status of the UE is applied. The S-GW 1-30 is a device that provides data bearers and generates or removes data bearers under the control of the MME 1-25. The MME is a device responsible for various control functions of the UE and a mobility management function, and is connected to multiple base stations.
[0040] Figure 2 A radio protocol structure in an LTE system according to an embodiment of the present disclosure is shown.
[0041] refer to Figure 2 The radio protocol of the LTE system consists of the Packet Data Convergence Protocol (PDCP) 2-05 and 2-40 in the UE and ENB, the Radio Link Control (RLC) 2-10 and 2-35, and the Medium Access Control (MAC) 2-15 and 2-30. The Packet Data Convergence Protocol (PDCP) 2-05 and 2-40 are responsible for operations such as IP header compression / decompression. The main functions of PDCP are summarized as follows:
[0042] - Header compression and decompression (ROHC only);
[0043] -Transmission of user data;
[0044] - In-sequence delivery of upper layer PDUs during PDCP re-establishment of RLC AM;
[0045] - For split bearers in DC (supported only by RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception;
[0046] - Duplicate detection of lower layer SDUs during PDCP re-establishment of RLC AM;
[0047] - Retransmission of PDCP SDUs during handover and, for split bearers in DC, retransmission of PDCP PDUs during PDCP data recovery in RLC AM;
[0048] - encryption and decryption; and
[0049] - Timer based SDU discard in uplink.
[0050] Radio Link Control (hereinafter referred to as RLC) 2-10 and 2-35 performs ARQ operations by reconfiguring PDCP packet data units (PDUs) to appropriate sizes. The main functions of RLC are summarized as follows:
[0051] -Transmission of upper layer PDU;
[0052] - Error correction through ARQ (for AM data transmission only);
[0053] - Concatenation, segmentation and reassembly of RLC SDU (only for UM and AM data transmission);
[0054] - Re-segmentation of RLC data PDU (only for AM data transmission);
[0055] - Reordering of RLC data PDUs (only for UM and AM data transmission);
[0056] - Duplicate detection (only for UM and AM data transmission);
[0057] -Protocol error detection (for AM data transmission only);
[0058] - RLC SDU discard (only for UM and AM data transmission); and
[0059] -RLC reconstruction.
[0060] MAC 2-15 and MAC 2-30 are connected to several RLC layers configured in one UE and perform operations of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC are summarized as follows:
[0061] - Mapping between logical channels and transport channels;
[0062] - Multiplexing MAC SDUs belonging to one or different logical channels into / demultiplexing MAC SDUs belonging to one or different logical channels from / to a transport block (TB) transmitted to / from the physical layer on a transport channel;
[0063] -Dispatch information report;
[0064] - Error correction through HARQ;
[0065] - Priority handling between logical channels of a UE;
[0066] - Prioritization between UEs through dynamic scheduling;
[0067] -MBMS service identifier;
[0068] -Transmission format selection; and
[0069] -filling.
[0070] The physical layers 2-20 and 2-25 channel-code and modulate the upper layer data, generate OFDM symbols and transmit the OFDM symbols through a radio channel, or demodulate and channel-decode OFDM symbols received through a radio channel and transmit them to an upper layer.
[0071] Figure 3 A structure of a next generation mobile communication system according to an embodiment of the present disclosure is shown.
[0072] refer to Figure 3 As shown in the figure, the radio access network of the next generation mobile communication system (hereinafter, NR or 5G) is composed of a next generation base station (new radio node B, hereinafter, NR gNB or NR base station) 3-10 and a new radio core network (NR CN) 3-05. The new radio user equipment (hereinafter, NR UE or terminal) 3-15 accesses the external network through the NR gNB 3-10 and the NR CN 3-05.
[0073] exist Figure 3 In the present invention, the NR gNB 3-10 corresponds to the evolved Node B (eNB) of the existing LTE system. The NR gNB is connected to the NR UE 3-15 through a radio channel and can provide services that are superior to those of the existing Node B. In the next generation mobile communication system, because all user services are served through a shared channel, a device for scheduling by collecting status information such as the buffer status of the UE, the available transmission power status, the channel status, etc. is required, and the NR NB 3-10 is responsible for this. One NR gNB typically controls multiple cells. Compared with the current LTE, a bandwidth greater than or equal to the existing maximum bandwidth can be applied to achieve ultra-high-speed data transmission, and additional beamforming technology can be transplanted by using orthogonal frequency division multiplexing (hereinafter referred to as OFDM) as a radio access technology.
[0074] In addition, an adaptive modulation and coding (hereinafter referred to as AMC) scheme for determining a modulation scheme and a channel coding rate according to the channel state of the UE is applied. NR CN 3-05 performs functions such as mobility support, bearer configuration, QoS configuration, etc. NR CN is a device responsible for various control functions of the UE and mobility management functions, and is connected to multiple base stations. In addition, the next generation mobile communication system can be linked with the existing LTE system, and the NR CN is connected to the MME 3-25 through a network interface. The MME is connected to the existing base station eNB 3-30.
[0075] Figure 4 A radio protocol structure of a next generation mobile communication system according to an embodiment of the present disclosure is shown.
[0076] refer to Figure 4 , the radio protocol of the next generation mobile communication system consists of NR SDAP 4-01 and 4-45, NR PDCP 4-05 and 4-40, NR RLC 4-10 and 4-35, and NR MAC 4-15 and 4-30 in UE and NR base station respectively.
[0077] The main functions of NR SDAP 4-01 and 4-45 may include some of the following:
[0078] -Transmission of user plane data;
[0079] - Mapping between QoS flows and DRBs for both DL and UL;
[0080] - marking the QoS Flow ID in both DL and UL packets; and
[0081] - Reflective QoS Flow to DRB mapping for UL SDAP PDU.
[0082] Regarding the SDAP layer, the UE may be configured with an RRC message indicating whether the SDAP layer header or the SDAP layer function is used for each PDCP layer, for each bearer, or for each logical channel, and in the case of configuring the SDAP header, the UE may indicate that the UE uses the 1-bit indicator (NAS Reflective QoS) of the SDAP header and the AS QoS Reflective Configuration 1-bit indicator (AS Reflective QoS) to update or reconfigure the mapping information for uplink and downlink QoS flows and data bearers. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used as data processing priority, scheduling information, etc. to support smooth services.
[0083] The main functions of NR PDCP 4-05 and 4-40 may include some of the following functions:
[0084] - Header compression and decompression (ROHC only);
[0085] -Transmission of user data;
[0086] - In-sequence delivery of upper layer PDUs;
[0087] - Out-of-order delivery of upper layer PDUs;
[0088] - Reordering of received PDCP PDUs;
[0089] - Duplicate detection of lower layer SDUs;
[0090] -Retransmission of PDCP SDU;
[0091] - encryption and decryption; and
[0092] - Timer based SDU discard in uplink.
[0093] In the above description, the reordering function of NR PDCP may refer to a function of reordering PDCP PDUs received from a lower layer in sequence based on a PDCP sequence number (SN), and may include a function of sending data to an upper layer in a rearranged order or a function of directly sending data without considering the order, a function of recording lost PDCP PDUs by rearranging the order, a function of reporting the status of lost PDCP PDUs to a transmitting side, and a function of requesting retransmission of lost PDCP PDUs.
[0094] The main functions of NR RLC 4-10 and 4-35 may include some of the following functions:
[0095] -Transmission of upper layer PDU;
[0096] - In-sequence delivery of upper layer PDUs;
[0097] - Out-of-order delivery of upper layer PDUs;
[0098] - Error correction through ARQ;
[0099] - Concatenation, segmentation and reassembly of RLC SDUs;
[0100] - Re-segmentation of RLC data PDUs;
[0101] - Reordering of RLC data PDUs;
[0102] - Repeated testing;
[0103] -Protocol error detection;
[0104] - RLC SDU discard; and
[0105] -RLC reconstruction.
[0106] In the above description, in-sequence delivery of NR RLC refers to a function of sequentially delivering RLC SDUs received from a lower layer to an upper layer, and may include a function of reassembling and delivering the divided RLC SDUs in a case where an initially one RLC SDU is divided into several RLC SDUs and received, may include a function of rearranging the received RLC PDUs based on an RLC sequence number (SN) or a PDCP sequence number (SN), a function of reordering and recording lost RLC PDUs, a function of reporting the status of lost RLC PDUs to a transmitting side, a function of requesting retransmission of lost RLC PDUs, a function of sequentially delivering only the RLC SDUs preceding the lost RLC SDU to an upper layer when there is a lost RLC SDU, or may include a function of sequentially delivering all RLC SDUs received before a predetermined timer is started to an upper layer if there is a lost RLC SDU, or may include a function of sequentially delivering all RLC SDUs received before a ... SDU, and a predetermined timer has expired, a function to sequentially deliver all RLC SDUs received so far to the upper layer.
[0107] In addition, in the above, the RLC PDUs may be processed in the order in which they are received (regardless of the order of sequence numbers and sequence numbers, in the order of arrival) and delivered to the PDCP device out of order (out of order delivery), and in the case of segmentation, the fragments stored in the buffer or to be received later are received, reconstructed into a complete RLC PDU, processed and sent to the PDCP device. The NR RLC layer may not include a cascading function, and the function may be performed by the NR MAC layer or replaced by a multiplexing function of the NR MAC layer.
[0108] In the above description, the out-of-order delivery of the NR RLC device refers to a function of directly delivering the RLC SDU received from the lower layer to the upper layer regardless of the order, and may include a function of reassembling and delivering when an original RLC SDU is divided into several RLC SDUs and received, and a function of storing the RLC SN or PDCP SN of the received RLC PDU, arranging the order and recording the lost RLC PDU.
[0109] NR MAC 4-15 and 4-30 may be connected to several NR RLC layers configured in one UE, and the main functions of NR MAC may include some of the following functions:
[0110] - Mapping between logical channels and transport channels;
[0111] -Multiplexing / demultiplexing of MAC SDU;
[0112] -Dispatch information report;
[0113] - Error correction through HARQ;
[0114] - Priority handling between logical channels of a UE;
[0115] - Prioritization between UEs through dynamic scheduling;
[0116] -MBMS service identifier;
[0117] -Transmission format selection; and
[0118] -filling.
[0119] The NR PHY layers 4-20 and 4-25 may channel encode and modulate the upper layer data, make OFDM symbols, and transmit the OFDM symbols through a radio channel, or may demodulate and channel decode OFDM symbols received through a radio channel and transmit them to an upper layer.
[0120] Figure 5 A technique for collecting and reporting cell measurement information according to an embodiment of the present disclosure is shown.
[0121] When establishing or optimizing a network, a mobile communication operator usually measures the signal strength in the expected service area, and based on this, places or readjusts the base station in the service area. The operator loads the signal measurement equipment on the vehicle and collects the cell measurement information in the service area, which requires a lot of time and cost. This process is generally referred to as a drive test using a vehicle. The UE is equipped with a function that can measure the signal to the base station in order to support operations such as cell reselection or switching, and to add a service cell when moving between cells. Therefore, instead of a drive test, the UE in the service area can be used, which is called minimization of drive test (MDT). The operator can configure the MDT operation to a specific UE through various configuration devices in the network, and the UE collects and stores signal strength information from the serving cell and the peripheral cell in RRC connected mode (RRC_CONNECTED), RRC idle mode (RRC_IDLE) or RRC inactive mode (RRC_INACTIVE). In addition, the UE also stores 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 is sent to a specific server.
[0122] The MDT operation is mainly classified into immediate MDT and logged MDT.
[0123] Immediate MDT is characterized by reporting the collected information to the network immediately. Since the reporting should be done immediately, only RRC connected mode UEs can perform this operation. Typically, the RRM measurement process used to support operations such as handover and adding serving cells is reused, and location information, time information, etc. are additionally reported.
[0124] The feature of logged MDT is that the collected information is stored without immediately reporting the information to the network, and then the stored information is reported after the UE switches to RRC connected mode. Generally, a UE in RRC idle mode or RRC inactive mode that cannot immediately report to the network performs this operation. In the present disclosure, a UE in RRC inactive mode introduced in a next generation mobile communication system is characterized by performing logged MDT. When a specific UE is in RRC connected mode, the network provides the UE with configuration information for performing logged MDT operation, and the UE collects and stores the configuration information after switching to RRC idle mode or RRC inactive mode.
[0125] The relationship between the type of MDT operation and the RRC state of the UE is summarized in Table 1 below.
[0126] Table 1
[0127]
[0128] Figure 6 A process in which a UE stores single RRC connection establishment / recovery failure information and reports it to an NR cell in an NR system according to an embodiment of the present disclosure is shown.
[0129] exist Figure 6 In the embodiment, depending on the configuration and / or definition on the system, not all steps described below must be included, and some steps may be omitted.
[0130] According to an embodiment of the present disclosure, the UE may store single RRC connection establishment / recovery failure information (single connection establishment / recovery failure information, hereinafter referred to as single CEF) in a UE variable (e.g., VarConnEstFailReport) including connection establishment failure and / or connection recovery failure information, and send it to the NR cell (or base station, or gNB, hereinafter used interchangeably). For example, the UE may store only the RRC connection establishment / recovery failure information of the cell that failed to establish / recover the RRC connection most recently, and send it to the NR cell. In the example, since the UE is forced to support the single CEF function, the NR cell may not be notified whether the single CEF function is supported.
[0131] refer to Figure 6 In step 6-05, UE 6-01 may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with NR cell 6-02.
[0132] In step 6-10, the NR cell 6-02 may send an RRC connection release message (RRCRelease) that does not include the suspend configuration information (suspendConfig) to the UE 6-01.
[0133] In step 6-15, UE 6-01 that has received the RRCRelease message may transition to the RRC idle mode (RRC_IDLE).
[0134] In step 6-20, the UE 6-01 in RRC idle mode may perform a public land mobile network (PLMN) selection process. In the UE, the AS may report available PLMNs to the NAS based on a request from the NAS or automatically. The UE may scan all RF channels in the NR band to find available PLMNs based on the capabilities of the UE. On each carrier, the UE may search for the strongest cell and read the UE's system information to find out which PLMN(s) the cell belongs to. If the UE can read one or several PLMN identities in the strongest cell, each found PLMN may be reported to the NAS as a high-quality PLMN (but without an RSRP value), provided that the following high-quality criteria are met.
[0135] -High quality standard: For NR cells, the measured RSRP value can be greater than or equal to -110dBm.
[0136] The discovered PLMNs that do not meet the high quality criteria but for which the UE has been able to read the PLMN identity are reported to the NAS together with their corresponding RSRP values. The quality measurements reported by the UE to the NAS may be the same for each PLMN discovered in a cell. The search for the PLMN may be stopped based on a request from the NAS. The UE uses the stored information (e.g., information about cell parameters that can be obtained from the frequency and measurement control information elements that were previously selectively received) to optimize the PLMN selection process. For reference, when the UE 6-01 in RRC idle mode registers the selected PLMN (the PLMN may be referred to as a registered PLMN, hereinafter referred to as RPLMN) before step 6-20 and does not deviate from the corresponding registration area, the UE may not perform step 6-20.
[0137] At step 6-25, the UE 6-01 in RRC idle mode may perform a cell selection procedure to camp on a suitable cell of the selected or registered PLMN.
[0138] At step 6-30, the UE 6-01 in RRC idle mode may perform a cell reselection procedure to find a better suitable cell.
[0139] In step 6-35, the UE 6-01 in RRC idle mode may initiate an RRC connection establishment process with the NR cell 6-02. When initiating the RRC connection establishment process, the UE may start the T300 timer.
[0140] At step 6-40, the T300 timer driven by the UE at step 6-35 may expire.
[0141] In step 6-45, the UE may perform operations 1 and 2 sequentially.
[0142] - Operation 1: Operation not related to VarConnEstFailReport
[0143] * Reset MAC, release MAC configuration and re-establish RLC for all established RBs; and
[0144] * If the UE supports RRC connection establishment failure with temporary offset and T300 has expired connEstFailCount times consecutively on the same cell for which connEstFailureControl is included in SIB1 within the period indicated by connEstFailOffsetValidity, connEstFailOffset shall be used for parameter Qoffsettemp of the relevant cell when performing cell selection and reselection according to TS 38.304 and TS 36.304.
[0145] - Operation 2: Operations related to VarConnEstFailReport
[0146] * If the UE has connection establishment failure information or connection recovery failure information available in VarConnEstFailReport and if RPLMN is not equal to plmn-identity stored in VarConnEstFailReport or if the cell identity of the current cell is not equal to the cell identity in measResultFailedCell stored in VarConnEstFailReport, then numberOfConnFail is reset to 0;
[0147] * Clears all content (if any) included in VarConnEstFailReport except numberOfConnFail; and
[0148] *Store the following connection establishment failure information in VarConnEstFailReport by setting its fields as follows:
[0149] ** Set plmn-Identity to the PLMN selected by upper layers (see TS24.501) from the PLMNs included in the plmn-IdentityList in SIB1;
[0150] **Based on the available SSB measurements collected until the UE detects the connection establishment failure, measResultFailedCell is set to include the global cell identity, tracking area code, cell-level and SS / PBCH block-level RSRP, RSRQ, and SS / PBCH block index of the failed cell; and
[0151] **If available, measResultNeighCells is set in descending order of ranking criteria for cell reselection to include neighbor cell measurements for up to the following number of neighbor cells: 6 intra-frequency neighbors and 3 inter-frequency neighbors per frequency, and 3 inter-RAT neighbors per frequency / frequency set per RAT, and according to the following:
[0152] ***For each neighbor cell included, include the available optional fields;
[0153] **If available, set locationInfo as follows:
[0154] *** Set commonLocationInfo to include detailed location information if available;
[0155] *** If available, bt-LocationInfo is set to include Bluetooth measurements in order of decreasing RSSI for Bluetooth beacons;
[0156] *** If available, wlan-LocationInfo is set to include WLAN measurements in order of decreasing RSSI for WLAN Ap; and
[0157] *** If available, set sensor-LocationInfo to include sensor measurements, as follows:
[0158] ****If available, sensor-MeasurementInformation; and
[0159] ****If available, include sensor-MotionInformation;
[0160] **Set perRAInfoList to indicate random access failure information; and
[0161] **If numberOfConnFail is less than 7, increase numberOfConnFail by 1;
[0162] *Notify the upper layer about the failure to establish the RRC connection. This process ends here.
[0163] In step 6-50, the UE 6-01 in RRC idle mode may initiate an RRC connection establishment process with the NR cell 6-03. When initiating the RRC connection establishment process, the UE may start the T300 timer.
[0164] At step 6-55, the T300 timer driven by the UE in step 6-50 may expire.
[0165] In step 6-60, the UE may sequentially perform the above operations 1 and 2. The UE that records a single RRC connection / resumption failure information may have the following characteristics.
[0166] -The UE may store a single RRC connection / recovery failure information in the VarconnestFaileport of the most recently failed cell 6-03. To this end, the UE may erase all information except the information indicating the number of consecutive RRC connection establishment / recovery failures in the same cell (e.g., numberOfConnFail) among the RRC connection establishment / recovery failure information stored in the VarconnestFaileport in step 6-45, and store the RRC connection establishment / recovery failure information in the VarConnEstFailReport of the cell 6-03 that failed to establish / recover the RRC connection in step 6-55. When the cell 6-02 that failed to establish / recover the RRC connection in step 6-40 is different from the cell 6-03 that failed to establish / recover the RRC connection in step 6-55, or when the plmn-Identity stored in the VarConnEstFailReport in step 6-45 is not RPLMN, numberOfConnFail may be reset to 0. The UE can determine whether the current cell and the most recently failed cell are the same by comparing the cell identifier of the current cell with the cell identifier stored in the information indicating the last measurement result performed in the cell where the RRC connection establishment / recovery failure of VarConnEstFailReport occurred (e.g., measResultFailedCell). When the cell 6-02 that failed to establish / recover the RRC connection in step 6-40 and the cell 6-03 that failed to establish / recover the RRC connection in step 6-55 are the same, the UE can increase the numberOfConnFail set in step 6-45 by 1 without resetting numberOfConnFail.
[0167] In step 6-65, the UE 6-01 in RRC idle mode may initiate an RRC connection establishment process with the NR cell 6-02. When initiating the RRC connection establishment process, the UE may start the T300 timer.
[0168] In step 6-70, UE 6-01 in RRC idle mode may send an RRC connection request (RRCSetupRequest) message to the NR cell 6-02.
[0169] In step 6-75, the NR cell 6-02 may send an RRC connection (RRCSetup) message to the UE 6-01 in RRC idle mode.
[0170] In step 6-76, UE 6-01 may stop the running T300 timer. In addition, UE 6-01 may transition to RRC connected mode.
[0171] In step 6-80, when the connection establishment / recovery failure information is stored in VarConnEstFailReport and the plmn-Identity stored in VarConnEstFailReport matches the RPLMN, the UE 6-01 that has switched to the RRC connection mode can send an RRC connection completion (RRCSetupComplete) message by including an indicator (e.g., ConnEstFailInfoAvailable) notifying the NR cell 6-02 of the RRC connection completion (RRCSetupComplete) message.
[0172] In step 6-85, the NR cell 6-02 may send a UEInformationRequest message to the UE 6-01 by setting information indicating whether information about RRC connection establishment / recovery failure is reported in a message (UEInformationRequest message) used to request information from the UE (e.g., connEstFailReportReq) to true.
[0173] In step 6-90, when connEstFailReportReq is set to true in the received UEInformationRequest message, the connection establishment / recovery failure information is stored in VarConnEstFailReport, and the plmn-Identity stored in VarConnEstFailReport is the same as the RPLMN, the UE 6-01 may send a message (UEInformationResponse message) for reporting the information requested by the base station to the NR cell by performing the following operations:
[0174] - set timeSinceFailure in VarConnEstFailReport to the time that has passed since the last connection establishment failure in NR; and
[0175] - Set connEstFailReport in the UEInformationResponse message to the value of connEstFailReport in VarConnEstFailReport.
[0176] Upon successful delivery of the UEInformationResponse message acknowledged by lower layers, the UE may discard the connEstFailReport from VarConnEstFailReport.
[0177] Figure 7 The process of a UE storing multiple RRC connection establishment / recovery failure information and reporting it to an NR cell in an NR system according to an embodiment of the present disclosure is shown.
[0178] exist Figure 7 In the embodiment, depending on the configuration and / or definition on the system, not all steps described below must be included, and some steps may be omitted.
[0179] According to an embodiment of the present disclosure, a UE may store multiple RRC connection establishment / recovery failure information (multiple connection establishment / recovery failure information, hereinafter referred to as multiple CEFs) and send it to an NR cell. Thus, the operator can optimize the network by identifying and solving the coverage imbalance problem of the downlink (hereinafter referred to as DL) and uplink (hereinafter referred to as UL) of the base station. In the present disclosure, a method for a UE to store multiple CEFs and report them to a base station is provided.
[0180] refer to Figure 7 In step 7-07, UE 7-01 can be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with the NR cell 7-02.
[0181] In step 7-08, the UE 7-01 in RRC connected mode may send a UE capability information message (UECapabilityInformation) to the NR cell 7-02. The message may include an indicator indicating whether the UE has the ability to store and report multiple CEFs (to the NR base station).
[0182] In step 7-10, the NR cell 7-02 may send an RRC connection release message (RRCRelease) that does not include the suspend configuration information (suspendConfig) to the UE 7-01.
[0183] In step 7-15, UE 7-01 that has received the RRCRelease message may transition to the RRC idle mode (RRC_IDLE).
[0184] In step 7-20, UE 7-01 in RRC idle mode may perform a PLMN selection procedure.
[0185] At step 7-25, the UE 7-01 in RRC idle mode may perform a cell selection procedure to camp on a suitable cell of the selected or registered PLMN.
[0186] In step 7-30, the UE 7-01 in RRC idle mode may perform a cell reselection procedure to find a better suitable cell.
[0187] In step 7-35, UE 7-01 in RRC idle mode may initiate an RRC connection establishment process with NR cell 7-02. When initiating the RRC connection establishment process, the UE may start the T300 timer.
[0188] At step 7-40, the T300 timer driven by the UE at step 7-35 may expire.
[0189] In step 7-45, the UE may Figure 6 The embodiment performs operations 1 and 2 sequentially.
[0190] In step 7-50, UE 7-01 in RRC idle mode may initiate an RRC connection establishment process with NR cell 7-03. When initiating the RRC connection establishment process, the UE may start the T300 timer.
[0191] At step 7-55, the T300 timer driven by the UE in step 7-50 may expire.
[0192] In step 7-60, when the T300 timer expires, the UE 7-01 may store the RRC connection establishment / recovery failure information that has failed in multiple cells. The UE supporting multiple CEF functions may perform at least one of the following operations sequentially or independently to prevent duplicate CEF information from being reported to the base station when recording multiple RRC connection establishment / recovery failure information.
[0193] - Operation A: When RRC connection establishment / recovery failure information is stored in the UE variable (VarConnEstFailReportList) including the connection establishment failure and / or connection recovery failure information list, but the plmn-Identity stored in the VarConnEstFailReportList or the VarConnEstFailReportList is different from the RPLMN, the UE may clear all information stored in the VarConnEstFailReportList.
[0194] *VarConnEstFailReport can be composed of connEstFailReport and plmn-Identity. For example, VarConnEstFailReport can be configured as shown in Table 2 below.
[0195] Table 2
[0196]
[0197] *When the UE determines that the RRC connection establishment / recovery failure information is stored in the VarConnEstFailReportList, but the plmn-Identity stored in the VarConnEstFailReport is different from the RPLMN, the VarConnEstFailReportList can be configured as shown in Table 3 below.
[0198] Table 3
[0199]
[0200] In Table 3, maxCEF-Report may refer to the maximum number of CEF reports that the UE may store. For example, the value of maxCEF-Report may be 8, and the value of maxCEFReport-1 may be 7. The UE has the advantage of not needing to manage a separate plmn-Identity in VarConnEstFailReportList.
[0201] When the UE determines that the RRC connection establishment / recovery failure information is stored in the VarConnEstFailReportList, but the plmn-Identity stored in the VarConnEstFailReportList is different from the RPLMN, the VarConnEstFailReportList may be configured as shown in Table 4 below.
[0202] Table 4
[0203]
[0204] For example, the value of maxCEF-Report may be 8, and the value of maxCEFReport-1 may be 7. The UE may manage only one plmn-Identity in VarConnEstFailReportList.
[0205] - Operation B: When the current cell (the cell that failed to establish / restore the RRC connection) is different from the cell that failed to establish / restore the most recent RRC connection stored in VarConnEstFailReport (which can be determined by the cell identity), the UE can store (or append) the information stored in VarConnEstFailReport to VarConnEstFailReportList. For example, when the most recent cell 7-02 that failed to establish / restore the RRC connection in step 7-40 and the current cell 7-03 that failed to establish / restore the RRC connection in step 7-55 are different, the UE can store the RRC connection establishment / restore failure information stored in the VarConnEstFailReport for the NR cell 7-02 in step 7-45 in VarConnEstFailReportList. The UE can perform operation B only when the plmn-Identity stored in VarConnEstFailReport or VarConnEstFailReportList is the same as the RPLMN. According to an embodiment of the present disclosure, the UE may store CEF information in the VarConnEstFailReportList until maxCEFReport-1. For example, the UE may store CEF information in the VarConnEstFailReportList only when maxCEFReport is not reached. In addition, when the UE stores CEF information in the VarConnEstFailReportList until maxCEFReport-1, the UE may erase the first stored CEF information and store new CEF information. Alternatively, when the UE stores CEF information in the VarConnEstFailReportList until maxCEFReport-1, the UE may no longer store CEF information in the VarConnEstFailReportList.
[0206] - Operation C: According to the operation (e.g., operation 2) of the above embodiment, the RRC connection establishment / recovery failure information of the cell in which the current RRC connection establishment / recovery has failed may be stored in VarConnEstFailReport. However, the UE may not store VarConnEstFailReport in VarConnEstFailReportList. For example, the UE may store the cell 7-03 in which the RRC connection establishment / recovery has failed through step 7-55 in VarConnEstFailReport according to operation 2 of the above embodiment.
[0207] In step 7-65, UE 7-01 in RRC idle mode may initiate an RRC connection establishment process with NR cell 7-02. When initiating the RRC connection establishment process, the UE may start the T300 timer.
[0208] In step 7-70, UE 7-01 in RRC idle mode can send an RRC connection request (RRCSetupRequest) message to the NR cell 7-02.
[0209] In step 7-75, the NR cell 7-02 may send an RRC connection (RRCSetup) message to the UE 7-01 which is in RRC idle mode.
[0210] In step 7-76, UE 7-01 may stop the running T300 timer. In addition, UE 7-01 may transition to RRC connected mode.
[0211] In step 7-80, when the connection establishment / recovery failure information is stored in VarConnEstFailReport and / or VarConnEstFailReportList, and the plmn-Identity stored in VarConnEstFailReportList matches the RPLMN, the UE 7-01 that has switched to the RRC connection mode can send an RRC connection completion (RRCSetupComplete) message by including an indicator (e.g., connEstFailInfoAvailable) notifying the NR cell 7-02 of the RRC connection completion (RRCSetupComplete) message.
[0212] In step 7-85, the NR cell 7-02 may send a UEInformationRequest message to the UE 7-01 by setting information indicating whether information about RRC connection establishment / recovery failure is reported in a message (UEInformationRequest message) used to request information from the UE (e.g., connEstFailReportReq) to true.
[0213] In step 7-90, when connEstFailReportReq is set to true in the received UEInformationRequest message, the connection establishment / recovery failure information is stored in VarConnEstFailReport and / or VarConnEstFailReportList, and the plmn-Identity stored in VarConnEstFailReportList and / or VarConnEstFailReportList is the same as the RPLMN, the UE 7-01 may send a message (UEInformationResponse message) for reporting the information requested by the base station to the NR cell by performing at least one of the following operations:
[0214] - Set timeSinceFailure in VarConnEstFailReport to the time elapsed since the last connection establishment failure in NR;
[0215] - set the connEstFailReport in the UEInformationResponse message to the value of connEstFailReport in VarConnEstFailReport; and
[0216] - Set the connEstFailReportList in the UEInformationResponse message to the value of the connEstFailReportList in VarConnEstFailReportList (in this case, the UE may set timeSinceFailure for the individual connEstFailReport included in the connEstFailReportList, indicating the time that has elapsed since the (most recent) RRC connection establishment / recovery failure in NR. For example, the UE may set the time that has elapsed from step 7-40 to now to timeSinceFailure).
[0217] Upon successful delivery of the UEInformationResponse message acknowledged by lower layers, the UE may discard the connEstFailReport from VarConnEstFailReport and / or the connEstFailReportList from VarConnEstFailReportList.
[0218] Figure 8The process of a UE storing multiple RRC connection establishment / recovery failure information and reporting it to an NR cell in an NR system according to an embodiment of the present disclosure is shown.
[0219] exist Figure 8 In the embodiment, depending on the configuration and / or definition on the system, not all steps described below must be included, and some steps may be omitted.
[0220] According to an embodiment of the present disclosure, a UE may store multiple RRC connection establishment / recovery failure information (multiple connection establishment / recovery failure information, hereinafter referred to as multiple CEFs) and send it to an NR cell. Thus, the operator can optimize the network by identifying and solving the coverage imbalance problem of the downlink (hereinafter referred to as DL) and uplink (hereinafter referred to as UL) of the base station. In the present disclosure, a method for a UE to store multiple CEFs and report them to a base station is provided.
[0221] refer to Figure 8 In step 8-07, UE 8-01 may be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with NR cell 8-02.
[0222] In step 8-08, UE 8-01 in RRC connection mode may send a UE capability information message (UECapabilityInformation) to NR cell 8-02. The message may include an indicator indicating that the UE has the ability to store multiple CEFs and report multiple CEFs to the NR base station.
[0223] In step 8-10, the NR cell 8-02 may send an RRC connection release message (RRCRelease) that does not include the suspension configuration information (suspendConfig) to the UE 8-01.
[0224] In step 8-15, UE 8-01 that has received the RRCRelease message may transition to the RRC idle mode (RRC_IDLE).
[0225] In step 8-20, UE 8-01 in RRC idle mode may perform a PLMN selection procedure.
[0226] At step 8-25, the UE 8-01 in RRC idle mode may perform a cell selection procedure to camp on a suitable cell of the selected or registered PLMN.
[0227] In step 8-30, UE 8-01 in RRC idle mode may perform a cell reselection procedure to find a better suitable cell.
[0228] In step 8-35, UE 8-01 in RRC idle mode may initiate an RRC connection establishment process with NR cell 8-02. When initiating the RRC connection establishment process, the UE may start the T300 timer.
[0229] At step 8-40, the T300 timer driven by the UE at step 8-35 may expire.
[0230] In step 8-45, the UE may sequentially perform the following operations i and ii.
[0231] - Operation i: Operations not related to VarConnEstFailReport / VarConnEstFailReportList
[0232] * Reset MAC, release MAC configuration and re-establish RLC for all established RBs; and
[0233] * If the UE supports RRC connection establishment failure with temporary offset and T300 has expired connEstFailCount times consecutively on the same cell for which connEstFailureControl is included in SIB1 within the period indicated by connEstFailOffsetValidity, connEstFailOffset shall be used for parameter Qoffsettemp of the relevant cell when performing cell selection and reselection according to TS 38.304 and TS 36.304.
[0234] - Operation ii: Operations related to VarConnEstFailReport / VarConnEstFailReportList
[0235] * If the UE has connection establishment failure information or connection recovery failure information available in VarConnEstFailReport and if RPLMN is not equal to plmn-identity stored in VarConnEstFailReport or if the cell identity of the current cell is not equal to the cell identity in measResultFailedCell stored in VarConnEstFailReport, then numberOfConnFail is reset to 0;
[0236] * If the UE has connection establishment failure information or connection recovery failure information available in VarConnEstFailReportList, and if the RPLMN is not equal to the plmn-identity stored in VarConnEstFailReportList or VarConnEstFailReportList, clear the contents included in VarConnEstFailReportList;
[0237] * Clears all content (if any) included in VarConnEstFailReport except numberOfConnFail; and
[0238] * The following connection establishment failure information is stored in VarConnEstFailReport by setting its fields as follows:
[0239] ** Set plmn-Identity to the PLMN selected by upper layers (see TS24.501) from the PLMNs included in the plmn-IdentityList in SIB1;
[0240] **Based on the available SSB measurements collected until the UE detects the connection establishment failure, measResultFailedCell is set to include the global cell identity, tracking area code, cell-level and SS / PBCH block-level RSRP, RSRQ, and SS / PBCH block index of the failed cell; and
[0241] **If available, measResultNeighCells is set in descending order of ranking criteria for cell reselection to include neighbor cell measurements for up to the following number of neighbor cells: 6 intra-frequency neighbors and 3 inter-frequency neighbors per frequency, and 3 inter-RAT neighbors per frequency / frequency set per RAT, and according to the following:
[0242] **For each neighbor cell included, include the available optional fields;
[0243] **If available, set locationInfo as follows:
[0244] *** If available, sets commonLocationInfo to include detailed location information; and
[0245] *** If available, bt-LocationInfo is set to include Bluetooth measurements in order of decreasing RSSI for Bluetooth beacons;
[0246] **If available, wlan-LocationInfo is set to include WLAN measurements in order of decreasing RSSI for WLAN Ap;
[0247] **If available, set sensor-LocationInfo to include sensor measurements as follows:
[0248] *** sensor-MeasurementInformation if available; and
[0249] ***If available, include sensor-MotionInformation;
[0250] **Set perRAInfoList to indicate random access failure information;
[0251] **If numberOfConnFail is less than 7, increase numberOfConnFail by 1;
[0252] *If UE supports multiple CEF reports:
[0253] **If the cgi-Info in the measResultFailedCell in the newly added VarConnEstFailReport (or in the ConnEstFailReport in the connEstFailReport List in the newly added VarConnEstFailReportList) is the same as the cgi-Info in the measResultFailedCell in the last entry in the VarConnEstFailReportList:
[0254] ***Replace all information for the entry of VarConnEstFailReport (or the entry of ConnEstFailReport) except numberOfConnFail;
[0255] **otherwise:
[0256] *** If maxCEFReport-r17 has not been reached:
[0257] ****Append VarConnEstFailReport (or ConnEstFailReport) as a new entry in VarConnEstFailReportList;
[0258] *Notify the upper layer about the failure to establish the RRC connection. This process ends here.
[0259] According to an embodiment of the present disclosure, VarConnEstFailReportList may be configured as one of the following Tables 5 or 6 (or may be configured as above in Figure 7 configurable as described in ).
[0260] Table 5
[0261]
[0262] Table 6
[0263]
[0264]
[0265] In step 8-50, UE 8-01 in RRC idle mode may initiate an RRC connection establishment process with NR cell 8-03. When initiating the RRC connection establishment process, the UE may start the T300 timer.
[0266] At step 8-55, the T300 timer driven by the UE in step 8-50 may expire.
[0267] In step 8-60, when the T300 timer expires, the UE 8-01 may store the RRC connection establishment / recovery failure information that has failed in multiple cells. According to an embodiment, a UE supporting multiple CEF functions may store duplicate CEF information when recording multiple RRC connection establishment / recovery failure information. Specifically, the following operations may be considered.
[0268] -The ConnEstFailReport stored in the last entry of the VarConnEstFailReportList (the last entry of the ConnEstFailReport in the ConnEstFailReportList in the VarConnEstFailReportList) may have the same value as the ConnEstFailReport stored in the VarConnEstFailReport. Alternatively, the VarConnEstFailReport stored in the last entry of the VarConnEstFailReportList may be the same value as the value stored in the VarConnEstFailReport. For example, the RRC connection establishment / recovery failure information of the cell 8-03 that has failed through the RRC connection establishment / recovery of step 8-55 may be stored in the VarConnEstFailReportList and also stored in the VarConnEstFailReport.
[0269] -The UE may store the RRC connection establishment / recovery failure information of the cell in which the RRC connection establishment / recovery has failed in VarConnEstFailReportList. For example, the UE may store the RRC connection establishment / recovery failure information of the cell 8-02 in which the RRC connection establishment / recovery through step 8-40 has failed in VarConnEstFailReportList. In addition, when the cell in which the current RRC connection establishment / recovery has failed is the same as the cell in which the most recent RRC connection establishment / recovery has failed (for example, when cells 8-02 and 8-03 are the same), the UE may then erase all information except numberOfConnFail, and replace numberOfConnFail with the RRC connection establishment / recovery failure information of the cell in which the current RRC connection establishment / recovery has failed, and store it in VarConnEstFailReportList.
[0270] That is, without adding new entries to VarConnEstFailReportList, the existing information can be replaced with the RRC connection establishment / recovery failure information of the cell in which the RRC connection establishment / recovery has failed. When the cell in which the current RRC connection establishment / recovery has failed is different from the cell in which the most recent RRC connection establishment / recovery has failed (for example, when cells 8-02 and 8-03 are different), the UE can store the RRC connection establishment / recovery failure information of the cell in which the RRC connection establishment / recovery has failed as a new entry in VarConnEstFailReportList. Up to maxCEFReport-r17 entries (i.e., each CEF value) can be stored in VarConnEstFailReportList.
[0271] In step 8-65, UE 8-01 in RRC idle mode may initiate an RRC connection establishment process with NR cell 8-02. When initiating the RRC connection establishment process, the UE may start the T300 timer.
[0272] In step 8-70, UE 8-01 in RRC idle mode may send an RRC connection request (RRCSetupRequest) message to the NR cell 8-02.
[0273] In step 8-75, the NR cell 8-02 may send an RRC connection (RRCSetup) message to the UE 8-01 in RRC idle mode.
[0274] In step 8-76, UE 8-01 may stop the running T300 timer. In addition, UE 8-01 may transition to RRC connected mode.
[0275] In step 8-80, when the connection establishment / recovery failure information is stored in VarConnEstFailReport and / or VarConnEstFailReportList, and the plmn-Identity stored in VarConnEstFailReportList matches the RPLMN, the UE 8-01 that has switched to the RRC connection mode can send an RRC connection completion (RRCSetupComplete) message by including an indicator (e.g., connEstFailInfoAvailable) notifying the NR cell 8-02 of the RRC connection completion (RRCSetupComplete) message.
[0276] In step 8-85, the NR cell 8-02 may send a UEInformationRequest message to the UE 8-01 by setting information indicating whether to report information about the RRC connection establishment / recovery failure in a message (UEInformationRequest message) for requesting information from the UE (e.g., connEstFailReportReq) to true. According to an embodiment of the present disclosure, in step 8-85, the NR cell 8-02 may set an indicator to true to report multiple CEFs in the UEInformationRequest message.
[0277] In step 8-90, when connEstFailReportReq is set to true in the received UEInformationRequest message, the connection establishment / recovery failure information is stored in VarConnEstFailReport and / or VarConnEstFailReportList, and the plmn-Identity stored in VarConnEstFailReportList and / or VarConnEstFailReportList is the same as the RPLMN, the UE 8-01 can send a message (UEInformationResponse message) for reporting the information requested by the base station to the NR cell by performing the following operations:
[0278] - Set timeSinceFailure in VarConnEstFailReport to the time elapsed since the last connection establishment failure in NR;
[0279] - set the connEstFailReport in the UEInformationResponse message to the value of connEstFailReport in VarConnEstFailReport; and
[0280] -Set the connEstFailReportList in the UEInformation message to the value of the connEstFailReportList in the VarConnEstFailReportList, except for the last entry in the connEstFailReportList in the VarConnEstFailReportList (i.e., the UE may exclude the ConnEstFailReport or the VarConnEstFailReport in the last entry in the ConnEstFailReportList stored in the VarConnEstFailReportList. According to an embodiment of the present disclosure, the UE may set timeSinceFailure for an individual connEstFailReport included in the connEstFailReportList, indicating the time that has elapsed since the (most recent) RRC connection establishment / recovery failure in the NR. For example, the UE may set the time that has elapsed from step 8-40 to now to timeSinceFailure).
[0281] Upon successful delivery of the UEInformationResponse message acknowledged by lower layers, the UE may discard the connEstFailReport from VarConnEstFailReport and / or the connEstFailReportList from VarConnEstFailReportList.
[0282] In step 8-90, when the indicator for reporting multiple CEFs in the received UEInformationRequest message is true, there is connection establishment / recovery failure information in VarConnEstFailReport and / or VarConnEstFailReportList, and the plmn-Identity stored in VarConnEstFailReportList and / or VarConnEstFailReportList is the same as the RPLMN, the UE 8-01 can send a UEInformationResponse message to the NR cell by performing the following operations:
[0283] -Set the connEstFailReportList in the UEInformationResponse message to the value of the connEstFailReportList in the VarConnEstFailReportList (in this case, the UE may set timeSinceFailure for the individual connEstFailReport included in the connEstFailReportList, indicating the time that has elapsed since the RRC connection establishment / recovery failure in NR. For example, the UE may set the time that has elapsed from step 8-40 to now to timeSinceFailure). That is, the UE may send only the information stored in the VarConnEstFailReportList to the UEInformationResponse message, and may not send the information stored in the VarConnEstFailReport to the UEInformationResponse message.
[0284] Upon successful delivery of the UEInformationResponse message acknowledged by lower layers, the UE may discard the connEstFailReport from VarConnEstFailReport and / or the connEstFailReportList from VarConnEstFailReportList.
[0285] Fig. 9 The process of a UE storing multiple RRC connection establishment / recovery failure information and reporting it to an NR cell in an NR system according to an embodiment of the present disclosure is shown.
[0286] exist Fig. 9 In the embodiment, depending on the configuration and / or definition on the system, not all steps described below must be included, and some steps may be omitted.
[0287] According to an embodiment of the present disclosure, a UE may store multiple RRC connection establishment / recovery failure information (multiple connection establishment / recovery failure information, hereinafter referred to as multiple CEFs) and send it to an NR cell. Thus, the operator can optimize the network by identifying and solving the coverage imbalance problem of the downlink (hereinafter referred to as DL) and uplink (hereinafter referred to as UL) of the base station. In the present disclosure, a method for a UE to store multiple CEFs and report them to a base station is provided.
[0288] refer to Fig. 9In step 9-03, UE 9-01 can be in RRC connected mode (RRC_CONNECTED) by establishing an RRC connection with NR cell 9-02.
[0289] In step 9-05, UE 9-01 in RRC connection mode may send a UE capability information message (UECapabilityInformation) to NR cell 9-02. The message may include an indicator indicating that the UE has the ability to store multiple CEFs and report multiple CEFs to the NR base station.
[0290] In step 9-10, the NR cell 9-02 may send an RRC connection release message (RRCRelease) that does not include the suspend configuration information (suspendConfig) to the UE 9-01.
[0291] In step 9-15, UE 9-01 that receives the RRCRelease message may transition to an RRC inactive mode (RRC_INACTIVE).
[0292] In step 9-20, the UE 9-01 in RRC idle mode may perform a cell selection procedure to camp on a suitable cell for the selected or registered PLMN.
[0293] In step 9-25, UE 9-01 in RRC idle mode may perform a cell reselection procedure to find a better suitable cell.
[0294] In step 9-30, UE 9-01 in RRC idle mode may initiate an RRC connection establishment process with NR cell 9-02. When initiating the RRC connection establishment process, the UE may start the T319 timer.
[0295] At step 9-35, the T319 timer driven by the UE at step 9-30 may expire.
[0296] In step 9-40, the UE may Figure 7 The embodiment of the present invention performs operation A, operation B and / or operation C, or according to Figure 8 The embodiment performs operation ii to store a plurality of CEFs.
[0297] At step 9-45, the UE may transition to RRC idle mode (RRC_IDLE).
[0298] Fig.10 A flow chart illustrating an operation of storing measurement results by a UE according to an embodiment of the present disclosure is shown.
[0299] exist Fig.10In the embodiment, depending on the configuration and / or definition on the system, not all steps described below must be included, and some steps may be omitted.
[0300] refer to Fig.10 In step 10-05, the UE can establish an RRC connection with the NR base station and be in RRC connection mode (RRC_CONNECTED).
[0301] In step 10-10, the RRC connected mode UE may receive a LoggedMeasurementConfiguration message from the NR base station.
[0302] Upon receiving the message, the UE may perform the following procedures:
[0303] *1>Discard the recorded measurement configuration and recorded measurement information;
[0304] *1> Store the received loggingDuration, reportType and areaConfiguration (if included) in VarLogMeasConfig;
[0305] *1> If the LoggedMeasurementConfiguration message includes plmn-IdentityList:
[0306] **2> Set plmn-IdentityList in VarLogMeasReport to include RPLMN and the PLMN included in plmn-IdentityList;
[0307] *1>Otherwise:
[0308] **2>Set plmn-IdentityList in VarLogMeasReport to include RPLMN;
[0309] *1> Store the received absoluteTimeInfo, traceReference, traceRecordingSessionRef, tce-Id and sigLoggedMeasType in VarLogMeasReport;
[0310] *1> Store the received bt-NameList (if included) in VarLogMeasConfig;
[0311] *1>Store the received wlan-NameList (if included) in VarLogMeasConfig;
[0312] *1>Store the received sensor-NameList (if included) in VarLogMeasConfig;
[0313] *1>Start timer T330, where the timer value is set to loggingDuration; and
[0314] *1> Store the received earlyMeasIndication (if included) in VarLogMeasConfigure
[0315] In steps 10-15, the UE may receive an RRC connection release message (RRCRelease) from the NR base station.
[0316] In step 10-20, the UE may transition to the RRC idle mode (RRC_IDLE) or the RRC inactive mode (RRC_INACTIVE) according to the above embodiments.
[0317] In step 10-25, the T330 timer started in step 10-10 may continue to run.
[0318] At step 10-30, the RRC idle mode or RRC inactive mode UE may determine whether to suspend measurement logging.
[0319] When it is determined in step 10-30 to suspend measurement logging, the UE may determine in step 10-35 whether an in-device coexistence (IDC) problem detected by the UE is resolved during the last logging interval.
[0320] In step 10-35, when the UE determines that the IDC problem detected by the UE has not been resolved during the most recent logging interval, the UE may continue to suspend the measurement logging in step 10-40.
[0321] In step 10-35, when the UE determines that the IDC problem detected by the UE during the most recent logging interval is resolved, measurement logging may be resumed in step 10-45.
[0322] When it is determined in step 10-30 that the measurement logging is not suspended or in step 10-45 that the measurement logging is resumed, the UE may perform the measurement logging in step 10-50. Specifically, the UE may perform the measurement logging by performing one of operation a, [operation b, operation c, operation d], and operation e. The differences between operation b, operation c, and operation d are as follows.
[0323] Operation b: If the UE detects an IDC problem during the last logging interval, the UE may perform measurement logging including inDeviceCoexDetected regardless of whether the measurement result of the serving cell is present in VarLogMeasReport, and suspend measurement logging from the next logging interval. Even if an IDC problem has been detected during the last logging interval, there is an advantage of notifying the base station that an IDC problem has occurred by performing measurement logging, because the UE can selectively include the measurement result of the serving cell in LogMeasInfo.
[0324] Operation c: If the UE detects an IDC problem during the last logging interval, the UE may perform measurement logging including inDeviceCoexDetected only when there is a measurement result of the serving cell in VarLogMeasReport or when reportType is configured as eventTriggered, and suspend measurement logging from the next logging interval. When reportType is configured as eventTriggered, there is an advantage that the UE can notify the base station that an event (outOfCoverage or eventL1) has occurred and an IDC problem has occurred, although a situation where there is no measurement result of the serving cell may occur.
[0325] Operation d: If the UE detects an IDC problem during the last logging interval, the UE may perform measurement logging including inDeviceCoexDetected only when there is a measurement result of the serving cell in VarLogMeasReport or when reportType is configured as eventTriggered and the corresponding eventType is configured as outOfCoverage, and suspend measurement logging from the next logging interval. This is because when eventType is outOfCoverage, there may be multiple cases where there is no measurement result of the serving cell in VarLogMeasReport.
[0326] Detailed description of the specific implementation mode Operation a to operation e are as follows:
[0327] Operation a:
[0328] **2> If reportType is set to periodic in VarLogMeasConfig:
[0329] ***3> If the UE is in any cell selection state (as specified in TS 38.304):
[0330] ****4> Perform logging at regular time intervals, as defined by loggingInterval in VarLogMeasConfig;
[0331] ***3> If the UE is in normal camping state on the NR cell and if the RPLMN is included in the plmn-IdentityList stored in VarLogMeasReport:
[0332] ****4>If VarLogMeasConfig does not include areaConfiguration; or
[0333] ****4> If the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig:
[0334] *****5> Perform logging at regular time intervals, as defined by loggingInterval in VarLogMeasConfig;
[0335] **2> Otherwise if reportType is set to eventTriggered and eventType is set to outOfCoverage:
[0336] ***3> Logging is performed at regular time intervals defined by loggingInterval in VarLogMeasConfig only when the UE is in any cell selection state;
[0337] ***3> When switching from any cell selection state to the normal state in NR:
[0338] ****4> If RPLMN is included in the plmn-IdentityList stored in VarLogMeasReport; and
[0339] ****4> If areaConfiguration is not included in VarLogMeasConfig or if the current camping cell is part of the area indicated by areaConfiguration in VarLogMeasConfig:
[0340] *****5>Execution record;
[0341] **2> Otherwise if reportType is set to eventTriggered and eventType is set to eventL1:
[0342] ***3> If the UE is in normal camping state on the NR cell and if the RPLMN is included in the plmn-IdentityList stored in VarLogMeasReport:
[0343] ****4>If VarLogMeasConfig does not include areaConfiguration; or
[0344] ****4>If the serving cell is part of the area indicated by areaConfig in areaConfiguration in VarLogMeasConfig;
[0345] *****5>Only when the condition indicated by eventL1 is met, logging is performed at regular time intervals defined by loggingInterval in VarLogMeasConfig;
[0346] **2>When executing the record:
[0347] Operation b:
[0348] ***3> If the UE detects an IDC problem during the last logging interval:
[0349] ****4>Include inDeviceCoexDetected;
[0350] ****4> Pause measurement recording from the next recording interval;
[0351] Operation c:
[0352] ***3> If the UE detects an IDC problem during the last logging interval:
[0353] ****4>If measResultServingCell in VarLogMeasReport is not empty; or
[0354] ****4>If reportType is set to eventTriggered:
[0355] *****>Include inDeviceCoexDetected;
[0356] *****5> Pause measurement recording from the next recording interval;
[0357] ****4> Otherwise:
[0358] *****5> Pause measurement recording;
[0359] Operation d:
[0360] ***3> If the UE detects an IDC problem during the last logging interval:
[0361] ****4>If measResultServingCell in VarLogMeasReport is not empty; or
[0362] ****4>If reportType is set to eventTriggered and eventType is set to outOfCoverage:
[0363] *****>Include inDeviceCoexDetected;
[0364] *****5> Pause measurement recording from the next recording interval;
[0365] ****4>Otherwise:
[0366] *****5> Pause measurement recording;
[0367] Operation e:
[0368] ***3> Set relativeTimeStamp to indicate the time elapsed since the moment the recorded measurement configuration was received;
[0369] ***3> If location information became available during the last logging interval, set the contents of locationInfo:
[0370] ***3> If the UE is in any cell selection state (as specified in TS 38.304):
[0371] ****4>Set anyCellSelectionDetected to indicate that no suitable or acceptable cell was found;
[0372] ****4> If reportType is set to eventTriggered in VarLogMeasConfig; and
[0373] ****4> If the RPLMN at the time of entering any cell selection state is included in the plmn-IdentityList stored in VarLogMeasReport; and
[0374] ****4> If areaConfiguration is not included in VarLogMeasConfig or if the last suitable cell the UE camped on is part of the area indicated by areaConfiguration in VarLogMeasConfig:
[0375] *****5> Set servCellIdentity to indicate the global cell identity of the last suitable cell on which the UE camped;
[0376] *****5> Set measResultServingCell to include the number of the last suitable cell on which the UE camped;
[0377] ****4>Otherwise, if reportType is set to periodic in VarLogMeasConfig:
[0378] *****5> Set servCellIdentity to indicate the global cell identity of the last recorded cell on which the UE camped;
[0379] *****5> Set measResultServingCell to include the number of the last recorded cell on which the UE was camped;
[0380] ***3>Otherwise:
[0381] ****4> Set servCellIdentity to indicate the global cell identity of the cell on which the UE is camped;
[0382] ****4> Set measResultServingCell to include the number of cells on which the UE is camped;
[0383] ***3> If available, measResultNeighCells is set in descending order of ranking criteria for cell reselection to include measurements of neighboring cells that became available during the last logging interval and according to the following:
[0384] ****4> According to the following content, including the measurement results of up to 6 neighboring cells on the NR service frequency and up to 3 cells on each NR neighboring frequency and the measurement results of NR neighboring frequencies:
[0385] *****5>If interFreqTargetInfo is included in VarLogMeasConfig:
[0386] ******6>If earlyMeasIndication is included in VarLogMeasConfig;
[0387] 7> Measurement results of NR adjacent frequencies included in both interFreqTargetInfo and measIdleCarrierListNR or SIB4;
[0388] ******6> Otherwise:
[0389] 7> including the measurement results of NR adjacent frequencies included in both interFreqTargetInfo and SIB4;
[0390] *****5>Otherwise:
[0391] ******6>If earlyMeasIndication is included in VarLogMeasConfig;
[0392] *******7>Including the measurement results of NR adjacent frequencies included in measIdleCarrierListNR or SIB4;
[0393] ******6> Otherwise:
[0394] 7> including the measurement results of NR adjacent frequencies included in SIB4;
[0395] ****4> Include measurement results of up to 3 neighbors per inter-RAT frequency according to the following:
[0396] *****5>If earlyMeasIndication is included in VarLogMeasConfig:
[0397] ******6>Including the measurement results of adjacent frequencies between RATs included in measIdleCarrierListEUTRA or SIB5;
[0398] *****5>Otherwise:
[0399] ******6>Including the measurement results of the inter-RAT frequencies included in SIB5;
[0400] ****4>For each neighboring cell included, include the available optional fields;
[0401] **2> When the memory reserved for logged measurement information becomes full, stop timer T330 and perform the same actions as performed when T330 expires, as specified in the 3GPP standard specification.
[0402] Fig.11 The internal structure of the UE according to an embodiment of the present disclosure is shown.
[0403] Referring to the drawing, the UE includes a Radio Frequency (RF) processor 11-10, a baseband processor 11-20, a storage device 11-30, and a controller 11-40.
[0404] The RF processor 11-10 performs functions for sending and receiving signals through a radio channel, such as frequency band conversion and amplification of signals. That is, the RF processor 11-10 up-converts the baseband signal provided by the baseband processor 11-20 to an RF band signal, sends the RF band signal through an antenna, and down-converts the RF band signal received by the antenna to a baseband signal. For example, the RF processor 11-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. In the figure, only one antenna is shown, but the UE may include multiple antennas. In addition, the RF processor 11-10 may include multiple RF chains. In addition, the RF processor 11-10 may perform beamforming. For beamforming, the RF processor 11-10 may adjust the phase and amplitude of each signal sent and received by multiple antennas or antenna elements. In addition, the RF processor may perform MIMO, and may receive multiple layers when performing MIMO operations.
[0405] The baseband processor 11-20 performs the function of converting between the baseband signal and the bit stream according to the physical layer standard of the system. For example, when sending data, the baseband processor 11-20 generates complex symbols by encoding and modulating the transmitted bit stream. In addition, when receiving data, the baseband processor 11-20 recovers the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 11-10. For example, in the case of following the orthogonal frequency division multiplexing (OFDM) scheme, when sending data, the baseband processor 11-20 generates complex symbols by encoding and modulating the transmitted bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols by inverse fast Fourier transform (IFFT) operation and cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processor 11-20 divides the baseband signal provided by the RF processor 11-10 into OFDM symbol units, recovers the signal mapped to the subcarrier by fast Fourier transform (FFT) operation, and then recovers the received bit stream by demodulation and decoding.
[0406] As described above, the baseband processor 11-20 and the RF processor 11-10 send and receive signals. Therefore, the baseband processor 11-20 and the RF processor 11-10 can be referred to as a transmitter, a receiver, a transceiver or a communicator. In addition, at least one of the baseband processor 11-20 and the RF processor 11-10 may include a plurality of communication modules to support a variety of different radio access technologies. In addition, at least one of the baseband processor 11-20 and the RF processor 11-10 may include different communication modules to process signals of different frequency bands. For example, different radio access technologies may include wireless LAN (e.g., IEEE 802.11), cellular networks (e.g., LTE), etc. In addition, different frequency bands may include ultra-high frequency (SHF) (e.g., 2.5 GHz, 5 GHz) bands and millimeter wave (e.g., 60 GHz) bands.
[0407] The storage device 11-30 stores data such as basic programs, applications, and configuration information for the operation of the UE. Specifically, the storage device 11-30 can store information related to a second access node that performs wireless communication using a second radio access technology. In addition, the memory 11-30 provides stored data according to a request of the controller 11-40.
[0408] The controller 11-40 controls the overall operation of the UE. For example, the controller 11-40 sends and receives signals through the baseband processor 11-20 and the RF processor 11-10. In addition, the controller 11-40 writes data into the storage device 11-30 and reads data. To this end, the controller 11-40 may include at least one processor. For example, the controller 11-40 may include a communication processor (CP) that controls communication and an application processor (AP) that controls an upper layer such as an application. For example, the controller 11-40 is configured to initiate a connection establishment process or a connection recovery process on a cell and start a timer corresponding to the connection establishment process or the connection recovery process, identify the expiration of the timer, and when the cell identifier of the cell is not equal to the cell identifier stored in the UE variable for the connection failure report, store the first connection failure report information stored in the UE variable in a new entry of the UE variable list for multiple connection failure reports, clear the UE variable and store the second connection failure report information of the cell in the UE variable, and send a message including the UE variable and the UE variable list via the transceiver (including the RF processor 11-10 and the baseband processor 11-20).
[0409] Fig.12 The configuration of an NR base station according to an embodiment of the present disclosure is shown.
[0410] As shown, the base station is configured to include an RF processor 12-10, a baseband processor 12-20, a backhaul communicator 12-30, a storage device 12-40, and a controller 12-50.
[0411] The RF processor 12-10 performs functions for sending and receiving signals through a radio channel, such as frequency band conversion and amplification of signals. That is, the RF processor 12-10 up-converts the baseband signal provided by the baseband processor 12-20 to an RF band signal, transmits the RF band signal through an antenna, and down-converts the RF band signal received by the antenna to a baseband signal. For example, the RF processor 12-10 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Although only one antenna is shown in the figure, the first access node may include multiple antennas. In addition, the RF processor 12-10 may include multiple RF chains. In addition, the RF processor 12-10 may perform beamforming. For beamforming, the RF processor 12-10 may adjust the phase and amplitude of each signal sent and received by multiple antennas or antenna elements. The RF processor may perform downlink MIMO operations by sending one or more layers.
[0412] The baseband processor 12-20 performs a function of converting between a baseband signal and a bit stream according to the physical layer standard of the first radio access technology. For example, when sending data, the baseband processor 12-20 generates complex symbols by encoding and modulating the transmitted bit stream. In addition, when receiving data, the baseband processor 12-20 recovers the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 12-10. For example, in the case of following the OFDM scheme, when sending data, the baseband processor 12-20 generates complex symbols by encoding and modulating the transmitted bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through IFFT operations and CP insertion. In addition, when receiving data, the baseband processor 12-20 divides the baseband signal provided by the RF processor 12-10 into OFDM symbol units, recovers the signal mapped to the subcarrier by FFT operations, and then recovers the received bit stream by demodulation and decoding. As described above, the baseband processor 12-20 and the RF processor 12-10 send and receive signals. Thus, the baseband processor 12-20 and the RF processor unit 12-10 may be referred to as transmitters, receivers, transceivers, communicators, or wireless communicators.
[0413] The backhaul communicator 12-30 provides an interface for performing communication with other nodes in the network. That is, the backhaul communicator 12-30 converts a bit stream sent from the main base station to another node (e.g., an auxiliary base station, a core network, etc.) into a physical signal, and converts a physical signal received from another node into a bit stream.
[0414] The storage device 12-40 stores data such as basic programs, application programs, and configuration information for the operation of the main base station. Specifically, the storage device 12-40 can store information about the bearer assigned to the accessed UE, the measurement results reported from the accessed UE, etc. In addition, the storage device 12-40 can store information used as a criterion for determining whether to provide or stop multiple connections to the UE. In addition, the storage device 12-40 provides the stored data according to the request of the controller 12-50.
[0415] The controller 12-50 controls the overall operation of the main base station. For example, the controller 12-50 sends and receives signals through the baseband processor 12-20 and the RF processor 12-10 or through the backhaul communicator 12-30. In addition, the controller 12-50 writes data into the storage device 12-40 and reads data. To this end, the controller 12-50 may include at least one processor. For example, the controller 12-50 is configured to perform a connection establishment process or a connection recovery process on a cell with the UE, and receives a message including a UE variable for a connection failure report and a UE variable list for multiple connection failure reports via a transceiver (including the RF processor 12-10 and the baseband processor 12-20).
[0416] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.
Claims
1. A method for a user equipment (UE) in a wireless communication system, the method include: Initiate a connection establishment process or a connection recovery process on the cell, and start a timer corresponding to the connection establishment process or the connection recovery process; Identify timer expiration; In a case where the cell identifier of the cell is not equal to the cell identifier stored in the UE variable for connection failure reporting, storing the first connection failure report information stored in the UE variable in a new entry of the UE variable list for multiple connection failure reports; Clearing the UE variable and storing the second connection failure report information of the cell in the UE variable; as well as A message including UE variables and a UE variable list is sent.
2. The method according to claim 1, in, Storing the first connection failure report information includes: When the PLMN identity of the registered public land mobile network (PLMN) is equal to the PLMN identity stored in the UE variable and the cell identity of the cell is not equal to the cell identity stored in the UE variable, the first connection failure report information stored in the UE variable is stored in a new entry of the UE variable list.
3. The method according to claim 2, further comprising: include: In case the PLMN identity of the registered PLMN is not equal to the PLMN identity stored in the UE variable list, the UE variable list is cleared.
4. The method according to claim 1, further comprising: include: UE capability information indicating whether the UE supports the plurality of connection failure reports is sent.
5. The method according to claim 1, in, Sending messages includes: For each entry of the UE variable list, setting information indicating the time that has elapsed since a connection establishment failure or a connection recovery failure; and The message also includes information indicating the time that has elapsed since the connection establishment failure or the connection recovery failure.
6. The method according to claim 1, in, The UE variable list includes up to a predetermined number of entries.
7. The method according to claim 2, in, Sending a message including a UE variable and a UE variable list includes: receiving a message for requesting UE information, the UE information including information indicating whether the UE reports connection failure information; and In a case where the information indicating whether the UE reports connection failure information is set to true and the PLMN identity of the registered PLMN is equal to the PLMN identity stored in the UE variable or the UE variable list, a message including the UE variable and the UE variable list is sent.
8. The method according to claim 1, further comprising: include: When successful delivery of the message is confirmed, the connection failure report information from the UE variables and UE variable lists is discarded, Wherein, in the case where the timer corresponds to the connection establishment process, the timer is T310, and In the case where the timer corresponds to the connection recovery process, the timer is T319.
9. A user equipment (UE) in a wireless communication system, the UE include: Transceiver; as well as A controller operatively coupled to the transceiver, the controller being configured to: Initiate a connection establishment process or a connection recovery process on the cell, and start a timer corresponding to the connection establishment process or the connection recovery process, Identify timer expiration, In a case where the cell identifier of the cell is not equal to the cell identifier stored in the UE variable for connection failure reporting, storing the first connection failure report information stored in the UE variable in a new entry of the UE variable list for multiple connection failure reports, clearing the UE variable and storing the second connection failure report information of the cell in the UE variable, and A message including the UE variables and the UE variable list is sent via the transceiver.
10. The UE according to claim 9, in, The controller is also configured to: When the PLMN identity of the registered public land mobile network (PLMN) is equal to the PLMN identity stored in the UE variable and the cell identity of the cell is not equal to the cell identity stored in the UE variable, the first connection failure report information stored in the UE variable is stored in a new entry of the UE variable list.
11. The UE according to claim 10, in, The controller is also configured to: In case the PLMN identity of the registered PLMN is not equal to the PLMN identity stored in the UE variable list, the UE variable list is cleared.
12. The UE according to claim 9, in, The controller is also configured to: sending, via the transceiver, UE capability information indicating whether the UE supports the plurality of connection failure reports, and The UE variable list includes a predetermined number of entries.
13. The UE according to claim 9, in, The controller is also configured to: For each entry of the UE variable list, setting information indicating the time that has elapsed since a connection establishment failure or a connection recovery failure; and The message also includes information indicating the time that has elapsed since the connection establishment failure or the connection recovery failure.
14. The UE according to claim 10, in, The controller is also configured to: receiving, via a transceiver, a message for requesting UE information, the UE information including information indicating whether the UE reports connection failure information, and In a case where the information indicating whether the UE reports connection failure information is set to true and the PLMN identity of the registered PLMN is equal to the PLMN identity stored in the UE variable or the UE variable list, a message including the UE variable and the UE variable list is sent via the transceiver.
15. The UE according to claim 11, in, The controller is also configured to: When successful delivery of the message is confirmed, the connection failure report information from the UE variables and UE variable lists is discarded, Wherein, in the case where the timer corresponds to the connection establishment process, the timer is T310, and In the case where the timer corresponds to the connection recovery process, the timer is T319.
Citation Information
Cited By
Wireless link failure data transmission method and device, and storage medium
CN121463048A
A method, device and storage medium for transmitting wireless link failure data
CN121463048B
