Skip to content
TechSpec
  • Foreword
  • 1 Scope
  • 2 References
  • 3 Definitions and abbreviations
  • 4 Introduction
  • 5 High level requirements
  • 6 Standardised service capability approach
  • 7 User service requirements
  • 8 Interworking requirements
  • 9 IP Addressing
  • 10 Interconnection requirements
  • 11 Support of WebRTC IMS Client access to IMS
    • 11.1 Service description (informative)
    • 11.2 Requirements
    • 11.3 Protocol Conversion Minimization Requirements
      • 11.3 Protocol Conversion Minimization Requirements
  • H.1 General
  • H.2 WebRTC-based application supports broad IMS client capabilities
  • H.3 User gets their IMS service via third-party WebRTC-based application
  • H.4 User gets third-party IMS service via WebRTC-based application
  • H.5 Anonymous user gets IMS service via third-party WebRTC-based application
  • H.6 End to end WebRTC bearer support over IMS
    • H.6.1 Description
    • H.6.2 Pre-conditions
    • H.6.3 Service flows
    • H.6.4 Post-conditions

9 IP Addressing

22.2283GPPRelease 16Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS)Stage 1TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

9.1 General

The Operator of an IMS infrastructure may base the implementation on IPv4 only, IPv6 only or both. The choice is an operator option.

The IMS may support UEs using IPv4 only, IPv6 only or both at an IP-based User-Network Interface. The choice is an operator option.

9.2 IP addressing for cdma2000 access to IMS

The IMS may support UEs using simultaneous multiple IP addresses.