TIPHON Perspective on Vo IP Numbering John Horrocks

TIPHON Perspective on Vo. IP Numbering John Horrocks (DTI) Tiphon WG 4 Chair Document IPW-11 1

Tiphon • Numbering relates to services not technology • Regulation depends on services not technology • IP can support many different services • Aiming primarily at needs of telcos who migrate services onto IP • Naming based on E. 164 for public telephony (alternatives not excluded) • Expect telcos will want protected boundaries so design for step/step call set-up with migration to end-end (hacking, quality control, call related charging, culture) • Not dependent on public E. 164 -IP resolution system for starting 2

Names and Addresses: Basics-1 • Name: Unique identifier of communicating entity, used by network, may be structured for user and contain geographic information • Address: Location of entity in terms of network structure 3

Names and Addresses: Basics-2 Acknowledgement: DGTP Netherlands 4

Main current work areas • IETF: IPTEL general work based on SIP • ENUM selection of means to communicate with E. 164 number, based on DNS, precursor to use of SIP for call • IETF: PINT Control connection between PSTN dial-up access and ISP • Tiphon: E. 164 to IP resolution Acknowledgement: DGTP Netherlands 5

Where Tiphon fits in (Search engines) Tiphon E. 164 ENUM Services E. 164 Choice Services E. 164 URL E. 164 SIP IPTEL User@host Acknowledgement: DGTP Netherlands IP address 6

Different service concepts Common service model Different service model ETSI Tiphon H. 323 Voice telephony service E. 164 Switched circuit networks IP networks IETF SIP SCN telephony E. 164 IP telephony User@host + E. 164 Switched circuit networks IP networks Acknowledgement: DGTP Netherlands 7

Common service numbering Needed for E. 164 - IP resolution Customers of IP operators allocated E. 164 numbers under this system Acknowledgement: DGTP Netherlands No updating from users or IP based operators without allocation from NRA 8

The Future: Multi-Everything Multiple Users (different roles, different persons, distinctive alerting) Multiple terminals Multiple accesses (eg fixed, mobile 1, mobile 2) Multiple service providers Multiple services (eg telephony, fax data, video) 9

Future caller needs 10

Future solutions • Avoid a wholly new system allow smooth market-led migration • Grow E. 164 for different roles/labels • Hide E. 164 with better terminals and search engines • Work needed on privacy vs exchange of information to facilitate search engines 11

Tiphon Approach • Many different voice related services supported on IP • E. 164 use depends on service implemented • Interconnected networks with real boundaries • Allow Step-by-step call set-up 12

Service resolution (may be repeated) Service information could also be accessed by later gatekeepers Service information may be accessed either from SCN or IP Search resolution Address book Search engine or Directory Any information on called party E. 164 - IP routing resolution (may be repeated) E. 164 -IP Resolver Called or Routing E. 164 number (directory number) Next hop information Called or Routing E. 164 Gatekeeper Called E. 164 Routing E. 164 - IP local endpoint resolution (may be repeated) E. 164 -IP Resolver Next hop information Called or Routing E. 164 Home Gatekeeper IP address for media If present Terminal information IP address for media H. 225 signalling Calling terminal Route on called E. 164 SCN switch Ingress IP gateway Media There are various options for this signalling Route on routing E. 164 Routing mostly uses tables in SCN switches. One switch may use IN for service information SCN technology IP technology 13

Resolves R(E. 164) into IP address for Gatekeeper at destination Service resolution Service information Home Gatekeeper Service control Routes on IP address but carries calling & called E. 164 R(E. 164) Cd(E. 164) Ingress Gatekeeper Call control R(E. 164) Cd(E. 164) Checks availability of terminal Negotiates IP addresses for media channel Call control IP address of terminal media port SCN switch Possible network boundary IP Routing (UDP) Media I’face Uses IP address from call control contains implicit call identification Media Terminal (or gateway back to SCN) Possible network boundary Uses available interconnections may give some quality control SCN Signalling I’face Ingress Gateway Possible extension to SCN H. 225 signalling Opens media SCN switch Call control IP Cd(E. 164) = Called E. 164 number R(E. 164) = Routing E. 164 number 14

E. 164 - IP Routing Resolution E. 164 - IP Local Endpoint Resolution SC 1 a - Cd R(E. 164) or Cd (E. 164) 4 a - Cd R(E. 164) 2 a - S 2 i When 2 a +2 b received Start SC 3 - Set-up 6 - Set-up contains S 1 o may contain M 1 o contains S 2 o may contain M 2 o S 2 i CC Signalling 12 - Connect may contain M 2 i 2 b - M 1 o reserved 13 - Activate media S 2 o BC 11 - Connect pairs (M 2 i, MTi), (M 2 o, M 1 o) 2 b - M 1 o reserved 13 - Activate media BC M 2 i 4 b - Reserve media 11 - Connect pairs (M 2 i, MTi), (M 2 o, M 1 o) 5 b - M 2 i, M 2 o reserved MC Ingress Gateway Call set-up direction 7 - Reserve media 9 - Activate media 8 - MTi Reserved MTi MC M 1 o 8 - MTi Reserved BC MTi M 2 i Bearer CC 10 - Connect may contain MTi 7 - Reserve media 5 b - M 2 i, M 20 9 - Activate reserved media M 2 o 4 b - Reserve media M 1 o 1 b - Reserve media STi CC S 1 o 1 b - Reserve media 5 a - STi Home Gateway MC M 2 o Terminal 15

SC SC 4 a - Cd R(E. 164) 2 a - S 2 i 1 a - Cd R(E. 164) When 2 a +2 b received Start 3 - Set-up contains S 1 o may contain M 1 o 6 - Set-up S 2 i contains S 2 o, M 2 o CC CC S 1 o 1 b - Reserve media 9 - Connect may contain M 2 i 2 b - M 1 i, M 1 o reserved 10 - Connect pairs (M 1 i, M 2 i), (M 1 o, M 0 o) 5 a - S 3 i S 2 o 4 b - Reserve media 7 - Connect 5 b - M 2 i, M 20 reserved 8 - Connect pairs (M 2 i, M 3 i), (M 2 o, M 1 o) M 1 o BC 1 b - Reserve media 10 - Connect pairs (M 1 i, M 2 i), (M 1 o, M 0 o) BC M 2 i 2 b - M 1 i, M 1 o reserved 4 b - Reserve media 5 b - M 2 i, M 2 o reserved 8 - Connect pairs (M 2 i, M 3 i), (M 2 o, M 1 o) M 1 i M 2 i MC Network 1 Gateway MC M 1 o Call set-up direction Network 2 Gateway M 2 o 16