WO2022154723A1 - Handling of missing handover radio link control (rlc) acknowledgements - Google Patents

Handling of missing handover radio link control (rlc) acknowledgements Download PDF

Info

Publication number
WO2022154723A1
WO2022154723A1 PCT/SE2022/050020 SE2022050020W WO2022154723A1 WO 2022154723 A1 WO2022154723 A1 WO 2022154723A1 SE 2022050020 W SE2022050020 W SE 2022050020W WO 2022154723 A1 WO2022154723 A1 WO 2022154723A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
rlf
network node
rlc
handover
Prior art date
Application number
PCT/SE2022/050020
Other languages
French (fr)
Inventor
Mattias BERGSTRÖM
Icaro Leonardo DA SILVA
Marco BELLESCHI
Lian ARAUJO
Anders Jonsson
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 WO2022154723A1 publication Critical patent/WO2022154723A1/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0079—Transmission or use of information for re-establishing the radio link in case of hand-off failure or rejection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1825—Adaptation of specific ARQ protocol parameters according to transmission conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present disclosure is generally related to wireless communications networks and is more particularly related to the handling of radio link control (RLC) acknowledgements in such networks.
  • RLC radio link control
  • Figure 1 illustrates a simplified wireless communication system, with a user equipment (UE) 102 that communicates with one or multiple network nodes 103, 104, which in turn are connected to another network node 106.
  • Network nodes 103, 104 which may be considered access nodes and which may be referred to as base stations, are part of the radio access network (RAN) 100.
  • the other network node 106 may be, for example, part of a core network.
  • the network nodes 103, 104 correspond typically to base stations referred to in 3GPP specifications as Evolved NodeBs (eNBs), while the network node 106 corresponds typically to either a Mobility Management Entity (MME) and/or a Serving Gateway (SGW).
  • 3GPP 3rd Generation Partnership Project
  • EPS Evolved Packet System
  • LTE Long Term Evolution
  • 4G 4G
  • the network nodes 103, 104 correspond typically to base stations referred to in 3GPP specifications as Evolved NodeBs (eNBs)
  • MME Mobility Management Entity
  • SGW Serving Gateway
  • the eNB is part of the RAN 100, which in this case is the E-UTRAN (Evolved Universal Terrestrial Radio Access Network), while the MME and SGW are both part of the EPC (Evolved Packet Core network).
  • the eNBs are inter-connected via the X2 interface, and connected to EPC via the SI interface, more specifically via Sl-C to the MME and Sl-U to the SGW.
  • the network nodes 103, 104 correspond typically to base stations referred to as 5G NodeBs, or gNBs, while the network node 106 corresponds typically to either an Access and Mobility Management Function (AMF) and/or a User Plane Function (UPF).
  • AMF Access and Mobility Management Function
  • UPF User Plane Function
  • the gNB is part of the RAN 100, which in this case is the NG-RAN (Next Generation Radio Access Network), while the AMF and UPF are both part of the 5G Core Network (5GC).
  • the gNBs are inter-connected via the Xn interface, and connected to 5GC via the NG interface, more specifically via NG-C to the AMF and NG-U to the UPF.
  • the specifications for both NR and LTE define a Radio Link Control (RLC) protocol, to be carried out by corresponding RLC entities in the gNB or eNB and the UE.
  • the RLC protocol is responsible for transfer of upper layer packet data units (PDUs) in either acknowledged mode (AM), unacknowledged mode (UM), and transparent mode (TM).
  • AM the RLC protocol also provides for error correction via retransmission of lost RLC PDUs, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs when a complete RLC PDU cannot be transmitted (AM), and reordering of RLC data PDUs.
  • the default behavior for a receiving RLC entity is to acknowledge a poll from the transmitting RLC entity with a status report (SR), which informs the transmitting RLC entity of which RLC PDUs have been received.
  • SR status report
  • This information is used by the transmitting RLC entity to determine whether the receiving RLC entity has received the transmitted data or higher layer signaling message or whether an RLC retransmission is necessary.
  • this rule has exceptions as outlined below.
  • Handover is a procedure whereby a user equipment (UE) connected to a first cell gets directed to connect to another cell, instead.
  • the purpose of handover is to move the UE from a source access node using a source radio connection (also known as source cell connection), to a target access node, using a target radio connection (also known as target cell connection).
  • the handover may be caused by movement of the UE, for example, or for other reasons where the target cell is better positioned to serve the UE.
  • the source radio connection is associated with a source cell controlled by the source access node.
  • the target radio connection is associated with a target cell controlled by the target access node. In other words, during a handover, the UE moves from the source cell to a target cell.
  • the source access node or the source cell is referred to as the "source”, and the target access node or the target cell is sometimes referred to as the "target”.
  • the source access node and the target access node may also be referred to as the source node and the target node, the source radio network node and the target radio network node or the source gNB and the target gNB.
  • the source access node and target access node are different nodes, such as different eNBs or gNBs. These cases are also referred to as inter-node handover, inter-eNB handover or inter-gNB handover. In other cases, the source access node and target access node are the same node, such as the same eNB and gNB. These cases are also referred to as intra-node handover, intra-eNB handover or intra-gNB handover and covers the case then source and target cells are controlled by the same access node. In yet other cases, handover is performed within the same cell (and thus also within the same access node controlling that cell) - these cases are also referred to as intra-cell handover.
  • source access node and "target access node” each refer to a role served by a given access node during a handover of a specific UE.
  • a given access node may serve as source access node during handover of one UE, while it also serves as the target access node during handover of a different UE.
  • the same access node serves both as the source access node and target access node for that UE.
  • An inter-node handover can further be classified as an Xn-based or NG-based handover, depending on whether the source and target node communicate directly using the Xn interface or indirectly via the core network using the NG interface.
  • An RRC_CONNECTED UE in E-UTRAN or NG-RAN can be configured by the network to perform measurements of serving and neighbor cells and based on the measurement reports sent by the UE, the network may decide to perform a handover of the UE to a neighbor cell. The network then sends a Handover Command message to the UE (in LTE an RRConnectionReconfiguration message with a field called mobilityControilnfo and in NR an RRCReconfiguration message with a reconfig ura tion WithSyn c f i e I d ) .
  • RRC Radio Resource Control
  • the reconfiguration parameters provided by the target access node contain, for example, information needed by the UE to access the target access node, e.g., random access configuration, a new C-RNTI assigned by the target access node, and security parameters enabling the UE to calculate new security keys associated to the target access node so the UE can send a Handover Complete message (in LTE an RRConnectionReconfiguratioComplete message and in NR an RRCReconfigurationComplete message) on SRB1 encrypted and integrity protected based on new security keys upon accessing the target access node.
  • a Handover Complete message in LTE an RRConnectionReconfiguratioComplete message and in NR an RRCReconfigurationComplete message
  • Figure 2 shows the signaling flow between the UE and source and target access node during an Xn- based inter-node handover in NR. Similar steps take place during an LTE handover. This might be regarded as the "legacy" handover procedure, i.e., a handover procedure that does not utilize "make-before-break” techniques and does not incorporate the various techniques described herein. Details of the steps shown in Figure 2, which can be divided into handover preparation 212, handover execution 213, and handover completion 214, are provided below.
  • the UE and source gNB have an established connection and are exchanging user data. Due to some trigger, e.g., a measurement report from the UE, the source gNB decides to handover the UE to the target gNB.
  • some trigger e.g., a measurement report from the UE
  • the source gNB sends a HANDOVER REQUEST message to the target gNB with necessary information to prepare the handover at the target side.
  • the information includes, among other things, the current source configuration and the UE capabilities.
  • the target gNB prepares the handover and responds with a HANDOVER REQUEST ACKNOWLEDGE message to the source gNB, which includes the handover command (a RRCReconfiguration message containing the reconfigurationWithSync field) to be sent to the UE.
  • the handover command includes information needed by the UE to access the target cell, e.g., random access configuration, a new C-RNTI assigned by the target access node and security parameters enabling the UE to calculate the target security key so the UE can send the handover complete message (a RRCReconfigurationComplete message).
  • the target gNB may be unable to comprehend the UE configuration provided by the source eNB in the HANDOVER REQUEST.
  • the target gNB can use so-called "full configuration" to reconfigure the UE for handover.
  • Full configuration option includes an initialization of the radio configuration, which makes the procedure independent of the configuration used in the source cell.
  • the target node uses so-called "delta configuration," where only the delta to the radio configuration in the source cell is included in the handover command. Delta configuration typically reduces the size of the handover command, which increases the speed and robustness of the handover.
  • the source gNB triggers the handover by sending the handover command received from the target node in the previous step to the UE.
  • the source gNB stops scheduling any further DL or UL data to the UE and sends a SN STATUS TRANSFER message to the target gNB, the message indicating the latest PDCP SN transmitter and receiver status.
  • the source node now also starts to forward user data to the target node, which buffers this data for now.
  • the UE sends the handover complete to the target gNB.
  • the target node can start exchanging user data with the UE.
  • the target node also requests the AMF to switch the DL data path from the UPF from the source node to the target node (not shown). Once the path switch is completed the target node sends the UE CONTEXT RELEASE message to the source node.
  • the UE executes the handover and moves to the target cell.
  • a handover command e.g., in NR this corresponds to an RRCReconfiguration message including the IE ReconfigurationWithSync, while in LTE this corresponds to an RRCConnectionReconfiguration message including the IE MobilityControilnfo
  • the UE executes the handover and moves to the target cell.
  • the expected behavior on RLC level when user data or higher layer signaling messages such as RRC messages are carried over RLC Acknowledged Mode (AM) is that the receiving RLC entity at the UE sends a Status Report (SR) whenever it receives an RLC PDU that has the poll bit set in the RLC header.
  • SR Status Report
  • the UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARO, and ARQ.) of this message.
  • the RLC protocol in NR and LTE has retransmission functionality. If the link is configured to use RLC
  • AM mode which is how a handover command is delivered by lower layers
  • the transmitter retransmits RLC packets to the receiver until the receiver has indicated successful reception of the packet, via an SR. Notice that in a handover situation there may be a higher likelihood that a retransmission is needed, since radio conditions with the serving cell may start to degrade when the network determines to handover the UE.
  • RLF Radio Link Failure
  • the UE shall:
  • the UE shall:
  • the UE When any of those triggers occur, the UE will declare that the radio link has failed, and the UE will then attempt to reconnect to the network. Under normal situations, this reconnecting happens by the UE trying to reestablish the connection by selecting the best cell and then initiating a reestablishment procedure towards that cell.
  • the network may determine whether an RLF event has occurred for the UE. The network may do this to be in-synch with the UE with regards to the state the UE is in. Also, the network may log this event, i.e., the event that the network assumes that an RLF event has happened for the UE. This information may be used to set parameters, or for troubleshooting, etc.
  • the network may release the RRC connection for the UE.
  • the network can do this by sending an RRC release message. If that RRC release message contains a "suspendConfig" indication the UE will go to the RRC INACTIVE state, otherwise the UE will go to RRC IDLE state. In both these states the UE has no active connection with any gNB. This state saves power in the UE and network resources, for example.
  • the UE shall:
  • the UE will delay the entering to RRC INACTIVE and RRC IDLE by sixty milliseconds, or until the UE has acknowledged the reception of the RRC release message.
  • the release message may further include redirect-information.
  • This information can include redirection-information which indicates to the UE that the UE shall, when moving to IDLE/INACTIVE, select a certain frequency that the network has selected.
  • the UE is allowed to execute a handover directly, without requirements on sending either RLC or HARQ. feedback to the network for the message containing the handover command.
  • This ambiguity may result in that the network assumes that the UE has not received the handover command, and hence the network will attempt many retransmissions of the message carrying the handover command, e.g., as many as 32 retransmissions.
  • Embodiments of the techniques and apparatus described in detail below address this problem by aborting RLC retransmission processes or reducing a number of RLC retransmissions, under certain circumstances. While several of these techniques are described below in the context of a handover procedure, it will be appreciated that these techniques may be applied in connection with other types of RRC commands as well.
  • An example method is carried out in a network node, such as a base station (e.g., gNB or eNB), operating in a wireless network.
  • This example method comprises the step of transmitting, to a UE, a message containing or concluding a RRC command of a predetermined type, where this predetermined type might be, for example, a handover command.
  • the method further comprises applying a first predetermined maximum number of RLC retransmissions to retransmissions of at least one RLC PDU associated with the message, where the first predetermined maximum number differs from a second predetermined maximum number of RLC retransmissions applicable to RLC PDUs not associated with a message containing or concluding an RRC command of the predetermined type.
  • a network node such as a base station (e.g., gNB or eNB), operating in a wireless network.
  • the first network node determines that a UE served by the first network node has been handed over or is being handed over to a second network node.
  • the first network node adjusts a retransmission process directed towards the UE, in response to said determining, e.g., by reducing or eliminating retransmissions.
  • Still another example method is likewise carried out in a first network node operating in a wireless network.
  • This method comprises transmitting a RLC PDU to a UE and receiving a medium access control (MAC) hybrid automatic-repeat-request (HARQ) acknowledgement, the MAC HARQ acknowledgement indicating that a MAC PDU corresponding to the RLC PDU was successfully decoded.
  • This method further comprises aborting an RLC retransmission process for the RLC PDU, in response to said receiving.
  • MAC medium access control
  • HARQ hybrid automatic-repeat-request
  • Another example method again implemented by a first network node operating in a wireless network, comprises the step of detecting a trigger indicating RLF for a UE, subsequent to beginning transmission of a RRC command of a predetermined type to the UE.
  • This predetermined type may be a handover command, for example.
  • This example method further comprises refraining from recording an RLF event corresponding to the trigger in a log of RLF events.
  • Yet another example method similarly comprises the step of detecting a trigger indicating RLF for a UE, subsequent to beginning transmission of a RRC command of a predetermined type to the UE.
  • This example method comprises the step of recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers.
  • Figure 1 is a simplified illustration of a wireless communication system.
  • Figure 2 illustrates handover in NR.
  • Figures 3, 4, 5, 6, and 7 illustrate example methods according to various exemplary embodiments of the present disclosure.
  • Figure 8 is a block diagram illustrating an example UE.
  • Figure 9 is a block diagram illustrating an example network node.
  • Figure 10 is a block diagram of an exemplary wireless network configurable according to various exemplary embodiments of the present disclosure.
  • FIG 11 is a block diagram of an exemplary user equipment (UE) configurable according to various exemplary embodiments of the present disclosure.
  • UE user equipment
  • Figure 12 is a block diagram of illustrating a virtualization environment that can facilitate virtualization of various functions implemented according to various exemplary embodiments of the present disclosure.
  • Figures 13 and 14 are block diagrams of exemplary communication systems configurable according to various exemplary embodiments of the present disclosure.
  • Figures 15, 16, 17, and 18 are flow diagrams illustrating various exemplary methods and/or procedures implemented in a communication system, according to various exemplary embodiments of the present disclosure.
  • embodiments of the techniques and apparatus described in detail below address a problem where a network node may fail to receive an RLC acknowledgement for an RRC command under circumstances where it is not clear whether it would be useful to continue RLC processes for the RRC command or related PDUs. According to several embodiments described herein, this problem is addressed by aborting RLC retransmission processes or reducing a number of RLC retransmissions, under certain circumstances. While several of these techniques are described below in the context of a handover procedure, it will be appreciated that these techniques may be applied in connection with other types of RRC commands as well.
  • the network e.g., a gNB or eNB
  • the network does any one or more of the following: • Applies a different (lower) number of retransmissions for handover commands (and transmissions close to the handover command).
  • the description herein describes behavior regarding a handover, which corresponds to a reconfiguration with sync procedure (as defined in 3GPP TS 38.331, the NR RRC specifications). This also comprises the case where the source and target cells are associated to a Secondary Node(s) for a UE configured with MR-DC.
  • an example scenario where the embodiments below can be applied is for the (normal) handover scenario where the network sends a handover command to the UE and the UE applies that command in response to the reception of the command.
  • some of the techniques described herein can also be applied in the scenario of a conditional handover. For example, described below is how the source cell may stop sending RLC retransmissions to a UE when the network gets an indication from a target node that the UE has (or is in the process of) performed a handover. This can be applied also in the case of conditional handover and can then be applied to transmissions the network has performed/initiated close in time to the execution of the conditional handover.
  • the techniques described herein could also be applied also for those transmissions. (Note, however, that based on current NR specifications, the UE behavior mandated by the 3GPP standards is conflicting regarding whether the UE must send acknowledgements for data received prior to the handover. The techniques described herein could be applied in the event any restriction is lifted.)
  • the UE is handed over from one cell to another.
  • the cell that the UE moves from is sometimes referred to as the source cell while the cell that the UE is moved to is sometimes referred to as the target cell.
  • these two cells can be associated with the same network node (intra-node handover), and in some special cases they can even be the same cell (intra-cell handover).
  • the network may apply a first number of maximum RLC retransmissions value for a transmission containing a handover command, and a second number of maximum RLC retransmissions value for a transmission does not contain a handover command.
  • the network may apply 31 retransmissions (i.e., 32 total transmissions) for transmissions that do not contain or complete a handover command but only two retransmissions (i.e., three total transmissions) for transmissions that contain or complete a handover command.
  • the network may apply the same behavior (i.e., a different number of RLC retransmissions) for transmissions that are performed close in time to the transmission of the handover command, e.g., within a predetermined time window before and after the transmission of the handover command.
  • Figure 3 is a process flow diagram illustrating an example method that may be considered a generalization of the technique described immediately above. This method may be carried out by a network node operating in a wireless network, such as an LTE eNB or an NR gNB.
  • a network node operating in a wireless network, such as an LTE eNB or an NR gNB.
  • the method comprises the step of transmitting, to a UE, a message containing or concluding an RRC, command of a predetermined type.
  • UE refers to any access terminal or end-user terminal, whether or not it is compliant with 3GPP specifications for such devices.
  • the method further comprises applying a first predetermined maximum number of RLC retransmissions to retransmissions of at least one RLC PDU associated with the message, where this first predetermined maximum number differs from a second predetermined maximum number of RLC retransmissions applicable to RLC PDUs not associated with a message containing or concluding a RRC command of the predetermined type.
  • the predetermined type of RRC command may be a handover command.
  • the technique may be applied to one or more other types, in addition to or instead of the handover command.
  • the predetermined type may be one of a plurality of types to which the first predetermined maximum number of RLC retransmissions is applicable, the plurality of types being a proper subset of RRC commands, i.e., consisting of some but fewer than all, RRC commands.
  • the first predetermined maximum number is less than the second predetermined maximum number.
  • the first predetermined maximum number may be 2, for example, while the second predetermined maximum number may be 16, or 32, in various examples.
  • the at least one RLC PDU associated with the message comprises an RLC PDU that forms all or part of the message. In some embodiments, the at least one RLC PDU associated with the message comprises an RLC PDU that forms all or part of a second message containing a portion of the RRC command. In some embodiments or instances, for example, a handover command may be fully contained within an RLC PDU. In other embodiments, the handover command or other RRC command may be carried by multiple RLC PDUs. In various instances or embodiments, the first predetermined maximum number may be applied to all of these multiple RLC PDUs, or only to the one concluding the command.
  • the first predetermined maximum number of retransmissions may be applied to RLC PDUs around the RLC PDU containing or completing the handover command or other RRC command, in some embodiments or instances.
  • the at least one RLC PDU associated with the message comprises an RLC PDU transmitted within a predetermined time window around the transmission of the message.
  • the steps shown in Figure 3 may be followed by the steps of detecting a trigger indicating radio link failure (RLF) for the UE, subsequent to beginning transmission of the handover command, and refraining from recording an RLF event corresponding to the trigger in a log of RLF events.
  • the steps shown in Figure 3 may be followed by the steps of detecting a trigger indicating RLF for the UE, subsequent to beginning transmission of the handover command, and recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers.
  • a network node may abort sending retransmissions to a UE (e.g., for transmissions containing or completing a handover command) if the network node receives an indication from another network node (e.g., a target node) that another network node would send (at least) in response to that the UE has performed (or is in the process of performing) a handover to that other network node. That message can be a Handover Success message or another message that the target node sends in response to the UE performing the handover to the target node.
  • This approach has the benefit that the network may continue to perform retransmissions to the UE until it is certain that the UE has received the handover command.
  • the network node in the event of handover to another cell that is controlled by the same network node, the network node will, in response to determining that the UE has performed (or is in the process of performing) a handover to that other cell of the same network node, abort (or refrain from) retransmissions.
  • the network adjusts its RLC behavior when it transmits a HO command to the UE.
  • the node determining the handover e.g., placed at a Central Unit (CU) hosting the RRC entity and handover algorithm
  • the RLC entity e.g., placed at a Distributed Unit (DU), hosting the RLC entity, that a handover command is being submitted, hence, the UE may leave, hence, the RLC entity should not perform retransmissions and/or adjust its RLC retransmission behavior (e.g., decrease the number of retransmissions).
  • CU Central Unit
  • DU Distributed Unit
  • the network adjusts its RLC behavior when it transmits a HO request command to a target cell X, while the serving cell still has good enough quality / radio conditions (e.g., SINR and/or RSRP and/or RSRQ.) above a certain threshold. That threshold for serving cell quality indicates that retransmissions are not expected to be required (e.g., based on statistics), as in good radio conditions with serving cell the UE should successfully receive the HO without the need for RLC retransmissions.
  • good enough quality / radio conditions e.g., SINR and/or RSRP and/or RSRQ.
  • the node initiating the handover e.g., placed at a Central Unit (CU), hosting the RRC entity and handover algorithm
  • the RLC entity e.g. placed at a Distributed Unit (DU) hosting the RLC entity
  • DU Distributed Unit
  • the RLC entity should not perform retransmissions and/or adjust its RLC retransmission behavior (e.g., decrease the number of retransmissions).
  • FIG. 4 is a process flow diagram illustrating an example method that may be considered a generalization of several of the techniques described immediately above. Again, this method may be carried out by a network node operating in a wireless network, such as an LTE eNB or an NR gNB.
  • a network node operating in a wireless network, such as an LTE eNB or an NR gNB.
  • the illustrated method includes the step of determining that a UE served by the first network node has been handed over or is being handed over to a second network node. As shown at block 420, the method further includes the step of adjusting a retransmission process directed towards the UE, in response to said determining.
  • the determining shown at block 410 comprises receiving, from the second network node, an indication that the UE has been handed over or is being handed over to the second network node.
  • the adjusting shown at block 420 comprises aborting an ongoing retransmission process directed towards the UE in response to receiving the indication.
  • the determining shown at block 410 comprises determining to initiate a handover of the UE to the second network node and the adjusting shown at block 420 comprises reducing or eliminating retransmissions for one or more transmissions to the UE.
  • the adjusting is further in response to determining that a quality of the link between the UE and the first network node is above a predetermined threshold.
  • the steps shown in Figure 4 may be followed by the steps of detecting a trigger indicating radio link failure (RLF) for the UE, subsequent to beginning transmission of the handover command, and refraining from recording an RLF event corresponding to the trigger in a log of RLF events.
  • the steps shown in Figure 4 may be followed by the steps of detecting a trigger indicating RLF for the UE, subsequent to beginning transmission of the handover command, and recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers.
  • a network node aborts sending retransmissions to a UE (e.g., for transmissions containing a handover command) when determining that the UE has sent HARQ. feedback indicating that the UE has successfully decoded the transmission that contains a handover command (or other RRC command of a predetermined type).
  • the network node in the event that the handover command is segmented into more than one MAC PDUs, i.e., transport blocks (TBs), the network node aborts sending retransmissions of the HO command when determining that the UE sends an HARQ.
  • the node determining the handover e.g., placed at a Central Unit (CU), hosting the RRC entity and handover algorithm, may indicate to the RLC entity (e.g., placed at a Distributed Unit (DU), hosting the RLC entity, that a handover command is being submitted.
  • CU Central Unit
  • DU Distributed Unit
  • the RLC entity in turn may inform the MAC entity that a certain RLC PDU contains the handover command or a segment of the handover command, or the last segment of the handover command.
  • the MAC entity Upon receiving an HARQ feedback indicating that the UE has successfully decoded the transmission which contains a handover command or which contains the last segment of the handover command, the MAC entity informs the RLC entity, which in turn will abort sending RLC retransmissions.
  • the network node ensures that the resource in which the HARQ. feedback for the handover command is transmitted by the UE occurs in the time domain earlier than when the UE is expected to complete the processing of the HO command. For example, if a UE is expected to process the handover command in 10 milliseconds after reception, the network may provide a KI value in the Physical Downlink Shared Channel (PDSCH) carrying the handover command, such that the uplink slot in which the corresponding HARQ feedback shall be transmitted occurs earlier than 10 milliseconds after the reception of the handover command, i.e., Kl ⁇ 10.
  • PDSCH Physical Downlink Shared Channel
  • the network ensures that if the UE has correctly received the handover command, the UE will manage to send at least an HARQ feedback before initiating the handover towards a target cell.
  • the network node keeps sending RLC retransmissions of the handover command either until a HARQ ACK feedback is received or until the maximum amount of RLC retransmissions are performed.
  • the network would, in response to an ACK on the HARQ level, determine to not send any more RLC retransmissions for the message containing the handover command.
  • FIG. 5 is a process flow diagram illustrating an example method that may be considered a generalization of several of the techniques described immediately above. Again, this method may be carried out by a network node operating in a wireless network, such as an LTE eNB or an NR gNB.
  • a network node operating in a wireless network, such as an LTE eNB or an NR gNB.
  • the illustrated method comprises the step of transmitting a RLC PDU to a UE.
  • This RLC PDU may contain or complete a handover command, for example.
  • the illustrated method further comprises receiving a MAC HARQ acknowledgement, the MAC HARQ. acknowledgement indicating that a MAC PDU corresponding to the RLC PDU was successfully decoded.
  • the method further comprises, as shown at block 530, the step of aborting an RLC retransmission process for the RLC PDU, in response to said receiving.
  • the steps shown in Figure 5 may be followed by the steps of detecting a trigger indicating radio link failure (RLF) for the UE, subsequent to beginning transmission of the handover command, and refraining from recording an RLF event corresponding to the trigger in a log of RLF events.
  • the steps shown in Figure 5 may be followed by the steps of detecting a trigger indicating RLF for the UE, subsequent to beginning transmission of the handover command, and recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers.
  • the network when it has sent (or has begun to send) a handover command to the UE, will determine that the UE has not experienced an RLF in a situation where it usually would be assumed that the UE has experienced RLF. For example, the network may, under normal circumstances, consider that an RLF has occurred for the UE if the network has performed a certain number of RLC retransmissions to the UE, e.g., 31 retransmissions (meaning 32 transmissions in total). However, if the network has sent (or begun to send) a handover command to the UE, the network may instead not consider that an RLF has occurred for the UE. Instead, the network may assume that the UE has received and executed the handover command.
  • the network may assume that the UE has received and executed the handover command.
  • the network may log this event. However, according to some embodiments, the network will not log that an RLF has happened in the event that the network has sent a handover command to the UE. In a variant of this technique, the network may consider that the RLF did indeed happen, but instead refrain from logging this RLF event. As an alternative embodiment, RLFs triggered under these circumstances are logged under a separate counter.
  • a first source network node may consider that the RLF happened if a first network sends a maximum number of RLC retransmissions of the HO command and it does not receive indication, e.g., within a certain time window, from a second target network node to which the handover was ordered that the handover was completed in a cell hosted by the second network node.
  • Figures 6 and 7 illustrate methods corresponding and generalizing these techniques.
  • an example method may comprise the step of detecting a trigger indicating RLF for the UE, subsequent to beginning transmission of a handover command or other RRC command of a predetermined type.
  • this method further comprises refraining from recording an RLF event corresponding to the trigger in a log of RLF events.
  • Figure 7 illustrates a related method, which includes, as shown at block 710, the step of detecting a trigger indicating RLF for the UE, subsequent to beginning transmission of a handover command or other RRC command of a predetermined type.
  • this method includes the further step of recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers (or with RRC commands of the predetermined type), separate from a log of RLF events not associated with handovers (or with RRC commands of the predetermined type).
  • the network node determines to release or suspend the UE (by sending the RRCRelease message) and the network node includes a redirect information (e.g., redirectedCarrierlnfo), the network node does not set the RLC poll-bit. This allows the UE to not send an RLC ACK before leaving to IDLE/INACTIVE. This has the benefit that it may speed up the release with redirect procedure.
  • a redirect information e.g., redirectedCarrierlnfo
  • FIG. 8 illustrates a diagram of a user equipment 50 configured to operate in a wireless network according to any of the techniques described above, according to some embodiments.
  • User equipment 50 may be considered to represent any wireless devices or terminals that may operate in a network, such as a UE in a cellular network.
  • Other examples may include a communication device, target device, MTC device, loT device, device to device (D2D) UE, machine type UE or UE capable of machine-to-machine communication (M2M), a sensor equipped with UE, PDA (personal digital assistant), tablet, IPAD tablet, mobile terminal, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), etc.
  • D2D device to device
  • M2M machine type UE or UE capable of machine-to-machine communication
  • PDA personal digital assistant
  • tablet IPAD tablet
  • mobile terminal smart phone
  • LEE laptop embedded equipped
  • LME laptop mounted equipment
  • CPE Customer Premise
  • User equipment 50 is configured to communicate with a network node or base station in a wide- area cellular network via antennas 54 and transceiver circuitry 56.
  • Transceiver circuitry 56 may include transmitter circuits, receiver circuits, and associated control circuits that are collectively configured to transmit and receive signals according to a radio access technology, for the purposes of using cellular communication services.
  • the radio access technology can be NR or LTE, for the purposes of this discussion.
  • User equipment 50 also includes one or more processing circuits 52 that are operatively associated with the radio transceiver circuitry 56.
  • Processing circuitry 52 comprises one or more digital processing circuits, e.g., one or more microprocessors, microcontrollers, DSPs, FPGAs, CPLDs, ASICs, or any mix thereof. More generally, processing circuitry 52 may comprise fixed circuitry, or programmable circuitry that is specially adapted via the execution of program instructions implementing the UE functionality described herein, or may comprise some mix of fixed and programmed circuitry. Processing circuitry
  • Processing circuitry 52 also includes a memory 64.
  • Memory 64 stores one or more computer programs 66 and, optionally, configuration data 68.
  • Memory 64 provides non- transitory storage for computer program 66 and it may comprise one or more types of computer- readable media, such as disk storage, solid-state memory storage, or any mix thereof.
  • memory 64 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in processing circuitry 52 and/or separate from processing circuitry 52.
  • Memory 64 may also store any configuration data 68 used by wireless device 50.
  • Processing circuitry 52 may be configured, e.g., through the use of appropriate program code stored in memory 64, to carry out one or more of the methods and/or signaling processes detailed herein.
  • Processing circuitry 52 of the user equipment 50 is configured, according to some embodiments, to perform any or all of the techniques described herein for a user equipment.
  • Network node 30 may correspond to any of the access nodes or other network nodes described herein.
  • Network node 30 may be configured to carry out one or more of the presently disclosed techniques.
  • Network node 30 may be an evolved Node B (eNodeB), Node B or gNB, for example.
  • Network node may represent a radio network node such as base station, radio base station, base transceiver station, base station controller, network controller, NR BS, Multi-cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), or a multi-standard BS (MSR BS).
  • MCE Multi-cell/multicast Coordination Entity
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • MSR BS multi-standard BS
  • network node 30 is described as being configured to operate as a cellular network access node in an LTE network or NR network, but network node 30 may also correspond to similar access nodes in other types of network.
  • Network node 30 facilitates communication between wireless terminals (e.g., UEs), other network access nodes and/or the core network.
  • Network node 30 may include communication interface circuitry 38 that includes circuitry for communicating with other nodes in the core network, radio nodes, and/or other types of nodes in the network for the purposes of providing data and/or cellular communication services.
  • Network node 30 communicates with wireless devices using antennas 34 and transceiver circuitry 36.
  • Transceiver circuitry 36 may include transmitter circuits, receiver circuits, and associated control circuits that are collectively configured to transmit and receive signals according to a radio access technology, for the purposes of providing cellular communication services.
  • Network node 30 also includes one or more processing circuits 32 that are operatively associated with the transceiver circuitry 36 and, in some cases, the communication interface circuitry 38.
  • Processing circuitry 32 comprises one or more digital processors 42, e.g., one or more microprocessors, microcontrollers, Digital Signal Processors (DSPs), Field Programmable Gate Arrays (FPGAs), Complex Programmable Logic Devices (CPLDs), Application Specific Integrated Circuits (ASICs), or any mix thereof. More generally, processing circuitry 32 may comprise fixed circuitry, or programmable circuitry that is specially configured via the execution of program instructions implementing the functionality taught herein, or some mix of fixed and programmed circuitry.
  • Processor 42 may be multi-core, i.e., having two or more processor cores utilized for enhanced performance, reduced power consumption, and more efficient simultaneous processing of multiple tasks.
  • Processing circuitry 32 also includes a memory 44.
  • Memory 44 stores one or more computer programs 46 and, optionally, configuration data 48.
  • Memory 44 provides non- transitory storage for the computer program 46 and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof.
  • “non-transitory” means permanent, semi-permanent, or at least temporarily persistent storage and encompasses both long-term storage in non-volatile memory and storage in working memory, e.g., for program execution.
  • memory 44 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in processing circuitry 32 and/or separate from processing circuitry 32.
  • Memory 44 may also store any configuration data 48 used by the network access node 30.
  • Processing circuitry 32 may be configured, e.g., through the use of appropriate program code stored in memory 44, to carry out one or more of the methods and/or signaling processes detailed hereinafter.
  • Processing circuitry 32 of the network node 30 is configured, according to some embodiments, to perform the techniques described herein for a network node, such as the first target node or second target node described in the several example techniques described above and illustrated in Figures 3-7.
  • a wireless network such as the example wireless network illustrated in Figure 10.
  • the wireless network of Figure 10 only depicts network 1406, network nodes 1460 and 1460b, and wireless devices 1410, 1410b, and 1410c.
  • a wireless network can 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 1460 and wireless device 1410 are depicted with additional detail.
  • the wireless network can 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 can 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 can be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network can 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 1406 can 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 1460 and wireless device 1410 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 can 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 can facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • 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 can be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station can be a relay node or a relay donor node controlling a relay.
  • a network node can 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 can 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 can 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 1460 includes processing circuitry 1470, device readable medium 1480, interface 1490, auxiliary equipment 1484, power source 1486, power circuitry 1487, and antenna 1462.
  • network node 1460 illustrated in the example wireless network of Figure 10 can represent a device that includes the illustrated combination of hardware components, other embodiments can 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 and/or procedures disclosed herein.
  • network node 1460 can comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 1480 can comprise multiple separate hard drives as well as multiple RAM modules).
  • network node 1460 can be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which can each have their own respective components.
  • network node 1460 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components can be shared among several network nodes.
  • a single RNC can control multiple NodeBs.
  • each unique NodeB and RNC pair can in some instances be considered a single separate network node.
  • network node 1460 can be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • some components can be duplicated (e.g., separate device readable medium 1480 for the different RATs) and some components can be reused (e.g., the same antenna 1462 can be shared by the RATs).
  • Network node 1460 can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1460, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or different chip or set of chips and other components within network node 1460.
  • Processing circuitry 1470 can be 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 1470 can include processing information obtained by processing circuitry 1470 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 1470 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 1470 can 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 1460 components, such as device readable medium 1480, network node 1460 functionality.
  • processing circuitry 1470 can execute instructions stored in device readable medium 1480 or in memory within processing circuitry 1470. Such functionality can include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry 1470 can include a system on a chip (SOC).
  • SOC system on a chip
  • processing circuitry 1470 can include one or more of radio frequency (RF) transceiver circuitry 1472 and baseband processing circuitry 1474.
  • radio frequency (RF) transceiver circuitry 1472 and baseband processing circuitry 1474 can 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 1472 and baseband processing circuitry 1474 can be on the same chip or set of chips, boards, or units.
  • processing circuitry 1470 executing instructions stored on device readable medium 1480 or memory within processing circuitry 1470.
  • some or all of the functionality can be provided by processing circuitry 1470 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry 1470 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1470 alone or to other components of network node 1460 but are enjoyed by network node 1460 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium 1480 can 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 can be used by processing circuitry 1470.
  • 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 1480 can 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 1470 and, utilized by network node 1460.
  • Device readable medium 1480 can be used to store any calculations made by processing circuitry 1470 and/or any data received via interface 1490.
  • processing circuitry 1470 and device readable medium 1480 can be considered to be integrated.
  • Interface 1490 is used in the wired or wireless communication of signalling and/or data between network node 1460, network 1406, and/or wireless devices 1410. As illustrated, interface 1490 comprises port(s)/terminal(s) 1494 to send and receive data, for example to and from network 1406 over a wired connection. Interface 1490 also includes radio front end circuitry 1492 that can be coupled to, or in certain embodiments a part of, antenna 1462. Radio front end circuitry 1492 comprises filters 1498 and amplifiers 1496. Radio front end circuitry 1492 can be connected to antenna 1462 and processing circuitry 1470. Radio front end circuitry can be configured to condition signals communicated between antenna 1462 and processing circuitry 1470.
  • Radio front end circuitry 1492 can receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 1492 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1498 and/or amplifiers 1496. The radio signal can then be transmitted via antenna 1462. Similarly, when receiving data, antenna 1462 can collect radio signals which are then converted into digital data by radio front end circuitry 1492. The digital data can be passed to processing circuitry 1470. In other embodiments, the interface can comprise different components and/or different combinations of components.
  • network node 1460 may not include separate radio front end circuitry 1492, instead, processing circuitry 1470 can comprise radio front end circuitry and can be connected to antenna 1462 without separate radio front end circuitry 1492.
  • processing circuitry 1470 can comprise radio front end circuitry and can be connected to antenna 1462 without separate radio front end circuitry 1492.
  • all or some of RF transceiver circuitry 1472 can be considered a part of interface 1490.
  • interface 1490 can include one or more ports or terminals 1494, radio front end circuitry 1492, and RF transceiver circuitry 1472, as part of a radio unit (not shown), and interface 1490 can communicate with baseband processing circuitry 1474, which is part of a digital unit (not shown).
  • Antenna 1462 can include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • Antenna 1462 can be coupled to radio front end circuitry 1490 and can be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • antenna 1462 can 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 omnidirectional antenna can be used to transmit/receive radio signals in any direction
  • a sector antenna can be used to transmit/receive radio signals from devices within a particular area
  • a panel antenna can be a line-of-sight antenna used to transmit/receive radio signals in a relatively straight line.
  • antenna 1462 can be separate from network node 1460 and can be connectable to network node 1460 through an interface or port.
  • Antenna 1462, interface 1490, and/or processing circuitry 1470 can 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 can be received from a wireless device, another network node and/or any other network equipment.
  • antenna 1462, interface 1490, and/or processing circuitry 1470 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals can be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry 1487 can comprise, or be coupled to, power management circuitry and can be configured to supply the components of network node 1460 with power for performing the functionality described herein. Power circuitry 1487 can receive power from power source 1486. Power source 1486 and/or power circuitry 1487 can be configured to provide power to the various components of network node 1460 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1486 can either be included in, or external to, power circuitry 1487 and/or network node 1460.
  • network node 1460 can 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 1487.
  • power source 1486 can comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1487. The battery can provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, can also be used.
  • network node 1460 can include additional components beyond those shown in Figure 10 that can 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 1460 can include user interface equipment to allow and/or facilitate input of information into network node 1460 and to allow and/or facilitate output of information from network node 1460. This can allow and/or facilitate a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1460.
  • a wireless device e.g., wireless device 1410 can be configured to communicate wirelessly with network nodes (e.g., 1460) and/or other wireless devices (e.g., 1410b, c). Communicating wirelessly can 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 can be configured to transmit and/or receive information without direct human interaction. For instance, a wireless device can 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 can 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 can 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 can 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 can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the wireless device can be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard.
  • NB-loT 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 can 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 can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, a wireless device as described above can be mobile, in which case it can also be referred to as a mobile device or a mobile terminal.
  • wireless device 1410 includes antenna 1411, interface 1414, processing circuitry 1420, device readable medium 1430, user interface equipment 1432, auxiliary equipment 1434, power source 1436 and power circuitry 1437.
  • Wireless device 1410 can include multiple sets of one or more of the illustrated components for different wireless technologies supported by wireless device 1410, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies can be integrated into the same or different chips or set of chips as other components within wireless device 1410.
  • Antenna 1411 can include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1414.
  • antenna 1411 can be separate from wireless device 1410 and be connectable to wireless device 1410 through an interface or port.
  • Antenna 1411, interface 1414, and/or processing circuitry 1420 can be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and/or signals can be received from a network node and/or another wireless device.
  • radio front end circuitry and/or antenna 1411 can be considered an interface.
  • interface 1414 comprises radio front end circuitry 1412 and antenna 1411.
  • Radio front end circuitry 1412 comprise one or more filters 1418 and amplifiers 1416.
  • Radio front end circuitry 1414 is connected to antenna 1411 and processing circuitry 1420 and can be configured to condition signals communicated between antenna 1411 and processing circuitry 1420.
  • Radio front end circuitry 1412 can be coupled to or a part of antenna 1411.
  • wireless device 1410 may not include separate radio front end circuitry 1412; rather, processing circuitry 1420 can comprise radio front end circuitry and can be connected to antenna 1411.
  • some or all of RF transceiver circuitry 1422 can be considered a part of interface 1414.
  • Radio front end circuitry 1412 can receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 1412 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1418 and/or amplifiers 1416. The radio signal can then be transmitted via antenna 1411. Similarly, when receiving data, antenna 1411 can collect radio signals which are then converted into digital data by radio front end circuitry 1412. The digital data can be passed to processing circuitry 1420. In other embodiments, the interface can comprise different components and/or different combinations of components.
  • Processing circuitry 1420 can 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 1410 components, such as device readable medium 1430, wireless device 1410 functionality. Such functionality can include providing any of the various wireless features or benefits discussed herein.
  • processing circuitry 1420 can execute instructions stored in device readable medium 1430 or in memory within processing circuitry 1420 to provide the functionality disclosed herein.
  • processing circuitry 1420 includes one or more of RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426.
  • the processing circuitry can comprise different components and/or different combinations of components.
  • processing circuitry 1420 of wireless device 1410 can comprise a SOC.
  • RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426 can be on separate chips or sets of chips.
  • part or all of baseband processing circuitry 1424 and application processing circuitry 1426 can be combined into one chip or set of chips, and RF transceiver circuitry 1422 can be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 1422 and baseband processing circuitry 1424 can be on the same chip or set of chips, and application processing circuitry 1426 can be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426 can be combined in the same chip or set of chips.
  • RF transceiver circuitry 1422 can be a part of interface 1414.
  • RF transceiver circuitry 1422 can condition RF signals for processing circuitry 1420.
  • processing circuitry 1420 executing instructions stored on device readable medium 1430, which in certain embodiments can be a computer-readable storage medium.
  • some or all of the functionality can be provided by processing circuitry 1420 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry 1420 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1420 alone or to other components of wireless device 1410, but are enjoyed by wireless device 1410 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry 1420 can 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 1420, can include processing information obtained by processing circuitry 1420 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 1410, 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 1420 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 1410, 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 1430 can 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 1420.
  • Device readable medium 1430 can 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 can be used by processing circuitry 1420.
  • processing circuitry 1420 and device readable medium 1430 can be considered to be integrated.
  • User interface equipment 1432 can include components that allow and/or facilitate a human user to interact with wireless device 1410. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment 1432 can be operable to produce output to the user and to allow and/or facilitate the user to provide input to wireless device 1410. The type of interaction can vary depending on the type of user interface equipment 1432 installed in wireless device 1410. For example, if wireless device 1410 is a smart phone, the interaction can be via a touch screen; if wireless device 1410 is a smart meter, the interaction can 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 1432 can include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1432 can be configured to allow and/or facilitate input of information into wireless device 1410, and is connected to processing circuitry 1420 to allow and/or facilitate processing circuitry 1420 to process the input information.
  • User interface equipment 1432 can 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 1432 is also configured to allow and/or facilitate output of information from wireless device 1410, and to allow and/or facilitate processing circuitry 1420 to output information from wireless device 1410. User interface equipment 1432 can 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 1432, wireless device 1410 can communicate with end users and/or the wireless network, and allow and/or facilitate them to benefit from the functionality described herein.
  • Auxiliary equipment 1434 is operable to provide more specific functionality which may not be generally performed by wireless devices. This can 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 1434 can vary depending on the embodiment and/or scenario.
  • Power source 1436 can, 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, can also be used.
  • Wireless device 1410 can further comprise power circuitry 1437 for delivering power from power source 1436 to the various parts of wireless device 1410 which need power from power source 1436 to carry out any functionality described or indicated herein.
  • Power circuitry 1437 can in certain embodiments comprise power management circuitry.
  • Power circuitry 1437 can additionally or alternatively be operable to receive power from an external power source; in which case wireless device 1410 can 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 1437 can also in certain embodiments be operable to deliver power from an external power source to power source 1436. This can be, for example, for the charging of power source 1436. Power circuitry 1437 can perform any converting or other modification to the power from power source 1436 to make it suitable for supply to the respective components of wireless device 1410.
  • Figure 11 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 can 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 can represent a device that is not intended for sale to, or operation by, an end user but which can be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE 1500 can be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE 1500 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.
  • 3GPP 3rd Generation Partnership Project
  • UE 1500 includes processing circuitry 1501 that is operatively coupled to input/output interface 1505, radio frequency (RF) interface 1509, network connection interface 1511, memory 1515 including random access memory (RAM) 917, read-only memory (ROM) 919, and storage medium 921 or the like, communication subsystem 931, power source 933, and/or any other component, or any combination thereof.
  • Storage medium 1521 includes operating system 1523, application program 1525, and data 1527. In other embodiments, storage medium 1521 can include other similar types of information.
  • Certain UEs can utilize all of the components shown in Figure 11, or only a subset of the components. The level of integration between the components can vary from one UE to another UE. Further, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry 1501 can be configured to process computer instructions and data.
  • Processing circuitry 1501 can 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 1501 can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.
  • input/output interface 1505 can be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE 1500 can be configured to use an output device via input/output interface 1505.
  • An output device can use the same type of interface port as an input device.
  • a USB port can be used to provide input to and output from UE 1500.
  • the output device can 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 1500 can be configured to use an input device via input/output interface 1505 to allow and/or facilitate a user to capture information into UE 1500.
  • the input device can 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 can include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor can 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 can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface 1509 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface 1511 can be configured to provide a communication interface to network 1543a.
  • Network 1543a can 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 1543a can comprise a Wi-Fi network.
  • Network connection interface 1511 can 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 1511 can implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.
  • RAM 1517 can be configured to interface via bus 1502 to processing circuitry 1501 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 1519 can be configured to provide computer instructions or data to processing circuitry 1501.
  • ROM 1519 can 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 nonvolatile memory.
  • Storage medium 1521 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives.
  • storage medium 1521 can be configured to include operating system 1523, application program 1525 such as a web browser application, a widget or gadget engine or another application, and data file 1527.
  • Storage medium 1521 can store, for use by UE 1500, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium 1521 can 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
  • HD- DVD high-density digital versatile disc
  • HD- DVD high-density digital versatile disc
  • HD- DVD high-density digital versatile disc
  • Blu-Ray optical disc drive holographic digital data storage (HDDS) optical disc drive
  • DIMM
  • Storage medium 1521 can allow and/or facilitate UE 1500 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 can be tangibly embodied in storage medium 1521, which can comprise a device readable medium.
  • processing circuitry 1501 can be configured to communicate with network 1543b using communication subsystem 1531.
  • Network 1543a and network 1543b can be the same network or networks or different network or networks.
  • Communication subsystem 1531 can be configured to include one or more transceivers used to communicate with network 1543b.
  • communication subsystem 1531 can 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.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • RAN radio access network
  • Each transceiver can include transmitter 1533 and/or receiver 1535 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 1533 and receiver 1535 of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.
  • the communication functions of communication subsystem 1531 can 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 1531 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network 1543b can 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 1543b can be a cellular network, a Wi-Fi network, and/or a near-field network.
  • Power source 1513 can be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1500.
  • communication subsystem 1531 can be configured to include any of the components described herein.
  • processing circuitry 1501 can be configured to communicate with any of such components over bus 1502.
  • any of such components can be represented by program instructions stored in memory that when executed by processing circuitry 1501 perform the corresponding functions described herein.
  • the functionality of any of such components can be partitioned between processing circuitry 1501 and communication subsystem 1531.
  • the non- computationally intensive functions of any of such components can be implemented in software or firmware and the computationally intensive functions can be implemented in hardware.
  • FIG 12 is a schematic block diagram illustrating a virtualization environment 1600 in which functions implemented by some embodiments can be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which can include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station, a virtualized radio access node, virtualized core network 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, a virtualized radio access node, virtualized core network 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 can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1600 hosted by one or more of hardware nodes 1630. 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 can be entirely virtualized.
  • the functions can be implemented by one or more applications 1620 (which can 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 1620 are run in virtualization environment 1600 which provides hardware 1630 comprising processing circuitry 1660 and memory 1690.
  • Memory 1690 contains instructions 1695 executable by processing circuitry 1660 whereby application 1620 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment 1600 comprises general-purpose or special-purpose network hardware devices 1630 comprising a set of one or more processors or processing circuitry 1660, which can 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 1660 can 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 can comprise memory 1690-1 which can be non- persistent memory for temporarily storing instructions 1695 or software executed by processing circuitry 1660.
  • Each hardware device can comprise one or more network interface controllers (NICs) 1670, also known as network interface cards, which include physical network interface 1680.
  • NICs network interface controllers
  • Each hardware device can also include non-transitory, persistent, machine-readable storage media 1690- 2 having stored therein software 1695 and/or instructions executable by processing circuitry 1660.
  • Software 1695 can include any type of software including software for instantiating one or more virtualization layers 1650 (also referred to as hypervisors), software to execute virtual machines 1640 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines 1640 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer 1650 or hypervisor. Different embodiments of the instance of virtual appliance 1620 can be implemented on one or more of virtual machines 1640, and the implementations can be made in different ways.
  • processing circuitry 1660 executes software 1695 to instantiate the hypervisor or virtualization layer 1650, which can sometimes be referred to as a virtual machine monitor (VMM).
  • VMM virtual machine monitor
  • Virtualization layer 1650 can present a virtual operating platform that appears like networking hardware to virtual machine 1640.
  • hardware 1630 can be a standalone network node with generic or specific components.
  • Hardware 1630 can comprise antenna 16225 and can implement some functions via virtualization.
  • hardware 1630 can 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) 1690, which, among others, oversees lifecycle management of applications 1620.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV).
  • NFV network function virtualization
  • NFV can 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 1640 can 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 1640, and that part of hardware 1630 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 1640, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units 16200 that each include one or more transmitters 16220 and one or more receivers 16210 can be coupled to one or more antennas 16225.
  • Radio units 16200 can communicate directly with hardware nodes 1630 via one or more appropriate network interfaces and can 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 16230 which can alternatively be used for communication between the hardware nodes 1630 and radio units 16200.
  • a communication system includes telecommunication network 1710, such as a 3GPP-type cellular network, which comprises access network 1711, such as a radio access network, and core network 1714.
  • Access network 1711 comprises a plurality of base stations 1712a, 1712b, 1712c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1713a, 1713b, 1713c.
  • Each base station 1712a, 1712b, 1712c is connectable to core network 1714 over a wired or wireless connection 1715.
  • a first UE 1791 located in coverage area 1713c can be configured to wirelessly connect to, or be paged by, the corresponding base station 1712c.
  • a second UE 1792 in coverage area 1713a is wirelessly connectable to the corresponding base station 1712a. While a plurality of UEs 1791, 1792 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 Telecommunication network 1710 is itself connected to host computer 1730, which can 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 1730 can be under the ownership or control of a service provider, or can be operated by the service provider or on behalf of the service provider. Connections 1721 and 1722 between telecommunication network 1710 and host computer 1730 can extend directly from core network 1714 to host computer 1730 or can go via an optional intermediate network 1720.
  • Intermediate network 1720 can be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1720, if any, can be a backbone network or the Internet; in particular, intermediate network 1720 can comprise two or more sub-networks (not shown).
  • the communication system of Figure 13 as a whole enables connectivity between the connected UEs 1791, 1792 and host computer 1730.
  • the connectivity can be described as an over-the-top (OTT) connection 1750.
  • Host computer 1730 and the connected UEs 1791, 1792 are configured to communicate data and/or signaling via OTT connection 1750, using access network 1711, core network 1714, any intermediate network 1720 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection 1750 can be transparent in the sense that the participating communication devices through which OTT connection 1750 passes are unaware of routing of uplink and downlink communications.
  • base station 1712 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1730 to be forwarded (e.g., handed over) to a connected UE 1791. Similarly, base station 1712 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1791 towards the host computer 1730.
  • host computer 1810 comprises hardware 1815 including communication interface 1816 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1800.
  • Host computer 1810 further comprises processing circuitry 1818, which can have storage and/or processing capabilities.
  • processing circuitry 1818 can 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 1810 further comprises software 1811, which is stored in or accessible by host computer 1810 and executable by processing circuitry 1818.
  • Software 1811 includes host application 1812.
  • Host application 1812 can be operable to provide a service to a remote user, such as UE 1830 connecting via OTT connection
  • host application 1812 can provide user data which is transmitted using OTT connection 1850.
  • Communication system 1800 can also include base station 1820 provided in a telecommunication system and comprising hardware 1825 enabling it to communicate with host computer 1810 and with UE 1830.
  • Hardware 1825 can include communication interface 1826 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1800, as well as radio interface 1827 for setting up and maintaining at least wireless connection 1870 with UE 1830 located in a coverage area (not shown in Figure 14) served by base station 1820.
  • Communication interface 1826 can be configured to facilitate connection 1860 to host computer 1810. Connection 1860 can be direct or it can pass through a core network (not shown in Figure 14) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • hardware 1825 of base station 1820 can also include processing circuitry 1828, which can 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 1820 further has software 1821 stored internally or accessible via an external connection.
  • Communication system 1800 can also include UE 1830 already referred to. Its hardware 1835 can include radio interface 1837 configured to set up and maintain wireless connection 1870 with a base station serving a coverage area in which UE 1830 is currently located. Hardware 1835 of UE 1830 can also include processing circuitry 1838, which can 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 1830 further comprises software 1831, which is stored in or accessible by UE 1830 and executable by processing circuitry 1838. Software 1831 includes client application 1832. Client application 1832 can be operable to provide a service to a human or non-human user via UE 1830, with the support of host computer 1810.
  • an executing host application 1812 can communicate with the executing client application 1832 via OTT connection 1850 terminating at UE 1830 and host computer 1810.
  • client application 1832 can receive request data from host application 1812 and provide user data in response to the request data.
  • OTT connection 1850 can transfer both the request data and the user data.
  • Client application 1832 can interact with the user to generate the user data that it provides.
  • host computer 1810, base station 1820 and UE 1830 illustrated in Figure 14 can be similar or identical to host computer 1730, one of base stations 1712a, 1712b, 1712c and one of UEs 1791, 1792 of Figure 13, respectively. This is to say, the inner workings of these entities can be as shown in Figure 14 and independently, the surrounding network topology can be that of Figure 13.
  • OTT connection 1850 has been drawn abstractly to illustrate the communication between host computer 1810 and UE 1830 via base station 1820, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure can determine the routing, which it can be configured to hide from UE 1830 or from the service provider operating host computer 1810, or both. While OTT connection 1850 is active, the network infrastructure can 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 1870 between UE 1830 and base station 1820 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 1830 using OTT connection 1850, in which wireless connection 1870 forms the last segment.
  • the exemplary embodiments disclosed herein can improve flexibility for the network to monitor end-to-end quality- of-service (QoS) of data flows, including their corresponding radio bearers, associated with data sessions between a user equipment (UE) and another entity, such as an OTT data application or service external to the 5G network.
  • QoS quality- of-service
  • a measurement procedure can be provided for the purpose of monitoring data rate, latency and other network operational aspects on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection 1850 can be implemented in software 1811 and hardware 1815 of host computer 1810 or in software 1831 and hardware 1835 of UE 1830, or both.
  • sensors can be deployed in or in association with communication devices through which OTT connection 1850 passes; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 1811, 1831 can compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection 1850 can include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1820, and it can be unknown or imperceptible to base station 1820. Such procedures and functionalities can be known and practiced in the art.
  • measurements can involve proprietary UE signaling facilitating host computer 1810's measurements of throughput, propagation times, latency and the like. The measurements can be implemented in that software 1811, 1831 causes messages to be transmitted, in particular empty or 'dummy' messages, using OTT connection 1850 while it monitors propagation times, errors, etc.
  • FIG. 15 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which, in some exemplary embodiments, can be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section.
  • the host computer provides user data.
  • substep 1911 (which can be optional) of step 1910, 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 1930 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 1940 the UE executes a client application associated with the host application executed by the host computer.
  • FIG 16 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which can 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.
  • 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 can pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step 2030 (which can be optional), the UE receives the user data carried in the transmission.
  • FIG 17 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which can 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.
  • step 2110 the UE receives input data provided by the host computer. Additionally or alternatively, in step 2120, the UE provides user data.
  • substep 2121 (which can be optional) of step 2120, the UE provides the user data by executing a client application.
  • substep 2111 (which can be optional) of step 2110, 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 can further consider user input received from the user.
  • the UE initiates, in substep 2130 (which can be optional), transmission of the user data to the host computer.
  • step 2140 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.
  • FIG 18 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which can 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.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step 2230 (which can be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • the exemplary embodiments described herein provide techniques for pre-configuring a UE for operation in a 3GPP non-terrestrial network (NTN). Such embodiments reduce the time needed for initial acquisition of an NTN (e.g., PLMN) and a cell within the NTN. This can provide various benefits and/or advantages, including reducing UE energy consumption (or, equivalently, increasing UE operational time on one battery charge) and improving user access to services provided by an NTN.
  • exemplary embodiments described herein can enable UEs to access network resources and OTT services more consistently and without interruption. This improves the availability and/or performance of these services as experienced by OTT service providers and end-users, including more consistent data throughout and fewer delays without excessive UE power consumption or other reductions in user experience.
  • Embodiments of the presently disclosed techniques and apparatuses include, but are not limited to, the following examples: a.
  • a method, in a network node operating in a wireless network comprising: transmitting, to a user equipment, UE, a message containing or concluding a Radio Resource Control, RRC, command of a predetermined type; and applying a first predetermined maximum number of radio link control, RLC, retransmissions to retransmissions of at least one RLC packet data unit, PDU, associated with the message, wherein the first predetermined maximum number differs from a second predetermined maximum number of RLC retransmissions applicable to RLC PDUs not associated with a message containing or concluding a RRC command of the predetermined type.
  • RRC Radio Resource Control
  • b The method of example embodiment (a), wherein the predetermined type is a handover command.
  • the predetermined type is one of a plurality of types to which the first predetermined maximum number of RLC retransmissions is applicable, the plurality of types being a proper subset of RRC commands.
  • d The method of any of example embodiments (a)-(c), wherein the first predetermined maximum number is less than the second predetermined maximum number.
  • the at least one RLC PDU associated with the message comprises an RLC PDU transmitted within a predetermined time window around the transmission of the message.
  • a method, in a first network node operating in a wireless network comprising: determining that a user equipment, UE, served by the first network node has been handed over or is being handed over to a second network node; and adjusting a retransmission process directed towards the UE, in response to said determining.
  • said determining comprises receiving, from the second network node, an indication that the UE has been handed over or is being handed over to the second network node; and said adjusting comprises aborting an ongoing retransmission process directed towards the UE in response to receiving the indication.
  • a method in a first network node operating in a wireless network, the method comprising: transmitting a Radio Link Control, RLC, packet data unit, PDU, to a user equipment, UE; receiving a medium access control, MAC, hybrid automatic-repeat-request, HARQ acknowledgement, the MAC HARQ.
  • RRC Radio Resource Control
  • RRC Radio Resource Control
  • y The method of example embodiment (w), wherein the predetermined type is a handover command.
  • a network node for operation in a wireless network the network node being adapted to carry out a method according to any one of example embodiments (a)-(x).
  • z A network node for operation in a wireless network, the network node comprising: radio circuitry configured to communicate with a user equipment, UE; and processing circuitry operatively connected to the radio circuitry and configured to cause the network node to carry out a method according to any one of example embodiments l-(a)-(x).
  • aa A computer program product comprising program instructions for execution by a processing circuit in a network node, the program instructions being configured to cause the network node to carry out a method according to any one of example embodiments (a)-(x).
  • a computer-readable medium comprising, stored thereupon, the computer program product of example embodiment (aa).
  • the term unit can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can 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.
  • any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses.
  • Each virtual apparatus may comprise a number of these functional units.
  • These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (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 (RAM), 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.
  • the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
  • device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor.
  • functionality of a device or apparatus can be implemented by any combination of hardware and software.
  • a device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other.
  • devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.

Landscapes

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

Abstract

An example method is carried out in a network node, such as a base station (e.g., gNB or eNB), operating in a wireless network. This example method comprises the step of transmitting (310), to a UE, a message containing or concluding a RRC command of a predetermined type, where this predetermined type might be, for example, a handover command. The method further comprises applying (320) a first predetermined maximum number of RLC retransmissions to retransmissions of at least one RLC PDU associated with the message, where the first predetermined maximum number differs from a second predetermined maximum number of RLC retransmissions applicable to RLC PDUs not associated with a message containing or concluding an RRC command of the predetermined type.(Fig. 3)

Description

HANDLING OF MISSING HANDOVER RADIO LINK CONTROL (RLC) ACKNOWLEDGEMENTS
TECHNICAL FIELD
The present disclosure is generally related to wireless communications networks and is more particularly related to the handling of radio link control (RLC) acknowledgements in such networks.
BACKGROUND
Figure 1 illustrates a simplified wireless communication system, with a user equipment (UE) 102 that communicates with one or multiple network nodes 103, 104, which in turn are connected to another network node 106. Network nodes 103, 104, which may be considered access nodes and which may be referred to as base stations, are part of the radio access network (RAN) 100. The other network node 106 may be, for example, part of a core network.
For wireless communication systems confirming to the 3rd Generation Partnership Project (3GPP) specifications for the Evolved Packet System (EPS), also referred to as Long Term Evolution (LTE) or 4G, as specified in 3GPP TS 36.300 and related specifications, the network nodes 103, 104 correspond typically to base stations referred to in 3GPP specifications as Evolved NodeBs (eNBs), while the network node 106 corresponds typically to either a Mobility Management Entity (MME) and/or a Serving Gateway (SGW). The eNB is part of the RAN 100, which in this case is the E-UTRAN (Evolved Universal Terrestrial Radio Access Network), while the MME and SGW are both part of the EPC (Evolved Packet Core network). The eNBs are inter-connected via the X2 interface, and connected to EPC via the SI interface, more specifically via Sl-C to the MME and Sl-U to the SGW.
On the other hand, for wireless communication systems pursuant to 3GPP specifications for the 3GPP 5G System, 5GS (also referred to as New Radio, NR, or 5G), as specified in 3GPP TS 38.300 and related specifications, the network nodes 103, 104 correspond typically to base stations referred to as 5G NodeBs, or gNBs, while the network node 106 corresponds typically to either an Access and Mobility Management Function (AMF) and/or a User Plane Function (UPF). In this example, the gNB is part of the RAN 100, which in this case is the NG-RAN (Next Generation Radio Access Network), while the AMF and UPF are both part of the 5G Core Network (5GC). The gNBs are inter-connected via the Xn interface, and connected to 5GC via the NG interface, more specifically via NG-C to the AMF and NG-U to the UPF.
The specifications for both NR and LTE define a Radio Link Control (RLC) protocol, to be carried out by corresponding RLC entities in the gNB or eNB and the UE. The RLC protocol is responsible for transfer of upper layer packet data units (PDUs) in either acknowledged mode (AM), unacknowledged mode (UM), and transparent mode (TM). In AM, the RLC protocol also provides for error correction via retransmission of lost RLC PDUs, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs when a complete RLC PDU cannot be transmitted (AM), and reordering of RLC data PDUs.
As defined for both LTE and NR, the default behavior for a receiving RLC entity is to acknowledge a poll from the transmitting RLC entity with a status report (SR), which informs the transmitting RLC entity of which RLC PDUs have been received. This information is used by the transmitting RLC entity to determine whether the receiving RLC entity has received the transmitted data or higher layer signaling message or whether an RLC retransmission is necessary. However, this rule has exceptions as outlined below.
Handover is a procedure whereby a user equipment (UE) connected to a first cell gets directed to connect to another cell, instead. The purpose of handover is to move the UE from a source access node using a source radio connection (also known as source cell connection), to a target access node, using a target radio connection (also known as target cell connection). The handover may be caused by movement of the UE, for example, or for other reasons where the target cell is better positioned to serve the UE. The source radio connection is associated with a source cell controlled by the source access node. The target radio connection is associated with a target cell controlled by the target access node. In other words, during a handover, the UE moves from the source cell to a target cell. Sometimes the source access node or the source cell is referred to as the "source", and the target access node or the target cell is sometimes referred to as the "target". The source access node and the target access node may also be referred to as the source node and the target node, the source radio network node and the target radio network node or the source gNB and the target gNB.
In some cases, the source access node and target access node are different nodes, such as different eNBs or gNBs. These cases are also referred to as inter-node handover, inter-eNB handover or inter-gNB handover. In other cases, the source access node and target access node are the same node, such as the same eNB and gNB. These cases are also referred to as intra-node handover, intra-eNB handover or intra-gNB handover and covers the case then source and target cells are controlled by the same access node. In yet other cases, handover is performed within the same cell (and thus also within the same access node controlling that cell) - these cases are also referred to as intra-cell handover. It should therefore be understood that the terms "source access node" and "target access node" each refer to a role served by a given access node during a handover of a specific UE. For example, a given access node may serve as source access node during handover of one UE, while it also serves as the target access node during handover of a different UE. And, in the case of an intranode or intra-cell handover of a given UE, the same access node serves both as the source access node and target access node for that UE.
An inter-node handover can further be classified as an Xn-based or NG-based handover, depending on whether the source and target node communicate directly using the Xn interface or indirectly via the core network using the NG interface.
An RRC_CONNECTED UE in E-UTRAN or NG-RAN can be configured by the network to perform measurements of serving and neighbor cells and based on the measurement reports sent by the UE, the network may decide to perform a handover of the UE to a neighbor cell. The network then sends a Handover Command message to the UE (in LTE an RRConnectionReconfiguration message with a field called mobilityControilnfo and in NR an RRCReconfiguration message with a reconfig ura tion WithSyn c f i e I d ) .
These reconfigurations are prepared by the target access node upon a request from the source access node (over X2 or SI interface in case of EUTRA-EPC or Xn or NG interface in case of NG- RAN-5GC) and take into account the existing Radio Resource Control (RRC) configuration and UE capabilities, as provided in the request from the source access node, as well as the capabilities and resource situation in the intended target cell and target access node. The reconfiguration parameters provided by the target access node contain, for example, information needed by the UE to access the target access node, e.g., random access configuration, a new C-RNTI assigned by the target access node, and security parameters enabling the UE to calculate new security keys associated to the target access node so the UE can send a Handover Complete message (in LTE an RRConnectionReconfiguratioComplete message and in NR an RRCReconfigurationComplete message) on SRB1 encrypted and integrity protected based on new security keys upon accessing the target access node.
Figure 2 shows the signaling flow between the UE and source and target access node during an Xn- based inter-node handover in NR. Similar steps take place during an LTE handover. This might be regarded as the "legacy" handover procedure, i.e., a handover procedure that does not utilize "make-before-break" techniques and does not incorporate the various techniques described herein. Details of the steps shown in Figure 2, which can be divided into handover preparation 212, handover execution 213, and handover completion 214, are provided below.
201-202. The UE and source gNB have an established connection and are exchanging user data. Due to some trigger, e.g., a measurement report from the UE, the source gNB decides to handover the UE to the target gNB.
203. The source gNB sends a HANDOVER REQUEST message to the target gNB with necessary information to prepare the handover at the target side. The information includes, among other things, the current source configuration and the UE capabilities.
204. The target gNB prepares the handover and responds with a HANDOVER REQUEST ACKNOWLEDGE message to the source gNB, which includes the handover command (a RRCReconfiguration message containing the reconfigurationWithSync field) to be sent to the UE. The handover command includes information needed by the UE to access the target cell, e.g., random access configuration, a new C-RNTI assigned by the target access node and security parameters enabling the UE to calculate the target security key so the UE can send the handover complete message (a RRCReconfigurationComplete message).
If the target gNB does not support the release of RRC protocol that the source gNB used to configure the UE, the target gNB may be unable to comprehend the UE configuration provided by the source eNB in the HANDOVER REQUEST. In this case, the target gNB can use so-called "full configuration" to reconfigure the UE for handover. Full configuration option includes an initialization of the radio configuration, which makes the procedure independent of the configuration used in the source cell. Otherwise, the target node uses so-called "delta configuration," where only the delta to the radio configuration in the source cell is included in the handover command. Delta configuration typically reduces the size of the handover command, which increases the speed and robustness of the handover.
205. The source gNB triggers the handover by sending the handover command received from the target node in the previous step to the UE.
206. Upon reception of the handover command the UE releases the connection to the old cell before synchronizing and connecting to the new cell. 207-209. The source gNB stops scheduling any further DL or UL data to the UE and sends a SN STATUS TRANSFER message to the target gNB, the message indicating the latest PDCP SN transmitter and receiver status. The source node now also starts to forward user data to the target node, which buffers this data for now.
210. Once the UE the has completed the random access to the target cell, the UE sends the handover complete to the target gNB.
211. Upon receiving the handover complete message, the target node can start exchanging user data with the UE. The target node also requests the AMF to switch the DL data path from the UPF from the source node to the target node (not shown). Once the path switch is completed the target node sends the UE CONTEXT RELEASE message to the source node.
When the UE has received a handover command (e.g., in NR this corresponds to an RRCReconfiguration message including the IE ReconfigurationWithSync, while in LTE this corresponds to an RRCConnectionReconfiguration message including the IE MobilityControilnfo), the UE executes the handover and moves to the target cell. In general, the expected behavior on RLC level when user data or higher layer signaling messages such as RRC messages are carried over RLC Acknowledged Mode (AM) is that the receiving RLC entity at the UE sends a Status Report (SR) whenever it receives an RLC PDU that has the poll bit set in the RLC header. However, according to wording in the NR RRC specification, there is an exception to this rule, with this exception allowing the UE to execute the handover and move to the target cell directly, without sending an SR in response to the polled RLC PDU. Similar wording is also present in the LTE RRC specifications 3GPP TS 36.331 (vl6.2.0), where it is stated that if the UE receives an RRCConnectionReconfiguration message including the mobilityControilnfo then the UE may leave the source cell without ACKing on the RLC level, even if polled as specified in section 5.3.5.4 note 1:
- begin specification excerpt -
1> start synchronising to the DL of the target PCell;
NOTE 1: The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARO, and ARQ.) of this message.
- enc| specification excerpt -
The RLC protocol in NR and LTE has retransmission functionality. If the link is configured to use RLC
AM mode, which is how a handover command is delivered by lower layers, the transmitter retransmits RLC packets to the receiver until the receiver has indicated successful reception of the packet, via an SR. Notice that in a handover situation there may be a higher likelihood that a retransmission is needed, since radio conditions with the serving cell may start to degrade when the network determines to handover the UE.
A UE which is connected to a network will monitor for the occurrence of so-called Radio Link Failure (RLF), based on certain triggers. These triggers indicate that a failure on the radio link has occurred. There are several of those triggers, one of them being that a certain number of RLC retransmissions has been performed, which indicates that there is a problem getting packets transmitted over the link. In 3GPP TS 38.331 this is specified as follows:
- begin specification excerpt -
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, T311 nor T319 are running; or
1> upon indication from MCG RLC that the maximum number of retransmissions has been reached:
2> if the indication is from MCG RLC and 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.5 to report RLC failure.
2> else:
3> consider radio link failure to be detected for the MCG i.e. RLF;
[-.]
3> else if AS security has been activated but SRB2 and at least one DRB have not been setup:
4> perform the actions upon going to RRCJDLE as specified in 5.3.11, with release cause 'RRC connection failure';
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 the indication is from SCG RLC and 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.5 to report RLC failure. 2> else:
3> consider radio link failure to be detected for the SCG, i.e. SCG RLF;
3> initiate the SCG failure information procedure as specified in 5.7.3 to report SCG radio link failure.
- enc| specification excerpt -
When any of those triggers occur, the UE will declare that the radio link has failed, and the UE will then attempt to reconnect to the network. Under normal situations, this reconnecting happens by the UE trying to reestablish the connection by selecting the best cell and then initiating a reestablishment procedure towards that cell.
The network may determine whether an RLF event has occurred for the UE. The network may do this to be in-synch with the UE with regards to the state the UE is in. Also, the network may log this event, i.e., the event that the network assumes that an RLF event has happened for the UE. This information may be used to set parameters, or for troubleshooting, etc.
The network may release the RRC connection for the UE. The network can do this by sending an RRC release message. If that RRC release message contains a "suspendConfig" indication the UE will go to the RRC INACTIVE state, otherwise the UE will go to RRC IDLE state. In both these states the UE has no active connection with any gNB. This state saves power in the UE and network resources, for example.
Below is an excerpt from the 3GPP TS 38.331 V16.2.0 specification describing the UE behavior with regards to receiving the RRC release message:
- begin specification excerpt -
5.3.8.3 Reception of the RRCRelease by the UE
The UE shall:
1> delay the following actions defined in this sub-clause 60 ms from the moment the RRCRelease message was received or optionally when lower layers indicate that the receipt of the RRCRelease message has been successfully acknowledged, whichever is earlier; 1> if the RRCRelease includes suspendConfig:
[-.]
2> enter RRCJNACTIVE and perform cell selection as specified in TS 38.304 [20];
1> else
2> perform the actions upon going to RRCJDLE as specified in 5.3.11, with the release cause 'other'.
- enc| specification excerpt -
As can be seen, the UE will delay the entering to RRC INACTIVE and RRC IDLE by sixty milliseconds, or until the UE has acknowledged the reception of the RRC release message.
The release message may further include redirect-information. This information can include redirection-information which indicates to the UE that the UE shall, when moving to IDLE/INACTIVE, select a certain frequency that the network has selected.
SUMMARY
As described above, the UE is allowed to execute a handover directly, without requirements on sending either RLC or HARQ. feedback to the network for the message containing the handover command. This means that the network may be unaware of whether the UE has received the handover command. This ambiguity may result in that the network assumes that the UE has not received the handover command, and hence the network will attempt many retransmissions of the message carrying the handover command, e.g., as many as 32 retransmissions. This represents a waste of radio resources on the network side, an increased interference generation (as signals are transmitted over the air even though the UE may not be listening to it), and an unnecessary expenditure of network energy.
Embodiments of the techniques and apparatus described in detail below address this problem by aborting RLC retransmission processes or reducing a number of RLC retransmissions, under certain circumstances. While several of these techniques are described below in the context of a handover procedure, it will be appreciated that these techniques may be applied in connection with other types of RRC commands as well.
An example method, according to some embodiments of the techniques described below, is carried out in a network node, such as a base station (e.g., gNB or eNB), operating in a wireless network. This example method comprises the step of transmitting, to a UE, a message containing or concluding a RRC command of a predetermined type, where this predetermined type might be, for example, a handover command. The method further comprises applying a first predetermined maximum number of RLC retransmissions to retransmissions of at least one RLC PDU associated with the message, where the first predetermined maximum number differs from a second predetermined maximum number of RLC retransmissions applicable to RLC PDUs not associated with a message containing or concluding an RRC command of the predetermined type.
Another example method, according to other embodiments described below, is also carried out in a network node, such as a base station (e.g., gNB or eNB), operating in a wireless network. According to this example method, the first network node determines that a UE served by the first network node has been handed over or is being handed over to a second network node. In response, the first network node adjusts a retransmission process directed towards the UE, in response to said determining, e.g., by reducing or eliminating retransmissions.
Still another example method, according to other embodiments described below, is likewise carried out in a first network node operating in a wireless network. This method comprises transmitting a RLC PDU to a UE and receiving a medium access control (MAC) hybrid automatic-repeat-request (HARQ) acknowledgement, the MAC HARQ acknowledgement indicating that a MAC PDU corresponding to the RLC PDU was successfully decoded. This method further comprises aborting an RLC retransmission process for the RLC PDU, in response to said receiving.
Another example method, again implemented by a first network node operating in a wireless network, comprises the step of detecting a trigger indicating RLF for a UE, subsequent to beginning transmission of a RRC command of a predetermined type to the UE. This predetermined type may be a handover command, for example. This example method further comprises refraining from recording an RLF event corresponding to the trigger in a log of RLF events.
Yet another example method, once more implemented by a first network node operating in a wireless network, similarly comprises the step of detecting a trigger indicating RLF for a UE, subsequent to beginning transmission of a RRC command of a predetermined type to the UE. This example method comprises the step of recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers.
These example methods and variants thereof are described in detail below and illustrated in the accompanying figures. Corresponding apparatuses and systems are also described.
BRIEF DESCRIPTION OF THE FIGURES
Figure 1 is a simplified illustration of a wireless communication system. Figure 2 illustrates handover in NR.
Figures 3, 4, 5, 6, and 7 illustrate example methods according to various exemplary embodiments of the present disclosure.
Figure 8 is a block diagram illustrating an example UE.
Figure 9 is a block diagram illustrating an example network node.
Figure 10 is a block diagram of an exemplary wireless network configurable according to various exemplary embodiments of the present disclosure.
Figure 11 is a block diagram of an exemplary user equipment (UE) configurable according to various exemplary embodiments of the present disclosure.
Figure 12 is a block diagram of illustrating a virtualization environment that can facilitate virtualization of various functions implemented according to various exemplary embodiments of the present disclosure.
Figures 13 and 14 are block diagrams of exemplary communication systems configurable according to various exemplary embodiments of the present disclosure.
Figures 15, 16, 17, and 18 are flow diagrams illustrating various exemplary methods and/or procedures implemented in a communication system, according to various exemplary embodiments of the present disclosure.
DETAILED DESCRIPTION
As noted above, embodiments of the techniques and apparatus described in detail below address a problem where a network node may fail to receive an RLC acknowledgement for an RRC command under circumstances where it is not clear whether it would be useful to continue RLC processes for the RRC command or related PDUs. According to several embodiments described herein, this problem is addressed by aborting RLC retransmission processes or reducing a number of RLC retransmissions, under certain circumstances. While several of these techniques are described below in the context of a handover procedure, it will be appreciated that these techniques may be applied in connection with other types of RRC commands as well.
According to various embodiments detailed below, the network (e.g., a gNB or eNB) does any one or more of the following: • Applies a different (lower) number of retransmissions for handover commands (and transmissions close to the handover command).
• Aborts retransmissions based on an indication (e.g., from another node) that the UE has performed (or has started to perform) the handover.
• Aborts RLC retransmissions based on HARQ. ACKs.
• Adjusts RLF logging.
Using the presently disclosed techniques, unnecessary retransmissions to the UE in case a handover has been initiated may be avoided. Consequently, there is no waste (or reduced waste) of radio resources on the network side, no (or reduced) increase in interference generation, and no (or reduced) unnecessary expenditures of network energy. Also, logging of RLF events is not obscured by the situation where the UE has been provided with a handover command and, for that reason, the UE does not respond. Still further, resources in the source node are not tied up with unnecessary retransmissions to a UE that has already dropped the connection to the source node.
In the description of the several techniques provided herein, various behaviors the network may apply for transmission that include or contain a handover command are described. It should be noted that in the case where a handover command is segmented, the presently disclosed techniques may be implemented so that the network only applies the disclosed methods for the transmissions containing a last segment of the handover command. In that case, the other transmissions (containing non-final segments of the handover command) would in this sense not contain a handover command." This situation may be addressed herein by referring to a message (such as an RLC PDU) that contains or completes a handover message (or other RRC command).
The description herein describes behavior regarding a handover, which corresponds to a reconfiguration with sync procedure (as defined in 3GPP TS 38.331, the NR RRC specifications). This also comprises the case where the source and target cells are associated to a Secondary Node(s) for a UE configured with MR-DC.
Also, an example scenario where the embodiments below can be applied is for the (normal) handover scenario where the network sends a handover command to the UE and the UE applies that command in response to the reception of the command. However, some of the techniques described herein can also be applied in the scenario of a conditional handover. For example, described below is how the source cell may stop sending RLC retransmissions to a UE when the network gets an indication from a target node that the UE has (or is in the process of) performed a handover. This can be applied also in the case of conditional handover and can then be applied to transmissions the network has performed/initiated close in time to the execution of the conditional handover. Further, in cases when the UE refrains from sending acknowledgements for transmissions that the UE received shortly before a normal handover, the techniques described herein could also be applied also for those transmissions. (Note, however, that based on current NR specifications, the UE behavior mandated by the 3GPP standards is conflicting regarding whether the UE must send acknowledgements for data received prior to the handover. The techniques described herein could be applied in the event any restriction is lifted.)
Note that in handover, the UE is handed over from one cell to another. The cell that the UE moves from is sometimes referred to as the source cell while the cell that the UE is moved to is sometimes referred to as the target cell. In a special case, these two cells can be associated with the same network node (intra-node handover), and in some special cases they can even be the same cell (intra-cell handover).
According to one technique, the network may apply a first number of maximum RLC retransmissions value for a transmission containing a handover command, and a second number of maximum RLC retransmissions value for a transmission does not contain a handover command. For example, the network may apply 31 retransmissions (i.e., 32 total transmissions) for transmissions that do not contain or complete a handover command but only two retransmissions (i.e., three total transmissions) for transmissions that contain or complete a handover command. The network may apply the same behavior (i.e., a different number of RLC retransmissions) for transmissions that are performed close in time to the transmission of the handover command, e.g., within a predetermined time window before and after the transmission of the handover command.
Figure 3 is a process flow diagram illustrating an example method that may be considered a generalization of the technique described immediately above. This method may be carried out by a network node operating in a wireless network, such as an LTE eNB or an NR gNB.
As shown at block 310, the method comprises the step of transmitting, to a UE, a message containing or concluding an RRC, command of a predetermined type. Note that the term "UE" as used herein refers to any access terminal or end-user terminal, whether or not it is compliant with 3GPP specifications for such devices.
As shown at block 320, the method further comprises applying a first predetermined maximum number of RLC retransmissions to retransmissions of at least one RLC PDU associated with the message, where this first predetermined maximum number differs from a second predetermined maximum number of RLC retransmissions applicable to RLC PDUs not associated with a message containing or concluding a RRC command of the predetermined type.
As in the specific examples described above, the predetermined type of RRC command may be a handover command. However, the technique may be applied to one or more other types, in addition to or instead of the handover command. Thus, the predetermined type may be one of a plurality of types to which the first predetermined maximum number of RLC retransmissions is applicable, the plurality of types being a proper subset of RRC commands, i.e., consisting of some but fewer than all, RRC commands.
In some embodiments, the first predetermined maximum number is less than the second predetermined maximum number. The first predetermined maximum number may be 2, for example, while the second predetermined maximum number may be 16, or 32, in various examples.
In some embodiments or instances, the at least one RLC PDU associated with the message comprises an RLC PDU that forms all or part of the message. In some embodiments, the at least one RLC PDU associated with the message comprises an RLC PDU that forms all or part of a second message containing a portion of the RRC command. In some embodiments or instances, for example, a handover command may be fully contained within an RLC PDU. In other embodiments, the handover command or other RRC command may be carried by multiple RLC PDUs. In various instances or embodiments, the first predetermined maximum number may be applied to all of these multiple RLC PDUs, or only to the one concluding the command.
The first predetermined maximum number of retransmissions may be applied to RLC PDUs around the RLC PDU containing or completing the handover command or other RRC command, in some embodiments or instances. Thus, in some embodiments of the method shown in Figure 3, the at least one RLC PDU associated with the message comprises an RLC PDU transmitted within a predetermined time window around the transmission of the message.
Other techniques that will be described more fully below may be combined with the method shown in Figure 3. Thus, for example, the steps shown in Figure 3 may be followed by the steps of detecting a trigger indicating radio link failure (RLF) for the UE, subsequent to beginning transmission of the handover command, and refraining from recording an RLF event corresponding to the trigger in a log of RLF events. In a similar example, the steps shown in Figure 3 may be followed by the steps of detecting a trigger indicating RLF for the UE, subsequent to beginning transmission of the handover command, and recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers. According to another technique, which may be combined with those described above, a network node may abort sending retransmissions to a UE (e.g., for transmissions containing or completing a handover command) if the network node receives an indication from another network node (e.g., a target node) that another network node would send (at least) in response to that the UE has performed (or is in the process of performing) a handover to that other network node. That message can be a Handover Success message or another message that the target node sends in response to the UE performing the handover to the target node. This approach has the benefit that the network may continue to perform retransmissions to the UE until it is certain that the UE has received the handover command.
In one variation of this embodiment, in the event of handover to another cell that is controlled by the same network node, the network node will, in response to determining that the UE has performed (or is in the process of performing) a handover to that other cell of the same network node, abort (or refrain from) retransmissions.
In another variant, the network adjusts its RLC behavior when it transmits a HO command to the UE. Upon determining to transmit a handover command, the node determining the handover, e.g., placed at a Central Unit (CU) hosting the RRC entity and handover algorithm, may indicate to the RLC entity, e.g., placed at a Distributed Unit (DU), hosting the RLC entity, that a handover command is being submitted, hence, the UE may leave, hence, the RLC entity should not perform retransmissions and/or adjust its RLC retransmission behavior (e.g., decrease the number of retransmissions).
In another variant, the network adjusts its RLC behavior when it transmits a HO request command to a target cell X, while the serving cell still has good enough quality / radio conditions (e.g., SINR and/or RSRP and/or RSRQ.) above a certain threshold. That threshold for serving cell quality indicates that retransmissions are not expected to be required (e.g., based on statistics), as in good radio conditions with serving cell the UE should successfully receive the HO without the need for RLC retransmissions. Hence, upon determining to transmit a handover command, and upon determining that the serving cell quality is above a threshold, the node initiating the handover, e.g., placed at a Central Unit (CU), hosting the RRC entity and handover algorithm, may indicate to the RLC entity, e.g. placed at a Distributed Unit (DU) hosting the RLC entity, that a handover command is being submitted and that the UE may leave, and that retransmissions should not be required, hence, the RLC entity should not perform retransmissions and/or adjust its RLC retransmission behavior (e.g., decrease the number of retransmissions). Figure 4 is a process flow diagram illustrating an example method that may be considered a generalization of several of the techniques described immediately above. Again, this method may be carried out by a network node operating in a wireless network, such as an LTE eNB or an NR gNB.
As shown at block 410, the illustrated method includes the step of determining that a UE served by the first network node has been handed over or is being handed over to a second network node. As shown at block 420, the method further includes the step of adjusting a retransmission process directed towards the UE, in response to said determining.
In some embodiments or instances, the determining shown at block 410 comprises receiving, from the second network node, an indication that the UE has been handed over or is being handed over to the second network node. In some of these embodiments, the adjusting shown at block 420 comprises aborting an ongoing retransmission process directed towards the UE in response to receiving the indication.
In other embodiments or instances, the determining shown at block 410 comprises determining to initiate a handover of the UE to the second network node and the adjusting shown at block 420 comprises reducing or eliminating retransmissions for one or more transmissions to the UE. In some of these embodiments or instances, the adjusting is further in response to determining that a quality of the link between the UE and the first network node is above a predetermined threshold.
Other techniques that will be described more fully below may be combined with the method shown in Figure 4. Thus, for example, the steps shown in Figure 4 may be followed by the steps of detecting a trigger indicating radio link failure (RLF) for the UE, subsequent to beginning transmission of the handover command, and refraining from recording an RLF event corresponding to the trigger in a log of RLF events. In a similar example, the steps shown in Figure 4 may be followed by the steps of detecting a trigger indicating RLF for the UE, subsequent to beginning transmission of the handover command, and recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers.
According to another technique, a network node aborts sending retransmissions to a UE (e.g., for transmissions containing a handover command) when determining that the UE has sent HARQ. feedback indicating that the UE has successfully decoded the transmission that contains a handover command (or other RRC command of a predetermined type). In one variation of this embodiment, in the event that the handover command is segmented into more than one MAC PDUs, i.e., transport blocks (TBs), the network node aborts sending retransmissions of the HO command when determining that the UE sends an HARQ. feedback indicating that the UE has successfully decoded the last segment, i.e., the last MAC PDU/TB, of the transmission that contains a handover command. In a manner similar to that described above, for the techniques where the retransmissions are aborted upon determining that the handover is completed the node determining the handover, e.g., placed at a Central Unit (CU), hosting the RRC entity and handover algorithm, may indicate to the RLC entity (e.g., placed at a Distributed Unit (DU), hosting the RLC entity, that a handover command is being submitted. The RLC entity in turn may inform the MAC entity that a certain RLC PDU contains the handover command or a segment of the handover command, or the last segment of the handover command. Upon receiving an HARQ feedback indicating that the UE has successfully decoded the transmission which contains a handover command or which contains the last segment of the handover command, the MAC entity informs the RLC entity, which in turn will abort sending RLC retransmissions.
In another variation of this embodiment, the network node ensures that the resource in which the HARQ. feedback for the handover command is transmitted by the UE occurs in the time domain earlier than when the UE is expected to complete the processing of the HO command. For example, if a UE is expected to process the handover command in 10 milliseconds after reception, the network may provide a KI value in the Physical Downlink Shared Channel (PDSCH) carrying the handover command, such that the uplink slot in which the corresponding HARQ feedback shall be transmitted occurs earlier than 10 milliseconds after the reception of the handover command, i.e., Kl<10. In this way, the network ensures that if the UE has correctly received the handover command, the UE will manage to send at least an HARQ feedback before initiating the handover towards a target cell. As a sub-embodiment of this embodiment, the network node keeps sending RLC retransmissions of the handover command either until a HARQ ACK feedback is received or until the maximum amount of RLC retransmissions are performed.
Note that in NR and LTE there are two levels or transmission protocols: the RLC retransmission protocol and the HARQ retransmission protocol. According to the techniques described just above, the network would, in response to an ACK on the HARQ level, determine to not send any more RLC retransmissions for the message containing the handover command.
Figure 5 is a process flow diagram illustrating an example method that may be considered a generalization of several of the techniques described immediately above. Again, this method may be carried out by a network node operating in a wireless network, such as an LTE eNB or an NR gNB.
As shown in block 510, the illustrated method comprises the step of transmitting a RLC PDU to a UE.
This RLC PDU may contain or complete a handover command, for example. As shown in block 520, the illustrated method further comprises receiving a MAC HARQ acknowledgement, the MAC HARQ. acknowledgement indicating that a MAC PDU corresponding to the RLC PDU was successfully decoded. The method further comprises, as shown at block 530, the step of aborting an RLC retransmission process for the RLC PDU, in response to said receiving.
Again, other techniques that will be described more fully below may be combined with the method shown in Figure 5. Thus, for example, the steps shown in Figure 5 may be followed by the steps of detecting a trigger indicating radio link failure (RLF) for the UE, subsequent to beginning transmission of the handover command, and refraining from recording an RLF event corresponding to the trigger in a log of RLF events. In a similar example, the steps shown in Figure 5 may be followed by the steps of detecting a trigger indicating RLF for the UE, subsequent to beginning transmission of the handover command, and recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers.
As suggested above, according to some embodiments of the presently disclosed techniques, the network, when it has sent (or has begun to send) a handover command to the UE, will determine that the UE has not experienced an RLF in a situation where it usually would be assumed that the UE has experienced RLF. For example, the network may, under normal circumstances, consider that an RLF has occurred for the UE if the network has performed a certain number of RLC retransmissions to the UE, e.g., 31 retransmissions (meaning 32 transmissions in total). However, if the network has sent (or begun to send) a handover command to the UE, the network may instead not consider that an RLF has occurred for the UE. Instead, the network may assume that the UE has received and executed the handover command.
Normally, when the network considers that an RLF has occurred for the UE, the network may log this event. However, according to some embodiments, the network will not log that an RLF has happened in the event that the network has sent a handover command to the UE. In a variant of this technique, the network may consider that the RLF did indeed happen, but instead refrain from logging this RLF event. As an alternative embodiment, RLFs triggered under these circumstances are logged under a separate counter.
In another variation of this technique, a first source network node may consider that the RLF happened if a first network sends a maximum number of RLC retransmissions of the HO command and it does not receive indication, e.g., within a certain time window, from a second target network node to which the handover was ordered that the handover was completed in a cell hosted by the second network node.
Figures 6 and 7 illustrate methods corresponding and generalizing these techniques. As shown at block 610 of Figure 6, for example, an example method may comprise the step of detecting a trigger indicating RLF for the UE, subsequent to beginning transmission of a handover command or other RRC command of a predetermined type. As shown at block 620, this method further comprises refraining from recording an RLF event corresponding to the trigger in a log of RLF events. Figure 7 illustrates a related method, which includes, as shown at block 710, the step of detecting a trigger indicating RLF for the UE, subsequent to beginning transmission of a handover command or other RRC command of a predetermined type. As shown at block 720, this method includes the further step of recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers (or with RRC commands of the predetermined type), separate from a log of RLF events not associated with handovers (or with RRC commands of the predetermined type).
According to another technique, when the network node determines to release or suspend the UE (by sending the RRCRelease message) and the network node includes a redirect information (e.g., redirectedCarrierlnfo), the network node does not set the RLC poll-bit. This allows the UE to not send an RLC ACK before leaving to IDLE/INACTIVE. This has the benefit that it may speed up the release with redirect procedure.
Figure 8 illustrates a diagram of a user equipment 50 configured to operate in a wireless network according to any of the techniques described above, according to some embodiments. User equipment 50 may be considered to represent any wireless devices or terminals that may operate in a network, such as a UE in a cellular network. Other examples may include a communication device, target device, MTC device, loT device, device to device (D2D) UE, machine type UE or UE capable of machine-to-machine communication (M2M), a sensor equipped with UE, PDA (personal digital assistant), tablet, IPAD tablet, mobile terminal, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), etc.
User equipment 50 is configured to communicate with a network node or base station in a wide- area cellular network via antennas 54 and transceiver circuitry 56. Transceiver circuitry 56 may include transmitter circuits, receiver circuits, and associated control circuits that are collectively configured to transmit and receive signals according to a radio access technology, for the purposes of using cellular communication services. The radio access technology can be NR or LTE, for the purposes of this discussion. User equipment 50 also includes one or more processing circuits 52 that are operatively associated with the radio transceiver circuitry 56. Processing circuitry 52 comprises one or more digital processing circuits, e.g., one or more microprocessors, microcontrollers, DSPs, FPGAs, CPLDs, ASICs, or any mix thereof. More generally, processing circuitry 52 may comprise fixed circuitry, or programmable circuitry that is specially adapted via the execution of program instructions implementing the UE functionality described herein, or may comprise some mix of fixed and programmed circuitry. Processing circuitry 52 may be multi-core.
Processing circuitry 52 also includes a memory 64. Memory 64, in some embodiments, stores one or more computer programs 66 and, optionally, configuration data 68. Memory 64 provides non- transitory storage for computer program 66 and it may comprise one or more types of computer- readable media, such as disk storage, solid-state memory storage, or any mix thereof. By way of nonlimiting example, memory 64 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in processing circuitry 52 and/or separate from processing circuitry 52. Memory 64 may also store any configuration data 68 used by wireless device 50. Processing circuitry 52 may be configured, e.g., through the use of appropriate program code stored in memory 64, to carry out one or more of the methods and/or signaling processes detailed herein.
Processing circuitry 52 of the user equipment 50 is configured, according to some embodiments, to perform any or all of the techniques described herein for a user equipment.
Figure 9 shows an example network node 30 that may correspond to any of the access nodes or other network nodes described herein. Network node 30 may be configured to carry out one or more of the presently disclosed techniques. Network node 30 may be an evolved Node B (eNodeB), Node B or gNB, for example. Network node may represent a radio network node such as base station, radio base station, base transceiver station, base station controller, network controller, NR BS, Multi-cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), or a multi-standard BS (MSR BS).
In the discussion herein, network node 30 is described as being configured to operate as a cellular network access node in an LTE network or NR network, but network node 30 may also correspond to similar access nodes in other types of network.
Those skilled in the art will readily appreciate how each type of node may be adapted to carry out one or more of the methods and signaling processes described herein, e.g., through the modification of and/or addition of appropriate program instructions for execution by processing circuits 32. Network node 30 facilitates communication between wireless terminals (e.g., UEs), other network access nodes and/or the core network. Network node 30 may include communication interface circuitry 38 that includes circuitry for communicating with other nodes in the core network, radio nodes, and/or other types of nodes in the network for the purposes of providing data and/or cellular communication services. Network node 30 communicates with wireless devices using antennas 34 and transceiver circuitry 36. Transceiver circuitry 36 may include transmitter circuits, receiver circuits, and associated control circuits that are collectively configured to transmit and receive signals according to a radio access technology, for the purposes of providing cellular communication services.
Network node 30 also includes one or more processing circuits 32 that are operatively associated with the transceiver circuitry 36 and, in some cases, the communication interface circuitry 38. Processing circuitry 32 comprises one or more digital processors 42, e.g., one or more microprocessors, microcontrollers, Digital Signal Processors (DSPs), Field Programmable Gate Arrays (FPGAs), Complex Programmable Logic Devices (CPLDs), Application Specific Integrated Circuits (ASICs), or any mix thereof. More generally, processing circuitry 32 may comprise fixed circuitry, or programmable circuitry that is specially configured via the execution of program instructions implementing the functionality taught herein, or some mix of fixed and programmed circuitry. Processor 42 may be multi-core, i.e., having two or more processor cores utilized for enhanced performance, reduced power consumption, and more efficient simultaneous processing of multiple tasks.
Processing circuitry 32 also includes a memory 44. Memory 44, in some embodiments, stores one or more computer programs 46 and, optionally, configuration data 48. Memory 44 provides non- transitory storage for the computer program 46 and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof. Here, "non-transitory" means permanent, semi-permanent, or at least temporarily persistent storage and encompasses both long-term storage in non-volatile memory and storage in working memory, e.g., for program execution. By way of non-limiting example, memory 44 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in processing circuitry 32 and/or separate from processing circuitry 32. Memory 44 may also store any configuration data 48 used by the network access node 30. Processing circuitry 32 may be configured, e.g., through the use of appropriate program code stored in memory 44, to carry out one or more of the methods and/or signaling processes detailed hereinafter. Processing circuitry 32 of the network node 30 is configured, according to some embodiments, to perform the techniques described herein for a network node, such as the first target node or second target node described in the several example techniques described above and illustrated in Figures 3-7.
Although the subject matter described herein can 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 10. For simplicity, the wireless network of Figure 10 only depicts network 1406, network nodes 1460 and 1460b, and wireless devices 1410, 1410b, and 1410c. In practice, a wireless network can 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 1460 and wireless device 1410 are depicted with additional detail. The wireless network can 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 can 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 can be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network can 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 1406 can 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 1460 and wireless device 1410 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 can 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 can facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
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 can be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node controlling a relay. A network node can 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 can also be referred to as nodes in a distributed antenna system (DAS).
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, a network node can be a virtual network node as described in more detail below. More generally, however, network nodes can 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 1460 includes processing circuitry 1470, device readable medium 1480, interface 1490, auxiliary equipment 1484, power source 1486, power circuitry 1487, and antenna 1462. Although network node 1460 illustrated in the example wireless network of Figure 10 can represent a device that includes the illustrated combination of hardware components, other embodiments can 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 and/or procedures disclosed herein. Moreover, while the components of network node 1460 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node can comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 1480 can comprise multiple separate hard drives as well as multiple RAM modules).
Similarly, network node 1460 can be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which can each have their own respective components. In certain scenarios in which network node 1460 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, can in some instances be considered a single separate network node. In some embodiments, network node 1460 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be duplicated (e.g., separate device readable medium 1480 for the different RATs) and some components can be reused (e.g., the same antenna 1462 can be shared by the RATs).
Network node 1460 can also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1460, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into the same or different chip or set of chips and other components within network node 1460.
Processing circuitry 1470 can be 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 1470 can include processing information obtained by processing circuitry 1470 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 1470 can 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 1460 components, such as device readable medium 1480, network node 1460 functionality. For example, processing circuitry 1470 can execute instructions stored in device readable medium 1480 or in memory within processing circuitry 1470. Such functionality can include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 1470 can include a system on a chip (SOC). In some embodiments, processing circuitry 1470 can include one or more of radio frequency (RF) transceiver circuitry 1472 and baseband processing circuitry 1474. In some embodiments, radio frequency (RF) transceiver circuitry 1472 and baseband processing circuitry 1474 can 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 1472 and baseband processing circuitry 1474 can 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 can be performed by processing circuitry 1470 executing instructions stored on device readable medium 1480 or memory within processing circuitry 1470. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 1470 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 1470 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1470 alone or to other components of network node 1460 but are enjoyed by network node 1460 as a whole, and/or by end users and the wireless network generally.
Device readable medium 1480 can 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 can be used by processing circuitry 1470. Device readable medium 1480 can 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 1470 and, utilized by network node 1460. Device readable medium 1480 can be used to store any calculations made by processing circuitry 1470 and/or any data received via interface 1490. In some embodiments, processing circuitry 1470 and device readable medium 1480 can be considered to be integrated.
Interface 1490 is used in the wired or wireless communication of signalling and/or data between network node 1460, network 1406, and/or wireless devices 1410. As illustrated, interface 1490 comprises port(s)/terminal(s) 1494 to send and receive data, for example to and from network 1406 over a wired connection. Interface 1490 also includes radio front end circuitry 1492 that can be coupled to, or in certain embodiments a part of, antenna 1462. Radio front end circuitry 1492 comprises filters 1498 and amplifiers 1496. Radio front end circuitry 1492 can be connected to antenna 1462 and processing circuitry 1470. Radio front end circuitry can be configured to condition signals communicated between antenna 1462 and processing circuitry 1470. Radio front end circuitry 1492 can receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 1492 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1498 and/or amplifiers 1496. The radio signal can then be transmitted via antenna 1462. Similarly, when receiving data, antenna 1462 can collect radio signals which are then converted into digital data by radio front end circuitry 1492. The digital data can be passed to processing circuitry 1470. In other embodiments, the interface can comprise different components and/or different combinations of components.
In certain alternative embodiments, network node 1460 may not include separate radio front end circuitry 1492, instead, processing circuitry 1470 can comprise radio front end circuitry and can be connected to antenna 1462 without separate radio front end circuitry 1492. Similarly, in some embodiments, all or some of RF transceiver circuitry 1472 can be considered a part of interface 1490. In still other embodiments, interface 1490 can include one or more ports or terminals 1494, radio front end circuitry 1492, and RF transceiver circuitry 1472, as part of a radio unit (not shown), and interface 1490 can communicate with baseband processing circuitry 1474, which is part of a digital unit (not shown).
Antenna 1462 can include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1462 can be coupled to radio front end circuitry 1490 and can be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 1462 can 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 omnidirectional antenna can be used to transmit/receive radio signals in any direction, a sector antenna can be used to transmit/receive radio signals from devices within a particular area, and a panel antenna can 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 can be referred to as MIMO. In certain embodiments, antenna 1462 can be separate from network node 1460 and can be connectable to network node 1460 through an interface or port. Antenna 1462, interface 1490, and/or processing circuitry 1470 can 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 can be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 1462, interface 1490, and/or processing circuitry 1470 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals can be transmitted to a wireless device, another network node and/or any other network equipment.
Power circuitry 1487 can comprise, or be coupled to, power management circuitry and can be configured to supply the components of network node 1460 with power for performing the functionality described herein. Power circuitry 1487 can receive power from power source 1486. Power source 1486 and/or power circuitry 1487 can be configured to provide power to the various components of network node 1460 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1486 can either be included in, or external to, power circuitry 1487 and/or network node 1460. For example, network node 1460 can 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 1487. As a further example, power source 1486 can comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 1487. The battery can provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, can also be used.
Alternative embodiments of network node 1460 can include additional components beyond those shown in Figure 10 that can 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 1460 can include user interface equipment to allow and/or facilitate input of information into network node 1460 and to allow and/or facilitate output of information from network node 1460. This can allow and/or facilitate a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1460.
In some embodiments, a wireless device (e.g., wireless device 1410) can be configured to communicate wirelessly with network nodes (e.g., 1460) and/or other wireless devices (e.g., 1410b, c). Communicating wirelessly can 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 can be configured to transmit and/or receive information without direct human interaction. For instance, a wireless device can 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 can 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 can in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a wireless device can 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 can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be referred to as an MTC device. As one particular example, the wireless device can be a UE implementing the 3GPP narrow band internet of things (NB-loT) 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 can 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 can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, a wireless device as described above can be mobile, in which case it can also be referred to as a mobile device or a mobile terminal.
As illustrated, wireless device 1410 includes antenna 1411, interface 1414, processing circuitry 1420, device readable medium 1430, user interface equipment 1432, auxiliary equipment 1434, power source 1436 and power circuitry 1437. Wireless device 1410 can include multiple sets of one or more of the illustrated components for different wireless technologies supported by wireless device 1410, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies can be integrated into the same or different chips or set of chips as other components within wireless device 1410. Antenna 1411 can include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 1414. In certain alternative embodiments, antenna 1411 can be separate from wireless device 1410 and be connectable to wireless device 1410 through an interface or port. Antenna 1411, interface 1414, and/or processing circuitry 1420 can be configured to perform any receiving or transmitting operations described herein as being performed by a wireless device. Any information, data and/or signals can be received from a network node and/or another wireless device. In some embodiments, radio front end circuitry and/or antenna 1411 can be considered an interface.
As illustrated, interface 1414 comprises radio front end circuitry 1412 and antenna 1411. Radio front end circuitry 1412 comprise one or more filters 1418 and amplifiers 1416. Radio front end circuitry 1414 is connected to antenna 1411 and processing circuitry 1420 and can be configured to condition signals communicated between antenna 1411 and processing circuitry 1420. Radio front end circuitry 1412 can be coupled to or a part of antenna 1411. In some embodiments, wireless device 1410 may not include separate radio front end circuitry 1412; rather, processing circuitry 1420 can comprise radio front end circuitry and can be connected to antenna 1411. Similarly, in some embodiments, some or all of RF transceiver circuitry 1422 can be considered a part of interface 1414. Radio front end circuitry 1412 can receive digital data that is to be sent out to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 1412 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1418 and/or amplifiers 1416. The radio signal can then be transmitted via antenna 1411. Similarly, when receiving data, antenna 1411 can collect radio signals which are then converted into digital data by radio front end circuitry 1412. The digital data can be passed to processing circuitry 1420. In other embodiments, the interface can comprise different components and/or different combinations of components.
Processing circuitry 1420 can 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 1410 components, such as device readable medium 1430, wireless device 1410 functionality. Such functionality can include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 1420 can execute instructions stored in device readable medium 1430 or in memory within processing circuitry 1420 to provide the functionality disclosed herein. As illustrated, processing circuitry 1420 includes one or more of RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426. In other embodiments, the processing circuitry can comprise different components and/or different combinations of components. In certain embodiments processing circuitry 1420 of wireless device 1410 can comprise a SOC. In some embodiments, RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426 can be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 1424 and application processing circuitry 1426 can be combined into one chip or set of chips, and RF transceiver circuitry 1422 can be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 1422 and baseband processing circuitry 1424 can be on the same chip or set of chips, and application processing circuitry 1426 can be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 1422, baseband processing circuitry 1424, and application processing circuitry 1426 can be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 1422 can be a part of interface 1414. RF transceiver circuitry 1422 can condition RF signals for processing circuitry 1420.
In certain embodiments, some or all of the functionality described herein as being performed by a wireless device can be provided by processing circuitry 1420 executing instructions stored on device readable medium 1430, which in certain embodiments can be a computer-readable storage medium. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 1420 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 1420 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 1420 alone or to other components of wireless device 1410, but are enjoyed by wireless device 1410 as a whole, and/or by end users and the wireless network generally.
Processing circuitry 1420 can 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 1420, can include processing information obtained by processing circuitry 1420 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by wireless device 1410, 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 1430 can 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 1420. Device readable medium 1430 can 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 can be used by processing circuitry 1420. In some embodiments, processing circuitry 1420 and device readable medium 1430 can be considered to be integrated.
User interface equipment 1432 can include components that allow and/or facilitate a human user to interact with wireless device 1410. Such interaction can be of many forms, such as visual, audial, tactile, etc. User interface equipment 1432 can be operable to produce output to the user and to allow and/or facilitate the user to provide input to wireless device 1410. The type of interaction can vary depending on the type of user interface equipment 1432 installed in wireless device 1410. For example, if wireless device 1410 is a smart phone, the interaction can be via a touch screen; if wireless device 1410 is a smart meter, the interaction can 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 1432 can include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 1432 can be configured to allow and/or facilitate input of information into wireless device 1410, and is connected to processing circuitry 1420 to allow and/or facilitate processing circuitry 1420 to process the input information.
User interface equipment 1432 can 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 1432 is also configured to allow and/or facilitate output of information from wireless device 1410, and to allow and/or facilitate processing circuitry 1420 to output information from wireless device 1410. User interface equipment 1432 can 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 1432, wireless device 1410 can communicate with end users and/or the wireless network, and allow and/or facilitate them to benefit from the functionality described herein. Auxiliary equipment 1434 is operable to provide more specific functionality which may not be generally performed by wireless devices. This can 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 1434 can vary depending on the embodiment and/or scenario.
Power source 1436 can, 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, can also be used. Wireless device 1410 can further comprise power circuitry 1437 for delivering power from power source 1436 to the various parts of wireless device 1410 which need power from power source 1436 to carry out any functionality described or indicated herein. Power circuitry 1437 can in certain embodiments comprise power management circuitry. Power circuitry 1437 can additionally or alternatively be operable to receive power from an external power source; in which case wireless device 1410 can 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 1437 can also in certain embodiments be operable to deliver power from an external power source to power source 1436. This can be, for example, for the charging of power source 1436. Power circuitry 1437 can perform any converting or other modification to the power from power source 1436 to make it suitable for supply to the respective components of wireless device 1410.
Figure 11 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 can 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 can represent a device that is not intended for sale to, or operation by, an end user but which can be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 1500 can be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 1500, as illustrated in Figure 11, 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 can be used interchangeable. Accordingly, although Figure 11 is a UE, the components discussed herein are equally applicable to a wireless device, and vice-versa.
In Figure 11, UE 1500 includes processing circuitry 1501 that is operatively coupled to input/output interface 1505, radio frequency (RF) interface 1509, network connection interface 1511, memory 1515 including random access memory (RAM) 917, read-only memory (ROM) 919, and storage medium 921 or the like, communication subsystem 931, power source 933, and/or any other component, or any combination thereof. Storage medium 1521 includes operating system 1523, application program 1525, and data 1527. In other embodiments, storage medium 1521 can include other similar types of information. Certain UEs can utilize all of the components shown in Figure 11, or only a subset of the components. The level of integration between the components can vary from one UE to another UE. Further, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
In Figure 11, processing circuitry 1501 can be configured to process computer instructions and data. Processing circuitry 1501 can 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 1501 can include two central processing units (CPUs). Data can be information in a form suitable for use by a computer.
In the depicted embodiment, input/output interface 1505 can be configured to provide a communication interface to an input device, output device, or input and output device. UE 1500 can be configured to use an output device via input/output interface 1505. An output device can use the same type of interface port as an input device. For example, a USB port can be used to provide input to and output from UE 1500. The output device can 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 1500 can be configured to use an input device via input/output interface 1505 to allow and/or facilitate a user to capture information into UE 1500. The input device can 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 can include a capacitive or resistive touch sensor to sense input from a user. A sensor can 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 can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
In Figure 11, RF interface 1509 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 1511 can be configured to provide a communication interface to network 1543a. Network 1543a can 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 1543a can comprise a Wi-Fi network. Network connection interface 1511 can 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 1511 can implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions can share circuit components, software or firmware, or alternatively can be implemented separately.
RAM 1517 can be configured to interface via bus 1502 to processing circuitry 1501 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 1519 can be configured to provide computer instructions or data to processing circuitry 1501. For example, ROM 1519 can 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 nonvolatile memory. Storage medium 1521 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 1521 can be configured to include operating system 1523, application program 1525 such as a web browser application, a widget or gadget engine or another application, and data file 1527. Storage medium 1521 can store, for use by UE 1500, any of a variety of various operating systems or combinations of operating systems.
Storage medium 1521 can 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 1521 can allow and/or facilitate UE 1500 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 can be tangibly embodied in storage medium 1521, which can comprise a device readable medium.
In Figure 11, processing circuitry 1501 can be configured to communicate with network 1543b using communication subsystem 1531. Network 1543a and network 1543b can be the same network or networks or different network or networks. Communication subsystem 1531 can be configured to include one or more transceivers used to communicate with network 1543b. For example, communication subsystem 1531 can 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.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver can include transmitter 1533 and/or receiver 1535 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 1533 and receiver 1535 of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.
In the illustrated embodiment, the communication functions of communication subsystem 1531 can 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 1531 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 1543b can 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 1543b can be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 1513 can be configured to provide alternating current (AC) or direct current (DC) power to components of UE 1500.
The features, benefits and/or functions described herein can be implemented in one of the components of UE 1500 or partitioned across multiple components of UE 1500. Further, the features, benefits, and/or functions described herein can be implemented in any combination of hardware, software, or firmware. In one example, communication subsystem 1531 can be configured to include any of the components described herein. Further, processing circuitry 1501 can be configured to communicate with any of such components over bus 1502. In another example, any of such components can be represented by program instructions stored in memory that when executed by processing circuitry 1501 perform the corresponding functions described herein. In another example, the functionality of any of such components can be partitioned between processing circuitry 1501 and communication subsystem 1531. In another example, the non- computationally intensive functions of any of such components can be implemented in software or firmware and the computationally intensive functions can be implemented in hardware.
Figure 12 is a schematic block diagram illustrating a virtualization environment 1600 in which functions implemented by some embodiments can be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which can 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, a virtualized radio access node, virtualized core network 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 can be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1600 hosted by one or more of hardware nodes 1630. 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 can be entirely virtualized.
The functions can be implemented by one or more applications 1620 (which can 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 1620 are run in virtualization environment 1600 which provides hardware 1630 comprising processing circuitry 1660 and memory 1690. Memory 1690 contains instructions 1695 executable by processing circuitry 1660 whereby application 1620 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
Virtualization environment 1600, comprises general-purpose or special-purpose network hardware devices 1630 comprising a set of one or more processors or processing circuitry 1660, which can 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 can comprise memory 1690-1 which can be non- persistent memory for temporarily storing instructions 1695 or software executed by processing circuitry 1660. Each hardware device can comprise one or more network interface controllers (NICs) 1670, also known as network interface cards, which include physical network interface 1680. Each hardware device can also include non-transitory, persistent, machine-readable storage media 1690- 2 having stored therein software 1695 and/or instructions executable by processing circuitry 1660. Software 1695 can include any type of software including software for instantiating one or more virtualization layers 1650 (also referred to as hypervisors), software to execute virtual machines 1640 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
Virtual machines 1640, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer 1650 or hypervisor. Different embodiments of the instance of virtual appliance 1620 can be implemented on one or more of virtual machines 1640, and the implementations can be made in different ways.
During operation, processing circuitry 1660 executes software 1695 to instantiate the hypervisor or virtualization layer 1650, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1650 can present a virtual operating platform that appears like networking hardware to virtual machine 1640.
As shown in Figure 12, hardware 1630 can be a standalone network node with generic or specific components. Hardware 1630 can comprise antenna 16225 and can implement some functions via virtualization. Alternatively, hardware 1630 can 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) 1690, which, among others, oversees lifecycle management of applications 1620. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV can 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 1640 can 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 1640, and that part of hardware 1630 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 1640, forms a separate virtual network elements (VNE).
In the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 1640 on top of hardware networking infrastructure 1630, and can correspond to application 1620 in Figure 12.
In some embodiments, one or more radio units 16200 that each include one or more transmitters 16220 and one or more receivers 16210 can be coupled to one or more antennas 16225. Radio units 16200 can communicate directly with hardware nodes 1630 via one or more appropriate network interfaces and can 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 16230 which can alternatively be used for communication between the hardware nodes 1630 and radio units 16200.
With reference to Figure 13, in accordance with an embodiment, a communication system includes telecommunication network 1710, such as a 3GPP-type cellular network, which comprises access network 1711, such as a radio access network, and core network 1714. Access network 1711 comprises a plurality of base stations 1712a, 1712b, 1712c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1713a, 1713b, 1713c. Each base station 1712a, 1712b, 1712c is connectable to core network 1714 over a wired or wireless connection 1715. A first UE 1791 located in coverage area 1713c can be configured to wirelessly connect to, or be paged by, the corresponding base station 1712c. A second UE 1792 in coverage area 1713a is wirelessly connectable to the corresponding base station 1712a. While a plurality of UEs 1791, 1792 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 Telecommunication network 1710 is itself connected to host computer 1730, which can 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 1730 can be under the ownership or control of a service provider, or can be operated by the service provider or on behalf of the service provider. Connections 1721 and 1722 between telecommunication network 1710 and host computer 1730 can extend directly from core network 1714 to host computer 1730 or can go via an optional intermediate network 1720. Intermediate network 1720 can be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 1720, if any, can be a backbone network or the Internet; in particular, intermediate network 1720 can comprise two or more sub-networks (not shown).
The communication system of Figure 13 as a whole enables connectivity between the connected UEs 1791, 1792 and host computer 1730. The connectivity can be described as an over-the-top (OTT) connection 1750. Host computer 1730 and the connected UEs 1791, 1792 are configured to communicate data and/or signaling via OTT connection 1750, using access network 1711, core network 1714, any intermediate network 1720 and possible further infrastructure (not shown) as intermediaries. OTT connection 1750 can be transparent in the sense that the participating communication devices through which OTT connection 1750 passes are unaware of routing of uplink and downlink communications. For example, base station 1712 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 1730 to be forwarded (e.g., handed over) to a connected UE 1791. Similarly, base station 1712 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1791 towards the host computer 1730.
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 14. In communication system 1800, host computer 1810 comprises hardware 1815 including communication interface 1816 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 1800. Host computer 1810 further comprises processing circuitry 1818, which can have storage and/or processing capabilities. In particular, processing circuitry 1818 can 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 1810 further comprises software 1811, which is stored in or accessible by host computer 1810 and executable by processing circuitry 1818. Software 1811 includes host application 1812. Host application 1812 can be operable to provide a service to a remote user, such as UE 1830 connecting via OTT connection
1850 terminating at UE 1830 and host computer 1810. In providing the service to the remote user, host application 1812 can provide user data which is transmitted using OTT connection 1850.
Communication system 1800 can also include base station 1820 provided in a telecommunication system and comprising hardware 1825 enabling it to communicate with host computer 1810 and with UE 1830. Hardware 1825 can include communication interface 1826 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 1800, as well as radio interface 1827 for setting up and maintaining at least wireless connection 1870 with UE 1830 located in a coverage area (not shown in Figure 14) served by base station 1820. Communication interface 1826 can be configured to facilitate connection 1860 to host computer 1810. Connection 1860 can be direct or it can pass through a core network (not shown in Figure 14) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 1825 of base station 1820 can also include processing circuitry 1828, which can 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 1820 further has software 1821 stored internally or accessible via an external connection.
Communication system 1800 can also include UE 1830 already referred to. Its hardware 1835 can include radio interface 1837 configured to set up and maintain wireless connection 1870 with a base station serving a coverage area in which UE 1830 is currently located. Hardware 1835 of UE 1830 can also include processing circuitry 1838, which can 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 1830 further comprises software 1831, which is stored in or accessible by UE 1830 and executable by processing circuitry 1838. Software 1831 includes client application 1832. Client application 1832 can be operable to provide a service to a human or non-human user via UE 1830, with the support of host computer 1810. In host computer 1810, an executing host application 1812 can communicate with the executing client application 1832 via OTT connection 1850 terminating at UE 1830 and host computer 1810. In providing the service to the user, client application 1832 can receive request data from host application 1812 and provide user data in response to the request data. OTT connection 1850 can transfer both the request data and the user data. Client application 1832 can interact with the user to generate the user data that it provides. It is noted that host computer 1810, base station 1820 and UE 1830 illustrated in Figure 14 can be similar or identical to host computer 1730, one of base stations 1712a, 1712b, 1712c and one of UEs 1791, 1792 of Figure 13, respectively. This is to say, the inner workings of these entities can be as shown in Figure 14 and independently, the surrounding network topology can be that of Figure 13.
In Figure 14, OTT connection 1850 has been drawn abstractly to illustrate the communication between host computer 1810 and UE 1830 via base station 1820, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure can determine the routing, which it can be configured to hide from UE 1830 or from the service provider operating host computer 1810, or both. While OTT connection 1850 is active, the network infrastructure can 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 1870 between UE 1830 and base station 1820 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 1830 using OTT connection 1850, in which wireless connection 1870 forms the last segment. More precisely, the exemplary embodiments disclosed herein can improve flexibility for the network to monitor end-to-end quality- of-service (QoS) of data flows, including their corresponding radio bearers, associated with data sessions between a user equipment (UE) and another entity, such as an OTT data application or service external to the 5G network. These and other advantages can facilitate more timely design, implementation, and deployment of 5G/NR solutions. Furthermore, such embodiments can facilitate flexible and timely control of data session QoS, which can lead to improvements in capacity, throughput, latency, etc. that are envisioned by 5G/NR and important for the growth of OTT services.
A measurement procedure can be provided for the purpose of monitoring data rate, latency and other network operational aspects on which the one or more embodiments improve. There can further be an optional network functionality for reconfiguring OTT connection 1850 between host computer 1810 and UE 1830, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 1850 can be implemented in software 1811 and hardware 1815 of host computer 1810 or in software 1831 and hardware 1835 of UE 1830, or both. In embodiments, sensors (not shown) can be deployed in or in association with communication devices through which OTT connection 1850 passes; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 1811, 1831 can compute or estimate the monitored quantities. The reconfiguring of OTT connection 1850 can include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 1820, and it can be unknown or imperceptible to base station 1820. Such procedures and functionalities can be known and practiced in the art. In certain embodiments, measurements can involve proprietary UE signaling facilitating host computer 1810's measurements of throughput, propagation times, latency and the like. The measurements can be implemented in that software 1811, 1831 causes messages to be transmitted, in particular empty or 'dummy' messages, using OTT connection 1850 while it monitors propagation times, errors, etc.
Figure 15 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which, in some exemplary embodiments, can be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section. In step 1910, the host computer provides user data. In substep 1911 (which can be optional) of step 1910, the host computer provides the user data by executing a host application. In step 1920, the host computer initiates a transmission carrying the user data to the UE. In step 1930 (which can 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 1940 (which can also be optional), the UE executes a client application associated with the host application executed by the host computer.
Figure 16 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can 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 2010 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 2020, the host computer initiates a transmission carrying the user data to the UE. The transmission can pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2030 (which can be optional), the UE receives the user data carried in the transmission.
Figure 17 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can 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 2110 (which can be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2120, the UE provides user data. In substep 2121 (which can be optional) of step 2120, the UE provides the user data by executing a client application. In substep 2111 (which can be optional) of step 2110, 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 can 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 2130 (which can be optional), transmission of the user data to the host computer. In step 2140 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 18 is a flowchart illustrating an exemplary method and/or procedure implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can 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 2210 (which can 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 2220 (which can be optional), the base station initiates transmission of the received user data to the host computer. In step 2230 (which can be optional), the host computer receives the user data carried in the transmission initiated by the base station.
The exemplary embodiments described herein provide techniques for pre-configuring a UE for operation in a 3GPP non-terrestrial network (NTN). Such embodiments reduce the time needed for initial acquisition of an NTN (e.g., PLMN) and a cell within the NTN. This can provide various benefits and/or advantages, including reducing UE energy consumption (or, equivalently, increasing UE operational time on one battery charge) and improving user access to services provided by an NTN. When used in UEs and/or network nodes, exemplary embodiments described herein can enable UEs to access network resources and OTT services more consistently and without interruption. This improves the availability and/or performance of these services as experienced by OTT service providers and end-users, including more consistent data throughout and fewer delays without excessive UE power consumption or other reductions in user experience.
EXAMPLE EMBODIMENTS
Embodiments of the presently disclosed techniques and apparatuses include, but are not limited to, the following examples: a. A method, in a network node operating in a wireless network, the method comprising: transmitting, to a user equipment, UE, a message containing or concluding a Radio Resource Control, RRC, command of a predetermined type; and applying a first predetermined maximum number of radio link control, RLC, retransmissions to retransmissions of at least one RLC packet data unit, PDU, associated with the message, wherein the first predetermined maximum number differs from a second predetermined maximum number of RLC retransmissions applicable to RLC PDUs not associated with a message containing or concluding a RRC command of the predetermined type. b. The method of example embodiment (a), wherein the predetermined type is a handover command. c. The method of example embodiment (a) or (b), wherein the predetermined type is one of a plurality of types to which the first predetermined maximum number of RLC retransmissions is applicable, the plurality of types being a proper subset of RRC commands. d. The method of any of example embodiments (a)-(c), wherein the first predetermined maximum number is less than the second predetermined maximum number. e. The method of example embodiment (d), wherein the first predetermined maximum number is 2. f. The method of any of any example embodiments (a)-(e), wherein the at least one RLC PDU associated with the message comprises an RLC PDU that forms all or part of the message. g. The method of any of example embodiments (a)-(f), wherein the at least one RLC PDU associated with the message comprises an RLC PDU that forms all or part of a second message containing a portion of the RRC command. h. The method of any of example embodiments (a)-(g), wherein the at least one RLC PDU associated with the message comprises an RLC PDU transmitted within a predetermined time window around the transmission of the message. i. The method of any of example embodiments (a)-(h), further comprising: subsequent to beginning transmission of the handover command, detecting a trigger indicating radio link failure, RLF, for the UE; and refraining from recording an RLF event corresponding to the trigger in a log of RLF events. j. The method of any of example embodiments (a)-(h), further comprising: subsequent to beginning transmission of the handover command, detecting a trigger indicating radio link failure, RLF, for the UE; and recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers. k. A method, in a first network node operating in a wireless network, the method comprising: determining that a user equipment, UE, served by the first network node has been handed over or is being handed over to a second network node; and adjusting a retransmission process directed towards the UE, in response to said determining. l. The method of example embodiment (k), wherein: said determining comprises receiving, from the second network node, an indication that the UE has been handed over or is being handed over to the second network node; and said adjusting comprises aborting an ongoing retransmission process directed towards the UE in response to receiving the indication. m. The method of example embodiment (k), wherein: said determining comprises determining to initiate a handover of the UE to the second network node; and said adjusting comprises reducing or eliminating retransmissions for one or more transmissions to the UE. n. The method of example embodiment (m), wherein said adjusting is further in response to determining that a quality of the link between the UE and the first network node is above a predetermined threshold. o. The method of any of example embodiments (k)-(n), further comprising: subsequent to beginning transmission of a handover command to the UE, detecting a trigger indicating radio link failure, RLF, for the UE; and refraining from recording an RLF event corresponding to the trigger in a log of RLF events. p. The method of any of example embodiments (k)-(n), further comprising: subsequent to beginning transmission of a handover command to the UE, detecting a trigger indicating radio link failure, RLF, for the UE; and recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers. q. A method, in a first network node operating in a wireless network, the method comprising: transmitting a Radio Link Control, RLC, packet data unit, PDU, to a user equipment, UE; receiving a medium access control, MAC, hybrid automatic-repeat-request, HARQ acknowledgement, the MAC HARQ. acknowledgement indicating that a MAC PDU corresponding to the RLC PDU was successfully decoded; and aborting an RLC retransmission process for the RLC PDU, in response to said receiving. r. The method of example embodiment (q), wherein the RLC PDU contains or completes a handover command. s. The method of example embodiment (q) or (r), further comprising: subsequent to beginning transmission of a handover command to the UE, detecting a trigger indicating radio link failure, RLF, for the UE; and refraining from recording an RLF event corresponding to the trigger in a log of RLF events. t. The method of example embodiment (q) or (r), further comprising: subsequent to beginning transmission of a handover command to the UE, detecting a trigger indicating radio link failure, RLF, for the UE; and recording an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers. u. A method, in a first network node operating in a wireless network, the method comprising: subsequent to beginning transmission of a Radio Resource Control, RRC, command of a predetermined type to a user equipment, UE, detecting a trigger indicating radio link failure, RLF, for the UE; and refraining from recording an RLF event corresponding to the trigger in a log of RLF events. v. The method of example embodiment u, wherein the predetermined type is a handover command. w. A method, in a first network node operating in a wireless network, the method comprising: subsequent to beginning transmission of a Radio Resource Control, RRC, command of a predetermined type to the UE, detecting a trigger indicating radio link failure, RLF, for the UE; and recording an RLF event corresponding to the trigger in a log of RLF events associated with RRC commands of the predetermined type, separate from a log of RLF events not associated with RRC commands of the predetermined type. x. The method of example embodiment (w), wherein the predetermined type is a handover command. y. A network node for operation in a wireless network, the network node being adapted to carry out a method according to any one of example embodiments (a)-(x). z. A network node for operation in a wireless network, the network node comprising: radio circuitry configured to communicate with a user equipment, UE; and processing circuitry operatively connected to the radio circuitry and configured to cause the network node to carry out a method according to any one of example embodiments l-(a)-(x). aa. A computer program product comprising program instructions for execution by a processing circuit in a network node, the program instructions being configured to cause the network node to carry out a method according to any one of example embodiments (a)-(x). bb. A computer-readable medium comprising, stored thereupon, the computer program product of example embodiment (aa). The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the spirit and scope of the disclosure. Various exemplary embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.
The term unit, as used herein, can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can 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.
Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (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 (RAM), 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 some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.
As described herein, device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor. Furthermore, functionality of a device or apparatus can be implemented by any combination of hardware and software. A device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other. Moreover, devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
In addition, certain terms used in the present disclosure, including the specification, drawings and exemplary embodiments thereof, can be used synonymously in certain instances, including, but not limited to, e.g., data and information. It should be understood that while these words and/or other words that can be synonymous to one another can be used synonymously herein, that there can be instances when such words can be intended to not be used synonymously. Further, to the extent that the prior art knowledge has not been explicitly incorporated by reference herein above, it is explicitly incorporated herein in its entirety. All publications referenced are incorporated herein by reference in their entireties.

Claims

What is claimed is:
1. A method, in a network node operating in a wireless network, the method comprising: transmitting (310), to a user equipment, UE, a message containing or concluding a Radio Resource Control, RRC, command of a predetermined type; and applying (320) a first predetermined maximum number of radio link control, RLC, retransmissions to retransmissions of at least one RLC packet data unit, PDU, associated with the message, wherein the first predetermined maximum number differs from a second predetermined maximum number of RLC retransmissions applicable to RLC PDUs not associated with a message containing or concluding a RRC command of the predetermined type.
2. The method of claim 1, wherein the predetermined type is a handover command.
3. The method of claim 1 or 2, wherein the predetermined type is one of a plurality of types to which the first predetermined maximum number of RLC retransmissions is applicable, the plurality of types being a proper subset of RRC commands.
4. The method of any of claims 1-3, wherein the first predetermined maximum number is less than the second predetermined maximum number.
5. The method of claim 4, wherein the first predetermined maximum number is 2.
6. The method of any of any claims 1-5, wherein the at least one RLC PDU associated with the message comprises an RLC PDU that forms all or part of the message.
7. The method of any of claims 1-6, wherein the at least one RLC PDU associated with the message comprises an RLC PDU that forms all or part of a second message containing a portion of the RRC command.
8. The method of any of claims 1-7, wherein the at least one RLC PDU associated with the message comprises an RLC PDU transmitted within a predetermined time window around the transmission of the message.
49
9. The method of any of claims 1-8, further comprising: subsequent to beginning transmission of the handover command, detecting (610) a trigger indicating radio link failure, RLF, for the UE; and refraining (620) from recording an RLF event corresponding to the trigger in a log of RLF events.
10. The method of any of claims 1-8, further comprising: subsequent to beginning transmission of the handover command, detecting (710) a trigger indicating radio link failure, RLF, for the UE; and recording (720) an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers.
11. A method, in a first network node operating in a wireless network, the method comprising: determining (410) that a user equipment, UE, served by the first network node has been handed over or is being handed over to a second network node; and adjusting (420) a retransmission process directed towards the UE, in response to said determining.
12. The method of claim 11, wherein: said determining (410) comprises receiving, from the second network node, an indication that the UE has been handed over or is being handed over to the second network node; and said adjusting (420) comprises aborting an ongoing retransmission process directed towards the UE in response to receiving the indication.
13. The method of claim 11, wherein: said determining (410) comprises determining to initiate a handover of the UE to the second network node; and said adjusting (420) comprises reducing or eliminating retransmissions for one or more transmissions to the UE.
14. The method of claim 13, wherein said adjusting (420) is further in response to determining that a quality of the link between the UE and the first network node is above a predetermined threshold.
50 method of any of claims 11-14, further comprising: subsequent to beginning transmission of a handover command to the UE, detecting (610) a trigger indicating radio link failure, RLF, for the UE; and refraining (620) from recording an RLF event corresponding to the trigger in a log of RLF events. method of any of claims 11-14, further comprising: subsequent to beginning transmission of a handover command to the UE, detecting (710) a trigger indicating radio link failure, RLF, for the UE; and recording (720) an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers. thod, in a first network node operating in a wireless network, the method comprising: transmitting (510) a Radio Link Control, RLC, packet data unit, PDU, to a user equipment, UE; receiving (520) a medium access control, MAC, hybrid automatic-repeat-request, HARQ acknowledgement, the MAC HARQ. acknowledgement indicating that a MAC PDU corresponding to the RLC PDU was successfully decoded; and aborting (530) an RLC retransmission process for the RLC PDU, in response to said receiving. method of claim 17, wherein the RLC PDU contains or completes a handover command. method of claim 17 or 18, further comprising: subsequent to beginning transmission of a handover command to the UE, detecting (610) a trigger indicating radio link failure, RLF, for the UE; and refraining (620) from recording an RLF event corresponding to the trigger in a log of RLF events. method of claim 17 or 18, further comprising: subsequent to beginning transmission of a handover command to the UE, detecting (710) a trigger indicating radio link failure, RLF, for the UE; and recording (720) an RLF event corresponding to the trigger in a log of RLF events associated with handovers, separate from a log of RLF events not associated with handovers. thod, in a first network node operating in a wireless network, the method comprising:
51 subsequent to beginning transmission of a Radio Resource Control, RRC, command of a predetermined type to a user equipment, UE, detecting (610) a trigger indicating radio link failure, RLF, for the UE; and refraining (620) from recording an RLF event corresponding to the trigger in a log of RLF events.
22. The method of claim 21, wherein the predetermined type is a handover command.
23. A method, in a first network node operating in a wireless network, the method comprising: subsequent to beginning transmission of a Radio Resource Control, RRC, command of a predetermined type to the UE, detecting (710) a trigger indicating radio link failure, RLF, for the UE; and recording (720) an RLF event corresponding to the trigger in a log of RLF events associated with RRC commands of the predetermined type, separate from a log of RLF events not associated with RRC commands of the predetermined type.
24. The method of claim 23, wherein the predetermined type is a handover command.
25. A network node for operation in a wireless network, the network node being adapted to carry out a method according to any one of claims 1-24.
26. A network node (30) for operation in a wireless network, the network node (30) comprising: radio circuitry (36, 34) configured to communicate with a user equipment, UE; and processing circuitry (32) operatively connected to the radio circuitry and configured to cause the network node (30) to carry out a method according to any one of claims 1-24.
27. A computer program product comprising program instructions (46) for execution by a processing circuit (32) in a network node (30), the program instructions (46) being configured to cause the network node (30) to carry out a method according to any one of claims 1-24.
28. A computer-readable medium (44) comprising, stored thereupon, the computer program product of claim 27.
52
PCT/SE2022/050020 2021-01-13 2022-01-13 Handling of missing handover radio link control (rlc) acknowledgements WO2022154723A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202163136827P 2021-01-13 2021-01-13
US63/136,827 2021-01-13

Publications (1)

Publication Number Publication Date
WO2022154723A1 true WO2022154723A1 (en) 2022-07-21

Family

ID=82447482

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2022/050020 WO2022154723A1 (en) 2021-01-13 2022-01-13 Handling of missing handover radio link control (rlc) acknowledgements

Country Status (1)

Country Link
WO (1) WO2022154723A1 (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140016617A1 (en) * 2011-04-06 2014-01-16 Telefonaktiebolaget L M Ericsson (Publ) Method for Managing Handover of a User Equipment
US20140341189A1 (en) * 2012-02-10 2014-11-20 Huawei Technologies Co., Ltd. Retransmission control method, communications system, and device
US20150189598A1 (en) * 2012-06-12 2015-07-02 Nokia Solutions And Networks Oy Radio Link Failure Information
WO2017092021A1 (en) * 2015-12-03 2017-06-08 华为技术有限公司 Method and apparatus for switching cell
WO2017149361A1 (en) * 2016-03-04 2017-09-08 Telefonaktiebolaget L M Ericsson (Publ) Handover notification
WO2018196978A1 (en) * 2017-04-27 2018-11-01 Nokia Solutions And Networks Oy Method for reduction of unwanted retransmissions

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140016617A1 (en) * 2011-04-06 2014-01-16 Telefonaktiebolaget L M Ericsson (Publ) Method for Managing Handover of a User Equipment
US20140341189A1 (en) * 2012-02-10 2014-11-20 Huawei Technologies Co., Ltd. Retransmission control method, communications system, and device
US20150189598A1 (en) * 2012-06-12 2015-07-02 Nokia Solutions And Networks Oy Radio Link Failure Information
WO2017092021A1 (en) * 2015-12-03 2017-06-08 华为技术有限公司 Method and apparatus for switching cell
WO2017149361A1 (en) * 2016-03-04 2017-09-08 Telefonaktiebolaget L M Ericsson (Publ) Handover notification
WO2018196978A1 (en) * 2017-04-27 2018-11-01 Nokia Solutions And Networks Oy Method for reduction of unwanted retransmissions

Similar Documents

Publication Publication Date Title
EP3738340B1 (en) Delta configuration in split cu-du ran architecture
US20230199577A1 (en) Keeping/Changing MR-DC Upon Conditional Handover (CHO)
US20230108496A1 (en) Triggering a Subsequent Handover during a Dual-Active Protocol Stack Handover
JP2022552190A (en) Master cell group failure while there is an ongoing secondary cell group change
WO2021091450A1 (en) Fallback to source cell during dual active protocol stack handover
US20220408325A1 (en) Conditional Configuration in Multi-Connectivity Operation
JP2023530813A (en) Method and apparatus for early data transfer in conditional handover of UE in multi-connectivity
US20240147322A1 (en) Enhancements to mro in case of rlf after successful (conditional) handover
US11864035B2 (en) Core network indication and security handling for handover
US20230292205A1 (en) User plane aspects considering duplicate discard for dual active protocol stack handover report
US20230269647A1 (en) Control Plane Aspects of Dual Active Protocol Stack Handover Report
US20230269646A1 (en) Dual Active Protocol Stack (DAPS) Handover During URLLC Packet Duplication
US11638191B2 (en) Intra-RAT handovers with core network change
US20230292195A1 (en) Conditional Handover Behavior Upon Dual Active Protocol Stacks Fallback
WO2022191763A1 (en) Mobility failure classification based on mcg failure information
US11963057B2 (en) Handover of unacknowledged mode bearer in a wireless communication system
WO2022154723A1 (en) Handling of missing handover radio link control (rlc) acknowledgements
WO2022154724A1 (en) Handling of missing radio link control (rlc) acknowledgements
US20240080695A1 (en) User Equipment Reporting of Reconnection after Link Failure
US20230388204A1 (en) Methods and Apparatuses for Reporting of Multiple Radio Link Failures
JP2024509905A (en) Enhancements to self-organizing network reporting for radio link failure after dual-active protocol stack fallback
WO2022031197A1 (en) Additional thresholds for dual connectivity data path switching
JP2024504279A (en) Signaling to release secondary cell group (SCG) configuration

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

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

Country of ref document: EP

Kind code of ref document: A1