Enhanced indication of network support of SRVCC and/or voice-over-IMS for an user equipment in an EPS network

1. A method for enhanced indication of network support of SRVCC and/or Voice-over-IMS for an User Equipment UE (UE) in an Evolved Packet System EPS network, said method comprising taking into account support of SRVCC and/or Voice-over-IMS by Radio Access Network RAN nodes, said method comprising:

an eNodeB serving said UE signalling to a Mobility Management Entity MME (MME) serving said UE, information as to said Voice-over-IMS and/or SRVCC support by RAN nodes, wherein the information as to said Voice-over-IMS and/or SRVCC support by RAN nodes comprises Radio Access Network RAN-level-support information, and

said MME sending to said UE a Voice-over-IMS support indication, indicating Voice-over-IMS supported or Voice-over-IMS not supported, taking into account said RAN-level support information received from said eNodeB.

2. A method according to claim 1 , comprising a step of:

said eNodeB signalling said RAN-level-support information to said MME during an Attach procedure or a mobility management procedure for said UE.

3. A method according to claim 1 , comprising a step of:

said eNodeB signalling said RAN-level support information to said MME in a dedicated message.

4. A method according to claim 1 , comprising a step of:

said eNodeB determining the information as to said Voice-over-IMS and/or SRVCC support by RAN nodes.

5. A method according to claim 4 , comprising a step of:

said eNodeB determining said RAN-level-support information using information as to radio capabilities of said UE, and/or RAN configuration information.

6. A method according to claim 5 , comprising a step of:

said MME signalling said information as to radio capabilities of said UE to said eNodeB.

7. A method according to claim 6 , comprising a step of:

said MME signalling said information as to radio capabilities of said UE to said eNodeB during an Attach procedure or a mobility management procedure for said UE.

8. A method according to claim 7 , comprising a step of:

said MME signalling said information as to radio capabilities of said UE to said eNodeB in a dedicated message.

9. A method according to claim 1 , comprising:

said MME triggering a procedure whereby the UE radio capabilities are first sent to the eNodeB in a downlink S1 message, and then the eNodeB responding with said RAN-level-support information sent to said MME.

10. An eNodeB comprising:

a processor; and

memory storing instructions that, when executed, cause the eNodeB to:

signal to a Mobility Management Entity MME (MME) serving an User Equipment UE (UE) served by said eNodeB in an Evolved Packet System EPS network, information as to Voice-over-IMS and/or SRVCC support by Radio Access Network RAN nodes, wherein the information as to Voice-over-IMS and/or SRVCC support by Radio Access Network RAN nodes comprises Radio Access Network RAN-level-support information, said signalling allowing a Voice-over-IMS indication indicating Voice-over-IMS supported or Voice-over-IMS not supported sent by said MME to said UE to take said RAN-level-support information into account.

11. An eNodeB according to claim 10 , wherein the instructions, when executed, further cause the eNodeB to:

signal said RAN-level-support information to said MME during an Attach procedure or a mobility management procedure for said UE.

12. An eNodeB according to claim 10 , wherein the instructions, when executed, further cause the eNodeB to:

signal said RAN-level support information to said MME in a dedicated message.

13. An eNodeB according to claim 10 , wherein the instructions, when executed, further cause the eNodeB to:

determine said RAN-level support information.

14. An eNodeB according to claim 13 , the instructions, when executed, further cause the eNodeB to:

determine said RAN-level-support information using information as to radio capabilities of said UE, and/or RAN configuration information.

15. An eNodeB according to claim 14 , wherein the instructions, when executed, further cause the eNodeB to:

receive information as to radio capabilities of said UE signalled to said eNodeB by said MME.

16. An eNodeB according to claim 14 , wherein the instructions, when executed, further cause the eNodeB to:

receive information as to radio capabilities of said UE signalled to said eNodeB by said MME during an Attach procedure or a mobility management procedure for said UE.

17. An eNodeB according to claim 14 , wherein the instructions, when executed, further cause the eNodeB to:

receive information as to radio capabilities of said UE signalled to said eNodeB by said MME in a dedicated message.

18. An eNodeB according to claim 10 , wherein the instructions, when executed, further cause the eNodeB to:

during a procedure triggered by said MME, first receive UE radio capabilities in a downlink S1 message, and then respond with said RAN-level-support information sent to said MME.

19. A Mobility Management Entity MME (MME), comprising:

a processor; and

memory storing instructions that, when executed, cause the MME to:

receive from an eNodeB serving a User Equipment UE (UE) served by said MME in an Evolved Packet System EPS network, information as to Voice-over-IMS and/or SRVCC support by Radio Access Network RAN nodes, wherein the information as to Voice-over-IMS and/or SRVCC support by Radio Access Network RAN nodes comprises Radio Access Network RAN-level-support information, and

send to said UE a Voice-over-IMS support indication, indicating Voice-over-IMS supported or Voice-over-IMS not supported, taking into account said RAN-level support information.

20. A Mobility Management Entity according to claim 19 , wherein the instructions, when executed, further cause the MME to:

receive said RAN-level-support information during an Attach procedure or a mobility management procedure for said UE.

21. A Mobility Management Entity according to claim 19 , wherein the instructions, when executed, further cause the MME to:

receive said RAN-level support information in a dedicated message.

22. A Mobility Management Entity according to claim 19 , wherein the instructions, when executed, further cause the MME to:

signal information as to radio capabilities of said UE to said eNodeB.

23. A Mobility Management Entity according to claim 22 , wherein the instructions, when executed, further cause the MME to:

signal said information as to radio capabilities of said UE to said eNodeB during an Attach procedure or a mobility management procedure for said UE.

24. A Mobility Management Entity according to claim 22 , wherein the instructions, when executed, further cause the MME to:

signal said information as to radio capabilities of said UE to said eNodeB in a dedicated message.

25. A Mobility Management Entity according to claim 19 , wherein the instructions, when executed, further cause the MME to:

trigger a procedure whereby UE radio capabilities are first sent to the eNodeB in a downlink S1 message, and then the MME receives said RAN-level-support information from said eNodeB.

26. A Mobility Management Entity according to claim 19 , wherein the RAN-level support information takes into account information as to radio capabilities of said UE and/or RAN configuration information.