Reestablishment of a communication device operating in multi-radio dual connectivity and configured with conditional handover

Abstract

The invention name of the present disclosure is "reestablishment of a communication device operating in multi-radio dual connectivity and configured with conditional handover". A method by a user equipment, UE, capable of operating in a network in a multi-radio dual connectivity, MR-DC, mode. The method can include initiating a reestablishment procedure, delaying release of the MR-DC in response to the UE being configured with a conditional handover, CHO, and selecting a cell.

Description

Technical Field

[0001] This disclosure generally relates to communications, and more specifically to communication methods and related devices and nodes that support wireless communications. Background Technology

[0002] Figure 1 A communication network is illustrated having multiple network nodes 110a-b and a communication device 120 (also referred to herein as a user equipment (“UE”)). In some examples, the communication device 120 may be connected to a wireless network via a first network node 110a (which may be referred to as a source network node) and switched to a second network node 110b (which may be referred to as a target network node).

[0003] In some examples, under different detectable fault conditions (such as radio link failure and handover failure), the New Radio (“NR”) legacy Rel-15 UE triggers a reconstruction process. In response to triggering this reconstruction process, the UE is able to perform some initiation steps (e.g., as defined in 5.3.7.2 of Release 15RRC Specification TS 38.331V15.9.0 (2020-03)) before performing cell selection, and perform the steps defined in 5.3.7.3 (the actions following cell selection while timer T311 is running).

[0004] One of these initiation steps is the release of the Multiple Radio Dual Connectivity (“MR-DC”), which means that if the UE is operating in the MR-DC and a fault is detected that leads to a rebuild, the UE should release the MR-DC before the following actions (e.g., releasing the secondary cell group (“SCG”) and SCGmeasConfig): transmitting a Radio Resource Control (“RRC”) rebuild request and receiving an RRC rebuild (for configuring the first signaling radio bearer (“SRB1”)) and an RRC reconfiguration (e.g., for restoring the data radio bearer (“DRB”), applying incremental signaling on top of the UE’s current configuration (without the MR-DC, since it has been released)). Summary of the Invention

[0005] According to some embodiments, a method for operating a user equipment (“UE”) is provided. The UE is capable of operating in a multi-radio dual connectivity (“MR-DC”) mode within a network. The method includes initiating a reconstruction procedure. The method further includes delaying the release of the MR-DC in response to the UE being configured with a conditional handover (“CHO”).

[0006] According to other embodiments, a communication device, computer program, and / or computer program product is provided for performing the above-described methods.

[0007] In the various embodiments described herein, a potential advantage of the UE not deleting the MR-DC when rebuild is initiated while timer T311 is running (before it determines which cell it has selected) is that it avoids a state / configuration mismatch between the UE and the target candidate cell for which the UE performs the CHO (in the event that the UE does not continue the rebuild process). Attached Figure Description

[0008] The accompanying drawings are included to provide a further understanding of this disclosure. These drawings are incorporated in and form part of this application and illustrate certain non-limiting embodiments of the disclosure. In the drawings:

[0009] Figure 1 This is a schematic diagram illustrating an example of a telecommunications network.

[0010] Figure 2 This is a data flow diagram illustrating CHO processing in an MR-DC configuration;

[0011] Figure 3 Examples of RRCReconfiguration messages according to some embodiments of this disclosure are shown;

[0012] Figure 4 Examples of CondReconfigToAddModList IEs according to some embodiments of this disclosure are shown;

[0013] Figure 5 This is a table illustrating an example of the description of the CondReconfigToAddMod field according to some embodiments of this disclosure;

[0014] Figure 6 This is a table illustrating examples of how condReconfigAdd is interpreted according to some embodiments of this disclosure;

[0015] Figure 7 Examples of ConditionalReconfiguration IEs according to some embodiments of this disclosure are shown;

[0016] Figure 8 This is a table that shows an example of the description of the ConditionalReconfiguration field;

[0017] Figure 9 Examples of VarConditionalReconfig according to some embodiments of this disclosure are shown;

[0018] Figures 10-11 This is a data flow diagram corresponding to the successful reconstruction of RRC connection and the fallback from RRC reconstruction to successful RRC establishment, based on some embodiments of this disclosure;

[0019] Figure 12 This is a block diagram illustrating a wireless device UE according to some embodiments of the present disclosure;

[0020] Figure 13 This is a block diagram illustrating a radio access network RAN ​​node (e.g., a base station eNB / gNB) according to some embodiments of the present disclosure;

[0021] Figure 14 This is a block diagram illustrating core network (“CN”) nodes (e.g., AMF nodes, SMF nodes, etc.) according to some embodiments of the present disclosure;

[0022] Figure 15 This is a block diagram illustrating operations performed by a UE capable of operating in an MR-DC within a network, according to some embodiments described herein;

[0023] Figure 16 This is a block diagram illustrating the operation of performing MR-DC release according to some embodiments herein;

[0024] Figure 17 This is a block diagram illustrating the operations performed to release the SCG configuration according to some embodiments herein;

[0025] Figure 18 This is a block diagram of a wireless network according to some embodiments;

[0026] Figure 19 This is a block diagram of a user equipment according to some embodiments;

[0027] Figure 20 This is a block diagram of a virtualized environment according to some embodiments;

[0028] Figure 21 This is a block diagram of a telecommunications network connected to a host computer via an intermediate network, according to some embodiments;

[0029] Figure 22 This is a block diagram illustrating how a host computer communicates with a user equipment via a base station through a partial wireless connection, according to some embodiments.

[0030] Figure 23 It is a block diagram of a method implemented in a communication system including a host computer, a base station and a user equipment, according to some embodiments;

[0031] Figure 24 It is a block diagram of a method implemented in a communication system including a host computer, a base station and a user equipment, according to some embodiments;

[0032] Figure 25 This is a block diagram illustrating a method implemented in a communication system comprising a host computer, a base station, and user equipment, according to some embodiments; and

[0033] Figure 26 It is a block diagram of a method implemented in a communication system including a host computer, a base station and a user equipment, according to some embodiments. Detailed Implementation

[0034] This disclosure will now be described more fully below with reference to the accompanying drawings, which illustrate examples of embodiments of the disclosure. However, this disclosure may be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be transparent and complete, and will fully convey the scope of this disclosure to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be assumed by default to be present / used in another embodiment.

[0035] The following description illustrates various embodiments of the disclosed subject matter. These embodiments are shown as illustrative examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded without departing from the scope of the described subject matter.

[0036] Figure 2 This is a data flow diagram illustrating the operations performed by UE 120, source gNB 110a, target gNB 110b, AMF 202, and UPF 204 to execute a conditional handover (“CHO”) procedure in the MR-DC configuration. Conditional handover and fault handling are discussed below.

[0037] Two new work projects for mobility enhancements in Long Term Evolution (“LTE”) and New Radio (“NR”) have been initiated in the 3rd Generation Partnership Project (“3GPP”) in Release 16. The aim of these work projects is to improve handover resilience and reduce handover interference time. For that purpose, provisions are being made for conditional handover (defined as conditional reconfiguration in RRC). Conditional handover is described in TS 38.300 Phase 2 in the new section 9.2.3.X. A conditional handover (“CHO”) is defined as a handover performed by the UE when one or more handover execution conditions are met. Upon receiving a CHO configuration, the UE begins evaluating the execution condition(s) ...

[0038] In some examples, the CHO configuration contains the configuration of one or more CHO candidate cells generated by one or more candidate gNBs and one or more execution conditions generated by the source gNB. In additional or alternative examples, the execution conditions may include one or two trigger conditions. Only a single reference signal (“RS”) type is supported, and up to two different trigger quantities (e.g., reference signal received power (“RSRP”) and reference signal received quality (“RSRQ”) and signal-to-interference-noise ratio (“SINR”)) can be configured simultaneously for evaluating the CHO execution conditions of a single candidate cell. In additional or alternative examples, upon receiving a handover (“HO”) command (without CHO configuration) before any CHO execution conditions are met, the UE executes the HO procedure as described in Clause 9.2.3.2 of TS 38.300 regardless of any previously received CHO configurations. In additional or alternative examples, the UE does not monitor the source cell when executing a CHO (e.g., from the start of synchronization with the target cell).

[0039] In this release specification, CHO is not supported for N2-based switching.

[0040] It has been agreed that if a UE configured with a CHO (e.g., has stored at least one RRCReconfiguration for each target candidate cell) detects a fault (e.g., radio link fault detection during CHO monitoring), the UE initiates a reconstruction procedure. Furthermore, if the selected cell is a cell for which the UE has a stored CHO configuration (e.g., RRCReconfiguration) while timer T311 is running, the UE applies the stored configuration instead of performing a reconstruction. Therefore, the UE only proceeds with reconstruction if the selected cell is not a cell for which the UE does not have a stored RRCReconfiguration.

[0041] If a fault is detected and attemptCondReconfig is configured (part of the CHO configuration), and if the selected cell is one of the candidate cells in the masterCellGroup of VarConditionalReCconfig that contains reconfigurationWithSync, the UE applies the stored condRRCReconfig associated with the selected cell and performs the action. Otherwise, the UE continues with the reconstruction steps.

[0042] In RAN2#109e, the agreement regarding CHO and MR-DC operation is that CHO (MCG) can work with MR-DC (e.g., receiving CHO when configuring MR-DC), and receiving SCG additions when CHO conditions are configured; SCG configuration in RRC reconfiguration with conditional reconfiguration is not excluded; and restrictions are placed on cases that do not have RAN3 impact. Therefore, according to the following agreement, a UE can operate in MR-DC while it is monitoring a CHO. Furthermore, the stored RRCReconfiguration generated by the target candidate can contain SCG configurations. There is no problem when the UE executes a CHO when the execution conditions are met. And the RRC reconfiguration generated by the target candidate containing the stated SCG(one) configurations can be applied.

[0043] However, a problem arises when a UE monitoring the CHO and operating in the MR-DC detects a fault and initiates a rebuild. Based on the running CR, the UE deletes the MR-DC before cell selection.

[0044] In some embodiments, a method on a UE device capable of operating in MR-DC and initiating a reconstruction process includes: initiating a reconstruction process; delaying the release of MR-DC if the UE is configured with a conditional handover (“CHO”); and applying the target cell configuration (i.e., applying the stored condRRCReconfig associated with the selected cell) if the UE with a CHO at cell selection selects a cell for which the UE has a stored target configuration (i.e., the selected cell is one of the candidate cells in the masterCellGroup of VarConditionalReCconfig containing reconfigurationWithSync). And execute the action); if a UE configured with a CHO during cell selection selects a cell for which it does not have a stored target configuration (i.e., the selected cell is one of the candidate cells in the masterCellGroup of VarConditionalReCconfig that contains reconfigurationWithSync), then release MR-DC release; and if a UE configured with a CHO during cell selection is not configured with an instruction from the network that allows the UE to execute the CHO upon reconstruction initiation (e.g., if the UE is not configured with an instruction attemptCondReconfig in its CHO configuration), then release MR-DC release.

[0045] The advantage of the UE not deleting the MR-DC during reconstruction initiation when timer T311 is running (before it determines which cell it has selected) is that it avoids state / configuration mismatch between the UE and the target candidate cell for the UE to perform CHO (in the event that the UE does not continue the reconstruction process).

[0046] Figure 12 This is a block diagram illustrating the elements of a communication device UE 1200 (also referred to as a mobile terminal, mobile communication terminal, wireless device, wireless communication device, wireless terminal, mobile device, wireless communication terminal, user equipment UE, user equipment node / terminal / device, etc.) configured to provide wireless communication according to embodiments of the present disclosure. (The communication device 1200 may be provided, for example, as described below for...) Figure 18 (As discussed in the wireless device 4110). As shown, the wireless device UE may include an antenna 1207 (e.g., corresponding to...). Figure 18 Antenna 4111) and transceiver circuit module 1201 (also called transceiver, for example, corresponding to Figure 18 The transceiver circuit module includes an interface 4114), which is configured to provide communication with one or more base stations (e.g., corresponding to a radio access network) of the radio access network. Figure 18 The network node 4160 (also referred to as the RAN node) is a transmitter and receiver for uplink and downlink radio communication. The communication device UE may also include a processing circuit module 1203 (also referred to as a processor, for example, corresponding to the transceiver circuit module) coupled to the transceiver circuit module. Figure 18 The processing circuit module 4120) and the memory circuit module 1205 (also referred to as memory, for example, corresponding to the processing circuit module) coupled to the processing circuit module. Figure 18 The device-readable medium 4130. The memory circuit module 1205 may contain computer-readable program code that, when executed by the processing circuit module 1203, causes the processing circuit module to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit module 1203 may be defined to include memory so that a separate memory circuit module is not required. The communication device UE may also include an interface (such as a user interface) coupled to the processing circuit module 1203, and / or the communication device UE may be incorporated into a vehicle.

[0047] As discussed herein, the operation of the communication device UE can be performed by the processing circuit module 1203 and / or the transceiver circuit module 1201. For example, the processing circuit module 1203 can control the transceiver circuit module 1201 to transmit communications to a radio access network node (also referred to as a base station) via the radio interface and / or to receive communications from a RAN node via the radio interface. Furthermore, modules can be stored in the memory circuit module 1205, and these modules can provide instructions such that when the instructions of the modules are executed by the processing circuit module 1203, the processing circuit module 1203 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments relating to wireless communication devices).

[0048] Figure 13 This is a block diagram illustrating elements of a radio access network RAN ​​node 1300 (also referred to as a network node, base station, eNodeB / eNB, gNodeB / gNB, etc.) configured to provide cellular communication according to embodiments of the present disclosure. (RAN node 1300 may be provided, for example, as described below for...) Figure 18 (As discussed in network node 4160). As shown, the RAN node may include transceiver circuit module 1301 (also called a transceiver, for example, corresponding to...). Figure 18 The transceiver circuit module (part of interface 4190) includes a transmitter and a receiver configured to provide uplink and downlink radio communication with the mobile terminal. The RAN node may include a network interface circuit module 1307 (also referred to as a network interface, for example, corresponding to...). Figure 18 The network interface circuit module (part of interface 4190) is configured to provide communication with other nodes (e.g., other base stations) of the RAN and / or core network CN. The network node may further include a processing circuit module 1303 (also referred to as a processor, e.g., corresponding to processing circuit module 4170) coupled to the transceiver circuit module and a memory circuit module 1305 (also referred to as a memory, e.g., corresponding to memory) coupled to the processing circuit module. Figure 18 (Apparatus-readable medium 4180). Memory circuit module 1305 may include computer-readable program code that, when executed by processing circuit module 1303, causes the processing circuit module to perform operations according to the embodiments disclosed herein. According to other embodiments, processing circuit module 1303 may be defined to include a processor so that a separate memory circuit module is not required.

[0049] As discussed herein, the operation of the RAN node can be performed by processing circuitry module 1303, network interface 1307, and / or transceiver 1301. For example, processing circuitry module 1303 can control transceiver 1301 to transmit downlink communications to one or more mobile terminal UEs via the radio interface and / or to receive uplink communications from one or more mobile terminal UEs via the radio interface. Similarly, processing circuitry module 1303 can control network interface 1307 to transmit communications to one or more other network nodes and / or to receive communications from one or more other network nodes via the network interface. Furthermore, modules can be stored in memory 1305, and these modules can provide instructions such that when the instructions of the modules are executed by processing circuitry module 1303, processing circuitry module 1303 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments involving RAN nodes).

[0050] According to some other embodiments, the network node may be implemented as a core network (“CN”) node without a transceiver. In such embodiments, transmissions to the wireless communication device UE may be initiated by the network node such that the transmissions to the wireless communication device UE are provided via a network node containing a transceiver (e.g., via a base station or RAN node). According to an embodiment where the network node is an RAN node containing a transceiver, initiating a transmission may involve transmission via the transceiver.

[0051] Figure 14 This is a block diagram illustrating the elements of a CN node 1400 (e.g., an SMF node, an AMF node, etc.) configured to provide cellular communication in a communication network according to embodiments of the present disclosure. As shown, the CN node 1400 may include a network interface circuit module 1407 (also referred to as a network interface) configured to provide communication with other nodes in the core network and / or the radio access network (RAN). The CN node 1400 may also include a processing circuit module 1403 (also referred to as a processor) coupled to the network interface circuit module and a memory circuit module 1405 (also referred to as a memory) coupled to the processing circuit module. The memory circuit module 1405 may contain computer-readable program code that, when executed by the processing circuit module 1403, causes the processing circuit module to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit module 1403 may be defined to include memory so that a separate memory circuit module is not required.

[0052] As discussed herein, the operation of CN node 1400 can be performed by processing circuit module 1403 and / or network interface circuit module 1407. For example, processing circuit module 1403 can control network interface circuit module 1407 to transmit communication to one or more other network nodes and / or to receive communication from one or more other network nodes via network interface circuit module 1407. Furthermore, modules can be stored in memory 1405, and these modules can provide instructions such that when the instructions of the modules are executed by processing circuit module 1403, processing circuit module 1403 performs corresponding operations (e.g., the operations discussed below with respect to example embodiments involving core network nodes).

[0053] This document describes various embodiments in scenarios where a UE is configured with multi-radio dual connectivity (“MR-DC”) and conditional handover (“CHO”), detects a fault, and initiates a reconstruction process. This document describes embodiments related to NR-DC (e.g., when both the primary and secondary nodes are NR gNBs); however, similar operations are equally applicable to other DC scenarios (e.g., NR Evolution Global Terrestrial Radio Access (“E-UTRA”) DC (“NE-DC”), Next Generation (“NG”)-RAN E-URTA DC (“(NG)EN-DC”), and LTE DC).

[0054] In some embodiments of this document, synonyms for CHO are used, such as conditional reconfiguration or conditional configuration (because the message stored and applied when the condition is met is RRCReconfiguration or RRCConnectionReconfiguration). At the terminology level, CHO can be interpreted in a broader sense.

[0055] The configuration principle can be the same as configuring one or more trigger / execution conditions and applying reconfiguration messages (when the one or more trigger conditions are met).

[0056] Some embodiments involve a CHO configuration or a UE configured with a CHO, corresponding to a UE that has received an RRC reconfiguration (e.g., an RRCReconfiguration message in NR format) that includes a CHO configuration, such as in Figure 3 The example of the RRCReconfiguration message is shown in the example.

[0057] Figure 4This shows an example of the CondReconfigToAddModList information element (“IE”). The CondReconfigToAddModList IE contains a list of conditional reconfigurations so that for each entry, condReconfigId and the associated condExcutionCond and condRRCReconfig can be added or modified. Figure 5 This is a table that shows an example of the description of the CondReconfigToAddMod field. Figure 6 This is a table that shows an example of how CondReconfigAdd is interpreted.

[0058] Figure 7 This shows an example of the ConditionalReconfiguration IE. The ConditionalReconfiguration IE is used to add, modify, and release the configuration for conditional reconfigurations. Figure 8 This is a table that shows an example of the description of the ConditionalReconfiguration field.

[0059] Figure 9 An example of VarConditionalReconfig is shown. The UE variable VarConditionalReconfig contains the following accumulated configuration: conditional handover or conditional PSCell change configuration, including a pointer to the conditional handover or conditional PSCell change execution condition (one or more associated measIds) and the stored target candidate SpCellRRCReconfiguration.

[0060] As provided herein, a UE performing an MR-DC release may perform one or more of the following actions: release SRB3 (if configured); release the measurement configuration associated with the secondary cell group (“SCG”); release the measurement configuration associated with the secondary node; if the UE is configured with an NR SCG, release the SCG configuration by performing at least the action of resetting the SCG MAC (if configured); perform an RLC bearer release procedure for each RLC bearer (which is part of the SCG configuration); and release the SCG step. If the UE is configured with a conditional PSCell change (“CPC”), the operation may include releasing the CPC configuration; if the UE is configured with a conditional PSCell attach (“CPA”), the operation may include releasing the CPA configuration; and if the UE is configured with a conditional reconfiguration, the operation may include releasing the CPA configuration.

[0061] The CPC configuration contains a configuration generated by the secondary node for PSCell changes (based on a configured condition, such as a condition related to the A3 / A5 event). This is a conditional reconfiguration. The RRC reconfiguration with the SCG configuration is provided to the UE but is not applied upon reception; it is applied only when the condition (e.g., the A3 / A5 event) is met. Deleting the CPC corresponds to releasing / deleting the UE variables in which the configuration is stored.

[0062] The CPA configuration contains a configuration generated by the secondary node for PSCell changes (based on a configured condition, such as a condition of the A3 / A5 event). This is a conditional reconfiguration. The RRC reconfiguration with the SCG configuration is provided to the UE but is not applied upon reception; it is applied only when a condition (such as the A2 / A1 event) is met. Deleting the CPA corresponds to releasing / deleting the UE variables in which the configuration is stored.

[0063] CHO, CPA, and CPC can be considered as one or more conditional reconfigurations. Deleting CPA / CPC / CHO corresponds to releasing / deleting the UE variables in which the configuration is stored.

[0064] The following describes examples of changes in the RRC specification.

[0065] In the first example, the UE initiates a reconstruction and determines whether it is configured with conditionalReconfiguration.

[0066] If the UE is not configured with conditionalReconfiguration but is configured with MR-DC, the UE performs MR-DC release and performs the action (Article 5.3.5.10 of TS 38.331).

[0067] If the UE is configured with conditionalReconfiguration, the UE attempts to perform a CHO during cell selection. If the cell selected during cell selection is one of the candidate cells in the masterCellGroup of VarConditionalReCconfig that contains reconfigurationWithSync, the UE applies the stored condRRCReconfig associated with the selected cell and performs the action as specified in 5.3.5.3 of TS 38.331.

[0068] If the cell selected during cell selection is not one of the candidate cells in the masterCellGroup of VarConditionalReCconfig that contains reconfigurationWithSync, and if the UE is configured with conditionalReconfiguration (i.e., configured with CHO), and if the UE is configured by MR-DC, then it performs MR-DC release as specified in Clause 5.3.5.10 of TS 38.331.

[0069] In other words, not all UEs will perform the MR-DC release procedure when rebuild is initiated, which will prevent state mismatch between the UE and the target candidate.

[0070] Now, a brief reference. Figures 10-11 , Figures 10-11 This is a data flow diagram corresponding to successful RRC connection reconstruction and RRC reconstruction rollback to successful RRC establishment, based on some embodiments in this document. For example... Figure 10 As shown, UE 120 sends an RRCReestablishment request (box 1010), receives an RRCReestablishment (box 1020), and sends an RRCReestablishmentComplete message to network 1000 (box 1030). Figure 11 As shown, UE 120 sends an RRCReestablishment request (box 1110), receives an RRCSetup message from network 1000 (box 1120), and sends an RRCSetupComplete message to network 1000 (box 1130).

[0071] This procedure can re-establish the RRC connection. A UE in RRC_CONNECTED (with its AS security activated and SRB2 and at least one DRB set) can initiate this procedure to continue the RRC connection. If the network can find and verify a valid UE context, the connection is successfully re-established; otherwise, if the UE context cannot be retrieved, the network responds with RRCSetup (according to Clause 5.3.3.4 of TS38.331).

[0072] The network may apply the procedure such that when AS security has been activated, the network retrieves or verifies the UE context in order to: reactivate AS security without changing the algorithm; and rebuild and restore SRB1. When the UE is rebuilding an RRC connection and the network is unable to retrieve or verify the UE context: discard the stored AS context and release all radio bearers (“RB”); and fall back to establish a new RRC connection.

[0073] If AS security is not yet activated, the UE should not initiate the procedure but should instead move directly to RRC_IDLE (due to release reason 'other'). If AS security is activated but SRB2 and at least one DRB are not set, the UE should not initiate the procedure but should instead move directly to RRC_IDLE (due to release reason 'RRC connection failure').

[0074] Reference will now be made to some embodiments according to this disclosure. Figures 15-17 To discuss using flowcharts (using) Figure 12 The operation of the communication device UE 1200 is implemented based on the block diagram structure. For example, the module can be stored in... Figure 12 The memory 1205 contains these modules, and these modules can provide instructions such that when the instructions of the modules are executed by the corresponding communication device UE 1200 processing circuit module 1203, the processing circuit module 1203 performs the corresponding operation of the flowchart.

[0075] Figure 15 The flowchart illustrates the operations performed by a UE capable of operating in an MR-DC within a network, according to some embodiments herein. In block 1510, the processing circuitry module 1203 initiates a reconstruction procedure. In block 1520, the processing circuitry module 1203 delays the release of the MR-DC in response to the UE being configured with a conditional handover CHO.

[0076] In block 1525, processing circuit module 1203 selects a cell. In some embodiments, processing circuit module 1203 performs cell selection before the deletion of delayed MR-DC.

[0077] In block 1530, the processing circuit module 1203 applies the stored target cell configuration in response to a UE configured with CHO having a stored target cell configuration for the selected cell.

[0078] In block 1540, processing circuit module 1203 performs MR-DC release in response to a cell selected in the UE being configured with a CHO, the cell not containing a cell with a stored target cell configuration for the UE. In some embodiments, the stored target cell configuration corresponds to a ReconfigurationWithSync information element, which is included in the MasterCellGroup in VarConditionalReconfig.

[0079] In some embodiments, MR-DC release is performed in response to a cell selected in the UE being configured with a CHO, wherein the cell is not configured with an instruction from the network that the UE can perform a CHO upon reconstruction initiation.

[0080] Some embodiments provide that, in response to a UE being configured with a conditional PSCell change CPC, performing an MR-DC release operation includes releasing the CPC configuration. In some embodiments, the conditional PSCell change includes a configuration generated by a secondary node (based on conditions of a certain configuration).

[0081] Some embodiments provide that, in response to the UE being configured with a conditional PSCell attached CPA, an MR-DC release is performed including releasing the CPA configuration.

[0082] In some embodiments, the conditional PSCell append includes a configuration generated by the secondary node (based on conditions of a certain configuration). In some embodiments, CHO, CPA, and CPC include conditional reconfiguration, and deleting CHO, CPA, and / or CPC includes releasing and / or deleting UE variables corresponding to the configuration storage.

[0083] In block 1550, processing circuit module 1203 determines whether the UE is configured for conditional reconfiguration. In some embodiments, in response to the UE not being configured for conditional reconfiguration and the UE being configured with MR-DC, the UE performs an MR-DC release. Some embodiments provide that, in response to the UE being configured for conditional reconfiguration, the UE further attempts to perform a CHO during cell selection.

[0084] Some embodiments provide that: an initiation of a reconstruction procedure is performed in response to at least one of the following: detection of a radio link failure of the MCG; reconfiguration due to a synchronization failure of the MCG; mobility failure from an NR failure; receiving an integrity check failure indication from a lower layer regarding SRB1 or SRB2 unless an integrity check failure is detected on an RRCRestablishment message; an RRC connection reconfiguration failure; detection of a radio link failure of the SCG when MCG transmission is suspended; reconfiguration due to a synchronization failure of the MCG when MCG transmission is suspended; an SCG change failure during MCG transmission in the NE-DC; an SCG configuration failure when MCG transmission is suspended; and an integrity check failure indication from a lower layer regarding SRB3 when the MCG is suspended.

[0085] In block 1570, in response to the UE determining whether it is configured with conditional reconfiguration, processing circuit module 1203 applies the stored condRRCReconfig associated with the selected cell. In some embodiments, in response to the UE determining that the selected cell is not one of the candidate cells containing reconfigurationWithSync in the masterCellGroup of VarConditionalReCconfig.

[0086] Some embodiments provide that performing an MR-DC release includes at least one of the following: releasing SRB3 (if configured); releasing the measurement configuration associated with the secondary cell group (“SCG”); releasing the measurement configuration associated with the secondary node; releasing the SCG configuration if the UE is configured with an NRSCG; this includes at least the following actions: resetting the SCG MAC (if configured); performing an RLC bearer release procedure for each RLC bearer (the RLC bearer being part of the SCG configuration); releasing the SCG configuration; releasing the CPC configuration if the UE is configured with a conditional PSCell change (“CPC”); releasing the CPA configuration if the UE is configured with a conditional PSCell attach (“CPA”); and releasing the CPA configuration if the UE is configured with a conditional reconfiguration.

[0087] Now refer to Figure 16 , Figure 16 This is a block diagram illustrating the operation of performing MR-DC release according to some embodiments herein. In block 1610, processing circuit module 1203 releases SRB3 (e.g., the signaling radio bearer for a specific RRC message when the UE is in EN-DC (all using the DCCH logical channel)). In block 1620, processing circuit module 1203 releases the measurement configuration associated with the secondary cell group (SCG). In block 1630, the processing circuit module releases the measurement configuration associated with the secondary node.

[0088] Now refer to Figure 17 , Figure 17 This is a block diagram illustrating the operations performed to release the SCG configuration according to some embodiments herein. In block 1710, processing circuit module 1203 releases the SCG configuration by resetting the SCG MAC (if configured). In block 1720, processing circuit module 1203 performs a radio link control RLC bearer release for each RLC bear that is a portion of the SCG configuration. In block 1730, processing circuit module 1203 releases the SCG configuration.

[0089] Figures 15-17 The various operations are optional. For example, in some embodiments, Figure 15 The frames are 1525, 1530, 1540, 1550, and 1570; Figure 16 Boxes 1610, 1620, and 1630; and Figure 17 Boxes 1710, 1720, and 1730 can be optional.

[0090] Additional explanations are provided below.

[0091] Generally, all terms used herein shall be interpreted according to their ordinary meaning in the relevant art, unless a different meaning is explicitly given and / or implied by the context in which it is used. All references to an element, device, component, part, step, etc., are open-ended and are interpreted as referring to at least one instance of the element, device, component, part, step, etc., unless otherwise expressly stated. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as occurring after or before another step and / or implied that a step must occur after or before another step. Any feature of any embodiment of the embodiments disclosed herein may be suitably applied to any other embodiment. Similarly, any advantage of any embodiment of the embodiments may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will be apparent from the following description.

[0092] Some embodiments of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; these embodiments are provided by way of example in order to convey the scope of the subject matter to those skilled in the art.

[0093] Figure 18 A wireless network according to some embodiments is shown.

[0094] While the topics described herein can be implemented in any suitable type of system using any appropriate components, the embodiments disclosed herein are relative to wireless networks (such as...). Figure 18 The example wireless network shown is used for description. For the sake of brevity, Figure 18 The wireless network shown only includes network 4106, network nodes 4160 and 4160b, and WD 4110, 4110b, and 4110c (also referred to as mobile terminals). In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (such as a landline telephone, service provider, or any other network node or terminal device). Among the components shown, network node 4160 and wireless device (“WD”) 4110 are shown in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate access and / or use of services provided by or via the wireless network.

[0095] Wireless networks may include any type of communication, telecommunications, data, cellular and / or radio networks or other similar types of systems and / or connected to them via an interface. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network may implement: communication standards such as Global System for Mobile Communications (“GSM”), Universal Mobile Telecommunications System (“UMTS”), Long Term Evolution (“LTE”) and / or other suitable 2G, 3G, 4G or 5G standards; wireless local area network (“WLAN”) standards such as the IEEE 802.11 standard; and / or any other suitable wireless communication standards such as Global Microwave Access Interoperability (“WiMax”), Bluetooth, Z-Wave and / or ZigBee standards.

[0096] Network 4106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (“PSTN”), packet data networks, optical networks, wide area networks (“WAN”), local area networks (“LAN”), wireless local area networks (“WLAN”), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0097] Network node 4160 and WD 4110 include various components described below in more detail. These components work together to provide the functionality of the network node and / or wireless device, such as providing wireless connectivity in a wireless network. In various embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals (whether via wired or wireless connections).

[0098] As used herein, a “network node” means a device that is capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (“APs”) (e.g., radio access points) and base stations (“BSs”) (e.g., radio base stations, Node Bs, evolved Node Bs (“eNBs”), and NR Node Bs (“gNBs”)). Base stations may be classified based on the coverage they provide (or, in other words, their transmit power level) and may then be referred to as femtocells, picocells, microcells, or macrocells. A base station may be a relay node or a relay donor node that controls a relay. A network node may also comprise one or more (or all) portions of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (“RRU”), sometimes referred to as a remote radio headend (“RRH”). Such remote radio units may or may not be integrated with an antenna as an antenna-integrated radio. The distributed radio base station portion may also be referred to as a node in a distributed antenna system (“DAS”). Other examples of network nodes include multi-standard radio (“MSR”) equipment (such as an MSR BS), network controllers (such as a radio network controller (“RNC”) or base station controller (“BSC”)), base transceiver stations (“BTS”), transport points, transport nodes, multi-cell / multicast coordination entities (“MCE”), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, location nodes (e.g., E-SMLC), and / or MDTs. As another example, a network node can be a virtual network node as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) capable of, configured to, arranged to, and / or operable to enable and / or provide access to a wireless network for wireless devices or to provide a service to wireless devices already connected to the wireless network.

[0099] Figure 18 In this network node 4160, there is a processing circuit module 4170, a device-readable medium 4180, an interface 4190, auxiliary equipment 4184, a power supply 4186, a power circuit module 4187, and an antenna 4162. Although Figure 18The network node 4160 shown in the example wireless network may represent an apparatus containing the illustrated combination of hardware components, but other embodiments may include network nodes having different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, while the components of network node 4160 are shown as a single frame contained within a larger frame or nested within multiple frames, in practice, a network node may include multiple different physical components that make up a single illustrated component (e.g., apparatus-readable medium 4180 may include multiple separate hard disk drives and multiple RAM modules).

[0100] Similarly, network node 4160 may be composed of multiple physically independent components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own corresponding components. In some cases where network node 4160 includes multiple independent components (e.g., BTS and BSC components), one or more of these independent components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such cases, each unique NodeB and RNC pair may be considered a single independent network node in some situations. In some embodiments, network node 4160 may be configured to support multiple radio access technologies (“RATs”). In such embodiments, some components (e.g., independent device-readable media 4180 for different RATs) may be duplicated, and some components (e.g., the same antenna 4162 may be shared by RATs) may be reused. Network node 4160 may also include multiple sets of various illustrated components of different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into network node 4160. These wireless technologies can be integrated into the same or different chips or chip sets and other components within network node 4160.

[0101] Processing circuit module 4170 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as provided by a network node. These operations performed by processing circuit module 4170 may include processing information acquired by processing circuit module 4170 through, for example, the following steps: converting the acquired information into other information, comparing the acquired or converted information with information stored in the network node, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing.

[0102] Processing circuit module 4170 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable alone or in combination with other network node 4160 components (such as device-readable medium 4180) to provide the functionality of network node 4160. For example, processing circuit module 4170 may execute instructions stored in device-readable medium 4180 or in memory within processing circuit module 4170. Such functionality may include any wireless feature, function, or benefit that provides the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuit module 4170 may include a system-on-a-chip (“SOC”).

[0103] In some embodiments, the processing circuit module 4170 may include one or more of a radio frequency (“RF”) transceiver circuit module 4172 and a baseband processing circuit module 4174. In some embodiments, the RF transceiver circuit module 4172 and the baseband processing circuit module 4174 may be located on separate chips (or chip sets), boards, or units (such as radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuit module 4172 and the baseband processing circuit module 4174 may be located on the same chip or chip set, board, or unit.

[0104] In some embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be executed by processing circuit module 4170 by executing instructions stored on device-readable medium 4180 or in memory within processing circuit module 4170. In alternative embodiments, some or all of the functionality may be provided by processing circuit module 4170, for example, by hard-wired configuration, without executing instructions stored on a separate or discrete device-readable medium. In any of those embodiments, processing circuit module 4170 may be configured to perform the aforementioned functionality regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to processing circuit module 4170 alone or other components of network node 4160, but are generally enjoyed by network node 4160 and / or generally by end users and wireless networks.

[0105] Device-readable medium 4180 may include any form of volatile or non-volatile computer-readable memory, including, without limitation, permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (“RAM”), read-only memory (“ROM”), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (“CD”), or digital video disc (“DVD”)) and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions usable by processing circuitry module 4170. Device-readable medium 4180 may store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, codes, tables, etc.) and / or other instructions (which can be executed by processing circuitry module 4170 and utilized by network node 4160). Device-readable medium 4180 may be used to store any calculations performed by processing circuitry module 4170 and / or any data received via interface 4190. In some embodiments, the processing circuit module 4170 and the device-readable medium 4180 may be considered integrated.

[0106] Interface 4190 is used for wired or wireless communication of signaling and / or data between network node 4160, network 4106, and / or WD 4110. As shown, interface 4190 includes one or more ports / terminals 4194 for sending and receiving data to and from network 4106 via a wired connection, for example. Interface 4190 also includes a radio front-end circuit module 4192, which may be coupled to antenna 4162 or, in some embodiments, a portion of antenna 4162. Radio front-end circuit module 4192 includes a filter 4198 and an amplifier 4196. Radio front-end circuit module 4192 may be connected to antenna 4162 and processing circuit module 4170. Radio front-end circuit module 4192 may be configured to modulate the signal transmitted between antenna 4162 and processing circuit module 4170. Radio front-end circuit module 4192 may receive digital data to be transmitted to other network nodes or WDs via a wireless connection. The radio front-end circuit module 4192 may use a combination of filter 4198 and / or amplifier 4196 to convert digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals can then be transmitted via antenna 4162. Similarly, when receiving data, antenna 4162 may collect radio signals, which are then converted into digital data by the radio front-end circuit module 4192. The digital data may be passed to processing circuit module 4170. In other embodiments, the interface may include different components and / or different combinations of components.

[0107] In some alternative embodiments, network node 4160 may not include a separate radio front-end circuit module 4192. Instead, processing circuit module 4170 may include a radio front-end circuit module and may be connected to antenna 4162 without the need for a separate radio front-end circuit module 4192. Similarly, in some embodiments, all or part of RF transceiver circuit module 4172 may be considered part of interface 4190. In other embodiments, interface 4190 may include one or more ports or terminals 4194, radio front-end circuit module 4192, and RF transceiver circuit module 4172 as part of a radio unit (not shown), and interface 4190 may communicate with baseband processing circuit module 4174, which is part of a digital unit (not shown).

[0108] Antenna 4162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 4162 may be coupled to radio front-end circuit module 4192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 4162 may include one or more omnidirectional, sector, or planar antennas operable to transmit / receive radio signals, for example, between 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sector antennas can be used to transmit / receive radio signals from a device in a specific area, and planar antennas can be line-of-sight antennas used to transmit / receive radio signals in a relative straight line. In some cases, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 4162 may be detachable from network node 4160 and may be connectable to network node 4160 via an interface or port.

[0109] Antenna 4162, interface 4190, and / or processing circuit module 4170 may be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals may be received from a wireless device, another network node, and / or any other network device. Similarly, antenna 4162, interface 4190, and / or processing circuit module 4170 may be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a wireless device, another network node, and / or any other network device.

[0110] Power circuit module 4187 may include or be coupled to a power management circuit module and is configured to supply power to components of network node 4160 for performing the functionality described herein. Power circuit module 4187 may receive power from power source 4186. Power source 4186 and / or power circuit module 4187 may be configured to supply power to various components of network node 4160 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). Power source 4186 may be included in power circuit module 4187 and / or network node 4160 or external to power circuit module 4187 and / or network node. For example, network node 4160 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit module or interface (such as a cable), whereby the external power source supplies power to power circuit module 4187. As another example, power source 4186 may include a power source in the form of a battery or battery pack, which is connected to or integrated into power circuit module 4187. The battery can provide backup power if the external power source fails. Other types of power sources (such as photovoltaic devices) may also be used.

[0111] Alternative embodiments of network node 4160 may include, in addition to Figure 18 In addition to the components shown herein, additional components may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the topics described herein. For example, network node 4160 may include a user interface device to allow information to enter into network node 4160 and to allow information to exit from network node 4160. This allows a user to perform diagnostic, maintenance, repair, and other management functions of network node 4160.

[0112] As used herein, a wireless device (“WD”) means a device capable of, configured to, arranged to, and / or operable to wirelessly communicate with network nodes and / or other wireless devices. Unless otherwise stated, the term “WD” is used interchangeably with “User Equipment” (“UE”) herein. Wireless communication may involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information over the air. In some embodiments, the WD may be configured to transmit and / or receive information without direct human interaction. For example, the WD may be designed to transmit information to the network based on a predetermined schedule, triggered by internal or external events, or in response to a request from the network. Examples of WD's devices include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (“VoIP”) phones, wireless local loop phones, desktop computers, personal digital assistants (“PDAs”), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (“LEE”), laptop mounted devices (“LME”), smart devices, wireless customer premises equipment (“CPE”), and vehicle-mounted wireless terminal devices. WD may support device-to-device (“D2D”) communication, for example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (“V2V”), vehicle-to-infrastructure (“V2I”), and vehicle-to-everything (“V2X”), and in this case, the device may be referred to as a D2D communication device. As another specific example, in the context of the Internet of Things (“IoT”), a WD can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another WD and / or network node. In this case, the WD can be a machine-to-machine (“M2M”) device, which in the 3GPP context may be referred to as an MTC device. As a specific example, a WD can be a UE implementing the 3GPP Narrowband Internet of Things (“NB-IoT”) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., power meters), industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), and personal wearables (e.g., watches, fitness trackers, etc.). In other cases, a WD can represent a vehicle or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation. As described above, a WD can represent a wirelessly connected endpoint, in which case the device may be referred to as a wireless terminal. Furthermore, as described above, a WD can be mobile, in which case it may be referred to as a mobile device or mobile terminal.

[0113] As shown, the wireless device 4110 includes an antenna 4111, an interface 4114, a processing circuit module 4120, a device-readable medium 4130, a user interface device 4132, an auxiliary device 4134, a power supply 4136, and a power circuit module 4137. The WD 4110 may include one or more of the components shown, representing various wireless technologies supported by the WD 4110 (such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few). These wireless technologies may be integrated into chips or sets of chips that are the same as or different from other components within the WD 4110.

[0114] Antenna 4111 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and is connected to interface 4114. In some alternative embodiments, antenna 4111 may be detachable from WD 4110 and may be connected to WD 4110 via an interface or port. Antenna 4111, interface 4114, and / or processing circuitry module 4120 may be configured to perform any receive or transmit operations described herein as performed by a WD. Any information, data, and / or signals may be received from network nodes and / or another WD. In some embodiments, the radio front-end circuitry module and / or antenna 4111 may be considered as the interface.

[0115] As shown, interface 4114 includes a radio front-end circuit module 4112 and an antenna 4111. Radio front-end circuit module 4112 includes one or more filters 4118 and an amplifier 4116. Radio front-end circuit module 4112 is connected to antenna 4111 and processing circuit module 4120 and is configured to modulate the signal transmitted between antenna 4111 and processing circuit module 4120. Radio front-end circuit module 4112 may be coupled to antenna 4111 or is part of antenna 4111. In some embodiments, WD 4110 may not include a separate radio front-end circuit module 4112; processing circuit module 4120 may instead include the radio front-end circuit module and may be connected to antenna 4111. Similarly, in some embodiments, part or all of RF transceiver circuit module 4122 may be considered part of interface 4114. Radio front-end circuit module 4112 may receive digital data that will be transmitted wirelessly to other network nodes or WD. The radio front-end circuit module 4112 may use a combination of filter 4118 and / or amplifier 4116 to convert digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals can then be transmitted via antenna 4111. Similarly, when receiving data, antenna 4111 may collect radio signals, which are then converted into digital data by the radio front-end circuit module 4112. The digital data may be passed to processing circuit module 4120. In other embodiments, the interface may include different components and / or different combinations of components.

[0116] Processing circuit module 4120 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable alone or in combination with other WD 4110 components (such as device-readable medium 4130) to provide WD 4110 functionality. Such functionality may include any wireless features or benefits that provide the various wireless features or benefits described herein. For example, processing circuit module 4120 may execute instructions stored in device-readable medium 4130 or in memory within processing circuit module 4120 to provide the functionality disclosed herein.

[0117] As shown, the processing circuit module 4120 includes one or more of an RF transceiver circuit module 4122, a baseband processing circuit module 4124, and an application processing circuit module 4126. In other embodiments, the processing circuit module may include different components and / or different combinations of components. In some embodiments, the processing circuit module 4120 of WD 4110 may include a System-on-a-Chip (SOC). In some embodiments, the RF transceiver circuit module 4122, the baseband processing circuit module 4124, and the application processing circuit module 4126 may be located on separate chips or chip sets. In alternative embodiments, some or all of the baseband processing circuit module 4124 and the application processing circuit module 4126 may be combined into a single chip or chip set, and the RF transceiver circuit module 4122 may be located on a separate chip or chip set. In still alternative embodiments, some or all of the RF transceiver circuit module 4122 and the baseband processing circuit module 4124 may be located on the same chip or chip set, and the application processing circuit module 4126 may be located on a separate chip or chip set. In other alternative embodiments, some or all of the RF transceiver circuit module 4122, baseband processing circuit module 4124, and application processing circuit module 4126 may be combined in the same chip or chip set. In some embodiments, the RF transceiver circuit module 4122 may be part of the interface 4114. The RF transceiver circuit module 4122 may regulate the RF signal of the processing circuit module 4120.

[0118] In some embodiments, some or all of the functionality described herein as being performed by WD may be provided by processing circuitry module 4120 executing instructions stored on device-readable medium 4130, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry module 4120, for example, in a hard-wired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any embodiment of those particular embodiments, processing circuitry module 4120 may be configured to perform the functionality regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to processing circuitry module 4120 alone or other components of WD 4110, but are generally enjoyed by WD 4110 and / or generally by end users and wireless networks.

[0119] Processing circuit module 4120 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. Such operations performed by processing circuit module 4120 may include processing information obtained by processing circuit module 4120 by, for example, the following steps: converting the obtained information into other information, comparing the obtained information or the converted information with information stored in WD 4110, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of said processing.

[0120] Device-readable medium 4130 may be operable to store computer programs, software, applications (including one or more of logic, rules, code, tables, etc.) and / or other instructions (which can be executed by processing circuitry module 4120). Device-readable medium 4130 may include computer memory (e.g., random access memory (“RAM” or read-only memory (“ROM”)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (“CD” or digital video disc (“DVD”))) and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory device (which stores information, data, and / or instructions that can be used by processing circuitry module 4120). In some embodiments, processing circuitry module 4120 and device-readable medium 4130 may be considered integrated.

[0121] User interface device 4132 may provide components that allow a human user to interact with WD 4110. Such interaction may take many forms, such as visual, auditory, tactile, etc. User interface device 4132 may be operable to produce output to the user and allow the user to provide input to WD 4110. The type of interaction may vary depending on the type of user interface device 4132 installed in WD 4110. For example, if WD 4110 is a smartphone, interaction may be via a touchscreen; if WD 4110 is a smart meter, interaction may be via a screen providing usage (e.g., gallons used) or a speaker providing audible alarms (e.g., smoke detected). User interface device 4132 may include input interfaces, means, and circuit modules, as well as output interfaces, means, and circuit modules. User interface device 4132 is configured to allow input of information to WD 4110 and is connected to processing circuit module 4120 to allow processing of the input information. User interface device 4132 may include, for example, a microphone, proximity or other sensor, buttons / buttons, a touch display, one or more cameras, a USB port, or other input circuitry modules. User interface device 4132 is also configured to allow output of information from WD 4110 and to allow processing circuitry module 4120 to output information from WD 4110. User interface device 4132 may include, for example, a speaker, display, vibration circuitry module, USB port, headphone jack, or other output circuitry modules. Using one or more input and output interfaces, devices, and circuitry modules of user interface device 4132, WD 4110 can communicate with end users and / or wireless networks, allowing them to benefit from the functionality described herein.

[0122] The auxiliary device 4134 is operable to provide more specific functionality, which may generally not be performed by the WD. This may include dedicated sensors for measurements for various purposes, interfaces for additional types of communication (such as wired communication), etc. The inclusion and type of components of the auxiliary device 4134 may vary depending on the embodiment and / or circumstances.

[0123] In some embodiments, power supply 4136 may take the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a power battery, may also be used. WD 4110 may further include a power circuit module 4137 for supplying power from power supply 4136 to various components of WD 4110 that require power from power supply 4136 to perform any functionality described or shown herein. In some embodiments, power circuit module 4137 may include a power management circuit module. As a supplement or alternative, power circuit module 4137 may be operable to receive power from an external power source; in this case, WD 4110 may be connectable to an external power source (such as an electrical outlet) via an input circuit module or interface (such as a power cable). In some embodiments, power circuit module 4137 may also be operable to supply power from an external power source to power supply 4136. This may be used, for example, for charging power supply 4136. The power circuit module 4137 can perform any formatting, conversion, or other modification on the power from the power source 4136 to make the power suitable for the corresponding components of the WD 4110 that are being powered.

[0124] Figure 19 A user device according to some embodiments is shown.

[0125] Figure 19 An embodiment of a UE according to the various aspects described herein is illustrated. As used herein, a “User Equipment” or “UE” may not necessarily have the meaning of a human user who owns and / or operates the associated device. Instead, a UE may refer to a device intended for sale to or for operation by a human user, but may not or initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may refer to a device not intended for sale to or for operation by an end user, but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 42200 may be any UE recognized by the Third Generation Partnership Project (“3GPP”), including NB-IoT UEs, Machine Type Communication (“MTC”) UEs, and / or Enhanced MTC (“eMTC”) UEs. Figure 19 As shown, the UE 4200 is an example of a WD configured to communicate according to one or more communication standards (such as 3GPP's GSM, UMTS, LTE, and / or 5G standards) issued by the 3rd Generation Partnership Project (“3GPP”). As previously stated, the terms “WD” and “UE” can be used interchangeably. Accordingly, although... Figure 19 It is a UE, but the components described in this article are also applicable to WD, and vice versa.

[0126] Figure 19In this embodiment, UE 4200 includes: a processing circuit module 4201 operatively coupled to an input / output interface 4205; a radio frequency (“RF”) interface 4209; a network connectivity interface 4211; a memory 4215 including random access memory (“RAM”) 4217, read-only memory (“ROM”) 4219, and storage medium 4221, or the like; a communication subsystem 4231; a power supply 4213; and / or any other components or any combination thereof. Storage medium 4221 includes an operating system 4223, application programs 4225, and data 4227. In other embodiments, storage medium 4221 may contain other similar types of information. Some UEs may utilize... Figure 19 The components shown can be all or only a subset of the components. The level of integration between components can be changed on a per-UE basis. In addition, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0127] Figure 19 In this embodiment, processing circuit module 4201 can be configured to process computer instructions and data. Processing circuit module 4201 can be configured to implement: any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic along with appropriate firmware; one or more stored programs, along with appropriate software, a general-purpose processor, such as a microprocessor or digital signal processor (“DSP”); or any combination thereof. For example, processing circuit module 4201 may include two central processing units (“CPUs”). Data may be information in a form suitable for computer use.

[0128] In the illustrated embodiment, the input / output interface 4205 can be configured to provide a communication interface to an input device, an output device, or both input and output devices. The UE 4200 can be configured to use an output device via the input / output interface 4205. The output device can use an interface port of the same type as the input device. For example, a USB port can be used to provide input to and output from the UE 4200. The output device can be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smart card, another output device, or any combination thereof. The UE 4200 can be configured to use an input device via the input / output interface 4205 to allow the user to capture information entering the UE 4200. The input device can include a touch or presence-sensitive display, a camera (e.g., a digital camera, digital video camera, webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0129] Figure 19 In this configuration, RF interface 4209 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. Network connectivity interface 4211 can be configured to provide a communication interface to network 4243a. Network 4243a may include wired and / or wireless networks, such as local area networks (“LANs”), wide area networks (“WANs”), computer networks, wireless networks, telecommunications networks, another similar network, or any combination thereof. For example, network 4243a may include a Wi-Fi network. Network connectivity interface 4211 can be configured to include receiver and transmitter interfaces for communicating with one or more other devices over a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, or the like). Network connectivity interface 4211 can implement receiver and transmitter functionality suitable for communication network links (e.g., optical, electrical, and the like). Transmitter and receiver functionality may share circuit components, software, or firmware, or alternatively may be implemented separately.

[0130] RAM 4217 may be configured to interface with processing circuitry module 4201 via bus 4202 to provide storage or caching of data or computer instructions during the execution of software programs (such as operating systems, application programs, and device drivers). ROM 4219 may be configured to provide computer instructions or data to processing circuitry module 4201. For example, ROM 4219 may be configured to store immutable low-level system code or data for basic system functions such as basic input and output (“I / O”), startup, or reception of keystrokes from a keyboard, stored in non-volatile memory. Storage medium 4221 may be configured to include memory such as RAM, ROM, programmable read-only memory (“PROM”), erasable programmable read-only memory (“EPROM”), electrically erasable programmable read-only memory (“EEPROM”), magnetic disk, optical disk, floppy disk, hard disk, removable magnetic tape, or flash drive. In one example, storage medium 4221 may be configured to contain operating system 4223, application 4225 (such as a web browser application, widget or accessory engine, or another application), and data file 4227. Storage medium 4221 may store any operating system or combination of operating systems for use by UE 4200.

[0131] Storage medium 4221 may be configured to include multiple physical drive units, such as a redundant array of independent disks (“RAID”), a floppy disk drive, flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital multifunction disc (“HD-DVD”) optical disc drive, an internal hard disk drive, a Blu-ray disc drive, a holographic digital data storage (“HDDS”) optical disc drive, an external small dual in-line memory module (“DIMM”), synchronous dynamic random access memory (“SDRAM”), an external micro DIMM SDRAM, smart card memory (such as a subscriber identity module or a removable user identity (“SIM / RUIM”) module), other memory, or any combination thereof. Storage medium 4221 may allow UE 4200 to access computer-executable instructions, applications, or the like stored on transient or non-transient storage media to offload or upload data. Manufactured articles (such as articles manufactured using communication systems) may be tangibly embodied in storage medium 4221, which may include a device-readable medium.

[0132] Figure 19In this configuration, the processing circuit module 4201 can be configured to communicate with network 4243b using communication subsystem 4231. Networks 4243a and 4243b can be one or more of the same networks or one or more different networks. Communication subsystem 4231 can be configured to include one or more transceivers for communicating with network 4243b. For example, communication subsystem 4231 can be configured to include one or more remote transceivers for communicating with one or more remote transceivers of another device (such as another WD, UE, or base station of a radio access network (“RAN”)) capable of wireless communication according to one or more communication protocols (such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like). Each transceiver can include transmitter 4233 and / or receiver 4235 to respectively implement transmitter or receiver functionality suitable for the RAN link (e.g., frequency allocation and the like). Furthermore, the transmitter 4233 and receiver 4235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[0133] In the illustrated embodiment, the communication functions of the communication subsystem 4231 may include data communication, voice communication, multimedia communication, short-range communication (such as Bluetooth, near-field communication), location-based communication (such as using a Global Positioning System (“GPS”) to determine location), another similar communication function, or any combination thereof. For example, the communication subsystem 4231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 4243b may include wired and / or wireless networks, such as a local area network (“LAN”), a wide area network (“WAN”), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 4243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 4213 may be configured to provide alternating current (“AC”) or direct current (“DC”) power to the components of the UE 4200.

[0134] The features, benefits, and / or functions described herein may be implemented in one of the components of UE 4200, or divided across multiple components of UE 4200. Furthermore, the features, benefits, and / or functions described herein may be implemented in any combination of hardware, software, or firmware. In one example, the communication subsystem 4231 may be configured to include any component of the components described herein. Additionally, the processing circuitry module 4201 may be configured to communicate with any component of such a component via bus 4202. In another example, any component of such a component may be represented by program instructions stored in memory, which, when executed by the processing circuitry module 4201, perform the corresponding functions described herein. In another example, the functionality of any component of such a component may be divided between the processing circuitry module 4201 and the communication subsystem 4231. In yet another example, the non-computationally intensive functions of any component of such a component may be implemented in software or firmware, while the computationally intensive functions may be implemented in hardware.

[0135] Figure 20 A virtualized environment according to some embodiments is shown.

[0136] Figure 20 This is a schematic block diagram illustrating a virtualized environment 4300, in which functionality implemented through some embodiments can be virtualized. In this context, virtualization means creating a virtual version of a device or apparatus, which may include virtualized hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to nodes (e.g., virtualized base stations or virtualized radio access nodes) or to apparatuses (e.g., UEs, wireless devices, or any other type of communication device) or their components, and involves at least a portion of its functionality being implemented as an implementation of one or more virtual components (e.g., one or more applications, components, functions, virtual machines, or containers executed via one or more physical processing nodes in one or more networks).

[0137] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (which are implemented in one or more virtual environments 4300 hosted by one or more hardware nodes of hardware node 4330). Furthermore, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node may be fully virtualized.

[0138] The functionality may be implemented by one or more applications 4320 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.), which are operable to implement some of the features, functions, and / or benefits of some embodiments disclosed herein. Application 4320 runs in a virtualization environment 4300, which provides hardware 4330 including a processing circuitry module 4360 and a memory 4390. The memory 4390 contains instructions 4395 executable by the processing circuitry module 4360, thereby enabling application 4320 to operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0139] The virtualization environment 4300 includes general-purpose or special-purpose network hardware devices 4330, which include a collection of one or more processors or processing circuitry modules 4360. These processors or processing circuitry modules may be commercial off-the-shelf (“COTS”) processors, dedicated application-specific integrated circuit (“ASIC”) modules, or any other type of processing circuitry module (containing digital or analog hardware components or a dedicated processor). Each hardware device may include a memory 4390-1, which may be a non-permanent memory for temporarily storing instructions 4395 or software executed by the processing circuitry module 4360. Each hardware device may include one or more network interface controllers (“NICs”) 4370 (also referred to as network interface cards), which include a physical network interface 4380. Each hardware device may also include a non-transitory permanent machine-readable storage medium 4390-2, in which software 4395 and / or instructions executable by the processing circuitry module 4360 are stored. Software 4395 may include any type of software, including software for executing one or more virtualization layers 4350 (also known as hypervisors), software for executing virtual machine 4340, and software that allows it to perform the functions, features, and / or benefits described in relation to some embodiments described herein.

[0140] Virtual machine 4340 includes virtual processing, virtual memory, virtual networking or interface, and virtual storage devices, and can be run by a corresponding virtualization layer 4350 or hypervisor. Different embodiments of instances of virtual appliance 4320 may be implemented on one or more virtual machines 4340, and the implementation may be carried out in different ways.

[0141] During operation, the processing circuit module 4360 executes software 4395 to executor a hypervisor or virtualization layer 4350, which may sometimes be referred to as a virtual machine monitor (“VMM”). The virtualization layer 4350 provides a virtual operating platform that appears to the virtual machine 4340 as networked hardware.

[0142] likeFigure 20 As shown, hardware 4330 can be a standalone network node with general or specific components. Hardware 4330 may include antenna 43225 and may implement some functions via virtualization. Alternatively, hardware 4330 may be part of a larger cluster of hardware (e.g., in a data center or customer premises equipment (“CPE”)), where many hardware nodes work together and are managed via management and orchestration (“MANO”) 43100, which also oversees the lifecycle management of application 4320.

[0143] Hardware virtualization is sometimes referred to as Network Functions Virtualization (“NFV”). NFV can be used to consolidate many types of network devices onto industry-standard high-capacity server hardware, physical switches, and physical storage devices, which can reside in data center and customer site equipment.

[0144] In the context of NFV, virtual machine 4340 can be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each virtual machine 4340 and the part of hardware 4330 that executes that virtual machine (if it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine and other virtual machines of virtual machine 4340) form an independent virtual network element (“VNE”).

[0145] Within the context of NFV, a Virtual Network Function (“VNF”) is responsible for handling specific network functions running in one or more virtual machines 4340 on top of the hardware networking infrastructure 4330, and corresponds to Figure 20 Application 4320.

[0146] In some embodiments, one or more radio units 43200, each including one or more transmitters 43220 and one or more receivers 43210, may be coupled to one or more antennas 43225. The radio unit 43200 may communicate directly with the hardware node 4330 via one or more suitable network interfaces and may be combined with virtual components to provide radio capabilities (such as radio access nodes or base stations) for virtual nodes.

[0147] In some embodiments, some signaling can be activated by using a control system 43230, which can alternatively be used for communication between hardware node 4330 and radio unit 43200.

[0148] Figure 21 This illustrates a telecommunications network that connects to a host computer via an intermediate network, according to some embodiments.

[0149] Reference Figure 21According to one embodiment, the communication system includes a telecommunications network 4410 (such as a 3GPP-type cellular network), which includes an access network 4411 (such as a radio access network) and a core network 4414. The access network 4411 includes multiple base stations 4412a, 4412b, and 4412c, such as NBs, eNBs, gNBs, or other types of wireless access points, each defining a corresponding coverage area 4413a, 4413b, and 4413c. Each base station 4412a, 4412b, and 4412c can be connected to the core network 4414 via a wired or wireless connection 4415. A first UE 4491 located in coverage area 4413c is configured to wirelessly connect to or be paged by the corresponding base station 4412c. A second UE 4492 located in coverage area 4413a can wirelessly connect to the corresponding base station 4412a. Although multiple UEs 4491 and 4492 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is located in a coverage area or where a single UE is connected to the corresponding base station 4412.

[0150] Telecommunications network 4410 is itself connected to host computer 4430, which may be implemented in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. Host computer 4430 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. Connections 4421 and 4422 between telecommunications network 4410 and host computer 4430 may extend directly from core network 4414 to host computer 4430, or may be made via optional intermediate network 4420. Intermediate network 4420 may be one or more of public, private, or hosted networks; intermediate network 4420 (if any) may be a backbone network or the Internet; in particular, intermediate network 4420 may include two or more subnetworks (not shown).

[0151] Figure 21The overall communication system enables connectivity between connected UEs 4491 and 4492 and host computer 4430. This connectivity can be described as an over-the-top (“OTT”) connection 4450. Host computer 4430 and connected UEs 4491 and 4492 are configured to transmit data and / or signaling via OTT connection 4450 using access network 4411, core network 4414, any intermediate network 4420, and other possible infrastructure (not shown) acting as intermediaries. OTT connection 4450 can be transparent in the sense that the participating communication devices within it are unaware of the routing of uplink and downlink communications. For example, base station 4412 may not be informed, or need not be informed, about past routing of incoming downlink communications containing data originating from host computer 4430 that will be forwarded (e.g., switched) to connected UE 4491. Similarly, base station 4412 does not need to know the future routing of outgoing uplink communication from UE 4491 to host computer 4430.

[0152] Figure 22 The illustration shows a host computer communicating with a user equipment via a base station through a partial wireless connection, according to some embodiments.

[0153] Now refer to Figure 22 This section describes an example implementation of the UE, base station, and host computer described above, according to one embodiment. In the communication system 4500, the host computer 4510 includes hardware 4515, which includes a communication interface 4516 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of the communication system 4500. The host computer 4510 further includes a processing circuit module 4518, which may have storage and / or processing capabilities. In particular, the processing circuit module 4518 may include one or more programmable processors, application-specific integrated circuit modules, field-programmable gate arrays, or combinations of these devices (not shown) suitable for executing instructions. The host computer 4510 further includes software 4511, which is stored in the host computer 4510 or is accessible to the host computer 4510 and executable by the processing circuit module 4518. The software 4511 includes a host application 4512. Host application 4512 is operable to provide services to remote users, such as UE 4530 connected via OTT connection 4550 terminated between UE 4530 and host computer 4510. In providing services to remote users, host application 4512 can provide user data transmitted using OTT connection 4550.

[0154] The communication system 4500 further includes a base station 4520, provided in a telecommunications system, and includes hardware 4525 enabling it to communicate with a host computer 4510 and a UE 4530. Hardware 4525 may include: a communication interface 4526 for establishing and maintaining a wired or wireless connection to different communication devices of the communication system 4500; and a radio interface 4527 for establishing and maintaining at least a wireless connection 4570 with the UE 4530, the UE 4530 being located within the coverage area served by the base station 4520. Figure 22 (Not shown in the image). Communication interface 4526 can be configured to facilitate a connection 4560 to host computer 4510. Connection 4560 can be direct, or it can be via the core network of a telecommunications system (…). Figure 9 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 4525 of the base station 4520 further includes a processing circuit module 4528, which may include one or more programmable processors, application-specific integrated circuit modules, field-programmable gate arrays, or combinations of such devices (not shown) suitable for executing instructions. The base station 4520 further has software 4521, which is either internally stored or accessible via an external connection.

[0155] The communication system 4500 further includes the previously mentioned UE 4530. Its hardware 4535 may include a radio interface 4537 configured to establish and maintain a wireless connection 4570 with a base station serving the coverage area currently occupied by the UE 4530. The hardware 4535 of the UE 4530 further includes a processing circuitry module 4538, which may include one or more programmable processors, application-specific integrated circuit modules, field-programmable gate arrays, or combinations of these devices (not shown) suitable for executing instructions. The UE 4530 further includes software 4531, which is stored in or accessible to the UE 4530 and executable by the processing circuitry module 4538. The software 4531 includes a client application 4532. The client application 4532 may be operable to provide services to human or non-human users via the UE 4530 with the support of a host computer 4510. In host computer 4510, host application 4512 can communicate with client application 4532 via OTT connection 4550 terminated between UE 4530 and host computer 4510. When providing services to a user, client application 4532 can receive request data from host application 4512 and provide user data in response to the request data. OTT connection 4550 can transmit request data and user data. Client application 4532 can interact with the user to generate the user data it provides.

[0156] Please note, Figure 22 The host computer 4510, base station 4520, and UE 4530 shown can respectively connect with... Figure 21 The host computer 4430, one of the base stations 4412a, 4412b, and 4412c, and one of the UEs 4491 and 4492 are similar to or the same. That is, the internal operation of these entities can be as follows: Figure 22 As shown, and independently, the surrounding network topology can be Figure 21 The topology.

[0157] Figure 22 The diagram abstractly depicts an OTT connection 4550 to illustrate communication between a host computer 4510 and a UE 4530 via a base station 4520, without explicitly mentioning any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine the routing, configuring it to be either for the UE 4530, the service provider operating the host computer 4510, or hidden from both. While the OTT connection 4550 is active, the network infrastructure can further make decisions, dynamically altering the routing (e.g., based on network load balancing considerations or reconfiguration).

[0158] The wireless connection 4570 between UE 4530 and base station 4520 conforms to the teachings of the embodiments described throughout this disclosure. One or more embodiments of the various embodiments may improve the performance of providing OTT services to UE 4530 using OTT connection 4550, wherein wireless connection 4570 forms the final segment. More precisely, the teachings of these embodiments may improve random access speed and / or reduce random access failure rate, and thereby provide, for example, faster and / or more reliable random access.

[0159] For the purpose of monitoring data rate, latency, and other factors for improvement in one or more of the embodiments, a measurement process may be provided. Optional network functionality may further exist for reconfiguring the OTT connection 4550 between the host computer 4510 and the UE 4530 in response to changes in measurement results. The measurement process and / or the network functionality for reconfiguring the OTT connection 4550 may be implemented in the software 4511 and hardware 4515 of the host computer 4510, or in the software 4531 and hardware 4535 of the UE 4530, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices within the OTT connection 4550; the sensors may participate in the measurement process by providing values ​​of the monitored quantities exemplified above, or by providing values ​​of other physical quantities from which the software 4511, 4531 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 4550 may include message formatting, retransmission settings, preferred routing, etc.; reconfiguration does not affect the base station 4520, and it may be unknown or undetectable to the base station 4520. Such processes and functionalities may be known and practiced in the art. In some embodiments, measurement may involve proprietary UE signaling that facilitates the host computer 4510 to measure throughput, propagation time, latency, and the like. Measurements are possible because software 4511 and 4531 use the OTT connection 4550 to transmit messages, particularly empty or 'false' messages, while it monitors propagation time, errors, etc.

[0160] Figure 23 The present invention illustrates a method implemented in a communication system comprising a host computer, a base station, and a user equipment, according to some embodiments.

[0161] Figure 23 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figures 21-22 The host computers, base stations, and UEs mentioned above. For the sake of brevity, this section will only contain descriptions of... Figure 23 The accompanying drawings are referenced. In step 4610, the host computer provides user data. In sub-step 4611 of step 4610 (which may be optional), the host computer provides user data by executing a host application. In step 4620, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, in step 4630 (which may be optional), the base station transmits user data to the UE, the user data being carried in the transmission initiated by the host computer. In step 4640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0162] Figure 24 The present invention illustrates a method implemented in a communication system comprising a host computer, a base station, and a user equipment, according to some embodiments.

[0163] Figure 24 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figures 21-22 The host computers, base stations, and UEs mentioned above. For the sake of brevity, this section will only contain descriptions of... Figure 24 The accompanying drawings are referenced. In step 4710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 4720, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission may be carried out via a base station. In step 4730 (which may be optional), the UE receives the user data carried in the transmission.

[0164] Figure 25 The present invention illustrates a method implemented in a communication system comprising a host computer, a base station, and a user equipment, according to some embodiments.

[0165] Figure 25 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figures 21-22 The host computers, base stations, and UEs mentioned above. For the sake of brevity, this section will only contain descriptions of... Figure 25 The accompanying drawings are referenced. In step 4810 (which may be optional), the UE receives input data provided by the host computer. Alternatively or complementaryly, in step 4820, the UE provides user data. In sub-step 4821 of step 4820 (which may be optional), the UE provides user data by executing a client application. In sub-step 4811 of step 4810 (which may be optional), the UE executes a client application that responds to the received input data provided by the host computer to provide user data. In providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE provides the transmission of user data to the host computer in sub-step 4830 (which may be optional). According to the teachings of the embodiments described throughout this disclosure, in step 4840 of the method, the host computer receives user data transmitted from the UE.

[0166] Figure 26The present invention illustrates a method implemented in a communication system comprising a host computer, a base station, and a user equipment, according to some embodiments.

[0167] Figure 26 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figures 21-22 The host computers, base stations, and UEs mentioned above. For the sake of brevity, this section will only contain descriptions of... Figure 26 The accompanying drawings are referenced. In step 4910 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 4920 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 4930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0168] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry modules, which may include one or more microprocessors or microcontrollers and may include digital signal processors (“DSPs”), dedicated digital logic, and other digital hardware such as these. The processing circuitry modules may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (“ROM”), random access memory (“RAM”), cache memory, flash memory devices, optical storage devices, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In some implementations, according to one or more embodiments of this disclosure, the processing circuitry modules may be used to cause corresponding functional units to perform corresponding functions.

[0169] The term “unit” may have the conventional meaning in the field of electronic devices, electrical apparatus and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc., as described herein.

[0170] The following discusses further definitions and examples.

[0171] In the above description of various embodiments of this disclosure, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the disclosure. Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will be further understood that terms (such as those defined in commonly used dictionaries) should be interpreted as having the same meaning as they have in the context of this specification and the relevant field, and will not be interpreted in an idealized or overly formal sense unless precisely as defined herein.

[0172] When an element is referred to as being “connected,” “coupled,” “responded,” or a variation thereof to another element, it is capable of being directly connected, coupled, or responded to the other element, or there may be an intermediate element. In contrast, when an element is referred to as being “directly connected,” “directly coupled,” “directly responded,” or a variation thereof to another element, there is no intermediate element. Similar numbers throughout refer to similar elements. Furthermore, “coupled,” “connected,” “responded,” or a variation thereof, as used herein, may include wireless coupling, connection, or response. As used herein, the singular forms “a / an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. For brevity and / or clarity, well-known functions or constructions may not be described in detail. The term “and / or” (abbreviated “ / ”) includes any and all combinations of one or more of the associated listed items.

[0173] It will be understood that while the terms "first," "second," "third," etc., may be used herein to describe various elements / operations, these elements / operations should not be limited by these terms. These terms are used only to distinguish one element / operation from another. Thus, a first element / operation in some embodiments may be referred to as a second element / operation in other embodiments without departing from the teachings of this disclosure. The same reference numerals or the same reference designations refer to the same or similar elements throughout this specification.

[0174] As used herein, the terms “comprise,” “comprising,” “comprises,” “include,” “including,” “includes,” “have,” “has,” “having,” or variations thereof are open-ended and include one or more of the stated features, integers, elements, steps, components, or functions, but do not exclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or groups thereof. Furthermore, as used herein, the common abbreviation “eg (for example),” derived from the Latin phrase “exempli gratia,” may be used to introduce or elaborate on one or more general examples of previously mentioned items and is not intended to be a limitation on such items. The common abbreviation “ie (i.e.),” derived from the Latin phrase “id est,” may be used to elaborate on a specific item in a more general manner.

[0175] Example embodiments are described herein with reference to flowchart illustrations and / or block diagrams of computer-implemented methods, apparatus (systems and / or devices), and / or computer program products. It should be understood that the blocks in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions executed by one or more computer circuits. These computer program instructions can be provided to processor circuitry of general-purpose computer circuitry, special-purpose computer circuitry, and / or other programmable data processing circuitry to produce a machine that causes instruction translation, executed via a processor of a computer and / or other programmable data processing apparatus, and controls transistors, values ​​stored in memory locations, and other hardware components within such circuit modules to implement the functions / actions specified in the block diagrams and / or one or more flowchart blocks, thereby creating methods (functionality) and / or structures for implementing the functions / actions specified in the block diagrams and / or one or more flowchart blocks.

[0176] These computer program instructions may also be stored in a tangible computer-readable medium, which is capable of directing a computer or other programmable data processing device to operate in a particular manner such that the instructions stored in the computer-readable medium produce an article of manufacture containing instructions that implement the functions / actions specified in block diagrams and / or one or more flowchart blocks. Accordingly, embodiments of this disclosure may be implemented in hardware and / or in software (including firmware, resident software, microcode, etc.) running on a processor (such as a digital signal processor that may be generally referred to as a "circuit module," "module," or variations thereof).

[0177] It should also be noted that in some alternative implementations, the functions / actions described in the boxes may occur outside the order shown in the flowchart. For example, two boxes shown consecutively may be executed substantially simultaneously, or sometimes the boxes may be executed in reverse order (depending on the functions / actions involved). Furthermore, the functionality of a given box in a flowchart and / or block diagram may be divided into multiple boxes, and / or the functionality of two or more boxes in a flowchart and / or block diagram may be at least partially integrated. Finally, without departing from the scope of this disclosure, other boxes may be added / inserted between the shown boxes, and / or boxes / operations may be omitted. Also, although some diagrams in the illustrations include arrows on communication paths to indicate the main direction of communication, it should be understood that communication may occur in the direction opposite to the depicted arrows.

[0178] Many variations and modifications can be made to the embodiments without substantially departing from the principles of this disclosure. All such variations and modifications herein are intended to be included within the scope of this disclosure. Accordingly, the subject matter disclosed above is to be considered illustrative rather than restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments falling within the spirit and scope of this disclosure. Therefore, to the maximum extent permitted by law, the scope of this disclosure will be determined by the widest permissible interpretation of this disclosure, including examples of embodiments and their equivalents, and should not be construed or limited by the foregoing detailed description.

Claims

1. A method performed by a user equipment (UE) capable of operating in a multi-radio dual connectivity (MR-DC) mode within a network, the method comprising: Initiate the reconstruction process; Perform cell selection and, as a result, have the cell selected by the UE; as well as Determine whether the UE has a stored configuration for the selected cell, and release the MR-DC in response to determining that the UE does not have a stored configuration for the selected cell and that the UE is configured with a conditional handover CHO.

2. The method as described in claim 1, wherein, Determining whether the UE has a stored configuration for the selected cell includes: determining that the selected cell of the UE is a cell for which the UE has a target cell configuration for which it does not have a stored configuration.

3. The method as described in any one of claims 1-2, wherein, The storage configuration for the selected cell corresponds to the ReconfigurationWithSync information element, which is included in the MasterCellGroup in VarConditionalReconfig.

4. The method as described in any one of claims 1-2, wherein, The MR-DC configuration is one of the following: SRB3; and The measConfig associated with the secondary cell group ("SCG").

5. The method as described in any one of claims 1-2, wherein, The release of the MR-DC includes at least one of the following: If configured, release SRB3; Release the measurement configuration associated with the secondary cell group ("SCG"); and If the UE is configured with an NR SCG, then release the SCG configuration.

6. The method as claimed in any one of claims 1-2, wherein, In response to the UE being configured with a new air interface (NR), the SCG performs the MR-DC release by releasing the SCG configuration through the following actions: If configured, reset (1710) SCG MAC; For each RLC bearer that is part of the SCG configuration, perform (1720) Radio Link Control RLC Bearer Release; and Release (1730) the SCG configuration.

7. The method as described in any one of claims 1-2, wherein, In response to the UE being configured with a conditional primary / secondary cell change CPC, the MR-DC release includes releasing the CPC configuration.

8. The method of claim 7, wherein, The CPC includes configurations generated by auxiliary nodes that are associated with conditions of a certain configuration.

9. The method as claimed in any one of claims 1-2, wherein, In response to the UE being configured with Conditional Primary / Secondary Cell Additional CPA, the MR-DC release includes releasing the CPA configuration.

10. The method of claim 9, wherein, The CPA includes the configuration generated by the auxiliary node associated with the conditions of a certain configuration.

11. The method as claimed in any one of claims 1-2, wherein, The CHO, CPA, and CPC include conditional reconfiguration, and Deleting the CHO, CPA, and / or CPC includes releasing and / or deleting UE variables corresponding to the configuration storage.

12. The method of claim 1, further comprising determining (1550) whether the UE is configured for conditional reconfiguration.

13. The method of claim 12, wherein, In response to the UE not being configured with conditional reconfiguration and the UE being configured with MR-DC, the UE performs MR-DC release.

14. The method of claim 12, wherein, In response to the UE being configured for conditional reconfiguration, the UE further attempts to perform a CHO during cell selection.

15. The method of claim 1, wherein, The initiation of the reconstruction process is in response to at least one of the following: A radio link failure was detected in the primary cell group (MCG). Reconfiguration due to the synchronization failure of the MCG; Mobility resulting from NR failures; Receive integrity check failure indication from a lower layer regarding SRB1 or SRB2, unless the integrity check failure is detected on an RRCRestablishment message; In the event of an RRC connection reconfiguration failure; A radio link failure in the secondary cell group SCG was detected when MCG transmission was suspended. Reconfiguration performed when MCG transmission is suspended due to a synchronization failure of the SCG; SCG change failure during MCG transmission in NE-DC; SCG configuration failure when MCG transmission is suspended; as well as When the MCG is suspended, an integrity check fault indication comes from the lower layer of the SCG regarding SRB3.

16. The method of claim 1, wherein, Selecting the cell includes selecting the cell before the delayed MR-DC deletion, and Specifically, in response to the UE determining whether it is configured with conditional reconfiguration... The method further includes: The application (1570) is associated with the stored condRRCReconfig of the cell; and In response to the UE determining that the cell is not one of the candidate cells containing reconfigurationWithSync in masterCellGroup in VarConditionalReconfig, the MR-DC release is performed (1540).

17. The method of any one of claims 1-2, further comprising performing (1540) MR-DC release.

18. The method of claim 17, wherein, Performing the MR-DC release includes at least one of the following: If configured, release SRB3; Release the measurement configuration associated with the secondary cell group SCG; Release the measurement configuration associated with the secondary node; If the UE is configured with an NR SCG, then the SCG configuration is released; this includes at least the following actions: if configured, then the SCG MAC is reset; For each RLC bearer that is a part of the SCG configuration, perform the RLC bearer release procedure; release the SCG configuration; If the UE is configured with a conditional primary / secondary cell change CPC, then release the CPC configuration; If the UE is configured with Conditional Primary / Secondary Cell Additional CPA, then release the CPA configuration; as well as If the UE is configured with conditional reconfiguration, then the CPA configuration is released.

19. A user equipment (UE) (1200) capable of operating in a network in a multi-radio dual-connectivity (MR-DC) mode, the UE comprising: Processing circuit module (1203); as well as Memory (1205), coupled to the processing circuit module and storing instructions executable by the processing circuit module to cause the UE to perform operations, including: Initiate the reconstruction process; Perform cell selection to select the cell chosen by the UE; as well as Determine whether the UE has a stored configuration for the selected cell, and release the MR-DC in response to determining that the UE does not have a stored configuration for the selected cell and that the UE is configured with a conditional handover CHO.

20. The user equipment as claimed in claim 19, wherein, The instruction causes the UE to determine whether it has a storage configuration for the selected cell by determining that the cell selected by the UE is a cell for which the UE does not have a target cell configuration.

21. The user equipment as claimed in claim 19 or 20, wherein, The instruction can be further executed by the processing circuit module to cause the UE to apply the stored configuration in response to the UE having a stored configuration for the selected cell.

22. The user equipment as claimed in any one of claims 19 to 20, wherein, The instruction can be further executed by the processing circuit module to cause the UE to perform MR-DC release in response to the fact that the cell selected by the UE is not configured with an instruction from the network that the UE can execute CHO at rebuild initiation.

23. The user equipment as claimed in any one of claims 19-20, wherein, The storage configuration for the selected cell corresponds to the ReconfigurationWithSync information element, which is contained in the MasterCellGroup within VarConditionalReConfig.

24. The user equipment as claimed in any one of claims 19-20, wherein, The MR-DC configuration is one of the following: SRB3; and The measConfig associated with the secondary cell group ("SCG").

25. The user equipment as claimed in any one of claims 19-20, wherein, Releasing the MR-DC includes at least one of the following: If configured, release SRB3; Release the measurement configuration associated with the secondary cell group ("SCG"); and If the UE is configured with an NR SCG, then release the SCG configuration.

26. An apparatus-readable medium having stored program code to be executed by a processing circuit module (1203) of a user equipment (UE) (1200), wherein execution of the program code causes the UE to perform an operation including any of the operations of claims 1-18.

27. A computer program product comprising a non-transitory computer-readable medium storing program code executable by a processing circuit module (1203) of a user equipment (UE) (1200) to perform operations including any of the operations of claims 1-18.

Images