WO2020165624A1 - Gestion de défaillance de groupe de cellules maîtresses par un nœud secondaire - Google Patents

Gestion de défaillance de groupe de cellules maîtresses par un nœud secondaire Download PDF

Info

Publication number
WO2020165624A1
WO2020165624A1 PCT/IB2019/051082 IB2019051082W WO2020165624A1 WO 2020165624 A1 WO2020165624 A1 WO 2020165624A1 IB 2019051082 W IB2019051082 W IB 2019051082W WO 2020165624 A1 WO2020165624 A1 WO 2020165624A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
failure
user equipment
node
configuration
Prior art date
Application number
PCT/IB2019/051082
Other languages
English (en)
Inventor
Antonino ORSINO
Patrick RUGELAND
Osman Nuri Can Yilmaz
Oumer Teyeb
Stefan Wager
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/IB2019/051082 priority Critical patent/WO2020165624A1/fr
Priority to PCT/IB2020/050933 priority patent/WO2020165697A1/fr
Priority to EP20704608.7A priority patent/EP3925399A1/fr
Priority to RU2021120689A priority patent/RU2769279C1/ru
Priority to BR112021013577-4A priority patent/BR112021013577A2/pt
Priority to JP2021545491A priority patent/JP7288965B2/ja
Priority to CN202080013775.6A priority patent/CN113424651B/zh
Priority to US16/930,573 priority patent/US11877332B2/en
Publication of WO2020165624A1 publication Critical patent/WO2020165624A1/fr
Priority to US18/531,532 priority patent/US20240129983A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the present disclosure relates to wireless communication systems such as cellular networks, and more particularly to methods, user equipments, and network nodes for handling a communication failure in dual and/or multiple connectivity network environments.
  • DC dual-connectivity
  • LTE Long Term Evolution
  • NR New Radio
  • DC includes a master node (MN) and a Secondary Node (SN), while Multi-connectivity (MC) includes additional nodes.
  • MN master node
  • SN Secondary Node
  • MC Multi-connectivity
  • URLLC Ultra Reliable Low Latency Communications
  • NR and LTE can be deployed without any interworking, denoted by NR stand-alone (SA) operation. That is, an NR base station (gNB) can be connected to a 5G core network (5GC) and an LTE base station (eNB) can be connected to EPC with no interconnection between the two.
  • SA NR stand-alone
  • gNB NR base station
  • eNB LTE base station
  • EN-DC E-UTRAN-NR Dual Connectivity
  • a gNB MN may be referred to as a MgNB and an eNB SN may be referred to as a SeNB.
  • the radio access network (RAN) node supporting NR may not have a control plane connection to the core network, and instead may rely on an MeNB. This is also called“Non- standalone NR.” In this scenario the functionality of an NR cell is limited and would be used for connected mode user equipments (UEs) as a booster and/or diversity leg, but a UE in an RRC IDLE mode would not be able to camp on these NR cells.
  • UEs connected mode user equipments
  • a gNB is connected to a 5GC.
  • an eNB can also be connected to a 5GC.
  • This configuration may also be known as eLTE, E- UTRAN/5GC, or LTE/5GC and the node can be referred to as an ng-eNB.
  • both NR and LTE are seen as part of the NG-RAN, and both the ng-eNB and the gNB can be referred to as NG-RAN nodes.
  • MR-DC Multi-Radio Dual Connectivity
  • EN-DC The master node in an LTE node and the secondary node is an NR node (EPC CN employed)
  • the master node is an NR node and the secondary node is an LTE node (5GCN employed)
  • NGEN-DC The master node in an LTE node and the secondary node is an NR node (5GCN employed)
  • NR-DC Dual connectivity, where both the master and secondary nodes are NR nodes (5GCN employed).
  • the UE Upon the initiation of a re-establishment procedure in LTE, the UE suspends all RBs except signaling radio bearer 0 (SRBO). The UE will then send the RRCConnectionReestablishmentRequest message on SRBO. At this stage, the UE will either receive a RRCConnectionReestablishment or a RRCConnectionReestablishmentReject message on SRBO. In case the UE receives an RRCConnectionReestablishment, it will re establish SRB 1 and send the RRCConnectionReestablishmentComplete message on SRB 1. According to 36.331, the network is not allowed to start sending downlink (DL) messages on SRB 1 until it receives the RRCConnectionReestablishmentComplete message.
  • DL downlink
  • the UE In case the UE gets back an RRCConnectionReestablishmentReject message, it will perform actions upon leaving an RRC connected state and inform the NAS layer about an RRC connection failure. This will trigger the NAS layer to perform recovery, which includes a new RRC connection setup. All these response messages after the transmission of an RRC connection re-establishment request message are sent on SRBO, which means that they are not encrypted or integrity protected.
  • the E-UTRA re-establishment procedure was revisited during NR standardization and in RAN2# 101 in Sanya. Some aspects have been agreed to be enhanced to speed up the failure recovery, for example in case of handover failures. These enhancements include the following:
  • RRCReestablishment on SRB 1 The RAN2 understanding was that there was no fundamental reason why the UE could not re-establish PDCP for SRB 1 and resume SRB 1 in the DL before submitting MSG3 to lower layers. This would make it possible to use SRB 1 for MSG4 instead of SRBO, which would in turn make it possible to send a subsequent RRC re -configuration message in conjunction with MSG4 or directly after instead of waiting for the UE response in MSG5, which would save a roundtrip in the re-establishment of data radio bearers (DRBs);
  • DRBs data radio bearers
  • RRCSetup message in response to an RRCReestablishmentRequest message The RAN2 understanding was that it would also be possible to support faster NAS recovery in the RAN in the case that the RAN is not able to re-establish the UE context (for example, when a cell is not prepared during handover failure). This could be done by the network sending an RRC connection setup message on SRBO (instead of an RRC re-establishment reject message) which could be used to initiate normal RRC connection setup; and
  • RRCReestablishmentReject message was removed: The RAN2 understanding was that this was not needed any longer because of a fallback procedure. If the UE tries to re-establish in a cell that is not prepared or that the network cannot re-establish the DRBs, the network can send an RRCSetup message. And, in the scenario where the cell is overloaded, network may simply wait until the failure timer T301 expires, so that the UE would enter RRC IDLE and would perform access control before trying again.
  • a UE determines a radio link failure (RLF) based on:
  • RLC radio link control
  • the UE When an RLF is detected, the UE prepares an RLF report, which includes, among other information, the measurement status of the serving and neighbor cells at the moment when RLF was detected.
  • the UE goes to IDLE mode, selects a cell following IDLE mode cell selection procedure (the selected cell could be the same serving node/cell or another node/cell) and starts the RRC re-establishment procedure, with a cause value set to rlf-cause.
  • the RLF detection procedure is similar to what was described above except that: for the out of sync indications are detected with respect to the PCell of the MN; the MAC is for the MCG MAC entity; the RLC is for the MCG; and the DRB in corresponds to the MCG and MCG-split DRBs. If the RLF is detected on the MCG, then the UE triggers the RRC re-establishment procedure. Accordingly, the RRC connection on the MCG and SCG would be released and a new RRC connection would be re-established.
  • the failure is determined based on:
  • the UE Upon detecting SCGFailure, the UE sends an SCGFailurelnformation message towards the MN, which also includes measurement reports, and the MN can either release the SN, change the SN/Cell, or re-configure the SCG. Thus, a failure on the SCG will not lead to a re-establishment to be performed on the MCG.
  • 3GPP has agreed to adopt the same principles in the context of EN-DC (i.e., re establishment in the case of RLE on the master leg and recovery via SCGFailurelnformation and SN release/change/modification in case of RLF on the secondary leg). Specifically, it has been agreed that for SgNB failures, the UE shall:
  • the examples disclosed in the present disclosure provide techniques for improving efficiency of communications in a radio access network by allowing a user equipment (UE) to send a failure message and/or report to a secondary node upon detecting a Master Cell Group (MCG) related radio link failure (RLF), or other failure relating to a Master Node.
  • the secondary node is therefore provided with the ability to take actions to address the failure.
  • RRC radio resource control
  • the failure is indicated by the reception of a Failurelnformation message via SRB3.
  • actions the SN can trigger to address the failure include handover, re-establishment, or fallback to an RRC IDLE state with accompanying RRC messages.
  • the techniques described herein further include network signaling and UE actions and procedures to enable these actions to be triggered by the secondary node (SN).
  • a system of one or more computers can be configured to perform particular operations or actions corresponding to the above examples by virtue of having software, firmware, hardware, or a combination thereof installed on the system that in operation causes or cause the system to perform the actions.
  • One or more computer programs can be configured to perform particular operations or actions corresponding to the above examples by virtue of including instructions that, when executed by data processing apparatus, cause the apparatus to perform the actions.
  • a method performed by a secondary node in a radio access network includes receiving, from a user equipment, a first message corresponding to a detected failure of a connection between the user equipment and a master node. The method also includes receiving, in response to a request sent to the master node, a user equipment context from the master node. The method also includes determining, based on the first message and the user equipment context, to perform an action that includes at least one of: a connection re-configuration, a connection re-establishment, or a connection setup. The method also includes providing, to the user equipment, a second message corresponding to the determined action.
  • RAN radio access network
  • a method performed by a user equipment includes detecting a failure corresponding to a connection between the UE and a master node in a radio access network, RAN.
  • the method also includes providing, to the secondary node via signaling radio bearer 3, SRB3, a first message corresponding to the detected failure.
  • the method also includes receiving, from the secondary node, a second message indicating to the UE to perform a connection re-configuration, a connection re-establishment, or a connection setup.
  • a system including the user equipment and/or network node are provided that perform one or both of the above methods.
  • the present disclosure also provides a non-transitory computer-readable storage medium comprising computer instructions stored thereon that, when executed by a processing circuit, cause the processing circuit to perform either of the above methods.
  • Figure 1 is a flow diagram illustrating a method for handling a failure by a secondary node in a RAN network, according to some examples.
  • Figure 2 is a flow diagram illustrating a method for handling a failure by a UE in a RAN network, according to some examples.
  • Figure 3 is a sequence diagram illustrating failure handling by RAN network components, including a secondary node, according to some examples.
  • Figure 4 is a block diagram illustrating a failure corresponding to an MCG SRB, and a corresponding communication via SRB3 with an SN, according to some examples.
  • Figure 5 is a block diagram illustrating a wireless network, according to some examples.
  • the re-establishment fails, and the UE enters an RRC IDLE state and performs NAS recovery (i.e. establish the connection from scratch). As a result of the failure of the re establishment, there is a long service interruption.
  • the re-establishment request will be accepted by the network and a re-establishment message is sent to the UE, to establish SRB1.
  • the network upon the reception of a re-establishment complete message from the UE, the network sends an RRC re-configuration message that will optionally re-configure and resume the SRB2/DRBs, since they were suspended on RLF detection.
  • the network could configure SCG during this first re-configuration after re-establishment or wait to get measurement reports from the UE before performing a re -configuration.
  • the techniques described herein address the issues described above, and provide useful improvements to technology, resulting in more efficient network communications and faster recovery from failures. These techniques apply, for instance, to use-cases where a UE experiences an RLF on an MCG and where there is an SCG that is not experiencing an RLF. In these instances, upon detecting an RFF on the MCG, the UE is allowed to send a failure report (such as a Failurelnformation message) to the SN via the SRB3. Once the failure message is sent to the SN, the SN can perform different actions to respond to the failure.
  • a failure report such as a Failurelnformation message
  • the techniques described herein provide advantages over conventional networking techniques. For example, if an RFF is detected on the MCG, if SRB3 is configured, the techniques provided herein allow the UE to send a failure message/report to the SN directly via SRB3 so that the SN can take the necessary actions. Accordingly, an RRC re establishment procedure corresponding to the associated service interruption may be avoided, thereby reducing signaling overhead and improving recovery times.
  • the MN and SN may adopt different versions of RRC specifications or even different radio access technology.
  • encapsulation may be used for message transmissions.
  • an E-UTRA RRC message may be encapsulated within an NR RRC message that is transmitted over SRB3.
  • conversion between message types may be used, such as the SN converting a UE context received from the MN to another specification version or radio access technology.
  • Figure 1 is a flow diagram illustrating an example method for handling a failure by a secondary node in a RAN network. It is understood that one or more of the SN steps performed in this method may be performed in combination with one or more of the steps performed by the UE that are discussed in detail with respect to Figure 2.
  • a secondary node (SN) in a radio access network (RAN) receives, from a user equipment, a first message corresponding to a detected failure of a connection between the user equipment and a master node.
  • the failure may be detected as relating to a connection between the UE and a group of serving cells (the MCG) associated with the master node.
  • the detected failure is at least one of: a radio link failure (RLF), handover failure, re-configuration failure, or integrity protection failure.
  • the first message includes a failure cause, one or more measurements (which may be provided in measurement report(s)), and/or other status report or failure recovery information. More detail regarding the information that the UE may provide in the first message is discussed with respect to step 204 of Figure 2.
  • the first message may be a failure report message, which in some examples is a Radio Resource Control (RRC) Failurelnformation message, MCGFailurelnformation message, or an extension (such as a modified version) of these messages that are specified in TS 38.331.
  • RRC Radio Resource Control
  • MCGFailurelnformation message or an extension (such as a modified version) of these messages that are specified in TS 38.331.
  • the first message is an RRCReestablishmentRequest message, or extension thereof.
  • the UE may send the first message to the SN via SRB3 upon detection of the failure.
  • the first message may be provided to the SN in other ways, such as via an SCG path of a split signaling radio bearer 1, SRB1.
  • the secondary node sends a request to a master node to retrieve the UE context and receives, in response to the request, a user equipment context from the master node.
  • the retrieve UE context and retrieve UE context response messages are legacy message types or extended versions of the legacy message types.
  • the legacy message types may be extended to include a new failure cause value (indicating a cause of the master node failure).
  • the SN determines, based on the first message and the user equipment context, an action to perform that includes at least one of: a connection re -configuration (with or without handover), a connection re-establishment, or a connection setup.
  • the SN may make a more informed determination regarding the action to take in response to the failure, when the user equipment includes information such as measurements, beam failure information, and failure cause information in the first message. For example, the determination by the SN may be based on the measurements indicating that:
  • the PCell is still the best cell, and failure was due to another reason such as an integrity verification failure, re -configuration failure, or beam failure detection. Accordingly, the SN may send a re-configuration message with sync to resume the suspended bearers. Since the UE continues using the configuration used prior to the reception of an RRCReconfiguration message (in case of re -configuration failure), even a delta configuration with a re-configuration with sync may suffice to address the failure. DC is maintained with the original MN and SN nodes and MCG/SCG configurations;
  • the PSCell or an SCell belonging to the SCG is the best cell.
  • the SN may trigger the handover with itself as new target eNB/gNB by requesting the UE context from the MN;
  • the SN may send a connection re -configuration message with sync to handover to this cell.
  • DC is maintained with the original MN and SN nodes, MCG configuration updated (PCell is changed), and the SCG configurations are kept; • Another cell that belongs to the SN is the best cell. Accordingly, the SN may send a re -configuration message with sync to handover to this cell.
  • DC if active
  • the SN may be updated (PCell is changed);
  • the SN may initiate inter-MN handover without SN change procedure
  • the SN may initiate an inter-MN handover with SN change;
  • the MN initiates a MN to SN role switch.
  • the beam failure detection information may indicate to the SN that a beam failure has been detected and a new candidate beam may be provided within the beamFailureRecoveryConfig information.
  • the SN may determine to configure the UE to perform a Random Access (RACH) procedure towards the MCG associated with the master node based on the configuration sent with the beamFailureRecoveryConfig information.
  • RACH Random Access
  • Other information available in the network such as UE mobility, current traffic load, or other information, may also be used by the SN for its determination to perform a handover or other action.
  • the SN may apply rules that do not include obtaining measurement information.
  • the SN may be configured with a rule that, whenever SRB3 is configured, the SN may attempt to perform a connection re-configuration with handover to the SN upon MCG failure if the SCG is still connected. If the SCG also fails, the UE may then perform legacy RLF and/or re-establishment procedures.
  • the SN may be configured to attempt a handover to the SN if the SCG is still connected (for example, during re -configuration failure, and/or integrity protection failure and/or MCG RLF, and so forth). This configuration could be standardized, configured per UE, or configured per node.
  • the SN may determine to perform a connection re-establishment.
  • the SN may determine that the UE should to fallback to an RRC IDLE state, and therefore determine to perform a connection setup action.
  • the secondary node provides, to the user equipment, a second message corresponding to the determined action.
  • the SN determines the type and content of the second message based on the determined action.
  • the SN provides the second message to the UE via SRB3.
  • the second message may be provided via SRB0 to the UE, or via an SCG path of a split SRB1. Accordingly, where the second message is provided to the UE via SRB0, the UE may begin monitoring SRB0 from the SN when (or before) the UE transmits the first message to the SN.
  • the second message is an RRCReconfiguration message, which causes the UE to execute a handover to the SN so that the SN becomes the new MN/MCG.
  • the second message may include a handover configuration corresponding to the secondary node or another cell.
  • the SN may update the security context and security keys based on the obtained UE context from the MN.
  • the second message may specify a full or delta configuration including one or more of a bearer configuration, measurement configuration, or lower layer configuration.
  • the second message when the SN determines to perform a connection re-establishment, the second message may be an RRCReestablishment message that includes a NextHopChainingCount parameter that is used to re-establish security. In yet other examples, when the SN determines to perform a connection setup, the second message may be an RRCSetup message that causes UE to fallback to an RRC IDLE state.
  • Figure 2 is a flow diagram illustrating an example method for handling a failure by a UE in a RAN network. It is understood that one or more of the UE steps performed in this method may be performed in combination with one or more of the steps performed by the SN that are discussed in detail with respect to Figure 1.
  • the user equipment detects a failure corresponding to a connection between the UE and a master node in a radio access network, RAN.
  • the failure may be detected as relating to a connection between the UE and a group of serving cells (the MCG) associated with the master node.
  • the detected failure is at least one of: a radio link failure (RLF), handover failure, re-configuration failure, or integrity protection failure.
  • RLF radio link failure
  • handover failure re-configuration failure
  • integrity protection failure integrity protection failure.
  • the UE provides, to the secondary node, a first message corresponding to the detected failure.
  • the UE may provide the first message to a group of serving cells (the SCG) associated with the secondary node.
  • the first message may be a Failurelnformation message, RRCReestablishmentRequest message, MCGFailurelnformation message, an extension of one of these message types, or a new message type.
  • the UE provides the first message to the secondary node via signaling radio bearer 3, SRB3.
  • the UE provides the first message to the secondary node via a split SRB 1.
  • the first message may include one or more of:
  • a failure cause failure causes that can lead to RLF may include one or more of an indication of a random access problem (randomAccessProblem), maximum retransmissions of RLC (rlc-MaxNumRetx), indication of a failure to comply with an RRC message or a failure to complete a re -configuration before a timer expires (reconfigurationFailure), integrity failure (integrityProtectionFailure), maximum UL timing difference failure (maxUL-TimingDiff), or a beam failure (beamFailure);
  • measurement to be included may refer to the latest
  • SCG and MCG measurements i.e., inter-frequency and intra-frequency when available
  • particular measurement parameters may include ssbFreuency, refFreqCSI-RS, measResultServingCell, measResultNeighCellFistNR, measResultNeighCellFistEUTRA, or other measurements;
  • a buffer status report The type of traffic the UE has prior to the MCG failure and the importance of quickly re-establishing connectivity may be indicated by a buffer status report.
  • the buffer status report indicates how much data the UE has left in an UL buffer. If the UE has a lot of outstanding data in the buffer, the network could attempt to quickly setup DC again, whereas if the UE has neither pending DL nor UL traffic, the network may re-configure the UE to a more robust single connectivity cell (e.g. at lower frequencies);
  • the first message may indicate the the BeamFailureRecoveryConfig information element that is used to configure the UE with RACH resources and candidate beams; or
  • the UE receives, from the secondary node, a second message indicating to the user equipment to perform a connection re-configuration (with or without handover), a connection re-establishment, or a connection setup.
  • the UE may receive the second message from a group of serving cells (the SCG) associated with the secondary node.
  • the UE receives the second message from the SN via SRB3.
  • the second message is provided to the UE via SRB0 or via a split SRB1. Accordingly, where the second message is provided to the UE via SRB0, the UE may begin monitoring SRB0 from the SN when (or before) the UE transmits the first message to the SN.
  • the UE may execute a procedure to update its configuration corresponding to the received second message. For example, when the second message indicates to the UE to perform a connection re -configuration with handover (such as where the second message is an RRCReconfiguration message), the UE may execute a handover to the SN so that the SN becomes the new MN/MCG. Accordingly, the second message may include an updated security context and security keys, and may include a full or a delta configuration for re -configuring the UE.
  • the UE may send a complete message (for example, RRCReconfigurationComplete, RRCReestablishmentComplete, RRCSetupComplete) on SRB1 to the SN (which is now the new MN) according to the new configuration.
  • the UE may further discard its current SN security context and derive a new security context based on the received second message.
  • the security context may be updated in a subsequent message.
  • the new MN may then perform actions such as a path switch procedure, and the UE context may be released from the previous MN.
  • the second message may indicate to the UE to perform a connection re-establishment (such as when the second message is an RRCReestablishment message).
  • the second message may include a NextHopChainingCount parameter that is used to re-establish security.
  • the second message when the second message indicates to the UE to perform a connection setup (such as when the second message is an RRCSetup message), the second message may cause the UE to fallback to an RRC IDLE state.
  • Figure 3 is a sequence diagram illustrating an example of failure handling by RAN network components, including a secondary node, according to some examples.
  • This diagram illustrates an example of a particular sequence corresponding to the steps discussed above with respect to Figures 1 and 2. Accordingly, it is understood that the details of the steps discussed with respect to Figures 1 and 2 may be applied to the steps shown in Figure 3.
  • the UE is configured to communicate with the SN via SRB3. This configuration may be performed based on the UE receiving instructions from a network node, such as the MN or SN.
  • the UE detects a failure, and sends, at step 306, a corresponding failure message (referred to in Figures 1 and 2 as a first message) to the SN.
  • the SN requests a UE context from the MN, and at step 310, the MN provides a response to the SN that includes the UE context.
  • the SN determines, based on the received message, to perform a connection re-configuration with handover. In some examples, the SN may determine to perform a handover, connection re-establishment, or connection setup prior to request the UE context, and then at step 308 determine whether to keep, modify, or override the earlier decision.
  • the SN determines to handover the UE from the MN to the SN.
  • the SN transmits an RRCReconfiguration message (such as via the configured SRB3) to trigger a Random Access process at step 316.
  • the UE provides, at step 318, a complete message (here, an RRCReconfigurationComplete message). Accordingly, at block 320, the UE is connected to the SN, which has now become the MN.
  • the SN After the SN becomes the MN, the SN (the new MN) then sends at step 322 a path switch request to the AMF, which responds at step 324 with a path switch response. At step 326, the SN sends a UE Context Release message to the UE.
  • Figure 4 is a block diagram illustrating an example failure corresponding to an MCG SRB, and a corresponding communication via SRB3 with an SN. While this example shows an interaction of a UE, MN, and SN in an EN-DC configuration, these messaging techniques may be applied to other networking configurations as well.
  • a master node is communicatively coupled to a secondary node (SN 404) and a user equipment (UE 406).
  • MN 402 is an LTE node, it includes an LTE RRC (Radio Resource Control), PDCP (Packet Data Convergence Control), RLC (Radio Link Control), MAC (Medium Access Layer), and PHY (Physical) protocol stack.
  • SN 404 is an NR node, it includes an NR RRC, PDCP, RLC, MAC, and PHY protocol stack.
  • the UE 406 includes both NR and LTE protocol stacks.
  • the MN 402 communicates with the UE 406 via an MCG SRB 408 that is established for the MCG. Because there is a failure detected relating to the MCG SRB 408 corresponding to the MN, the UE 406 communicates with the SN 404 via SRB3 412 that is established between the UE 406 and the SN 404.
  • the SN 404 and the MN 402 communicate via an X2 interface 410 that is established between the MN 402 and SN 404.
  • the X2 interface 410 may communicate, for example, UE context information.
  • FIG. 5 is a block diagram illustrating an example wireless network.
  • the wireless network of Figure 5 depicts network 506, network nodes 560 and 560b, and wireless devices 510, 510b, and 510c.
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node 560 and wireless device (WD) 510 are depicted with additional detail.
  • the wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WLAN wireless local area network
  • WiMax Worldwide Interoperability for Microwave Access
  • Bluetooth Z-Wave and/or ZigBee standards.
  • Network 506 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), 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.
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless local area networks
  • wired networks wireless networks, metropolitan area networks, and other networks to enable communication between devices.
  • Network node 560 and WD 510 comprise various components described in more detail below. These components work together to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units 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).
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node 560 includes processing circuitry 570, device readable medium 580, interface 590, auxiliary equipment 584, power source 586, power circuitry 587, and antenna 562.
  • network node 560 illustrated in the example wireless network of Figure 5 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein.
  • network node 560 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 580 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 560 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node 560 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node 560 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node 560 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 560, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 560.
  • Processing circuitry 570 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 570 may include processing information obtained by processing circuitry 570 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 570 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Processing circuitry 570 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 560 components, such as device readable medium 580, network node 560 functionality.
  • processing circuitry 570 may execute instructions stored in device readable medium 580 or in memory within processing circuitry 570. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 570 may include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry 570 may include one or more of radio frequency (RF) transceiver circuitry 572 and baseband processing circuitry 574.
  • radio frequency (RF) transceiver circuitry 572 and baseband processing circuitry 574 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry 572 and baseband processing circuitry 574 may be on the same chip or set of chips, boards, or units
  • processing circuitry 570 executing instructions stored on device readable medium 580 or memory within processing circuitry 570.
  • some or all of the functionality may be provided by processing circuitry 570 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 570 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 570 alone or to other components of network node 560, but are enjoyed by network node 560 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 580 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, 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 devices that store information, data, and/or instructions that may be used by processing circuitry 570.
  • volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or
  • Device readable medium 580 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 570 and, utilized by network node 560.
  • Device readable medium 580 may be used to store any calculations made by processing circuitry 570 and/or any data received via interface 590.
  • processing circuitry 570 and device readable medium 580 may be considered to be integrated.
  • Interface 590 is used in the wired or wireless communication of signalling and/or data between network node 560, network 506, and/or WDs 510. As illustrated, interface 590 comprises port(s)/terminal(s) 594 to send and receive data, for example to and from network 506 over a wired connection. Interface 590 also includes radio front end circuitry 592 that may be coupled to, or in certain embodiments a part of, antenna 562. Radio front end circuitry 592 comprises filters 598 and amplifiers 596. Radio front end circuitry 592 may be connected to antenna 562 and processing circuitry 570. Radio front end circuitry may be configured to condition signals communicated between antenna 562 and processing circuitry 570.
  • Radio front end circuitry 592 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 592 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 598 and/or amplifiers 596. The radio signal may then be transmitted via antenna 562. Similarly, when receiving data, antenna 562 may collect radio signals which are then converted into digital data by radio front end circuitry 592. The digital data may be passed to processing circuitry 570. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • network node 560 may not include separate radio front end circuitry 592, instead, processing circuitry 570 may comprise radio front end circuitry and may be connected to antenna 562 without separate radio front end circuitry 592.
  • processing circuitry 570 may comprise radio front end circuitry and may be connected to antenna 562 without separate radio front end circuitry 592.
  • all or some of RF transceiver circuitry 572 may be considered a part of interface 590.
  • interface 590 may include one or more ports or terminals 594, radio front end circuitry 592, and RF transceiver circuitry 572, as part of a radio unit (not shown), and interface 590 may communicate with baseband processing circuitry 574, which is part of a digital unit (not shown).
  • Antenna 562 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 562 may be coupled to radio front end circuitry 590 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 562 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 562 may be separate from network node 560 and may be connectable to network node 560 through an interface or port.
  • Antenna 562, interface 590, and/or processing circuitry 570 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 562, interface 590, and/or processing circuitry 570 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 587 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 560 with power for performing the functionality described herein. Power circuitry 587 may receive power from power source 586. Power source 586 and/or power circuitry 587 may be configured to provide power to the various components of network node 560 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 586 may either be included in, or external to, power circuitry 587 and/or network node 560.
  • network node 560 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 587.
  • power source 586 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 587. The battery may provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, may also be used.
  • network node 560 may include additional components beyond those shown in Figure 5 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node 560 may include user interface equipment to allow input of information into network node 560 and to allow output of information from network node 560. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 560.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term WD may be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle- mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • PDA personal digital assistant
  • a wireless cameras a gaming console or device
  • a music storage device a playback appliance
  • a wearable terminal device a wireless endpoint
  • a mobile station a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (L
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to-everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device 510 includes antenna 511, interface 514, processing circuitry 520, device readable medium 530, user interface equipment 532, auxiliary equipment 534, power source 536 and power circuitry 537.
  • WD 510 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 510, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 510.
  • Antenna 511 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 514. In certain alternative embodiments, antenna 511 may be separate from WD 510 and be connectable to WD 510 through an interface or port. Antenna 511, interface 514, and/or processing circuitry 520 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 511 may be considered an interface.
  • interface 514 comprises radio front end circuitry 512 and antenna 511.
  • Radio front end circuitry 512 comprise one or more filters 518 and amplifiers 516.
  • Radio front end circuitry 514 is connected to antenna 511 and processing circuitry 520, and is configured to condition signals communicated between antenna 511 and processing circuitry 520.
  • Radio front end circuitry 512 may be coupled to or a part of antenna 511.
  • WD 510 may not include separate radio front end circuitry 512; rather, processing circuitry 520 may comprise radio front end circuitry and may be connected to antenna 511.
  • some or all of RF transceiver circuitry 522 may be considered a part of interface 514.
  • Radio front end circuitry 512 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 512 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 518 and/or amplifiers 516. The radio signal may then be transmitted via antenna 511. Similarly, when receiving data, antenna 511 may collect radio signals which are then converted into digital data by radio front end circuitry 512. The digital data may be passed to processing circuitry 520. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 520 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 510 components, such as device readable medium 530, WD 510 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 520 may execute instructions stored in device readable medium 530 or in memory within processing circuitry 520 to provide the functionality disclosed herein.
  • processing circuitry 520 includes one or more of RF transceiver circuitry 522, baseband processing circuitry 524, and application processing circuitry 526.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry 520 of WD 510 may comprise a SOC.
  • RF transceiver circuitry 522, baseband processing circuitry 524, and application processing circuitry 526 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 524 and application processing circuitry 526 may be combined into one chip or set of chips, and RF transceiver circuitry 522 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 522 and baseband processing circuitry 524 may be on the same chip or set of chips, and application processing circuitry 526 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 522, baseband processing circuitry 524, and application processing circuitry 526 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 522 may be a part of interface 514.
  • RF transceiver circuitry 522 may condition RF signals for processing circuitry 520.
  • processing circuitry 520 executing instructions stored on device readable medium 530, which in certain embodiments may be a computer- readable storage medium.
  • some or all of the functionality may be provided by processing circuitry 520 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 520 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 520 alone or to other components of WD 510, but are enjoyed by WD 510 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 520 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 520, may include processing information obtained by processing circuitry 520 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 510, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing information obtained by processing circuitry 520 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 510, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • Device readable medium 530 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 520.
  • Device readable medium 530 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (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 devices that store information, data, and/or instructions that may be used by processing circuitry 520.
  • processing circuitry 520 and device readable medium 530 may be considered to be integrated.
  • User interface equipment 532 may provide components that allow for a human user to interact with WD 510. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 532 may be operable to produce output to the user and to allow the user to provide input to WD 510. The type of interaction may vary depending on the type of user interface equipment 532 installed in WD 510. For example, if WD 510 is a smart phone, the interaction may be via a touch screen; if WD 510 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment 532 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 532 is configured to allow input of information into WD 510, and is connected to processing circuitry 520 to allow processing circuitry 520 to process the input information. User interface equipment 532 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 532 is also configured to allow output of information from WD 510, and to allow processing circuitry 520 to output information from WD 510. User interface equipment 532 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 532, WD 510 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 534 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 534 may vary depending on the embodiment and/or scenario.
  • Power source 536 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD 510 may further comprise power circuitry 537 for delivering power from power source 536 to the various parts of WD 510 which need power from power source 536 to carry out any functionality described or indicated herein.
  • Power circuitry 537 may in certain embodiments comprise power management circuitry.
  • Power circuitry 537 may additionally or alternatively be operable to receive power from an external power source; in which case WD 510 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry 537 may also in certain embodiments be operable to deliver power from an external power source to power source 536. This may be, for example, for the charging of power source 536. Power circuitry 537 may perform any formatting, converting, or other modification to the power from power source 536 to make the power suitable for the respective components of WD 510 to which power is supplied.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne des systèmes, des procédés, et des appareils pour un équipement utilisateur, et des nœuds de réseau. Un exemple de procédé exécuté par un nœud secondaire comprend les étapes suivantes : le nœud secondaire reçoit, d'un équipement utilisateur, un premier message correspondant à une défaillance détectée d'une connexion entre l'équipement utilisateur et un nœud maître. Le nœud secondaire reçoit, du nœud maître, un contexte d'équipement utilisateur en réponse à une demande envoyée au nœud maître. Le nœud secondaire détermine, sur la base du premier message et du contexte d'équipement utilisateur, l'exécution d'une action comprenant au moins un élément parmi une reconfiguration de connexion, un rétablissement de connexion, ou un établissement de connexion. Le nœud secondaire fournit à l'équipement utilisateur un second message correspondant à l'action déterminée.
PCT/IB2019/051082 2019-02-11 2019-02-11 Gestion de défaillance de groupe de cellules maîtresses par un nœud secondaire WO2020165624A1 (fr)

Priority Applications (9)

Application Number Priority Date Filing Date Title
PCT/IB2019/051082 WO2020165624A1 (fr) 2019-02-11 2019-02-11 Gestion de défaillance de groupe de cellules maîtresses par un nœud secondaire
PCT/IB2020/050933 WO2020165697A1 (fr) 2019-02-11 2020-02-05 Gestion de défaillance de groupe de cellules maîtresses par un nœud maître
EP20704608.7A EP3925399A1 (fr) 2019-02-11 2020-02-05 Gestion de défaillance de groupe de cellules maîtresses par un n?ud maître
RU2021120689A RU2769279C1 (ru) 2019-02-11 2020-02-05 Обработка отказов главной группы сот главным узлом
BR112021013577-4A BR112021013577A2 (pt) 2019-02-11 2020-02-05 Manuseio de falha de grupo de células mestre por um nó mestre
JP2021545491A JP7288965B2 (ja) 2019-02-11 2020-02-05 マスタノードによるマスタセルグループ障害ハンドリング
CN202080013775.6A CN113424651B (zh) 2019-02-11 2020-02-05 主节点执行的主小区组失败处理
US16/930,573 US11877332B2 (en) 2019-02-11 2020-07-16 Master cell group failure handling by a master node
US18/531,532 US20240129983A1 (en) 2019-02-11 2023-12-06 Master cell group failure handling by a master node

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2019/051082 WO2020165624A1 (fr) 2019-02-11 2019-02-11 Gestion de défaillance de groupe de cellules maîtresses par un nœud secondaire

Publications (1)

Publication Number Publication Date
WO2020165624A1 true WO2020165624A1 (fr) 2020-08-20

Family

ID=65516692

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2019/051082 WO2020165624A1 (fr) 2019-02-11 2019-02-11 Gestion de défaillance de groupe de cellules maîtresses par un nœud secondaire

Country Status (1)

Country Link
WO (1) WO2020165624A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210014923A1 (en) * 2019-10-02 2021-01-14 Intel Corporation Radio link failure recovery with srb3 in mr-dc
WO2023273926A1 (fr) * 2021-07-01 2023-01-05 华为技术有限公司 Procédé et appareil de communication dans une connectivité multiple

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9980159B2 (en) * 2014-09-26 2018-05-22 Mediatek Inc. RRC re-establishment on secondary eNodeB for dual connectivity

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9980159B2 (en) * 2014-09-26 2018-05-22 Mediatek Inc. RRC re-establishment on secondary eNodeB for dual connectivity

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 37.340, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V15.4.0, 14 January 2019 (2019-01-14), pages 1 - 67, XP051591711 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210014923A1 (en) * 2019-10-02 2021-01-14 Intel Corporation Radio link failure recovery with srb3 in mr-dc
WO2023273926A1 (fr) * 2021-07-01 2023-01-05 华为技术有限公司 Procédé et appareil de communication dans une connectivité multiple

Similar Documents

Publication Publication Date Title
US11877332B2 (en) Master cell group failure handling by a master node
US11895545B2 (en) Suspend-resume in conditional handover
JP7318116B2 (ja) マスタセルグループ高速回復プロシージャの使用を指示するための方法、デバイス、コンピュータプログラムおよびコンピュータプログラム製品
WO2020197480A1 (fr) Amélioration des paramètres de transfert intercellulaire conditionnel dans la 5g
US20220345957A1 (en) Master cell group failure while there is an ongoing secondary cell group change
WO2021028807A1 (fr) Reprise de double connectivité sur une défaillance de liaison terrestre
WO2021091450A1 (fr) Repli vers la cellule source pendant un transfert intercellulaire à double pile de protocoles active
US20220264397A1 (en) Conditional handover upon measurement configuration modification
CN112567807B (zh) 用于切换的核心网指示和安全性处理
WO2020165624A1 (fr) Gestion de défaillance de groupe de cellules maîtresses par un nœud secondaire
US20230217280A1 (en) Measurement Triggering Based on Data Traffic
EP4193582A1 (fr) Mesures de qoe spéciales pendant une mobilité d'état connectée rrc
CN113424651B (zh) 主节点执行的主小区组失败处理
WO2022028230A1 (fr) Procédé et appareil de rétablissement de connexion entre un dispositif terminal et un réseau
US20240080695A1 (en) User Equipment Reporting of Reconnection after Link Failure
US20240089812A1 (en) Signaling for Releasing a Secondary Cell Group (SCG) Configuration
US20220369174A1 (en) Method for coordination of control plane traffic management during device reconfigurations and related apparatus
WO2022191763A1 (fr) Classification de défaillance de mobilité basée sur des informations de défaillance de mcg
CN116472738A (zh) 用于报告多个无线电链路故障的方法和设备
CN117395732A (zh) 切换信息报告方法以及用户设备
CN117063527A (zh) 对用于双活动协议栈回退后的无线电链路故障的自组织网络报告的增强

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19706759

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19706759

Country of ref document: EP

Kind code of ref document: A1