ECMA TR 77-1999 Telephony System with Integrated Internet Access - Overview《带有整合式互联网接入的电话系统 概述》.pdf

《ECMA TR 77-1999 Telephony System with Integrated Internet Access - Overview《带有整合式互联网接入的电话系统 概述》.pdf》由会员分享，可在线阅读，更多相关《ECMA TR 77-1999 Telephony System with Integrated Internet Access - Overview《带有整合式互联网接入的电话系统 概述》.pdf（24页珍藏版）》请在麦多课文档分享上搜索。

1、ECMA Technical Report TR/77December 1999Standardizing Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chTelephony System with IntegratedInternet Access -Overview.ECMA Technical Report TR/77December 1999Standardizi

2、ng Information and Communication SystemsPhone: +41 22 849.60.00 - Fax: +41 22 849.60.01 - URL: http:/www.ecma.ch - Internet: helpdeskecma.chIW TR-077.DOC 03-01-00 10,01Telephony System with IntegratedInternet Access -Overview.Brief HistoryThis Technical Report provides information on telephony syste

3、ms with integrated Internet access, coveringdefinitions, general architecture and standardization areas.Originally, the work was started in ISRF (Internet Screenphone Reference Forum) and has been brought to ECMATC32 for standardization in December 1998. TC32 has established a new Task Group (TG16)

4、being responsible forstandardization activities in this field.This document is the first document of a set of related documents, which will cover specification of functional entitiesof such a system and the corresponding procedures and protocols.The Technical Report is based upon the practical exper

5、ience of ECMA member companies and the results of theiractive and continuous participation in the work of ISO, ITU-T, ETSI and other international and nationalstandardization organisations.This Technical Report has been adopted by the ECMA General Assembly of December 1999.- 2 -.- i -Table of conten

6、ts1Scope 12 References 13 Acronyms 14 Definitions 24.1 Screenphone 24.2 Terminal Manager 24.3 Terminal profile 24.4 User Profile 25 Introduction 26 General architecture 36.1 Reference Model 36.1.1 Screenphone 36.1.2 Terminal Manager 46.2 Configuration examples 56.2.1 Private network (PISN) 56.2.2 Sc

7、reenphone connected to a PISN, Terminal Manager connected to a public telephonynetwork 66.2.3 Screenphone connected to a public telephony network, Terminal Manager to a PISN 66.2.4 Public telephony network 76.2.5 Connection of Terminal Manager to the Internet 77 Standardization paths 87.1 Potential

8、standardization areas 87.2 Co-operation with other standardization organizations 8Annex A - Services example 9Annex B - Status of related standardization activities 11- ii -.1ScopeThis Technical Report investigate Screenphones and network functionality in support of Screenphones.Possible standardiza

9、tion activities in this area are identified. Screenphones requiring no additional networkfunctionality are outside the scope of this Technical Report.2 ReferencesECMA 133 Standard ECMA-133 Private Integrated Services Network (PISN) - Reference Configuration forPISN Exchanges (PINX)ISRF ISRF-Specific

10、ation ISRF Webphone document, www.isrf.orgMExE 3GPP ETSI GSM02.57“Digital cellular telecommunications system (Phase 2+); MExE Stage 1Description“WAPTMWAPTMWireless Application Protocol (WAPTM), www.wapforum.org.W3C World Wide WebConsortiumwww.w3.org3 AcronymsAPI Application Programming InterfaceCP C

11、ontent ProviderECMA An International Europe-based Industry Association for Standardizing Information andCommunication SystemsETSI European Telecommunications Standards InstituteGSM Global System for Mobile CommunicationHTML Hyper Text Mark-up LanguageHTTP Hyper Text Transfer ProtocolIP Internet Prot

12、ocolISDN Integrated Services Digital NetworkISP InternetService ProviderISRF Internet Screenphone Reference ForumITU-T Telecommunication sector of International Telecommunication UnionMExE Mobile (Station) Execution EnvironmentPC Personal ComputerPINX PISN ExchangesPISN Private Integrated Services N

13、etworkPSTN Public Switched Telephone NetworkSMS Short Message ServiceSP Service ProviderTCP/IP Transport Control Protocol/Internet ProtocolWAPTMWireless Application ProtocolWWW World Wide Web- 2 -4 DefinitionsFor the purposes of this Technical Report, the following definitions apply:4.1 ScreenphoneP

14、hone with a display providing access to Internet based services.4.2 Terminal ManagerFunctional entity that fulfils services such as: access control, terminal configuration, Screenphone softwareupdate, etc.4.3 Terminal profileDefined set of functionalities of a Screenphone (hardware and software rela

15、ted).4.4 User ProfileCharacteristics defined by the user himself (e.g., personalised look and feel, etc.).5 IntroductionThere are two major networks for telecommunication: the Internet and the telephony network, but the accessto their services is usually based on separate terminal equipment, namely

16、PC and telephone. Considering this,it appears obvious to combine both technologies in a single device.This report describes a telephony system that enables telephony networks and Internet to offer complementaryvoice and information services accessible by a single terminal, a so-called Screenphone.Th

17、is Technical Report limits itself to the case where a Screenphone is attached to a (non-IP) TelephonyNetwork and accesses Internet via the Telephony Network. This does not preclude future studies ofScreenphones attached directly to Internet and using IP-Telephony techniques.Figure 1 Simple merger of

18、 telephony and Internet technologiesSimply merging these two technologies, as shown in figure 1, does not require additional standardization andis not considered further in this Technical Report. Instead this Technical Report focuses on an enhancedsystem architecture.In addition to the access to tel

19、ephony and Internet services, this system architecture will support:- implementation of Screenphones as low-cost dedicated devices,- service mobility/ user mobility in the sense of VHE (Virtual Home Environment),- zero maintenance end-user terminals (maintenance by network services, e.g. software up

20、dates),- provision of click-to-dial features.IP-NetworkScreenphoneTelephony Network(non -IP)- 3 -In order to fulfil these requirements, new functions are required, separate from the Screenphone itself. Thesefunctions are deemed to exist within a new functional entity known as a Terminal Manager, in

21、charge of themanagement of Screenphones. This is shown in figure 2.Figure 2 Screenphone system architecture with Terminal Manager6 General architectureThe general architecture chapter describes the “new” entities (the Screenphone and the Terminal Manager), areference configuration and some example s

22、cenarios.6.1 Reference ModelTwo new functional entities are of importance for this Technical Report: the Screenphone and TerminalManager functional entities. The Screenphone is the functional entity serving the user and the TerminalManager is the functional entity that provides the network functions

23、 in support of Screenphones. The twofunctional entities are separated by the new TM reference point as shown in figure hereafter.TerminalManagerTMScreenphoneFigure 3 Reference Model6.1.1 ScreenphoneA Screenphone may be used as an ordinary telephony device accessing common telephone servicesoffered b

24、y operators such as voice calls, fax, messaging (e.g. SMS) and supplementary services, and asan Internet access device.Typical characteristics of a Screenphone include a selection of the following: A single compact device for integrated voice and data communication. A screen to display alphanumerica

25、l and/or graphical data. Extended input device, e.g. keyboard, pointing device, touch screen. Easy to use, intuitive graphical user interface. Transparent access to network-based features. Integration of telephony and data services with click-to-phone features.IP-NetworkScreenphoneTelephony Network(

26、non -IP)TerminalManager- 4 - Administration and maintenance of terminal and services via network. Support of Smartcards: A Screenphone may include a smartcard reader device, which does notdepend on the type of card (e.g. memory cards, Javacards, multi-application cards, etc.) nor on thecard reader d

27、evice.6.1.2 Terminal ManagerAs the architecture must allow for zero maintenance end-user terminals (see clause 5), there is a need fora terminal management entity outside the terminal. This entity in the network is called TerminalManager.The Terminal Manager may be within the telephony network or ou

28、tside the telephony network (in theInternet).The Terminal Manager provides: The ability to personalize the user interface. This can be done directly by the end-user or by theTerminal Manager under the control of the end-user (acknowledgement). The ability to personalize services. Means to download n

29、ew features to the terminal (see 6.1.2.2). Means for remote maintenance of the terminal (see 6.1.2.1). The means for operator-specific services to be supported by all terminals of a particular terminalprofile, independent of the terminal vendor. A security architecture that provides an access contro

30、l to terminal resources, service control, etc.(see 6.1.2.3). The ability to charge subscribers for services. Storage of data, e.g. configuration values, subscribed services, Screenphone capabilities in user andterminal profiles.6.1.2.1 MaintenanceMaintenance of a Screenphone includes:- software upda

31、te, upgrade, addition, removal,- data management (update, removal),- memory management (garbage collection).6.1.2.2 ConfigurationConfiguration management refers to the behaviour of the Screenphone (terminal profile), and theability of the user to modify the terminal to behave in his preferred manner

32、 (user profile).The configuration parameter values which are specific to the Screenphone, and the user specific datamay be stored in the network (ISP, Operator, Terminal Manager) or locally in the terminal.User profileThe user profile may include the appearance of the display, the user interface and

33、 the access topersonalised services. It is securely managed and stored at least partly by the Terminal Managerconcerned.This covers mainly the following topics: Service subscription and unsubscription, e.g., weather, stock market information, etc The users and Terminal Managers capability to control

34、 the “look and feel” of applications/services The ability of the user to personalize the user interface Personalization of applications.- 5 -Terminal ProfileThe terminal profile includes data characterising the hardware and software capabilities of a specificScreenphone, e.g. kind of display and res

35、olution, input devices, APIs, local software applications,revision status, etc6.1.2.3 Access controlThe access control feature of the Terminal Manager may cover several aspects:- Filtering of the URLs (parental authorization for example).- Access control of the terminal resources: rejection of unaut

36、horized or unsupported services.- Gateway/proxy features: Translation of content (unsupported format) or protocols, etc6.2 Configuration examplesFor the purpose of this edition of the Technical Report, it is assumed that the Screenphone and theTerminal Manager functional entities have a one-to-one r

37、elationship with physical equipments. A furtherdecomposition of the Terminal Manager may be the subject of future investigations.A Screenphone may be connected only to a (public or private) telephony network, not directly to theInternet (IP Phone). A Terminal Manager may be connected to either netwo

38、rk. This leads to the physicalconfigurations shown hereafter.Interfaces to telephony networks already exist and are not affected by the introduction of these newentities, so these interfaces are not mentioned in the figures below.Different telephony network types are considered: private telephony ne

39、tworks (PISN) and public telephonynetworks (PSTN or public ISDN).In each of the physical configurations in 6.2.1 to 6.2.4, the Internet is not shown, as it is always “after” theTerminal Manager.6.2.1 Private network (PISN)In a PISN environment, the Screenphone and the Terminal Manager are connected

40、to a PINX. TheScreenphone may be connected to same PINX as the Terminal Manager or to a different PINX.Figure 4 Terminal Manager and Screenphone connected to the same PINXScreenphonePINXTerminalManagerTM- 6 -Figure 5 Terminal Manager and Screenphone connected to different PINXs6.2.2 Screenphone conn

41、ected to a PISN, Terminal Manager connected to a public telephony networkFigure 6 Screenphone connected to the PISN, Terminal Manager connected to a public telephony network6.2.3 Screenphone connected to a public telephony network, Terminal Manager to a PISNScreenphonePISNTerminalManagerPSTN /public

42、 ISDNTMFigure 7 Screenphone connected to the public telephony network, Terminal Manager connected to the PISNScreenphonePISN PSTN /public ISDNTerminalManagerTMPINXScreenphonePINXTerminalManagerTM- 7 -6.2.4 Public telephony networkThe two new entities are connected to a public telephony network.Scree

43、nphoneTerminalManagerPSTN /public ISDNTMFigure 8 Terminal Manager and Screenphone connected to a Public telephony network6.2.5 Connection of Terminal Manager to the InternetThe Screenphone is not directly connected to the Internet but the Terminal Manager can be, as shown infigure below.ScreenphoneP

44、ublic or privatetelephonynetworkTerminalManagerInternetTMFigure 9 Terminal Manager connected to the Internet- 8 -7 Standardization pathsStandards will ensure interoperability between multi-vendors products (Screenphone and Terminal Manager).Standardization should focus on new services and features t

45、hat are not already available from Internet orTelephony networks.7.1 Potential standardization areasPotential items for standardization by ECMA are:Screenphone:- interface specifications (may depend on the underlying access network)- signalling protocols and flows- procedures for terminal maintenanc

46、e (e.g. software download)- selection of supported payload transmission formats- information coding format (will depend on the display capabilities of the terminal)- support of supplementary telephony services (access network dependent).Terminal manager:- service definitions: related to maintenance,

47、 administration, admission, service request control androuting, data services, format conversion- interface specifications (APIs)- specification of signalling protocols and flows- selection of supported transmission formats.7.2 Co-operation with other standardization organizationsInternet services a

48、nd telephony services are discussed within external standardization organisations. Inorder to avoid work duplication, collaboration with the following organisations has been initiated: ISRF 3GPP / ETSI SMG 4 MExE WAP ForumTM IETF W3C ITU-T SG 16 Question 13, Packet based multi-systems and services I

49、TU-T SG 11 Question 5, IN related ISO/IEC JTC1 SC 6 WG 6 ISO/IEC JTC1 SC 35Available documents from these organisations might be considered as input for the work.- 9 -Annex A-Services exampleA.1 Internet ServicesPotential Internet services provided by a Screenphone in addition to voice telephony are: Access to WWW information sites E-Mail Customer care and provisioning Message notification Unified messaging (fax, SMS, voice-mail)?!? Weather and traffic alerts News, sports and information services E-commerce, stock transa