ETSI TS 129 155-2016 LTE Traffic steering control Representational State Transfer (REST) over St reference point (V13 1 0 3GPP TS 29 155 version 13 1 0 Release 13)《长期演进技术(LTE) 业务量定.pdf

1、 ETSI TS 1TraffRepresentational State T(3GPP TS 29.1TECHNICAL SPECIFICATION129 155 V13.1.0 (2016LTE; affic steering control; e Transfer (REST) over St refe.155 version 13.1.0 Release 1316-04) ference point 13) ETSI ETSI TS 129 155 V13.1.0 (2016-04)13GPP TS 29.155 version 13.1.0 Release 13Reference R

2、TS/TSGC-0329155vd10 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 http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: https:/portal.ets

6、i.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 modified wit

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

8、embers. 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.1.0 (2016-04)23GPP TS 29.155 version 13.1.0 Release 13Intellect

9、ual 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 Rights (

10、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 searches, has be

11、en 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 by ETSI 3

12、rd 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 between GSM, UMT

13、S, 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 of the ETSI

14、 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.1.0 (2016-04)33GPP TS 29.155 version 13.1.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal

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

16、oint . 8g34.4.1 General 8g34.4.2 Traffic Steering Policy Provisioning over St 8g34.4.3 Traffic Steering Rule Error Handling . 8g35 St protocol 9g35.1 Introduction 9g35.2 Transport layer . 10g35.3 Application delivery layer 10g35.3.1 Methods 11g35.3.2 Resources and URI design 11g35.3.3 HTTP request/r

17、esponse formats 12g35.3.3.1 General 12g35.3.3.2 POST /stapplication/sessions 13g35.3.3.3 PUT /stapplication/sessions/stsessionid 15g35.3.3.4 PATCH /stapplication/sessions/stsessionid. 16g35.3.3.5 DELETE /stapplication/sessions/stsessionid . 17g35.3.3.6 GET /stapplication/sessions/stsessionid 18g35.3

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

19、7.4 3gpp-Notification-Base-URL 23g35.4 Specific application communication 23g35.4.1 General 23g35.4.2 Content type 23g35.4.3 JSON session fields 23g35.4.3.1 General 23g35.4.3.2 session-id 24g35.4.3.3 ue-ipv4 24g35.4.3.4 ue-ipv6-prefix . 24g35.4.3.5 tsrules 24g35.4.3.6 ts-rule-name 25g3ETSI ETSI TS 1

20、29 155 V13.1.0 (2016-04)43GPP TS 29.155 version 13.1.0 Release 135.4.3.7 precedence 25g35.4.3.8 tdf-application-identifier . 25g35.4.3.9 flow-information . 25g35.4.3.10 flow-description 26g35.4.3.11 tos-traffic-class . 26g35.4.3.12 security-parameter-index 26g35.4.3.13 flow-label 26g35.4.3.14 flow-d

21、irection . 26g35.4.3.15 ts-policy-identifier-dl 26g35.4.3.16 ts-policy-identifier-ul 26g35.4.3.17 predefined-tsrules . 26g35.4.3.18 predefined-group-of-tsrules 27g35.4.3.19 ts-rule-base-name 27g35.4.4 JSON errors and informational response fields 27g35.4.4.1 General 27g35.4.4.2 errors . 27g35.4.4.3

22、error-type 28g35.4.4.4 error-message 28g35.4.4.5 error-tag 28g35.4.4.6 error-path 28g35.4.4.7 error-info . 28g35.4.4.6 success-message . 28g35.4.4.7 success-path 29g35.4.4.8 success-info. 29g35.4.5 JSON report fields 29g35.4.5.1 General 29g35.4.5.2 ts-rule-reports 29g35.4.5.3 resource-paths . 30g35.

23、4.5.4 rule-status 30g35.4.5.5 rule-failure-code . 30g35.4.6 JSON notification fields . 31g35.4.6.1 General 31g35.4.6.2 notifications 31g35.4.6.3 notification-type 31g35.4.6.4 notification-message . 32g35.4.6.5 notification-tag 32g35.4.6.6 notification-info 32g35.5 TSSF discovery 32g36 Secure communi

24、cation . 32g3Annex A (informative): Call Flows 33g3A.1 General . 33g3A.2 Traffic Steering Control Information Provisioning 33g3A.3 Traffic Steering Control Information Update . 33g3A.4 Traffic Steering Control Information Removal 34g3A.5 Traffic Steering Control Notification . 35g3Annex B (normative

25、): JSON Schema . 36g3B.1 Session body schema 36g3B.2 Error and Informational response schema 38g3B.3 Report schema 40g3B.4 Notification schema 41g3Annex C (informative): Change history 43g3History 44 ETSI ETSI TS 129 155 V13.1.0 (2016-04)53GPP TS 29.155 version 13.1.0 Release 13Foreword This Technic

26、al 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 present document, it will be re-released by t

27、he 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 change control. y the second digit is increm

28、ented 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.1.0 (2016-04)63GPP TS 29.155 version 13.1.0 Release 131 Scope The present document

29、 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 reference in this text, constitute provisions

30、 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 version applies. In the case of a reference

31、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 charging control architecture“. 3 IETF R

32、FC 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: “Uniform Resource Locators (URL)“. 7 3GPP TS 33

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 IETF RFC 5789: “PATCH Method for HTTP“.

34、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-05: “A Language for Rules Describing JSON Content“. Editors note:

35、 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 mapping“. 19 IETF RFC 2818:“HTTP Over T

36、LS“. ETSI ETSI TS 129 155 V13.1.0 (2016-04)73GPP TS 29.155 version 13.1.0 Release 133 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following apply. A term defined in the present document takes precedenc

37、e 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-based services. (S)Gi-LAN service function: A function located in the (S)Gi-LAN that provides value-added IP

38、-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 specifying the interchange of data in JSON as defined in RFC 7159 10. 3.2 Abbreviations For the purposes of the

39、 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 any, in TR 21.905 1. JCR JSON Content Rules JSON JavaScript Object Notation PCRF Policy and Charging Ru

40、les 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 steering control information from the PCRF to the TSSF. 4.2 Reference model The St reference point resid

41、es 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 TS 129 155 V13.1.0 (2016-04)83GPP TS 29.155 version 13.1.0 Release 134.3 Functional elements 4.3.1 TSSF T

42、he 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 is locally configured in TSSF and can be used for uplink, downlink or for both directions. To ensure tha

43、t 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 2 is applicable. In addition, the PCRF shall be able to make a decision of traffic steering policies us

44、ed 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 policy, the reporting of detected applications to the PCRF or any other information can be used. 4.4 Proce

45、dures 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 When the PCRF determines the traffic steering control information needed for the IP-CAN session; the PCRF

46、 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 of the HTTP POST, the PCRF shall provide the St Session ID, the UE IPv4 address and/or UE IPv6 prefix and

47、 one or more sets of traffic steering control information to the TSSF. The PCRF may modify or remove traffic steering control information 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

48、 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 pr

49、ovided in the body of the HTTP PUT. When using an HTTP PATCH to modify the session resource, the PCRF shall provide the modifications within the body of the HTTP PATCH as defined in subclause 5.3.3.3. In this case, the TSSF shall update the existing session resource based on the content of the body of the HTTP PATCH. In order to remove all of the traffic steering control information associated with an IP-CAN session when the IP-CAN session is terminated, the PCRF shall send to the TSSF an HTTP DELETE messa