ETSI TS 102 289-2003 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) TIPHON UMTS Harmonization Guidelines for implementation of service capabilities《网_1.pdf

1、 ETSI TS 102 289 V1.1.1 (2003-11)Technical Specification Telecommunications and Internet ProtocolHarmonization Over Networks (TIPHON);TIPHON/UMTS Harmonization:Guidelines for implementation of service capabilitiesETSI ETSI TS 102 289 V1.1.1 (2003-11) 2 Reference DTS/TISPAN-02011-tech Keywords 3GPP,

2、architecture, IP, service, telephony, UMTS, voice ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important noti

3、ce Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable

4、 Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on

5、 the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editoretsi.org Copyright Notification No part may be reproduced except as authorized by written permission. The copyright

6、and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2003. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being

7、registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 289 V1.1.1 (2003-11) 3 Contents Intellectual Property Rights4 Foreword.4 Introduction 4 1 Scope 5 2 References 5 3 Def

8、initions and abbreviations.5 3.1 Definitions5 3.2 Abbreviations .6 4 Creation of services from service capabilities6 4.1 Method overview6 4.1.1 TIPHON Service capabilities6 4.2 Example of a multimedia service .8 4.2.1 Operation invocation sequence for the example multimedia call .8 4.3 UMTS location

9、 service.11 4.3.1 Operation invocation sequence for the location service12 4.4 Location Based Information services .12 4.4.1 Navigation example 12 4.4.2 Operation invocation sequence for part 1 navigation example .13 4.4.3 Operation invocation sequence for part 2 of the navigation example.16 4.4.4 O

10、peration invocation sequence for part 3 of the navigation example.17 History 20 ETSI ETSI TS 102 289 V1.1.1 (2003-11) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if

11、any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available

12、 on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server)

13、 which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Project Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON). Introduction The present document uses examples to show how TIPHON serv

14、ice capabilities can be used as building blocks to synthesize complete UMTS services, both basic services and supplementary services. ETSI ETSI TS 102 289 V1.1.1 (2003-11) 5 1 Scope The present document specifies how UMTS IP Multimedia Subsystem (IMS) services can be realized using the TIPHON servic

15、e capabilities specified in TS 101 878 1 and TS 102 283 2. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication and/or edition number or version

16、number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. 1 ETSI TS 101

17、878: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Service Capability Definition; Service Capabilities for TIPHON Release 4“. 2 ETSI TS 102 283: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON); TIPHON/UMTS Harmonization; Serv

18、ice capabilities for harmonization between TIPHON and 3G UMTS“. 3 ETSI TS 122 071: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Location Services (LCS); Stage 1 (3GPP TS 22.071)“. 4 ETSI TS 101 724: “Digital cellular telecommunications sy

19、stem (Phase 2+); Location Services (LCS); Functional description; Stage 2 (3GPP TS 03.71 Release 1999)“. 5 ETSI TR 129 998-6: “Universal Mobile Telecommunications System (UMTS); Open Service Access (OSA) Application Programming Interface (API) Mapping for Open Service Access; Part 6: User Location a

20、nd User Status Service Mapping to MAP (3GPP TR 29.998-06 Release 5)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: bearer: logical association of functional entities in an IP telephony application and transport n

21、etwork which creates an end to end media flow for no longer than the duration of a call domain: collection of physical or functional entities within an administrative domain which share a consistent set of policies and common technologies end-user: entity using the services of an IP telephony servic

22、e provider or transport network operator interface: shared boundary between two communicating systems, devices or equipment IP network: packet transport network comprising one or more transport domains each employing the IP protocol IP telephony: any telephony related service that is supported on a

23、managed IP Network ETSI ETSI TS 102 289 V1.1.1 (2003-11) 6 IP telephony service provider: service provider who offers IP telephony services NOTE: The same business entity may act as both a transport network operator and an IP telephony service provider. protocol: set of semantics, syntax and procedu

24、res, which govern the exchange of information across an interface terminal: endpoint within the user equipment on which signalling and media flows originate and/or terminate ticket: obtained through the registration session, when used in a call it provides the terminal/user with a means to show a va

25、lid registration exists transport domain: collection of transport resources sharing a common set of policies, QoS mechanisms and transport technologies under the control of a transport network operator transport network: collection of transport resources, which provide IP transport functionality tra

26、nsport network operator: business entity operating a transport network user equipment: equipment under the control of an end-user user profile: service specific information about a user of a service application 3.2 Abbreviations For the purposes of the present document, the following abbreviations a

27、pply: IMS IP Multimedia Subsystem IP Internet Protocol NUL Network User Location QoS Quality of Service UMTS Universal Mobile Telecommunication System 4 Creation of services from service capabilities The flexibility of the approach taken in TIPHON to define service capabilities rather than standardi

28、zed services means that there may be many ways to construct the same potential service. The presentations of services in the present document are therefore examples that demonstrate the use of service capabilities and which do not emulate precisely the UMTS services. 4.1 Method overview 4.1.1 TIPHON

29、 Service capabilities TS 101 878 1 describes the set of TIPHON service capabilities and TS 102 283 2 proposes additional service capabilities to complete the harmonization between TIPHON and UMTS. The full range of defined and proposed TIPHON service capabilities is as follows: Call: - setup; - clea

30、r down; - re-direct; - join; - identity delivery; - set priority; ETSI ETSI TS 102 289 V1.1.1 (2003-11) 7 - interrogate; - location delivery; - set condition; - clear condition; - route. Bearer: - optimize; - create; - delete; - modify; - join; - set condition; - clear condition. Profile: - register

31、; - attach; - deregister; - detach; - authenticate; - authorize; - transfer; - set status; - get status; - set condition; - clear condition. Media: - clear media encode; - create transport; - clear transport; - set media encode. ETSI ETSI TS 102 289 V1.1.1 (2003-11) 8 Message: - create; - retrieve;

32、- delete; - set status; - get status. 4.2 Example of a multimedia service The following example shows how TIPHON service capabilities may be used to construct a multimedia call. 4.2.1 Operation invocation sequence for the example multimedia call Figure 1 shows the example multimedia call. It is impo

33、rtant to note that this example shows how a non-standardized application may use TIPHON standardized service capabilities to synthesize an example multimedia service. Note that either User may be a UMTS user. Figure 1 conforms to the UML conventions for an operation invocation sequence diagram. ETSI

34、 ETSI TS 102 289 V1.1.1 (2003-11) 9 22 ALERTING :Session :Bearer :Media :Profile 2 1 ALERTING 29 setup_Return (SessionId) T erm inating Application 20 ALERTING 23 ANSWER 30 Paths established O riginating Application :TIPHON User 1 request to setup a multimedia session to calledParty 2 authorise (reg

35、Id, service) 4 setup (calledParty, callingParty, service) 3 authorise_Return (ticket) 5 create (bearer#1) 7 setMediaEncode (media#1) 9 createTransport: (transport#1) 10 createTransport_Return ( tHandle) 8 setMedia_Return (mHandle) 6 Create_Return (bearerId) 24 ANSWER 17 route (calledParty, callingPa

36、rty, service) 1 8 setup (calledParty, c allingParty, service) 19 I/C SESSION 31 Session Close 32 cleardown (sessionId) 33 delete (bearerId) 34 clearM ediaEncoder (mHandle) 35 clearTransport (tHandle) 11 create (bearer#2) 13 setM ediaEncode (m edia#2) 15 createTransport: (transport#2) 16 createTransp

37、ort_Return ( tH andle) 14 setM edia_R eturn (m H andle) 12 Create_Return (bearerId) 36 delete (bearerId) 37 clearM ediaEncoder (mHandle) 38 clearTransport (tHandle) :TIP H O N User 25 m odify (bearer#1) 26 modify_Return (bearerId) 27 m odify (bearer#2) 28 modify_Return (bearerId) Figure 1: Example o

38、peration invocation sequence for the multimedia call ETSI ETSI TS 102 289 V1.1.1 (2003-11) 10Table 1 describes the class object invocations for the multimedia call example. The parameters that are supplied to and returned by each operation are identified. Table 1: Explanation of operation invocation

39、 sequences for an example call # Operation class Parameters Comments 1 The TIPHON/UMTS User requests a session to a given called party 2 authorize Profile user identity, service capability to be authorized 3 authorize_Return Profile authorization ticket 4 Setup Session calling user identifier, calle

40、d user identifier, session identity, service type, service provider preference, QoS service class, authorization token 5 create Bearer bearer characteristics This bearer is created for Medium#1 6 create_Return Bearer bearer identifier This bearer is created for Medium#1 7 setMediaEncode Media media

41、type, media attributes, transport characteristics This media encoder is set for Medium#1 8 setMedia_Return Media media identifier This media encoder is set for Medium#1 9 createTransport Media transport descriptor This transport is created for Medium#1 10 createTransport_Return Media transport ident

42、ifier This transport is created for Medium#1 11 create Bearer bearer characteristics This bearer is created for Medium#2 12 create_Return Bearer bearer identifier This bearer is created for Medium#2 13 setMediaEncode Media media type, media attributes, transport characteristics This media encoder is

43、 set for Medium#2 14 setMedia_Return Media media identifier This media encoder is set for Medium#2 15 createTransport Media transport descriptor This transport is created for Medium#2 16 createTransport_Return Media transport identifier This transport is created for Medium#2 17 Route Session calling

44、 user identifier, called user identifier, service provider preference, QoS service class, next network name Obtain routing for the next instance of session 18 setup Session calling user identifier, called user identifier, session identity, service type, service provider preference, QoS service class

45、, bearer information Next instance of setup 19 Terminating application informs called party terminal of an incoming session 20 Called party terminal informs the terminating application that the called user is being alerted 21 The terminating application informs the originating application that the c

46、alled user is being alerted 22 The originating application informs the calling party that the called user is being alerted ETSI ETSI TS 102 289 V1.1.1 (2003-11) 11# Operation class Parameters Comments 23 The called party answers the session and informs the terminating application 24 The terminating

47、application informs the originating application that the called user has answered. This message may include the bearer information of the called party (Note that this information may be received in Alerting message) 25 Modify Bearer Bearer characteristics (address of called party, port identity, Cod

48、ec) This modifies the original bearer#1 created, and provides the bearer information of called party to calling partys bearer class. 26 Modify_Return Bearer The bearer modify is confirmed for bearer#1 27 Modify Bearer Bearer characteristics (address of called party, port identity, Codec) This modifi

49、es the original bearer#2 created, and provides the bearer information of called party to calling partys bearer class. 28 Modify_Return Bearer The bearer modify is confirmed for bearer#2 29 setup_Return Session session identifier 30 The path is established 31 The calling party closes the session 32 cleardown Session session identifier The session for Media#1 and #2 is closed 33 delete Bearer bearer identifier The bearer for Medium#1 is deleted 34 clearMediaEncode Media media identifier The media encoder for Medium#1 is cleared 35 cl