3GPP LS Response on External Data Channel Content Access Requirements

Document Overview

This is a Liaison Statement (LS) response from 3GPP TSG SA to GSMA NG UPG addressing concerns about external data channel content access requirements. The document consolidates feedback from multiple SA Working Groups (SA1, SA3, SA4, and SA6) regarding the handling of external resources in IMS Data Channel applications.

Main Technical Contributions

SA1 Feedback: Regulatory Scope

SA1 clarifies the regulatory framework for IMS Data Channel applications:

• IMS Telephony Context: When IMS Data Channel is used as part of IMS telephony services, the applications (including HTML and JavaScript content) are expected to be subject to local telecom regulation
• Standalone Data Channel: When used for other services, they are subject to applicable regulations which could also include local telecom regulations
• Regulatory Determination: SA1 explicitly states it is not within their scope to decide which specific regulation(s) HTML and JavaScript content would be subject to

SA2 Feedback

SA2 has provided a separate, direct reply to GSMA NG UPG (not included in this consolidated response).

SA3 Feedback: Security Architecture

SA3 addresses security concerns for external content:

• Current Status: SA3 does not currently have plans to standardize security architecture and measures for:
• Content and source validation
• Methods to compute trust towards external hosts and content
• Future Updates: SA3 commits to keeping GSMA NG UPG informed of any future developments in this area

SA4 Feedback: Specification Gaps and Study Plans

SA4 provides the most detailed technical response:

• Acknowledgment of Issue: SA4 acknowledges the gaps identified by GSMA NG UPG regarding ambiguity in handling external resource access in IMS Data Channel applications
• Current Specification Limitations: TS 26.114 does not explicitly address scenarios involving external resource mashups clearly enough
• Original Design Assumption: SA4 originally assumed that the Data Channel Signalling Function (DCSF) and Data Channel Application Server (DC AS) would be the exclusive hosts for all content, and did not anticipate scenarios involving external resources
• Planned Action: SA4 commits to studying this issue and providing necessary clarifications as part of the DC Enhancements (FS_DCE_MED) study in Release 20

SA6 Feedback: Interworking Architecture and CAPIF Reference

SA6 provides architectural context and potential solutions:

• Current Status: SA6 has not yet studied procedures and architecture for interworking between the IMS domain and external (non-IMS) content sources
• CAPIF Framework Reference: SA6 highlights the CAPIF framework (3GPP TS 23.222) as a potential reference:
• Introduces third-party API providers
• Enables third-party API providers to securely expose their capabilities to other services under PLMN control
• Resources of third-party API providers can be securely utilized by other services
• The architecture and procedures for third-party API providers in non-3GPP systems could serve as a reference for IMS session interworking with external (non-IMS) content sources
• Future Updates: SA6 commits to keeping GSMA NG UPG informed of their progress

Actions

The LS requests GSMA NG UPG to take the consolidated feedback from all SA Working Groups into account.