Primary cell group failure when there is an ongoing secondary cell group change

Abstract

A communication device configured to operate in dual connectivity ("DC") with a primary node ("MN") and a secondary node ("SN") may be configured with a primary cell group ("MCG") configuration associated with the MN and a secondary cell group ("SCG") configuration associated with the SN. The communication device may detect a radio link failure on the MCG. The communication device may also determine whether a primary-secondary cell group cell ("PSCell") change procedure is in progress. The communication device may also respond to a radio link failure on the MCG based on whether a PSCell change procedure is in progress.

Description

Technical Field

[0001] The present disclosure relates generally to communications, and more particularly to handling a master cell group ("MCG") failure when there is an ongoing secondary cell group ("SCG") change. Background Art

[0002] The 5th generation ("5G") in the 3rd Generation Partnership Project ("3GPP") introduces both a new core network ("5GC") and a new radio access network ("NR"). However, 5GC may also support other radio access technologies ("RATs") in addition to NR. It has been agreed that Long Term Evolution ("LTE") (or Evolved Universal Terrestrial Radio Access ("E-UTRA")) should also be connected to 5GC, and that LTE base stations connected to 5GC are called ng-eNBs and are part of the 5th Generation Radio Access Network ("NG-RAN"), which may also include NR base stations ("gNBs"). Figure 1 It shows how base stations connect to each other and to nodes in 5GC.

[0003] In 3GPP, dual connectivity ("DC") has been specified for LTE and between LTE and NR. In DC, two nodes may be involved, a primary node ("MN or MeNB") and a secondary node ("SN or SeNB"). Multi-connectivity ("MC") is the term used when more than two nodes are involved. In addition, it has been proposed in 3GPP that DC be used in ultra-reliable low-latency communication ("URLLC") situations to enhance robustness and avoid connection interruptions.

[0004] There are different ways to deploy 5G networks that interwork or do not interwork with LTE (also known as E-UTRA) and Evolved Packet Core (“EPC”), such as Figures 2 to 7 In principle, NR and LTE can be deployed without any interworking, represented by NR standalone (“SA”) operation, i.e., the gNB in ​​NR can be connected to the 5GC, and the eNB can be connected to the EPC, with no direct interconnection between the two at the RAN level (e.g., in Figures 2 to 3 On the other hand, the first supported NR version is E-UTRAN-NR Dual Connectivity ("EN-DC"), such as Figure 4As shown. In such a deployment, dual connectivity between NR and LTE is applied with LTE as the primary node and NR as the secondary node. The RAN node (gNB) supporting NR may not have a control plane connection with the EPC, instead it may rely on LTE as the primary node ("MeNB"). This may also be referred to as non-independent ("NSA") NR. The functionality of NSA NR may be limited and may be used as a booster and / or diversity branch for UEs in connected mode, but RRC_IDLE UEs may not be able to reside on these NR cells. The NR cell may be able to act as a "non-independent cell" for one user equipment or wireless device ("UE") while acting as an "independent cell" for other UEs. In order to be able to act as an "independent cell", the gNB supporting the NR cell may need to be connected to the 5GC.

[0005] With the introduction of 5GC, other options may also be effective. As mentioned above, Figure 3 Supports standalone NR deployment, where gNB is connected to 5GC. Similarly, LTE can also be connected to 5GC, such as Figure 6 As shown (also referred to as eLTE, E-UTRA / 5GC, or LTE / 5GC, and the node may be referred to as ng-eNB). In these cases, both NR and LTE are considered part of NG-RAN (and both ng-eNB and gNB may be referred to as NG-RAN nodes). Figure 5 and Figure 8 Another variant of dual connectivity between LTE and NR is shown, which will be standardized as part of the NG-RAN connected to the 5GC, denoted by Multi-RAT Dual Connectivity ("MR-DC"). Figure 4 As shown), NE-DC (as Figure 5 As shown), NGEN-DC (as Figure 7 shown) and NR-DC ( Figure 3 The variants shown) can fall under the MR-DC umbrella. Figure 4 Depicted is an EN-DC where LTE is the primary node and NR is secondary (using EPC CN). Figure 5 Depicts NE-DC with NR as primary node and LTE as secondary (using 5GCN). Figure 7 Depicted is a NGEN-DC where LTE is the primary node and NR is secondary (with 5GCN). Figure 3 A variant may depict NR-DC with dual connectivity, where both the primary and secondary are NR (using 5GCN).

[0006] Since the migration of these options can vary between different operators, multiple options can be deployed in parallel in the same network. Figure 3 and Figure 5In the same network, there may be NR base stations that support the options shown in Figure 4 , Figure 6 and Figure 7 The eNB base station of the options shown in . In combination with the dual connectivity solution between LTE and NR, carrier aggregation (“CA”) in each cell group (e.g., primary cell group (“MCG”) and secondary cell group (“SCG”)) and dual connectivity between nodes on the same RAT (e.g., New Radio New Radio Dual Connectivity (“NR-NR DC”)) can also be supported. For LTE cells, the result of these different deployments is the coexistence of LTE cells associated with eNBs connected to EPC, 5GC, or EPC / 5GC.

[0007] If an MCG link failure occurs during an SCG change, communication delays of the MCG failure information may occur and / or the MCG failure information may never reach the MN. Summary of the invention

[0008] According to some embodiments, a method of operating a communication device is provided. The communication device may be configured to operate in a dual connection ("DC") with a master node ("MN") and a secondary node ("SN"), and is configured with a master cell group ("MCG") configuration associated with the MN and a secondary cell group ("SCG") configuration associated with the SN. The method may include detecting a radio link failure on the MCG. The method may also include determining whether a primary and secondary cell group cell ("PSCell") change process is in progress. The method may also include responding to a radio link failure on the MCG based on whether a PSCell change process is in progress.

[0009] According to other embodiments, a method of operating a first network node in a communication network is provided. The communication network may include a communication device configured to operate in a dual connection ("DC") with a primary node ("MN") and a secondary node ("SN"), and the first network node may be the MN. The method may include sending a first message to a target SN as part of a primary-secondary cell group cell ("PSCell") change procedure performed by the communication device. The method may also include detecting a radio link failure between the first network node and the communication device. The method may also include sending a second message to the target SN in response to detecting the radio link failure.

[0010] According to other embodiments, a network node, a communication device, a computer program and / or a computer program product for performing one or more of the above methods is provided.

[0011] The various embodiments described herein allow the UE and the network to avoid any ambiguity regarding the SCG configuration in response to an MCG failure during a PSCell / SCG change. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The accompanying drawings illustrate certain non-limiting embodiments of the inventive concept, and are included to provide a further understanding of the present disclosure, and are incorporated in and constitute a part of this application. In the drawings:

[0013] Figure 1 is a diagram showing an example of a 5th Generation System (“5GS”) architecture including 5GC and NG-RAN;

[0014] Figures 2 to 7 is a diagram showing an example of LTE and NR interworking options;

[0015] Figure 8 is a block diagram illustrating an example of a control plane architecture for dual connectivity in LTE DC and EN-DC according to some embodiments of the present disclosure;

[0016] Fig. 9 is a block diagram illustrating an example of network-side protocol termination options for MCG, SCG, and split bearers in MR-DC (EN-DC) with EPC according to some embodiments of the present disclosure;

[0017] Fig.10 is a block diagram illustrating an example of a network architecture for a control plane in an EN-DC according to some embodiments of the present disclosure;

[0018] Fig.11 is a block diagram illustrating an example of a radio link failure due to a physical layer problem according to some embodiments of the present disclosure;

[0019] Fig.12 is a table showing examples of timers according to some embodiments of the present disclosure;

[0020] Fig.13 is a table showing examples of constants according to some embodiments of the present disclosure;

[0021] Fig.14 is a signal flow diagram illustrating an example of SCG fault information according to some embodiments of the present disclosure;

[0022] Fig.15 is a signal flow diagram illustrating an example of MCG fault information according to some embodiments of the present disclosure;

[0023] Fig.16 is a block diagram illustrating an example of a wireless device ("UE") according to some embodiments of the present disclosure;

[0024] Fig.17 is a block diagram illustrating an example of a radio access network ("RAN") node (e.g., a base station eNB / gNB) according to some embodiments of the present disclosure;

[0025] Fig.18 is a block diagram illustrating an example of a core network ("CN") node (e.g., an AMF node, an SMF node, an OAM node, etc.) according to some embodiments of the present disclosure;

[0026] Fig.19 is a flow chart illustrating an example of a process performed by a wireless device according to some embodiments of the present disclosure;

[0027] Fig. 20 is a flow chart illustrating an example of a process performed by a network node according to some embodiments of the present disclosure;

[0028] Fig.21 is a block diagram of a wireless network according to some embodiments;

[0029] Fig. 22 is a block diagram of a user equipment according to some embodiments;

[0030] Fig.23 is a block diagram of a virtualization environment according to some embodiments;

[0031] Fig.24 is a block diagram of a telecommunications network connected to a host computer via an intermediate network according to some embodiments;

[0032] Fig.25 is a block diagram of a host computer communicating with a user device via a base station over a partially wireless connection according to some embodiments;

[0033] Fig.26 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;

[0034] Fig. 27 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;

[0035] Fig.28 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; and

[0036] Fig.29 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 DESCRIPTION

[0037] Hereinafter, the inventive concept will be described more fully with reference to the accompanying drawings, in which examples of embodiments of the inventive concept are shown. However, the inventive concept can be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided so that the disclosure will be comprehensive and complete, and the scope of the inventive concept will be fully conveyed to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. A component from one embodiment can be assumed by default to be present in / used in another embodiment.

[0038] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, some details of the embodiments may be modified, omitted or expanded without departing from the scope of the subject matter.

[0039] DC has been standardized for LTE and E-UTRA-NR DC (EN-DC). The design of LTE DC and EN-DC can differ when it comes to which nodes control what. Two examples include: a centralized embodiment (e.g., LTE-DC) and a decentralized embodiment (e.g., EN-DC).

[0040] Figure 8 An example of a schematic control plane architecture for LTE DC and EN-DC is shown. In EN-DC, the SN may have a separate RRC entity (NR RRC). Although the SN may need to coordinate with the MN, the SN may control the UE and sometimes without knowing the MN. In LTE-DC, the RRC decision may come from the MN (e.g., MN to UE). The SN may still decide on the configuration of the SN because the SN may be the only node that knows the resources and capabilities of the SN.

[0041] The differences between EN-DC and LTE DC may include: introduction of split bearers from SN (called SCG split bearers); introduction of split bearers for RRC; and introduction of direct RRC from SN (also called SCG SRBs).

[0042] Figures 9 and 10 An example of a user plane ("UP") and control plane ("CP") architecture for EN-DC is depicted.

[0043] In the case where LTE is the primary node and NR is the secondary node, the SN can be called SgNB (where gNB is the NR base station), and the MN is the MeNB. In the case where NR is the primary node and LTE is the secondary node, the corresponding terms are SeNB and MgNB.

[0044] Splitting the RRC messages can be used to create diversity and the transmitter can decide to select one of the links to schedule the RRC message or it can duplicate the message on both links. In the downlink, path switching between MCG or SCG branches or duplication on both can be left to the network implementation. For UL, the network can configure the UE to use the MCG, SCG, or both branches. The terms "branch", "path", and "RLC bearer" are used interchangeably throughout this document.

[0045] When carrier aggregation ("CA") is configured, the UE may have only one RRC connection with the network. In addition, one serving cell provides NAS mobility information upon RRC connection establishment / reestablishment / switching, and one serving cell provides security input upon RRC connection reestablishment / switching. This cell may be referred to as a primary cell ("PCell"). In addition, depending on the UE capabilities, a secondary cell ("SCell") may be configured to form a set of serving cells together with the PCell. Therefore, the set of serving cells configured for the UE always includes one PCell and one or more SCells. In addition, when dual connectivity is configured, it may be the case that one carrier under the SCG may be used as a PSCell. Therefore, in this case, we have one PCell and one or more SCells on the MCG, and one PSCell and one or more SCells on the SCG.

[0046] Reconfiguration, addition and removal of SCells can be performed via RRC. RRC can also add, remove or reconfigure SCells for use with the target PCell when switching within a RAT. When a new SCell is added, dedicated RRC signaling is used to send all required system information for the SCell, i.e., when in connected mode, the UE does not need to obtain broadcast system information directly from the SCell.

[0047] Fig.11 is a block diagram depicting a radio link failure due to a physical layer problem. It may happen that the UE loses coverage of the cell to which the UE is currently connected. This may happen in situations when the UE enters a fading trough, or a handover is required as described above, but the handover fails for one reason or another. This is especially true if the "handover region" is very short, as will be described further below.

[0048] The quality of the radio link can be monitored in the UE (e.g., at the physical layer, as described in 3GPP TS 38.300, TS 38.331, and TS 38.133). When the physical layer detects that a problem has occurred according to the standard defined in TS 38.133, the physical layer sends an indication of the detected problem (out-of-sync indication) to the RRC protocol.

[0049] Some of the timers and counters mentioned above are Figure 12 to Figure 13 As shown in the table. Fig.12 The table in describes the start, stop and expiration of MCG timer T310 and timer T311. Fig.13 The table in describes the use of the out-of-sync constant N310 and the synchronization constant N311. After a configurable number (e.g., out-of-sync constant N310) of such consecutive indications, a timer (T310) may be started. If the link quality does not improve (recover) while the timer T310 is running (e.g., there are no synchronization number N311 consecutive indications from the physical layer), a radio link failure may be declared in the UE, see Fig.11 .

[0050] The UE reads the timer value from the system information broadcast in the cell.Alternatively, the UE may be configured with values ​​of UE-specific timers and constants using dedicated signaling, ie, where specific values ​​are given to specific UEs using messages directed only to each specific UE.

[0051] If for an MCG, timer T310 expires and as indicated above, the UE initiates connection re-establishment to resume the ongoing RRC connection. The procedure now includes a cell selection by the UE. That is, an RRC_CONNECTED UE should now try to autonomously find a better cell to connect to, since according to the described measurements, the connection to the previous cell failed (it may happen that the UE returns to the first cell anyway, but the same procedure is then performed). Once a suitable cell has been selected (as further described in TS 38.304), the UE requests re-establishment of the connection in the selected cell. It is important to note the difference in mobility behavior compared to the network controlled mobility that is normally applied, since RLF results in UE-based cell selection.

[0052] If the re-establishment is successful (which depends inter alia on whether the selected cell and the gNB controlling that cell are ready to maintain the connection to the UE), the connection between the UE and the gNB can be restored.

[0053] A re-establishment failure means that the UE enters RRC_IDLE and the connection is released. In order to continue communication, a brand new RRC connection must then be requested and established.

[0054] The reason for introducing the above timers T310, T311 and counters N310, N311 is to add some freedom and hysteresis to the criteria for configuring when the radio link should be considered failed (and restored). This is desirable because if the loss of link quality is temporary and the UE successfully recovers the connection without any further action or process (e.g. before timer T310 expires, or before the count reaches the value N310), then the performance for the end user will be impaired if the connection is abandoned too early.

[0055] Fig.14 is a signal flow diagram showing an example of a process for providing SCG failure information. The process may notify the E-UTRAN or NR MN of the SCG failures that the UE has experienced, namely, SCG radio link failure, failure of SCG synchronization reconfiguration, SCG configuration failure of RRC messages on SRB3, and SCG integrity check failure. The UE may initiate the process of reporting an SCG failure when neither MCG transmission nor SCG transmission is suspended and when one of the following conditions is met: 1) upon detection of a radio link failure of the SCG in accordance with sub-clause 5.3.10.3; 2) upon a synchronization reconfiguration failure of the SCG in accordance with sub-clause 5.3.5.8.3; 3) upon an SCG configuration failure in accordance with sub-clause 5.3.5.8.2; or 4) upon an integrity check failure indication regarding SRB3 from the SCG lower layer. When initiating the process, the UE may suspend SCG transmission of all SRBs and DRBs; reset the SCG MAC; and stop timer T304 (if running). If the UE is in (NG) EN-DC, the UE may initiate the transmission of the SCGFailureInformationNR message as specified in clause 5.6.13a of TS 36.331

[10] . Otherwise, the UE may initiate the transmission of the SCGFailureInformation message as specified in clause 5.7.3.5.

[0056] Fig.15 is a signal flow diagram illustrating a process for providing MCG failure information. The process may inform the NR MN of an MCG failure (e.g., MCG radio link failure) that the UE has experienced. A UE configured with split SRB1 may initiate a process for reporting an MCG failure when SCG transmission is not suspended and when a radio link failure of the MCG is detected, according to 5.3.10.3,

[0057] When initiating this process, the UE may suspend MCG transmission of all SRBs and DRBs; reset MCG-MAC; and initiate transmission of MCG failure information (MCGFailureInformation) message according to 5.7.y.5.

[0058] 5.7.y.3 Fault type determination

[0059] The UE shall set the MCG fault type as follows:

[0060] 1> If the UE initiates the transmission of the MCGFailureInformation message due to T310 expiration:

[0061] 2> Set the failure type (failureType) to t310-expired;

[0062] 1> Otherwise, if the UE initiates the transmission of the MCGFailureInformation message to provide a random access problem indication from the MCG MAC:

[0063] 2> Set failureType to random access problem (randomAccessProblem);

[0064] 1> Otherwise, if the UE initiates the transmission of the MCGFailureInformation message to provide an indication from the MCG RLC that the maximum number of retransmissions has been reached:

[0065] 2> Set failureType to rlc-MaxNumRetx;

[0066] 5.7.y.4 Set the content of the measurement result MCG-Failure (MeasResultMCG-Failure)

[0067] The UE shall set the content of MeasResultMCG-Failure as follows:

[0068] Editor's Note: FFS: How to capture measurements of MCG, SCG and non-serving cells

[0069] 2.1.5.1 5.7.y.5 Actions related to the transmission of MCGFailureInformation message

[0070] The UE shall set the content of the MCGFailureInformation message as follows:

[0071] 1>Include and set failureType according to 5.7.y.3;

[0072] 1> Include and set MeasResultMCG-Failure according to 5.7.y.4;

[0073] The UE shall submit the MCGFailureInformation message to lower layers for transmission.

[0074] According to the current protocol, if the UE detects a failure on the PCell, it may trigger MCG recovery (if configured). The UE may then send a MCGFailureInformation message via the SCG, via SRB3, or via the SCG branch that splits SRB1.

[0075] If the UE experiences an MCG failure (intra-node or inter-node) while the UE is performing a PSCell change, it is unclear how the network will handle the MCGFailureInformation message and the PSCell.

[0076] Furthermore, there may be some race conditions because the UE may send an RRCReconfigurationComplete to the MN, acknowledging receipt of the new SCG configuration, even before it has started the random access procedure to the new PSCell.

[0077] If the UE experiences an MCG failure while trying to connect to a new PSCell, there may be a significant delay until it can send an MCGFailureInformation via the SCG so that the MN can take appropriate action to recover the MCG.

[0078] Various embodiments herein describe procedures for a UE operating in dual connectivity with a primary node (MN) and a secondary node (SN), wherein the UE is configured with a primary cell group (MCG) configuration associated with the MN and a secondary cell group (SCG) configuration associated with the SN. Some embodiments include detecting a radio link failure on the MCG and determining whether there is an ongoing SCG change procedure.

[0079] In additional or alternative embodiments, even if the UE is configured with split SRB1 or SRB3 and is capable of performing the MCG failure recovery procedure, the re-establishment procedure may always be triggered.

[0080] In an additional or alternative embodiment, the re-establishment process may be triggered solely based on determining that an ongoing SCG change process is instructing the UE to change the SN, and if the SN is not changed (e.g., PSCell changes within the same SN, synchronous reconfiguration of the SCG without PSCell change due to key refresh, etc.), the MCG fault recovery process may be triggered.

[0081] In an additional or alternative embodiment, the reestablishment process may be triggered only based on determining that an ongoing SCG change process is instructing the UE to change the PSCell to a cell within the same SN. The MCG fault recovery process may be triggered only if the PSCell has not been changed (e.g., synchronous reconfiguration of the SCG without a PSCell change due to a key refresh).

[0082] In an additional or alternative embodiment, when the MN receives a MCGFailureInformation message after it has sent an RRCReconfiguration message with SCG and / or PSCell modification but before it has received an RRCReconfigurationComplete message for SCG and / or PSCell modification, the MN may release the SCG configuration and / or the radio bearer configuration associated with the SN. Regardless of whether the UE has applied the new SCG configuration or is still using the old configuration, the MN may apply the complete configuration after a failure.

[0083] In additional or alternative embodiments, the UE behavior may be configurable. For example, even if an SCG change is in progress (e.g., T304 is running), the UE may be configured to perform MCG failure recovery. This may be for all cases, or it may be only for specific cases (e.g., only when the SN is not changed or only when the PSCell is not changed).

[0084] In some embodiments, the UE and the network can avoid any ambiguity about the SCG configuration in the event of an MCG failure during a PSCell / SCG change. For example, if the SN initiates an SCG modification or a PSCell change via SRB3 without the participation of the MN, the MN may not be aware of the latest SCG configuration when it receives the MCGFailureInformation. During an SCG change, the UE may send an RRCReconfigurationComplete message to the MN before performing a random access procedure towards the PSCell, as shown in TS 37.340v15.7.0. Even if the MN has received an indication that the UE has received new SCG configurations, it may not know whether the UE has successfully applied them or is still trying to access the PSCell.

[0085] If the UE experiences an MCG failure while attempting to access a PSCell (e.g., after it has received an RRCReconfiguration message containing a PScell ​​synchronization reconfiguration (ReconfigurationWithSync)), the UE may create a MCGFailureInformation message and attempt to send the MCGFailureInformation message via the SCG (e.g., via SRB3 or the SCG portion of a split SRB1).

[0086] Since the UE has started synchronizing with the target PSCell, it may have been disconnected from the source PSCell and will not have any connection to any network node at this time. The protection timer for MCG failure recovery must expire before the UE re-establishes a connection (or T304 must expire), which may result in unnecessary delays before connecting. Since the T304 timer can be set to a value as large as 10 seconds, this means that the delay can be quite large. By ensuring that re-establishment is triggered when an MCG failure is detected while an SCG change is in progress, this unnecessary delay can be avoided and the performance of the UE can be greatly improved.

[0087] In some embodiments, when the UE detects a failure on the MCG, it checks whether there is an ongoing PSCell change (i.e., whether the timer T304 for the PSCell is running in NR or whether the timer T307 is not running in LTE). If the timer is running, the UE can perform RRC reestablishment. If the timer is not running, the UE can continue with MCG failure information reporting.

[0088] In some embodiments, methods are disclosed to allow the network to indicate to the UE whether the MCG / PCell fast recovery procedure should be used or the UE directly triggers the re-establishment procedure.

[0089] Fig.16 1 is a block diagram illustrating elements of a wireless device UE 1600 (also referred to as a mobile terminal, a mobile communication terminal, a wireless communication device, a wireless terminal, a wireless communication terminal, a user equipment UE, a user equipment node / terminal / device, etc.) configured to provide wireless communication according to an embodiment of the present inventive concept. (The wireless device 1600 may be provided, for example, as described below with respect to Fig.21 As shown in the figure, the wireless device UE may include an antenna 1607 (eg, corresponding to Fig.21 antenna 4111) and transceiver circuit 601 (also referred to as a transceiver, for example, corresponding to Fig.21 The transceiver circuit 601 includes a transmitter and a receiver, which is configured to provide communication with a base station of a radio access network (eg, corresponding to Fig.21 The wireless device UE may also include a processing circuit 1603 (also referred to as a processor, e.g., corresponding to a processor) coupled to the transceiver circuit. Fig.21 Processing circuit 4120) and memory circuit 1605 (also referred to as memory, e.g., corresponding to Fig.21 The memory circuit 1605 may include a computer-readable program code that, when executed by the processing circuit 1603, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processing circuit 1603 may be defined to include a memory so that a separate memory circuit is not required. The wireless device UE may also include an interface (e.g., a user interface) coupled to the processing circuit 1603, and / or the wireless device UE may be included in a carrier.

[0090] As discussed herein, the operations of the wireless device UE may be performed by the processing circuit 1603 and / or the transceiver circuit 1601. For example, the processing circuit 1603 may control the transceiver circuit 1601 to send communications to a radio access network node (also referred to as a base station) over a radio interface through the transceiver circuit 1601, and / or receive communications from a RAN node over a radio interface through the transceiver circuit 1601. In addition, modules may be stored in the memory circuit 1605, and these modules may provide instructions such that when the processing circuit 1603 executes the instructions of the modules, the processing circuit 1603 performs corresponding operations.

[0091] Fig.17 1 is a block diagram illustrating elements of a radio access network (RAN) node 1700 (also referred to as a network node, base station, eNodeB / eNB, gNodeB / gNB, etc.) configured to provide cellular communications according to an embodiment of the present inventive concept. (The RAN node 1700 may be provided, for example, as described below with respect to Fig.21 As shown in the figure, the RAN node may include a transceiver circuit 1701 (also referred to as a transceiver, for example, corresponding to Fig.21 The RAN node may include a network interface circuit 1707 (also referred to as a network interface, e.g., corresponding to a network interface circuit 1708). Fig.21The network node may also include a processing circuit 1703 (also referred to as a processor, for example, corresponding to the processing circuit 4170) coupled to the transceiver circuit and a memory circuit 1705 (also referred to as a memory, for example, corresponding to the memory) coupled to the processing circuit. Fig.21 Device readable medium 4180). Memory circuit 1705 may include computer readable program code that, when executed by processing circuit 1703, causes the processing circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, processing circuit 1703 may be defined to include memory so that a separate memory circuit is not required.

[0092] As discussed herein, the operations of the RAN node may be performed by the processing circuit 1703, the network interface 1707, and / or the transceiver 1701. For example, the processing circuit 1703 may control the transceiver 1701 to send downlink communications to one or more mobile terminals UE over the radio interface through the transceiver 1701, and / or to receive uplink communications from one or more mobile terminals UE over the radio interface through the transceiver 1701. Similarly, the processing circuit 1703 may control the network interface 1707 to send communications to one or more other network nodes through the network interface 1707 and / or to receive communications from one or more other network nodes through the network interface. In addition, modules may be stored in the memory 1705, and these modules may provide instructions so that when the processing circuit 1703 executes the instructions of the modules, the processing circuit 1703 performs the corresponding operations.

[0093] According to some other embodiments, the network node may be implemented as a core network CN node without a transceiver. In such an embodiment, the transmission to the wireless device UE may be initiated by the network node, such that the transmission to the wireless device is provided by the network node including the transceiver (e.g., by a base station or RAN node). According to an embodiment in which the network node is a RAN node including a transceiver, initiating the transmission may include transmitting through the transceiver.

[0094] Fig.181 is a block diagram showing the elements of a core network CN node 1800 (e.g., SMF node, AMF node, etc.) of a communication network configured to provide cellular communications according to an embodiment of the present invention. As shown, the CN node 1800 may include a network interface circuit 1807 (also referred to as a network interface) configured to provide communication with other nodes of the core network and / or the radio access network RAN. The CN node 1800 may also include a processing circuit 1803 (also referred to as a processor) coupled to the network interface circuit and a memory circuit 1805 (also referred to as a memory) coupled to the processing circuit. The memory circuit 1805 may include a computer-readable program code that causes the processing circuit to perform operations according to the embodiments disclosed herein when executed by the processing circuit 1803. According to other embodiments, the processing circuit 1803 may be defined as including a memory so that a separate memory circuit is not required.

[0095] As discussed herein, the operations of the CN node 1800 may be performed by the processing circuit 1803 and / or the network interface circuit 1807. For example, the processing circuit 1803 may control the network interface circuit 1807 to send communications to one or more other network nodes through the network interface circuit 1807 and / or receive communications from one or more other network nodes through the network interface circuit 1807. In addition, modules may be stored in the memory 1805, and these modules may provide instructions such that when the processing circuit 1803 executes the instructions of the modules, the processing circuit 1803 performs the corresponding operations.

[0096] As discussed herein, the operations of UE 1600 may be performed by processing circuit 1603 and / or transceiver 1601. For example, processing circuit 1603 may control transceiver 1601 to send communications to one or more network nodes via antenna 1607 and / or receive communications from one or more network nodes via antenna 1607. In addition, modules may be stored in memory 1605, and these modules may provide instructions such that when processing circuit 1603 executes the instructions of the modules, processing circuit 1603 performs corresponding operations.

[0097] According to some embodiments of the present invention, reference will now be made to Fig.19 Let's discuss the operation of UE 1600. For example, a module (also referred to as a unit) may be stored in Fig.16 The memory 1605 of the processor 1603 may provide instructions so that when the processing circuit 1603 executes the instructions of the module, the processing circuit 1603 executes the instructions of the module. Fig.19 The corresponding operations of the flowchart.

[0098] Fig.19A flow chart illustrating an example of a process for operating a communication device to respond to a radio link failure on an MCG is depicted.The communication device may be configured to operate in a DC with a MN and a SN, and the communication device may be configured with an MCG configuration associated with the MN and an SCG configuration associated with the SN.

[0099] At block 1910 , the processing circuit 1603 detects a radio link failure on the MCG.

[0100] At block 1920 , the processing circuit 1603 determines whether there is an ongoing PSCell change procedure.

[0101] At block 1930, the processing circuit 1603 responds to a radio link failure on the MCG. In some embodiments, responding to the radio link failure is based on whether a PSCell change procedure is ongoing. In additional or alternative embodiments, responding to the radio link failure on the MCG is also based on whether the PSCell change procedure includes reconfiguring the DC to be between the MN and a different SN. In additional or alternative embodiments, responding to the radio link failure on the MCG is also based on whether the PSCell change procedure includes changing the PSCell to a different cell within the SN.

[0102] In some embodiments, determining whether a PSCell change procedure is in progress includes determining whether a timer for the PSCell is running. In additional or alternative embodiments, the MN and the SN operate in an NR network, and the DC is an NR-DC. Determining whether an SCG change procedure is in progress includes determining whether a timer for the PSCell is running. At block 1932, in response to determining that there is an ongoing PSCell change procedure, the processing circuit 1603 performs an RRC reestablishment.

[0103] In some embodiments, the MN operates in a Long Term Evolution LTE network, the SN operates in an NR network, and the DC is an EN-DC. Determining whether a PSCell change procedure is in progress includes determining whether a timer for the PSCell is not running. At block 1934, the processing circuit 1603 reports MCG failure information in response to determining that there is no PSCell change procedure in progress.

[0104] In some embodiments, responding to a radio link failure on the MCG comprises: in response to detecting a radio link failure, always performing an RRC re-establishment.

[0105] With respect to some embodiments, Fig.19 Various operations of may be optional. For example, with respect to Embodiment 1 (described below), blocks 1932 and 1934 may be optional.

[0106] According to some embodiments of the present invention, reference will now be made to Fig. 20 The operation of the RAN node 1700 is discussed below. For example, a module (also referred to as a unit) may be stored in Fig.17 The memory 1705 of the processor 1703 and the modules can provide instructions so that when the processing circuit 1703 executes the instructions of the modules, the processing circuit 1703 executes Fig. 20 The corresponding operations of the flowchart.

[0107] Fig. 20 A flow chart showing an example of a process by which a first network node (1700) handles a MCG radio link failure between the first network node and a communication device is depicted. The communication device may be configured to operate in a DC with a MN and a SN. The first network node may be a MN.

[0108] At block 2010, processing circuit 1703 sends a first message to the target SN via transceiver 1701. In some embodiments, the first message may be part of a PSCell change procedure. In some embodiments, the target SN is a network node different from the SN, and the PSCell change procedure includes reconfiguring the DC to be a DC with the MN and the target SN. In additional or alternative embodiments, the target SN is the SN, and the PSCell change procedure includes changing the PSCell to a different cell within the SN. In additional or alternative embodiments, the DC includes at least one of: NR-DC and EN-DC.

[0109] At block 2020, the processing circuit 1703 detects an MCG radio link failure with the communication device. In some embodiments, detecting an MCG radio link failure between the first network node and the communication device comprises receiving a communication device context request from a third network node in the communication network. The third network node may have become an MN for the communication device. In additional or alternative embodiments, detecting an MCG radio link failure between the first network node and the communication device comprises receiving an RRC reestablishment request message from the communication device.

[0110] At block 2030, the processing circuit 1703 sends a second message to the target SN via the transceiver 1701. In some embodiments, the second message is a SN release request message.

[0111] With respect to some embodiments, Fig. 20 Various operations may be optional.

[0112] Example embodiments are discussed below. Reference numerals / letters are provided in parentheses by way of example / illustration and not to limit example embodiments to the specific elements indicated by the reference numerals / letters.

[0113] Embodiment 1. A method for operating a communication device, the communication device being configured to operate in a dual-connection DC with a primary node MN and a secondary node SN, and being configured with a primary cell group MCG configuration associated with the MN and a secondary cell group SCG configuration associated with the SN, the method comprising:

[0114] Detecting (1910) a radio link failure on the MCG;

[0115] Determine (1920) whether a primary and secondary cell group cell PSCell change procedure is in progress; and

[0116] Based on whether the PSCell change procedure is in progress, respond (1930) to a radio link failure on the MCG.

[0117] Embodiment 2. The method of embodiment 1, wherein responding to the radio link failure on the MCG is further based on whether the PSCell change procedure includes reconfiguring a DC between the MN and a different SN.

[0118] Embodiment 3. The method of embodiment 1, wherein responding to the radio link failure on the MCG is further based on whether the PSCell change procedure includes changing the PSCell to a different cell within the SN.

[0119] Embodiment 4. The method according to any one of embodiments 1-3, wherein determining whether a PSCell change process is in progress comprises: determining whether a timer for the PSCell is running.

[0120] Embodiment 5 The method according to embodiment 4, wherein determining whether the PSCell change process is in progress comprises: determining whether a timer for the PSCell is running.

[0121] Embodiment 6. The method of embodiment 5, wherein responding to a radio link failure on the MCG comprises: in response to determining that a timer is running, performing (1932) a radio resource control (RRC) re-establishment.

[0122] Embodiment 7 The method of embodiment 4, wherein determining whether a PSCell change procedure is in progress comprises determining whether a timer for the PSCell is not running.

[0123] Embodiment 8. The method of embodiment 7, wherein responding to a radio link failure on the MCG comprises: in response to determining that the timer is not running, reporting (1934) MCG failure information.

[0124] Embodiment 9. The method according to any one of embodiments 1 to 8, wherein the DC comprises one of the following: New Radio-New Radio Dual Connectivity NR-DC; Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity EN-DC connected to Evolved Packet Core; Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity NGEN-DC connected to 5th Generation Core; New Radio Evolved Universal Terrestrial Radio Access New Dual Connectivity NE-DC; or Multi-Radio Dual Connectivity MR-DC.

[0125] Embodiment 10. A method for operating a first network node in a communication network, the communication network comprising a communication device, the communication device being configured to operate in a dual connection DC with a primary node MN and a secondary node SN, the first network node being the MN, the method comprising:

[0126] Sending (2010) a first message to a target SN as part of a primary and secondary cell group cell PSCell change procedure performed by the communication device;

[0127] detecting (2020) a master cell group (MCG) radio link failure between the first network node and the communication device; and

[0128] In response to (2030) detecting an MCG radio link failure, a second message is sent to the target SN.

[0129] Embodiment 11. According to the method of embodiment 10, sending the second message to the target SN includes: sending an SN release request message.

[0130] Embodiment 12. The method according to any one of embodiments 10-11, wherein detecting an MCG radio link failure between the first network node and the communication device comprises: receiving a communication device context request from a third network node in the communication network, the third network node having received at least one message from the communication device.

[0131] Embodiment 13. The method according to any one of embodiments 10-11, wherein detecting an MCG radio link failure between the first network node and the communication device comprises: receiving a radio resource control (RRC) reestablishment request message from the communication device.

[0132] Embodiment 14. The method according to any one of embodiments 10-13, wherein the target SN is a network node different from the SN, and

[0133] The PSCell change process includes reconfiguring the DC to be a DC with the MN and the target SN.

[0134] Embodiment 15. The method according to any one of embodiments 10-13, wherein the target SN is SN, and

[0135] The PSCell change process includes changing the PSCell to a different cell within the SN.

[0136] Embodiment 16. The method according to any one of embodiments 10-15, wherein the DC comprises one of the following: New Radio-New Radio Dual Connectivity NR-DC; Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity EN-DC connected to Evolved Packet Core; Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity NGEN-DC connected to 5th Generation Core; New Radio Evolved Universal Terrestrial Radio Access New Dual Connectivity NE-DC; or Multi-Radio Dual Connectivity MR-DC.

[0137] Embodiment 17. A communication device (1600) is configured to operate in a dual-connection DC with a primary node MN and a secondary node SN, and is configured with a primary cell group MCG configuration associated with the MN and a secondary cell group SCG configuration associated with the SN, the communication device comprising:

[0138] processing circuit (1603); and

[0139] a memory (1605) coupled to the processing circuit and storing instructions executable by the processing circuit to cause the communication device to perform operations, the operations comprising:

[0140] Detecting (1910) a radio link failure on the MCG;

[0141] Determine (1920) whether a primary and secondary cell group cell PSCell change procedure is in progress; and

[0142] Based on whether the PSCell change procedure is in progress, respond (1930) to a radio link failure on the MCG.

[0143] Embodiment 18. The communication device of embodiment 17, wherein responding to the radio link failure on the MCG is further based on whether the PSCell change procedure includes reconfiguring a DC between the MN and a different SN.

[0144] Embodiment 19. The communication device of embodiment 17, wherein responding to the radio link failure on the MCG is further based on whether the PSCell change procedure includes changing the PSCell to a different cell within the SN.

[0145] Embodiment 20: The communication device according to any one of embodiments 17-19, wherein determining whether a PSCell change process is in progress comprises: determining whether a timer for the PSCell is running.

[0146] Embodiment 21 The communication device of embodiment 20, wherein determining whether a PSCell change procedure is in progress comprises determining whether a timer for the PSCell is running.

[0147] Embodiment 22. The communication device of embodiment 21, wherein responding to a radio link failure on the MCG comprises: in response to determining that a timer is running, performing (1932) a radio resource control (RRC) re-establishment.

[0148] Embodiment 23 The communication device of embodiment 20, wherein determining whether a PSCell change procedure is in progress comprises determining whether a timer for the PSCell is not running.

[0149] Embodiment 24. The communication device of embodiment 23, wherein responding to a radio link failure on the MCG comprises: in response to determining that the timer is not running, reporting (1934) MCG failure information.

[0150] Embodiment 25. A communication device according to any one of embodiments 17-24, wherein the DC comprises one of: New Radio-New Radio Dual Connectivity NR-DC; Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity EN-DC connected to an Evolved Packet Core; Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity NGEN-DC connected to a 5th Generation Core; New Radio Evolved Universal Terrestrial Radio Access New Dual Connectivity NE-DC; or Multi Radio Dual Connectivity MR-DC.

[0151] Embodiment 26. A communication device (1600) is configured to operate in a dual-connection DC with a primary node MN and a secondary node SN, and is configured with a primary cell group MCG configuration associated with the MN and a secondary cell group SCG configuration associated with the SN, and is suitable for performing operations, the operations comprising:

[0152] Detecting (1910) a radio link failure on the MCG;

[0153] Determine (1920) whether a primary and secondary cell group cell PSCell change procedure is in progress; and

[0154] Based on whether the PSCell change procedure is in progress, respond (1930) to a radio link failure on the MCG.

[0155] Embodiment 27. The communication device according to embodiment 26, wherein the operation includes any operation of embodiments 2-9.

[0156] Embodiment 28. A computer program, comprising program code to be executed by a processing circuit (1603) of a communication device (1600), the communication device (1600) being configured to operate in a dual-connection DC with a primary node MN and a secondary node SN and being configured with a primary cell group MCG configuration associated with the MN and a secondary cell group SCG configuration associated with the SN, whereby execution of the program code causes the communication device to perform operations, the operations comprising:

[0157] Detecting (1910) a radio link failure on the MCG;

[0158] Determine (1920) whether a primary and secondary cell group cell PSCell change procedure is in progress; and

[0159] Based on whether the PSCell change procedure is in progress, respond (1930) to a radio link failure on the MCG.

[0160] Embodiment 29. According to the computer program of embodiment 28, the operations further include any operations of embodiments 2-9.

[0161] Embodiment 30. A computer program product comprising a non-transitory storage medium, the non-transitory storage medium comprising program code to be executed by a processing circuit (1603) of a communication device (1600), the communication device (1600) being configured to operate in a dual-connectivity DC with a primary node MN and a secondary node SN and being configured with a primary cell group MCG configuration associated with the MN and a secondary cell group SCG configuration associated with the SN, whereby execution of the program code causes the communication device to perform operations comprising:

[0162] Detecting (1910) a radio link failure on the MCG;

[0163] Determine (1920) whether a primary and secondary cell group cell PSCell change procedure is in progress; and

[0164] Based on whether the PSCell change procedure is in progress, respond (1930) to a radio link failure on the MCG.

[0165] Embodiment 31. According to the computer program product of embodiment 30, the operations further include any of the operations of embodiments 2-9.

[0166] Embodiment 32. A first network node (1700) in a communication network, the communication network comprising a communication device, the communication device being configured to operate in a dual connection DC with a primary node MN and a secondary node SN, the first network node being the MN, the first network node comprising:

[0167] processing circuit (1703); and

[0168] a memory (1705) coupled to the processing circuit and storing instructions executable by the processing circuit to cause the first network node to perform operations comprising:

[0169] Sending (2010) a first message to a target SN as part of a primary and secondary cell group cell PSCell change procedure performed by the communication device;

[0170] detecting (2020) a master cell group (MCG) radio link failure between the first network node and the communication device; and

[0171] In response to (2030) detecting an MCG radio link failure, a second message is sent to the target SN.

[0172] Embodiment 33. According to the first network node of embodiment 32, sending the second message to the target SN comprises: sending an SN release request message.

[0173] Embodiment 34. The first network node according to any one of embodiments 32-33, wherein detecting an MCG radio link failure between the first network node and the communication device comprises: receiving a communication device context request from a third network node in the communication network, the third network node having received at least one message from the communication device.

[0174] Embodiment 35. The first network node according to any one of embodiments 32-33, wherein detecting an MCG radio link failure between the first network node and the communication device comprises: receiving a radio resource control (RRC) reestablishment request message from the communication device.

[0175] Embodiment 36. The first network node according to any one of embodiments 33-35, wherein the target SN is a network node different from the SN, and

[0176] The PSCell change process includes reconfiguring the DC to be a DC with the MN and the target SN.

[0177] Embodiment 37. The first network node according to any one of embodiments 33-35, wherein the target SN is SN, and

[0178] The PSCell change process includes changing the PSCell to a different cell within the SN.

[0179] Embodiment 38. The first network node according to any one of embodiments 33-37, wherein the DC comprises one of: New Radio-New Radio Dual Connectivity NR-DC; Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity EN-DC connected to Evolved Packet Core; Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity NGEN-DC connected to 5th Generation Core; New Radio Evolved Universal Terrestrial Radio Access New Dual Connectivity NE-DC; or Multi Radio Dual Connectivity MR-DC.

[0180] Embodiment 39. A first network node (1700) in a communication network, the communication network comprising a communication device, the communication device being configured to operate in a dual connection DC with a primary node MN and a secondary node SN, the first network node being the MN and being adapted to perform operations comprising:

[0181] Sending (2010) a first message to a target SN as part of a primary and secondary cell group cell PSCell change procedure performed by the communication device;

[0182] detecting (2020) a master cell group (MCG) radio link failure between the first network node and the communication device; and

[0183] In response to (2030) detecting an MCG radio link failure, a second message is sent to the target SN.

[0184] Embodiment 40. The first network node of embodiment 39, wherein the operations include any of the operations of embodiments 11-16.

[0185] Embodiment 41. A computer program comprising program code to be executed by a processing circuit (1703) of a first network node (1700) in a communication network, the communication network comprising a communication device, the communication device being configured to operate in a dual connection DC with a primary node MN and a secondary node SN, the first network node being the MN, whereby execution of the program code causes the first network node to perform operations comprising:

[0186] Sending (2010) a first message to a target SN as part of a primary and secondary cell group cell PSCell change procedure performed by the communication device;

[0187] detecting (2020) a master cell group (MCG) radio link failure between the first network node and the communication device; and

[0188] In response to (2030) detecting an MCG radio link failure, a second message is sent to the target SN.

[0189] Embodiment 42. According to the computer program of embodiment 41, the operations further include any of the operations of embodiments 11-16.

[0190] Embodiment 43. A computer program product comprising a non-transitory storage medium, the non-transitory storage medium comprising program code to be executed by a processing circuit (1703) of a first network node (1700) in a communication network, the communication network comprising a communication device, the communication device being configured to operate in a dual connection DC with a primary node MN and a secondary node SN, the first network node being the MN, whereby execution of the program code causes the first network node to perform operations comprising:

[0191] Sending (2010) a first message to a target SN as part of a primary and secondary cell group cell PSCell change procedure performed by the communication device;

[0192] detecting (2020) a master cell group (MCG) radio link failure between the first network node and the communication device; and

[0193] In response to (2030) detecting an MCG radio link failure, a second message is sent to the target SN.

[0194] Embodiment 44. According to the computer program product of embodiment 43, the operations further include any of the operations of embodiments 11-16.

[0195] An explanation of the abbreviations disclosed above is provided below:

[0196] Abbreviations

[0197] 5GC 5G Core Network

[0198] 5GS 5G System

[0199] AMF Access and Mobility Management Function

[0200] ACK Acknowledgement

[0201] AP Application Protocol

[0202] BSR Buffer Status Report

[0203] BWP Bandwidth Part

[0204] C-RNTI Cell Radio Network Temporary Identifier

[0205] CA Carrier Aggregation

[0206] CE Control Elements

[0207] CP Control Plane

[0208] CQI Channel Quality Indicator

[0209] DC Dual Connection

[0210] DCI Downlink Control Information

[0211] DL Downlink

[0212] DRB Data Radio Bearer

[0213] eNB E-UTRAN NodeB

[0214] EN-DC E-UTRAN-NR Dual Connectivity

[0215] E-UTRA Evolved Universal Terrestrial Radio Access

[0216] E-UTRAN Evolved Universal Terrestrial Radio Access Network

[0217] EPC Evolved Packet Core

[0218] EPS Evolved Packet System

[0219] E-RAB EUTRAN Radio Access Bearer

[0220] FDD Frequency Division Duplex

[0221] gNB NR Base Station

[0222] GTP-U GPRS Tunneling Protocol - User Plane

[0223] HO Handover

[0224] IP Internet Protocol

[0225] LTE Long Term Evolution

[0226] MAC Media Access Control

[0227] MCG Master Cell Group

[0228] MeNB Master eNB

[0229] MgNB Master gNB

[0230] MME Mobility Management Entity

[0231] MN Master Node

[0232] MR Multi-RAT

[0233] MR-DC Multi-RAT Dual Connectivity

[0234] NACK Negative acknowledgment

[0235] NG Next Generation

[0236] NR New Radio

[0237] PCell Primary Cell

[0238] PCI Physical Cell Identifier

[0239] PDCP Packet Data Convergence Protocol

[0240] PSCell Primary SCell

[0241] PUSCH Physical Uplink Shared Channel

[0242] P-GW Packet Gateway

[0243] RAN Radio Access Network

[0244] RAT Radio Access Technology

[0245] RLC Radio Link Control

[0246] RLF Radio Link Failure

[0247] RRC Radio Resource Control

[0248] SMF session management functions

[0249] SCG Secondary Cell Group

[0250] SCell Secondary Cell

[0251] SCTP Stream Control Transmission Protocol

[0252] SeNB Secondary eNB

[0253] SINR Signal to Interference and Noise Ratio

[0254] S-GW Service Gateway

[0255] S-MN Source MN

[0256] SN Secondary Node

[0257] S-SN Source SN

[0258] SR Scheduling Request

[0259] SRB Signalling Radio Bearer

[0260] SUL Supplementary Uplink

[0261] TDD Time Division Duplex

[0262] TEID Tunnel Endpoint Identifier

[0263] TNL Transport Network Layer

[0264] T-MN Target MN

[0265] TDD Time Division Duplex

[0266] TEID Tunnel Endpoint Identifier

[0267] TNL Transport Network Layer

[0268] UCI Uplink Control Information

[0269] UDP User Datagram Protocol

[0270] UE User Equipment

[0271] UL Uplink

[0272] UP User Plane

[0273] URLLC Ultra-Reliable Low Latency Communications

[0274] X2 Interface between base stations

[0275] Additional explanation is provided below.

[0276] Generally, unless clearly given and / or different meanings are implied from the context in which the term is used, all terms used in this article will be interpreted according to their common meaning in the relevant technical field. Unless otherwise clearly stated, all references to one / one / described element, equipment, assembly, device, step, etc. should be openly interpreted as referring to at least one example in element, equipment, assembly, device, step, etc. Unless a step must be clearly described as after or before another step and / or a step must be after or before another step implicitly, the steps of any method disclosed herein do not have to be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applicable to any other embodiment, and vice versa. By the following description, other purposes, features and advantages of the attached embodiments will be apparent.

[0277] Some 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; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0278] Fig.21 A wireless network in accordance with some embodiments is shown.

[0279] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to wireless networks (e.g. Fig.21 For simplicity, Fig.21 The wireless network of FIG. 41 depicts only the network 4106, the network nodes 4160 and 4160b, and the WDs 4110, 4110b, and 4110c (also referred to as mobile terminals). In practice, the wireless network may also include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). In the illustrated components, the network node 4160 and the wireless device (WD) 4110 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless device to access and / or use services provided by or via the wireless network.

[0280] A wireless network may include and / or interface with any type of communication, telecommunication, data, cellular and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, a particular embodiment of a wireless communication 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 IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0281] 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 (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0282] The network node 4160 and the WD 4110 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connections in a wireless network. In different 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 can facilitate or participate in the communication of data and / or signals (whether via a wired connection or via a wireless connection).

[0283] As used herein, a network node refers to a device that is capable of, configured, arranged 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 implement and / or provide wireless access to a wireless device and / or perform other functions (e.g., management) in a wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, NodeBs, evolved NodeBs (eNBs), and NR NodeBs (gNBs)). Base stations can be classified based on the amount of coverage they provide (or in other words, based on their transmit power levels), so they can also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay host node that controls a relay. A network node may also include one or more (or all) parts 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 head (RRH)). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Still other examples of network nodes include multi-standard radio (MSR) equipment (such as an MSR BS), a network controller (such as a radio network controller (RNC) or a base station controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node, as described in more detail below. However, more generally, a network node may represent any suitable device (or device group) that is capable of, configured, arranged, and / or operable to enable and / or provide access to a wireless network to a wireless device, or to provide a certain service to a wireless device that has accessed a wireless network.

[0284] exist Fig.21In the embodiment, the network node 4160 includes a processing circuit 4170, a device readable medium 4180, an interface 4190, an auxiliary device 4184, a power supply 4186, a power supply circuit 4187, and an antenna 4162. Fig.21 The network node 4160 shown in the example wireless network of can represent a device including a combination of the hardware components shown, but other embodiments can include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node 4160 are depicted as a single box located within a larger box or nested within multiple boxes, in reality, the network node may include multiple different physical components that constitute a single illustrated component (for example, the device readable medium 4180 may include multiple separate hard drives and multiple RAM modules).

[0285] Similarly, the network node 4160 may be composed of multiple physically separated 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 certain scenarios where the network node 4160 includes multiple separated components (e.g., BTS and BSC components), one or more of these separated components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may be considered to be a single separate network node in some instances. In some embodiments, the network node 4160 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components may be replicated (e.g., separate device-readable media 4180 for different RATs), and some components may be reused (e.g., the same antenna 4162 may be shared by RATs). The network node 4160 may also include multiple groups of various components shown for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into the network node 4160. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 4160 .

[0286] The processing circuit 4170 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being provided by the network node. These operations performed by the processing circuit 4170 may include processing the information obtained by the processing circuit 4170 by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information and making a determination based on the results of the processing.

[0287] The processing circuit 4170 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic, which is operable to provide network node 4160 functions alone or in combination with other network node 4160 components (e.g., device readable medium 4180). For example, the processing circuit 4170 may execute instructions stored in the device readable medium 4180 or stored in a memory within the processing circuit 4170. Such functions may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit 4170 may include a system on a chip (SOC).

[0288] In some embodiments, the processing circuit 4170 may include one or more of a radio frequency (RF) transceiver circuit 4172 and a baseband processing circuit 4174. In some embodiments, the radio frequency (RF) transceiver circuit 4172 and the baseband processing circuit 4174 may be located on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, part or all of the RF transceiver circuit 4172 and the baseband processing circuit 4174 may be on the same chip or chipset, board, or unit.

[0289] In certain embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by a processing circuit 4170 that executes instructions stored on a device-readable medium 4180 or a memory within the processing circuit 4170. In alternative embodiments, some or all of the functions may be provided by the processing circuit 4170, for example, in a hardwired manner, without executing instructions stored on a separate or discrete device-readable medium. In any of these embodiments, the processing circuit 4170 may be configured to perform the described functions, whether or not executing instructions stored on a device-readable storage medium. The benefits provided by such functionality are not limited to the processing circuit 4170 or to other components of the network node 4160, but are enjoyed by the network node 4160 as a whole and / or by end users and the wireless network as a whole.

[0290] Device readable medium 4180 may include any form of volatile or non-volatile computer readable memory, including but not limited to 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 disk (CD) or digital video disk (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 that can be used by processing circuit 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 that can be executed by processing circuit 4170 and used by network node 4160. Device readable medium 4180 may be used to store any calculations made by processing circuit 4170 and / or any data received via interface 4190. In some embodiments, the processing circuit 4170 and the device readable medium 4180 may be considered to be integrated.

[0291] 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 port / terminal 4194 for sending data to network 4106 and receiving data from network 4106, for example, via a wired connection. Interface 4190 also includes radio front-end circuit 4192, which can be coupled to antenna 4162, or in some embodiments is part of antenna 4162. Radio front-end circuit 4192 includes filter 4198 and amplifier 4196. Radio front-end circuit 4192 can be connected to antenna 4162 and processing circuit 4170. Radio front-end circuit can be configured to adjust the signal communicated between antenna 4162 and processing circuit 4170. Radio front-end circuit 4192 can receive digital data, which will be sent out to other network nodes or WDs via a wireless connection. The radio front end circuit 4192 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 4198 and / or amplifiers 4196. The radio signal may then be transmitted via antenna 4162. Similarly, when receiving data, the antenna 4162 may collect the radio signal, which may then be converted into digital data by the radio front end circuit 4192. The digital data may be passed to the processing circuit 4170. In other embodiments, the interface may include different components and / or different combinations of components.

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

[0293] Antenna 4162 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 4162 may be coupled to radio front-end circuit 4192 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 4162 may include one or more omnidirectional, sector or flat panel antennas operable to send / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals to / from devices in a specific area, and flat panel antennas may be line of sight antennas for sending / receiving radio signals in a relatively straight line. In some cases, using more than one antenna may be referred to as MIMO. In some embodiments, antenna 4162 may be separated from network node 4160 and may be connected to network node 4160 via an interface or port.

[0294] Antenna 4162, interface 4190 and / or processing circuit 4170 can be configured to perform any receiving operation and / or certain obtaining operation described herein as being performed by a network node. Any information, data and / or signal can be received from a wireless device, another network node and / or any other network device. Similarly, antenna 4162, interface 4190 and / or processing circuit 4170 can be configured to perform any sending operation performed by a network node described herein. Any information, data and / or signal can be sent to a wireless device, another network node and / or any other network device.

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

[0296] Alternative embodiments of network node 4160 may include beyond Fig.21 , which may be responsible for providing certain aspects of the functionality of the network node, including any of the functionality described herein and / or any functionality required to support the subject matter described herein. For example, the network node 4160 may include a user interface device to allow information to be input into the network node 4160 and to allow information to be output from the network node 4160. This may allow a user to perform diagnostic, maintenance, repair, and other management functions for the network node 4160.

[0297] As used herein, a wireless device (WD) refers to a device that can, is configured to, is arranged to and / or is operable to communicate wirelessly with a network node and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with a user equipment (UE) in this article. Wireless transmission may include using electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information through the air to send and / or receive wireless signals. In some embodiments, a WD may be configured to send and / or receive information without direct human interaction. For example, a WD may be designed to send information to a network with a predetermined schedule when triggered by an internal or external event, or in response to a request from a network. Examples of WD include, but are not limited to, smart phones, 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 terminal devices, wireless endpoints, mobile stations, tablet computers, portable computers, portable embedded devices (LEEs), portable installation devices (LMEs), smart devices, wireless customer premises equipment (CPEs), vehicle-mounted wireless terminal devices, etc. WD can support device-to-device (D2D) communication, vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-anything (V2X) communication, for example, by implementing the 3GPP standard for sidelink communication, and in this case can be referred to as a D2D communication device. As another specific example, in the Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, WD can be a UE that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., electric meters), industrial machines, or household or personal devices (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, WD can represent a vehicle or other device that can monitor and / or report its operating status or other functions associated with its operation. As mentioned above, WD can represent the end point of wireless connection, in which case, the device can be referred to as a wireless terminal. In addition, as mentioned above, WD can be mobile, in which case, it can also be referred to as a mobile device or a mobile terminal.

[0298] As shown, wireless device 4110 includes antenna 4111, interface 4114, processing circuit 4120, device-readable medium 4130, user interface device 4132, auxiliary device 4134, power supply 4136, and power supply circuit 4137. WD 4110 may include multiple groups of one or more of the components shown for different wireless technologies supported by WD 4110 (e.g., GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to mention just a few). These wireless technologies may be integrated into the same or different chips or chipsets as other components within WD 4110.

[0299] Antenna 4111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 4114. In some alternative embodiments, antenna 4111 can be separated from WD 4110 and can be connected to WD4110 through an interface or port. Antenna 4111, interface 4114 and / or processing circuit 4120 can be configured to perform any receiving or sending operation described herein as being performed by WD. Any information, data and / or signal can be received from a network node and / or another WD. In some embodiments, radio front end circuit and / or antenna 4111 can be considered as an interface.

[0300] As shown, the interface 4114 includes a radio front-end circuit 4112 and an antenna 4111. The radio front-end circuit 4112 includes one or more filters 4118 and an amplifier 4116. The radio front-end circuit 4112 is connected to the antenna 4111 and the processing circuit 4120, and is configured to condition the signals transmitted between the antenna 4111 and the processing circuit 4120. The radio front-end circuit 4112 may be coupled to the antenna 4111 or may be part of the antenna 4111. In certain alternative embodiments, the WD 4110 may not include a separate radio front-end circuit 4112; instead, the processing circuit 4120 may include the radio front-end circuit and may be connected to the antenna 4111. Similarly, in some embodiments, some or all of the RF transceiver circuit 4122 may be considered to be part of the interface 4114. The radio front-end circuit 4112 may receive digital data, which will be sent out to other network nodes or WDs via a wireless connection. The radio front end circuit 4112 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 4118 and / or amplifiers 4116. The radio signal may then be transmitted via antenna 4111. Similarly, when receiving data, the radio signal may be collected by antenna 4111 and then converted into digital data by the radio front end circuit 4112. The digital data may be passed to processing circuit 4120. In other embodiments, the interface may include different components and / or different combinations of components.

[0301] The processing circuit 4120 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or coded logic, which is operable to provide WD 4110 functions alone or in combination with other WD4110 components (e.g., device-readable medium 4130). Such functions may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 4120 may execute instructions stored in the device-readable medium 4130 or in a memory within the processing circuit 4120 to provide the functions disclosed herein.

[0302] As shown, the processing circuit 4120 includes one or more of the RF transceiver circuit 4122, the baseband processing circuit 4124, and the application processing circuit 4126. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 4120 of the WD 4110 may include a SOC. In some embodiments, the RF transceiver circuit 4122, the baseband processing circuit 4124, and the application processing circuit 4126 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit 4124 and the application processing circuit 4126 may be combined into one chip or chipset, and the RF transceiver circuit 4122 may be on a separate chip or chipset. In another alternative embodiment, part or all of the RF transceiver circuit 4122 and the baseband processing circuit 4124 may be on the same chip or chipset, and the application processing circuit 4126 may be on a separate chip or chipset. In other alternative embodiments, part or all of the RF transceiver circuit 4122, baseband processing circuit 4124, and application processing circuit 4126 may be combined in the same chip or chipset. In some embodiments, the RF transceiver circuit 4122 may be part of the interface 4114. The RF transceiver circuit 4122 may condition the RF signal for the processing circuit 4120.

[0303] In some embodiments, some or all of the functions described herein as being performed by the WD may be provided by a processing circuit 4120 that executes instructions stored on a device-readable medium 4130, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by the processing circuit 4120, for example, in a hardwired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these particular embodiments, the processing circuit 4120 may be configured to perform the described functions, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuit 4120 or to other components of the WD 4110, but are enjoyed by the WD 4110 as a whole and / or by the end user and the wireless network as a whole.

[0304] The processing circuit 4120 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by the WD. These operations performed by the processing circuit 4120 may include processing the information obtained by the processing circuit 4120 by, for example, converting the obtained information to other information, comparing the obtained information or the converted information to information stored by the WD 4110, and / or performing one or more operations based on the obtained information or the converted information and making a determination based on the results of the processing.

[0305] The device-readable medium 4130 is operable to store computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions executable by the processing circuit 4120. The device-readable medium 4130 may include a computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), a mass storage medium (e.g., a hard disk), a removable storage medium (e.g., a compact disk (CD) or a digital video disk (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 that may be used by the processing circuit 4120. In some embodiments, the processing circuit 4120 and the device-readable medium 4130 may be considered to be integrated.

[0306] The user interface device 4132 can provide a component that allows a human user to interact with the WD 4110. This interaction can have a variety of forms, such as visual, auditory, tactile, etc. The user interface device 4132 is operable to generate output to the user and allow the user to provide input to the WD 4110. The type of interaction can vary according to the type of user interface device 4132 installed in the WD 4110. For example, if the WD 4110 is a smart phone, the interaction can be carried out via a touch screen; if the WD 4110 is a smart meter, the interaction can be carried out through a screen that provides the amount (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 4132 can include an input interface, device and circuit, and an output interface, device and circuit. The user interface device 4132 is configured to allow information to be input into the WD 4110, and is connected to the processing circuit 4120 to allow the processing circuit 4120 to process the input information. User interface device 4132 may include, for example, a microphone, proximity or other sensors, keys / buttons, a touch display, one or more cameras, USB ports or other input circuits. User interface device 4132 is also configured to allow information to be output from WD 4110, and allows processing circuit 4120 to output information from WD 4110. User interface device 4132 may include, for example, a loud speaker, display, vibration circuit, USB port, headphone jack or other output circuits. By using one or more input and output interfaces, devices and circuits of user interface device 4132, WD 4110 may communicate with terminal users and / or wireless networks, and allow them to benefit from the functions described herein.

[0307] Auxiliary device 4134 is operable to provide more specific functions that may not normally be performed by a WD. This may include specialized sensors for measuring for various purposes, interfaces for other types of communications such as wired communications, etc. The inclusion and type of components of auxiliary device 4134 may vary depending on the embodiment and / or scenario.

[0308] In some embodiments, the power source 4136 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery cell. WD 4110 may also include a power circuit 4137 for delivering power from the power source 4136 to various parts of WD 4110, and various parts of WD 4110 require power from the power source 4136 to perform any function described or indicated herein. In some embodiments, the power circuit 4137 may include a power management circuit. The power circuit 4137 may additionally or alternatively be operable to receive power from an external power source; in this case, the WD 4110 may be connected to an external power source (e.g., a power outlet) through an input circuit or an interface such as a power cable. In some embodiments, the power circuit 4137 may also be operable to deliver power from an external power source to the power source 4136. For example, this may be used for charging the power source 4136. The power circuit 4137 may perform any formatting, conversion, or other modifications to the power from the power source 4136 to make the power suitable for the various components of the WD 4110 being powered.

[0309] Fig. 22 A user equipment according to some embodiments is shown.

[0310] Fig. 22 An embodiment of a UE according to various aspects described herein is shown. As used herein, a "user equipment" or "UE" may not necessarily have a "user" in the sense of a human user who owns and / or operates the associated device. Alternatively, a UE may represent a device that is intended to be sold to or operated by a human user but may not or may not initially be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart meter). UE 4200 may be any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Fig. 22 As shown, UE 4200 is an example of a WD configured for communication according to one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms WD and UE may be used interchangeably. Therefore, although Fig. 22 It is UE, but the components discussed in this article are also applicable to WD and vice versa.

[0311] exist Fig. 22In the embodiment, UE 4200 includes a processing circuit 4201, which is operably coupled to an input / output interface 4205, a radio frequency (RF) interface 4209, a network connection interface 4211, a memory 4215 including a random access memory (RAM) 4217, a read-only memory (ROM) 4219, and a storage medium 4221, a communication subsystem 4231, a power supply 4213, and / or any other components, or any combination thereof. The storage medium 4221 includes an operating system 4223, an application 4225, and data 4227. In other embodiments, the storage medium 4221 may include other similar types of information. Some UEs may use Fig. 22 All components shown in the UE may be used, or only a subset of these components may be used. The level of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0312] exist Fig. 22 , processing circuit 4201 may be configured to process computer instructions and data. Processing circuit 4201 may be configured to implement any sequential state machine operable to execute machine instructions stored as a machine-readable computer program in a memory, such as: one or more hardware-implemented state machines (e.g., implemented in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored programs, general-purpose processors (e.g., microprocessors or digital signal processors (DSPs)) together with suitable software; or any combination of the above. For example, processing circuit 4201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0313] In the depicted embodiment, the input / output interface 4205 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 4200 may be configured to use an output device via the input / output interface 4205. The output device may use an interface port of the same type as the input device. For example, a USB port may be used to provide input to and output from the UE 4200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 4200 may be configured to use an input device via the input / output interface 4205 to allow a user to capture information into the UE 4200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a touchpad, a scroll wheel, a smart card, etc. 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.

[0314] exist Fig. 22 In the embodiment of the present invention, the RF interface 4209 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. The network connection interface 4211 can be configured to provide a communication interface to the network 4243a. The network 4243a can include a wired and / or wireless network, 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 4243a can include a Wi-Fi network. The network connection interface 4211 can be configured to include a receiver and a transmitter interface, and the receiver and transmitter interface are used to communicate with one or more other devices through a communication network according to one or more communication protocols (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface 4211 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0315] RAM 4217 can be configured to interface with processing circuit 4201 via bus 4202 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications and device drivers. ROM 4219 can be configured to provide computer instructions or data to processing circuit 4201. For example, ROM 4219 can be configured to store unchanged low-level system code or data for basic system functions stored in non-volatile memory, such as basic input and output (I / O), startup or reception of keystrokes from keyboard. Storage medium 4221 can 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), disk, optical disk, floppy disk, hard disk, removable tape cassette or flash drive. In one example, storage medium 4221 can be configured to include operating system 4223, application 4225 such as web browser application, widget or gadget engine or another application and data file 4227. Storage medium 4221 may store any one or a combination of various operating systems for use by UE 4200 .

[0316] The 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, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disk (HD-DVD) optical drive, a built-in hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory such as a user identity module or a removable user identity (SIM / RUIM) module, other memories or any combination thereof. The storage medium 4221 may allow the UE 4200 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to unload data or upload data. Articles such as articles utilizing a communication system may be tangibly embodied in the storage medium 4221, which may include a device-readable medium.

[0317] exist Fig. 22In the embodiment of the present invention, the processing circuit 4201 can be configured to communicate with the network 4243b using the communication subsystem 4231. The network 4243a and the network 4243b can be one or more identical networks or one or more different networks. The communication subsystem 4231 can be configured to include one or more transceivers for communicating with the network 4243b. For example, the communication subsystem 4231 can be configured to include one or more transceivers for communicating with another device (e.g., another WD, UE) or one or more remote transceivers of a base station of a radio access network (RAN) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver may include a transmitter 4233 and / or a receiver 4235 to respectively implement a transmitter or receiver function (e.g., frequency allocation, etc.) suitable for a RAN link. In addition, the transmitter 4233 and the receiver 4235 of each transceiver may share circuit components, software or firmware, or may be implemented separately instead.

[0318] 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 use of a global positioning system (GPS) for determining 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 a wired and / or wireless network, 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.

[0319] The features, benefits and / or functions described herein may be implemented in one of the components of UE 4200, or divided between multiple components of UE 4200. In addition, 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 described herein. In addition, the processing circuit 4201 may be configured to communicate with any such component via bus 4202. In another example, any such component may be represented by a program instruction stored in a memory, and when executed by the processing circuit 4201, the program instruction performs the corresponding function described herein. In another example, the function of any such component may be divided between the processing circuit 4201 and the communication subsystem 4231. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0320] Fig.23 A virtualized environment is shown in accordance with some embodiments.

[0321] Fig.23 4300 is a schematic block diagram showing a virtualized environment, in which the functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualized hardware platforms, storage devices, and network resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and relates to an implementation in which at least a portion of the functions are implemented as one or more virtual components (e.g., by one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0322] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 4300 hosted by one or more hardware nodes 4330. Furthermore, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), the network nodes may be fully virtualized at this point.

[0323] These functions 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 features, functions, and / or benefits of some embodiments disclosed herein. The applications 4320 run in a virtualized environment 4300, which provides hardware 4330 including processing circuitry 4360 and memory 4390. The memory 4390 contains instructions 4395 executable by the processing circuitry 4360, whereby the applications 4320 are operable to provide one or more features, benefits, and / or functions disclosed herein.

[0324] The virtualized environment 4300 includes a general or special purpose network hardware device 4330, which includes a set of one or more processors or processing circuits 4360, which may be commercial off-the-shelf (COTS) processors, application-specific integrated circuits (ASICs), or any other type of processing circuit including digital or analog hardware components or special purpose processors. 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 circuit 4360. Each hardware device may include one or more network interface controllers (NICs) 4370, also known 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 circuit 4360 are stored. The software 4395 may include any type of software, including software for instantiating one or more virtualization layers 4350 (also known as hypervisors), software for executing virtual machines 4340, and software that allows them to perform the functions, features, and / or benefits described in connection with some embodiments described herein.

[0325] The virtual machine 4340 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by a corresponding virtualization layer 4350 or hypervisor. Different embodiments of instances of the virtual device 4320 can be implemented on one or more of the virtual machines 4340, and the implementation can be made in different ways.

[0326] During operation, processing circuitry 4360 executes software 4395 to instantiate a hypervisor or virtualization layer 4350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 4350 may present a virtual operating platform that appears to virtual machine 4340 as networked hardware.

[0327] like Fig.23As shown, hardware 4330 can be an independent network node with common or specific components. Hardware 4330 can include antenna 43225 and some functions can be implemented through virtualization. Alternatively, hardware 4330 can be part of a larger hardware cluster (e.g., in a data center or customer premises equipment (CPE)), where many hardware nodes work together and are managed by management and coordination (MANO) 43100, which oversees life cycle management of application 4320, etc.

[0328] In some contexts, virtualization of hardware is referred to as network function virtualization (NFV). NFV can be used to unify numerous network equipment types onto industry-standard high-capacity server hardware, physical switches, and physical storage that can be located in data centers and customer premises equipment.

[0329] In the context of NFV, virtual machines 4340 may be software implementations of physical machines that run programs as if they were executed on a physical, non-virtualized machine. Each virtual machine 4340 and the portion of hardware 4330 that executes the virtual machine (which may be hardware dedicated to the virtual machine and / or hardware shared by the virtual machine and other virtual machines in virtual machines 4340) form a separate virtual network element (VNE).

[0330] Still in 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 network infrastructure 4330 and corresponds to Fig.23 Applications in 4320.

[0331] 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 units 43200 may communicate directly with the hardware nodes 4330 via one or more suitable network interfaces, and may be used in conjunction with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station.

[0332] In some embodiments, some signaling may be implemented using a control system 43230 , which may alternatively be used for communications between the hardware node 4330 and the radio unit 43200 .

[0333] Fig.24 A telecommunications network is shown connected to a host computer via an intermediary network in accordance with some embodiments.

[0334] Reference Fig.24According to an embodiment, a communication system includes a telecommunication network 4410 (e.g., a cellular network of the 3GPP type), the telecommunication network 4410 including an access network 4411 (e.g., a radio access network) and a core network 4414. The access network 4411 includes a plurality of base stations 4412a, 4412b, 4412c (e.g., NB, eNB, gNB or other types of wireless access points), each base station defining a corresponding coverage area 4413a, 4413b, 4413c. Each base station 4412a, 4412b, 4412c is connectable to the core network 4414 via a wired or wireless connection 4415. A first UE 4491 located in the coverage area 4413c is configured to be wirelessly connected to the corresponding base station 4412c or to be paged by the corresponding base station 4412c. A second UE 4492 in the coverage area 4413a is wirelessly connectable to the corresponding base station 4412a. Although multiple UEs 4491 , 4492 are shown in this example, the disclosed embodiments are equally applicable to situations where only a UE is in the coverage area or a only UE is connected to the corresponding base station 4412 .

[0335] The telecommunications network 4410 itself is connected to a host computer 4430, which may be implemented in hardware and / or software as a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server cluster. The host computer 4430 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 4421 and 4422 between the telecommunications network 4410 and the host computer 4430 may extend directly from the core network 4414 to the host computer 4430, or may be made via an optional intermediate network 4420. The intermediate network 4420 may be a combination of one or more of a public, private, or carrier network; the intermediate network 4420 (if present) may be a backbone network or the Internet; specifically, the intermediate network 4420 may include two or more subnetworks (not shown).

[0336] Fig.24The communication system as a whole implements a connection between the connected UEs 4491, 4492 and the host computer 4430. The connection can be described as an over-the-top (OTT) connection 4450. The host computer 4430 and the connected UEs 4491, 4492 are configured to use the access network 4411, the core network 4414, any intermediate networks 4420 and possible other infrastructure (not shown) as intermediaries to transmit data and / or signaling via the OTT connection 4450. The OTT connection 4450 can be transparent in the sense that the participating communication devices through which the OTT connection 4450 passes are not aware of the routing of the uplink and downlink communications. For example, the base station 4412 may not be informed or may not need to be informed of the past routing of the incoming downlink communication with data originating from the host computer 4430 to be forwarded (e.g., handed over) to the connected UE 4491. Similarly, the base station 4412 need not be aware of the future routing of outgoing uplink communications originating from the UE 4491 to the host computer 4430.

[0337] Fig.25 A host computer is shown communicating with a user device via a base station over a partially wireless connection in accordance with some embodiments.

[0338] Now refer to Fig.25 To describe an example implementation of the UE, base station, and host computer discussed in the previous paragraph according to the embodiment. In the communication system 4500, the host computer 4510 includes hardware 4515, and the hardware 4515 includes a communication interface 4516, which is configured to establish and maintain a wired or wireless connection with the interface of different communication devices of the communication system 4500. The host computer 4510 also includes a processing circuit 4518, which may have storage and / or processing capabilities. Specifically, the processing circuit 4518 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination thereof (not shown) suitable for executing instructions. The host computer 4510 also includes software 4511, which is stored in the host computer 4510 or can be accessed by the host computer 4510 and can be executed by the processing circuit 4518. Software 4511 includes a host application 4512. The host application 4512 is operable to provide services to a remote user (e.g., UE 4530), which is connected via an OTT connection 4550 terminated at the UE 4530 and the host computer 4510. In providing services to the remote user, the host application 4512 may provide user data sent using the OTT connection 4550.

[0339] The communication system 4500 also includes a base station 4520 provided in the telecommunication system, the base station 4520 including hardware 4525 enabling it to communicate with the host computer 4510 and with the UE 4530. The hardware 4525 may include: a communication interface 4526 for establishing and maintaining a wired or wireless connection with the interface of different communication devices of the communication system 4500; and a radio interface 4527 for establishing and maintaining at least a connection with a network located in the coverage area ( Fig.25 The communication interface 4526 may be configured to facilitate a connection 4560 to the host computer 4510. The connection 4560 may be direct, or it may pass through a core network (eg, a wireless network) of the telecommunications system. Fig.25 45) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 4525 of the base station 4520 also includes processing circuitry 4528, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 4520 also has software 4521 stored internally or accessible via an external connection.

[0340] The communication system 4500 also includes the UE 4530 already mentioned. Its hardware 4535 may include a radio interface 4537, which is configured to establish and maintain a wireless connection 4570 with a base station serving the coverage area where the UE 4530 is currently located. The hardware 4535 of the UE4530 also includes a processing circuit 4538, which may include one or more programmable processors, application-specific integrated circuits, field programmable gate arrays, or a combination thereof (not shown) suitable for executing instructions. The UE4530 also includes software 4531, which is stored in the UE 4530 or can be accessed by the UE 4530 and can be executed by the processing circuit 4538. The software 4531 includes a client application 4532. The client application 4532 is operable to provide services to human or non-human users via the UE 4530 with the support of the host computer 4510. In the host computer 4510, the executing host application 4512 can communicate with the executing client application 4532 via the OTT connection 4550 terminated at the UE 4530 and the host computer 4510. When providing services to users, the client application 4532 can receive request data from the host application 4512 and provide user data in response to the request data. The OTT connection 4550 can transmit both the request data and the user data. The client application 4532 can interact with the user to generate the user data it provides.

[0341] Notice, Fig.25The host computer 4510, base station 4520 and UE 4530 shown can be respectively Fig.24 The host computer 4430, one of the base stations 4412a, 4412b, 4412c and one of the UEs 4491, 4492 may be similar or identical. That is, the internal workings of these entities may be similar to or identical to those of the host computer 4430, one of the base stations 4412a, 4412b, 4412c and one of the UEs 4491, 44 Fig.25 As shown, and independently, the surrounding network topology can be Fig.24 network topology.

[0342] exist Fig.25 45, an OTT connection 4550 has been abstractly drawn to show communications between a host computer 4510 and a UE 4530 via a base station 4520, without explicitly mentioning any intermediate devices and the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from the UE 4530 or from the service provider operating the host computer 4510, or from both. While the OTT connection 4550 is active, the network infrastructure can also make decisions that dynamically change the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0343] The wireless connection 4570 between the UE 4530 and the base station 4520 is in accordance with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments may improve the performance of an OTT service provided to the UE 4530 using the OTT connection 4550, wherein the wireless connection 4570 forms the last leg in the OTT connection 4550. More specifically, the teachings of these embodiments may increase random access speed and / or reduce random access failure rate, thereby providing benefits such as faster and / or more reliable random access.

[0344] For the purpose of monitoring the data rate, latency and other factors improved by one or more embodiments, a measurement process may be provided. There may also be an optional network function for reconfiguring the OTT connection 4550 between the host computer 4510 and the UE 4530 in response to changes in the measurement results. The measurement process and / or network function for reconfiguring the OTT connection 4550 may be implemented in software 4511 and hardware 4515 of the host computer 4510 or in software 4531 and hardware 4535 of the UE 4530 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 4550 passes; the sensor may participate in the measurement process by providing the value of the monitoring quantity exemplified above or providing the value of other physical quantities that the software 4511, 4531 can use to calculate or estimate the monitoring quantity. Reconfiguration of the OTT connection 4550 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration need not affect the base station 4520, and it may be unknown or imperceptible to the base station 4520. Such processes and functions may be known and practiced in the art. In a particular embodiment, the measurement may involve proprietary UE signaling that facilitates the host computer 4510 to measure throughput, propagation time, latency, etc. The measurement may be implemented as follows: the software 4511 and 4531 enable the use of the OTT connection 4550 to send messages (specifically, empty messages or "fake" messages) while it monitors propagation time, errors, etc.

[0345] Fig.26 A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is shown.

[0346] Fig.26 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be a reference Figure 24 to Figure 25 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section will be included. Fig.26 In step 4610, the host computer provides user data. In sub-step 4611 of step 4610 (which may be optional), the host computer provides the user data by executing a host application. In step 4620, the host computer initiates a transmission to the UE carrying the user data. In step 4630 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 4640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0347] Fig. 27 A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is shown.

[0348] Fig. 27 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be a reference Figure 24 to Figure 25 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section will be included. Fig. 27 In step 4710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 4720, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be via a base station. In step 4730 (which may be optional), the UE receives the user data carried in the transmission.

[0349] Fig.28 A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is shown.

[0350] Fig.28 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be a reference Figure 24 to Figure 25 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section will be included. Fig.28 . In step 4810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, 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, which provides user data in response to input data provided by the received host computer. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner of providing user data, the UE initiates transmission of user data to the host computer in sub-step 4830 (which may be optional). In step 4840 of the method, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data sent from the UE.

[0351] Fig.29 A method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments is shown.

[0352] Fig.29 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which may be a reference Figure 24 to Figure 25 For the sake of simplicity of this disclosure, only the host computer, base station and UE described in this section will be included. Fig.29 In step 4910 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station receives user data from the UE. In step 4920 (which may be optional), the base station initiates 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.

[0353] 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 a plurality of these functional units. These functional units may be implemented by a processing circuit, which may include one or more microprocessors or microcontrollers and other digital hardware (may include a digital signal processor (DSP), dedicated digital logic, etc.). The processing circuit may be configured to execute program codes stored in a memory, which may include one or more types of memory, such as a read-only memory (ROM), a random access memory (RAM), a cache memory, a flash memory device, an optical storage device, 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, the processing circuit may be used to cause the corresponding functional unit to perform corresponding functions according to one or more embodiments of the present disclosure.

[0354] The term unit may have a conventional meaning in the field of electronic products, electrical devices and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing various tasks, processes, calculations, output and / or display functions, etc. (such as those described herein).

[0355] Further definitions and embodiments are discussed below.

[0356] In the above description of various embodiments of the inventive concept, it is to be understood that the terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the inventive concept. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meanings as commonly understood by ordinary technicians in the field to which the inventive concept belongs. It should also be understood that terms such as those defined in general dictionaries should be interpreted as having meanings consistent with their meanings in the context of this specification and the relevant technology, and not interpreted as ideal or overly superficial meanings, unless so clearly defined herein.

[0357] When an element is referred to as being "connected", "coupled", "responsive" or a variation thereof relative to another element, it may be directly connected, coupled to or responsive to other elements, or there may be an intermediate element. On the contrary, when an element is referred to as being "directly connected", "directly coupled", "directly responsive" or a variation thereof relative to another element, there is no intermediate element. Throughout the text, similar reference numerals represent similar elements. In addition, "coupling", "connection", "responsiveness" or a variation thereof used herein may include wireless coupling, connection or response. As used herein, the singular forms "one", "an" and "said" are intended to also include plural forms, unless the context clearly indicates otherwise. For the sake of brevity and / or clarity, known functions or structures may not be described in detail. The term "and / or" (abbreviated as " / ") includes any and all combinations of one or more related listed items.

[0358] It will be understood that although the terms first, second, third, etc. can be used herein to describe each element / operation, these elements / operations should not be limited by these terms. These terms are only used to distinguish one element / operation from another element / operation. Therefore, the first element / operation in some embodiments can be referred to as the second element / operation in other embodiments without departing from the teaching of the inventive concept. Throughout the specification, the same reference numerals or the same reference signs represent the same or similar elements.

[0359] 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 stated features, integers, elements, steps, components, or functions, but do not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions, or combinations thereof. In addition, as used herein, the commonly used abbreviation "eg," derived from the Latin phrase "exempli gratia," may be used to introduce or specify one or more general examples of a previously mentioned item without being intended as a limitation of that item. The commonly used abbreviation "ie," derived from the Latin phrase "idest," may be used to specify a specific item of a more general reference.

[0360] Example embodiments are described herein with reference to block diagrams and / or flowchart illustrations of computer-implemented methods, devices (systems and / or equipment), and / or computer program products. It should be understood that the blocks of the block diagrams and / or flowchart illustrations and the combination of blocks in the block diagrams and / or flowchart illustrations can be implemented by computer program instructions executed by one or more computer circuits. These computer program instructions can be provided to processor circuits of general-purpose computer circuits, special-purpose computer circuits, and / or other programmable data processing circuits to produce a machine, so that instructions executed by processors of computers and / or other programmable data processing devices convert and control transistors, values ​​stored in memory locations, and other hardware components within such circuits to implement the functions / actions specified in the block diagrams and / or flowcharts, and thereby create a device (functional body) and / or structure for implementing the functions / actions specified in the block diagrams and / or flowcharts.

[0361] These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing device to act in a specific manner so that the instructions stored in the computer-readable medium produce an article of manufacture, the article of manufacture including instructions for implementing the functions / actions specified in the blocks of the block diagrams and / or flow charts. Therefore, embodiments of the present inventive concept 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, which may be collectively referred to as a "circuit", "module" or variations thereof.

[0362] It should also be noted that in some alternative implementations, the function / action marked in the frame may not occur in the order marked in the flow chart. For example, depending on the function / action involved, the two frames shown in succession can actually be performed substantially simultaneously, or the frame can sometimes be performed in the opposite order. In addition, the function of a given frame of a flow chart and / or block diagram can be divided into multiple frames and / or the function of two or more frames of a flow chart and / or block diagram can be integrated at least in part. Finally, without departing from the scope of the inventive concept, other frames can be added / inserted between the frames shown, and / or the frame / operation can be omitted. In addition, although some figures include arrows on the communication path to illustrate the main direction of communication, it should be understood that communication can occur in the direction opposite to the arrows depicted.

[0363] Under the premise of not departing from the principle of the inventive concept in principle, many changes and modifications can be made to the embodiments. All these changes and modifications are intended to be included in the scope of the inventive concept herein. Therefore, the subject matter disclosed above should be understood as exemplary and not restrictive, and the examples of the embodiments are intended to cover all these modifications, enhancements and other embodiments that fall within the spirit and scope of the inventive concept. Therefore, to the maximum extent permitted by law, the scope of the inventive concept should be determined by the widest permissible interpretation of the present disclosure including the examples of the embodiments and their equivalents, and should not be limited to or restricted to the previous specific embodiments.

Claims

1. A method for operating a communication device, the communication device being configured to operate in a dual-connection DC with a primary node MN and a secondary node SN, and being configured with a primary cell group MCG configuration associated with the MN and a secondary cell group SCG configuration associated with the SN, the method comprising: detecting (1910) a radio link failure on the MCG; Determine (1920) whether a primary and secondary cell group cell PSCell change process is in progress; as well as Based on whether the PSCell change procedure is in progress, respond (1930) to a radio link failure on the MCG.

2. The method according to claim 1, wherein: Responding to a radio link failure on the MCG is also based on whether the PSCell change procedure includes reconfiguring the DC between the MN and a different SN.

3. The method according to claim 1, wherein: Responding to a radio link failure on the MCG is also based on whether the PSCell change procedure includes changing the PSCell to a different cell within the SN.

4. The method according to any one of claims 1 to 3, wherein: Determining whether the PSCell change process is in progress includes: determining whether a timer for the PSCell is running.

5. The method according to claim 4, wherein: Responding to a radio link failure on the MCG includes, in response to determining that the timer is running, performing (1932) a radio resource control, RRC, re-establishment.

6. The method according to claim 4, wherein: Determining whether the PSCell change procedure is in progress includes determining whether a timer for the PSCell is not running.

7. The method according to claim 6, wherein: Responding to a radio link failure on the MCG includes, in response to determining that the timer is not running, reporting (1934) MCG failure information.

8. The method according to any one of claims 1 to 3, wherein: The DC includes one of the following: New Radio - New Radio Dual Connectivity NR-DC; Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity EN-DC connected to Evolved Packet Core; Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity NGEN-DC connected to 5th Generation Core; New Radio Evolved Universal Terrestrial Radio Access New Dual Connectivity NE-DC; or multi-radio dual-connection MR-DC.

9. A communication device (1600), configured to operate in a dual-connection DC with a primary node MN and a secondary node SN, and configured with a primary cell group MCG configuration associated with the MN and a secondary cell group SCG configuration associated with the SN, the communication device comprising: Processing circuit (1603); as well as A memory (1605) coupled to the processing circuit and storing instructions executable by the processing circuit to cause the communication device to perform operations, the operations comprising: detecting (1910) a radio link failure on the MCG; Determine (1920) whether a primary and secondary cell group cell PSCell change procedure is in progress; and Based on whether the PSCell change procedure is in progress, respond (1930) to a radio link failure on the MCG.

10. The communication device according to claim 9, wherein: Responding to a radio link failure on the MCG is also based on whether the PSCell change procedure includes reconfiguring the DC between the MN and a different SN.

11. The communication device according to claim 9, wherein: Responding to a radio link failure on the MCG is also based on whether the PSCell change procedure includes changing the PSCell to a different cell within the SN.

12. The communication device according to any one of claims 9 to 11, wherein: Determining whether the PSCell change process is in progress includes: determining whether a timer for the PSCell is running.

13. The communication device according to claim 12, wherein: Responding to a radio link failure on the MCG includes, in response to determining that the timer is running, performing (1932) a radio resource control, RRC, re-establishment.

14. The communication device according to claim 11, wherein: Determining whether the PSCell change procedure is in progress includes determining whether a timer for the PSCell is not running.

15. The communication device according to claim 14, wherein: Responding to a radio link failure on the MCG includes, in response to determining that the timer is not running, reporting (1934) MCG failure information.

16. The communication device according to any one of claims 9 to 11, wherein: The DC includes one of the following: New Radio - New Radio Dual Connectivity NR-DC; Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity EN-DC connected to Evolved Packet Core; Evolved Universal Terrestrial Radio Access New Radio Dual Connectivity NGEN-DC connected to 5th Generation Core; New Radio Evolved Universal Terrestrial Radio Access New Dual Connectivity NE-DC; or multi-radio dual-connection MR-DC.

17. A computer program product comprising program code to be executed by a processing circuit (1603) of a communication device (1600), the communication device (1600) being configured to operate in a dual-connectivity DC with a primary node MN and a secondary node SN and being configured with a primary cell group MCG configuration associated with the MN and a secondary cell group SCG configuration associated with the SN, whereby execution of the program code causes the communication device to perform operations comprising: detecting (1910) a radio link failure on the MCG; Determine (1920) whether a primary and secondary cell group cell PSCell change process is in progress; as well as Based on whether the PSCell change procedure is in progress, respond (1930) to a radio link failure on the MCG.

18. The computer program product of claim 17, the operations further comprising any of the operations of any of claims 2 to 8.

19. A non-transitory storage medium comprising a program code to be executed by a processing circuit (1603) of a communication device (1600), the communication device (1600) being configured to operate in a dual-connectivity DC with a primary node MN and a secondary node SN and being configured with a primary cell group MCG configuration associated with the MN and a secondary cell group SCG configuration associated with the SN, whereby execution of the program code causes the communication device to perform operations comprising: detecting (1910) a radio link failure on the MCG; Determine (1920) whether a primary and secondary cell group cell PSCell change process is in progress; as well as Based on whether the PSCell change procedure is in progress, respond (1930) to a radio link failure on the MCG.

20. The non-transitory storage medium of claim 19, the operations further comprising any of the operations of any of claims 2 to 8.

Images