Network initiated inter-RAT handover

1. A method implemented by a Mobility Management node in a core network of handing over a User Equipment (UE) from a first type of Radio Access Technology (RAT) to a second type of RAT, wherein the UE is attached to the core network via a Radio Access Network (RAN) utilizing the first type of RAT, the method comprising:

receiving, from a network function in the core network, an indication that a particular service is to be invoked for the UE, wherein the indication is received prior to setup of a Quality of Service (QoS) flow for the particular service;

determining that the UE is to be handed over from the first type of RAT to the second type of RAT for supporting the particular service;

responsive to determining that the UE is to be handed over to the second type of RAT, sending an indication to wait for confirmation that the handover is completed before continuing with the setup of the QoS flow; and

requesting, by the Mobility Management node, the RAN to hand over the UE from the first RAT to the second RAT before the setup of the QoS flow for the particular service for the UE is completed.

2. The method of claim 1 , wherein the method further comprises, prior to the receiving, the Mobility Management node subscribing to the network function for receiving notifications whenever the particular service is to be invoked for the UE.

3. The method of claim 1 , wherein the method further comprises informing, by the Mobility Management node, the network function that the UE is to be handed over from the first RAT to the second RAT for the particular service.

4. The method of claim 1 , wherein the method further comprises:

receiving a confirmation from the RAN that the UE is handed over from the first RAT to the second RAT, the confirmation being a confirmation of mobility for the UE;

transmitting the confirmation to the network function.

5. The method of claim 1 , wherein the determining comprises the Mobility Management node determining that the particular service requires a Quality of Service that the first type of RAT is at least momentary not able to support.

6. The method of claim 1 , wherein the network function is any of:

a Session Management Function+Packet gateway node;

a Policy Control Function node;

an Application Function node.

7. A method implemented by a network function in a core network of supporting the handing over a User Equipment (UE) from a first type of Radio Access Technology (RAT) to a second type of RAT, wherein the UE is attached to the core network via a Radio Access Network (RAN) utilizing the first type of RAT, the method comprising:

receiving, from a Mobility Management node in the core network, a subscription request for receiving notifications whenever a particular service is to be invoked for the UE;

determining that the particular service is to be invoked for the UE; and

transmitting, by the network function and to the Mobility Management node, an indication that the particular service is to be invoked for the UE, wherein the transmitting is performed before setup of a Quality of Service (QoS) flow for the particular service is completed;

suspending setup of the QoS flow for the particular service to wait for a handover from the first type of RAT to a second type of RAT for supporting the particular service;

resuming the setup of the QoS flow for the particular service when the handover from the first type of RAT to the second type of RAT is completed.

8. The method of claim 7 , further comprising:

receiving, by the network function and from the Mobility Management node, an information message that the UE is to be handed over from the first RAT to the second RAT for the particular service;

suspending, by the network function, establishment of the particular service to be invoked for the UE.

9. The method of claim 8 , further comprising:

receiving, by the network function, a confirmation that the UE is handed over from the first RAT to the second RAT, the confirmation being a confirmation of mobility for the UE;

unsuspending, by the network function, establishment of the particular service to be invoked for the UE.

10. A Mobility Management node configured to operate in a core network and configured to support handing over a User Equipment (UE) from a first type of Radio Access Technology (RAT) to a second type of RAT, wherein the UE is attached to a core network via a Radio Access Network (RAN) utilizing the first type of RAT, the Mobility Management node comprising:

receive circuitry configured to receive, from a network function in the core network, an indication that a particular service is to be invoked for the UE, wherein the indication is received prior to setup of a Quality of Service (QoS) flow for the particular service;

inform circuitry configured to send, responsive to determining that the UE is to be handed over to the second type of RAT, an indication to wait for confirmation that the handover is completed before continuing with the setup of the QoS flow;

processing circuitry configured to determine that the UE is to be handed over from the first type of RAT to the second type of RAT for supporting the particular service; and

transmit circuitry configured to request, before setup of the QoS flow for the particular service for the UE is completed, the RAN to hand over the UE from the first RAT to the second RAT.

11. The Mobility Management node of claim 10 , wherein the node further comprises subscribe circuitry configured to subscribe, to the network function, for receiving notifications whenever the particular service is to be invoked for the UE.

12. The Mobility Management node of claim 10 :

wherein the receive circuitry is further configured to receive, from the RAN, a confirmation that the UE is handed over from the first RAT to the second RAT; and

wherein the transmit circuitry is further configured to transmit the confirmation to the network function.

13. The Mobility Management node of claim 10 , wherein the processing circuitry is further configured to determine that the particular service requires a Quality of Service that the first type of RAT is at least momentary not able to support.

14. A network node in a core network and configured to support the handing over a User Equipment (UE) from a first type of Radio Access Technology (RAT) to a second type of RAT, wherein the UE is attached to a core network via a Radio Access Network (RAN) utilizing the first type of RAT, the network node comprising:

receive circuitry configured to receive, from a Mobility Management node in the core network, a subscription request for receiving notifications whenever a particular service is to be invoked for the UE;

processing circuitry configured to determine that the particular service is to be invoked for the UE; and

transmit circuitry configured to transmit, before setup of a Quality of Service (QoS) flow for the particular service for the UE is complete, an indication that the particular service is to be invoked for the UE;

suspend circuitry configured to:

suspend the setup of the QoS flow for the particular service to wait for a handover of the UE from the first type of RAT to the second type of RAT; and

resume the setup of the QoS flow for the particular service when the handover form the first type of RAT to the second type of RAT is completed.

15. The network node of claim 14 :

wherein the receive circuitry is further configured to receive, from the Mobility Management node, an information message that the UE is to be handed over from the first RAT to the second RAT for the particular service; and

wherein the suspend circuitry configured to suspend of the setup of the QoS flow for the particular service responsive to the information message.

16. The network node of claim 15 :

wherein the receive circuitry is further configured to receive a confirmation that the UE is handed over from the first RAT to the second RAT; and

wherein the suspend circuitry is further configured to unsuspend the establishment of the particular service to be invoked for the UE.

17. The network node of claim 14 , wherein the node is configured to perform any of:

a Session Management Function+Packet gateway;

a Policy Control Function;

an Application Function.

18. A non-transitory computer readable recording medium storing a computer program product for controlling handing over a User Equipment (UE) from a first type of Radio Access Technology (RAT) to a second type of RAT, wherein the UE is attached to a core network via a Radio Access Network (RAN) utilizing the first type of RAT, the computer program product comprising software instructions which, when run on processing circuitry of a Mobility Management node in the core network, causes the Mobility Management node to:

receive, from a network function in the core network, an indication that a particular service is to be invoked for the UE, wherein the indication is received prior to setup of a Quality of Service (QoS) flow for the particular service;

determine that the UE is to be handed over from the first type of RAT to the second type of RAT for supporting the particular service;

responsive to determining that the UE is to be handed over to the second type of RAT, send an indication to wait for confirmation that the handover is completed before continuing with the setup of the QoS flow; and

request, before the setup of the QoS flow for the particular service for the UE is completed, the RAN to hand over the UE from the first RAT to the second RAT.

19. A non-transitory computer readable recording medium storing a computer program product for controlling support of handing over a User Equipment (UE) from a first type of Radio Access Technology (RAT) to a second type of RAT, wherein the UE is attached to a core network via a Radio Access Network (RAN) utilizing the first type of RAT, the computer program product comprising software instructions which, when run on processing circuitry of a network function in the core network, causes the network function to:

receive, from a Mobility Management node in the core network, a subscription request for receiving notifications whenever a particular service is to be invoked for the UE;

determine that the particular service is to be invoked for the UE; and

transmit, to the Mobility Management node and before the setup of the QoS flow for the particular service for the UE is completed, an indication that the particular service is to be invoked for the UE;

suspend the setup of the QoS flow for the particular service to wait for a handover from the first type of RAT to a second type of RAT for supporting the particular service; and

resume the setup of the QoS flow for the particular service when the handover from the first type of RAT to the second type of RAT is completed.