ETSI TS 129 155-2017 LTE Traffic steering control Representational State Transfer (REST) over St reference point (V14 3 0 3GPP TS 29 155 version 14 3 0 Release 14)《长期演进技术(LTE) 交通转向.pdf

《ETSI TS 129 155-2017 LTE Traffic steering control Representational State Transfer (REST) over St reference point (V14 3 0 3GPP TS 29 155 version 14 3 0 Release 14)《长期演进技术(LTE) 交通转向.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 129 155-2017 LTE Traffic steering control Representational State Transfer (REST) over St reference point (V14 3 0 3GPP TS 29 155 version 14 3 0 Release 14)《长期演进技术(LTE) 交通转向.pdf（47页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 1TraffRepresentational State T(3GPP TS 29.1TECHNICAL SPECIFICATION129 155 V13.2.0 (2017LTE; affic steering control; e Transfer (REST) over St refe.155 version 13.2.0 Release 1317-01) ference point 13) ETSI ETSI TS 129 155 V13.2.0 (2017-01)13GPP TS 29.155 version 13.2.0 Release 13Reference R

2、TS/TSGC-0329155vd20 Keywords LTE 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 notice The present do

3、cument can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In

4、case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the doc

5、ument may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https:/

6、portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the PDF version shall not be mo

7、dified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefi

8、t of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 155 V13.2.0 (2017-01)23GPP TS 29.155 version 13.2.0 Release 1

9、3Intellectual 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 Propert

10、y 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 (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR search

11、es, 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 been produced

12、 by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference betwee

13、n GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 o

14、f the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 129 155 V13.2.0 (2017-01)33GPP TS 29.155 version 13.2.0 Release 13Contents Intellectual Property Rights 2g3Foreword

15、. 2g3Modal verbs terminology 2g3Foreword . 6g31 Scope 7g32 References 7g33 Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 St reference point . 8g34.1 Overview 8g34.2 Reference model . 8g34.3 Functional elements 9g34.3.1 TSSF . 9g34.3.2 PCRF 9g34.4 Procedures over St r

16、eference point . 9g34.4.1 General 9g34.4.2 Traffic Steering Policy Provisioning over St 9g34.4.3 Traffic Steering Rule Error Handling . 10g34.4.4 UE IPv4 address provisioning 10g35 St protocol 11g35.1 Introduction 11g35.2 Transport layer . 11g35.3 Application delivery layer 11g35.3.1 Methods 12g35.3

17、.2 Resources and URI design 12g35.3.3 HTTP request/response formats 13g35.3.3.1 General 13g35.3.3.2 POST /stapplication/sessions 14g35.3.3.3 PUT /stapplication/sessions/stsessionid 16g35.3.3.4 PATCH /stapplication/sessions/stsessionid. 17g35.3.3.5 DELETE /stapplication/sessions/stsessionid . 18g35.3

18、.3.6 GET /stapplication/sessions/stsessionid 19g35.3.3.7 POST /notificationbaseurl/stsessionid . 20g35.3.4 St session ID . 21g35.3.5 HTTP status codes 22g35.3.6 Feature negotiation . 23g35.3.6.1 General 23g35.3.7 HTTP custom headers . 23g35.3.7.1 3gpp-Optional-Features . 23g35.3.7.2 3gpp-Required-Fe

19、atures 23g35.3.7.3 3gpp-Accepted-Features . 24g35.3.7.4 3gpp-Notification-Base-URL 24g35.4 Specific application communication 24g35.4.1 General 24g35.4.2 Content type 24g35.4.3 JSON session fields 24g35.4.3.1 General 24g35.4.3.2 session-id 25g35.4.3.3 ue-ipv4 25g35.4.3.4 ue-ipv6-prefix . 25g35.4.3.5

20、 tsrules 25g3ETSI ETSI TS 129 155 V13.2.0 (2017-01)43GPP TS 29.155 version 13.2.0 Release 135.4.3.6 ts-rule-name 26g35.4.3.7 precedence 26g35.4.3.8 tdf-application-identifier . 26g35.4.3.9 flow-information . 26g35.4.3.10 flow-description 27g35.4.3.11 tos-traffic-class . 27g35.4.3.12 security-paramet

21、er-index 27g35.4.3.13 flow-label 27g35.4.3.14 flow-direction . 27g35.4.3.15 ts-policy-identifier-dl 27g35.4.3.16 ts-policy-identifier-ul 27g35.4.3.17 predefined-tsrules . 27g35.4.3.18 predefined-group-of-tsrules 28g35.4.3.19 ts-rule-base-name 28g35.4.3.20 called-station-id 28g35.4.4 JSON errors and

22、informational response fields 28g35.4.4.1 General 28g35.4.4.2 errors . 29g35.4.4.3 error-type 29g35.4.4.4 error-message 30g35.4.4.5 error-tag 30g35.4.4.6 error-path 30g35.4.4.7 error-info . 30g35.4.4.6 success-message . 30g35.4.4.7 success-path 30g35.4.4.8 success-info. 30g3The success-info field is

23、 defined as an object type. It may include any additional information under the root level of the JSON content for an informational response. . 30g35.4.5 JSON report fields 30g35.4.5.1 General 30g35.4.5.2 ts-rule-reports 31g35.4.5.3 resource-paths . 31g35.4.5.4 rule-status 31g35.4.5.5 rule-failure-c

24、ode . 31g35.4.6 JSON notification fields . 32g35.4.6.1 General 32g35.4.6.2 notifications 33g35.4.6.3 notification-type 33g35.4.6.4 notification-message . 33g35.4.6.5 notification-tag 33g35.4.6.6 notification-info 34g35.5 TSSF discovery 34g36 Secure communication . 34g3Annex A (informative): Call Flo

25、ws . 35g3A.1 General . 35g3A.2 Traffic Steering Control Information Provisioning 35g3A.3 Traffic Steering Control Information Update . 35g3A.4 Traffic Steering Control Information Removal 36g3A.5 Traffic Steering Control Notification . 37g3Annex B (normative): JSON Schema . 38g3B.1 Session body sche

26、ma 38g3B.2 Error and Informational response schema 40g3B.3 Report schema 42g3B.4 Notification schema 43g3ETSI ETSI TS 129 155 V13.2.0 (2017-01)53GPP TS 29.155 version 13.2.0 Release 13Annex C (informative): Change history . 45g3History 46g3ETSI ETSI TS 129 155 V13.2.0 (2017-01)63GPP TS 29.155 versio

27、n 13.2.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the prese

28、nt document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under chan

29、ge control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 155 V13.2.0 (2017-01)73GPP TS 29.155 version 13.2.

30、0 Release 131 Scope The present document describes the Representational State Transfer (REST) protocol-based St reference point, which is used to provision the traffic steering control information to the TSSF from the PCRF. 2 References The following documents contain provisions which, through refer

31、ence in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest vers

32、ion applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 23.203: “Policy and

33、charging control architecture“. 3 IETF RFC 793: “Transmission Control Protocol“. 4 IETF RFC 2616: “Hypertext Transfer Protocol HTTP/1.1“. 5 3GPP TS 29.201: “Representational State Transfer (REST) reference point between Application Function (AF) and Protocol Converter (PC)“. 6 IETF RFC 1786: “Unifor

34、m Resource Locators (URL)“. 7 3GPP TS 33.210: “3G security; Network Domain Security (NDS); IP network layer security“. 8 IETF RFC 1983: Internet Users Glossary“. 9 IETF RFC 3588: “Diameter Base Protocol“. 10 IETF RFC 7159: “The JavaScript Object Notation (JSON) Data Interchange Format“. 11 Void. 12

35、IETF RFC 5789: “PATCH Method for HTTP“. 13 IETF RFC 3986: “Uniform Resource Identifier (URI): Generic Syntax“. 14 IETF RFC 6902: “JavaScript Object Notation (JSON) Patch“. 15 IETF RFC 6901: “JavaScript Object Notation (JSON) Pointer“. 16 IETF draft-newton-json-content-rules-07: “A Language for Rules

36、 Describing JSON Content“. Editors note: The above document cannot be formally referenced until it is published as an RFC. 17 3GPP TS 29.212: “Policy and Charging Control (PCC); Reference points“. 18 3GPP TS 29.213: “Policy and charging control signalling flows and Quality of Service (QoS) parameter

37、 mapping“. 19 IETF RFC 2818: “HTTP Over TLS“. 20 3GPP TS 23.003: “Numbering, addressing and identification“. ETSI ETSI TS 129 155 V13.2.0 (2017-01)83GPP TS 29.155 version 13.2.0 Release 133 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definiti

38、ons given in TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. (S)Gi-LAN: The network infrastructure connected to the 3GPP network over the SGi or Gi reference point that provides various IP-base

39、d services. (S)Gi-LAN service function: A function located in the (S)Gi-LAN that provides value-added IP-based services e.g. NAT, anti-malware, parental control, DDoS protection. JSON Content Rules: JSON Content Rules (JCR), as defined in IETF draft-newton-json-content-rules 16 is a language specify

40、ing the interchange of data in JSON as defined in RFC 7159 10. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if

41、 any, in TR 21.905 1. JCR JSON Content Rules JSON JavaScript Object Notation PCRF Policy and Charging Rules Function TSSF Traffic Steering Support Function 4 St reference point 4.1 Overview The St reference point resides between the PCRF and TSSF. St reference point is used to provision the traffic

42、steering control information from the PCRF to the TSSF. 4.2 Reference model The St reference point resides between the PCRF and TSSFas depicted in figure 4.2.1. The overall PCC architecture is depicted in subclause 3a of 3GPP TS 29.213 18. TSSFg3Stg3PCRFg3Figure 4.2.1: St reference model ETSI ETSI T

43、S 129 155 V13.2.0 (2017-01)93GPP TS 29.155 version 13.2.0 Release 134.3 Functional elements 4.3.1 TSSF The TSSF is a function that receives traffic steering control information from the PCRF and ensures that the related traffic steering policy is enforced in the (S)Gi-LAN. A traffic steering policy

44、is locally configured in TSSF and can be used for uplink, downlink or for both directions. To ensure that the traffic steering policy is enforced, the TSSF performs deployment specific actions as configured for that traffic steering policy. 4.3.2 PCRF The PCRF functionality defined in 3GPP TS 23.203

45、 2 is applicable. In addition, the PCRF shall be able to make a decision of traffic steering policies used to control the steering of the subscriber“s traffic to appropriate (S)Gi-LAN service functions. NOTE: In order to allow the PCRF to select and provision an application based traffic steering po

46、licy, the reporting of detected applications to the PCRF or any other information can be used. 4.4 Procedures over St reference point 4.4.1 General The procedures which can be operated at the St interface are described in the following subclauses. 4.4.2 Traffic Steering Policy Provisioning over St W

47、hen the PCRF determines the traffic steering control information needed for the IP-CAN session; the PCRF shall send an HTTP POST message to the TSSF to create a new session resource. The PCRF shall provide the representation of the session resource within the body of the HTTP POST. Within the body o

48、f the HTTP POST, the PCRF shall provide the St Session ID, the PDN information if required by the operator policies, the UE IPv4 address and/or UE IPv6 prefix and one or more sets of traffic steering control information to the TSSF. The PCRF may modify or remove traffic steering control information

49、at any time (e.g. due to subscription change or network status change) by sending either an HTTP PUT or HTTP PATCH message to the TSSF including the St session ID within the request URL. When using an HTTP PUT to modify the session resource, the PCRF shall provide the entire state of the session resource within the body of the HTTP PUT. In this case, the TSSF shall replace the existing session information associated with this resource with the information provided in the body of the HTTP PUT. When usi