WO2020030378A1 - Methods providing dual connectivity to single connectivity inter-system handover and related network nodes and computer program products - Google Patents

Methods providing dual connectivity to single connectivity inter-system handover and related network nodes and computer program products Download PDF

Info

Publication number
WO2020030378A1
WO2020030378A1 PCT/EP2019/068874 EP2019068874W WO2020030378A1 WO 2020030378 A1 WO2020030378 A1 WO 2020030378A1 EP 2019068874 W EP2019068874 W EP 2019068874W WO 2020030378 A1 WO2020030378 A1 WO 2020030378A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
handover
node
handover command
station node
Prior art date
Application number
PCT/EP2019/068874
Other languages
French (fr)
Inventor
Lian ARAUJO
Patrik Rugeland
Oumer Teyeb
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 WO2020030378A1 publication Critical patent/WO2020030378A1/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/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • 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/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
    • H04W36/00222—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies between different packet switched [PS] network technologies, e.g. transferring data sessions between LTE and WLAN or LTE and 5G

Definitions

  • the present disclosure relates generally to communications, and more particularly, to wireless communications and related wireless devices and network nodes.
  • Wireless device UE handover between 5GS and EPS may occur.
  • Handover within a certain radio access technology is known as intra- RAT handover, while handover between different radio access technologies is referred to as inter-RAT handover (e.g. NR to LTE).
  • intra-RAT handover e.g. NR to LTE
  • inter-RAT handover e.g. NR to LTE
  • handover can be intra-system (core network system remains the same) or inter-system (the core networks involved are using different systems, as in EPC to 5GC handover or vice versa).
  • four different types of handover may occur, i.e.
  • intra-RAT intra-system e.g., LTE to LTE or NR to NR
  • intra-RAT inter-system e.g., between LTE connected to EPC and LTE connected to 5GC
  • inter-RAT intra-system e.g., between LTE connected to 5GC and NR
  • inter-RAT inter system e.g., between LTE connected to EPC and NR
  • the term 5GS refers to the 5G system including the NG-RAN and the 5GC.
  • the term EPS refers to the LTE system including the E-UTRAN and the EPC.
  • Figure 1 is a diagram illustrating an Inter-system handover from 5GS to EPS.
  • an inter-system handover may always involve the core network and may be executed via the Sl or N2 interface.
  • the MME and the AMF may communicate via the N26 interface which is used to exchange UE context information and security related parameters and to forward handover information between the source and target RAN nodes.
  • Stage 2 aspects for inter-system handover between 5GS and EPS are defined in TS 23.502 (referred to as Reference [1]), namely in section 4.11.1.2.1 for the handover from 5GS to EPS and section 4.11.1.2.2 for the handover from EPS to 5GS.
  • the source node gNB
  • the source node gNB
  • gNB forwards a RRCConneetionReconfiguration message from the target inside a MobilityFromNRCommand message.
  • the source node eNB or ng-eNB forwards a RRCReconfiguration message (if target is
  • the procedures the UE performs are covered in inter- RAT procedures.
  • Dual connectivity is defined for intra-E- UTRA Dual Connectivity (DC) as depicted in Figure 2, which highlights the C-plane (control plane) and U-Plane (user plane) connectivity.
  • DC Dual Connectivity
  • Both MeNB and SeNB are E-UTRA nodes, with an EPC CN entity.
  • Figure 2 thus illustrates C-Plane and U-Plane connectivity of eNBs involved in Dual Connectivity.
  • MR-DC Multi- RAT Dual Connectivity
  • the core network CN entity associated to MR-DC can be either EPC or 5GC, which divides MR-DC cases into the following categories:
  • E-UTRA-NR Dual Connectivity comprised in EPS, as a master node MN eNB and an en-gNB as a secondary node SN (en-gNB refers to a gNB that is operating in a non-standalone mode operating as the SN);
  • NGEN-DC ⁇ NG-RAN E-UTRA-NR Dual Connectivity
  • 5GS a MN ng- eNB
  • ng-eNB refers to LTE eNB connected to 5GC
  • gNB gNode B
  • NE-DC NR-E-UTRA Dual Connectivity
  • a gNB or ng-eNB are collectively referred to as NG-RAN node.
  • C-plane and U-Plane connectivity for the EN-DC case is illustrated in Figure 3.
  • C-plane and U-plane connectivity for the MR-DC case associated with 5GC is illustrated in Figure 4.
  • NR-NR-DC the dual connectivity case where the MN and SN are NR nodes is called NR-NR-DC, which is agreed in RAN 2 meeting Reference [4] (cited below) to be covered in TS 37.340.
  • C-plane and U-Plane connectivity for NR-NR-DC can be illustrated by Figure 4, as in the case of MR-DC associated with 5GC.
  • a method may be provided to operate a first base station node acting as a master node in coordination with a second base station node acting as a secondary node for dual connectivity communication with a wireless device.
  • a first handover command message is received from a core network node, wherein the first handover command relates to handover for the wireless device.
  • a release request message is transmitted to the second base station node responsive to receiving the first handover command message.
  • a second handover command message is transmitted to the wireless device responsive to receiving the first handover command message.
  • a first base station node may be adapted to act as a master node in coordination with a second base station node acting as a secondary node for dual connectivity communication with a wireless device.
  • the first base station is adapted to receive a first handover command message from a core network node, wherein the first handover command relates to handover for the wireless device, to transmit a release request message to the second base station node responsive to receiving the first handover command message, and to transmit a second handover command message to the wireless device responsive to receiving the first handover command message.
  • a first base station node may be adapted to act as a master node in coordination with a second base station node acting as a secondary node for dual connectivity communication with a wireless device.
  • the first base station node includes a processor and memory coupled with the processor.
  • the memory includes instructions that when executed by the processor cause the processor to receive a first handover command message from a core network node wherein the first handover command relates to handover for the wireless device, to transmit a release request message to the second base station node responsive to receiving the first handover command message, and to transmit a second handover command message to the wireless device responsive to receiving the first handover command message.
  • Some embodiments of inventive concepts may enable improved inter-system handover in situations when a wireless device is configured with dual connectivity. Such embodiments may provide faster operation, for example, not requiring release of dual connectivity before performing inter-system handover.
  • Figure 1 is a block diagram illustrating inter-system handover between 5GS and EPS
  • Figure 2 is a diagram illustrating C-plane and U-plane connectivity of eNBS involved in Dual Connectivity
  • Figure 3 is a diagram illustrating c-plane and u-plane connectivity of EN-DC
  • Figure 4 is a diagram illustrating c-plane and u-plane connectivity of MR-DC with 5GC;
  • Figure 5A is a table illustrating different mobility combinations
  • Figure 5B is a table illustrating Node Types for different dual connectivity scenarios
  • Figure 6 is a message diagram illustrating EN-DC or FTE-DC to NG-RAN change procedure according to some embodiments of inventive concepts
  • Figure 7 is a message diagram illustrating MR-DC or NR-NR-DC to eNB change procedure according to some embodiments of inventive concepts
  • Figure 8 is a block diagram illustrating a radio access network RAN node according to some embodiments of inventive concepts
  • Figure 9 is a flow chart illustrating operations of a RAN node according to some embodiments of inventive concepts.
  • Figure 10 is a block diagram of a wireless network in accordance with some embodiments;
  • FIG. 11 is a block diagram of a user equipment in accordance with some embodiments
  • Figure 12 is a block diagram of a virtualization environment in accordance with some embodiments.
  • Figure 13 is a block diagram of a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments;
  • Figure 14 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;
  • Figure 15 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;
  • Figure 16 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;
  • Figure 17 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • Figure 18 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • FIG. 8 is a block diagram illustrating elements of a base station node 203 (also referred to as a network node, radio access network node, RAN node, base station, eNB, eNodeB, gNB, gNodeB, etc.) of a radio access network configured to provide cellular communication according to embodiments of inventive concepts.
  • base station node 203 may include a transceiver circuit 5001 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink radio communications with wireless devices.
  • the base station node 203 may include a network interface circuit 5007 (also referred to as a network interface) configured to provide communications with other nodes (e.g., with other base stations and/or core network nodes) of the wireless communication network.
  • the base station node 203 may also include a processor circuit 5003 (also referred to as a processor) coupled to the transceiver circuit, and a memory circuit 5005 (also referred to as memory) coupled to the processor circuit.
  • the memory circuit 5005 may include computer readable program code that when executed by the processor circuit 5003 causes the processor circuit to perform operations according to embodiments disclosed herein. According to other embodiments, processor circuit 5003 may be defined to include memory so that a separate memory circuit is not required.
  • operations of the base station node 203 may be performed by processor 5003, network interface 5007, and/or transceiver 5001.
  • processor 5003 may control transceiver 5001 to transmit downlink communications through transceiver 5001 over a radio interface to one or more UEs and/or to receive uplink communications through transceiver 5001 from one or more UEs over a radio interface.
  • processor 5003 may control network interface 5007 to transmit communications through network interface 5007 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes.
  • modules may be stored in memory 5005, and these modules may provide instructions so that when instructions of a module are executed by processor 5003, processor 5003 performs respective operations (e.g., operations discussed below with respect to Example Embodiments).
  • a structure similar to that of Figure 8 may be used to implement other network nodes (e.g., MME, S-GW, P-GW, AMF, SMF, UPF, AF, and/or NEF nodes), for example, omitting transceiver 5001.
  • network nodes discussed herein may be implemented as virtual network nodes.
  • the secondary node SN Release procedure may be initiated either by the master node MN or by the secondary node SN and is used to initiate the release of the UE context at the SN.
  • the recipient node of this request can reject it (e.g., if a SN change procedure is triggered by the SN).
  • a detailed description of the release of a SN can be found in TS 37.340 (Reference [3]) in section 10.4 for EN-DC and MR-DC with 5GC.
  • TS 37.340 In TS 37.340 (Reference [3]), handover is covered for dual connectivity scenarios, in the context of intra-system handover (i.e., from EPS to EPS or 5GS to 5GS).
  • the handover from dual connectivity to single connectivity is described by section 10.8 Master node to eNB/gNB change from TS 37.340 (Reference [3]), which covers the case when the UE has a connection with a source MN and a source SN, and performs an intra-system handover to a target node, which can be an eNB (for intra-system EPS handover) or an NG-RAN node (for intra-system 5GS handover).
  • a target node which can be an eNB (for intra-system EPS handover) or an NG-RAN node (for intra-system 5GS handover).
  • This handover scenario is further divided between handover from EPS to EPS or 5GS to 5GS, with the former describing EN-DC (LTE-DC is covered in TS 36.300, referred to as Reference [2]) and the latter describing MR-DC with 5GC.
  • handover procedures may be performed between 5GS and EPS, as detailed in section 2.1.1. If a source MN with a SN connection decides to perform handover to a target node, SN release procedures should be triggered, and afterwards handover procedures can be performed between 5GS and EPS. Hence, it should be noted that in an inter-system case, dual connectivity operation and handover may be disjoint procedures.
  • Handover from dual connectivity to single connectivity may be supported for intra system handover scenarios in TS 36.300 (Reference [2]) and TS 37.340 (Reference [3]).
  • Table 1 of Figure 5 A provides a summary of handover possibilities between EPS and 5GS, and within EPS and 5GS, for a given source node or source MN and SN, and a target node or target MN and SN. Cases covered in TS 36.300 (Reference [2]) and TS 37.340 (Reference [3]) are identified using diagonal fill. Handover scenarios currently not supported are identified using checkered fill and are a focus of the present disclosure (e.g., EN-DC to eLTE, EN-DC to NR, NGEN-DC to LTE, NR-NR DC to LTE, NR-NR DC to eLTE, NR-NR DC to NR, LTE DC to eLTE, and LTE DC to NR).
  • Figure 5B illustrates master/secondary node types and core network types for different dual connectivity scenarios.
  • procedures and associated message flows may be defined to support inter-system handover from dual connectivity to single connectivity.
  • procedures may be provided for handover between 5GS and EPS, with the possibility to perform release operations for a source SN.
  • inter- system handover procedures may be enabled for cases when the UE is configured with DC in the source system. This may enable a faster operation compared to disjoint procedures for releasing the DC and afterwards performing inter-system handover.
  • the source MN may need to release the source node SN after receiving the handover command from the core network CN.
  • An example of inter-system procedures from a source MN and SN to a target node is provided below.
  • FIG. 6 is a message diagram illustrating handover operations of an EN-DC or LTE-DC handover to NG-RAN (also referred to as an EN-DC or LTE-DC to NG-RAN change procedure).
  • NG-RAN may refer to a gNB or ng-eNB.
  • the eNB MN to NG-RAN (ng-eNB/gNB) Change procedure may be used to transfer UE context data from a source eNB MN and eNB/en-gNB SN to a target NG-RAN node.
  • Figure 6 illustrates an example a signaling/message flow for a EN-DC or LTE-DC to NG-RAN change/handover procedure. Operations of Figure 6 are discussed below:
  • Operation 1 of Figure 6 may be performed according to steps/operations
  • the source MME sends a Handover Command message to the source eNodeB.
  • This message conveys a Target to Source transparent container, generated by the target MN, to be sent to the UE (in Operation 4) as an
  • MN RRC message to perform the handover, and may also provide forwarding addresses (e.g., IntemetProtocol IP address for the Target Node) to the source MN.
  • forwarding addresses e.g., IntemetProtocol IP address for the Target Node
  • the source MN upon detecting that the handover being initiated is an inter-system handover, sends a SgNB release request message towards the source SN including a Cause indicating master carrier group MCG mobility.
  • the source SN acknowledges the release request. If data forwarding is needed, the MN provides data forwarding addresses (e.g., forwarding addresses from Operation 2) to the source SN. Reception of the SgNB Release Request message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding (based on the forwarding addresses).
  • data forwarding addresses e.g., forwarding addresses from Operation 2
  • the source MN triggers the UE to perform handover with a handover command (e.g., a MobilityFromEUTRACommand message including the MN RRC message of Operation 2) and applies the new configuration.
  • a handover command e.g., a MobilityFromEUTRACommand message including the MN RRC message of Operation 2
  • the UE Upon receiving the new configuration, the UE releases the entire secondary carrier group SCG configuration.
  • the UE synchronizes to the target NG-RAN node and replies with an
  • Operation 7 If applicable, data forwarding takes place from source MN and SN to target MN (using the forwarding addresses of Operation 2).
  • Operation 8 of Figure 6 may be performed according to steps/operations
  • Operation 9 Upon reception of the UE Context Release message from the MME (from clause 4.11.1.2.2.3 in 3GPP TS 23.502 vl5.2.0, which is part of the handover execution phase), the source MN initiates UE Context Release towards the source SN, which releases radio and C-plane related resource associated to the UE context. Any ongoing data forwarding may continue.
  • Figure 7 is a message diagram illustrating handover operations of an NG-RAN MN to eNB Change procedure used to transfer UE context data from a source NG-RAN MN/SN to a target eNB. Operations of Figure 7 may apply to an MR-DC or NR-NR-DC to eNB change procedure. Figure 7 illustrates message/signalling flows for MR-DC or NR-NR-DC to eNB change procedure. Operations of Figure 7 are discussed below:
  • Operation 1 of Figure 7 may be performed according to steps/operations
  • the AMF sends a Handover Command message to the source NG-RAN node.
  • This message conveys a Target to Source transparent container, generated by the target MN, to be sent to the UE as an E-UTRA RRC message, including a NR RRC configuration message, to perform the handover, and may also provide forwarding addresses to the source MN.
  • the source MN upon detecting that the handover being initiated is an inter-system handover, sends a SN release request message including a Cause indicating MCG mobility.
  • the source SN acknowledges the release request. If data forwarding is needed, the MN provides data forwarding addresses to the source SN. Reception of the SN Release Request message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding.
  • Operation 4 The source MN triggers the UE to perform handover (with
  • MobilityFromEUTRACommand or MobilityFromNRCommand message and apply the new configuration.
  • the UE Upon receiving the new configuration, the UE releases the entire SCG configuration.
  • the UE synchronizes to the target eNB and replies with MN
  • Operation 7 If applicable, data forwarding takes place from source MN and SN to target MN.
  • Operation 8 of Figure 7 may be performed according to steps/operations l2b-2l from clause 4.11.1.2.1 in 3GPP TS 23.502 vl5.2.0 for handover from 5GS to EPS, including l2b,l2c and l2d.
  • Operation 9 Upon reception of the UE Context Release message from the AMF (from clause 4.11.1.2.1 in 3GPP TS 23.502 vl5.2.0), the source MN initiates UE Context Release towards the source SN, which releases radio and C-plane related resource associated to the UE context. Any ongoing data forwarding may continue.
  • Some embodiments of inventive concepts may thus provide the exchange of messages in handover between EPS and 5GS, from a source MN and SN to a target node.
  • the release of the source SN may be implicitly triggered by the reception of a handover request at the source MN that indicates that the handover is an inter-system handover.
  • base station node 203 Operations of base station node 203 (referred to as a first base station node) are illustrated in the flow chart of Figure 9.
  • modules may be stored in base station memory 5005 of Figure 8, and these modules may provide instructions so that when the instructions of a module are executed by processor 5003, processor 5003 performs respective operations of the flow chart of Figure 9.
  • first base station node 203 acts as a master node (e.g., S-MN of Figure 6 and/or Figure 7) in coordination with a second base station node acting as a secondary node (e.g., S-SN of Figure 6 and/or Figure 7) for dual connectivity communication with a wireless device (e.g., UE of Figure 6 and/or Figure 7).
  • a master node e.g., S-MN of Figure 6 and/or Figure 7
  • second base station node acting as a secondary node e.g., S-SN of Figure 6 and/or Figure 7
  • a wireless device e.g., UE of Figure 6 and/or Figure 7
  • processor 5003 provides (e.g., through transceiver 5001 and/or network interface 5007) dual connectivity communication in coordination with the second base station node for the wireless device before receiving a first handover command message.
  • processor 5003 receives (e.g., through network interface 5007) a first handover command message from a core network node (e.g., MME of Figure 6 and/or Figure 7), wherein the first handover command relates to handover for the wireless device.
  • a core network node e.g., MME of Figure 6 and/or Figure 7
  • the first handover command relates to handover for the wireless device.
  • Operations of block 903, for example, may be performed as discussed above with respect to the handover command of operation 2 of Figure 6 and/or operation 2 of Figure 7.
  • processor 5003 detects that the first handover command message relates to an inter-system handover, for example, based on information in the first handover command message.
  • processor 5003 may transmit a release request message (e.g., through network interface 5007) to the second base station node responsive to receiving the first handover command message. Moreover, the release request message may be transmitted upon (e.g., responsive to) detecting that the first handover command message relates to an inter-system handover.
  • the release request message may include an indication of a cause relating to master cell group MCG mobility, and the indication of the cause relating to MCG mobility may be included responsive to detecting that the first handover command message relates to an inter system handover. Operations of block 905, for example, may be performed as discussed above with respect to the release request message of operation 3a of Figure 6 and/or operation 3a of Figure 7.
  • processor 5003 may receive (e.g., through network interface 5007) an acknowledgment from the second base station node, wherein the acknowledgment corresponds to the release request message.
  • Operations of block 907 may be performed as discussed above with respect to the release request acknowledge message of operation 3b of Figure 6 and/or operation 3b of Figure 7.
  • processor 5003 may transmit a second handover command message (e.g., through transceiver 5001) to the wireless device responsive to receiving the first handover command message.
  • Operations of block 911 may be performed as discussed above with respect to the handover command message of operation 4 of Figure 6 and/or operation 4 of Figure 7.
  • the first handover command message of block 903 may include a data forwarding address to be used for data to be forwarded to the wireless device, and at block 914, processor 5003 may forward data for the wireless device using the data forwarding address.
  • the data forwarding address may include an address for the third base station node (e.g., T-MN of Figure 6).
  • Operations of block 914 for example, may be performed as discussed above with respect to data forwarding of operation 7 of Figure 6 and/or operation 7 of Figure 7.
  • the release request message of block 905 includes the data forwarding address.
  • the second handover command message of block 911 may provide an indication of the third base station node (e.g., T-MN of Figure 6 and/or Figure 7) as target node for the handover.
  • first base station node 203 may be coupled with a first core network of a first core network technology
  • the third network node may be coupled with a second core network of a second core network technology different than the first core network technology.
  • the second base station node may be coupled with the first core network.
  • Various operations from the flow chart of Figure 9 may be optional with respect to some embodiments of base stations and related methods. Regarding methods of example embodiment 1 (set forth below), for example, operations of blocks 901, 904, 907, and 914 of Figure 9 may be optional.
  • a method of operating a first base station node acting as a master node in coordination with a second base station node acting as a secondary node for dual connectivity communication with a wireless device comprising: receiving (903, operation 2 of Fig. 6, operation 2 of Fig. 7) a first handover command message from a core network node, wherein the first handover command relates to handover for the wireless device; transmitting (905, operation 3a of Fig. 6, operation 3a of Fig. 7) a release request message to the second base station node responsive to receiving the first handover command message; and transmitting (911, operation 4 of Fig. 6, operation 4 of Fig. 7) a second handover command message to the wireless device responsive to receiving the first handover command message.
  • Embodiment 5 The method of Embodiment 4, wherein the first base station node is coupled with a first core network of a first core network technology, and wherein the third network node is coupled with a second core network of a second core network technology different than the first core network technology.
  • Packet Core, EPC network. 8. The method of any of Embodiment 5-6, wherein the first core network comprises an Evolved Packet Core, EPC, network, and wherein the second core network comprises a 5 th Generation, 5G, core network.
  • LTE eNB base station node LTE eNB base station node.
  • Embodiment 14 further comprising: detecting (904) that the first handover command message relates to an inter-system handover based on information in the first handover command message.
  • transmitting the second handover command message comprises transmitting the second handover command message to the wireless device after receiving the acknowledgment from the second base station node.
  • transmitting the second handover command message comprises transmitting the second handover command message to the wireless device after transmitting the release request message to the second base station node.
  • Embodiment 32 The method of Embodiment 31, wherein the second base station comprises an NR gNB base station.
  • the core network node is a node of a 5 th Generation Core, 5GC, network.
  • the node of the 5GC network comprises an Access and Mobility Management Function, AMF, node.
  • Embodiment 36 The method of Embodiment 35, wherein the first base station comprises an LTE eNB base station.
  • Embodiment 38 The method of Embodiment 37, wherein the first base station comprises an NR gNB base station.
  • Embodiment 40 The method of Embodiment 39, wherein the second base station comprises an LTE eNB base station.
  • the first core network node is a mobility management entity, MME, core network node
  • the second core network node is a serving gateway, S-GW, core network node.
  • AMF Mobility Management Function
  • UPF User Plane Function
  • a first base station node adapted to perform according to any of embodiments 1-45.
  • a first base station node comprising: a processor; and memory coupled with the processor, wherein the memory includes instructions that when executed by the processor cause the processor to perform operations according to any of Embodiments 1-45.
  • a computer program product comprising: a non-transitory computer readable storage medium comprising computer readable program code embodied in the medium that when executed by a processor of a base station node causes the base station node to perform operations according to any of Embodiments 1-45.
  • E-UTRA Evolved Universal Mobile Terrestrial Radio Access
  • E-UTRAN Evolved Universal Mobile Terrestrial Radio Access Network
  • E-UTRA Evolved Universal Terrestrial Radio Access Network
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof.
  • the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item.
  • the common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.
  • Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits.
  • These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).
  • Figure 10 A wireless network in accordance with some embodiments.
  • a wireless network such as the example wireless network illustrated in Figure 10.
  • the wireless network of Figure 10 only depicts network QQ106, network nodes QQ160 and QQl60b, and WDs QQ110, QQ1 lOb, and QQ1 lOc (also referred to as mobile terminals).
  • a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device.
  • network node QQ160 and wireless device (WD) QQ110 are depicted with additional detail.
  • the wireless network may provide
  • the wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system.
  • the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures.
  • particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile
  • 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 ZigBee
  • Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks
  • PSTNs public switched telephone networks
  • WANs wide-area networks
  • LANs local area networks
  • WLANs wireless networks
  • wireless networks wireless networks
  • metropolitan area networks metropolitan area networks
  • Network node QQ160 and WD QQ110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network.
  • the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • eNBs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs remote radio units
  • RRHs Remote Radio Heads
  • Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio.
  • Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • MSR multi-standard radio
  • RNCs radio network controllers
  • BSCs base station controllers
  • BTSs base transceiver stations
  • transmission points transmission nodes
  • MCEs multi-cell/multicast coordination entities
  • core network nodes e.g., MSCs, MMEs
  • O&M nodes e.g., OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs.
  • network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
  • network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ 187, and antenna QQ 162.
  • network node QQ 160 illustrated in the example wireless network of Figure 10 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • network node QQ160 may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).
  • network node QQ160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • network node QQ160 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple NodeB’s.
  • each unique NodeB and RNC pair may in some instances be considered a single separate network node.
  • network node QQ160 may be configured to support multiple radio access technologies (RATs).
  • RATs radio access technologies
  • Network node QQ160 may also include multiple sets of the various illustrated components for different wireless
  • network node QQ160 technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ160.
  • Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 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 QQ170 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 QQ170 may comprise a combination of one or more of a
  • processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein.
  • processing circuitry QQ170 may include a system on a chip (SOC).
  • processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174.
  • radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units.
  • part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units.
  • processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170.
  • some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner.
  • processing circuitry QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.
  • Device readable medium QQ180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170.
  • 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
  • Device readable medium QQ180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170 and, utilized by network node QQ160.
  • Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190.
  • processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.
  • Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170.
  • Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection.
  • Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162.
  • antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192.
  • the digital data may be passed to processing circuitry QQ170.
  • the interface may comprise different components and/or different combinations of components.
  • network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192.
  • all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190.
  • interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).
  • Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz.
  • An omni-directional antenna may be used to transmit/receive radio signals in any direction
  • a sector antenna may be used to transmit/receive radio signals from devices within a particular area
  • a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line.
  • the use of more than one antenna may be referred to as MIMO.
  • antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.
  • Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any
  • information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
  • Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ 186. Power source QQ 186 and/or power circuitry QQ 187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160.
  • network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187.
  • power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail.
  • Other types of power sources such as photovoltaic devices, may also be used.
  • network node QQ160 may include additional components beyond those shown in Figure 10 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.
  • wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices.
  • the term WD may be used interchangeably herein with user equipment (UE).
  • Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air.
  • a WD may be configured to transmit and/or receive information without direct human interaction.
  • a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network.
  • Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc.
  • VoIP voice over IP
  • PDA personal digital assistant
  • PDA personal digital assistant
  • a wireless cameras a gaming console or device
  • a music storage device a playback appliance
  • a wearable terminal device a wireless endpoint
  • a mobile station a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (L
  • a WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to -vehicle (V2V), vehicle-to -infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device.
  • D2D device-to-device
  • V2V vehicle-to -vehicle
  • V2I vehicle-to -infrastructure
  • V2X vehicle-to-everything
  • a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node.
  • the WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device.
  • M2M machine-to-machine
  • the WD may be a UE implementing the 3 GPP narrow band internet of things (NB-IoT) standard.
  • NB-IoT narrow band internet of things
  • machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.).
  • a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • a WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
  • wireless device QQ110 includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137.
  • WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110.
  • Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114.
  • antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port.
  • Antenna QQ111, interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD.
  • radio front end circuitry and/or antenna QQ111 may be considered an interface.
  • interface QQ114 comprises radio front end circuitry QQ112 and antenna QQ111.
  • Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116.
  • Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120.
  • Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ111.
  • WD QQ110 may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ111.
  • Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ 118 and/or amplifiers QQ 116. The radio signal may then be transmitted via antenna QQ 111. Similarly, when receiving data, antenna QQ111 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120.
  • the interface may comprise different components and/or different combinations of components.
  • Processing circuitry QQ120 may comprise a combination of one or more of a
  • processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.
  • processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126.
  • the processing circuitry may comprise different components and/or different combinations of components.
  • processing circuitry QQ120 of WD QQ110 may comprise a SOC.
  • RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips.
  • part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips.
  • part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips.
  • RF transceiver circuitry QQ122 may be a part of interface QQ114.
  • RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.
  • processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer- readable storage medium.
  • some or all of the functionality may be provided by processing circuitry QQ120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.
  • processing circuitry QQ120 can be configured to perform the described functionality.
  • the benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end users and the wireless network generally.
  • Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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 QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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 QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120.
  • Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120.
  • processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated.
  • User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).
  • usage e.g., the number of gallons used
  • a speaker that provides an audible alert
  • User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110.
  • User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
  • Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.
  • Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used.
  • WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein.
  • Power circuitry QQ137 may in certain embodiments comprise power management circuitry.
  • Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable.
  • Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.
  • FIG. 11 User Equipment in accordance with some embodiments
  • 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 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • UE QQ2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • UE QQ200 is one example of a WD 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
  • the term WD and UE may be used interchangeable. Accordingly, although Figure 11 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
  • UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231, power source QQ233, and/or any other component, or any combination thereof.
  • Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 11, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • processing circuitry QQ201 may be configured to process computer instructions and data.
  • Processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
  • input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device.
  • UE QQ200 may be configured to use an output device via input/output interface QQ205.
  • An output device may use the same type of interface port as an input device.
  • a USB port may be used to provide input to and output from UE QQ200.
  • the output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200.
  • the input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof.
  • the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
  • RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna.
  • Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a.
  • Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network QQ243a may comprise a Wi-Fi network.
  • Network connection interface QQ211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like.
  • Network connection interface QQ211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like).
  • the transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
  • RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 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 QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201.
  • ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory.
  • Storage medium QQ221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable
  • storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227.
  • Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.
  • Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM synchronous dynamic random access memory
  • SIM/RUIM removable user identity
  • Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221 , which may comprise a device readable medium.
  • processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231.
  • Network QQ243a and network QQ243b may be the same network or networks or different network or networks.
  • Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b.
  • communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like.
  • Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
  • the communication functions of communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof.
  • communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication.
  • Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof.
  • network QQ243b may be a cellular network, a Wi-Fi network, and/or a near- field network.
  • Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.
  • communication subsystem QQ231 may be configured to include any of the components described herein.
  • processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202.
  • any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein.
  • the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231.
  • the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
  • FIG. 12 Virtualization environment in accordance with some embodiments
  • FIG 12 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized.
  • virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources.
  • virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).
  • a node e.g., a virtualized base station or a virtualized radio access node
  • a device e.g., a UE, a wireless device or any other type of communication device
  • some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
  • the functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390.
  • Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
  • Virtualization environment QQ300 comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated
  • COTS commercial off-the-shelf
  • Each hardware device may comprise memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360.
  • Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380.
  • NICs network interface controllers
  • Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360.
  • Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • virtualization layers QQ350 also referred to as hypervisors
  • software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
  • Virtual machines QQ340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.
  • processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM).
  • Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.
  • hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.
  • CPE customer premise equipment
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine.
  • Each of virtual machines QQ340, and that part of hardware QQ330 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 QQ340, forms a separate virtual network elements (VNE).
  • VNE virtual network elements
  • VNF Virtual Network Function
  • one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225.
  • Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.
  • some signalling can be effected with the use of control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.
  • FIG. 13 Telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.
  • a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411, such as a radio access network, and core network QQ414.
  • Access network QQ411 comprises a plurality of base stations QQ4l2a, QQ4l2b, QQ4l2c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ4l3a, QQ4l3b, QQ4l3c.
  • Each base station QQ4l2a, QQ4l2b, QQ4l2c is connectable to core network QQ414 over a wired or wireless connection QQ415.
  • a first UE QQ491 located in coverage area QQ4l3c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ4l2c.
  • a second UE QQ492 in coverage area QQ4l3a is wirelessly connectable to the corresponding base station QQ4l2a. While a plurality ofUEs QQ491, QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.
  • Telecommunication network QQ410 is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider.
  • Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network
  • Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 13 as a whole enables connectivity between the connected UEs QQ491, QQ492 and host computer QQ430.
  • the connectivity may be described as an over-the-top (OTT) connection QQ450.
  • Host computer QQ430 and the connected UEs QQ491, QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411, core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries.
  • OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications.
  • base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491. Similarly, base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE
  • Figure 14 Host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.
  • host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500.
  • Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities.
  • processing circuitry QQ518 may comprise one or more programmable processors, application-specific integrated circuits, field
  • Host computer QQ510 further comprises software QQ511, which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518.
  • Software QQ511 includes host application QQ512.
  • Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.
  • Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530.
  • Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in Figure 14) served by base station QQ520.
  • Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510.
  • Connection QQ560 may be direct or it may 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 QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.
  • Communication system QQ500 further includes UE QQ530 already referred to.
  • Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located.
  • Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions.
  • UE QQ530 further comprises software QQ531, which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538.
  • Software QQ531 includes client application QQ532.
  • Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510.
  • an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510.
  • client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data.
  • OTT connection QQ550 may transfer both the request data and the user data.
  • Client application QQ532 may interact with the user to generate the user data that it provides.
  • host computer QQ510, base station QQ520 and UE QQ530 illustrated in Figure 14 may be similar or identical to host computer QQ430, one of base stations QQ4l2a,
  • OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure.
  • One or more of the various embodiments may improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve the deblock filtering for video processing and thereby provide benefits such as improved video encoding and/or decoding.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550 may be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both.
  • sensors may be deployed in or in association with communication devices through which OTT connection QQ550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software QQ511 , QQ531 may compute or estimate the monitored quantities.
  • the reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating host computer QQ5lO’s measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that software QQ511 and QQ531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.
  • Figure 15 Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • FIG. 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section.
  • the host computer provides user data.
  • substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application.
  • step QQ620 the host computer initiates a transmission carrying the user data to the UE.
  • step QQ630 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 QQ640 the UE executes a client application associated with the host application executed by the host computer.
  • Figure 16 Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • FIG 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • step QQ730 (which may be optional), the UE receives the user data carried in the transmission.
  • Figure 17 Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • FIG 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 17 will be included in this section.
  • step QQ810 the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data.
  • substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application.
  • substep QQ811 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 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 Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
  • FIG 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • step QQ930 (which may be optional)
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • 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 processors (DSPs), special-purpose digital logic, and the like.
  • the processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (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.
  • the term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Landscapes

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

Abstract

A method may be provided to operate a first base station node acting as a master node in coordination with a second base station node acting as a secondary node for dual connectivity communication with a wireless device. A first handover command message is received from a core network node, wherein the first handover command relates to handover for the wireless device. A release request message is transmitted to the second base station node responsive to receiving the first handover command message. A second handover command message is transmitted to the wireless device responsive to receiving the first handover command message. Related base station nodes are also discussed.

Description

METHODS PROVIDING DUAL CONNECTIVITY TO SINGLE CONNECTIVITY INTER SYSTEM HANDOVER AND RELATED NETWORK NODES AND COMPUTER
PROGRAM PRODUCTS
TECHNICAL FIELD
The present disclosure relates generally to communications, and more particularly, to wireless communications and related wireless devices and network nodes.
BACKGROUND
Wireless device UE handover between 5GS and EPS may occur.
Handover within a certain radio access technology (e.g., LTE to LTE) is known as intra- RAT handover, while handover between different radio access technologies is referred to as inter-RAT handover (e.g. NR to LTE). From the core network point of view, handover can be intra-system (core network system remains the same) or inter-system (the core networks involved are using different systems, as in EPC to 5GC handover or vice versa). Thus, four different types of handover may occur, i.e. intra-RAT intra-system (e.g., LTE to LTE or NR to NR), intra-RAT inter-system (e.g., between LTE connected to EPC and LTE connected to 5GC), inter-RAT intra-system (e.g., between LTE connected to 5GC and NR), and inter-RAT inter system (e.g., between LTE connected to EPC and NR).
The term 5GS refers to the 5G system including the NG-RAN and the 5GC. The term EPS refers to the LTE system including the E-UTRAN and the EPC.
Figure 1 is a diagram illustrating an Inter-system handover from 5GS to EPS. Unlike an intra-system handover where the source and target RAN node can communicate directly via the X2 or Xn interface, an inter-system handover may always involve the core network and may be executed via the Sl or N2 interface. During the handover, the MME and the AMF may communicate via the N26 interface which is used to exchange UE context information and security related parameters and to forward handover information between the source and target RAN nodes.
Stage 2 aspects for inter-system handover between 5GS and EPS are defined in TS 23.502 (referred to as Reference [1]), namely in section 4.11.1.2.1 for the handover from 5GS to EPS and section 4.11.1.2.2 for the handover from EPS to 5GS. When a handover is performed for wireless device UE from NR to E-UTRA connected to EPC or 5GC, the source node (gNB) forwards a RRCConneetionReconfiguration message from the target inside a MobilityFromNRCommand message. In case of handover from E-UTRA connected to EPC or 5GC to NR, or inter- system handover within E-UTRA (between EPC and 5GC), the source node (eNB or ng-eNB) forwards a RRCReconfiguration message (if target is
NR) or a RRCConneetionReconfiguration message (if target is LTE) inside a
MobilityFromEUTRACommand message.
Even though the RRC reconfiguration message transmitted may be the same message used for intra-RAT intra-system handover, the procedures the UE performs are covered in inter- RAT procedures.
Various dual connectivity options are discussed below.
In TS 36.300 (referred to as Reference [2]), dual connectivity is defined for intra-E- UTRA Dual Connectivity (DC) as depicted in Figure 2, which highlights the C-plane (control plane) and U-Plane (user plane) connectivity. Both MeNB and SeNB are E-UTRA nodes, with an EPC CN entity. Figure 2 thus illustrates C-Plane and U-Plane connectivity of eNBs involved in Dual Connectivity.
In TS 37.340 (referred to as Reference [3]), dual connectivity is further defined for Multi- RAT Dual Connectivity (MR-DC), which implies having a wireless device UE configured with two different nodes - one providing E-UTRA access and the other one providing NR access. The core network CN entity associated to MR-DC can be either EPC or 5GC, which divides MR-DC cases into the following categories:
• E-UTRA-NR Dual Connectivity (EN-DC), comprised in EPS, as a master node MN eNB and an en-gNB as a secondary node SN (en-gNB refers to a gNB that is operating in a non-standalone mode operating as the SN);
· NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC), comprised in 5GS, as a MN ng- eNB (ng-eNB refers to LTE eNB connected to 5GC) and a gNB as the SN; and
• NR-E-UTRA Dual Connectivity (NE-DC), comprised in 5GS, as a MN gNB and an ng- eNB as the SN.
A gNB or ng-eNB are collectively referred to as NG-RAN node. C-plane and U-Plane connectivity for the EN-DC case is illustrated in Figure 3. C-plane and U-plane connectivity for the MR-DC case associated with 5GC (NGEN-DC and NE-DC) is illustrated in Figure 4.
Besides MR-DC definition, the dual connectivity case where the MN and SN are NR nodes is called NR-NR-DC, which is agreed in RAN 2 meeting Reference [4] (cited below) to be covered in TS 37.340. C-plane and U-Plane connectivity for NR-NR-DC can be illustrated by Figure 4, as in the case of MR-DC associated with 5GC.
With the various resulting handover possibilities, improved handover operations may be desired.
SUMMARY
According to some embodiments of inventive concepts, a method may be provided to operate a first base station node acting as a master node in coordination with a second base station node acting as a secondary node for dual connectivity communication with a wireless device. A first handover command message is received from a core network node, wherein the first handover command relates to handover for the wireless device. A release request message is transmitted to the second base station node responsive to receiving the first handover command message. A second handover command message is transmitted to the wireless device responsive to receiving the first handover command message.
According to some other embodiments of inventive concepts, a first base station node may be adapted to act as a master node in coordination with a second base station node acting as a secondary node for dual connectivity communication with a wireless device. The first base station is adapted to receive a first handover command message from a core network node, wherein the first handover command relates to handover for the wireless device, to transmit a release request message to the second base station node responsive to receiving the first handover command message, and to transmit a second handover command message to the wireless device responsive to receiving the first handover command message.
According to still other embodiments of inventive concepts, a first base station node may be adapted to act as a master node in coordination with a second base station node acting as a secondary node for dual connectivity communication with a wireless device. The first base station node includes a processor and memory coupled with the processor. The memory includes instructions that when executed by the processor cause the processor to receive a first handover command message from a core network node wherein the first handover command relates to handover for the wireless device, to transmit a release request message to the second base station node responsive to receiving the first handover command message, and to transmit a second handover command message to the wireless device responsive to receiving the first handover command message.
Some embodiments of inventive concepts may enable improved inter-system handover in situations when a wireless device is configured with dual connectivity. Such embodiments may provide faster operation, for example, not requiring release of dual connectivity before performing inter-system handover.
BRIEF DESCRIPTION OF THE DRAWINGS
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in a constitute a part of this application, illustrate certain non- limiting embodiments of inventive concepts. In the drawings:
Figure 1 is a block diagram illustrating inter-system handover between 5GS and EPS;
Figure 2 is a diagram illustrating C-plane and U-plane connectivity of eNBS involved in Dual Connectivity;
Figure 3 is a diagram illustrating c-plane and u-plane connectivity of EN-DC;
Figure 4 is a diagram illustrating c-plane and u-plane connectivity of MR-DC with 5GC;
Figure 5A is a table illustrating different mobility combinations;
Figure 5B is a table illustrating Node Types for different dual connectivity scenarios;
Figure 6 is a message diagram illustrating EN-DC or FTE-DC to NG-RAN change procedure according to some embodiments of inventive concepts;
Figure 7 is a message diagram illustrating MR-DC or NR-NR-DC to eNB change procedure according to some embodiments of inventive concepts;
Figure 8 is a block diagram illustrating a radio access network RAN node according to some embodiments of inventive concepts;
Figure 9 is a flow chart illustrating operations of a RAN node according to some embodiments of inventive concepts; Figure 10 is a block diagram of a wireless network in accordance with some embodiments;
Figure 11 is a block diagram of a user equipment in accordance with some embodiments
Figure 12 is a block diagram of a virtualization environment in accordance with some embodiments;
Figure 13 is a block diagram of a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments;
Figure 14 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;
Figure 15 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;
Figure 16 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;
Figure 17 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments; and
Figure 18 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
DETAILED DESCRIPTION
Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment. The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter.
Figure 8 is a block diagram illustrating elements of a base station node 203 (also referred to as a network node, radio access network node, RAN node, base station, eNB, eNodeB, gNB, gNodeB, etc.) of a radio access network configured to provide cellular communication according to embodiments of inventive concepts. As shown, base station node 203 may include a transceiver circuit 5001 (also referred to as a transceiver) including a transmitter and a receiver configured to provide uplink and downlink radio communications with wireless devices. The base station node 203 may include a network interface circuit 5007 (also referred to as a network interface) configured to provide communications with other nodes (e.g., with other base stations and/or core network nodes) of the wireless communication network. The base station node 203 may also include a processor circuit 5003 (also referred to as a processor) coupled to the transceiver circuit, and a memory circuit 5005 (also referred to as memory) coupled to the processor circuit. The memory circuit 5005 may include computer readable program code that when executed by the processor circuit 5003 causes the processor circuit to perform operations according to embodiments disclosed herein. According to other embodiments, processor circuit 5003 may be defined to include memory so that a separate memory circuit is not required.
As discussed herein, operations of the base station node 203 may be performed by processor 5003, network interface 5007, and/or transceiver 5001. For example, processor 5003 may control transceiver 5001 to transmit downlink communications through transceiver 5001 over a radio interface to one or more UEs and/or to receive uplink communications through transceiver 5001 from one or more UEs over a radio interface. Similarly, processor 5003 may control network interface 5007 to transmit communications through network interface 5007 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory 5005, and these modules may provide instructions so that when instructions of a module are executed by processor 5003, processor 5003 performs respective operations (e.g., operations discussed below with respect to Example Embodiments). In addition, a structure similar to that of Figure 8 may be used to implement other network nodes (e.g., MME, S-GW, P-GW, AMF, SMF, UPF, AF, and/or NEF nodes), for example, omitting transceiver 5001. Moreover, network nodes discussed herein may be implemented as virtual network nodes.
The secondary node SN Release procedure may be initiated either by the master node MN or by the secondary node SN and is used to initiate the release of the UE context at the SN. The recipient node of this request can reject it (e.g., if a SN change procedure is triggered by the SN). A detailed description of the release of a SN can be found in TS 37.340 (Reference [3]) in section 10.4 for EN-DC and MR-DC with 5GC.
In TS 37.340 (Reference [3]), handover is covered for dual connectivity scenarios, in the context of intra-system handover (i.e., from EPS to EPS or 5GS to 5GS). The handover from dual connectivity to single connectivity is described by section 10.8 Master node to eNB/gNB change from TS 37.340 (Reference [3]), which covers the case when the UE has a connection with a source MN and a source SN, and performs an intra-system handover to a target node, which can be an eNB (for intra-system EPS handover) or an NG-RAN node (for intra-system 5GS handover). This handover scenario is further divided between handover from EPS to EPS or 5GS to 5GS, with the former describing EN-DC (LTE-DC is covered in TS 36.300, referred to as Reference [2]) and the latter describing MR-DC with 5GC.
In an inter-system case, handover procedures may be performed between 5GS and EPS, as detailed in section 2.1.1. If a source MN with a SN connection decides to perform handover to a target node, SN release procedures should be triggered, and afterwards handover procedures can be performed between 5GS and EPS. Hence, it should be noted that in an inter-system case, dual connectivity operation and handover may be disjoint procedures.
Handover from dual connectivity to single connectivity may be supported for intra system handover scenarios in TS 36.300 (Reference [2]) and TS 37.340 (Reference [3]).
However, other dual connectivity handover cases may be possible, considering inter-system handover.
Table 1 of Figure 5 A provides a summary of handover possibilities between EPS and 5GS, and within EPS and 5GS, for a given source node or source MN and SN, and a target node or target MN and SN. Cases covered in TS 36.300 (Reference [2]) and TS 37.340 (Reference [3]) are identified using diagonal fill. Handover scenarios currently not supported are identified using checkered fill and are a focus of the present disclosure (e.g., EN-DC to eLTE, EN-DC to NR, NGEN-DC to LTE, NR-NR DC to LTE, NR-NR DC to eLTE, NR-NR DC to NR, LTE DC to eLTE, and LTE DC to NR). Figure 5B illustrates master/secondary node types and core network types for different dual connectivity scenarios.
According to some embodiments disclosed herein, procedures and associated message flows may be defined to support inter-system handover from dual connectivity to single connectivity. For example, procedures may be provided for handover between 5GS and EPS, with the possibility to perform release operations for a source SN.
According to some embodiments disclosed herein, inter- system handover procedures may be enabled for cases when the UE is configured with DC in the source system. This may enable a faster operation compared to disjoint procedures for releasing the DC and afterwards performing inter-system handover.
Stage 2 operations for handover from dual connectivity to single connectivity are discussed below.
To enable handover from a source MN and SN to a target node, the source MN may need to release the source node SN after receiving the handover command from the core network CN. An example of inter-system procedures from a source MN and SN to a target node is provided below.
Figure 6 is a message diagram illustrating handover operations of an EN-DC or LTE-DC handover to NG-RAN (also referred to as an EN-DC or LTE-DC to NG-RAN change procedure). As discussed above, NG-RAN may refer to a gNB or ng-eNB. The eNB MN to NG-RAN (ng-eNB/gNB) Change procedure may be used to transfer UE context data from a source eNB MN and eNB/en-gNB SN to a target NG-RAN node.
As noted above, Figure 6 illustrates an example a signaling/message flow for a EN-DC or LTE-DC to NG-RAN change/handover procedure. Operations of Figure 6 are discussed below:
Operation 1. Operation 1 of Figure 6 may be performed according to steps/operations
1-15 from clause 4.11.1.2.2.2 in 3GPP TS 23.502 vl5.2.0 for handover preparation phase.
Operation 2. The source MME sends a Handover Command message to the source eNodeB. This message conveys a Target to Source transparent container, generated by the target MN, to be sent to the UE (in Operation 4) as an
MN RRC message, to perform the handover, and may also provide forwarding addresses (e.g., IntemetProtocol IP address for the Target Node) to the source MN.
Operation 3. The source MN, upon detecting that the handover being initiated is an inter-system handover, sends a SgNB release request message towards the source SN including a Cause indicating master carrier group MCG mobility. The source SN acknowledges the release request. If data forwarding is needed, the MN provides data forwarding addresses (e.g., forwarding addresses from Operation 2) to the source SN. Reception of the SgNB Release Request message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding (based on the forwarding addresses).
Operation 4. The source MN triggers the UE to perform handover with a handover command (e.g., a MobilityFromEUTRACommand message including the MN RRC message of Operation 2) and applies the new configuration. Upon receiving the new configuration, the UE releases the entire secondary carrier group SCG configuration.
Operation(s) 5/6. The UE synchronizes to the target NG-RAN node and replies with an
RRC message to the corresponding target MN (gNB or ng-eNB).
Operation 7. If applicable, data forwarding takes place from source MN and SN to target MN (using the forwarding addresses of Operation 2).
Operation 8. Operation 8 of Figure 6 may be performed according to steps/operations
4-13 from clause 4.11.1.2.2.3 in 3GPP TS 23.502 vl5.2.0 for handover execution phase.
Operation 9. Upon reception of the UE Context Release message from the MME (from clause 4.11.1.2.2.3 in 3GPP TS 23.502 vl5.2.0, which is part of the handover execution phase), the source MN initiates UE Context Release towards the source SN, which releases radio and C-plane related resource associated to the UE context. Any ongoing data forwarding may continue.
MR-DC or NR-NR-DC to eNB change is discussed below.
Figure 7 is a message diagram illustrating handover operations of an NG-RAN MN to eNB Change procedure used to transfer UE context data from a source NG-RAN MN/SN to a target eNB. Operations of Figure 7 may apply to an MR-DC or NR-NR-DC to eNB change procedure. Figure 7 illustrates message/signalling flows for MR-DC or NR-NR-DC to eNB change procedure. Operations of Figure 7 are discussed below:
Operation 1. Operation 1 of Figure 7 may be performed according to steps/operations
1-10 from clause 4.11.1.2.1 in 3GPP TS 23.502 vl5.2.0 for handover from 5GS to EPS, including operations lOa, lOb and lOc.
Operation 2. The AMF sends a Handover Command message to the source NG-RAN node. This message conveys a Target to Source transparent container, generated by the target MN, to be sent to the UE as an E-UTRA RRC message, including a NR RRC configuration message, to perform the handover, and may also provide forwarding addresses to the source MN.
Operation 3. The source MN, upon detecting that the handover being initiated is an inter-system handover, sends a SN release request message including a Cause indicating MCG mobility. The source SN acknowledges the release request. If data forwarding is needed, the MN provides data forwarding addresses to the source SN. Reception of the SN Release Request message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding.
Operation 4. The source MN triggers the UE to perform handover (with
MobilityFromEUTRACommand or MobilityFromNRCommand message) and apply the new configuration. Upon receiving the new configuration, the UE releases the entire SCG configuration.
Operation(s) 5/6. The UE synchronizes to the target eNB and replies with MN
RRCConneetionReconfigurationComplete message.
Operation 7. If applicable, data forwarding takes place from source MN and SN to target MN.
Operation 8. Operation 8 of Figure 7 may be performed according to steps/operations l2b-2l from clause 4.11.1.2.1 in 3GPP TS 23.502 vl5.2.0 for handover from 5GS to EPS, including l2b,l2c and l2d.
Operation 9. Upon reception of the UE Context Release message from the AMF (from clause 4.11.1.2.1 in 3GPP TS 23.502 vl5.2.0), the source MN initiates UE Context Release towards the source SN, which releases radio and C-plane related resource associated to the UE context. Any ongoing data forwarding may continue.
Some embodiments of inventive concepts may thus provide the exchange of messages in handover between EPS and 5GS, from a source MN and SN to a target node. The release of the source SN may be implicitly triggered by the reception of a handover request at the source MN that indicates that the handover is an inter-system handover.
Operations of base station node 203 (referred to as a first base station node) are illustrated in the flow chart of Figure 9. For example, modules may be stored in base station memory 5005 of Figure 8, and these modules may provide instructions so that when the instructions of a module are executed by processor 5003, processor 5003 performs respective operations of the flow chart of Figure 9.
For operations of Figure 9, first base station node 203 acts as a master node (e.g., S-MN of Figure 6 and/or Figure 7) in coordination with a second base station node acting as a secondary node (e.g., S-SN of Figure 6 and/or Figure 7) for dual connectivity communication with a wireless device (e.g., UE of Figure 6 and/or Figure 7).
At block 901, processor 5003 provides (e.g., through transceiver 5001 and/or network interface 5007) dual connectivity communication in coordination with the second base station node for the wireless device before receiving a first handover command message.
At block 903, processor 5003 receives (e.g., through network interface 5007) a first handover command message from a core network node (e.g., MME of Figure 6 and/or Figure 7), wherein the first handover command relates to handover for the wireless device. Operations of block 903, for example, may be performed as discussed above with respect to the handover command of operation 2 of Figure 6 and/or operation 2 of Figure 7.
At block 904, processor 5003 detects that the first handover command message relates to an inter-system handover, for example, based on information in the first handover command message.
At block 905, processor 5003 may transmit a release request message (e.g., through network interface 5007) to the second base station node responsive to receiving the first handover command message. Moreover, the release request message may be transmitted upon (e.g., responsive to) detecting that the first handover command message relates to an inter-system handover. The release request message may include an indication of a cause relating to master cell group MCG mobility, and the indication of the cause relating to MCG mobility may be included responsive to detecting that the first handover command message relates to an inter system handover. Operations of block 905, for example, may be performed as discussed above with respect to the release request message of operation 3a of Figure 6 and/or operation 3a of Figure 7.
At block 907, processor 5003 may receive (e.g., through network interface 5007) an acknowledgment from the second base station node, wherein the acknowledgment corresponds to the release request message. Operations of block 907, for example, may be performed as discussed above with respect to the release request acknowledge message of operation 3b of Figure 6 and/or operation 3b of Figure 7.
At block 911, processor 5003 may transmit a second handover command message (e.g., through transceiver 5001) to the wireless device responsive to receiving the first handover command message. Operations of block 911, for example, may be performed as discussed above with respect to the handover command message of operation 4 of Figure 6 and/or operation 4 of Figure 7.
According to some embodiments, the first handover command message of block 903 may include a data forwarding address to be used for data to be forwarded to the wireless device, and at block 914, processor 5003 may forward data for the wireless device using the data forwarding address. The data forwarding address, for example, may include an address for the third base station node (e.g., T-MN of Figure 6). Operations of block 914, for example, may be performed as discussed above with respect to data forwarding of operation 7 of Figure 6 and/or operation 7 of Figure 7. In addition, the release request message of block 905 includes the data forwarding address.
According to some embodiments, the second handover command message of block 911 may provide an indication of the third base station node (e.g., T-MN of Figure 6 and/or Figure 7) as target node for the handover. For example, first base station node 203 may be coupled with a first core network of a first core network technology, and the third network node may be coupled with a second core network of a second core network technology different than the first core network technology. Moreover, the second base station node may be coupled with the first core network. Various operations from the flow chart of Figure 9 may be optional with respect to some embodiments of base stations and related methods. Regarding methods of example embodiment 1 (set forth below), for example, operations of blocks 901, 904, 907, and 914 of Figure 9 may be optional.
Example embodiments of inventive concepts are set forth below.
1. A method of operating a first base station node acting as a master node in coordination with a second base station node acting as a secondary node for dual connectivity communication with a wireless device, the method comprising: receiving (903, operation 2 of Fig. 6, operation 2 of Fig. 7) a first handover command message from a core network node, wherein the first handover command relates to handover for the wireless device; transmitting (905, operation 3a of Fig. 6, operation 3a of Fig. 7) a release request message to the second base station node responsive to receiving the first handover command message; and transmitting (911, operation 4 of Fig. 6, operation 4 of Fig. 7) a second handover command message to the wireless device responsive to receiving the first handover command message.
2. The method of Embodiment 1, wherein the first handover command message includes a Radio Resource Control, RRC, handover message, and wherein the second handover command message includes the RRC handover message from the first handover command message.
3. The method of any of Embodiments 1-2, wherein the second handover command message comprises a Mobility FromEUTRACommand message and/or a
MobilityFromNRCommand message.
4. The method of any of Embodiments 1-3, wherein the second handover command message provides an indication of a third base station node as target node for the handover.
5. The method of Embodiment 4, wherein the first base station node is coupled with a first core network of a first core network technology, and wherein the third network node is coupled with a second core network of a second core network technology different than the first core network technology.
6. The method of Embodiment 5, wherein the second base station node is coupled with the first core network.
7. The method of any of Embodiments 5-6, wherein the first core network comprises a 5th Generation, 5G, core network, and wherein the second core network comprises an Evolved
Packet Core, EPC, network. 8. The method of any of Embodiment 5-6, wherein the first core network comprises an Evolved Packet Core, EPC, network, and wherein the second core network comprises a 5th Generation, 5G, core network.
9. The method of any of Embodiments 4-8, wherein the third base station node comprises a New Radio, NR, base station node.
10. The method of Embodiment 9, wherein the third base station node comprises an NR gNB base station node.
11. The method of any of Embodiments 4-8, wherein the third base station node comprises a Long Term Evolution, LTE, base station node.
12. The method of Embodiment 11, wherein the third base station node comprises an
LTE eNB base station node.
13. The method of any of Embodiments 1-12, wherein the release request message includes an indication of a cause relating to master cell group, MCG, mobility.
14. The method of Embodiment 13, wherein the indication of the cause relating to MCG mobility is included responsive to detecting that the first handover command message relates to an inter-system handover.
15. The method of Embodiment 14, further comprising: detecting (904) that the first handover command message relates to an inter-system handover based on information in the first handover command message.
16. The method of any of Embodiments 4-15, wherein the first handover command message includes a data forwarding address to be used for data to be forwarded to the wireless terminal.
17. The method of Embodiment 16, wherein the release request message includes the data forwarding address.
18. The method of any of Embodiments 16-17, further comprising: forwarding (914,
Operation 7 of Fig. 6, Operation 7 of Fig. 7) data for the wireless device using the data forwarding address.
19. The method of any of Embodiments 16-18, wherein the data forwarding address comprises an address for the third base station node.
20. The method of Embodiment 19, wherein the data forwarding address comprises an
Internet Protocol, IP, address for the third base station node. 21. The method of any of Embodiments 1-20 further comprising: providing (901) dual connectivity communication in coordination with the second base station node for the wireless device before receiving the first handover command message.
22. The method of any of Embodiments 1-21 further comprising: receiving (907, operation 3b of Fig. 6, operation 3b of Fig. 7) an acknowledgment from the second base station node, wherein the acknowledgment corresponds to the release request message.
23. The method of Embodiment 22, wherein transmitting the second handover command message comprises transmitting the second handover command message to the wireless device after receiving the acknowledgment from the second base station node.
24. The method of any of Embodiments 1-23, wherein transmitting the second handover command message comprises transmitting the second handover command message to the wireless device after transmitting the release request message to the second base station node.
25. The method of any of Embodiments 1-24, wherein the core network node is a node of an evolved packet core, EPC, network.
26. The method of Embodiment 25, wherein the node of the EPC network comprises a mobility management entity, MME, node.
27. The method of any of Embodiments 25-26, wherein the first base station comprises a Long Term Evolution, LTE, base station.
28. The method of Embodiment 27, wherein the first base station comprises an LTE eNB base station.
29. The method of any of Embodiments 25-28, wherein the second base station comprises a Long Term Evolution, LTE, base station.
30. The method of Embodiment 29, wherein the second base station comprises an LTE eNB base station.
31. The method of any of Embodiments 25-28, wherein the second base station comprises a New Radio, NR, base station.
32. The method of Embodiment 31, wherein the second base station comprises an NR gNB base station.
33. The method of any of Embodiments 1-24, wherein the core network node is a node of a 5th Generation Core, 5GC, network. 34. The method of Embodiment 33, wherein the node of the 5GC network comprises an Access and Mobility Management Function, AMF, node.
35. The method of any of Embodiments 33-34, wherein the first base station comprises a Fong Term Evolution, FTE, base station.
36. The method of Embodiment 35, wherein the first base station comprises an LTE eNB base station.
37. The method of any of Embodiments 33-34, wherein the first base station comprises a New Radio, NR, base station.
38. The method of Embodiment 37, wherein the first base station comprises an NR gNB base station.
39. The method of any of Embodiments 33-38, wherein the second base station comprises a Long Term Evolution, LTE, base station.
40. The method of Embodiment 39, wherein the second base station comprises an LTE eNB base station.
41. The method of any of Embodiments 33-38, wherein the second base station comprises a New Radio, NR, base station.
42. The method of Embodiment 41, wherein the second base station comprises an NR gNB base station.
43. The method of Embodiment 18, wherein the core network node is a first core network node, and wherein forwarding comprises forwarding the data for the wireless device via a second core network node different than the first core network node.
44. The method of Embodiment 43, wherein the first core network node is a mobility management entity, MME, core network node, and wherein the second core network node is a serving gateway, S-GW, core network node.
45. The method of Embodiment 43, wherein the first core network node is an Access and
Mobility Management Function, AMF, core network node, and wherein the second core network node is a User Plane Function, UPF core network node.
46. A first base station node adapted to perform according to any of embodiments 1-45.
47. A first base station node comprising: a processor; and memory coupled with the processor, wherein the memory includes instructions that when executed by the processor cause the processor to perform operations according to any of Embodiments 1-45. 48. A computer program product comprising: a non-transitory computer readable storage medium comprising computer readable program code embodied in the medium that when executed by a processor of a base station node causes the base station node to perform operations according to any of Embodiments 1-45.
Explanations are provided below for abbreviations that are mentioned in the present disclosure.
Abbreviation Explanation
5GC 5G Core Network
5GS 5G System
AMF Access and Mobility Management Function
DC Dual Connectivity
eNB E-UTRAN NodeB
EN-DC E-UTRA-NR Dual Connectivity
E-UTRA Evolved Universal Mobile Terrestrial Radio Access
E-UTRAN Evolved Universal Mobile Terrestrial Radio Access Network
EPC Evolved Packet Core
EPS Evolved Packet System
HO Handover
LTE Long Term Evolution
LTE-DC LTE Dual Connectivity
MME Mobility Management Entity
MN Master Node
MR Multi-RAT
MR-DC Multi-RAT Dual Connectivity
NE-DC NR-E-UTRA Dual Connectivity
NG Next Generation
NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity
NR New Radio
NR-NR-DC New Radio - New Radio Dual Connectivity
P-GW Packet Data Gateway
RAN Radio Access Network RAT Radio Access Technology
RRC Radio Resource Control
SMF Session Management Function
S-GW Serving GateWay
S-MN Source MN
SN Secondary Node
S-SN Source SN
T-MN Target MN
UE User Equipment
UPF User Plane Function
Full citations are provided below for references that are mentioned in the present disclosure.
Reference [1] 3GPP TS 23.502 vl5.2.0:“Procedures for the 5G System; Stage 2”.
Reference [2] 3GPP TS 36.300 vl5.2.0:“Evolved Universal Terrestrial Radio Access
(E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E- UTRAN); Overall description; Stage 2”.
Reference [3] 3GPP TS 37.340 vl5.2.0:“Evolved Universal Terrestrial Radio Access
(E-UTRA) and NR; Multi- connectivity; Stage 2”.
Reference [4] RAN 2 chair notes, 3GPP TSG-RAN WG2 AH#l80l, Vancouver,
Canada, 22th - 26th January, 2018
Further definitions and embodiments are discussed below.
In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. 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 present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, 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. When an element is referred to as being "connected", "coupled", "responsive", or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, "coupled", "connected", "responsive", or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term "and/or" includes any and all combinations of one or more of the associated listed items.
It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another
element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.
As used herein, the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having", or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation "e.g.", which derives from the Latin phrase "exempli gratia," may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation "i.e.", which derives from the Latin phrase "id est," may be used to specify a particular item from a more general recitation.
Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).
These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as "circuitry," "a module" or variants thereof.
It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.
Additional explanation is provided below.
Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.
Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
Figure 10: A wireless network in accordance with some embodiments.
Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 10. For simplicity, the wireless network of Figure 10 only depicts network QQ106, network nodes QQ160 and QQl60b, and WDs QQ110, QQ1 lOb, and QQ1 lOc (also referred to as mobile terminals). In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node QQ160 and wireless device (WD) QQ110 are depicted with additional detail. The wireless network may provide
communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.
The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile
Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks
(WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
Network node QQ160 and WD QQ110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi- standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
In Figure 10, network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ 187, and antenna QQ 162. Although network node QQ 160 illustrated in the example wireless network of Figure 10 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node QQ160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).
Similarly, network node QQ160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node QQ160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of the various illustrated components for different wireless
technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ160.
Processing circuitry QQ170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry QQ170 may include processing information obtained by processing circuitry QQ170 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 QQ170 may comprise a combination of one or more of a
microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node QQ160 components, such as device readable medium QQ180, network node QQ160 functionality. For example, processing circuitry QQ170 may execute instructions stored in device readable medium QQ180 or in memory within processing circuitry QQ170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry QQ170 may include a system on a chip (SOC).
In some embodiments, processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units.
In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170 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 QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.
Device readable medium QQ180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ170. Device readable medium QQ180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ170 and, utilized by network node QQ160. Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190. In some embodiments, processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.
Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170. In other embodiments, the interface may comprise different components and/or different combinations of components.
In certain alternative embodiments, network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown). Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.
Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any
information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
Power circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ 186. Power source QQ 186 and/or power circuitry QQ 187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160. For example, network node QQ160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry QQ187. As a further example, power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.
Alternative embodiments of network node QQ160 may include additional components beyond those shown in Figure 10 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.
As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to -vehicle (V2V), vehicle-to -infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3 GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
As illustrated, wireless device QQ110 includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137. WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110.
Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port. Antenna QQ111, interface QQ114, and/or processing circuitry QQ120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna QQ111 may be considered an interface.
As illustrated, interface QQ114 comprises radio front end circuitry QQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120. Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ111. In some embodiments, WD QQ110 may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 may be considered a part of interface QQ114. Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ 118 and/or amplifiers QQ 116. The radio signal may then be transmitted via antenna QQ 111. Similarly, when receiving data, antenna QQ111 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120. In other embodiments, the interface may comprise different components and/or different combinations of components.
Processing circuitry QQ120 may comprise a combination of one or more of a
microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ110 components, such as device readable medium QQ130, WD QQ110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein.
As illustrated, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry QQ120 of WD QQ110 may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122 may be a part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.
In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120 executing instructions stored on device readable medium QQ130, which in certain embodiments may be a computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ120 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 QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end users and the wireless network generally.
Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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 QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120. Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120. In some embodiments, processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated.
User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110. User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario.
Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein. Power circuitry QQ137 may in certain embodiments comprise power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.
Figure 11 : User Equipment in accordance with some embodiments
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 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE QQ2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE QQ200, as illustrated in Figure 11, is one example of a WD 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 WD and UE may be used interchangeable. Accordingly, although Figure 11 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.
In Figure 11, UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231, power source QQ233, and/or any other component, or any combination thereof. Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 11, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
In Figure 11, processing circuitry QQ201 may be configured to process computer instructions and data. Processing circuitry QQ201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry QQ201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.
In the depicted embodiment, input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200 may be configured to use an output device via input/output interface QQ205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE QQ200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
In Figure 11, RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a. Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243a may comprise a Wi-Fi network. Network connection interface QQ211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface QQ211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.
RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 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 QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium QQ221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable
programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems. Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221 , which may comprise a device readable medium.
In Figure 11, processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231. Network QQ243a and network QQ243b may be the same network or networks or different network or networks.
Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.
In the illustrated embodiment, the communication functions of communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243b may be a cellular network, a Wi-Fi network, and/or a near- field network. Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.
The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200 or partitioned across multiple components of UE QQ200.
Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem QQ231 may be configured to include any of the components described herein. Further, processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
Figure 12: Virtualization environment in accordance with some embodiments
Figure 12 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks). In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments QQ300 hosted by one or more of hardware nodes QQ330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
The functions may be implemented by one or more applications QQ320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
Virtualization environment QQ300, comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, which may be commercial off-the-shelf (COTS) processors, dedicated
Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360. Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380. Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360. Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
Virtual machines QQ340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.
During operation, processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.
As shown in Figure 12, hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320.
Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
In the context of NFV, virtual machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine. Each of virtual machines QQ340, and that part of hardware QQ330 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 QQ340, forms a separate virtual network elements (VNE).
Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines QQ340 on top of hardware networking infrastructure QQ330 and corresponds to application QQ320 in Figure 12.
In some embodiments, one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225. Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signalling can be effected with the use of control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.
Figure 13: Telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.
With reference to Figure 13, in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411, such as a radio access network, and core network QQ414. Access network QQ411 comprises a plurality of base stations QQ4l2a, QQ4l2b, QQ4l2c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ4l3a, QQ4l3b, QQ4l3c. Each base station QQ4l2a, QQ4l2b, QQ4l2c is connectable to core network QQ414 over a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ4l3c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ4l2c. A second UE QQ492 in coverage area QQ4l3a is wirelessly connectable to the corresponding base station QQ4l2a. While a plurality ofUEs QQ491, QQ492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station QQ412.
Telecommunication network QQ410 is itself connected to host computer QQ430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer QQ430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network
QQ420. Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown).
The communication system of Figure 13 as a whole enables connectivity between the connected UEs QQ491, QQ492 and host computer QQ430. The connectivity may be described as an over-the-top (OTT) connection QQ450. Host computer QQ430 and the connected UEs QQ491, QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411, core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries. OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications. For example, base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491. Similarly, base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE
QQ491 towards the host computer QQ430.
Figure 14: Host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.
Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to Figure 14. In communication system QQ500, host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities. In particular, processing circuitry QQ518 may comprise one or more programmable processors, application-specific integrated circuits, field
programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer QQ510 further comprises software QQ511, which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518. Software QQ511 includes host application QQ512. Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.
Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530. Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in Figure 14) served by base station QQ520.
Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510. Connection QQ560 may be direct or it may 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 QQ525 of base station QQ520 further includes processing circuitry QQ528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station QQ520 further has software QQ521 stored internally or accessible via an external connection.
Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530 further comprises software QQ531, which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532. Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510. In host computer QQ510, an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the user, client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data. OTT connection QQ550 may transfer both the request data and the user data. Client application QQ532 may interact with the user to generate the user data that it provides.
It is noted that host computer QQ510, base station QQ520 and UE QQ530 illustrated in Figure 14 may be similar or identical to host computer QQ430, one of base stations QQ4l2a,
QQ4l2b, QQ4l2c and one of UEs QQ491, QQ492 of Figure 13, respectively. This is to say, the inner workings of these entities may be as shown in Figure 14 and independently, the surrounding network topology may be that of Figure 13.
In Figure 14, OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
Wireless connection QQ570 between UE QQ530 and base station QQ520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve the deblock filtering for video processing and thereby provide benefits such as improved video encoding and/or decoding.
A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection QQ550 between host computer QQ510 and UE QQ530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550 may be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection QQ550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software QQ511 , QQ531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer QQ5lO’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software QQ511 and QQ531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.
Figure 15: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
Figure 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section. In step QQ610, the host computer provides user data. In substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.
Figure 16: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section. In step QQ710 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 QQ720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ730 (which may be optional), the UE receives the user data carried in the transmission.
Figure 17: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
Figure 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 17 will be included in this section. In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ811 (which may be optional) of step QQ810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 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: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.
Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 13 and 14. For simplicity of the present disclosure, only drawing references to Figure 18 will be included in this section. In step QQ910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step QQ920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station. 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 processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (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.
The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Claims

CLAIMS:
1. A method of operating a first base station node acting as a master node in coordination with a second base station node acting as a secondary node for dual connectivity communication with a wireless device, the method comprising:
receiving (903) a first handover command message from a core network node, wherein the first handover command relates to handover for the wireless device;
transmitting (905) a release request message to the second base station node responsive to receiving the first handover command message; and
transmitting (911) a second handover command message to the wireless device responsive to receiving the first handover command message.
2. The method of Claim 1, further comprising:
detecting (904) that the first handover command message relates to an inter-system handover, wherein the release request message is transmitted upon detecting that the first handover command message relates to an inter-system handover.
3. The method of Claim 1, wherein the release request message is transmitted upon detecting that the handover for the wireless device is an inter-system handover.
4. The method of any of Claims 1-3, wherein the second handover command message provides an indication of a third base station node as target node for the handover.
5. The method of Claim 4, wherein the first base station node is coupled with a first core network of a first core network technology, and wherein the third network node is coupled with a second core network of a second core network technology different than the first core network technology.
6. The method of Claim 5, wherein the second base station node is coupled with the first core network.
7. The method of Claim 1, wherein the release request message includes an indication of a cause relating to master cell group, MCG, mobility.
8. The method of Claim 7, wherein the indication of the cause relating to MCG mobility is included responsive to detecting that the first handover command message relates to an inter system handover.
9. The method of Claim 8, further comprising:
detecting (904) that the first handover command message relates to an inter-system handover based on information in the first handover command message.
10. The method of any of Claims 4-9, wherein the first handover command message includes a data forwarding address to be used for data to be forwarded to the wireless terminal.
11. The method of Claim 10, wherein the release request message includes the data forwarding address.
12. The method of any of Claims 10-11, further comprising:
forwarding (914) data for the wireless device using the data forwarding address.
13. The method of any of Claims 10-12, wherein the data forwarding address comprises an address for the third base station node.
14. The method of any of Claims 1-13 further comprising:
providing (901) dual connectivity communication in coordination with the second base station node for the wireless device before receiving the first handover command message.
15. The method of any of Claims 1-14 further comprising:
receiving (907) an acknowledgment from the second base station node, wherein the acknowledgment corresponds to the release request message.
16. A first base station node (203) adapted to act as a master node in coordination with a second base station node acting as a secondary node for dual connectivity communication with a wireless device, wherein the first base station node is further adapted to:
receive a first handover command message from a core network node, wherein the first handover command relates to handover for the wireless device;
transmit a release request message to the second base station node responsive to receiving the first handover command message; and
transmit a second handover command message to the wireless device responsive to receiving the first handover command message.
17. The first base station node (203) of Claim 16, wherein the first base station node is further adapted to:
detect that the first handover command message relates to an inter-system handover, wherein the release request message is transmitted upon detecting that the first handover command message relates to an inter-system handover.
18. The first base station node (203) of Claim 16, wherein the release request message is transmitted upon detecting that the handover for the wireless device is an inter-system handover.
19. The first base station node (203) of Claim 16, wherein the release request message includes an indication of a cause relating to master cell group, MCG, mobility, wherein the indication of the cause relating to MCG mobility is included responsive to detecting that the first handover command message relates to an inter-system handover, wherein the first base station node is further adapted to:
detect that the first handover command message relates to an inter-system handover based on information in the first handover command message.
20. The first base station node (203) of any of Claims 16-19, wherein the second handover command message provides an indication of a third base station node as target node for the handover, wherein the first handover command message includes a data forwarding address to be used for data to be forwarded to the wireless terminal, wherein the first base station node is further adapted to:
forward data for the wireless device using the data forwarding address.
21. The first base station node (203) of any of Claims 16-20, wherein the first base station node is further adapted to:
provide dual connectivity communication in coordination with the second base station node for the wireless device before receiving the first handover command message.
22. The first base station node (203) of any of Claims 16-21, wherein the first base station node is further adapted to:
receive an acknowledgment from the second base station node, wherein the
acknowledgment corresponds to the release request message.
23. A first base station node (203) adapted to act as a master node in coordination with a second base station node acting as a secondary node for dual connectivity communication with a wireless device, the first base station node comprising:
a processor (5003); and
memory (5005) coupled with the processor, wherein the memory includes instructions that when executed by the processor cause the processor to,
receive a first handover command message from a core network node, wherein the first handover command relates to handover for the wireless device,
transmit a release request message to the second base station node responsive to receiving the first handover command message, and
transmit a second handover command message to the wireless device responsive to receiving the first handover command message.
24. The first base station node (203) of Claim 23, wherein the memory further includes instructions that when executed by the processor cause the processor to, detect that the first handover command message relates to an inter-system handover, wherein the release request message is transmitted upon detecting that the first handover command message relates to an inter-system handover.
25. The first base station node (203) of Claim 23, wherein the release request message is transmitted upon detecting that the handover for the wireless device is an inter-system handover.
26. The first base station node (203) of Claim 23, wherein the release request message includes an indication of a cause relating to master cell group, MCG, mobility, wherein the indication of the cause relating to MCG mobility is included responsive to detecting that the first handover command message relates to an inter-system handover, wherein the memory further includes instructions that when executed by the processor cause the processor to,
detect that the first handover command message relates to an inter-system handover based on information in the first handover command message.
27. The first base station node (203) of any of Claims 23-26, wherein the second handover command message provides an indication of a third base station node as target node for the handover, wherein the first handover command message includes a data forwarding address to be used for data to be forwarded to the wireless terminal, wherein the memory further includes instructions that when executed by the processor cause the processor to,
forward data for the wireless device using the data forwarding address.
28. The first base station node (203) of any of Claims 23-27, wherein the memory further includes instructions that when executed by the processor cause the processor to,
provide dual connectivity communication in coordination with the second base station node for the wireless device before receiving the first handover command message.
29. The first base station node (203) of any of Claims 23-28, wherein the memory further includes instructions that when executed by the processor cause the processor to, receive an acknowledgment from the second base station node, wherein the acknowledgment corresponds to the release request message.
30. A computer program product comprising:
a non-transitory computer readable storage medium comprising computer readable program code embodied in the medium that when executed by a processor (5003) of a base station node (203) causes the base station node (203) to perform operations according to any of Claims 1-15.
PCT/EP2019/068874 2018-08-09 2019-07-12 Methods providing dual connectivity to single connectivity inter-system handover and related network nodes and computer program products WO2020030378A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201862716891P 2018-08-09 2018-08-09
US62/716891 2018-08-09

Publications (1)

Publication Number Publication Date
WO2020030378A1 true WO2020030378A1 (en) 2020-02-13

Family

ID=67303462

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2019/068874 WO2020030378A1 (en) 2018-08-09 2019-07-12 Methods providing dual connectivity to single connectivity inter-system handover and related network nodes and computer program products

Country Status (1)

Country Link
WO (1) WO2020030378A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021196854A1 (en) * 2020-04-01 2021-10-07 中兴通讯股份有限公司 Communication method, apparatus and device, and storage medium
CN113810956A (en) * 2020-06-11 2021-12-17 维沃移动通信有限公司 Method and device for switching multicast service

Non-Patent Citations (7)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 37.340, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. V15.2.0, 20 June 2018 (2018-06-20), pages 1 - 55, XP051472914 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15)", 3GPP STANDARD; TECHNICAL SPECIFICATION; 3GPP TS 23.502, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V15.2.0, 19 June 2018 (2018-06-19), pages 1 - 308, XP051472861 *
"Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2", 3GPP TS 36.300 VL5.2.0
"Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2", 3GPP TS 37.340 VL5.2.0
"Procedures for the 5G System; Stage 2", 3GPP TS 23.502 VL5.2.0
3GPP TSG-RAN WG2 AH#1801, 22 January 2018 (2018-01-22)
ZTE: "Further Consideration on MR-DC Mobility Procedures", vol. RAN WG3, no. Sophia-Antipolice, France; 20180122 - 20180126, 13 January 2018 (2018-01-13), XP051387491, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG3%5FIu/TSGR3%5FAHGs/R3%2DAH%2D1801/Docs/> [retrieved on 20180113] *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021196854A1 (en) * 2020-04-01 2021-10-07 中兴通讯股份有限公司 Communication method, apparatus and device, and storage medium
EP4132203A4 (en) * 2020-04-01 2024-04-10 Zte Corp Communication method, apparatus and device, and storage medium
CN113810956A (en) * 2020-06-11 2021-12-17 维沃移动通信有限公司 Method and device for switching multicast service
CN113810956B (en) * 2020-06-11 2023-03-31 维沃移动通信有限公司 Method and device for switching multicast service

Similar Documents

Publication Publication Date Title
US20200120559A1 (en) Delta Configuration in Split CU-DU RAN Architecture
US11140598B2 (en) Network initiated inter-RAT handover
US11659451B2 (en) Serving gateway control plane function to manage a plurality of serving gateway user plane functions, and mobility management entity to communicate with the same
EP3646639B1 (en) A method, network functions and a computer program product for supporting the handing over of a user equipment, ue, from a first type of radio access technology, rat, to a second type of rat
WO2020030676A1 (en) Inter-system handover from single/dual connectivity systems to dual connectivity systems
US11546765B2 (en) Master gNodeBs and method of operating master gNodeB
WO2022074620A1 (en) Handling conditional pscell change (cpc) upon sn release
US20230180065A1 (en) Methods and Apparatuses for Early Data Forwarding in Conditional Handover of a UE in Multi-Connectivity
WO2021086254A1 (en) Conditional configuration in multi-connectivity operation
EP3695628A1 (en) Network node, user equipment (ue) and methods for handling communication in a narrowband internet of things (nb-iot) or machine type communication (mtc) network
US20220369194A1 (en) Enhancements in mobility history information
WO2021236004A1 (en) Request to store information for a plurality of cells
WO2020030378A1 (en) Methods providing dual connectivity to single connectivity inter-system handover and related network nodes and computer program products
US20230189095A1 (en) Re-establishment of communication devices configured with conditional handover and operating in multi-radio dual connectivity
US11751269B2 (en) Methods providing UE state indication upon delivery failure and related networks and network nodes
US20210227382A1 (en) To Increase Security of Dual Connectivity
WO2021063978A1 (en) Security settings for user plane data sent over different accesses of a network
EP3912429A1 (en) Nas-as interaction for early data transmission
EP4026388B1 (en) Uplink aware dual connectivity
US11445474B2 (en) Mobile switching node and mobility management node to page terminal device
US11985556B2 (en) Optimized handling of traffic management-initiated access change
US20230276219A1 (en) Reporting of Secondary Node Related Operations
WO2023056788A1 (en) Method, apparatus for network exposure service continuity across edge data networks
WO2024022278A1 (en) Method and apparatus for mobility management
EP4154672A1 (en) Ue-requested cp-pur configuration change

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

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

Country of ref document: EP

Kind code of ref document: A1