- 1 -
FGNGN-OD-0009770
INTERNATIONAL TELECOMMUNICATION UNION / Focus Group On Next Generation NetworksTELECOMMUNICATION
STANDARDIZATION SECTOR
STUDY PERIOD 2005-2008 / FGNGN-OD-00097XXX
Original: English
WG(s) / WG1 / Jeju, March 16-22 2005
OUTPUT DOCUMENT
Source: / Co-Editors (M. Carugi, Brent Hirschmann)
Title: / NGN Release 1 scope document – WG1 output of Jeju March 2005 FGNGN meeting
- Abstract
This document provides the update of the NGN Release 1 scope document generated as WG1 output of JejuMarch 2005 FG NGN meeting.
The updated text is shown as revision marks to FGNGN-OD-00070 (output of Geneva November 2004 FG NGN meeting).
Editor’s note: to check with TSB if this page is necessary
ITU-T FG NGN Release 1 Document
NGN Release 1 Scope
Summary
To be aligned with the Scope section.
Key words
TBD
Table of Contents
Editor’s notes:
- specific Editor’s notes capture some technical issues to be solved and areas for contributions
- introduction of an Annex listing all deliverables of Release 1 has to be considered
-various requirements and high-level objectives have to be reworded in terms of requirement level (SHALL, SHOULD, MAY etc.)
- the document should be reviewed in terms of in scope versus out of scope where this clarification is considered useful or absolutely necessary
1Scope
Introduction
2References
3Terms and definitions
3.1Definitions
3.2Acronyms
4NGN target environment
4.1General
4.2Architecture and Interfaces
4.3Mobility
4.4Quality of Service
4.5Security
4.6Management
5NGN Release 1 Scope
5.1NGN Release 1 environment overview
5.2Business models
5.3Service subsystems
5.3.13GPP/3GPP2 IMS
5.3.2PSTN/ISDN Emulation
5.4 Service Framework and Application Support
5.4.1APIs to 3rd party Service Providers
5.5 Interconnection and NNIs
5.5.1NNIs to non-NGN networks
5.5.2NNIs between NGN domains
5.6 Access Networks
5.7Customer networks
5.8NGN end user equipment
6NGN Release 1 services
6.1PSTN/ISDN Emulation services
6.3PSTN/ISDN Simulation services
6.4Multi-media services
6.4.1General principles for codecs use in NGN
6.5Internet access
6.6Other services
6.7Public Services Aspects
6.7.1 Service delivery under specific country or local conditions
7NGN Release 1 service capabilities
7.1Basic network capabilities
7.1.1Routing
7.1.2Network management aspects
7.1.3Basic OAM
7.1.4Mobility management
7.1.5QoS-based Resource and Traffic Management
7.1.6Security and Privacy
7.1.7Identification, authentication and authorization
7.1.8Interoperability and Interworking
7.1.9Access Network capabilities
7.1.10Policy management
7.1.11User Profile management
7.1.12 User device
7.1.13 Communication handling
7.1.14Media resource management
7.1.15Session handling
7.1.16Numbering, naming and addressing aspects
7.1.17Accounting, Charging and Billing
7.2 Service support capabilities
7.2.1Service enablers
7.2.2Open service environment
7.2.3PSTN/ISDN emulation support
7.3Public service aspects
Appendix I (informative) – Service Descriptions and Use Cases
I.1General Use Cases
I.2Business Use cases
I.3Medical Use Cases
Appendix II (informative) – Examples of categorization of Services
II.1Basic/Enhanced services versus Service/Transport stratum
II.2Unicast/Multicast/Broadcast versus Real-time/Non-real-time: General mapping
II.3Business Mapping
II.4Medical Mapping
Appendix III (informative) – Mapping of Services and Service Enablers Capabilities
1Scope
This document provides a high level description of NGN Release 1 and its scope in terms of supported services and capabilities.
This document describes the services and capabilities provided within the scope of the first Release of an NGN.
This document describes high level objectives, in terms of the services and capabilities. Further documents provide the detailed requirements for NGN Release 1.
Introduction
The scope of the documents forming Release 1 is aligned with the general goals and objectives of an NGN. Release 1 is considered the first step towards a comprehensive framework of services, capabilities and network functions that are considered to constitute an NGN, as described in [1].
An NGN is expected to provide an extensible framework that provides the ability to deliver services tailored to both users and Service Providers requirements. Specific realisations of NGN Release 1 may therefore support additional services and capabilities not described in this document. Service Provider requirements will determine which of the particular set of services and capabilities to support in a particular network.
Release 1 Services described in this document have been limited to the set of services that compromise a particular PSTN/ISDN (as part of a replacement scenario); the set of service capabilities and structure that a 3GPP/3GPP2 IMS [Reference needed] can provide but adapted to support other user equipment and access network technologies. Public service requirements are taken into account.
The document is organised as follows:
-section 2 provides references;
-section 3 provides terms and definitions;
-section 4 provides an overview of the NGN target environment;
-section 5 provides the scope of NGN Release 1 in terms of environment and key aspects;
-section 6 provides a list of NGN Release 1 services;
-section 7 provides a list of NGN Release 1 service capabilities
1Scope
This document provides the scope of NGN Release 1 in terms of services, capabilities and requirements as high-level objectives.
This scope is aligned with the general goals and objectives of an NGN [1].
The detailed services, capabilities and requirements of Release 1 are contained in other documents.
Specific realizations of NGN Release 1 may support additional services and capabilities not covered in this document.
The document is organised as follows:
-section 2 provides an overview of an NGN target environment;
section 3 provides references;
section 4 provides terms and definitions;
section 5 provides the scope of NGN Release 1 in the various areas of services, capabilities and network components
2Overview of an NGN target environment
NGN will offer the user access to a comprehensive set of services in a converged IP-based core network, supporting a multiplicity of access networks and a variety of mobile and fixed terminal types. The trend towards heterogeneous networks with complementary capabilities implies that support for scalable network elements and multi-communication mode terminals will be important. The mobile user in particular requires seamless and transparent mechanisms for roaming between network operators and continual access to tailored services from a variety of environments while using a variety of terminals with varying capabilities. In particular, rich multimedia applications involving voice, audio, data, graphics and video/TV pictures receive prominent support from NGN to satisfy expectations of end users, and to allow service providers, network providers and equipment manufacturers to benefit from new opportunities.
Editor’s note: the term “converged” in the initial sentence needs to be clarified
2References
The following ITU-T Recommendations and other references contain provisions, which, through reference in this text, constitute provisions of this Specification. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Specification are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
Editor’s notes:
-references to be completed and positioned appropriately (in section 3 or bibliography)
-distinction among normative and informative references to be considered
[1] ITU-T Recommendation Y.2001: General overview of NGN functions and characteristics
[2] ITU-T Recommendation Y.2011: General Reference Model for Next Generation Networks
[3] ITU-T Recommendation Y.101: GII terminology: Terms and definitions
[4] ETSI TISPAN_NGN TR 00001 Release 1 Definition
[Y.NGN-FRA]
[reference NGN-FRMOB]
[Y.110]
[SG13 Recc. on Emergency services]
[M.3050/eTOM]
[ATIS-NGN-FMWK] – ATIS NGN Framework – Part 1
CableLabs PacketCable Multimedia
[E.1646] ITU-T Recommendation E.164
[H.5107] ITU-T Recommendation H.510
[F.8528] ITU-T Recommendation F.852
[Q.17619] ITU-T Recommendation Q.1761
[ENUM]
[OMA-RD_PoC-V1] – OMA Push to Talk over Cellular Requirements Version 1.0
[3GPP-IMS-REL6]
[3GPP2-IMS-RevisionA]
[22.057] – 3GPP Series, 22.057, Mobile Execution Environment (MExE).
[22.140] – 3GPP Series, 22.140, Multimedia Services (MMS).
[22.146] – 3GPP Series, 22.146, Multimedia Broadcast/Multicast Services (MBMS).
[42.033] – 3GPP Series, 42.033, Lawful Intercept for GSM Networks.
[22.127] – 3GPP Series, 22.127, Requirements for Open Services Architecture – Stage 1.
[23.127] – 3GPP Series, 23.127, Virtual Home Environment (VHE) / Open Service Access (OSA) (Release 6)
[23.141] – 3GPP Series, 23.141, Requirements for Presence Services – Stage 1.
[reference-IPe2eQoS]
[reference NGN-SEC guide]
Others (ITU-T FG NGN, ITU-T SG13, ITU-T FG NGN Management, 3GPP Release 6, 3GPP2 revision A etc.)
References for Access Network technologies
Wireless Local Area Network (WLAN)
[802.11]IEEE 802.11 Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, 1999
[802.11a]IEEE 802.11a Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: High-speed Physical Layer in the 5 GHz Band, 1999
[802.11b]IEEE 802.11b Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications: Higher-Speed Physical Layer Extension in the 2.4 GHz Band, 1999
[802.11d]IEEE 802.11d “Specification for Operation in Additional Regulatory Domains”, 2001
[802.11e] IEEE 802.11e Draft - Medium Access Control (MAC) Quality of Service (QoS) Enhancements, 2004
[802.11f]IEEE 802.11f Recommended Practice for Multi-Vendor Access Point Interoperability via an Inter-Access Point Protocol Across Distribution Systems Supporting IEEE 802.11 Operation, 2002
[7802.11g]IEEE 802.11g Further Higher-Speed Physical Layer Extension in the 2.4 GHz Band, 2003
[802.11h] IEEE 802.11h Spectrum and Transmit Power Management Extensions in the 5GHz band in Europe 2002
[802.11i]IEEE 802.11i Medium Access Control (MAC) Security Enhancements, 2004
[802.11j]IEEE 802.11j Draft - 4.9GHz-5GHz Operation in Japan, 2004
[802.1X]IEEE 802.1X IEEE Standard for Local and Metropolitan Area Networks - Port-Based Network Access Control”, 2001
Broadband Wireless Access
[802.16]IEEE 802.16-2001 Air Interface for Fixed Broadband Wireless Access Systems
[2802.16a]IEEE 802.16a-2003 Air Interface for Fixed Broadband Wireless Access Systems--Amendment 2: Medium Access Control Modifications and Additional Physical Layer Specifications for 2-11 GHz
[802.16c]IEEE 802.16c-2002 Air Interface for Fixed Broadband Wireless Access Systems--Amendment 1: Detailed System Profiles for 10-66 GHz
[802.16e]IEEE 802.16e-2002 Draft - Air Interface for Fixed Broadband Wireless Access Systems--Amendment for Physical and Media Access Layers for Combined Fixed and Mobile Operation in Licensed Bands
Broadcast
[DVB-S]ETSI EN 300 421 DVB-S: Framing structure, channel coding and modulation for 11/12 GHz satellite services
[DVB-S2]ETSI EN 302 307 DVB-S2: Second generation framing structure, channel coding and modulation systems for Broadcasting, Interactive Services, News Gathering and other broadband satellite applications (DVB-S2)
[dvb-T]ETSI EN 300 744 DVB-T Framing structure, channel coding and modulation for digital terrestrial television
[DVB-H]ETSI EN 302 304 DVB-H: Transmission System for Handheld Terminals (DVB-H)
[DVB-SI]ETSI EN 300 468 DVB-SI: Specification for Service Information (SI) in DVB systems
[DVB-Data]ETSI EN 301 192 DVB-Data: Specification for data broadcasting
[ATSC 53C]ATSC A/53C: ATSC Digital Television Standard, Rev. C
[ATSC 65B]ATSC A/65B: Program and System Information Protocol for Terrestrial Broadcast and Cable, Rev. B
[ATSC 90]ATSC A/90: Data Broadcast Standard
[ARIB B10]ARIB STD-B10 Service Information for Digital Broadcasting System
[ARIB B20]ARIB STD-B20 Transmission System for Digital Satellite Broadcasting
[ARIB B24]ARIB STD-B24 Data Coding and Transmission Specification for Digital Broadcasting
[ARIB B31]ARIB STD-B31 Transmission System for Digital Terrestrial Television Broadcasting (ISDB-T)
[J.160]Architectural framework for the delivery of time-critical services over cable television networks using cable modems
[J.178]IPCablecom CMS to CMS signalling
[J.179]IPCablecom support for multimedia
3Terms and definitions
3.1Definitions
Editor’s notes:
- definitions have to be provided and agreed across the whole set of NGN deliverables;
- the terms listed below are directly defined in this document, other terms used in this document are defined in other documents but their reference is provided here;
- a number of terms and definitions could go into an Appendix, to avoid references to unapproved external documents in the main body of the specification
- terminology is required (using existing references wherever possible) for:
-Mobility terms (nomadism, roaming, handover, mobility management )
-“IMS”, “subsystem”
-Access network
-Core network
-Interfaces (various interfaces to be defined)
-Interconnection
-PSTN/ISDN emulation and simulation
-IP-CAN
-etc.
This document defines the following terms (reference is provided for the term is defined in another document):
TBC
Generalized Mobility: the ability for the user to communicate and access the same services irrespective of changes of the location or access technology capabilities or technical environment such as the Access Network capabilities, with or without service continuity.
Terminal Mobility: Terminal Mobility is defined as the terminal having the ability to be moved to different physical locations and provide the user access to their services.
Personal Mobility: The ability of a user to access services independent of the terminal or the location of the terminal. The ability of a user to access services at any terminal.
Editor’s note: other case of mobility has to be covered (“Network termination Point”)
Service Continuity: The ability for a user to maintain an ongoing service during Generalized Mobility.
Continuous Terminal Mobility: Terminal mobility with service continuity.
Nomadism: Personal or Terminal mobility without service continuity.
Editor’s note: other terms require definition (NTP, etc.)
34.2Acronyms
BBCBasic Bearer Capability
CUGClosed User Group
DRMDigital Right Management
DVBDigital Video Broadcast
EBCEnhanced Bearer Capability
FTTHFiber to the Home
GPSGlobal Positioning System
HDTVHigh Definition Television
IMInstant Messaging
ISDBISDN Digital Broadcast
MMSMultimedia Message Service
MODMusic on Demand
OTAOver the Air
OTNOver the Network
PDAPersonal Digital Assistant
PoNPush to talk over NGN
PSTNPublic Switched Telephone Network
RFIDRadio Frequency Identification
SCFService Capability Features
SCSServcie Capability Servers
SLAService Level Agreement
SMSShort Message Service
TDMTime Division Multiplex
URLUniform Resource Locator
VODVideo on Demand
VoIPVoice over Internet Protocol
VPNVirtual Private Network
WLANWireless Local Area Network
xDSLVarious types of Digital Subscriber Line
To be completed and checked
4NGN target environment
4.1General
NGN will offer the user access to a comprehensive set of services that are carried over a unifying IP layer network. It supports a multiplicity of access networks and a variety of mobile and fixed terminal types. Services are not limited to those of the “home network”, but may be obtained from multiple Service Providers. The trend towards heterogeneous networks with complementary capabilities implies that support for scalable network elements and multi-communication mode terminals will be important. The mobile user in particular requires seamless and transparent mechanisms for roaming between network operators and continual access to tailored services from a variety of environments while using a variety of terminals with varying capabilities. In particular, rich multimedia applications involving voice, audio, data, graphics and video/TV pictures receive prominent support from NGN to satisfy expectations of end users, and to allow service providers, network providers and equipment manufacturers to benefit from new opportunities.
Recommendation Y.2001 gives a general overview of what constitutes and defines a Next Generation Network (NGN). More specifically, it identifies the fundamental characteristics and capabilities that an NGN should be able to support.
4.2Architecture and Interfaces
It’s assumed that NGN Release 1 services and capabilities be based where possible on existing specifications.
Editor’s note : above text and figure from ID-491 have to be confirmed and possibly modified based on output of WG2 discussions. Rel.1 dependencies have to be removed from the text.
One of the main features of NGN architecture is the separation between service and transport as described in the NGN general reference model Recommendation Y.2011. The NGN architecture framework consists of a service stratum and a transport stratum as shown in figure 1. In this figure, there are the oval, which means a platform accommodated the function group, the square, which means a specific function such as customer profile management, the cloud, which means transport functions.
NGN functions are divided into service functions such as application functions and transport functions such as access transport functions. In the transport stratum, access transport functions are located in the access network layer and core transport functions located in core network layer. Other networks are interconnected through NNI, as shown on the right side of the figure. Customer networks are connected by UNI.
NGN supports the delivery of end-user services through application servers, rather than directly embedding services as capabilities in the control protocols. For real-time conversational services (SIP based session control), the application server controls the communication session by modifying the behaviour of the generic session control (e.g. using triggers).
NGN supports open APIs to allow 3rd party Service Providers to apply NGN capabilities to create enhanced services for NGN users.
APIs should be secure and standardized. The APIs should be independent of vendor specific solutions and programming languages/operating systems agnostic. The APIs should be also independent of the location, access technology within the environment where service capabilities are implemented and independent of supported service capabilities in the network.
Editor’s note: Need to add text on 3rd party API in figure below.
Figure 1 - NGN architecture overview
4.3Mobility
NGN communications and services are available to all qualified users requesting those services, regardless of the type of access network technology. NGN is supporting wireless as well as wired access and in principle the possibility for the user to gain access to any service from any fixed or mobile terminal as long as the desired service can be tailored for the specific terminal type and is compatible with the QoS of the access network. The actual level of mobility of the user will depend on the commercial arrangements with his “home network” provider. Figure 2 depicts the levels of mobility in NGN.
Figure 2 – Mobility levels in NGN
NOTE: Figure 2 is an extended version of Figure 8/ Y.2011
The User can use any type of Terminal Equipment anywhere as long as it allows him to authorize himself for service access with his “home network” provider. The Terminal Equipment can be associated with any Network Termination as long as it has a compatible interface. A Network Termination may support one or more Terminal Equipments. A Network Termination may have a fixed or dynamic (mobile) association with any compatible Network Attachment Point as long as it can be authorized for network access. by its “home network”.