Abstract: Embodiments of the present invention include a method for enhanced indication of network support of SRVCC and/or Voice over IMS for an User Equipment UE in an Evolved Packet System EPS network said method comprising at least one step based on taking into account support of SRVCC and/or Voice over IMS by Radio Access Network RAN nodes and/or by Radio Access Technologies RATs available for SRVCC for said UE in said EPS network.
1. A method for enhanced indication of network support of Voice -over-IMS for an User
Equipment (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 (eNB) serving said UE signalling to a Mobility Management Entity (MME) serving said UE, information as to said Voice-over-IMS and/or SRVCC support by RAN nodes, referred to as Radio Access Network RAN-level-support information,
- said MME sending to said UE, in an Attach, or Tracking Area Update TAU, Accept message, 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. The method as claimed in 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. The method as claimed in claim 1 or 2, comprising a step of:
- said eNodeB signalling said RAN-level support information to said MME, in a
dedicated message.
4. The method as claimed in any of claims 1 to 3, comprising a step of:
- said eNodeB determining information as to said Voice-over-IMS and/or SRVCC
support by RAN nodes, referred to as Radio Access Network RAN-level-support
information, using information as to radio capabilities of said UE, and/or RAN
configuration information.
5. The method as claimed in claim 4, 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.
6. The method as claimed in claim 5, comprising a step of:
- said MME signalling said information as to radio capabilities of said UE to said
eNodeB in a dedicated message.
7. The method as claimed in any of claims 1 to 6, comprising a step of:
- said MME triggering a procedure whereby the UE radio capabilities are first
sent to the eNodeB in a downlink SI message, and then the eNodeB responds with said
RAN-level-support information sent to said MME.
8. An eNodeB (eNB), comprising
- means for signalling to a Mobility Management Entity (MME) serving a User
Equipment (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, referred to as Radio Access Network RAN-level-support information, said
signaling allowing a Voice-over-IMS indication indicating Voice-over-IMS supported or
Voice-over-IMS not supported sent by said MME to said UE in an Attach, or Tracking
Area Update (TAU), Accept message, to take said RAN-level-support information into
account.
9. The eNodeB as claimed in claim 8, comprising:
- means for signaling said RAN-level-support information to said MME during an
Attach procedure or a mobility management procedure for said UE.
10. The eNodeB as claimed in claim 8 or 9, comprising:
- means for signaling said RAN-level support information to said MME, in a
dedicated message.
11. The eNodeB as claimed in any of claims 8 to 10, comprising:
- means for determining said RAN-level-support information, using information
as to radio capabilities of said UE, and/or RAN configuration information.
12. The eNodeB as claimed in claim 11, comprising:
-means ror receiving information as to radio capabilities or said Uh, signaled to said eNodeB by said MME.
13. The eNodeB as claimed in claim 11 or 12, comprising:
- means for receiving information as to radio capabilities of said UE signaled to
said eNodeB by said MME during an Attach procedure or a mobility management
procedure for said UE.
14. The eNodeB as claimed in any of claims 11 to 13, comprising:
- means for receiving information as to radio capabilities of said UE signaled to
said eNodeB by said MME in a dedicated message.
15. The eNodeB as claimed in any of claims 8 to 14, comprising:
- means for, during a procedure triggered by said MME, first receiving UE radio
capabilities in a downlink SI message, and then responding with said RAN-level-
support information sent to said MME.
16. A Mobility Management Entity (MME), comprising:
- means for receiving from an eNodeB (eNB) serving a User Equipment (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, referred to as Radio Access Network RAN-level-support information,
- means for sending to said UE, in an Attach, or Tracking Area Update (TAU), Accept message, 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.
17. The Mobility Management Entity (MME) as claimed in claim 16, comprising:
- means for receiving said RAN-level-support information during an Attach
procedure or a mobility management procedure for said UE.
18. The Mobility Management Entity (MME) as claimed in claim 16 or 17,
comprising:
- means for receiving said RAN-level support information, in a dedicated
message.
19. The Mobility Management Entity (MME) as claimed in any of claims 16 to 18,
comprising:
- means for signalling information as to radio capabilities of said UE to said
eNodeB, during an Attach procedure or a mobility management procedure for said UE.
20. The Mobility Management Entity (MME) as claimed in claim 19, comprising:
-means for signalling said information as to radio capabilities of said UE to said
eNodeB in a dedicated message.
21. The Mobility Management Entity (MME) as claimed in any of claims 16 to 20,
comprising:
- means for triggering a procedure whereby UE radio capabilities are first sent to
the eNodeB in a downlink SI message, and then the MME receives said RAN-level-
support information from said eNodeB.
| # | Name | Date |
|---|---|---|
| 1 | OTHERS.pdf | 2014-06-02 |
| 2 | Form 5.pdf | 2014-06-02 |
| 3 | form 3.pdf | 2014-06-02 |
| 4 | CLAIMS.pdf | 2014-06-02 |
| 5 | ALCATEL LUCENT.pdf | 2014-06-02 |
| 6 | 4082-CHENP-2014 FORM-13 16-06-2014.pdf | 2014-06-16 |
| 7 | 4082-CHENP-2014 CORRESPONDENCE OTHERS 16-06-2014.pdf | 2014-06-16 |
| 8 | 4082-CHENP-2014 AMENDED PAGES OF SPACIFICATION 16-06-2014.pdf | 2014-06-16 |
| 9 | 4082-CHENP-2014 AMENDED CLAIMS 16-06-2014.pdf | 2014-06-16 |
| 10 | 4082-CHENP-2014.pdf | 2014-07-10 |
| 11 | 4082-CHENP-2014 FORM-3 28-11-2014.pdf | 2014-11-28 |
| 12 | 4082-CHENP-2014 FORM-1 28-11-2014.pdf | 2014-11-28 |
| 13 | 4082-CHENP-2014 CORRESPONDENCE OTHERS 28-11-2014.pdf | 2014-11-28 |
| 14 | abstract 4082-CHENP-2014.jpg | 2015-01-29 |
| 15 | 4082-CHENP-2014 FORM-3 04-03-2015.pdf | 2015-03-04 |
| 16 | 4082-CHENP-2014 CORRESPONDENCE OTHERS 04-03-2015.pdf | 2015-03-04 |
| 17 | 4082-CHENP-2014 FORM-3 10-06-2015.pdf | 2015-06-10 |
| 18 | 4082-CHENP-2014 CORRESPONDENCE OTHERS 10-06-2015.pdf | 2015-06-10 |
| 19 | Form 3 [02-06-2016(online)].pdf | 2016-06-02 |
| 20 | Form 3 [25-11-2016(online)].pdf | 2016-11-25 |
| 21 | Form 3 [04-05-2017(online)].pdf | 2017-05-04 |
| 22 | 4082-CHENP-2014-FORM 3 [11-08-2017(online)].pdf | 2017-08-11 |
| 23 | 4082-CHENP-2014-FORM 3 [08-01-2018(online)].pdf | 2018-01-08 |
| 24 | 4082-CHENP-2014-FORM 3 [24-03-2018(online)].pdf | 2018-03-24 |
| 25 | 4082-CHENP-2014-FORM 3 [13-06-2018(online)].pdf | 2018-06-13 |
| 26 | 4082-CHENP-2014-FER.pdf | 2019-03-26 |
| 27 | 4082-CHENP-2014-Information under section 8(2) (MANDATORY) [25-09-2019(online)].pdf | 2019-09-25 |
| 28 | 4082-CHENP-2014-FORM 4(ii) [25-09-2019(online)].pdf | 2019-09-25 |
| 29 | 4082-CHENP-2014-FORM 3 [25-09-2019(online)].pdf | 2019-09-25 |
| 30 | 4082-CHENP-2014-OTHERS [24-12-2019(online)].pdf | 2019-12-24 |
| 31 | 4082-CHENP-2014-Information under section 8(2) (MANDATORY) [24-12-2019(online)].pdf | 2019-12-24 |
| 32 | 4082-CHENP-2014-FORM-26 [24-12-2019(online)].pdf | 2019-12-24 |
| 33 | 4082-CHENP-2014-FORM 3 [24-12-2019(online)].pdf | 2019-12-24 |
| 34 | 4082-CHENP-2014-FER_SER_REPLY [24-12-2019(online)].pdf | 2019-12-24 |
| 35 | 4082-CHENP-2014-DRAWING [24-12-2019(online)].pdf | 2019-12-24 |
| 36 | 4082-CHENP-2014-COMPLETE SPECIFICATION [24-12-2019(online)].pdf | 2019-12-24 |
| 37 | 4082-CHENP-2014-CLAIMS [24-12-2019(online)].pdf | 2019-12-24 |
| 38 | 4082-CHENP-2014-ABSTRACT [24-12-2019(online)].pdf | 2019-12-24 |
| 39 | 4082-CHENP-2014-FORM-26 [03-01-2020(online)].pdf | 2020-01-03 |
| 40 | 4082-CHENP-2014_Form26_General Power of Attorney_06-01-2020.pdf | 2020-01-06 |
| 41 | 4082-CHENP-2014_Correspondence_06-01-2020.pdf | 2020-01-06 |
| 42 | 4082-CHENP-2014-US(14)-HearingNotice-(HearingDate-06-12-2021).pdf | 2021-10-28 |
| 43 | 4082-CHENP-2014-FORM-26 [01-12-2021(online)].pdf | 2021-12-01 |
| 44 | 4082-CHENP-2014-Correspondence to notify the Controller [01-12-2021(online)].pdf | 2021-12-01 |
| 45 | 4082-CHENP-2014-PETITION UNDER RULE 138 [21-12-2021(online)].pdf | 2021-12-21 |
| 46 | 4082-CHENP-2014-Written submissions and relevant documents [20-01-2022(online)].pdf | 2022-01-20 |
| 47 | 4082-CHENP-2014-Retyped Pages under Rule 14(1) [20-01-2022(online)].pdf | 2022-01-20 |
| 48 | 4082-CHENP-2014-PETITION UNDER RULE 137 [20-01-2022(online)].pdf | 2022-01-20 |
| 49 | 4082-CHENP-2014-FORM 3 [20-01-2022(online)].pdf | 2022-01-20 |
| 50 | 4082-CHENP-2014-2. Marked Copy under Rule 14(2) [20-01-2022(online)].pdf | 2022-01-20 |
| 51 | 4082-CHENP-2014-RELEVANT DOCUMENTS [03-08-2023(online)].pdf | 2023-08-03 |
| 1 | 4082-chenp-2014_14-03-2019.pdf |