WO2024056026A1

WO2024056026A1 - Mobility information reporting method and user equipment

Info

Publication number: WO2024056026A1
Application number: PCT/CN2023/118806
Authority: WO
Inventors: 常宁娟; 刘仁茂
Original assignee: 夏普株式会社; 常宁娟
Priority date: 2022-09-14
Filing date: 2023-09-14
Publication date: 2024-03-21
Also published as: CN117750446A

Abstract

Provided in the present disclosure are a mobility information reporting method and a user equipment. The mobility information reporting method comprises: during a primary secondary cell (PSCell) release or a PSCell change, a user equipment (UE) in dual connectivity creating an entry, i.e., the most recent entry, in an information element visitedPSCellInfoList in a variable VarMobilityHistoryReport; and when it is determined that secondary cell group (SCG) failure occurs in the UE before the PSCell release or the PSCell change, the UE deleting the next most recent entry prior to the most recent entry, which is created in the information element visitedPSCellInfoList.

Description

Mobile Information Reporting Methods and User Equipment

Technical field

The present disclosure relates to the field of wireless communication technology, and more specifically, the present disclosure relates to a mobile information reporting method and corresponding user equipment in a dual connectivity (Dual Connectivity, DC) scenario.

Background technique

In wireless networks, network performance can be optimized through network optimization. Generally, data collection and data analysis are performed on existing deployed and running networks to find out the reasons that affect network quality, and network performance is improved by modifying configured network parameters, adjusting network structure and deployed equipment. For Self-configuration and Self-Optimization Network (SON), it refers to the process of automatically adjusting the network based on measurements/performance measurements of user equipment and/or base stations. The network side can configure the UE to perform measurements for SON. The SON function includes many aspects, such as the Automatic Neighbor Relation Function (ANR, Automatic Neighbor Relation Function) used to reduce the operator's neighbor cell management burden, and the Mobility Load Balancing function (MLB, Mobility Load) used to balance the responsibilities between different cells. Balancing), mobile robustness optimization function (MRO, Mobility Robustness Optimization) to optimize mobile performance, random access channel optimization function to optimize random access channel parameters and wireless link failure to optimize coverage and MRO Reporting functions, etc.

The mobile information reporting mechanism has been enhanced in the NR system of version 17 of the 3rd Generation Partnership Project (3GPP), and a mobile information reporting mechanism based on primary and secondary cell (Primary Secondary Cell, PSCell) changes has been introduced.

The purpose of this disclosure is to implement a mobility information reporting mechanism based on PSCell changes in the NR system, and further, how the UE records mobility information when a secondary cell group link fails in a dual connectivity (Dual Connectivity, DC) scenario. Propose solutions to the problem.

Contents of the invention

The purpose of the embodiments of the present disclosure is to implement a mobile information reporting mechanism based on PSCell changes in the version 17 NR system. Furthermore, a solution is proposed for the problem of how the UE records PSCell-related mobility information when the secondary cell group link fails in the DC scenario. Embodiments of the present disclosure provide a mobile information reporting method executed in user equipment and corresponding user equipment.

According to the first aspect of the present disclosure, a mobility information reporting method is proposed, including: when the user equipment UE in dual connectivity releases or changes the primary and secondary cell PSCell, create an entry in the visitedPSCellInfoList information element in the variable VarMobilityHistoryReport, that is, The latest entry; when the UE determines that the secondary cell group SCG failed before PSCell release or PSCell change, the UE deletes the next new entry before the latest entry created in the visitedPSCellInfoList information element.

In the mobility information reporting method of the first aspect, preferably, the latest entry may include the identification of the previous PSCell and the time elapsed in the previous PSCell when connected to the current primary cell PCell.

In the mobility information reporting method of the above first aspect, preferably, the UE creates the second new entry in the visitedPSCellInfoList information element when the SCG fails.

In the mobility information reporting method of the above first aspect, preferably, when the UE determines that the PSCell in the latest entry and the PSCell in the next newer entry are the same cell, the UE will Entry deleted.

In the mobile information reporting method of the first aspect, preferably, the identity of the PSCell is a global cell identity GCI, or a combination of a physical cell identity PCI and a carrier frequency.

According to the second aspect of the present disclosure, a mobility information reporting method is proposed, including: when the user equipment UE in dual connectivity releases or changes the primary and secondary cells PSCell, create an entry in the visitedPSCellInfoList information element in the variable VarMobilityHistoryReport, that is, The latest entry; the UE determines that the PSCell is released or If the secondary cell group SCG fails before the PSCell is changed, the latest entry includes the time elapsed since the SCG failed when connecting to the current primary cell PCell.

In the mobile information reporting method of the second aspect, preferably, the latest entry contains the identification of the previous PSCell.

In the mobility information reporting method of the second aspect above, preferably, the UE creates a new entry in the visitedPSCellInfoList information element when the SCG fails, and the UE determines that the PSCell in the latest entry is the same as the second entry. If the PSCell in the new entry is the same cell, the latest entry includes the time elapsed since the SCG failed when connecting to the current primary cell PCell.

In the mobile information reporting method of the second aspect, preferably, the latest entry does not contain any PSCell identifier.

According to a third aspect of the present disclosure, a user equipment UE is proposed, including: a processor; and a memory storing instructions; wherein the instructions, when executed by the processor, perform the movement information reporting according to the context method.

Invention effect

According to the present invention, a mobility information reporting method executed in user equipment and corresponding user equipment are provided, so that in the case of failure involving a secondary cell group, the UE can record more accurate PSCell-based mobility information. When the UE reports mobility information to the network side, it can avoid the network side from making inappropriate mobility decisions due to inaccurate mobility information of the PSCell obtained, such as incorrect estimation of the UE's mobility speed or selecting a mobile speed for the UE. Wrong target PSCell. Therefore, while reducing the signaling overhead of UE mobility information reporting, it also avoids problems caused by the network side incorrectly analyzing repeated MHIs for the current cell.

Description of drawings

For a more complete understanding of the present disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a schematic diagram showing the recording method of PSCell movement history information in the existing mechanism.

FIG. 2 is a schematic diagram showing the mobility information reporting method (ie, the PSCell mobility history information recording method) implemented on the UE in Embodiment 1.

FIG. 3 is a schematic diagram showing the mobility information reporting method implemented on the UE (ie, the PSCell mobility history information recording method) in Embodiment 2.

FIG. 4 is a block diagram showing user equipment UE according to the present invention.

In the drawings, the same or similar structures are identified with the same or similar reference signs.

Detailed ways

Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description of exemplary embodiments of the disclosure, taken in conjunction with the annexed drawings.

In this disclosure, the terms "include" and "contain" and their derivatives mean inclusion and not limitation; the term "or" is inclusive, meaning and/or.

In this specification, the various embodiments described below to describe the principles of the disclosure are illustrative only and should not be construed in any way to limit the scope of the disclosure. The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of exemplary embodiments of the present disclosure as defined by the claims and their equivalents. The following description includes various specific details to aid understanding, but these details should be considered exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the disclosure. Additionally, descriptions of well-known functions and constructions are omitted for the sake of clarity and conciseness. Additionally, throughout the drawings, the same reference numerals are used for similar functions and operations.

The following uses the Long Term Evolution (LTE)/NR mobile communication system and its subsequent evolved versions as an example application environment to specifically describe multiple embodiments according to the present disclosure. However, it should be noted that the present disclosure is not limited to the following embodiments, but may be applicable to more other wireless communication systems. If there is no special explanation, in this disclosure, the concepts of cell and base station can be interchanged; the LTE system is also used to refer to 5G and subsequent LTE systems (such as called eLTE systems, or LTE systems that can be connected to the 5G core network). ), while LTE can use Evolved Universal Terrestrial Radio Access (E-UTRA) or Evolved Universal Terrestrial Radio Access network E-UTRAN to replace. PSCell change refers to the change of the primary and secondary cells. The source PSCell and the target PSCell can be the same cell or different cells. The source PSCell can also be called the source secondary base station, source secondary cell group (SCG), source beam (beam), source transmission point (Transmission point, TRP) or source cell; the target PSCell can also be called the target secondary cell. Base station, target beam, target transmission point, target secondary cell group SCG or target cell. The PSCell change command is used to trigger the UE to perform PSCell change. In the NR system, it is an RRC reconfiguration message containing the synchronous reconfiguration (Reconfigurationwithsync) information element for the SCG. Therefore, PSCell change may also be called synchronous reconfiguration of SCG or synchronous reconfiguration of PSCell. In the present disclosure, the RRC inactive state may also correspond to the RRC idle state in which the RRC connection in the LTE system is suspended. Cancel, Release, Delete, Empty and Clear can be replaced. Execution, use and application are interchangeable. Configuration and reconfiguration can be replaced. Links and connections can be replaced. Monitor and detect are interchangeable.

The following briefly describes the prior art involved in the embodiments of the present disclosure.

Secondary cell group SCG and PSCell under DC

In the DC scenario, the UE can obtain wireless resources through two base stations at the same time. One of them is the master base station (Master Node, MN), which is the base station for the UE to maintain the RRC connection and access through the initial access process or handover process; the other is called the secondary base station (Secondary Node, SN), which can be the base station for the UE. Provide additional wireless resources. For a UE, the MN can contain one or more serving cells, called the Master Cell Group (MCG), which contains a primary cell (PCell); the SN can also contain one or more serving cells, called the secondary cell. Secondary Cell Group (SCG), which contains a primary and secondary cell group cell/or primary and secondary cell PSCell. PCell and PSCell can also be collectively referred to as special cells spCell. In this disclosure, SN, SCG, and PSCell can be replaced, and MN, MCG, and PCell can be replaced. Unless otherwise specified, SN add/change/release, SCG add/change/release, MR-DC add/change/release, and PSCell add/change/release can be replaced.

SCG failed

When the UE meets one or more of the following conditions, if neither MCG nor SCG transmission is suspended at this time, the UE will initiate the SCG failure information process to report the SCG failure to the network side: the wireless link of the SCG is monitored (Radio Link Failure, RLF), PSCell beam failure detected when SCG is deactivated, SCG synchronization reconfiguration failure, SCG configuration failure and integrity check failure indication associated with SRB3 received from the bottom layer, etc. During the SCG failure process, the UE usually suspends SCG transmission, resets the SCG MAC entity, stops the running timer T304, and sends the SCGFailureInformation RRC message to the network side through the MCG link. When receiving SCGFailureInformation, as a response to SCGFailureInformation, according to the content in SCGFailureInformation, MCG can send an RRC message containing the synchronous reconfiguration of SCG to the UE, trigger the change of PSCell, and access the target PSCell to restore the SCG link; or to The UE sends an RRC message containing a release SCG link indication to release the SCG. However, the network side's response is not necessary, that is, the network side does not need to respond to the SCGFailureInformation message sent by the UE.

Mobility information reporting mechanism in version 16 NR system:

In the NR system of version 16, the UE records mobility history information (Mobility History Information, MHI) based on PCell. In this disclosure, mobility history information is also referred to as mobility information or mobility history report. The MHI records the change information of the serving cell/primary cell (Primary Cell, PCell) experienced by the UE. By obtaining the MHI of the UE, the network side can learn the movement trajectory of the UE and determine the movement speed of the UE to a certain extent. When deciding the mobility operations of the UE, such as the configuration of handover parameters and the selection of the handover target cell, the network side can combine the obtained information to perform more optimized configurations, thereby ensuring the mobility performance of the UE.

When a UE in the RRC idle state and RRC connected state changes the serving cell/primary cell, an entry is added to the UE variable VarMobilityHistoryReport. An entry can contain a visitedCellId information element and a timeSpent information element. The cell identity of the previous serving cell/PCell (global cell identity or physical cell identity and carrier frequency of the cell) is recorded in the visitedCellId information element, and the timeSpent information element records Time spent/staying in the neighborhood. When the UE enters E-UTRA/NR, if it was previously out of service or used other access technology (Radio Access Technology, RAT), the UE will also add an entry to the variable VarMobilityHistoryReport, in the timeSpent information element. Record the time when the UE is in no network state. The non-network state here includes out of service state or using other RATs. In the NR system, when the UE enters the normal camped state (camped normally state) or E-UTRA, if it was previously in the "any cell selection" or "camped on any cell" state of LTE or NR, the UE is in the variable VarMobilityHistoryReport Add an entry and set the timeSpent element to the time spent in the "any cell selection" or "camped on any cell" state of LTE or NR. The 3GPP protocol defines the maximum number of MHI entries saved by the UE, such as 16. When the UE performs the above operation of adding a new entry, if the number of saved entries has reached the maximum value, the UE will not add a new entry before adding a new entry. , delete the oldest entry among the saved MHI entries.

For a UE in the RRC connected state, if the UE supports saving MHI and there is an available MHI in the VarMobilityHistoryReport variable, the UE will include a username in the uplink RRC message (such as RRC connection establishment completed, RRC connection recovery completed, RRC link reconfiguration completed). To inform the base station that it has an indication of the saved MHI (mobilityHistoryAvail information element), set the value of this information element to TRUE. The UE reports the saved MHI to the base station in the subsequent UE information process. Specifically, the base station requests the UE to report the saved MHI by carrying the mobilityHistoryReportReq information element set to TRUE in the UEInformationRequest message, and the UE includes the relevant mobility history information in the mobilityHistoryReport information element in the response UEInformationResponse message and reports it to the base station. When generating the mobilityHistoryReport information element in the UEInformationResponse message, in addition to including all entries related to the historical cells in the saved UE variable VarMobilityHistoryReport in the mobilityHistoryReport information element, the UE will also create a new entry in the information element to record the current community information, that is, set this item The purpose visitedCellId information element is the cell identification of the current cell and the timeSpent information element is set to the time elapsed in the current cell.

Mobility information reporting mechanism in version 17 NR system:

The cell information described in the mobility information reporting mechanism of version 16 is for PCell. In the DC scenario, in addition to PCell mobility, the UE also performs PSCell mobility. In the existing MHI mechanism, the SN cannot obtain the MHI of the PCell/serving cell; secondly, considering the different network deployment situations of the MN and the SN (for example, in the EN-DC scenario, the MN and the SN are different RATs), even if the SN The MHI of the PCell/serving cell can be obtained from the MN. Because the SN lacks network deployment information about the relevant PCell/serving cell, such as the cell range size, the SN may not be able to obtain helpful information from the MHI. Taking into account the above reasons, the version 17 NR system introduces the MHI for the PSCell recorded by the UE in the RRC connection state. The MHI can be reported to the MN for parameter optimization when the PSCell is added/changed triggered by the MN, or Reported to SN through MN for PSCell selection or parameter optimization when PSCell changes triggered by SN. In the existing MHI mechanism, the records of PCell and PSCell are associated in a nested structure and stored in the same UE variable VarMobilityHistoryReport. The UE variable VarMobilityHistoryReport of version 17 contains the visitedCellInfoList information element and visitedPSCellInfoList information element. Each entry in the visitedCellInfoList information element records the time that the UE has experienced in a PCell and the identity of this cell. It also records the information of one or more PSCells that the UE has recently experienced when connected to this PCell (in the form of visitedPSCellInfoListReport information element). logo). The visitedPSCellInfoList information element records the information of one or more PCells recently experienced when connecting to the current PCell. Similar to PCell mobility information, the PSCell identifier in a PSCell entry does not necessarily exist. At this time, the entry records a period of time when the UE is in a PSCell-free state.

For UEs that support the PSCell mobility history information mechanism, in PSCell mobility that does not involve PCell changes, when a PSCell is added, an entry is created in the visitedPSCellInfoList information element in the variable VarMobilityHistoryReport. If the entry is not the first entry for the PCell since the UE entered the current PCell PSCell entry, then the UE contains the timeSpent information element in this entry, which is used to record the PSCell-free time experienced after the UE enters the current PCell and is released from the latest PSCell or after SCG failure. When connected to the current PCell, the UE creates an entry in the visitedPSCellInfoList information element in the variable VarMobilityHistoryReport when at least one of the PSCell is released, the PSCell is changed, or when the PSCell detects a failure. The UE includes the cell identity of the previous PSCell in this entry and sets the timeSpent field to the time that the UE has experienced in this PSCell.

As mentioned before, the SCG failure scenario is considered in the PSCell mobility history information mechanism of version 17. For example, when an SCG failure occurs, the UE creates an entry in the VarMobilityHistoryReport variable to record the time experienced in the previous PSCell. Based on the recording method of PSCell movement history information in the existing mechanism, consider the following scenario. Figure 1 is a schematic diagram showing the recording method of PSCell movement history information in the existing mechanism. As shown in Figure 1, the UE is connected to the current cell PCell X. At time point T1, the UE is configured with PSCell A, that is, the UE executes Addition of PSCell. At time point T2, an SCG failure occurs. The UE initiates the SCGFailureInformation process, suspends SCG transmission and sends an SCGFailureInformation message to the network side to report the failure. At this time, according to the existing mobility history information mechanism, the UE creates/includes an entry in the visitedPSCellInfoList information element in the variable VarMobilityHistoryReport to record the identity of PSCell A before the SCG failed and the time T2-T1 experienced in PSCell A. , recorded here as entry 1. At time T3, the UE receives the RRC reconfiguration message from the network side in response to SCGFailureInformation. The message instructs the UE to perform PSCell change to PSCell B or instructs the UE to perform PSCell release to release the SCG. At this time, according to the existing mobility history information mechanism, the UE creates/includes an entry in the visitedPSCellInfoList information element in the variable VarMobilityHistoryReport to record the identity of PSCell A and the time spent in PSCell A before the PSCell was changed or released. T3-T1, here recorded as entry 2. It can be seen that entry 1 and entry 2 in the variable VarMobilityHistoryReport twice record the two periods of time when the UE was in PSCell A, and these two periods are not continuous, but overlap. of. If the UE reports the above recorded mobility information to the network side, there is a possibility that the network side will mistakenly believe that the time experienced by the UE in PSCell A is (T3-T1) + (T2-T1), that is, entries 1 and The sum of time in item 2 makes it possible for the network side to fail to make an optimal judgment on the UE's mobility, thus affecting the network's future mobility performance settings and related decisions for the UE. Generally speaking, the information recorded in accurate movement history information should be continuous and non-overlapping in time order. Therefore, the present disclosure focuses on the problems existing in the above scenarios and proposes the following solutions so that the UE can provide accurate movement history information to the network side even in the scenario where SCG failure occurs.

To address the above problems, the present disclosure describes the following embodiments as examples. All the described embodiments are only examples and do not limit the present disclosure.

Example 1

This embodiment provides a method for recording PSCell movement history information implemented on the UE. In this embodiment, when the aforementioned scenario occurs, the UE deletes the aforementioned entry 1 saved thereon, so that the PSCell movement information recorded by the UE is accurate.

FIG. 2 is a schematic diagram showing the mobility information reporting method implemented on the UE (ie, the PSCell mobility history information recording method) in Embodiment 1.

As shown in Figure 2, when the PSCell is released or the PSCell is changed, the UE performs the following operations:

Operation 101: Create an entry (denoted as entry 2, also called the latest entry) in the visitedPSCellInfoList information element in the variable VarMobilityHistoryReport. In this entry, the UE contains the identification of the previous PSCell (previous PSCell) and sets the timeSpent information element to the time elapsed in the previous PSCell when it is connected to the current PCell.

Operation 102: Determine whether an SCG failure has just been experienced before PSCell release or PSCell change. If so, the UE deletes an entry 1 before entry 2 created in operation 101 in the visitedPSCellInfoList information element. Determining whether an SCG failure has just been experienced before PSCell release or PSCell change can be expressed as the second latest entry in the visitedPSCellInfoList information element (i.e. entry 1, also known as sub-new entry) was created when the SCG failed (that is, the event that triggered the creation of the entry was the SCG failure). If so, the second latest entry is deleted. Optionally, in addition to determining that the second latest entry in the visitedPSCellInfoList information element was created when the SCG failed, the UE further determines whether the PSCell in the second latest entry (entry 1) and the latest entry (entry 2) are the same. A cell; if so, delete the second latest entry. The determination of whether the PSCell is the same cell may be based on whether the PSCell identifiers are the same.

The PSCell release can be performed by the UE after receiving the RRC message containing the PSCell release indication, or it can be performed by the UE itself, such as the UE performing SCG release by itself during the RRC re-establishment process. The PSCell change can be performed by the UE after receiving the RRC message containing the synchronized reconfiguration information element for SCG, or it can be that the UE performs conditional reconfiguration for SCG, that is, a conditional PSCell Change (Conditional PSCell Change) is performed. , CPC).

The identity of the PSCell may be a Global Cell Identity (GCI), or a combination of a Physical Cell Identity (PCI) and a carrier frequency.

As mentioned above, the SCG failure may be one or more of the following: SCG RLF, PSCell beam failure detected when the SCG is deactivated, SCG synchronization reconfiguration failure, SCG (re)configuration failure, and Received the integrity check failure indication related to SRB3 from the bottom layer, etc.

Obviously, before the above-mentioned UE performs PSCell release or PSCell change, it also includes that the UE monitors the SCG failure and creates entry 1 in the PSCell movement history information when the SCG fails, which contains the identification of the PSCell before the SCG failure. and the time elapsed in this PSCell.

Example 2

This embodiment provides another method for recording PSCell movement history information implemented on the UE. In this embodiment, when the foregoing scenario occurs, the UE sets the time information in entry 2 in the foregoing scenario to the time elapsed since the SCG failure, so that the UE The time information recorded and reported in Entry 1 and Entry 2 does not overlap, ensuring its accuracy.

As shown in Figure 3, when the PSCell is released or the PSCell is changed, the UE creates an entry (denoted as entry 2, also called the latest entry) in the visitedPSCellInfoList information element in the variable VarMobilityHistoryReport. Set this entry as follows:

Operation 201: Contain the identification of the previous PSCell.

Operation 202: Determine whether an SCG failure has just been experienced before the PSCell is released or the PSCell is changed. If so, set the timeSpent information element to the time elapsed since the SCG failure when connecting to the current PCell. Determining whether an SCG failure has just occurred before PSCell release or PSCell change can be expressed as whether the second latest entry (i.e., entry l, also called the second latest entry) in the visitedPSCellInfoList information element was created when SCG failed (i.e., triggered The event that created this entry was SCG failure). If so, set the timeSpent information element to the time elapsed since the SCG failed when connecting to the current PCell. Optionally, in addition to determining that the second latest entry in the visitedPSCellInfoList information element was created when the SCG failed, the UE further determines whether the PSCell in the second latest entry (entry 1) and the latest entry (entry 2) are the same. A cell; if so, set the timeSpent information element to the time elapsed since the SCG failed when connecting to the current PCell. The determination of whether the PSCell is the same cell may be based on whether the PSCell identifiers are the same.

The PSCell release can be performed by the UE after receiving the RRC message containing the PSCell release indication, or it can be performed by the UE itself, such as the UE performing SCG release by itself during the RRC re-establishment process. The PSCell change may be performed by the UE after receiving the RRC message containing the synchronized reconfiguration information element for SCG, or the UE may perform conditional reconfiguration for SCG, that is, perform a conditional PSCell Change (Conditional PSCell Change). , CPC).

Example 3

This embodiment provides yet another method for recording PSCell movement history information implemented on the UE. In this embodiment, when the foregoing scenario occurs, the UE sets the time information in entry 2 in the foregoing scenario to the time elapsed since the SCG failed when connecting to the current PCell, but this entry does not contain any PSCell identifier. (with no PSCell), so that the time information in entry 1 and entry 2 recorded and reported by the UE does not overlap, and the time elapsed after the SCG failure is considered to be the no PSCell time.

When the PSCell is released or the PSCell is changed, the UE creates an entry (denoted as entry 2, also called the latest entry) in the visitedPSCellInfoList information element in the variable VarMobilityHistoryReport. Set this entry as follows: determine whether an SCG failure has just been experienced before PSCell release or PSCell change. If so, set the timeSpent information element to the PSCell-free time experienced since the SCG failure when connecting to the current PCell. Determining whether an SCG failure has just occurred before PSCell release or PSCell change can be expressed as whether the second latest entry in the visitedPSCellInfoList information element (i.e. entry 1, also called the second latest entry) was created when SCG failed (i.e. triggered The event that created the entry is SCG failure). If so, set the timeSpent information element to the PSCell-free time elapsed since the SCG failed when connecting to the current PCell.

Example 4

This embodiment describes the user equipment UE of the present disclosure. FIG. 4 is a block diagram showing user equipment UE according to the present invention. As shown in Figure 4, the user equipment UE40 includes a processor 401 and a memory 402. The processor 401 may include, for example, a microprocessor, a microcontroller, an embedded processor, or the like. The memory 402 may include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory. Memory 402 stores program instructions. When executed by the processor 401, this instruction can execute various methods such as the above-mentioned movement information reporting method described in detail in the present invention.

In this disclosure, some different embodiments may work together, and unless otherwise specified, the concepts or definitions between the embodiments may be common.

In this disclosure, "base station" refers to a mobile communication data and control switching center with larger transmission power and wider coverage area, including functions such as resource allocation and scheduling, data reception and transmission. "User equipment" refers to user mobile terminals, including mobile phones, notebooks and other terminal equipment that can wirelessly communicate with base stations or micro base stations.

The method and related equipment of the present disclosure have been described above in conjunction with preferred embodiments. Those skilled in the art will understand that the methods shown above are only exemplary. The method of the present disclosure is not limited to the steps and sequence shown above. The base station and user equipment shown above may include more modules, for example, may also include modules that may be developed or developed in the future and may be used for the base station, MME, or UE, and so on. The various identifications shown above are only illustrative and not restrictive, and the present disclosure is not limited to the specific information elements as examples of these identifications. Many changes and modifications may be made by those skilled in the art in light of the teachings of the illustrated embodiments.

The program running on the device according to the present disclosure may be a program that causes the computer to implement the functions of the embodiments of the present disclosure by controlling a central processing unit (CPU). The program or information processed by the program may be temporarily stored in volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems.

Programs for realizing the functions of each embodiment of the present disclosure may be recorded on a computer-readable recording medium. Corresponding functions can be realized by causing the computer system to read programs recorded on the recording medium and execute these programs. The so-called "computer system" here may be a computer system embedded in the device, which may include an operating system or hardware (such as peripheral devices). The "computer-readable recording medium" may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a short-term dynamic storage program recording medium, or any other recording medium readable by a computer.

Various features or functional modules of the devices used in the above-described embodiments may be implemented or performed by circuits (eg, single-chip or multi-chip integrated circuits). Circuitry designed to perform the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), a special purpose processor ASIC, field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination of the foregoing. A general-purpose processor can be a microprocessor or any existing processor, controller, microcontroller, or state machine. The above circuit may be a digital circuit or an analog circuit. When new integrated circuit technologies emerge to replace existing integrated circuits due to advances in semiconductor technology, one or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies.

Furthermore, the present disclosure is not limited to the above-described embodiment. Although various examples of the embodiments have been described, the disclosure is not limited thereto. Fixed or non-mobile electronic equipment installed indoors or outdoors can be used as terminal equipment or communication equipment, such as AV equipment, kitchen equipment, cleaning equipment, air conditioners, office equipment, vending machines, and other household appliances.

As above, the embodiments of the present disclosure have been described in detail with reference to the accompanying drawings. However, the specific structure is not limited to the above-described embodiment, and the present disclosure also includes any design changes that do not deviate from the gist of the present disclosure. In addition, various modifications can be made to the present disclosure within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present disclosure. Furthermore, components having the same effect described in the above embodiments may be substituted for each other.

Claims

A mobile information reporting method including:

When the user equipment UE in dual connectivity is released or the PSCell is changed in the primary and secondary cells, an entry is created in the visitedPSCellInfoList information element in the variable VarMobilityHistoryReport, which is the latest entry;

When the UE determines that the secondary cell group SCG failed before PSCell release or PSCell change, the UE deletes the next new entry before the latest entry created in the visitedPSCellInfoList information element.
The mobile information reporting method according to claim 1, wherein,

The latest entry includes the identification of the previous PSCell and the time elapsed in the previous PSCell when connecting to the current primary cell PCell.
The mobile information reporting method according to claim 1 or 2, wherein,

The UE creates the new entry in the visitedPSCellInfoList information element when SCG fails.
The mobile information reporting method according to claim 1 or 2, wherein,

When the UE determines that the PSCell in the latest entry and the PSCell in the next new entry are the same cell, the UE deletes the next new entry.
The mobile information reporting method according to claim 1 or 2, wherein,

The identity of the PSCell is a global cell identity GCI, or a combination of a physical cell identity PCI and a carrier frequency.
A mobile information reporting method including:

When the user equipment UE in dual connectivity is released or the PSCell is changed in the primary and secondary cells, an entry is created in the visitedPSCellInfoList information element in the variable VarMobilityHistoryReport, which is the latest entry;

When the UE determines that it has experienced a secondary cell group SCG failure before PSCell release or PSCell change, the latest entry includes the time elapsed since the SCG failure when connecting to the current primary cell PCell.
The mobile information reporting method according to claim 6, wherein,

The latest entry contains the identification of the previous PSCell.
The mobile information reporting method according to claim 6 or 7, wherein,

The UE created a new entry in the visitedPSCellInfoList information element when the SCG failed,

When the UE determines that the PSCell in the latest entry and the PSCell in the next new entry are the same cell, when the latest entry contains PCell connected to the current primary cell, it starts from the failure of the SCG time experienced.
The mobile information reporting method according to claim 6, wherein,

The latest entry does not contain any PSCell identifier.
A user device including:

processor; and

A memory on which instructions are stored;

Wherein, the instruction, when executed by the processor, causes the user equipment to execute the mobile information reporting method according to any one of claims 1-9.