9 Scenarios relating to roaming
24.5233GPPArchitecture and functional descriptionCore and enterprise Next Generation Network (NGN) interaction scenariosRelease 17TS
9.1 Scenario 7: NGCN user roaming into NGN public network
9.1.1 Introduction
This scenario describes the provision of capabilities of the NGN to support end users whose home location is an NGCN roaming into an NGN.
9.1.2 Involved functional entities
Figure 9.1.1: NGCN user registering from visited NGN with which NGCN has a roaming agreement
Figure 9.1.2: NGCN user registering from visited NGN via NGN with which both visited NGN and NGCN have a roaming agreement
NOTE: Functional entities in NGN with which the NGCN has a roaming agreement support either
peering-based or subscription-based approach for business trunking.
A registration request submitted by an NGCN UE attached to a NGN is routed into the NGCN, either to the NGCN site directly when there exists a roaming agreement between the NGN and the NGCN; or indirectly via an NGN that has a roaming agreement with the NGCN which then transits the traffic to the home NGCN where the registrar is located. IBCF or equivalent functionality may exist at the network borders.
Other requests (e.g. for call establishment) are routed similarly to the proxy in the NGCN home site. Requests to the NGCN UE are sent in the opposite direction.
See 3GPP TS 24.525 [5] for further information.
9.1.3 Void
9.1.4 Interoperability with other scenarios
The Roaming NGCN User scenario can interoperate with any originating scenario and any terminating scenario. Specifically, a roaming NGCN user can:
– originate a call in which the user’s home NGCN is the originating side of the NGCN transit scenario;
– originate a call in which the user’s home NGCN is the originating side of a business trunking scenario (subscription-based or peering-based);
– terminate a call in which the user’s home NGCN is the terminating side of the NGCN transit scenario;
– terminate a call in which the user’s home NGCN is the terminating side of a business trunking scenario (subscription-based or peering-based).
9.1.5 Emergency calls
NOTE: Not addressed in this release of the document.
9.1.6 Configuration / provisioning issues
NOTE: Not addressed in this release of the document.
9.1.7 Security issues
NOTE: Not addressed in this release of the document.
9.1.8 Charging issues
NOTE: Not addressed in this release of the document.
9.1.9 Transport control issues
NOTE: Definition of the transport control issues in this scenario is outside the scope of this release of the present document.
9.2 Scenario 8: NGCN user roaming into another NGCN site of the same enterprise
9.2.1 Introduction
This scenario describes the provision of capabilities of the NGN to support end users whose home location is an NGCN site roaming into another NGCN site of the same enterprise. This scenario is not supported in the current release.
9.3 Scenario 9: HES user roams into NGCN site of the same enterprise
9.3.1 Introduction
This scenario describes the provision of capabilities of the NGN to support HES users whose home location is an NGN roaming into an NGCN site of the same enterprise. This scenario is not supported in the current release.
9.4 Scenario 10: HES user roams into another NGN
9.4.1 Introduction
This scenario utilizes existing NGN roaming capabilities.
9.5 Scenario 11: NGN public network user roaming into NGCN
9.5.1 Introduction
This scenario describes the provision of capabilities of the NGN to support end users whose home location is an NGN roaming into an NGCN. This scenario is not supported in the current release.
9.6 Scenario 12: NGCN user roaming into an NGCN of a different enterprise
9.6.1 Introduction
This scenario describes the provision of capabilities of the NGN to support end users whose home location is an NGCN roaming into another NGCN belonging to a different enterprise. This scenario is not supported in the current release.
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
March 2014 |
Version for input to 3GPP CT1#86bis |
0.0.0 |
|||||
|
April 2014 |
Version collecting comments from 3GPP CT1#86bis |
0.0.0 |
0.0.1 |
||||
|
May 2014 |
Version including revisions from CT1#87 from the following documents: C1-142086, C1-142087 |
0.0.1 |
0.1.0 |
||||
|
June 2014 |
CT-64 |
CP-140282 |
Version 1.0.0 created for presentation for information and approval at CT-64 |
0.1.0 |
1.0.0 |
||
|
June 2014 |
Post CT-64 |
Version 12.0.0 created after approval at CT-64 |
1.0.0 |
12.0.0 |
|||
|
September 2014 |
CT-65 |
CP-140653 |
0001 |
Recognition of VINE functional in business trunking scenarios |
12.0.0 |
12.1.0 |
|
|
September 2014 |
CT-65 |
CP-140653 |
0002 |
Fixing non-specific versions of references |
12.0.0 |
12.1.0 |
|
|
December 2014 |
CT-66 |
24.523 |
0004 |
Removal of further study items |
12.1.0 |
12.2.0 |
|
|
December 2014 |
CT-66 |
24.523 |
0005 |
1 |
Intelligent routeing tables in peering-based business trunking |
12.1.0 |
12.2.0 |
|
December 2015 |
CT-67 |
24.523 |
Upgrade to Rel-13 |
12.2.0 |
13.0.0 |
||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
CT-75 |
Upgrade to Rel-14 |
14.0.0 |
||||
|
2018-06 |
SA-80 |
– |
– |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
|
|
2020-07 |
SA-88e |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
|
2022-04 |
CT-95e |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |