WO2020167212A1 - Radio link failure recovery over supplementary uplink - Google Patents

Radio link failure recovery over supplementary uplink Download PDF

Info

Publication number
WO2020167212A1
WO2020167212A1 PCT/SE2020/050118 SE2020050118W WO2020167212A1 WO 2020167212 A1 WO2020167212 A1 WO 2020167212A1 SE 2020050118 W SE2020050118 W SE 2020050118W WO 2020167212 A1 WO2020167212 A1 WO 2020167212A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
message
radio
sul
network node
Prior art date
Application number
PCT/SE2020/050118
Other languages
French (fr)
Inventor
Antonino ORSINO
Osman Nuri Can Yilmaz
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)
Publication of WO2020167212A1 publication Critical patent/WO2020167212A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0058—Allocation criteria
    • H04L5/006—Quality of the received signal, e.g. BER, SNR, water filling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0078—Timing of allocation
    • H04L5/0085—Timing of allocation when channel conditions change
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0014—Three-dimensional division
    • H04L5/0023—Time-frequency-space
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • 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
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for Radio Link Failure (RLF) recover over Supplementary Uplink (SUL).
  • RLF Radio Link Failure
  • FIGURE 1 illustrates LTE and NR interworking options. More specifically, as depicted in FIGURE 1, there are different ways to deploy 5G network with or without interworking with Long-Term Evolution (LTE), which may also be referred to as Evolved Universal Terrestrial Radio Access Network (E-UTRA) and evolved packet core (EPC).
  • LTE Long-Term Evolution
  • E-UTRA Evolved Universal Terrestrial Radio Access Network
  • EPC evolved packet core
  • SA NR stand-alone
  • gNB gNode B
  • 5GC 5G core network
  • eNode B eNode B
  • EPC evolved packet core
  • the first supported version of NR is referred to as Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity (EN-DC) and is illustrated by Option 3 in FIGURE 1.
  • Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity EN-DC
  • dual connectivity between NR and LTE is applied with LTE as the master and NR as the secondary node (SN).
  • the Radio Access Network (RAN) node supporting NR such as, for example, a gNB, may not have a control plane connection to core network. Instead, the RAN node relies on the LTE as a master node (MN) or master eNB (MeNB).
  • MN master node
  • MeNB master eNB
  • Non-standalone NR This is also called “Non-standalone NR.”
  • NR Non-standalone NR
  • the functionality of an NR cell is limited and would be used for connected mode UEs as a booster and/or diversity leg but an RRC IDLE user equipment (UE) cannot camp on these NR cells.
  • UE RRC IDLE user equipment
  • option 2 supports stand-alone NR deployment where gNB is connected to 5GC.
  • LTE can also be connected to 5GC using option 5, which is also known as evolved LTE (eLTE), E-UTRA/5GC, or LTE/5GC, and the node can be referred to as an ng-eNB.
  • eLTE evolved LTE
  • E-UTRA/5GC E-UTRA/5GC
  • LTE/5GC LTE/5GC
  • ng-eNB evolved LTE
  • 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).
  • Option 4 and Option 7 are other variants of dual connectivity between LTE and NR which will be standardized as part of NG-RAN connected to 5GC, denoted by Multi-Radio Dual Connectivity (MR-DC). Under the MR-DC umbrella, there is:
  • EN-DC (Option 3): LTE is the MN and NR is the SN (EPC CN employed)
  • NR is the MN and LTE is the SN (5GCN employed)
  • NGEN-DC Next Generation Radio Access Technology Network-Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity (Option 7): LTE is the MN and NR is the SN (5GCN employed)
  • New Radio-Dual Connectivity (variant of Option 2): Dual connectivity where both the MN and SN are NR (5GCN employed).
  • CA Carrier Aggregation
  • MCG master cell group
  • SCG secondary cell group
  • LTE cells a consequence of these different deployments is the co-existence of LTE cells associated to eNBs connected to EPC, 5GC, or both EPC/5GC.
  • LTE DC and EN-DC are designed differently when it comes to which nodes control what. Basically, there are two options:
  • a centralized solution such as, for example, LTE-DC, or
  • a decentralized solution such as, for example, EN-DC.
  • FIGURE 2 illustrates the schematic control plane architecture for LTE DC and EN-DC.
  • the SN has a separate Radio Resource Control (RR.C) entity, which may be referred to as a NR RR.C.
  • RR.C Radio Resource Control
  • the SN can also control the UE.
  • the SN may control the UE without the knowledge of the MN. But, the SN often needs to coordinate with the MN.
  • RR.C decisions always come from the MN (MN to UE). However, the SN still decides the configuration of the SN since it is only the SN itself that has knowledge of what kind of resources, capabilities, etc. the SN have. Two different DC specifications and their respective RRC messages are discussed below in more detail.
  • FIGURE 2 illustrates the control plane architecture for Dual Connectivity (DC) in LTE DC and EN-DC.
  • DC Dual Connectivity
  • LTE-NR DC also referred to as LTE-NR tight interworking
  • LTE-NR tight interworking the major changes from LTE DC are:
  • FIGURES 3 and 4 show the User Plane (UP) and Control Plane (CP) architectures for LTE-NR tight interworking. Specifically, FIGURE 3 illustrates the UP architecture for LTE- NR tight interworking, and FIGURE 4 illustrates the CP architecture for LTE-NR tight interworking.
  • UP User Plane
  • CP Control Plane
  • the SN is sometimes referred to as the SgNB, where the gNB is an NR base station.
  • the MN may be referred to as the MeNB where LTE is the MN and NR is the SN.
  • LTE is the MN
  • NR is the MN
  • SeNB SeNB
  • Split RRC messages are mainly used for creating diversity, and the sender can decide to either choose one of the links for scheduling the RRC messages, or it can duplicate the message over both links.
  • the path switching between the MCG or SCG legs or the duplication on both is left to network implementation.
  • the network configures the UE to use the MCG, SCG or both legs.
  • the terms“leg” and“path” are used interchangeably throughout this document.
  • FIGURE 5 illustrates a supplementary uplink in EN-DC.
  • the UE With the SUL, the UE is configured with two UL carriers and one DL carrier on the same cell. The switching between one carrier and another is controlled by the network through LI signaling.
  • a SUL When a SUL is configured to a UE, it is an additional uplink only secondary cell (SCell) and the control of the SUL depends on a regular paired primary cell (PCell).
  • SCell additional uplink only secondary cell
  • PCell regular paired primary cell
  • the UE is not allowed to use both carriers at the same time, and it is the network that indicates which carrier to use. For this case, usually the UE is configured with a contention free random access resource. Otherwise, if no indication is provided by the network, the UE performs a contention based random access procedure on the carrier (SUL or non-SUL) with the highest RSRP value.
  • the UE When CA is configured, the UE only has one RRC connection with the network. Further, at RRC connection establishment/re-establishment/handover, one serving cell provides the Non-Access Stratum (NAS) mobility information, and at RRC connection re establishment/handover, one serving cell provides the security input. This cell is referred to as the Primary Cell (PCell).
  • PCell Primary Cell
  • SCells Secondary Cells
  • PSCell Primary SCell
  • RRC signaling can also be used to add, remove, or reconfigure SCells for usage with the target PCell.
  • dedicated RRC signalling is used for sending all required system information of the SCell. For example, while in connected mode, UEs need not acquire broadcasted system information directly from the SCells.
  • a UE considers a radio link failure (RLF) to be detected in the following scenarios:
  • 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 then 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 (i) we are concerned only the PCell of the MN, the MAC in (ii) is the MCG MAC entity and the RLC in (iii) is the MCG RLC and the DRB in (iii) corresponds to MCG and MCG-split DRBs.
  • SCGFailure failure on the secondary side
  • 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 reconfigure 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 LTE-NR interworking (i.e. re-establishment in the case of RLF 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:
  • UE Upon SgNB failures, UE shall:
  • UE reports the failure to the gNB (e.g. SCell-RLF) but no RRC re-establishment happens
  • the UE Upon receiving N311 consecutive "in-sync" indications for the SpCell from lower layers while T310 is running, the UE shall:
  • the UE maintains the RRC connection without explicit signalling, i.e. the UE maintains the entire radio resource configuration.
  • the UE shall:
  • the UE shall:
  • FIG. 1 depicts Figure 5.7.5.1-1 from 3 GPP TS 38.331 V. 15.4.0, which illustrates the signaling flow for failure information.]
  • the purpose of this procedure is to inform the network about a failure detected by the UE.
  • a UE initiates the procedure when there is a need inform the network about a failure detected by the UE.
  • the UE initiates the procedure when the following condition is met:
  • the UE Upon initiating the procedure, the UE shall:
  • the UE shall:
  • the Failurelnformation message is used to inform the network about a failure detected by the UE.
  • Signalling radio bearer SRBl or SRB3
  • a UE can be configured with an SUL carrier in NR uplink either in a Non-StandAlone (NSA) or a StandAlone (SA) NR deployment scenario.
  • SUL the UE has at least two UL carriers (and only one DL) in the same cell and the network may decide to switch the UE over the two UL carriers using the LI signaling.
  • RLF happens to an RLC entity mapped to a PCell (i.e., on the MCG side)
  • RRC re-establishment procedure is triggered. This may also happen in the case of NR standalone.
  • the UE sends a report to the network (i.e., Failurelnformation message) and no RRC re-establishment is triggered.
  • the RRC re-establishment procedure is triggered. This results in additional signaling overhead and a longer service interruption time.
  • a method is proposed to prevent re-establishment and unnecessary signaling thereof in case of a detected Radio Link Failure (RLF) on the Primary Cell (PCell) (i.e., in case of New Radio-Dual Connectivity (NR-DC) and Standalone (SA)) when a user equipment (UE) is configured with Supplementary Uplink (SUL).
  • RLF Radio Link Failure
  • PCell Primary Cell
  • SA Standalone
  • UE user equipment
  • SUL Supplementary Uplink
  • a method is performed by a UE configured with an UL and a DL associated with a PCell and a SUL for communicating with a base station.
  • the method includes detecting a RLF on the PCell and transmitting, to a network node, a message comprising failure information associated with the RLF on the SUL.
  • a UE is configured with an UL and a DL associated with a PCell and a SUL for communicating with a base station.
  • the UE includes processing circuitry configured to detect a RLF on the PCell and transmitting, to a network node, a message comprising failure information associated with the RLF on the SUL.
  • a method is performed by a base station communicating with a UE configured with an UL and a DL associated with a PCell and a SUL.
  • the method includes receiving from the UE, on the SUL, a message comprising failure information associated with a RLF detected by the UE on the PCell.
  • a base station communicating with a UE configured with an UL and a DL associated with a PCell and a SUL includes processing circuitry configured to receive from the UE, on the SUL, a message comprising failure information associated with a RLF detected by the UE on the PCell.
  • Certain embodiments may provide one or more of the following technical advantages. For example, when Carrier Aggregation (CA) duplication with the SUL carrier is configured, upon an RLF over the PCell, an Radio Resource Control (RRC) re-establishment is typically called.
  • RRC Radio Resource Control
  • this procedure causes a considerable amount of service interruption time that cannot be tolerated, for example, when considering ultra-reliable and low-latency communication (URLLC) or even other delay-sensitive services with less stringent requirements than URLLC such as, for example, video call or video conferencing service.
  • URLLC ultra-reliable and low-latency communication
  • a technical advantage may be that certain embodiments avoid RRC re establishment procedure by sending a failure report over the SUL carrier when RLF has been detected on another carrier on which the PCell operates.
  • the UE may not be forced to trigger RRC re-establishment procedure and the network may decide, for example, to deactivate CA duplication, make the Secondary Cell (SCell), if not failed, the new PCell, or reconfigure the UE for handover over to a new cell or a new target gNB.
  • SCell Secondary Cell
  • Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.
  • FIGURE 1 illustrates Long-Term Evolution (LTE) and New Radio (NR) interworking options
  • FIGURE 2 illustrates the schematic control plane architecture for LTE Direct Connectivity (LTE DC) and Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity (EN-DC);
  • LTE DC LTE Direct Connectivity
  • EN-DC Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity
  • FIGURE 3 illustrates a user plane (UP) architecture for LTE-NR tight interworking
  • FIGURE 4 illustrates a control plane (CP) architecture for LTE-NR tight interworking
  • FIGURE 5 illustrates a supplementary uplink in EN-DC
  • FIGURE 6 depicts Figure 5.7.5.1-1 from 3GPP TS 38.331 V. 15.4.0, which illustrates the signaling flow for failure information;
  • FIGURE 7 illustrates the scenario where PCell fails and a wireless device, such as a UE, sends a failure report to a network node over the SUL, according to certain embodiments;
  • FIGURE 8 an example flowchart for reporting Radio Link Failure (RLF) over the SUL, according to certain embodiments
  • FIGURE 9 illustrates an example wireless network, according to certain embodiments.
  • FIGURE 10 illustrates an example network node, according to certain embodiments.
  • FIGURE 11 illustrates an example wireless device, according to certain embodiments.
  • FIGURE 12 illustrate an example user equipment, according to certain embodiments.
  • FIGURE 13 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments
  • FIGURE 14 illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments
  • FIGURE 15 illustrates a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments;
  • FIGURE 16 illustrates a method implemented in a communication system, according to one embodiment;
  • FIGURE 17 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 18 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 19 illustrates another method implemented in a communication system, according to one embodiment
  • FIGURE 20 illustrates an example method by a wireless device, according to certain embodiments
  • FIGURE 21 illustrates an exemplary virtual computing device, according to certain embodiments.
  • FIGURE 22 illustrates another example method by a wireless device, according to certain embodiments.
  • FIGURE 23 illustrates an exemplary virtual computing device, according to certain embodiments.
  • FIGURE 24 illustrates an example method by a network node, according to certain embodiments.
  • FIGURE 25 illustrates another exemplary virtual computing device, according to certain embodiments.
  • FIGURE 26 illustrates an example method by a network node, according to certain embodiments.
  • FIGURE 27 illustrates another exemplary virtual computing device, according to certain embodiments.
  • a more general term“network node” may be used and may correspond to any type of radio network node or any network node, which communicates with a UE (directly or via another node) and/or with another network node.
  • network nodes are NodeB, MeNB, ENB, a network node belonging to MCG or SCG, base station (BS), multi -standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MSC, MME, etc.), O&M, OSS, SON, positioning node (e.g. E-SMLC), MDT, test equipment (physical node or software), etc.
  • MSR multi -standard radio
  • RNC
  • the non-limiting term user equipment (UE) or wireless device may be used and may refer to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system.
  • UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, UE category Ml, UE category M2, ProSe UE, V2V UE, V2X UE, etc.
  • terminologies such as base station/gNodeB and UE should be considered non-limiting and do in particular not imply a certain hierarchical relation between the two; in general,“gNodeB” could be considered as device 1 and“UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And in the following the transmitter or receiver could be either gNB, or UE.
  • a method is proposed to prevent re-establishment and unnecessary signaling thereof in case of a detected Radio Link Failure (RLF) on the Primary Cell (PCell) (i.e., in case of New Radio-Dual Connectivity (NR-DC) and Standalone (SA) when UE is configured with Secondary Uplink (SUL).
  • RLF Radio Link Failure
  • PCell Primary Cell
  • SA Standalone
  • RRC Radio Resource Control
  • the UE may not be forced to trigger RRC re-establishment procedure and the network can decide, for example, to deactivate Carrier Aggregation (CA) duplication, make the Secondary Cell (SCell), if not failed, the new PCell, or reconfigure the UE for handover over a new cell or a new target gNode B (gNB).
  • CA Carrier Aggregation
  • SCell Secondary Cell
  • gNB gNode B
  • the UE may perform the random access procedure over the SUL carrier and sends a message such as a Failurelnformation message, for example, to the network, which may then take the necessary actions.
  • the UE may operate as follows, according to certain embodiments:
  • the UE will perform the contention-free random access to initiate the UL carrier switch.
  • UE will perform the contention-based random access to initiate the UL carrier switch. If the UL switch succeeds, then the UE sends a report to indicate the problem to the network, according to certain embodiments. Otherwise, the UE applies RRC re-establishment procedure.
  • the scenario that is targeted is when the UE has an UL and DL carrier, and SUL is configured.
  • the UE may not necessarily be operating in CA duplication. This it may refer to the standalone case or New Radio-Direct Connectivity (NR-DC) option where the Master Cell Group (MCG) is NR.
  • NR-DC New Radio-Direct Connectivity
  • MCG Master Cell Group
  • the UE may send the Failurelnformation message via the SUL carrier to the network, according to certain embodiments.
  • FIGURE 7 illustrates the scenario where PCell 120 fails and a wireless device 110, such as a UE, sends a failure report to a network node 160 over the SUL 140, according to certain embodiments. Upon receiving the failure report, the network may then take necessary action(s).
  • FIGURE 8 illustrates an example flowchart 200 for reporting RLF over the SUL, according to certain embodiments.
  • the UE detects an RLF over PCell.
  • the UE reports the RLF to the network via SUL.
  • the network sends the UE an RRC reconfiguration message to reconfigure the UE.
  • the UE continues communication with the network based on the new configuration received.
  • the triggers for RLF may be the same as the triggers defined in TS 3GPP 38.331 section 5.3.10.3, entitled Detection of radio link failure.
  • RLF may be detected upon the maximum number of Radio Link Control (RLC) retransmissions being reached.
  • RLC Radio Link Control
  • a radio link problem may be detected if the measured Reference Signal Received Power (RSRP) is too low (given a related threshold) or upon a failure to decode Physical Downlink Control Channel (PDCCH) / Physical Downlink Shared Channel (PDSCH) due to low power signal quality (e.g., low RSRP and/or Reference Signal Received Quality (RSRQ)).
  • RSRP Reference Signal Received Power
  • the radio link problem may be detected upon receiving N out of synch indications from the lower layers similar to RLF and Radio Link Monitoring (RLM) procedure in LTE or upon receiving indication from the Medium Access Control (MAC) that random access has failed.
  • RLM Radio Link Monitoring
  • the UE may perform the random access according to the SUL Random Access Channel (RACH) parameters, which may be broadcasted within the SIB1.
  • RACH SUL Random Access Channel
  • the UE may perform the contention-free random access to initiate the SUL carrier switch. If the UE has not been allocated with a contention-free resource, UE may perform the contention-based random access to initiate the SUL carrier switch.
  • the Failurelnf or motion message to be sent via the SUL carrier may be enhanced to include latest available measurements.
  • the Failurelnf or motion message may be enhanced by adding a failure cause that helps the network to understand what kind of failure has been detected.
  • the network upon receiving the Failurelnformation message, the network generates the RRC messages according to the RRC procedure decided and sends it via the SCell if this is still available.
  • RRC signaling messages could be simply an RRC reconfiguration message.
  • MR-DC Multi Radio-Dual Connectivity
  • NGEN-DC Next Generation Radio Access Technology Network-Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity
  • NE-DC New Radio-Evolved Universal Terrestrial Radio Access Network-Dual Connectivity
  • NR-DC New Radio-Dual Connectivity
  • the network upon receiving the Failurelnformation message the network generates the RRC messages and sends it via Split Radio Bearer (SRB) to the UE, in case UE is still reachable on one of the cell groups.
  • SRB Split Radio Bearer
  • MR-DC upon receiving the hailure Informal ion message the MN sends the RRC message via inter-node RRC messages to the SN that forward such a message to the UE via the SRB3.
  • the MN upon receiving the Failurelnformation message the MN send an indication to the SN by requesting a certain RRC procedure to be performed (e.g., handover, reconfiguration, or re-establishment).
  • the MN upon receiving the Failurelnformation message the MN forward such message to the SN (i.e., via inter-node RRC message) and the SN decides itself what actions to perform.
  • FIGURE 9 illustrates a wireless network, in accordance with some embodiments.
  • a wireless network such as the example wireless network illustrated in FIGURE 9.
  • the wireless network of FIGURE 9 only depicts network 306, network nodes 360 and 360b, and wireless devices 310, 310b, and 310c.
  • 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 360 and wireless device 310 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 306 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 360 and wireless device 310 comprise various components described in more detail below. These components work together in order 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.
  • FIGURE 10 illustrates an example network node 360, according to certain embodiments.
  • 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 360 includes processing circuitry 370, device readable medium 380, interface 390, auxiliary equipment 384, power source 386, power circuitry 387, and antenna 362.
  • network node 360 illustrated in the example wireless network of FIGURE 10 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 360 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 380 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 360 may be composed of multiple physically separate components (e.g., aNodeB component and aRNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node 360 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 360 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node 360 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 360, 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 360.
  • Processing circuitry 370 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 370 may include processing information obtained by processing circuitry 370 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 370 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 370 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 360 components, such as device readable medium 380, network node 360 functionality.
  • processing circuitry 370 may execute instructions stored in device readable medium 380 or in memory within processing circuitry 370. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 370 may include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry 370 may include one or more of radio frequency (RF) transceiver circuitry 372 and baseband processing circuitry 374.
  • radio frequency (RF) transceiver circuitry 372 and baseband processing circuitry 374 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 372 and baseband processing circuitry 374 may be on the same chip or set of chips, boards, or units.
  • processing circuitry 370 executing instructions stored on device readable medium 380 or memory within processing circuitry 370.
  • some or all of the functionality may be provided by processing circuitry 370 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 370 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 370 alone or to other components of network node 360 but are enjoyed by network node 360 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 380 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 370.
  • 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 380 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 370 and, utilized by network node 360.
  • Device readable medium 380 may be used to store any calculations made by processing circuitry 370 and/or any data received via interface 390.
  • processing circuitry 370 and device readable medium 380 may be considered to be integrated.
  • Interface 390 is used in the wired or wireless communication of signalling and/or data between network node 360, network 306, and/or wireless devices 310. As illustrated, interface 390 comprises port(s)/terminal(s) 394 to send and receive data, for example to and from network 306 over a wired connection. Interface 390 also includes radio front end circuitry 392 that may be coupled to, or in certain embodiments a part of, antenna 362. Radio front end circuitry 392 comprises filters 398 and amplifiers 396. Radio front end circuitry 392 may be connected to antenna 362 and processing circuitry 370. Radio front end circuitry may be configured to condition signals communicated between antenna 362 and processing circuitry 370.
  • Radio front end circuitry 392 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 392 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 398 and/or amplifiers 396. The radio signal may then be transmitted via antenna 362. Similarly, when receiving data, antenna 362 may collect radio signals which are then converted into digital data by radio front end circuitry 392. The digital data may be passed to processing circuitry 370. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • network node 360 may not include separate radio front end circuitry 392, instead, processing circuitry 370 may comprise radio front end circuitry and may be connected to antenna 362 without separate radio front end circuitry 392. Similarly, in some embodiments, all or some of RF transceiver circuitry 372 may be considered a part of interface 390. In still other embodiments, interface 390 may include one or more ports or terminals 394, radio front end circuitry 392, and RF transceiver circuitry 372, as part of a radio unit (not shown), and interface 390 may communicate with baseband processing circuitry 374, which is part of a digital unit (not shown).
  • Antenna 362 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 362 may be coupled to radio front end circuitry 390 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 362 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 362 may be separate from network node 360 and may be connectable to network node 360 through an interface or port.
  • Antenna 362, interface 390, and/or processing circuitry 370 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 362, interface 390, and/or processing circuitry 370 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 387 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 360 with power for performing the functionality described herein. Power circuitry 387 may receive power from power source 386. Power source 386 and/or power circuitry 387 may be configured to provide power to the various components of network node 360 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 386 may either be included in, or external to, power circuitry 387 and/or network node 360. For example, network node 360 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 387.
  • an external power source e.g., an electricity outlet
  • power source 386 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 387.
  • 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 360 may include additional components beyond those shown in FIGURE 10 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 360 may include user interface equipment to allow input of information into network node 360 and to allow output of information from network node 360. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 360.
  • FIGURE 11 illustrates an example wireless device 360, according to certain embodiments.
  • 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 wireless device 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 wireless device may be configured to transmit and/or receive information without direct human interaction.
  • a wireless device 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 wireless device 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
  • LME laptop-embedded equipment
  • LME laptop-mounted equipment
  • CPE wireless customer-premise equipment
  • a wireless device 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 wireless device 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 wireless device and/or a network node.
  • the wireless device 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 wireless device 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 wireless device 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 wireless device 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 wireless device 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 310 includes antenna 311, interface 314, processing circuitry 320, device readable medium 330, user interface equipment 332, auxiliary equipment 334, power source 336 and power circuitry 337.
  • Wireless device 310 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by wireless device 310, 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 wireless device 310.
  • Antenna 311 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 314. In certain alternative embodiments, antenna 311 may be separate from wireless device 310 and be connectable to wireless device 310 through an interface or port. Antenna 311, interface 314, and/or processing circuitry 320 may be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and/or signals may be received from a network node and/or another wireless device. In some embodiments, radio front end circuitry and/or antenna 311 may be considered an interface.
  • interface 314 comprises radio front end circuitry 312 and antenna 311.
  • Radio front end circuitry 312 comprise one or more filters 318 and amplifiers 316.
  • Radio front end circuitry 314 is connected to antenna 311 and processing circuitry 320 and is configured to condition signals communicated between antenna 311 and processing circuitry 320.
  • Radio front end circuitry 312 may be coupled to or a part of antenna 311.
  • wireless device 310 may not include separate radio front end circuitry 312; rather, processing circuitry 320 may comprise radio front end circuitry and may be connected to antenna 311.
  • some or all of RF transceiver circuitry 322 may be considered a part of interface 314.
  • Radio front end circuitry 312 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 312 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 318 and/or amplifiers 316. The radio signal may then be transmitted via antenna 311. Similarly, when receiving data, antenna 311 may collect radio signals which are then converted into digital data by radio front end circuitry 312. The digital data may be passed to processing circuitry 320. In other embodiments, the interface may comprise different components and/or different combinations of components.
  • Processing circuitry 320 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 wireless device 310 components, such as device readable medium 330, wireless device 310 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 320 may execute instructions stored in device readable medium 330 or in memory within processing circuitry 320 to provide the functionality disclosed herein.
  • processing circuitry 320 includes one or more of RF transceiver circuitry 322, baseband processing circuitry 324, and application processing circuitry 326.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry 320 of wireless device 310 may comprise a SOC.
  • RF transceiver circuitry 322, baseband processing circuitry 324, and application processing circuitry 326 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 324 and application processing circuitry 326 may be combined into one chip or set of chips, and RF transceiver circuitry 322 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 322 and baseband processing circuitry 324 may be on the same chip or set of chips, and application processing circuitry 326 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 322, baseband processing circuitry 324, and application processing circuitry 326 may be combined in the same chip or set of chips.
  • RF transceiver circuitry 322 may be a part of interface 314.
  • RF transceiver circuitry 322 may condition RF signals for processing circuitry 320.
  • processing circuitry 320 executing instructions stored on device readable medium 330, which in certain embodiments may be a computer-readable storage medium.
  • some or all of the functionality may be provided by processing circuitry 320 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 320 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 320 alone or to other components of wireless device 310, but are enjoyed by wireless device 310 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 320 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a wireless device. These operations, as performed by processing circuitry 320, may include processing information obtained by processing circuitry 320 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 310, 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 320 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 310, 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 330 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 320.
  • Device readable medium 330 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 320.
  • processing circuitry 320 and device readable medium 330 may be considered to be integrated.
  • User interface equipment 332 may provide components that allow for a human user to interact with wireless device 310. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 332 may be operable to produce output to the user and to allow the user to provide input to wireless device 310. The type of interaction may vary depending on the type of user interface equipment 332 installed in wireless device 310. For example, if wireless device 310 is a smart phone, the interaction may be via a touch screen; if wireless device 310 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 332 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 332 is configured to allow input of information into wireless device 310 and is connected to processing circuitry 320 to allow processing circuitry 320 to process the input information. User interface equipment 332 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 332 is also configured to allow output of information from wireless device 310, and to allow processing circuitry 320 to output information from wireless device 310. User interface equipment 332 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 332, wireless device 310 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.
  • Auxiliary equipment 334 is operable to provide more specific functionality which may not be generally performed by wireless devices. 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 334 may vary depending on the embodiment and/or scenario.
  • Power source 336 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.
  • Wireless device 310 may further comprise power circuitry 337 for delivering power from power source 336 to the various parts of wireless device 310 which need power from power source 336 to carry out any functionality described or indicated herein.
  • Power circuitry 337 may in certain embodiments comprise power management circuitry.
  • Power circuitry 337 may additionally or alternatively be operable to receive power from an external power source; in which case wireless device 310 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 337 may also in certain embodiments be operable to deliver power from an external power source to power source 336. This may be, for example, for the charging of power source 336. Power circuitry 337 may perform any formatting, converting, or other modification to the power from power source 336 to make the power suitable for the respective components of wireless device 310 to which power is supplied.
  • FIGURE 12 illustrates one embodiment of a UE in accordance with various aspects described 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 relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 400 may be any UE identified by the 3 rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 400 as illustrated in FIGURE 12, is one example of a wireless device configured for communication in accordance with one or more communication standards promulgated by the 3 rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards.
  • 3GPP 3 rd Generation Partnership Project
  • the term wireless device and UE may be used interchangeable. Accordingly, although FIGURE 12 is a UE, the components discussed herein are equally applicable to a wireless device, and vice- versa.
  • UE 400 includes processing circuitry 401 that is operatively coupled to input/output interface 405, radio frequency (RF) interface 409, network connection interface 411, memory 415 including random access memory (RAM) 417, read-only memory (ROM) 419, and storage medium 421 or the like, communication subsystem 431, power source 433, and/or any other component, or any combination thereof.
  • Storage medium 421 includes operating system 423, application program 425, and data 427. In other embodiments, storage medium 421 may include other similar types of information.
  • Certain UEs may utilize all of the components shown in FIGURE 12, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 401 may be configured to process computer instructions and data.
  • Processing circuitry 401 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 401 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface 405 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 400 may be configured to use an output device via input/output interface 405.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE 400.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE 400 may be configured to use an input device via input/output interface 405 to allow a user to capture information into UE 400.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence- sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 409 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 411 may be configured to provide a communication interface to network 443a.
  • Network 443a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 443a may comprise a Wi-Fi network.
  • Network connection interface 411 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface 411 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM 417 may be configured to interface via bus 402 to processing circuitry 401 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers.
  • ROM 419 may be configured to provide computer instructions or data to processing circuitry 401.
  • ROM 419 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium 421 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 421 may be configured to include operating system 423, application program 425 such as a web browser application, a widget or gadget engine or another application, and data file 427.
  • Storage medium 421 may store, for use by UE 400, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 421 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM synchronous dynamic random access memory
  • SIM/RUIM removable user identity
  • Storage medium 421 may allow UE 400 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 421, which may comprise a device readable medium.
  • processing circuitry 401 may be configured to communicate with network 443b using communication subsystem 431.
  • Network 443a and network 443b may be the same network or networks or different network or networks.
  • Communication subsystem 431 may be configured to include one or more transceivers used to communicate with network 443b.
  • communication subsystem 431 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another wireless device, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.4, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver may include transmitter 433 and/or receiver 435 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 433 and receiver 435 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem 431 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem 431 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network 443b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network 443b may be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 413 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 400.
  • communication subsystem 431 may be configured to include any of the components described herein.
  • processing circuitry 401 may be configured to communicate with any of such components over bus 402.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 401 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry 401 and communication subsystem 431.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIGURE 13 is a schematic block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a wireless device or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 500 hosted by one or more of hardware nodes 530. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications 520 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications 520 are run in virtualization environment 500 which provides hardware 530 comprising processing circuitry 560 and memory 590.
  • Memory 590 contains instructions 595 executable by processing circuitry 560 whereby application 520 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 500 comprises general-purpose or special-purpose network hardware devices 530 comprising a set of one or more processors or processing circuitry 560, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • processors or processing circuitry 560 which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors.
  • Each hardware device may comprise memory 590-1 which may be non-persistent memory for temporarily storing instructions 595 or software executed by processing circuitry 560.
  • Each hardware device may comprise one or more network interface controllers (NICs) 570, also known as network interface cards, which include physical network interface 580.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media 590-2 having stored therein software 595 and/or instructions executable by processing circuitry 560.
  • Software 595 may include any type of software including software for instantiating one or more virtualization layers 550 (also referred to as hypervisors), software to execute virtual machines 540 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 540 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 550 or hypervisor. Different embodiments of the instance of virtual appliance 520 may be implemented on one or more of virtual machines 540, and the implementations may be made in different ways.
  • processing circuitry 560 executes software 595 to instantiate the hypervisor or virtualization layer 550, which may sometimes be referred to as a virtual machine monitor (VMM).
  • Virtualization layer 550 may present a virtual operating platform that appears like networking hardware to virtual machine 540.
  • hardware 530 may be a standalone network node with generic or specific components.
  • Hardware 530 may comprise antenna 5225 and may implement some functions via virtualization.
  • hardware 530 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 5100, which, among others, oversees lifecycle management of applications 520.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV).
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine 540 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of virtual machines 540, and that part of hardware 530 that executes that virtual machine be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 540, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 5200 that each include one or more transmitters 5220 and one or more receivers 5210 may be coupled to one or more antennas 5225.
  • Radio units 5200 may communicate directly with hardware nodes 530 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • control system 5230 which may alternatively be used for communication between the hardware nodes 530 and radio units 5200.
  • FIGURE 14 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.
  • a communication system includes telecommunication network 610, such as a 3GPP-type cellular network, which comprises access network 611, such as a radio access network, and core network 614.
  • Access network 611 comprises a plurality of base stations 612a, 612b, 612c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 613a, 613b, 613c.
  • Each base station 612a, 612b, 612c is connectable to core network 614 over a wired or wireless connection 615.
  • a first UE 691 located in coverage area 613c is configured to wirelessly connect to, or be paged by, the corresponding base station 612c.
  • a second UE 692 in coverage area 613a is wirelessly connectable to the corresponding base station 612a. While a plurality of UEs 691, 692 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 612.
  • Telecommunication network 610 is itself connected to host computer 630, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer 630 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider.
  • Connections 621 and 622 between telecommunication network 610 and host computer 630 may extend directly from core network 614 to host computer 630 or may go via an optional intermediate network 620.
  • Intermediate network 620 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 620, if any, may be a backbone network or the Internet; in particular, intermediate network 620 may comprise two or more sub-networks (not shown).
  • the communication system of FIGURE 14 as a whole enables connectivity between the connected UEs 691, 692 and host computer 630.
  • the connectivity may be described as an over-the-top (OTT) connection 650.
  • Host computer 630 and the connected UEs 691, 692 are configured to communicate data and/or signaling via OTT connection 650, using access network 611, core network 614, any intermediate network 620 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 650 may be transparent in the sense that the participating communication devices through which OTT connection 650 passes are unaware of routing of uplink and downlink communications.
  • base station 612 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 630 to be forwarded (e.g., handed over) to a connected UE 691. Similarly, base station 612 need not be aware of the future routing of an outgoing uplink communication originating from the UE 691 towards the host computer 630.
  • FIGURE 15 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.
  • host computer 710 comprises hardware 715 including communication interface 716 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 700.
  • Host computer 710 further comprises processing circuitry 718, which may have storage and/or processing capabilities.
  • processing circuitry 718 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Host computer 710 further comprises software 711, which is stored in or accessible by host computer 710 and executable by processing circuitry 718.
  • Software 711 includes host application 712.
  • Host application 712 may be operable to provide a service to a remote user, such as UE 730 connecting via OTT connection 750 terminating at UE 730 and host computer 710. In providing the service to the remote user, host application 712 may provide user data which is transmitted using OTT connection 750.
  • Communication system 700 further includes base station 720 provided in a telecommunication system and comprising hardware 725 enabling it to communicate with host computer 710 and with UE 730.
  • Hardware 725 may include communication interface 726 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 700, as well as radio interface 727 for setting up and maintaining at least wireless connection 770 with UE 730 located in a coverage area (not shown in FIGURE 15) served by base station 720.
  • Communication interface 726 may be configured to facilitate connection 760 to host computer 710. Connection 760 may be direct or it may pass through a core network (not shown in FIGURE 15) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 725 of base station 720 further includes processing circuitry 728, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station 720 further has software 721 stored internally or accessible via an external connection.
  • Communication system 700 further includes UE 730 already referred to. Its hardware 735 may include radio interface 737 configured to set up and maintain wireless connection 770 with a base station serving a coverage area in which UE 730 is currently located. Hardware 735 of UE 730 further includes processing circuitry 738, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE 730 further comprises software 731, which is stored in or accessible by UE 730 and executable by processing circuitry 738.
  • Software 731 includes client application 732. Client application 732 may be operable to provide a service to a human or non-human user via UE 730, with the support of host computer 710.
  • an executing host application 712 may communicate with the executing client application 732 via OTT connection 750 terminating at UE 730 and host computer 710.
  • client application 732 may receive request data from host application 712 and provide user data in response to the request data.
  • OTT connection 750 may transfer both the request data and the user data.
  • Client application 732 may interact with the user to generate the user data that it provides.
  • host computer 710, base station 720 and UE 730 illustrated in FIGURE 15 may be similar or identical to host computer 630, one of base stations 612a, 612b, 612c and one of UEs 691, 692 of FIGURE 14, respectively.
  • the inner workings of these entities may be as shown in FIGURE 15 and independently, the surrounding network topology may be that of FIGURE 14.
  • OTT connection 750 has been drawn abstractly to illustrate the communication between host computer 710 and UE 730 via base station 720, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE 730 or from the service provider operating host computer 710, or both. While OTT connection 750 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection 770 between UE 730 and base station 720 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments improve the performance of OTT services provided to UE 730 using OTT connection 750, in which wireless connection 770 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and/or extended battery lifetime.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 750 may be implemented in software 711 and hardware 715 of host computer 710 or in software 731 and hardware 735 of UE 730, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 750 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or supplying values of other physical quantities from which software 711, 731 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 750 may include message format, retransmission settings, preferred routing etc. ; the reconfiguring need not affect base station 720, and it may be unknown or imperceptible to base station 720. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer 710’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software 711 and 731 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection 750 while it monitors propagation times, errors etc.
  • FIGURE 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 13 and 14. For simplicity of the present disclosure, only drawing references to FIGURE 16 will be included in this section.
  • the host computer provides user data.
  • substep 811 (which may be optional) of step 810, the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • step 830 the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 840 the UE executes a client application associated with the host application executed by the host computer.
  • FIGURE 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 13 and 14. For simplicity of the present disclosure, only drawing references to FIGURE 17 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 930 (which may be optional), the UE receives the user data carried in the transmission.
  • FIGURE 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 13 and 14. For simplicity of the present disclosure, only drawing references to FIGURE 18 will be included in this section.
  • step 1010 the UE receives input data provided by the host computer. Additionally or alternatively, in step 1020, the UE provides user data.
  • substep 1021 (which may be optional) of step 1020, the UE provides the user data by executing a client application.
  • substep 1011 (which may be optional) of step 1010, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in substep 1030 (which may be optional), transmission of the user data to the host computer.
  • step 1040 of the method the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIGURE 19 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 13 and 14. For simplicity of the present disclosure, only drawing references to FIGURE 19 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 1130 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • FIGURE 20 depicts a method 1200 by a wireless device 310, such as a UE, which is configured with a primary cell and an associated SUL for communicating with a base station.
  • the method begins at step 1202 when the wireless device 310 detects a RLF on the primary cell.
  • the wireless device transmits, to a network node 360, a RLF message on the SUL.
  • FIGURE 21 illustrates a schematic block diagram of a virtual apparatus 1300 in a wireless network (for example, the wireless network shown in FIGURE 9).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 310 or network node 360 shown in FIGURE 9).
  • Apparatus 1300 is operable to carry out the example method described with reference to FIGURE 20 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 20 is not necessarily carried out solely by apparatus 1300. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1300 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause detecting module 1310, transmitting module K20, and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.
  • detecting module 1310 may perform certain of the detecting functions of the apparatus 1300. For example, detecting module 1310 may detect detects a RLF on the primary cell.
  • transmitting module 1320 may perform certain of the transmitting functions of the apparatus 1300. For example, transmitting module 1320 may transmit, to a network node, a RLF message on the SUL.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • FIGURE 22 depicts a method 1400 by a wireless device 310 configured with an UL and a DL associated with a PCell and a SUL for communicating with a network node 360, according to certain embodiments.
  • the method begins at step 1402, when UE 400 detects a RLF on the PCell.
  • the UE 400 transmits, to the network node 360, a message comprising failure information associated with the RLF on the SUL.
  • the network node may include a base station and the wireless device may include a UE 400.
  • detecting the RLF includes detecting that a maximum number of RLC transmissions has been reached.
  • detecting the RLF includes receiving an indication from a medium access control, MAC, that random access has failed.
  • MAC medium access control
  • the UE 400 in response to detecting the RLF on the PCell and prior to transmitting the message comprising the failure information on the SUL, the UE 400 performs a random access procedure over the SUL to initiate a switch to the SUL.
  • the UE 400 in response to transmitting the message comprising the failure information on the SUL, receives a response message indicating to the UE to perform at least one of: deactivating carrier aggregation, CA, duplication; making the secondary cell a new primary cell; and initiating a handover to a new cell or a new target base station.
  • the response message is received on a secondary cell.
  • MC-DC is enabled, and the MC-DC may include at least one of: EN-DC, NGEN-DC, NE-DC, and NR-DC.
  • the response message is received via SRB from a MN and a SN, or the response message is received from the base station via signaling initiated by a SN.
  • the response message is received via RRC signaling.
  • the message including the failure information includes a result of at least one measurement performed by the UE.
  • the at least one measurement comprising at least one of a RSRP measurement and a RSRQ measurement.
  • the message including the failure information includes a failure cause.
  • FIGURE 23 illustrates a schematic block diagram of a virtual apparatus 1500 in a wireless network (for example, the wireless network shown in FIGURE 9).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 310 or network node 360 shown in FIGURE 9).
  • Apparatus 1500 is operable to carry out the example method described with reference to FIGURE 22 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 22 is not necessarily carried out solely by apparatus 1500. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause detecting module 1510, transmitting module 1520, and any other suitable units of apparatus 1500 to perform corresponding functions according one or more embodiments of the present disclosure.
  • detecting module 1510 may perform certain of the detecting functions of the apparatus 1500. For example, detecting module 1510 may detect a RLF on the PCell.
  • transmitting module 1520 may perform certain of the transmitting functions of the apparatus 1500. For example, transmitting module 1520 may transmit, to a network node 360, a message comprising failure information associated with the RLF on the SUL.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • FIGURE 24 depicts a method 1600 by a network node 360 such as a base station, which is communicating with a wireless device 310 such as a UE configured with a primary cell and an associated SUL.
  • the method begins at step 1602 when the network node receives, on the SUL, a RLF message from the wireless device.
  • the RLF message indicates a RLF detected by UE on the primary cell.
  • FIGURE 25 illustrates a schematic block diagram of a virtual apparatus 1700 in a wireless network (for example, the wireless network shown in FIGURE 9).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 310 or network node 360 shown in FIGURE 9).
  • Apparatus 1700 is operable to carry out the example method described with reference to FIGURE 24 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 24 is not necessarily carried out solely by apparatus 1700. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause receiving module 1710 and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.
  • receiving module 1710 may perform certain of the receiving functions of the apparatus 1700. For example, receiving module 1710 may receive, on the SUL, a RLF message from the wireless device. The RLF message indicates a RLF detected by UE on a primary cell.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • FIGURE 26 depicts a method 1800 by a network node 360, which is communicating with a wireless device 310 configured with an UL and a DL associated with a PCell and a SUL.
  • the method begins at step 1802 when the network node receives from the wireless device 310, on the SUL, a message comprising failure information associated with a RLF detected by the UE on the PCell.
  • the network node 360 may include a base station and the wireless device 110 may include a UE 400.
  • the network node configures the UE to detect the RLF when a maximum number of RLC transmissions has been reached.
  • the network node configures the UE to detect the RLF when an indication that random access has failed is received from a medium access control, MAC.
  • the network node prior to receiving the message comprising the failure information, receives at least one random access message over the SUL to initiate a switch of the UE to the SUL.
  • the network node in response to receiving the message comprising the failure information on the SUL, transmits a response message indicating to the UE to perform an action comprising at least one of: deactivating CA duplication; making the secondary cell a new primary cell; and initiating a handover to a new cell or a new target network node.
  • the message comprising the failure information includes a failure cause
  • the network node determines the action to be performed by the UE based on the failure cause.
  • the response message is transmitted on a secondary cell.
  • MC-DC is enabled, and the MC-DC may include at least one of: EN-DC, NGEN-DC, NE-DC, and NR-DC.
  • the response message is transmitted via split signal radio bearers, SRB, from a master node and a secondary node or the response message is transmitted from the network node via signaling initiated by a secondary node.
  • the response message is transmitted via radio resource control, RRC, signaling.
  • RRC radio resource control
  • the message comprising the failure information includes a result of at least one measurement performed by the UE.
  • the at least one measurement may include at least one of a Reference Signal Received Power, RSRP, measurement and a Reference Signal Received Quality, RSRQ, measurement.
  • FIGURE 27 illustrates a schematic block diagram of a virtual apparatus 1900 in a wireless network (for example, the wireless network shown in FIGURE 9).
  • the apparatus may be implemented in a wireless device or network node (e.g., wireless device 310 or network node 360 shown in FIGURE 9).
  • Apparatus 1900 is operable to carry out the example method described with reference to FIGURE 26 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 26 is not necessarily carried out solely by apparatus 1900. At least some operations of the method can be performed by one or more other entities.
  • Virtual Apparatus 1900 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc.
  • Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments.
  • the processing circuitry may be used to cause receiving module 1910 and any other suitable units of apparatus 1900 to perform corresponding functions according one or more embodiments of the present disclosure.
  • receiving module 1910 may perform certain of the receiving functions of the apparatus 1900.
  • receiving module 1910 may receive from a wireless device 310 such as a UE 400, which is configured with an UL and a DL associated with a PCell and a SUL, a message on the SUL.
  • the message includes failure information associated with a RLF detected by the UE on the PCell.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
  • Example Embodiment 1 A method performed by a user equipment (UE) configured with a primary cell and an associated secondary uplink (SUL) for communicating with a base station, the method comprising: detecting a radio link failure (RLF) on the primary cell; and transmitting, to a network node, a RLF message on the SUL.
  • UE user equipment
  • SUL secondary uplink
  • Example Embodiment 2 The method of Embodiment 1, wherein the UE is configured with a New Radio-dual connectivity (NR-DC) configuration and a master cell group (MCG) is New Radio (NR).
  • NR-DC New Radio-dual connectivity
  • MCG master cell group
  • NR New Radio
  • Example Embodiment 3 The method of Embodiment 1, wherein the UE is configured with a standalone configuration.
  • Example Embodiment 4 The method of any one of Embodiments 1 to 3, further comprising: in response to detecting the RLF on the primary cell and prior to transmitting the RLF message on the SUL, performing a radio access procedure over a carrier associated with the SUL to initiate a switch to the carrier associated with the SUL.
  • Example Embodiment 5 The method of Embodiment 4, further comprising receiving, from the base station, an indication of a contention-free random access resource, and wherein the random access procedure is performed using the contention-free random access resource.
  • Example Embodiment 6 The method of Embodiment 4, further comprising receiving, from the base station, an indication of a contention-based random access resource, and wherein the random access procedure is performed using the contention-based random access resource.
  • Example Embodiment 7 The method of any one of Embodiments 1 to 6, further comprising: in response to transmitting the RLF message on the SUL, receiving a response message, the response message identifying an action to be taken by the UE; and taking the action identified in the response message.
  • Example Embodiment 8 The method of Embodiment 7, wherein the action comprises at least one of: deactivating carrier aggregation (CA) duplication; making the secondary cell a new primary cell; and initiating a handover to a new cell or a new target base station.
  • CA carrier aggregation
  • Example Embodiment 9 The method of any one of Embodiments 7 to 8, wherein the response message is received on a secondary cell.
  • Example Embodiment 10 The method of any one of Embodiments 7 to 9, wherein the response message is received via radio resource control (RRC) signaling.
  • RRC radio resource control
  • Example Embodiment 11 The method of any one of Embodiments 7 to 10, wherein EN-DC, NGEN-DC, NE-DC, or NR-DC is enabled, and the response message is received via split signal radio bearers (SRB) from a master node and a secondary node.
  • SRB split signal radio bearers
  • Example Embodiment 12 The method of any one of Embodiments 7 to 10, wherein MR-DC is enabled, and the response message is received from the base station via RRC signaling forwarded from a secondary node that is different from the network node.
  • Example Embodiment 13 The method of any one of Embodiments 7 to 10, wherein MR-DC is enabled, and the response message is received via RRC signaling initiated by a secondary node.
  • Example Embodiment 14 The method of any one of Embodiments 1 to 13, wherein the RLF message is transmitted on the SUL instead of initiating a radio resource control (RRC) re-establishment procedure to reestablish the link associated with the RLF.
  • RRC radio resource control
  • Example Embodiment 15 The method of any one of Embodiments 1 to 14, wherein detecting the RLF on the primary cell comprises detecting a trigger and detecting the RLF in response to detecting the trigger.
  • Example Embodiment 16 The method of Embodiment 15, wherein the detecting the trigger comprises at least one of: detecting that a maximum number of RLC transmissions has been reached; determining that a measured reference signal resource power (RSRP) is below a threshold; detecting a failure to decode a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH) due to a lower power signal quality; receiving a number of indications from one or more lower layers; and receiving an indication from a medium access control (MAC) that random access has failed.
  • RSRP reference signal resource power
  • Example Embodiment 17 The method of any one of Embodiments 1 to 16, wherein the RLF message that is transmitted on the SUL comprises at least one measurement performed by the UE.
  • Example Embodiment 18 The method of any one of Embodiments 1 to 17, wherein the RLF message that is transmitted on the SUL comprises a failure cause.
  • Example Embodiment 19 A method performed by a base station communicating with a user equipment (UE) configured with a primary cell and an associated secondary uplink (SUL), the method comprising: receiving, on the SUL, a radio link failure (RLF) message from the UE, the RLF message indicating a RLF detected by UE on the primary cell.
  • UE user equipment
  • SUL secondary uplink
  • Example Embodiment 20 The method of Embodiment 19, wherein, prior to receiving the RLF message, the base station transmits to the UE, a New Radio-dual connectivity (NR- DC) configuration, and wherein a master cell group (MCG) is New Radio (NR).
  • NR- DC New Radio-dual connectivity
  • MCG master cell group
  • NR New Radio
  • Example Embodiment 21 The method of Embodiment 19, wherein, prior to receiving the RLF message, the base station transmits to the UE, a standalone configuration.
  • Example Embodiment 22 The method of any one of Embodiments 19 to 21, further comprising: prior to receiving, the RLF message, receiving at least one random access message over a carrier associated with the SUL to initiate a switch of the UE to the carrier associated with the SUL.
  • Example Embodiment 23 The method of Embodiment 22, further comprising transmitting, to the UE, an indication of a contention-free random access resource, and wherein the at least one random access message is received using the contention-free random access resource.
  • Example Embodiment 24 The method of Embodiment 22, further comprising transmitting, to the UE, an indication of a contention-free random access resource, and wherein the at least one random access message is received using the contention-based random access resource.
  • Example Embodiment 25 The method of any one of Embodiments 19 to 24, further comprising: in response to receiving the RLF message on the SUL, transmitting a response message.
  • Example Embodiment 26 The method of Embodiment 25, wherein the response message identifying an action to be taken by the UE, and wherein the action comprises at least one of: deactivating carrier aggregation (CA) duplication; making the secondary cell a new primary cell; and initiating a handover to a new cell or a new target network node.
  • CA carrier aggregation
  • Example Embodiment 27 The method of any one of Embodiments 25 to 26, wherein the response message is transmitted on a secondary cell.
  • Example Embodiment 28 The method of any one of Embodiments 25 to 27, wherein the response message is transmitted via radio resource control (RRC) signaling.
  • Example Embodiment 29 The method of any one of Embodiments 25 to 28 wherein EN-DC, NGEN-DC, NE-DC, or NR-DC is enabled, and the response message is transmitted via split signal radio bearers (SRB) from a master node and a secondary node.
  • RRC radio resource control
  • Example Embodiment 30 The method of any one of Embodiments 25 to 28, wherein MR-DC is enabled, wherein the response message indicates an action to be taken by the UE, and wherein the response message is transmitted from the base station to a secondary node for forwarding to the UE.
  • Example Embodiment 31 The method of any one of Embodiments 25 to 28, wherein MR-DC is enabled, and the response message is transmitted to a secondary node, and wherein the response message indicates that the secondary node is to determine the action to be taken by the UE.
  • Example Embodiment 32 The method of any one of Embodiments 19 to 31, wherein the RLF message is received on the SUL instead of the UE initiating a radio resource control (RRC) re-establishment procedure to reestablish the link associated with the RLF.
  • RRC radio resource control
  • Example Embodiment 33 The method of any one of Embodiments 19 to 32, further comprising configuring the UE to detect the RLF on the primary cell in response to detection of a trigger.
  • Example Embodiment 34 The method of Embodiment 33, wherein the trigger comprises at least one of: detecting that a maximum number of RLC transmissions has been reached; determining that a measured reference signal resource power (RSRP) is below a threshold; detecting a failure to decode a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH) due to a lower power signal quality; receiving a number of indications from one or more lower layers; and receiving an indication from a medium access control (MAC) that random access has failed.
  • RSRP reference signal resource power
  • Example Embodiment 35 The method of any one of Embodiments 19 to 34, wherein the RLF message that is received on the SUL comprises at least one measurement performed by the UE.
  • Example Embodiment 36 The method of any one of Embodiments 19 to 35, wherein the RLF message that is received on the SUL comprises a failure cause and wherein the base station identifies an action to be taken by the UE based on the failure cause.
  • Example Embodiment 37 A wireless device for improving network efficiency, the wireless device comprising: processing circuitry configured to perform any of the steps of Example Embodiments 1 to 18 and power supply circuitry configured to supply power to the wireless device.
  • Example Embodiment 38 A base station for improving network efficiency, the base station comprising: processing circuitry configured to perform any of the steps of Example Embodiments 19 to 36 and power supply circuitry configured to supply power to the wireless device.
  • Example Embodiment 39 A user equipment (UE) for improving network efficiency, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of Example Embodiments 1 to 18; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
  • UE user equipment
  • Example Embodiment 40 A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of Example Embodiments 19 to 36.
  • UE user equipment
  • Example Embodiment 41 The communication system of the pervious embodiment further including the base station.
  • Example Embodiment 42 The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
  • Example Embodiment 43 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • Example Embodiment 44 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of Example Embodiments 19 to 36.
  • UE user equipment
  • Example Embodiment 45 The method of the previous embodiment, further comprising, at the base station, transmitting the user data.
  • Example Embodiment 46 The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.
  • Example Embodiment 47 A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.
  • UE user equipment
  • Example Embodiment 48 A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of Example Embodiments 1 to 18.
  • a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of Example Embodiments 1 to 18.
  • UE user equipment
  • Example Embodiment 49 The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.
  • Example Embodiment 50 The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • Example Embodiment 51 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of Example Embodiments 1 to 18.
  • UE user equipment
  • Example Embodiment 52 The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.
  • Example Embodiment 53 A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of Example Embodiments 1 to 18.
  • UE user equipment
  • Example Embodiment 54 The communication system of the previous embodiment, further including the UE.
  • Example Embodiment 55 The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • Example Embodiment 56 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • Example Embodiment 57 The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • Example Embodiment 58 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of Example Embodiments 1 to 18.
  • UE user equipment
  • Example Embodiment 59 The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.
  • Example Embodiment 60 The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.
  • Example Embodiment 61 The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.
  • Example Embodiment 62 A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of Example Embodiments 19 to 36.
  • UE user equipment
  • Example Embodiment 63 The communication system of the previous embodiment further including the base station.
  • Example Embodiment 64 The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
  • Example Embodiment 65 The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • Example Embodiment 66 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of Example Embodiments 1 to 18.
  • UE user equipment
  • Example Embodiment 67 The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.
  • Example Embodiment 68 The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • gNB gNode B (a base station in NR; a Node B supporting NR and connectivity to NGC)

Landscapes

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

Abstract

A method is performed by a user equipment (UE) configured with an uplink, UL, and a downlink (DL) associated with a primary cell (PCell) and a supplementary uplink (SUL) for communicating with a network node. The method includes detecting a radio link failure (RLF) on the PCell and transmitting, to a network node, a message comprising failure information associated with the RLF on the SUL.

Description

RADIO LINK FAILURE RECOVERY OVER SUPPLEMENTARY UPLINK
TECHNICAL FIELD
The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for Radio Link Failure (RLF) recover over Supplementary Uplink (SUL).
BACKGROUND
FIGURE 1 illustrates LTE and NR interworking options. More specifically, as depicted in FIGURE 1, there are different ways to deploy 5G network with or without interworking with Long-Term Evolution (LTE), which may also be referred to as Evolved Universal Terrestrial Radio Access Network (E-UTRA) and evolved packet core (EPC). In principle, New Radio (NR) and LTE can be deployed without any interworking, denoted by NR stand-alone (SA) operation, that is gNode B (gNB) in NR can be connected to 5G core network (5GC) and eNode B (eNB) can be connected to EPC with no interconnection between the two (Option 1 and Option 2 in FIGURE 1).
On the other hand, the first supported version of NR is referred to as Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity (EN-DC) and is illustrated by Option 3 in FIGURE 1. In such a deployment, dual connectivity between NR and LTE is applied with LTE as the master and NR as the secondary node (SN). The Radio Access Network (RAN) node supporting NR such as, for example, a gNB, may not have a control plane connection to core network. Instead, the RAN node relies on the LTE as a master node (MN) or master eNB (MeNB). This is also called “Non-standalone NR." In this case, the functionality of an NR cell is limited and would be used for connected mode UEs as a booster and/or diversity leg but an RRC IDLE user equipment (UE) cannot camp on these NR cells.
With introduction of 5G Core (5GC), other options may be also valid. As mentioned above, option 2 supports stand-alone NR deployment where gNB is connected to 5GC. Similarly, LTE can also be connected to 5GC using option 5, which is also known as evolved LTE (eLTE), E-UTRA/5GC, or LTE/5GC, and the node can be referred to as an ng-eNB. In these cases, 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). It is worth noting that, Option 4 and Option 7 are other variants of dual connectivity between LTE and NR which will be standardized as part of NG-RAN connected to 5GC, denoted by Multi-Radio Dual Connectivity (MR-DC). Under the MR-DC umbrella, there is:
• EN-DC (Option 3): LTE is the MN and NR is the SN (EPC CN employed)
• New Radio-Evolved Universal Terrestrial Radio Access Network-Dual Connectivity (NE-DC) (Option 4): NR is the MN and LTE is the SN (5GCN employed)
• Next Generation Radio Access Technology Network-Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity (NGEN-DC) (Option 7): LTE is the MN and NR is the SN (5GCN employed)
• New Radio-Dual Connectivity (NR-DC) (variant of Option 2): Dual connectivity where both the MN and SN are NR (5GCN employed).
As migration for these options may differ for different operators, it is possible to have deployments with multiple options in parallel in the same network, For example, there could be an eNB base station supporting options 3, 5 and 7 in the same network as an NR base station supporting options 2 and 4. In combination with dual connectivity solutions between LTE and NR, it is also possible to support Carrier Aggregation (CA) in each cell group (i.e., master cell group (MCG) and secondary cell group (SCG)) and dual connectivity between nodes on a same RAT such as, for example, NR-NR DC. For the LTE cells, a consequence of these different deployments is the co-existence of LTE cells associated to eNBs connected to EPC, 5GC, or both EPC/5GC.
As discussed above, DC is standardized for both LTE and EN-DC. However, LTE DC and EN-DC are designed differently when it comes to which nodes control what. Basically, there are two options:
1. A centralized solution such as, for example, LTE-DC, or
2. A decentralized solution such as, for example, EN-DC.
FIGURE 2 illustrates the schematic control plane architecture for LTE DC and EN-DC. The main difference is that in EN-DC the SN has a separate Radio Resource Control (RR.C) entity, which may be referred to as a NR RR.C. This means that the SN can also control the UE. Sometimes the SN may control the UE without the knowledge of the MN. But, the SN often needs to coordinate with the MN. In LTE-DC, RR.C decisions always come from the MN (MN to UE). However, the SN still decides the configuration of the SN since it is only the SN itself that has knowledge of what kind of resources, capabilities, etc. the SN have. Two different DC specifications and their respective RRC messages are discussed below in more detail. FIGURE 2 illustrates the control plane architecture for Dual Connectivity (DC) in LTE DC and EN-DC.
LTE-NR DC (also referred to as LTE-NR tight interworking) is currently being discussed for Rel-15. In this context, the major changes from LTE DC are:
• the introduction of split bearer from the SN (known as secondary cell group (SCG) split bearer),
• the introduction of split bearer for RRC, and
• the introduction of a direct RRC from the SN (also referred to as SCG signaling radio bearer (SRB)).
FIGURES 3 and 4 show the User Plane (UP) and Control Plane (CP) architectures for LTE-NR tight interworking. Specifically, FIGURE 3 illustrates the UP architecture for LTE- NR tight interworking, and FIGURE 4 illustrates the CP architecture for LTE-NR tight interworking.
The SN is sometimes referred to as the SgNB, where the gNB is an NR base station. The MN may be referred to as the MeNB where LTE is the MN and NR is the SN. In the other case, where NR is the MN and LTE is the SN, the corresponding terms are MgNB and SeNB, respectively.
Split RRC messages are mainly used for creating diversity, and the sender can decide to either choose one of the links for scheduling the RRC messages, or it can duplicate the message over both links. In the downlink, the path switching between the MCG or SCG legs or the duplication on both is left to network implementation. On the other hand, for the UL, the network configures the UE to use the MCG, SCG or both legs. The terms“leg” and“path” are used interchangeably throughout this document.
In EN-DC, to improve the uplink coverage of the secondary node (NR) working on high frequencies, a supplementary uplink (SUL) can be configured. FIGURE 5 illustrates a supplementary uplink in EN-DC.
With the SUL, the UE is configured with two UL carriers and one DL carrier on the same cell. The switching between one carrier and another is controlled by the network through LI signaling. When a SUL is configured to a UE, it is an additional uplink only secondary cell (SCell) and the control of the SUL depends on a regular paired primary cell (PCell). Also, differently from CA, the UE is not allowed to use both carriers at the same time, and it is the network that indicates which carrier to use. For this case, usually the UE is configured with a contention free random access resource. Otherwise, if no indication is provided by the network, the UE performs a contention based random access procedure on the carrier (SUL or non-SUL) with the highest RSRP value.
When CA is configured, the UE only has one RRC connection with the network. Further, at RRC connection establishment/re-establishment/handover, one serving cell provides the Non-Access Stratum (NAS) mobility information, and at RRC connection re establishment/handover, one serving cell provides the security input. This cell is referred to as the Primary Cell (PCell). In addition, depending on UE capabilities, Secondary Cells (SCells) can be configured to form together with the PCell a set of serving cells. The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. Further, when dual connectivity is configured, it could be the case that one carrier under the SCG is used as the Primary SCell (PSCell). In this case, there is one PCell and one or more SCell(s) over the MCG and one PSCell and one or more SCell(s) over the SCG.
The reconfiguration, addition, and removal of SCells can be performed by RRC. At intra-RAT handover, RRC signaling can also be used to add, remove, or reconfigure SCells for usage with the target PCell. When adding a new SCell, dedicated RRC signalling is used for sending all required system information of the SCell. For example, while in connected mode, UEs need not acquire broadcasted system information directly from the SCells.
In LTE, a UE considers a radio link failure (RLF) to be detected in the following scenarios:
• upon detecting a certain number of out of sync indications from the lower layers associated with the PCell within a given time, or
• upon random access problem indication from Medium Access Control (MAC), or
• upon indication from RLC that the maximum number of retransmissions has been reached for an SRB or for a Data Radio Bearer (DRB) When 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 then 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.
In the case of LTE DC, the RLF detection procedure is similar to what was described above except that for (i) we are concerned only the PCell of the MN, the MAC in (ii) is the MCG MAC entity and the RLC in (iii) is the MCG RLC and the DRB in (iii) corresponds to MCG and MCG-split DRBs.
On the other hand, failure on the secondary side, known as SCGFailure, is detected by:
• upon detecting radio link failure for the SCG, in accordance with i, ii, and iii above (i.e. replace PCell for PSCell, MCG MAC for SCG MAC, and MCG/MCG-Split DRB for SCG DRB), or
• upon SCG change failure (i.e., not being able to finalize SCG change within a certain duration after the reception of an RRC connection reconfiguration message instructing the UE to do so), or
• upon stopping uplink transmission towards the PSCell due to exceeding the maximum uplink transmission timing difference when powerControlMode is configured to 1.
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 reconfigure 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 LTE-NR interworking (i.e. re-establishment in the case of RLF 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:
Upon SgNB failures, UE shall:
• suspend all SCG DRBs and suspend SCG transmission for MCG split DRBs, and SCG split DRBs;
• suspend direct SCG SRB and SCG transmission for MCG split SRB; • reset SCG-MAC;
• send the SCGFailurelnformation message to the MeNB with corresponding cause values.
Furthermore, in the RAN2 #99 meeting, the following agreements have been made for the user plane in case the RLF happens on the SCell when CA level duplication is employed:
• RLC reports maxNumberofRLC retransmissions are reached to RRC.
• For a logical channel restricted to one or multiple SCell(s) (i.e. logical channel configured for duplication) UE reports the failure to the gNB (e.g. SCell-RLF) but no RRC re-establishment happens
The procedures for NR radio link failure detection related actions, as discussed in 3GPP TS 38.331 V. 15.4.0, are shown below:
5.3.10 Radio link failure related actions
5.3.10.1 Detection of physical layer problems in RRC CONNECTED The UE shall:
1> upon receiving N310 consecutive "out-of-sync" indications for the SpCell from lower layers while neither T300, T301, T304, T319 not T311 is running:
2> start timer T310 for the corresponding SpCell.
5.3.10.2 Recovery of physical layer problems
Upon receiving N311 consecutive "in-sync" indications for the SpCell from lower layers while T310 is running, the UE shall:
1> stop timer T310 for the corresponding SpCell.
NOTE 1: In this case, the UE maintains the RRC connection without explicit signalling, i.e. the UE maintains the entire radio resource configuration.
NOTE 2: Periods in time where neither "in-sync" nor "out-of-sync" is reported by layer 1 do not affect the evaluation of the number of consecutive "in-sync" or "out-of-sync" indications.
5.3.10.3 Detection of radio link failure The UE shall:
1> upon T310 expiry in PCell; or
1> upon random access problem indication from MCG MAC while neither T300, T301, T304 nor T311 is running; or
1> upon indication from MCG RLC that the maximum number of retransmissions has been reached:
2> if CA duplication is configured and activated; and for the corresponding logical channel allowedServingCells only includes SCell(s):
3> initiate the failure information procedure as specified in 5.7.x to report RLC failure.
2> else:
3> consider radio link failure to be detected for the MCG i.e. RLF;
3> if AS security has not been activated:
4> perform the actions upon going to RRC IDLE as specified in 5.3.11, with release cause 'other';
3> else:
4> initiate the connection re-establishment procedure as specified in 5.3.7.
The UE shall:
1> upon T310 expiry in PSCell; or
1> upon random access problem indication from SCG MAC; or
1> upon indication from SCG RLC that the maximum number of retransmissions has been reached:
2> if CA duplication is configured and activated; and for the corresponding logical channel allowedServingCells only includes SCell(s):
3> initiate the failure information procedure as specified in 5.7.x to report RLC failure.
2> else:
3> consider radio link failure to be detected for the SCG i.e. SCG-RLF; 2> initiate the SCG failure information procedure as specified in 5.7.3 to report SCG radio link failure. 5.7.5 Failure information
5.7.5.1 General
[FIGURE 6 depicts Figure 5.7.5.1-1 from 3 GPP TS 38.331 V. 15.4.0, which illustrates the signaling flow for failure information.] The purpose of this procedure is to inform the network about a failure detected by the UE.
5.7.5.2 Initiation
A UE initiates the procedure when there is a need inform the network about a failure detected by the UE. In particular, the UE initiates the procedure when the following condition is met:
1> upon detecting failure for an RLC bearer, in accordance with 5.3.10;
Upon initiating the procedure, the UE shall:
1> initiate transmission of the Failurelnformation message as specified in 5.7.5.3;
5.7.5.3 Actions related to transmission of Failurelnformation message
The UE shall:
1> if initiated to provide RLC failure information:
2> set logicalChannelldentity to the logical channel identity of the failing RLC bearer;
2> set cellGroupIndication to the cell group of the failing RLC bearer;
2> set failureType to the type of failure that was detected;
1> if used to inform the network about a failure for an MCG RLC bearer:
2> submit the Failurelnformation message to lower layers for transmission via SRB1;
1> else if used to inform the network about a failure for an SCG RLC bearer: and if the UE is configured with EN-DC:
2> if SRB3 is configured:
3> submit the Failurelnformation message to lower layers for transmission via SRB3; 2> else:
3> submit the Failurelnformation message via the EUTRA MCG embedded in E-UTRA RRC message
ULInformationTransferMRDC as specified in TS 36.331 [10]
- Failurelnformation
The Failurelnformation message is used to inform the network about a failure detected by the UE.
Signalling radio bearer: SRBl or SRB3
RLC-SAP: AM
Logical channel: DCCH
Direction: UE to network
Failurelnformation message
- ASN1 START
- T AG-F AILUREINF ORMATION - ST ART
Failurelnformation ::= SEQUENCE {
criticalExtensions CHOICE {
failurelnformation Failurelnformation-IEs,
criticalExtensionsFuture SEQUENCE {}
}
}
Failurelnformation-IEs ::= SEQUENCE {
failurelnfoRLC-Bearer FailurelnfoRLC-Bearer OPTIONAL lateNonCriticalExtension OCTET STRING OPTIONAL,
nonCriticalExtension SEQUENCE {} OPTIONAL
}
FailurelnfoRLC-Bearer ::= SEQUENCE {
cellGroupId CellGroupId, logicalChannelldentity Logical Channelldentity,
failureType ENUMERATED {duplication, spare3, spare2, spare 1 }
}
- T AG-F AILUREINF ORMATION - STOP
- ASN1STOP
Certain problems exist. For example, a UE can be configured with an SUL carrier in NR uplink either in a Non-StandAlone (NSA) or a StandAlone (SA) NR deployment scenario. In case of SUL, the UE has at least two UL carriers (and only one DL) in the same cell and the network may decide to switch the UE over the two UL carriers using the LI signaling.
When an RLF is experienced on one of the carriers where CA duplication is activated, different actions are performed based on whether the RLF has been performed on the SCell or on the PCell/PSCell. In particular:
• If the RLF happens to an RLC entity mapped to a PCell (i.e., on the MCG side), RRC re-establishment procedure is triggered. This may also happen in the case of NR standalone.
• If the RLF happens to an RLC entity mapped to a PSCell (i.e., on the SCG side), the SCGFailurelnformation procedure is used and the RLF is reported to the MCG and no RRC re-establishment is triggered.
• If the RLF happens to an RLC entity mapped to an SCell (i.e., regardless if is on the MCG or SCG side), the UE sends a report to the network (i.e., Failurelnformation message) and no RRC re-establishment is triggered.
Thus, according to the first case (i.e., RLF on the PCell), the RRC re-establishment procedure is triggered. This results in additional signaling overhead and a longer service interruption time.
SUMMARY
Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, according to certain embodiments, a method is proposed to prevent re-establishment and unnecessary signaling thereof in case of a detected Radio Link Failure (RLF) on the Primary Cell (PCell) (i.e., in case of New Radio-Dual Connectivity (NR-DC) and Standalone (SA)) when a user equipment (UE) is configured with Supplementary Uplink (SUL).
According to certain embodiments, a method is performed by a UE configured with an UL and a DL associated with a PCell and a SUL for communicating with a base station. The method includes detecting a RLF on the PCell and transmitting, to a network node, a message comprising failure information associated with the RLF on the SUL.
According to certain embodiments, a UE is configured with an UL and a DL associated with a PCell and a SUL for communicating with a base station. The UE includes processing circuitry configured to detect a RLF on the PCell and transmitting, to a network node, a message comprising failure information associated with the RLF on the SUL.
According to certain embodiments, a method is performed by a base station communicating with a UE configured with an UL and a DL associated with a PCell and a SUL. The method includes receiving from the UE, on the SUL, a message comprising failure information associated with a RLF detected by the UE on the PCell.
According to certain embodiments, a base station communicating with a UE configured with an UL and a DL associated with a PCell and a SUL includes processing circuitry configured to receive from the UE, on the SUL, a message comprising failure information associated with a RLF detected by the UE on the PCell.
Certain embodiments may provide one or more of the following technical advantages. For example, when Carrier Aggregation (CA) duplication with the SUL carrier is configured, upon an RLF over the PCell, an Radio Resource Control (RRC) re-establishment is typically called. However, this procedure causes a considerable amount of service interruption time that cannot be tolerated, for example, when considering ultra-reliable and low-latency communication (URLLC) or even other delay-sensitive services with less stringent requirements than URLLC such as, for example, video call or video conferencing service. As disclosed herein, a technical advantage may be that certain embodiments avoid RRC re establishment procedure by sending a failure report over the SUL carrier when RLF has been detected on another carrier on which the PCell operates. In this way, the UE may not be forced to trigger RRC re-establishment procedure and the network may decide, for example, to deactivate CA duplication, make the Secondary Cell (SCell), if not failed, the new PCell, or reconfigure the UE for handover over to a new cell or a new target gNB. Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.
BRIEF DESCRIPTION OF THE DRAWINGS
For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:
FIGURE 1 illustrates Long-Term Evolution (LTE) and New Radio (NR) interworking options;
FIGURE 2 illustrates the schematic control plane architecture for LTE Direct Connectivity (LTE DC) and Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity (EN-DC);
FIGURE 3 illustrates a user plane (UP) architecture for LTE-NR tight interworking;
FIGURE 4 illustrates a control plane (CP) architecture for LTE-NR tight interworking;
FIGURE 5 illustrates a supplementary uplink in EN-DC;
FIGURE 6 depicts Figure 5.7.5.1-1 from 3GPP TS 38.331 V. 15.4.0, which illustrates the signaling flow for failure information;
FIGURE 7 illustrates the scenario where PCell fails and a wireless device, such as a UE, sends a failure report to a network node over the SUL, according to certain embodiments;
FIGURE 8 an example flowchart for reporting Radio Link Failure (RLF) over the SUL, according to certain embodiments;
FIGURE 9 illustrates an example wireless network, according to certain embodiments;
FIGURE 10 illustrates an example network node, according to certain embodiments;
FIGURE 11 illustrates an example wireless device, according to certain embodiments;
FIGURE 12 illustrate an example user equipment, according to certain embodiments;
FIGURE 13 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments;
FIGURE 14 illustrates a telecommunication network connected via an intermediate network to a host computer, according to certain embodiments;
FIGURE 15 illustrates a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to certain embodiments; FIGURE 16 illustrates a method implemented in a communication system, according to one embodiment;
FIGURE 17 illustrates another method implemented in a communication system, according to one embodiment;
FIGURE 18 illustrates another method implemented in a communication system, according to one embodiment;
FIGURE 19 illustrates another method implemented in a communication system, according to one embodiment;
FIGURE 20 illustrates an example method by a wireless device, according to certain embodiments;
FIGURE 21 illustrates an exemplary virtual computing device, according to certain embodiments;
FIGURE 22 illustrates another example method by a wireless device, according to certain embodiments;
FIGURE 23 illustrates an exemplary virtual computing device, according to certain embodiments;
FIGURE 24 illustrates an example method by a network node, according to certain embodiments;
FIGURE 25 illustrates another exemplary virtual computing device, according to certain embodiments;
FIGURE 26 illustrates an example method by a network node, according to certain embodiments; and
FIGURE 27 illustrates another exemplary virtual computing device, according to certain embodiments.
DETAILED DESCRIPTION
Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only 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.
Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.
In some embodiments, a more general term“network node” may be used and may correspond to any type of radio network node or any network node, which communicates with a UE (directly or via another node) and/or with another network node. Examples of network nodes are NodeB, MeNB, ENB, a network node belonging to MCG or SCG, base station (BS), multi -standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MSC, MME, etc.), O&M, OSS, SON, positioning node (e.g. E-SMLC), MDT, test equipment (physical node or software), etc.
In some embodiments, the non-limiting term user equipment (UE) or wireless device may be used and may refer to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, PDA, PAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, UE category Ml, UE category M2, ProSe UE, V2V UE, V2X UE, etc.
Additionally, terminologies such as base station/gNodeB and UE should be considered non-limiting and do in particular not imply a certain hierarchical relation between the two; in general,“gNodeB” could be considered as device 1 and“UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And in the following the transmitter or receiver could be either gNB, or UE.
According to certain embodiments, a method is proposed to prevent re-establishment and unnecessary signaling thereof in case of a detected Radio Link Failure (RLF) on the Primary Cell (PCell) (i.e., in case of New Radio-Dual Connectivity (NR-DC) and Standalone (SA) when UE is configured with Secondary Uplink (SUL). Specifically, for example, an Radio Resource Control (RRC) re-establishment procedure is avoided by sending a failure report over the SUL carrier when RLF has been detected on the PCell. In this way, the UE may not be forced to trigger RRC re-establishment procedure and the network can decide, for example, to deactivate Carrier Aggregation (CA) duplication, make the Secondary Cell (SCell), if not failed, the new PCell, or reconfigure the UE for handover over a new cell or a new target gNode B (gNB).
According to certain embodiments, when the RLF is detected on the PCell and SUL is configured, the UE may perform the random access procedure over the SUL carrier and sends a message such as a Failurelnformation message, for example, to the network, which may then take the necessary actions.
Regarding the random access procedure, the UE may operate as follows, according to certain embodiments:
• If the UE has been allocated with contention-free random access resource in SIB1, the UE will perform the contention-free random access to initiate the UL carrier switch.
• If the UE has not been allocated with a contention-free resource, UE will perform the contention-based random access to initiate the UL carrier switch. If the UL switch succeeds, then the UE sends a report to indicate the problem to the network, according to certain embodiments. Otherwise, the UE applies RRC re-establishment procedure.
Thus, the scenario that is targeted is when the UE has an UL and DL carrier, and SUL is configured. The UE may not necessarily be operating in CA duplication. This it may refer to the standalone case or New Radio-Direct Connectivity (NR-DC) option where the Master Cell Group (MCG) is NR. In such a case, if an RLF is detected on the PCell, the UE may send the Failurelnformation message via the SUL carrier to the network, according to certain embodiments. FIGURE 7 illustrates the scenario where PCell 120 fails and a wireless device 110, such as a UE, sends a failure report to a network node 160 over the SUL 140, according to certain embodiments. Upon receiving the failure report, the network may then take necessary action(s).
FIGURE 8 illustrates an example flowchart 200 for reporting RLF over the SUL, according to certain embodiments. As depicted in FIGURE 8, in a first step 202, the UE detects an RLF over PCell. In a second step 204, the UE reports the RLF to the network via SUL. In a third step 206, the network sends the UE an RRC reconfiguration message to reconfigure the UE. In a fourth step 208, the UE continues communication with the network based on the new configuration received.
In particular embodiments, the triggers for RLF may be the same as the triggers defined in TS 3GPP 38.331 section 5.3.10.3, entitled Detection of radio link failure. For example, RLF may be detected upon the maximum number of Radio Link Control (RLC) retransmissions being reached. As another example, a radio link problem may be detected if the measured Reference Signal Received Power (RSRP) is too low (given a related threshold) or upon a failure to decode Physical Downlink Control Channel (PDCCH) / Physical Downlink Shared Channel (PDSCH) due to low power signal quality (e.g., low RSRP and/or Reference Signal Received Quality (RSRQ)). Further, the radio link problem may be detected upon receiving N out of synch indications from the lower layers similar to RLF and Radio Link Monitoring (RLM) procedure in LTE or upon receiving indication from the Medium Access Control (MAC) that random access has failed.
In a particular embodiment, before sending the failure information over the SUL carrier, the UE may perform the random access according to the SUL Random Access Channel (RACH) parameters, which may be broadcasted within the SIB1. In particular, if the UE has been allocated with a contention-free random access resource, the UE may perform the contention-free random access to initiate the SUL carrier switch. If the UE has not been allocated with a contention-free resource, UE may perform the contention-based random access to initiate the SUL carrier switch.
According to certain embodiments, the Failurelnf or motion message to be sent via the SUL carrier may be enhanced to include latest available measurements. In another embodiment, the Failurelnf or motion message may be enhanced by adding a failure cause that helps the network to understand what kind of failure has been detected.
In a particular embodiment, upon receiving the Failurelnformation message, the network generates the RRC messages according to the RRC procedure decided and sends it via the SCell if this is still available. Here, RRC signaling messages could be simply an RRC reconfiguration message.
In another embodiment, if any of the existing Multi Radio-Dual Connectivity (MR-DC) options are enabled such as, for example, EN-DC, Next Generation Radio Access Technology Network-Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity (NGEN-DC), New Radio-Evolved Universal Terrestrial Radio Access Network-Dual Connectivity (NE-DC), or New Radio-Dual Connectivity (NR-DC), upon receiving the Failurelnformation message the network generates the RRC messages and sends it via Split Radio Bearer (SRB) to the UE, in case UE is still reachable on one of the cell groups. In an alternative embodiment, if MR-DC is enabled, upon receiving the hailure Informal ion message the MN sends the RRC message via inter-node RRC messages to the SN that forward such a message to the UE via the SRB3. Yet, in another embodiment, if MR-DC is enabled, upon receiving the Failurelnformation message the MN send an indication to the SN by requesting a certain RRC procedure to be performed (e.g., handover, reconfiguration, or re-establishment). In another embodiment, if MR-DC is enabled, upon receiving the Failurelnformation message the MN forward such message to the SN (i.e., via inter-node RRC message) and the SN decides itself what actions to perform.
FIGURE 9 illustrates a wireless network, in accordance with some embodiments. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIGURE 9. For simplicity, the wireless network of FIGURE 9 only depicts network 306, network nodes 360 and 360b, and wireless devices 310, 310b, and 310c. In practice, 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. Of the illustrated components, network node 360 and wireless device 310 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. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, 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.
Network 306 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.
Network node 360 and wireless device 310 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, 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.
FIGURE 10 illustrates an example network node 360, according to certain embodiments. As used herein, 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. 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, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). 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. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of 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. As another example, anetwork node may be a virtual network node as described in more detail below. More generally, however, 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.
In FIGURE 10, network node 360 includes processing circuitry 370, device readable medium 380, interface 390, auxiliary equipment 384, power source 386, power circuitry 387, and antenna 362. Although network node 360 illustrated in the example wireless network of FIGURE 10 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. Moreover, while the components of network node 360 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 380 may comprise multiple separate hard drives as well as multiple RAM modules).
Similarly, network node 360 may be composed of multiple physically separate components (e.g., aNodeB component and aRNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 360 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 360 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 380 for the different RATs) and some components may be reused (e.g., the same antenna 362 may be shared by the RATs). Network node 360 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 360, 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 360.
Processing circuitry 370 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 370 may include processing information obtained by processing circuitry 370 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 370 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 360 components, such as device readable medium 380, network node 360 functionality. For example, processing circuitry 370 may execute instructions stored in device readable medium 380 or in memory within processing circuitry 370. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 370 may include a system on a chip (SOC).
In some embodiments, processing circuitry 370 may include one or more of radio frequency (RF) transceiver circuitry 372 and baseband processing circuitry 374. In some embodiments, radio frequency (RF) transceiver circuitry 372 and baseband processing circuitry 374 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 372 and baseband processing circuitry 374 may be on the same chip or set of chips, boards, or units.
In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 370 executing instructions stored on device readable medium 380 or memory within processing circuitry 370. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 370 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 370 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 370 alone or to other components of network node 360 but are enjoyed by network node 360 as a whole, and/or by end users and the wireless network generally.
Device readable medium 380 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 370. Device readable medium 380 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 370 and, utilized by network node 360. Device readable medium 380 may be used to store any calculations made by processing circuitry 370 and/or any data received via interface 390. In some embodiments, processing circuitry 370 and device readable medium 380 may be considered to be integrated.
Interface 390 is used in the wired or wireless communication of signalling and/or data between network node 360, network 306, and/or wireless devices 310. As illustrated, interface 390 comprises port(s)/terminal(s) 394 to send and receive data, for example to and from network 306 over a wired connection. Interface 390 also includes radio front end circuitry 392 that may be coupled to, or in certain embodiments a part of, antenna 362. Radio front end circuitry 392 comprises filters 398 and amplifiers 396. Radio front end circuitry 392 may be connected to antenna 362 and processing circuitry 370. Radio front end circuitry may be configured to condition signals communicated between antenna 362 and processing circuitry 370. Radio front end circuitry 392 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 392 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 398 and/or amplifiers 396. The radio signal may then be transmitted via antenna 362. Similarly, when receiving data, antenna 362 may collect radio signals which are then converted into digital data by radio front end circuitry 392. The digital data may be passed to processing circuitry 370. In other embodiments, the interface may comprise different components and/or different combinations of components.
In certain alternative embodiments, network node 360 may not include separate radio front end circuitry 392, instead, processing circuitry 370 may comprise radio front end circuitry and may be connected to antenna 362 without separate radio front end circuitry 392. Similarly, in some embodiments, all or some of RF transceiver circuitry 372 may be considered a part of interface 390. In still other embodiments, interface 390 may include one or more ports or terminals 394, radio front end circuitry 392, and RF transceiver circuitry 372, as part of a radio unit (not shown), and interface 390 may communicate with baseband processing circuitry 374, which is part of a digital unit (not shown).
Antenna 362 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 362 may be coupled to radio front end circuitry 390 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 362 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 362 may be separate from network node 360 and may be connectable to network node 360 through an interface or port.
Antenna 362, interface 390, and/or processing circuitry 370 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 362, interface 390, and/or processing circuitry 370 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 387 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 360 with power for performing the functionality described herein. Power circuitry 387 may receive power from power source 386. Power source 386 and/or power circuitry 387 may be configured to provide power to the various components of network node 360 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 386 may either be included in, or external to, power circuitry 387 and/or network node 360. For example, network node 360 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 387. As a further example, power source 386 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 387. 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.
Alternative embodiments of network node 360 may include additional components beyond those shown in FIGURE 10 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. For example, network node 360 may include user interface equipment to allow input of information into network node 360 and to allow output of information from network node 360. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 360.
FIGURE 11 illustrates an example wireless device 360, according to certain embodiments. As used herein, wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term wireless device 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. In some embodiments, a wireless device may be configured to transmit and/or receive information without direct human interaction. For instance, a wireless device 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 wireless device 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. A wireless device 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. As yet another specific example, in an Internet of Things (IoT) scenario, a wireless device 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 wireless device and/or a network node. The wireless device may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the wireless device may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such 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.). In other scenarios, a wireless device 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 wireless device 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 wireless device as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
As illustrated, wireless device 310 includes antenna 311, interface 314, processing circuitry 320, device readable medium 330, user interface equipment 332, auxiliary equipment 334, power source 336 and power circuitry 337. Wireless device 310 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by wireless device 310, 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 wireless device 310.
Antenna 311 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 314. In certain alternative embodiments, antenna 311 may be separate from wireless device 310 and be connectable to wireless device 310 through an interface or port. Antenna 311, interface 314, and/or processing circuitry 320 may be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and/or signals may be received from a network node and/or another wireless device. In some embodiments, radio front end circuitry and/or antenna 311 may be considered an interface.
As illustrated, interface 314 comprises radio front end circuitry 312 and antenna 311. Radio front end circuitry 312 comprise one or more filters 318 and amplifiers 316. Radio front end circuitry 314 is connected to antenna 311 and processing circuitry 320 and is configured to condition signals communicated between antenna 311 and processing circuitry 320. Radio front end circuitry 312 may be coupled to or a part of antenna 311. In some embodiments, wireless device 310 may not include separate radio front end circuitry 312; rather, processing circuitry 320 may comprise radio front end circuitry and may be connected to antenna 311. Similarly, in some embodiments, some or all of RF transceiver circuitry 322 may be considered a part of interface 314. Radio front end circuitry 312 may receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 312 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 318 and/or amplifiers 316. The radio signal may then be transmitted via antenna 311. Similarly, when receiving data, antenna 311 may collect radio signals which are then converted into digital data by radio front end circuitry 312. The digital data may be passed to processing circuitry 320. In other embodiments, the interface may comprise different components and/or different combinations of components.
Processing circuitry 320 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 wireless device 310 components, such as device readable medium 330, wireless device 310 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 320 may execute instructions stored in device readable medium 330 or in memory within processing circuitry 320 to provide the functionality disclosed herein.
As illustrated, processing circuitry 320 includes one or more of RF transceiver circuitry 322, baseband processing circuitry 324, and application processing circuitry 326. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 320 of wireless device 310 may comprise a SOC. In some embodiments, RF transceiver circuitry 322, baseband processing circuitry 324, and application processing circuitry 326 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 324 and application processing circuitry 326 may be combined into one chip or set of chips, and RF transceiver circuitry 322 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 322 and baseband processing circuitry 324 may be on the same chip or set of chips, and application processing circuitry 326 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 322, baseband processing circuitry 324, and application processing circuitry 326 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 322 may be a part of interface 314. RF transceiver circuitry 322 may condition RF signals for processing circuitry 320.
In certain embodiments, some or all of the functionality described herein as being performed by a wireless device may be provided by processing circuitry 320 executing instructions stored on device readable medium 330, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 320 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 320 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 320 alone or to other components of wireless device 310, but are enjoyed by wireless device 310 as a whole, and/or by end users and the wireless network generally.
Processing circuitry 320 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a wireless device. These operations, as performed by processing circuitry 320, may include processing information obtained by processing circuitry 320 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 310, 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 330 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 320. Device readable medium 330 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 320. In some embodiments, processing circuitry 320 and device readable medium 330 may be considered to be integrated.
User interface equipment 332 may provide components that allow for a human user to interact with wireless device 310. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 332 may be operable to produce output to the user and to allow the user to provide input to wireless device 310. The type of interaction may vary depending on the type of user interface equipment 332 installed in wireless device 310. For example, if wireless device 310 is a smart phone, the interaction may be via a touch screen; if wireless device 310 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). User interface equipment 332 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 332 is configured to allow input of information into wireless device 310 and is connected to processing circuitry 320 to allow processing circuitry 320 to process the input information. User interface equipment 332 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 332 is also configured to allow output of information from wireless device 310, and to allow processing circuitry 320 to output information from wireless device 310. User interface equipment 332 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 332, wireless device 310 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein.
Auxiliary equipment 334 is operable to provide more specific functionality which may not be generally performed by wireless devices. 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 334 may vary depending on the embodiment and/or scenario.
Power source 336 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. Wireless device 310 may further comprise power circuitry 337 for delivering power from power source 336 to the various parts of wireless device 310 which need power from power source 336 to carry out any functionality described or indicated herein. Power circuitry 337 may in certain embodiments comprise power management circuitry. Power circuitry 337 may additionally or alternatively be operable to receive power from an external power source; in which case wireless device 310 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 337 may also in certain embodiments be operable to deliver power from an external power source to power source 336. This may be, for example, for the charging of power source 336. Power circuitry 337 may perform any formatting, converting, or other modification to the power from power source 336 to make the power suitable for the respective components of wireless device 310 to which power is supplied.
FIGURE 12 illustrates one embodiment of a UE in accordance with various aspects described herein. 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 relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which 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 for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 400 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 400, as illustrated in FIGURE 12, is one example of a wireless device configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term wireless device and UE may be used interchangeable. Accordingly, although FIGURE 12 is a UE, the components discussed herein are equally applicable to a wireless device, and vice- versa.
In FIGURE 12, UE 400 includes processing circuitry 401 that is operatively coupled to input/output interface 405, radio frequency (RF) interface 409, network connection interface 411, memory 415 including random access memory (RAM) 417, read-only memory (ROM) 419, and storage medium 421 or the like, communication subsystem 431, power source 433, and/or any other component, or any combination thereof. Storage medium 421 includes operating system 423, application program 425, and data 427. In other embodiments, storage medium 421 may include other similar types of information. Certain UEs may utilize all of the components shown in FIGURE 12, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
In FIGURE 12, processing circuitry 401 may be configured to process computer instructions and data. Processing circuitry 401 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 401 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
In the depicted embodiment, input/output interface 405 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 400 may be configured to use an output device via input/output interface 405. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 400. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 400 may be configured to use an input device via input/output interface 405 to allow a user to capture information into UE 400. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence- sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
In FIGURE 12, RF interface 409 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 411 may be configured to provide a communication interface to network 443a. Network 443a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 443a may comprise a Wi-Fi network. Network connection interface 411 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 411 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
RAM 417 may be configured to interface via bus 402 to processing circuitry 401 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 419 may be configured to provide computer instructions or data to processing circuitry 401. For example, ROM 419 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 421 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 421 may be configured to include operating system 423, application program 425 such as a web browser application, a widget or gadget engine or another application, and data file 427. Storage medium 421 may store, for use by UE 400, any of a variety of various operating systems or combinations of operating systems.
Storage medium 421 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 421 may allow UE 400 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 421, which may comprise a device readable medium.
In FIGURE 12, processing circuitry 401 may be configured to communicate with network 443b using communication subsystem 431. Network 443a and network 443b may be the same network or networks or different network or networks. Communication subsystem 431 may be configured to include one or more transceivers used to communicate with network 443b. For example, communication subsystem 431 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another wireless device, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.4, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 433 and/or receiver 435 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 433 and receiver 435 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
In the illustrated embodiment, the communication functions of communication subsystem 431 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 431 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 443b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 443b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 413 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 400.
The features, benefits and/or functions described herein may be implemented in one of the components of UE 400 or partitioned across multiple components of UE 400. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 431 may be configured to include any of the components described herein. Further, processing circuitry 401 may be configured to communicate with any of such components over bus 402. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 401 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 401 and communication subsystem 431. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
FIGURE 13 is a schematic block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 500 hosted by one or more of hardware nodes 530. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
The functions may be implemented by one or more applications 520 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 520 are run in virtualization environment 500 which provides hardware 530 comprising processing circuitry 560 and memory 590. Memory 590 contains instructions 595 executable by processing circuitry 560 whereby application 520 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
Virtualization environment 500, comprises general-purpose or special-purpose network hardware devices 530 comprising a set of one or more processors or processing circuitry 560, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 590-1 which may be non-persistent memory for temporarily storing instructions 595 or software executed by processing circuitry 560. Each hardware device may comprise one or more network interface controllers (NICs) 570, also known as network interface cards, which include physical network interface 580. Each hardware device may also include non-transitory, persistent, machine-readable storage media 590-2 having stored therein software 595 and/or instructions executable by processing circuitry 560. Software 595 may include any type of software including software for instantiating one or more virtualization layers 550 (also referred to as hypervisors), software to execute virtual machines 540 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
Virtual machines 540, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 550 or hypervisor. Different embodiments of the instance of virtual appliance 520 may be implemented on one or more of virtual machines 540, and the implementations may be made in different ways.
During operation, processing circuitry 560 executes software 595 to instantiate the hypervisor or virtualization layer 550, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 550 may present a virtual operating platform that appears like networking hardware to virtual machine 540.
As shown in FIGURE 13, hardware 530 may be a standalone network node with generic or specific components. Hardware 530 may comprise antenna 5225 and may implement some functions via virtualization. Alternatively, hardware 530 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 5100, which, among others, oversees lifecycle management of applications 520. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
In the context of NFV, virtual machine 540 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 540, and that part of hardware 530 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 540, forms a separate virtual network elements (VNE).
Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 540 on top of hardware networking infrastructure 530 and corresponds to application 520 in FIGURE 13.
In some embodiments, one or more radio units 5200 that each include one or more transmitters 5220 and one or more receivers 5210 may be coupled to one or more antennas 5225. Radio units 5200 may communicate directly with hardware nodes 530 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
In some embodiments, some signaling can be affected with the use of control system 5230 which may alternatively be used for communication between the hardware nodes 530 and radio units 5200.
FIGURE 14 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.
With reference to FIGURE 14, in accordance with an embodiment, a communication system includes telecommunication network 610, such as a 3GPP-type cellular network, which comprises access network 611, such as a radio access network, and core network 614. Access network 611 comprises a plurality of base stations 612a, 612b, 612c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 613a, 613b, 613c. Each base station 612a, 612b, 612c is connectable to core network 614 over a wired or wireless connection 615. A first UE 691 located in coverage area 613c is configured to wirelessly connect to, or be paged by, the corresponding base station 612c. A second UE 692 in coverage area 613a is wirelessly connectable to the corresponding base station 612a. While a plurality of UEs 691, 692 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 612.
Telecommunication network 610 is itself connected to host computer 630, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 630 may be under the ownership or control of a service provider or may be operated by the service provider or on behalf of the service provider. Connections 621 and 622 between telecommunication network 610 and host computer 630 may extend directly from core network 614 to host computer 630 or may go via an optional intermediate network 620. Intermediate network 620 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 620, if any, may be a backbone network or the Internet; in particular, intermediate network 620 may comprise two or more sub-networks (not shown).
The communication system of FIGURE 14 as a whole enables connectivity between the connected UEs 691, 692 and host computer 630. The connectivity may be described as an over-the-top (OTT) connection 650. Host computer 630 and the connected UEs 691, 692 are configured to communicate data and/or signaling via OTT connection 650, using access network 611, core network 614, any intermediate network 620 and possible further infrastructure (not shown) as intermediaries. OTT connection 650 may be transparent in the sense that the participating communication devices through which OTT connection 650 passes are unaware of routing of uplink and downlink communications. For example, base station 612 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 630 to be forwarded (e.g., handed over) to a connected UE 691. Similarly, base station 612 need not be aware of the future routing of an outgoing uplink communication originating from the UE 691 towards the host computer 630.
FIGURE 15 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.
Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIGURE 15. In communication system 700, host computer 710 comprises hardware 715 including communication interface 716 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 700. Host computer 710 further comprises processing circuitry 718, which may have storage and/or processing capabilities. In particular, processing circuitry 718 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 710 further comprises software 711, which is stored in or accessible by host computer 710 and executable by processing circuitry 718. Software 711 includes host application 712. Host application 712 may be operable to provide a service to a remote user, such as UE 730 connecting via OTT connection 750 terminating at UE 730 and host computer 710. In providing the service to the remote user, host application 712 may provide user data which is transmitted using OTT connection 750.
Communication system 700 further includes base station 720 provided in a telecommunication system and comprising hardware 725 enabling it to communicate with host computer 710 and with UE 730. Hardware 725 may include communication interface 726 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 700, as well as radio interface 727 for setting up and maintaining at least wireless connection 770 with UE 730 located in a coverage area (not shown in FIGURE 15) served by base station 720. Communication interface 726 may be configured to facilitate connection 760 to host computer 710. Connection 760 may be direct or it may pass through a core network (not shown in FIGURE 15) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 725 of base station 720 further includes processing circuitry 728, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 720 further has software 721 stored internally or accessible via an external connection.
Communication system 700 further includes UE 730 already referred to. Its hardware 735 may include radio interface 737 configured to set up and maintain wireless connection 770 with a base station serving a coverage area in which UE 730 is currently located. Hardware 735 of UE 730 further includes processing circuitry 738, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 730 further comprises software 731, which is stored in or accessible by UE 730 and executable by processing circuitry 738. Software 731 includes client application 732. Client application 732 may be operable to provide a service to a human or non-human user via UE 730, with the support of host computer 710. In host computer 710, an executing host application 712 may communicate with the executing client application 732 via OTT connection 750 terminating at UE 730 and host computer 710. In providing the service to the user, client application 732 may receive request data from host application 712 and provide user data in response to the request data. OTT connection 750 may transfer both the request data and the user data. Client application 732 may interact with the user to generate the user data that it provides.
It is noted that host computer 710, base station 720 and UE 730 illustrated in FIGURE 15 may be similar or identical to host computer 630, one of base stations 612a, 612b, 612c and one of UEs 691, 692 of FIGURE 14, respectively. This is to say, the inner workings of these entities may be as shown in FIGURE 15 and independently, the surrounding network topology may be that of FIGURE 14.
In FIGURE 15, OTT connection 750 has been drawn abstractly to illustrate the communication between host computer 710 and UE 730 via base station 720, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 730 or from the service provider operating host computer 710, or both. While OTT connection 750 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
Wireless connection 770 between UE 730 and base station 720 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 730 using OTT connection 750, in which wireless connection 770 forms the last segment. More precisely, the teachings of these embodiments may improve the data rate, latency, and/or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, and/or extended battery lifetime.
A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 750 between host computer 710 and UE 730, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 750 may be implemented in software 711 and hardware 715 of host computer 710 or in software 731 and hardware 735 of UE 730, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 750 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or supplying values of other physical quantities from which software 711, 731 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 750 may include message format, retransmission settings, preferred routing etc. ; the reconfiguring need not affect base station 720, and it may be unknown or imperceptible to base station 720. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 710’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 711 and 731 causes messages to be transmitted, in particular empty or‘dummy’ messages, using OTT connection 750 while it monitors propagation times, errors etc.
FIGURE 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 13 and 14. For simplicity of the present disclosure, only drawing references to FIGURE 16 will be included in this section. In step 810, the host computer provides user data. In substep 811 (which may be optional) of step 810, the host computer provides the user data by executing a host application. In step 820, the host computer initiates a transmission carrying the user data to the UE. In step 830 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 840 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.
FIGURE 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 13 and 14. For simplicity of the present disclosure, only drawing references to FIGURE 17 will be included in this section. In step 910 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 920, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 930 (which may be optional), the UE receives the user data carried in the transmission.
FIGURE 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 13 and 14. For simplicity of the present disclosure, only drawing references to FIGURE 18 will be included in this section. In step 1010 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1020, the UE provides user data. In substep 1021 (which may be optional) of step 1020, the UE provides the user data by executing a client application. In substep 1011 (which may be optional) of step 1010, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 1030 (which may be optional), transmission of the user data to the host computer. In step 1040 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
FIGURE 19 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGURES 13 and 14. For simplicity of the present disclosure, only drawing references to FIGURE 19 will be included in this section. In step 1110 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1120 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1130 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station. FIGURE 20 depicts a method 1200 by a wireless device 310, such as a UE, which is configured with a primary cell and an associated SUL for communicating with a base station. The method begins at step 1202 when the wireless device 310 detects a RLF on the primary cell. At step 1204, the wireless device transmits, to a network node 360, a RLF message on the SUL.
FIGURE 21 illustrates a schematic block diagram of a virtual apparatus 1300 in a wireless network (for example, the wireless network shown in FIGURE 9). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 310 or network node 360 shown in FIGURE 9). Apparatus 1300 is operable to carry out the example method described with reference to FIGURE 20 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 20 is not necessarily carried out solely by apparatus 1300. At least some operations of the method can be performed by one or more other entities.
Virtual Apparatus 1300 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause detecting module 1310, transmitting module K20, and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.
According to certain embodiments, detecting module 1310 may perform certain of the detecting functions of the apparatus 1300. For example, detecting module 1310 may detect detects a RLF on the primary cell.
According to certain embodiments, transmitting module 1320 may perform certain of the transmitting functions of the apparatus 1300. For example, transmitting module 1320 may transmit, to a network node, a RLF message on the SUL. The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
FIGURE 22 depicts a method 1400 by a wireless device 310 configured with an UL and a DL associated with a PCell and a SUL for communicating with a network node 360, according to certain embodiments. The method begins at step 1402, when UE 400 detects a RLF on the PCell. At step 1404, the UE 400 transmits, to the network node 360, a message comprising failure information associated with the RLF on the SUL. In particular embodiments, the network node may include a base station and the wireless device may include a UE 400.
In a particular embodiment, detecting the RLF includes detecting that a maximum number of RLC transmissions has been reached.
In a particular embodiment, detecting the RLF includes receiving an indication from a medium access control, MAC, that random access has failed.
In a particular embodiment, in response to detecting the RLF on the PCell and prior to transmitting the message comprising the failure information on the SUL, the UE 400 performs a random access procedure over the SUL to initiate a switch to the SUL.
In a particular embodiment, in response to transmitting the message comprising the failure information on the SUL, the UE 400 receives a response message indicating to the UE to perform at least one of: deactivating carrier aggregation, CA, duplication; making the secondary cell a new primary cell; and initiating a handover to a new cell or a new target base station.
In a particular embodiment, the response message is received on a secondary cell.
In a particular embodiment, MC-DC is enabled, and the MC-DC may include at least one of: EN-DC, NGEN-DC, NE-DC, and NR-DC.
In a particular embodiment, the response message is received via SRB from a MN and a SN, or the response message is received from the base station via signaling initiated by a SN.
In a particular embodiment, the response message is received via RRC signaling. In a particular embodiment, the message including the failure information includes a result of at least one measurement performed by the UE. The at least one measurement comprising at least one of a RSRP measurement and a RSRQ measurement.
In a particular embodiment, the message including the failure information includes a failure cause.
FIGURE 23 illustrates a schematic block diagram of a virtual apparatus 1500 in a wireless network (for example, the wireless network shown in FIGURE 9). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 310 or network node 360 shown in FIGURE 9). Apparatus 1500 is operable to carry out the example method described with reference to FIGURE 22 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 22 is not necessarily carried out solely by apparatus 1500. At least some operations of the method can be performed by one or more other entities.
Virtual Apparatus 1500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause detecting module 1510, transmitting module 1520, and any other suitable units of apparatus 1500 to perform corresponding functions according one or more embodiments of the present disclosure.
According to certain embodiments, detecting module 1510 may perform certain of the detecting functions of the apparatus 1500. For example, detecting module 1510 may detect a RLF on the PCell.
According to certain embodiments, transmitting module 1520 may perform certain of the transmitting functions of the apparatus 1500. For example, transmitting module 1520 may transmit, to a network node 360, a message comprising failure information associated with the RLF on the SUL. The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
FIGURE 24 depicts a method 1600 by a network node 360 such as a base station, which is communicating with a wireless device 310 such as a UE configured with a primary cell and an associated SUL. The method begins at step 1602 when the network node receives, on the SUL, a RLF message from the wireless device. The RLF message indicates a RLF detected by UE on the primary cell.
FIGURE 25 illustrates a schematic block diagram of a virtual apparatus 1700 in a wireless network (for example, the wireless network shown in FIGURE 9). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 310 or network node 360 shown in FIGURE 9). Apparatus 1700 is operable to carry out the example method described with reference to FIGURE 24 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 24 is not necessarily carried out solely by apparatus 1700. At least some operations of the method can be performed by one or more other entities.
Virtual Apparatus 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 1710 and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.
According to certain embodiments, receiving module 1710 may perform certain of the receiving functions of the apparatus 1700. For example, receiving module 1710 may receive, on the SUL, a RLF message from the wireless device. The RLF message indicates a RLF detected by UE on a primary cell.
The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
FIGURE 26 depicts a method 1800 by a network node 360, which is communicating with a wireless device 310 configured with an UL and a DL associated with a PCell and a SUL. The method begins at step 1802 when the network node receives from the wireless device 310, on the SUL, a message comprising failure information associated with a RLF detected by the UE on the PCell. In particular embodiments, the network node 360 may include a base station and the wireless device 110 may include a UE 400.
In a particular embodiment, the network node configures the UE to detect the RLF when a maximum number of RLC transmissions has been reached.
In a particular embodiment, the network node configures the UE to detect the RLF when an indication that random access has failed is received from a medium access control, MAC. In a particular embodiment, prior to receiving the message comprising the failure information, the network node receives at least one random access message over the SUL to initiate a switch of the UE to the SUL.
In a particular embodiment, in response to receiving the message comprising the failure information on the SUL, the network node transmits a response message indicating to the UE to perform an action comprising at least one of: deactivating CA duplication; making the secondary cell a new primary cell; and initiating a handover to a new cell or a new target network node.
In a particular embodiment, the message comprising the failure information includes a failure cause, and the network node determines the action to be performed by the UE based on the failure cause.
In a particular embodiment, the response message is transmitted on a secondary cell.
In a particular embodiment, MC-DC is enabled, and the MC-DC may include at least one of: EN-DC, NGEN-DC, NE-DC, and NR-DC. In a particular embodiment, the response message is transmitted via split signal radio bearers, SRB, from a master node and a secondary node or the response message is transmitted from the network node via signaling initiated by a secondary node.
In a particular embodiment, the response message is transmitted via radio resource control, RRC, signaling.
In a particular embodiment, the message comprising the failure information includes a result of at least one measurement performed by the UE. The at least one measurement may include at least one of a Reference Signal Received Power, RSRP, measurement and a Reference Signal Received Quality, RSRQ, measurement.
FIGURE 27 illustrates a schematic block diagram of a virtual apparatus 1900 in a wireless network (for example, the wireless network shown in FIGURE 9). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 310 or network node 360 shown in FIGURE 9). Apparatus 1900 is operable to carry out the example method described with reference to FIGURE 26 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 26 is not necessarily carried out solely by apparatus 1900. At least some operations of the method can be performed by one or more other entities.
Virtual Apparatus 1900 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 1910 and any other suitable units of apparatus 1900 to perform corresponding functions according one or more embodiments of the present disclosure.
According to certain embodiments, receiving module 1910 may perform certain of the receiving functions of the apparatus 1900. For example, receiving module 1910 may receive from a wireless device 310 such as a UE 400, which is configured with an UL and a DL associated with a PCell and a SUL, a message on the SUL. The message includes failure information associated with a RLF detected by the UE on the PCell.
The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.
EXAMPLE EMBODIMENTS
Example Embodiment 1. A method performed by a user equipment (UE) configured with a primary cell and an associated secondary uplink (SUL) for communicating with a base station, the method comprising: detecting a radio link failure (RLF) on the primary cell; and transmitting, to a network node, a RLF message on the SUL.
Example Embodiment 2. The method of Embodiment 1, wherein the UE is configured with a New Radio-dual connectivity (NR-DC) configuration and a master cell group (MCG) is New Radio (NR).
Example Embodiment 3. The method of Embodiment 1, wherein the UE is configured with a standalone configuration.
Example Embodiment 4. The method of any one of Embodiments 1 to 3, further comprising: in response to detecting the RLF on the primary cell and prior to transmitting the RLF message on the SUL, performing a radio access procedure over a carrier associated with the SUL to initiate a switch to the carrier associated with the SUL.
Example Embodiment 5. The method of Embodiment 4, further comprising receiving, from the base station, an indication of a contention-free random access resource, and wherein the random access procedure is performed using the contention-free random access resource.
Example Embodiment 6. The method of Embodiment 4, further comprising receiving, from the base station, an indication of a contention-based random access resource, and wherein the random access procedure is performed using the contention-based random access resource.
Example Embodiment 7. The method of any one of Embodiments 1 to 6, further comprising: in response to transmitting the RLF message on the SUL, receiving a response message, the response message identifying an action to be taken by the UE; and taking the action identified in the response message.
Example Embodiment 8. The method of Embodiment 7, wherein the action comprises at least one of: deactivating carrier aggregation (CA) duplication; making the secondary cell a new primary cell; and initiating a handover to a new cell or a new target base station.
Example Embodiment 9. The method of any one of Embodiments 7 to 8, wherein the response message is received on a secondary cell. Example Embodiment 10. The method of any one of Embodiments 7 to 9, wherein the response message is received via radio resource control (RRC) signaling.
Example Embodiment 11. The method of any one of Embodiments 7 to 10, wherein EN-DC, NGEN-DC, NE-DC, or NR-DC is enabled, and the response message is received via split signal radio bearers (SRB) from a master node and a secondary node.
Example Embodiment 12. The method of any one of Embodiments 7 to 10, wherein MR-DC is enabled, and the response message is received from the base station via RRC signaling forwarded from a secondary node that is different from the network node.
Example Embodiment 13. The method of any one of Embodiments 7 to 10, wherein MR-DC is enabled, and the response message is received via RRC signaling initiated by a secondary node.
Example Embodiment 14. The method of any one of Embodiments 1 to 13, wherein the RLF message is transmitted on the SUL instead of initiating a radio resource control (RRC) re-establishment procedure to reestablish the link associated with the RLF.
Example Embodiment 15. The method of any one of Embodiments 1 to 14, wherein detecting the RLF on the primary cell comprises detecting a trigger and detecting the RLF in response to detecting the trigger.
Example Embodiment 16. The method of Embodiment 15, wherein the detecting the trigger comprises at least one of: detecting that a maximum number of RLC transmissions has been reached; determining that a measured reference signal resource power (RSRP) is below a threshold; detecting a failure to decode a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH) due to a lower power signal quality; receiving a number of indications from one or more lower layers; and receiving an indication from a medium access control (MAC) that random access has failed.
Example Embodiment 17. The method of any one of Embodiments 1 to 16, wherein the RLF message that is transmitted on the SUL comprises at least one measurement performed by the UE.
Example Embodiment 18. The method of any one of Embodiments 1 to 17, wherein the RLF message that is transmitted on the SUL comprises a failure cause.
Example Embodiment 19. A method performed by a base station communicating with a user equipment (UE) configured with a primary cell and an associated secondary uplink (SUL), the method comprising: receiving, on the SUL, a radio link failure (RLF) message from the UE, the RLF message indicating a RLF detected by UE on the primary cell.
Example Embodiment 20. The method of Embodiment 19, wherein, prior to receiving the RLF message, the base station transmits to the UE, a New Radio-dual connectivity (NR- DC) configuration, and wherein a master cell group (MCG) is New Radio (NR).
Example Embodiment 21. The method of Embodiment 19, wherein, prior to receiving the RLF message, the base station transmits to the UE, a standalone configuration.
Example Embodiment 22. The method of any one of Embodiments 19 to 21, further comprising: prior to receiving, the RLF message, receiving at least one random access message over a carrier associated with the SUL to initiate a switch of the UE to the carrier associated with the SUL.
Example Embodiment 23. The method of Embodiment 22, further comprising transmitting, to the UE, an indication of a contention-free random access resource, and wherein the at least one random access message is received using the contention-free random access resource.
Example Embodiment 24. The method of Embodiment 22, further comprising transmitting, to the UE, an indication of a contention-free random access resource, and wherein the at least one random access message is received using the contention-based random access resource.
Example Embodiment 25. The method of any one of Embodiments 19 to 24, further comprising: in response to receiving the RLF message on the SUL, transmitting a response message.
Example Embodiment 26. The method of Embodiment 25, wherein the response message identifying an action to be taken by the UE, and wherein the action comprises at least one of: deactivating carrier aggregation (CA) duplication; making the secondary cell a new primary cell; and initiating a handover to a new cell or a new target network node.
Example Embodiment 27. The method of any one of Embodiments 25 to 26, wherein the response message is transmitted on a secondary cell.
Example Embodiment 28. The method of any one of Embodiments 25 to 27, wherein the response message is transmitted via radio resource control (RRC) signaling. Example Embodiment 29. The method of any one of Embodiments 25 to 28 wherein EN-DC, NGEN-DC, NE-DC, or NR-DC is enabled, and the response message is transmitted via split signal radio bearers (SRB) from a master node and a secondary node.
Example Embodiment 30. The method of any one of Embodiments 25 to 28, wherein MR-DC is enabled, wherein the response message indicates an action to be taken by the UE, and wherein the response message is transmitted from the base station to a secondary node for forwarding to the UE.
Example Embodiment 31. The method of any one of Embodiments 25 to 28, wherein MR-DC is enabled, and the response message is transmitted to a secondary node, and wherein the response message indicates that the secondary node is to determine the action to be taken by the UE.
Example Embodiment 32. The method of any one of Embodiments 19 to 31, wherein the RLF message is received on the SUL instead of the UE initiating a radio resource control (RRC) re-establishment procedure to reestablish the link associated with the RLF.
Example Embodiment 33. The method of any one of Embodiments 19 to 32, further comprising configuring the UE to detect the RLF on the primary cell in response to detection of a trigger.
Example Embodiment 34. The method of Embodiment 33, wherein the trigger comprises at least one of: detecting that a maximum number of RLC transmissions has been reached; determining that a measured reference signal resource power (RSRP) is below a threshold; detecting a failure to decode a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH) due to a lower power signal quality; receiving a number of indications from one or more lower layers; and receiving an indication from a medium access control (MAC) that random access has failed.
Example Embodiment 35. The method of any one of Embodiments 19 to 34, wherein the RLF message that is received on the SUL comprises at least one measurement performed by the UE.
Example Embodiment 36. The method of any one of Embodiments 19 to 35, wherein the RLF message that is received on the SUL comprises a failure cause and wherein the base station identifies an action to be taken by the UE based on the failure cause.
Example Embodiment 37. A wireless device for improving network efficiency, the wireless device comprising: processing circuitry configured to perform any of the steps of Example Embodiments 1 to 18 and power supply circuitry configured to supply power to the wireless device.
Example Embodiment 38. A base station for improving network efficiency, the base station comprising: processing circuitry configured to perform any of the steps of Example Embodiments 19 to 36 and power supply circuitry configured to supply power to the wireless device.
Example Embodiment 39. A user equipment (UE) for improving network efficiency, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of Example Embodiments 1 to 18; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.
Example Embodiment 40. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of Example Embodiments 19 to 36.
Example Embodiment 41. The communication system of the pervious embodiment further including the base station.
Example Embodiment 42. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
Example Embodiment 43. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application. Example Embodiment 44. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of Example Embodiments 19 to 36.
Example Embodiment 45. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.
Example Embodiment 46. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.
Example Embodiment 47. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.
Example Embodiment 48. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a radio interface and processing circuitry, the UE’s components configured to perform any of the steps of any of Example Embodiments 1 to 18.
Example Embodiment 49. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.
Example Embodiment 50. The communication system of the previous 2 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE’s processing circuitry is configured to execute a client application associated with the host application.
Example Embodiment 51. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of Example Embodiments 1 to 18.
Example Embodiment 52. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station. Example Embodiment 53. A communication system including a host computer comprising: communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the UE comprises a radio interface and processing circuitry, the UE’s processing circuitry configured to perform any of the steps of any of Example Embodiments 1 to 18.
Example Embodiment 54. The communication system of the previous embodiment, further including the UE.
Example Embodiment 55. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
Example Embodiment 56. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
Example Embodiment 57. The communication system of the previous 4 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
Example Embodiment 58. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of Example Embodiments 1 to 18.
Example Embodiment 59. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.
Example Embodiment 60. The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application. Example Embodiment 61. The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application, wherein the user data to be transmitted is provided by the client application in response to the input data.
Example Embodiment 62. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of Example Embodiments 19 to 36.
Example Embodiment 63. The communication system of the previous embodiment further including the base station.
Example Embodiment 64. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
Example Embodiment 65. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
Example Embodiment 66. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of Example Embodiments 1 to 18.
Example Embodiment 67. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.
Example Embodiment 68. The method of the previous 2 embodiments, further comprising at the base station, initiating a transmission of the received user data to the host computer.
Modifications, additions, or omissions may be made to the systems and apparatuses described herein without departing from the scope of the disclosure. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document,“each” refers to each member of a set or each member of a subset of a set.
Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of the disclosure. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.
Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the spirit and scope of this disclosure.
ABBREVIATIONS
At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent bsting(s). lx RTT CDMA2000 lx Radio Transmission Technology
3GPP 3rd Generation Partnership Project
5G 5th Generation
5GS 5G System
5QI 5G QoS Identifier
ABS Almost Blank Subframe
ACK Acknowledgement
AN Access Network
AN Access Node
AP Application Protocol
ARQ Automatic Repeat Request
AS Access Stratum
AWGN Additive White Gaussian Noise
BCCH Broadcast Control Channel BCH Broadcast Channel
BSR Buffer Status Report
CA Carrier Aggregation
CC Carrier Component
CCCH SDU Common Control Channel SDU
CDMA Code Division Multiplexing Access
CE Control Element
CGI Cell Global Identifier
CIR Channel Impulse Response
CN Core Network
CP Cyclic Prefix
CPICH Common Pilot Channel
CPICH Ec/No CPICH Received energy per chip divided by the power density in the band
CQI Channel Quality Indicator
C-RNTI Cell RNTI
CSI Channel State Information
DC Dual Connectivity
DCI Downlink Control Information
DCCH Dedicated Control Channel
DL Downlink
DM Demodulation
DMRS Demodulation Reference Signal
DRB Data Radio Bearer
DRX Discontinuous Reception
DTX Discontinuous Transmission
DTCH Dedicated Traffic Channel
DUT Device Under Test
E-CID Enhanced Cell-ID (positioning method)
E-SMLC Evolved-Serving Mobile Location Centre
ECGI Evolved CGI
eMBB Enhanced Mobile BroadBand
eNB E-UTRAN NodeB
ePDCCH enhanced Physical Downlink Control Channel EPS Evolved Packet System
E-SMLC evolved Serving Mobile Location Center
E-UTRA Evolved UTRA
E-UTRAN Evolved Universal Terrestrial Radio Access Network
E-RAB EUTRAN Radio Access Bearer
FDD Frequency Division Duplex
FFS For Further Study
GERAN GSM EDGE Radio Access Network
gNB gNode B (a base station in NR; a Node B supporting NR and connectivity to NGC)
GNSS Global Navigation Satellite System
GSM Global System for Mobile communication
GTP-U GPRS Tunneling Protocol - User Plane
HARQ Hybrid Automatic Repeat Request
HO Handover
HSPA High Speed Packet Access
HRPD High Rate Packet Data
IP Internet Protocol
LOS Line of Sight
LPP LTE Positioning Protocol
LTE Long-Term Evolution
MAC Medium Access Control
MBMS Multimedia Broadcast Multicast Services
MBSFN Multimedia Broadcast multicast service Single Frequency Network
MBSFN ABS MBSFN Almost Blank Subframe
MCG Master Cell Group
MeNB Master eNB
MgNB Master gNB
MDT Minimization of Drive Tests
MIB Master Information Block
MME Mobility Management Entity
MSC Mobile Switching Center
MN Master Node
NACK Negative Acknowledgement NGC Next Generation Core
NPDCCH Narrowband Physical Downlink Control Channel
NR New Radio
OCNG OFDMA Channel Noise Generator
OFDM Orthogonal Frequency Division Multiplexing
OFDMA Orthogonal Frequency Division Multiple Access
OSS Operations Support System
OTDOA Observed Time Difference of Arrival
O&M Operation and Maintenance
PBCH Physical Broadcast Channel
P-CCPCH Primary Common Control Physical Channel
PCell Primary Cell
PCFICH Physical Control Format Indicator Channel
PDCCH Physical Downlink Control Channel
PDCP Packet Data Convergence Protocol
PDP Profile Delay Profile
PDSCH Physical Downlink Shared Channel
PGW Packet Gateway
PHICH Physical Hybrid-ARQ Indicator Channel
PLMN Public Land Mobile Network
PMI Precoder Matrix Indicator
PRACH Physical Random Access Channel
PRS Positioning Reference Signal
PS Packet Switched
PSCell Primary SCell
PSS Primary Synchronization Signal
PUCCH Physical Uplink Control Channel
PUSCH Physical Uplink Shared Channel
RACH Random Access Channel
QAM Quadrature Amplitude Modulation
RAB Radio Access Bearer
RAN Radio Access Network
RANAP Radio Access Network Application Part
RAT Radio Access Technology RLC Radio Link Control
RLF Radio Link Failure
RLM Radio Link Management
RNC Radio Network Controller
RNTI Radio Network Temporary Identifier
RRC Radio Resource Control
RRM Radio Resource Management
RS Reference Signal
RSCP Received Signal Code Power
RSRP Reference Symbol Received Power OR
Reference Signal Received Power
RSRQ Reference Signal Received Quality OR
Reference Symbol Received Quality
RSSI Received Signal Strength Indicator
RSTD Reference Signal Time Difference
RWR Release with Redirect
SCH Synchronization Channel
SCell Secondary Cell
SCG Secondary Cell Group
SCS Subcarrier Spacing
SCTP Stream Control Transmission Protocol
SDU Service Data Unit
SeNB Secondary eNB
SFN System Frame Number
SN Secondary Node
SGW Serving Gateway
SI System Information
SIB System Information Block
SNR Signal to Noise Ratio
S-NSSAI Single Network Slice Selection Assistance Information SON Self Optimized Network
SR Secondary Request
SRB Signaling Radio Bearer
SS Synchronization Signal SSS Secondary Synchronization Signal
SUL Supplementary Uplink
TBS Transport Block Size
TDD Time Division Duplex
TDOA Time Difference of Arrival
TEID Tunnel Endpoint Identifier
TNL Transport Network Layer
TO A Time of Arrival
TSS Tertiary Synchronization Signal
TTI Transmission Time Interval
UE User Equipment
UL Uplink
UCI Uplink Control Information
UDP User Datagram Protocol
UE User Equipment
UL Uplink
UP User Plane
UMTS Universal Mobile Telecommunication System
URLLC Ultra Reliable Low Latency Communication USIM Universal Subscriber Identity Module
UTDOA Uplink Time Difference of Arrival
UTRA Universal Terrestrial Radio Access
UTRAN Universal Terrestrial Radio Access Network
X2 Interface between base stations
WCDMA Wide CDMA
WLAN Wide Local Area Network

Claims

1. A method (1400) performed by a user equipment, UE, (110, 310, 400) configured with an uplink, UL, and a downlink, DL, associated with a primary cell, PCell, (120) and a supplementary uplink, SUL, (140) for communicating with a network node (160, 360), the method comprising:
detecting (1402) a radio link failure, RLF, on the PCell; and
transmitting (1404), to the network node (160, 360), a message comprising failure information associated with the RLF on the SUL.
2. The method of Claim 1, wherein detecting the RLF comprises detecting that a maximum number of RLC transmissions has been reached.
3. The method of any one of Claims 1 to 2, wherein detecting the RLF comprises receiving an indication from a medium access control, MAC, that random access has failed.
4. The method of any one of Claims 1 to 3, further comprising:
in response to detecting the RLF on the PCell and prior to transmitting the message comprising the failure information on the SUL, performing a random access procedure over the SUL to initiate a switch to the SUL.
5. The method of any one of Claims 1 to 4, further comprising:
in response to transmitting the message comprising the failure information on the SUL, receiving a response message indicating to the UE to perform at least one of:
deactivating carrier aggregation, CA, duplication;
making the secondary cell a new PCell; and
initiating a handover to a new cell or a new target network node.
6. The method of Claim 5, wherein the response message is received on a secondary cell, SCell.
7. The method of any one of Claims 5 to 6, wherein at least one of:
Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity, EN-DC, is enabled;
Next Generation Radio Access Technology Network-Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity, NGEN-DC, is enabled;
New Radio-Evolved Universal Terrestrial Radio Access Network-Dual Connectivity, NE-DC, is enabled; and
New Radio-Dual Connectivity, NR-DC, is enabled.
8. The method of any one of Claims 5 to 7, wherein:
the response message is received via split signal radio bearers, SRB, from a master node and a secondary node; or
the response message is received from the network node via signaling initiated by a secondary node.
9. The method of any one of Claims 5 to 8, wherein the response message is received via radio resource control, RRC, signaling.
10. The method of any one of Claims 1 to 9, wherein the message comprising the failure information comprises a result of at least one measurement performed by the UE, the at least one measurement comprising at least one of a Reference Signal Received Power, RSRP, measurement and a Reference Signal Received Quality, RSRQ, measurement.
11. The method of any one of Claims 1 to 10, wherein the message comprising the failure information comprises a failure cause.
12. A method (1800) performed by a network node (160, 360) communicating with a user equipment, UE, (110, 310, 400) configured with an uplink, UL, and a downlink, DL, associated with a primary cell, PCell, (120) and a supplementary uplink, SUL, (140) the method comprising:
receiving (1802) from the UE, on the SUL, a message comprising failure information associated with a Radio Link Failure, RLF, detected by the UE on the PCell.
13. The method of Claim 12, further comprising configuring the UE to detect the RLF when a maximum number of RLC transmissions has been reached.
14. The method of Claim 12, further comprising configuring the UE to detect the RLF when an indication that random access has failed is received from a medium access control, MAC.
15. The method of any one of Claims 12 to 14, further comprising:
prior to receiving, the message comprising the failure information, receiving at least one random access message over the SUL to initiate a switch of the UE to the SUL.
16. The method of any one of Claims 12 to 15, further comprising:
in response to receiving the message comprising the failure information on the SUL, transmitting a response message indicating to the UE to perform an action comprising at least one of:
deactivating carrier aggregation, CA, duplication; making the secondary cell a new PCell; and
initiating a handover to a new cell or a new target network node.
17. The method of Claim 16, wherein the message comprising the failure information comprises a failure cause and the method further comprises determining the action to be performed by the UE based on the failure cause.
18. The method of any one of Claims 16 to 17, wherein the response message is transmitted on a secondary cell, SCell.
19. The method of any one of Claims 16 to 18, wherein at least one of:
Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity, EN-DC, is enabled;
Next Generation Radio Access Technology Network-Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity, NGEN-DC, is enabled;
New Radio-Evolved Universal Terrestrial Radio Access Network-Dual Connectivity, NE-DC, is enabled; and
New Radio-Dual Connectivity, NR-DC, is enabled.
20. The method of any one of Claims 16 to 19, wherein:
the response message is transmitted via split signal radio bearers, SRB, from a master node and a secondary node; or
the response message is transmitted from the network node via signaling initiated by a secondary node.
21. The method of any one of Claims 16 to 20, wherein the response message is transmitted via radio resource control, RRC, signaling.
22. The method of any one of Claims 12 to 21, wherein the message comprising the failure information comprises a result of at least one measurement performed by the UE, the at least one measurement comprising at least one of a Reference Signal Received Power, RSRP, measurement and a Reference Signal Received Quality, RSRQ, measurement.
23. A user equipment, UE, (110, 360, 400) configured with an uplink, UL, and a downlink, DL, associated with a primary cell, PCell (120) and a supplementary uplink, SUL, (140) for communicating with a network node (160, 360), the UE comprising:
processing circuitry (320) configured to: detect a radio link failure, RLF, on the PCell; and
transmit, to the network node (160, 360), a message comprising failure information associated with the RLF on the SUL.
24. The UE of Claim 23, wherein when detecting the RLF the processing circuitry is configured to detect that a maximum number of RLC transmissions has been reached.
25. The UE of any one of Claims 23 to 24, wherein when detecting the RLF the processing circuitry is configured to receive an indication from a medium access control, MAC, that random access has failed.
26. The UE of any one of Claims 23 to 25, wherein the processing circuitry is configured to:
in response to detecting the RLF on the primary cell and prior to transmitting the message comprising the failure information on the SUL, perform a random access procedure over the SUL to initiate a switch to the SUL.
27. The UE of any one of Claims 23 to 26, wherein the processing circuitry is configured to:
in response to transmitting the message comprising the failure information on the SUL, receive a response message indicating to the UE to perform at least one of:
deactivate carrier aggregation, CA, duplication;
make the secondary cell a new PCell; and
initiate a handover to a new cell or a new target network node.
28. The UE of Claim 27, wherein the response message is received on a secondary cell, SCell.
29. The UE of any one of Claims 27 to 28, wherein at least one of:
Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity, EN-DC, is enabled;
Next Generation Radio Access Technology Network-Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity, NGEN-DC, is enabled;
New Radio-Evolved Universal Terrestrial Radio Access Network-Dual Connectivity, NE-DC, is enabled; and
New Radio-Dual Connectivity, NR-DC, is enabled
30. The UE of any one of Claims 27 to 29, wherein: the response message is received via split signal radio bearers, SRB, from a master node and a secondary node; or
the response message is received from the network node via signaling initiated by a secondary node.
31. The UE of any one of Claims 27 to 30, wherein the response message is received via radio resource control, RRC, signaling.
32. The UE of any one of Claims 23 to 31, wherein the message comprising the failure information comprises a result of at least one measurement performed by the UE, the at least one measurement comprising at least one of a Reference Signal Received Power, RSRP, measurement and a Reference Signal Received Quality, RSRQ, measurement.
33. The UE of any one of Claims 23 to 32, wherein the message comprising the failure information comprises a failure cause.
34. A network node (160, 360) communicating with a user equipment, UE, (110, 310) configured with an uplink, UL, and a downlink, DL, associated with a primary cell, PCell, (120) and a supplementary uplink, SUL, (140) the network node comprising:
processing circuitry (370) configured to receive from the UE, on the SUL, a message comprising failure information associated with a Radio Link Failure, RLF, detected by the UE on the PCell.
35. The network node of Claim 34, wherein the processing circuitry is configured to configure the UE to detect the RLF when a maximum number of RLC transmissions has been reached.
36. The network node of Claim 43, wherein the processing circuitry is configured to configure the UE to detect the RLF when an indication that random access has failed is received from a medium access control, MAC.
37. The network node of any one of Claims 34 to 36, wherein the processing circuitry is configured to:
prior to receiving, the message comprising the failure information, receive at least one random access message over the SUL to initiate a switch of the UE to the SUL.
38. The network node of any one of Claims 34 to 37, wherein the processing circuitry is configured to: in response to receiving the message comprising the failure information on the SUL, transmit a response message indicating to the UE to perform an action comprising at least one of:
deactivating carrier aggregation, CA, duplication;
making the secondary cell a new PCell; and
initiating a handover to a new cell or a new target network node.
39. The network node of Claim 38, wherein the message comprising the failure information comprises a failure cause and the method further comprises determining the action to be performed by the UE based on the failure cause.
40. The network node of any one of Claims 38 to 39, wherein the response message is transmitted on a secondary cell, SCell.
41. The network node of any one of Claims 38 to 40, wherein at least one of:
Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity, EN-DC, is enabled;
Next Generation Radio Access Technology Network-Evolved Universal Terrestrial Radio Access Network-New Radio Dual Connectivity, NGEN-DC, is enabled;
New Radio-Evolved Universal Terrestrial Radio Access Network-Dual Connectivity, NE-DC, is enabled; and
New Radio-Dual Connectivity, NR-DC, is enabled.
42. The network node of any one of Claims 38 to 41, wherein:
the response message is transmitted via split signal radio bearers, SRB, from a master node and a secondary node; or
the response message is transmitted from the network node via signaling initiated by a secondary node.
43. The network node of any one of Claims 38 to 42, wherein the response message is transmitted via radio resource control, RRC, signaling.
44. The network node of any one of Claims 34 to 43, wherein the message comprising the failure information comprises a result of at least one measurement performed by the UE, the at least one measurement comprising at least one of a Reference Signal Received Power, RSRP, measurement and a Reference Signal Received Quality, RSRQ, measurement.
PCT/SE2020/050118 2019-02-13 2020-02-06 Radio link failure recovery over supplementary uplink WO2020167212A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962804911P 2019-02-13 2019-02-13
US62/804,911 2019-02-13

Publications (1)

Publication Number Publication Date
WO2020167212A1 true WO2020167212A1 (en) 2020-08-20

Family

ID=69650681

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2020/050118 WO2020167212A1 (en) 2019-02-13 2020-02-06 Radio link failure recovery over supplementary uplink

Country Status (1)

Country Link
WO (1) WO2020167212A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112787794A (en) * 2021-03-08 2021-05-11 深圳市佳贤通信设备有限公司 SUL-based URLLC service uplink transmission method
WO2024015042A1 (en) * 2022-07-11 2024-01-18 Rakuten Mobile, Inc. Automatic enabling endc umts terrestrial radio access network (e-utran) new radio - dual connectivity for 4g lte enb

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150181479A1 (en) * 2013-01-18 2015-06-25 Mediatek Inc. Mechanism for Radio Link Monitoring and Radio Link Failure Handling in Small Cell Networks
WO2018203736A1 (en) * 2017-05-05 2018-11-08 Samsung Electronics Co., Ltd. System, data transmission method and network equipment supporting pdcp duplication function method and device for transferring supplementary uplink carrier configuration information and method and device for performing connection mobility adjustment

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150181479A1 (en) * 2013-01-18 2015-06-25 Mediatek Inc. Mechanism for Radio Link Monitoring and Radio Link Failure Handling in Small Cell Networks
WO2018203736A1 (en) * 2017-05-05 2018-11-08 Samsung Electronics Co., Ltd. System, data transmission method and network equipment supporting pdcp duplication function method and device for transferring supplementary uplink carrier configuration information and method and device for performing connection mobility adjustment

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "RLM and RLF in NR", vol. RAN WG2, no. Spokane, USA; 20170403 - 20170407, 14 May 2017 (2017-05-14), XP051274698, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20170514] *
KDDI CORPORATION: "Discussions on reporting SCG-RLF towards MeNB", vol. RAN WG2, no. Valencia, Spain; 20140331 - 20140404, 22 March 2014 (2014-03-22), XP050792437, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20140322] *
XIAOMI: "Random access failure consideration for SUL", vol. RAN WG2, no. Vancouver, Canada; 20180122 - 20180126, 12 January 2018 (2018-01-12), XP051386093, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG2%5FRL2/TSGR2%5FAHs/2018%5F01%5FNR/Docs/> [retrieved on 20180112] *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112787794A (en) * 2021-03-08 2021-05-11 深圳市佳贤通信设备有限公司 SUL-based URLLC service uplink transmission method
WO2024015042A1 (en) * 2022-07-11 2024-01-18 Rakuten Mobile, Inc. Automatic enabling endc umts terrestrial radio access network (e-utran) new radio - dual connectivity for 4g lte enb

Similar Documents

Publication Publication Date Title
US11425581B2 (en) Wireless device, second node, and methods performed thereby for handling a failure in a secondary cell serving the wireless device
US11265801B2 (en) Information exchange for initial user equipment access
US11606833B2 (en) Packet data convergence protocol data recovery
US20230262546A1 (en) Dual active protocol stack and connection/link failure handling
US20220353775A1 (en) Early Radio Link Issue Indication
US20240073752A1 (en) Co-Existence of Inter-SN and Intra-SN CPC
US20210211944A1 (en) Methods for Indication of Radio Access Technology
WO2022086389A1 (en) Methods, apparatus and computer-readable media relating to conditional reconfigurations in wireless networks
EP4014532A1 (en) Updating a pci in a du-cu split architecture
CN112956279B (en) NAS-AS interaction for early data transfer
WO2022086388A1 (en) Methods, apparatus and computer-readable media relating to conditional reconfigurations in wireless networks
WO2020167212A1 (en) Radio link failure recovery over supplementary uplink
US20230403646A1 (en) Scg activation during mobility
US20230363028A1 (en) Configuring a wireless device with multi-radio access technology dual connectivity
WO2022086399A1 (en) User equipment and a method performed therein
US20220015038A1 (en) Mobile Terminated Early Data Transmission Reachability for RAN Context
US11985556B2 (en) Optimized handling of traffic management-initiated access change
US12004249B2 (en) Flexible resume and reconfigurations in multi-radio dual connectivity and standalone scenarios
US20240056835A1 (en) Management of master and secondary cell group configurations
US20230068134A1 (en) Synchronization and Random Access During Connection Resume
US20210337615A1 (en) Flexible resume and reconfigurations in multi-radio dual connectivity and standalone scenarios
WO2022214844A1 (en) Master node to enb change with sn node direct forwarding

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: 20706855

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: 20706855

Country of ref document: EP

Kind code of ref document: A1