INTER-SYSTEM HANDOVER FROM SINGLE/DUAL CONNECTIVITY SYSTEMS TO DUAL

CONNECTIVITY SYSTEMS

BACKGROUND

[0001] Wireless device (UE) handover, which refers to the transfer of a UE's connection from one radio channel to another, may occur between 5GS wireless communication systems and EPS wireless communication systems. The term 5GS refers to the 5G system, including the NG-RAN radio access technology (RAT) and the 5GC core network (CN). The term EPS refers to the LTE system, including the E-UTRAN (LTE) RAT and the EPC CN.

[0002] A handover within a particular radio access technology (e.g., LTE to LTE) is known as an intra-RAT handover, while a handover between different radio access technologies is referred to as an inter-RAT handover (e.g. NR to LTE or LTE to NR). The core network of a communication system may be EPC or 5GC. From the core network point of view, a handover can be intra-system (i.e., the core network system remains the same) or inter-system (the core networks involved use different systems, as in EPC to 5GC handover or vice versa). Thus, four different types of handovers may occur, namely, intra-RAT/intra-system (e.g., LTE/EPC to LTE/EPC or NR/5GC to NR/5GC), intra-RAT/inter-system (e.g., between LTE/EPC and LTE/5GC), inter-RAT intra-system (e.g., between LTE/5GC and NR/5GC), and inter-RAT inter-system (e.g., between LTE/EPC and NR/5GC).

[0003] Figure 1 is a diagram illustrating an inter-system handover from a first communication system (e.g., a 5GS communication system) to a second communication system (e.g., an EPS communication system). In particular, Figure 1 illustrates a 5GS communication system including a core network (CN) including a CN node (i.e., the Access and Mobility

Management Function (AMF)) and a radio access network (RAN) including a RAN node (i.e., the gNB/ng-eNB) and an EPS communication system including a CN having a CN node (i.e., the Mobility Management Entity (MME)) and a RAN having a RAN node (i.e., the eNB). 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 involves the core networks and may be executed via the SI or N2 interface. During the handover, the MME (in the EPS system) and the AMF (in the 5GS system) 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.

[0004] Stage 2 aspects for inter-system handover between 5GS and EPS are defined in 3GPP TS 23.502 V15.2.0, 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. [0005] When a handover is performed for a wireless device UE from NR to E-UTRA connected to an EPC or 5GC core, the source node (gNB) forwards a

RRCConnectionReconfiguration message from the target inside a MobilityFromNRCommand message. In case of handover from E-UTRA connected to an EPC or 5GC core to NR, or in the case of an 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

RRCConnectionReconfiguration message (if target is LTE) inside a

MobilityFromEUTRACommand message.

[0006] Even though the RRC reconfiguration message transmitted may be the same message used for an intra-RAT/intra-system handover, the procedures the UE performs are covered in inter-RAT procedures.

[0007] Various dual connectivity options are discussed below.

[0008] In 3GPP TS 36.300 V15.2.0, dual connectivity is defined for intra-E-UTRA Dual Connectivity (DC) as depicted in Figure 2, which illustrates the C-plane (control plane) and U- Plane (user plane) connectivity. Both the MeNB and the 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.

[0009] In 3GPP TS 37.340 V15.2.0, dual connectivity is further defined for Multi-RAT Dual Connectivity (MR-DC), which is directed to 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.

[0010] A gNB or ng-eNB are collectively referred to as NG-RAN node.

[0011] 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.

[0012] The dual connectivity case where the master node (MN) and secondary node (SN) are NR nodes is referred to as NR-NR-DC, which has been agreed in RAN 2 meeting (RAN 2 chair notes, 3GPP TSG-RAN WG2 AH#1801, Vancouver, Canada, 22th - 26th January, 2018) to be covered in TS 37.340. C-plane and U-Plane connectivity for NR-NR-DC can be illustrated by Figure 5, as in the case of MR-DC associated with 5GC. [0013] These cases are summarized in Table 1, below.

Table 1 - Dual Connectivity Possibilities

SUMMARY

[0014] A method of performing an inter-system handover of a user equipment, UE, from a source radio access network, RAN, in a source communication system to a target RAN in a target communication system, according to some embodiments is provided, wherein the target RAN operates according to a different radio access technology from the source RAN, the target RAN supports dual connectivity, the source communication system includes a source core network, CN, and the target communication system includes a target CN. The method includes receiving, at the target RAN, a handover request from the target CN; in response to the handover request, adding a target secondary node in the target RAN to support dual connectivity for the UE in the target RAN; and after adding the target secondary node, transmitting a handover request acknowledgement to the target CN.

[0015] The method may further include, after transmitting the handover request acknowledgement, receiving a random access message from the UE at a target master node in the target RAN; receiving a radio resource control, RRC, reconfiguration complete message from the UE in response to the random access procedure; and in response to receiving the RRC reconfiguration complete message, sending an RRC message from the target master node to a target secondary node in the target communication system indicating that RRC reconfiguration of the UE was successful.

[0016] The target RAN may include a 5G RAN and adding the target secondary node may include transmitting an SN Addition Request to the target secondary node. [0017] The target RAN may include a long term evolution, LTE, RAN, and adding the target secondary node may include transmitting an SgNB Addition Request to the target secondary node.

[0018] The method may further include receiving a relocation request from the source CN at the target CN, wherein the handover request is sent in response to the relocation request; receiving the handover request acknowledgement at the target CN; and transmitting a relocation response to the source CN in response to receiving the handover request acknowledgement at the target CN.

[0019] The method may further include receiving the relocation response at the source CN; in response to receiving the relocation response, transmitting a handover command from the source CN to the source RAN; and in response to the handover command, transmitting a release request from a source master node in the source RAN to a source secondary node in the source RAN.

[0020] The target RAN may include a 5G RAN, and the release request may include a SgNB Release Request.

[0021] The source RAN may include an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access, E-UTRA, RAN, and the release request may include an SN Release Request.

[0022] A network node according to some embodiments includes a network interface, a processor circuit coupled to the network interface, and a memory coupled to the processor circuit. The memory includes computer-readable program instructions that, when executed by the processor circuit, cause the processor circuit to perform operations including performing inter-system handover of a user equipment, UE, from a source radio access network, RAN, in a source communication system that operates according to a first radio access technology to a target RAN in a target communication system that operates according to a second radio access technology that is different from the first radio access technology, wherein the target RAN supports dual connectivity, wherein the source communication system includes a source core network, CN, and the target communication system includes a target CN. Performing the inter system handover includes receiving, at the network node, a handover request from the target CN; in response to the handover request, adding a target secondary node in the target RAN to support dual connectivity for the UE in the target RAN; and after adding the target secondary node, transmitting a handover request acknowledgement to the target CN.

[0023] The processor may be further configured to perform operations including, after transmitting the handover request acknowledgement, performing a random access procedure in the target RAN; receiving a radio resource control, RRC, reconfiguration complete message from the UE in response to the random access procedure; and in response to receiving the RRC reconfiguration complete message, sending an RRC message to a target secondary node in the target communication system indicating that RRC reconfiguration of the UE was successful. [0024] The target RAN may include a 5G RAN and adding the target secondary node may include transmitting an SN Addition Request to the target secondary node.

[0025] The target RAN may include a long term evolution, LTE, RAN, and adding the target secondary node may include transmitting an SgNB Addition Request to the target secondary node.

[0026] A target communication system according to some embodiments includes a target radio access network, RAN, and a target core network, CN, wherein the target RAN operates according to a first radio access technology and supports dual connectivity. The system includes a target RAN node in the target RAN configured to receive a handover request from the target CN to receive handover of a user equipment, UE, from a source radio access node that according to a second radio access technology that is different from the first radio access technology, wherein the handover request includes a request to add a target secondary node in the target RAN to support dual connectivity for the UE in the target RAN, and, after adding the target secondary node, to transmit a handover request acknowledgement to the target CN; and a target CN node in the target CN configured to receive a relocation request from a source CN node, to send the handover request in response to the relocation request, to receive the handover request acknowledgement from the target RAN node, and to transmit a relocation response to the source CN node in response to receiving the handover request acknowledgement.

[0027] The target RAN node may be further configured to perform operations including after transmitting the handover request acknowledgement, performing a random access procedure at a target master node in the target RAN; receiving a radio resource control, RRC, reconfiguration complete message from the UE in response to the random access procedure; and in response to receiving the RRC reconfiguration complete message, sending an RRC message from the target master node to a target secondary node in the target RAN indicating that RRC reconfiguration of the UE was successful.

[0028] The target RAN may include a 5G RAN and adding the target secondary node may include transmitting an SN Addition Request to the target secondary node.

[0029] The target RAN may include a long term evolution, LTE, RAN, and adding the target secondary node may include transmitting an SgNB Addition Request to the target secondary node.

[0030] The target CN node may be further configured to perform operations including receiving a relocation request from the source CN, wherein the handover request is sent in response to the relocation request; receiving the handover request acknowledgement; and transmitting a relocation response to the source CN in response to receiving the handover request acknowledgement.

[0031] A method of operating a user equipment, UE, according to some embodiments includes receiving a handover command from a source node in a first radio access network that operates according to a first radio access technology, wherein the handover command instructs the UE to connect to a target node in a second radio access network that operates according to a second radio access technology that is different from the first radio access technology, wherein the handover command includes a secondary node configuration for adding a secondary node in the second radio access network; performing a first random access procedure to access the target node; and performing a second random access procedure to access the secondary node according to the secondary node configuration.

[0032] The may further include transmitting an RRCReconfigurationComplete message or RRCConnectionReconfigurationComplete message to the target node before performing the second random access procedure.

[0033] A user equipment, UE, according to some embodiments includes a processor circuit; a memory coupled to the processor circuit; and a wireless transceiver coupled to the processor circuit. The memory includes computer-readable program instructions that, when executed by the processor circuit, cause the processor circuit to perform operations including receiving a handover command from a source node in a first radio access network that operates according to a first radio access technology, wherein the handover command instructs the UE to connect to a target node in a second radio access network that operates according to a second radio access technology that is different from the first radio access technology, wherein the handover command includes a secondary node configuration for adding a secondary node in the second radio access network; performing a first random access procedure to access the target node; and performing a second random access procedure to access the secondary node according to the secondary node configuration.

[0034] The operations may further include transmitting an

RRCReconfigurationComplete message or RRCConnectionReconfigurationComplete message to the target node before performing the second random access procedure.

BRIEF DESCRIPTION OF THE DRAWINGS

[0035] Figure 1 is a block diagram illustrating inter-system handover from a 5GS source network to an EPS target network.

[0036] Figure 2 illustrates C-Plane and U-Plane connectivity of eNBs involved in Dual Connectivity (DC).

[0037] Figure 3 illustrates C-plane and U-Plane connectivity for EN-DC.

[0038] Figure 4 illustrates C-plane and U-Plane connectivity for NR-NR-DC.

[0039] Figure 5 illustrates various handover possibilities between EPS and 5GS, and within EPS and 5GS. [0040] Figures 6A and 6B are flow diagrams that illustrate an example of signaling flow for a handover from a dual connectivity (source) EPS system to a dual connectivity (target) 5GS system.

[0041] Figures 7A and 7B are flow diagrams that illustrate an example of signaling flow for a handover from a dual connectivity (source) 5GS system to a dual connectivity (target) EPS system.

[0042] Figure 8 is a flow diagram that illustrates an example of signaling flow for a handover from a single connectivity (source) EPS system to a dual connectivity (target) 5GS system.

[0043] Figure 9 is a flow diagram that illustrates an example of signaling flow for a handover from a single connectivity 5GS system to EN-DC or LTE-DC.

[0044] Figures 10A, 10B, 11, 12 and 13 are flowcharts that illustrate operations of systems/methods according to some embodiments.

[0045] Figure 14A is a block diagram illustrating a network node according to some embodiments.

[0046] Figure 14B is a block diagram illustrating a user equipment according to some embodiments.

[0047] Figure 15 is a block diagram of a wireless network in accordance with some embodiments.

[0048] Figure 16 is a block diagram of a user equipment in accordance with some embodiments.

[0049] Figure 17 is a block diagram of a virtualization environment in accordance with some embodiments.

[0050] Figure 18 is a block diagram of a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

[0051] Figure 19 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.

[0052] Figure 20 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.

[0053] Figure 21 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.

[0054] Figure 22 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. [0055] Figure 23 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.

DESCRIPTION OF EMBODIMENTS

[0056] 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.

[0057] 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.

[0058] With the various resulting handover possibilities, improved handover operations may be desired.

[0059] 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 in section 10.4 for EN-DC and MR-DC with 5GC.

[0060] In TS 37.340, handover is covered for dual connectivity scenarios, in the context of an 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, 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) and the latter describing MR-DC with 5GC.

[0061] In an inter-system case, handover procedures may be performed between 5GS and EPS systems, as noted above. If a source MN with a SN connection decides to perform handover to a target node, the 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.

[0062] Handover from single connectivity or dual connectivity systems to dual connectivity systems may be supported for intra-system handover scenarios in TS 36.300 and TS 37.340. However, other dual connectivity handover cases may be possible, considering inter system handover.

[0063] Figure 5 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, in the case of handover to a dual connectivity system. Cases already covered in TS 36.300 and TS 37.340 are depicted in Figure 5 with no shading. The handover scenarios depicted in Figure 5 with single hatching are currently not supported and are the focus of the present disclosure.

[0064] Some embodiments described herein define procedure(s) and associated message flow(s) to support inter-system handover that includes dual connectivity setup at the target system, specifically the procedures for handover between 5GS and EPS, with the possibility to perform SN addition at the target as a part of the handover procedure. In particular, the addition of the SN is performed as part of the inter-system handover procedure rather than an additional procedure performed after the inter-system handover is completed.

[0065] Some embodiments described herein may enable a faster dual connectivity set up in the target MN compared with performing a handover and afterwards adding a SN, since SN addition will be jointly performed in the handover procedure. Some embodiments described herein cover handovers from either single connectivity or dual connectivity to NR-NR- DC, NE-DC, NG-EN-DC, or LTE DC during an inter-RAT or inter-system handover.

[0066] To enable handover from a source node or source MN and SN to a target MN and SN, the target MN may add the target SN before acknowledging the handover request from the CN. In the case of a source MN and SN, the source MN may also release the source SN after receiving the handover command from the CN.

[0067] An example of the inter-system procedures for handover from a source node or source MN and SN to a target MN and SN is described below in connection with Figures 6A and 6B. In particular, Figures 6A and 6B illustrate an example of signaling flow for a handover from an EN-DC or LTE-DC to MR-DC (including NG-EN-DC, EN-DC and NE-DC) or NR-NR-DC. That is, Figures 6A and 6B illustrate an example of signaling flow for a handover from a dual

connectivity (source) EPS system 250 to a dual connectivity (target) 5GS system 350.

[0068] Referring to Figure 6A, handover operations for a handover of a UE 100 from EN- DC or LTE-DC to MR-DC (including NG-EN-DC, EN-DC and NE-DC) or NR-NR-DC are initiated by a source radio network 200 (block 602) that currently serves the UE. In this example, the radio access technology (RAT) of the source radio network 200 is E-UTRAN. When the source radio network 200 determines that handover to a target radio network 300 that operates according to a different RAT is desired, the source radio network 200 sends a handover required message 604 to the core network 400 in the EPS 250. In this example, the target radio network 300 is an NG-RAN network.

[0069] In this example, the source core network 400 is an EPC network, and the handover required message 604 is sent to the mobility management entity (MME) 410 in the source core network 400.

[0070] Upon receipt of the handover required message, the MME 410 sends a forward relocation request 606 to the target core network 500. In this example, the target core network 500 is a 5GC core network in the 5GS system 350, and the forward relocation request 606 is sent to the access and mobility management function (AMF) 510 of the target core network 500.

[0071] The AMF 510 sends a handover request 608 to the target radio network 300 informing it of the handover.

[0072] Upon receiving the handover request, the target radio network 300 performs a secondary node addition procedure 610 to add a secondary node for providing dual connectivity service to the UE 100. The target radio network 300 then transmits a handover request acknowledgement 612 back to the AMF 510, which then sends a forward relocation request response 614 to the MME 410 in the source core network 400.

[0073] Some operations of Figure 6A are illustrated in more detail in Figure 6B along with further operations. Referring to Figures 6A and 6B, handover operations for a handover of a UE 100 from the EPS 250 to the 5GS 350 with dual connectivity include the following:

[0074] Operation 1. Initially, steps 1-9 from clause 4.11.1.2.2.2 in TS 23.502 are performed for the handover preparation phase when the source RAN 200 transmits a handover required message 604 to the source CN 400. A forward relocation request 606 is then transmitted from the source CN 400 (namely, from the source MME 410) to the target 5GC CN (namely, the AMF 510). A handover request 608 is then transmitted from the AMF to the NG- RAN 300 in the 5GS 350.

[0075] Operation 2. Upon receipt at the NG-RAN of the handover request, the target master node (T-MN) in the NG-RAN initiates a secondary node (SN) addition procedure 610 by sending an SN Addition Request 620 to the target SN (T-SN) in the NG-RAN 300.

[0076] Operation 3. The target SN replies with an SN Addition Request Acknowledge message 622. If data forwarding is needed, the target SN may provide forwarding addresses to the target MN.

[0077] Operation 4. Steps 10-15 from clause 4.11.1.2.2.2 in TS 23.502 are then performed for the handover preparation phase. In particular, the NG-RAN 300 may transmit a handover request acknowledgement 612 to the AMF 510 at this point, and the AMF 510 may reply to the forward relocation request 606 from the source MME 410 with a forward relocation request response 614. [0078] Operation 5. Referring to Figure 6B, the source MME 410 sends a Handover Command message 624 to the source MN. This message conveys a Target to Source

transparent container, generated by the target MN, to be sent to the UE 100 as an MN RRC message including a SN RRC configuration message which also includes the SCG configuration, to perform the handover, and may also provide forwarding addresses to the source MN.

[0079] Operation 6. The source MN initiates the release of the source SN resources towards the source SN by sending a SgNB Release Request (6a) 626 including a Cause indicating MCG mobility. The source SN acknowledges the release request via a SgNB Release Request Acknowledge message (6b) 628. If data forwarding is needed, the source MN provides data forwarding addresses 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.

[0080] Operation 7. The source MN triggers the UE to perform a handover with a handover command message 630 (which may be a MobilityFromEUTRACommand message) and apply the new configuration.

[0081] Operations 8/9. The UE synchronizes to the target MN via a random access procedure 632 and replies with an RRC message 634 (e.g., RRCReconfigurationComplete) to the target MN (which may be, for example, a gNB or ng-eNB).

[0082] Operation 10. The UE synchronizes to the target SN via random access procedure 636.

[0083] Operation 11. If the RRC reconfiguration procedure was successful, the target MN informs the target SN via the applicable RRC message 638 (e.g.,

SNReconfigurationComplete) for the corresponding SN (gNB or ng-eNB).

[0084] Operation 12. If applicable, data forwarding takes place from source MN and SN to target MN and SN.

[0085] Operation 13. Steps 4-13 from clause 4.11.1.2.2.3 in TS 23.502 are then performed for the handover execution phase.

[0086] Operation 14. Upon reception of a UE Context Release message 640 from the MME (from clause 4.11.1.2.2.3 in TS 23.502, which is part of the handover execution phase), the source MN initiates a 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.

[0087] A further example of procedures for inter-system handover is described below in connection with Figures 7A and 7B. In particular, Figures 7A and 7B illustrate an example of signaling flow for a handover from MR-DC (including NG-EN-DC, EN-DC and NE-DC) or NR-NR- DC to EN-DC or LTE-DC. That is, Figures 7A and 7B illustrate an example of signaling flow for a handover from a dual connectivity (source) 5GS system 350 to a dual connectivity (target) EPS system 250. [0088] Referring to Figure 7A, handover operations for a handover of a UE 100 from MR-DC (including NG-EN-DC, EN-DC and NE-DC) or NR-NR-DC to EN-DC or LTE-DC are initiated by a source radio network 300 (block 702) that currently serves the UE 100. In this example, the radio access technology (RAT) of the source radio network 300 is NG-RAN. When the source radio network 300 determines that handover to a target radio network 200 that operates according to a different RAT is desired, the source radio network 300 sends a handover required message 704 to the core network 500 in the 5GS 350. In this example, the target radio network 200 is an E-UTRAN network.

[0089] In this example, the source core network 500 is a 5GC network, and the handover required message 704 is sent to the access and mobility management function 510 in the source core network 500.

[0090] Upon receipt of the handover required message, the AMF 510 sends a relocation request 706 to the target core network 400. In this example, the target core network 400 is an EPC core network in the EPS system 250, and the relocation request 706 is sent to the mobility management entity (MME) 410 of the target core network 400.

[0091] The MME 410 sends a handover request 708 to the target radio network 200 informing it of the handover.

[0092] Upon receiving the handover request, the target radio network 200 performs a secondary node addition procedure 710 to add a secondary node for providing dual connectivity service to the UE 100. The target radio network 200 then transmits a handover request acknowledgement 712 back to the MME 410, which then sends a relocation request response 714 to the AMF 510 in the source core network 500.

[0093] Some operations of Figure 7A are illustrated in more detail in Figure 7B along with further operations. Referring to Figures 7A and 7B, handover operations for a handover of a UE 100 from the 5GS 350 to the EPS 250 with dual connectivity include the following:

[0094] Operation 1. Steps 1-6 from clause 4.11.1.2.1 in TS 23.502 for handover from 5GS to EPS are performed. In particular, the source NG-RAN 300 sends a handover required message 704 to the source AMF 510 in the source CN 500. In response, the source AMF 510 sends a relocation request 706 to the target MME 410 in the target CN 400, and the target MME 410 sends a handover request 708 to the target RAN 200.

[0095] Operation 2. Referring to Figure 7B, in response to the handover request (and before the target RAN acknowledges the handover request), the target MN sends an SgNB Addition Request 720 to the target SN as part of a SN addition procedure 710.

[0096] Operation 3. The target SN replies with SgNB Addition Request Acknowledge 722. If data forwarding is needed, the target SN provides forwarding addresses to the target MN.

[0097] Operation 4. Steps 7-10 from clause 4.11.1.2.1 in TS 23.502 for handover from 5GS to EPS are then performed, including steps 10a, 10b and 10c. In particular, after receiving the SgNB Addition Request Acknowledge, the target RAN sends an acknowledgement 712 of the handover request to the target MME.

[0098] Operation 5. The AMF 510 in the source CN 500 then sends a Handover

Command 724 message to the source MN node. This message conveys a Target to Source transparent container, generated by the target MN, to be sent to the UE 100 as an E-UTRA RRC message, including a NR RRC configuration message which also includes the SCG configuration, to perform the handover, and may also provide forwarding addresses to the source MN node.

[0099] Operation 6. The source MN initiates the release of the source SN resources towards the source SN by sending an SN Release Request (6a) 726 including a Cause indicating MCG mobility to the source SN. The source SN acknowledges the release request in a message (6b) 728. 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.

[0100] Operation 7. The source MN node triggers the UE 100 to perform handover via a handover command 730 (with a MobilityFromEUTRACommand or MobilityFromNRCommand message) and apply the new configuration.

[0101] Operations 8/9. The UE 100 then synchronizes to the target MN via a random access procedure 732 and, upon successful synchronization, transmits an

RRCConnectionReconfigurationComplete message 734 to the target MN.

[0102] Operation 10. The UE 100 then synchronizes to the target SN via a random access procedure 736.

[0103] Operation 11. If the RRC connection reconfiguration procedure was successful, the target MN informs the target SN via a SgNB Reconfiguration Complete message 738.

[0104] Operation 12. If applicable, data forwarding takes place from source MN and SN to target MN and SN.

[0105] Operation 13. Steps 12b-21 from clause 4.11.1.2.1 in TS 23.502 for handover from 5GS to EPS are then performed, including steps 12b, 12c and 12d.

[0106] Operation 14. Upon reception of a UE Context Release message 740 from the AMF (from clause 4.11.1.2.1 in TS 23.502), 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.

[0107] A further example of procedures for inter-system handover is described below in connection with Figure 8. In particular, Figure 8 illustrates an example of signaling flow for a handover from a single connectivity EPS system to MR-DC (including NG-EN-DC, EN-DC and NE- DC) or NR-NR-DC. That is, Figure 8 illustrates an example of signaling flow for a handover from a single connectivity (source) EPS system to a dual connectivity (target) 5GS system. [0108] The eNB to MN change procedure shown in Figure 8 is used to transfer UE context data from a source eNB to a target NG-RAN MN that adds an SN during the handover. Referring to Figure 8:

[0109] Operation 1. Steps 1-9 from clause 4.11.1.2.2.2 in TS 23.502 ("EPS to 5GS handover using N26 interface") for handover preparation phase are performed for the handover preparation phase when the source RAN transmits a handover required message to the source CN. A forward relocation request is then transmitted from the EPS CN (namely, from the source MME) to the target 5GC CN (namely, the AMF). A handover request is then transmitted from the AMF to the NG-RAN in the 5GS.

[0110] Operation 2. If the target MN, based on the measurement results received during the handover preparation part 1, decides to initiate DC, it sends a SN Addition Request 620 in an SN addition procedure 610 to the target SN.

[0111] Operation 3. The target SN replies with SN Addition Request Acknowledge 622. If data forwarding is needed, the target SN provides forwarding addresses to the target MN.

[0112] Operation 4. Step 10-15 from clause 4.11.1.2.2.2 in TS 23.502 are then performed for handover preparation phase. In particular, the NG-RAN may transmit a handover request acknowledgement to the AMF at this point, and the AMF may reply to the forward relocation request from the source MME.

[0113] Operation 5. The source MME sends a Handover Command message 624 to the source eNodeB. This message conveys a Target to Source transparent container, generated by the target MN, to be sent to the UE as an MN RRC message including a SN RRC configuration message which also includes the SCG configuration, to perform the handover, and may also provide forwarding addresses to the source eNB.

[0114] Operation 6. The source eNB triggers the UE to perform handover with a MobilityFromEUTRACommand message 630 and apply the new configuration.

[0115] Operations 7/8. The UE synchronizes to the target MN via random access procedure 632 and replies with a RRCReconfigurationComplete message 634 to the MN.

[0116] Operation 9. The UE synchronizes to the target SN via random access procedure 636.

[0117] Operation 10. If the RRC reconfiguration procedure was successful, the target MN informs the target SN via SN Reconfiguration Complete message 638.

[0118] Operation 11. If applicable, data forwarding takes place from source MN to target MN and SN.

[0119] Operation 12. Steps 4-13 from clause 4.11.1.2.2.3 in TS 23.502 are then performed for the handover execution phase.

[0120] A further example of the inter-system procedures for handover is described below in connection with Figure 9. In particular, Figure 9 illustrates an example of signaling flow for a handover from a single connectivity 5GS system to EN-DC or LTE-DC. That is, Figure 9 illustrates an example of signaling flow for a handover from a single connectivity (source) 5GS system to a dual connectivity (target) EPS system. The NG-RAN to MN change procedure is used to transfer UE context data from a source NG-RAN node (ng-eNB or gNB) to a target MN connected to EPC, that adds an SN during the handover. Accordingly, Figure 9 shows an example signalling flow for a NG-RAN to EN-DC or LTE-DC change procedure, with SN addition. Referring to Figure 9:

[0121] Operation 1. Step 1-6 from clause 4.11.1.2.1 in TS 23.502 for handover from 5GS to EPS. In particular, the source NG-RAN sends a handover required message to the source AMF in the source CN. In response, the source AMF sends a relocation request to the target MME in the target CN, and the target MME sends a handover request to the target RAN.

[0122] Operation 2. Next, before acknowledging the handover request from the target MME, the target MN, based on the measurement results received during the handover preparation part 1, decides to initiate DC, and sends a SgNB Addition Request 720 to the target SN as part of an SN addition procedure 710.

[0123] Operation 3. The target SN replies with SgNB Addition Request Acknowledge 722. If data forwarding is needed, the target SN provides forwarding addresses to the target MN.

[0124] Operation 4. Step 7-10 from clause 4.11.1.2.1 in TS 23.502 for handover from 5GS to EPS, including 10a, 10b and 10c.

[0125] Operation 5. The AMF sends a Handover Command message 724 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 the SCG

configuration, to perform the handover, and may also provide forwarding addresses to the source NG-RAN node.

[0126] Operation 6. The source NG-RAN node triggers the UE to perform handover via a handover command 730 (e.g., a MobilityFromEUTRACommand or MobilityFromNRCommand message) and apply the new configuration.

[0127] Operations 7/8. The UE synchronizes to the target MN via random access procedure 732 and replies with MN RRCConnectionReconfigurationComplete message 734.

[0128] Operation 9. The UE synchronizes to the target SN via random access procedure 736.

[0129] Operation 10. If the RRC connection reconfiguration procedure was successful, the target MN informs the target SN via SgNB Reconfiguration Complete message 738.

[0130] Operation 11. If applicable, data forwarding takes place from source MN to target MN and SN.

[0131] Operation 12. Step 12b-21 from clause 4.11.1.2.1 in TS 23.502 for handover from 5GS to EPS, including 12b, 12c and 12d.

[0132] Stage 3 operation for dual connectivity handover. [0133] In order to setup dual connectivity during inter-RAT and inter-system handover, the UE must receive the secondary node configurations during the handover. As intra-RAT, intra-system handover already supports configuring a secondary node during handover, similar procedures can be employed.

[0134] If the target mode is LTE DC, the MobilityFromEUTRACommand or

MobilityFromNRCommand will contain a RRCConnectionReconfiguration message that includes SCG reconfigurations for example in the scg-Configuration-rl2 IE which allows the configuration of a secondary eNB.

SCG-Configuration-rl2 ::= CHOICE {

release NULL,

setup SEQUENCE {

scg-ConfigPartMCG-rl2 SEQUENCE {

scg-Counter-rl2 INTEGER (0.. 65535) OPTIONAL, - Need ON

powerCoordinationlnfo-rl2 powerCoordinationlnfo-rl2

OPTIONAL, - Need ON

} OPTIONAL, - Need ON

scg-ConfigPartSCG-rl2 SCG-ConfigPartSCG-rl2 OPTIONAL - Need ON

}

[0135] If the target mode is EN-DC; the MobilityFromEUTRACommand or

MobilityFromNRCommand will contain a RRCConnectionReconfiguration message that includes SCG reconfigurations for example in the nr-Config-rl5 along with the sk-Counter and nr- RadioBearerConfigl/2, which allows the configuration of a secondary en-gNB.

RRCConnectionReconfiguration-vl510-IEs ::= SEQUENCE {

nr-Config-rl5 CHOICE {

release NULL,

setup SEQUENCE {

endc-ReleaseAndAdd-rl5 BOOLEAN,

nr-SecondaryCellGroupConfig-rl5 OCTET STRING OPTIONAL, Need ON p-MaxEUTRA-rl5 P-Max OPTIONAL, - Need ON

}

}

OPTIONAL, - Need ON

sk-Counter-rl5 INTEGER (0.. 65535) OPTIONAL, - Need ON nr-RadioBearerConfigl-rl5 OCTET STRING OPTIONAL, - Need ON nr-RadioBearerConfig2-rl5 OCTET STRING OPTIONAL, - Need ON tdm-PatternConfig-rl5 CHOICE {

release NULL,

setup SEQUENCE {

subframeAssignment-rl5 SubframeAssignment-rl5,

harq-Offset-rl5 INTEGER (0.. 9)

}

[0136] If the target is NGEN-DC, the MobilityFromEUTRACommand will contain a RRCConnectionReconfiguration message that includes SCG reconfigurations for example the nr- Config-rl5, could be reused. However, it is also possible to introduce a new IE, with similar content. For NGEN-DC, the UE would need the RadioBearerConfig, and the

secondaryCellGroupConfig and the sk-Counter.

[0137] If the target is NE-DC or NN-DC, the MobilityFromEUTRACommand will contain a RRCReconfiguration message that includes SCG reconfigurations for example the

RadioBearerConfig and CellGroupConfig for the SN as well as an IE containing the sk-Counter

RRCReconfiguration-IEs ::= SEQUENCE {

radioBearerConfig RadioBearerConfig OPTIONAL, -- Need M secondaryCellGroup OCTET STRING (CONTAINING CellGroupConfig)

OPTIONAL, - Need M

measConfig MeasConfig OPTIONAL, -- Need M

lateNonCritical Extension OCTET STRING OPTIONAL,

nonCriticalExtension RRCReconfiguration-vxx-IEs OPTIONAL

}

RRCReconfiguration-vxx-IEs ::= SEQUENCE {

masterCellGroup OCTET STRING (CONTAINING CellGroupConfig) OPTIONAL, -

Need M

fullConfig ENUMERATED {true} OPTIONAL, - Need N

dedicatedNAS-MessageList SEQUENCE (SIZE(l..maxDRB)) OF DedicatedlnfoNAS

OPTIONAL, - Cond nonHO

keyRefresh KeyRefresh OPTIONAL, -- Cond MasterKeyChange dedicatedSIBl-Deli ery OCTET STRING (CONTAINING SIB1) OPTIONAL,

dedicatedSystemlnformationDelivery OCTET STRING (CONTAINING

Systemlnformation) OPTIONAL,

nonCriticalExtension SEQUENCE {} OPTIONAL

}

KeyRefresh ::= SEQUENCE {

keySetChangelndicator BOOLEAN OPTIONAL, - Cond MasterKeyChange nextHopChainingCount NextHopChainingCount OPTIONAL, - Cond MasterKeyChangeNCC

n2ModeNAS-Container OCTET STRING OPTIONAL, - Cond InterSystemHO sk-Counter INTEGER (0.. 65535) OPTIONAL, - Cond SN-

AddMod

} [0138] Some embodiments of inventive concepts may thus provide the exchange of messages in handover between EPS and 5GS, from a source node or MN and SN to a target MN and SN. 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.

[0139] Operations according to some embodiments are illustrated in Figure 10A. As shown therein, some embodiments provide a method of performing an inter-system handover of a user equipment, UE, from a source radio access network, RAN, in a source communication system to a target RAN in a target communication system, wherein the target RAN supports dual connectivity, wherein the source communication system includes a source core network, CN, and the target communication system includes a target CN. The method includes receiving (1002), at the target RAN, a handover request from the target CN. In response to the handover request, the target RAN adds (1004) a target secondary node in the target RAN to support dual connectivity for the UE in the target RAN, and after adding the target secondary node, transmits (1006) a handover request acknowledgement to the target CN.

[0140] Further operations are illustrated in Figure 10B. As shown therein, the methods may include, after transmitting the handover request acknowledgement, receiving (1012) a random access message from the UE at a target master node in the target RAN and performing a random access procedure in response to the random access message, receiving (1014) a radio resource control, RRC, reconfiguration complete message from the UE in response to the random access procedure, and in response to receiving the RRC reconfiguration complete message, sending (1016) an RRC message from the target master node to a target secondary node in the target communication system indicating that RRC reconfiguration of the UE was successful.

[0141] Operations of a UE 100 according to some embodiments are illustrated in Figure 11. As shown therein, the operations may include receiving (1102) a handover command (630) from a source node in a first radio access network that operates according to a first radio access technology, wherein the handover command instructs the UE to connect to a target node in a second radio access network that operates according to a second radio access technology that is different from the first radio access technology. The handover command further includes a secondary node configuration for adding a secondary node in the second radio access network. The method further includes performing (1104) a first random access procedure (632) to access the target master node, and performing (1106) a second random access procedure (636) to access the secondary node according to the secondary node configuration

[0142] Further operations are illustrated in Figure 12. As shown therein, operations according to some embodiments may include receiving (1202) a forward relocation request from the source CN at the target CN, wherein the handover request is sent in response to the forward relocation request, receiving (1204) the handover request acknowledgement at the target CN, and transmitting (1206) a forward relocation response to the source CN in response to receiving the handover request acknowledgement at the target CN.

[0143] Further operations are illustrated in Figure 13. As shown therein, operations according to some embodiments may include receiving (1302) the forward relocation response at the source CN, in response to receiving the forward relocation response, transmitting (1304) a handover command from the source CN to the source RAN, and in response to the handover command, transmitting (1306) a release request from a source master node in the source RAN to a source secondary node in the source RAN.

[0144] Figure 14A is a block diagram illustrating elements of a network node 1400 of a communication system. The network node 1400 is configured to perform operations according to embodiments disclosed herein.

[0145] The network node 1400 may implement a RAN node and/or a CN node in the communication system. As shown, the network node may include a network interface circuit 1407 (also referred to as a network interface) configured to provide communications with other nodes (e.g., with other base stations, RAN nodes and/or core network nodes) of the

communication network. The network node 1400 may also include a wireless transceiver circuit 1402 for providing a wireless communication interface with UEs. The network node 1400 may also include a processor circuit 1403 (also referred to as a processor) coupled to the transceiver circuit 1402 and the network interface 1407, and a memory circuit 1405 (also referred to as memory) coupled to the processor circuit. The memory circuit 1405 may include computer readable program code that when executed by the processor circuit 1403 causes the processor circuit to perform operations according to embodiments disclosed herein. According to other embodiments, processor circuit 1403 may be defined to include memory so that a separate memory circuit is not required.

[0146] As discussed herein, operations of the network node may be performed by processor 1403, the wireless transceiver circuit 1402 and/or the network interface 1407. For example, the processor 1403 may control the network interface 1407 to transmit

communications through network interface 1407 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 1405, and these modules may provide instructions so that when instructions of a module are executed by processor 1403, processor 1403 performs respective operations (e.g., operations discussed herein with respect to Example Embodiments).

[0147] Figure 14B is a block diagram illustrating elements of a user equipment, UE, 1500 of a communication system. The UE 1500 is configured to perform operations according to embodiments disclosed herein

[0148] According to a further embodiment the UE 1500 includes a wireless transceiver circuit 1502 for providing a wireless communication interface with network nodes. The UE 1500 also includes a processor circuit 1503 (also referred to as a processor) coupled to the transceiver circuit 1502 and the network interface 1507, and a memory circuit 1505 (also referred to as memory) coupled to the processor circuit. The memory circuit 1505 may include computer readable program code that when executed by the processor circuit 1503 causes the processor circuit to perform operations according to embodiments disclosed herein. According to other embodiments, processor circuit 1503 may be defined to include memory so that a separate memory circuit is not required.

[0149] As discussed herein, operations of the UE may be performed by processor circuit 1503 and/or the wireless transceiver circuit 1502. For example, the processor circuit 1503 may control the wireless transceiver circuit 1502 to transmit communications to one or more other network nodes and/or to receive communications from one or more network nodes.

Moreover, modules may be stored in memory 1505, and these modules may provide instructions so that when instructions of a module are executed by processor circuit 1503, processor circuit 1503 performs respective operations discussed herein.

[0150] The following are certain enumerated embodiments further illustrating various aspects of the disclosed subject matter:

Embodiment 1. A method of performing an inter-system handover of a user equipment, UE, from a source radio access network, RAN, in a source communication system to a target RAN in a target communication system, wherein the target RAN supports dual connectivity, wherein the source communication system includes a source core network, CN, and the target communication system includes a target CN, the method comprising: receiving (1002), at the target RAN, a handover request from the target CN; in response to the handover request, adding (1004) a target secondary node in the target RAN to support dual connectivity for the UE in the target RAN; and after adding the target secondary node, transmitting (1006) a handover request acknowledgement to the target CN.

Embodiment 2. The method of Embodiment 1, further comprising: after transmitting the handover request acknowledgement, performing (1102) a random access procedure at a target master node in the target RAN; receiving (1104) a radio resource control, RRC, reconfiguration complete message from the UE in response to the random access procedure; and in response to receiving the RRC reconfiguration complete message, sending (1106) an RRC message from the target master node to a target secondary node in the target

communication system indicating that RRC reconfiguration of the UE was successful.

Embodiment 3. The method of Embodiment 1, wherein the target RAN comprises a 5G RAN, and wherein adding the target secondary node comprises transmitting an SN

Addition Request to the target secondary node.

Embodiment 4. The method of Embodiment 1, wherein the target RAN comprises a long term evolution, LTE, RAN, and wherein adding the target secondary node comprises transmitting an SgNB Addition Request to the target secondary node.

Embodiment 5. The method of Embodiment 1, further comprising: receiving (1202) a forward relocation request from the source CN at the target CN, wherein the handover request is sent in response to the forward relocation request; receiving (1204) the handover request acknowledgement at the target CN; and transmitting (1206) a forward relocation response to the source CN in response to receiving the handover request acknowledgement at the target CN.

Embodiment 6. The method of Embodiment 5, further comprising: receiving (1302) the forward relocation response at the source CN; in response to receiving the forward relocation response, transmitting (1304) a handover command from the source CN to the source RAN; and in response to the handover command, transmitting (1306) a release request from a source master node in the source RAN to a source secondary node in the source RAN.

Embodiment 7. The method of Embodiment 6, wherein the target RAN comprises a 5G RAN, and wherein the release request comprises a SgNB Release Request.

Embodiment 8. The method of Embodiment 6, wherein the source RAN comprises a long term evolution, LTE, RAN, and wherein the release request comprises an SN Release Request.

Embodiment 9. A network node (1400), comprising: a network interface (1407); and a processor (1403) coupled to the network interface, wherein the processor is configured to provide network communications through the network interface, and wherein the processor is configured to perform operations of performing inter-system handover of a user equipment, UE, from a source radio access network, RAN, in a source communication system to a target RAN in a target communication system, wherein the target RAN supports dual connectivity, wherein the source communication system includes a source core network, CN, and the target communication system includes a target CN, the operations comprising: receiving (1002), at the network node, a handover request from the target CN; in response to the handover request, adding (1004) a target secondary node in the target RAN to support dual connectivity for the UE in the target RAN; and after adding the target secondary node, transmitting (1006) a handover request acknowledgement to the target CN.

Embodiment 10. The network node of Embodiment 9, wherein the processor is further configured to perform operations comprising: after transmitting the handover request acknowledgement, performing (1102) a random access procedure in the target RAN; receiving (1104) a radio resource control, RRC, reconfiguration complete message from the UE in response to the random access procedure; and in response to receiving the RRC reconfiguration complete message, sending (1106) an RRC message to a target secondary node in the target communication system indicating that RRC reconfiguration of the UE was successful.

Embodiment 11. The network node of Embodiment 9, wherein the target RAN comprises a 5G RAN, and wherein adding the target secondary node comprises transmitting an SN Addition Request to the target secondary node.

Embodiment 12. The network node of Embodiment 9, wherein the target RAN comprises a long term evolution, LTE, RAN, and wherein adding the target secondary node comprises transmitting an SgNB Addition Request to the target secondary node.

Embodiment 13. A target communication system including a target radio access network, RAN, and a target core network, CN, wherein the target RAN supports dual connectivity, comprising: a target RAN node (1400) in the target RAN configured to receive a handover request from the target CN, to add a target secondary node in the target RAN in response to the handover request to support dual connectivity for the UE in the target RAN, and, after adding the target secondary node, to transmit a handover request acknowledgement to the target CN; and a target CN node (1400) in the target CN configured to receive a forward relocation request from a source CN node, to send the handover request in response to the forward relocation request, to receive the handover request acknowledgement from the target RAN node, and to transmit a forward relocation response to the source CN node in response to receiving the handover request acknowledgement.

[0151] 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 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

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 15: 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 15. For simplicity, the wireless network of Figure 15 only depicts network OQ.106, network nodes OO160 and OO160b, and WDs OO110, OOHOb, and OOHOc (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 00160 and wireless device (WD) OO110 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 Q.Q.106 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 OO160 and WD Q.Q.110 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 15, network node OQ.160 includes processing circuitry OO170, device readable medium OO180, interface 00190, auxiliary equipment 00184, power source 00186, power circuitry QQ187, and antenna Q.Q.162. Although network node Q.Q.160 illustrated in the example wireless network of Figure 15 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 Q.Q.160 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 Q.Q.170 may include one or more of radio frequency (RF) transceiver circuitry Q.Q.172 and baseband processing circuitry Q.Q.174. In some embodiments, radio frequency (RF) transceiver circuitry Q.Q.172 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 Q.Q.110. 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 Q.Q.162. Similarly, when receiving data, antenna Q.Q.162 may collect radio signals which are then converted into digital data by radio front end circuitry Q.Q.192. The digital data may be passed to processing circuitry Q.Q.170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node Q.Q.160 may not include separate radio front end circuitry Q.Q.192, 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 QQ186. Power source QQ186 and/or power circuitry QQ187 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 Q.Q.187. 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 Q.Q.160 may include additional components beyond those shown in Figure 15 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 Q.Q.160 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 (loT) 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 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a 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 Q.Q.110 includes antenna QQ111, interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source Q.Q.136 and power circuitry Q.Q.137. WD Q.Q.110 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 QQ118 and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. 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 Q.Q.126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry Q.Q.120 of WD QQ110 may comprise a SOC. In some embodiments, RF transceiver circuitry Q.Q.122, baseband processing circuitry Q.Q.124, and application processing circuitry Q.Q.126 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 Q.Q.132 may be operable to produce output to the user and to allow the user to provide input to WD Q.Q.110. The type of interaction may vary depending on the type of user interface equipment Q.Q.132 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 Q.Q.110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD Q.Q.110 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 Q.Q.110 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 Q.Q.110 to which power is supplied.

Figure 16: User Equipment in accordance with some embodiments

Figure 16 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 Q.Q.2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE Q.Q.200, as illustrated in Figure 16, 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 16 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In Figure 16, UE Q.Q.200 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 16, 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 16, 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 16, RF interface 00209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 00211 may be configured to provide a communication interface to network 0.0.243a. Network 00243a 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 00243a may comprise a Wi-Fi network. Network connection interface 00211 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 00211 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 00217 may be configured to interface via bus 00202 to processing circuitry 00201 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 00219 may be configured to provide computer instructions or data to processing circuitry 00201. For example, ROM 00219 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 00221 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 00221 may be configured to include operating system 00223, application program 00225 such as a web browser application, a widget or gadget engine or another application, and data file 00227. Storage medium 00221 may store, for use by UE 00200, any of a variety of various operating systems or combinations of operating systems.

Storage medium 00221 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 00221 may allow UE 00200 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 00221, which may comprise a device readable medium.

In Figure 16, processing circuitry OO201 may be configured to communicate with network 0.0.243b using communication subsystem 00231. Network 00243a and network 00243b may be the same network or networks or different network or networks.

Communication subsystem 00231 may be configured to include one or more transceivers used to communicate with network 00243b. For example, communication subsystem 00231 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.OO2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 00233 and/or receiver 00235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 00233 and receiver 00235 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 00231 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 00231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 00243b 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 00243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 00213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 00200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 00200 or partitioned across multiple components of UE 00200.

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 00231 may be configured to include any of the components described herein. Further, processing circuitry 00201 may be configured to communicate with any of such components over bus 00202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 00201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 00201 and communication subsystem 00231. 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 17: Virtualization environment in accordance with some embodiments

Figure 17 is a schematic block diagram illustrating a virtualization environment 00300 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 Q.Q.300 hosted by one or more of hardware nodes Q.Q.330. 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 Q.Q.320 (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 Q.Q.320 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 Q.Q.350 may present a virtual operating platform that appears like networking hardware to virtual machine Q.Q.340.

As shown in Figure 17, hardware Q.Q.330 may be a standalone network node with generic or specific components. Hardware Q.Q.330 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 17.

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 18: Telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments.

With reference to FIGURE 18, 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 QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c. A second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs 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 Q.Q.412.

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 Q.Q.421 and QQ422 between telecommunication network Q.Q.410 and host computer Q.Q.430 may extend directly from core network Q.Q.414 to host computer QQ430 or may go via an optional intermediate network Q.Q.420. Intermediate network Q.Q.420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network Q.Q.420, 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 18 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 Q.Q.411, 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 19: 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 19. 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 Q.Q.525 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 19) 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 19) 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 19 may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, Q.Q412C and one of UEs QQ491, QQ492 of Figure 18, respectively. This is to say, the inner workings of these entities may be as shown in Figure 19 and independently, the surrounding network topology may be that of Figure 18.

In Figure 19, 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 Q.Q.570 between UE Q.Q.530 and base station Q.Q.520 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 Q.Q.530 using OTT connection OO550, 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 OQ550 may be implemented in software 00511 and hardware 00515 of host computer 00510 or in software 00531 and hardware 00535 of UE OO530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection OO550 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 00511, 00531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection OO550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station OO520, and it may be unknown or imperceptible to base station OO520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer OO510's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 00511 and 00531 causes messages to be transmitted, in particular empty or 'dummy' messages, using OTT connection OO550 while it monitors propagation times, errors etc.

Figure 20: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

Figure 20 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 18 and 19. For simplicity of the present disclosure, only drawing references to Figure 20 will be included in this section. In step 00610, the host computer provides user data. In substep 00611 (which may be optional) of step 00610, the host computer provides the user data by executing a host application. In step OO620, the host computer initiates a transmission carrying the user data to the UE. In step OO630 (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 OO640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer. Figure 21: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

Figure 21 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 18 and 19. For simplicity of the present disclosure, only drawing references to Figure 21 will be included in this section. In step Q.Q.710 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 Q.Q.720, 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 22: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

Figure 22 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 18 and 19. For simplicity of the present disclosure, only drawing references to Figure 22 will be included in this section. In step Q.Q.810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step Q.Q.820, the UE provides user data. In substep Q.Q.821 (which may be optional) of step Q.Q.820, 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 23: Methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

Figure 23 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 18 and 19. For simplicity of the present disclosure, only drawing references to Figure 23 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.