Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TR 22.844  Word version:  18.2.0

Top   Top   Up   Prev   None
1…   5…   5.5…   5.8…   5.13…   6…   7…

 

7  Conclusions and RecommendationsWord‑p. 43

This technical report provides use cases and potential new requirements. The resulting service requirements have been consolidated in clause 6.
It is recommended to consider the consolidated requirements identified in this TR as the baseline for subsequent normative work.

A  Interworking between Networks Operators and Application Providers for localized servicesWord‑p. 43

In TS 22.278, Annex B1 provides various scenarios applicable for interworking between mobile operators and data applications for EPS and 5GS including:
  • Operator owned non-roaming scenario
  • Collaborative non-roaming scenario
  • Operator owned/collaborative roaming scenario - Home Routed
  • Collaborative roaming scenario - Local Breakout
This clause extends the roaming scenarios applicable for interworking between hosting network operator (PLMN or NPN) and data applications based on service agreements for localized services among network operators and application/service providers:
  • Hosting network operator owns the 5G network which provides access and IP connectivity to roaming UEs.
  • Network operator owned application layer entities include Service Hosting Environment, and IMS network.
  • Application platforms in third party domain can be owned by third party application/service providers, or home/other network operators.
  • The Application platforms could be application servers (e.g. Video on Demand Server, Cloud gaming server, etc.), 3rd party software development platforms, and third party/operator Service Hosting Environments.
The following Figures show the collaborative relationship in three domains including network operator providing access and IP connectivity, network operators providing services via IMS/application platforms, and application/service providers providing services via application platforms or applications. The dashed lines between visited hosting network operator and Home network operators are based on service level e-agreement and the horizontal line represents the demarcation between the network operator domains and the 3rd party domain. In an operator network, the application layer entities include IMS network, Application platforms, and API Gateway for third party applications developed using APIs (e.g. REST, GSMA OneAPI).
Figure A-1 provides the home-routed roaming scenario for collaborative scenarios where traffic is routed to home network operator and applications are delivered by the home operator owned IMS or Application platform via roaming agreements between network operators.
Copy of original 3GPP image for 3GPP TS 22.844, Fig. A-1: Home Operator owned/collaborative roaming scenario - Home Routed
Up
Figure A-2 provides the local breakout scenario for both owned and collaborative scenarios between visited hosting network operator and operators in 3rd party domains where traffic is routed to application from the hosting network to 1) hosting network owned application platforms, 2) collaborative home network owned application platforms, and 3) third parties via roaming agreements between visited hosting network operator and home/other network operators, and between hosting network operators and other application/service providers.
Copy of original 3GPP image for 3GPP TS 22.844, Fig. A-2: Hosting Network Operator owned/collaborative roaming scenario - Local Breakout
Up
Other interworking scenarios are not excluded.

$  Change historyWord‑p. 45


Up   Top