Computer-readable medium and method of operating a base station

Abstract

This application relates to devices and components, including apparatuses, systems, and methods for mobility optimization based on user equipment (UE), including machine learning (ML) assisted techniques, as described herein.

Description

Technical Field

[0001] This disclosure relates in its entirety to handover and / or measurement configurations based on anticipated UE mobility. Background Technology

[0002] The 3GPP Technical Specifications (TS) define the standards for wireless networks. These TSs describe aspects related to mobility for operations within such networks. Summary of the Invention

[0003] According to one aspect of this disclosure, one or more computer-readable media are provided, the one or more computer-readable media having instructions that, when executed by one or more processors, cause a user-equipped UE to: identify a candidate target cell based on stored knowledge of a cell used by the UE; send a first message identifying the candidate target cell; and receive a command to perform a reconfiguration of a Radio Resource Control (RRC) connection, wherein the command to perform the reconfiguration identifies the candidate target cell, wherein the candidate target cell is one of a plurality of candidate target cells identified in the first message, and wherein for each of the plurality of candidate target cells, the first message includes a corresponding weight.

[0004] According to another aspect of this disclosure, a method for operating a base station is provided, the method comprising: receiving from a user equipment (UE) a first message identifying a target cell as a proposed candidate for handover; and based on the first message, generating a command for performing a reconfiguration of a Radio Resource Control (RRC) connection for the UE, wherein the command for performing the reconfiguration identifies the target cell, wherein the target cell is one of a plurality of target cells identified as proposed candidates for handover in the first message, and wherein for each of the plurality of target cells, the first message includes a corresponding weight. Attached Figure Description

[0005] Figure 1 A network environment according to some implementation schemes is shown.

[0006] Figure 2 An exemplary call flow according to some implementation schemes is shown.

[0007] Figure 3 An example of an Abstract Syntax Marker 1 (ASN.1) signaling description according to some implementation schemes is shown.

[0008] Figure 4 An exemplary call flow according to some implementation schemes is shown.

[0009] Figure 5 It shows Figure 4 The call process continues.

[0010] Figure 6 An example of an ASN.1 signaling description according to some implementation schemes is shown.

[0011] Figure 7 A diagram illustrating the functional framework of Radio Access Network (RAN) intelligence is shown.

[0012] Figure 8 The operational flow / algorithm structure according to some implementation schemes is shown.

[0013] Figure 9 The operational flow / algorithm structure according to some implementation schemes is shown.

[0014] Figure 10 The operational flow / algorithm structure according to some implementation schemes is shown.

[0015] Figure 11 The operational flow / algorithm structure according to some implementation schemes is shown.

[0016] Figure 12 A beamforming component of a device according to some embodiments is shown.

[0017] Figure 13 User equipment according to some implementation schemes is shown.

[0018] Figure 14 A base station according to some implementation schemes is shown. Detailed Implementation

[0019] The following detailed description relates to the accompanying drawings. The same reference numerals may be used in different drawings to identify the same or similar elements. In the following description, specific details, such as particular structures, architectures, interfaces, technologies, etc., are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the embodiments. However, it will be apparent to those skilled in the art that various aspects of the embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrase "A or B" means (A), (B), or (A and B). For the purposes of this document, the phrase "A based on B" means "A is at least based on B".

[0020] The following is a glossary of terms that may be used in this disclosure.

[0021] As used herein, the term "circuit" refers to, is part of, or includes the following: hardware components such as electronic circuits, logic circuits, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-chips (SoCs)), digital signal processors (DSPs), etc. In some embodiments, a circuit may execute one or more software or firmware programs to provide at least some of the said functions. The term "circuit" may also refer to a combination of one or more hardware elements and program code for performing the functions (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0022] As used herein, the term "processor circuit" means, is part of, or includes the following: a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0023] As used herein, the term "interface circuit" refers to, is part of, or includes a circuit that enables the exchange of information between two or more components or devices. The term "interface circuit" can refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, network interface cards, etc.

[0024] As used herein, the term "user equipment" or "UE" refers to equipment of a remote user that has radio communication capabilities and can describe network resources in a communication network. Furthermore, the term "user equipment" or "UE" can be considered synonymous and can be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Additionally, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0025] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to the various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0026] As used herein, the term "resource" refers to physical or virtual devices, physical or virtual components within a computing environment, or physical or virtual components within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power supply, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, databases and applications, units of workload, etc. "Hardware resource" can refer to computing, storage, or networking resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or networking resources provided by virtualization infrastructure to applications, devices, systems, etc. The terms "network resource" or "communication resource" can refer to resources that computer equipment / systems can access via a communication network. The term "system resource" can refer to any kind of shared entity providing services and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0027] As used herein, the term "channel" refers to any tangible or intangible transmission medium used for transmitting data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a path or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices used for transmitting and receiving information.

[0028] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0029] The term “connection” can mean that two or more elements at a common communication protocol layer have an established signaling relationship with each other through a communication channel, link, interface, or reference point. The term “obtain” is used to indicate any of its common meanings, such as calculation, derivation, (e.g., from another element or device) receiving and / or (e.g., from a memory / storage device as described below) retrieval.

[0030] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as networked computers, network hardware, network equipment, network nodes, virtualized network functions, etc.

[0031] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0032] This paper describes techniques for user equipment (UE)-based mobility optimization, including machine learning (ML)-assisted techniques. Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include a UE 104 and one or more access nodes, such as, for example, access nodes 108 and 112. UE 104 may communicate with access nodes 108 and 112 via a 3GPP TS-compatible air interface (e.g., via an NR-Uu interface) that defines standards for Long Term Evolution (LTE) or Fifth Generation (5G) New Radio (NR) systems. Each access node 108 and 112 may provide one or more 5G NR cells to provide NR user plane and control plane protocol termination to UE 104. Each access node 108, 112 may be a base station such as a Next Generation Node B (gNB), or may be controlled by it.

[0033] As described in the embodiments herein, access node 108 can provide the serving cell to which UE 104 is initially communicatively coupled, and access node 112 can provide the target cell. UE 104 and access nodes 108 / 112 can cooperate to hand over UE 104's communication session from the serving cell to the target cell (e.g., according to a predefined handover (HO) procedure) in order to maintain UE 104's connectivity to the network.

[0034] In some implementations, access node 112 may be a neighboring base station providing coverage for adjacent geographical locations. In this implementation, access node 112 may provide neighboring cells that operate independently and differently from the serving cell.

[0035] In some implementations, access node 108 may be one of multiple access nodes providing services to UE 104 via dual connectivity (DC) operation. Access nodes may be coupled to each other via an X2 interface through ideal or non-ideal backhaul. Access nodes may include a primary node (MN) to provide control plane connectivity to the core network. The MN may be associated with a serving cell group called a primary cell group (MCG). Access nodes may also include secondary nodes (SNs), which may not have control plane connectivity to the core network. SNs may be used to provide additional resources to UE 104. SNs may be associated with a serving cell group called a secondary cell group (SCG). In these implementations, access node 108 may represent a first SN providing the primary cell (PSCell) of the SCG, and access node 112 may represent a second SN. Handover may then involve UE 104 transferring the PSCell from the first SN to the second SN.

[0036] Access node 108 can transmit information (e.g., data and control signaling) in the downlink direction by mapping logical channels onto transport channels and transport channels onto physical channels. Logical channels can transmit data between the Radio Link Control (RLC) layer and the Media Access Control (MAC) layer; transport channels can transmit data between the MAC and PHY layers; and physical channels can transmit information across the air interface.

[0037] UE 104 can communicate with access nodes 108 / 112 via frequency bands in frequency range 1 (FR1) or frequency range 2 (FR2). For FR1 (e.g., below 7.225 GHz), the transmit antenna of UE 104 is typically implemented as an omnidirectional antenna. For FR2 (e.g., 24.250 GHz and above, also known as mmWave), the transmit antenna of UE 104 can be implemented as a panel with multiple antenna elements. For example, the multiple antenna elements of the panel can be driven as a phased array (e.g., to guide a beam in a desired direction).

[0038] Predictions of UE mobility can help optimize handover (HO) preparation and / or measurement configuration. For example, predicting the best future cell candidate for an HO (or predicting multiple suggested candidate cells for an HO) can help reduce the incidence of HO failures. For example, predicting the visibility of certain measurement objects can help reduce UE power consumption.

[0039] In theory, UE mobility prediction can be performed either in the gNB or in the UE. Network-based prediction avoids standardization issues (e.g., it can be performed without additional data transmission between the UE and the network). However, network-based prediction may also have some drawbacks. For example, the collection of UE mobility information within the network may raise privacy concerns, and it may be expected that the gNB cannot associate Cell Radio Network Temporary Identifiers (C-RNTIs) belonging to the same UE. For these reasons, network-based prediction schemes may be limited to a general model applicable to all UEs, which may lack easily optimized scenarios (e.g., users traveling along the same path to work every workday).

[0040] In contrast, UE-based trained mobility prediction models can be UE-specific and therefore more accurate, while also protecting user privacy. It may be desirable to use machine learning (ML) to predict UE mobility, and the techniques disclosed herein include 3GPP-based UE mobility optimization using machine learning (ML), which can be implemented at one or more higher layers of the control plane protocol stack (e.g., at the Radio Resource Control (RRC) layer). For example, the UE may include an ML model trained to predict one or more next best candidate cells and / or beams, and the UE may inform the network about the most likely cell and / or beam candidates. Potential benefits of training models in the UE may include protecting user privacy and / or obtaining trained models that are more accurately tailored to the mobility patterns of that particular user.

[0041] However, since mobility in NR is controlled by the network, UE-based prediction schemes may require some standard modifications to allow the UE to inform the network of the prediction (e.g., best target cell candidate). Such predictions can be applied to regular HO, conditional HO (CHO), beam mobility, beam failure prediction, and / or dual connectivity (DC).

[0042] In a standard home HO procedure (also known as a “baseline HO”), the HO is controlled by the network (e.g., the network indicates when a handover will occur and to which target cell). If the UE can predict the next one or more target cells, it can inform the network of this prediction. The network can then take this information into account when determining the target cell for the HO, thereby selecting a potentially better target cell. Potential advantages of this approach may include mobility robustness (e.g., a reduction in the number of HO failures).

[0043] Figure 2An example of a call flow in which UE-based prediction is incorporated into the HO procedure as described above is shown. In this example, UE-based prediction is incorporated into the gNB handover procedure (e.g., as in 3GPP TS 38.300, “5G; NR; NR and NG-RAN Overall description; Stage-2”, v16.5.0 (2021-04)). Figure 9 As shown in .2.3.1-1.

[0044] At phase 0 of the call flow, the UE notifies the network of its prediction of the next or more target cells. For example, the UE can notify the network by sending the cell identifiers of the predicted next or more target cells to the source gNB within a supplementary message, which can be a Radio Resource Control (RRC) message. UE Assistance Information A message (such as described in Clause 6.2.2 (“Message Definition”) below: 3GPP TS 38.331 (“5G; NR; Radio Resource Control (RRC); Protocol specification”), V16.4.1 (2021-04)) is an example of an auxiliary message that a UE may use to indicate UE auxiliary information to the network. In other implementations, the UE may use different messages to inform the network of its predictions for one or more target cells.

[0045] exist Figure 2 In the specific example shown, the UE uses UE Assistance Information RRC messages are used to send predictions for one or more target cells to the source gNB. Figure 3 An example of an abstract syntax marker-1 (ASN.1) signaling description that can be incorporated into such a message is shown. In practice, the string "v1xyz" shown in this example can be replaced with a specific version number of the specification in which the implementation is introduced (e.g., "v1710" for version 17.1.0). Figure 3 As shown, UE Assistance Information This example of an RRC message includes one with candidateBestTargetCell Fields mobility Assistance Information element (IE), in which candidateBestTargetCell The value of this field indicates the physical cell ID of the target cell.

[0046] exist Figure 3In the example, the UE indicates the candidate target cell by using the Physical Cell Identifier (PCI) of the candidate target cell. Alternatively or additionally, the UE may indicate the candidate target cell by using one or more other identifiers (e.g., NR Cell Identifier (NCI), NR Cell Global Identifier (NCGI)) (e.g., in auxiliary messages such as...). UE Assistance Information (within the message). Additionally or alternatively, the UE may report (e.g., in auxiliary messages such as...) UE Assistance Information (Within the message) Two or more candidate target cells. In this case, the report may also include a weight for each identified candidate target cell, where the weight may indicate, for example, the likelihood of a candidate's HO success.

[0047] In such Figure 2 In phase 1 of the call flow shown, the source gNB initiates a handover procedure by sending a handover request to the target gNB (e.g., via the Xn interface). The target gNB can be a candidate target cell, as indicated by the UE to the source gNB in ​​phase 0. In phase 2, the target gNB provides a handover request confirmation including the new RRC configuration. In phase 3, the source gNB completes the handover procedure by sending a handover request confirmation received in the handover request confirmation. RRC Reconfiguration The message is forwarded to the UE to instruct it to reconfigure the RRC connection. At phase 4, the UE moves the RRC connection to the target gNB and... RRC Reconfiguration Complete A message is sent to the target gNB to confirm the reconfiguration.

[0048] Conditional Handover (CHO) was introduced in 3GPP NR Release 16 to improve the mobility robustness and reliability of the baseline HO procedure. In a CHO procedure, Access Node 108 can pre-configure handover assistance information about one or more candidate cells for UE 104 and can provide information about UE 104 to each of these candidate cells. UE 104 can then monitor link quality for various handover execution conditions, and if a specified condition is detected, it performs a handover to a target cell selected from the candidate cells without requiring an explicit handover command from Access Node 108. When the handover execution conditions are met and UE 104 can directly perform a handover to the target cell, the serving cell does not need to be notified.

[0049] In a CHO procedure, the network configures a list of one or more candidate cells and associated handover execution conditions to the UE. The network also “prepares” a target cell by reserving resources for a possible handover for the UE in each target cell, which can consume significant network resources (if many target cells are configured). A CHO can also impose costs on the UE (e.g., by increasing the number of cells it expects to measure). If the UE can predict its mobility, it can inform the network which candidate target cells are unlikely to be used, allowing the network to release resources in those cells and / or allow the UE to abort measurements in those cells. Additionally or alternatively, if the UE can predict its mobility, it can suggest new candidate target cells to the network (e.g., in addition to those included in the list provided by the network), allowing the network to prepare (and configure in the UE) cells more likely to be used for handover.

[0050] As in the baseline HO procedure described above, the UE can notify the network of its prediction of one or more target cells by sending the cell identifiers of the predicted next target cells to the source gNB within an auxiliary message, which can be a Radio Resource Control (RRC) message. (See above, for example, reference...) Figure 2 and / or Figure 3 The above is described UE Assistance Information A message is an example of an auxiliary message that a UE can use to indicate UE auxiliary information to the network.

[0051] In another example, the UE can notify the network of its prediction of one or more target cells by sending the cell identifiers of the predicted next target cells to the source gNB within an acknowledgment message. This acknowledgment message could be sent from the UE to the network... RRC Reconfiguration Complete Messages (such as those described in Clause 6.2.2 of 3GPP TS 38.331, V16.4.1 (2021-04)). Such messages may include a list of “recommended target cells” that the network can use for subsequent CHO (re)configuration. Additionally or alternatively, such messages may include a list of “rejected target cells” (e.g., in a list provided by the network). Cond Reconfig To Add Mod List In addition to the field, the field may include in RRC Reconfiguration message Conditional Reconfiguration (In IE). If the network accepts the UE's recommendation, it can prepare a new target cell and / or release resources in a previously prepared target cell that is no longer needed, and the network can send a new CHO configuration to the UE. As mentioned above, PCI, NR cell global identifier, or other identifiers can be used to identify the recommended or rejected target cell. Potential advantages of this UE-assisted CHO procedure may include more optimized network resource utilization and / or increased mobility robustness.

[0052] Figure 4An example of a call flow in which UE-based prediction is incorporated into the CHO procedure as described above is shown. In this example, UE-based prediction is incorporated into a CHO procedure such as 3GPP TS 38.300 v16.5.0 (2021-04). Figure 9 In the CHO procedure shown in .2.3.2.1-1 (“Intra-AMF / UPF Handover”). Figure 5 It shows [[ID=I43]]Figure 4 The continuation of the call flow, which includes, for example: Figure 4 The call flow shown is the same as stages 5 to 7.3, and also includes subsequent operations such as handover execution and handover completion.

[0053] In such Figure 4 In phase 2 of the call flow shown, the source gNB decides to initiate a CHO procedure (e.g., based on measurement control information sent by the source gNB to the UE and the measurement report received by the source gNB from the UE in phase 1). In phase 3, the source gNB issues a handover request (e.g., via the Xn interface) to each of the one or more target gNBs, requesting the target gNBs to reserve resources for a potential handover of the UE. In phase 5, each target gNB provides a handover request confirmation to the source gNB. In phase 6, the source gNB, through... RRC Reconfiguration In the message (for example, in RRC Reconfiguration message Conditional Reconfiguration IE Cond Reconfig To Add Mod List The field provides the UE with a list of candidate cells and associated handover execution conditions to command the UE to perform RRC connection reconfiguration.

[0054] At stage 7, the UE will... RRC Reconfiguration Complete A message is sent to the source gNB in ​​response to the conditional reconfiguration command. As described above, such a message may include a list of "suggested target cells" and / or a list of "rejected target cells" that the network can use for subsequent CHO (re)configuration. In either case, the message may also include a weight for each identified target cell, where the weight may indicate, for example, the likelihood of a successful HO for the target cell. For cases where the message identifies one or more rejected target cells to which the source gNB has already sent a handover request in Phase 3, the source gNB may send a conditional handover cancellation to the target cell in Phase 7.1 (e.g., to release reserved resources in that cell). At Phase 7.2, the source gNB... RRC Reconfiguration The message will send a new reconfiguration command to the UE, incorporating one or more predictions from the UE's forecasts (e.g., recommending and / or rejecting target cells). For example, RRC Reconfiguration The message can omit sending the target cell for conditional handover cancellation in phase 7.1. At phase 7.3, the UE will...RRC Reconfiguration Complete A message is sent to the source gNB to confirm the condition reconfiguration.

[0055] exist Figure 4 In the specific example shown, the UE uses RRC Reconfiguration Complete RRC messages are used to send predictions for one or more target cells to the source gNB. Figure 6 An example of an ASN.1 signaling description that can be incorporated into such a message is shown. In practice, the string "v1xyz" shown in this example can be replaced with a specific version number of the specification in which the implementation is introduced (e.g., "v1710" for version 17.1.0). Figure 6 As shown, RRC Reconfiguration Complete This example of an RRC message includes messages with... candidateBestTargetCell Fields mobility Assistance Information element (IE), in which candidateBestTargetCell The value of this field indicates the physical cell ID of the target cell.

[0056] exist Figure 6 In the example, the UE indicates a candidate target cell by using its Physical Cell Identifier (PCI). Additionally or alternatively, the UE may indicate a candidate target cell by using one or more other identifiers (e.g., NR Cell Identifier (NCI), NR Cell Global Identifier (NCGI)) (e.g., in confirmation messages such as...). RRC Reconfiguration Complete (within the message). Additionally or alternatively, the UE may report (e.g., in an acknowledgment message such as...) RRC Reconfiguration Complete (Within the message) Two or more candidate target cells. In this case, the report may also include a weight for each identified candidate target cell, where the weight may indicate, for example, the likelihood of a candidate's HO success.

[0057] like Figure 6 As shown, RRC Reconfiguration Complete This example of an RRC message also includes cond Mobility Assistance Information elements (IE), which may include rejected Cells List Fields and / or suggested Cells List Fields. Each of these fields may include a corresponding cell identifier (such as PCI, NCI, and / or NCGI) indicating one or more candidate cells. Candidate Cell List Data elements. In this case, the list may also include a weight for each identified candidate cell, where the weight may indicate, for example, the likelihood of a candidate's HO success.

[0058] As a supplement to or alternative to the baseline HO and / or CHO optimizations described above, predictions of UE mobility can aid in measurement optimization. This includes historically-based predictions of transmission from the UE to the network (e.g., using auxiliary messages such as those referenced above). Figure 3 The aforementionedUE Assistance Information Messaging can also be used for measurement optimization. For example, a network can use UE-based predictions of visibility into certain measurement objects to optimize measurement configuration by configuring only the best candidate cells (e.g., the candidate cells most likely to be measured by the UE) for the UE to measure. By performing predictions only within the UE, the information on which the predictions are based remains confidential within the UE, and user privacy is protected.

[0059] For example, a measurement framework can be implemented that allows the network to configure a set of measurement objects (e.g., frequencies, cells, and / or beams to be measured) and measurement reporting configurations (e.g., periodic, conditionally or event-triggered, etc.) to the UE. In one example, the network can perform a reconfiguration of the RRC connection by sending a command to the UE that can specify the measurement objects and reporting configurations (e.g., report triggering conditions). RRC Reconfiguration The UE executes measurement configurations using messages. It can perform measurements on configured measurement objects (e.g., frequency, cell, and / or beam) and report the measurement results to the network when reporting conditions are met.

[0060] Such a measurement framework can be implemented to include UE-based mobility information. For example, after the network configures the UE for measurement as described above, the UE can send auxiliary information based on the history of the measurement objects used (e.g., in the form of a list of one or more rejected measurement objects and / or a list of one or more suggested measurement objects) to the network. By generating the auxiliary information entirely within the UE, the mobility information from which the auxiliary information is derived remains confidential, and user privacy is protected. The UE can also use auxiliary messages (e.g., as referenced above) Figure 3 The aforementioned UE Assistance Information In the message and / or in the confirmation message (e.g., as referenced above) Figure 6 The aforementioned RRC Reconfiguration Complete This auxiliary information can be sent in a message. In one example, the UE can use an auxiliary message (e.g., as referenced above) to send such information. Figure 3 The aforementioned UE Assistance Information The UE may use a confirmation message to indicate to the network that it is unlikely to be within the coverage area of ​​some of the configured frequencies, beams, and / or cells (e.g., a list of one or more rejected measurement targets). Additionally or alternatively, the UE may use a confirmation message (e.g., as referenced above). Figure 6 The aforementioned RRCReconfigurationComplete (Message) to indicate to the network that it is unlikely to be within the coverage of some of the configured frequencies, beams and / or cells (e.g., a list of one or more objects to be refused measurement).

[0061] Based on the received auxiliary information, the network can decide to update the measurement configuration. For example, the network can reconfigure different sets of measurement objects to the UE (e.g., using commands such as those for reconfiguring RRC connections). RRCReconfiguration The network updates the measurement configuration using a message. This different set of measurement objects may include one or more measurement objects from the original set. The different set of measurement objects may include one or more measurement objects not included in the original set, and / or may exclude one or more measurement objects included in the original set. Alternatively, the network can update the measurement configuration by indicating one or more measurement objects to be added to the original set and / or one or more measurement objects to be omitted from the original set. If the network omits certain frequencies and / or cells and / or beams from the updated configuration, the amount of measurements to be performed by the UE can be reduced, resulting in power savings for the UE.

[0062] As noted above, in addition to or as an alternative to cell identification, the UE can also predict (and signal to the network) one or more beams that are likely to be the best candidates. For example, the transmission of historical information from the UE to the network (e.g., using auxiliary messages such as those referenced above). Figure 3 The aforementioned UEAssistanceInformation (The message) can also be used for beam fault detection (BFD) optimization.

[0063] A BFD procedure can be implemented, enabling the gNB to configure a BFD reference signal (BFD-RS) to the UE. The BFD-RS can be a Synchronization Signal Block (SSB) and / or a Channel State Information Reference Signal (CSI-RS). The UE can declare a beam fault when the number of beam fault instance indications from the physical layer reaches a configured threshold before the configured timer expires. When a beam fault is declared, the UE can trigger a Beam Fault Recovery (BFR) procedure by initiating a random access procedure, which takes some time and can be costly in terms of network resources.

[0064] BFD procedures can be implemented to include UE-based mobility information. In one example, after BFD-RS is configured by the network, the UE can use auxiliary messages (e.g., as referenced above). Figure 3 The aforementioned UEAssistanceInformation A message may be sent to the network to indicate that it is unlikely to be within the coverage area of ​​some of the configured BFD-RSs (e.g., as described in the reference measurement above). Such a message may include, for example, a list of one or more rejected BFD-RSs (e.g., SSB IDs and / or CSI-RS IDs). Additionally or alternatively, such a message may include, for example, a list of one or more recommended BFD-RSs (e.g., SSB IDs and / or CSI-RS IDs).

[0065] In another example, the UE may determine that the configuration of BFD-RS received from the gNB could lead to a beam failure claim. For example, the UE may determine that it is unlikely to be within the coverage of one or more (possibly all) of the configured BFD-RSs (e.g., based on the history of the BFD-RSs used, such as time series of SSB IDs and / or CSI-RS IDs). Based on this determination, the UE may indicate to the network that a beam failure is "expected" (e.g., using auxiliary messages such as those referenced above). Figure 3 The aforementioned UEAssistanceInformation (Message). In one example, this indication is implemented as a single IE (e.g., a binary tag) of the message. Based on this indication, the network can provide the UE with different configurations of BFD-RS. This prediction-based reconfiguration avoids triggering random access procedures for beam fault recovery, thereby reducing the likelihood of potential service interruptions.

[0066] As mentioned above, model training can be performed within the UE (e.g., to protect user privacy). The problem for training the model can be formulated as time series prediction: for example, predicting the next cell based on past knowledge of UE mobility (e.g., a list of cells used in the past). It might be desirable to implement such a model for time series prediction as a recurrent neural network (RNN) (e.g., a long short-term memory (LSTM) network), but other network models with memory can also be used, or other types of network models (e.g., convolutional neural networks (CNNs)) can also be used.

[0067] The model can work with any of the cell identifiers (PCI, NCI, NCGI) mentioned in this paper, for example. The data can be viewed as a time series of cell identifiers, where the previous n identifiers can be used to predict the identifier (n+1): that is, the next cell identifier for the UE is most likely to be used. Alternatively, the model can be implemented to output a vector of probabilities of multiple cell identifiers (e.g., a list of cell identifiers and their corresponding weights) rather than a single optimal net cell identifier.

[0068] In one example, the training set includes the form "input (PCI1, PCI2, ..., PCI1)". n Output (PCI) n+1 The model can perform inference on a list of the last n cell identifiers based on past knowledge of UE mobility (which may be stored locally in the UE (e.g., in the UE's memory)). The model can then predict the next cell identifier (or a list of the next few cell identifiers with associated probabilities) based on this past knowledge. The past mobility knowledge used by the UE for training and inference is not shared with the network, thus protecting user privacy. The UE only sends the resulting predictions to the network, making the underlying mobility information untraceable by the network. It should be noted that the various techniques described herein (e.g., references to...) Figures 2 to 6The call flow and signaling description shown are not limited to any particular form or model of prediction made by the UE.

[0069] For measurement optimization and / or BFD optimization applications as described herein, the identifiers of the measurement objects used by the UE (e.g., cell ID, frequency, beam identifiers (e.g., SSB ID and / or CSI-RS ID)) can be used to perform model training and inference in the same manner as described above in the reference cell identifier section.

[0070] Figure 7 A diagram illustrating the functional framework of Radio Access Network (RAN) intelligence is provided (e.g., 3GPP Technical Report (TR) 37.817, "3rd Generation Partnership Project; Technical Specification Group RAN; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Study on enhancement for Data Collection for NR and EN-DC (Release 17)" V0.2.0 (2021-05). Figure 4 The method described in .2-1 can be used to implement prediction models within the UE as described herein. As noted above, in one such example, an RNN is used to implement the model.

[0071] Figure 8 An operational flow / algorithm structure 800 according to some implementation schemes is shown. The operational flow / algorithm structure 800 may be executed or implemented by a UE such as, for example, UE 104 or UE 1300; or by components such as baseband processor 1304A.

[0072] The operation flow / algorithm structure 800 may include, at 804, identifying candidate target cells based on stored knowledge of the cells used by the UE. For example, the operation flow / algorithm structure 800 may include using a recurrent neural network (RNN) to indicate candidate target cells based on stored knowledge. The RNN may be, for example, a long short-term memory (LSTM) network.

[0073] The operation flow / algorithm structure 800 may include: at 808, sending a first message identifying the candidate target cell. In one example, the first message is... UEAssistanceInformation Message. In another example, the first message is RRCReconfigurationCompleteThe first message may include information elements that identify the candidate target cell. The first message may identify the candidate target cell by at least one of, for example, Physical Cell ID (PCI), New Radio Interface (NR) Cell Identifier (NCI), or NR Cell Global Identifier (NCGI).

[0074] The operation flow / algorithm structure 800 may include, at 812, receiving a command to perform a reconfiguration of the Radio Resource Control (RRC) connection, wherein the command to perform the reconfiguration may identify a candidate target cell. The command to perform the reconfiguration may be, for example... RRCReconfiguration information.

[0075] The operation procedure / algorithm structure 800 may also include sending a confirmation of reconfiguration completion to the candidate target cell. This confirmation may be, for example... RRCReconfigurationComplete information.

[0076] Figure 9 An operational flow / algorithm structure 900 according to some implementation schemes is shown. The operational flow / algorithm structure 900 may be executed or implemented by a UE such as, for example, UE 104 or UE 1300; or by components thereof such as baseband processor 1304A.

[0077] The operation flow / algorithm structure 900 may include, at 904, receiving a first message identifying the object to be measured. This first message may be a command to perform a reconfiguration of the Radio Resource Control (RRC) connection. The object to be measured may be, for example, a frequency, cell, or beam.

[0078] The operation flow / algorithm structure 900 may include: at 908, based on the first message, generating a second message indicating at least one of a prediction of a fault related to the measured object or a rejection of the measured object. This second message may be based on stored knowledge of the measured object measured by the UE. For an example where the measured object is a Synchronization Signal Block (SSB), the second message may indicate a prediction of a beam fault related to the SSB. The second message may be an auxiliary information message (e.g., UEAssistanceInformation (Message). Additionally or alternatively, a second message may identify the object being measured.

[0079] Figure 10 An operational flow / algorithm structure 1000 according to some implementation schemes is shown. The operational flow / algorithm structure 1000 may be executed or implemented by a base station such as, for example, base station 108 or 1400; or by components thereof such as baseband processor 1404A.

[0080] The operation flow / algorithm structure 1000 may include: at 1004, receiving a first message from the user equipment (UE) identifying the target cell as a proposed candidate for handover. This first message may be an auxiliary information message (e.g., UEAssistanceInformation(Message). The target cell is one of a plurality of target cells identified in the first message. For each of the plurality of target cells, the first message includes a corresponding weight.

[0081] The operation flow / algorithm structure 1000 may include: at 1008, based on the first message, generating a command that causes the UE to perform a reconfiguration of the Radio Resource Control (RRC) connection, wherein the command to perform the reconfiguration identifies the target cell. The command to perform the reconfiguration may be, for example... RRCReconfiguration information.

[0082] The operation flow / algorithm structure 1000 may further include: receiving confirmation from the UE that reconfiguration is complete. Alternatively or otherwise, the operation flow / algorithm structure 1000 may further include: generating a handover request message to the target cell.

[0083] Figure 11 An operational flow / algorithm structure 1100 according to some implementation schemes is shown. The operational flow / algorithm structure 1100 may be executed or implemented by a base station such as, for example, base station 108 or 1400; or by components thereof such as baseband processor 1404A.

[0084] The operation flow / algorithm structure 1100 may include: at 1104, sending a first message to the UE identifying at least one target cell for conditional handover. This first message may be a command to perform a reconfiguration of the Radio Resource Control (RRC) connection. For example, the first message may be... RRCReconfiguration information.

[0085] The operation flow / algorithm structure 1100 may include: at 1108, receiving a second message identifying the target cell from the UE. This second message may be... RRCReconfigurationComplete information.

[0086] The operation process / algorithm structure 1100 may include: at 1112, sending a handover cancellation message to the target cell based on the second message.

[0087] The operation flow / algorithm structure 1100 may also include: sending a command to the UE, based on the second message, to perform a reconfiguration of the RRC connection (e.g., RRCReconfiguration In this case, the operation flow / algorithm structure 1100 may also include: receiving confirmation from the UE that the reconfiguration is complete (e.g., message). RRCReconfigurationComplete information).

[0088] Figure 12A receiving component 1200 of a device according to some embodiments is shown. The device may be a UE 104 or an access node 108 or 112. The receiving component 1200 may include a first antenna panel, namely panel 1 1204, and a second antenna panel, namely panel 2 1208. Each antenna panel may include multiple antenna elements.

[0089] Antenna panels can be coupled to corresponding analog beamforming (BF) components. For example, panel 1 1204 can be coupled to analog BF component 1212, and panel 2 1208 can be coupled to analog BF component 1216.

[0090] The analog baseband (BF) component can be coupled to one or more radio frequency (RF) chains. For example, analog BF component 1212 can be coupled to one or more RF chains 1220, and analog BF component 1216 can be coupled to one or more RF chains 1224. The RF chains can amplify the received analog RF signal, down-convert the RF signal to baseband, and convert the analog baseband signal into a digital baseband signal that can be provided to digital BF component 1228. Digital BF component 1228 can provide baseband (BB) signals for further baseband (BB) processing.

[0091] In various implementations, control circuitry residing in the baseband processor can provide BF weights to the analog / digital BF components to provide a received beam at the corresponding antenna panel. These BF weights can be determined by the control circuitry based on a received reference signal and corresponding QCL / TCI information as described herein. In some implementations, the BF weights can be phase shift values ​​provided to the phase shifter of the analog BF component 1212 or complex weights provided to the digital BF component 1228. In some implementations, the BF components and antenna panels can operate together to provide a dynamic phased array capable of guiding the beam in a desired direction.

[0092] In various implementations, beamforming can include analog beamforming, purely digital beamforming, or a hybrid analog-digital beamforming. Digital beamforming can utilize separate RF chains, each corresponding to an antenna element.

[0093] While beamforming component 1200 describes receive beamforming, other embodiments may include beamforming components that perform transmit beamforming in a similar manner.

[0094] Figure 13 A UE 1300 according to some implementation schemes is shown. UE 1300 may be similar to Figure 1 The UE 104 is essentially interchangeable with it.

[0095] UE 1300 can be any mobile or non-mobile computing device, such as, for example, mobile phones, computers, tablets, industrial wireless sensors (e.g., microphones, carbon dioxide sensors, pressure sensors, humidity sensors, thermometers, motion sensors, accelerometers, laser scanners, fluid level sensors, stock sensors, voltmeters / ammeters, actuators, etc.), video surveillance / monitoring devices (e.g., cameras, camcorders, etc.), wearable devices (e.g., smartwatches), and loosely coupled IoT devices.

[0096] UE 1300 may include a processor 1304, RF interface circuitry 1308, memory / storage device 1312, user interface 1316, sensor 1320, drive circuitry 1322, power management integrated circuit (PMIC) 1324, antenna structure 1326, and battery 1328. Components of UE 1300 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 13 The block diagram is intended to show a high-level view of some of the components of the UE 1300. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0097] Components of UE 1300 can be coupled to various other components via one or more interconnects 1332, which can represent any type of interface, input / output, bus (local, system, or extended), transmission line, trace, optical connector, etc., that allows various circuit components (on common or different chips or chipsets) to interact with each other.

[0098] Processor 1304 may include processor circuitry such as baseband processor circuitry (BB) 1304A, central processing unit circuitry (CPU) 1304B, and graphics processing unit circuitry (GPU) 1304C. Processor 1304 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions, such as program code, software modules, or functional processes from memory / storage device 1312, to cause UE 1300 to perform the operations described herein.

[0099] In some implementations, the baseband processor circuit 1304A can access the communication protocol stack 1336 in the memory / storage device 1312 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 1304A can access the communication protocol stack to perform user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access layers. In some implementations, PHY layer operation may additionally / optionally be performed by components of the RF interface circuit 1308.

[0100] The baseband processor circuit 1304A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (“CP-OFDM”) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (“DFT-S-OFDM”) in the uplink.

[0101] Memory / storage device 1312 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 1336) that can be executed by one or more processors in processor 1304 to cause UE 1300 to perform the various operations described herein. Memory / storage device 1312 includes any type of volatile or non-volatile memory that can be distributed throughout UE 1300. In some embodiments, some memory / storage devices in memory / storage device 1312 may be located on processor 1304 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 1312 may be located external to processor 1304 but accessible via a memory interface. Memory / storage device 1312 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0102] RF interface circuitry 1308 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows UE 1300 to communicate with other devices via a radio access network. RF interface circuitry 1308 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0103] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 1326 and continue to filter and amplify the signal (using a low-noise amplifier). This signal can be provided to the receiver of the transceiver, which downconverts the RF signal into a baseband signal that is provided to the baseband processor of processor 1304.

[0104] In the transmission path, the transceiver's transmitter upconverts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM amplifies the RF signal using a power amplifier before it is radiated across the air interface via antenna 1326.

[0105] In various implementations, the RF interface circuit 1308 can be configured to transmit / receive signals in a manner compatible with NR access technology.

[0106] Antenna 1326 may include antenna elements to convert electrical signals into radio waves for propagation through the air and to convert received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna 1326 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input / multiple-output communication. Antenna 1326 may include microstrip antennas, printed antennas fabricated on the surface of one or more printed circuit boards, patch antennas, phased array antennas, etc. Antenna 1326 may have one or more panels designed for a specific frequency band included in FR1 or FR2.

[0107] User interface circuitry 1316 includes various input / output (I / O) devices designed to enable users to interact with UE 1300. User interface circuitry 1316 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, a headset, etc. Output device circuitry includes any physical or virtual means for displaying information or otherwise conveying information, such as sensor readings, actuator positions, or other similar information. Output device circuitry may include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators, such as light-emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touchscreens (e.g., liquid crystal displays, LED displays, quantum dot displays, projectors, etc.), wherein the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of UE 1300.

[0108] Sensor 1320 may include devices, modules, or subsystems intended to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including triaxial accelerometers, triaxial gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; etc.

[0109] The driving circuitry 1322 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the UE 1300. The driving circuitry 1322 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may exist within or be connected to the UE 1300. For example, the driving circuitry 1322 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings of the sensor circuitry 1320 and controlling and allowing access to the sensor circuitry 1320; a driver for acquiring actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0110] The PMIC 1324 manages the power supplied to various components of the UE 1300. Specifically, relative to the processor 1304, the PMIC 1324 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0111] In some implementations, the PMIC 1324 may control or otherwise incorporate various power-saving mechanisms of the UE 1300, including DRX, as discussed herein.

[0112] Battery 1328 can power UE 1300, but in some examples, UE 1300 may be installed in a fixed location and may have a power source coupled to the grid. Battery 1328 may be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 1328 may be a typical lead-acid automotive battery.

[0113] Figure 14 An access node 1400 (e.g., a base station or gNB) according to some embodiments is shown. Access node 1400 may be similar to access node 108 and is substantially interchangeable with it.

[0114] Access node 1400 may include processor 1404, RF interface circuit 1408, core network (CN) interface circuit 1412, memory / storage device circuit 1416 and antenna structure 1426.

[0115] The components of access node 1400 can be coupled to various other components via one or more interconnectors 1428.

[0116] The processor 1404, RF interface circuit 1408, memory / storage device circuit 1416 (including communication protocol stack 1410), antenna structure 1426, and interconnect 1428 are similar to those in the reference. Figure 13 Similar named elements are shown and described.

[0117] The CN interface circuit 1412 may provide connectivity to a core network (e.g., a 5GC using a 5G core network (5GC) compatible network interface protocol, such as Carrier Ethernet, or some other suitable protocol). Network connectivity may be provided to / from access node 1400 via fiber optic or wireless backhaul. The CN interface circuit 1412 may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface circuit 1412 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0118] As described above, one aspect of the present invention is the collection and use of data available from specific and legitimate sources for mobility optimization. This disclosure envisions that, in some instances, the collected data may include personal information data that uniquely identifies or can be used to identify a specific person. Such personal information data may include demographic data, location-based data, online identifiers, telephone numbers, email addresses, home addresses, data or records related to a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other personal information.

[0119] This disclosure recognizes that the use of such personal information data in the techniques of this invention can benefit users. For example, personal information data can be used to reduce the incidence of handover failures.

[0120] This disclosure assumes that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information data will comply with established privacy policies and / or privacy practices. Specifically, it is expected that such entities will implement and consistently apply privacy practices generally recognized as meeting or exceeding industry or governmental requirements for protecting user privacy. Such information regarding the use of personal data should be highlighted and easily accessible to users, and should be updated as the collection and / or use of data changes. Users' personal information should be collected only for lawful use. Furthermore, such collection / sharing should only occur after receiving user consent or other lawful grounds provided for in applicable law. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data and ensure that others with access to personal information data comply with their privacy policies and processes. Additionally, such entities may be subject to third-party assessments to demonstrate their compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific types of personal information data collected and / or accessed, and made applicable to applicable laws and standards, including jurisdiction-specific considerations that may be used to impose higher standards. For example, in the United States, the collection or access to certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly.

[0121] Regardless of the foregoing, this disclosure also contemplates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure contemplates providing hardware and / or software components to prevent or block access to such personal information data. For example, the technology of this invention can be configured to allow users to opt-in or opt-out at any time during or after registering for the service, participating in the collection of mobility data. As another example, users can choose to limit the length of time mobility-related data is retained, or completely block the development of historical mobility prediction models. In addition to providing "opt-in" and "opt-out" options, this disclosure envisions providing notifications related to access to or use of personal information. For example, users may be notified that historical mobility predictions will be provided to the network.

[0122] Furthermore, the purpose of this disclosure is to manage and process personal information data to minimize the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by limiting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, by removing identifiers, controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods such as differentiated privacy.

[0123] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not be rendered inoperable due to the absence of all or part of such personal information data. For example, content can be selected and delivered to the user based on aggregated non-personal information data or an absolute minimum amount of personal information, such as content processed only on the user's device or other non-personal information that can be used for content delivery services.

[0124] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods as described in the Examples section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. Similarly, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0125] Example

[0126] Further exemplary implementations are provided in the following sections.

[0127] Example 1 includes one or more computer-readable media having instructions that, when executed by one or more processors, cause a UE to: identify a candidate target cell based on stored knowledge of a cell used by the UE; send a first message identifying the candidate target cell; and receive a command to perform a reconfiguration of an RRC connection, wherein the command to perform the reconfiguration identifies the candidate target cell.

[0128] Example 2 includes one or more computer-readable media according to Example 1 or some other embodiment of this document, wherein the candidate target cell is one of a plurality of candidate target cells identified in a first message, and for each of the plurality of candidate target cells, the first message includes a corresponding weight.

[0129] Example 3 includes one or more computer-readable media according to Example 1 or some other embodiment of this document, wherein the first message includes information elements identifying a candidate target cell.

[0130] Example 4 includes one or more computer-readable media according to Example 1 or some other embodiment herein, wherein the first message identifies a candidate target cell by at least one of PCI, NCI or NCGI.

[0131] Example 5 includes one or more computer-readable media according to Example 1 or some other embodiment of this document, wherein the command to perform reconfiguration is RRCReconfiguration information.

[0132] Example 6 includes one or more computer-readable media according to Example 1 or some other embodiment of this document, wherein the instructions, when executed by one or more processors, further cause the UE to send an acknowledgment of reconfiguration completion to the candidate target cell.

[0133] Example 7 includes one or more computer-readable media according to Example 6 or some other embodiment herein, wherein the confirmation is RRCReconfigurationComplete information.

[0134] Example 8 includes one or more computer-readable media according to any one of Examples 1 to 7 or some other embodiment of this document, wherein the first message is UEAssistanceInformation information.

[0135] Example 9 includes one or more computer-readable media according to any one of Examples 1 to 7 or some other embodiment of this document, wherein the first message is RRCReconfigurationComplete information.

[0136] Example 10 includes one or more computer-readable media according to any one of Examples 1 to 7 or some other embodiment herein, wherein the instructions, when executed by one or more processors, further cause the UE to use an RNN to indicate candidate target cells based on stored knowledge.

[0137] Example 11 includes an apparatus (e.g., a chip or chipset) comprising: a processing circuit for: receiving a first message identifying a measurement object; generating a second message indicating rejection of the measurement object based on the first message; and a memory coupled to the processing circuit for storing knowledge of a measurement object measured by a user equipment, wherein the measurement object includes a frequency, cell, or beam; and the second message is based on the stored knowledge.

[0138] Example 12 includes the apparatus according to Example 11 or some other embodiment herein, wherein the object of measurement includes SSB.

[0139] Example 13 includes the apparatus according to Example 11 or some other embodiment herein, wherein the first message is a command to perform reconfiguration of the RRC connection.

[0140] Example 14 includes the apparatus according to Example 11 or some other embodiment herein, wherein the second message is an auxiliary information message.

[0141] Example 15 includes the apparatus according to any one of Examples 11 to 14 or some other embodiment herein, wherein the second message identifies the object being measured.

[0142] Example 16 includes an apparatus (e.g., a chip or chipset) comprising: processing circuitry configured to: receive a first message identifying a BFD-RS; generate, based on the first message, a second message indicating a prediction of a beam fault associated with the BFD-RS; and a memory coupled to the processing circuitry configured to store knowledge of the BFD-RS used by user equipment, wherein the second message is based on the stored knowledge.

[0143] Example 17 includes the apparatus according to Example 16 or some other embodiment herein, wherein the first message is a command to perform a reconfiguration of the RRC connection.

[0144] Example 18 includes the apparatus according to Example 16 or some other embodiment herein, wherein the second message is an auxiliary information message.

[0145] Example 19 includes the apparatus according to any one of Examples 16 to 18 or some other embodiment herein, wherein the BFD-RS includes an SSB.

[0146] Example 20 includes a method of operating a base station, the method comprising: receiving from a UE a first message identifying a target cell as a proposed candidate for handover; and based on the first message, generating a command that causes the UE to perform a reconfiguration of an RRC connection, wherein the command to perform the reconfiguration identifies the target cell.

[0147] Example 21 includes the method according to Example 20 or some other embodiment of this document, the method further comprising: receiving an acknowledgment from the UE that reconfiguration is complete.

[0148] Example 22 includes the method according to Example 20 or some other embodiment of this document, the method further comprising: generating a handover request message to the target cell.

[0149] Example 23 includes the method according to any one of Examples 20 to 22 or some other embodiment herein, wherein the first message is an auxiliary information message.

[0150] Example 24 includes the method according to any one of Examples 20 to 22 or some other embodiment herein, wherein the target cell is one of a plurality of target cells identified in the first message as proposed candidates for handover.

[0151] Example 25 includes the method according to Example 24 or some other embodiment herein, wherein the command to perform reconfiguration identifies more than one of a plurality of target cells.

[0152] Example 26 includes the method according to Example 24 or some other embodiment herein, wherein for each of a plurality of target cells, the first message includes a corresponding weight.

[0153] Example 27 includes one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by one or more processors, cause the base station to: send a first message to the UE identifying at least one target cell for conditional handover; receive a second message from the UE identifying the target cell; and, based on the second message, send a handover cancellation message to the target cell.

[0154] Example 28 includes one or more computer-readable media according to Example 27 or some other embodiment herein, wherein the first message is a command to perform reconfiguration of the RRC connection.

[0155] Example 29 includes one or more computer-readable media according to Example 27 or some other embodiment herein, wherein the second message is RRCReconfigurationComplete information.

[0156] Example 30 includes one or more computer-readable media according to any one of Examples 27 to 29 or some other embodiment of this document, wherein the instructions, when executed by one or more processors, further cause the base station to send a command to the UE to perform a reconfiguration of the RRC connection based on a second message.

[0157] Example 31 includes one or more computer-readable media according to Example 30 or some other embodiment of this document, the method further comprising: receiving an acknowledgment from the UE that reconfiguration is complete.

[0158] Example 32 may include an apparatus comprising means for performing one or more elements of the method described or associated with any of Examples 1 to 31 or any other method or process described herein.

[0159] Example 33 may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method or any other method or process described herein according to any one of Examples 1 to 31.

[0160] Example 34 may include an apparatus comprising one or more elements of a logic component, module, or circuit for performing a method or process described or associated with any of Examples 1 to 31 or any other method or process described herein.

[0161] Example 35 may include the methods, techniques or processes described or associated with any one of Examples 1 to 31 or any part or component thereof.

[0162] Embodiment 36 may include an apparatus comprising one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process described or associated with any one or a portion thereof according to Embodiments 1 to 31.

[0163] Example 37 may include signals described or associated with any one of Examples 1 to 31 or any part or component thereof.

[0164] Example 38 may include datagrams, information elements, data packets, frames, segments, PDUs or messages described or associated with any one of Examples 1 to 31 or any part or component thereof, or otherwise described in this disclosure.

[0165] Example 39 may include data-encoded signals described or associated with any one of Examples 1 to 31 or any part or component thereof, or otherwise described in this disclosure.

[0166] Example 40 may include signals encoded in datagrams, IEs, packets, frames, segments, PDUs or messages as described or associated with any one of Examples 1 to 31 or any part or component thereof, or otherwise described in this disclosure.

[0167] Example 41 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause one or more processors to perform a method, technique or process described or associated with any one or a portion thereof according to Examples 1 to 31.

[0168] Example 42 may include a computer program comprising instructions, wherein execution of the program by a processing element will cause the processing element to perform a method, technique, or process described or associated with any one or a portion thereof according to Examples 1 to 31.

[0169] Example 43 may include signals in a wireless network as shown and described herein.

[0170] Example 44 may include a method for communicating in a wireless network as shown and described herein.

[0171] Example 45 may include a system for providing wireless communication as shown and described herein.

[0172] Example 46 may include a device for providing wireless communication as shown and described herein.

[0173] Unless otherwise expressly stated, any of the examples above may be combined with any other example (or combination of examples). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In light of the teachings above, modifications and variations are possible, or modifications and variations may be derived from practice of various embodiments.

[0174] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed by one or more processors, cause a user to equip a UE: Candidate target cells are identified based on the knowledge stored in the cells used by the UE; Send a first message identifying the candidate target cell; and Receives a command to reconfigure the Radio Resource Control (RRC) connection. The command that executes the reconfiguration identifies the candidate target cell. The candidate target cell is one of the multiple candidate target cells identified in the first message, and For each of the plurality of candidate target cells, the first message includes a corresponding weight.

2. The one or more computer-readable media according to claim 1, wherein the first message includes information elements identifying the candidate target cell.

3. One or more computer-readable media according to any one of claims 1 to 2, wherein the first message identifies the candidate target cell by at least one of Physical Cell ID (PCI), New Radio Cell Identifier (NCI), or NR Cell Global Identifier (NCGI).

4. One or more computer-readable media according to any one of claims 1 to 2, wherein the command for performing the reconfiguration is RRCReconfiguration information.

5. One or more computer-readable media according to any one of claims 1 to 2, wherein the instructions, when executed by the one or more processors, further cause the UE to send an acknowledgment of reconfiguration completion to the candidate target cell.

6. The one or more computer-readable media according to claim 5, wherein the confirmation is RRCReconfigurationComplete information.

7. One or more computer-readable media according to any one of claims 1 to 2, wherein the first message is UEAssistanceInformation information.

8. One or more computer-readable media according to any one of claims 1 to 2, wherein the first message is RRCReconfigurationComplete information.

9. One or more computer-readable media according to any one of claims 1 to 2, wherein the instructions, when executed by the one or more processors, further cause the UE to use a recurrent neural network (RNN) to indicate the candidate target cell based on stored knowledge.

10. A method of operating a base station, the method comprising: The user equipment (UE) receives a first message identifying the target cell as a proposed candidate for handover. as well as Based on the first message, a command is generated for the UE to perform a reconfiguration of the Radio Resource Control (RRC) connection, wherein the command to perform the reconfiguration identifies the target cell. The target cell is one of a plurality of target cells identified as suggested candidates for handover in the first message, and For each candidate target cell among the plurality of target cells, the first message includes a corresponding weight.

11. The method according to claim 10, further comprising: Receive confirmation from the UE that the reconfiguration is complete.

12. The method according to any one of claims 10 to 11, further comprising: A handover request message to the target cell is generated.

13. The method according to any one of claims 10 to 11, wherein the first message is an auxiliary information message.

14. The method according to any one of claims 10 to 11, wherein the command executing the reconfiguration identifies more than one of the plurality of target cells.

Images