ETSI TS 101 882-5-2003 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4 Protocol Framework Definition Part 5 Transport control service《网络上电信和_1.pdf

《ETSI TS 101 882-5-2003 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4 Protocol Framework Definition Part 5 Transport control service《网络上电信和_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 101 882-5-2003 Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4 Protocol Framework Definition Part 5 Transport control service《网络上电信和_1.pdf（47页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 101 882-5 V4.1.1 (2003-11)Technical Specification Telecommunications and Internet ProtocolHarmonization Over Networks (TIPHON) Release 4;Protocol Framework Definition;Part 5: Transport control servicefloppy3 ETSI ETSI TS 101 882-5 V4.1.1 (2003-11) 2 Reference DTS/TIPHON-03016-5R4 Keywords c

2、ontrol, interface, IP, meta-protocol, protocol, transport 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 Import

3、ant notice 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

4、Portable 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. Inform

5、ation on 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 co

6、pyright 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 currentl

7、y being 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 101 882-5 V4.1.1 (2003-11) 3 Contents Intellectual Property Rights5 Foreword.5 Introduction 5 1 Scope 6 2 Referenc

8、es 6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4 Transport control service7 4.1 Purpose.7 4.2 Description .7 4.3 Procedures 7 4.3.1 Provision/withdrawal7 4.3.2 Normal procedures7 4.3.2.1 Activation/deactivation .7 4.3.2.2 Invocation and operation.8 4.3.3 Exceptional pro

9、cedures.8 4.4 Interaction with other services or service capabilities8 4.4.1 Media control service8 4.5 Service capabilities used in service definition8 4.6 Overall behaviour.8 5 Functional entity model and information flows .9 5.1 Functional entity model9 5.1.1 Description of model 9 5.1.2 Descript

10、ion of functional entities10 5.1.2.1 Transport User.10 5.1.2.2 TFE1TRM10 5.1.2.3 TFE2ITF10 5.1.2.4 TFE3ETF.10 5.2 Information flows.10 5.2.1 Definition of information flows10 5.2.1.1 Relationship ra 10 5.2.1.1.1 TransportReserve.10 5.2.1.1.2 TransportAssign 11 5.2.1.1.3 TransportRelease .11 5.2.1.2

11、Relationship rb 12 5.2.1.2.1 AssignIngressPoint 12 5.2.1.2.2 ReleaseIngressPoint.12 5.2.1.2.3 ConnectIngressPoint12 5.2.1.3 Relationship rc 13 5.2.1.3.1 AssignEgressPoint.13 5.2.1.3.2 ReleaseEgressPoint13 5.2.2 Timers.13 5.2.2.1 Reservation hold timer 13 5.2.3 Information flow sequences14 5.2.3.1 No

12、rmal operation 14 5.2.3.2 Exceptional behaviour.16 5.3 Transport service functional entity actions.18 5.3.1 Actions of TFE1TRM18 5.3.2 Actions of TFE2ITF19 5.3.3 Actions of TFE3ETF.20 5.4 Transport control service functional entity behaviour20 5.4.1 Information flows specified as ASN.1 operations 20

13、 ETSI ETSI TS 101 882-5 V4.1.1 (2003-11) 4 5.4.2 Behaviour of TFE1TRM23 5.4.3 Behaviour of TFE2ITF.34 5.4.4 Behaviour of TFE3ETF.40 5.5 Allocation of functional entities to domains.45 Annex A (informative): Simulation and validation SDL model.46 History 47 ETSI ETSI TS 101 882-5 V4.1.1 (2003-11) 5 I

14、ntellectual 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 any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property

15、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 on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, includin

16、g 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) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has b

17、een produced by ETSI Project Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON). The present document is part 5 of a multi-part deliverable. Full details of the entire series can be found in part 1 1. Introduction The present document is a product in TIPHON Release 4 (see

18、TR 101 301) of step C of the TIPHON development process described in TR 101 835. ETSI ETSI TS 101 882-5 V4.1.1 (2003-11) 6 1 Scope The present document defines the stage 1 and stage 2 (as defined by ITU-T Recommendation I.130 6) requirements for the transport control service. 2 References The follow

19、ing 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 number) or non-specific. For a specific reference, subsequent revisions do not app

20、ly. 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 882-1: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPH

21、ON) Release 4; Protocol Framework Definition; Part 1: Meta-protocol design rules, development method, and mapping guideline“. 2 ETSI TS 101 314: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Abstract Architecture and Reference Points Definition; Network Ar

22、chitecture and Reference Points“. 3 ETSI TS 101 878: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 4; Service Capability Definition; Service Capabilities for TIPHON Release 4“. 4 ITU-T Recommendation Z.100: “Specification and description language (SDL) with c

23、orrigendum 1“. 5 ITU-T Recommendation X.680: “Information technology - Open Systems Interconnection - Abstract Syntax Notation One (ASN.1): Specification of basic notation“. 6 ITU-T Recommendation I.130: “Integrated Services Digital Network (ISDN); Method for the characterization of telecommunicatio

24、ns services supported by an ISDN and network capabilities of an ISDN“. 7 ETSI TR 101 301: “Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; Release Definition; TIPHON Release 3 Definition“. 8 ETSI TR 101 835. “Telecommunications and Internet Protocol Harmoniza

25、tion over Networks (TIPHON); Project method definition“. ETSI ETSI TS 101 882-5 V4.1.1 (2003-11) 7 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 101 878 3 apply. 3.2 Abbreviations For the purposes of the present docume

26、nt, the abbreviations given in TS 101 878 3 and the following apply: ASN.1 Abstract Syntax Notation 1 ETF Egress Transport Flow FE Functional Entity ITF Ingress Transport Flow MSC Message Sequence Chart PDU Protocol Data Unit QoS Quality of Service SDL Specification and Description Language TC Trans

27、port Control TFE Transport Functional Entity TRM Transport Resource Management TU Transport User UML Unified Modelling Language 4 Transport control service 4.1 Purpose The Transport Control (TC) service provides a means of reserving, assigning and releasing specific transport capabilities to control

28、 inter-domain transport connections. 4.2 Description The Transport Control service establishes the transport capabilities to support the IP Telephony Application plane. The TC service allows the TC service user to reserve and allocate transport resources, fulfilling specific QoS requirements and the

29、reby establish QoS specific inter-domain transport connections. Release of allocated transport resources and connections is also controlled via the TC service. 4.3 Procedures 4.3.1 Provision/withdrawal The transport control service shall be available to all transport service users in a TIPHON system

30、. 4.3.2 Normal procedures 4.3.2.1 Activation/deactivation The transport control service shall be permanently activated. ETSI ETSI TS 101 882-5 V4.1.1 (2003-11) 8 4.3.2.2 Invocation and operation The TC service shall be invoked by a transport user agent requesting reservation of a transport resource

31、with specific transport capabilities. Allocated transport resources shall be released upon request from the transport user. 4.3.3 Exceptional procedures If a transport resource reservation or activation request fails the transport user agent shall be notified. The following causes of failing to rese

32、rve requested transport resources may be reported: transport resource not available; requested transport resource not supported; previous or next domain connection address can not be identified. The activation of reserved transport resource fails if the resources have been released due to reservatio

33、n time expiration. 4.4 Interaction with other services or service capabilities In the transport layer domain TIPHON Release 4 defines the following additional service capabilities. 4.4.1 Media control service No interaction. 4.5 Service capabilities used in service definition Although not explicitly

34、 identified, aspects of the following services and service capabilities are used in definition of the transport control service: simple call service. The TIPHON Release 4 service capabilities are defined in 3. 4.6 Overall behaviour The UML activity diagram in figure 1 shows the dynamic transport ser

35、vice signalling for a TIPHON system providing transport control service. ETSI ETSI TS 101 882-5 V4.1.1 (2003-11) 9 ActivatedTransport resourcerequestActivatedTransport resourceallocation responseResource allocationfailedTransport resourcerelease requestAllocate transportresourceReject resourcealloca

36、tionTransport resourcesallocatedFigure 1: Overall behaviour of transport control service signalling 5 Functional entity model and information flows 5.1 Functional entity model 5.1.1 Description of model The functional model of the transport control service shall comprise of the following transport c

37、ontrol service functional entities: TU the Transport User that instigates the transport service request; TFE1TRMthe Transport Resource Management functional entity; TFE2ITFthe Transport Flow functional entity handling ingress connection requests; TFE3ETFthe Transport Flow functional entity handling

38、egress connection requests. The following functional relationships shall exist between these MFEs: ra between the TU and the transport resource management functional entity (TFE1TRM); rb between the transport resource management functional entity (TFE1TRM) and the ingress transport flow functional e

39、ntity (TFE2ITF); rc between the transport resource management functional entity (TFE1TRM) and the egress transport flow functional entity (TFE4ETF). ETSI ETSI TS 101 882-5 V4.1.1 (2003-11) 10TUrarbTFE2ITFTFE3ETFTFE1TRMrcFigure 2: Transport control service functional entity model 5.1.2 Description of

40、 functional entities 5.1.2.1 Transport User The TU acts on behalf of a media control entity to request or respond to reservation, allocation, or release of transport capabilities. 5.1.2.2 TFE1TRMThe transport resource management functional entity controls reservation, allocation, and release of tran

41、sport resources based on local state information. 5.1.2.3 TFE2ITFThe transport flow functional entity controlling the ingress points of the transport domain. 5.1.2.4 TFE3ETFThe transport flow functional entity controlling the egress points of the transport domain. 5.2 Information flows 5.2.1 Definit

42、ion of information flows NOTE: In the tables within this clause, the following convention is used in the “value“ columns. Un-bulleted lists of values indicate that all items in the list are included in the associated information element; bulleted lists of values indicate that only one item in the li

43、st is included in the information element. 5.2.1.1 Relationship ra 5.2.1.1.1 TransportReserve TransportReserve is a confirmed information flow that shall be sent across relationship ra from the transport user to TFE1TRMto reserve transport resource. Table 1 lists the information elements in the Tran

44、sportReserve information flow. ETSI ETSI TS 101 882-5 V4.1.1 (2003-11) 11Table 1: Contents of TransportReserve TransportReserve Information element Value Request Response BearerIdentifier Alphanumeric “handle“ M Transport QoS parameters Maximum delay, Maximum packet delay variation, Maximum mean pac

45、ket loss M O (see note1) Transport parameters qualifier - Transport QoS parameters indicate total remaining budget - Transport QoS parameters indicate budget available per domain M Traffic descriptor Media peak rate, Maximum media frame size M PreviousDomainEgressAddress (forward path) Network speci

46、fic address M NextDomainAddress Network domain address O (see note 2) UserDomainAddress Network specific address O (see note 2) Egress Point (forward path) Network specific address O(see note 3) Result - Transport resource reserved - Rejection cause - resource unavailable - destination unknown M NOT

47、E 1: This information element shall be included if the value of the transport parameters qualifier in the request is “Transport QoS parameters indicate total remaining budget“. NOTE 2: Exactly one of these information elements must be present. NOTE 3: The EgressDomainAddress shall be included if inf

48、ormation element value “result“ is “transport resource reserved“. 5.2.1.1.2 TransportAssign TransportAssign is a confirmed information flow that shall be sent across relationship ra from the transport user to TFE1TRMto allocate a reserved transport resource. Table 2 lists the information elements in

49、 the TransportAssign information flow. Table 2: Contents of TransportAssign TransportAssign Information element Value Request Response BearerIdentifier Alphanumeric “handle“ M Next Domain Egress point (backward path) Network specific address M Egress point (backward path) Network specific address O (see note) Result - Reserved Connection completed - Rejection cause - unable to complete connection M NOTE: Shall be present if result is “transport resource assigned“. 5.2.1.1.3 TransportRelease TransportRelease is an unconfirm