IN Internet Overview of Standardisation activitities

1
IN / Internet Overview of Standardisation
activitities

• Valérie Blavette
• France Telecom
• valerie.blavette_at_cnet.francetelecom.fr

2
Overview

• IETF
• SigTran
• Megaco
• PINT/PIN
• ITU SG11- Q5
• ETSI TIPHON
• IN-FORUM

• TINA-IN WG
• ...P909...
• MSF
• Parlay
• JAIN
• ETSI SPAN3
• ETSI NA6- SPAR

3
IETF- SIGTRAN

• To define an architecture and related protocols
  to support transport and interworking of
  signalling (ISUP, ...) over IP.
• Applications
• off-load of Internet traffic, by means of SS7
• integrated services (eg. VoIP)
• IP transport of SS7 signaling
• - Proposed Standard by summer/99

4
IETF- MEGACO

• Requirements analysis and protocol definition for
  controlling Media Gateways from external servers
  
• Media Gateway Controller.

5
IETF ITU- MEGACO
History

IPDC (Level 3)
SGCP (Cisco/Bellcore)

MGCP (Telcordia, Level3 IETF draft, April 99)
ITU-T SG16 H.248/MeGaCo (draft Sept.99)
6
IETF PINT/PIN WG

• PINT (PSTN and Internet Interworking) Internet
  to PSTN
• Milestone services click-to-dial, click-to-fax,
  
• Protocole PINT based on a SIP protocol
  extension
• PIN (PSTN Internet Notification) PSTN to
  Internet
• Milestone services Internet Call Waiting,
• Protocole PIN not already defined

IP Network
PINT/PIN Gateway
PINT/PIN Client
PINT/PIN Protocol
7
ITU SG11- Q5 architecture IN Internet
8
ITU SG11- Q5 - INH.323

• Functional model involving IN and H.323
  interworking. The location of the different
  functional entities in physical entities depends
  on the H.323 routing model used
• Possible groupings in MGC and GK
• DRCDirect-routed callThe terminals or gateways
  exchange call control signalling (H.225, H.245)
  directly with each other. Interaction between
  terminal/GW and GK is only via RAS
• GRC Gatekeeper-routed call In addition to RAS,
  the terminals or GWs exchange call control
  signalling via the GK, which acts as a signalling
  proxy. The GK may alter the signalling
  information.

9
ITU SG11- Q5 - INH.323
10
ITU SG11- Q5 - INH.323
11
ITU SG11- Q5 - INH.323
12
ITU SG11- Q5 - INPINT
13
ETSI Project TIPHON

• Telecommunications and Internet Protocol
  Harmonization Over Networks
• Objective to support a market for voice
  communication and related multimedia aspects
  between users in IP based networks and users in
  switched circuit network (SCN), as well as
  between users in an SCN using IP based networks
  for connection/trunking between involved SCN, by
  the production of appropriate ETSI deliverables.

14
ETSI Project TIPHON

• TIPHON works for interoperability using existing
  standards
• IETF IP, TCP, UDP, RTP, RTCP, ...
• ITU-T
• H.323 Packet based multimedia communications
  systems
• H.225.0 Call Signalling Protocols and Media
  Stream Packetization for Packet Based Multimedia
  Communications Systems
• H.245 Control protocol for multimedia
  communication
• G-Series (G.711, G.722, G.723, G.728 und G.729)
  Codecs
• GSM Codecs 06.10 FR, 06.20 HR und 06.60 EFR
• TIA/EIA IS-641 Enhanced Full-Rate Speech Codec
• Q.931 (DSS1), SS7 ISUP, etc

15
ETSI Project TIPHON

• Scenario 0 IP Terminal (PC) to PC
• Scenario 1 IP Terminal to Phone (including
  IN services)
• Scenario 2 Phone to IP Terminal
• Scenario 3 Phone via Internet to Phone
• Scenario 4 IP Terminal via SCN to IP Terminal
  (useful?)
• (PSTN/ISDN/GSM)

16
Why is standardisation and TIPHON needed?

• Provider (IP-Telephony Service Provider) want to
  use products from different manufacturers in
  their networks.
• Manufacturers want to specialise on specific
  products (e.g. gateways, gatekeeper, clients,
  etherphones, ...)
• Standards are necessary for the interworking
  between administrative domains.
• Centralized and global services are necessary
  (clearing houses, certification authorities, the
  global Internet-Telephony directory service, ...)

17
IN Forum - IN-CT

• support wide range of services IN-CT
• define association and interworking between IN
  CT
• identify relevant standards and submit inputs to
  them
• Position Paper IN-CT Interworking
  opportunities
• opportunities for new services in IN-CT
• focus on IN-CT services Net Call Center
  Internet Enhanced Telephony (later moved to
  IN-IP)

18
Joint group ECTF / INF IN-CT Architecture

• (ECTF Enterprise Computer Telephony Forum
• definition of CTI open architecture)
• Mission To create a functional level reference
  architecture relating common components and
  interfaces across the Intelligent Network and
  Computer Telephony architectures. The functional
  architecture will be used to define an
  Interworking specification for cross IN-CT
  services

19
IN Forum - IN-IP

• Starting end of 98 Chair GTE, Compaq
• facilitate the broader application of IN
  capabilities in the PSTN to access Internet
  functionalities and viceversa, for providing
  synergistic arrangements for new and existing
  services...
• Objective .. Enhance industry awareness of
  IN-IP services/capabilities, so as to assist both
  individual companies and the industry in their
  efforts to develop and deploy IN-IP
  services/capabilities..

20
IN-IP - Activities

• Architecture for IW and protocols in liaison with
  other Fora
• IN-IP focuses on services and capabilities
• service selection
• monitoring of industry activities
• service descriptions by means of end to end call
  flows
• identification of service logic and data
  distribution
• performance issues
• business and regulatory issues

21
IN-IP - Expected Outputs

• 1st release of specification for an initial set
  of services 1stH99
• Selected services CNAM (Calling NAMe), VPN,
  Voice Mail, UM, IN Routing, CF, LNP, 800,
  Mobility, Network Call Center

22
IN-IP

• Specifications consists of
• service description (user view)
• call completion scenarios
• end to end call/message flows
• network diagram
• it uses as reference architecture a merge
  between IETF ETSI TIPHON
• it liaises with IETF SIGTRAN, MeGaCoP (objective
  is to reduce the number of different proposals
  8-10 during 98)

23
IN-IP IETF

• Signalling Transport WG - SIGTRAN
• have a first draft on requirements some
  proposals for carrying SS7 over IP April
  99
• will identify the method of encapsulation of
  different signalling protocols
• goal is to provide RFCs for transport of
  packet-based PSTN signaling over IP Networks,
  taking into account functional and performance
  requirements of the PSTN signaling July 99

24
IN-IP IETF (2)

• Media Gateway Control WG - MEGACO has produced
• megaco requirements,
• an architecture and requirements document,
• a protocol document on control of an MG by an MGC
  (open issue is the scope IP only, or does it
  also include ATM ?)

25
TINA-IN WG

• Intelligent Networks migration towards TINA
• part of the structure of the TINA Forum, since
  April 97
• Goal To enable the development of industrial
  quality products related to the evolution of
  Intelligent Networks infrastructure and services,
  by proposing implementable interfaces to real
  business needs.
• Work process Issue of RFR/Ss, evaluation of
  responses and submission of them to the TINA
  Architecture Board (TAB) and TINA Forum (TF) for
  endorsement as TINA specifications.
• 17 Members Alcatel, ATT, Bellcore, BT, Cegetel,
  CSELT, Deutsche Telekom, France Télécom,
  GMD-Fokus, Humboldt University, KPN, Lucent,
  Nortel, NTT, Siemens, Sprint, Sun
• http//www.tinac.com/wg_sig/in/Main.htm

26
TINA-IN WG - Areas of interest

• In line with market needs and business
  opportunities related to IN and IN evolution,
  such as
• Existing IN services that need integration with
  other IN or non-IN services,
• New IN services that could take advantage of TINA
  capabilities (i.e. distribution of intelligence,
  connection management),
• Web and IN convergence, like service interaction
  requiring IN connection management (e.g.
  click2dial), or IN service customization and
  management using Web access
• Services that span PSTN and corporate telephone
  networks domains (CTI and IN convergence).

27
TINA-IN WG - current activities

• RfP IN access to TINA services Connection
  Management (IN-TINA Adaptation Unit)
• issued end of 98
• endorsement of the merged answer to the RFP by
  the TAB (Oct.)
• call control interfaces included in the response
  rely on Parlay specs
• IN-Evolution problem statement document (CSELT,
  Lucent)
• close to P909, mainly targeted on IN-Internet
  integration
• no further activity yet
• Possible RfP on VoIP issues (Alcatel)
• Def. Call Control interface that maps on x.GCP,
  closely related to TINA-IN RfP
• problem statement document in work

28
TINA to P909

• Common cultural background
• project proposal comes from TINA-IN members
• Modeling concept
• information computational models
• Use of a distributed architecture
• Reuse and extension of TINA defined
  components/concepts
• user profile, session model
• Reference points and APIs (IDL)

29
P909 to TINA-IN Parlay

• Applying TINA architectures and concepts to P909
  reference architecture
• Use of TINA components and interfaces to
  implement P909 network services and service
  scenarios
• Mapping Identified Functionality to TINA
• Identification of new components
• TINA and P909 Call Control (Parlay)
• TINA and IN-Interworking
• TINA and Messaging
• Messaging, Virtual Presence and C2D scenarios
• P909 Parlay WG report

30
MSF Multiservice Switching Forum

• Background ideas Decrease dependencies on
  underlying technology
• choose a switching fabric (eg. ATM)
• Intelligence in a single point, distribution of
  HW
• separation control/ switching
• provide switches with standard itf
• Virtual Switch Model (virtual switch
  partitioning)
• control partitions from several systems
  (SS7/ISUP, UNI/PNNI, IP/PMPLS)
• definition of interface and protocol for VSC
  (Virtual Switch Control protocol)

31
MSF architecture view

• 3 WG Architecture, Switch Control, Media Gateway
  Control

32
The Parlay group context

• A closed group composed by 11 members (BT,
  Microsoft, Nortel Networks, Siemens, Ulticom
  ATT, Cegetel, Cisco, Ericsson, IBM, and Lucent )
• Goal to define APIsto enable secure public
  access to core capabilities of telecom and data
  networks

33
Parlay Group work status

• Specifications are available (v1.2)
• No Reference implementation available,No SDL
  available, No Product.

34
The Parlay Group influence

• Parlay specifications are introduced in different
  organisations
• OMG TSAS (only some parts of the Parlay
  framework)
• ETSI SPAN 3
• JAIN
• TINA-IN WG
• ...

35
JAIN context

• JAIN specifications is carried out under the
  terms of Sun s Java Specification Participation
  Agreement
• 12 participating companies
• The work is splitted between the two groups of
  experts PEG and the AEG.

36
JAIN area of interest

• Java specification requirements related to JAIN
  are covering
• SIP API, MAP API, Connectivity Management, Call
  Control API, MGCP API, OAM API, ISUP API, TCAP
  API, SCE/SLEE API, Parlay-JAIN API

37
JAIN work status

• JAIN TCAP public review closed
• JAIN OAM public review closed
• Other items are under work inside JAIN community

38
SPAN3 APIs

• API for Third Party Service protocol design and
  interfaces
• API for Third Party Service protocol mapping
  jointly with H.323 (SG16), 3GPP and IETF

39
SPAN3 APIs- Work Item status

• Currently 3 supporting organisations (BT,
  Alcatel and Ericsson). One more is needed.
• Initial inputs sent by BT (Parlay specs a
  Parlay INAP mapping)
• SPAN 3 would base the API specification upon the
  requirements given in the new SPAN 6 work item
  entitled Modelling Service

40
SPAR Service Provider Access Requirements

• ETSI- NA6 Working Group
• Under TC SPAN Services and Protocols for
  Advanced Networks, merged Network Access (NA) and
  Signalling protocols and Switching (SPS) groups
• Working to provide guides/requirements for SPA as
  input to standardisation

41
What SPAR is working with

• Providing documents as guidelines for input to
  standardisation work in the SPA area
• Three documents
• NA-061601 - Service providers access
  requirements
• NA-061602 - Mobility and Internet Telephony
  requirements
• NA-061603 - Network operators requirements for
  the delivery of service provider access

42
Status of SPAR work

• NA-061601 Frozen
• NA-061602 Work barely started. Co-operation
  with the UMTS Task Force. Due to be completed
  spring 2000
• NA-061603 Work progressing. Due to be completed
  in December 1999

43
Conclusion

• IN-Internet is a  hot subject
• Many bodies tackle the IN-IP subject
• from the architecture point of view
• from the protocol point of view
• from the API point of view
• gt But a global view of these aspects is often
  missing
• Within one year timeframe should the situation
  be clearer