Reporting procedure for successful change of primary cell of a secondary cell group

Abstract

Embodiments of the disclosed technology provide a framework and procedures for supporting a user equipment to perform a subsequent conditional PSCell (primary cell of a secondary cell group) addition or change (CPAC) procedure or a subsequent layer 1 / layer 2 (L1 / L2) triggered mobility (LTM) procedure in mobility robustness optimization (MRO). An example wireless communication method includes generating or updating, by a wireless device, a report for a subsequent conditional handover procedure; and transmitting the report to a network node. In this example, the report includes a successful handover report.

Description

Technical Field

[0001] This disclosure generally relates to digital wireless communications. Background Technology

[0002] Mobile telecommunications technologies are driving the world toward an increasingly interconnected and networked society. Compared to existing wireless networks, next-generation systems and wireless communication technologies will need to support a wider range of use cases and provide more complex and granular access requirements and flexibility.

[0003] Long-Term Evolution (LTE) is a wireless communication standard for mobile devices and data terminals developed by the 3rd Generation Partnership Project (3GPP). LTE-A is a wireless communication standard that enhances the LTE standard. The fifth-generation wireless system, 5G, is an evolution of the LTE and LTE-A standards, aiming to support higher data rates, massive connectivity, ultra-low latency, high reliability, and other emerging service requirements. Summary of the Invention

[0004] This document discloses techniques for generating and / or updating, and subsequently sending, reports related to subsequent Conditional PSCell (primary cell of a secondary cell group) addition or change (CPAC) procedures or subsequent Layer 1 / Layer 2 (L1 / L2) triggered mobility (LTM) procedures. The described embodiments, for example, provide reduced latency and overhead, advantageously improving network communications by providing a mobility experience similar to beam-switching mobility.

[0005] In one example aspect, a wireless communication method includes: generating or updating a report by a wireless device for subsequent mobility processes; and sending the report to a network node.

[0006] In another example, a wireless communication method includes: receiving a report from a wireless device by a network node for subsequent mobility procedures; and transmitting data or control signaling based on the report. In this example, the wireless device is configured to generate or update the report before the network node receives it.

[0007] In yet another example, a wireless communication method includes: transmitting mobility history information, which includes one or more service characteristics and activation / deactivation information, from a wireless device to a network node.

[0008] In yet another example, a wireless communication method includes: receiving mobility history information from a wireless device by a network node, the mobility history information including one or more service characteristics and activation / deactivation information; and transmitting data or control signaling based on the mobility history information.

[0009] In yet another example, the above method is implemented in the form of processor-executable code and stored in a non-transitory computer-readable storage medium. The code contained in this computer-readable storage medium, when executed by a processor, causes the processor to implement the method described in this patent document.

[0010] In yet another example, a device configured or operable to perform the methods described above is disclosed.

[0011] The above and other aspects, and their implementations, are described in more detail in the accompanying drawings, description, and claims. Attached Figure Description

[0012] Figures 1 to 4 This is a flowchart of an example wireless communication method.

[0013] Figure 5 A block diagram of an example hardware platform is shown, which may be part of a network device or a communication device.

[0014] Figure 6 Examples of wireless communications, including base stations (BS) and user equipment (UE), based on some implementations of the disclosed technology are shown. Detailed Implementation

[0015] Existing cellular systems (e.g., 3GPP Rel-18) support Layer 1 / Layer 2 (L1 / L2) triggered mobility (LTM), a cell handover process triggered by a Medium Access Control (MAC) control element based on L1 measurements. This is used to further enhance UE mobility, avoid full L2 (and L1) resets, and reduce latency, overhead, and / or interruptions, thereby providing a mobility experience similar to beam-switching mobility.

[0016] These systems also support enhanced Conditional Post-Configuration Cell Addition or Change (CPAC) for secondary cell groups, a process that allows the UE to continue CPAC based on candidate configurations pre-configured from the network. Here, the UE's secondary cell group (SCG) automatically changes from one to another within a set of candidate SCGs, while the master cell group (MCG) remains unchanged. Configuring SCG pools for the UE and automating other aspects of this process is beneficial to the network.

[0017] However, current 3GPP Self-Organizing Network (SON) and Minimization of Drive Testing (MDT) techniques neither cover nor support subsequent LTM or subsequent CPAC. Specifically, Mobility Robustness Optimization (MRO) in SON needs to be enhanced to better support subsequent LTM or subsequent CPAC. This will enable the network to be better aware of failure and near-failure scenarios.

[0018] The embodiments of the disclosed technology at least solve the following technical problems: – At the UE, reports used for subsequent LTMs may be overwritten; – At the UE, reports intended for subsequent CPAC may be overwritten; and – The network, as part of the Mobility History Information (MHI) from the UE, may not be aware that the UE is configured to support dual connectivity.

[0019] The example headings used in the following sections are intended to facilitate understanding of the disclosed subject matter and do not in any way limit the scope of the claimed subject matter. Therefore, one or more features of one example section may be combined with one or more features of another example section. Furthermore, for clarity of explanation, the term 5G (or 5G NR) is used, but the technologies disclosed in this document are not limited to 5G (or 5G NR) technology and can be used in wireless systems implementing other communication protocols.

[0020] 1. Example solutions related to CPAC's SPR being covered Subsequent Conditional PSCell Addition or Modification (Subsequent CPAC) is a conditional PSCell addition or modification procedure that is executed after a PSCell addition, PSCell modification, PCell modification, or SCG release, based on a pre-configured subsequent CPAC configuration of the candidate PSCell, without requiring reconfiguration and reinitialization of the Conditional PSCell Modification (CPC) / Conditional PSCell Addition (CPA). Further details of subsequent CPAC are provided in 3GPP TS 38.300 Release 18.1.0, for example.

[0021] Furthermore, the UE retains the configured subsequent CPAC settings (unless the network instructs it to be released) and evaluates the execution conditions of candidate PSCells after PSCell addition, PSCell change, PCell change, or SCG release is completed. Intra-SN subsequent CPACs initiated by the SN and inter-SN subsequent CPACs initiated by the MN or SN are supported. For more details, please refer to 3GPP TS 37.340 Release 18.1.0.

[0022] If subsequent CPAC is configured for the UE, various reports may need to be generated more frequently, for example, when the SCG is at FR2 or any higher frequency band. However, the network also needs to be configured to acquire these reports at a higher frequency (compared to when the UE is not configured with subsequent CPAC). If every report generated by the UE is not acquired by the network, suboptimal success or near-failure reports (e.g., PSCell Successful Change Report (SPR)) may be overridden, and near-failure information will not be perceived by the network. This could lead to subsequent CPAC being stopped as soon as a failure occurs in the SCG. It is important to note that the overriding issue does not apply to failure information, as failure information is reported to the network in real time.

[0023] The embodiments of the disclosed technology provide the following technical solutions to prevent the SPR of subsequent CPACs from being overwritten.

[0024] 1.1 Regarding the subsequent reuse of existing SPRs in CPAC In some embodiments, for each subsequent CPAC configuration, a report used to store all SPRs associated with that subsequent CPAC configuration is reused. For example, this can be achieved by using an indication to specify a particular SPR for a subsequent CPAC, in which case the SPR is marked as being for the subsequent CPAC, and each near-failure CPAC is recorded in a report by merging that report with the latest SPR.

[0025] In some examples, when the conditions for updating the SPR are met and the new SPR is associated with the same subsequent CPAC configuration, the existing SPR at the UE is not overwritten, but rather expanded to include the new SPR information for that subsequent CPAC. The existing report is merged with the new SPR information. In alternative scenarios (e.g., the new SPR does not correspond to the same subsequent CPAC configuration, or the conditions for updating the SPR are not met), the new SPR overwrites the previous SPR in the existing report. In this example, the conditions include a near-failure event occurring in the PSCell, such as reaching a configuration threshold for timers T304, T310, or T312.

[0026] 1.2 For subsequent CPACs, a new SPR will be used. In some embodiments, a new report is used for subsequent CPACs. For each subsequent CPAC configuration, an independent SPR is defined, independent of the SPRs of other mobility configurations (e.g., non-subsequent CPACs). Whenever the conditions for updating the SPR are met and the existing SPR and the new SPR belong to the same subsequent CPAC configuration, the existing SPR at the UE (e.g., through merging) is expanded to include the new SPR information for that subsequent CPAC. However, if the existing SPR contains information about another subsequent CPAC configuration (i.e., a different subsequent CPAC associated with the new SPR), the existing report is overwritten. In this example, the conditions include a near-failure event occurring on the PSCell, such as reaching a configuration threshold for timers T304, T310, or T312.

[0027] In the embodiments described in Sections 1.1 and 1.2, the SPR is configured to include at least one of the following: – When a PSCell change / addition is successfully executed, the last measurement results obtained in neighboring NR cells are based on the initiating node configuration. – When a successful PSCell change or addition triggers this report, the PCell to which the UE is connected, for example, the PSCell Successful Addition or Change Report (SPR). – Record whether the PSCell change process for this report was initiated by the secondary node (SN). –Reasons why PSCell successfully added or modified reports – The source PSCell that triggered this report for the successful PSCell change – In a PSCell change, when a successful PSCell change triggers this report, the last measurement result obtained from the source PSCell. – The target PSCell that triggered this report for successful PSCell additions / changes – In a successful PSCell addition or change that triggers this report, the last measurement result obtained in the target PSCell. – (a) the time elapsed between initiating the last conditional reconfiguration execution for the target PSCell and (b) receiving the latest conditional reconfiguration for the target PSCell. 1.3 UE Instructions to the Network In some embodiments, a legacy SPR can be reused. Whenever the UE updates the SPR associated with a subsequent CPAC, it sends an indication to the network that the SPR associated with that specific subsequent CPAC is available. Based on this indication, the network can retrieve the report before it is overwritten by an updated SPR resulting from another near-failed CPAC. In some examples, this indication is carried in a Radio Resource Control (RRC) message. In other examples, it is carried in a Medium Access Control (MAC) control element (CE).

[0028] 2. Example solutions related to RLF reporting / SHR coverage for MCG LTM Subsequent LTM is defined as performing an L1 / L2 triggered mobility cell handover process between candidate cells without network RRC configuration during this period. In other words, subsequent LTM is performed by repeating the steps of early synchronization, LTM cell handover execution, and LTM cell handover completion, without releasing other LTM candidate configurations after each LTM cell handover completion.

[0029] Due to the nature of subsequent LTM, LTM cell handovers may automatically and frequently occur from one candidate cell group to another. To mitigate this impact, it is beneficial for the network to configure a pool of candidate LTM cells for the UE and then trigger LTM cell handovers only when necessary with minimal data interruption.

[0030] If a subsequent LTM is configured for the UE, various reports may need to be generated more frequently (i.e., at a higher frequency). For example, in the event of a failure (even if an LTM recovery process has been performed on the failed LTM), RLF reports are generated more frequently; for near-failure scenarios, SHR updates are more frequent. However, the network also needs to be configured to acquire these reports at a higher frequency (compared to when the UE is not configured with a subsequent LTM). If every report generated by the UE is not acquired by the network, failure reports (e.g., Radio Link Failure (RLF) reports) or near-failure reports (e.g., Successful Handover Reports (SHR)) may be overwritten, and this information will not be perceived by the network.

[0031] The embodiments of the disclosed technology provide the following technical solutions to prevent subsequent LTM RLF reports or SHRs from being overwritten.

[0032] 2.1 For subsequent LTM reuse of existing RLF reports or SHR In some embodiments, for each subsequent LTM configuration, a report used to store all RLF reports associated with that subsequent LTM configuration is reused. For example, this can be achieved by using an indication to specify a particular RLF report for subsequent LTM, in which case the RLF report is marked as for subsequent LTM, and each LTM cell handover failure is recorded in the existing LTM RLF report by merging that report with the latest RLF report information.

[0033] In one example, when the conditions for updating the LTM RLF report are met and the new RLF report is associated with the same subsequent LTM configuration, the existing LTM RLF report at the UE is not overwritten, but rather expanded to include the new RLF report for that subsequent LTM. The existing report is merged with the new LTM information. In alternative scenarios (e.g., the new LTM cell handover does not correspond to the same subsequent LTM configuration, or the conditions for updating the RLF report are not met), the new RLF report overwrites the previous RLF report in the existing report. In this example, the conditions include a radio link failure (RLF) event or a handover failure (HOF) event occurring at the UE.

[0034] In some embodiments, for each subsequent LTM configuration, a report used to store all SHRs associated with that subsequent LTM configuration is reused. For example, this can be achieved by using an indication to specify a particular SHR for a subsequent LTM, in which case the SHR is marked as being used for a subsequent LTM, and each LTM cell handover near failure is recorded in the existing LTM SHR by merging that report with the latest SHR information.

[0035] In one example, when the conditions for updating the LTM SHR are met and the new SHR is associated with the same subsequent LTM configuration, the existing LTM SHR at the UE is not overwritten, but rather expanded to include the new SHR for that subsequent LTM. The existing report is merged with the new SHR. In alternative scenarios (e.g., the new LTM cell handover does not correspond to the same subsequent LTM configuration, or the conditions for updating the SHR are not met), the new SHR overwrites the previous SHR in the existing report. In this example, the conditions include a near-failure event occurring on the PSCell, such as reaching a configured threshold for timers T304, T310, or T312.

[0036] 2.2 For subsequent LTMs, use the new RLF report or SHR. In some embodiments, a new report is used for subsequent LTMs. For each subsequent LTM configuration, a separate RLF report or SHR is defined, independent of the RLF reports or SHRs of other mobility configurations (e.g., non-subsequent LTMs). Whenever the conditions for updating an RLF report or SHR are met and the existing RLF report or SHR and the new RLF report or SHR belong to the same subsequent LTM configuration, the existing RLF report or SHR at the UE is expanded (e.g., by merging) to include the new RLF report or SHR for that subsequent LTM. However, if the existing RLF report or SHR contains information about another subsequent LTM configuration (i.e., different from the subsequent LTM associated with the new RLF report or SHR), the existing report is overwritten. In this example, the conditions include a radio link failure (RLF) event or a handover failure (HOF) event at the UE (for RLF reports), and a near failure event at the PSCell, such as reaching a configured threshold for timers T304, T310, or T312 (for SHRs).

[0037] 3. Example solutions related to SPR coverage of SCG LTM The embodiments of the disclosed technology provide the following technical solutions to prevent the SPR of subsequent LTMs configured for SCG from being overwritten.

[0038] 3.1 Subsequent LTM reuse of existing SPR for SCG In some embodiments, for each SCG's subsequent LTM configuration, a report used to store all SPRs associated with that SCG's subsequent LTM configuration is reused. For example, this can be achieved by using an indication to specify a particular SPR for the SCG's subsequent LTM, in which case the SPR is marked as being used for the SCG's subsequent LTM, and each near-failure LTM is recorded in the report by merging that report with the latest SPR.

[0039] In some examples, when the conditions for updating the SPR are met and the new SPR is associated with a subsequent LTM configuration for the same SCG, the existing SPR at the UE is not overwritten, but rather expanded to include the new SPR information for the subsequent LTM of the SCG. The existing report is merged with the new SPR information. In alternative scenarios (e.g., the new SPR does not correspond to a subsequent LTM configuration for the same SCG, or the conditions for updating the SPR are not met), the new SPR overwrites the previous SPR in the existing report. In this example, the conditions include a near-failure event occurring in the PSCell, such as reaching a configuration threshold for timers T304, T310, or T312.

[0040] 3.2 Use the new SPR for subsequent LTMs of SCG In some embodiments, a new report is used for subsequent LTMs of an SCG. For each SCG's subsequent LTM configuration, an independent SPR is defined, independent of the SPRs of other mobility configurations (e.g., subsequent LTMs of non-SCGs). Whenever the conditions for updating the SPR are met and the existing SPR and the new SPR belong to the same SCG's subsequent LTM configuration, the existing SPR at the UE (e.g., through merging) is expanded to include the new SPR information for the SCG's subsequent LTM. However, if the existing SPR contains information about the subsequent LTM configuration of another SCG (i.e., different from the subsequent LTM of the SCG associated with the new SPR), the existing report is overwritten. In this example, the conditions include a near-failure event occurring on the PSCell, such as reaching a configuration threshold for timers T304, T310, or T312.

[0041] 4 Example solutions related to SCG activation information in MHI Mobility history information (MHI) is typically generated by the UE when requested by a network node and may include the UE’s beam-related information, sensor information, location information, and / or dual connectivity information.

[0042] In existing implementations, enhancing the MHI to allow storage of SCG (de)activation information is based on enabling the network to understand the activation time of the SCG. This allows the network to learn about the efficiency of the configured SCG. Based on this information, the network can then optimize future dual-connectivity configurations, for example, to balance UE battery usage and data service efficiency. This MHI enhancement is achieved by including the SCG activation time (the duration of SCG activation, or the percentage of time the SCG is active) in the PSCellMHI.

[0043] However, this existing implementation completely ignores the impact of service characteristics, which are essential for determining network efficiency. In one example, a 10% activation time can only be judged as a beneficial or detrimental dual-connectivity configuration when evaluated in conjunction with service requirements; for example, it might be a good strategy for bursty services that are only active 10% of the time. In this case, the network activates the SCG at appropriate times to maximize efficiency. In another example, a 50% activation time cannot be characterized without knowing the service requirements at the time.

[0044] Therefore, it is beneficial for the network to know the efficiency of the configured SCG. This allows the network to optimize future dual connectivity (DC) configurations to balance UE battery usage and data service efficiency. On the other hand, activation and deactivation information becomes irrelevant in the absence of data service features.

[0045] The disclosed embodiments provide a scheme for reporting service characteristics along with activation and deactivation information. In some examples, service information can be characterized by at least one of the following: – The data rate of the SCG during its activation period. For example, a short deactivation period but a high data rate may indicate that the SCG configuration is still efficient enough to meet the data rate requirements.

[0046] – The amount of data generated by the SCG during its activation period. For example, a short deactivation period but a high data volume may indicate that the SCG configuration is still efficient enough to meet data capacity requirements.

[0047] – The data rate or data volume of the SCG during the deactivation time of the Primary Cell Group (MCG). For example, a high data rate and / or data volume of the MCG during the SCG deactivation time may indicate that the network deactivated the SCG at an incorrect time.

[0048] In the above example, the data rate or data volume can be calculated as the average uplink (UL) data rate or data volume, the downlink (DL) data rate or data volume, or a combination of both.

[0049] Alternatively, service characteristics that can be reported to the network to better assess and determine activation and deactivation cycles may include aggregated carrier bandwidth configured for the UE and / or aggregated bandwidth portions configured for the UE.

[0050] Example implementations and embodiments of the 5 disclosed technologies Figure 1 A flowchart of an example wireless communication method 100 is shown. Method 100 includes, at operation 110, a report generated or updated by a wireless device for subsequent mobility procedures.

[0051] Method 100 includes sending the report to the network node at operation 120.

[0052] Figure 2 A flowchart of an example wireless communication method 200 is shown. Method 200 includes, at operation 210, a network node receiving a report from a wireless device for subsequent mobility procedures.

[0053] Method 200 includes, at operation 220, sending data or control signaling based on the report. In this example, the wireless device is configured to generate or update the report before the network node receives it.

[0054] Figure 3 A flowchart of an example wireless communication method 300 is shown. Method 300 includes, at operation 310, a wireless device sending mobility history information to a network node, the mobility history information including one or more service characteristics and activation / deactivation information.

[0055] Figure 4 A flowchart of an example wireless communication method 400 is shown. Method 400 includes, at operation 410, a network node receiving mobility history information from a wireless device, the mobility history information including one or more service characteristics and activation / deactivation information.

[0056] Method 400 includes, at operation 420, sending data or control signaling based on the mobility history information.

[0057] The described features can be implemented to further provide one or more of the following technical solutions: A1. A wireless communication method comprising: generating or updating a report for subsequent mobility procedures by a wireless device; and transmitting the report to a network node. In some examples, the subsequent mobility procedures include a subsequent conditional PSCell add-or-change (CPAC) procedure, such as that described in Section 1. In other examples, the subsequent mobility procedures include a subsequent L1 / L2 triggered mobility (LTM) procedure, such as that described in Section 2. In still other examples, the subsequent mobility procedures include a subsequent L1 / L2 triggered mobility (LTM) procedure configured for a secondary cell group (SCG), such as that described in Section 3.

[0058] A2. A wireless communication method comprising: receiving, by a network node, a report from a wireless device for subsequent mobility procedures; and transmitting data or control signaling based on the report, wherein the wireless device is configured to generate or update the report prior to the network node receiving the report. In some examples, the subsequent mobility procedures include a subsequent conditional PSCell add-or-change (CPAC) procedure, such as that described in Section 1. In other examples, the subsequent mobility procedures include a subsequent L1 / L2 triggered mobility (LTM) procedure, such as that described in Section 2. In still other examples, the subsequent mobility procedures include a subsequent L1 / L2 triggered mobility (LTM) procedure configured for a secondary cell group (SCG), such as that described in Section 3.

[0059] A3. The method according to scheme A1 or A2, wherein the report includes an indication of the association between the report and subsequent mobility procedures. In some examples, corresponding to the subsequent mobility procedures described in sections 1 through 3, the report includes a PSCell Successful Change Report (SPR), a Radio Link Failure (RLF) report, or a Successful Handover Report (SHR), or an SPR.

[0060] A4. The method according to scheme A1 or A2, wherein: when an existing report is associated with a configuration that triggers a subsequent mobility process that generates or updates the report, the report is merged with the existing report; otherwise, the existing report is overwritten by the new report. In some examples, report overwriting corresponds to the existing report being cleared and overwritten by the new report. In other examples, report overwriting corresponds to the existing report being replaced by the new report. In still other examples, report overwriting corresponds to the existing report being marked (or labeled) as "not used" (or "invalid") and used as the new report.

[0061] A5. The method described according to scheme A1 or A2, wherein the reports used for subsequent mobility procedures are independent of reports from other mobility configurations.

[0062] A6. The method according to scheme A5, wherein: when an existing report is associated with a configuration that triggers a subsequent mobility process that generates or updates the report, the report is merged with the existing report; otherwise, the existing report is overwritten by the new report. In some examples, report overwriting corresponds to the existing report being cleared and overwritten by the new report. In other examples, report overwriting corresponds to the existing report being replaced by the new report. In still other examples, report overwriting corresponds to the existing report being marked (or labeled) as "not used" (or "invalid") and used as the new report.

[0063] A7. The method according to any one of schemes A1 to A6, wherein the subsequent mobility process includes a subsequent conditional handover process, and the report includes a successful handover report. In some examples, schemes A7 to A10 are described in Section 1, wherein the report includes a PSCell Successful Change Report (SPR), and the subsequent mobility process includes a subsequent conditional PSCell Addition or Change (CPAC).

[0064] A8. The method according to scheme A7, wherein the report includes at least one of the following: the last measurement result obtained from the neighboring New Radio (NR) cell based on the initiating node configuration when a change or addition of the primary cell (PSCell) of the secondary cell group is successfully performed; the identifier of the primary cell (PCell) of the primary cell group connected to the radio device when the successful change or addition of the PSCell triggers the report; whether the secondary node (SN) initiated an instruction to trigger the report; the reason for generating or updating the report; the source PSCell of the successful change or addition of the PSCell; the last measurement result obtained in the source PSCell of the successful change or addition of the PSCell; the target PSCell of the successful change or addition of the PSCell; the last measurement result obtained in the target PSCell of the successful change or addition of the PSCell; and the time elapsed between initiating the last conditional reconfiguration for the target PSCell and receiving the latest conditional reconfiguration for the target PSCell.

[0065] A9. The method according to scheme A7, wherein the report is a conventional report associated with subsequent condition handover procedures, and the indication for generating or updating the report is carried in a Radio Resource Control (RRC) message or a Media Access Control (MAC) control element (CE).

[0066] A10. The method according to scheme A9, wherein the wireless device is configured to send the indication when the report is generated or updated.

[0067] A11. The method according to any one of schemes A7 to A10, wherein the successful switch report is a PSCell Successful Change Report (SPR), and the subsequent conditional switch process is a Conditional PSCell Addition or Change (CPAC).

[0068] A12. The method according to any one of schemes A1 to A6, wherein the subsequent mobility process includes a subsequent lower-layer triggered mobility process, and the report includes a radio link failure report or a successful handover report. In some examples, schemes A12 and A13 are described in Section 2.

[0069] A13. According to the method described in scheme A12, the radio link failure report is a radio link failure (RLF) report, the successful handover report is a successful handover report (SHR), and the subsequent lower layer triggering mobility process is a layer 1 / layer 2 (L1 / L2) triggering mobility (LTM) process.

[0070] A14. The method according to any one of schemes A1 to A6, wherein the subsequent mobility process includes a subsequent low-layer triggered mobility process configured for the secondary cell group, and the report includes a successful cell handover report. In some examples, schemes A14 and A15 are described in Section 3.

[0071] A15. According to the method described in scheme A14, the successful cell handover report is a PSCell Successful Change Report (SPR), and the subsequent low-level mobility triggering procedure configured for the secondary cell group is the Layer 1 / Layer 2 (L1 / L2) Mobility Triggering (LTM) procedure configured for the secondary cell group (SCG).

[0072] A16. A wireless communication method comprising: transmitting mobility history information, including one or more service characteristics and activation / deactivation information, from a wireless device to a network node. In some examples, schemes A16 to A19 are described in Section 4.

[0073] A17. A wireless communication method comprising: receiving mobility history information from a wireless device by a network node, the mobility history information including one or more service characteristics and activation / deactivation information; and transmitting data or control signaling based on the mobility history information.

[0074] A18. The method according to scheme A16 or A17, wherein the one or more service characteristics include at least one of the following: the data rate of the secondary cell group (SCG) during at least one active time; or the amount of data of the SCG during the at least one active time.

[0075] A19. The method according to scheme A18, wherein the data rate is based on the average uplink (UL) data rate or the average downlink (DL) data rate, and the data volume is based on the uplink (UL) data volume or the downlink (DL) data volume during the at least one activation time.

[0076] A20. An apparatus for wireless communication, comprising one or more processors configured to implement the method described in one or more of schemes A1 to A19.

[0077] A21. A non-transitory computer-readable program storage medium having code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement one or more of the methods described in schemes A1 to A19.

[0078] The described features can be implemented to further provide one or more of the following technical solutions: B1. A wireless communication method comprising: generating or updating a report by a wireless device for a subsequent conditional handover process; and sending the report to a network node, wherein the report includes a successful handover report.

[0079] B2. A wireless communication method comprising: receiving, by a network node, a report from a wireless device for a subsequent conditional handover process; and transmitting data or control signaling based on the report, wherein the wireless device is configured to generate or update the report prior to the network node receiving the report, the report including a successful handover report.

[0080] B3. The method according to scheme B1 or B2, wherein the report includes an indication of the association between the report and subsequent condition switching procedures.

[0081] B4. The method according to scheme B1 or B2, wherein: when an existing report is associated with a configuration that triggers a subsequent condition switching process that generates or updates the report, the report is merged with the existing report; otherwise, the existing report is overwritten by the report.

[0082] B5. The method described according to scheme B1 or B2, wherein the reports used for subsequent condition switching procedures are independent of reports from other mobility configurations.

[0083] B6. The method according to scheme B5, wherein: when an existing report is associated with a configuration that triggers a subsequent condition switching process that generates or updates the report, the report is merged with the existing report; otherwise, the existing report is overwritten by the report.

[0084] B7. The method according to scheme B4 or B6, wherein the report includes at least one of the following: the last measurement result obtained from the neighboring New Radio (NR) cell based on the initiating node configuration when a change or addition of the primary cell (PSCell) of the secondary cell group is successfully performed; the identifier of the primary cell (PCell) of the primary cell group connected to the radio device when the successful change or addition of the PSCell triggers the report; whether the secondary node (SN) initiated an instruction to trigger the report; the reason for generating or updating the report; the source PSCell of the successful change or addition of the PSCell; the last measurement result obtained in the source PSCell of the successful change or addition of the PSCell; the target PSCell of the successful change or addition of the PSCell; the last measurement result obtained in the target PSCell of the successful change or addition of the PSCell; and the time elapsed between initiating the last conditional reconfiguration for the target PSCell and receiving the latest conditional reconfiguration for the target PSCell.

[0085] B8. The method according to scheme B1 or B2, wherein the report is a conventional report associated with subsequent condition handover procedures, and the indication for generating or updating the report is carried in a Radio Resource Control (RRC) message or a Media Access Control (MAC) control element (CE).

[0086] B9. The method according to scheme B8, wherein the wireless device is configured to send the instruction when the report is generated or updated.

[0087] B10. The method according to any one of schemes B1 to B9, wherein the successful switch report is a PSCell Successful Change Report (SPR), and the subsequent conditional switch process is a Conditional PSCell Addition or Change (CPAC).

[0088] B11. A wireless communication method comprising: generating or updating a report by a wireless device for subsequent lower-layer triggering of a mobility process; and sending the report to a network node, wherein the report includes a wireless link failure report or a successful handover report.

[0089] B12. A wireless communication method comprising: receiving, by a network node, a report from a wireless device for subsequently triggering a mobility process at a lower layer; and transmitting data or control signaling based on the report, wherein the wireless device is configured to generate or update the report prior to the network node receiving the report, the report including a wireless link failure report or a successful handover report.

[0090] B13. The method according to scheme B11 or B12, wherein the report includes an indication of the association between the report and subsequent lower-level triggered mobility procedures.

[0091] B14. The method according to scheme B11 or B12, wherein: when an existing report is associated with a configuration that triggers a subsequent lower-level mobility process that generates or updates the report, the report is merged with the existing report; otherwise, the existing report is overwritten by the report.

[0092] B15. The method according to scheme B11 or B12, wherein the report used for subsequent low-level triggering of mobility procedures is independent of reports from other mobility configurations.

[0093] B16. The method according to scheme B15, wherein: when an existing report is associated with a configuration that triggers a subsequent lower-level mobility process that generates or updates the report, the report is merged with the existing report; otherwise, the existing report is overwritten by the report.

[0094] B17. The method according to any one of schemes B11 to B16, wherein the radio link failure report is a radio link failure (RLF) report, the successful handover report is a successful handover report (SHR), and the subsequent lower layer trigger mobility process is a layer 1 / layer 2 (L1 / L2) trigger mobility (LTM) process.

[0095] B18. A wireless communication method comprising: generating or updating a report by a wireless device for configuring a subsequent low-layer triggered mobility procedure for a secondary cell group; and transmitting the report to a network node, wherein the report includes a successful cell handover report.

[0096] B19. A wireless communication method comprising: receiving, by a network node, a report from a wireless device for configuring a subsequent lower-layer triggered mobility procedure for a secondary cell group; and transmitting data or control signaling based on the report, wherein the wireless device is configured to generate or update the report prior to the network node receiving the report, and wherein the report includes a successful cell handover report.

[0097] B20. The method according to scheme B18 or B19, wherein the report includes an indication of the association between the report and subsequent low-level triggered mobility procedures configured for the secondary cell group.

[0098] B21. The method according to scheme B18 or B19, wherein: when an existing report is associated with a configuration that triggers the generation or update of the report and is configured for a subsequent low-level mobility triggering process for a secondary cell group, the report is merged with the existing report; otherwise, the existing report is overwritten by the report.

[0099] B22. The method according to scheme B18 or B19, wherein the reporting of subsequent low-level triggered mobility procedures for configuring secondary cell groups is independent of the reporting of other mobility configurations.

[0100] B23. The method according to scheme B22, wherein: when an existing report is associated with a configuration that triggers the generation or update of the report and is configured for a subsequent low-level mobility triggering process for a secondary cell group, the report is merged with the existing report; otherwise, the existing report is overwritten by the report.

[0101] B24. The method according to any one of schemes B18 to B23, wherein the successful cell handover report is a PSCell Successful Change Report (SPR), and the subsequent low-level mobility triggering procedure configured for the secondary cell group is a Layer 1 / Layer 2 (L1 / L2) Mobility Triggering (LTM) procedure configured for the secondary cell group (SCG).

[0102] B25. A wireless communication method comprising: transmitting mobility history information from a wireless device to a network node, the mobility history information including one or more service characteristics and activation / deactivation information.

[0103] B26. A wireless communication method comprising: receiving mobility history information from a wireless device by a network node, the mobility history information including one or more service characteristics and activation / deactivation information; and transmitting data or control signaling based on the mobility history information.

[0104] B27. The method according to scheme B25 or B26, wherein the one or more service characteristics include at least one of the following: the data rate of the secondary cell group (SCG) during at least one active time; or the amount of data of the SCG during the at least one active time.

[0105] B28. The method according to scheme B27, wherein the data rate is based on the average uplink (UL) data rate or the average downlink (DL) data rate, and the data volume is based on the uplink (UL) data volume or the downlink (DL) data volume during the at least one activation time.

[0106] B29. An apparatus for wireless communication, comprising one or more processors configured to implement one or more of the methods described in schemes B1 to B28.

[0107] B30. A non-transitory computer-readable program storage medium having code stored thereon, which, when executed by at least one processor, causes the at least one processor to implement one or more of the methods described in schemes B1 to B28.

[0108] Figure 5 A block diagram of an example hardware platform 500 is shown, which may be part of a network device (e.g., a base station) or a communication device (e.g., a user equipment (UE)). The hardware platform 500 includes at least one processor 510 and a memory 505 storing instructions. These instructions, when executed by the processor 510, configure the hardware platform 500 to perform its functions. Figures 1 to 4 The operations shown and described in the various embodiments described in this patent document. Transmitter 515 sends or transmits information or data to another device. For example, a transmitter of a network device can send a message to a user device. Receiver 520 receives information or data sent or transmitted by another device. For example, a user device can receive a message from a network device.

[0109] The implementation of the above discussion will be applicable to wireless communication. Figure 6 An example of a wireless communication system (e.g., a 5G or NR cellular network) is illustrated, comprising a base station 620 and one or more user equipments (UEs) 611, 612, and 613. In some embodiments, the UE accesses the BS (i.e., the network) using a communication link to the network (sometimes referred to as the uplink, as shown by dashed arrows 631, 632, and 633), subsequently enabling communication from the BS to the UE (e.g., as shown in the direction from the network to the UE, sometimes referred to as the downlink, as shown by arrows 641, 642, and 643). In some embodiments, the BS sends information to the UE (sometimes referred to as the downlink, as shown by arrows 641, 642, and 643), subsequently enabling communication from the UE to the BS (e.g., as shown in the direction from the UE to the BS, sometimes referred to as the uplink, as shown by dashed arrows 631, 632, and 633). The UE may be, for example, a smartphone, tablet, mobile computer, machine-to-machine (M2M) device, Internet of Things (IoT) device, etc.

[0110] Some embodiments described herein are described in the general context of methods or processes that may be implemented in one embodiment by a computer program product embodied in a computer-readable medium, including computer-executable instructions, such as program code, executed by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), optical disc (CD), digital versatile optical disc (DVD), etc. Therefore, the computer-readable medium may include non-transitory storage media. Typically, program modules may include routines, programs, objects, components, data structures, etc., for performing a specific task or implementing a specific abstract data type. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for performing the steps of the methods disclosed herein. Specific sequences of these executable instructions or associated data structures represent examples of corresponding actions for implementing the functions described in these steps or processes.

[0111] Some of the disclosed embodiments can be implemented using hardware circuitry, software, or a combination thereof as devices or modules. For example, hardware circuitry implementations may include discrete analog and / or digital components, for example, integrated as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs). Some implementations may also additionally or alternatively include digital signal processors (DSPs), which are dedicated microprocessors with an architecture optimized for the digital signal processing operational requirements of the functions disclosed herein. Similarly, various components or sub-components within each module can be implemented using software, hardware, or firmware. Connections between modules and / or between components within a module can be provided using any connection method and medium known in the art, including but not limited to communication via the Internet, wired, or wireless networks using appropriate protocols.

[0112] While this document contains numerous specific details, these should not be construed as limiting the scope of the claimed invention or the scope that may be claimed, but rather as a description of features of particular embodiments. Certain features described in the context of individual embodiments in this document may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, while features may be described above as functioning in certain combinations, or even initially claimed as such combinations, in some cases one or more features from the claimed combination may be removed from that combination, and the claimed combination may refer to a sub-combination or a variation of a sub-combination. Similarly, although operations are depicted in a specific order in the drawings, this should not be construed as requiring these operations to be performed in the specific order shown or sequentially, or requiring all shown operations to achieve the desired result.

[0113] Only a few implementation methods and examples have been described, and other implementation methods, functional enhancements and variations can be designed based on what is described and shown in this disclosure.

Claims

1. A wireless communication method, characterized in that, The wireless communication method includes: Reports generated or updated by wireless devices for subsequent mobility processes; and The report is sent to the network nodes.

2. A wireless communication method, characterized in that, The wireless communication method includes: The network node receives reports from the wireless device for subsequent mobility procedures; and Data or control signaling is sent based on the report. The wireless device is configured to generate or update the report before the network node receives the report.

3. The method according to claim 1 or 2, characterized in that, The report includes indications of the association between the report and the subsequent mobility process.

4. The method according to claim 1 or 2, characterized in that: When an existing report is associated with a configuration that triggers the generation or updating of the report, the report is merged with the existing report; Otherwise, the existing report is overridden by the report mentioned above.

5. The method according to claim 1 or 2, characterized in that, The reports used for the subsequent mobility process are independent of the reports for other mobility configurations.

6. The method according to claim 5, characterized in that: When an existing report is associated with a configuration that triggers the generation or updating of the report, the report is merged with the existing report; Otherwise, the existing report is overridden by the report mentioned above.

7. The method according to any one of claims 1 to 6, characterized in that, The subsequent mobility process includes a subsequent conditional handover process, and the report includes a successful handover report.

8. The method according to claim 7, characterized in that, The report includes at least one of the following: When a change or addition of the primary cell (PSCell) of a secondary cell group is successfully executed, the last measurement results obtained from the neighboring New Radio (NR) cell are based on the configuration of the initiating node. When a successful change or addition of a PSCell triggers the report, the identifier of the primary cell (PCell) of the primary cell group connected to the wireless device; Whether the secondary node (SN) initiated an instruction to trigger the report; The reason for generating or updating the report; The source PSCell for successful changes or additions to PSCell; The last measurement result obtained from the source PSCell when a PSCell is successfully changed or added; Successful modification or addition of a target PSCell; The final measurement result obtained in the target PSCell when the PSCell is successfully changed or added; and The time elapsed between initiating the last conditional reconfiguration for the target PSCell and receiving the latest conditional reconfiguration for the target PSCell.

9. The method according to claim 7, characterized in that, The report is a conventional report associated with the subsequent condition handover process, and the indication for generating or updating the report is carried in a Radio Resource Control (RRC) message or a Media Access Control (MAC) control element (CE).

10. The method according to claim 9, characterized in that, The wireless device is configured to send the instruction when the report is generated or updated.

11. The method according to any one of claims 7 to 10, characterized in that, The successful switchover report is the PSCell Successful Change Report (SPR), and the subsequent conditional switchover process is the Conditional PSCell Addition or Change (CPAC).

12. The method according to any one of claims 1 to 6, characterized in that, The subsequent mobility process includes a subsequent low-level triggered mobility process, and the report includes a radio link failure report or a successful handover report.

13. The method according to claim 12, characterized in that, The radio link failure report is a radio link failure (RLF) report, the successful handover report is a successful handover report (SHR), and the subsequent lower layer triggered mobility process is a layer 1 / layer 2 (L1 / L2) triggered mobility (LTM) process.

14. The method according to any one of claims 1 to 6, characterized in that, The subsequent mobility process includes a subsequent low-level triggered mobility process configured for the secondary cell group, and the report includes a successful cell handover report.

15. The method according to claim 14, characterized in that, The successful cell handover report is a PSCell Successful Change Report (SPR), and the subsequent low-level mobility triggering procedure configured for the secondary cell group is the Layer 1 / Layer 2 (L1 / L2) Mobility Triggering (LTM) procedure configured for the secondary cell group (SCG).

16. A wireless communication method, characterized in that, The wireless communication method includes: The wireless device sends mobility history information to the network node, wherein the mobility history information includes one or more service characteristics and activation / deactivation information.

17. A wireless communication method, characterized in that, The wireless communication method includes: The network node receives mobility history information from the wireless device, wherein the mobility history information includes one or more service characteristics and activation / deactivation information; and Data or control signaling is sent based on the mobility history information.

18. The method according to claim 16 or 17, characterized in that, The one or more business characteristics include at least one of the following: The data rate of the secondary cell group (SCG) during at least one active time; or The amount of data in the SCG during the at least one activation time.

19. The method according to claim 18, characterized in that, The data rate is based on the average uplink (UL) data rate or the average downlink (DL) data rate, and the data volume is based on the uplink (UL) data volume or downlink (DL) data volume during the at least one activation time.

20. A wireless communication device, characterized in that, The device includes one or more processors and is configured to implement the method of one or more of claims 1 to 19.

21. A non-transitory computer-readable program storage medium, characterized in that, The storage medium stores code that, when executed by at least one processor, causes the at least one processor to implement the method of one or more of claims 1 to 19.

Images