Active Call Handover

Abstract

A method for an active call handover, including: receiving, at a mobile network operator (MNO), a handover request to transfer an active call, which is currently active between a first user equipment (UE) and a third-party device, from the first UE to a second UE; sending, by the MNO, a first invitation message to the second UE and a second invitation message to the third-party device; and transferring the active call from the first UE to the second UE.

Claims

1-15. (canceled)

16. A method for an active call handover, comprising: receiving, at a mobile network operator (MNO), a handover request to transfer an active call, which is currently active between a first user equipment (UE) and a third-party device, from the first UE to a second UE; sending, by the MNO, a first invitation message to the second UE and a second invitation message to the third-party device; and transferring the active call from the first UE to the second UE.

17. The method of claim 16, wherein the first UE uses a first communication profile of the user for communication over a mobile network, and wherein the second UE uses a second communication profile of the user for communication over the mobile network.

18. The method of claim 17, wherein the first communication profile and the second communication profile have a same telephone number.

19. The method of claim 17, wherein the first communication profile is an eSIM profile of the user, and wherein the second communication profile is an eSIM profile of the user

20. The method of claim 16, wherein the handover request to transfer the active call is sent by either the first UE or the second UE to the MNO.

21. The method of claim 16, further including: sending, by the MNO, a termination message to the first UE.

22. The method of claim 16, wherein the first UE and the second UE are selected from the group consisting of a mobile terminal, a communication module, a communication module of a vehicle, and a vehicle.

23. The method of claim 16, wherein the first UE is a vehicle and the second UE is a mobile terminal, or wherein the first UE is a mobile terminal and the second UE is a vehicle.

24. The method of claim 16, wherein, if a timeout period of at least one of: the handover request, the first invitation message, and the second invitation message expires, the active call handover is aborted and the active call is restored between the first UE and the second UE.

25. The method of claim 16, wherein, if an error in at least one of: the handover request, the first invitation message, and the second invitation message occurs, the active call handover is aborted and the active call is restored between the first UE and the second UE.

26. A non-transitory computer-readable storage medium comprising instructions which, when executed on one or more processors, cause the one or more processors to perform the method of claim 16.

27. A server of a mobile network operator (MNO), comprising one or more processors configured to: receive a handover request to transfer an active call, which is currently active between a first user equipment (UE) and a third-party device, from the first UE to a second UE; send a first invitation message to the second UE and a second invitation message to the third-party device; and transfer the active call from the first UE to the second UE.

28. A user equipment (UE), comprising one or more processors configured to: send, to a mobile network operator (MNO), a handover request to transfer an active call, which is currently active between the UE and a third-party device, from the UE to another UE; and terminate the active call.

29. A user equipment (UE), comprising one or more processors configured to: receive, from a mobile network operator (MNO), a first invitation message to transfer an active call, which is currently active between another UE and a third-party device, from the other UE to the UE; and enable the active call from the other UE.

30. A system, comprising: the server of the mobile network operator (MNO) of claim 27; and the user equipment (UE) of claim 28.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0029] So that the manner in which the above recited features of the present disclosure can be understood in detail, a more particular description of the disclosure, briefly summarized above, may be had by reference to embodiments. The accompanying drawings relate to embodiments of the disclosure and are described in the following:

[0030] FIG. 1 shows a flow chart of method for an active call handover according to embodiments described herein;

[0031] FIG. 2 shows a schematic view of a vehicle and a mobile terminal according to embodiments described herein;

[0032] FIG. 3 shows an active call handover according to embodiments described herein;

[0033] FIG. 4 shows a timeout according to embodiments described herein;

[0034] FIG. 5 shows an error according to embodiments described herein;

[0035] FIG. 6 shows a timeout according to further embodiments described herein;

[0036] FIG. 7 shows an error according to further embodiments described herein;

[0037] FIG. 8 shows a timeout according to further embodiments described herein;

[0038] FIG. 9 shows an error according to further embodiments described herein;

[0039] FIG. 10 shows an active call handover according to further embodiments described herein;

[0040] FIG. 11 shows an error according to further embodiments described herein;

[0041] FIG. 12 shows a timeout according to further embodiments described herein; and

[0042] FIG. 13 shows an error according to further embodiments described herein.

DETAILED DESCRIPTION OF THE DRAWINGS

[0043] Reference will now be made in detail to the various embodiments of the disclosure, one or more examples of which are illustrated in the figures. Within the following description of the drawings, the same reference numbers refer to same components. Generally, only the differences with respect to individual embodiments are described. Each example is provided by way of explanation of the disclosure and is not meant as a limitation of the disclosure. Further, features illustrated or described as part of one embodiment can be used on or in conjunction with other embodiments to yield yet a further embodiment. It is intended that the description includes such modifications and variations.

[0044] Although the embodiments of the present disclosure are described with reference to a vehicle, it is to be understood that the present disclosure is not limited thereto and that the embodiments described herein may be implemented in and/or used with a number of different types of UE devices, including but not limited to cellular phones, tablet computers, wearable computing devices, portable media players, vehicles, and any of various other computing devices.

[0045] FIG. 1 shows a flow chart of method 100 for an active call handover according to embodiments described herein.

[0046] The method 100 includes in block 110 receiving, at a mobile network operator, MNO, a handover request to transfer an active call, which is currently active between a first user equipment, UE, and a third-party device, from the first UE to a second UE; in block 120 sending, by the MNO, a first invitation message to the second UE and a second invitation message to the third-party device; and in block 130 transferring the active call from the first UE to the second UE.

[0047] The MNO may also be referred to as a wireless service provider, wireless carrier, cellular company, or mobile network carrier, and is a provider of wireless communications services that owns or controls all the elements necessary to sell and deliver services to a user. In particular, the MNO owns or controls the elements of the network infrastructure necessary to provide services to subscribers (users) over a licensed spectrum.

[0048] The UEs and the MNO communicate via a transmission medium, such as a network. In a preferred embodiment, the network is a mobile network managed by the MNO. The transmission medium may use any of various wireless communication technologies, or telecommunication standards, such as GSM, UMTS, LTE, LTE-Advanced (LTE-A), 5G, HSPA, and the like. A communication via future telecommunication standards is possible.

[0049] FIG. 2 shows a schematic view of a vehicle 20 and a mobile terminal 30 according to embodiments described herein.

[0050] In the example shown in FIG. 2, the first UE is a vehicle 20 or a communication module 200 of the vehicle 10. The second UE is a mobile terminal 30 which includes the second communication module 300.

[0051] However, the present disclosure is not limited thereto and the embodiments may be implemented in and/or used with a number of different types of UE devices, including, but not limited to, cellular phones, tablet computers, wearable computing devices, portable media players, and any of various other computing devices.

[0052] FIG. 3 shows an active call handover according to embodiments described herein. In the example of FIG. 3, the active call is transferred from a vehicle to a mobile terminal of a user when the user leaves the vehicle.

[0053] Generally, a purpose of the Active Call Handover (ACH) is to have a stable ongoing voice call while the user is entering or leaving a vehicle. When exiting the vehicle, the call shall be handed over from the vehicle phone to the consumer's personal phone. In some embodiments, the vehicle detects whether the user is entering or leaving the vehicle, and the vehicle provides a trigger message (i.e., the handover request) for the Active Call Handover.

[0054] In some implementations, the embodiments of the preset disclosure are based on the standard 3GPP TS 24.337 Version 15, as will be explained in the following.

[0055] The network design may require coping with any kind of SIP clients with their capabilities and limitations. For the current use case, there are three devices implicated with the following requirements:

[0056] Vehicle (transferor): Requires a VoLTE device as defined in GSMA IR.92 enhanced with REFER procedure.

[0057] User's mobile phone (transfer target): VoLTE device as specified in GSMA IR.92.

[0058] Communication partner (transferee): any kind of SIP client.

[0059] In case the vehicle is involved in the original call and the user is leaving the vehicle, the message flow starts with a handover request in step 001 (e.g. SIP REFER based on the standard 3GPP TS 24.337 Version 15).

[0060] The SIP REFER header may include a REFER TO parameter set to the Public Primary MSISDN of the user's account. In more detail, the header of the handover request may include at least some of the following values:

TABLE-US-00001 SIP Header Value Request-URI Targeted at the same UE instance that is involved in the initial dialog as specified in RFC 3261, section 12.2.1.1 (i.e. communication partner (transferee)) Contact Registered contact id of the transferor sending the REFER (i.e. vehicle phone) Refer-To The public user identity of the user for the call being transferred, (i.e. IMPU of served vehicle user). (vehicle phone can't address to a specific UA instance which is registered to the given MSIM IMPU) Accept- — Contact Expires Time value after which Call Transfer attempt is terminated. Referred-By The public user identity of the user for the call being transferred (i.e. IMPU of served vehicle user). Require no-sub Accept- (MMTEL ICSI) Contact P-Preferred- (MMTEL ICSI) Service User-Agent User-Agent id of the transferor's client sending the REFER (user's vehicle phone client) All other fields may be as defined in RFC 3261 and 24.229.

[0061] The handover request in step 001 is sent by the first UE to the MNO.

[0062] In step 002, the MNO sends an OK message (REFER OK) to the first UE.

[0063] In step 003, the MNO sends the first invitation message (SIP INVITE) to the second UE.

[0064] In step 004, the second UE sends an OK message (INVITE OK) to the MNO.

[0065] In step 005, the MNO sends the second invitation message (SIP re-INVITE) to the third-party device.

[0066] In step 006, the third-party device sends an OK message (re-INVITE OK) to the MNO.

[0067] In step 007, the MNO sends an acknowledgement (INVITE ACK) to the second

[0068] UE.

[0069] In step 008, the MNO sends another acknowledgement (re-INVITE ACK) to the third-party device.

[0070] According to some embodiments, the method further includes, in step 009, sending, by the MNO, a termination message (SIP BYE) to the first UE.

[0071] In step 010, the first UE sends an OK message (BYE OK) to the MNO.

[0072] By completing the above process, the media path between the second UE (e.g. the user's smartphone) and the third-party device can be established.

[0073] FIG. 4 shows a timeout of the handover request according to embodiments described herein.

[0074] During the transfer of the call, the third party is not on hold, that is, if the transfer execution time is too long, the third party may hang up due to interruption of the voice communication during the change of device.

[0075] Thus, according to some embodiments, if a timeout period of at least one of the handover request, the first invitation message and the second invitation message expires, the active call handover is aborted and the active call is restored between the first UE and the second UE.

[0076] In the example of FIG. 4, a timeout period of the handover request expires. If the timeout period of the handover request expires, the active call handover is aborted, and the active call is restored.

[0077] FIG. 5 shows an error of the handover request according to embodiments described herein.

[0078] During the transfer of the call, the third party is not on hold, that is, if the transfer execution time is too long, the third party may hang up due to interruption of the voice communication during the change of device.

[0079] Thus, according to some embodiments, if an error of at least one of the handover request, the first invitation message and the second invitation message expires, the active call handover is aborted and the active call is restored between the first UE and the second UE.

[0080] In the example of FIG. 5, an error of the handover request occurs, and the active call handover is aborted, and the active call is restored.

[0081] FIG. 6 shows a timeout of the first invitation message (SIP INVITE) according to embodiments described herein.

[0082] During the transfer of the call, the third party is not on hold, that is, if the transfer execution time is too long, the third party may hang up due to interruption of the voice communication during the change of device.

[0083] Thus, according to some embodiments, if a timeout period of at least one of the handover request, the first invitation message and the second invitation message expires, the active call handover is aborted and the active call is restored between the first UE and the second UE.

[0084] In the example of FIG. 6, a timeout period of the first invitation message expires. If the timeout period of the first invitation message expires, the active call handover is aborted, and the active call is restored.

[0085] FIG. 7 shows an error of the first invitation message according to embodiments described herein.

[0086] During the transfer of the call, the third party is not on hold, that is, if the transfer execution time is too long, the third party may hang up due to interruption of the voice communication during the change of device.

[0087] Thus, according to some embodiments, if an error of at least one of the handover request, the first invitation message and the second invitation message expires, the active call handover is aborted and the active call is restored between the first UE and the second UE.

[0088] In the example of FIG. 7, an error of the first invitation message occurs, and the active call handover is aborted, and the active call is restored.

[0089] FIG. 8 shows a timeout of the second invitation message (SIP re-INVITE) according to embodiments described herein.

[0090] During the transfer of the call, the third party is not on hold, that is, if the transfer execution time is too long, the third party may hang up due to interruption of the voice communication during the change of device.

[0091] Thus, according to some embodiments, if a timeout period of at least one of the handover request, the first invitation message and the second invitation message expires, the active call handover is aborted and the active call is restored between the first UE and the second UE.

[0092] In the example of FIG. 8, a timeout period of the second invitation message expires. If the timeout period of the second invitation message expires, the active call handover is aborted, and the active call is restored.

[0093] FIG. 9 shows an error of the second invitation message according to embodiments described herein.

[0094] During the transfer of the call, the third party is not on hold, that is, if the transfer execution time is too long, the third party may hang up due to interruption of the voice communication during the change of device.

[0095] Thus, according to some embodiments, if an error of at least one of the handover request, the first invitation message and the second invitation message expires, the active call handover is aborted and the active call is restored between the first UE and the second UE.

[0096] In the example of FIG. 9, an error of the second invitation message occurs, and the active call handover is aborted, and the active call is restored.

[0097] FIG. 10 shows an active call handover according to embodiments described herein. In the example of FIG. 10, the active call is transferred from a mobile terminal of a user to a vehicle when the user enters the vehicle.

[0098] Generally, a purpose of the Active Call Handover (ACH) is to have a stable ongoing voice call while the user is entering or leaving a vehicle. When entering the vehicle, the call shall be handed over from the user's phone to the vehicle phone with the active and enabled consumer eSIM. In some embodiments, the vehicle detects whether the user is entering or leaving the vehicle, and the vehicle provides a trigger message (i.e., the handover request) for the Active Call Handover.

[0099] In some implementations, the embodiments of the preset disclosure are based on the standard 3GPP TS 24.337 Version 15, as will be explained in the following.

[0100] The network design may require coping with any kind of SIP clients with their capabilities and limitations. For the current use case, there are three devices implicated with the following requirements:

[0101] Vehicle: transfer target

[0102] User's mobile phone: transferor

[0103] Communication partner: transferee

[0104] The handover request in step 001 is sent by the second UE to the MNO.

[0105] In step 002, the MNO sends the second invitation message (SIP re-INVITE) to the third-party device.

[0106] In step 003, the third-party device sends an OK message (re-INVITE OK) to the MNO.

[0107] In step 004, the MNO sends the first invitation message (SIP INVITE) to the second UE.

[0108] In step 005, the second UE sends an acknowledgement (INVITE ACK) to the MNO.

[0109] In step 006, the MNO sends another acknowledgement (re-INVITE ACK) to the third-party device.

[0110] According to some embodiments, the method further includes, in step 007, sending, by the MNO, a termination message (SIP BYE) to the first UE.

[0111] In step 008, the first UE sends an OK message (BYE OK) to the MNO.

[0112] By completing the above process, the media path between the first UE (e.g. the vehicle) and the third-party device can be established.

[0113] FIG. 11 shows an error of the first invitation message according to embodiments described herein.

[0114] During the transfer of the call, the third party is not on hold, that is, if the transfer execution time is too long, the third party may hang up due to interruption of the voice communication during the change of device.

[0115] Thus, according to some embodiments, if an error of at least one of the handover request, the first invitation message and the second invitation message expires, the active call handover is aborted and the active call is restored between the first UE and the second UE.

[0116] In the example of FIG. 11, an error of the first invitation message occurs, and the active call handover is aborted, and the active call is restored.

[0117] FIG. 12 shows a timeout of the second invitation message (SIP re-INVITE) according to embodiments described herein.

[0118] During the transfer of the call, the third party is not on hold, that is, if the transfer execution time is too long, the third party may hang up due to interruption of the voice communication during the change of device.

[0119] Thus, according to some embodiments, if a timeout period of at least one of the handover request, the first invitation message and the second invitation message expires, the active call handover is aborted and the active call is restored between the first UE and the second UE.

[0120] In the example of FIG. 12, a timeout period of the second invitation message expires. If the timeout period of the second invitation message expires, the active call handover is aborted, and the active call is restored.

[0121] FIG. 13 shows an error of the second invitation message according to embodiments described herein.

[0122] During the transfer of the call, the third party is not on hold, that is, if the transfer execution time is too long, the third party may hang up due to interruption of the voice communication during the change of device.

[0123] Thus, according to some embodiments, if an error of at least one of the handover request, the first invitation message and the second invitation message expires, the active call handover is aborted and the active call is restored between the first UE and the second UE.

[0124] In the example of FIG. 13, an error of the second invitation message occurs, and the active call handover is aborted, and the active call is restored.

[0125] While the foregoing is directed to embodiments of the disclosure, other and further embodiments of the disclosure may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.