Mobile Information Reporting Method and User Equipment

By recording and reporting PSCell's mobile information in the UE, the problem that UE cannot effectively report PSCell's mobile information in the DC scenario is solved, and the network performance optimization capability is improved.

CN114630375BActive Publication Date: 2025-07-08SHARP KK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011435617.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-10
Publication Date
2025-07-08
Estimated Expiration
2040-12-10

AI Technical Summary

Technical Problem

In the dual connection (DC) scenario, the prior art cannot effectively record and report the mobile information of the primary and secondary cell group cells (PSCell) of the user equipment (UE), resulting in the network side being unable to optimize the mobile performance.

Method used

Implementing a mobile information recording and reporting method in a user equipment (UE), including saving and updating the S-MHI in the RRC inactive state and the RRC idle state, recording the mobile information of the PSCell, and reporting it to the network side when appropriate.

Benefits of technology

By recording and reporting PSCell's mobile information, the network side can better optimize mobility operations and improve network performance and user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114630375B_ABST
    Figure CN114630375B_ABST
Patent Text Reader

Abstract

The present disclosure provides a mobile information reporting method and a user equipment. The mobile information reporting method includes: a user equipment (UE) enters the RRC connected state from the RRC inactive state through an RRC connection resume procedure, or enters the RRC connected state from the RRC idle state through an RRC connection establishment procedure; and the UE stores mobile history information based on a primary secondary cell (PSCell), i.e., S-MHI, where the S-MHI includes the time experienced by the UE in the RRC inactive state or the RRC idle state before entering the RRC connected state.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of wireless communication technologies. More specifically, the present disclosure relates to a method for reporting mobile information in a Dual Connectivity (DC) scenario and a corresponding user equipment. Background Art

[0002] In a wireless network, network performance can be optimized through network optimization. Generally, data collection and data analysis are performed on an existing deployed and operating network to find out the reasons affecting network quality, and network performance is improved by modifying configured network parameters, adjusting network structure and deployed devices, etc. For a Self-configuration and Self-Optimization Network (SON), it refers to a process of automatically adjusting a 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 an Automatic Neighbour Relation Function (ANR) for reducing the operator's neighbour cell management burden, a Mobility Load Balancing (MLB) function for balancing the mobile load among different cells, a Mobility Robustness Optimization (MRO) function for optimizing mobile performance, a Random Access Channel Optimization function for optimizing random access channel parameters, and a Radio Link Failure Reporting function for optimizing coverage and MRO.

[0003] In April 2019, a new research project on a 5G technology standard was approved at the 86th plenary session of the 3rd Generation Partnership Project (3GPP) RAN (see non-patent literature: RP-193255: New WID on enhancement of data collection for SON / MDT in NR). One of its research purposes is to enhance the mobile information reporting mechanism in the NR system of Release 16.

[0004] The purpose of the present disclosure is to implement an enhanced mobile information reporting mechanism in the NR system. Further, a solution is proposed for the problem of how a UE records mobile information in a DC scenario. Summary of the Invention

[0005] The purpose of the embodiments of the present disclosure is to implement an enhanced mobility information reporting mechanism in the NR system of Release 16. Further, a solution is proposed for the problem of how a UE records mobility information about a Primary Secondary CellGroup Cell (PSCell) in a DC scenario. The embodiments of the present disclosure provide a method for recording and reporting mobility information executed in a user equipment and the corresponding user equipment.

[0006] According to a first aspect of the present disclosure, a method for reporting mobility information is provided, including: a user equipment UE enters the RRC connected state from the RRC inactive state through an RRC connection resume procedure, or enters the RRC connected state from the RRC idle state through an RRC connection establishment procedure; and the UE stores mobility history information based on a Primary Secondary Cell (PSCell), i.e., S-MHI, where the S-MHI includes the time the UE has experienced in the RRC inactive state or the RRC idle state before entering the RRC connected state.

[0007] In the method for reporting mobility information in the first aspect above, the UE may add an entry to a UE variable for storing the S-MHI, and record the S-MHI through the entry.

[0008] In the method for reporting mobility information in the first aspect above, the S-MHI may include: the time the UE has experienced in the RRC inactive state or the RRC idle state between the release of the previous RRC connection and the entry into the RRC connected state this time.

[0009] In the method for reporting mobility information in the first aspect above, in the case where the UE performs an operation of entering the RRC inactive state from the RRC connected state, the UE records the S-MHI so that the S-MHI includes: the cell identifier of the current PSCell and the time experienced in this PSCell.

[0010] In the method for reporting mobility information in the first aspect above, when a successful PSCell change occurs, the UE records the S-MHI so that the S-MHI includes: the mobility information of the source PSCell at the time of PSCell change, i.e., the cell identifier of the source PSCell and the time experienced in this PSCell.

[0011] In the method for reporting mobility information in the first aspect above, when the UE receives an RRC resume message, if the RRC resume message does not include a restoreSCG information element, the UE records the S-MHI so that the S-MHI includes: the cell identifier of the previous PSCell and the time experienced in this PSCell.

[0012] In the mobile information reporting method of the first aspect above, in the case where the change of the PSCell is the first PSCell change since the UE entered the RRC connected state through the RRC resume procedure, the time may be the time experienced by the UE on the previous PSCell since the RRC connection of the UE was resumed.

[0013] In the mobile information reporting method of the first aspect above, when the UE successfully adds a PSCell, the UE may record the S-MHI such that the S-MHI includes: the time the UE experienced in the state without SCG / PSCell configuration before the PSCell addition.

[0014] In the mobile information reporting method of the first aspect above, when the UE supports saving the S-MHI, the UE may record the S-MHI.

[0015] According to a second aspect of the present disclosure, there is provided a user equipment, including: a processor; and a memory storing instructions; wherein, the instructions, when run by the processor, execute the mobile information reporting method according to the context. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] To more fully understand the present disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which:

[0017] Figure 1 is a flowchart showing the mobile information reporting method in Embodiment 1 of the present invention.

[0018] Figure 2 is a flowchart showing the mobile information reporting method in Embodiment 2 of the present invention.

[0019] Figure 3 is a block diagram showing the user equipment UE involved in the present invention.

[0020] In the drawings, the same or similar structures are identified with the same or similar reference numerals. DETAILED DESCRIPTION

[0021] From the following detailed description of the exemplary embodiments of the present disclosure in conjunction with the accompanying drawings, other aspects, advantages and prominent features of the present disclosure will become apparent to those skilled in the art.

[0022] In the present disclosure, the terms "include" and "comprise" and their derivatives are intended to be inclusive and not limiting; the term "or" is inclusive and means and / or.

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

[0024] The following takes the Long Term Evolution (LTE) / NR mobile communication system and its subsequent evolved versions as an example application environment, and specifically describes multiple embodiments according to the present disclosure. However, it should be noted that the present disclosure is not limited to the following embodiments, but is applicable to more other wireless communication systems. Unless otherwise specified, in the present disclosure, the concepts of cell and base station can be replaced with each other; the LTE system is also used to refer to the LTE system after 5G (such as the so-called eLTE system, or the LTE system that can be connected to the 5G core network), and at the same time, LTE can be replaced with Evolved Universal Terrestrial Radio Access (E-UTRA) or Evolved Universal Terrestrial Radio Access Network E-UTRAN. In the present disclosure, the RRC inactive state can 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. Execute, use, and apply can be replaced. Configure and reconfigure can be replaced. Link and connection can be replaced. Monitor and detect can be replaced.

[0025] The following briefly describes the prior art related to the embodiments of the present disclosure.

[0026] Secondary Cell Group SCG and PSCell under DC

[0027] In the DC scenario, the UE can obtain radio resources through two base stations simultaneously. One is the master base station (Master Node, MN), which is the base station to which the UE maintains the RRC connection and is the base station accessed through the initial access process or the handover process; the other is called the secondary base station (Secondary Node, SN), which can provide additional radio resources for the UE. For a UE, the MN can include one or more serving cells, called the Master Cell Group (MCG), which includes a primary cell (PCell); the SN can also include one or more serving cells, called the Secondary Cell Group (SCG), which includes a primary and secondary cell group cell / or a primary and secondary cell PSCell. The PCell and the PSCell can be collectively referred to as the special cell spCell. In this disclosure, the SN and the SCG can be replaced, and the MN and the MCG can be replaced. The addition / change / release of the SN, the addition / change / release of the SCG, the addition / change / release of the MR-DC, and the addition / change / release of the PSCell can be replaced to a certain extent.

[0028] SCG Configuration Handling during RRC Resume Process

[0029] In the current NR / LTE system, when the UE enters the RRC inactive state, if it is configured with an SCG, the SCG configuration (such as the mrdc-SecondaryCellGroup configuration) is saved in the UE's non-active access stratum context. In the subsequent RRC connection resume process for resuming the RRC connection, the UE sends an RRCResume request message to the network side to request the resumption of the RRC connection. In the received response message, the RRCResume message, if it does not contain the restoreSCG indication information for indicating the resumption of the saved SCG configuration, the UE releases the corresponding multi-radio dual connectivity (MR-DC) related configuration, that is, the SCG configuration, from the saved UE non-active access stratum context; otherwise, the UE resumes the saved SCG configuration from the UE non-active access stratum context. At the same time, the RRCresume message may also include an mrdc-SecondaryCellGroup configuration, and a change of the PSCell can be performed in this SCG configuration, that is, it includes a reconfigurationWithSync information element, and the cell identifier therein is different from the cell identifier of the current PSCell. Of course, the SCG configuration can also be a reconfiguration of the current PSCell, that is, it does not include a change of the PSCell.

[0030] That is to say, during the RRC restoration process, according to the configuration of the network side, the PSCell saved by the UE can have three situations: 1: Release the entire SCG configuration including the configuration of the PSCell; 2: Reconfigure the SCG and the PSCell changes; 3: Reconfigure the SCG and the PSCell remains unchanged.

[0031] The mobility information reporting mechanism in the existing mechanism:

[0032] In the current LTE system and the NR system of Release 16, the UE records Mobility History Information (MHI), which is also simply referred to as mobility information in this disclosure. The MHI records the change information of the serving cell / primary cell (PCell) experienced by the UE. When the serving cell / primary cell changes for the UE in the RRC idle state and the RRC connected state, an entry is added to the UE variable VarMobilityHistoryReport, and the cell identity (global cell identity or physical cell identity and the carrier frequency of the cell) of the previous serving cell / PCell is recorded in the visitedCellId information element, and it also includes the time spent in the cell (identified by the timeSpent information element). In the LTE system, when the UE enters the E-UTRA, if it was previously in the out of service state or using another radio access technology (RAT), the UE also adds an entry to the variable VarMobilityHistoryReport, and records in the timeSpent information element therein the time when the UE was outside the E-UTRA. Being outside the E-UTRA here includes both the out of service state and using other RATs. In the NR system, when the UE enters the camped normally state or the E-UTRA, if it was previously in the "any cell selection" or "camped on any cell" state of LTE or NR, the UE adds an entry to the variable VarMobilityHistoryReport and sets the timeSpent element in others to the time experienced in the "any cell selection" or "camped on any cell" state of LTE or NR. The 3GPP protocol defines the maximum number of entries of the MHI saved by the UE, such as 16. When the UE performs the operation of adding a new entry as described above, if the number of saved entries has reached the maximum value, the UE deletes the oldest entry among the saved MHI entries before adding the new entry.

[0033] When the UE enters the RRC connected state through the RRC connection establishment or RRC connection restoration process, if the UE supports saving the MHI and there is available MHI in the VarMobilityHistoryReport variable, the UE includes an indication (mobilityHistoryAvail information element) in the RRC connection establishment complete message or RRC connection restoration complete message to inform the base station that it has saved MHI, and sets the value of this information element to TRUE. The UE reports the saved MHI to the base station during 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 entries of the saved MHI in the mobilityHistoryReport information element in the response UEInformationResponse message and reports them to the base station. In addition, the UE also includes an entry in the mobilityHistoryReport information element to record the current cell information, that is, sets the visitedCellId information element of this entry to the global cell identifier of the current cell and sets the timeSpent information element to the time experienced in the current cell.

[0034] In the above mechanism, by obtaining the MHI of the UE, the network side can know the movement trajectory of the UE and determine the movement speed of the UE to a certain extent. When deciding on the mobility operations of this UE, such as the configuration of handover parameters and the selection of handover target cells, the network side can make more optimized configurations by combining the obtained information, so as to ensure the mobility performance of the UE.

[0035] In the existing mechanism, the cell information is for the serving cell in the idle state or RRC inactive state or the PCell in the RRC connected state. In the DC scenario in the LTE / NR system, in addition to the mobility of the PCell, the UE simultaneously performs the mobility of the PSCell. For the change of the PSCell, the secondary node (SN) can initiate the change of the PSCell by itself without the participation of the master node (MN). First, in the existing MHI mechanism, the SN cannot obtain the MHI of the PCell / serving cell; second, 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 can obtain the MHI of the PCell / serving cell from the MN, because the SN lacks the network deployment information of the relevant PCell / serving cell, such as the cell range size, etc., the SN may not be able to obtain helpful information from the MHI. Considering the above reasons, a feasible method is to enhance the MHI, and the enhancement includes that the UE records the MHI for the SCG PSCell, and this MHI can be reported to the SN or reported to the MN for parameter optimization when the MN triggers the addition / change of the PSCell and when the SN triggers the change of the PSCell. For the convenience of description, in this disclosure, the MHI in the existing mechanism is called M-MHI, and the MHI recorded based on the change of the PSCell is called S-MHI.

[0036] This disclosure proposes a solution to the problem of how to record the S-MHI on the UE side.

[0037] Different from the PCell, the PSCell of the UE is optional and not necessarily present. In some cases, such as when the traffic volume of the UE in the RRC connected state is small, the network side can choose to release the SCG of the UE or not configure the SCG, so that the UE is in a single connection state, and at this time the UE does not have a configured PSCell. In addition, as mentioned above, when the UE enters the RRC inactive state, the UE will save its SCG configuration in the UE inactive state access stratum context. However, the UE in the RRC inactive state does not perform the mobility of the PSCell, and when the RRC connection is restored, the network side can decide whether to retain or change the PSCell. The above two situations result in the UE's experience of the PSCell being intermittent. In these cases, the existing MHI mechanism cannot be directly used to record the S-MHI.

[0038] The following are several embodiments executed on the UE in this disclosure based on the above problems.

[0039] Embodiment 1

[0040] This embodiment proposes a method for recording S-MHI when a UE enters the RRC inactive state.

[0041] Figure 1 It is a flowchart showing the mobile information reporting method in Embodiment 1 of the present invention. In Embodiment 1, as Figure 1 shown, in step S101, the UE performs an operation of entering the RRC inactive state from the RRC connected state.

[0042] When the UE performs the operation of entering the RRC inactive state from the RRC connected state, in step S102, the UE records and saves the S-MHI so that the S-MHI can include the cell identifier of the current PSCell and the time experienced in this PSCell.

[0043] As an example, for instance, when the UE performs the operation of entering the RRC inactive state, if the UE supports saving the S-MHI and the UE is configured with an SCG, the UE adds an entry in the UE variable for saving the S-MHI, and this entry is used to record the current PSCell mobility information of the UE. The entry includes the cell identifier of the current PSCell and the time experienced in this PSCell. Optionally, the entry may also include the cell identifier of the PCell corresponding to the UE when this PSCell is configured. Considering the scenario where the PSCell of the UE may not change when the PCell is switched, there may be more than one PCell corresponding to the PSCell. The cell identifier may be a global cell identifier or a physical cell identifier.

[0044] When the UE performs the operation of entering the RRC inactive state, it may occur when the UE performs an RRC release, such as the RRC release operation performed when the UE receives an RRC release message for suspending the RRC connection. Preferably, the UE being configured with an SCG means that the UE has a configured secondaryCellGroup configuration or an mrdc-secondarycellGroupConfig configuration.

[0045] Embodiment 2

[0046] This embodiment proposes a method for recording S-MHI when a UE enters the RRC connected state from the RRC inactive state through the RRC connection restoration process. It should be noted that this method is also applicable to the method for recording S-MHI when a UE enters the RRC connected state from the RRC idle state through the RRC connection establishment process. Through this embodiment, the UE also records the time experienced in the RRC inactive state or the RRC idle state in the S-MHI, thereby providing more information for mobility assessment to the base station.

[0047] Figure 2 It is a flowchart showing the mobile information reporting method in Embodiment 2 of the present invention. In Embodiment 2, as Figure 2 shown, in step S201, the UE enters the RRC connected state from the RRC inactive state through the RRC connection resume procedure, or enters the RRC connected state from the RRC idle state through the RRC connection establishment procedure.

[0048] In addition, in step 202, the UE saves the S-MHI (i.e., the mobility history information based on the primary secondary cell PSCell), and the S-MHI may include the time experienced by the UE in the RRC inactive state or the RRC idle state before entering the RRC connected state.

[0049] As an example, for instance, when the UE enters the RRC connected state, if the UE supports saving the S-MHI, the UE adds an entry in the UE variable for saving the S-MHI, and the entry is used to record the time experienced by the UE in the RRC inactive state (i.e., the time when the SCG is not used) before entering the RRC connected state. The entry includes the time experienced by the UE in the RRC inactive state between the release of the previous RRC connection and the entry into the RRC connected state this time. Optionally, the entry may further include the cell identifiers of one or more PSCs corresponding to the UE during this period. The cell identifier may be a global cell identifier or a physical cell identifier. Since the UE does not use the SCG during the above-mentioned time in the RRC inactive state, even if the UE has a saved SCG / PSCell configuration at this time, the entry does not contain any PSCell identifier.

[0050] Optionally, for an RRC inactive UE, the above operation is only performed when the UE is configured with an SCG or has a saved SCG configuration before entering the RRC connected state.

[0051] The UE enters the RRC connected state, which may mean that the UE receives an RRC resume message during the RRC resume procedure. Optionally, it means that the received RRC resume message is successfully received and applied, or it may also mean that the UE delivers the RRC resume complete message to the lower layer for transmission.

[0052] When the above method is applicable to the RRC idle state, the above RRC inactive state can be replaced by the RRC idle state. The UE enters the RRC connected state, which may mean that the UE receives an RRC establishment message during the RRC establishment procedure. Optionally, it means that the received RRC establishment message is successfully received and applied, or it may also mean that the UE delivers the RRC establishment complete message to the lower layer for transmission.

[0053] Embodiment 3

[0054] This embodiment proposes an S-MHI recording method for a UE to enter the RRC connected state from RRC inactive through the RRC connection restoration process.

[0055] This embodiment is applicable to the case where the UE receives an RRC restoration message containing the restoreSCG information element during the RRC restoration process, and the RRC restoration message indicates a PSCell change.

[0056] As an example, for instance, when a PSCell change is successful, if the UE supports saving S-MHI, the UE adds an entry in the UE variable for saving S-MHI, and the entry is used to record the mobility information of the UE's previous PSCell (i.e., the source PSCell at the time of PSCell change). When the UE performs the above operation, the case where the PSCell change occurs during the RRC restoration process is excluded, that is, the case where the PSCell change command is included in the RRC restoration message. The entry includes the cell identifier of the previous PSCell and the time experienced in this PSCell. Optionally, the entry may also include the cell identifier of the PCell corresponding to the UE when this PSCell is configured. Considering the scenario where the UE's PSCell may not change when the PCell is switched, there may be more than one PCell corresponding to the PSCell. The cell identifier may be a global cell identifier or a physical cell identifier.

[0057] The PSCell change refers to the execution of reconfigurationWithSync for the SCG. Preferably, it also includes that the PSCell is not the same (the PSCell identifier in the reconfigurationWithSync is different from the previous PSCell identifier). The PSCell change command refers to the RRC message containing the reconfigurationWithSync for the SCG. The successful PSCell change refers to the case where the reconfigurationWithSync information element for the SCG is included in the RRC message and the MAC layer successfully completes the random access process triggered thereby.

[0058] Embodiment 4

[0059] This embodiment proposes an S-MHI recording method for a UE to enter the RRC connected state from RRC inactive through the RRC connection restoration process.

[0060] This embodiment can be applicable to the case where the UE receives an RRC restoration message that does not contain the restoreSCG information element during the RRC restoration process.

[0061] As an example, when the UE receives an RRC resume message, if the message does not contain the restoreSCG information element, the UE performs the release of the MR-DC related configuration, releases the MR-DC or SCG, and does not perform the update of the S-MHI when releasing the MR-DC or SCG.

[0062] In other words, when performing the release of the MR-DC or SCG, if the UE supports saving the S-MHI, the UE adds an entry in the UE variable used to save the S-MHI, and the entry is used to record the mobility information of the UE's previous PSCell. When the UE performs the above operations, the case where the release of the MR-DC or SCG occurs during the RRC resume process is excluded, that is, the case where the restoreSCG information element is not included in the RRC resume message.

[0063] The entry includes the cell identifier of the previous PSCell and the time experienced in this PSCell. Optionally, the entry may further include the cell identifier of the PCell corresponding to the UE when the UE is configured with this PSCell. Considering the scenario where the UE's PSCell may not change when the PCell is switched, there may be more than one PCell corresponding to the PSCell. The cell identifier may be a global cell identifier or a physical cell identifier.

[0064] Embodiment 5

[0065] This embodiment proposes a method for recording S-MHI when the first PSCell change occurs after the UE enters the RRC connected state from RRC inactive.

[0066] This embodiment can be applied to the case where the UE performs the recovery of the MR-DC / SCG during the RRC resume process but does not change the PSCell, and subsequently receives a PSCell change command included in the RRC reconfiguration message. That is, when the UE receives an RRC resume message containing the restoreSCG information element during the RRC resume process, but the RRC resume message does not contain the synchronization reconfiguration for the SCG, but subsequently receives an RRC reconfiguration message containing the synchronization reconfiguration for the SCG.

[0067] As an example, when a PSCell is successfully changed, if the UE supports saving S-MHI, the UE adds an entry in the UE variable for saving S-MHI, and the entry is used to record the mobility information of the UE's previous PSCell (i.e., the source PSCell at the time of PSCell change). The entry includes the cell identifier of the previous PSCell and the time experienced in this PSCell. When the change of the PSCell is the first PSCell change since the UE enters the RRC connected state through the RRC resume procedure, the time is the time experienced in the previous PSCell since the UE's RRC connection is resumed. Since the RRC connection is resumed can also be expressed as since the UE enters the RRC connected state. The first PSCell change since the UE enters the RRC connected state can also be expressed as the first synchronization reconfiguration for SCG received after the UE receives the RRC resume message. Preferably, the synchronization reconfiguration includes a new PSCell identifier (indicating the change of the PSCell).

[0068] Optionally, the entry may further include the cell identifier of the PCell corresponding to the UE when the PSCell is configured. Considering the scenario where the UE's PSCell may not change when the PCell is switched, there may be more than one PCell corresponding to the PSCell. The cell identifier may be a global cell identifier or a physical cell identifier.

[0069] The PSCell change refers to the execution of the synchronization reconfiguration for SCG (reconfigurationWithSync). Preferably, it also includes that the PSCell is not the same (the PSCell identifier in the synchronization reconfiguration is different from the previous PSCell). The PSCell change command refers to the RRC message containing the synchronization reconfiguration for SCG. The successful PSCell change means that when the synchronization reconfiguration information element for SCG is included in the RRC message and the MAC layer successfully completes the random access procedure triggered thereby.

[0070] Embodiment 6

[0071] This embodiment provides a method for recording S-MHI when a PSCell is added.

[0072] As an example, when the UE successfully adds a PSCell, if the UE supports saving S-MHI, the UE adds an entry in the UE variable for saving S-MHI, and the entry is used to record the time experienced by the UE in the state of no SCG / PSCell configuration before the PSCell is added.

[0073] Preferably, when the addition of the PSCell is the first PSCell addition since the UE enters the RRC connected state through the RRC resume / establishment procedure, the time is the time elapsed from the restoration / establishment of the UE's RRC connection to the addition of the first PSCell. The time since the RRC connection is restored / established can also be expressed as the time since the UE enters the RRC connected state. The first PSCell addition since the UE enters the RRC connected state can also be expressed as the first synchronization reconfiguration for the SCG received after the UE receives the RRC resume / establishment message. When the addition of the PSCell is not the first PSCell addition since the UE enters the connected state, that is, the UE has performed MR-DC / SCG / PSCell release or has been configured with SCG / PSCell before this PSCell addition during this RRC connection procedure, the time is the time elapsed from the previous MR-DC / SCG / PSCell release to this PSCell addition. Optionally, when the addition of the PSCell is not the first PSCell addition since the UE enters the connected state, it can also be expressed as when there is a saved S-MHI on the UE.

[0074] The addition of the PSCell can also be expressed as the addition of the SCG.

[0075] Preferably, the addition of the PSCell refers to performing the synchronization reconfiguration (reconfigurationWithSync) for the SCG and the UE is not configured with the SCG at this time. The PSCell addition command refers to the RRC message containing the synchronization reconfiguration for the SCG and the UE is not configured with the SCG at this time. The successful addition of the PSCell refers to when the UE was not previously configured with the SCG, when it receives and executes the synchronization reconfiguration information element for the SCG contained in the RRC message and the MAC layer successfully completes the random access procedure triggered thereby.

[0076] Optionally, the entries may further include the cell identifiers of one or more PCells corresponding to the UE during the time. The cell identifier may be a global cell identifier or a physical cell identifier.

[0077] In the above embodiment, when the UE adds an entry to the S-MHI, it may further include removing the oldest entry in the UE variable for saving the S-MHI.

[0078] Embodiment 7

[0079] This embodiment provides a method for processing the S-MHI when the UE leaves the RRC connected state.

[0080] As an example, when the UE leaves the RRC connected state, if the UE has saved S-MHI, the saved S-MHI is discarded.

[0081] The leaving of the RRC connected state may be that the UE enters the RRC idle state, or the UE enters the RRC inactive state, for example, because it receives an RRC release message for suspending the RRC connection.

[0082] Embodiment 8

[0083] This embodiment proposes a method for recording S-MHI when the UE releases the SCG.

[0084] As an example, when performing the release of MR-DC or SCG, if the UE supports saving S-MHI, the UE adds an entry to the UE variable for saving S-MHI, and the entry is used to record the mobility information of the UE's previous PSCell. The entry includes the cell identifier of the previous PSCell and the time experienced in this PSCell. Optionally, the entry may further include the cell identifier of the PCell corresponding to the UE when the UE is configured with this PSCell. Considering the scenario where the UE's PSCell may not change when the PCell is switched, there may be more than one PCell corresponding to the PSCell. The cell identifier may be a global cell identifier or a physical cell identifier.

[0085] Embodiment 9

[0086] This embodiment proposes a method for recording S-MHI when the UE enters the RRC connected state from the RRC inactive state through the RRC connection restoration process.

[0087] This embodiment can be applied to the case where the UE receives an RRC restoration message containing a restoreSCG information element during the RRC restoration process, and the RRC restoration message indicates a change in a PSCell.

[0088] As an example, when a PSCell is successfully changed, if the UE supports saving S-MHI, the UE adds an entry in the UE variable for saving S-MHI, and the entry is used to record the mobility information of the UE's previous PSCell (i.e., the source PSCell at the time of PSCell change). The entry includes the cell identifier of the previous PSCell and the time experienced in this PSCell. The time experienced in the PSCell is from the time when this PSCell is added to this PSCell change, including the time when the PSCell in the UE non-active state access stratum context saved when the UE is in the RRC inactive state is this PSCell. Optionally, the entry may further include the cell identifier of the PCell corresponding to the UE when this PSCell is configured. Considering the scenario where the UE's PSCell may not change when the PCell is switched, there may be more than one PCell corresponding to the PSCell. The cell identifier may be a global cell identifier or a physical cell identifier.

[0089] The PSCell change refers to the execution of a synchronous reconfiguration (reconfigurationWithSync) for the SCG. Preferably, it further includes that the PSCells are not the same (the PSCell identifier in the synchronous reconfiguration is different from the previous PSCell identifier). The PSCell change command refers to an RRC message containing the synchronous reconfiguration for the SCG. The successful PSCell change means that when the synchronous reconfiguration information element for the SCG is included in the RRC message and the MAC layer successfully completes the random access procedure triggered thereby.

[0090] Embodiment 10

[0091] This embodiment proposes an S-MHI recording method for a UE to enter the RRC connected state from the RRC inactive state through the RRC connection recovery process.

[0092] This embodiment can be applicable to the case where the UE receives an RRC recovery message that does not contain the restoreSCG information element during the RRC recovery process.

[0093] As an example, when receiving an RRC resume message, if the message does not contain the restoreSCG information element, the UE performs the release of the MR-DC related configuration, releasing MR-DC or SCG. When performing the release of MR-DC or SCG, if the UE supports saving S-MHI, the UE adds an entry in the UE variable for saving S-MHI, and the entry is used to record the mobility information of the UE's previous PSCell. The entry includes the cell identifier of the previous PSCell and the time experienced in this PSCell. The time experienced in the PSCell is the time elapsed from when this PSCell is added to when it is released, including the time when the PSCell in the UE non-active state access stratum context saved when the UE is in the RRC inactive state is this PSCell. Optionally, the entry may further include the cell identifier of the PCell corresponding to the UE when this PSCell is configured. Considering the scenario where the UE's PSCell may not change when the PCell is switched, there may be more than one PCell corresponding to the PSCell. The cell identifier may be a global cell identifier or a physical cell identifier.

[0094] Embodiment 11

[0095] This embodiment proposes a method for recording S-MHI when the first PSCell change occurs after the UE enters the RRC connected state from the RRC inactive state.

[0096] This embodiment is applicable to the case where the UE performs the recovery of MR-DC / SCG during the RRC resume process but does not change the PSCell, and subsequently receives a PSCell change command included in the RRC reconfiguration message. That is, when the UE receives an RRC resume message containing the restoreSCG information element during the RRC resume process, but the RRC resume message does not contain the synchronous reconfiguration for SCG, and subsequently receives an RRC reconfiguration message containing the synchronous reconfiguration for SCG.

[0097] As an example, when a successful PSCell change occurs, if the UE supports saving the S-MHI, the UE adds an entry in the UE variable used to save the S-MHI. The entry is used to record the mobility information of the UE's previous PSCell (i.e., the source PSCell at the time of PSCell change). The entry includes the cell identifier of the previous PSCell and the time experienced in this PSCell. When the PSCell change is the first PSCell change since the UE entered the RRC connected state through the RRC resume procedure, the time experienced in the PSCell is from the time when this PSCell was added to the time of this PSCell change, including the time when the PSCell in the UE non-active state access stratum context saved when the UE was in the RRC inactive state was this PSCell. Since the RRC connection was resumed can also be expressed as since the UE entered the RRC connected state. The first PSCell change since the UE entered the RRC connected state can also be expressed as the first synchronization reconfiguration for the SCG received after the UE received the RRC resume message. Preferably, the synchronization reconfiguration contains a new PSCell identifier (indicating the PSCell change).

[0098] Optionally, the entry may further include the cell identifier of the PCell corresponding to the UE when this PSCell is configured. Considering the scenario where the UE's PSCell may not change when the PCell is switched, there may be more than one PCell corresponding to the PSCell. The cell identifier may be a global cell identifier or a physical cell identifier.

[0099] The PSCell change refers to the execution of the synchronization reconfiguration for the SCG (reconfigurationWithSync). Preferably, it also includes that the PSCells are not the same (the PSCell identifier in the synchronization reconfiguration is different from the previous PSCell). The PSCell change command refers to the RRC message containing the synchronization reconfiguration for the SCG. The successful PSCell change means that when the synchronization reconfiguration information element for the SCG is included in the RRC message and the MAC layer successfully completes the random access procedure triggered thereby.

[0100] Embodiment 12

[0101] This embodiment provides a method for recording S-MHI during S-MHI reporting.

[0102] When the UE performs the reporting of S-MHI, if the UE is not configured with DC / SCG / PSCell at this time, the UE adds an entry in the UE variable used to save S-MHI or in the message used to report S-MHI, and the entry is used to record the time experienced by the UE in the state of no SCG / PSCell configuration before reporting S-MHI.

[0103] When the UE performs S-MHI reporting, it means that the UE reports the recorded S-MHI information to the network side through an RRC message. Generally, the RRC message is the UEInformationresponse message. The UE reports the information to the network side after receiving the S-MHI reporting request from the network side, and the request is implemented by including a request indication information in the RRC message used to request S-MHI reporting, such as the UEInformationRequest message.

[0104] In the above embodiment, when the UE adds an entry in S-MHI, it may also include removing the oldest entry in the UE variable used to save S-MHI.

[0105] Embodiment 13

[0106] This embodiment proposes an S-MHI recording method.

[0107] In this embodiment, when a PSCell addition / change / release occurs, the UE records the absolute time of the event that occurs. For example, the UE is configured to add a PSCell at time T1, then configured to perform a PSCell change to PSCell2 at time T2, and configured to release PSCell2 and SCG at time T3. The UE records the time information of PSCell1 in S-MHI as T1 and T2, and the time information of PSCell2 as T2 and T3. That is, for a PSCell, the previous time identifies the time when the cell is added, and the latter time identifies the time when the cell is released or changed or the time when the UE performs S-MHI reporting.

[0108] Considering the scenario where the UE is in the RRC inactive state. For example, if the UE is configured to add a PSCell at time T1, then at time T2, it is configured to enter the RRC inactive state and save the SCG configuration. During the subsequent RRC connection restoration process, at time T3, an RRC connection restoration message is received. For different configurations during RRC restoration, (1) perform SCG restoration at time T3 and change the PSCell to PSCell2; (2) be configured to release PSCell2 and the SCG at time T3; (3) be configured to restore the SCG configuration at time T3 but not change the PSCell, and then perform the change or release of PSCell1 at time T4. The UE records the time information of PSCell1 in the S-MHI as T1, T2, T3, T4. That is, for a PSCell1, the previous time T1 indicates the time when the cell was added, one of the times T2 indicates the time when the cell was saved / suspended and entered the RRC inactive state, one of the times T3 indicates the time when the cell's RRC was restored and entered the RRC connection; the latter time T4 indicates the time when the cell was released or changed. T3 and T4 can be the same, and optionally, at this time, T4 / T3 may not exist.

[0109] Embodiment 14

[0110] This embodiment describes the user equipment UE of the present disclosure. Figure 3 It is a block diagram showing the user equipment UE involved in the present invention. As Figure 3 shown, the user equipment UE30 includes a processor 301 and a memory 302. The processor 301 may include, for example, a microprocessor, a microcontroller, an embedded processor, etc. The memory 302 may include, for example, a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memories. Program instructions are stored on the memory 302. When these instructions are run by the processor 301, various methods such as the above-mentioned mobile information reporting method described in detail in the present invention can be executed.

[0111] In the present disclosure, some different embodiments can work together. Unless otherwise specified, the concepts or definitions between the embodiments can be common.

[0112] In the present disclosure, a "base station" refers to a mobile communication data and control switching center with a relatively large transmission power and a relatively wide coverage area, including functions such as resource allocation scheduling, data reception and transmission. A "user equipment" refers to a user mobile terminal, for example, including a mobile phone, a notebook, etc., which are terminal devices that can perform wireless communication with a base station or a micro base station.

[0113] The methods and related devices of the present disclosure have been described above in connection with preferred embodiments. Those skilled in the art can understand that the methods shown above are merely exemplary. The methods of the present disclosure are not limited to the steps and sequences shown above. The base stations and user equipment shown above may include more modules. For example, they may also include modules that can be developed or will be developed for use in base stations, MMEs, or UEs, and so on. The various identifiers shown above are merely exemplary rather than restrictive, and the present disclosure is not limited to the specific cells that are examples of these identifiers. Those skilled in the art can make many changes and modifications according to the teachings of the illustrated embodiments.

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

[0115] The programs for implementing the functions of the embodiments of the present disclosure can be recorded on a computer-readable recording medium. The corresponding functions can be implemented by causing a computer system to read the programs recorded on the recording medium and execute these programs. The so-called "computer system" here can be a computer system embedded in the device, and can include an operating system or hardware (such as peripheral devices). The "computer-readable recording medium" can be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium for temporarily storing a program dynamically, or any other recording medium readable by a computer.

[0116] The various features or functional modules of the devices used in the above embodiments can be implemented or executed by circuits (for example, single-chip or multi-chip integrated circuits). The circuits designed to execute the functions described in this specification may include a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of the above devices. The general-purpose processor can be a microprocessor, or any existing processor, controller, microcontroller, or state machine. The above circuits can be digital circuits or analog circuits. In the case where new integrated circuit technologies emerge to replace existing integrated circuits due to the progress of semiconductor technology, one or more embodiments of the present disclosure can also be implemented using these new integrated circuit technologies.

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

[0118] As described 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 embodiments, and the present disclosure also includes any design changes that do not deviate from the gist of the present disclosure. In addition, various changes 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. In addition, components having the same effects described in the above embodiments can be substituted for each other.

Claims

1. A mobile information reporting method, comprising: A user equipment UE enters the RRC connected state from the RRC inactive state through an RRC connection restoration process, or enters the RRC connected state from the RRC idle state through an RRC connection establishment process; And The UE stores mobile history information based on the primary secondary cell PSCell, i.e., S-MHI, The S-MHI includes the time experienced by the UE in the RRC inactive state or the RRC idle state before entering the RRC connected state, When the UE receives an RRC restoration message, if the RRC restoration message does not contain the restoreSCG information element, the UE performs the release of the MR-DC related configuration, releases the MR-DC or the SCG, and the UE does not perform the update of the S-MHI when releasing the MR-DC or the SCG.

2. The mobile information reporting method according to claim 1, wherein, The UE adds an entry in the UE variable for storing the S-MHI, and records the S-MHI through the entry.

3. The mobile information reporting method according to claim 1 or 2, wherein, The S-MHI includes: the time experienced by the UE in the RRC inactive state or the RRC idle state between the release of the previous RRC connection and the entry into the RRC connected state this time.

4. The mobile information reporting method according to claim 1 or 2, wherein, In the case where the UE performs an operation of entering the RRC inactive state from the RRC connected state, the UE records the S-MHI so that the S-MHI includes: the cell identifier of the current PSCell and the time experienced in this PSCell.

5. The mobile information reporting method according to claim 1 or 2, wherein, When a successful PSCell change occurs, the UE records the S-MHI so that the S-MHI includes: the mobile information of the source PSCell at the time of PSCell change, i.e., the cell identifier of the source PSCell and the time experienced in this PSCell.

6. The mobile information reporting method according to claim 5, wherein, In the case where the change of the PSCell is the first PSCell change since the UE enters the RRC connected state through the RRC restoration process, the time is the time experienced in the previous PSCell since the RRC connection of the UE is restored.

7. The mobile information reporting method according to claim 1 or 2, wherein, When the UE successfully adds a PSCell, the UE records the S-MHI so that the S-MHI includes: the time experienced by the UE in the state without SCG / PSCell configuration before the PSCell addition.

8. The mobile information reporting method according to claim 1 or 2, wherein, When the UE supports storing the S-MHI, the UE records the S-MHI.

9. A user equipment UE, comprising: A processor; And A memory storing instructions; Wherein, when being run by the processor, the instruction executes the mobile information reporting method according to any one of claims 1 to 8.